0MQ Requests for Comments

26/CurveZMQ Authentication and Encryption Protocol - Raw
This document describes CurveZMQ, a protocol for secure messaging across the Internet. CurveZMQ is closely based on Daniel J. Bernstein's CurveCP, adapted for use in ZeroMQ over TCP. The curvecp.org site acts as a primary reference for CurveCP and is foundation material for this document. A reference implementation of CurveZMQ is provided at curvezmq.org. This document describes version 1.0 of CurveZMQ. (27 Apr 2013 12:25)

25/ZMTP CURVE Security Mechanism - Raw
The ZMTP CURVE mechanism provides secure authentication and confidentiality for ZMTP 3.0. This mechanism implements the CurveZMQ security protocol. It is intended for use on public networks where security requirements are high. (08 Apr 2013 15:20)

24/ZMTP PLAIN Security Mechanism - Raw
The ZMTP PLAIN mechanism defines a simple username/password mechanism for ZMTP 3.0 that lets a server authenticate a client. PLAIN makes no attempt at security or confidentiality. It is intended for use on internal networks where security requirements are low. (08 Apr 2013 11:28)

14/WMP - Worker-Manager Protocol - Raw
Worker-Manager Protocol is a generalization of request-reply pattern, allowing many workers talk to many managers (servers) with intermediate devices and custom load-balancing. This paper is a rather brief description of protocol, it lacks details and is not complete. I will do my best to finish it and to provide a reference implementation as soon as possible. (30 Jun 2011 08:45)

27/ZAP - ZeroMQ Authentication Protocol - Draft
This document specifies ZAP, the ZeroMQ Authentication Protocol. The use case for ZAP is a set of servers that need authentication of remote clients, and which talk to an handler that checks client credentials. ZAP defines how the servers connect to the handler, and the messages they exchange. (19 May 2013 09:08)

23/ZMTP - ZeroMQ Message Transport Protocol - Draft
The ZeroMQ Message Transport Protocol (ZMTP) is a transport layer protocol for exchanging messages between two peers over a connected transport layer such as TCP. This document describes ZMTP 3.0. The major change in this version is the addition of security mechanisms and the removal of hard-coded connection metadata (socket type and identity) from the greeting. (08 Apr 2013 11:27)

22/Collective Code Construction Contract (C4.1) - Draft
The Collective Code Construction Contract (C4) is an evolution of the github.com Fork + Pull Model, aimed at providing an optimal collaboration model for free software projects. This is revision 1 of the C4 specification. (20 Mar 2013 17:58)

21/CLASS - C Language Style for Scalability - Draft
The C Language Style for Scalability (CLASS) defines a consistent style and organization for scalable C library and application code built on modern C compilers and operating systems. CLASS aims to collect industry best practice into one reusable standard. (16 Jan 2013 19:55)

20/ZRE - ZeroMQ Realtime Exchange Protocol - Draft
The ZeroMQ Realtime Exchange Protocol (ZRE) governs how a group of peers on a network discover each other, organize into groups, and send each other events. ZRE runs over the ZeroMQ ZMTP protocol. (22 Nov 2012 15:59)

18/MDP - Majordomo Protocol 0.2 - Draft
The Majordomo Protocol (MDP) defines a reliable service-oriented request-reply dialog between a set of client applications, a broker and a set of worker applications. MDP covers presence, heartbeating, and service-oriented request-reply processing. It originated from the Majordomo pattern defined in Chapter 4 of the Guide. This is MDP version 0.2, which adds support for multiple replies for a single request. (04 Aug 2012 02:45)

17/ZDCF - ZeroMQ Device Configuration File - Draft
The ZeroMQ Device Configuration File (ZDCF) specifies a standard language for configuring 0MQ devices. It provides information to configure a 0MQ context, and a set of 0MQ sockets. This specification aims to make it easier to build, share, and reuse 0MQ devices and build systems for device administration. (21 Mar 2012 07:04)

