[rohc] RFC 5857 on IKEv2 Extensions to Support Robust Header Compression over IPsec

rfc-editor@rfc-editor.org Fri, 14 May 2010 23:07 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0F423A68AB; Fri, 14 May 2010 16:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[AWL=0.209, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boFdbAEYf6MG; Fri, 14 May 2010 16:07:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id B72703A68F6; Fri, 14 May 2010 16:07:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1555AE0674; Fri, 14 May 2010 16:07:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100514230719.1555AE0674@rfc-editor.org>
Date: Fri, 14 May 2010 16:07:19 -0700 (PDT)
Cc: rohc@ietf.org, rfc-editor@rfc-editor.org
Subject: [rohc] RFC 5857 on IKEv2 Extensions to Support Robust Header Compression over IPsec
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 23:07:29 -0000

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:    ertekin_emre@bah.com, 
                    christou_chris@bah.com, 
                    ro@breakcheck.com,  kivinen@iki.fi, 
                    cabo@tzi.org
        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 rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC