Multi-year Expectations: Bringing Up IPv6 and Taking Down IPv4 Fred Baker, Cisco Systems © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 The Europe/America/East Asia/ANZ Fiber Corridor Today © 2012 Cisco and/or its affiliates. All rights reserved. Map copyright 2008 TeleGeography Cisco Public 2 No Internet 71.27% Internet 28.73% Asia Pop 3.8B 825m Europe Pop 813M Africa Pop 1B Latin America Pop: 592M Middle East Pop 212M North America Pop 344M Oceania Pop 34M No Internet (Pop 4.9B) 21.5% Source: http://www.internetworldstats.com/stats.htm June 2010 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 3 - 5.9bn mobile-celluar subscriptions (87% of world population) - 1.2bn mobile broadband subscriptions (twice as many as fixed-wired broadband subscriptions) Source: ITU, 2011 © 2012 Cisco and/or its affiliates. All rights reserved. Incremental Annual GDP Growth from Every Ten Percent Points Difference in ICT Penetration High-Income Countries 1.5% Emerging Countries - By 2016, it will be $4.2tr. “If it were a national economy, the Internet economy would rank in the world’s top five.” 1.0% - In some countries, the Internet is contributing up to 8 percent of GDP. 0.0% Source: BCG, 2012 Source: World Bank, 2009 0.5% Cisco Public 4 Courtesy Bob Pepper, formerly FCC, now Cisco VP Government Affairs Global Stats: - Over 2.2bn Internet Users (33% of total population) Impact: - In 2010: The Internet for the G-20 countries, the Internet “amounted to 4.1 percent of GDP, or $2.3tr…” © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 6 ISPs and content providers are deploying IPv6 throughout their networks • There are strong pressures to do so from the perspective of business operations There is a question of timing • Networks are not on the verge of collapse • Networks are working out strategic plans to ensure their and their customer’s futures Businesses respond to their businesses realities http://www.potaroo.net/tools/ipv4/plotend.png © 2012 Cisco and/or its affiliates. All rights reserved. • Most find a need to keep their IPv4 services running while deploying IPv6 • Some find more urgent needs than others Cisco Public 7 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 8 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 9 • A provider mentioned on IPv4 and IPv4+IPv6 Customers nanog@nanog.org is starting from a miniscule IPv4 allocation Net solution: he has to deploy an IPv6 network and carry IPv4 as an overlay or in translation • That has issues for IPv4-only customers providing services Global IPv4 address space will be expensive and potentially unavailable due to APNIC policy Hence, customers will need to provide IPv6-capable applications from the start. IPv4 Overlay Native IPv6 IPv6 Service Network IPv4/IPv4 NAPT Native IPv6 • This is an extreme case For most providers, existing IPv4 resources will carry them in the near term © 2012 Cisco and/or its affiliates. All rights reserved. IPv4+IPv6 Global Internet Cisco Public 11 Providers today may have IPv4 resources for various services For a while… IPv6 deployment takes a year or more for hardware/software audit, upgrade planning, and actual deployment Hence, important to keep IPv4 running during IPv6 deployment and a while afterwards In some cases, providers are already using IPv4/IPv4 NAPT internally Especially mobile providers Net effect for them: complexity Complexity results in capital and operational costs, which are passed on to customers IPv6 Offers the opportunity to making operations simpler Consistent address space makes it easier to route traffic to a subscriber, and identify a subscriber for various reasons We have a number of customers telling us they want to limit the coexistence period within their own networks to something approximating a single equipment deployment cycle – a couple of years. © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 12 • Adoption follows an “Adoption curve”: The more users adopt, the more users adopt, over a period of time • ISP deployment relatively easy as a consensus develops that it is needed 70% Turn IPv4 off That gets us only part-way there One equipment Life cycle • How do we drive unsophisticated users and networks towards deployment? It has to appear feasible and desirable to users: users have to believe it works for their purposes Tools have to support businesses of providers and edge networks Companies need a material reason to change their contracts, which means cost and incentives © 2012 Cisco and/or its affiliates. All rights reserved. 28% “Turn IPv6 on”: entrance to coexistence phase We are here: 12.5% Worldwide Cisco Public 13 APNIC RIPE LACNIC All Countries AFRINIC ARIN 8 June 2011 http://v6asns.ripe.net/v/6?s=_ALL;s=_RIR_APNIC;s=_RIR_AfriNIC;s=_RIR_ARIN;s=_RIR_LACNIC;s=_RIR_RIPE_NCC - 25 April 2012 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 14 Network and Applications IPv6 Internet IPv4 Internet IPv6 over IPv4 Tunnel+NAT44 All IPv4 © 2012 Cisco and/or its affiliates. All rights reserved. IPv4 over IPv6 Dual-Stack IPv4 and IPv6 All IPv6 Cisco Public 15 • Primary target today: Dual Stack deployment • Solutions for difficult points in IPv4 networks • 6rd solution pioneered by Free “6to4 done right” Enables an IPv6 network to auto-tunnel over an IPv4-only domain, which might be a network or a piece of equipment • NAT64 translation Enable IPv6 hosts to access IPv4 services Enable IPv4 hosts to access IPv6-only services with IPv4-mapped addresses • Solutions for IPv4 turn-down Expect ds-lite and others Translation not likely to be useful in this phase, as translation doesn’t facilitate IPv4 access to non-mapped IPv6 addresses © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 16 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 17 • Every 3-5 years, the Internet fundamentally changes in the payload it carries 1990: FTP, Network News, telnet 1992: World Wide Web, SMTP, multicast, experimental voice/video 1995: WWW with multiple sessions in parallel, Voice on IP 2000: Peer to Peer file sharing in various forms 2003: Web 2.0 applications like Myspace, Facebook, BitTorrent File Sharing 2008: Cyberlockers replacing file sharing, Hadoop as a data center model 1990-2011: Rise of video in various forms Next… • On the commercial backbone, video is becoming dominant, primarily from ICPs that colocate with some or all of an ISP’s POPs • In private networks (Smart Grid, Health Care, Public and Private Safety) we see distributed telemetry and distributed control. © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 18 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 19 • Imagine a high end home network: Audio/Video Wireless Telecommuting Home Area Network “Home Area Network” ISP His Office • What is the HAN? Her Network connecting sensors in Office the home Communications with utilities Services to residents Home Wireless © 2012 Cisco and/or its affiliates. All rights reserved. A/V LAN HDTV Cisco Public 20 • Infrared • Motion sensors Health Network ISP • EKG • Pedometers • … His Office Her Office Home Wireless © 2012 Cisco and/or its affiliates. All rights reserved. A/V LAN HDTV Cisco Public 21 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 22 “ RFC 6540, BCP 177: “IPv6 Support Required for All IP-Capable Nodes” © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 23 • CPE Router Requirements Deployment of IPv6 to residential and SOHO networks • IPv4/IPv6 Interoperation: translation IPv6-only Networks Deployment of IPv6 to content providers © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 24 • Network Architecture IPv4 Residential Network IPv6 Residential Network Other uses ISP • General Requirements IPv6 Node Requirements • WAN-side Requirements Prefix deployment with DHCPv6 Service Provider Interaction His Office Her Office • LAN-side Requirements PCP • Transition Technologies Home Wireless A/V LAN HDTV IPv6 Rapid Deployment (6rd) IPv4 sunset (ds-lite, 4rd) © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 25 • We have several drafts that look at service provider networks that move their customers to IPv6-only networks. • In Mobile (3GPP, LTE) Networks draft-chen-v6ops-nat64-experience-01.txt (China Mobile) draft-ietf-v6ops-464xlat-02.txt (several providers) • In Wireline Networks draft-ietf-v6ops-ivi-icmp-address-01.txt (CERNET) draft-ietf-v6ops-wireline-incremental-ipv6-01.txt (Rogers) • For Enterprise/Content Provider draft-ietf-v6ops-icp-guidance-00.txt draft-sunq-v6ops-contents-transition-03.txt (China Telecom) draft-yang-v6ops-fast6-00.txt (Huawei) draft-yang-v6ops-fast6-pppoe-02.txt (Huawei) © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 26 • DNS64: Translate DNS records: A->AAAA • Translator: Stateless mode (SIIT) Uses Service Provider Prefix, IPv4 prefix embedded in IPv6 prefix Scalable translation IPv4<->IPv6 Stateful mode (NAT64) similar to IPv4/IPv4 NAT Permits session initiation IPv6-native -> IPv4 hosts No session initiation IPv4 -> IPv6-native • Effect: Encourage movement of IPv4 servers to IPv6only network Facilitate deployment of IPv6-only networks © 2012 Cisco and/or its affiliates. All rights reserved. IPv4 Internet DNS ALG IPv6 Network Cisco Public 27 © 2012 Cisco and/or its affiliates. All rights reserved. IPv6 Core Source: 172.16.0.0/12 Source: 172.16.0.0/12 Stateful NAT64 .2. Stateful NAT64 .3. Source: 172.16.0.0/12 10.0.0.0/8 Stateless NAT64 .3. Stateful NAT64 .1. Destination: Destination: Destination: 2001:db8:2:3::IPv4 2001:db8:2:2::IPv4 2001:db8:2:1::IPv4 10.0.0.0/8 Stateless NAT64 .2. Source Source Source 2001:db8:1:3::IPv4 2001:db8:1:2::IPv4 2001:db8:1:1::IPv4 10.0.0.0/8 Stateless NAT64 .1. IPv4 Content Provider Data Center IPv4 Content Provider Data Center IPv4 Internet Cisco Public 28 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 30 • Have you assessed a risk and security related to IPv6? Planned the implementation of the mitigation solutions? • Is the relevant staff trained for IPv6? • Has an IPv6 assessment of your infrastructure and applications been performed? What hardware or software needs an update? • Did you get IPv6 address space from the RIR or your Service Provider with an addressing plan? • Do your upstream service providers support IPv6? Have you negotiated service agreements for it? • Are your purchasing, development and service policies and guidelines aligned for IPv6? • Do you have a deployment and maintenance plan in place? © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 31 Thank you.