contexts on a • separate bearer single shared for IPv4 and bearer IPv6 . Type IPv4v6). IPv4v6 PDP Protocol.3GPP STANDARDS Release 99 Release 7 Release 8 Release 9 Release 10 • Introduction of • 3G network • single shared • Introduction of • Introduction of IPv6 deployments bearer for IPv4 support in GPRS DHCPv6-PD using GTPv1 – and IPv6 for (GTPv1) for Generic GTPv2 only dual-stack Tunneling (bearer of PDN.

NOKIA Do Nothing The traditional way Drastic Improved The smart way IPv4 only IPv4 and IPv6 IPv6 only IPv6 only + NAT64 IPv6 only + 464XLAT • DELAY THE • DUAL-STACK APPROACH • REMOVE IPV4 • ADDITION OF NAT64 AND • IPv4 IS OFFERED AS A SERVICE OVER IPv6 INTRODUCTION • dual-stack networks are more complex to COMPLETELY DNS64 as an IPv4 continuation for all applications (DNS and non-DNS) OF IPv6 to a later deploy. or dual stack operator’s devices. and manage NOT COMPROMISED • Address management solution is required only for IPv6 addresses. • Release 9 multiple component upgrade in since many still use IPv4 • works only for DNS-based IPv4-only. IPv4 packets date and remain an • address management solution for both IPv4 continuation • IPv4 is offered as a service over are translated to IPv6 packets by the UE and all-IPv4 network IPv4 and IPv6 addresses • Not require public IPv4 IPv6 for DNS-based applications translated back to IPv4 packets by a central CG- • MNO will need to • Release 8 requires Dual Bearers – reduce addresses • DNS64 also embeds IPv4 internet NAT64 resolve the problem the scale of GGSN. • Cost savings are achieved by bypassing the CG-NAT64 customers • • END-USER SERVICE EXPERIENCE IS IPv6-only networks are simpler to deploy. • no impact on scale. applications. • requires support of the customer translator of increased accounting. charging. non-DNS applications will be INFERIOR NAT broken SERVICE for the • supports IPv4. IPv6-only. and manage • need not invest in legacy mechanism • For IPv4-only. operate. IPV6 MIGRATION STRATEGIES . and make roaming and QoS and OPEX • IPv6 packets are translated to IPv4 (CLAT) on the UE device demand for IP more complex • INFERIOR SERVICE packets by a central CG-NAT64 • works with websites and applications that are addresses with CG. and roaming because only a single bearer with a single stack is required Source: NOKIA . or that support dual stack NAT the mobile core that has a huge cost impact applications • SERVICE IS NEVER INFERIOR • result in an on the MNO • INFERIOR SERVICE since IPv4- • Cost savings are reaped by bypassing CG. operate. require double • savings in both CAPEX destinations in IPv6 addresses. only. etc.or IPv6-only. non-DNS applications.


464XLAT IN MOBILE NETWORKS • RFC 6877 • provides IPv4 connectivity across an IPv6-only network by combining existing and well- known: • Stateful protocol translation (RFC 6146) at CG-NAT64 • Stateless protocol translation (RFC 6145) at the UE • DNS64 (RFC 6147) mechanisms at the DNS server • IPv4 embedding into IPv6 addresses .

. • DNS64 • a mechanism for synthesizing IPv6 address (AAAA) resource records from IPv4 address (A) records.enabled websites and applications are natively routed over the GGSN/PGW towards the IPv6 internet.464XLAT IN MOBILE NETWORKS • Native IPv6 • single IPv6/64 prefix is handed out to the UE on the mobile network • IPv6.

• translates N:1 global IPv6 addresses to public IPv4 addresses.464XLAT IN MOBILE NETWORKS • CLAT • Customer-side Translator (CLAT) • software that runs inside the UE • implements stateless protocol translation and offers a private IPv4 address and an IPv4 default route to IPv4-only applications on the UE. • Traffic with an IPv4 destination is translated to IPv6 by the CLAT • PLAT • Provider-side Translator (PLAT) • implements well-known stateful protocol translation. and vice versa • holds the Pref64/n prefix • All traffic towards this IPv6 prefix must be routed to the PLAT • derives the destination IPv4 address from the destination IPv6 address • implements Application Layer Gateways (ALG) to allow certain protocols to traverse the CG-NAT component • implements a scalable logging mechanism to log all CG-NAT64 bindings for legal purposes. .

This way the same public IPv4 addresses can be used on both the active and standby PLAT.NOKIA • The Nokia 7750 Service Router (SR) supports the PLAT function. In addition to CG-NAT with high- session scalability and system reliability. This mechanism is preferred where the standby PLAT only advertises the Pref64/n prefix and the public IPv4 addresses upon detecting that the primary PLAT has become inactive. . The PLAT function can be deployed on the 7750 SR with inter- chassis redundancy by using anycast addressing for the Pref64/n IPv6 prefix.