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 ]
Peter Koch
pk at DENIC.DE
Fri Apr 8 13:34:05 CEST 2016
On Fri, Apr 08, 2016 at 12:15:29PM +0100, Nick Hilliard 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. >From a data protection perspective, you don't need a reason to delete, you'd need a reason to keep, so the "hurry" starts as soon as the last reference is revoked. Is there a substantive risk? Maybe not. I'd still like to understand what purpose that six months period is supposed to serve. -Peter
- 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 ]