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/[email protected]/

[db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database

Previous message (by thread): [db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database
Next message (by thread): [db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Sascha Luck [ml] dbwg at c4inet.net
Thu Apr 14 14:08:44 CEST 2016

On Thu, Apr 14, 2016 at 02:02:42PM +0200, Peter Hessler wrote:
>In English, "you" can be either 2nd person singular, or 2nd person
>plural.  I personally could use it to refer to any or all of the DB-WG,
>the DB-WG Admins, RIPE, or the RIPE NCC.
>

Semantics and accusations aside, Denis is not wrong on the issue
of the locked objects.
>From a data protection PoV, leaving them locked but visible is
*exactly* the wrong thing to do. If they are non-verifiable,
delete them. Do it NOW. If that causes issues with objects that
reference the locekd objects, replace the reference with a
template object or something until it can be replaced.

rgds,
Sascha Luck

Previous message (by thread): [db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database
Next message (by thread): [db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]