Skip to main content

RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3242.
Authors Lars-Erik Jonsson , Ghyslain Pelletier
Last updated 2013-03-02 (Latest revision 2001-11-09)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3242 (Proposed Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note
Send notices to <>, <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3242

        Title:      RObust Header Compression (ROHC):
                    A Link-Layer Assisted Profile for IP/UDP/RTP
        Author(s):  L-E. Jonsson, G. Pelletier
        Status:     Standards Track
        Date:       April 2002
        Pages:      21
        Characters: 49007
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rohc-rtp-lla-03.txt


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 making
use of this header-free packet.

This document is a product of the Robust Header Compression Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.