Subject: [rohc] RFC 4996 on RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)

From: [email-masked]
Date: Mon, 30 Jul 2007 18:03:56 -0700 (PDT)

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

        RFC 4996

        Title:      RObust Header Compression (ROHC): A 

                    Profile for TCP/IP (ROHC-TCP) 

        Author:     G. Pelletier, K. Sandlund,

                    L-E. Jonsson, M. West

        Status:     Standards Track

        Date:       July 2007

        Mailbox:    [email-masked], 

                    [email-masked], 

                    [email-masked],  [email-masked]

        Pages:      94

        Characters: 183113

        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rohc-tcp-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4996.txt

This document specifies a ROHC (Robust Header Compression) profile

for compression of TCP/IP packets.  The profile, called ROHC-TCP,

provides efficient and robust compression of TCP headers, including

frequently used TCP options such as SACK (Selective Acknowledgments)

and Timestamps.

ROHC-TCP works well when used over links with significant error rates

and long round-trip times.  For many bandwidth-limited links where

header compression is essential, such characteristics are common.  [STANDARDS TRACK]

This document is a product of the Robust Header Compression

Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 [email-masked].  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]

        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 [email-masked].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.

Submissions for Requests for Comments should be sent to

[email-masked].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...

_______________________________________________
Rohc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/rohc