RFC 4362: RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP
In plain English — editorial summary, not part of the RFC
This document defines a ROHC (Robust Header Compression) profile for compression of IP/UDP/RTP (Internet Protocol/User Datagram Protocol/Real-Time Transport Protocol) packets, utilizing functionality provided by the lower layers to increase compression efficiency by completely eliminating the header for most packets during optimal operation. The profile is built as an extension to the ROHC RTP profile. It defines additional mechanisms needed in ROHC, states requirements on the assisting layer to guarantee transparency, and specifies general logic for compression and decompression related to the usage of the header-free packet format. This document is a replacement for RFC 3242, which it obsoletes. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4362
- Published
- January 2006
- Authors
- L-E. Jonsson; G. Pelletier; K. Sandlund
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 23
- Also known as
- —
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 2508Compressing IP/UDP/RTP Headers for Low-Speed Serial LinksCurrent
February 1999
- RFC 4019RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) LiteUpdated
April 2005
- RFC 3095RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressedUpdated
July 2001
- RFC 2454IP Version 6 Management Information Base for the User Datagram ProtocolObsoleted
December 1998
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
- RFC 4654TCP-Friendly Multicast Congestion Control (TFMCC): Protocol SpecificationCurrent
August 2006
- RFC 3753Mobility Related TerminologyCurrent
June 2004
- RFC 3738Wave and Equation Based Rate Control (WEBRC) Building BlockCurrent
April 2004
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?