IPv4 Address Lifetime Expectancy Revisited Geoff Huston March 2004 Research activity supported by APNIC The Regional Internet Registries s do not make.

Slides:



Advertisements
Similar presentations
Kuala Lumpur February 2004 APNIC 17 Kuala Lumpur February 2004 APNIC 17 IPv4 /8 Address Space Status.
Advertisements

Copyright © 2007 JPNIC All Rights Reserved. IPv4 Countdown Policy Proposal (LAC ) Toshiyuki Hosaka Working Group on the policy for IPv4 address.
IPv4 Address Lifetime Presented by Paul Wilson, APNIC Research activity conducted by Geoff Huston and supported by APNIC.
Axel Pawlik. LACNIC VI, March 2004, Montevideo. An RIR in 2010 History, Continuity and Future presented by: Axel Pawlik.
Allocation vs Announcement A comparison of RIR IPv4 Allocation Records with Global Routing Announcements Geoff Huston February 2004 (Supported by APNIC)
Geoff Huston, APNIC March 2006 APRICOT 2006 IPv4 Numerology.
IPv4 Address Lifetime Expectancy Revisited Geoff Huston September 2003 Presentation to the RIPE 46 Plenary Research activity supported by APNIC The Regional.
ARIN Public Policy Meeting
Measuring IPv6 Deployment Geoff Huston George Michaelson
IPv4 Address Transfer proposal APNIC prop-050-v002 Geoff Huston.
BGP AS Number Exhaustion Geoff Huston Research activity supported by APNIC March 2003.
Routing Table Status Report Geoff Huston February 2005 APNIC.
Routing Table Status Report November 2005 Geoff Huston APNIC.
IPv4 Consumption Update
IPv4 Unallocated Address Space Exhaustion Geoff Huston Chief Scientist APNIC APNIC 24, September 2007.
BGP Status Update Geoff Huston September What Happening (AS4637) Date.
December 2011 Internet Number Resource Report. December 2011 Internet Number Resource Report INTERNET NUMBER RESOURCE STATUS REPORT As of 30 December.
March 2011 Internet Number Resource Report. INTERNET NUMBER RESOURCE STATUS REPORT As of 31 March 2011 March 2011.
June 2008 Internet Number Resource Report. INTERNET NUMBER RESOURCE STATUS REPORT As of 30 June 2008.
March 2008 Internet Number Resources Status Report.
March 2010 Internet Number Resource Report. INTERNET NUMBER RESOURCE STATUS REPORT As of 31 March 2010 March 2010.
Internet Number Resource Status Report As of 31 March 2006.
Internet Number Resource Status Report As of 31 March 2005.
Spearheading Internet technology and policy development in the African Region IPv4 exhaustion The Situation in Africa AfriNIC-9 Mauritius, 27th November.
A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E APNIC Open Policy Meeting Address Policy (Procedures) SIG 1 March 2001.
IPv4 Addresses. Internet Protocol: Which version? There are currently two versions of the Internet Protocol in use for the Internet IPv4 (IP Version 4)
March 2014 Internet Number Resource Report. March 2014 Internet Number Resource Report INTERNET NUMBER RESOURCE STATUS REPORT As of 31 March 2014 Prepared.
1 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.
IPv4 Address Lifetime Expectancy Geoff Huston, APNIC 31 October 2005 Australian IPv6 Summit.
IPv4 Consumption Status Geoff Huston. Status of IPv4 today.
Allocations vs Announcements A comparison of RIR IPv4 Allocation Records with Global Routing Announcements Geoff Huston May 2004 (Activity supported by.
IPv4 Address Lifetime Expectancy Geoff Huston Research activity supported by APNIC The Regional Internet Registries s do not make forecasts or predictions.
Overview of policy proposals Policy SIG 27 February 2008 APNIC 25, Taipei.
IPv4 Addresses. Internet Protocol: Which version? There are currently two versions of the Internet Protocol in use for the Internet IPv4 (IP Version 4)
1 IPv6 Address Space Management Report of IPv6 Registry Simulation Policy SIG 1 Sept 2004 APNIC18, Nadi, Fiji Geoff Huston.
IPv4 Address Lifetime Presented by Nurani Nimpuno, APNIC Research activity conducted by Geoff Huston and supported by APNIC.
Internet Addressing and the RIR system (part 2) 12 February 2004 Phnom Penh, Cambodia Paul Wilson, APNIC.
APNIC Depletion of the IPv4 free address pool – IPv6 deployment The day after!! 8 August 2008 Queenstown, New Zealand In conjunction with APAN Cecil Goldstein,
IPv4 Unallocated Address Space Exhaustion Geoff Huston Chief Scientist APNIC November 2007.
IPv4 Address Lifetime Expectancy Revisited - Revisited Geoff Huston November 2003 Presentation to the IEPG Research activity supported by APNIC The Regional.
1 AS Consumption Patterns Geoff Huston APNIC May 2005.
Routing Table Status Report Geoff Huston November 2004 APNIC.
IPv4 Address Lifetime Expectancy Geoff Huston, APNIC 26 October 2005 ARIN XVI.
1 IPv4 Address Lifetime Presented by Paul Wilson, APNIC Research activity conducted by Geoff Huston and supported by APNIC.
AS Numbers NANOG 35 Geoff Huston APNIC. Current AS Number Status.
IPv4 Address Lifetime SANOG IV Presented by Nurani Nimpuno, APNIC Research activity conducted by Geoff Huston and supported by APNIC.
The Internet will switch versions of IP. Projection based on 3 years.
IPv4. The End of the World is nigh (er) ! Geoff Huston Chief Scientist APNIC.
Routing Table Status Report Geoff Huston August 2004 APNIC.
Tracking the Internet’s BGP Table Geoff Huston Telstra December 2000.
1 Transition to IPv6: Should ISPs consider it now? PITA 11th AGM Meeting 2007 Tahiti, French Polynesia 24 April 2007.
Policy SIG Report APNIC AGM Friday 29 August 2008 Christchurch, New Zealand 1.
IP Address Management The RIR System Nurani Nimpuno APNIC.
Routing 2015 Scaling BGP Geoff Huston APNIC May 2016.
The Status of APNIC’s IPv4 Resources: Exhaustion & Transfers
Addressing 2016 Geoff Huston APNIC.
René Wilhelm & Henk Uijterwaal RIPE NCC APNIC21, 18 September 2018
IPv4.
IP Addresses in 2016 Geoff Huston APNIC.
Routing and Addressing in 2017
IPv6 Address Space Management Report of IPv6 Registry Simulation
Geoff Huston September 2002
IPv6 Address Space Management Report of IPv6 Registry Simulation
RIPE October 2005 Geoff Huston APNIC
IPv4 Address Lifetime Expectancy
IPv4 Address Lifetime Expectancy Revisited
2005 – A BGP Year in Review February 2006 Geoff Huston
4-Byte AS number registry Policy Proposal [LACNIC Proposal ]
Overview of policy proposals
IPv4 Address Lifetime Expectancy
Presentation transcript:

IPv4 Address Lifetime Expectancy Revisited Geoff Huston March 2004 Research activity supported by APNIC The Regional Internet Registries s do not make forecasts or predictions about number resource lifetimes. The RIRs provide statistics of what has been allocated. The following presentation is a personal contribution based on extrapolation of RIR allocation data.

IPv4 Address Lifetime Expectancy This was an IETF activity starting as part of the Routing and Addressing (ROAD) activity in the early 1990s The objective was to understand the rate of allocation of IPv4 addresses and make some predictions as to the date of eventual exhaustion of the unallocated address pool At the time the prediction was made from analysis of IANA allocation data that the pool of IPv4 addresses would be exhausted around This is a re-visiting of this activity with consideration of additional data derived from the characteristics of the BGP routing table

The IPv4 Address Space A 32 bit field spanning some 4.4B entries The IETF, through standards actions, has determined some space to be used for global unicast, some for multicast and some held in reserve IANA has allocated some unicast space to the RIRs for further allocation and assignment, assigned some space directly, and reserved some space for particular purposes

The IPv4 Top Level Structure Breakdown of IPv4 address Space by /8 block equivalents Reserved – 7.8% Multicast – 6.2% Unicast – 88%

Modeling the Process A number of views can be used to make forward projections: The rate at which IPv4 number blocks are passed from IANA to the RIRs The rate at which RIRs undertake assignments of IPv4 address blocks to LIRs and end users The growth of the number of announced addresses in the BGP routing table

Data Sets IANA IPv4 Address Registry Allocation of /8 blocks to RIRs and others RIR Stats files Allocation of blocks to LIRs BGP Routing table Amount of address space advertised as reachable

IANA Allocations The IPv4 address registry records the date of each /8 allocation undertaken by the IANA This data has some inconsistencies, but is stable enough to allow some form of projection

IANA Registry Comments The allocation dates for those address blocks prior to 1995 are inaccurate The earliest date is 1991, and a large block has been recorded as allocated in This is inconsistent with dates recorded in the RIR stats files, which record allocations back to 1983 It would appear that there was a revision of the IANA registry in the period 1991 – 1993, and the IANA recorded dates are the revision dates Useable dates appear to start from allocations from 1995 onwards

IANA – Current Status Reserved – 7.8% Multicast – 6.2% IANA Pool – 33.6% Allocated – 52.4%

IANA Allocations IANA Registry – Allocation History

IANA Projections Exponential Growth Projection of IANA Allocations

IANA Projections This projection of 2019 for IANA address pool exhaustion is very uncertain because of: Sensitivity of allocation rate to prevailing RIR assignment policies Sensitivity to any significant uptake up of new applications that require end-to-end IPv4 addressing vs use of NATs

RIR Allocations The RIR stats files records the date of each allocation to an LIR, together with the allocation details

RIR Allocations – Current Status Reserved – 7.8% Multicast – 6.2% IANA Pool – 33.6% RIR Pool – 5.0% Assigned – 47.3%

RIR Allocations /8

RIR Allocations RIR Assignment Data

RIR Projections Exponential Growth Projection for RIR Assignment Data

RIR Projections This projections of 2024 for 221 /8s has the same levels of uncertainty as noted for the IANA projections

BGP Routing Table The BGP routing table spans a set of advertised addresses A similar analysis of usage and projection can be undertaken on this date

The Route Views view

The AS1221 view

BGP Routing Table - Status Reserved – 7.8% Multicast – 6.2% IANA Pool – 33.6% Unadvertised – 17.4% Advertised – 29.9%

BGP Address Allocations /8

Age of Unannounced Blocks

Age of Unannounced Blocks (cumulative)

BGP Address Span

BGP Projections

This projection of 2027 uses a 3 year data baseline to obtain the projection This is much shorter baseline than the IANA and RIR projections There are, again, considerable uncertainties associated with this projection

Another look at that BGP data:… Comments received about this projection have prompted me to review the BGP address data and see if a more detailed analysis of the BGP data modifies this model It appears to be the case that there is a different view that can be formed from the data:……

Another look at that BGP data:… Firstly, heres the raw data – hourly measurements over 3 years.

Another look at that BGP data:…

The most obvious noise comes from flaps in /8 advertisements. The first step was to remove this noise by recalculating the address data using a fixed number of /8 advertisements The value of 19 was used to select one of the tracks in the data

Another look at that BGP data:…

This is still noisy, but there is no systematic method of raw data grooming that can efficiently reduce this noise. At this stage I use gradient smoothing, limiting the absolute values of the first order differential of the data (gradient limiting) to smooth the data

Another look at that BGP data:…

Its now possible to apply a best fit function to the data. A linear model appears to be the most appropriate fit:…

Another look at that BGP data:…

An inspection of the first order differential of the data reveals why the linear fit is considered to be the most appropriate for the available data. While the period through 2000 shows a pattern of an increasing first order differential that is consistent with an exponential growth model, subsequent data reveals an oscillating value for the differential, and a linear model provides a constant first order differential This linear model appears to be the most conservative fit to the data, although the most recent data shows some discontinuities in the rate

Another look at that BGP data:…

Combining the Data

Recent Data

Holding Pools: RIR Pool and Unannounced Space

Modelling the Process Assume that the RIR efficiency in allocation slowly declines, so that the amount of RIR- held space increases over time Assume that the Unannounced space shrinks at the same rate as shown over the past3 years Assume an exponential best fit model to the announced address space projections and base RIR and IANA pools from the announced address space projections, using the above 2 assumptions

Modelling the Process Projections IANA Pool Exhaustion 2016 RIR Pool Exhaustion 2018

Modelling the Process Assume that the RIR efficiency in allocation slowly declines, then the amount of RIR-held space increases over time Assume that the Unannounced space shrinks at the same rate as shown over the past3 years Assume linear best fit model to the announced address space projections and base RIR and IANA pools from the announced address space projections

Modelling the Process Projections IANA Pool Exhaustion 2026 RIR Pool Exhaustion 2031

Observations Extrapolation of current allocation practices and current demand models using an exponential growth model derived from a 2000 – 2004 data would see RIR IPv4 space allocations being made for the next 2 decades, with the unallocated draw pool lasting until The use linear growth model sees RIR IPv4 space allocations being made for the next 3 decades, with the unallocated draw pool lasting until 2030 – 2037 Re-introducing the held unannounced space into the routing system over the coming years would extend this point by a further decade, prolonging the useable lifetime of the unallocated draw pool until 2038 – 2045 This is just a model – reality tends to express its own will!

Questions Will the routing table continue to reflect allocation rates (i.e. all allocated addresses are BGP advertised)? Is the model of the unadvertised pools and RIR holding pools appropriate? Externalities: What are the underlying growth drivers and how are these best modeled? What forms of disruptive events would alter this model? What would be the extent of the disruption (order of size of the disruptive address demand)?