Nurani Nimpuno On behalf of Geoff Huston APNIC 25 May 2006

Slides:



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

Axel Pawlik. LACNIC VI, March 2004, Montevideo. An RIR in 2010 History, Continuity and Future presented by: Axel Pawlik.
IPv4 Address Lifetime Expectancy Revisited Geoff Huston September 2003 Presentation to the RIPE 46 Plenary Research activity supported by APNIC The Regional.
BGP AS Number Exhaustion Geoff Huston Research activity supported by APNIC March 2003.
4-Byte AS number registry Policy Proposal [LACNIC Proposal ] Geoff Huston APNIC 25 May.
Experimental Internet Resource Allocations Philip Smith, Geoff Huston September 2002.
IPv4 Unallocated Address Space Exhaustion Geoff Huston Chief Scientist APNIC APNIC 24, September 2007.
1 Muhammed Rudman
IPv4 Depletion IPv6 Adoption 3 February /8s Remaining.
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 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.
IPv4 Depletion and IPv6 Adoption Today Community Use Slide Deck Courtesy of ARIN May 2014.
IPv4 Address Exhaustion: A Progress Report Geoff Huston Chief Scientist APNIC.
IPv6 Unique Local Addresses Update on IETF Activity Policy SIG Feb 2004 APNIC19 Geoff Huston.
IPv4 Address Lifetime Expectancy Geoff Huston Research activity supported by APNIC The Regional Internet Registries s do not make forecasts or predictions.
2009-3: Allocation of IPv4 Blocks to Regional Internet Registries.
Overview of policy proposals Policy SIG 27 February 2008 APNIC 25, Taipei.
Proposal of “Time-Limited” IPv4 Address Allocation Policy Project leader : Jun Murai Project officiers: –Hiroshi Esaki –Akira Kato –Osamu Nakamura –Masaki.
IPv4 Addresses. Internet Protocol: Which version? There are currently two versions of the Internet Protocol in use for the Internet IPv4 (IP Version 4)
IPv4 Address Lifetime Presented by Nurani Nimpuno, APNIC Research activity conducted by Geoff Huston and supported by 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.
Policy Experience Report Leslie Nobile. Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness Identify areas where new or modified.
ARIN Section 4.10 Austerity Policy Update.
1 APNIC Update LACNIC IX Guatemala city, Guatemala May 2006 Nurani Nimpuno.
Policy Implementation & Experience Report Leslie Nobile.
1 AS Consumption Patterns Geoff Huston APNIC May 2005.
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.
4 Byte AS Number Update Geoff Huston August 2008.
IPv4 Address Lifetime SANOG IV Presented by Nurani Nimpuno, APNIC Research activity conducted by Geoff Huston and supported by APNIC.
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 Emerging Registry Criteria ASO General Assembly Budapest, 19 May 2000.
Current Policy Topics Emilio Madaio RIPE NCC RIPE November 2010, Rome.
1 Transition to IPv6: Should ISPs consider it now? PITA 11th AGM Meeting 2007 Tahiti, French Polynesia 24 April 2007.
Advisory Council Shepherds: David Farmer & Chris Grundemann Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA.
Policy SIG Report APNIC AGM Friday 29 August 2008 Christchurch, New Zealand 1.
RIPE Network Coordination Centre October Andrew de la Haye 32-bit ASN Adjustment to Global Policy Proposal Stacy Hughes Andrew.
IPv6 Adoption Status and Scheduling for Sustainable Development 24 July 2012 Nate Davis Chief Operating Officer, ARIN.
AS Numbers - Again Geoff Huston APNIC October 2009
IPv4 shortage and CERN 15 January 2013
2002網際網路趨勢研討會IPv6 Tutorial
A proposal to deprecate ip6.int reverse DNS service in APNIC
René Wilhelm & Henk Uijterwaal RIPE NCC APNIC21, 18 September 2018
IPv4 Addresses.
Regional Internet Registries
A Coordinated Proposal Regional Internet Registries
IP Addresses in 2016 Geoff Huston APNIC.
Geoff Huston APNIC August 2009
The IPv4 Consumption Model
APNIC IPv6 pools and delegation practice
IPv6 Address Space Management Report of IPv6 Registry Simulation
A Proposal for IPv4 Essential Infrastructure
IPv6 Unique Local Addresses Report on IETF Activity
An Update on BGP Support for 4-byte ASN
IPv6 Address Space Management Report of IPv6 Registry Simulation
RIPE October 2005 Geoff Huston APNIC
IPv4 Address Lifetime Expectancy
IPv4 Address Lifetime Expectancy Revisited
News from APNIC ARIN XXII 16 October 2008.
Policy SIG Thursday 26 February Manila, Philippines
4-Byte AS number registry Policy Proposal [LACNIC Proposal ]
Prop-078-V002: IPv6 deployment criteria for IPv4 final /8 delegations
Overview of policy proposals
Experimental Internet Resource Allocations
Overview of policy proposals
IPv4 Address Lifetime Expectancy
Design Expectations vs. Deployment Reality in Protocol Development
4-Byte AS Numbers The view from the old BGP world
IPv6 Unique Local Addresses Update on IETF Activity
prop-081-v001: Eligibility for assignments from the final /8
Presentation transcript:

