We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byAkira Raby
Modified over 2 years ago
IPv6 Address and Migration Challenges Peter.J.Willis@bt.com
© British Telecommunications plc 20012 Contents - IPv6 Addresses sTLAs are too small. NLAs are too small. IPv6 Address Hierarchies, which one? Commercial restraints caused by the address allocation rules. Alternative schemes. My crystal ball.
© British Telecommunications plc 20013 Contents IPv6 Deployment Challenges - Cost modelling of migration. - Suggested strategy for migration Where are the NGN applications? Home Networks - Home gateways - Addressing & naming in context - Its about communications not architectures.
© British Telecommunications plc 20014 Why is address structure important? Address structure is more than the total number of bits. It is the address format & structure that defines the fundamental nature of a network. (Think of the close relationship between IPv4 address structures & the Internet.) The structure can define the way you build networks. If you get the structure wrong it costs you money to build a network to make that address structure work. (Think of the cost of memory for all those IPv4 routes.)
© British Telecommunications plc 20015 Registries eg. 2001::/23 Internet Service Providers (ISP’s) Exchanges / Carriers eg. 2001:618::/35 Sites / SME’s / Home Users (Site) eg. 2001:618:100B::/48 Mobile Phones / Home Apps PDA’s IPv6 – Addressing Issues eg. 2001:618:100B:F8:/64 Internet Assigned Numbers Authority
© British Telecommunications plc 20016 sTLAs Are Too Small Currently IPv6 network service providers (NSP) are using sub-TLAs during the boot- strap phase of IPv6. The sTLA is a /35 The first 13 bits after the /35 is the NLA (Next-Level Aggregation) Identifier. This NLA space has to be used to address the customers & describe the NSP topology. If the customer is an ISP then they too have to use the NLA space. (Ripe-196)
© British Telecommunications plc 20017 NLA Field Explained Sub-TLA holders have 13bits of Next Level Aggregation (NLA ID) Example 1 Example 2 NLA1 NLA2 /35 /40 /48 NLA1 NLA2 /35 /43 /48 NLA1, 5 bit = 32 ISPs & NLA2, 8 bits = 256 End sites NLA1, 8 bits = 256 ISPs & NLA2, 5 bits = 32 End sites
© British Telecommunications plc 20018 Sub-TLA IDs - Use the reserved field NLA field can grow from 13 bits to 19 bits using the reserved bits subTLA NLA SLA Interface 2001:618::/29 19 16 64 bits /29 /48 /64 19 bits = 524,288 /48’s per subTLA /29 /35 /48 /64 subTLA NLA SLA Interface 2001:618::/35 13 16 64 bits 13 bits = 8,192 /48’s per subTLA RESRES
© British Telecommunications plc 20019 Using the NLA Hierarchically In NGNs with billions of attached devices the only way networks will scale will be with a deep hierarchy. To keep the routing table to a minimum size each layer of the hierarchy must do near perfect routing aggregation. Lets explore some network hierarchies and see how many bits are required:
© British Telecommunications plc 200110 Network Addressing Scheme1 Hierarchical Level SizeNumber of bits Continent73 Country2218 State/County646 Town1287 Line/Site102410 Total = 34 bits Remember current NLA size = 24 bits. +8 more reserved bits
© British Telecommunications plc 200111 Network Addressing Scheme2 Hierarchical Level SizeNumber of bits International backbone 10 PoPs4 Continental backbone 20 PoPs5 Country backbone 1000 PoPs10 Lines to customers 1024 lines10 Total = 29 bits Remember current NLA size = 24 bits. +8 more reserved bits
© British Telecommunications plc 200112 Network Addressing Scheme3 and NLA Size Conclusion Assume very efficient address allocation without any network hierarchy (not a recommended design!)then how many lines to customers could we have with a 24 bit NLA? 2^24 = 16 Million. Using the Huitema-Durand method then 31 bits is required to address 30 Million homes. (See notes) Simply a NLA of 24 bits is not big enough for a global network operator nor big enough for a UK operator aiming to reach every home. A 34 bit NLA should be sufficient.
© British Telecommunications plc 200113 IPv6 Address Hierarchies, which one? FPFP RESRES TLA NLA SLA INTERFACE ID ID ID ID /3 /16 /24 /48 /64 RFC 2374 “An Aggregatable Global Unicast Address Format” TLA sub NLA SLA INTERFACE ID TLA ID ID ID FPFP RESRES /3 /16 /29 /35 /48 /64 RIPE 196 “Provisional IPv6 Assignment and Allocation Policy Document” TLA sub NLA SLA INTERFACE ID TLA ID ID ID FPFP /3 /16 /29 /48 /64 RFC 2450 “Proposed TLA and NLA Assignment Rules
© British Telecommunications plc 200114 IPv6 Address Hierarchies,even more? global routingSubnet INTERFACE prefix IDID n bitsm bits 128-n-m bits draft-ietf-ipngwg-addr-arch-v3-06.txt Now an RFC. See also http://www.apnic.net/meetings/12/sigs/joint_ipv6.html RIPE 40 1st October Prague http://www.ripe.net /ripe/meetings/current/ripe-40/index.html
© British Telecommunications plc 200115 Commercial restraints caused by the address allocation rules. The TLA/NLA/SLA structuring and address assignment rules drives a commercial model of customers dependent on Tier 2 ISPs dependent on Tier 1 ISPs. This is not the way it works with 3G! Slow start rules provide unfair competitive advantage to established & large networks. Address utilisation targets if set too high cause a flattening of network hierarchy which leads to higher engineering costs.
© British Telecommunications plc 200116 Alternatives draft-hain-ipv6-pi-addr-00.txt “An IPv6 Provider-Independent Global Unicast Address Format”. The users IPv6 address is derived from their latitude and longitude. Increase the number of bits in the global routing prefix by reducing the number in the interface id. Then allow any ISP unqualified address space. The ideal situation is that every ISP has enough address space to address everyone.
© British Telecommunications plc 200117 My Crystal Ball In the short term looking to see some improvement in the IPv6 address structure and allocation rules in the current RIRs considerations. In the long term I expect IPv6.1 which will make much better use of the 128 bit address space.
© British Telecommunications plc 200118 IPv6 Deployment Strategy: Cost Modelling of IPv6 Migration Understanding the business case for deploying IPv6 is the first key step. Understanding the costs of IPv6 is key and it is the costs that will form a significant obstacle. Your IPv6 deployment strategy should seek to minimise costs and maximise commercial advantages.
© British Telecommunications plc 200119 IPv6 Migration Costs Study The study looked at the whole costs of migrating to IPv6 for the following scenarios: - A Big or Tier1 ISP - A Big enterprise - A SME - A Dial-ISP The study examined the costs of migrating now and migrating in 5 years time. Extra maintenance costs included.
© British Telecommunications plc 200120 IPv6 Migration Costs Assumptions Attempted to include all costs, including new software, memory, hardware, OSS and desktop upgrades. Extra maintenance costs assume the extra costs of running IPv6 on an existing IPv4 network. That is assuming a dual-stack scenario. Once IPv4 is phased out then extra- maintenance costs no longer apply. Application migration costs not included but allowed for with BITS s/w for legacy IPv4 applications that could not be migrated.
© British Telecommunications plc 200121 Big ISP Migration Costs Big ISP equivalent to a Tier 1 ISP Now +5 Years Cost/ customer £1K £2K £4K Max cost Min cost
© British Telecommunications plc 200122 Big ISP Extra Maintenance Costs Big ISP equivalent to a Tier 1 ISP Now +5 Years Cost/ customer £50 £100 £200 Max cost Min cost
© British Telecommunications plc 200123 Big Enterprise Migration Costs 100,000 Desktops Now +5 Years £1K Max cost Min cost £500 £250 Cost/ Employee
© British Telecommunications plc 200124 Big Enterprise Extra Maintenance Costs 100,000 Desktops Now +5 Years £100 Max cost Min cost £50 £25 Cost/ Employee
© British Telecommunications plc 200125 SME Migration Costs Now +5 Years £1K Max cost Min cost £500 £250 Cost/ Employee
© British Telecommunications plc 200126 SME Extra Maintenance Costs Now +5 Years £10 £5 Cost/ Employee £15
© British Telecommunications plc 200127 Dial-ISP Migration Costs 1 Million lines Now +5 Years Max cost Min cost £20 £10 Cost/ Line £30
© British Telecommunications plc 200128 Dial-ISP Extra Maintenance Costs 1 Million lines Now +5 Years £5 £2.5 Cost/ Line £7.5
© British Telecommunications plc 200129 Recommendations Do not upgrade to IPv6 now but plan to do it in about 5 years time. Ensure as kit & software is churned or upgraded for operational reasons that it is upgraded to be IPv6 capable. Start work on your IPv6 upgrade strategy now. Waiting for the killer IPv6 application or until your competition has upgraded to IPv6 could be more expensive than a planned gradual upgrade in IPv6 capability. Once IPv6 is deployed shortening the life time of IPv4 will reduce maintenance costs.
© British Telecommunications plc 200130 Where are the NGN applications? NGN is not the same as IPv6. What is stopping NGN applications being deployed in IPv4? If you have an application but can’t deploy it because of a lack of IPv4 addresses or because IPv6 not widely deployed we need to know!
© British Telecommunications plc 200131 Home Networks and IPv6 When thinking about naming & addressing we need to consider the context of the communications. The residential/home gateway may be a better place to manage communications in & out of the house. The Internet’s end-to-end architecture may no longer be appropriate. Architectures develop as technology changes. “Meta networks” with “intelligent” translation of messages at the edge of network domains may now be more appropriate. SIP & NAT are examples. This gives security & control (no more dDOS attacks). Given a “SIP” that works then global IP addresses are no longer needed - communications routed on names. (XML routing is another alternative tech.)
© British Telecommunications plc 200132 Conclusion As an industry we need to make sure we don’t make the same “Class A,B,C” mistake we made with IPv4. That is not thinking about the future. If IPv6 happens the costs of migrating to it can be mitigated by an IPv6 upgrade strategy applied now. Don’t become religious about architectural principles that were created in a different technological era.
Thank you. Peter.J.Willis@bt.com
Is the IPv6 Address Space Too Small?
Introduction to IP Addressing & IPv6 Deployment Status.
IPv6: The Future of the Internet? July 27th, 1999 Auug.
IAB/IESG Recommendations on IPv6 Address Allocation Bob Hinden at RIPE Sept Brian Carpenter at ARIN Oct Alain Durand at APNIC Oct
TU/e technische universiteit eindhoven WebNet 2001October 26, XML to XML through XML Pim Lemmens Geert-Jan Houben Eindhoven University of Technology.
Possible Broadband Deployments Post IPv4 Completion Alain Durand, Work in progress #include.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 9: Subnetting IP Networks Introduction to Networking 9.0.
APNIC IPv6 Allocation Update IPv6 Technical SIG APRICOT, Bangkok 5 March 2002.
1 IPv6 HD Ratio ARIN Public Policy Meeting April 2005 Geoff Huston APNIC.
R I P E N e t w o r k C o o r d i n a t i o n C e n t r e. h t t p : / / w w w. r i p e. n e t. n c r i p e. n e t 1 The Internet Registry System IPv4.
ARIN Update Marc Crandall ARIN Advisory Council. Policy Discussions Last Call – Equitable IPv4 Run-Out When ARIN gets its last /8, instead of giving ISPs.
Demystifying IPv6: Ensuring a Smooth Transition John Curran ARIN President & CEO.
Internet Number Resources 1. Internet IPv4 addresses IPv6 addresses Autonomous System number Fully Qualified Domain Name Key Internet resources.
A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E APNIC Open Address Policy Meeting Address Policy SIG October 26th, Brisbane.
LACNIC Policy Update Roque Gagliano LACNIC. Current Policies Proposals - LACNIC As a result of the Open Policy Forum at LACNIC XI four policy proposals.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 8: Subnetting IP Networks Network Fundamentals.
Planning Your Conversion from IPv4 to IPv6 John Curran ARIN President & CEO.
IPv4 to IPv6 transition ALS Capacity Building April 2014 Leo Vegoda.
Migration to IPv6 – Has Tomorrow Finally Arrived? John Curran ARIN President & CEO.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Addressing the Network – IPv4 Network Fundamentals – Chapter 6.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 1 v3.1 Module 9 TCP/IP Protocol Suite and IP Addressing.
Analysis of the impact of IPv4 transfer policies; Issues and solutions Dawit Bekele & John Schnizlein Internet Society AfriNIC-9 Mauritius.
Università di AnconaCoopIS01 September 6, C OOPERATION S TRATEGIES FOR I NFORMATION I NTEGRATION Maurizio Panti, Luca Spalazzi, Loris Penserini
Mirjam Kühne 1 IPv6 Registration at the RIPE NCC IPv6 Forum, Berlin Mirjam Kühne, RIPE NCC.
Monitoring very high speed links Gianluca Iannaccone Sprint ATL joint work with: Christophe Diot – Sprint ATL Ian Graham – University of Waikato Nick McKeown.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 EN0129 PC AND NETWORK TECHNOLOGY I IP ADDRESSING AND SUBNETS Derived From CCNA Network Fundamentals.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 1: Introduction to Scaling Networks Scaling Networks.
Where Do We Go From Here? John Curran ARIN President & CEO.
Sharing a single IPv4 address among many broadband customers
Supporting Internet Growth and Evolution: The Transition to IPv6 SANOG January George Kuo Member Services Manager, APNIC.
IPv6: The Next Generation Internet Protocol CEOS WGISS 18: Beijing, China September 2004 Dave Hartzell Computer Sciences Corp, NASA Ames
IPv6: No Longer Optional John Curran President & CEO, ARIN.
Business Drivers / Why Now Technology Drivers How all of this affects our business and our customers Frequently Asked Questions Appendix.
John Rullan Cisco Certified Instructor Trainer Thomas A. Edison CTE HS Stephen Lynch Network Architect, CCIE #36243 ABS Technology Architects IPv6 Addressing.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 1 v3.1 Module 10 Routing Fundamentals and Subnets.
IPv6 Addressing Internet2 IPv6 Workshop Research Triangle Park, NC 5-7 March 2002.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPN Technology Introducing MPLS VPN Architecture.
1 Optical network CERNET's experience and prospective Xing Li, Congxiao Bao
IPv6 allocations to closed networks LACNIC VI Mar 29 – Apr 1, 2004 Montevideo, Uruguay.
IPv6 Transition Roque Gagliano What is transition? IPv4 only.IPv4 Only Bone is borned IPv4 Only Experimental IPv6. Majority:
1 IPv6 Unique Local Addresses Update on IETF Activity ARIN Public Policy Meeting April 2005 Geoff Huston APNIC.
Internet Addressing A Technical Overview David R. Conrad Internet Software Consortium.
1 MCT620 – Distributed Systems Workshop 1 – Lecture 3 Introduction to Networks.
IP-Internet Protocol Addresses. Computer Engineering Department 2 Addresses for the Virtual Internet The goal of internetworking is to provide a seamless.
IPv4 Addresses. Internet Protocol: Which version? There are currently two versions of the Internet Protocol in use for the Internet IPv4 (IP Version 4)
Routing Items from IAB Utrecht Workshop Geoff Huston IAB.
Internet Protocol Addresses What are they like and how are the managed? Paul Wilson APNIC.
A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E Internet Registry allocation and assignment Policies.
© 2017 SlidePlayer.com Inc. All rights reserved.