The document provides guidelines for developing an IPv6 addressing plan and discusses common mistakes to avoid. It recommends using /64 subnets instead of longer prefixes, as anything other than /64 will cause issues. It also recommends pre-allocating address space based on network topology rather than host counts, and assuming the initial plan will need revisions rather than trying to get it perfect the first time. The document provides an example addressing scheme and additional resources for IPv6 address planning.
The document discusses IPv6 addressing plans and fundamentals. It covers how IPv6 addresses are distributed from IANA to RIRs to ISPs and end users. Key topics include assigning /64 subnets, minimum allocation sizes, IPv6 subnetting, different address notation formats, benefits of creating an addressing plan, and considerations for addressing plans for ISPs and point-to-point links. An exercise demonstrates drafting an addressing plan for a sample network topology.
IPv4 and IPv6 - addressing Internet infrastructureRIPE NCC
This document discusses IPv4 and IPv6 addressing and the Internet infrastructure. It provides an overview of RIPE and the RIPE NCC, which develops addressing policies and distributes IP addresses in Europe and the Middle East. The document outlines topics like IPv4 exhaustion, policies for obtaining the last chunks of IPv4 addresses, getting IPv6 addresses, and transitioning from IPv4 to IPv6. It includes statistics on the depletion of the IPv4 address pool and levels of IPv6 adoption. Challenges to IPv6 deployment are discussed along with World IPv6 Day and implications for Internet governance.
This manual will show you how to prepare an effective IPv6 addressing plan. In making that plan, you will need to make a number of important choices. Please think carefully about these choices to ensure that the addressing plan will meet the requirements of your organisation. The manual will provide suggestions to help you to make the right choices.
The document discusses IPv6 address planning and subnetting. It explains that creating an IPv6 address plan helps with routing, security policies, network management and troubleshooting. Unlike IPv4, the focus for IPv6 subnetting is on network planning and optimization rather than conserving addresses. The document provides examples of how to plan and assign subnets using different factors like location, business units, applications and regions. It also discusses calculating the number of required subnets and choosing a subnet prefix length.
instructor ppt_chapter8.2.2 - i_pv6 addressing with exercises of IPv6cyberjoex
The document discusses IPv6 addressing and the transition from IPv4 to IPv6. It covers the need for IPv6 due to the depletion of IPv4 addresses, the structure of IPv6 addresses which use 128-bit addressing and are written in hexadecimal, and methods for compressing IPv6 addresses. IPv6 addresses can be represented in different compressed formats by omitting leading zeros in each section or replacing consecutive sections of zeros with a double colon. The document also discusses types of IPv6 addresses and techniques for IPv4 and IPv6 coexistence like dual stack, tunneling, and translation.
The document is a presentation on migrating to IPv6 given by Shumon Huque at the USENIX LISA conference on November 4th, 2013. It discusses IPv6 addressing and protocol details, including the larger 128-bit address space of IPv6 compared to 32-bit IPv4 addresses. It also covers topics like IPv6 network prefixes, special use IPv4 addresses, IPv6 in URLs, and IPv6 DNS records. The presentation aims to provide an introduction to IPv6 and guidance on migrating networks to support both IPv4 and IPv6.
As IPv6 address migration is catching up in all enterprise networks, we'll take a look at some of the operational best practices to migrate to and subnet IPv6 addresses.
IPv6 Deployment Planning Tutorial, by Philip Smith [APNIC 38]APNIC
This document provides an overview of the key considerations for planning an IPv6 deployment. It discusses performing an audit of existing network hardware and software to determine IPv6 compatibility. The goals of deployment and options for network architectures are outlined. The presentation also covers procuring IPv6 address space, creating an addressing plan, optimizing the existing IPv4 network, and approaches for deploying IPv6 connectivity to customers.
The document discusses IPv6 addressing plans and fundamentals. It covers how IPv6 addresses are distributed from IANA to RIRs to ISPs and end users. Key topics include assigning /64 subnets, minimum allocation sizes, IPv6 subnetting, different address notation formats, benefits of creating an addressing plan, and considerations for addressing plans for ISPs and point-to-point links. An exercise demonstrates drafting an addressing plan for a sample network topology.
IPv4 and IPv6 - addressing Internet infrastructureRIPE NCC
This document discusses IPv4 and IPv6 addressing and the Internet infrastructure. It provides an overview of RIPE and the RIPE NCC, which develops addressing policies and distributes IP addresses in Europe and the Middle East. The document outlines topics like IPv4 exhaustion, policies for obtaining the last chunks of IPv4 addresses, getting IPv6 addresses, and transitioning from IPv4 to IPv6. It includes statistics on the depletion of the IPv4 address pool and levels of IPv6 adoption. Challenges to IPv6 deployment are discussed along with World IPv6 Day and implications for Internet governance.
This manual will show you how to prepare an effective IPv6 addressing plan. In making that plan, you will need to make a number of important choices. Please think carefully about these choices to ensure that the addressing plan will meet the requirements of your organisation. The manual will provide suggestions to help you to make the right choices.
The document discusses IPv6 address planning and subnetting. It explains that creating an IPv6 address plan helps with routing, security policies, network management and troubleshooting. Unlike IPv4, the focus for IPv6 subnetting is on network planning and optimization rather than conserving addresses. The document provides examples of how to plan and assign subnets using different factors like location, business units, applications and regions. It also discusses calculating the number of required subnets and choosing a subnet prefix length.
instructor ppt_chapter8.2.2 - i_pv6 addressing with exercises of IPv6cyberjoex
The document discusses IPv6 addressing and the transition from IPv4 to IPv6. It covers the need for IPv6 due to the depletion of IPv4 addresses, the structure of IPv6 addresses which use 128-bit addressing and are written in hexadecimal, and methods for compressing IPv6 addresses. IPv6 addresses can be represented in different compressed formats by omitting leading zeros in each section or replacing consecutive sections of zeros with a double colon. The document also discusses types of IPv6 addresses and techniques for IPv4 and IPv6 coexistence like dual stack, tunneling, and translation.
The document is a presentation on migrating to IPv6 given by Shumon Huque at the USENIX LISA conference on November 4th, 2013. It discusses IPv6 addressing and protocol details, including the larger 128-bit address space of IPv6 compared to 32-bit IPv4 addresses. It also covers topics like IPv6 network prefixes, special use IPv4 addresses, IPv6 in URLs, and IPv6 DNS records. The presentation aims to provide an introduction to IPv6 and guidance on migrating networks to support both IPv4 and IPv6.
As IPv6 address migration is catching up in all enterprise networks, we'll take a look at some of the operational best practices to migrate to and subnet IPv6 addresses.
IPv6 Deployment Planning Tutorial, by Philip Smith [APNIC 38]APNIC
This document provides an overview of the key considerations for planning an IPv6 deployment. It discusses performing an audit of existing network hardware and software to determine IPv6 compatibility. The goals of deployment and options for network architectures are outlined. The presentation also covers procuring IPv6 address space, creating an addressing plan, optimizing the existing IPv4 network, and approaches for deploying IPv6 connectivity to customers.
This chapter discusses IPv6 addressing and subnetting. It covers how IPv4 addresses are organized into classes and reserved as public or private, while IPv6 does not use classes but IANA still reserves ranges for specific purposes. The chapter has two major sections on global unicast addresses as public IPv6, and unique local addresses as private IPv6. It aims to identify appropriate IPv6 schemes and describe addresses and troubleshooting for exam topics on IP addressing and configurations.
Module 4: Configuring and Troubleshooting IPv6 TCP/IP
This module introduces you to IPv6, a technology that will help ensure that the Internet can support a growing user base and the increasingly large number of IP-enabled devices. The current Internet Protocol Version 4 (IPv4) has served as the underlying Internet protocol for almost thirty years. Its robustness, scalability, and limited feature set is now challenged by the growing need for new IP addresses, due in large part to the rapid growth of new network-aware devices.
Lessons
Overview of IPv6
IPv6 Addressing
Coexistence with IPv6
IPv6 Transition Technologies
Transitioning from IPv4 to IPv6
Lab : Configuring an ISATAP Router
Configuring a New IPv6 Network and Client
Configuring an ISATAP Router to Enable Communication Between an IPv4 Network and an IPv6 Network
Lab : Converting the Network to Native IPv6
Transitioning to a Native IPv6 Network
After completing this module, students will be able to:
Describe the features and benefits of IPv6.
Implement IPv6 addressing.
Implement an IPv6 coexistence strategy.
Describe and select a suitable IPv6 transition solution.
Transition from IPv4 to IPv6.
Troubleshoot an IPv6-based network.
This document outlines an IPv6 lab and techtorial that covers IPv6 addressing, neighbor discovery, static routing, OSPFv3, BGP, and tunneling. The agenda includes lectures on these topics as well as corresponding labs to provide hands-on experience. Prerequisites for the session are basic network engineering knowledge and interest in Cisco technologies. The document then goes on to describe IPv6 addressing formats, types of addresses, and how addresses are allocated to interfaces.
1. The document provides guidance on strategically planning and designing an IPv6 address plan for a large multi-national enterprise called ACME.
2. It outlines the requirements including supporting up to 37 countries and 40 campus locations within the largest country. The plan should be highly hierarchical, uniform and scalable.
3. Byte boundaries are recommended between hierarchy levels to support many countries, with nibble boundaries between buildings within campuses given fewer buildings. The plan should include infrastructure addressing.
IPv6 Autoconfig full process from initial configuration of IPV6 Node. Refreshment of IPv6 Addresses using RA or DHCPv6. How to keep your home config everywhere you go and only logout when you want to, not when you move to a new access point.
The document provides an overview of IPv6 including:
- Limitations of IPv4 that IPv6 addresses such as limited address space and lack of security.
- Key features of IPv6 like a larger 128-bit address space, simpler header format, and built-in security.
- Protocols that support IPv6 functionality like Neighbor Discovery Protocol, Path MTU Discovery, and stateless and stateful address autoconfiguration.
This document summarizes a training presentation on IPv6 theory. It includes sections on IPv4 address exhaustion, OSI layer review, Ethernet and TCP/IP segment formats, common protocols like HTTP and UDP, IPv4 and IPv6 header formats, IPv6 extension headers, IPv6 addressing including examples and shorthand, subnetting and netmasks, address types and scopes, multicast addressing, neighbor discovery, router advertisements, stateless address autoconfiguration, IPv6 support in Cisco IOS, and an example IPv6 network map and configuration.
The document describes an IPv6 lab and techtorial. The agenda includes lectures on IPv6 addressing, neighbor discovery, configuration, routing protocols and deployment techniques. The labs cover these same topics as well as static routing, OSPFv3, BGP and tunneling. Prerequisites include basic networking knowledge and interest in Cisco technologies.
1. The host will automatically generate a link-local address starting with fe80::.
2. It will perform duplicate address detection to ensure the address is unique on the local link.
3. If the address is unique, it is assigned to the interface.
4. The host will send a router solicitation to discover network prefixes advertised by routers.
5. Upon receiving a router advertisement with network prefixes, the host will autoconfigure an IPv6 address by combining the prefix with its interface ID.
The document discusses the impending exhaustion of IPv4 addresses and the need to transition to IPv6. It provides background on IPv6 including that it provides 128-bit addresses to solve exhaustion, utilizes extensions to DHCPv6 for home network prefix assignment, and can be implemented via dual stack, tunneling, or translation methods. Charts show the decreasing pool of available IPv4 addresses and acceleration in depletion rates. The document argues for early adoption of IPv6 to avoid risks from delayed transition and outlines a 3-tier strategy using technologies like dual stack, 6rd, NAT64, and Dual-Stack Lite.
How to set up an IPv6 LAN with Linux. Using IPv6 requires two steps, firstly setting up the local LAN to support IPv6 and secondly connecting to the internet. The exact mechanism to connect to the Internet depends on your ISP. If you have an IPv4 address of IPv6 and whether you trying to access an IPv4 or IPv6 host.
Jumping Bean offers IPv6 training for businesses (http://www.jumpingbean.co.za/ipv6-training)
This document provides an overview of IPv6 including addressing, routing, autoconfiguration, transition technologies, and Linux implementation. Key points covered include IPv6 address formats and types, stateless and stateful autoconfiguration using ICMPv6 and DHCPv6, static and adaptive routing protocols like RIPng and OSPFv3, DNS record formats, and dual stack and tunneling transition technologies. It also reviews how to configure an IPv6 router using the radvd daemon on Linux systems.
This document summarizes a large European service provider's plans for deploying IPv6 across its various networks, including residential, L3 MPLS VPN, and public networks. It discusses challenges around operating multivendor networks with interdependent services. The service provider is taking a dual-stack approach, initially exposing only external-facing services to IPv6. Configuration details are provided for residential broadband network elements like Juniper E320/ERX routers, covering topics like interfaces, routing, subscriber addressing, DNS servers, accounting, and LNS configuration. The goal is a transparent rollout that maintains existing IPv4 customer experiences while introducing IPv6 connectivity.
interoperatbility between IPv4 and IPv6Nitin Gehlot
This document discusses interoperability between IPv4 and IPv6. It outlines challenges with the transition from IPv4 to IPv6 including ensuring minimal downtime and maintaining network reachability and security. It proposes using tunneling techniques like Generic Routing Encapsulation (GRE) to transport IPv6 packets over an IPv4 infrastructure and allow dual stack implementations. The project aims to address scalability between IPv4 and IPv6 using the OSPF routing protocol and virtualizing physical links with Cisco IOS to enable IPv6 multicast routing.
The document discusses IPv6 adoption on the InteropNET network, including transition strategies used like dual stacking, autoconfiguration so clients can obtain IPv6 addresses, DNS services load balanced across both IPv4 and IPv6, and wireless access points supporting both protocols, with the goal of making internal services fully available over both IPv4 and IPv6. Challenges included ensuring services published AAAA records and coordinated with vendors to support IPv6, and some monitoring of IPv6 attack traffic was also performed.
This document provides an introduction to IPv6, including an overview of its key features and differences from IPv4. It discusses how IPv6 was developed to address the exhaustion of IPv4 address space and larger routing tables. The core features covered are the new IPv6 header format, its large 128-bit address space, stateless and stateful address configuration, built-in security via IPsec, and improved support for areas like quality of service and network interactions through protocols like Neighbor Discovery.
The document discusses IPv6 and the transition from IPv4 to IPv6. It provides details about:
- The author who manages the IIT Kanpur campus network and internet services.
- Reasons for adopting IPv6 like shortage of IPv4 addresses and new features in IPv6.
- Elements of IPv6 including the 128-bit address format, address types and scopes, stateless and stateful address autoconfiguration, routing, and neighbor discovery.
- Transition mechanisms from IPv4 to IPv6 like dual stack, tunnels, and translation.
- Current status of IPv6 deployment and recommended steps for migration including checking IPv6 compliance and planning IPv6 addressing.
Deploying IPv6 in Cisco's Labs by Robert Beckett at gogoNET LIVE! 3 IPv6 Conf...gogo6
gogo6 IPv6 Video Series. Event, presentation and speaker details below:
EVENT
gogoNET LIVE! 3: Enterprise wide Migration. http://gogonetlive.com
November 12 – 14, 2012 at San Jose State University, California
Agenda: http://gogonetlive.com/4105/gogonetlive3-agenda.asp
PRESENTATION
Deploying IPv6 in Cisco's Labs
Presentation video: http://www.gogo6.com/video/deploying-ipv6-in-cisco-s-labs-by-robert-beckett-at-gogonet-live
Interview video: http://www.gogo6.com/video/interview-with-robert-beckett-at-gogonet-live-3-ipv6-conference
SPEAKER
Robert Beckett - Services Technical Leader, Cisco Systems
Bio/Profile: http://www.gogo6.com/profile/RobertBeckett
MORE
Learn more about IPv6 on the gogoNET social network
http://www.gogo6.com
Get free IPv6 connectivity with Freenet6
http://www.gogo6.com/Freenet6
Subscribe to the gogo6 IPv6 Channel on YouTube
http://www.youtube.com/subscription_center?add_user=gogo6videos
Follow gogo6 on Twitter
http://twitter.com/gogo6inc
Like gogo6 on Facebook
http://www.facebook.com/pages/IPv6-products-community-and-services-gogo6/161626696777
- The document provides guidance on assigning IPv6 addresses from a /32 allocation to a small colocation and broadband provider network with 3 POPs.
- It recommends assigning a /48 prefix per POP, using 4-bit boundaries for assignments (e.g. /56, /60), and considering ease of aggregation and most important devices/connections.
- An addressing plan is outlined assigning infrastructure addresses and customer prefixes from the provider's 2001:DB8::/32 allocation.
Networking - TCP/IP stack introduction and IPv6Rodolfo Kohn
The document discusses IPv6 and Mobile IPv6 fundamentals, new services, and applications. It begins with an introduction to TCP/IP and the Internet and then covers the OSI and TCP/IP reference models. It describes the physical, data link, network, transport, and application layers. It focuses on IPv6 features like addressing, autoconfiguration, and mobility support through Mobile IPv6. It also discusses new applications and challenges with the transition from IPv4 to IPv6.
This chapter discusses IPv6 addressing and subnetting. It covers how IPv4 addresses are organized into classes and reserved as public or private, while IPv6 does not use classes but IANA still reserves ranges for specific purposes. The chapter has two major sections on global unicast addresses as public IPv6, and unique local addresses as private IPv6. It aims to identify appropriate IPv6 schemes and describe addresses and troubleshooting for exam topics on IP addressing and configurations.
Module 4: Configuring and Troubleshooting IPv6 TCP/IP
This module introduces you to IPv6, a technology that will help ensure that the Internet can support a growing user base and the increasingly large number of IP-enabled devices. The current Internet Protocol Version 4 (IPv4) has served as the underlying Internet protocol for almost thirty years. Its robustness, scalability, and limited feature set is now challenged by the growing need for new IP addresses, due in large part to the rapid growth of new network-aware devices.
Lessons
Overview of IPv6
IPv6 Addressing
Coexistence with IPv6
IPv6 Transition Technologies
Transitioning from IPv4 to IPv6
Lab : Configuring an ISATAP Router
Configuring a New IPv6 Network and Client
Configuring an ISATAP Router to Enable Communication Between an IPv4 Network and an IPv6 Network
Lab : Converting the Network to Native IPv6
Transitioning to a Native IPv6 Network
After completing this module, students will be able to:
Describe the features and benefits of IPv6.
Implement IPv6 addressing.
Implement an IPv6 coexistence strategy.
Describe and select a suitable IPv6 transition solution.
Transition from IPv4 to IPv6.
Troubleshoot an IPv6-based network.
This document outlines an IPv6 lab and techtorial that covers IPv6 addressing, neighbor discovery, static routing, OSPFv3, BGP, and tunneling. The agenda includes lectures on these topics as well as corresponding labs to provide hands-on experience. Prerequisites for the session are basic network engineering knowledge and interest in Cisco technologies. The document then goes on to describe IPv6 addressing formats, types of addresses, and how addresses are allocated to interfaces.
1. The document provides guidance on strategically planning and designing an IPv6 address plan for a large multi-national enterprise called ACME.
2. It outlines the requirements including supporting up to 37 countries and 40 campus locations within the largest country. The plan should be highly hierarchical, uniform and scalable.
3. Byte boundaries are recommended between hierarchy levels to support many countries, with nibble boundaries between buildings within campuses given fewer buildings. The plan should include infrastructure addressing.
IPv6 Autoconfig full process from initial configuration of IPV6 Node. Refreshment of IPv6 Addresses using RA or DHCPv6. How to keep your home config everywhere you go and only logout when you want to, not when you move to a new access point.
The document provides an overview of IPv6 including:
- Limitations of IPv4 that IPv6 addresses such as limited address space and lack of security.
- Key features of IPv6 like a larger 128-bit address space, simpler header format, and built-in security.
- Protocols that support IPv6 functionality like Neighbor Discovery Protocol, Path MTU Discovery, and stateless and stateful address autoconfiguration.
This document summarizes a training presentation on IPv6 theory. It includes sections on IPv4 address exhaustion, OSI layer review, Ethernet and TCP/IP segment formats, common protocols like HTTP and UDP, IPv4 and IPv6 header formats, IPv6 extension headers, IPv6 addressing including examples and shorthand, subnetting and netmasks, address types and scopes, multicast addressing, neighbor discovery, router advertisements, stateless address autoconfiguration, IPv6 support in Cisco IOS, and an example IPv6 network map and configuration.
The document describes an IPv6 lab and techtorial. The agenda includes lectures on IPv6 addressing, neighbor discovery, configuration, routing protocols and deployment techniques. The labs cover these same topics as well as static routing, OSPFv3, BGP and tunneling. Prerequisites include basic networking knowledge and interest in Cisco technologies.
1. The host will automatically generate a link-local address starting with fe80::.
2. It will perform duplicate address detection to ensure the address is unique on the local link.
3. If the address is unique, it is assigned to the interface.
4. The host will send a router solicitation to discover network prefixes advertised by routers.
5. Upon receiving a router advertisement with network prefixes, the host will autoconfigure an IPv6 address by combining the prefix with its interface ID.
The document discusses the impending exhaustion of IPv4 addresses and the need to transition to IPv6. It provides background on IPv6 including that it provides 128-bit addresses to solve exhaustion, utilizes extensions to DHCPv6 for home network prefix assignment, and can be implemented via dual stack, tunneling, or translation methods. Charts show the decreasing pool of available IPv4 addresses and acceleration in depletion rates. The document argues for early adoption of IPv6 to avoid risks from delayed transition and outlines a 3-tier strategy using technologies like dual stack, 6rd, NAT64, and Dual-Stack Lite.
How to set up an IPv6 LAN with Linux. Using IPv6 requires two steps, firstly setting up the local LAN to support IPv6 and secondly connecting to the internet. The exact mechanism to connect to the Internet depends on your ISP. If you have an IPv4 address of IPv6 and whether you trying to access an IPv4 or IPv6 host.
Jumping Bean offers IPv6 training for businesses (http://www.jumpingbean.co.za/ipv6-training)
This document provides an overview of IPv6 including addressing, routing, autoconfiguration, transition technologies, and Linux implementation. Key points covered include IPv6 address formats and types, stateless and stateful autoconfiguration using ICMPv6 and DHCPv6, static and adaptive routing protocols like RIPng and OSPFv3, DNS record formats, and dual stack and tunneling transition technologies. It also reviews how to configure an IPv6 router using the radvd daemon on Linux systems.
This document summarizes a large European service provider's plans for deploying IPv6 across its various networks, including residential, L3 MPLS VPN, and public networks. It discusses challenges around operating multivendor networks with interdependent services. The service provider is taking a dual-stack approach, initially exposing only external-facing services to IPv6. Configuration details are provided for residential broadband network elements like Juniper E320/ERX routers, covering topics like interfaces, routing, subscriber addressing, DNS servers, accounting, and LNS configuration. The goal is a transparent rollout that maintains existing IPv4 customer experiences while introducing IPv6 connectivity.
interoperatbility between IPv4 and IPv6Nitin Gehlot
This document discusses interoperability between IPv4 and IPv6. It outlines challenges with the transition from IPv4 to IPv6 including ensuring minimal downtime and maintaining network reachability and security. It proposes using tunneling techniques like Generic Routing Encapsulation (GRE) to transport IPv6 packets over an IPv4 infrastructure and allow dual stack implementations. The project aims to address scalability between IPv4 and IPv6 using the OSPF routing protocol and virtualizing physical links with Cisco IOS to enable IPv6 multicast routing.
The document discusses IPv6 adoption on the InteropNET network, including transition strategies used like dual stacking, autoconfiguration so clients can obtain IPv6 addresses, DNS services load balanced across both IPv4 and IPv6, and wireless access points supporting both protocols, with the goal of making internal services fully available over both IPv4 and IPv6. Challenges included ensuring services published AAAA records and coordinated with vendors to support IPv6, and some monitoring of IPv6 attack traffic was also performed.
This document provides an introduction to IPv6, including an overview of its key features and differences from IPv4. It discusses how IPv6 was developed to address the exhaustion of IPv4 address space and larger routing tables. The core features covered are the new IPv6 header format, its large 128-bit address space, stateless and stateful address configuration, built-in security via IPsec, and improved support for areas like quality of service and network interactions through protocols like Neighbor Discovery.
The document discusses IPv6 and the transition from IPv4 to IPv6. It provides details about:
- The author who manages the IIT Kanpur campus network and internet services.
- Reasons for adopting IPv6 like shortage of IPv4 addresses and new features in IPv6.
- Elements of IPv6 including the 128-bit address format, address types and scopes, stateless and stateful address autoconfiguration, routing, and neighbor discovery.
- Transition mechanisms from IPv4 to IPv6 like dual stack, tunnels, and translation.
- Current status of IPv6 deployment and recommended steps for migration including checking IPv6 compliance and planning IPv6 addressing.
Deploying IPv6 in Cisco's Labs by Robert Beckett at gogoNET LIVE! 3 IPv6 Conf...gogo6
gogo6 IPv6 Video Series. Event, presentation and speaker details below:
EVENT
gogoNET LIVE! 3: Enterprise wide Migration. http://gogonetlive.com
November 12 – 14, 2012 at San Jose State University, California
Agenda: http://gogonetlive.com/4105/gogonetlive3-agenda.asp
PRESENTATION
Deploying IPv6 in Cisco's Labs
Presentation video: http://www.gogo6.com/video/deploying-ipv6-in-cisco-s-labs-by-robert-beckett-at-gogonet-live
Interview video: http://www.gogo6.com/video/interview-with-robert-beckett-at-gogonet-live-3-ipv6-conference
SPEAKER
Robert Beckett - Services Technical Leader, Cisco Systems
Bio/Profile: http://www.gogo6.com/profile/RobertBeckett
MORE
Learn more about IPv6 on the gogoNET social network
http://www.gogo6.com
Get free IPv6 connectivity with Freenet6
http://www.gogo6.com/Freenet6
Subscribe to the gogo6 IPv6 Channel on YouTube
http://www.youtube.com/subscription_center?add_user=gogo6videos
Follow gogo6 on Twitter
http://twitter.com/gogo6inc
Like gogo6 on Facebook
http://www.facebook.com/pages/IPv6-products-community-and-services-gogo6/161626696777
- The document provides guidance on assigning IPv6 addresses from a /32 allocation to a small colocation and broadband provider network with 3 POPs.
- It recommends assigning a /48 prefix per POP, using 4-bit boundaries for assignments (e.g. /56, /60), and considering ease of aggregation and most important devices/connections.
- An addressing plan is outlined assigning infrastructure addresses and customer prefixes from the provider's 2001:DB8::/32 allocation.
Networking - TCP/IP stack introduction and IPv6Rodolfo Kohn
The document discusses IPv6 and Mobile IPv6 fundamentals, new services, and applications. It begins with an introduction to TCP/IP and the Internet and then covers the OSI and TCP/IP reference models. It describes the physical, data link, network, transport, and application layers. It focuses on IPv6 features like addressing, autoconfiguration, and mobility support through Mobile IPv6. It also discusses new applications and challenges with the transition from IPv4 to IPv6.
The document outlines an IPv6 addressing plan for a multi-site service provider network. It allocates address blocks and subnets for infrastructure, customer connections, and internal networks at three point of presence sites. Address space is also assigned to different customer types.
- IPv6 is needed to address the impending exhaustion of IPv4 address space. It features a 128-bit address compared to 32-bit in IPv4, vastly expanding the available addresses.
- Security issues in transitioning from IPv4 to IPv6 include weaknesses in enumeration, scanning and managing the large IPv6 address space. Firewalls and other perimeter defenses must also protect both IPv4 and IPv6 networks to prevent bypass.
- Attacks can exploit protocols like neighbor discovery in IPv6, as well as vulnerabilities in applications that operate over both IPv4 and IPv6. Proper implementation and maintenance of defenses is needed to secure the transition.
(1) The document discusses IPv6 and Mobile IPv6 (MIPv6), focusing on fundamentals, new services, and applications enabled by mobility. (2) It describes key concepts in MIPv6 like mobile nodes, home agents, care-of addresses, and route optimization. (3) MIPv6 provides a network layer solution for mobility and transparency to applications, allowing IPv6 devices to connect and roam across different networks.
This document provides an overview and introduction to the book "Understanding IPv6". It discusses the history and need for a new internet protocol to replace IPv4 due to address depletion. IPv6 was developed in the late 1990s to address this need. The document outlines the chapters covered in the book, including IPv6 fundamentals, addressing, headers, neighbor discovery, and services. It also discusses some IPv6 certification programs.
The document discusses IPv6 addressing fundamentals and policies. It covers how to obtain IPv6 address space from RIPE, including the minimum allocation sizes and requirements. Guidelines are provided for creating IPv6 addressing plans, including recommending customers receive a /48 block and examples of addressing plans for networks and end users. Transition mechanisms between IPv4 and IPv6 are also briefly mentioned.
IPv6 for CMU discusses IPv6 addressing, header basics, autoconfiguration, and transition from IPv4. It covers why IPv6 is needed due to limited IPv4 addresses, IPv6 address formats and types, stateless and stateful configuration, neighbor discovery, and integration with IPv4 using mapped and compatible addresses.
The document summarizes a training session on IPv6 addressing hosted by Ferenc Csorba of RIPE NCC. RIPE NCC is a not-for-profit organization located in Amsterdam that distributes internet number resources like IP addresses and AS numbers. The training covered IPv6 addressing plans and subnetting. Some key points discussed included the philosophy change from IPv4 to IPv6 where the default subnet size is /64 to allow for more efficient autoconfiguration, and how to determine how many subnets and addresses to allocate to customers based on their needs.
This document provides an overview of IPv6 addressing and address types. It discusses the 128-bit IPv6 address space and address notation. The main types of IPv6 addresses covered are unicast addresses, including global unicast, link-local, and unique local addresses, as well as multicast addresses and their uses for neighbor discovery. Solicited-node addresses are described as a method for IPv6 nodes to resolve link-layer addresses without broadcasting.
IPv6 is the next generation Internet protocol that replaces IPv4. It features a vastly larger 128-bit address space to avoid future address exhaustion. IPv6 addresses are written as eight groups of four hexadecimal digits separated by colons and supports stateless autoconfiguration of hosts and other improvements over IPv4.
The document discusses various types of faults in distributed systems including transient, intermittent, and permanent faults. It describes approaches to achieving fault tolerance through redundancy of information, time, and physical components. The document also discusses active replication using triple modular redundancy and the primary backup approach. It introduces the two army problem and Byzantine Generals problem regarding reaching agreement in faulty systems and solutions requiring multiple participants and message rounds.
This document provides an agenda and overview for an IPv6 networking training session. The summary includes:
1) The training will cover IPv6 addressing, neighbor discovery, tools and resources, network layers, and hands-on labs.
2) Prerequisites include a willingness to learn, understanding of networks, and bringing a laptop for the hands-on portion using CORE virtual machines.
3) The hands-on portion will use CORE virtual machines and allow participants to set up an IPv6 lab environment.
The document discusses IPv4 and IPv6 addressing. It notes that IPv4 provides 4.3 billion addresses while IPv6 provides 3.4 undecillion addresses. It then outlines some limitations of IPv4 including limited addresses and lack of built-in security. Improvements in IPv6 are discussed such as built-in security, more efficient routing, and vastly increased address space. Examples of IPv4 and IPv6 addresses are provided. The document also discusses IPv6 addressing formats, types of IPv6 addresses including unicast, anycast and multicast, and IPv6 transition technologies.
IPv6 is the most recent version of the Internet Protocol (IP), and was developed by IETF to overcome the inevitable exhaustion of IPv4 addresses. In order to simplify the transition towards IPv6, the protocol iterated very little on how IPv4 operates other than offering more address space. This inadvertently produced the exact opposite of the intended effect: with no compelling new features for anyone outside of network engineering, IPv6 deployment has been hampered for decades, as developers find increasingly creative ways of efficiently using IPv4 address space rather than bearing the cost of transition.
In this talk, Fastly Network Engineer João Taveira discusses these protocol design failures and instead explain how Fastly re-architected its infrastructure around IPv6. By addressing IPv6 in a clean-slate manner, Fastly avoided perpetuating many of the mistakes of IPv4, and the resulting network architecture has the potential to significantly affect the performance, resilience, and economics of content delivery.
This document provides an overview of IPv6 addressing and connectivity. It describes the various types of IPv6 addresses including global aggregateable unicast addresses, site-local addresses, unique local addresses, and link-local addresses. It also covers IPv6 address formats and special addresses like the unspecified, loopback, multicast, and solicited node multicast addresses. Transition mechanisms from IPv4 to IPv6 are also briefly mentioned.
This document provides an overview of IPv6 fundamentals, including:
- Key differences between IPv4 and IPv6 such as larger addressing space and elimination of NAT.
- Details of the IPv6 header format and use of extension headers for additional functions.
- The IPv6 addressing architecture including the various address types and formats.
- Protocols for autoconfiguration, neighbor discovery, and multicast in IPv6 networks.
Fault tolerance is important for distributed systems to continue functioning in the event of partial failures. There are several phases to achieving fault tolerance: fault detection, diagnosis, evidence generation, assessment, and recovery. Common techniques include replication, where multiple copies of data are stored at different sites to increase availability if one site fails, and check pointing, where a system's state is periodically saved to stable storage so the system can be restored to a previous consistent state if a failure occurs. Both techniques have limitations around managing consistency with replication and overhead from checkpointing communications and storage requirements.
This document provides an overview of IPv6 address planning, including how IPv6 addresses are constructed, how to determine how many addresses are needed, where to obtain address space, and why creating an IPv6 address plan is important. It discusses infrastructure addressing plans, customer addressing plans, and provides examples of addressing plans for backbone point-to-point links and customer links. The document also lists some addressing planning tools and IPv6 subnet calculators that can assist with creating deployable IPv6 address plans.
12 steps for IPv6 Deployment in Governments and EnterprisesAPNIC
Training is the first step, as IPv6 requires redesigning networks and is not like IPv4. A transition plan requires in-depth IPv6 knowledge of the current network and future evolution. It affects client devices, applications, and how small entities will deploy IPv6. The document outlines 12 steps for transitioning to a dual-stack network with the long-term goal of IPv6-only, including getting training, creating a deployment strategy, controlling DNS, considering BGP, developing an addressing plan, obtaining internet resources, using an IPAM tool, assigning and auditing addresses, verifying IPv6 support, testing applications, and checking contracts with third parties.
This document discusses various techniques for IPv6 transition and coexistence with IPv4, including:
- Dual-stack which allows simultaneous support of both IPv4 and IPv6.
- Tunnels which encapsulate IPv6 packets in IPv4 packets to provide IPv6 connectivity through IPv4 networks.
- Translation techniques like NAT64 which allow communication between IPv4-only and IPv6-only nodes.
On demand expansion of IPv6 address allocation size in legacy IPv6 space by T...APNIC
The document proposes allowing organizations in legacy IPv6 blocks to request expanding their existing /32 allocations up to a /29 without meeting normal utilization requirements. This would utilize address blocks reserved in the past that may go unused. Some argue this could lead to inefficient use of space, but larger allocations increase maintenance costs discouraging unnecessary requests. It was discussed on a mailing list with mixed opinions on supporting nibble boundary allocation versus subsequent allocation methods.
IETF IPv6 Activities Report by Cathy Aronson at ARIN 36. Presentation and webcast archive available at: https://www.arin.net/participate/meetings/reports/ARIN_36/ppm.html
The document outlines an agenda for a 3HOWs event discussing IPv6 and MPLS technology. The morning sessions will cover how to deal with IPv6, including why it is important now due to limited IPv4 addresses, IPv6 addressing details, and how to connect to IPv6. The afternoon will discuss how to connect with MPLS technology, the benefits it provides for interconnecting offices, and actual customer case studies. Questions from attendees will conclude the event.
This document provides guidance on rapidly deploying IPv6 for ISP networks. It begins by outlining common concerns with IPv6 implementation and then provides steps to take including: starting implementation in a lab; enabling IPv6 on core infrastructure; enabling customer services in stages from easiest to hardest; and conducting a network readiness assessment. The document then provides examples of enabling IPv6 on routers and end customer connections using a simplified IPv6 addressing scheme. It discusses additional considerations like security, Linux and Windows test beds, non-networking devices, sources of help, and convincing management of the need for IPv6 deployment.
The document discusses various techniques for transitioning from IPv4 to IPv6, including dual stack, tunnels, and translation. Dual stack allows simultaneous support of both IPv4 and IPv6 by keeping both protocol stacks. Tunnels encapsulate IPv6 packets in IPv4 packets to carry IPv6 traffic over IPv4 networks. Translation techniques like NAT64 algorithmically translate IPv4 and IPv6 addresses to allow communication between IPv4-only and IPv6-only nodes. Newer methods like 464XLAT and DS-Lite aim to address IPv4 exhaustion by sharing public IPv4 addresses among more clients.
The document discusses IPv4 addressing and subnetting. It describes how IPv4 addresses are structured, including the network and host parts. It also covers subnet masks and prefix lengths. The document discusses IPv4 address types like unicast, broadcast, and multicast. It explains public and private IP addresses and how NAT is used for routing between private and public networks. The document also covers network segmentation and how subnetting can be used to partition large networks into smaller broadcast domains.
Ipv6 neighbor discovery problems and mitigationsKarunakant Rai
IPv6 neighbor discovery implementations are vulnerable to denial of service attacks due to the large subnet sizes of IPv6 (/64). Scanning or resolving many unassigned addresses can overwhelm router resources. The RFC 6583 describes these problems and potential mitigations. Operational mitigations include filtering unused address space, using smaller subnets like /120, and routing techniques to limit routes advertised. Router configuration changes can also help avoid losing track of existing neighbors during attacks. However, none of these are general solutions and /64 subnets are still needed in many cases.
Americas Headquarters IPv6 Addressing White Paper IPv6 IntroductionScott Faria
This document provides an overview of IPv6 addressing and describes how to build an IPv6 addressing plan. It discusses address representation in IPv6, address types including unicast, anycast and multicast. It covers IPv6 address scopes, and describes how to assign interface identifiers. The document aims to refresh the reader on basic IPv6 addressing concepts and serve as an introduction to developing an IPv6 addressing plan.
IPv6 was developed to address the limitations of IPv4, such as its limited 32-bit address space that is nearly exhausted. IPv6 features a 128-bit address space providing vastly more addresses. It allows for automatic configuration of addresses, simpler header format, and built-in security features. IPv6 addresses are represented through eight groups of four hexadecimal digits separated by colons. The address space is hierarchically allocated into global unicast, unique local, link-local, multicast, and unspecified addresses.
CompTIA exam study guide presentations by instructor Brian Ferrill, PACE-IT (Progressive, Accelerated Certifications for Employment in Information Technology)
"Funded by the Department of Labor, Employment and Training Administration, Grant #TC-23745-12-60-A-53"
Learn more about the PACE-IT Online program: www.edcc.edu/pace-it
This document provides an overview of IPv6 and its implementation status at UNC. Some key points:
- IPv4 addresses are exhausted, while IPv6 provides vast addressing space to support future growth. However, IPv6 deployment is still low, around 6% of networks.
- IPv6 offers features like stateless address autoconfiguration, no ARP, and multicast addressing instead of broadcasts.
- At UNC, IPv6 is enabled on limited campus VLANs and servers. Implementation focuses on dual-stack while addressing security, monitoring, and other issues. Slow expansion is recommended over the near term.
This chapter discusses IPv6, including what it is, why it is needed, IPv6 addressing, address types, special addresses, autoconfiguration, configuring IPv6, and tunneling. IPv6 was created to replace IPv4 and address the problem of looming address exhaustion. It uses 128-bit addresses instead of 32-bit in IPv4. The document outlines various IPv6 address types including unicast, multicast, and anycast. It also describes special IPv6 addresses like the link-local and unique local address ranges. Autoconfiguration and configuring IPv6 on routers and interfaces is also covered.
Roadmap to Next Generation IP Networks: A Review of the FundamentalsNetwork Utility Force
This document discusses the requirement for all IP-capable nodes to support IPv6 given the depletion of IPv4 address space. It advises that IPv6 support is no longer optional, and cautions that references to "IP" may refer to IPv4, IPv6, or both depending on context. The document then provides an overview of IPv6 fundamentals including addressing, interconnectivity, security, staff training, and transition approaches. It emphasizes that IPv6 works in practice and addresses challenges but nothing that can't be overcome.
Fernando Gont - The Hack Summit 2021 - State of the Art in IPv6 SecurityEdgeUno
The IPv6 protocol suite was designed to accommodate the present and future growth of the Internet, by providing a much larger address space than that of its IPv4 counterpart, and is expected to be the successor of the original IPv4 protocol suite. It has already been deployed by most major content providers (including Google and Facebook) and many Internet Service Providers (ISPs). While the ultimate goal of IPv6 is virtually the same as that of IPv4 (moving packets across the Internet), the underlying mechanisms and technical details are significantly different, typically resulting in unexpected security and privacy implications. In this presentation, Fernando will cover the state of the art in everything ranging from IPv6 pentesting, to security controls and operational mitigations for IPv6 attacks, thus providing valuable information to red, blue, and purple teams.
The document discusses IPv4 and IPv6 addressing. It notes that IPv4 address space is limited and running out, leading to problems like NAT. IPv6 was created to address this by providing a much larger 128-bit address space. The document covers different types of IPv6 addresses like unicast, multicast, anycast, and how interface identifiers are used. It also discusses obtaining address space and recommended practices for IPv6 allocation and representation.
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...Dr. Vinod Kumar Kanvaria
Exploiting Artificial Intelligence for Empowering Researchers and Faculty,
International FDP on Fundamentals of Research in Social Sciences
at Integral University, Lucknow, 06.06.2024
By Dr. Vinod Kumar Kanvaria
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
The simplified electron and muon model, Oscillating Spacetime: The Foundation...RitikBhardwaj56
Discover the Simplified Electron and Muon Model: A New Wave-Based Approach to Understanding Particles delves into a groundbreaking theory that presents electrons and muons as rotating soliton waves within oscillating spacetime. Geared towards students, researchers, and science buffs, this book breaks down complex ideas into simple explanations. It covers topics such as electron waves, temporal dynamics, and the implications of this model on particle physics. With clear illustrations and easy-to-follow explanations, readers will gain a new outlook on the universe's fundamental nature.
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
1. Developing an IPv6 Addressing Plan
Guidelines, Rules, Best Practice
Ron Broersma
DREN Chief Engineer
SPAWAR Network Security Manager
ron@spawar.navy.mil
2. Introduction
• IPv6 deployment includes:
– obtaining a block of IPv6 addresses (a “prefix”) for your
organization and its networks.
– establishing a plan for how those addresses will be assigned
to your networks and subnets.
• Observation: Many plans have serious flaws
– usually takes about 3 times to get it right
– many plans include the same basic mistakes
• Goal of this presentation:
– not intended to be a comprehensive tutorial
– review the common mistakes, and the reasons behind them
– save everyone time and effort, by avoiding those mistakes
• less re-numbering
– take full advantage of the vast address space now available
to us
16-Nov-2011 2
3. The piece that has changed
16-Nov-2011 3
ISO 7 Layer Model
Application
Presentation
Session
Transport
Network
Link
Physical
Sockets
TCP, UDP
IP
Mac Layer
Internet Stack
IPv6
4. Address Structure
• Unicast addresses are structured as a
subnetwork prefix and an interface identifier.
16-Nov-2011 4
Subnet prefix
Interface ID
(host part)
Allocated through a
hierarchy of registries,
service providers, and sites
(global unicast)
Automatically assigned
using stateless
autoconfiguration, or
statically, or with DHCPv6
Size of a given (sub)network is effectively not limited by the
number of unique host values as was the case in IPv4
where a /24 (Class C) net can only have 254 hosts.
/64 /128
6. Example Allocation
• Your enterprise is allocated a Global Unicast
Prefix*
• How do you assign xxxx and yyyy throughout
your enterprise?
16-Nov-2011 6
2001 0DB8 xxxx yyyy Interface ID
/32 /48 /64
2001:DB8::/32
* ”The default provider allocation via the RIRs is currently a /32.” (RFC 5375)
7. Big mistake #1
• Using other than /64 for subnets
• Some choose /120
• Reasoning:
– “host” part is same size as in IPv4 (8 bits)
– /64 is wasteful
– the security guy wants to be able to enumerate all
hosts by scanning the subnet, just like in IPv4
16-Nov-2011 7
2001 0DB8 xxxx yyyy
/120
8. IPv4 practice gets in the way
• Being conservative with addresses
– operating on the notion that addresses are very
scarce
• Making the subnet mask long, to avoid waste.
Examples:
– /30 for point-to-point links
– if you only have 10 hosts on a subnet, then allocate
a /28
– squeezing as many subnets as possible out of a /24
16-Nov-2011 8
9. Making the paradigm shift
• You may be un-qualified to develop a final
IPv6 addressing plan if you think:
– /64 for subnets is wasteful
– /64 for point-to-point links is wasteful
– /48 for small sites is wasteful
16-Nov-2011 9
10. Subnets are /64
• If you choose other than /64, the following
things will not work:
– Neighbor Discovery
– Secure Neighbor Discovery
– Stateless Address Autoconfiguration (SLAAC)
– Microsoft DHCPv6
– Multicast with Embedded-RP
– Mobile-IPv6
– and many other things in the future
• Using other than /64 for subnets goes against:
– RFC 4291 “IPv6 Addressing Architecture”
– RFC 5375 “IPv6 Addressing Considerations”
16-Nov-2011 10
11. Subnets are /64
16-Nov-2011 11
“For all unicast addresses, except those that start with the binary value 000,
Interface IDs are required to be 64 bits long.” (RFC 4291)
“Using /64 subnets is strongly recommended, also for links connecting
only routers. A deployment compliant with the current IPv6 specifications
cannot use other prefix lengths.” (RFC 5375)
12. What about point-to-point
links?
• Even if we finally agree that subnets are /64, some will argue
that point-to-point links must be /126 (like an IPv4 /30) or /127.
– Can’t waste a whole /64 when you need only 2 addresses
• Best practice is to allocate /64 for point-to-point links
– whether you need 2 out of 2**64 or 200 out of 2**64, there’s not
much difference in “waste”
• But what about that DoS problem from the ping-pong effect?
– This will not happen on a RFC 4443 compliant IPv6 implementation
– If you have a non-compliant device (Juniper), you can set the
interface mask to /126 on the interface as a temporary workaround
until your device is fixed, but you should still allocate a /64 for the
link.
– Never use /127 (See RFC 3627), but also look at RFC 6164.
16-Nov-2011 12
13. Mistake #2
• Thinking you have to get the addressing plan
right the first time
– Unless you have operational experience with IPv6
deployments and transition, you WILL get it
wrong.
– Usually takes about 3 times to get it right.
• Thinking you can’t afford to re-address
– Since the first plan is probably a throw-away, you
will have to re-address when you come up with a
revised plan.
16-Nov-2011 13
14. Iterative planning approach
• Assume the first plan is a throwaway
– Don’t put too much energy into it, because it is only temporary
• Do some initial limited IPv6 deployments based on the
initial addressing plan
– testbeds
– public facing services
• Gain operational experience
– realize ways to improve the addressing plan
– interact with the community to get ideas
• Develop your next addressing plan
– put more energy into this one
– readdress the existing IPv6 infrastructure
• Do a wider deployment with the new plan
– internal servers, maybe clients.
• Iterate
16-Nov-2011 14
15. Mistake #3
• Trying to be too creative about how much
address space to allocate to a “site”
– Thinking you need to allocate large amounts of
space to large sites, and much smaller amounts to
small sites
• Assuming that large allocations to small sites
is wasteful
– Go back and review the slide on being stuck in the
IPv4 conservation paradigm.
16-Nov-2011 15
16. “Sites” get a /48
• Here, the “site” field is 0x0000-0xFFFF
– That gives you 65,536 sites!
– That’s not enough?
• And each site get 65,536 subnets
– That’s not enough? Its like a “Class A” block of
huge subnets.
• Standardize!
– It simplifies things administratively and
operationally.
16-Nov-2011 16
2001 0DB8 “site” yyyy Interface ID
/32 /48 /64
17. Mistake #4
• Justify “upwards”, rather than pre-allocate
“downwards”.
– Requiring sites to develop documentation and
justification for their address space requirements
– Allocating to those groups or sites based on that
justification
16-Nov-2011 17
18. Pre-allocation
• You can easily pre-allocate to the site level
– see slide on “sites get a /48”
• Within sites, addressing can align with
existing subnet structure
– later, you may want to re-address your IPv4
networks (but don’t worry about that just yet).
16-Nov-2011 18
19. Mistake #5
• Host-centric allocation rather than subnet-
centric
– Thinking that address allocation has anything to
do with the number of hosts
16-Nov-2011 19
20. Focus on subnets
• A /64 subnet has enough room for this many
hosts:
• You don’t have to think about whether a
subnet is large enough for all your hosts.
• You don’t have to worry about “growing” a
subnet later if you get more hosts.
• Just focus on your network topology (links,
subnets, VLANs, etc.) and align with that.
16-Nov-2011 20
18,446,744,073,709,551,616
21. Once again
16-Nov-2011 21
When doing an address plan, a major driver in IPv4
was efficiency and conservation
In IPv6, efficiency and conservation is NOT a major
driver, but instead it is all about better alignment
with network topology, accommodation of security
architecture, and operational simplicity through
standardization
22. Other Considerations
• In IPv6, every interface has multiple
addresses
– In IPv4, we thought of a “host” as having a single
IP address
• Embedding IPv4 addresses in IPv6 addresses
adds administrative burden and limits
flexibility
– limited long term benefit, so don’t do it
– It is reasonable to copy just the “host” part of the
IPv4 address into the IID (host part) of the IPv6
address
16-Nov-2011 22
23. Other Considerations
• There is an opportunity to align the
addressing plan with security topology, to
simplify ACLs
– This is the type of thing you may start to
incorporate into your 3rd version of your plan.
• Internal aggregation is not nearly as critical
as aggregating route announcements to your
ISP
– you can afford to carry a few thousand routes
internally, but the Internet can’t afford to carry all
your /48’s or longer.
16-Nov-2011 23
24. Other Considerations
• Most of the context here has been for large
enterprises that aggregate into a very few
connections to one or two ISPs, and use
“provider-independent” (PI) space.
• If you have a lot of small outlier sites that are
single-homed directly to an ISP, have them
get their address space from that ISP, known
as “provider-aggregatable” (PA) space.
16-Nov-2011 24
25. Adding structure or
hierarchy
• Examples:
– grouping of sites by
• region
• service delivery point
– grouping of subnets within a site to align
with
• IPv4 mapping
• routing topology
• security topology
16-Nov-2011 25
26. Adding structure or
hierarchy
• Recommendation: add grouping or hierarchy
on nibble (4 bit) boundaries
– Aligns better with hex digits
– Aligns better with grouping in DNS PTR records
• Examples:
– /36 for regions
• 16 regions with 4096 sites per region
– /44 for service delivery points
• 16 customers per SDP, up to 4096 SDPs
– /52 to align with IPv4 allocations
• can map up to 16 allocations
16-Nov-2011 26
27. Subnet numbering example
• You could just assign them incrementally
– 0, 1, 2, 3, etc
• You could have them match some part of your existing
IPv4 subnet numbers
– Like the 3rd octet of your subnets addresses, if you have a “Class
B” and all your subnets are /24’s
• You may want to create some hierarchy, if you have
separate enclaves or security zones or want to map to
multiple existing IPv4 allocations.
2001 0DB8 1234 subnet Interface ID
/32 /48 /64
0000 to FFFF
28. Hierarchy Example
• Save the top 4 bits of the subnet number for mapping to IPv4
allocation (or other grouping)
– That’s a /52
• Subnet numbers are then 000 to FFF
– 4096 subnets per /52 (you only need 256, but 3 hex digits allows
you to keep decimal notation)
2001 0DB8 1234 subnet Interface ID
/32 /48 /64
0000 to FFFF
29. Example Addressing Scheme
• Address the network for consistency between protocols
– Align VLAN number with 3rd octet of IPv4 address
– Align IPv6 “subnet number” with the above
16-Nov-2011 29
2001 0DB8 1234 subnet Interface ID
128 123 subnet host
IPv6
IPv4
VLAN-id
30. IPv6 Addressing Example
Subnet IPv4 IPv6
Offices 128.123.1.0/24 2001:480:1234:1::/64
Computer Room 128.123.2.0/24 2001:480:1234:2::/64
DMZ (BR) 128.123.100.0/24 2001:480:1234:1100::/64
DMZ (FW) 128.123.101.0/24 2001:480:1234:1101::/64
fw-to-br 128.123.254.0/30 2001:480:1234:1000::/64
fw-to-ir 128.123.254.4/30 2001:480:1234:0000::/64
Notes:
- Used subnet 000 for “infrastructure” links
- /52 used to designate security zone (0 – trust, 1 – untrust)
- IPv4 and IPv6 subnet numbers try to align, where possible (when IPv4 subnets are /24)
- didn’t use /126’s nor /127’s for the point-to-point links
31. Privacy Addresses (RFC 4941)
• Incompatible with many Enterprise environments
– Need address stability for many reasons
• Logging, Forensics, DNS stability, ACLs, etc.
• Enabled by default in Windows
– Breaks plug-n-play because we have to visit every Windows
machine to disable this feature.
• Just added in Mac OS X “Lion”.
• Ubuntu thinking about making it default.
[Privacy addresses] are horrible and I hope nobody really uses them, but they're better than NAT.
… Owen DeLong, Hurricane Electric
16-Nov-2011 31
32. Living with Privacy addresses
• Where your clients support DHCPv6, use that to
assign addresses
– No DHCPv6 client support in Windows XP, Mac OSX before 10.7
(Lion), etc.
• If all your Windows systems are in Active Directory,
use GPO to disable privacy addresses
• Options for other systems:
– configure system to disable privacy addresses
• registry setting in Windows (see below)
– configure addresses statically on the hosts
– keep a historical record of all MAC address to IPv6 address
mappings for every host, for correlation in IDS and forensics tools
16-Nov-2011 32
netsh interface ipv6 set privacy state=disabled store=persistent
netsh interface ipv6 set global randomizeidentifiers=disabled store=persistent
33. Additional Guides
• Preparing an IPv6 Addressing Plan
• IPv6 Address Design, a few practical
principles
16-Nov-2011 33
http://www.ripe.net/lir-services/training/material/IPv6-for-LIRs-Training-Course/IPv6_addr_plan4.pdf
http://www.txv6tf.org/wp-content/uploads/2011/09/Doyle-TXv6TF_09142011.pdf
36. What’s missing:
IPv6 Operational Experience
• Lots of planning is underway
– transition planning
– address planning
• Much of this planning is done by individuals who
have never touched an IPv6 packet
• Too much energy is being wasted on plans that are
flawed, because they are not based on operational
experience
• It is more important to turn on IPv6 now and start
moving some IPv6 traffic, than it is to have a
complete plan
16-Nov-2011 36
37. Getting IPv6 experience
• Run IPv6 at home
– Get a tunnel from Hurricane Electric
• Get the IPv6 Certification from HE
• Managers:
– make sure your network engineers are doing the
above, or something similar
• Run IPv6 in a testbed environment
• IPv6-enable just your public-facing services to
start with
• Then you can start comprehensive planning
16-Nov-2011 37
38. Go native
• “native IPv6” means “don’t use tunnels”.
– some confuse this term to mean IPv6-only, but
that is not the case.
• Access to Legacy IPv4 networks and systems
will be necessary for years to come.
– we need both IPv4 and IPv6 at the same time.
– IPv4 and IPv6 are not directly interoperable
• Use “dual stack” as the IPv6 transition
mechanism
– can use translators in the interim, but NOT long
term. goal is end-to-end native IPv6.
16-Nov-2011 38
39. About translators
• Common scenario:
– Don’t IPv6-enable your actual public web site, but
instead front-end it with an IPv6-to-IPv4 translator
• This is OK as an interim step, because of the
extreme importance of IPv6-enabling the
public Internet
• But the target is end-to-end native IPv6, so
consider any such translators to be very
temporary
– unless that translation device is already in the
path for reasons unrelated to IPv6 transition
16-Nov-2011 39
41. IPv6 traffic percentage
• From a server perspective, what percentage of the
Internet will try to reach you over IPv6 today?
– 0.4%
• From a client perspective, what percentage of
Internet traffic is IPv6, where everything at your site
is IPv6-enabled:
16-Nov-2011 41
42. Another event like
World IPv6 Day?
• June 2012
• You should plan to
IPv6-enable your
public facing
services before then
16-Nov-2011 42