This document summarizes routing and addressing trends on the internet from 2016-2017. It finds that routing table growth for IPv4 continues steadily at around 53,000 new prefixes and 3,400 new ASNs per year. IPv4 address exhaustion is being addressed through more specific advertisements and address recovery rather than a slowdown in growth. IPv6 routing table growth also remains steady, with around 10,000 new prefixes added annually. The overall stability of routing and limited growth in routing updates suggests that BGP will continue to effectively route the internet for the foreseeable future. Hardware suppliers may need to optimize routing tables to address the growing size of forwarding tables.
This document discusses trends in internet routing from 1994 to 2016 based on Route Views peering data. Some key points:
- IPv4 routing table and AS numbers continue to grow steadily at around 54,000 new entries and 3,400 new ASes per year despite IPv4 address exhaustion. Growth is supported by address recycling and shorter prefixes.
- IPv6 routing table is growing but at a slower rate than IPv4, increasing by around 6,000 entries per year. IPv6 adoption is still concentrated among early adopters.
- BGP update rates have remained relatively constant for IPv4 despite overall growth, likely due to Minimum Route Advertisement Interval (MRAI) damping. IPv6 updates are more uneven
Routing in 2016 remained stable, with IPv4 growing at around 54,000 new routing prefixes and 3,450 new ASNs per year. IPv6 growth was slower, with around 6,000 new routing prefixes and 1,700 new ASNs per year. While IPv4 addresses are exhausted, routing continues to grow through the increased use of more specific prefixes and the recycling of older addresses. BGP routing tables and updates remained mostly stable and predictable in both IPv4 and IPv6.
This document summarizes routing and addressing trends from 2016-2018 as viewed through BGP routing data. Some key points:
- IPv4 routing table and AS numbers continue growing at a steady pace, despite address exhaustion. More specific routes and shorter prefixes are being used.
- IPv6 routing table and AS numbers are growing faster than IPv4, though inter-AS connectivity remains similar.
- Address recovery and transfers have slowed the growth of advertised IPv4 space while increasing the pool of unused addresses.
- BGP update rates and convergence times have remained relatively stable for both IPv4 and IPv6.
- The absolute size of the IPv6 routing table is projected to match IPv4 within 5 years, posing hardware
The trend stats of routing table at JPIX route serversAPNIC
1) JPIX operates internet exchange points and route servers in Tokyo and Osaka, Japan.
2) An analysis of routing tables from JPIX route servers shows that the number of IPv4 and IPv6 routes has generally increased over time as more members connect and existing members advertise more routes.
3) The distribution of prefix sizes is dominated by the typical minimum assignment sizes of /24 for IPv4 and /48 for IPv6, though some larger prefixes are present.
IPv4 addresses delegated in Indonesia have steadily increased from 2005 to 2015. As of 2015, Indonesia has received over 5 million IPv4 addresses. IPv4 address transfers allow addresses to be moved between organizations, with over 30 transfers processed for Indonesian organizations. Key requirements for transfers include the addresses being administered by APNIC and the recipient justifying their needs. Transfers can occur between APNIC members, other RIR members, and between APNIC and other NIRs.
This document summarizes routing and addressing trends on the internet from 2016-2017. It finds that routing table growth for IPv4 continues steadily at around 53,000 new prefixes and 3,400 new ASNs per year. IPv4 address exhaustion is being addressed through more specific advertisements and address recovery rather than a slowdown in growth. IPv6 routing table growth also remains steady, with around 10,000 new prefixes added annually. The overall stability of routing and limited growth in routing updates suggests that BGP will continue to effectively route the internet for the foreseeable future. Hardware suppliers may need to optimize routing tables to address the growing size of forwarding tables.
This document discusses trends in internet routing from 1994 to 2016 based on Route Views peering data. Some key points:
- IPv4 routing table and AS numbers continue to grow steadily at around 54,000 new entries and 3,400 new ASes per year despite IPv4 address exhaustion. Growth is supported by address recycling and shorter prefixes.
- IPv6 routing table is growing but at a slower rate than IPv4, increasing by around 6,000 entries per year. IPv6 adoption is still concentrated among early adopters.
- BGP update rates have remained relatively constant for IPv4 despite overall growth, likely due to Minimum Route Advertisement Interval (MRAI) damping. IPv6 updates are more uneven
Routing in 2016 remained stable, with IPv4 growing at around 54,000 new routing prefixes and 3,450 new ASNs per year. IPv6 growth was slower, with around 6,000 new routing prefixes and 1,700 new ASNs per year. While IPv4 addresses are exhausted, routing continues to grow through the increased use of more specific prefixes and the recycling of older addresses. BGP routing tables and updates remained mostly stable and predictable in both IPv4 and IPv6.
This document summarizes routing and addressing trends from 2016-2018 as viewed through BGP routing data. Some key points:
- IPv4 routing table and AS numbers continue growing at a steady pace, despite address exhaustion. More specific routes and shorter prefixes are being used.
- IPv6 routing table and AS numbers are growing faster than IPv4, though inter-AS connectivity remains similar.
- Address recovery and transfers have slowed the growth of advertised IPv4 space while increasing the pool of unused addresses.
- BGP update rates and convergence times have remained relatively stable for both IPv4 and IPv6.
- The absolute size of the IPv6 routing table is projected to match IPv4 within 5 years, posing hardware
The trend stats of routing table at JPIX route serversAPNIC
1) JPIX operates internet exchange points and route servers in Tokyo and Osaka, Japan.
2) An analysis of routing tables from JPIX route servers shows that the number of IPv4 and IPv6 routes has generally increased over time as more members connect and existing members advertise more routes.
3) The distribution of prefix sizes is dominated by the typical minimum assignment sizes of /24 for IPv4 and /48 for IPv6, though some larger prefixes are present.
IPv4 addresses delegated in Indonesia have steadily increased from 2005 to 2015. As of 2015, Indonesia has received over 5 million IPv4 addresses. IPv4 address transfers allow addresses to be moved between organizations, with over 30 transfers processed for Indonesian organizations. Key requirements for transfers include the addresses being administered by APNIC and the recipient justifying their needs. Transfers can occur between APNIC members, other RIR members, and between APNIC and other NIRs.
From Policy to Practice: Addressing and Routing in 2014 by Geoff Huston [APRI...APNIC
The document discusses the state of addressing and routing in 2014. It notes that the regional internet registries (RIRs) have run out of IPv4 addresses to allocate, with only AFRINIC still having addresses remaining. As a result, IPv4 address transfers between organizations have increased significantly. IPv6 allocation and routing has continued to grow annually but still makes up a small percentage of overall internet traffic. The average size of routing advertisements and path lengths have remained steady for both IPv4 and IPv6. IPv4 growth is slowing due to address shortages and transition to IPv6, while IPv6 growth is still in the 20-40% range annually.
Presented by Elly Tawhai, APNIC Senior Hostmaster, at the 2017 New Zealand Network Operators Group (NZNOG) meeting was held in Tauranga, New Zealand from 26 to 27 January.
This document discusses RIPE Atlas, a global Internet measurement network. It provides an overview of RIPE Atlas, including its coverage of over 14,000 probes in July 2016. New features are discussed, such as increased measurement limits and improved security. Plans for the future include giving contributors more credits based on their probe's popularity. The document also examines RIPE Atlas' view of Indonesia, showing its single anchor and potential for using the IXP-Jedi tool to analyze paths within the country. The RIPE Atlas community is encouraged to get involved by using, contributing to, or sponsoring the network.
The document discusses the Resource Public Key Infrastructure (RPKI) which aims to address routing incidents caused by IP prefix hijacking and misorigination. It provides an overview of RPKI technical details, components, and deployment status. RPKI uses digital certificates and Route Origin Authorizations (ROAs) to validate that IP prefixes are announced by their legitimate holders and prevent unauthorized route announcements. Major RPKI components include Certificate Authorities (CAs), Relying Parties (RPs), and routers configured to use RPKI data to validate BGP routes.
Vivek Nigam and Pubudu Jayasinghe discuss the Internet in Myanmar, IPv4 depletion and how Members can manage that, deploying IPv6, and routing security.
The document provides an overview of Autonomous System Numbers (ASNs) including how they are distributed and used for interconnection in Indonesia. It notes that Indonesia currently has 530 advertised ASNs and discusses challenges around the adoption of 4-byte ASNs in the country. The document also visualizes Indonesia's position within the global routing ecosystem and provides recommendations around routing security, resource registration, and route aggregation.
Internet Resource Analyst George Odagi gives an update on the implementation of APNIC policy proposal prop-132: RPKI ROAs for unallocated and unassigned APNIC address space.
IPv6 - delegations, deployment and trends, SANOG 29APNIC
Presented by Pubudu Jayasinghe, from APNIC Members Services team, at the 29th South Asian Network Operators Group meeting (SANOG29) held in Islamabad, Pakistan from 23 to 30 January 2017
The document discusses the state of IPv6 adoption and the transition from IPv4 to dual stack networks supporting both IPv4 and IPv6. It finds that while IPv6 adoption is growing, reaching about 18% of internet users, gaps still remain in parts of Asia, Eastern Europe, and Africa. It predicts that in the next few years some providers will stop supporting IPv4 only and offer IPv6 only services, which will leave remaining IPv4 only users, networks and services limited to a smaller portion of the internet. This "crunch time" where the transition is complete will be determined by market forces and could begin within the next 12-24 months.
This document discusses two options for connecting a bank to the internet: single-homing and multi-homing. Single-homing involves connecting to a single internet service provider (ISP) and is cheaper and easier to set up but offers less reliability. Multi-homing connects to multiple ISPs and offers better availability, reliability, and performance through load balancing, but requires more networking skills and expertise. The document recommends most banks start with single-homing and consider upgrading to multi-homing if internet uptime is critical to their operations.
This document provides an overview and schedule for an APNIC Member Gathering in Guangzhou, China in April 2017. The schedule includes presentations on IPv4 exhaustion, IPv4 transfers, IPv6 deployment status, and an introduction to APNIC services. Statistics are presented on IPv4 and IPv6 allocations and deployments in China and globally by year. Key topics covered include the current IPv4 and IPv6 policies of each RIR, IPv4 transfer policies and procedures, and the higher levels of IPv6 deployment seen in some Asia Pacific countries and networks.
An Update on Mobility in Today's Internet, by Geoff Huston.
Presented at the APNIC 40 "Internet – Mobility Nexus: Are We Ready for Real Mobile/Wireless Broadband?" session, Wed 9 Sep 2015.
This document discusses IPv4 transfers and the Resource Public Key Infrastructure (RPKI). It provides information on who can transfer IPv4 addresses between APNIC members and other RIRs, and shows statistics on IPv4 transfers from Singapore. It describes what RPKI is and how it helps secure internet routing by validating routes. It provides instructions on how to create Route Origin Authorization (ROA) objects in MyAPNIC to participate in RPKI and the benefits of maintaining ROAs. Statistics on ROA adoption in several Asian countries are also presented, along with an example of a successful ROA deployment campaign in Bangladesh.
Comcast began deploying IPv6 in 2005 to support future growth as IPv4 addresses were becoming inadequate. They have since made IPv6 the primary protocol for managing their network and services. Over 99% of their devices are now managed using IPv6-only, and around 40% of their internet traffic occurs over IPv6. Their goal is to continue transitioning their entire infrastructure and services to IPv6-only to fully leverage its capabilities.
Andrzej Wolski – I am trainer at RIPE NCC where I develop, manage and deliver trainings mostly about Internet Governance, RIR/LIR aspects of numeric resource distribution and best practices in IP assignment and Internet Routing with focus on RPKI in general. You can find my speaker profile at RIPE NCC website
Topic of Presentation: IPv4 Transfers
Language: Polish
Abstract: On 14 September 2012, the RIPE NCC reached its Last /8. Since then, the supply of unallocated IPv4 space has been limited to a single /22 for each Local Internet Registry. Since then there has been a growing interest in transfers of IPv4 allocations under the RIPE Transfer Policy. In this presentation I will describe the transfer process, policies and procedures in the RIPE NCC service region as well as provide the background information on how we got to this point in time and a glimpse of what will come in the future, such as inter-RIR transfers.
The document provides an overview of the IANA Department within ICANN. It discusses the IANA functions of maintaining unique internet identifiers like domain names, protocol parameters, and internet number resources. It describes the process for reviewing and approving requests to update protocol parameter registries and allocate internet number resources according to established policies. The goal of the IANA Department is to coordinate these systems globally to ensure interoperability of the internet.
Whats so special about 512?, by Geoff Huston [APNIC 38 / APOPS 3]APNIC
The document discusses how the growth of routing tables poses challenges for routers. It summarizes BGP routing statistics that show IPv4 routing tables growing at around 10% per year while IPv6 tables grow faster at 20-40% per year. While overall growth is manageable now, projections estimate IPv4 tables could reach 1 million entries by 2024. Router memory technologies like TCAM have limitations in capacity, cost and power that may be strained by future growth. Memory and processing speeds will also need to improve to sustain higher link speeds, potentially requiring changes to routing protocols or packet formats. In summary, routing table and traffic growth trends pose technical challenges for router scaling that may require innovative solutions if unchecked.
From Policy to Practice: Addressing and Routing in 2014 by Geoff Huston [APRI...APNIC
The document discusses the state of addressing and routing in 2014. It notes that the regional internet registries (RIRs) have run out of IPv4 addresses to allocate, with only AFRINIC still having addresses remaining. As a result, IPv4 address transfers between organizations have increased significantly. IPv6 allocation and routing has continued to grow annually but still makes up a small percentage of overall internet traffic. The average size of routing advertisements and path lengths have remained steady for both IPv4 and IPv6. IPv4 growth is slowing due to address shortages and transition to IPv6, while IPv6 growth is still in the 20-40% range annually.
Presented by Elly Tawhai, APNIC Senior Hostmaster, at the 2017 New Zealand Network Operators Group (NZNOG) meeting was held in Tauranga, New Zealand from 26 to 27 January.
This document discusses RIPE Atlas, a global Internet measurement network. It provides an overview of RIPE Atlas, including its coverage of over 14,000 probes in July 2016. New features are discussed, such as increased measurement limits and improved security. Plans for the future include giving contributors more credits based on their probe's popularity. The document also examines RIPE Atlas' view of Indonesia, showing its single anchor and potential for using the IXP-Jedi tool to analyze paths within the country. The RIPE Atlas community is encouraged to get involved by using, contributing to, or sponsoring the network.
The document discusses the Resource Public Key Infrastructure (RPKI) which aims to address routing incidents caused by IP prefix hijacking and misorigination. It provides an overview of RPKI technical details, components, and deployment status. RPKI uses digital certificates and Route Origin Authorizations (ROAs) to validate that IP prefixes are announced by their legitimate holders and prevent unauthorized route announcements. Major RPKI components include Certificate Authorities (CAs), Relying Parties (RPs), and routers configured to use RPKI data to validate BGP routes.
Vivek Nigam and Pubudu Jayasinghe discuss the Internet in Myanmar, IPv4 depletion and how Members can manage that, deploying IPv6, and routing security.
The document provides an overview of Autonomous System Numbers (ASNs) including how they are distributed and used for interconnection in Indonesia. It notes that Indonesia currently has 530 advertised ASNs and discusses challenges around the adoption of 4-byte ASNs in the country. The document also visualizes Indonesia's position within the global routing ecosystem and provides recommendations around routing security, resource registration, and route aggregation.
Internet Resource Analyst George Odagi gives an update on the implementation of APNIC policy proposal prop-132: RPKI ROAs for unallocated and unassigned APNIC address space.
IPv6 - delegations, deployment and trends, SANOG 29APNIC
Presented by Pubudu Jayasinghe, from APNIC Members Services team, at the 29th South Asian Network Operators Group meeting (SANOG29) held in Islamabad, Pakistan from 23 to 30 January 2017
The document discusses the state of IPv6 adoption and the transition from IPv4 to dual stack networks supporting both IPv4 and IPv6. It finds that while IPv6 adoption is growing, reaching about 18% of internet users, gaps still remain in parts of Asia, Eastern Europe, and Africa. It predicts that in the next few years some providers will stop supporting IPv4 only and offer IPv6 only services, which will leave remaining IPv4 only users, networks and services limited to a smaller portion of the internet. This "crunch time" where the transition is complete will be determined by market forces and could begin within the next 12-24 months.
This document discusses two options for connecting a bank to the internet: single-homing and multi-homing. Single-homing involves connecting to a single internet service provider (ISP) and is cheaper and easier to set up but offers less reliability. Multi-homing connects to multiple ISPs and offers better availability, reliability, and performance through load balancing, but requires more networking skills and expertise. The document recommends most banks start with single-homing and consider upgrading to multi-homing if internet uptime is critical to their operations.
This document provides an overview and schedule for an APNIC Member Gathering in Guangzhou, China in April 2017. The schedule includes presentations on IPv4 exhaustion, IPv4 transfers, IPv6 deployment status, and an introduction to APNIC services. Statistics are presented on IPv4 and IPv6 allocations and deployments in China and globally by year. Key topics covered include the current IPv4 and IPv6 policies of each RIR, IPv4 transfer policies and procedures, and the higher levels of IPv6 deployment seen in some Asia Pacific countries and networks.
An Update on Mobility in Today's Internet, by Geoff Huston.
Presented at the APNIC 40 "Internet – Mobility Nexus: Are We Ready for Real Mobile/Wireless Broadband?" session, Wed 9 Sep 2015.
This document discusses IPv4 transfers and the Resource Public Key Infrastructure (RPKI). It provides information on who can transfer IPv4 addresses between APNIC members and other RIRs, and shows statistics on IPv4 transfers from Singapore. It describes what RPKI is and how it helps secure internet routing by validating routes. It provides instructions on how to create Route Origin Authorization (ROA) objects in MyAPNIC to participate in RPKI and the benefits of maintaining ROAs. Statistics on ROA adoption in several Asian countries are also presented, along with an example of a successful ROA deployment campaign in Bangladesh.
Comcast began deploying IPv6 in 2005 to support future growth as IPv4 addresses were becoming inadequate. They have since made IPv6 the primary protocol for managing their network and services. Over 99% of their devices are now managed using IPv6-only, and around 40% of their internet traffic occurs over IPv6. Their goal is to continue transitioning their entire infrastructure and services to IPv6-only to fully leverage its capabilities.
Andrzej Wolski – I am trainer at RIPE NCC where I develop, manage and deliver trainings mostly about Internet Governance, RIR/LIR aspects of numeric resource distribution and best practices in IP assignment and Internet Routing with focus on RPKI in general. You can find my speaker profile at RIPE NCC website
Topic of Presentation: IPv4 Transfers
Language: Polish
Abstract: On 14 September 2012, the RIPE NCC reached its Last /8. Since then, the supply of unallocated IPv4 space has been limited to a single /22 for each Local Internet Registry. Since then there has been a growing interest in transfers of IPv4 allocations under the RIPE Transfer Policy. In this presentation I will describe the transfer process, policies and procedures in the RIPE NCC service region as well as provide the background information on how we got to this point in time and a glimpse of what will come in the future, such as inter-RIR transfers.
The document provides an overview of the IANA Department within ICANN. It discusses the IANA functions of maintaining unique internet identifiers like domain names, protocol parameters, and internet number resources. It describes the process for reviewing and approving requests to update protocol parameter registries and allocate internet number resources according to established policies. The goal of the IANA Department is to coordinate these systems globally to ensure interoperability of the internet.
Whats so special about 512?, by Geoff Huston [APNIC 38 / APOPS 3]APNIC
The document discusses how the growth of routing tables poses challenges for routers. It summarizes BGP routing statistics that show IPv4 routing tables growing at around 10% per year while IPv6 tables grow faster at 20-40% per year. While overall growth is manageable now, projections estimate IPv4 tables could reach 1 million entries by 2024. Router memory technologies like TCAM have limitations in capacity, cost and power that may be strained by future growth. Memory and processing speeds will also need to improve to sustain higher link speeds, potentially requiring changes to routing protocols or packet formats. In summary, routing table and traffic growth trends pose technical challenges for router scaling that may require innovative solutions if unchecked.
The document discusses trends in internet routing from 2014 as seen through BGP routing data. Some key points:
- IPv4 routing table growth slowed in late 2014, likely due to IPv4 address exhaustion, with the table crossing 512,000 routes. IPv4 growth is projected to continue slowing.
- IPv6 growth was steady at 20-40% per year in 2014, with the IPv6 network projected to match the IPv4 network size in about 16 years at this rate.
- Address reuse is increasing for IPv4, with 50% of new addresses in 2014 being over 1 year old, indicating greater reliance on address conservation methods like NAT.
- Uncertainty around IPv4 exhaustion and IPv6
BGP: Whats so special about the number 512?GeoffHuston
It was reported that parts of the Internet crashed when the number of routes in the Internet's Inter-domain routing table (BGP) exceeded 512K routes. This presentation looks at the growth of the Internet's routing table and how this correlates to the capacity and speed of memory in hardware routers.
The document discusses how the number 512 relates to routing table sizes on Cisco and Brocade networking equipment. It analyzes growth trends in IPv4 and IPv6 BGP routing tables based on historical data. While absolute sizes are increasing, the annual growth rates have slowed slightly. Projections indicate routing tables could continue growing within the capabilities of current router technologies for the foreseeable future if trends continue.
The document provides an overview of IP address management and the rationale for IPv6. It discusses the history of IP address allocation, the role of regional internet registries (RIRs) in allocating addresses, and IPv6 policies and procedures. Key aspects of IPv6 include a vastly larger address space, simpler headers, and stateless autoconfiguration. IPv6 policies aim to make large amounts of address space easily available while ensuring efficient utilization.
This document discusses the exhaustion of IPv4 addresses and the growth of IPv6 usage. Some key points:
- The regional internet registries have exhausted their free pools of IPv4 addresses, with just AFRINIC remaining. IPv4 address transfers in the aftermarket have increased dramatically to meet ongoing demand.
- IPv6 allocation and routing table growth has increased steadily over time but still lags IPv4. IPv6 usage varies globally but has doubled in 2015, now reaching around 25% usage in some countries.
- Despite IPv4 exhaustion, the growth of new routing table entries and more specific routes has continued apace, increasing the routing table size. The average routing advertisement is getting smaller.
With the exhaustion of global IPv4 addresses, all operators cannot apply to the IPv4 address pool of the public network. All countries have adopted IPv6 as the direction of the next-generation Internet, and China has also clearly accelerated the strategy of building IPv6-based next-generation Internet.
IPv4 addresses are nearly exhausted while IPv6 provides a vast address space to support continued Internet growth. While IPv4 and IPv6 can coexist, IPv6 adoption is needed as the only sustainable solution. Global metrics show increasing IPv6 deployment over time through allocations, routing entries, and user access, though challenges remain around applications, skills, and justification. RIRs and IETF are committed to IPv6 to maintain the openness and development of the Internet.
This document provides a summary of internet number resource statistics as of June 30, 2018 from the five Regional Internet Registries (RIRs): AFRINIC, APNIC, ARIN, LACNIC, and RIPE NCC. It includes statistics on the distribution of IPv4 and IPv6 address space and autonomous system numbers (ASNs), as well as the available and allocated resources held by each RIR over time.
PhNOG 2020: Securing your resources with RPKI and IRTAPNIC
APNIC Senior Internet Resource Analyst Anna Mulingbayan gives an overview of how to secure your resources with RPKI and IRT at PhNOG 2020 in Manila, Philippines, on 24 February 2020.
RPKI (Resource Public Key Infrastructure) is a framework that helps secure Internet routing by validating route origins and paths. It works by (1) having certificate authorities like regional internet registries issue certificates binding IP addresses and ASNs, (2) having address holders issue Route Origin Authorizations specifying which ASNs are authorized to originate which address ranges, and (3) having routers perform validation of routes based on this published data. While adoption is still in early stages, RPKI deployment is gradually increasing and provides benefits like preventing route hijacking and misorigination.
The document discusses the widespread use of Network Address Translation (NAT) devices on today's Internet. Some key points:
- NATs allow sharing of public IPv4 addresses by mapping private internal IP addresses to public addresses, enabling a large number of devices to connect using a limited number of IP addresses.
- NATs have become ubiquitous due to their ability to extend the lifetime of IPv4 addresses and enable incremental deployment without coordination. They isolate private networks from each other.
- While NATs were initially criticized for violating the original IP architecture, they have enabled the continued growth of the Internet by extending the available IPv4 address space. The Internet now relies on widespread use of NATs.
- Even IPv
Over 23% of allocated IPv4 addresses in APNIC's registry are unadvertised in BGP routing tables. Approximately 110 million of APNIC's 880 million IPv4 addresses are unadvertised. Around 30% of the unadvertised addresses were allocated by APNIC in the three years before the IPv4 pool was exhausted in 2011, and 10% are from recent address transfers that have not yet been advertised. The remaining 30% are pre-APNIC legacy allocations from organizations like AUNIC and the New Zealand registry.
The document provides an overview of Internet Protocol (IP) addressing and the role of the American Registry for Internet Numbers (ARIN) and other Regional Internet Registries (RIRs). It discusses IP addresses and autonomous system numbers, the domain name system, IP address allocation and management, and the purpose of WHOIS directories. ARIN is responsible for managing IP address space and ASNs in its service region, which includes Canada, the US, and many Caribbean islands.
Review of IPv4 and IPv6 and various implementation methods of IPv6IRJET Journal
This document compares IPv4 and IPv6 and reviews various implementation methods of IPv6. It finds that while IPv6 provides many advantages over IPv4 like a vastly larger address space and improved security features, full deployment of IPv6 requires complete network participation which has hindered adoption. Various transition techniques allow IPv6 networks to communicate over existing IPv4 infrastructure to facilitate gradual deployment, including tunneling which encapsulates IPv6 packets in IPv4 packets to traverse IPv4 networks. Dual stack backbones that support both protocols and protocol translation mechanisms also help transition. Global IPv6 deployment continues to progress with over 30% user support currently.
- The document provides guidance on configuring BGP and receiving prefixes from different sources such as customers, peers, and upstream providers.
- It emphasizes the importance of proper filtering to only accept prefixes that the source is authorized to announce. This includes checking assignments in regional internet registries.
- Guidelines are given for Cisco IOS configurations to implement the recommended filtering practices for each source type.
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.
TechWiseTV Workshop: Segment Routing for the DatacenterRobb Boyd
(This was a Live Webinar on July 21, 2016 at 10:00 am Pacific Time / 1:00 pm Eastern Time)
Watch the Replay at: bit.ly/29Mw58Q
Catch the original TV episode or any other topics at www.techwisetv.com
Description:
Networks are moving toward simplification, increased operational efficiency, and programmability using technologies such as software-defined networking. Cisco continues to demonstrate innovation by introducing the concept of segment routing in the data center, making the network more intelligent and adaptive to the applications running on top of it. Segment routing delivers application-optimized network transport. Encoding the path information directly at the source (that is, either at the virtual switch or at the top of rack) and using per-app policies, segment routing puts control in the hands of the network operators by empowering them to create secure, adaptive, and optimal paths based on the requirements of the application itself.
Please join us in the session to learn how Cisco is helping organizations increase network efficiency by allocating resources on demand and optimizing the network to better support business-critical applications, all while preserving security.
Agenda
Topics to discuss include:
- Introducing segment routing
- Why the need for application-optimized transport
- Features and benefits of segment routing
- Differences between segment routing and MPLS transport
- Relevance of segment routing in the data center
- Use cases and applicability of segment routing
- Summary and conclusion
APNIC Foundation, presented by Ellisha Heppner at the PNG DNS Forum 2024APNIC
Ellisha Heppner, Grant Management Lead, presented an update on APNIC Foundation to the PNG DNS Forum held from 6 to 10 May, 2024 in Port Moresby, Papua New Guinea.
Registry Data Accuracy Improvements, presented by Chimi Dorji at SANOG 41 / I...APNIC
Chimi Dorji, Internet Resource Analyst at APNIC, presented on Registry Data Accuracy Improvements at SANOG 41 jointly held with INNOG 7 in Mumbai, India from 25 to 30 April 2024.
APNIC Policy Roundup, presented by Sunny Chendi at the 5th ICANN APAC-TWNIC E...APNIC
Sunny Chendi, Senior Advisor, Membership and Policy at APNIC, presents 'APNIC Policy Roundup' at the 5th ICANN APAC-TWNIC Engagement Forum and 41st TWNIC OPM in Taipei, Taiwan from 23 to 24 April.
DDoS In Oceania and the Pacific, presented by Dave Phelan at NZNOG 2024APNIC
Dave Phelan, Senior Network Analyst/Technical Trainer at APNIC, presents 'DDoS In Oceania and the Pacific' at NZNOG 2024 held in Nelson, New Zealand from 8 to 12 April 2024.
'Future Evolution of the Internet' delivered by Geoff Huston at Everything Op...APNIC
Geoff Huston, Chief Scientist at APNIC deliver keynote presentation on the 'Future Evolution of the Internet' at the Everything Open 2024 conference in Gladstone, Australia from 16 to 18 April 2024.
IP addressing and IPv6, presented by Paul Wilson at IETF 119APNIC
Paul Wilson, Director General of APNIC delivers a presentation on IP addressing and IPv6 to the Policymakers Program during IETF 119 in Brisbane Australia from 16 to 22 March 2024.
draft-harrison-sidrops-manifest-number-01, presented at IETF 119APNIC
Tom Harrison, Product and Delivery Manager at APNIC presents at the Registration Protocols Extensions working group during IETF 119 in Brisbane, Australia from 16-22 March 2024
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...APNIC
Che-Hoo Cheng, Senior Director, Development at APNIC presents on the "Benefits of doing Internet peering and running an Internet Exchange (IX)" at the Communications Regulatory Commission of Mongolia's IPv6, IXP, Datacenter - Policy and Regulation International Trends Forum in Ulaanbaatar, Mongolia on 7 March 2024
APNIC Update and RIR Policies for ccTLDs, presented at APTLD 85APNIC
APNIC Senior Advisor, Membership and Policy, Sunny Chendi presented on APNIC updates and RIR Policies for ccTLDs at APTLD 85 in Goa, India from 19-22 February 2024.
Lao Digital Week 2024: It's time to deploy IPv6APNIC
APNIC Development Director Che-Hoo Cheng presents on the importance of deploying IPv6 at the Lao Digital Week 2024, held in Vientiane, Lao PDR from 10 to 14 January 2024.
HijackLoader Evolution: Interactive Process HollowingDonato Onofri
CrowdStrike researchers have identified a HijackLoader (aka IDAT Loader) sample that employs sophisticated evasion techniques to enhance the complexity of the threat. HijackLoader, an increasingly popular tool among adversaries for deploying additional payloads and tooling, continues to evolve as its developers experiment and enhance its capabilities.
In their analysis of a recent HijackLoader sample, CrowdStrike researchers discovered new techniques designed to increase the defense evasion capabilities of the loader. The malware developer used a standard process hollowing technique coupled with an additional trigger that was activated by the parent process writing to a pipe. This new approach, called "Interactive Process Hollowing", has the potential to make defense evasion stealthier.
2. 22
Through the Routing Lens …
There are very few ways to assemble a
single view of the entire Internet
The lens of routing is one of the ways in
which information relating to the entire
reachable Internet is bought together
Even so, its not a perfect lens, but it can
provide some useful insights about the
entire scope of the Internet
3. 33
1994: Introduction of CIDR
2001: The Great Internet Boom and Bust
2005: Consumer Market
2011: Address Exhaustion
25 Years of Routing the Internet
This is a view pulled together from
each of the routing peers of
Route-Views
6. 66
Routing Indicators for IPv4
Routing prefixes – growing by
some 52,000 prefixes per year
AS Numbers– growing by some
3,400 prefixes per year
7. 77
Routing Indicators for IPv4
More Specifics are still taking up
slightly more than one half of
the routing table
But the average size of a
routing advertisement continues
to shrink
8. 88
Routing Indicators for IPv4
Address Exhaustion is now
visible in the extent of
advertised address space
The “shape” of inter-AS
interconnection appears to be
relatively steady
9. 99
AS Adjacencies (AS131072)
4,144 AS6939 HURRICANE - Hurricane Electric, Inc., US
4.032 AS3356 LEVEL3 - Level 3 Communications, Inc., US
3,702 AS174 COGENT-174 - Cogent Communications, US
1,724 AS6461 ZAYO Bandwidth, US
1,646 AS7018 ATT-INTERNET4 - AT&T Services, Inc., US
1,618 AS3549 LVLT – Level 3 Parent, US
1,428 AS3257 GTT-Backbone, DE
1,377 AS2914 NTT America, US
1,208 AS209 CENTURYLINK, US
957 AS701 Verizon Business, US
51,613 out of 63,080 ASNs have 1 or 2 AS Adjacencies (82%)
1,803 ASNs have 10 or more adjacencies
9 ASNs have >1,000 adjacencies
Most networks are stub AS’s A small number of major connectors
10. 1010
What happened in 2018 in V4?
Routing Business as usual – despite IPv4 address exhaustion!
– From the look of the growth plots, its business as usual, despite the increasing
pressures on IPv4 address availability
– The number of entries in the IPv4 default-free zone reached 750,000 by the
end of 2018
– The pace of growth of the routing table is still relatively constant at ~52,000
new entries and 3,400 new AS’s per year
• IPv4 address exhaustion is not changing this!
• Instead, we appear to be advertising shorter prefixes into the routing system
11. 1111
What about IPv4 Address Exhaustion?
ARIN – no free pool left
AFRINIC – May 2020
LACNIC – November 2019
APNIC – November 2020
RIPE NCC – January 2020
RIR Address Pool runout
projections (as of April 2019):
12. 1212
Post-Exhaustion Routing Growth
• What’s driving this post-exhaustion growth?
– Transfers?
– Last /8 policies in RIPE and APNIC?
– Leasing and address recovery?
13. 1313
Advertised Address “Age”
80% of all new addresses announced in 2010
were allocated or assigned within the past 12
months
2% of all new addresses announced in 2010
were >= 20 years ‘old’ (legacy)
2010
14. 1414
Advertised Address “Age”
20% of all new addresses announced in 2018 were
allocated or assigned within the past 12 months
48% of all new addresses announced in
2018 were >= 20 years ‘old’ (legacy)
2018
16. 1616
2000 – 2018: Unadvertised Addresses
Total volume of
“reclaimed” addresses
17. 1717
2018: Assigned vs Recovered
Change in Advertised Addresses
Change in the Unadvertised Address Pool
RIR Allocations
“draw down”
18. 1818
V4 in 2018
• The equivalent of 1.4 /8s were removed from the routing table across 2018
• Approximately 0.86 /8s were assigned by RIRs in 2015
– 0.37 /8’s assigned by Afrinic
– 0.28 /8s assigned by the RIPE NCC (last /8 allocations)
– 0.10 /8s were assigned by APNIC (last /8 allocations)
• And a net of 2.1 /8’s were added to the pool of unadvertised addresses
In 2018 we saw legacy blocks transferring away from ISPs / end user sites
and heading towards cloud SPs.
21. 2121
Routing Indicators for IPv6
Routing prefixes – growing by
some 15,000 prefixes per year
AS Numbers– growing by some
2,000 ASNs per year (which is
60% the V4 growth)
22. 2222
Routing Indicators for IPv6
More Specifics now take up more
than one third of the routing
table
The average size of a routing
advertisement is getting smaller
23. 2323
Routing Indicators for IPv6
Advertised Address span is
growing at an exponential rate
The “shape” of inter-AS
interconnection in IPv6 is rising
slightly. Local connections appear
to be replacing overlay trunk
transits
24. 2424
AS Adjacencies (AS131072)
13,095 out of 16,465 ASNs have 1 or 2 AS Adjacencies (79%)
573 ASNs have 10 or more adjacencies
2 ASNs have >1,000 adjacencies
4,295 AS6939 HURRICANE - Hurricane Electric, Inc., US
1,049 AS3356 LEVEL3 - Level 3 Communications, Inc., US
749 AS174 COGENT-174 - Cogent Communications, US
719 AS2915 NTT America, US
632 AS1299 Telia Carrier, SE
25. 2525
V6 in 2018
• Overall IPv6 Internet growth in terms of BGP is still
increasing, and is currently at some 15,000 route entries
p.a.
27. 2727
BGP Size Projections
How quickly is the routing space growing?
What are the projections of future BGP FIB size?
28. 2828
V4 - Daily Growth Rates
Growth in the V4 network appears to be constant at a long term average of 140
additional routes per day, or some 52,000 additional routes per year
32. 3232
BGP Table Growth
The absolute size of the IPv6 routing table is growing much faster
than the IPv4 table
IPv6 will require the same memory size in around 5 years time,
given that each IPv6 entry is 4 times the memory size of an IPv4
entry
As long as we are prepared to live within the technical constraints
of the current routing paradigm, the Internet’s use of BGP will
continue to be viable for some time yet
36. 3636
Updates in IPv4 BGP
Still no great level of concern …
• The number of updates per instability event and the time to
converge has been relatively constant
• Likely contributors to this outcome are the damping effect of
widespread use of the MRAI interval by eBGP speakers, and the
compressed topology factor, as seen in the relatively constant
AS Path Length
39. 3939
Routing Futures
• There is little in the way of scaling pressure from BGP as a routing
protocol – the relatively compressed topology and stability of the
infrastructure links tend to ensure that BGP remains effective in routing
the internet
• The issues of FIB size, line speeds and equipment cost of line cards
represent a more significant issue for hardware suppliers – we can
expect cheaper line cards to to use far smaller LRU cache local FIBs in
the high speed switches and push less used routes to a slower / cheaper
lookup path. This approach may also become common in very high
speed line cards
40. 4040
Some Practical Suggestions
• Understand your hardware’s high speed FIB capacity in the
default-free parts of your network
• Review your IPv4 / IPv6 portioning - a dual-stack eBGP router will
need 900,000 IPv4 slots and 110,000 IPv6 slots for a full eBGP
routing table in line cards over the coming 24 months if they are
using a full FIB load
• Judicious use of default routes in your internal network may allow
you drop this requirement significantly