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] Fwd: proposal: new attribute 'geofeed:
- Previous message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
- Next message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Friaças
cfriacas at fccn.pt
Tue Jan 12 10:46:01 CET 2021
Greetings, I still see "purpose" on having person: objects in the database. Contact information for networks and abuse contacts need to be available to anyone. I consider these contacts to be professional, not personal. If anyone has the same personal and professional details, they don't stop to be professional by that fact. A new postal address is not something which is "free", but it is a service that can be subscribed in most places, right? A new EU NIS2 directive is also upcoming. I hope the need for whois/rdap/whatever accurate data could be clarified in some of its articles. Regards, Carlos On Mon, 11 Jan 2021, Randy Bush via db-wg wrote: >> Hi guys > > ahem > >> GDPR applies to the entire RIPE Database because the RIPE NCC, who >> operate the database, is based in the EU. > > appreciate the legal opinion. how come person: objects are allowed? > > randy >
- Previous message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
- Next message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]