Nurani Nimpuno On behalf of Geoff Huston APNIC 25 May 2006 4-Byte AS number registry Policy Proposal [LACNIC Proposal 2006-04] http://lacnic.net/documentos/lacnicix/LAC-2006-04-EN.pdf Nurani Nimpuno On behalf of Geoff Huston APNIC 25 May 2006 The references to the LACNIC Policy Proposal number and the text of the proposal are included here.

32-bit AS number registry A policy proposal for LACNIC to assist in the general transition to the use of 32 bit AS numbers Essential attributes of this policy: Ease of transitional arrangements Predictability of registry actions Clear dates in terms of registry actions As the Internet continues to grow the ability to deploy new versions of infrastructure protocols gets harder and more consideration regarding pre-deployment actions needs to be taken into account. This policy proposal attempts to create some predictable and clear dates for the transition from 16 bit to 32 bit AS numbers. This is to allow software vendors, network operators, trainers, documenters, users and of course registries sufficient time to understand what aspects of their environment needs to change in order to support 32 bit AS numbers.

Why Now and not Later? Triggered by the completion of the IETF 4-Byte AS Number proposal* to Proposed Standard publication and predictions of effective exhaustion of the 16-bit AS number pool** Proposes to provide a 3 year period of transition to support piecemeal testing and deployment of revised BGP versions that support 32-bit AS numbers This proposal is being introduced now to allow a minimum of a three year period to achieve an orderly transition to the use of 32 bit AS numbers. This synchronises with a forecast of 16 bit AS number exhaustion of October 2010 (http://www.potaroo.net/tools/asns). It also coincodes with the completion of the definitional work on the IETF standards to support 32 bit AS Numbers. Currently ~ 30% still available for assignment (out of practically available pool of the 16-bit number pool) (Henk Uitervaal has done similar work in this area, taking into consideration possible future reclamation by the RIRs, which buys us a few years.) * draft-ietf-idr-as4bytes-12.txt ** variously estimated to occur between 2010 and 2012

Assumptions The IANA actions as specified in the IETF 4-Byte AS Number document will be completed by 1 January 2007 LACNIC will have ensured that its data systems are 32-bit ‘clean’ for the AS Number registry by 1 January 2007 The assumptions behind this policy proposal are listed here.

The ASN Registry Proposal Proposed AS assignment transition in 3 phases: Commencing on 1 January 2007 the registry will process applications for 32-bit only AS numbers1 upon specific request. 16-bit only AS numbers2 will be assigned by default Commencing on 1 January 2009 the registry will assign 32-bit only AS numbers1 by default. 16-bit only AS numbers will be assigned upon specific request2 Commencing on 1 January 2010 the registry will assign from the extended AS number space3 Note that a requestor does not need to justify why they require a 16 bit or a 32 bit AS numbewr – they simply have to ask for one or the other. Also note that as of 1 January 2010 there will be no further distinction drawn between the two number pools – they will all just be considered as 32 bit AS Numbers. 1 – AS numbers in the range 65,536 – 4,294,967,295 2 – AS numbers in the range 0 – 65,535 3 – AS numbers in the range 0 - 4,294,967,295

This proposal does NOT: Introduce any extensions to the private AS number space Define any documentation-use AS numbers Advocate the continuation of any 2-byte AS number ‘legacy pool’ beyond 1 January 2010 Create policies that extend beyond 1 January 2010 Require LACNIC to undertake any RIR-coordinated actions Define a different AS number allocation practice for registry operations i.e. there are no other changes to the eligibility or conditions for AS number assignment in this policy. (Private pool: 64,512-65,5340) As of 2010, no 2-byte AS number pool is maintained LACNIC can adopt this proposal unilaterally

Thank You Muchas Gracias Muita Obrigada Nurani Nimpuno on behalf of Geoff Huston draft-ietf-idr-as4bytes-12.txt www.potaroo.net/tools/asns