I also support dropping NWI-17. Removing contact information (address/phones) from the database just because "it looks like PII" would get more confused LEAs contacting RIPE and just defeat the purpose of the DB - a way to find contact information for _who_registered_this_resource_. For GDPR there is the "legitimate interest" when dealing with persons, while company addresses are not PII at all. Some persons found ways to keep the DB "accurate" regarding phone numbers, among other things, just check out a few examples nic-hdl: haz nic-hdl: fsci Radu On Sat, Jul 6, 2024 at 4:33 PM Nick Hilliard via db-wg <db-wg@ripe.net> wrote:
Denis,
denis walker via db-wg wrote on 03/07/2024 17:33:
The Task Force (TF) made the recommendation in NWI-17, but did not give any justification for it.
the justification is included in the final DB-TF report which was published as ripe-767. The recommendations in the various NWIs should be read in the context of this report.
The high cost and low (if any) benefit of splitting this data is completely pointless. [...]
My recommendation is that we drop NWI-17.
The DB-TF considerations behind NWI-17 related to GDPR, so this wasn't a recommendation that came out of nowhere. It would be a better idea to do something about the recommendation rather than unilaterally dropping it.
Since 2021, ML has become a thing. It would be interesting to see if any of the LLMs would return anything useful in response to a query along the lines of "provide a list of all database objects containing information which looks like it's PII".
Nick
--
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