Mapping the BEEP Core onto TCP

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 8
Abstract: This memo describes how a BEEP (Blocks Extensible Exchange Protocol) session is mapped onto a single TCP (Transmission Control Protocol) connection. [STANDARDS-TRACK]
Publication Date: 2001-03-01
Status Note: Proposed Standard
DOI: 10.17487/RFC3081
Link: https://doi.org/10.17487/RFC3081
Author(s): Dr. Marshall T. Rose
Keyword(s): TCP, BEEP

Latest version of IETF RFC 3081

Document Versions — IETF RFC 3081

▶ IETF RFC 3081 (2001-03-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IETF RFC 793 [Superseded*]
IETF RFC 1122 [Active*]
IETF RFC 1982 [Active*]
IETF RFC 2234 [Superseded*]
IETF RFC 3080 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3081.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 3081, Mapping the BEEP Core onto TCP. Available at https://doi.org/10.17487/RFC3081

Snippet:

IETF RFC 3081, Mapping the BEEP Core onto TCP. Available at https://doi.org/10.17487/RFC3081

HTML (ISO 690 compliant)

Preview:

IETF RFC 3081, Mapping the BEEP Core onto TCP. Available at https://doi.org/10.17487/RFC3081

Snippet:

<span class="citation"><cite>IETF RFC 3081</cite>, Mapping the BEEP Core onto TCP. Available at <a href="https://doi.org/10.17487/RFC3081" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3081</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 3081, Mapping the BEEP Core onto TCP
doi: 10.17487/RFC3081
url: https://doi.org/10.17487/RFC3081

Snippet:

<li>
<cite id="bib-rfc3081">IETF RFC 3081</cite>, Mapping the BEEP Core onto TCP
<span class="doi">10.17487/RFC3081</span>
</li>

Referenced By

IETF RFC 3080 [Active*]
IETF RFC 3195 [Active*]
IETF RFC 3760 [Active*]
IETF RFC 3983 [Active*]
IETF RFC 4744 [Active*]