DOCSLIB.ORG

Etsi Tr 101 569 V1.1.1 (2012-12)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Etsi Tr 101 569 V1.1.1 (2012-12) ETSI TR 101 569 V1.1.1 (2012-12) Technical Report Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; Cable Network Transition to IPv6 2 ETSI TR 101 569 V1.1.1 (2012-12) Reference DTR/ATTM-003018 Keywords cable, DOCSIS, HFC, IPv6 ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © European Telecommunications Standards Institute 2012. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI 3 ETSI TR 101 569 V1.1.1 (2012-12) Contents Intellectual Property Rights ................................................................................................................................ 6 Foreword ............................................................................................................................................................. 6 Introduction ........................................................................................................................................................ 6 1 Scope ........................................................................................................................................................ 7 2 References ................................................................................................................................................ 7 2.1 Normative references ......................................................................................................................................... 7 2.2 Informative references ........................................................................................................................................ 7 3 Symbols and abbreviations ..................................................................................................................... 11 3.1 Symbols ............................................................................................................................................................ 11 3.2 Abbreviations ................................................................................................................................................... 12 4 Transition to Next Generation IP ........................................................................................................... 16 4.1 General Considerations .................................................................................................................................... 16 4.2 Development of Transition Technologies ........................................................................................................ 18 4.3 End-to-end IPv6 and Network Support Systems and Applications .................................................................. 19 4.4 Network Management ...................................................................................................................................... 20 4.5 MSO Considerations ........................................................................................................................................ 20 5 Background and Concept of Transition .................................................................................................. 21 5.1 Broadband Cable Network Providers ............................................................................................................... 21 5.2 IP Connectivity in Cable Networks .................................................................................................................. 22 5.2.1 Customer Host ............................................................................................................................................ 22 5.2.2 Home Network ............................................................................................................................................ 22 5.2.3 Access Gateway .......................................................................................................................................... 22 5.2.4 Access Network .......................................................................................................................................... 23 5.2.5 Headend ...................................................................................................................................................... 23 5.2.6 Internet ........................................................................................................................................................ 23 6 Analysis of Cable Network Deployments .............................................................................................. 23 6.1 Overview .......................................................................................................................................................... 23 6.2 End-user CPE ................................................................................................................................................... 24 6.2.1 Stand-alone Cable Modem .......................................................................................................................... 25 6.2.2 Home Router ............................................................................................................................................... 25 6.2.3 eRouter ........................................................................................................................................................ 25 6.2.4 Set-top Box ................................................................................................................................................. 25 6.2.5 Consumer Equipment ................................................................................................................................. 25 6.2.6 E-MTA ........................................................................................................................................................ 26 6.3 Access Network ................................................................................................................................................ 26 6.3.1 DHCP .......................................................................................................................................................... 26 6.3.2 TFTP ........................................................................................................................................................... 26 6.3.3 ToD ............................................................................................................................................................. 27 6.4 CMTS ............................................................................................................................................................... 27 6.5 Core Network ................................................................................................................................................... 27 6.6 Datacentre......................................................................................................................................................... 27 6.6.1 DNS ............................................................................................................................................................ 28 6.6.1.1 Authoritative DNS ................................................................................................................................ 28 6.6.1.2 Recursive DNS ...................................................................................................................................... 28 6.6.2 Email ........................................................................................................................................................... 28 6.6.3 Web Portals ................................................................................................................................................. 28 6.7 Support Services ..............................................................................................................................................
Load more

