[AfriNIC-rpd] Modifications to the 32-bit ASN policy document

[Ernest - (AfriNIC)]

Dear Colleagues,

Following the approval and consequent publication of RFC5396, 32-bit
AS Numbers will be represented in their decimal notation. The text
in the "4-byte ASN policy document" still displays 32-bit AS Numbers
with the "asdot+" notation (also mentioned in RFC5396).

The 4-byte ASN policy document has hereby been modified, and the
text follows below. Comments from the community are welcome.




32-bit ASN Policy
-----------------

Date:  22 December 2005
Status:  Implemented
Author:  Geoff Huston, APNIC

1.0 Background
2.0 Nomenclature
3.0 Proposal
4.0 Rationale

*1.0 Background*:
-----------------

Recent studies of AS Number consumption rates indicate that the
existing 16-bit 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 expanded the AS Number space
to a 32-bit field [3].

It is noted that some advance period may be required by network
operators to undertake the appropriate procedures relating to
support of 32-bit 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 16-bit 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 32-bit 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.0 Nomenclature*:
-------------------

AS Numbers will be identified using the "asplain" format as
described in RFC5396. Using the "asplain" method,  all AS numbers
will be identified and represented in their decimal integer notation.


*3.0 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 32-bit only AS Numbers and allocate such AS
Numbers as requested by the applicant. In the absence of any
specific request for a 32-bit only AS Number, a 16-bit only AS
Number will be allocated by the registry.

On 1 January 2009 the registry will process applications that
specifically request 16-bit only AS Numbers and allocate such AS
Numbers as requested by the applicant. In the absence of any
specific request for a 16-bit only AS Number, a 32-bit only AS
Number will be allocated by the registry.

On 1 January 2010 the registry will cease to make any distinction
between 16-bit only AS Numbers and 32-bit only AS Numbers, and will
operate AS Number allocations from an undifferentiated 32-bit AS
Number allocation pool.

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


*4.0 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.

References

[1] Daily AS Number Report: http://www.potaroo.net/tools/asns
[2] ASNs MIA: A Comparison of RIR Statistics and RIS Reality:
    http://www.nanog.org/mtg-0510/wilhelm.html
[3] BGP Support for Four-octet AS Number Space:
    http://www.ietf.org/rfc/rfc4893.txt