[address-policy-wg] RIPE NCC to Assign 16-bit ASNs Until ASN Pool is Replenished
- Previous message (by thread): [address-policy-wg] RIPE NCC to Assign 16-bit ASNs Until ASN Pool is Replenished
- Next message (by thread): [address-policy-wg] RIPE NCC to Assign 16-bit ASNs Until ASN Pool is Replenished
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Havard Eidnes
he at uninett.no
Thu Mar 14 14:13:32 CET 2013
>> 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
- Previous message (by thread): [address-policy-wg] RIPE NCC to Assign 16-bit ASNs Until ASN Pool is Replenished
- Next message (by thread): [address-policy-wg] RIPE NCC to Assign 16-bit ASNs Until ASN Pool is Replenished
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]