Skip to main content

IANA Policy for Allocation of ASN Blocks to RIRs

This policy proposal has been accepted

2007-04
Publication date:
06 Jan 2011
State:
Accepted
Draft document
DRAFT: Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks to Regional Internet Registries
Author(s)
  • AfriNIC
  • APNIC
  • ARIN
  • LACNIC
  • RIPE NCC
  • AfriNIC
  • APNIC
  • ARIN
  • LACNIC
  • RIPE NCC
  • AfriNIC
  • APNIC
  • ARIN
  • LACNIC
  • RIPE NCC
  • AfriNIC
  • APNIC
  • ARIN
  • LACNIC
  • RIPE NCC
  • AfriNIC
  • APNIC
  • ARIN
  • LACNIC
  • RIPE NCC
Proposal Version
1.0 - 01 May 2007
All Versions
Accepted
17 Sep 2007
Working Group
Address Policy Working Group
Proposal type
  • New
Policy term
Renewable

This This proposal is to have a global policy for the Regional Internet Registries (RIRs) to receive blocks of Autonomous System Numbers (ASNs) from the Internet Assigned Numbers Authority (IANA).

Summary of Proposal:

This proposal is to have a global policy for the Regional Internet Registries (RIRs) to receive blocks of Autonomous System Numbers (ASNs) from the Internet Assigned Numbers Authority (IANA).

Rationale:

Arguments Supporting the Proposal

There are global policies governing the allocation of IPv4 and IPv6 blocks from the IANA to RIRs. At this point there is no specific policy regarding the allocation of Autonomous System Numbers from the IANA to the RIRs. This proposal will create a policy to fill this gap.

The criteria being proposed has already been the practice between IANA and RIRs so far and it has been proven to work. It is designed to allow RIRs to request ASN blocks from the IANA in a timely fashion and maintain enough ASNs in holding to ensure that their registration services can be sustained.

It is also proposed that the RIRs be allocated as many ASN blocks as are needed to support their registration needs for the next 12 months. This will generally mean that each RIR will only need to make one ASN request from the IANA each year, thus lowering operational overhead for the RIRs.

Arguments Opposing the Proposal

None.

Additional Information:

Note: In order to provide additional information related to the proposal, details of an impact analysis carried out by the RIPE NCC are documented below. The projections presented in this analysis are based on existing data and should be viewed only as an indication of the possible impact that the policy may have if the proposal is accepted and implemented.

A. Impact of Policy on Registry and Addressing System

Address/Internet Number Resource Consumption:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.

Fragmentation/Aggregation:
After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.

B. Impact of Policy on RIPE NCC Operations/Services

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.