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

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:    ghyslain.pelletierericsson.com, 
                    kristofer.sandlundericsson.com, 
                    lars-eriklejonsson.com, 
mark.a.westroke.co.uk
        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 IETF-REQUESTIETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list
should
be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained
by sending
an EMAIL message to rfc-infoRFC-EDITOR.ORG with the
message body 

help: ways_to_get_rfcs. For example:

        To: rfc-infoRFC-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-ManagerRFC-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-EDITORRFC-EDITOR.ORG.  Please consult RFC 2223,
Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
rfc-dist mailing list
rfc-distmailman.rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org