Skip to main content

RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP Compression
draft-ietf-rohc-rtp-0-byte-requirements-02

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 an RFC.
Author Lars-Erik Jonsson
Last updated 2013-03-02 (Latest revision 2001-08-31)
Stream Internet Engineering Task Force (IETF)
Formats
Stream WG state (None)
Document shepherd (None)
This information refers to IESG processing after the RFC was initially published:
IESG IESG state RFC 3243 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note Responsible: Finished
Send notices to <cabo@tzi.org>, <lars-erik.jonsson@ericsson.com>
draft-ietf-rohc-rtp-0-byte-requirements-02
A new Request for Comments is now available in online RFC libraries.

        RFC 3243

        Title:      RObust Header Compression (ROHC):
                    Requirements and Assumptions for 0-byte IP/UDP/RTP
                    Compression
        Author(s):  L-E. Jonsson
        Status:     Informational
        Date:       April 2002
        Mailbox:    lars-erik.jonsson@ericsson.com
        Pages:      6
        Characters: 12451
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rohc-rtp-0-byte-requirements-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3243.txt

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.

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

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.