BEEP specification, documents and related RFCs

Here is a set of RFCs which implements the BEEP protocol or makes use of it to implement a new application protocol.

• RFC3080: BEEP Core protocol definition.
  This document contains the BEEP Core protocol definition, without including its mapping into a concrete transport layer. Currently BEEP is only mapped onto TCP.
• RFC3081: BEEP Core protocol mapping onto TCP
  On this document is found how BEEP protocol is mapped on top of TCP protocol.
• RFC3117: On the Design of Application Protocols
  This document doesn't specify any standard but explains how decisions were taken to build BEEP protocol, previously called BXXP.
• RFC3195: Reliable delivery for syslog
  An standard protocol describing how to implement a reliable delivery for event messages generated by BSD syslog systems.
• RFC3349: Transient prefix identification
  A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force.
• RFC3529: A definition to perform XML-RPC
  Describes a way of using extensible markup language to perform remote procedure calling (XML-RPC) on top of BEEP.
• RFC3620: An application layer proxy for BEEP peers: TUNNEL profile
  This document defines how an application layer proxy must be implemented to provide proxy services to BEEP-enabled peers.
• RFC3767: A protocol description to provide access to user security credentials: SACRED protocol
  This document describes a protocol whereby a user can acquire cryptographic credentials (e.g., private keys, PKCS #15 structures) from a credential server.
• RFC3983 Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)
  This document specifies how to use the Blocks Extensible Exchange Protocol (BEEP) as the application transport substrate for the Internet Registry Information Service (IRIS).
• RFC4227 Using SOAP on top of BEEP
  This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol (BEEP) core. A SOAP binding describes how SOAP messages are transmitted in the network.
• RFC4324 Calendar Access Protocol (CAP)
  The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS).
• RFC4744 NETCONF over BEEP
  On this document is explained how NETCONF protocol is mapped onto BEEP.
• RFC5573 Asynchronous Channels for BEEP
  A BEEP extension to provide out of order intra-channel message delivery.

Internet drafts

Here is a set of draft being defined around BEEP at this moment:

• TARTARE profile: New BEEP profile to transport syslog
  This new BEEP profile to transport syslog is being defined to remove some limitations found at COOKED and RAW profiles, and to better accommodate with signaled syslog.
• HELD over BEEP: BEEP binding for the HELD protocol
  This internet draft describes a BEEP mapping for HELD: a protocol that allows to retrieve geo location information.
• APEX framework to historic status: Deprecating APEX framework
  Internet draft proposing APEX framework as historic RFC, assuming it hasn't been implemented, knowing that all functionality is already provided by the XMPP protocol, which is deployed and have a large community.
• CYBEX The Cybersecurity Information Exchange Framework (X.1500)
  An ITU-T standarization effort to build a framework to exchange security information.

Related documentation

• IANA BEEP: Standard track BEEP profiles registry
  Current BEEP profiles list, which are standardized, and well-defined on RFC documents and/or Internet Drafts.