GDPR AND WHOIS
GDPR and WHOIS edit
The GDPR directly impacts the domain name system, most notability the WHOIS service and data that is collected, escrowed, transferred and displayed via public WHOIS by ICANN's contracted parties (Registries and Registrars). In light of the uncertainty around the implications of GDPR on WHOIS, ICANN announced in February 2018 that it would defer action against registries and registrars for noncompliance related to registration data, as long as it shares its model with ICANN Contractual Compliance and the Global Domains Division.[1]
Processes edit
GDPR enforcement beings 25 May 2018 and there are several processes underway that are either impacted by or in response to the EU Regulation.
Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS (Next-Gen RDS) PDP edit
The Next Generation gTLD RDS to Replace WHOIS PDP Working Group was formed in November 2015 to define the purpose of collecting, maintaining and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate, as the foundation for a new gTLD policy.
The "Cookbook" edit
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]
Calzone Model edit
| Domain Name | |
| Registry Domain ID | |
| Registrar WHOIS Server | |
| Registrar URL | |
| Updated Date | |
| Creation Date | |
| Registry Expiry Data | |
| Registrar Registration Expiration Date Registrar | |
| Registrar IANA ID | |
| Registrar Abuse Contact Email Registrar Abuse Contact Phone Reseller | |
| Domain Status | |
| Domain Status | |
| Domain Status | |
| Registry Registrant ID | |
| Registrant Name | |
| Registrant Organization | |
| Registrant Street | |
| Registrant City | |
| Registrant State/Province | |
| Registrant Postal Code | |
| Registrant Country | |
| Registrant Phone | |
| Registrant Phone Ext | |
| Registrant Fax | |
| Registrant Fax Ext | |
| Registrant Email | |
| Registry Admin ID | |
| Admin Name | |
| Admin Organization | |
| Admin Street | |
| Admin City | |
| ICANN Proposed Interim Model | |
| Legal and Natural persons | |
| Admin State/Province | Do not display |
| Admin Postal Code | Do not display |
| Admin Country | Do not display |
| Admin Phone | Do not display |
| Admin Phone Ext | Do not display |
| Admin Fax | Do not display |
| Admin Fax Ext | Do not display |
| Admin Email | Anonymized email or web form |
| Registry Tech ID | Do not display |
| Tech Name | Do not display |
| Tech Organization | Do not display |
| Tech Street | Do not display |
| Tech City | Do not display |
| Tech State/Province | Do not display |
| Tech Postal Code | Do not display |
| Tech Country | Do not display |
| Tech Phone | Do not display |
| Tech Phone Ext | Do not display |
| Tech Fax | Do not display |
| Tech Fax Ext | Do not display |
| Tech Email | Anonymized email or web form |
| Name Server | Display |
| Name Server | Display |
| DNSSEC | Display |
| DNSSEC | Display |
| URL of ICANN Whois Inaccuracy Complaint Form | Display |
| >>> Last update of WHOIS database | Display |
Accreditation Model edit
References edit
- ↑ ICANN Contractual Compliance Statement Accessed 2 February 2018
- ↑ Data Protection/Privacy Issues: ICANN61 Wrap-up and Next Steps
- ↑ [1]