(2)IPv6 Summit - Early Experiences With IPv6 Services

8/13/2019 (2)IPv6 Summit - Early Experiences With IPv6 Services

1/31

2010 Cisco and/or its affiliates. All rights reserved. 1

2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1


Don Kasemtanachote

[email protected]

2ndSeptember 2013


2/31


Motivation for IPv6 Perspectives on IPv6 IPv6 Adoption Transition from IPv4 to IPv6

Enterprise Service Provider Consumer

Conclusion


3/31



4/31


IP

Data

IndustrialControls

Video

Mobility

3G/4G

Voice

P2P

Social

Networks

M2M /VDIServices/Clouds

Devices

Information

IPv4 Addresses

Internet Users

Source: F. Wettling Global IPv6 Strategies

Mobility / Device

Proliferation

IP Video /

Collaboration

Embedded Internet

Internet growth in terms the number of connecteddevices - is accelerating at an exponential rate

The Internet of Things is Changing the Game

Preserve, Prepare, Prosper


5/31



6/31


Most Service Providers will not consider IPv6 unless

Lack of IPv4 space hinders their progress

There is a consumer (ISP or Enterprise) requirement to drive it There is a service or application requirement - collaboration, content delivery, mobility

Enterpriseswill consider IPv6 unless

They have an application requirement to drive it Their presence on the Internet is compromised by lack of IPv4 access The price of an IPv4 address exceeds the hardware cost to route it

Consumers

Do not care about IPv4 or IPv6 broadband/mobile delivery but care about services and costs



Adoption Barriers

IPv4addresses

consumed

Adoptionby

serviceprovider

Adoptionby

government

MobilityandBYOD

trend

Expensefortransition

Securityand

compatibilityissues

Processdevelopment

Concerns with IPv6

IPv6 integration challenges vary from oneorganization to another, in terms of

IT infrastructure Various existing technologies Policies Future needs

IPv6 currently rely on tunneling traffic, creatingadditional performance degradation

No short-term return with Training staff for IPv6 Application development

High security concerns with Current support in security products More adoption of BYOD trend

Source: IPv6Observatory, NetworkComputing, Network Computing


9/31 2010 Cisco and/or its affiliates. All rights reserved. 9 2010 Cisco and/or its affiliates. All rights reserved. 9

IPv6 Market Adoption: 6lab.cisco.com/stats

~80 % of Internet Core transit (top 5% ASs) is IPv6 enabled ~ 35% of global Internet content/Web pages are reachable over IPv6 ~1% of Internet users have IPv6

Great disparities across countries



IPv6 Estimated Adoption Timeframes

EarlyAdopters

Globalization

IPv6 Government

Mandate Deadlines

IPv4/IPv6Co-existence

High RiskLow Risk Moderate Risk

2010 2012 2014

Transition

Planning

2012: Mandates take effect Globalization -WorldIPv6Launch - Massive Mobile deployment.

Transition to IPv6 forces customers to acquire product or

managed services to sustain business and customer reach

IPv6 Business Impact The Cost of Waiting Goes Up

2010: Low Impact Buying behaviour shiftlimited to mandated and early adopters

2014: IPv6 is mainstream customers without transitioninfrastructure experience reduced service levels,

diminished customer reach



US &Canada Japan Europe APAC EmergingMarket

Federal

University

Service

Provider

Tech

Enterprise

Manufacturing

Retail

Healthcare

Financial

! IPv6 Mandated

! IPv6 Deployment & Readiness Low IPv6 Awareness



0 10 20 30 40 50 60

In Progress

6 months

12 months

24 months

No plans

when are you planning to deploy IPv6 in production

July 2010

0 10 20 30 40 50 60

In Progress

6 months

12 months

24 months

No plans

April 2011

32%

40%

56%

25%

Main driver = Internet evolution: 65%



http://www.worldipv6launch.org/



DeploymentScenario

Basic Network Infrastructure

HardwareSupport

IP AddressingRoutingProtocols

Networked Infrastructure Services

DNS &DHCP

LoadBalancing &

ContentSwitching

Security(Firewalls &

IDS/IPS)

ContentDistribution

Instrumentation

Optimization(WAAS, SSLacceleration)

StaffTr

ainingandOperations

VPNAccess

Networked Device Support

Data CenterServers

ClientAccess(PCs)

PrintersCollaboration

Devices &Gateways

Sensors &Controllers

Applications & Application Suites

Web Content Management

Connectivity

Roll-ou

tReleases&

Planning

IP Services (QoS, Multicast, Mobility, Translation)

IPv6 over MPLS(6PE/6VPE)

IPv6 over IPv4 Tunnels(Configured, 6to4, ISATAP, GRE)

Dual-Stack



Establish IPv6project

managementteam

2

IPv6 TrainingStrategy -

Consultancy4

Decide IPv6architectural

solution

6Developsecurity

policy

8

Develop IPv6exceptionstrategy

10

Evaluate effecton business

