draft-ietf-rohc-ikev2-extensions-hcoipsec-11.txt   draft-ietf-rohc-ikev2-extensions-hcoipsec-12.txt 
Network Working Group E. Ertekin Network Working Group E. Ertekin
Internet-Draft C. Christou Internet-Draft C. Christou
Intended status: Standards Track R. Jasani Intended status: Standards Track R. Jasani
Expires: August 6, 2010 Booz Allen Hamilton Expires: August 19, 2010 Booz Allen Hamilton
T. Kivinen T. Kivinen
Safenet, Inc. Safenet, Inc.
C. Bormann C. Bormann
Universitaet Bremen TZI Universitaet Bremen TZI
February 2, 2010 February 15, 2010
IKEv2 Extensions to Support Robust Header Compression over IPsec IKEv2 Extensions to Support Robust Header Compression over IPsec
draft-ietf-rohc-ikev2-extensions-hcoipsec-11 draft-ietf-rohc-ikev2-extensions-hcoipsec-12
Abstract Abstract
In order to integrate Robust Header Compression (ROHC) with IPsec, a In order to integrate Robust Header Compression (ROHC) with IPsec, a
mechanism is needed to signal ROHC channel parameters between end- mechanism is needed to signal ROHC channel parameters between end-
points. Internet Key Exchange (IKE) is a mechanism which can be points. Internet Key Exchange (IKE) is a mechanism which can be
leveraged to exchange these parameters. This document specifies leveraged to exchange these parameters. This document specifies
extensions to IKEv2 that will allow ROHC and its associated channel extensions to IKEv2 that will allow ROHC and its associated channel
parameters to be signaled for IPsec security associations (SAs). parameters to be signaled for IPsec security associations (SAs).
skipping to change at page 1, line 46 skipping to change at page 1, line 46
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 6, 2010. This Internet-Draft will expire on August 19, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 3, line 7 skipping to change at page 3, line 7
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. ROHC Channel Initialization for ROHCoIPsec . . . . . . . . . . 4 3. ROHC Channel Initialization for ROHCoIPsec . . . . . . . . . . 3
3.1. ROHC_SUPPORTED Notify Message . . . . . . . . . . . . . . 4 3.1. ROHC_SUPPORTED Notify Message . . . . . . . . . . . . . . 3
3.1.1. ROHC Attributes . . . . . . . . . . . . . . . . . . . 6 3.1.1. ROHC Attributes . . . . . . . . . . . . . . . . . . . 5
3.1.2. ROHC Attribute Types . . . . . . . . . . . . . . . . . 7 3.1.2. ROHC Attribute Types . . . . . . . . . . . . . . . . . 6
3.2. ROHC Channel Parameters that are Implicitly Set . . . . . 9 3.2. ROHC Channel Parameters that are Implicitly Set . . . . . 8
4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . 12 7.2. Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
Increased packet header overhead due to IPsec [IPSEC] can result in Increased packet header overhead due to IPsec [IPSEC] can result in
the inefficient utilization of bandwidth. Coupling ROHC [ROHC] with the inefficient utilization of bandwidth. Coupling ROHC [ROHC] with
IPsec offers an efficient way to transfer protected IP traffic. IPsec offers an efficient way to transfer protected IP traffic.
ROHCoIPsec [ROHCOIPSEC] requires configuration parameters to be ROHCoIPsec [ROHCOIPSEC] requires configuration parameters to be
initialized at the compressor and decompressor. Current initialized at the compressor and decompressor. Current
specifications for hop-by-hop ROHC negotiate these parameters through specifications for hop-by-hop ROHC negotiate these parameters through
skipping to change at page 7, line 20 skipping to change at page 7, line 20
3.1.2. ROHC Attribute Types 3.1.2. ROHC Attribute Types
This section describes five ROHC Attribute Types: MAX_CID, This section describes five ROHC Attribute Types: MAX_CID,
ROHC_PROFILE, ROHC_INTEG, ROHC_ICV_LEN, and MRRU. The value ROHC_PROFILE, ROHC_INTEG, ROHC_ICV_LEN, and MRRU. The value
allocated for each ROHC Attribute Type is specified in Section 4. allocated for each ROHC Attribute Type is specified in Section 4.
MAX_CID (Maximum Context Identifier, AF = 1) MAX_CID (Maximum Context Identifier, AF = 1)
The MAX_CID attribute is a mandatory attribute. Exactly one The MAX_CID attribute is a mandatory attribute. Exactly one
MAX_CID attribute MUST be sent. The MAX_CID field indicates the MAX_CID attribute MUST be sent. The MAX_CID field indicates the
maximum value of a context Identifier supported by the ROHCoIPsec maximum value of a context identifier supported by the ROHCoIPsec
decompressor. This attribute value is two octets in length. The decompressor. This attribute value is two octets in length. The
range of values for MAX_CID MUST be at least 0 and at most 16383 range of values for MAX_CID MUST be at least 0 and at most 16383.
(the value 0 implies having one context). The recipient of the Since CIDs can take values between 0 and MAX_CID, the actual
MAX_CID Attribute MUST only use up to MAX_CID context identifiers number of contexts that can be used are MAX_CID+1. If MAX_CID is
for compression. 0, this implies having one context. The recipient of the MAX_CID
Attribute MUST only use up to MAX_CID context identifiers for
compression.
Note that the MAX_CID parameter is a one-way notification (i.e., Note that the MAX_CID parameter is a one-way notification (i.e.,
the sender of the attribute indicates what it can handle to the the sender of the attribute indicates what it can handle to the
other end); therefore, different values for MAX_CID may be other end); therefore, different values for MAX_CID may be
announced in each direction. announced in each direction.
ROHC_PROFILE (ROHC Profile, AF = 1) ROHC_PROFILE (ROHC Profile, AF = 1)
The ROHC_PROFILE attribute is a mandatory attribute. Each The ROHC_PROFILE attribute is a mandatory attribute. Each
ROHC_PROFILE attribute has a fixed length of 4 octets, and its ROHC_PROFILE attribute has a fixed length of 4 octets, and its
attribute value is a two-octet long ROHC Profile Identifier attribute value is a two-octet long ROHC Profile Identifier
 End of changes. 8 change blocks. 
20 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/