DOCSLIB.ORG

Best Practices for Deploying Ipv6 Over Broadband Access

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Best Practices for Deploying Ipv6 Over Broadband Access WHITE PAPER Best Practices for Deploying IPv6 over Broadband Access www.ixiacom.com 915-0123-01 Rev. D, January 2016 2 Table of Contents Introduction ................................................................................................. 4 IPv6 Solutions for Broadband Access......................................................... 4 Translation ................................................................................................... 5 Tunneling ..................................................................................................... 5 Dual-Stack Lite (DS-Lite) ............................................................................ 5 IPv6 Rapid Deployment (6rd) ...................................................................... 6 Dual-Stack ................................................................................................... 8 How Dual-Stack PPP works ....................................................................... 8 Test Requirements ....................................................................................... 9 Testing Tunneling ......................................................................................... 9 Testing Dual-Stack PPP ............................................................................. 11 Conclusion ..................................................................................................12 3 Introduction Service Providers: The IPv6 Bell Tolls for Thee! After more than a decade of forewarning, the IPv4 to IPv6 transition has finally reached critical mass. On February 1, 2011, the Internet Assigned Numbers Authority (IANA) allocated the last freely-available block of IPv4 addresses. At the same time, the number of users and “endpoints” requiring Internet access, and thus a unique IP address, continues to explode. With broadband deployments achieving global exponential growth, next-generation wireless rollouts on the horizon, and smart-phone use escalating, it is expected that there will be an increase of 5 billion unique endpoints between 2010 and 2015. Service providers are challenged to prepare their networks for the influx of IPv6 addresses. As exemplified by Google’s support of IPv6 on its search, news, docs, maps, and YouTube, the Internet is already rich with IPv6 content and services; but IPv4 won’t just vanish as IPv6 comes on board. This creates a challenging situation for service providers, who must upgrade their network infrastructures to handle IPv4 and IPv6 co-existence. While network cores are well-equipped to handle both IPv4 and IPv6, broadband access After more than networks are not. IPv4 and IPv6 co-existence stresses the underlying network systems, a decade of which can introduce latency, degrade network responsiveness, and compromise service- level agreements (SLAs). The biggest transition concern is its impact on customers – will forewarning, introducing IPv6 endpoints, forwarding tables, and services affect connectivity speed, the IPv4 to IPv6 service quality, and network reliability? transition has finally With fierce industry competitiveness over customer retention, service providers need reached critical assurance of a seamless IPv6 transition – at least from the customer perspective. To proactively address customer-impacting problems, service providers need a quick and mass. On February reliable test solution that enables them to predict the effect of the IPv6 transition on their 1, 2011, the Internet broadband access network. Assigned Numbers IPv6 Solutions for Broadband Access Authority (IANA) allocated the last An abrupt transition of the legacy IPv4 infrastructure to IPv6 is not practical because most Internet services are still based on IPv4 and many customers still run operating freely-available systems that do not fully support IPv6. Service providers must support both IPv4 and IPv6 block of IPv4 endpoints and services to guarantee the quality of service (QoS) defined in their SLAs. addresses. There are different methods used to achieve this goal across broadband access networks including: • Translation • Tunneling (includes dual-stack lite and IPv6 rapid deployment) • Dual-stack 4 Translation The easiest way to conserve the depleting IPv4 address space is to use translation so that the outward-facing interface uses a public interface while the private network uses IP addresses that are not routed on the Internet. However, the known performance and scalability issues compel most service providers to deploy either tunneling or dual-stack transition mechanisms in broadband access networks. Tunneling Tunneling mechanisms are used to tunnel IPv6 island traffic over IPv4 networks and vice versa. The two tunneling schemes currently receiving significant industry attention are: • Dual-stack Lite • IPv6 rapid deployment Dual-Stack Lite (DS-Lite) While service While service providers aim to capitalize on the benefits of quickly embracing IPv6, they providers aim to must also contain the costs of doing so and ensure uninterrupted IPv4 support. With DS-Lite, broadband service providers handle IPv4 addresses using IP in IP (IPv4-in- capitalize on the IPv6) tunneling and Network Address Translation (NAT). DS-Lite simplifies the IPv4/IPv6 benefits of quickly transition by de-coupling IPv6 deployment in the service provider network from the rest of the Internet. embracing IPv6, they must also How DS-Lite works contain the costs of DS-Lite uses IPv6-only links between the provider and the customer. The DS-Lite home doing so and ensure gateway is provisioned with an IPv6 address on its WAN interface. At the LAN-side interface, it operates its own DHCPv4 server, handing out RFC1918 private addresses to uninterrupted IPv4 home devices. There is no NAT service on the customer premise equipment (CPE) device, support. such as a home gateway. The NAT service is located on a carrier-grade NAT device in the provider’s network, which is also a tunnel terminator for the Pv4-in-IPv6 tunnel. The IPv4 packet from the home device to an external destination is encapsulated in an IPv6 packet by the DS-Lite home gateway and transported into the provider network. The packet is decapsulated at the carrier-grade NAT device (CGN), also referred to as an Address Family Translation Router (AFTR) and NAT44 is performed to map the home device’s private IPv4 address to a public IPv4 address. The IPv6 tunnel source address is added to the NAT table, along with an IPv4 source address and port, to both disambiguate the customer private address and provide the reference for the tunnel endpoint. If a home device needs to access an IPv6 service, it is transported “as-is” and routed to an Internet server. With DS-Lite technology, the communications between end-nodes stay within their address family without requiring protocol family translation. If a home device needs to access an IPv6 service, it is transported “as-is” and routed to an Internet server. 5 CGN/AFTR: • Builds NAT table (maps IPv4/IPv6) • Terminates IPv4-in-IPv6 tunnel • Encapsulates IPv4 packet in IPv6 tunnel DS-Lite Home Gateway: • Uses IPv6 address WAN interfaces • Operates DHCPv4 server on LAN interfaces • Encapsulates IPv4 packet in IPv6 going to network To quickly offer • Decapsulates IPv6 packet coming from network end-to-end IPv6 service, providers Figure 1: How DS-Lite Works use 6rd to There are multiple advantages of DS-Lite over using NAT cascading: encapsulate IPv6 Tunneling IPv4 over IPv6 is far simpler than translation so it performs much better than traffic in IPv4 NAT464. headers, and tunnel The deployment of IPv6 in the service provider network is decoupled and independent of home users’ IPv6 the customers migrating to IPv6. If customer equipment is IPv6-aware, the packets simply traffic through follow the IPv6 routing to reach the destination, and no tunneling is performed. the IPv4 network Increased traffic load is handled by adding more AFTR elements in the service provider to IPv6 internet network, providing flexibility to adapt to changing traffic load. service. IPv6 Rapid Deployment (6rd) In order to quickly offer end-to-end IPv6 service, providers use 6rd to encapsulate IPv6 traffic in IPv4 headers, and tunnel home users’ IPv6 traffic through the IPv4 network to IPv6 internet service. This tunnel is terminated by an edge router on the service provider network and native IPv6 packets are then transmitted to the IPv6-capable Internet. This allows for rapid introduction of IPv6 services in provider networks as they transition from IPv4 to IPv6. This approach minimizes deployment costs because it only requires upgrades to the routers at the customer edge (CE routers) to support 6rd and additional border routers (BR) that terminate the tunnel. The service provider can operate one or several BRs at its border between its IPv4 infrastructure and the IPv6 Internet depending on the number of IPv6 hosts it has to support and the capacity of a single BR. How 6rd works 6rd relies on IPv4 and is designed to deliver production-quality IPv6 alongside IPv4 with as little change to IPv4 networking and operation as possible.A 6rd domain consists of: 6 • 6rd CE routers, also referred to as Residential Gateways (RGs) or Customer Premises Equipment (CPE). A 6rd CE router functions as a customer edge in a 6rd deployment and is the initiator of the 6rd tunnel • One or more 6rd BRs. A 6rd-enabled router is managed by the service provider at the edge of a 6rd domain. The BR terminates the IPv4 tunnel and transmits native IPv6 into the IPv6 network. 6rd CPE: • Encapsulates
Load more