Recommended publications
  • A Review and Qualitative Analysis of Ipv6 and Ipv4 Interoperability Technologies
    A Review and Qualitative Analysis of IPv6 and IPv4 Interoperability Technologies Antti Maula Helsinki University of Technology [email protected] Abstract structured as follows: section 2 contains descriptions of ex- isting solutions and their main technical features. Section 3 Deployment of IPv6 has been delayed even though the stan- presents some discussion about the state of the technologies dard has existed for over ten years and the number of free and section 4 presents the required future work and the final IPv4 addresses is decreasing fast. Some obstacles in deploy- conclusions are drawn in section 5. ment are economic but also technical issues remain. The Internet cannot be converted to IPv6 overnight, thus a transi- tion period is required during which both protocols co-exist 2 Related technologies and work together seamlessly. There is a vast amount of in- teroperability technologies available and this paper presents This section presents the existing IPv6 and IPv4 interop- proposed solutions to operate IPv6-only network segments erability technologies and their technical details. Interop- in cooperation with IPv4-only network segments. erability technologies include techniques which allow use of isolated IPv6 subnets in mostly IPv4 based Internet and KEYWORDS: IPv6, IPv4, interoperability, technology re- all of these technologies are intended to be used only dur- view, qualitative analysis ing the transition period and they should automatically stop working when underlying network infrastructure has imple- mented full IPv6 support. Some of the methods presented 1 Introduction here are implemented only by software while others re- quire additional hardware to function. These two models IP protocol version 4 (IPv4), which is currently used in most are namely “End-host” and “Middlebox” architectures, in parts of the internet, is becoming outdated.
    [Show full text]
  • Performance Analysis and Comparison of 6To4 Relay Implementations
    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 4, No. 9, 2013 Performance Analysis and Comparison of 6to4 Relay Implementations Gábor Lencse Sándor Répás Department of Telecommunications Department of Telecommunications Széchenyi István University Széchenyi István University Győr, Hungary Győr, Hungary Abstract—the depletion of the public IPv4 address pool may delegated the last five “/8” IPv4 address blocks to the five speed up the deployment of IPv6. The coexistence of the two Regional Internet Registries in 2011 [3]. Therefore an versions of IP requires some transition mechanisms. One of them important upcoming coexistence issue is the problem of an is 6to4 which provides a solution for the problem of an IPv6 IPv6 only client and an IPv4 only server, because internet capable device in an IPv4 only environment. From among the service providers (ISPs) can still supply the relatively small several 6to4 relay implementations, the following ones were number of new servers with IPv4 addresses from their own selected for testing: sit under Linux, stf under FreeBSD and stf pool but the huge number of new clients can get IPv6 addresses under NetBSD. Their stability and performance were investigat- only. DNS64 [4] and NAT64 [5] are the best available ed in a test network. The increasing measure of the load of the techniques that make it possible for an IPv6 only client to 6to4 relay implementations was set by incrementing the number communicate with an IPv4 only server. Another very important of the client computers that provided the traffic. The packet loss and the response time of the 6to4 relay as well as the CPU coexistence issue comes from the case when the ISP does not utilization and the memory consumption of the computer support IPv6 but the clients do and they would like to running the tested 6to4 relay implementations were measured.
    [Show full text]
  • Routing Loop Attacks Using Ipv6 Tunnels
    Routing Loop Attacks using IPv6 Tunnels Gabi Nakibly Michael Arov National EW Research & Simulation Center Rafael – Advanced Defense Systems Haifa, Israel {gabin,marov}@rafael.co.il Abstract—IPv6 is the future network layer protocol for A tunnel in which the end points’ routing tables need the Internet. Since it is not compatible with its prede- to be explicitly configured is called a configured tunnel. cessor, some interoperability mechanisms were designed. Tunnels of this type do not scale well, since every end An important category of these mechanisms is automatic tunnels, which enable IPv6 communication over an IPv4 point must be reconfigured as peers join or leave the tun- network without prior configuration. This category includes nel. To alleviate this scalability problem, another type of ISATAP, 6to4 and Teredo. We present a novel class of tunnels was introduced – automatic tunnels. In automatic attacks that exploit vulnerabilities in these tunnels. These tunnels the egress entity’s IPv4 address is computationally attacks take advantage of inconsistencies between a tunnel’s derived from the destination IPv6 address. This feature overlay IPv6 routing state and the native IPv6 routing state. The attacks form routing loops which can be abused as a eliminates the need to keep an explicit routing table at vehicle for traffic amplification to facilitate DoS attacks. the tunnel’s end points. In particular, the end points do We exhibit five attacks of this class. One of the presented not have to be updated as peers join and leave the tunnel. attacks can DoS a Teredo server using a single packet. The In fact, the end points of an automatic tunnel do not exploited vulnerabilities are embedded in the design of the know which other end points are currently part of the tunnels; hence any implementation of these tunnels may be vulnerable.
    [Show full text]
  • IPV6 MIGRATION and ADOPTION in INDIA by Shweta Satao
    Episteme: an online interdisciplinary, multidisciplinary & multi-cultural journal Bharat College of Arts and Commerce, Badlapur, MMR, India Volume 8, Issue 3 December 2019 IPV6 MIGRATION AND ADOPTION IN INDIA By Shweta Satao Abstract One of the major reasons for the IPv6 transition is because the allocation of IPv4 address space is running out of control and is gradually being exhausted. Though the Regional Internet Registries of all the continents are still allocating IPv4 addresses. Annually hundreds of millions of new smart phones that require internet connectivity are being sold. These demands for mobile phone have made the demand for internet connectivity to be increasing exponentially. We are in the age of smart mobile devices, social networking, and cloud computing and other new internet developments that are linked to the internet. There is need for Service Providers to ensure there is good, smooth and reliable internet connectivity via IP addresses. These makes IP addresses critical resources that sustain the business growth of service providers and also sustains an exponential economic growth generated through the internet. As hundreds of millions of mobile users are connected to the internet, there is need for a network that is ready for an internet that have both IPv4 and IPv6 addresses “IPv4 and IPv6 networks are not directly interoperable but the technologies used in the transition mechanisms allow hosts on either network to be involved in networking with opposing networks”. The transition mechanisms include: - Dual Stack Techniques - IPv6 over IPv4 tunneling techniques: 6to4 tunnel, Tunnel broker, Manually Configured Tunnel, ISATAP tunnels, IPv6 over IPv4 GRE tunnel.
    [Show full text]
  • Allied Telesis Solutions Tested Solution:Ipv6 Transition Technologies
    Allied Telesis Solutions IPv6 Transition Technologies Tested Solution: IPv6 Transition Technologies Moving a network from IPv4 addressing to IPv6 addressing cannot be performed in a single step. The transition necessarily proceeds in stages, with islands of IPv6 developing within the IPv4 network, and gradually growing until they cover the whole network. During this transition process, the islands of IPv6 need to be able to communicate with each other across the IPv4 network. Additionally, it is desirable to be able to transition some network functions across to IPv6 while the majority of the network is still using IPv4. Allied Telesis provides robust solutions for IPv4-to-IPv6 network transitioning, using IPv6 tunneling and dual IPv4/IPv6 network management. The Allied Telesis IPv6 transition technologies integrate seamlessly with the complementary facilities provided within Microsoft server and workstation operating systems. The Allied Telesis IPv6 transition solution will be presented here by a detailed description of an example IPv4/IPv6 hybrid network, consisting of Allied Telesis switches and servers and workstations running various versions of Microsoft Windows Network topology The example network used in this example consists of two sections of IPv4 network, and a section of pure IPv6 network. IPv4 133.27.65.34 v4 router 139.72.129.56/24 Vista 136.34.23.11/24 133.27.65.2 6to4 host/router x600 6to4 relay XP 2002:8B48:8139::10/64 136.34.23.10/24 139.72.129.57/24 2002:8B48:8139:1001::12/64 6to4 host/router IPv6 router Server 2008 2002:8b48:8139:1003::12/642002:8b48:8139:1002::12/64 ISATAP router 2002:8b48:8139:1003::10/64 192.168.2.254 192.168.2.54 IPv6 v4 router Server 2008 192.168.3.254 2002:8b48:8139:1002::10/64 192.168.3.11 IPv4 8000S ISATAP The workstations in the upper IPv4 network are able to communicate using both IPv4 and IPv6.
    [Show full text]
  • Internet Engineering Task Force G. Chen Internet-Draft T
    Internet Engineering Task Force G. Chen Internet-Draft T. Yang Intended status: Informational L. Li Expires: January 5, 2012 H. Deng China Mobile July 4, 2011 IPv6 Practices on China Mobile IP Bearer Network draft-chen-v6ops-ipv6-bearer-network-trials-00 Abstract This memo has introduced IPv6 practices on China Mobile IP bearer network, in which IP backbone network and broadband access routers have been covered. In the practice, IPv6 protocol conformance and data packages forwarding capabiliteis have been tested in multi- vendors environments. Several IPv6 transition schemes have been deployed to validate interoperabilities. Based on concrete testing data, IPv6-enable deployment experiencies have been learned to share with community. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on January 5, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document.
    [Show full text]
  • Ipv6 – from Assessment to Pilot
    IPv6 – From Assessment to Pilot James Small CDW Advanced Technology Services Session Objectives State of Things Business Case Plan Design Implement Security & Operations Current Trends Depletion replaced by Growth Population penetration Geoff Huston’s IPv4 Address Report Multiple mobile device penetration The Internet of Things – M2M The Internet of Everything Current Trends Global growth: Penetration doubling every 9 months US penetration: IPv6 Deployment: 24.76% Prefixes: 40.78% Transit AS: 59.48% Content: 47.72% Google’s global IPv6 statistics graph Users: 3.92% Relative Index: 6.2 out of 10 Global IPv6 growth Graphs from Cisco Live Orlando 2013 – PSOSPG 1330 • US Growth/Penetration is Double the Global Rate • Critical mass in US next year (10% penetration) Opinions on Action Gartner – Enterprises must start upgrading their Internet presence to IPv6 now Deloitte – In short, we recommend starting (v6 deployment) now “Starting sooner can give organizations enough lead-time for a deliberate, phased roll-out, while waiting could lead to a costly, risky fire drill.” Roadmap State of things Business Case Plan Design Implement Security & Operations New Trends IPv6-Only Data Centers and Networks (especially mobile ones) on the rise Internet-of-Things – many key protocols are IPv6 only (IPv4 doesn’t have necessary scale) Many new trends are IPv6-Only (e.g. IoT) Smart Factories/Buildings/Cities/Grid Intelligent Transportation System General Business Case 65% of Cisco Enterprise Technology Advisory Board members will have IPv6 web sites by the end of this year (2013) Top drivers for IPv6 BYOD Globalization Internet Evolution/Internet Business Continuity (B2B/B2C) Legal Business Cases Mobile (Tablets/Smartphones) LTE/4G an IPv6 technology Multinational Firms – Europe far down the IPv6 path, where are you compared to your counterparts? Federal – Goal for full IPv6 deployment by 2014 with some trying to eliminate IPv4 by years end (VA) Legal Business Cases IPv6 Critical mass is coming next year (2014) – B2B, B2C, M2M, and other innovation will follow.
    [Show full text]
  • Deploying Ipv6 in Fixed and Mobile Broadband Access Networks
    Deploying IPv6 in Fixed and Mobile Broadband Access Networks Tomás Lynch – Ericsson Jordi Palet Mar8nez – Consulintel Ariel Weher – LACNOG Agenda (1/2) • IPv6 in Broadband Networks – Where are we? • IPv6 TransiHon Mechanisms for Broadband Networks • IPv6 Prefix Assignment • Deployment of IPv6 in Mobile Broadband Networks • Deployment of IPv6 in PPPoE & IPoE Networks • Deployment of IPv6 in Cable Networks Agenda (2/2) • Current IPv6 Deployments in Broadband Access Networks • Other Systems Involved in IPv6 Deployment • IPv6 TransiHon Planning • Useful Documents • Conclusions IPv6 in Broadband Networks Where Are We? IPv4 Yes, the IPv4 pool IPv4 with NAT But we can use IPv4 and NAT!!! Yeah, right … IPv6 Why IPv6? Move to IPv6 Now! New Business Operaonal OpportuniHes Needs Allows continuous growth Simplify service of Internet business providers operations Ready for Cloud and M2M IPv4 Address (moving towards 50 billion) Depletion Increasing government New business models regulations requiring IPv6 deployment IPv6 Readiness – No Excuses! › Laptops, pads, mobile phones, dongles, CPEs: Ready! – OS: 90% of all Operating systems are IPv6 capable – Browsers are ready! – Mobile devices: Android, IOS6, LTE devices are ready! – Mobile Apps: More than 85% with IPv6 support – CPEs: More than 45% support IPv6 IPv6 Traffic is Growing – No Excuses! In LACNIC23, May 2015 • Peru 13% • World 6% Source: Google IPv6 StasHcs - 8/16/2015 So ISP what are you doing? • You may have IPv6 in your backbone: – Dual stack backbone, 6PE, 6VPE – Easy stuff! • Loopbacks, IGP (yes, ISIS is great), we love to configure BGP! – If not, what are you waiHng for? • What about your customers? – Mobile broadband: customers change their phone more quickly than their clothes, easy stuff but those GGSN licenses are killing me.
    [Show full text]
  • Ipv6 Multicast Layer 3 Features
    Chapter 13 IPv6 Multicast Support Prerequisites for IPv6 Multicast 13 IPv6 Multicast Support • Prerequisites for IPv6 Multicast, page 13-1 • Restrictions for IPv6 Multicast, page 13-1 • Information About IPv6 Multicast Support, page 13-2 • How to Configure IPv6 Multicast Support, page 13-4 • Verifying the IPv6 Multicast Layer 3 Configuration, page 13-4 Tip For additional information about Cisco Catalyst 6500 Series Switches (including configuration examples and troubleshooting information), see the documents listed on this page: http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html Participate in the Technical Documentation Ideas forum Prerequisites for IPv6 Multicast None. Restrictions for IPv6 Multicast • The PFC and DFCs provide hardware support for the following: – Completely switched IPv6 multicast flows – IPv6 PIM-Sparse Mode (PIM-SM) (S,G) and (*,G) forwarding – Multicast RPF check for IPv6 PIM-SM (S,G) traffic using the NetFlow table – Rate limiting of IPv6 PIM-SM (S,G) traffic that fails the multicast RPF check – Static IPv6 multicast routes – SSM Mapping for IPv6 (PIM-SSM) – IPv6 multicast forwarding information base (MFIB) using the NetFlow table – IPv6 distributed MFIB (dMFIB) using the NetFlow table – Link-local and link-global IPv6 multicast scopes – Egress multicast replication with the ipv6 mfib hardware-switching command – Ingress interface statistics for multicast routes (egress interface statistics not available) – RPR and RPR+ redundancy mode (see Chapter 9, “Route Processor Redundancy
    [Show full text]
  • Área De Ingeniería Telemática Dpto. Automática Y Computación Soluciones
    Transición a IPv6 Área de Ingeniería Telemática Dpto. Automática y Computación http://www.tlm.unavarra.es/ Soluciones ‣ Doble pila ‣ Dispositivos con IPv4 e IPv6 ‣ Túneles ‣ Comunicar IPv6 a través de zonas IPv4 ‣ Traducción ‣ Comunicar hosts IPv6 con IPv4 IPv6 Dual stack Área de Ingeniería Telemática Dpto. Automática y Computación http://www.tlm.unavarra.es/ Dual stack (Doble pila) ‣ Hosts con pila IPv4 e IPv6 ‣ Las aplicaciones deciden: PF/AF_INET o PF/AF_INET6 ‣ Si manejan direcciones pueden elegir ‣ Si manejan nombres según que devuelva el DNS ‣ RFC para elegir según reglas Dual stack ‣ Primero IPv6 ‣ Primero IPv4? ‣ Elegir según reglas? IPv6 Túneles Área de Ingeniería Telemática Dpto. Automática y Computación http://www.tlm.unavarra.es/ Tunel manual ‣ Cualquier protocolo de VPN/tunnel que soporte IPv6 sobre paquetes IPv4 ‣ Tuneles IPv6 sobre IPv4 (RFC 4213) proto=41 ‣ GRE (RFC 2473) ‣ OpenVPN, socat o similares ‣ … ‣ Túneles estáticos (entre IPs conocidas) ‣ Túneles dinámicos? ‣ De un cliente en cualquier IP a un proveedor? ‣ road-warriors, clientes residenciales con IP dinámica… Tuneles semi-automáticos/dinámicos ‣ Un lado se mantiene conectado a un proveedor ‣ AICCU (Automatic IPv6 Connectivity Client Utility) ‣ Tuneles ‣ 6in4 IPv6 sobre IPv4 ‣ 6in4 con heartbeat (el proveedor deshabilita el túnel si no le llegan heartbeats) ‣ AYIYA (anything in anything) para IPv6 sobre UDP para poder saltar NATs ‣ Tunnel brokers Tunnel broker Túneles automáticos ‣ Configurar tuneles automaticamente para que hosts en islas IPv6 se puedan comunicar
    [Show full text]
  • Ipv6-Only Deployment in Broadband and Cellular Networks Ipv4 As-A-Service
    IPv6-only Deployment in Broadband and Cellular Networks IPv4 as-a-Service LACNIC31 May, 2019 Punta Cana, DO @JordiPalet ([email protected]) - 1 Transition / Co-Existence Techniques • IPv6 has been designed for easing the transition and coexistence with IPv4 • Several strategies have been designed and implemented for coexisting with IPv4 hosts, grouped in three categories: – Dual stack: Simultaneous support for both IPv4 and IPv6 stacks – Tunnels: IPv6 packets encapsulated in IPv4 ones • This has been the commonest choice • Today expect IPv4 packets in IPv6 ones! – Translation: Communication of IPv4-only and IPv6- only. Initially discouraged and only “last resort” (imperfect). Today no other choice! • Expect to use them in combination! - 2 Dual-Stack Approach • When adding IPv6 to a system, do not delete IPv4 – This multi-protocol approach is familiar and well-understood (e.g., for AppleTalk, IPX, etc.) – In the majority of the cases, IPv6 is be bundled with all the OS release, not an extra-cost add-on • Applications (or libraries) choose IP version to use – when initiating, based on DNS response: • if (dest has AAAA record) use IPv6, else use IPv4 – when responding, based on version of initiating packet • This allows indefinite co-existence of IPv4 and IPv6, and gradual app-by-app upgrades to IPv6 usage • A6 record is experimental - 3 Dual-Stack Approach IPv6 IPv6 IPv4 IPv4 Application Application Application Application TCP/UDP TCP/UDP TCP/UDP IPv6 IPv6 IPv4 IPv4 IPv6-only stack Dual-stack (IPv4 & IPv6) IPv4-only stack IPv6
    [Show full text]
  • Ipv6, a Passport to the Future Internet
    AFNIC’s Issue Papers IPv6, A Passport For The Future Internet 1 - Background 2 - Specification for the new version of IP (v6) Executive 3 - What’s new with IPv6? summary 4 - What "exhaustion of IPv4 space" After a historical review situating the means, and what lies behind it? exhaustion of the IPv4 address space, this paper underlines the real issues involved 5 - The integration of IPv6: how, who in this phenomenon and in the inevitable and where? transition from IPv4 to IPv6. It then briefly highlights the contributions of IPv6, recalls 6 - IPv6 integration: communication the roles of the various Internet stakeholders models, classification and describes the communication models for which IPv6 integration should be prioritized. 7 - A few examples of transition A set of illustrative but non-limitative mechanisms examples of transition mechanisms are given in order to show IPv6 integration in practice 8 - A few practical recommendations within various technical contexts. Finally, this for IPv6 integration paper makes operational recommendations to support the deployment of IPv6 and 9 - Seize the IPv6 opportunity – now! launches an appeal for stakeholders to seize – immediately – the opportunities provided 10 - Useful references by IPv6, in order to make the "The Future Internet" an open field for innovation. 1/10 IPv6, A Passport For The Future Internet Copyright AFNIC 2011 Reproduction of the texts authorized subject to acknowledgement of source: www.afnic.fr 1 Background The Internet was invented in the early 1970s in exceptional allocation of "Class B"1, address blocks, the United States and grew quite slowly until the the reuse of Class C blocks2, then the abolition of late 1980s.
    [Show full text]