Network Working Group E. Ertekin Internet-Draft C. Christou Expires:
April 16,August 6, 2009 J. Pezeshki M. CaseyBooz Allen Hamilton C. Bormann Universitaet Bremen TZI October 13, 2008February 2, 2009 IPsec Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec) draft-ietf-rohc-ipsec-extensions-hcoipsec-03draft-ietf-rohc-ipsec-extensions-hcoipsec-04 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or sheThis Internet-Draft is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed,submitted to IETF in accordancefull conformance with Section 6the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on April 16,August 6, 2009. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract Integrating ROHC with IPsec (ROHCoIPsec) offers the combined benefits of IP security services and efficient bandwidth utilization. However, in order to integrate ROHC with IPsec, extensions to the SPD and SAD are required in order to integrate ROHC with IPsec.required. This document describes the IPsec extensions required to support ROHCoIPsec. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Extensions to IPsec Databases . . . . . . . . . . . . . . . . . 3 2.1. Security Policy Database (SPD) . . . . . . . . . . . . . . 3 2.2. Security Association Database (SAD) . . . . . . . . . . . . 4 3. Extensions to IPsec Processing . . . . . . . . . . . . . . . . 5 3.1. Addition to the IANA Protocol Numbers Registry . . . . . . 5 3.2. Verifying the Integrity of Decompressed Packet Headers . . 5 3.2.1. ICV Computation and Integrity Verification . . . . . . 6 3.3. Nested IPComp and ROHCoIPsec Processing . . . . . . . . . 6. 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7. 8 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7. 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.1. Normative References . . . . . . . . . . . . . . . . . . . 8 7.2. Informative References . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . . . 111. Introduction Using IPsec ([IPSEC]) protection offers various security services for IP traffic. However, these benefits come at the cost of additional packet headers, which increase packet overhead. As described in [ROHCOIPSEC], Robust Header Compression (ROHC [ROHC]) can be used with IPsec to reduce the overhead associated with IPsec-protected packets. IPsec-protected traffic is carried over Security Associations (SAs), whose parameters are negotiated on a case-by-case basis. The Security Policy Database (SPD) specifies the services that are to be offered to IP datagrams, and the parameters associated with SAs that have been established are stored in the Security Association Database (SAD). To integrate ROHC and IPsec,For ROHCoIPsec, various extensions to the SPD and SAD that incorporate ROHC-relevant parameters are required. In addition, three extensions to IPsec processing are required. First, a mechanism for identifying ROHC packets must be defined. Second, a mechanism is requiredto ensure the integrity of the decompressed packet.packet is needed. Finally, the order of the inbound and outbound processing must be enumerated when nesting IP Compression (IPComp [IPCOMP]), ROHC, and IPsec processing. 2. Extensions to IPsec Databases The following subsections specify extensions to the SPD and the SAD to support ROHCoIPsec. 2.1. Security Policy Database (SPD) In general, the SPD is responsible for specifying the security services that are offered to IP datagrams. Entries in the SPD specify how to derive the corresponding values for SAD entries. To support ROHC, the SPD must be extended to include per-channel ROHC parameters. Together, the existing IPsec SPD parameters and the ROHC parameters will dictate the security and header compression services that are provided to packets protected by IPsec.packets. The fields contained within each SPD entry are defined in [IPSEC], Section 126.96.36.199. To support ROHC, several processing info fields must be added to the SPD; these fields contain information regarding the ROHC profiles and channel parameters supported by the local ROHC instance. The SPD specifies what services are to be offered to IP datagrams, and in what fashion. To offer IP datagrams compression services, two per-channel configuration parameters are added to the SPD. Specifically, thefollowing twoROHC channel parameters must be included if the processing info field in the SPD is set to PROTECT (suggested values for these parameters are consistent with [ROHCPPP]): MAX_CID: The field indicates the highest context ID number tothat will be useddecompressed by the compressor.local decompressor. MAX_CID must be at least 0 and at most 16383 (The value 0 implies having one context). The suggested value for MAX_CID is 15. PROFILES: This indicates thefield is a list of ROHC profiles supported by the local decompressor. The list of possiblePossible values for this field may assume is definedlist are contained in the [ROHCPROF] registry. In addition to these ROHC channel parameters, a field within the SPD is required to store a list of integrity algorithms supported by the ROHCoIPsec instance: INTEGRITY ALGORITHM: This field is a list of integrity algorithms supported by the ROHCoIPsec instance. This will be used by the ROHC process to ensure that packet headers are properly decompressed (see Section 3.2). Several other ROHC channel parameters are omitted from the SPD, because they are set implicitly. The ROHComitted channel parameters are LARGE_CIDS, MRRU, and FEEDBACK_FOR. The LARGE_CIDS channel parameter is set implicitly, based on the value of MAX_CID (e.g. if MAX_CID is <= 15, LARGE_CIDS is assumed to be 0). Furthermore, since in-order delivery of ROHC packets cannot be guaranteed, the MRRU parameter must be set to 0; since packets may be reordered across a ROHCoIPsec channel, a compression session must not use segmentation.0 (as stated in Section 188.8.131.52 of [ROHC] and Section 6.1 of [ROHCV2]). Finally, the ROHC FEEDBACK_FOR channel parameter is set implicitly to the ROHC channel associated with the SA in the reverse direction. If an SA in the reverse direction does not exist, the FEEDBACK_FOR channel parameter is not set, and ROHC must not operate in the Unidirectionalbidirectional Mode. 2.2. Security Association Database (SAD) Each entry within the SAD defines the parameters associated with each established SA. Unless ifthe "populate from packet" (PFP) flag is asserted for a particular field, SAD entries are determined by the corresponding SPD entries during the creation of the SA. The data items contained within the SAD are defined in [IPSEC], Section 184.108.40.206. To support ROHC, this list of data items is augmented to include a "ROHC Data Item" fieldthat definescontains the parameters used by ROHC parameters. Theseinstance. The ROHC Data Item exists for both inbound and outbound SAs. The ROHC Data Item includes the ROHC channel parameters (i.e.,for the SA. These channel parameters (i.e., MAX_CID, PROFILES) are enumerated above in Section 2.1. In addition,For inbound SAs, the FEEDBACK_FOR parameter is also included, which is associated withROHC Data Item includes ROHC channel parameters that are used by the SA inlocal decompressor instance; conversely, for outbound SAs, the reverse direction (this data item does not needROHC Data Item includes ROHC channel parameters that are used by local compressor instance. In addition to be included inthese ROHC channel parameters, the SPD, since its value is implicitly derived). Finally,ROHC Data Item for both inbound and outbound SAs includes two additional parameters. Specifically, these parameters are required tostore the Integrity Algorithmintegrity algorithm and respective key thatused by ROHC (see Section 3.2). The integrity algorithm and its associated key are used to calculate a ROHC ICV; this ICV is used to verify the packet headers post-decompression. Finally, for inbound SAs, the ROHC Data Item includes a FEEDBACK_FOR parameter. The parameter is a reference to a ROHC channel in the opposite direction (i.e., the outbound SA) between the same compression endpoints. A ROHC channel associated with an inbound SA and a ROHC channel associated with an outbound SA may be usedcoupled to ensure that packets are properly decompressed (seeform a Bi-directional ROHC channel as defined in Section 3.2). These6.1 and Section 6.2 in [ROHC-TERM]. "ROHC Data Item" values may be initialized manually (i.e., administratively configured for manual SAs), or initialized via a key exchange protocol (e.g. IKEv2 [IKEV2]) that has been extended to support the negotiationsignaling of ROHC parameters [IKEV2EXT]. 3. Extensions to IPsec Processing 3.1. Addition to the IANA Protocol Numbers Registry In order to demultiplex header-compressed from uncompressed traffic on a ROHC-enabled SA, a "ROHC" value must be reserved in the IANA Protocol Numbers registry. If an outbound packet has a compressed header, the Next Header field of the security protocol header (e.g., AH [AH], ESP [ESP]) must be set to the "ROHC" protocol identifier. If the packet header has not been compressed, the Next Header field remains unaltered. Conversely, for an inbound packet, the value of the security protocol Next Header field is checked to determine if the packet includes a ROHC header.header, in order to determine if it requires ROHC decompression. 3.2. Verifying the Integrity of Decompressed Packet Headers Since ROHC is inherently a lossy compression algorithm, ROHCoIPsec may use an additional Integrity Algorithm (and respective key) to compute a second Integrity Check Value (ICV) for the uncompressed packet. This ICV is computed over the uncompressed IP header, as well at the higher-layer headers and the packet payload, and is appended to the ROHC-compressed packet. At the decompressor, the decompressed packet (including the uncompressed IP header, higher-layerhigher- layer headers, and packet payload; but not including the authentication data) will be used with the Integrity Algorithmintegrity algorithm (and its respective key) to compute a value that will be compared to the appended ICV. If these values are not identical, the decompressed packet must be dropped by the decompressor. Figure 1 illustrates the composition of a ROHCoIPsec-processed IPv4 packet. In the example, TCP/IP compression is applied, and the packet is processed with tunnel mode ESP. BEFORE COMPRESSION AND APPLICATION OF ESP ---------------------------- IPv4 |orig IP hdr | | | |(any options)| TCP | Data | ---------------------------- AFTER ROHCOIPSEC COMPRESSION AND APPLICATION OF ESP ------------------------------------------------------ IPv4 | new IP hdr | | Cmpr. | | ROHC | ESP | ESP| |(any options)| ESP | Hdr. |Data| ICV |Trailer| ICV| ------------------------------------------------------ Figure 1. Example of a ROHCoIPsec-processed packet. Note: The authentication data should nevermust not be included in the calculation of the ICV. 3.2.1. ICV Computation and Integrity Verification In order to correctly verify the integrity of the decompressed packets, the processing steps for ROHCoIPsec must be implemented in a specific order, as given below. For outbound packets that are to be processed by ROHC: o An ICV is computed for the uncompressed packet via ROHCoIPsec's Integrity Algorithm (and respective key) o The packet header(s) is(are) compressed by the ROHC process o The ICV is appended to the end of the compressed packet o The security protocol is applied to the packet For inbound packets that are to be decompressed by ROHC: o A packet received on a ROHC-enabled SA is IPsec-processed o The packetPacket header(s) is(are) decompressed by the ROHC process o The decompressed packet is used with the Integrity Algorithmintegrity algorithm (and its respective key) to compute a valueROHC ICV that is compared to the appended ICV (if these two values differ, the packet is dropped) 3.3. Nested IPComp and ROHCoIPsec Processing IPComp ([IPCOMP]) is another mechanism that can be implemented to reduce the size of an IP datagram. If IPComp and ROHCoIPsec are implemented in a nested fashion, the order of the outbound and inbound processingfollowing steps must be carefully enumerated.followed for outbound and inbound packets. For outbound packets that are to be processed by IPcomp and ROHC: o The ICV is computed for the uncompressed packet, and the appropriate ROHC compression profile is applied to the packet o IPComp is applied, and the packet is sent to the IPsec process o The security protocol is applied to the packet Conversely, for inbound packets that are to be both ROHC- and IPcomp- decompressed: o A packet received on a ROHC-enabled SA is IPsec-processed o The datagram is decompressed based on the appropriate IPComp algorithm o The packet is sent to the ROHC module for header decompression and integrity verification 4. Security Considerations A ROHCoIPsec implementer should consider the strength of protection provided by the integrity check algorithm used to verify the valid decompression of ROHC-compressed packets. Failure to implement a strong integrity check algorithm increases the probability of an invalidly decompressed packet to be forwarded by a ROHCoIPsec device into a protected domain. In general, if an integrity check algorithm is used with IPsec, it is recommended that the integrity check algorithm used by ROHC is at least the same strength.The implementation of ROHCoIPsec may increase the susceptibility for traffic flow analysis, where an attacker can identify new traffic flows by monitoring the relative size of the encrypted packets (i.e. a group of "long" packets, followed by a long series of "short" packets may indicate a new flow for some ROHCoIPsec implementations). To mitigate this concern, ROHC padding mechanisms may be used to arbitrarily add padding to transmitted packets to randomize packet sizes. This technique, however, reduces the overall efficiency benefit offered by header compression. 5. IANA Considerations IANA is requested to allocate one value within the "Protocol Numbers" registry [PROTOCOL] for "ROHC". This value will be used to indicate that the next level protocol header is a ROHC header. 6. Acknowledgments The authors would like to thank Mr. Sean O'Keeffe, Mr. James Kohler, Ms. Linda Noone of the Department of Defense, and Mr. A. Rich Espy of OPnet for their contributions and support for developing this document. In addition, theThe authors would also like to thank Mr. Rohan JasaniYoav Nir, and Mr. Robert A Stangarone Jr.: both served as committed document reviewers for his valuable assistance.this specification. Finally, the authors would like to thank the following for their numerous reviews and comments to this document: o Dr. Stephen Kent o Mr. Lars-Erik JonnsonJonsson o Mr. Carl Knutsson o Mr. Pasi Eronen o Dr. Jonah Pezeshki o Mr. Tero Kivinen o Dr. Joseph Touch o Mr. Rohan Jasani 7. References 7.1. Normative References [IPSEC] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, December 2005. [ROHC] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H., Hannu, H.,Jonsson, L., Hakenberg, R., Koren, T., Le, K., Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, T., Yoshimura, T.,L-E., Pelletier, G., and H. Zheng, "RObustK. Sandlund, "The RObust Header Compression (ROHC): Framework(ROHC) Framework", RFC 4995, July 2007. [ROHCV2] Pelletier, G. and four profiles:K. Sandlund, "RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, ESP,IP, ESP and uncompressed",UDP-Lite", RFC 3095, July 2001.5225. [IPCOMP] Shacham, A., Monsour, R., Pereira, and Thomas, "IP Payload Compression Protocol (IPComp)", RFC 3173, September 2001. [ROHCPPP] Bormann, C., "Robust Header Compression (ROHC) over PPP", RFC 3241, April 2002. [IKEV2] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", RFC 4306, December 2005. [IKEV2EXT] Pezeshki, J.,Ertekin, E., and C. Christou,et al., "Extensions to IKEv2 to Support Robust Header Compression over IPsec (ROHCoIPsec)", work in progress , October 2008.February 2009. [AH] Kent, S., "IP Authentication Header", RFC 4302, December 2005. [ESP] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, December 2005. 7.2. Informative References [ROHCOIPSEC] Ertekin, E.E., Jasani, R., Christou, C., and C. Christou,Bormann, "Integration of Header Compression over IPsec Security Associations", work in progress , October 2008.February 2009. [ROHCPROF] "RObust Header Compression (ROHC) Profile Identifiers", www.iana.org/assignments/rohc-pro-ids , October 2005. [ROHC-TERM] Jonsson, L-E., "Robust Header Compression (ROHC): Terminology and Channel Mapping Examples", RFC 3759, April 2004. [PROTOCOL] IANA, ""Assigned Internet Protocol Numbers", IANA registry at: http://www.iana.org/assignments/protocol-numbers". Authors' Addresses Emre Ertekin Booz Allen Hamilton 13200 Woodland Park Dr. Herndon, VA 20171 US Email: email@example.com Chris Christou Booz Allen Hamilton 13200 Woodland Park Dr. Herndon, VA 20171 US Email: firstname.lastname@example.org Jonah Pezeshki Booz Allen Hamilton 13200 Woodland Park Dr. Herndon, VA 20171 US Email: email@example.com Michele Casey Booz Allen Hamilton 13200 Woodland Park Dr. Herndon, VA 20171 US Email: firstname.lastname@example.orgCarsten Bormann Universitaet Bremen TZI Postfach 330440 Bremen D-28334 Germany Email: email@example.com Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at firstname.lastname@example.org.