Company Confidential

Advances in IPv6 in Mobile

John Loughney, Nokia

john.loughney@nokia.com

Company Confidential

Motivations

• 5.3 billion mobile subscribers, ITU-T figures for 2010.

• Large percentage are IP capable −Trend toward Always-On applications (details next slide)

• LTE is happening now, will be soon doing voice over IP only.

• Operators run both a circuit switched and IP networks, causing higher CAPEX and OPEX.

• In the future, services will migrate to IP.

• Carrier grade NATs are a misnomer.

• So the choice is between −IPv4 with NAT frequent keep-alives & additional investments

−IPv6 and long lived connections

Company Confidential

Company Confidential. ©2011 Nokia

Major IPv4 address pools are empty

• Huge address space for the Internet growth • Enables internet access for “the Next Billion” people • Improved solution for the whole value chain

• IPv6 is the only solution for the IPv4 exhaustion

No more crying for wolf, it’s here already

IPv6

• Internet Assigned Numbers Authority ran out of IPv4 address blocks on 3rd February 2011

• APNIC ran out on

15th April 2011

• Other RIRs are following • IPv4 usage getting complex and increasingly expensive

• IPv4 address purchases are costly, approx $11 apiece

IPv4

Company Confidential

NATs with keep alive messages

• IPv4 Mobile Devices are usually behind IPv4 NATs

−Always on application are becoming more prevalent −Applications that want to be reachable need to send

periodic keep-alives to keep NAT state active − Current NATs require keep-alives from 40 seconds to 5 minutes − Need to implement for minimum (~30 seconds)

• Sending of NAT periodic keep-alive messages decreases mobile device standby time by several days

• Not a problem for devices with power cords, but for mobile devices it is a big problem

Client, Private IPv4 address 1

Server, Public IPv4 address 3 Client, Private IPv4 address 2 UDP port = 6538

The UDP inactivity timer in NATs causes the public UDP port 6538 to be assigned to a different mobile, if the mobile does not send any data within a certain amount of time, about every 40 seconds …

There should be NO NATs between the terminal and the

server!

Company Confidential

5

Key apps and services

Peer-to-peer apps and service • Gaming

• Content transfer

Server-driven apps

• Streaming • IP TV, video-on-demand • Cloud apps and services

Apps requiring long-time sessions

• Voice, video, VoIP, etc • Hybrid apps

LTE is a data only solution,

no circuit switched voice and messaging.

All apps and services that want

‘uncomplicated’ connectivity

Company Confidential 6

Deployment approaches

Dual-stack approach is the most customer-friendly solution for transitioning to IPv6

Dual-stack is also the standard approach (3GPP) and appears to be the most favored approach

IPv6-only transition solution based on protocol translation can cause service discontinuity, and is only an option for specific cases due to discrete reasons

Company Confidential 7

Details of dual-stack

3GPP release-8 introduced a new bearer type: IPv4v6

IPv4 and IPv6 bearers can be used in parallel when IPv4v6 is not supported (since 3GPP release-99)

Various fallback scenarios are involved that are not present with IPv4-only devices, e.g. IPv4v6 -> IPv4 & IPv6

References: 3GPP release-8 23.060, 23.401 draft-ietf-v6ops-3gpp-eps

Company Confidential

Services & Content

IPv6 impacts at all levels

Applications Browsers, E-mail, IM, VoIP, Games, Utilities, Middleware entities like HTTP, ...

Modem Renesas, Qualcomm, ST-E, GCT, Broadcom, Icera (Nvidia), Marvell, Infineon, MediaTek, ...

TCP/IP Stack Symbian, iOS, Android, Windows Phone, various flavors of Linux, Series 40, RIM,

API Qt, Java, Posix, Symbian & other OS APIs, ...

Google, YouTube, Akamai, Facebook, Bing, ...

Company Confidential 9

IPv6 on handsets

IPv6 support on the modem

IPv6 support on the TCP/IP stack

