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 <[email protected]> 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://lists.ripe.net/mailman/listinfo/db-wg -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
