Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Note to updaters: Graph is Figure 18b from
  • With such a huge address space, ISPs will have sufficient IP addresses to allocate enough addresses to every customer so that every IP device has a truly unique address---whether it’s behind a firewall or not. NAT (network address translation) has become a very common technique to deal with the shortage of IP addresses. Unfortunately, NAT doesn’t work very well for many Internet applications, ranging from old dependables, such as NFS and DNS, to newer applications such as group conferencing. NAT has also been an impediment for business-to-business direct network connections, requiring baroque and elaborate address translators to make everything work reliably, scaling poorly, and offering a highly vulnerable single point of failure. One of the goals of IPv6’s address space expansion is to make NAT unnecessary, improving total connectivity, reliability, and flexibility. IPv6 will re-establish transparency and end-to-end traffic across the Internet. Additional address space will also help the core of the Internet---it is hoped---by reducing the size and complexity of the global routing tables. Although IPv6 doesn’t solve the problems of routing in the Internet, it can help in several areas, reducing the initial size of the tables and offering a hierarchical address space. The new IPv6 addresses are large and cumbersome to deal with, so IPv6 reduces the number of people who have to read and write them. A second major goal of IPv6 is to reduce the total time which people have to spend configuring and managing systems. An IPv6 system can participate in "stateless" autoconfiguration, where it creates a guaranteed-unique IP address by combining its LAN MAC address with a prefix provided by the network router---DHCP is not needed. Of couse, DHCP is still useful for other parameters, such as DNS servers, and is supported as DHCPv6 where needed. IPv6 also offers a middle ground between the two extremes with protocols such as SLP ("Service Location Protocol"), which may make the lives of network managers easier. Although IPv4 is a simple protocol, it was not designed for giga-bit and tera-bit routers which need to look at millions of packets a second. The third major goal of IPv6 is to speed up the network, both from a performance and from a deployment point of view. IPv6 embodies the lessons learned at trying to build high-speed routers for IPv4 by changing the header of the IP packet to be more regular and to streamline the work of high-speed routers moving packets across the Internet backbone. IPv6 has fixed header sizes, and little-used IPv4 fields have been removed. A side effect of the redesign of the IP packet header is that future extensions to IPv6 are simplified: adding a new option to IP can be done without a major re-engineering of IP routers everywhere.
  • High-bandwidth multimedia and fault tolerance applications are the focus of the fourth major goal of IPv6. Multimedia applications can take advantage of multicast: the transmission of a single datagram to multiple receivers. Although IPv4 has some multicast capabilities, these are optional and not every router and host supports them. With IPv6, multicast is a requirement. IPv6 also defines a new kind of service, called "anycast." Like multicast, anycast has groups of nodes which send and receive packets. But when a packet is sent to an anycast group in IPv6, it is only delivered to one of the members of the group. This new capability is especially appropriate in a fault-tolerant environment: web servers and DNS servers could all benefit from IPv6’s anycast technology. The fifth major goal of IPv6 is VPNs, virtual private networks. The new IPSec security protocols, ESP (encapsulating security protocol) and AH (authentication header) are add-ons to IPv4. IPv6 builds-in and requires these protocols, which will mean that secure networks will be easier to build and deploy in an IPv6 world. Another aspect of IPv6 is QoS (Quality of Service). IPv6 supports the same QoS features as IPv4, including the DiffServ indication, as well as a new 20-bit traffic flow field. Although the use of this part of IPv6 is not defined, it is provided as a solid base to build QoS protocols.
  • Only really care about IPv6 in IPv4 and IPv4 in IPv6 tunnelling here - but mention the others for completeness as they are being used.
  • Slide first shows IPv4 only Click the button to see IPv6 added on top This is the dream scenario, but we needed to start doing this a few years ago.
  • Slide shows IPv4 first Click the button to get the native IPv6 overlay IPv4 hosts speak to IPv4 hosts IPv6 hosts speak to IPv6 hosts Subscriber router must be v6-capable No IPv6 to IPv4 capability (or visa versa) Requires full v4 and IPv6 SP deployment
  • Roman

    1. 1. How can Service Providers Prepare for IPv6 Deployment A Review of SP IPv4-IPv6 Co-Existence Techniques
    2. 2. What Is IPv6? <ul><li>IP stands for I nternet P rotocol which is one of the main pillars that supports the Internet today </li></ul><ul><li>Current version of IP protocol is IPv4 </li></ul><ul><li>The new version of IP protocol is IPv6 </li></ul><ul><li>IPv6 is not backward compatible with IPv4 </li></ul><ul><li>So we need to build a parallel Internet with dual stack to access content from either IPv4 only or IPv6 enable host </li></ul>
    3. 3. “ The times, They are a’ changing’” Source: (Feb 2011) IPv4 All Gone!
    4. 4. Is IPv4 really running out? <ul><li>Yes! </li></ul><ul><ul><li>IANA IPv4 free pool ran out on 3rd February 2011 </li></ul></ul><ul><ul><li>RIR IPv4 free pool will run out soon after </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><ul><li>(depends on RIR soft-landing policies) </li></ul></ul></ul><ul><li>The runout gadgets and widgets are now watching when the RIR pools will run out: </li></ul><ul><ul><li> </li></ul></ul><ul><ul><li> </li></ul></ul>
    5. 5. Background Of IPv6 Protocol <ul><li>August 1990 </li></ul><ul><ul><li>First wakeup call by Solensky in IETF on IPv4 address exhaustion </li></ul></ul><ul><li>December 1994 </li></ul><ul><ul><li>IPng area were formed within IETF to manage IPng effort [RFC1719] </li></ul></ul><ul><li>December 1994 </li></ul><ul><ul><li>List of technical criteria was defined to choose IPng [RFC1726] </li></ul></ul><ul><li>January 1995 </li></ul><ul><ul><li>IPng director recommendation to use 128 bit address [RFC1752] </li></ul></ul><ul><li>December 1995 </li></ul><ul><ul><li>First version of IPv6 address specification [RFC1883] </li></ul></ul><ul><li>December 1998 </li></ul><ul><ul><li>Updated version changing header format from 1 st version [RFC2460] </li></ul></ul>
    6. 6. Motivation Behind IPv6 Protocol <ul><li>New generation Internet need: </li></ul><ul><ul><li>Plenty of address space (PDA, Mobile Phones, Tablet PC, Car, TV etc etc  ) </li></ul></ul><ul><ul><li>Solution of very complex hierarchical addressing need, which IPv4 is unable provide </li></ul></ul><ul><ul><li>End to end communication without the need of NAT for some real time application i.e online transaction </li></ul></ul><ul><ul><li>Ensure security, reliability of data and faster processing of protocol overhead </li></ul></ul>
    7. 7. New Functional Improvement In IPv6 <ul><li>Address Space </li></ul><ul><ul><li>Increase from 32-bit to 128-bit address space </li></ul></ul><ul><li>Management </li></ul><ul><ul><li>Stateless autoconfiguration means no more need to configure IP addresses for end systems, even via DHCP </li></ul></ul><ul><li>Performance </li></ul><ul><ul><li>Fixed header sizes (40 byte) and 64-bit header alignment mean better performance from routers and bridges/switches </li></ul></ul>
    8. 8. New Functional Improvement In IPv6 <ul><li>No hop-by-hop segmentation </li></ul><ul><ul><li>Path MTU discovery </li></ul></ul><ul><li>Mobile IP </li></ul><ul><ul><li>Eliminate triangular routing and simplify deployment of mobile IP-based systems </li></ul></ul><ul><li>Virtual Private Networks </li></ul><ul><ul><li>Built-in support for ESP/AH encrypted/ authenticated virtual private network protocols; built-in support for QoS tagging </li></ul></ul><ul><li>No more broadcast </li></ul>
    9. 9. Strategies available for Service Providers <ul><li>Do nothing </li></ul><ul><ul><li>Wait and see what competitors do </li></ul></ul><ul><ul><li>Business not growing, so don’t care what happens </li></ul></ul><ul><li>Extend life of IPv4 </li></ul><ul><ul><li>Force customers to NAT </li></ul></ul><ul><ul><li>Buy IPv4 address space on the marketplace </li></ul></ul><ul><li>Deploy IPv6 </li></ul><ul><ul><li>Dual-stack infrastructure </li></ul></ul><ul><ul><li>IPv6 and NATed IPv4 for customers </li></ul></ul><ul><ul><li>6rd (Rapid Deploy) with native or NATed IPv4 for customers </li></ul></ul><ul><ul><li>Or various other combinations of IPv6, IPv4 and NAT </li></ul></ul>
    10. 10. Definition of Terms
    11. 11. Dual-Stack Networks <ul><li>Both IPv4 and IPv6 have been fully deployed across all the infrastructure </li></ul><ul><ul><li>Routing protocols handle IPv4 and IPv6 </li></ul></ul><ul><ul><li>Content, application, and services available on IPv4 and IPv6 </li></ul></ul><ul><li>End-users use dual-stack network transparently: </li></ul><ul><ul><li>If DNS returns IPv6 address for domain name query, IPv6 transport is used </li></ul></ul><ul><ul><li>If no IPv6 address returned, DNS is queried for IPv4 address, and IPv4 transport is used instead </li></ul></ul><ul><li>It is envisaged that the Internet will operate dual-stack for many years to come </li></ul>
    12. 12. IPv6 in IPv4 Tunnel <ul><li>A mechanism whereby an IP packet from one address family is encapsulated in an IP packet from another address family </li></ul><ul><ul><li>Enables the original packet to be transport over network of another address family </li></ul></ul><ul><li>Allows ISP to provide dual-stack service prior to completing infrastructure deployment </li></ul><ul><li>Tunnelling techniques include: </li></ul><ul><ul><li>IPinIP, GRE, 6to4, Teredo, ISATAP, 6rd </li></ul></ul>
    13. 13. Network Address Translation (NAT) <ul><li>NAT is translation of one IP address into another IP address </li></ul><ul><li>NAPT (Network Address & Port Translation) translates multiple IP addresses into one other IP address </li></ul><ul><ul><li>TCP/UDP port distinguishes different packet flows </li></ul></ul><ul><li>NAT-PT (NAT - Protocol Translation) is a particular technology which does protocol translation in addition to address translation </li></ul><ul><ul><li>NAT-PT has now been made obsolete by the IETF </li></ul></ul>
    14. 14. Carrier Grade NAT (CGN) <ul><li>ISP version of subscriber NAT </li></ul><ul><ul><li>Subscriber NAT can handle only hundreds of translations </li></ul></ul><ul><ul><li>ISP NAT can handle millions of translations </li></ul></ul><ul><li>Not limited to just translation within one address family, but does address family translation as well </li></ul><ul><li>Often referred to as Large Scale NAT (LSN) </li></ul>
    15. 15. Strategy One Do Nothing
    16. 16. IPv4 only Network <ul><li>The situation for many organizations today: </li></ul><ul><ul><li>No IPv6 for new host </li></ul></ul><ul><ul><li>IPv4 scaling lasts as long as IPv4 addresses are available </li></ul></ul>IPv4 Internet IPv4 host IPv4+IPv6 host Subscriber Network IPv4-only SP Network Internet IPv4 Customer Router IPv6 host IPv6 Internet IPv6
    17. 17. IPv4 only: Issues <ul><li>Pros </li></ul><ul><ul><li>Easiest and most cost effective short term strategy </li></ul></ul><ul><li>Cons </li></ul><ul><ul><li>Limited to IPv4 address availability (RIRs or marketplace) </li></ul></ul><ul><ul><li>No access to IPv6 </li></ul></ul><ul><ul><li>Negative public perception of SP as a laggard </li></ul></ul><ul><ul><li>Strategy will have to be reconsidered once IPv4 address space is no longer available </li></ul></ul>
    18. 18. Strategy Two Extend life of IPv4 network
    19. 19. Extending life of IPv4 Network <ul><li>Two ways of extending IPv4 network </li></ul><ul><ul><li>Next step along from “Strategy One: Do nothing” </li></ul></ul><ul><li>Force customers to use NAT </li></ul><ul><ul><li>Customers moved to RFC1918 address space </li></ul></ul><ul><ul><li>SP infrastructure moved to RFC1918 address space where feasible </li></ul></ul><ul><li>Acquire IPv4 address space from another organisation </li></ul><ul><ul><li>IPv4 subnet trading </li></ul></ul>
    20. 20. SP NAT in IPv4-only network <ul><li>Next step on from “doing nothing”: </li></ul><ul><ul><li>SP introduces NAT in core when IPv4 addresses run out </li></ul></ul><ul><ul><li>No access to IPv6 Internet for IPv6 enabled hosts </li></ul></ul>IPv4 Internet IPv4 host IPv4+IPv6 host Subscriber Network SP IPv4-only Network using RFC1918 addresses Internet IPv4 Customer Router IPv6 host IPv6 Internet IPv6 SP NAT Sharing IPv4 address(es)
    21. 21. Strategy Three IPv4/v6 Coexistence/Transition techniques
    22. 22. IPv4/IPv6 coexistence & transition <ul><li>Three strategies for IPv6 transition: </li></ul><ul><ul><li>Dual Stack Network </li></ul></ul><ul><ul><ul><li>The original strategy </li></ul></ul></ul><ul><ul><ul><li>Depends on sufficient IPv4 being available </li></ul></ul></ul><ul><ul><li>6rd (Rapid Deploy) </li></ul></ul><ul><ul><ul><li>Improvement on 6to4 for SP customer deployment </li></ul></ul></ul><ul><ul><ul><li>Activity of IETF Softwires Working Group </li></ul></ul></ul><ul><ul><li>Large Scale NAT (LSN) </li></ul></ul><ul><ul><ul><li>SP deploys large NAT boxes to do address and/or protocol translation </li></ul></ul></ul>
    23. 23. Dual-Stack Network <ul><li>The original transition scenario, but dependent on: </li></ul><ul><ul><li>IPv6 being available all the way to the consumer </li></ul></ul><ul><ul><li>Sufficient IPv4 address space for the consumer and SP core </li></ul></ul>IPv4 Internet IPv4 host IPv4+IPv6 host Subscriber Network Dual-Stack SP Network Internet IPv4 Customer Router IPv6 host IPv6 Internet IPv6
    24. 24. Dual-Stack Network: Issues <ul><li>Pros </li></ul><ul><ul><li>Most cost effective long term model </li></ul></ul><ul><ul><li>Once services are on IPv6, IPv4 can simply be discontinued </li></ul></ul><ul><li>Cons </li></ul><ul><ul><li>IPv4 growth limited to available IPv4 address space </li></ul></ul><ul><ul><li>Running dual-stack network requires extra staff training </li></ul></ul><ul><ul><li>IPv6 on existing IPv4 infrastructure might cost extra in terms of hardware changes (RIB and FIB memories) </li></ul></ul>
    25. 25. Dual-Stack with SP NAT <ul><li>More likely scenario: </li></ul><ul><ul><li>IPv6 being available all the way to the consumer </li></ul></ul><ul><ul><li>SP core and customer has to use IPv4 NAT due to v4 depletion </li></ul></ul>SP NAT Sharing IPv4 address(es) IPv4 Internet IPv4 host IPv4+IPv6 host Subscriber Network Dual-Stack SP Network using RFC1918 addresses Internet IPv4 Customer Router IPv6 host IPv6 Internet IPv6
    26. 26. Dual-Stack with SP NAT: Issues <ul><li>Pros </li></ul><ul><ul><li>Inherits benefits of the shared IPv4 address model </li></ul></ul><ul><ul><li>SP can offer IPv6 connectivity too </li></ul></ul><ul><ul><li>Does not postpone IPv6 deployment </li></ul></ul><ul><li>Cons </li></ul><ul><ul><li>SP incurs additional investment and operational expenditure by deploying CGN infrastructure </li></ul></ul>
    27. 27. 6rd <ul><li>6rd (Rapid Deploy) used where ISP infrastructure to customer is not IPv6 capable (eg IPv4-only BRAS) </li></ul><ul><ul><li>Customer has IPv4 Internet access either natively or via NAT </li></ul></ul><ul><ul><li>Customer IPv6 address space based on ISP IPv4 block </li></ul></ul>
    28. 28. 6rd: Issues <ul><li>Pros </li></ul><ul><ul><li>The service provider has a relatively quick way of providing IPv6 to their customer without deplying IPv6 across their infrastructure </li></ul></ul><ul><ul><li>Subscribers can readily get access to IPv6 </li></ul></ul><ul><ul><li>6rd relay and CPE are becoming available from vendors </li></ul></ul><ul><li>Cons </li></ul><ul><ul><li>6rd is not a long-term solution for transitioning to IPv6 – one further transition step to remove the tunnels </li></ul></ul><ul><ul><li>The ISP has to deploy one or several 6rd termination devices </li></ul></ul>
    29. 29. IPV6 Deployment Checklist
    30. 30. IPV6 Deployment Checklist <ul><li>Three area of a network to investigate: </li></ul><ul><li>IP Core Network </li></ul><ul><li>Customer/Access Network </li></ul><ul><li>Content hosting/Datacenter Network </li></ul>
    31. 31. IP Core Network <ul><li>For an IPv4 only network: </li></ul><ul><li>Transport link maximum capacity </li></ul><ul><li>Total network traffic </li></ul><ul><ul><li>IPv4 only </li></ul></ul><ul><li>Router memory and average CPU load </li></ul><ul><ul><li>Including IGP + EGP + Full IPV4 BGP feed </li></ul></ul><ul><li>Traffic processing engine </li></ul><ul><ul><li>Majority of the core routers process traffic by line card </li></ul></ul>
    32. 32. IP Core Network <ul><li>For a dual stack IP core network: </li></ul><ul><li>Transport link maximum capacity </li></ul><ul><ul><li>Any upgrade plan in near future? </li></ul></ul><ul><li>Total network traffic </li></ul><ul><ul><li>Total IPv4 traffic + Future IPV6 Traffic </li></ul></ul><ul><ul><li>Usually 5%~40% increased in IPV6 traffic in one year + normal network growth </li></ul></ul><ul><li>Router memory and average CPU load </li></ul><ul><ul><li>Including IGP + EGP Full IPV4 BGP feed + Full IPV6 BGP feed </li></ul></ul>
    33. 33. IP Core Network <ul><li>For a dual stack IP core network: </li></ul><ul><li>Traffic processing engine </li></ul><ul><ul><li>Majority of the core routers process traffic by line card </li></ul></ul><ul><ul><li>Increased traffic usually will not increase memory & CPU load. Good to investigate in detail </li></ul></ul><ul><li>Router with TCP/IP hardware acceleration </li></ul><ul><ul><li>Need to replace or new product need both TCP/IPv4 and TCP/IPv6 hardware acceleration support </li></ul></ul>
    34. 34. IP Core Network <ul><li>Core router software compatibility: </li></ul><ul><li>Basic IPv6 forwarding function </li></ul><ul><ul><li>OS version, Advance IP image for Cisco etc </li></ul></ul><ul><ul><li>i.e. Cisco 12.2(2)T or later (For IPv6 support) </li></ul></ul><ul><li>IPv6 supported IGP routing protocol </li></ul><ul><ul><li>I.e. OSPFv3, IS-IS etc </li></ul></ul><ul><ul><li>i.e. 12.2(15)T or later (For OSPFv3) </li></ul></ul><ul><li>BGP4/MP-BGP routing support </li></ul>
    35. 35. Customer/Access Network <ul><li>End users IPv6 support: </li></ul><ul><li>Same PC can be used for IPv6 </li></ul><ul><li>End station OS might need to upgrade </li></ul><ul><ul><li>WinXP, Vista, Winwods7, Linux, Mac OS etc </li></ul></ul><ul><ul><li>Some early version of WinXP don’t support GUI IPv6 configuration and DNS query over IPv6 transport </li></ul></ul><ul><ul><li>Windows Vista and Windows 7 have complete IPv6 support </li></ul></ul>
    36. 36. Customer/Access Network <ul><li>Service provider IPv6 support in access: </li></ul><ul><li>IPv6 supported Customer CPE </li></ul><ul><ul><li>For a list of IPv6 compliant CPE </li></ul></ul><ul><ul><li> </li></ul></ul><ul><li>Network authentication </li></ul><ul><ul><li>BRAS/PPPoE/RADIUS server </li></ul></ul><ul><li>DHCPv6 prefix delegation </li></ul><ul><li>OSS and billing system support IPv6 </li></ul>
    37. 37. Customer/Access Network <ul><li>Service provider IPv6 support in access: </li></ul><ul><li>Enterprise network is straight forward </li></ul><ul><ul><li>Mostly used Ethernet/Fast Ethernet </li></ul></ul><ul><li>ISP use hybrid access technology </li></ul><ul><ul><li>DSL, Dialup, Wimax, 3G, Wifi etc </li></ul></ul><ul><ul><li>Nothing to be changed as long as they use layer 2 services. </li></ul></ul><ul><ul><li>I.e. Some Wifi AP use IP routing, NAT, DHCPv4 services. Those devices need to be upgraded for IPv6 support. </li></ul></ul>
    38. 38. Addressing Plans – Customer <ul><li>Corporate Customers get one /48 </li></ul><ul><ul><li>Unless they have more than 65k subnets in which case they get a second /48 (and so on) </li></ul></ul><ul><li>In typical end site deployments today: </li></ul><ul><ul><li>Several ISPs give small customers a /56 or single LAN end-sites a /64, e.g.: </li></ul></ul><ul><ul><li>/64 if end-site will only ever be a LAN </li></ul></ul><ul><ul><li>/56 for medium end-sites (e.g. small business) </li></ul></ul><ul><ul><li>/48 for large end-sites </li></ul></ul>
    39. 39. Content/Datacenter Network <ul><li>Server hardware: </li></ul><ul><li>Most server hardware do not need to change for IPv6 support </li></ul><ul><ul><li>NIC do not need to change unless there is some IPv4 specific hardware acceleration </li></ul></ul><ul><li>Server OS need to check for IPv6 support </li></ul><ul><ul><li>Many server applications specially open source are IPv6 supported now </li></ul></ul><ul><ul><li>Application i.e. DNS, Mail, WWW etc also need IPv6 support </li></ul></ul>
    40. 40. Content/Datacenter Network <ul><li>IPv6 support in firewall: </li></ul><ul><li>Dual stack firewall will ensure security for both IPv4 and IPv6 packet </li></ul><ul><li>Separate process for IPv4 and IPv6 firewall </li></ul><ul><ul><li>Check both iptable and ipv6table on the server host </li></ul></ul><ul><li>SSL VPN will likely to move to IPSecVPN </li></ul>
    41. 41. Content/Datacenter Network <ul><li>IPv6 DNS support: </li></ul><ul><li>Need IPv6 glue record in root DNS </li></ul><ul><ul><li>Not all domain register support IPv6 name server glue [root server support it though] </li></ul></ul><ul><ul><li> domain also need IPv6 name server glue record [APNIC already support it] </li></ul></ul><ul><li>End to end IPv6 DNS transport is recommended </li></ul>
    42. 42. Questions?
    43. 43. Thank you! 