RFC 5857 on IKEv2 Extensions to Support Robust Header Compression over IPsec
[email protected] Fri, 14 May 2010 16:07:19 -0700 (PDT)
| Newsgroups | gmane.ietf.rohc |
|---|---|
| Message-ID | <[email protected]> |
A new Request for Comments is now available in online RFC libraries.
RFC 5857
Title: IKEv2 Extensions to Support Robust
Header Compression over IPsec
Author: E. Ertekin, C. Christou,
R. Jasani, T. Kivinen,
C. Bormann
Status: Standards Track
Stream: IETF
Date: May 2010
Mailbox: [email protected],
[email protected],
[email protected], [email protected],
[email protected]
Pages: 13
Characters: 27063
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rohc-ikev2-extensions-hcoipsec-12.txt
URL: http://www.rfc-editor.org/rfc/rfc5857.txt
In order to integrate Robust Header Compression (ROHC) with IPsec, a
mechanism is needed to signal ROHC channel parameters between
endpoints. Internet Key Exchange (IKE) is a mechanism that can be
leveraged to exchange these parameters. This document specifies
extensions to IKEv2 that will allow ROHC and its associated channel
parameters to be signaled for IPsec Security Associations (SAs).
[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-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 protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC