[db-wg] NWI-13 Geofeed Legal Analysis

I am not sure how you came to that conclusion, the way I read Maria's
email didn't make me come to a conclusion anything like that.

Maria said:
> The RIPE Database is meant to contain specific information for the purposes that are defined in the RIPE Database Terms and Conditions.

The RIPE DB T&C and the DBTF report are not the same and the RIPE DB
T&C could be amended.

Maria also says:
> If the community's interests have changed since then and it is now agreed that geolocation is one of the purposes the RIPE Database must fulfil, this should be decided via the community's processes and reflected in the RIPE Database Terms and Conditions.

I feel like this directly goes against what you are saying, it seems
very clear to me that it is possible to change the purposes.

-Cynthia

On Fri, Jul 29, 2022 at 3:29 AM Ronald F. Guilmette via db-wg
<db-wg at ripe.net> wrote:
>
> In message <CAKw1M3PZPzwJHoNyGrSAY_2azHeZpTw4aVw7GwCLhmT_qt2CiA at mail.gmail.com>
> =?UTF-8?Q?Cynthia_Revstr=C3=B6m?= <me at cynthia.re> wrote:
>
> >The purposes could change...
>
> No, they couldn't.
>
> It appears that the RIPE Database Requirements Task Force issued its
> "final report" sometime late last year, and now the wheels have ground
> on further to bring us to the point where RIPE legal has issued an
> official proclamation to the effect that everything that does not
> comport with the Task Force's final list of defined purposes _must_
> be jetisoned and thrown overboard.
>
> That would appear to be the short version of where things stand now.
>
> Based upon the principal of stare decisis, it would seem to be a bit
> late in the game to try to roll back any of what has already been
> adjudicated.
>
>
> Regards,
> rfg
>
>
>
> --
>
> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/