Source Avi Lior, Bridgewater Jun Wang and George Cherian, Qualcomm Incorporated Dec 07, 2009 Page 1 IPv4 Exhaustion and IPv4-IPv6 Transition in 3GPP2 Notice © All rights reserved. Qualcomm Incorporated and Bridgewater grant 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 and Bridgewater are 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 and Bridgewater 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 and Bridgewater. Qualcomm Incorporated and Bridgewater 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 and Bridgewater other than provided in the copyright statement above.

Outline IPv4 Exhaustion IPv4-IPv6 Transition IPv6 Support in Current 3GPP2 Standards Page 2

IPv4 Exhaustion In case more than 16 million MSs are active in the same network at the same time, the network will run out of private IPv4 addresses An option to solve this might lie in re-using the available private IPv4 address ranges by performing the NAT function in the PDSN/HA/LMA and – by this – being able to reuse the available private IPv4 address ranges (e.g., the – range) per PDSN/HA/LMA instance. However there are issues with NAT, for example: In existing deployments the IPv4 address, which is assigned to MSs may also serve as a means to identify customers in the operator’s network. The PCRF doesn’t have the interface to PDSN/HA/LMA for port number based identifications NAT may not work with PUSH services The total active connections to the internet will be limited by the number of public IP addresses multiplies the number of ports Each MS may need multiple ports (for example 100) New operators may not obtain the public IPv4 address(es) from ARIN Page 3

Components that affect IPv4 Exhaustion Basic Components NameStates Terminal IP capabilityIPv4 only, dual stack, (or IPv6 only in far future) Type of application programIPv4 capable only, dual stack capable, or IPv6 capable only Type of assigned IP addressIPv4 address only, dual stack addresses, or IPv6 address only Home Network IP capabilityIPv4 network, dual stack network, IPv6 network. Visitor Network IP capabilityIPv4 network, dual stack network, IPv6 network. Internet CapabilityIPv4 or dual stack Service/peer capabilityIPv4 only, dual stack, IPv6 only

IPv4-IPv6 Transition Long term solution will be using IPv6 across all components identified earlier Some of the solutions identified in IETF include: NAT NAT64+DNS64 DS lite DSMIP6 Page 5

NAT64 + DNS64 Solution to connect an IPv6 host to an IPv4 server IPv6 host queries DNS64 for an FQDN’s IPv6 address while there’s only IPv4 address DNS64 synthesize IPv6 address out of IPv4 address embed IPv4 in low order 32-bits of an IPv6 address with a site configured prefix e.g.,  2001:cafe:: IPv6 host send IPv6 packets to synthesized IPv6 address which is routed thru NAT64 NAT64 translate addresses and protocol

DS Lite Operations (Host Based) How to have IPv4 communications if the network is IPv6 only Hosts are Dual Stack Configured with a dynamic IPv6 address Statically configured with a well-known IPv4 address or with any private address Tunnel IPv4 traffic into IPv6 Providers deploy carrier-grade IPv4 NAT at border IPv6 only core Carrier grade NAT maps IPv4 address/port tuple into a public one

DSMIPv6 Defined in draft-ietf-mext-nemo-v4traversal-10 DSMIPv6 extends MIPv6 to allow the following MN can have an IPv4 HoA in addition to IPv6 HoA and run IPv4 applications CCoA can be either IPv4 or IPv6

IPv6 Support in Current 3GPP2 Standards Simple IPv6 is added in P.S0011-B (2002) The PDSN is required to support both IPv4 and IPv6 Mobile IPv6 is added in X.S0011-D (2006 ) and X.S0047 (2009) In addition, all the following documents fully support IPv6: X.S0024 (IP based Position Location), 2005 X.S0022-A (BCMCS Network Support), 2007 X.S0040 (Alt PPP), 2007 X.S0057 (eHRPD-LTE Interworking), 2009 X.S0060 (HRPD Support for Emergency Service), 2008 X.S0061 (PMIP Operation in cdma2000), 2008 Page 9

3GPP2 Standards that might not fully support IPv6 X.S0028 (WLAN Interworking), 2007 X.S seems to miss IPv6 accounting record X.S0034 (cdma2000/GPRS roaming), 2005 No IPv6 support. But do we need it? X.S0037 (Tunneling Support for Simple IP), 2006 No IPv6 support. But do we need it? X.S0058 (WiMAX Interworking), 2008 No MIPv6 support X.S (Femto Support), in V&V RIPA doesn’t support IPv6 address assignment (QC had a V&V comment to add it) Page 10