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] 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 ]

Nick Hilliard nick at inex.ie
Fri Apr 8 13:15:29 CEST 2016

Peter Koch wrote:
> From a data protection perspective, this cool down phase appears rather long,
> especially given that even after following (3b) there's no proposed way to actively delete
> the locked (and re-instantiated) object.  What's the perceived drawback of few days only?

Is there a particular hurry to delete these objects?  180 days sounds
fine to me.

Nick

• 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 ]