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]/
[ncc-services-wg] RIPE NCC as communication go-between, was RIPE Database Proxy Service Issues
- Previous message (by thread): [ncc-services-wg] Personal Data and Database Proxy services
- Next message (by thread): [ncc-services-wg] RIPE NCC as communication go-between, was RIPE Database Proxy Service Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Thu Jan 3 14:13:33 CET 2013
Andrey, On Wednesday, 2013-01-02 20:43:33 +0200, Andrey Semenchuk <andrey at trifle.net> wrote: > > 2. Data must provide contact information to any parties to be able to > communicate with the person who described by the personal data object > ============================================================================== > In this case personal data provided and processed in the same way and > purpose that they were collected and no restrictions should be used An alternate approach would be for the RIPE NCC to act as a go-between for communicating with resource holders. For example, if I know which hotel you are staying at, I can call the hotel and ask them to put me through to your room so I can talk to you, or I can leave a message. The hotel should not give me your room number, or any other information about you that they know. Likewise the RIPE NCC could convey messages to resource holders. In such a system we would not have to publish ANY private information. Cheers, -- Shane
- Previous message (by thread): [ncc-services-wg] Personal Data and Database Proxy services
- Next message (by thread): [ncc-services-wg] RIPE NCC as communication go-between, was RIPE Database Proxy Service Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]