Dear colleagues of the RIPE NCC database group! I'm using the RIPE whois database in its bulk version ripe.db.inetnum for statistical uses while evaluating the netflow data of our border routers. What I'm much interested in is the origin of an IP address which I get by the country entry of the respective inetnum block of the database. Therefore, I'm always a bit confused about the many addresses which are located in the Netherlands. Since I prefer large inetnum blocks for reasons of performance of my software, I often use entries of many C blocks which are registered for the RIPE NCC with the country entry NL. In the meantime, I already corrected the country entries of some inetnums in my own local copy of the database but this is just a workaround which isn't really satisfying. So I would like to suggest the change of the country entry of - at least - the following inetnum blocks (only inetnum, netname and country entries): inetnum: 0.0.0.0 - 255.255.255.255 netname: IANA-BLK country: NL proposed country: EU # Country is really world wide inetnum: 10.0.0.0 - 10.255.255.255 netname: IANA-ABLK-RESERVED1 country: NL proposed country: EU # Country is really world wide inetnum: 145.224.0.0 - 145.254.255.255 netname: RIPE-NCC-145 country: NL proposed country: EU # Country is really world wide inetnum: 145.0.0.0 - 145.127.255.255 netname: RIPE-NL country: NL proposed country: EU inetnum: 147.233.0.0 - 147.237.255.255 netname: RIPE-ISRAELB-NET country: NL proposed country: EU [or IL] inetnum: 149.132.0.0 - 149.134.255.255 netname: RIPE-149-BLK country: NL proposed country: EU inetnum: 149.202.0.0 - 149.204.255.255 netname: RIPE-149-202-BLK country: NL proposed country: EU inetnum: 149.221.0.0 - 149.250.255.255 netname: EU-ZZ-990225 country: NL proposed country: DE inetnum: 149.206.0.0 - 149.251.255.255 netname: RIPE-149-206-BLK country: NL proposed country: EU inetnum: 163.156.0.0 - 163.175.255.255 netname: NETBLK-RIPE-B country: NL proposed country: EU inetnum: 164.128.0.0 - 164.143.255.255 netname: NETBLK-RIPE-B-128 country: NL proposed country: EU inetnum: 164.0.0.0 - 164.40.255.255 netname: RIPE-164-BLK country: NL proposed country: EU inetnum: 172.16.0.0 - 172.31.255.255 netname: IANA-BBLK-RESERVED1 country: NL proposed country: EU # Country is really world wide inetnum: 192.168.0.0 - 192.168.255.255 netname: IANA-CBLK-RESERVED1 country: NL proposed country: EU # Country is really world wide With the entry 'EU # Country is really world wide' I'm referring to an invention of the RIPE NCC due to the ERX project. You created in 2003 the following inetnums: inetnum: 141.0.0.0 - 141.255.255.255 netname: EU-ZZ-141 country: EU # Country is really world wide inetnum: 151.0.0.0 - 151.255.255.255 netname: EU-ZZ-151 country: EU # Country is really world wide inetnum: 188.0.0.0 - 188.255.255.255 netname: EU-ZZ-188 country: EU # Country is really world wide Better would be nevertheless the creation of let's say 'ZZ' or 'WW' for worldwide use, but if you put in exactly 'EU # Country is really world wide', this will be easily been parsed by Perl. I think that this is a good solution, since it doesn't make sense to put in NL for the whole IPv4 address space for example or for let's say RIPE-ISRAELB-NET. The fact that anybody in the Netherlands has to deal with the related range is clearly reflected by the contact persons or roles which is CREW-RIPE or something like that and which is situated in NL. I'm looking forward to hear your opinion. Best regards, Christoph Mohr -- -- Christoph Mohr, BelWue Coordination ---------- mailto:mohr@belwue.de ----- Computing Center University of Stuttgart (RUS) Phone: +49 711 685-2079 Allmandring 30, D-70550 Stuttgart Fax: +49 711 678-8363 ------------------------------------------------- http://www.belwue.de/ -----