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 ]
Peter Koch
pk at DENIC.DE
Tue Oct 27 17:36:01 CET 2009
Wilfried, > particular end-system using a particualr address, at a particular point in > time, from a block registered in a particular RIR's DB as an assignment is > very bad idea to begin with. > > At least for the RIPE-DB, there are no agreed or definend semantics for > the interpretation of the country: attribute. The data is a hint, at best. agreed, but the problem in question is not necessarily related to the RIPE DB being used as source of the geolocation information. What seems to be desirable is some notification of changes when a certain address block is unassigned or, more importantly, reassigned. This doesn't have to provide the new location information, but should initiate a new run of the location magic for this address range, so the GeoLoc provider knows when to update/refresh which information. Of course, we know similar demands from the domain business and these requests aren't all free of concern, but the situation might be different here in the addressing world. -Peter
- 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 ]