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 ]
denis walker
ripedenis at gmail.com
Fri Jul 29 11:31:05 CEST 2022
Hi Randy On Fri, 29 Jul 2022 at 02:55, Randy Bush via db-wg <db-wg at ripe.net> wrote: > > the purpose has been for operational use since dirt was invented. the The term 'operational use' has never actually been defined. But if we were to define it then I suspect it will be more about network operators solving technical problems with keeping networks online. > geofeed: attribute points to data which operators, namely content > providers, need. Content providers 'not=' network operators. > maybe we do not need to make a bureaucratic mountain > out of a molehill. Welcome to the modern world. Like it or not, legal considerations have much more influence on technical life now than they did in the early days of the internet. We have to live with this and work with it rather than try to fight against it. The solution is simple in principle...we bring the purposes of the database into line with the content and usage. The need to do this has been on the horizon for a long time... cheers denis co-chair DB-WG > > 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 ]