RFC 4163: RObust Header Compression (ROHC): Requirements on TCP/IP Header Compression
In plain English — editorial summary, not part of the RFC
This document contains requirements on the TCP/IP header compression scheme (profile) to be developed by the RObust Header Compression (ROHC) Working Group. The document discusses the scope of TCP compression, performance considerations, assumptions about the surrounding environment, as well as Intellectual Property Rights concerns. The structure of this document is inherited from RFC 3096, which defines IP/UDP/RTP requirements for ROHC. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4163
- Published
- August 2005
- Authors
- L-E. Jonsson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3979Intellectual Property Rights in IETF TechnologyObsoleted
March 2005
- RFC 3978IETF Rights in ContributionsObsoleted
March 2005
- RFC 3667IETF Rights in ContributionsObsoleted
February 2004
- RFC 4748RFC 3978 Update to Recognize the IETF TrustObsoleted
October 2006
- RFC 3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesCurrent
March 2003
- RFC 5378Rights Contributors Provide to the IETF TrustCurrent
November 2008
- RFC 2507IP Header CompressionCurrent
February 1999
- RFC 4019RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) LiteUpdated
April 2005
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?