[db-wg] geofeed issue: can't add geofeed attribute to PI /48

> On 20220224, at 16:56, Gert Doering via db-wg <db-wg at ripe.net> wrote:
> 
> Hi,
> 
> On Thu, Feb 24, 2022 at 04:28:39PM +0100, Edward Shryane via db-wg wrote:
>> The Legal review in November recommended:
>> 
>> "if the geofeed attribute is inserted for registrations of assignments that are reasonably assumed to be related to one individual user, then the attribute will be considered personal data. "
> 
> This is something I'd agree to.
> 
> The consequences of that ("insert arbitrary rules into the RIPE DB based
> on assumptions on what might or might not consider an end-user assignment,
> and disallow some attributes on that"), not.
> 
> We don't ever register inet(6)num: for individuals, only for corporate
> customers.
> 
> Even if we did, if I had agreement from the customer (in writing!) that
> they are fine with me putting their full name, phone number, postal 
> address *and* geofeed attribute in the DB, this is not the NCC's 
> business to disallow "geofeed", while allowing all the other PII data.

^---- +1 on all that what Gert writes.

While RIPE NCC should provide guidance, it should not restrict it so much that one cannot do this.

Greets,
 Jeroen