This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] First round of cleanup of Database WG NWIs
- Previous message (by thread): [db-wg] First round of cleanup of Database WG NWIs
- Next message (by thread): [db-wg] IPv6 object update error
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Sat Jul 6 15:33:23 CEST 2024
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
- Previous message (by thread): [db-wg] First round of cleanup of Database WG NWIs
- Next message (by thread): [db-wg] IPv6 object update error
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]