-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Tim, Tim Wilde wrote: [...]
Andrea,
Thank you for this pointer, this is indeed an interesting and helpful file. However, I note that it has the same problem as the traditional delegated prefixes file, ie, it lists the "debogon" prefixes listed in your announcement (185.0.0.0/16, 185.1.0.0/21, and 185.1.24.0/24) as available as part of an "available" listing for all of 185.0.0.0/10:
ripencc||ipv4|185.0.0.0|4194304||available
If we were to use this file, we would have the same problem that we have using the traditional delegated list; we would list your "debogon" prefixes as bogon, because, according to your records, they are available, ie unallocated/unassigned, ie bogon. Do you see the problem we're running into? From my perspective, the "debogon" prefixes should be considered allocated - it's an internal allocation, and a temporary one, but it's still an allocation. This is, in fact, how 185.0.0.0/17 is listed in the RIPE WHOIS database:
% Information related to '185.0.0.0 - 185.1.255.255'
inetnum: 185.0.0.0 - 185.1.255.255 netname: EU-ZZ-20100510 org: ORG-NCC1-RIPE descr: RIPE NCC Test Announce country: EU admin-c: HU266-RIPE tech-c: RISM-RIPE status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-by: RIPE-NCC-RIS-MNT source: RIPE # Filtered
But this is not reflected in the delegated-latest file. Should it not be there (and in this new experimental file) as an allocation, since that's what WHOIS says it is?
Historically these pilot prefixes have never been listed in the delegated-latest file. However I agree with you that they should. We will add these temporary allocations to the delegated-latest file in the coming days. Best regards, Andrea Cima RIPE NCC
Best regards, Tim Wilde
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk1b93gACgkQXOgsmPkFrjMPwwCgiqYrdIhlGWvk87v7LH+MXHVS 4pkAoJJUbYrHpEKBbuQ5TIx/gnLYndiu =iJ0m -----END PGP SIGNATURE-----