Recommended publications
  • DSL-Based Access Solutions Thomas Martin Session SPL-211
    SPL_211 © 2001, Cisco Systems, Inc. All rights reserved. 1 Design Principles for DSL-Based Access Solutions Thomas Martin Session SPL-211 SPL_211 © 2001, Cisco Systems, Inc. All rights reserved. 3 Agenda • Digital Subscriber Line Technologies • Subscriber Connection Models • Reaching the Services • Case Studies • Summary, Question and Answer SPL_211 © 2001, Cisco Systems, Inc. All rights reserved. 4 What is Digital Subscriber Line (DSL)? End-User DSL E’net ATM Value-Added Copper Loop Packet Network DSL DSL “Modem” “Modem” • DSL is a pair of “modems” on either end of a copper wire pair • DSL converts ordinary phone lines into high-speed data conduits • Like dial, cable, wireless, and E1, DSL by itself is a transmission technology, not a complete end-to-end solution • End-users don’t buy DSL, they buy services such as high-speed Internet access, intranet, leased-line, voice, VPN, and video on demand SPL_211 © 2001, Cisco Systems, Inc. All rights reserved. 5 DSL Modem Technology DSLDSL ServiceService Max.Max. DataData RateRate AnalogAnalog VoiceVoice Max.Max. ReachReach Down/UplinkDown/Uplink (bps)(bps) SupportSupport (km-feet)(km-feet) Residential VDSL–Very 25M/1.6M25M/1.6M YesYes .9–3,000.9–3,000 High Bit Rate oror 8M/8M8M/8M SOHO ADSL–Asymmetric 8M/1M8M/1M YesYes 5.5–18,0005.5–18,000 G.SHDSL 2.3M/2.3M.2.3M/2.3M. NoNo 8.15–26,0008.15–26,000 Business • Trade-off is reach vs. Bandwidth • Reach numbers imply “clean copper” • Different layer 1 transmission technologies, need a common upper protocol layer to tie them together SPL_211 © 2001, Cisco Systems, Inc.
    [Show full text]
  • VRF-Aware Ipv6 Rapid Deployment Tunnel
    VRF-Aware IPv6 Rapid Deployment Tunnel Virtual Routing and Forwarding - aware tunnels are used to connect customer networks separated by untrusted core networks or core networks with different infrastructures (IPv4 or IPv6). The VRF-Aware IPv6 Rapid Deployment Tunnel feature extends Virtual Routing and Forwarding (VRF) awareness to IPv6 rapid deployment tunnels. • Finding Feature Information, on page 1 • Restrictions for the VRF-Aware IPv6 Rapid Deployment Tunnel, on page 1 • Information About the VRF-Aware IPv6 Rapid Deployment Tunnel, on page 2 • How to Configure the VRF-Aware IPv6 Rapid Deployment Tunnel, on page 2 • Feature Information for the VRF-Aware IPv6 Rapid Deployment Tunnel , on page 10 Finding Feature Information Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required. Restrictions for the VRF-Aware IPv6 Rapid Deployment Tunnel The VRF- Aware IPv6 Rapid Deployment Tunnel feature has the following restrictions: • The incoming physical interface, and the tunnel interface should have the same VRF instance defined. • The tunnel transport VRF and the egress physical interface, through which the traffic leaves should have the same VRF instance defined.
    [Show full text]
  • Qos Support in MPLS Networks
    1 QoS Support in MPLS Networks MPLS/Frame Relay Alliance White Paper May 2003 By: Victoria Fineberg, Consultant [email protected] Abstract MPLS is sometimes used synonymously with QoS, but more accurately, it is a QoS- enabling technology that forces application flows into connection-oriented paths and provides mechanisms for traffic engineering and bandwidth guarantees along these paths. Furthermore, when an MPLS network supports DiffServ, traffic flows can receive class- based admission, differentiated queue servicing in the network nodes, preemption priority, and other network treatment that provide bases for QoS guarantees. The IETF work in this area has been augmented by the MPLS/Frame Relay Alliance Implementation Agreement which extends MPLS to the user-network interface, and thus serves as a foundation for implementing QoS end-to-end. This paper describes various QoS and MPLS mechanisms and analyzes their applicability. 2 Table of Contents 1. Introduction..................................................................................................................3 1.1 QoS Drivers .........................................................................................................3 1.2 Main Definitions ..................................................................................................4 1.3 Necessary Conditions for QoS.............................................................................5 2. Initial QoS and TE Models ..........................................................................................6
    [Show full text]
  • ISP Architecture – MPLS Overview, Design and Implementation for Wisps
    www.iparchitechs.com 1-855-MIKROTI(K) ISP Architecture – MPLS Overview, Design and Implementation for WISPs. KEVIN MYERS, NETWORK ARCHITECT / MANAGING PARTNER MTCINE #1409 MIKROTIK CERTIFIED TRAINER •Kevin Myers, Network Architect • Jackson, Mississippi – United States • 18 + years in IT, Network Architecture and Engineering • Areas of Design Focus: •MikroTik integration with large multi-vendor networks •Design/Implement/Operate BGP/MPLS/OSPF Wireline and WISP service provider networks •Design/Implement/Operate Data Center (Enterprise and Cloud) networks • Certifications • MTCINE #1409 & MikroTik Certified Trainer • MikroTik – MTCWE, MTCUME, MTCRE, MTCTCE, MTCNA • Cisco/Microsoft – CCNP, CCNA, MCP •www.iparchitechs.com •Global Leaders in MikroTik Design and Engineering •#1 ranked MikroTik consulting firm in North America •The most successful MikroTik global integrator – we bill thousands of hours in MikroTik engineering across 6 continents. •The first consulting firm to offer 24/7 MikroTik technical assistance with enterprise level SLAs •Operate at large scale supporting networks with tens of thousands or routers, switches, firewalls, etc •www.iparchitechs.com •Our Services •Global Professional Services – Consulting for Design, Engineering, Integration and Operations •Fully Managed Network Services - per rack unit support for full network management and monitoring •24/7 support contracts per device – support all MikroTik devices with 24/7 TAC support and 4 hour SLAs. • MultiLingual Support in: English, Français, Polski, Español MPLS – What is it? • Theory: Briefly introduce the MPLS protocol and how it works in conjunction with existing L2/L3 networks • Design: Discuss an MPLS architecture and preparing your WISP for implementing MPLS. • Business Justification: Identify the business and financial use case for implementing MPLS in a WISP.
    [Show full text]
  • Ipv6 in Broadband Networks MR-244
    IPv6 in Broadband Networks MR-244 January 2011 Agenda 1. Introduction to the Broadband Forum 2. Business drivers for IPv6 and IPv4 exhaustion 3. Key IPv6 attributes and deployment challenges 4. IPv6 strategies for broadband access to support Internet access and new services 5. Summary 2 IPv6 in Broadband Networks Tutorial Contributors Christophe Alter – France Telecom Salman Asadullah – Cisco David Allan – Ericsson Michel Borgne – France Telecom Dave Christophe – Alcatel-Lucent Guillaume Gottardi – Cisco Michael Hanrahan – Huawei Christian Jacquenet – France Telecom David Kessens – NSN Suresh Krishnan – Ericsson Roberta Maglione – Telecom Italia Drew Rexrode – Verizon 3 We are the Broadband Forum http://www.broadband-forum.org The Broadband Forum is the central organization driving broadband solutions and empowering converged packet networks worldwide to better meet the needs of vendors, service providers and their customers. We develop multi-service broadband packet networking specifications addressing interoperability, architecture and management. Our work enables home, business and converged broadband services, encompassing customer, access and backbone networks. 4 The BroadbandSuite Goals and Focus The BroadbandSuite is broken down into three major domains: BroadbandManagement – Goal – enhance network management capabilities and enable an intelligent, programmable control layer that unifies diverse networks – Focus - empower service providers to deliver and efficiently maintain personalized services that enhance the
    [Show full text]
  • Guidelines for the Secure Deployment of Ipv6
    Special Publication 800-119 Guidelines for the Secure Deployment of IPv6 Recommendations of the National Institute of Standards and Technology Sheila Frankel Richard Graveman John Pearce Mark Rooks NIST Special Publication 800-119 Guidelines for the Secure Deployment of IPv6 Recommendations of the National Institute of Standards and Technology Sheila Frankel Richard Graveman John Pearce Mark Rooks C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 December 2010 U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Dr. Patrick D. Gallagher, Director GUIDELINES FOR THE SECURE DEPLOYMENT OF IPV6 Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-119 Natl. Inst. Stand. Technol. Spec. Publ. 800-119, 188 pages (Dec. 2010) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.
    [Show full text]
  • The Role of Emerging Broadband Technologies on the Converged
    The Role of Emerging Broadband Technologies on the Converged Packet-Based Network Introduction The vision of network convergence toward a consolidated packet-based network has been discussed for years, though it is still not a reality. Currently, there are numerous overlay networks such as IP, ATM, FR, Ethernet, SONET, DWDM and wireless for different services. The evolution pace toward convergence has been slow due to economic, technical and regulatory issues. However, the fact is that data traffic volume is now surpassing voice traffic volume. Traditional TDM voice traffic is moving to IP packets and TDM private line is moving to Ethernet private line. The wave of broadband applications such as Internet access, VOD, and IPTV create high bandwidth requirements for the network. These applications are packet-based, but have a much lower margin of profit for the service providers when compared to traditional voice service. Today’s overlay and traditional circuit-based infrastructure will become less optimal for the new packet-based services as the profit margin decreases. Most of the wireless networks in North America today are still circuit-based because most of the current wireless service is still voice-based. However, with emerging wireless access technologies such as WiMAX and Wi-Fi, more broadband wireless data and video services can be deployed. As a result, the wireless core network evolves toward a packet-based network. Service offerings drive network evolution. As more packet-based broadband services are launched and bundled together in service offerings, service providers start to add more packet-aware features into their current network components.
    [Show full text]
  • About A10 Networks Or About Its Products Or Services, Including but Not Limited to Fitness for a Particular Use and Noninfringement
    THE END OF IPV4? A Service providers guide to Transitioning from IPV4 to IPV6 The IPv6 adoption rate is increasing rapidly. On The End of IPv4? World IPv6 Day and World IPv6 Launch, in June On February 3, 2011, the Internet Assigned 2011 and 2012, the world turned on IPv6 and left Numbers Authority (IANA) allocated the last it on. It was a success according to the event or- five remaining “/8”s of IPv4 address space to ganizers. For example, in 2012, over 60 access the Regional Internet Registries (RIRs); the local providers and more than 3,000 websites public- registries are running low on IPv4 addresses, ly participated in the launch event.Those partic- rapidly. ipants all have committed to keeping IPv6 run- ning as part of normalbusiness operations. The advent of new Internet-connected locations (from hotels to planes and more world-wide) and new Internet-connected devices (notable examples include smartphones, smart meters, Migration Paths to IPv6 gaming devices and other household applianc- IPv6 removes the IP address scarcity by creat- es) has exacerbated the shortage. Each of these ing a new address space with vastly more po- extra devices places greater pressure on the tential addresses. IPv6 also provides many oth- existing IPv4 infrastructure. er benefits to service providers and end-users, such as improved efficiency, security, simplicity and Quality of Service (QoS) versus IPv4. Many vendors of enterprise and consumer elec- tronics are offering support for IPv6 network connectivity, for both IPv6 management and IPv6 traffic handling, support that is on par with IPv4 functionality.
    [Show full text]
  • Service Provider Ipv6 Deployment BRKSPG-3300
    Service Provider IPv6 Deployment BRKSPG-3300 Amarjit Gahir – Solutions Architect BRKSPG-3300 Prerequisites: Session Abstract • This session focuses on SP IPv6 deployment techniques in core networks which will help network designers and administrators understand IPv6 operation and implementation options for native IPv4 and MPLS core environments. This session will also shed light on IPv6 Multihoming, addressing and Cisco Carrier- Grade IPv6 (CGv6) Solution considerations in core networks. • Attendee must have a solid foundation of IPv6 basics (Protocol, Addressing, Routing), MPLS and Multicast. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 2 Agenda • SP IPv6 Integration Strategy • IPv6 in Core Networks and Deployment Models • IPv6 Addressing Considerations • IPv6 Multi-homing Considerations • Carrier-Grade IPv6 Solution – CGv6 • Conclusion Growing Internet Challenge & Evolution Moving from 1 to 2 to 3 to 1 ….. Public Public IPv4 IPv4 Public IPv6 IPv4 Private IPv6 Private IPv4 IPv4 • 2012: Mandates take effect – GlobAlization - WorldIPv6LAunch - Massive Mobile deployment. Transition to IPv6 forces Services & Applications running over IPv6 customers to acquire product or managed services to sustain business and IPv4/IPv6 Coexistence Infrastructure customer reach IPv6 Internet • 2015: IPv6 is mAinstreAm Customers without transition Preserve IPv4 infrastructure experience v4 run out reduced service levels, diminished customer reach 2012 2015 2020+ © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public IPv4 Runout RIR Projected RemAining ExhAustion Addresses in Date RIR Pool (/8s) APNIC 19-Apr-2011 0.6079 (actual) RIPE NCC 14-Sep-2012 0.9394 (actual) LACNIC 10-Jun-2014 0.1067 (actual) ARIN 24 Sep-2015 (actual) AFRINIC 11-Jan-2019 1.6947 5 © 2017 Cisco and/or its affiliates.
    [Show full text]
  • Implementing Trust-To-Trust with Customer Edge Switching
    Implementing Trust-to-Trust with Customer Edge Switching Raimo A. Kantola, Member, IEEE, Department of Communications and Networking Aalto University Helsinki, Finland [email protected] for the duration of a session. Abstract — A Network Address Translator allows hosts in a The UNSAF architecture requires a STUN client in the private address space to communicate with servers in the pub- hosts and STUN servers to be deployed in the global net- lic Internet. There is no accepted solution for an arbitrary host work but it leaves the NATs themselves as they are. UNSAF from the public IP network to initiate communication with a uses IP addresses for identification. It clutters applications host in a private address space although attempts have been made to create one. This paper proposes the replace NATs with code that has nothing to do with the task of the with a more comprehensive concept we call Customer Edge application. It scales poorly particularly for mobile hosts. It Switching (CES). Customer edge switching assumes connection does not help in deploying servers in private address space state on the trust boundary between the user and the core net- and thus hampers the user innovation potential. works. The connection state is managed by implicit signaling. An application on a user device such as a mobile termi- The state gives means for the private network operator to ap- nal that wants to be reachable needs to maintain a NAT ply elaborate access control to packet flows arriving from the Internet to the private network. CES is a way of moving from mapping by a keep-alive mechanism that wakes the device the end-to-end principle to the trust-to-trust principle advo- at regular intervals and keeps the NAT state alive.
    [Show full text]
  • VPLS: the Switched Ethernet
    VPLS: The Switched Ethernet Executive Summary VPLS is becoming a popular networking option. Its inherent Ethernet any-to-any connectivity model makes VPLS a popular choice for enterprises adding or deleting sites. Existing Ethernet users may have a simple implementation by modifying existing Ethernet equipment, which will also scale easily to meet future bandwidth needs. Although it has many advantages, VPLS may not be right for every business. This paper explains VPLS and discusses when it is a good networking solution. VPLS: The Switched Ethernet __________________________________________________________________________________________________________________ 2 VPLS, or Virtual Private LAN Service, is a widely used term in today’s bottom half of the Data Link Layer. The Data Link Layer uses Media networking environment. Often referred to as “the network of the Access Control (MAC) Addresses to identify endpoints and it formats future”, VPLS seems to be evolving into the next “in” technology. When data in frames (see Figure 1). discussing the topic, it is important to understand the user’s definition. Ethernet can use either layer 2 or layer 3 services to create a Virtual Private LAN or Line? networking solution providing high-bandwidth connectivity between Although it is growing in popularity today, in fact, VPLS has been locations within a metropolitan area, between two cities or across a available for some time and care should be taken to understand how WAN. Ethernet can be implemented either as an access method to a the term is defined. Some believe VPLS stands for Virtual Private Line layer 3 technology, or as a point-to-point, point-to-multi-point or any- Service, and may consider it to be any long-haul service.
    [Show full text]
  • Ipv6 TRANSITION TECHNOLOGIES
    IPv6 TRANSITION TECHNOLOGIES Alastair JOHNSON [email protected] April 2011 AGENDA 1. Introduction 2. Native IPv6 dual-stack 3. DS-Lite 4. NAT64 5. 6rd / 4rd 6. 464XLAT 7. IVI 8. Summary 3 COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. INTRODUCTION This presentation covers… • A look at some of the most common (or popular) IPv6 transition technologies and how they can be deployed • What technology is appropriate where, and what support looks like • A brief comparison of the technologies • Mostly focused on ISPs offering residential or consumer Internet services, however many technologies are applicable in other service environments • Mostly focusing on the access, aggregation, and edge components of the network – assumes core and other infrastructure is IPv6 ready 4 COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. INTRODUCTION LARGE SCALE NAT • Large Scale NAT (LSNAT), Carrier Grade NAT (CGNAT), or any other type of service provider IPv4-to-IPv4 based NAT platforms and technologies are not a transition mechanism to IPv6 • These technologies are IPv4 continuity solutions • LSNAT is one of several mechanisms that an operator may use to manage IPv4 exhaustion in their network while deploying IPv6 services • This presentation will not discuss LSNAT beyond this slide 5 COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. INTRODUCTION WHAT ARE TRANSITION TECHNOLOGIES • Transition technologies are mechanisms that allow operators to deploy and migrate their subscriber-base to IPv6 • These transition technologies have
    [Show full text]