0. Source: Qualcomm Incorporated Contact: Jun Wang/George Cherian
RoHCv2 Support
Source: Qualcomm Incorporated
Contact: Jun Wang/George Cherian
Oct. 25, 2010
Notice ©2010. All rights reserved.
Qualcomm Incorporated grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any Organizational Partner’s standards publication even though it may include all or portions of this contribution; and at the Organizational Partner’s sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner’s standards publication. Qualcomm Incorporated is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.
This document has been prepared by the Qualcomm Incorporated to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on Qualcomm Incorporated. Qualcomm Incorporated specifically reserve the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the Qualcomm Incorporated other than provided in the copyright statement above.

1. Background Both RoHCv1 and RoHC v2 are supported in 3GPP LTE R8 and R9
Optional for both UE and eNB
Supported v1 and V2 profiles:
0x0000 ROHC uncompressed (RFC 4995)
0x0001 ROHC RTP (RFC 3095, RFC 4815)
0x0002 ROHC UDP (RFC 3095, RFC 4815)
0x0003 ROHC ESP (RFC 3095, RFC 4815)
0x0004 ROHC IP (RFC 3843, RFC 4815)
0x0006 ROHC TCP (RFC 4996)
0x0101 ROHCv2 RTP (RFC 5225)
0x0102  ROHCv2 UDP (RFC 5225)
0x0103 ROHCv2 ESP (RFC 5225)
0x0104 ROHCv2 IP (RFC 5225)
If both v1 and v2 ROHC profile identifiers corresponding to the same profile type are supported, only the profile corresponding to the highest value shall be applied.
eHRPD only supports RoHCv1 in X.S0057-0
RoHCv1 can be performed between UE and eAN or between UE and HSGW

2. RoHC Profiles Specified in RFC
RoHCV1 support the following profiles:
RTP/UDP/IP(Profile 0x0001) RFC3095/RFC4815
UDP/IP(Profile 0x0002) RFC3095/RFC4815
ESP/IP(Profile 0x0003) RFC3095/RFC4815
uncompressed (Profile 0x0000) RFC3095/RFC4815
IP (Profile 0x0004) RFC3843
RTP/UDP-Lite/IP (Profile 0x0007) RFC4019
UDP-Lite/IP (Profile 0x0008) RFC4019
ROHC TCP (0x0006) RFC 4996 (Note: This can be treated as RoHCv2 as well)
RoHCv2 support the following profiles: RFC 5225
RTP/UDP/IP (Profile 0x0101)
UDP/IP (Profile 0x0102)
ESP/IP (Profile 0x0103)
IP (Profile 0x0104)
RTP/UDP-Lite/IP (Profile 0x0107)
UDP-Lite/IP (Profile 0x0108)

3. Add RoHC v2 Support in eHRPD
RoHCv2 support over SO 67/SO72
TSG-C C.S0063-A signaling can already support RoHC v2 since it refers to:
on all supported RoHC profiles
TSG-A A.S0008/A.S0009/A.S0022 signaling also supports sending a list of supported RoHC profiles on A11 signaling
We just need to add the following clarifications:
If both v1 and v2 ROHC profile identifiers corresponding to the same profile type are supported by both UE and eAN (or HSGW), only the profile corresponding to the highest value shall be applied.
Add the appropriate IETF RFC references
RoHCv2 support over VSNP (SO 59/SO64)
RoHC over PPP (RFC 3241) also allows to list all supported profile
We just need to add the following clarifications
If both v1 and v2 ROHC profile identifiers corresponding to the same profile type are supported by both UE and HSGW, only the profile corresponding to the highest value shall be applied.
10/10/2009
QUALCOMM Proprietary

4. Recommendations
Add RoHCv2 support in eHRPD (X.S0057-A and X.S if open another addendum)
Add RoHCv2 support in HRPD/1x if X.S0011 opens addendum or another revision
Not preclude any RoHC profiles supported by IETF RFCs
Support of Profile 0x0000 is mandatory
Support of rest of profiles is optional
Stage 3 changes will follow up in separate contributions
10/10/2009
QUALCOMM Proprietary

5. IETF RFC Referecnes
RFC 3095: RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed 
RFC 3843: RObust Header Compression (ROHC): A Compression Profile for IP
RFC 4815: RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095 
RFC 4019: RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) Lite 
RFC 4996: RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP) 
RFC 5225: RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite
RFC 5795: The RObust Header Compression (ROHC) Framework 
10/10/2009
QUALCOMM Proprietary