"Integration of Robust Header Compression (ROHC) over IPsec Security Associations", Emre Ertekin, Rohan Jassani, Chris Christou, Carsten Bormann, 2-Feb-09. ( bytes)
IP Security (IPsec) provides various security services for IP traffic. However, the benefits of IPsec come at the cost of increased overhead. This document outlines a framework for integrating Robust Header Compression (ROHC) over IPsec (ROHCoIPsec). By compressing the inner headers of IP packets, ROHCoIPsec proposes to reduce the amount of overhead associated with the transmission of traffic over IPsec Security Associations (SAs).
"IKEv2 Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec)", Emre Ertekin, Chris Christou, Rohan Jassani, Tero Kivinen, Carsten Bormann, 2-Feb-09. ( bytes)
In order to integrate ROHC with IPsec [ROHCOIPSEC], a mechanism is needed to signal ROHC channel parameters between end-points. Internet Key Exchange (IKE) is a mechanism which can be leveraged to exchange these parameters. This document specifies extensions to IKEv2 [IKEV2] that will allow ROHC and its associated channel parameters to be signaled for IPsec security associations (SAs).
"IPsec Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec)", Emre Ertekin, Chris Christou, Carsten Bormann, 2-Feb-09. ( bytes)
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. This document describes the IPsec extensions required to support ROHCoIPsec.
"The RObust Header Compression (ROHC) Framework", Kristofer Sandlund, Ghyslain Pelletier, Lars-Erik Jonsson, 13-Jul-09. ( bytes)
The Robust Header Compression (ROHC) protocol provides an efficient, flexible, and future-proof header compression concept. It is designed to operate efficiently and robustly over various link technologies with different characteristics. The ROHC framework, along with a set of compression profiles, was initially defined in RFC 3095. To improve and simplify the ROHC specifications, this document explicitly defines the ROHC framework and the profile for uncompressed separately. More specifically, the definition of the framework does not modify or update the definition of the framework specified by RFC 3095. This specification obsoletes RFC 4995. It fixes one interoperability issue that was erroneously introduced in RFC 4995, and adds some minor clarifications.

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to Internet-Draft directory.

Return to IETF home page.