RFC 3081: Mapping the BEEP Core onto TCP
In plain English — editorial summary, not part of the RFC
This memo describes how a BEEP (Blocks Extensible Exchange Protocol) session is mapped onto a single TCP (Transmission Control Protocol) connection. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3081
- Published
- March 2001
- Authors
- M. Rose
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3080The Blocks Extensible Exchange Protocol CoreCurrent
March 2001
- RFC 3042Enhancing TCP's Loss Recovery Using Limited TransmitCurrent
January 2001
- RFC 2988Computing TCP's Retransmission TimerObsoleted
November 2000
- RFC 2883An Extension to the Selective Acknowledgement (SACK) Option for TCPCurrent
July 2000
- RFC 3293General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP)Current
June 2002
- RFC 2861TCP Congestion Window ValidationObsoleted
June 2000
- RFC 3347Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design ConsiderationsCurrent
July 2002
- RFC 3390Increasing TCP's Initial WindowCurrent
November 2002
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?