model1

Assessnetwork

hardware andsoftware

3

Obtain IPv6prefix(es) 5

Testapplication

software andservices

7

Developprocurement

plan9

Build a Lab

Business Case Identified/Justified and timescale set

IPv6 is the foundation of a lifecycle management discussion



Translation (NAT)

Share IPv4 addresses Well understood Not true end-to-end

connectivity

Can createcomplications

and disruptions

Dual Stack

Easiest to deploy Requires IPv4

addresses

Tunneling(Encapsulation)

Encapsulate v6 traffic inv4 packets (and vice

versa)

Routing can besub-optimal

Requires new CPEfirmware

tunnel where youneed to

Dual stack whenyou can

translate when youmust.



IPv6Internet

IPv4Internet

IPv4 AccessNetwork

IPv4 Core

SubscriberNetwork

NAT

IPv4 Carrier Grade NAT

NATIPv6 Access

Network

Dual Stack Core

SubscriberNetwork

CE

IPv6-Only Subscriber

6!4

Dual Stack Core

v6over

v4

SubscriberNetwork

IPv6 Rapid Deployment

6rdorL2TP

6rd BR

SubscriberNetwork

v4over

v6

Dual Stack Core

4rdorDS-Lite

IPv6-Only Access Network

NAT

Dual Stack

Core+

Access(ex: DOCSIS 3.0)

SubscriberNetwork

PE

Native

Dual Stack

For more info see: http://www.cisco.com/go/cgv6

PE

CE CE

4rd BRAFTR

CE

LNS

Preserve Prepare Prosper

Service Provider Core

Service Provider Service Gateway xDSL / FTTx / Cable / WiFi /3G,4G etc.

Service Provider Subscribers Access xDSL / FTTx / Cable / WiFi / 3G,4G etc.


21/31


IPv6Internet

IPv4Internet

IPv4 AccessNetwork

IPv4 Core

SubscriberNetwork

NAT

IPv4 Carrier Grade NAT

NATIPv6 Access

Network

Dual Stack Core

SubscriberNetwork

CE

IPv6-Only Subscriber

6!4

Dual Stack Core

v6over

v4

SubscriberNetwork

IPv6 Rapid Deployment

6rdorL2TP

6rd BR

SubscriberNetwork

v4over

v6

Dual Stack Core

4rdorDS-Lite

IPv6-Only Access Network

NAT

Dual Stack

Core+

Access(ex: DOCSIS 3.0)

SubscriberNetwork

PE

Native

Dual Stack

For more info see: http://www.cisco.com/go/cgv6

PE

CE CE

4rd BRAFTR

CE

LNS

Preserve Prepare Prosper


22/31


Public addressesEnd-to-end transparent TCP session


23/31


CGN

IPv4

Sharing public IPv4 addresses => IPv4 Content traverses NATs.Challenges: Transparency to applications, location, security

CGN creates State (and logging) for every session


24/31


!"#$ $&'#()$* "+ #',"- .$/ *01$

Application # of TCP sessions

No operation 510

Yahoo top page 1020

Google image search 3060

5080

OCN photo friend 170200+

iTunes 230270iGoogle 80100

(Rakuten) 5060

Amazon 90

HMV 100

YouTube 90

Browser behavior, Port consumption

End-User experience drives up Port count (AJAX)

Source: NTT : http://www.nttv6.jp/~miyakawa/IETF72/IETF-IAB-TECH-PLENARY-NTT-miyakawa.pdfOrange Labs : http://opensourceaplusp.weebly.com/experiments-results.html


25/31


Myth: I Can Run My Business on IPv4NAT Is Not a Replacement for a Dual-stack Strategy

Web 2.0 Application Behavior Under Constrained NAT Resources

20 NAT Sessions15 NAT Sessions10 NAT Sessions30 NAT Sessions times millions of usersHow many concurrent sessions will your business require?


26/31


CGN

IPv4

IPv6

End to End model restored !IPv6 Content bypasses NAT Resources, DNS is the switch


27/31


Home networking isevolving towards more

services, including fixed/

mobile convergence

Requires easy InternetPlug & Play features

IPv6 Internet

/64

/64/64

/64/64

/64

/64

DHCPv6server

DHCPv6

relay agent

SP edge routerService Provider


28/31



29/31


30/31


Think about business continuity The size of IPv6 address space makes IPv6 compelling IPv6 is, in principle, simple and an evolution from IPv4. Most of the

things you need to care about are the same

IPv6 is NOT just about the networks team. It must be adopted by thewhole of the IT organization and needs CIO / CEO sponsorship:

IPv6 requires an architectural approach - not a box-by-box approach There are a number of deployment and transition models to consider:

Dual stack where you can Tunnel where you must Translate when you

have a gun to your head

Have a plan! Organisations should plan ahead for IPv4 addressexhaustion and prepare for IPv6


31/31

Documents

(2)IPv6 Summit - Early Experiences With IPv6 Services