RFC 3843: RObust Header Compression (ROHC): A Compression Profile for IP
In plain English — editorial summary, not part of the RFC
The original RObust Header Compression (ROHC) RFC (RFC 3095) defines a framework for header compression, along with compression protocols (profiles) for IP/UDP/RTP, IP/ESP (Encapsulating Security Payload), IP/UDP, and also a profile for uncompressed packet streams. However, no profile was defined for compression of IP only, which has been identified as a missing piece in RFC 3095. This document defines a ROHC compression profile for IP, similar to the IP/UDP profile defined by RFC 3095, but simplified to exclude UDP, and enhanced to compress IP header chains of arbitrary length. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3843
- Published
- June 2004
- Authors
- L-E. Jonsson; G. Pelletier
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 16
- Also known as
- —
- Updated by:
- RFC 4815
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 3816Definitions of Managed Objects for RObust Header Compression (ROHC)Current
June 2004
- RFC 3408Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assisted RObust Header Compression (ROHC) ProfileCurrent
December 2002
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 3241Robust Header Compression (ROHC) over PPPUpdated
May 2002
- RFC 3095RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressedUpdated
July 2001
- RFC 3409Lower Layer Guidelines for Robust RTP/UDP/IP Header CompressionCurrent
December 2002
- RFC 5225RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-LiteCurrent
April 2008
- RFC 5856Integration of Robust Header Compression over IPsec Security AssociationsCurrent
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?