This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] IP geolocation services
- Previous message (by thread): [ncc-services-wg] IP geolocation services
- Next message (by thread): [ncc-services-wg] IP geolocation services
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Per Heldal
heldal at eml.cc
Wed Oct 28 10:46:14 CET 2009
The importance of geolocation wrt many end-user-services is well understood, but you're missing the point. Geolocation is not an attribute in the RIRs DBs, nor can the RIRs be held responsible for 3rd parties use of the data for unintended purposes. The country-attribute may say something about the location of the LIRs administrative HQ, but nothing prevents a particular prefix from being used somewhere else, or even across many different countries world-wide. What you're asking for would require new policies that place specific requirements on LIRs to register and maintain inetnum-objects for subnets consistent with national borders. //per
- Previous message (by thread): [ncc-services-wg] IP geolocation services
- Next message (by thread): [ncc-services-wg] IP geolocation services
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]