GDPR AND WHOIS: Difference between revisions
Dustin Loup (talk | contribs) Created page with "==GDPR and WHOIS== The GDPR directly impacts the domain name space, most notability the WHOIS service. Prior to the GDPR enforcement date, ICANN's contracted parties (..." |
Dustin Loup (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
===Accreditation Model=== | ===Accreditation Model=== | ||
==References== | |||
Revision as of 14:31, 9 April 2018
GDPR and WHOIS[edit | edit source]
The GDPR directly impacts the domain name space, most notability the WHOIS service. Prior to the GDPR enforcement date, ICANN's contracted parties (Registries and Registrars) expressed concern about their about to comply with their contractual requirement and be GDPR compliant. In light of this concern and the uncertainty around the implications of GDPR on WHOIS, ICANN announced that it would defer action against registries and registrars for noncompliance related to registration data.[1]
The "Cookbook"[edit | edit source]
On 8 March 2018, the ICANN Organization released its "Interim Model for Compliance with ICANN Agreements and Policies in Relation to the European Union's General Data Protection Regulation,"[2] (or The Cookbook) including a description of the interim model, as well as explanation and rationale for its plan. The Cookbook also provides open question about several elements, seeking guidance from the community and DPAs.[3]
Accreditation Model[edit | edit source]
References[edit | edit source]
- ↑ ICANN Contractual Compliance Statement Accessed 2 February 2018
- ↑ Data Protection/Privacy Issues: ICANN61 Wrap-up and Next Steps
- ↑ [1]