RFC 4995: The RObust Header Compression (ROHC) Framework
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5795.
Current version: 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4995
- Published
- July 2007
- Authors
- L-E. Jonsson; G. Pelletier; K. Sandlund
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 40
- Also known as
- —
- Obsoleted by:
- RFC 5795
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 4996RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)Obsoleted
July 2007
- RFC 4997Formal Notation for RObust Header Compression (ROHC-FN)Current
July 2007
- RFC 5040A Remote Direct Memory Access Protocol SpecificationUpdated
October 2007
- RFC 5041Direct Data Placement over Reliable TransportsUpdated
October 2007
- RFC 5042Direct Data Placement Protocol (DDP) / Remote Direct Memory Access Protocol (RDMAP) SecurityUpdated
October 2007
- RFC 5043Stream Control Transmission Protocol (SCTP) Direct Data Placement (DDP) AdaptationUpdated
October 2007
- RFC 5044Marker PDU Aligned Framing for TCP SpecificationUpdated
October 2007
- RFC 5045Applicability of Remote Direct Memory Access Protocol (RDMA) and Direct Data Placement (DDP)Updated
October 2007
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?