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] RIPE NCC as communication go-between, was RIPE Database Proxy Service Issues
- 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 15:15:38 CET 2013
Andrey, On Thursday, 2013-01-03 16:03:28 +0200, Andrey Semenchuk <andrey at trifle.net> wrote: > Shane Kerr wrote: > > 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. > > > Actually this method was proposed in the letter you quote :) It will > not work with phone numbers but with the emails - it will work. And > already works for some public organisations which operates with > personal data in compliance with Directive 95/46/EC. So RIPE has > nothing to devise in this situation Oh, I see. I should read more carefully. One slight difference is that I don't propose any particular mechanism, including where or how data is stored, or how messages are received or transmitted. I'm glad that other organisations have figured this out, and that we can happily copy what they have done. :) Cheers, -- Shane
- Previous message (by thread): [ncc-services-wg] RIPE NCC as communication go-between, was RIPE Database Proxy Service Issues
- 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 ]