draft-ietf-rohc-ikev2-extensions-hcoipsec-10.txt   draft-ietf-rohc-ikev2-extensions-hcoipsec-11.txt 
Network Working Group E. Ertekin Network Working Group E. Ertekin
Internet-Draft C. Christou Internet-Draft C. Christou
Expires: June 7, 2010 R. Jasani Intended status: Standards Track R. Jasani
Booz Allen Hamilton Expires: August 6, 2010 Booz Allen Hamilton
T. Kivinen T. Kivinen
Safenet, Inc. Safenet, Inc.
C. Bormann C. Bormann
Universitaet Bremen TZI Universitaet Bremen TZI
December 4, 2009 February 2, 2010
IKEv2 Extensions to Support Robust Header Compression over IPsec IKEv2 Extensions to Support Robust Header Compression over IPsec
(ROHCoIPsec) draft-ietf-rohc-ikev2-extensions-hcoipsec-11
draft-ietf-rohc-ikev2-extensions-hcoipsec-10
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 47 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 June 7, 2010. This Internet-Draft will expire on August 6, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 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
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. ROHC Channel Initialization for ROHCoIPsec . . . . . . . . . . 3 3. ROHC Channel Initialization for ROHCoIPsec . . . . . . . . . . 4
3.1. ROHC_SUPPORTED Notify Message . . . . . . . . . . . . . . 3 3.1. ROHC_SUPPORTED Notify Message . . . . . . . . . . . . . . 4
3.1.1. ROHC Attributes . . . . . . . . . . . . . . . . . . . 5 3.1.1. ROHC Attributes . . . . . . . . . . . . . . . . . . . 6
3.1.2. ROHC Attribute Types . . . . . . . . . . . . . . . . . 6 3.1.2. ROHC Attribute Types . . . . . . . . . . . . . . . . . 7
3.2. ROHC Channel Parameters that are Implicitly Set . . . . . 8 3.2. ROHC Channel Parameters that are Implicitly Set . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 10 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . 11 7.2. Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
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 4, line 34 skipping to change at page 4, line 34
document are to be interpreted as described in RFC 2119 [BRA97]. document are to be interpreted as described in RFC 2119 [BRA97].
3. ROHC Channel Initialization for ROHCoIPsec 3. ROHC Channel Initialization for ROHCoIPsec
The following subsections define extensions to IKEv2 which enables an The following subsections define extensions to IKEv2 which enables an
initiator and a responder to signal parameters required to establish initiator and a responder to signal parameters required to establish
a ROHC channel for a ROHCoIPsec session. a ROHC channel for a ROHCoIPsec session.
3.1. ROHC_SUPPORTED Notify Message 3.1. ROHC_SUPPORTED Notify Message
ROHC channel parameters MUST be signaled at either the establishment ROHC channel parameters MUST be signaled separately for each ROHC-
or rekeying of a Child SA. Specifically, a new Notify message type enabled IPsec SA. Specifically, a new Notify message type MUST be
is used during the IKE_AUTH and CREATE_CHILD_SA exchanges to convey included in the IKE_AUTH and CREATE_CHILD_SA exchanges whenever a new
these parameters. ROHC-enabled IPsec SA is created, or an existing one is rekeyed.
The Notify payload sent by the initiator MUST contain the channel The Notify payload sent by the initiator MUST contain the channel
parameters for the ROHC session. These parameters indicate the parameters for the ROHC session. These parameters indicate the
capabilities of the ROHC decompressor at the initiator. Upon receipt capabilities of the ROHC decompressor at the initiator. Upon receipt
of the initiator's request, the responder will either ignore the of the initiator's request, the responder will either ignore the
payload (if it doesn't support ROHC or the proposed parameters) or payload (if it doesn't support ROHC or the proposed parameters) or
respond with a Notify payload that contains its own ROHC channel respond with a Notify payload that contains its own ROHC channel
parameters. parameters.
Note that only one Notify payload is used to convey ROHC parameters. Note that only one Notify payload is used to convey ROHC parameters.
skipping to change at page 6, line 27 skipping to change at page 6, line 27
3.1.1. ROHC Attributes 3.1.1. ROHC Attributes
The ROHC_SUPPORTED Notify message is used to signal channel The ROHC_SUPPORTED Notify message is used to signal channel
parameters between ROHCoIPsec compressor and decompressor. The parameters between ROHCoIPsec compressor and decompressor. The
message contains a list of "ROHC Attributes" which contain the message contains a list of "ROHC Attributes" which contain the
parameters required for the ROHCoIPsec session. parameters required for the ROHCoIPsec session.
The format for signaling ROHC Attributes takes a similar format to The format for signaling ROHC Attributes takes a similar format to
the Transform Attributes described in Section 3.3.5 of RFC the Transform Attributes described in Section 3.3.5 of RFC
4306[IKEV2]. The ROHC Attribute is shown in Figure 2. 4306[IKEV2]. The format of the ROHC Attribute is shown in Figure 2.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
!A! ROHC Attribute Type ! AF=0 ROHC Attribute Length ! !A! ROHC Attribute Type ! AF=0 ROHC Attribute Length !
!F! ! AF=1 ROHC Attribute Value ! !F! ! AF=1 ROHC Attribute Value !
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! AF=0 ROHC Attribute Value ! ! AF=0 ROHC Attribute Value !
! AF=1 Not Transmitted ! ! AF=1 Not Transmitted !
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 45 skipping to change at page 10, line 45
1 Maximum Context Identifier (MAX_CID) TV [rfcThis] 1 Maximum Context Identifier (MAX_CID) TV [rfcThis]
2 ROHC Profile (ROHC_PROFILE) TV [rfcThis] 2 ROHC Profile (ROHC_PROFILE) TV [rfcThis]
3 ROHC Integrity Algorithm (ROHC_INTEG) TV [rfcThis] 3 ROHC Integrity Algorithm (ROHC_INTEG) TV [rfcThis]
4 ROHC ICV Length in bytes (ROHC_ICV_LEN) TV [rfcThis] 4 ROHC ICV Length in bytes (ROHC_ICV_LEN) TV [rfcThis]
5 Maximum Reconstructed Reception Unit (MRRU) TV [rfcThis] 5 Maximum Reconstructed Reception Unit (MRRU) TV [rfcThis]
6-16383 Unassigned [rfcThis] 6-16383 Unassigned [rfcThis]
16384-32767 Private use [rfcThis] 16384-32767 Private use [rfcThis]
Following the policies outlined in [IANA-CONSIDERATIONS], the IANA Following the policies outlined in [IANA-CONSIDERATIONS], the IANA
policy for assigning new values for the ROHC Attribute Types registry policy for assigning new values for the ROHC Attribute Types registry
shall be Designated Expert. shall be Expert Review.
For registration requests, the responsible IESG area director will For registration requests, the responsible IESG area director will
appoint the Designated Expert during the IETF last call. The appoint the Designated Expert. The Designated Expert will post a
intention is that any allocation will be accompanied by a published request to both the rohc and ipsec mailing lists (or a successor
RFC. The Designated expert will post a request to both the rohc and designated by the Area Director) for comment and review. The
ipsec mailing lists (or a successor designated by the Area Director)
for comment and review. Before expiration of the IETF last call, the
Designated Expert will either approve or deny the registration Designated Expert will either approve or deny the registration
request and publish a notice of the decision to both mailing lists request and publish a notice of the decision to both mailing lists
(or their successors), as well as informing IANA. A denial notice (or their successors), as well as informing IANA. A denial notice
must be justified by an explanation. must be justified by an explanation.
6. Acknowledgments 6. Acknowledgments
The authors would like to thank Mr. Sean O'Keeffe, Mr. James Kohler, The authors would like to thank Mr. Sean O'Keeffe, Mr. James Kohler,
and Ms. Linda Noone of the Department of Defense, as well as Mr. Rich and Ms. Linda Noone of the Department of Defense, as well as Mr. Rich
Espy of OPnet for their contributions and support in the development Espy of OPnet for their contributions and support in the development
skipping to change at page 11, line 31 skipping to change at page 11, line 29
In addition, the authors would like to thank the following for their In addition, the authors would like to thank the following for their
numerous reviews and comments to this document: numerous reviews and comments to this document:
o Mr. Magnus Westerlund o Mr. Magnus Westerlund
o Dr. Stephen Kent o Dr. Stephen Kent
o Mr. Lars-Erik Jonsson o Mr. Lars-Erik Jonsson
o Mr. Pasi Eronen o Mr. Pasi Eronen
o Dr. Jonah Pezeshki o Dr. Jonah Pezeshki
o Mr. Carl Knutsson o Mr. Carl Knutsson
o Dr. Joseph Touch o Dr. Joseph Touch
o Mr. David Black
o Mr. Glen Zorn
Finally, the authors would also like to thank Mr. Tom Conkle, Ms. Finally, the authors would also like to thank Mr. Tom Conkle, Ms.
Michele Casey, and Mr. Etzel Brower. Michele Casey, and Mr. Etzel Brower.
7. References 7. References
7.1. Normative References 7.1. Normative References
[IPSEC] Kent, S. and K. Seo, "Security Architecture for the [IPSEC] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, December 2005. Internet Protocol", RFC 4301, December 2005.
skipping to change at page 12, line 19 skipping to change at page 12, line 19
Compression (ROHC): Framework and four profiles: RTP, UDP, Compression (ROHC): Framework and four profiles: RTP, UDP,
ESP, and uncompressed", RFC 3095, July 2001. ESP, and uncompressed", RFC 3095, July 2001.
[ROHCV2] Pelletier, G. and K. Sandlund, "RObust Header Compression [ROHCV2] Pelletier, G. and K. Sandlund, "RObust Header Compression
Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP
Lite", RFC 5225, April 2008. Lite", RFC 5225, April 2008.
[IPSEC-ROHC] [IPSEC-ROHC]
Ertekin, E., Christou, C., and C. Bormann, "IPsec Ertekin, E., Christou, C., and C. Bormann, "IPsec
Extensions to Support ROHCoIPsec", work in progress , Extensions to Support ROHCoIPsec", work in progress ,
December 2009. February 2010.
[IANA-CONSIDERATIONS]
Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226,
October 1998.
7.2. Informative References 7.2. Informative References
[ROHCOIPSEC] [ROHCOIPSEC]
Ertekin, E., Jasani, R., Christou, C., and C. Bormann, Ertekin, E., Jasani, R., Christou, C., and C. Bormann,
"Integration of Header Compression over IPsec Security "Integration of Header Compression over IPsec Security
Associations", work in progress , December 2009. Associations", work in progress , February 2010.
[ROHC-PPP] [ROHC-PPP]
Bormann, C., "Robust Header Compression (ROHC) over PPP", Bormann, C., "Robust Header Compression (ROHC) over PPP",
RFC 3241, April 2002. RFC 3241, April 2002.
[ROHCPROF] [ROHCPROF]
"RObust Header Compression (ROHC) Profile Identifiers", "RObust Header Compression (ROHC) Profile Identifiers",
www.iana.org/assignments/rohc-pro-ids , May 2008. www.iana.org/assignments/rohc-pro-ids , May 2008.
[CRYPTO-ALG] [CRYPTO-ALG]
Manral, V., "Cryptographic Algorithm Implementation Manral, V., "Cryptographic Algorithm Implementation
Requirements for Encapsulating Security Payload (ESP) and Requirements for Encapsulating Security Payload (ESP) and
Authentication Header (AH)", RFC 4835, April 2007. Authentication Header (AH)", RFC 4835, April 2007.
[IKEV2-PARA] [IKEV2-PARA]
IANA, "IKEv2 Parameters, IANA, "IKEv2 Parameters,
http://www.iana.org/assignments/ikev2-parameters", http://www.iana.org/assignments/ikev2-parameters",
November 2009. November 2009.
[IANA-CONSIDERATIONS]
Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226,
October 1998.
Authors' Addresses Authors' Addresses
Emre Ertekin Emre Ertekin
Booz Allen Hamilton Booz Allen Hamilton
5220 Pacific Concourse Drive, Suite 200 5220 Pacific Concourse Drive, Suite 200
Los Angeles, CA 90045 Los Angeles, CA 90045
US US
Email: ertekin_emre@bah.com Email: ertekin_emre@bah.com
 End of changes. 14 change blocks. 
39 lines changed or deleted 38 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/