Status: NRPM Section 10.3
Formal introduction on PPML on 31August 2009
Draft Policy - 31 August 2009 (with staff assessment)
Last call - 28 October through 13 November 2009
AC recommened Board adopt - 24 November 2009
Adopted by the ARIN Board - 13 January 2010
Adopted by the ICANN Board - 21 September 2010
NRPM updated - 12 January 2011Public Policy Mailing List
ARIN Public Policy Meeting:ARIN XXIV
ARIN Advisory Council:
Stacy Hughes and Marla Azinger
- 18 June 2009
- 16 July 2009
ARIN Board of Trustees:18 December 2009
Implementation:21 September 2010
Draft Policy 2009-6 (Global)
Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries
Version/Date: 31 August 2009
Modification of NRPM section 10.3 extending the deadline for an undifferentiated ASN pool by
1 year to read:
1. Allocation Principles
IANA allocates ASNs to RIRs in blocks of 1024 ASNs. In this document the term "ASN block"
refers to a set of 1024 ASNs. Until 31 December 2010, allocations of 16-bit and 32-bit only ASN
blocks will be made separately and independent of each other .
This means until 31 December 2010, RIRs can receive two separate ASN blocks, one for 16-bit
ASNs and one for 32-bit only ASNs from the IANA under this policy. After this date, IANA and
the RIRs will cease to make any distinction between 16-bit and 32-bit only ASNs, and will
operate ASN allocations from an undifferentiated 32-bit ASN allocation pool.
a. Arguments supporting the proposal
Due to operational issues external to the IANA/RIR policy process, 32-bit only ASNs are not
being issued by the RIRs at the anticipated rate. As it stands, RIRs will likely not be able to
justify a new block of ASNs from the IANA after 31 December 2009 due to a glut of free 32 bit
only ASNs in the RIR's pool. This leaves available, essential 16-bit ASNs stranded in the IANA
free pool. This proposal seeks to remedy the potential problem by extending the deadline for
differentiation by one year.
With this proposal the policy will be aligned with the actual reality in regards to 32-bit ASN
deployment and usage.
The subject was raised during RIPE 58 and a presentation was made:
The feedback in this session suggested that a global policy proposal should be developed and
should be discussed.
b. Arguments opposing the proposal
Some may think that extending the previously set timeline can be perceived as some
discouragement for the deployment of 32-bit ASNs. One counter argument to this is that RIRs
and Internet community have some other mechanisms and activities to raise awareness for 32-bit
ASN pool (via public presentations and trainings). These activities will continue while 16-bit
ASN blocks are still allocated to RIRs by the IANA as they are available and they are needed.
Timetable for implementation: Immediately upon ratification by ICANN Board