Policy Pre-CPM

Last Modified on -

Details
  • Ref. Name:
    AAFPUB-2005-ASN-001
  • Old Ref:
    afpol-asn200509
  • Status:
    Implemented
  • Date:
    22 Sept 2005
  • Author:
    • Geoff Huston
      APNIC

1) Background

Recent studies of AS Number consumption rates indicate that the existing 2-byte pool of unallocated AS Numbers will be exhausted sometime in the period between 2010 and 2016, absent of any concerted efforts of recovery of already-allocated AS Numbers [1] [2]. Standardisation work in the IETF has produced a document that is currently being submitted as a Proposed Standard that will expand the AS Number space to a 4-byte field [3].

It is noted that some advance period may be required by network operators to undertake the appropriate procedures relating to support of 4-byte AS Numbers, and while no flag day is required in the transition to the longer AS Number field, it is recognised that a prudent course of action is to allow for allocation of these extended AS Numbers well in advance of an anticipated 2-byte AS Number exhaustion date.

This policy proposal details a set of actions and associated dates for RIR AS Number allocation policies to assist in an orderly transition to use of the 4-byte AS Number space.

The essential attributes of this policy proposal are to facilitate the ease of transitional arrangements by equipment vendors, network managers and network operations staff, to provide the industry with some predictability in terms of dates and associated actions with respect to registry operational procedures for AS Number allocations.

 

2) Nomenclature

It is proposed to identify 4-byte AS Numbers using a syntax of..

Accordingly, a 4-byte AS Number of value 65546 (decimal) would be identified as "1.10".

 

3) Terminology

  • "2-byte only AS Numbers" refers to AS Numbers in the range 0 - 65535
  • "4-byte only AS Numbers" refers to AS Numbers in the range 1.0 - 65535.65535 (decimal range 65,536 - 4,294,967,295)
  • "4-byte AS Numbers" refers to AS Numbers in the range 0.0 - 65535.65535 (decimal range 0 - 4,294,967,295) Draft Policy Text

 

4) Proposal

This policy proposal nominates three dates for changes to the current AS Number allocation policy for the registry:

  • On 1 January 2007 the registry will process applications that specifically request 4-byte only AS Numbers and allocate such AS Numbers as requested by the applicant. In the absence of any specific request for a 4-byte only AS Number, a 2-byte only AS Number will be allocated by the registry.
  • On 1 January 2009 the registry will process applications that specifically request 2-byte only AS Numbers and allocate such AS Numbers as requested by the applicant. In the absence of any specific request for a 2-byte only AS Number, a 4-byte only AS Number will be allocated by the registry.
  • On 1 January 2010 the registry will cease to make any distinction between 2-byte only AS Numbers and 4-byte only AS Numbers, and will operate AS Number allocations from an undifferentiated 4- byte AS Number allocation pool.

No other changes in AS Number allocation policy are implied by this proposal.

 

5) Rationale

The essential attributes of this policy proposal are to facilitate the ease of transitional arrangements by equipment vendors, network managers and network operations staff, to provide the industry with some predictability in terms of dates and associated actions with respect to registry operational procedures for AS Number allocations.

 

6) References

[1] Daily AS Number Report

[2] ASNs MIA: A Comparision of RIR Statistics and RIS Reality

[3] BGP Support for Four-octet AS Number Space: draft-ietf-idr-as4bytes-12.txt

 

 

History
09.12.2005 Proposal first posted to rpd mailing list
17.05.2006 Consensus reached to accept the proposal during AfriNIC-4 in Nairobi, Kenya
13.11.2006 15 Days Last Call for Comments period starts.
28.11.2006 15 Days Last Call for Comments ends.

 

Last Modified on -

 

Details
  • Ref. Name:
    AFPUB-2006-v6-001
  • Old Ref:
    afpol-glbipv6200508
  • Status:
    Implemented
  • Date:
    17 May 2005
  • Author:
    • Alan Barett

1) Introduction

This document describes the policy governing the allocation of IPv6 address space from the IANA to the Regional Internet Registries (RIRs). This document does not stipulate performance requirements in the provision of services by IANA to an RIR in accordance with this policy. Such requirements will be specified by appropriate agreements between ICANN and the NRO.

 

2) Allocation Principles

The unit of IPv6 allocation (and therefore the minimum IPv6 allocation) from IANA to an RIR is a /12

The IANA will allocate sufficient IPv6 address space to the RIRs to support their registration needs for at least an 18 month period.

The IANA will allow for the RIRs to apply their own respective chosen allocation and reservation strategies in order to ensure the efficiency and efficacy of their work.

 

3) Initial Allocations

On inception of this policy, each current RIR with less than a /12 unallocated address space, shall receive an IPv6 allocation from IANA

Any new RIR shall, on recognition by ICANN receive an IPv6 allocation from the IANA

 

4) Additional Allocations

A RIR is eligible to receive additional IPv6 address space from the IANA when either of the following conditions are met.

The RIR's AVAILABLE SPACE of IPv6 addresses is less than 50% of a /12.

The RIR's AVAILABLE SPACE of IPv6 addresses is less than its established NECESSARY SPACE for the following 9 months.

In either case, IANA shall make a single IPv6 allocation, sufficient to satisfy the established NECESSARY SPACE of the RIR for an 18 month period.

 

5) Calculation of AVAILABLE SPACE

The AVAILABLE SPACE of IPv6 addresses of a RIR shall be determined as follows:

AVAILABLE SPACE = CURRENTLY FREE ADDRESSES + RESERVATIONS EXPIRING DURING THE FOLLOWING 3 MONTHS - FRAGMENTED SPACE

FRAGMENTED SPACE is determined as the total amount of available blocks smaller than the RIR's minimum allocation size within the RIR's currently available stock.

 

6) Calculation of NECESSARY SPACE

If the applying Regional Internet Registry does not establish any special needs for the period concerned, NECESSARY SPACE shall be determined as follows:

NECESSARY SPACE = AVERAGE NUMBER OF ADDRESSES ALLOCATED MONTHLY DURING  THE PAST 6 MONTHS * LENGTH OF PERIOD IN MONTHS

If the applying RIR anticipates that due to certain special needs the rate of allocation for the period concerned will be different from the previous 6 months, it may determine its NECESSARY SPACE as follows:

Calculate NECESSARY SPACE as its total needs for that period according to its projection and based on the special facts that justify these needs.

Submit a clear and detailed justification of the above mentioned projection (Item A).

If the justification is based on the allocation tendency prepared by the Regional Internet Registry, data explaining said tendency must be enclosed.

If the justification is based on the application of one or more of the Regional Internet Registry's new allocation policies, an impact analysis of the new policy/policies must be enclosed.

If the justification is based on external factors such as new infrastructure, new services within the region, technological advances or legal issues, the corresponding analysis must be enclosed together with references to information sources that will allow verification of the data.

If IANA does not have elements that clearly question the Regional Internet Registry's projection, the special needs projected for the following 18 months, indicated in Item A above, shall be considered valid.

 

7) Announcement of IANA Allocations

The IANA, the NRO, and the RIRs will make announcements and update their respective web sites regarding an allocation made by the IANA to an RIR. ICANN and the NRO will establish administrative procedures to manage this process.

 

 

History
03.12.2005 Consensus reached at AfriNIC 3 (Cairo - Egypt) to send to AfriNIC board for approval
09.02.2006 15 Days Last Call for Comments starts
24.02.2006 15 Days Last Call for Comments ends.
17.05.2006 Implemented

 

Page 9 of 12