RFC 3408: Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assisted RObust Header Compression (ROHC) Profile
In plain English — editorial summary, not part of the RFC
This document defines an additional mode of the link-layer assisted RObust Header Compression (ROHC) profile, also known as the zero-byte profile, beyond the two defined in RFC 3242. Zero-byte header compression exists in order to prevent the single-octet ROHC header from pushing a packet voice stream into the next higher fixed packet size for the radio. It is usable in certain widely deployed older air interfaces. This document adds the zero-byte operation for ROHC Bidirectional Reliable mode (R-mode) to the ones specified for Unidirectional (U-mode) and Bidirectional Optimistic (O-mode) modes of header compression in RFC 3242. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3408
- Published
- December 2002
- Authors
- Z. Liu; K. Le
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 3816Definitions of Managed Objects for RObust Header Compression (ROHC)Current
June 2004
- RFC 3843RObust Header Compression (ROHC): A Compression Profile for IPUpdated
June 2004
- 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?