RFC 4996: RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6846.
Current version: RFC 6846 — RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)
In plain English — editorial summary, not part of the RFC
This document specifies a ROHC (Robust Header Compression) profile for compression of TCP/IP packets. The profile, called ROHC-TCP, provides efficient and robust compression of TCP headers, including frequently used TCP options such as SACK (Selective Acknowledgments) and Timestamps. ROHC-TCP works well when used over links with significant error rates and long round-trip times. For many bandwidth-limited links where header compression is essential, such characteristics are common. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4996
- Published
- July 2007
- Authors
- G. Pelletier; K. Sandlund; L-E. Jonsson; M. West
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 94
- Also known as
- —
- Obsoleted by:
- RFC 6846
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 4997Formal Notation for RObust Header Compression (ROHC-FN)Current
July 2007
- RFC 4995The RObust Header Compression (ROHC) FrameworkObsoleted
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?