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/db-wg@ripe.net/
[db-wg] NWI-13 Geofeed Legal Analysis
- Previous message (by thread): [db-wg] NWI-13 Geofeed Legal Analysis
- Next message (by thread): [db-wg] NWI-13 Geofeed Legal Analysis
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hank Nussbacher
hank at interall.co.il
Fri Jul 29 08:43:16 CEST 2022
On 29/07/2022 03:55, Randy Bush via db-wg wrote: > the purpose has been for operational use since dirt was invented. the > geofeed: attribute points to data which operators, namely content > providers, need. maybe we do not need to make a bureaucratic mountain > out of a molehill. > > randy > +1. We can argue it but operators like Google already require it otherwise your IPs might be reassigned to another country. See: https://www.iucc.ac.il/en/blog/2021-05-google-geo-location/ for when Google placed all Israeli academic IPs inside Iceland. For Google, RFC8805 is bible and if you don't have a configured CSV for them to parse you might find your IPs being reassigned to some other country (as documented in numerous NANOG postings over the past 2 years). -Hank
- Previous message (by thread): [db-wg] NWI-13 Geofeed Legal Analysis
- Next message (by thread): [db-wg] NWI-13 Geofeed Legal Analysis
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]