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 ]
Jim Reid
jim at rfc1035.com
Wed Oct 28 10:13:02 CET 2009
On 28 Oct 2009, at 08:57, konradpl at zt.piotrkow.tpsa.pl wrote: > It seems that BGP is the only answer for the problem. Nope. Every IP address (or /24) could have a LOC record associated with it. That could work the same way as a reverse DNS lookup. That said, I think this WG could develop a "Geolocation info from RIR databases (or DNS) considered harmful" RIPE document. IMO there's no need for an RFC or cleverness with ASNs.
- 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 ]