Subject: [rohc] RFC 5856 on Integration of Robust Header Compression over IPsec Security Associations

From: [email-masked]
Date: Fri, 14 May 2010 16:07:07 -0700 (PDT)

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

        RFC 5856

        Title:      Integration of Robust Header Compression 
                    over IPsec Security Associations 
        Author:     E. Ertekin, R. Jasani,
                    C. Christou, C. Bormann
        Status:     Informational
        Stream:     IETF
        Date:       May 2010
        Mailbox:    [email-masked], 
                    [email-masked], 
                    [email-masked],  [email-masked]
        Pages:      15
        Characters: 34548
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rohc-hcoipsec-13.txt

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

IP Security (IPsec) provides various security services for IP
traffic.  However, the benefits of IPsec come at the cost of
increased overhead.  This document outlines a framework for
integrating Robust Header Compression (ROHC) over IPsec (ROHCoIPsec).
By compressing the inner headers of IP packets, ROHCoIPsec proposes
to reduce the amount of overhead associated with the transmission of
traffic over IPsec Security Associations (SAs).  This document is not an 
Internet Standards Track specification; it is published for informational 
purposes.

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

INFORMATIONAL: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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.

The RFC Editor Team
Association Management Solutions, LLC