RFC 3243: RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP Compression
In plain English — editorial summary, not part of the RFC
This document contains requirements for the 0-byte IP/UDP/RTP (Internet Protocol/User Datagram Protocol/Real-Time Transport Protocol) header compression scheme to be developed by the Robust Header Compression (ROHC) Working Group. It also includes the basic assumptions for the typical link layers over which 0-byte compression may be implemented, and assumptions about its usage in general.
Document record
- Document ID
- RFC3243
- Published
- April 2002
- Authors
- L-E. Jonsson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3096Requirements for robust IP/UDP/RTP header compressionCurrent
July 2001
- RFC 3759RObust Header Compression (ROHC): Terminology and Channel Mapping ExamplesCurrent
April 2004
- RFC 2147TCP and UDP over IPv6 JumbogramsObsoleted
May 1997
- RFC 2767Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)Obsoleted
February 2000
- RFC 2395IP Payload Compression Using LZSCurrent
December 1998
- RFC 2394IP Payload Compression Using DEFLATECurrent
December 1998
- RFC 2393IP Payload Compression Protocol (IPComp)Obsoleted
December 1998
- RFC 2354Options for Repair of Streaming MediaCurrent
June 1998
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?