[address-policy-wg] RIPE NCC to Assign 16-bit ASNs Until ASN Pool is Replenished

Dear colleagues,

The RIPE NCC has less than 100 32-bit Autonomous System Numbers (ASNs)
available in its pool. Given current assignment rates, we expect that we
will run out of 32-bit ASNs before May 2013. We will soon begin to
assign 16-bit ASNs for all requests until our pool has been replenished
by IANA. This will not result in any operational issues for requestors
as 16-bit ASNs are compatible with equipment designed to run BGP.  This
situation was anticipated and covered during the RIPE NCC Registration
Services update during the RIPE 65 Meeting.

You can see the details in
the "Feedback from RIPE NCC Registration Services" presentation
available at:
<https://ripe65.ripe.net/programme/meeting-plan/address-policy-wg/>

--------------------------
Replenishing our ASN Pool
--------------------------
The RIPE NCC requests additional ASNs from IANA based on "IANA Policy
for Allocation of ASN Blocks to RIRs:
<https://www.ripe.net/ripe/docs/ripe-480>

Under this policy, we need to demonstrate 80% usage of "the previously
received ASN block" (which includes both 16-bit and 32-bit ASNs we
received from IANA on 3 March 2012) to replenish our ASN pool. We are
expecting to reach this usage rate within six to eight months.

The RIPE NCC will return to the usual procedure of assigning 32-bit AS
numbers "by default" once our ASN pool is replenished.

--------------------------------------------------------------------
Background on 32-bit ASN assignments in the RIPE NCC service region
--------------------------------------------------------------------

The RIPE NCC assigns ASNs based on the "Autonomous System (AS) Number
Assignment Policies and Procedures":
<https://www.ripe.net/ripe/docs/ripe-52>.

In accordance with the RIPE Address Policy Working Group decision,
announced at:
<http://www.ripe.net/ripe/mail/archives/address-policy-wg/2010-January/004977.html>,

the RIPE NCC assigns 32-bit ASNs by default unless a 16-bit ASN is
specifically requested.

As a result of this practice, 32-bit ASNs are currently supported by
most vendors and routed globally. Of the 3,400 32-bit ASNs in the global
routing table, 64% were assigned by the RIPE NCC within its service
region (Europe, the Middle East and parts of Central Asia).

Best regards,

Andrew de la Haye
Chief Operations Officer
RIPE NCC