RFC 5795: The RObust Header Compression (ROHC) Framework
In plain English — editorial summary, not part of the RFC
The Robust Header Compression (ROHC) protocol provides an efficient, flexible, and future-proof header compression concept. It is designed to operate efficiently and robustly over various link technologies with different characteristics. The ROHC framework, along with a set of compression profiles, was initially defined in RFC 3095. To improve and simplify the ROHC specifications, this document explicitly defines the ROHC framework and the profile for uncompressed separately. More specifically, the definition of the framework does not modify or update the definition of the framework specified by RFC 3095. This specification obsoletes RFC 4995. It fixes one interoperability issue that was erroneously introduced in RFC 4995, and adds some minor clarifications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5795
- Published
- March 2010
- Authors
- K. Sandlund; G. Pelletier; L-E. Jonsson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 41
- Also known as
- —
- Obsoletes:
- RFC 4995
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5780NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)Updated
May 2010
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 5769Test Vectors for Session Traversal Utilities for NAT (STUN)Current
April 2010
- RFC 5766Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Obsoleted
April 2010
- RFC 5762RTP and the Datagram Congestion Control Protocol (DCCP)Updated
April 2010
- RFC 5740NACK-Oriented Reliable Multicast (NORM) Transport ProtocolCurrent
November 2009
- RFC 5856Integration of Robust Header Compression over IPsec Security AssociationsCurrent
May 2010
- RFC 5857IKEv2 Extensions to Support Robust Header Compression over IPsecCurrent
May 2010
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?