ARIN-PPML Message

[arin-ppml] Draft Policy 2009-6 (Global): IANA Policy for Allocation of ASNs to RIRs

Draft Policy 2009-6 (Global)
Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN
Blocks (ASNs) to Regional Internet Registries

On 20 August 2009 the ARIN Advisory Council (AC) selected "Internet
Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks
(ASNs) to Regional Internet Registries" as a draft policy for adoption
discussion on the PPML and at the Public Policy Meeting in Dearborn.

The draft was developed by the AC from "Policy Proposal 89. (Global)
Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN
Blocks (ASNs) to Regional Internet Registries". Per the Policy
Development Process the AC submitted text to ARIN for a staff and legal
assessment prior to its selection as a draft policy. After reviewing the
assessment the AC did not change the text.

Draft Policy 2009-6 is below and can be found at:
https://www.arin.net/policy/proposals/2009_6.htm

Below the draft policy is the ARIN staff and legal assessment, including
the original proposal text.

You are encouraged to discuss Draft Policy 2009-6 on the PPML prior to
the October Public Policy Meeting. Both the discussion on the list and
at the meeting will be used by the ARIN Advisory Council to determine
the community consensus for adopting this as policy.

The ARIN Policy Development Process can be found at:
https://www.arin.net/policy/pdp.html

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html

Regards,

Member Services
American Registry for Internet Numbers (ARIN)


## * ##


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

Policy statement:

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 [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.

Rationale:

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:
http://www.ripe.net/ripe/meetings/ripe-58/content/presentations/asn32-take-up-report.pdf 






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

#####

Staff Assessment

Proposal: Internet Assigned Numbers Authority (IANA) Policy for
Allocation of ASN Blocks (ASNs) to Regional Internet Registries

Proposal Version (Date): 27 May 2009

Date of Assessment: 08-18-09

1. Proposal Summary (Staff Understanding)

This is a global proposal. It modifies section 10.3 of the NRPM to
extend the current deadline for an undifferentiated pool of ASNs from
Dec 31, 2009 to Dec 31, 2010. This proposal would allow IANA to issue
the RIRs blocks of both 16-bit ASNs and 32-bit ASNs until Dec 31, 2010.
After that time, no distinction would be made between the two types of
ASNs, and all ASNs would be allocated from a 32-bit pool.

2. Comments

A. ARIN Staff Comments

The policy can be implemented as written.

The policy would completely remove the word ‘byte’ from the NRPM in
favor of the term ‘bit’.

B. ARIN General Counsel

Counsel does not see any material legal issues related to this policy.

3. Resource Impact

This policy would have minimal resource impact. It is estimated that
implementation would occur within 3 months after ratification by the
ARIN Board of Trustees. The following would be needed in order to implement:
Updated guidelines
Staff training

4. Proposal Text

Policy Proposal Name: Internet Assigned Numbers Authority (IANA) Policy
for Allocation of ASN Blocks (ASNs) to Regional Internet Registries

Date: 27 May 2009

Policy statement: 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 [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.

Rationale:

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:
http://www.ripe.net/ripe/meetings/ripe-58/content/presentations/asn32-take-up-report.pdf 






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