RFC 6260: Compressed Bundle Header Encoding (CBHE)
In plain English — editorial summary, not part of the RFC
This document describes a convention by which Delay-Tolerant Networking (DTN) Bundle Protocol (BP) "convergence-layer" adapters may represent endpoint identifiers in a compressed form within the primary blocks of bundles, provided those endpoint identifiers conform to the structure prescribed by this convention. Compressed Bundle Header Encoding (CBHE) compression is a convergence-layer adaptation. It is opaque to bundle processing. Therefore, it has no impact on the interoperability of different Bundle Protocol implementations, but instead affects only the interoperability of different convergence-layer adaptation implementations. This document is a product of the Delay-Tolerant Networking Research Group and has been reviewed by that group. No objections to its publication as an RFC were raised. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6260
- Published
- May 2011
- Authors
- S. Burleigh
- Status
- EXPERIMENTAL
- Stream
- IRTF
- Area
- —
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 9758
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6259Delay-Tolerant Networking Previous-Hop Insertion BlockCurrent
May 2011
- RFC 6258Delay-Tolerant Networking Metadata Extension BlockCurrent
May 2011
- RFC 6256Using Self-Delimiting Numeric Values in ProtocolsCurrent
May 2011
- RFC 6255Delay-Tolerant Networking Bundle Protocol IANA RegistriesCurrent
May 2011
- RFC 6693Probabilistic Routing Protocol for Intermittently Connected NetworksCurrent
August 2012
- RFC 5050Bundle Protocol SpecificationCurrent
November 2007
- RFC 9171Bundle Protocol Version 7Updated
January 2022
- RFC 9675Delay-Tolerant Networking Management Architecture (DTNMA)Current
November 2024
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?