IPv6 support on the connection manager

IPv6 support in the applications

IPv6 support on application APIs

IPv6 support required at different levels

Company Confidential

Phone support for IPv6

Android Motorola Droid Bionic handset for Verizon Reportedly has have IPv6 for cellular. Samsung Nexus S Has IPv6 for WLAN only.

iPhone 4S IPv6 for WLAN only

Windows Phone 7 Mango IPv4 only as no IPv6 yet on WP OS; IPv6 support coming in Apollo release

LG VL600 CDMA/LTE dongle

Symbian Has supported IPv6 since 2004, and used in trials. Apps can use IPv4 or IPv6 cellular access but not both simultaneously. This works normally when using WiFi access.

Nokia N9 IPv6 add-on enables dual-stack in 3G and WiFi accesses.

Nokia 21M-02 2G/3G /3.5G USB dongle Supports IPv6 and IPv4v6 PDP types

Company Confidential

• Dual-stack with single PDP (IPv6v4) is the most common solution

• Some network operators are considering dual-stack with parallel PDPs (IPv6 & IPv4).

− It is required for a 3GPP fallback scenario.

• IPv6-only solution is also required by a few

• Other solutions are also queried and investigated, but not required yet − PNAT, DS-Lite, DSMIP6, A+P & DS-Lite, 6rd.

• Configurability to single PDP (IPv4v6), parallel PDPs (IPv6 & IPv4), or only

IPv6 − OMA DM (operator configuration) for APN setting

• Gradual fallback in roaming and error cases for improved user experience

− IPv4v6 ► IPv4 & IPv6 ► IPv4 or IPv6 − IPv6 ► IPv4

High level cellular requirements

Company Confidential

• Closed IPv6 trials at least since 2003 • First commercial IPv6 deployments at 2010

− While many operators are conducting internal (lab) trials

• Public trials and some commercial deployments occurring

during 2011 − Even more operators are trialing − Number of cellular IPv6 capable devices also increasing

• And things are getting even better for 2012 ! • But there are some gotchas

12

IPv6 status on mobile networks

Company Confidential 13

IPv6 changes tethering significantly

Traditional dial-up style IPv4 tethering uses dedicated PDP context for the dial-up IPv4 tethering solutions, often use

NAT and DHCP to allow sharing of the same mobile connection with internal applications

Traditional dial-up is possible also with IPv6

IPv6 does not use NATting, but instead Neighbor Discovery Proxy ”bridging function” that does not require explicit network support, or explicit and more proper DHCPv6 Prefix Delegation as is defined in 3GPP Release-10

Company Confidential

Cellular operator’s services

Internet

WiFi access

WiFi offloading - under study

Cellular access

DHCPv6 server

Access Network Discovery and Selection Function

PDN GW

Rules via DHCPv6

Provisioning rules with OMA-DM

Rules via IPv6 Router Advertisements RFC4191 draft-ietf-mif-dhcpv6-route-option draft-ietf-mif-dns-server-selection draft-korhonen-mif-ra-offload 3GPP 24.312 ANDSF

14

Routing rule DB

Company Confidential

Key specifications and standards are complete and matured for product creation and deployment

Additional features and improvements are actively researched, developed, and standardized. Nokia participates, for example, to: IPv6 protocol maintenance, Multi-Interface improvements, IP mobility solutions, protocol translation topics, and Happy Eyeballs

15

IPv6 standards are ready

Company Confidential

• Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts

−http://tools.ietf.org/html/rfc3316

• IPv6 Node Requirements −http://tools.ietf.org/html/rfc4294

• Happy Eyeballs: Success with Dual-Stack Hosts −http://tools.ietf.org/html/draft-ietf-v6ops-happy-eyeballs-05

• Dual Stack Hosts Using "Bump-in-the-Host" (BIH) −http://tools.ietf.org/html/draft-ietf-behave-v4v6-bih-06

16

Additional reading