Hi there, That's interesting. Does it mean that services providing contact information for abuse (e.g. https://ipinfo.io/abuse) are legally wrong? are you going to take any action?
Regards, Laurent Le lun. 7 oct. 2019 à 12:38, Edward Shryane via db-wg <[email protected]> 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 > > Apologies if this was not clear. > > Regards > Ed Shryane > RIPE NCC > > > > On 27 May 2019, at 11:30, Edward Shryane via db-wg <[email protected]> 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 > > Regards > Ed Shryane > RIPE NCC > > > >
