RFC 4224 on RObust Header Compression (ROHC): ROHC over Channels That Can Reorder Packets

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.


        RFC 4224

        Title:      RObust Header Compression (ROHC):
                    ROHC over Channels That Can Reorder Packets
        Author(s):  G. Pelletier, L-E. Jonsson, K. Sandlund
        Status:     Informational
        Date:       January 2006
        Mailbox:    ghyslain.pelletier@ericsson.com,
                    lars-erik.jonsson@ericsson.com,
                    kristofer.sandlund@ericsson.com
        Pages:      21
        Characters: 49416
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rohc-over-reordering-03.txt

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


RObust Header Compression (ROHC), RFC 3095, defines a framework for
header compression, along with a number of compression protocols
(profiles).  One operating assumption for the profiles defined in RFC
3095 is that the channel between compressor and decompressor is
required to maintain packet ordering.  This document discusses aspects
of using ROHC over channels that can reorder packets.  It provides
guidelines on how to implement existing profiles over such channels,
as well as suggestions for the design of new profiles.

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.

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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc4224.txt>
_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux