This document discusses IPv6 deployment and provides statistics on IPv6 adoption. It summarizes Hurricane Electric's 11 years of experience with IPv6 and their global IPv6 network footprint. Visualization tools are presented for analyzing global and regional IPv6 routing statistics, including a graphical representation of IPv6 routing within India between major autonomous systems. Motivation is provided for networks to implement IPv6 ahead of IPv4 address exhaustion.
Martin J Levy - Hurricane Electric - The IPv6 global view - norway ipv6 - apr...IKT-Norge
The document discusses Hurricane Electric's IPv6 network and services. It notes that Hurricane Electric has over a decade of experience with IPv6 and currently operates one of the largest IPv6 backbones globally. The presentation examines questions around IPv6 deployment worldwide and the readiness of the IPv6 routing table for real-world use. Tools for checking global IPv6 routing and statistics, such as Hurricane Electric's BGP monitoring site, are demonstrated.
This document discusses the history and current state of IPv4 and IPv6 addressing. It notes that IPv4 addresses were initially allocated in 1985 for academic and research networks, but spread widely through the 1990s as internet service providers grew. By 2010, over 90% of IPv4 addresses had been allocated, with less than 3% remaining. IPv6 was standardized in 1998 to address the impending exhaustion of IPv4 addresses. IPv6 provides enough addresses that each person on Earth could have trillions, far more than needed. While IPv6 deployment is still in early stages, regions like Asia and Europe have allocated more addresses. One challenge remaining is greater adoption of IPv6 in domains name system infrastructure.
PERN2 is a high-speed national research and education network for universities and academic institutions in Pakistan. It will provide integrated communication infrastructure using advanced ICT. The network will connect major cities through 10GbE metro networks and provide services like VOIP, online lectures, streaming, VPNs, and high-speed internet. It will also connect to international research networks through a 155Mbps link to the TEIN2 network in Singapore. The PERN2 network uses MPLS and other technologies to establish redundancy and fault tolerance across its IP/MPLS backbone.
Jan Zorz - IPv6 and mobile emergency response teamsIKT-Norge
Jan Žorž presented on his work with IPv6 and emergency response systems. He discussed the GEN6 project which is developing IPv6-enabled self-organizing systems for emergency teams. As part of this, Jan Žorž is leading a Slovenian pilot project that will deploy an IPv6 network for a fire department to demonstrate seamless connectivity, automatic configuration, mobility, and secure transmission of data, voice, and video across different network technologies. Jan Žorž also discussed his role in updating the RIPE-501 IPv6 procurement document and demonstrated the DSMIPv6-TLS technology for secure mobile IPv6 communications.
This document discusses the RIPE NCC's efforts to facilitate IPv6 deployment. It provides an overview of the RIPE NCC, including its role in distributing IP addresses and overseeing the policy development process. It then outlines some of the RIPE NCC's services that support IPv6 adoption such as measurements of IPv6 usage, an IPv6 readiness rating system, and capacity building events. It also discusses how the RIPE NCC engages with governments and other stakeholders to encourage IPv6 deployment.
50 billion connected wireless devices... IPv6, anyone?: Fredrik Garneij, Syst...IPv6no
50 billion connected wireless devices... IPv6, anyone?: Fredrik Garneij, Systems Manager, Ericsson
IKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011
Here are the key steps to include IPv6 on an existing IPv4 MPLS VPN using 6PE and CsC:
1. Upgrade PE routers to support 6PE and CsC. This allows the PEs to tunnel IPv6 packets over the existing IPv4 MPLS infrastructure.
2. Configure loopback addresses for the PE routers and advertise these addresses over MP-iBGP to exchange IPv6 reachability information.
3. Configure IPv6 VPN address families and enable the send-label option to exchange VPNv6 routes and labels over MP-iBGP.
4. Configure IPv6 VPN routes on the PEs and redistribute these routes into the VPNv6 address family to advertise to other PEs.
6. IPv6 Internetzugang für Privatkunden: Die Lösung von Swisscom - Martin GysiDigicomp Academy AG
Um ihren Kunden den Zugang zum IPv6 Internet zu ermöglichen, hat Swisscom den 6rd Mechanismus gewählt. Der Vortrag gibt einen Überblick zur Funktionsweise von 6rd und über den geplanten Dienst.
Martin J Levy - Hurricane Electric - The IPv6 global view - norway ipv6 - apr...IKT-Norge
The document discusses Hurricane Electric's IPv6 network and services. It notes that Hurricane Electric has over a decade of experience with IPv6 and currently operates one of the largest IPv6 backbones globally. The presentation examines questions around IPv6 deployment worldwide and the readiness of the IPv6 routing table for real-world use. Tools for checking global IPv6 routing and statistics, such as Hurricane Electric's BGP monitoring site, are demonstrated.
This document discusses the history and current state of IPv4 and IPv6 addressing. It notes that IPv4 addresses were initially allocated in 1985 for academic and research networks, but spread widely through the 1990s as internet service providers grew. By 2010, over 90% of IPv4 addresses had been allocated, with less than 3% remaining. IPv6 was standardized in 1998 to address the impending exhaustion of IPv4 addresses. IPv6 provides enough addresses that each person on Earth could have trillions, far more than needed. While IPv6 deployment is still in early stages, regions like Asia and Europe have allocated more addresses. One challenge remaining is greater adoption of IPv6 in domains name system infrastructure.
PERN2 is a high-speed national research and education network for universities and academic institutions in Pakistan. It will provide integrated communication infrastructure using advanced ICT. The network will connect major cities through 10GbE metro networks and provide services like VOIP, online lectures, streaming, VPNs, and high-speed internet. It will also connect to international research networks through a 155Mbps link to the TEIN2 network in Singapore. The PERN2 network uses MPLS and other technologies to establish redundancy and fault tolerance across its IP/MPLS backbone.
Jan Zorz - IPv6 and mobile emergency response teamsIKT-Norge
Jan Žorž presented on his work with IPv6 and emergency response systems. He discussed the GEN6 project which is developing IPv6-enabled self-organizing systems for emergency teams. As part of this, Jan Žorž is leading a Slovenian pilot project that will deploy an IPv6 network for a fire department to demonstrate seamless connectivity, automatic configuration, mobility, and secure transmission of data, voice, and video across different network technologies. Jan Žorž also discussed his role in updating the RIPE-501 IPv6 procurement document and demonstrated the DSMIPv6-TLS technology for secure mobile IPv6 communications.
This document discusses the RIPE NCC's efforts to facilitate IPv6 deployment. It provides an overview of the RIPE NCC, including its role in distributing IP addresses and overseeing the policy development process. It then outlines some of the RIPE NCC's services that support IPv6 adoption such as measurements of IPv6 usage, an IPv6 readiness rating system, and capacity building events. It also discusses how the RIPE NCC engages with governments and other stakeholders to encourage IPv6 deployment.
50 billion connected wireless devices... IPv6, anyone?: Fredrik Garneij, Syst...IPv6no
50 billion connected wireless devices... IPv6, anyone?: Fredrik Garneij, Systems Manager, Ericsson
IKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011
Here are the key steps to include IPv6 on an existing IPv4 MPLS VPN using 6PE and CsC:
1. Upgrade PE routers to support 6PE and CsC. This allows the PEs to tunnel IPv6 packets over the existing IPv4 MPLS infrastructure.
2. Configure loopback addresses for the PE routers and advertise these addresses over MP-iBGP to exchange IPv6 reachability information.
3. Configure IPv6 VPN address families and enable the send-label option to exchange VPNv6 routes and labels over MP-iBGP.
4. Configure IPv6 VPN routes on the PEs and redistribute these routes into the VPNv6 address family to advertise to other PEs.
6. IPv6 Internetzugang für Privatkunden: Die Lösung von Swisscom - Martin GysiDigicomp Academy AG
Um ihren Kunden den Zugang zum IPv6 Internet zu ermöglichen, hat Swisscom den 6rd Mechanismus gewählt. Der Vortrag gibt einen Überblick zur Funktionsweise von 6rd und über den geplanten Dienst.
IPv6 Deployment -- Solving a Chicken-and-Egg Problem In Divide-and-Conquer StyleChristian Vogt
The document discusses IPv6 deployment and the challenges of a complex transition from IPv4. It proposes a "divide and conquer" approach with three stages: 1) enabling IPv6 connectivity for users first before upgrading network internals, 2) leveraging content delivery networks to accelerate IPv6 availability of content, and 3) simplifying legacy IPv4 support through IPv4-IPv6 translation in the long term. This staged approach addresses critical business needs and aims to promote IPv6 adoption incrementally despite technical difficulties of a full transition.
PLNOG 4: Klaudiusz Staniek - Efficient Technique for Enforcing Internet Peeri...PROIDEA
This document proposes an efficient technique for enforcing internet peering policies at the data plane level using Cisco router capabilities. It tags peer and customer prefixes uniquely in the BGP and forwarding information base (FIB) tables. It then tags incoming packets based on the longest prefix match and forwards or discards packets according to the tag. This glues the BGP control plane policies to the IP data plane policies to block peer-to-peer transit traffic while allowing customer-to-peer and customer-to-customer traffic. The technique is available on many Cisco routers today and complements other BGP applications.
The document discusses IPv6 over MPLS on Cisco routers, including:
- 6PE allows IPv6 connectivity over an IPv4/MPLS backbone by using MPLS labels between PE routers to tunnel IPv6 packets. Configuration on Cisco routers is straightforward, requiring IPv6 BGP neighbor configuration and the "neighbor send-label" command.
- 6VPE extends the concept of VPNs to IPv6 using scoped addressing architecture. It allows dual-stacked VRFs for consistent IPv4 and IPv6 VPN services. Configuration requires defining VRFs and associating interfaces using "vrf forwarding".
Gabriel Paues - IPv6 address planning + making the case for WHYIKT-Norge
The document discusses planning for IPv6 addressing and deployment, providing tips and examples for allocating IPv6 addresses within a /48 assignment in a hierarchical manner using subnets of /64 to simplify administration and support techniques that rely on a consistent subnet size, as well as enabling IPv6 services gradually on servers without initially exposing them to IPv6 DNS records. It also addresses common objections to IPv6 deployment and provides strategies for getting started with IPv6.
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.
This document provides an overview of mobility management and key concepts in IP mobility. It discusses macro mobility protocols including Mobile IPv6 (MIPv6) and Fast Handovers for MIPv6 (FMIPv6), as well as micro-mobility protocols like Cellular IP, HAWAII, and Hierarchical Mobile IPv6 (HMIPv6). The introduction defines IP mobility and the need for mobility support in IP given that the current IP address model assumes fixed locations. It also describes how Mobile IP allows devices to move between networks while keeping the same IP address.
Overview slide deck on HSPA+, explaining the evolution path, performance enhancements, user experience, network commitments, deployments, launches worldwide,and the growing eco-system of user devices.
This presentation draws upon the Global HSPA+ Network Commitments and Deployments information paper published by GSA on June 9, 2010 and the HSPA Devices Survey published by GSA on April 22, 2010.
This document provides an overview of the Sonaps networked production system, including its file-based workflow, remote connectivity capabilities, and support services. The system allows for planning, acquisition, editing, playout and archiving in a collaborative environment. It has been implemented in over 300 facilities worldwide, supporting news, sports and live production. Remote sites can access centralized content and contribute material efficiently using the system's distributed workflow and network infrastructure. Comprehensive support is also provided through remote monitoring, automatic fault reporting, and rapid on-site response capabilities.
SpringOne 2GX 2011 - Writing applications for Cloud Foundry using Spring and ...trisberg
The document discusses writing applications for Cloud Foundry using Spring and MongoDB. It provides an introduction to Cloud Foundry and MongoDB, describes Spring Data support for MongoDB including using MongoTemplate and Mongo Repository, and discusses why one would run MongoDB in the cloud. Key topics covered include characteristics of PaaS platforms like Cloud Foundry, choices of frameworks, application services, and clouds available in Cloud Foundry, data modeling in MongoDB using documents rather than tables, and querying and indexing MongoDB.
NASA OIG: Status of NASA's Transition to Internet Protocol Version 6 (IPv6)Bill Duncan
Results NASA has taken preliminary steps to meet OMB requirements for IPv6 transition and integration, including assigning a lead official in November 2005 to coordinate NASA's efforts, developing inventories of IP-aware devices and an impact analysis, and in June 2008 demonstrating IPv6 capability of one NASA network
.
However, as of March 2010 the Agency did not have an updated or complete IPv6 transition plan as required by OMB. This occurred, in part, because the Agency has ample IPv4 addresses to meet its current and future requirements and because the individual who was leading the IPv6 transition effort left NASA in November 2006 and no one has been assigned to replace him.
As a result, the Agency does not have adequate assurance that it has considered all necessary transition elements or that the security and interoperability of its systems will not be affected as other Government agencies and entities transition to IPv6. Accordingly, even if NASA can continue meeting its communication needs using IPv4 addresses, it should ensure that its systems are prepared as other Internet users transition to IPv6.
Openflow Stanford University - Ericsson CollaborationEricsson Labs
1. Stanford University and Ericsson are collaborating on OpenFlow and SDN research to improve network performance and enable new applications.
2. Their work includes evaluating SDN architecture designs, improving network resiliency and reducing latency between controllers and switches.
3. Inline service chaining allows dynamic ordering of network services for subscribers based on policies, with different service paths for different traffic types.
The Internet Society's Deploy360 program aims to advance the real-world deployment of Internet protocols like IPv6 and DNSSEC by providing hands-on technical resources for implementers. It works with first adopters to collect deployment experiences and create documentation to distribute to other networks. Deploy360 encourages participants to use its online resources, provide feedback, and help create additional content to help more people adopt these open standards.
The document discusses the importance of transitioning to IPv6. IPv4 addresses are depleted, while IPv6 provides vastly more addresses required for continued Internet growth. IPv6 was designed for the global commercial Internet and makes business sense as IPv4 addresses now cost money. IPv6 deployment is already underway by many major service providers, content companies, and operating systems. IPv6 is mandatory for the Internet to keep growing and accommodating new users, devices, and services.
Can IPv6 and SIP really work together well? At the SIP Network Operators Conference (SIPNOC) on April 24, 2013, Dan York moderated a panel on this specific question and gave an update on IPv6 deployment and interaction with VoIP.
Presentation during ION Belfast called "Why Implement DNSSEC" from Jim Galvin of Afilias.
DNSSEC helps prevent attackers from subverting and modifying DNS messages and sending users to wrong (and potentially malicious) sites. So what needs to be done for DNSSEC to be deployed on a large scale? We’ll discuss the business reasons for, and financial implications of, deploying DNSSEC, from staying ahead of the technological curve, to staying ahead of your competition, to keeping your customers satisfied and secure on the Internet. We’ll also examine some of the challenges operators have faced and the opportunities to address those challenges and move deployment forward.
In 2014, the Internet Society launched a project to address the perceived gap between Operators and the IETF. The objective of this project is ultimately to facilitate communications between the operator community and the IETF to help ensure that operational realities inform the development of key standards. The first phase of this project was a survey of the operator community that was conducted over the first half of 2014. This talk aims to synthesize the survey results, along with information we collected directly from operators during the survey window. The primary purpose of doing this is to start a conversation which we hope will lead to increases in the level of operational input and feedback to the IETF standards making process. We understand the problems, now let’s start finding solutions!
Feel free to read our Internet-Draft ahead of time: https://tools.ietf.org/html/draft-opsawg-operators-ietf
This document discusses a speech given at an Internet Society conference in Ljubljana, Slovenia in October 2012. The speech emphasizes the importance of preserving core Internet principles like freedom of expression, open information, and participation. It also stresses the role of measurement and continued development of technologies like IPv6 and DNSSEC to ensure the longevity and sustainable development of the Internet infrastructure. Additionally, it provides an overview of the work done by the Slovenian chapter of the Internet Society to contribute to Internet governance issues and development.
The IETF is a global community that develops open standards (RFCs) to improve the Internet through working groups and meetings. It has produced standards for key Internet technologies like TCP/IP, email, routing, DNS, and web. The IETF operates through an open process involving mailing lists, draft documents, and meetings held around the world. It has over 100 working groups organized in 7 areas. Participation is open to volunteers and fellowships are available to encourage participation from underrepresented groups.
Who are you really calling? When we we use VoIP systems, how can we be sure we are talking to the correct people? Particularly as we increasingly move communications to IP? In this presentation at SIPNOC 2013, Dan York introduced the ideas around DNSSEC and DANE and asked questions around how these might potentially be used to add an additionally layer of security for VoIP.
For more info, see:
http://www.internetsociety.org/deploy360/dnssec/
This document provides a 3-paragraph summary of a 10-page project report on IPv6. The report was submitted by Udipto Ghosh to MIT Pune in partial fulfillment of a post-graduate diploma in management. The summary discusses that IPv6 is an evolutionary upgrade to IPv4 designed to allow continued growth of the internet. It also describes some key features of IPv6 like larger address space and auto-configuration. The transition from IPv4 to IPv6 is expected to occur gradually as IPv6 is deployed incrementally for early benefits while coexisting with IPv4 for a long time.
This document discusses strategies for transitioning from IPv4 to IPv6. It describes:
1. Dual-stack as the simplest approach, allowing IPv4 and IPv6 to operate simultaneously and maintain legacy IPv4 applications while adding new IPv6 applications.
2. Tunneling mechanisms like configured and automatic tunnels that allow IPv6 packets to be encapsulated and sent over IPv4 networks.
3. Transition scenarios involving gradual deployment of dual-stack systems and applications until pure IPv6 is achieved, maintaining compatibility with IPv4 nodes during transition.
The key recommendation is for applications to support dual-stack environments to facilitate a smooth transition and interoperability between IPv4 and IPv6 nodes. Careful planning
IPv6 Deployment -- Solving a Chicken-and-Egg Problem In Divide-and-Conquer StyleChristian Vogt
The document discusses IPv6 deployment and the challenges of a complex transition from IPv4. It proposes a "divide and conquer" approach with three stages: 1) enabling IPv6 connectivity for users first before upgrading network internals, 2) leveraging content delivery networks to accelerate IPv6 availability of content, and 3) simplifying legacy IPv4 support through IPv4-IPv6 translation in the long term. This staged approach addresses critical business needs and aims to promote IPv6 adoption incrementally despite technical difficulties of a full transition.
PLNOG 4: Klaudiusz Staniek - Efficient Technique for Enforcing Internet Peeri...PROIDEA
This document proposes an efficient technique for enforcing internet peering policies at the data plane level using Cisco router capabilities. It tags peer and customer prefixes uniquely in the BGP and forwarding information base (FIB) tables. It then tags incoming packets based on the longest prefix match and forwards or discards packets according to the tag. This glues the BGP control plane policies to the IP data plane policies to block peer-to-peer transit traffic while allowing customer-to-peer and customer-to-customer traffic. The technique is available on many Cisco routers today and complements other BGP applications.
The document discusses IPv6 over MPLS on Cisco routers, including:
- 6PE allows IPv6 connectivity over an IPv4/MPLS backbone by using MPLS labels between PE routers to tunnel IPv6 packets. Configuration on Cisco routers is straightforward, requiring IPv6 BGP neighbor configuration and the "neighbor send-label" command.
- 6VPE extends the concept of VPNs to IPv6 using scoped addressing architecture. It allows dual-stacked VRFs for consistent IPv4 and IPv6 VPN services. Configuration requires defining VRFs and associating interfaces using "vrf forwarding".
Gabriel Paues - IPv6 address planning + making the case for WHYIKT-Norge
The document discusses planning for IPv6 addressing and deployment, providing tips and examples for allocating IPv6 addresses within a /48 assignment in a hierarchical manner using subnets of /64 to simplify administration and support techniques that rely on a consistent subnet size, as well as enabling IPv6 services gradually on servers without initially exposing them to IPv6 DNS records. It also addresses common objections to IPv6 deployment and provides strategies for getting started with IPv6.
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.
This document provides an overview of mobility management and key concepts in IP mobility. It discusses macro mobility protocols including Mobile IPv6 (MIPv6) and Fast Handovers for MIPv6 (FMIPv6), as well as micro-mobility protocols like Cellular IP, HAWAII, and Hierarchical Mobile IPv6 (HMIPv6). The introduction defines IP mobility and the need for mobility support in IP given that the current IP address model assumes fixed locations. It also describes how Mobile IP allows devices to move between networks while keeping the same IP address.
Overview slide deck on HSPA+, explaining the evolution path, performance enhancements, user experience, network commitments, deployments, launches worldwide,and the growing eco-system of user devices.
This presentation draws upon the Global HSPA+ Network Commitments and Deployments information paper published by GSA on June 9, 2010 and the HSPA Devices Survey published by GSA on April 22, 2010.
This document provides an overview of the Sonaps networked production system, including its file-based workflow, remote connectivity capabilities, and support services. The system allows for planning, acquisition, editing, playout and archiving in a collaborative environment. It has been implemented in over 300 facilities worldwide, supporting news, sports and live production. Remote sites can access centralized content and contribute material efficiently using the system's distributed workflow and network infrastructure. Comprehensive support is also provided through remote monitoring, automatic fault reporting, and rapid on-site response capabilities.
SpringOne 2GX 2011 - Writing applications for Cloud Foundry using Spring and ...trisberg
The document discusses writing applications for Cloud Foundry using Spring and MongoDB. It provides an introduction to Cloud Foundry and MongoDB, describes Spring Data support for MongoDB including using MongoTemplate and Mongo Repository, and discusses why one would run MongoDB in the cloud. Key topics covered include characteristics of PaaS platforms like Cloud Foundry, choices of frameworks, application services, and clouds available in Cloud Foundry, data modeling in MongoDB using documents rather than tables, and querying and indexing MongoDB.
NASA OIG: Status of NASA's Transition to Internet Protocol Version 6 (IPv6)Bill Duncan
Results NASA has taken preliminary steps to meet OMB requirements for IPv6 transition and integration, including assigning a lead official in November 2005 to coordinate NASA's efforts, developing inventories of IP-aware devices and an impact analysis, and in June 2008 demonstrating IPv6 capability of one NASA network
.
However, as of March 2010 the Agency did not have an updated or complete IPv6 transition plan as required by OMB. This occurred, in part, because the Agency has ample IPv4 addresses to meet its current and future requirements and because the individual who was leading the IPv6 transition effort left NASA in November 2006 and no one has been assigned to replace him.
As a result, the Agency does not have adequate assurance that it has considered all necessary transition elements or that the security and interoperability of its systems will not be affected as other Government agencies and entities transition to IPv6. Accordingly, even if NASA can continue meeting its communication needs using IPv4 addresses, it should ensure that its systems are prepared as other Internet users transition to IPv6.
Openflow Stanford University - Ericsson CollaborationEricsson Labs
1. Stanford University and Ericsson are collaborating on OpenFlow and SDN research to improve network performance and enable new applications.
2. Their work includes evaluating SDN architecture designs, improving network resiliency and reducing latency between controllers and switches.
3. Inline service chaining allows dynamic ordering of network services for subscribers based on policies, with different service paths for different traffic types.
The Internet Society's Deploy360 program aims to advance the real-world deployment of Internet protocols like IPv6 and DNSSEC by providing hands-on technical resources for implementers. It works with first adopters to collect deployment experiences and create documentation to distribute to other networks. Deploy360 encourages participants to use its online resources, provide feedback, and help create additional content to help more people adopt these open standards.
The document discusses the importance of transitioning to IPv6. IPv4 addresses are depleted, while IPv6 provides vastly more addresses required for continued Internet growth. IPv6 was designed for the global commercial Internet and makes business sense as IPv4 addresses now cost money. IPv6 deployment is already underway by many major service providers, content companies, and operating systems. IPv6 is mandatory for the Internet to keep growing and accommodating new users, devices, and services.
Can IPv6 and SIP really work together well? At the SIP Network Operators Conference (SIPNOC) on April 24, 2013, Dan York moderated a panel on this specific question and gave an update on IPv6 deployment and interaction with VoIP.
Presentation during ION Belfast called "Why Implement DNSSEC" from Jim Galvin of Afilias.
DNSSEC helps prevent attackers from subverting and modifying DNS messages and sending users to wrong (and potentially malicious) sites. So what needs to be done for DNSSEC to be deployed on a large scale? We’ll discuss the business reasons for, and financial implications of, deploying DNSSEC, from staying ahead of the technological curve, to staying ahead of your competition, to keeping your customers satisfied and secure on the Internet. We’ll also examine some of the challenges operators have faced and the opportunities to address those challenges and move deployment forward.
In 2014, the Internet Society launched a project to address the perceived gap between Operators and the IETF. The objective of this project is ultimately to facilitate communications between the operator community and the IETF to help ensure that operational realities inform the development of key standards. The first phase of this project was a survey of the operator community that was conducted over the first half of 2014. This talk aims to synthesize the survey results, along with information we collected directly from operators during the survey window. The primary purpose of doing this is to start a conversation which we hope will lead to increases in the level of operational input and feedback to the IETF standards making process. We understand the problems, now let’s start finding solutions!
Feel free to read our Internet-Draft ahead of time: https://tools.ietf.org/html/draft-opsawg-operators-ietf
This document discusses a speech given at an Internet Society conference in Ljubljana, Slovenia in October 2012. The speech emphasizes the importance of preserving core Internet principles like freedom of expression, open information, and participation. It also stresses the role of measurement and continued development of technologies like IPv6 and DNSSEC to ensure the longevity and sustainable development of the Internet infrastructure. Additionally, it provides an overview of the work done by the Slovenian chapter of the Internet Society to contribute to Internet governance issues and development.
The IETF is a global community that develops open standards (RFCs) to improve the Internet through working groups and meetings. It has produced standards for key Internet technologies like TCP/IP, email, routing, DNS, and web. The IETF operates through an open process involving mailing lists, draft documents, and meetings held around the world. It has over 100 working groups organized in 7 areas. Participation is open to volunteers and fellowships are available to encourage participation from underrepresented groups.
Who are you really calling? When we we use VoIP systems, how can we be sure we are talking to the correct people? Particularly as we increasingly move communications to IP? In this presentation at SIPNOC 2013, Dan York introduced the ideas around DNSSEC and DANE and asked questions around how these might potentially be used to add an additionally layer of security for VoIP.
For more info, see:
http://www.internetsociety.org/deploy360/dnssec/
This document provides a 3-paragraph summary of a 10-page project report on IPv6. The report was submitted by Udipto Ghosh to MIT Pune in partial fulfillment of a post-graduate diploma in management. The summary discusses that IPv6 is an evolutionary upgrade to IPv4 designed to allow continued growth of the internet. It also describes some key features of IPv6 like larger address space and auto-configuration. The transition from IPv4 to IPv6 is expected to occur gradually as IPv6 is deployed incrementally for early benefits while coexisting with IPv4 for a long time.
This document discusses strategies for transitioning from IPv4 to IPv6. It describes:
1. Dual-stack as the simplest approach, allowing IPv4 and IPv6 to operate simultaneously and maintain legacy IPv4 applications while adding new IPv6 applications.
2. Tunneling mechanisms like configured and automatic tunnels that allow IPv6 packets to be encapsulated and sent over IPv4 networks.
3. Transition scenarios involving gradual deployment of dual-stack systems and applications until pure IPv6 is achieved, maintaining compatibility with IPv4 nodes during transition.
The key recommendation is for applications to support dual-stack environments to facilitate a smooth transition and interoperability between IPv4 and IPv6 nodes. Careful planning
IPv6 campus transition: A Central Luzon State University case studyjournalBEEI
Internet connections still use IPv4 as the primary address protocol and it is now facing exhaustion. However, academic institutions specifically in the Philippines should devise steps to address the exhaustion of IPv4. In this paper, this is brought to light as we present the IPv4 to IPv6 campus transition techniques to address the issue. The experiment is carried out in Central Luzon State University and is assessed if the university is able to adopt the IPv6 transition in their campus network. Two IPv6 transition mechanisms were implemented and tested. As a general result, it has been found out, through testbeds, that the dual-stack transition mechanism is more suitable than 6 to 4 tunnel broker. The results have also shown that 6 to 4 tunnel broker was outperformed by dual-stack transition mechanism in all areas and presents better performance. Additionally, results also showed that IPv4 presents slight advantages in terms of network performance than IPv6 with a very small percentage in difference, and this does mean that migration to IPv6 is possible without performance detriments. Furthermore, the results also provide a proof of concept for the university especially in the Philippines to consider IPv6 for future migration within their campus network.
Ieee Transition Of I Pv4 To I Pv6 Network Applicationsguest0215f3
This document discusses transitioning IPv4 network applications to IPv6. It begins with an introduction to the need for IPv6 due to IPv4 address depletion. It then discusses IPv6 architecture and some key benefits of IPv6 like increased address space and built-in security. The document outlines three primary considerations for transitioning applications: using IPv6 multicast instead of IPv4 broadcast, enabling multicast reception, and ensuring dual stack compatibility. It categorizes transition complexity and provides examples of changes needed, such as replacing IPv4 data structures and function calls with IPv6 equivalents. Related work on transitioning applications is also discussed.
A Survey On Next Generation Internet Protocol IPv6Carrie Romero
This document discusses IPv6 and the need to transition from IPv4 to IPv6. It provides an overview of IPv6, including that IPv6 was developed to address the limited address space of IPv4 and improve security. It also discusses some of the key challenges in transitioning to IPv6, such as the need for IPv6 and IPv4 to coexist during transition. The document summarizes various transition techniques between IPv6 and IPv4, including dual stack, tunneling, and translation methods.
IRJET- Evaluating the Impact of IPv4 to IPv6 Tunneling with MPLS on VOIPIRJET Journal
This document summarizes a research paper that evaluates the impact of transitioning from IPv4 to IPv6 using tunneling with MPLS on voice over IP (VOIP) performance. It first provides background on the need to transition from IPv4 to IPv6 due to limited IPv4 address space. It then discusses different transition mechanisms like tunneling and their benefits. The paper reviews previous studies that found 6-to-4 tunneling provides VOIP performance similar to IPv6. It also discusses how MPLS can ensure quality of service for real-time applications like VOIP. The goal of the research was to analyze how tunneling from IPv4 to IPv6 with MPLS impacts VOIP performance metrics.
The document provides an overview of IPv6 adoption around the world and in Malaysia specifically. It discusses the depletion of IPv4 addresses forcing a transition to IPv6. The US government has mandated all federal agencies upgrade to IPv6 by certain deadlines. In Malaysia, the National IPv6 Council was established in 2004 to guide the transition. ISPs have undergone compliance audits to test IPv6 connectivity. The Malaysian government also released IPv6 transition guidelines for the public sector outlining a phased approach for agencies to upgrade networks and applications to IPv6.
IPV6 Deployment for Broadband Internet by Azura Mat SalimMyNOG
Telekom Malaysia (TM) has been deploying IPv6 since 2004 to prepare for IPv4 address exhaustion. In 2011, TM accelerated its IPv6 implementation by forming a steering committee and focusing on network infrastructure, operations, IT systems, products, and training. Currently, TM has over 100 IPv6 peering partners globally and provides dual-stack broadband Internet using PPPoE and DHCPv6 with delegated IPv6 prefixes. While IPv6 traffic is still less than 1% of TM's total traffic, the number of dual-stack subscribers is growing steadily as more users acquire IPv6-compatible devices. TM's deployment strategy is to push IPv6 configurations gradually without forcing migration and provide education to address common user misconceptions
This document provides a report on a vocational training in IPV6 that was completed by Rashmi Kumari. It includes an introduction to IPV6 that compares it to IPV4 and highlights its larger address space, built-in multicasting, and network layer security. It also details IPV6's simplified packet format and routing. The report then discusses addressing, OSPF, implementing OSPF for IPV6, and building a simulated network with dual stack transition in GNS3 to test IPV6 functionality.
This document discusses IPv6 tunneling algorithms used in 4G networks. It provides background on limitations of IPv4 including limited address space and routing table issues. It then introduces IPv6, describing its larger address space, simplified header format, and other features. It discusses types of IPv6 tunnels including automatic and configured tunnels. Configured or static tunnels are described as manually assigning IPv4 addresses to permanently link isolated IPv6 networks over an IPv4 backbone.
This document summarizes an update on IPv6 activity in CERNET2 that was presented on March 5, 2015. It discusses that CERNET2 has had a pure IPv6 backbone since 2003 connecting over 600 universities. IPv6 related research and experiments are conducted on CERNET2. Traffic statistics from January 2015 show backbone traffic exceeding 40Gbps and 10Gbps in some locations. The document also discusses challenges with scaling the DNS root server system and efforts to address this through techniques like anycasting and expanding the number of root server operators.
The document discusses considerations for adopting IPv6, including drivers for IPv6 adoption like addressing the shortage of IPv4 addresses, and factors that affect the timing of IPv6 adoption. It summarizes Tata Communication's IPv6 network and services, noting they have been an early IPv6 adopter with over 40 major customers connected via both IPv4 and IPv6.
Oasis Communication Technologies is an expert in IPv6 deployment based on their experience implementing IPv6 networks for various clients over many years. They discuss three case studies: an early dual-stack deployment for IGLD, a global IPv6 rollout for PCCW Global using 6PE, and a customer deployment for Xfone 018. They also discuss lessons learned, including that the core network is simple but access networks are complex, addressing design is challenging, and that lack of IPv6-enabled content and customer equipment readiness are major barriers to adoption.
Whitepaper what enterprises should do about i pv6 in 2011 cisco_eric.vynckeNTTE_France
The white paper discusses how enterprises should prepare for IPv4 address exhaustion, which is projected to occur between 2011-2013. It recommends that enterprises assess their position on IPv6 in 2011 to start drafting requirements, plans, and opportunities. As IPv4 addresses run out, integration strategies like dual-stack, shared IPv4 addresses, and IPv6-only will be used, leading to different types of Internet users over the next 3-5 years. Enterprises should take a conservative approach for IPv4 users and aggressive approach for IPv6.
The document describes a new transition methodology called BD-SIIT for translating between IPv4 and IPv6. BD-SIIT uses a bidirectional mapping algorithm between IPv4 and IPv6 headers and addresses. It avoids embedding the IPv4 address directly into the IPv6 address. Instead, it uses a new address mapping approach based on identifying corresponding public IPv4 and IPv6 addresses.
I pv6 migration_strategies_for_mobile_networks_whitepaperAbdo sayed
This white paper discusses IPv6 migration strategies for mobile networks using 464XLAT. 464XLAT allows mobile operators to transition to an IPv6-only network while still providing IPv4 services. It combines stateful NAT64 translation, stateless translation on user devices, and DNS64. This provides IPv4 connectivity across an IPv6 network for all applications in a simple, scalable way. 464XLAT reduces costs for mobile operators by minimizing traffic that must pass carrier-grade NAT. It also ensures a high quality experience for users as both IPv4 and IPv6 applications and websites are supported.
Tony Smith presented on the status of IPv6 deployment globally and in the Asia Pacific region based on various statistics. He found that IPv6 deployment is varied among regions, economies, and network operators, with some being more active than others. Statistics showed growth of IPv6 adoption in countries like China, Hong Kong, Japan, Singapore, and Taiwan due to initiatives by governments and private sectors working together. Mobile networks were also shifting to IPv6 to support growth in mobile broadband usage. Continuous information sharing and collaboration between stakeholders was key to supporting current and future Internet growth.
23 November 2017 - At ION Belgrade, Kevin Meynell discusses what happened at the recent IETF meeting, and how to get involved in the open Internet standards community.
The document provides information about the Internet Society and its Deploy360 program. It summarizes that the Internet Society was founded 25 years ago to support the technical evolution and use of the Internet. Its Deploy360 program aims to advance the real-world deployment of protocols like IPv6, DNSSEC, and TLS by providing hands-on technical resources for networks. The program involves online documentation, events, and engaging with first adopters to share deployment experiences. It encourages participation through its website, social media, and industry events.
This document provides information about joining the Internet Society and its Serbia chapter to help preserve the open internet. It encourages attendees to get involved by creating content or providing feedback to help develop resources for internet deployments. Contact details and links are given to follow developments and access presentation materials from the conference.
September 2017 - Aftab Siddiqui presents on the Mutually Agreed Norms for Routing Security (MANRS), and how we can work together to improve the security and resiliency of the Internet's routing system.
18 September 2017 - ION Malta
What’s happening at the Internet Engineering Task Force (IETF)? What RFCs and Internet-Drafts are in progress related to IPv6, DNSSEC, Routing Security/Resiliency, and other key topics? We’ll give an overview of the ongoing discussions in several working groups and discuss the outcomes of recent Birds-of-a-Feather (BoF) sessions, and provide a preview of what to expect in future discussions.
Collaboration and shared responsibility are two pillars supporting the Internet’s growth and success. While the global routing system has worked well, it has significant security challenges that we must address. In this panel, security experts will discuss how we can create a culture of collective responsibility and improve the global routing system, including an introduction to the “Mutually Agreed Norms for Routing Security” (MANRS).
18 September 2017 - ION Malta
DNSSEC helps prevent attackers from subverting and modifying DNS messages and sending users to wrong (and potentially malicious) sites. So what needs to be done for DNSSEC to be deployed on a large scale? We’ll discuss the reasons for deploying DNSSEC, examine some of the challenges operators have faced, and address those challenges and move deployment forward.
18 September 2017 - Rick Lamb, ICANN, on DANE:
If you connect to a “secure” server using TLS/SSL (such as a web server, email server or xmpp server), how do you know you are using the correct certificate? With DNSSEC now being deployed, “DANE” (“DNS-Based Authentication of Named Entities”) has emerged allowing you to securely specify exactly which TLS/SSL certificate an application should use to connect to your site. DANE has great potential to make the Internet much more secure by marrying the strong integrity protection of DNSSEC with the confidentiality of SSL/TLS certificates. In this session, we will explain how DANE works and how you can use it to secure your websites, email, XMPP, VoIP, and other web services.
18 September 2017 - At ION Malta, Adam Peake discusses the IANA transition:
The IANA transition was successfully completed in October 2016 creating strengthened relationships between the IETF (Internet protocols and standards), Regional Internet Registries RIRs (IP addresses), and ccTLD and gTLD operators and TLD community and ICANN. A new organisation, Public Technical Identifiers (PTI), an affiliate of ICANN, is now responsible for performing the IANA functions and delivering the IANA Services on behalf of ICANN. The session will discuss these new arrangements and how they have enhanced ICANN’s accountability and transparency to the global Internet community. The session will also describe how ICANN is preparing for the Root KSK Rollover.
This document summarizes Finland's efforts to promote IPv6 adoption. It discusses the formation of the Finnish IPv6 Task Force to develop recommendations for IPv6 implementation. It also describes Finland's national IPv6 launch in 2015, where major ISPs enabled IPv6 for over 5 million broadband subscriptions. As a result, IPv6 usage increased significantly. The document discusses challenges faced during the transition like upgrading network equipment and changing attitudes. It concludes that while work remains, the launch was successful and IPv6 introduction costs can be limited by starting with easier implementations.
The document discusses Marco d'Itri's thoughts on the transition to IPv6. It describes the transition as ongoing, with no flag days, as IPv6 adoption grows. It notes that while IPv4 NAT is easy for access networks, it is difficult for servers. Many large content providers already use IPv6. The transition involves steps before IPv4 addresses ran out, the current transition period, and after the transition when IPv4 will be optional. IPv6 adoption is growing in several countries like Belgium and the US. Eventually IPv4-only islands will need to make themselves accessible over IPv6. The document provides advice on starting an IPv6 transition and offers a simple IPv6 addressing plan.
MANRS protects networks and reputations by preventing BGP leaks and spoofing that can saturate networks or attack infrastructure. Implementing MANRS filtering of BGP customers and spoofed traffic helps avoid these issues. It also allows other networks to filter your routes to prevent leaks. While RPSL is complex, registering autonomous systems and routes in the RIPE database through simple objects helps third parties and saves time for automation. Overall, MANRS establishes basic management practices that benefit networks by improving stability and security.
The document provides information about celebrating 25 years of the Internet Society and getting involved in various initiatives. It encourages readers to help shape the future of the internet, visit websites for more resources, follow social media accounts, and find presentation archives from a past conference. Contact details are also listed.
The document summarizes Thato Mfikwe's presentation at the ION Conference 2017 in Durban about the ISOC South Africa Gauteng Chapter. It provides details about the chapter's establishment, vision, pillars, membership reach across Africa and Europe, and projects from 2014-2016 and planned for 2017 focusing on community networks, policy engagement, outreach, and training. It also discusses ICT, internet governance landscape, topics at the ION conference including DNS, IPv6, cyber threats, and secure routing.
7 September 2017 - At ION Conference Durban, South Africa, Kevin Meynell discusses what's happening at the IETF in the world of Internet standards, and how you can get involved in the process.
More from Deploy360 Programme (Internet Society) (20)
1. Industry Collaboration:
Working Together to Deploy IPv6
ION Conference
Mumbai India
10th October 2012
Martin J. Levy, Director IPv6 Strategy
Hurricane Electric
2. Agenda
IPv6 IPv6 IPv6 *
11+ years of IPv6 at Hurricane Electric
Visualizing IPv6 usage and more
Motivate networks into implementing IPv6?
* A reference to Dorothy’s ruby slippers from The Wizard of Oz
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 2
3. HURRICANE ELECTRIC
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 3
4. Hurricane Electric – Roots and History
Founded 17+ years ago - ISP & datacenter operator
1994 – Roots within the Silicon Valley high-tech community
1999 – Expanded IPv4 network nationwide in the US
2001 – Started IPv6 native and tunnel connectivity ( http://tunnelbroker.net )
2006 – Full “technology refresh” enabled native dual-stack IPv6 backbone
2008 – Became largest IPv6 backbone globally ( > 1Gbps IPv6 traffic level)
2009 – Continued expansion into Asia; enabled IPv6 6to4 & Teredo global service
2010 – Added more geographic coverage; expanded IPv6 6to4 and DNS service
2011 – Try to convince people to stop talking about IPv6; just talk about the “Internet”
2012 – World IPv6 Launch – 6th June 2012 – ready and waiting
Deployed fully IPv6 ready
Europe, Asia and the US
and Toronto, Canada
Further expansion in
datacenter building
expanded to 9 US,
services in Atlanta
Backbone for BGP
4 European Cities
IPv6 tunnelbroker
In Singapore and
Tokyo and Zurich
three continents
6to4 and teredo
Ranked #1 IPv6
Added services
Added services
five other cities
IPv6 backbone
dns.he.net into
Deployed IPv6
relays globally
in Hong Kong
IPv6 services
In Stockholm,
206,000 sq ft
adjacencies
Added IPv6
Purchased
Expansion
dual-stack
Rolled out
European
Added
Q1 Q1 Q2 Q3 Q4 Q1 Q2 Q2
2005 2006 2007 2008 2008 2008 2008 2009 2009 2010 2011 2012
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 4
5. Hurricane Electric’s 11 year experience with IPv6
IANA IPv4 exh
aust ion
IETF kicks o
ff IPng (IPv
6)
2011
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
Curiosity & Intrigue True operational experience
.net
IPv6 tunnelbroker
2001
Full technology re
fresh
2006
Deployed 6to4
& Teredo
2009
Eleven years of experience really helps!
IPv6 has matured World IPv6
Launch
2012 – IPv6 is part of day-to-day work; no big deal! 2012
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 5
6. Hurricane Electric – IPv6 Global Network
All Hurricane Electric POPs are full IPv6 Native routing and peering
Hong Kong Bay Area Los Angeles Kansas City New York Area Paris
Equinix
Equinix Telehouse
1100 Walnut Interxion
Oak Tower
Newark
Fremont
Palo Alto One Wilshire New York
Mega-i 600 W 7th 1102 Grand Telehouse
San Jose
Vancouver
Seattle
Stockholm
Portland Montreal
Minneapolis Toronto
Dublin Amsterdam Berlin
Warsaw
Salt Lake City Cleveland New York Frankfurt
London Prague
Tokyo Bay Area Paris
Seoul Chicago
Zurich Vienna
Denver Ashburn
New Delhi Kansas City Milan
Las Vegas
Hong Kong Taipei Los Madrid
Angeles Phoenix Atlanta
Bangalore
Dallas
Singapore Houston
Miami
AS6939 Map o IPv6 peering at all major
utdate peering points in US, Europe &
d!
Asia. Private and public
peering capacity at 10Gbps
and above.
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 6
7. IT’S TWENTY TWELVE …
IPv6 BY THE NUMBERS
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 7
8. IPv6 measured at via BGP ASNs with IPv6
http://bgp.he.net/ipv6-progress-report.cgi
Networks Running IPv6
We can measure the percentage of networks running IPv6 by comparing the set
of ASes in the IPv6 routing table to those in the combined set of IPv4 and IPv6.
IPv4 and IPv6 RIBs
Last Parsed: Wed Oct 10 01:10:25 PDT 2012 15%
14%
14.6%
W6L
13%
IPv4 ASes: 42474 12%
IPv6 ASes: 6207
Percentage of ASNs running v6
11%
ASes using only IPv4: 36382 10%
W6D
ASes using only IPv6: 115 9%
8%
ASes using IPv4 and IPv6: 6092
IANA Runout
7%
ASes using IPv4 or IPv6: 42589 6%
Percentage of ASes (IPv4 or IPv6) 5%
running IPv6: 14.6% 4%
3%
2%
1% 3.6%
0%
10/2008
10/2009
10/2010
01/2011
04/2011
07/2011
10/2011
10/2012
07/2008
01/2009
04/2009
07/2009
01/2010
04/2010
07/2010
01/2012
04/2012
07/2012
Date
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 8
9. Is IPv6 routing/interconnect/peering prevalent?
~70% average increase per year!
http://bgp.he.net/report/prefixes#_prefixes
~50% average increase per year!
http://bgp.he.net/report/prefixes#_networks
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 9
10. http://www.worldipv6launch.org/
2012 & WORLD IPv6 LAUNCH
Don’t be left behind
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 10
11. But first … 2011 World IPv6 Day
World IPv6 Day was about enabling web-based traffic for IPv6
Focus on content providers
Web (port 80 & 443 TCP traffic) plotted below
Instant traffic
at 00:00 UTC
5X traffic peak
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 11
12. 2012 World IPv6 Launch - real IPv6 traffic
Long term win since W6D in IPv6 traffic levels
That means there are both content and eyeballs in play
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 12
13. 2012 World IPv6 Launch - real IPv6 traffic
Exchange points showing IPv6 traffic spikes
DE-CIX Frankfurt
AMS-IX Amsterdam
Interesting IPv6 traffic spike in Frankfurt prior to W6L
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 13
14. VISUALIZING IPv6
GLOBALLY AND WITHIN
INDIA
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 14
15. Checking global IPv6 routing – graphically!
Showing IPv4/IPv6 route propagation
in a graphical form
.ne t/
gp .he
ttp ://b
h
Caveat:
- This tool is only as good as its source data.
- IP information is uploaded from RIPE RIS & Oregon routeviews.
- Some views are missing; not all routes and paths are visible.
- NOT based on the Hurricane Electric routing tables.
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 15
16. http://bgp.he.net/ - Searching on ASN, IP, etc.
ASN AS5713
IPv4 address 196.21.79.50
Search IPv4 block 196.4.160.0/23
command IPv6 address 2001:4200:ffff:a::1
IPv6 block 2001:4208::/32
…etc …¯¯¯
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 16
17. Example of BGP tools – IPv4/IPv6 statistics
IPv6 and IP4 BGP
and routing information
http://bgp.he.net/
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 17
18. http://bgp.he.net/ – Route propagation graphs
Select tab for v4 or v6 graphs
Routes see downstream of peers
Peers that see routes
ASN originating
routes
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 18
19. Can regional IPv6 routing be measured?
Question:
Is there enough IPv6 routing between ISPs?
Can IPv6 BGP routing tables provide insight?
Methodology:
Lots of BGP routing tables collected globally
Data from http://bgp.he.net/ processed further
Graphical view on a country-to-country basis
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 19
20. Measuring BGP routing by collecting tables
Build on exceptional work by others
RIPE/RIS & Oregon routeviews collect BGP tables
A hearty “thank you” to RIPE & University of Oregon
Use Hurricane Electric’s http://bgp.he.net/ site and it’s database
Daily processing of those BGP tables
Results are user-friendly visualization of routing
Take the data one step further …
Only look at BGP peer data (v4 & v6)
It’s only interesting to look at BGP adjacency
Map ASN to country-codes
Search for adjacencies where CCs are different
Process resulting data to search for in-region connections
Clean up the data
Display the data
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 20
21. Example processing – CC & ASN
Process each ASN within each country
http://bgp.he.net/country/MY
http://bgp.he.net/AS24514#_peers
Remove all peers within CC
Note the ASNs within the country …
Note the peer connections that are
outside the country …
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 21
22. Visualizing IPv6 routing within India
Full country listing at http://bgp.he.net/country/IN
http://bgp.he.net/country/IN
ASNs sorted by Adjacency count
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 22
23. Visualizing IPv6 routing within India
Routing propagation graphs for four providers in India
These change all the time; it’s best to look online for latest BGP propagation
Caveat: Not all links will show within these graphs
10 Oct 2012 Martin J Levy - Hurricane Electric - Working Together to Deploy IPv6 23