15/ZMTP - ZeroMQ Message Transport Protocol - Draft
The ZeroMQ Message Transport Protocol (ZMTP) is a transport layer protocol for exchanging messages between two peers over a connected transport layer such as TCP. This document describes ZMTP/2.0. (14 Jul 2011 12:02)

12/CHP - Clustered Hashmap Protocol - Draft
The Clustered Hashmap Protocol (CHP) defines a cluster-wide key-value hashmap, and mechanisms for sharing this across a set of clients. CHP allows clients to work with subtrees of the hashmap, to update values, and to define ephemeral values. CHP originated from the Clone pattern defined in Chapter 5 of the Guide. (16 Apr 2011 12:18)

11/MTL - Message Transfer Layer - Draft
This document proposes a Message Transport Layer (MTL), a connection-oriented protocol that supports broker-based messaging. MTL connects a set of clients with a central message broker, allowing clients to issue commands to the broker, send messages to the broker, and receive messages back from the broker. (06 Apr 2011 10:44)

10/FLP - Freelance Protocol - Draft
The Freelance Protocol (FLP) defines brokerless reliable request-reply dialogs across an N-to-N network of clients and servers. It originated in Chapter 4 of the Guide. (13 Mar 2011 06:33)

9/TSP - Titanic Service Protocol - Draft
The Titanic Service Protocol (SP) defines a set of services, requests, and replies that implement the Titanic pattern for disconnected persistent messaging across a network of arbitrarily connected clients and workers. (08 Mar 2011 17:21)

8/MMI - Majordomo Management Interface - Draft
The Majordomo Management Interface (MMI) defines a namespace and set of management services that MDP brokers may provide. MMI is layered on top of the 7/MDP protocol. (05 Mar 2011 12:41)

6/PPP - Paranoid Pirate Protocol - Draft
The Paranoid Pirate Protocol (PPP) defines a reliable request-reply dialog between a client (or client) and a worker peer. PPP covers presence, heartbeating, and request-reply processing. It originated in Chapter 4 of the Guide. (28 Feb 2011 16:31)

5/ZDCF - ZeroMQ Device Configuration File - Draft
The ZeroMQ Device Configuration File (ZDCF) specifies a standard language for configuring 0MQ devices. It provides information to configure a 0MQ context, and a set of 0MQ sockets. This specification aims to make it easier to build, share, and reuse 0MQ devices and build systems for device administration. (09 Feb 2011 11:44)

19/FILEMQ - File Message Queuing Protocol - Stable
The File Message Queuing Protocol (FILEMQ) governs the delivery of files between a 'client' and a 'server'. FILEMQ runs over the ZeroMQ ZMTP protocol. (22 Sep 2012 08:21)

16/Collective Code Construction Contract (C4) - Stable
The Collective Code Construction Contract (C4) is an evolution of the github.com Fork + Pull Model, aimed at providing an optimal collaboration model for free software projects. C4 is derived from the ZeroMQ contribution policy of early 2012. (18 Mar 2012 20:18)

13/ZMTP - ZeroMQ Message Transport Protocol - Stable
The ZeroMQ Message Transport Protocol (ZMTP) is a transport layer protocol for exchanging messages between two peers over a connected transport layer such as TCP. This document describes ZMTP/1.0 as implemented by the 0MQ/2.x generation of software. (30 Apr 2011 12:15)

7/MDP - Majordomo Protocol - Stable
The Majordomo Protocol (MDP) defines a reliable service-oriented request-reply dialog between a set of client applications, a broker and a set of worker applications. MDP covers presence, heartbeating, and service-oriented request-reply processing. It originated from the Majordomo pattern defined in Chapter 4 of the Guide. (28 Feb 2011 20:57)

4/ZPL - ZeroMQ Property Language - Stable
The ZeroMQ Property Language (ZPL) defines a minimalistic framing language for specifying property sets, expressed as a hierarchy of name-value property pairs. (24 Aug 2010 12:11)