RFC 3080: The Blocks Extensible Exchange Protocol Core
In plain English — editorial summary, not part of the RFC
This memo describes a generic application protocol kernel for connection-oriented, asynchronous interactions called the BEEP (Blocks Extensible Exchange Protocol) core. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3080
- Published
- March 2001
- Authors
- M. Rose
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 58
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3081Mapping the BEEP Core onto TCPCurrent
March 2001
- RFC 3117On the Design of Application ProtocolsCurrent
November 2001
- RFC 3529Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)Updated
April 2003
- RFC 3620The TUNNEL ProfileUpdated
October 2003
- RFC 3767Securely Available Credentials ProtocolUpdated
June 2004
- RFC 2310The Safe Response Header FieldCurrent
April 1998
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2112The MIME Multipart/Related Content-typeObsoleted
March 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?