* Alex Le Heux
Thank you for reporting these issues.
We hope to have these fixed today.
I can see that they are, thanks! I have a couple questions regarding some changes from the "beta" delegated-extended files (that were available from http://albatross.ripe.net/delegated-extended/): 1) A new status field "reserved" has appeared. Most (all?) of the IPv4 resources with this status was "available" in the beta files. A couple of random examples:
From beta file: ripencc||ipv4|5.10.0.0|16384||available ripencc||ipv4|194.145.208.0|512||available
From new file: ripencc||ipv4|5.10.0.0|16384||reserved ripencc||ipv4|194.145.208.0|512||reserved
Am I correct in assuming that reserved resources are either deemed to problematic for delegation by the debogon project, or recently returned resources placed in a temporary quarantine? Are there any other reasons why (IPv4) resources may end up as reserved? Will all of these reserved resources be automatically freed up and delegated by the NCC prior to implementing the last /8 policy, or will they be considered unavailable for the purpose of determining whether or not the last /8 policy's trigger criteria, «RIPE NCC is required to make allocations from the final /8 it receives from the IANA», is met? 2) Available resources are no longer split into CIDR boundaries. Not a big deal, but I must admit I preferred the old way from the beta file, so I am wondering if this is an intentional change or if would be possible to get the old way back. Random example:
From beta file: ripencc||ipv4|194.153.156.64|64||available ripencc||ipv4|194.153.156.128|128||available
From new file: ripencc||ipv4|194.153.156.64|192||available
Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com/