| Ref Name | AFPUB-2008-ASN-001 | Old Ref. | afpol-asn200708 |
| Status | Obsolete | ||
| Date | 27 Feb 2008 | ||
| Author(s) | Andrew de la Haye Stacy Hughes |
||
| Organisation | |||
| TOC | |||
1.0 Proposal:
Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries (Global Policy proposal)
According to the current global policy (AFPUB-2008-ASN-001), IANA will cease to make any distinction between 16-bit and 32-bit only ASN blocks by 31 December 2009, when making allocations to RIRs. This proposal is to extend this date by one year, to 31 December 2010.
This document describes the policy governing the allocation of Autonomous System Numbers (ASNs) from the IANA to the Regional Internet Registries (RIRs).
This policy document does not stipulate performance requirements in the provision of services by the IANA to an RIR. Such requirements will be specified by appropriate agreements between ICANN and the Number Resource Organization (NRO).
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 [1].
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.
16-bit ASNs are the AS Numbers in the range: 0 - 65535
32-bit only ASNs are the AS Numbers in the range: 65536 - 4294967295
32-bit ASNs are the AS Numbers in the range: 0 - 4294967295
Each new RIR will be allocated a new ASN block.
An RIR is eligible to receive (an) additional ASN block(s) from the IANA if one of the following conditions is met:
4.1. The RIR has assigned 80% of the previously received ASN block
or
4.2. The number of free ASNs currently held by the RIR is less than the RIRs two months’ need. This projection is based on the monthly average number of ASNs assigned by the RIR over the previous six months.
An RIR will be allocated as many ASN blocks as are needed to support their registration needs for the next 12 months, based on their average assignment rate over the previous six months, unless the RIR specifically requests fewer blocks than it qualifies for.
5.0 Announcement of IANA Allocations
The IANA, the NRO and the RIRs will make announcements and update their respective websites/databases when an allocation is made by the IANA to an RIR. ICANN and the NRO will establish administrative procedures to manage this process.
6.1 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.
6.2 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.
| History | |
| 29.08.2007 | Proposal was posted to rpd mailing list. AFPUB-2008-ASN-001 Initial Version |
| 02.10.2007 | 15 Days Last Call for Comments starts. |
| 17.10.2007 | 15 Days Last Call for Comments ends. |
| 20.08.2007 | Submitted for board approval. |
| 30.01.2008 | Ratified by board. |
| 27.02.2008 | Announcement made on rpd about board approval. |
| 24.11.2010 | Obsoleted by AFPUB-2009-GEN-005 |
