Hello, A very disappointing side-effect. Is it possible to have IANA derogate to the rule ? It's like falling in a trap we dug ourselves... Hopefully, we did not make the same mistake for IPv4/v6 addresses ! Bertrand -----Message d'origine----- De : address-policy-wg-bounces@ripe.net [mailto:address-policy-wg-bounces@ripe.net] De la part de Havard Eidnes Envoyé : jeudi 14 mars 2013 14:14 À : rg@teamix.de Cc : address-policy-wg@ripe.net Objet : Re: [address-policy-wg] RIPE NCC to Assign 16-bit ASNs Until ASN Pool is Replenished
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.
+1 - Håvard