(Amended) IANA Policy for Allocation of ASN Blocks to RIRs
1) Summary of 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.
2) Policy text
Current Policy Text (in current AFPUB-2008-ASN-001):
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 2009, allocations of 2-byte only and 4-byte only ASN blocks will be made separately and independent of each other. This means until 31 December 2009, RIRs can receive two separate ASN blocks, one for 2-byte only ASNs and one for 4-byte only ASNs from the IANA under this policy. After this date, IANA and the RIRs will cease to make any distinction between 2-byte only and 4-byte only ASNs, and will operate ASN allocations from an undifferentiated 4-byte ASN allocation pool.
3) New Policy Text
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 [*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
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.
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.
|28.08.2009||Submitted to rpd mailing list|
|27.11.2009||Consensus to accept was reached at AfriNIC-11|
|04.12.2009||15 Days Last Call for Comments starts.|
|19.12.2009||15 Days Last Call for Comments ends.|
|20.12.2009||Awaiting board approval till date.|
|25.05.2010||Approved by board|
Discussions are taking place on the policy working group mailing list if you want to subscribe to the mailing send your subscription request to rpd-request [at] afrinic.net with 'Subscribe' as subject line
Mailing list archives can be found at https://lists.afrinic.net/pipermail/rpd