Future Architecture, Technology and Application Enablers Roadmap- 02

© 2011 AT&T Intellectual Property. All rights reserved. AT&T, AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other trademarks are the property of their owners. This document is not an offer, commitment, representation or warranty by AT&T and is subject to change.

Embracing IPv6

This presentation is part of the Joint GSMA/NGMN Conference Stream “Technology Evolution”

Mobile World Congress 2011, BarcelonaHall 5, Auditorium 2

Thursday, 17 February, 2011

Vijay Perumbeti

Executive Director, Strategic Standards

AT&TAT&T


Outline

1. IP Address demand

2. IPv6 Drivers, Scope, and Readiness

3. Transition and Co-existence considerations and h i mechanisms

4. Roaming and Interoperability Aspects – GSMA Activity

Th Mi ti P5. The Migration Process

6. Key Takeaways

IANA ran out of IPv4 Addresses: February 2011IANA ran out of IPv4 Addresses: February, 2011


3

IP Address Demand


4

Drivers for migrating to IPv6

• Primary Driver: The Internet is running out of IPv4 addresses

– Need to ensure business continuity and growth

• Derived Drivers– National/Governmental Strategies, Mandates

• EU, US DoD, China NGI

– Demand from new and evolving infrastructures• Machine to machine, Smart Grid, LTE, “Internet of Things”

– Take advantage of new IPv6 Content Applications– Take advantage of new IPv6 Content, Applications

• IPv6 has functional improvements: Streamlined header format, native mobile IP support, native IPSEC support, Auto configuration, etc.– But these are not driving the migration to IPv6But these are not driving the migration to IPv6– These functional improvements will be harnessed in due course

IPv6 migration affects ….E t f th t k d IT i f t tEvery part of the network and IT infrastructureEvery customer-facing application and deviceEvery application the company uses internallyEvery business function


55

IPv6 Migration Scope What does IPv6 Touch?

D t M i VoIP Data Center

IPTV Security Messaging

etc

.) IT In

. . . . .

IP Network

CP,

AAA,

NTP, n

frastructu

re ng

Secu

r

IP Network

Access/Aggregationces

