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]/
[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 ]
Cynthia Revström
me at cynthia.re
Fri Jul 29 03:02:09 CEST 2022
After having looked closer at Article 3 of the RIPE DB T&C[1], I have to agree with Denis and the legal team, geofeed doesn't really fit into any of those purposes. I should have done this earlier but I have to admit that I had never properly read the RIPE DB T&C before and it was quite dumb of me to comment without doing that, so apologies to the legal team for what I said earlier. So I do think we might need to update the T&C for geofeed to be covered. [1]: https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms -Cynthia On Fri, Jul 29, 2022 at 2:55 AM Randy Bush via db-wg <db-wg at ripe.net> 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 > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- 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 ]