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 ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Wed Oct 28 17:03:49 CET 2009
On 28.10 09:29, Marco Hogewoning wrote: ... > I can think of option 1 happening, in fact that mechanism is there, Vergard (and others) found out this is not happening. > option 2 (push) is almost impossible to achieve agree > and I don't like option 3 at all. The RIRs are currently discussing an extended 'stats' file format that will include the "unallocated" address space. This waay ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest and similar files from other RIRs would include the unallocated address space as well. This way we aim to publish once a day a onsistent view about *all* address space. Once implemented this couldbe used as option 3. If it was useful we could add a "quarantined" flag to help. What do people think? Daniel
- 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 ]