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

Hi,

On Thu, Mar 14, 2013 at 09:52:08AM +0100, Andrew de la Haye wrote:
> 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.
> 
> 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.

Mh, not April first.


Seriously, where has this gone wrong?  the utilization rate of 16Bit
ASNs should not be a measure for replenishing the 32 bit Pool.

It should never have been.


This way you're actually forced to hand out 16bit ASNs BEFORE your 32bit
pool runs out because there shouldnt be the situation that when somene
explicitely asks for a 32bit ASN RIPE NCC is not able to "supply" one.



Rico.

MfG/regards,
-- 
Rico Gloeckner
Sr. System Engineer

Amtsgericht Nuernberg, HRB 18320
Geschaeftsfuehrer: Oliver Kuegow, Richard Mueller