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/[email protected]/
[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 ]
konradpl at zt.piotrkow.tpsa.pl
konradpl at zt.piotrkow.tpsa.pl
Wed Oct 28 10:57:39 CET 2009
I do agree that we can put as many records to the database as we want. Problem is in usabilility (BGP feed is easier to deal with on CDN platforms) and first of all speed - with BGP you can follow automaticly every change in network topology while separate database needs manual intervention. Konrad Plich On Wed, 28 Oct 2009, Jim Reid wrote: > 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 ]