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] 2022-01 New Version Policy Proposal (Personal Data in the RIPE Database)

Previous message (by thread): [db-wg] 2022-01 New Version Policy Proposal (Personal Data in the RIPE Database)
Next message (by thread): [db-wg] 2022-01 New Version Policy Proposal (Personal Data in the RIPE Database)

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

Niels Bakker niels=dbwg at bakker.net
Tue Jun 21 13:21:41 CEST 2022

* Ronald F. Guilmette [Tue 21 Jun 2022, 08:14 CEST]:
[..]
>denis contends that this makes RIPE responsible in some way, 
>presumably legally, for the publication of the relevant PII and that 
>thus it is RIPE that is violating GDPR... and on a grand scale.
>
>I disagree entirely, and apparently you do also.

You're misunderstanding the problem statement on two levels. RIPE NCC
currently offers no way out of publishing information that people may
want to keep private, for no legal basis, and denis's proposal (which
I support) changes this. Furthermore, the analogy goes awry where the
Hamburg store owner currently hangs customer lists in the shop window.


	-- Niels.

Previous message (by thread): [db-wg] 2022-01 New Version Policy Proposal (Personal Data in the RIPE Database)
Next message (by thread): [db-wg] 2022-01 New Version Policy Proposal (Personal Data in the RIPE Database)

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

[ db-wg Archives ]