Hi Warren I totally agree with you. We are waiting for a response from the RIPE NCC legal team otherwise we are all making guesses in the dark. I'm sure a response will come soon....
Cheers Denis Co-chair DB-WG On Mon, 24 Apr 2023, 21:50 Warren Kumari, <war...@kumari.net> wrote: > > > > > On Thu, Apr 13, 2023 at 5:34 PM, denis walker <db-wg@ripe.net> wrote: > >> Hi Randy, Sylvain >> >> IANAL either but I understood the main legal issue was that there is no >> defined purpose to use the RIPE Database for geolocation services. So >> whatever is in that referenced file is not covered by a valid purpose. We >> have had the "geoloc:" attribute for a long time. The value of this >> attribute is similar to the data contained in this file. So if that data >> was the problem we would already have a problem without "geofeed:". >> >> Maybe we can cover all this with an appropriate purpose. Suppose we >> defined it in this way: >> >> "Providing geolocation information related to Internet number resources >> in a format defined by current IETF specifications." >> >> This covers having a referenced file as long as the content of that file >> is as defined in the IETF specs. >> > > > Seeing as the concerns seem to be legal, and NOUAALNDWPTOTV (None Of Us > Are Actual Lawyers Nor Do We Play Them On TeleVision), I suspect that we > need some input from the lawyers. > > If we ask "Would adding 'Providing geolocation information related to > Internet number resources in a format defined by current IETF > specifications.' alleviate your concerns?" and they nod happily, then job > done… ? > W > > > >> cheers >> denis >> co-chair DB-WG >> >> On Thu, 13 Apr 2023 at 20:20, Randy Bush via db-wg <db-wg@ripe.net> >> wrote: >> >> IANAL and try not to play one on the net. but ... >> >> my reading of why NCC legal has problems with the geofeed: attribute is >> that they see the NCC as legally liable for the content of the geofeed data >> file to which it points. >> >> this concern may be based, for example, in the courts finding pirate bay >> liable for the content to which they pointed, and similar precident. >> >> so the question is not so much the purpose of the database, it is >> constraining the privacy exposing danger in the geofeed files. i think the >> authors of RFC 8805 could be of help here. >> >> but again, IANAL. for one, i charge less :) >> >> 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 >> > >
-- 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
