[db-wg] GDPR and the RIPE Database
- Previous message (by thread): [db-wg] GDPR and the RIPE Database
- Next message (by thread): [db-wg] GDPR and the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Mon Oct 7 14:22:51 CEST 2019
Sorry Laurent, accidentally sent this to you instead of the ML first. I think it is reasonable to keep abuse email info. Just my humble opinion though. - Cynthia On Mon, 7 Oct 2019, 14:19 Laurent Pellegrino via db-wg, <db-wg at ripe.net> wrote: > Hi there, > > That's interesting. Does it mean that services providing contact > information for abuse (e.g. https://ipinfo.io/abuse > <http://email.mailgun.ipregistry.co/c/eJwdjLsKgzAAAL8mbhGNqZohg1VEROtWaZeSlxrqq76qf18pHMdNJ6kUzEGOoWkYpOVj4nZxC7NLuCcsj4rd_cRJnsC4fEoOnOiebke2HvA1k_cG0BWKL8BWx3Rr1n-LoTMaqnzCiS-Z5xK3UsIiGNsKW9IniGPPE0ZLm2UZZ-AEAMUnetR9NZh6OJvxdVbGRCWH3_q8T3pUZq-WH7hRNU4>) are > legally wrong? are you going to take any action? > > Regards, > Laurent > > Le lun. 7 oct. 2019 à 12:38, Edward Shryane via db-wg <db-wg at ripe.net> a > écrit : > >> Dear Working Group, >> >> We implemented and deployed the changes below for GDPR compliance as part >> of Whois 1.95.1, on the 18th September: >> >> https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-release-1.95 >> <http://email.mailgun.ipregistry.co/c/eJw1jk-LgzAUxD9NvD0xsZHmkENrESn9c9uye1leTLSymrombdpvv3GhMAzMb3iP0VI3mLM86WW52V8-Z0XPp_LAy2eNx935WfxW9bGG6vKlFcl3H_vH63B_wbcTPw_CttAEsspG7Ie0-_fmNiZXydaC07YQrOBm3VLBqFihzgzyNhNKNMkgr95PjuQbwqqoEEI695NJrfExjmixM9BPDtBqQGddpHEBq2YzGHQG7M2bBS5XoNGjWui7pangySy1gtDFge_Xf7CeTEE> >> >> Apologies if this was not clear. >> >> Regards >> Ed Shryane >> RIPE NCC >> >> >> >> On 27 May 2019, at 11:30, Edward Shryane via db-wg <db-wg at ripe.net> >> wrote: >> >> Dear Working Group, >> >> as mentioned in last week's DB-WG meeting, we will shortly be >> implementing the following changes: >> >> - Do not include personal data in historical queries (notify, e-mail, >> address attributes). >> - Do not include person/role references in historical queries (admin-c, >> tech-c, ping-hdl, zone-c). >> >> A legal review found we should not return historical contact details, as >> they may contain personal data, which is not in line with the purpose of >> the RIPE database or data protection legislation. >> >> For background, Maria Stafyla from RIPE NCC Legal presented on this topic >> at RIPE 76: >> https://ripe76.ripe.net/presentations/101-GDPR-Database-WG-RIPE-76.pdf >> <http://email.mailgun.ipregistry.co/c/eJw1Tk1vwjAU-zXp7VWkoWl3yIG1KwXxJQ6rtgt6r0mhGpTShK9_v2wSkmXLlmxZK12jiETQqmwyr74G4utVtoizR4nLfP2Ql6JcllBU35qYyD_nt-fi-oSdffu5segd6jsbj07YHsP9P9fnU3BQXDYpEcYSBYko1bKhhDdJ6q3PYgqO6uBcb5mYsKjwGNreJDL8k7Azzif9YKzpHLr23Fnv-YjDNN9sIUeHhNZANYXtbPMBvtfrJhiUJrjv_Z3Xyi-SvUUW> >> >> Regards >> Ed Shryane >> RIPE NCC >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20191007/096f400d/attachment.html>
- Previous message (by thread): [db-wg] GDPR and the RIPE Database
- Next message (by thread): [db-wg] GDPR and the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]