(DN

S,

DH

C (BSS, O

SS, MIP

Addre

ssinrity In

frastruct

DSL WiFiRemote Access

Access/Aggregation Infrastructure

EthernetCellular Networket

work

Ser

vic

Mgm

t Tools, et

ture

. . . Access

Devices

NetworkNtc)

Residential Customer Mobility

Devices

Business Customer


6 Page 6

Devices DevicesDevices

IPv6 Readiness

• What is IPv6 Readiness?• What is IPv6 Readiness?– Have the ability to sell, provision, install and maintain new

services with IPv6– Handle current and forecasted volumes– Provide interoperability between IPv4 and IPv6 sites, content and

networks– Provide a seamless transition for customers, network and

operations

• AT&T has an active program to be “IPv6 ready” • AT&T has an active program to be IPv6 ready – Multi-year program in place– Over a 100 funded projects– Recent milestones include IPv6 support for AT&T’s services to

enterprise customers -- Internet Access, VPN and Peering services


7

IPv6-IPv4 Co-existence

v4 dominant(Current)

v4 address exhaustion(~2011/2012)

V6 dominant(TBD)

IPV4-only

IPV4/IPv6 dual stack

IPv6-only

IPv4 and IPv6 will co-exist for a long time. We need to address how different types of nodes

( 4 l 6 l 4/ 6 d l t k) ill (v4-only, v6-only, v4/v6 dual stack) will communicate with one another


8

IPv6-IPv4 Co-existenceA Mobility perspective

v4

IPv4 InternetNAT/Proxy

v4/v6 Dual Stack

IP networkIP network

IPv6 InternetNAT64

v6

IPv4 <-> IPv4 trafficIPv6 < > IPv6 traffic

NAT Network Address Translator


9

IPv6 <-> IPv6 traffic

IPv6-IPv4 Co-existenceA Wireline perspectivep p

v4

Public v4 addr

P bli 4 & 6 dd

TS

v6 over v4NAT/Proxy

CPELANIPv4 Internet

v4/v6 Dual Stack

IP network

Public v4 & v6 addr

CPELAN

IP network

Public v6 addr NAT64 IPv6 Internet

v6

TSv4 over v6CPELAN

TS

IPv4 <-> IPv4 trafficIPv6 < > IPv6 traffic

Tunnel Server

NAT Network Address Translator


10

IPv6 <-> IPv6 traffic

Tunnel Traffic

IPv4-to-IPv6Transition Mechanisms and Co-existence Proposals

• IETF has defined mechanisms for transitions and co-existence:D l t k ll IP 4 d IP 6 t i t i th d i d t k– Dual-stack allows IPv4 and IPv6 to co-exist in the same devices and networks

– Tunneling allows IPv6 packets to be transmitted over an IPv4 infrastructure or vice versa -- when IPv6 becomes the more prevalent network

– Translation allows IPv6-only devices to communicate with IPv4-only devices (work y y (in progress)

• IPv6/IPv4 Co-existence Proposals – NAT 444 (draft-shirasaki-nat444)

• Extends life of IPv4 addresses• Translates private v4’ to private v4 and then to public v4

– 6rd (RFC 5969)• Supports IPv6 TransitionSupports IPv6 Transition• IPv6 over IPv4 tunneling

– Dual Stack Lite (draft-ietf-softwire-dual-stack-lite)• Supports IPv6 Transition

Allows IPv6 network to continue access IPv4 resources via NAT44 and Tunneling• Allows IPv6 network to continue access IPv4 resources via NAT44 and Tunneling

– IPv6-IPv4 Translation (draft-ietf-behave-v6v4-framework)• Supports IPv6 Transition• Provides IPv6-only client with IPv4 access


11

– Gateway Initiated Dual Stack Lite (draft-ietf-softwire-gateway-init-ds-lite)• Extends life of IPv4 addresses

Roaming and InteroperabilityGSMA Activity to Facilitate MNO Migration to IPv6

• Task force launched in 3Q2010 to address:• Task force launched in 3Q2010 to address:– “Roaming and Interoperability Impacts of IPv6 Transition” – Task force had active contributions from IPv6 experts from 18 MNOs

• Release 1 of white paper just completed:• Release 1 of white paper just completed:– Focus on the user plane and HPLMN services, where the IPv4 address and/or the

IPv6 prefix is assigned by Home PLMN– Describes 27 use cases for inter-operability and roaming– Describes high level guidelines to facilitate uninterrupted roaming across PLMNs for

IMS and non-IMS services– Identify minimum requirements to ensure inter-operability and roaming in a mixed

environmentenvironment

• Release 2 will address Local Breakout scenarios and transport plane issues as they relate to local breakout

• The white paper provides guidance to GSMA Work Groups to update or • The white paper provides guidance to GSMA Work Groups to update or create new PRDs

• For further information contact: Jose Aranda, Project ManagerJaranda@gsm org


12

– [email protected]

Roaming and InteroperabilityVariables affecting roaming and interoperability

• PLMN user level can be IPv4, IPv6 or Dual stack IPv4&6PLMN user level can be IPv4, IPv6 or Dual stack IPv4&6

• Different components of a PLMN may evolve at different time frames (e.g. Packet Core, Applications, IMS Core, etc.)

• Three RAN/CORE environments:– EPS Release 8.0 and beyond– UMTS/GSM Release 9.0 (A Bearer can carry both IPv4 and IPv6 packets)– UMTS/GSM Release 8.0 and before (There are two Bearers: one for IPv4 and another for IPv6)

• Interfaces for data roaming • Interfaces for data roaming – Roaming using Gp interface– Roaming using S8 interface via EPC

• Private IPv4 or Public IPv4 addresses will be assigned

• Terminal to network and terminal to terminal based services

• Roaming with or with out local breakout

• User Equipment with IPv4, IPv6 and Dual Stack IPv4v6 capabilities

• Internet websites and applications can be IPv4, IPv6 or Dual Stack IPv4v6

• Networks might control whether inbound unsolicited packets are permitted to reach a particular IPv6 address or addresses


13

• Supported IP version(s) of the GRX and IPX user plane for IMS interworking

The Migration ProcessThe 4 Pillars of IPv6 Migration

• Program Management • Program Management – Execute on an end to end integrated work plan

• Financial Managementg– Vigilant capital tracking; Ensure investments are properly timed

with requirements and ROIC criteria met

Ri k M t• Risk Management– Have a detailed association of revenue and infrastructure

elements to cross check that planned projects account for all elements of v6 readiness

• CommunicationEmployees Customers Suppliers industry participants– Employees, Customers, Suppliers, industry participants

– Awareness, training, progress


14

The Migration ProcessThe Planning Process for IPv6 Migration

Program Governance and Communication

C IP 6 i i

Infrastructure ReadinessInfrastructure Readiness Strategy and ArchitectureStrategy and Architecture

• Quantify infrastructure readiness • Research IPv6 technologies • Create IPv6 transition timelines, sequencing and interdependencies

• Identify governance team to oversee plan

Quantify infrastructure readiness and understand transition impacts

• Categorize Components for Readiness

Research IPv6 technologies utilized for transition (tunnels, translation mechanisms)

• Develop IP Addressing Plan• Develop a thorough transition

strategyto oversee plan

• Develop review and program management aspects of overall plan, timelines and assigned transition teams

Design and EngineeringDesign and Engineering Testing and PilotingTesting and Piloting

strategy

• Develop detailed design and equipment configurations

• Create IPv6 test labsassigned transition teams

• Execute planequipment configurations, including:– IP addressing

– DNS

• Identify and assign transition sequencing and

• Develop test plans and production piloting

• Conduct dual stack testing • Tunneling

transition sequencing and engineering tasks


15

Key Takeaways

• Must operate on the premise that IPv4 exhaust is imminent and IPv6 is inevitableinevitable

– IPv4 exhaust is no longer a distant problem

• There are architecture and design choices to made;• Some affect only operators’ own networks• Some affect only operators own networks• Others affect interworking and roaming

• In order to be IPv6 ready, we not only need to implement IPv6 but also consider how IPv6 will co-exist with IPv4

• IPv6 Migration is complex, requires careful planning, and needs considerable resources

– Introduction and migration of IPv6 can start now and can be incremental– Complete IPv6 migration will be a multi-year program– New services should be targeted to support IPv6 from Day 1 to avoid transition

costs later

In an interconnected world, IPv6 migration planning has to be a collaborative industry effort

Embrace it!


16

Embrace it!

Thank [email protected]


1717
