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. (Just for completeness, I don't actually intend to *use* geofeed, but this discussion really upsets me, because it's wasting life time for no good reason) Gert Doering -- LIR contact -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279