Jump to content

GDPR AND WHOIS: Difference between revisions

From ICANNWiki
← Older edit
VisualWikitext
Dustin Loup (talk | contribs)
Bureaucrats, Interface administrators, lookupuser, staff, Administrators, translator
11,770 edits
No edit summary
Dustin Loup (talk | contribs)
Bureaucrats, Interface administrators, lookupuser, staff, Administrators, translator
11,770 edits
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 6: Line 6:


===Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS (Next-Gen RDS) PDP===
===Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS (Next-Gen RDS) PDP===
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 [[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.
 
Despite years of work on the WHOIS reform, the opportunity for


===The "Cookbook"===
===The "Cookbook"===
Line 12: Line 14:


====Calzone Model====
====Calzone Model====
{| class="mw-collapsible mw-collapsed" cellpadding="0" cellspacing="0" border="0" style="margin-left:15px;"
 
!WHOIS Data Fields
!Legal and Natural persons
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;"|Domain Name
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registry Domain ID
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrar WHOIS Server
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrar URL
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Updated Date
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Creation Date
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registry Expiry Data
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrar Registration Expiration Date Registrar
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrar IANA ID
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrar Abuse Contact Email
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrar Abuse Contact Phone Reseller
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Domain Status
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Domain Status
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Domain Status
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|Registry Registrant ID
|Do not display
|-
|Registrant Name
|Do not display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrant Organization
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|sytle="border: 1px solid #E0E0E0;background-color: #FF5E57"|Registrant Street
|sytle="border: 1px solid #E0E0E0;background-color: #FF5E57"|Do not display
|-
|sytle="border: 1px solid #E0E0E0;background-color: #FF5E57"|Registrant City
|sytle="border: 1px solid #E0E0E0;background-color: #FF5E57"|Do not display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrant State/Province
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|sytle="border: 1px solid #E0E0E0;background-color: #FF5E57"|Registrant Postal Code
|sytle="border: 1px solid #E0E0E0;background-color: #FF5E57"|Do not display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Registrant Country
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|Registrant Phone
|Do not display
|-
|Registrant Phone Ext
|Do not display
|-
|Registrant Fax
|Do not display
|-
|Registrant Fax Ext
|Do not display
|-
|Registrant Email
|Anonymized email or web form 
|-
|Registry Admin ID
|Do not display
|-
|Admin Name
|Do not display
|-
|Admin Organization
|Do not display
|-
|Admin Street
|Do not display
|-
|Admin City
|Do not display
|-
|ICANN Proposed Interim Model
|Do not display
|-
|Legal and Natural persons
|Do not display
|-
|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
|- 
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Name Server
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Name Server
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|DNSSEC
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|DNSSEC
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|URL of ICANN Whois Inaccuracy Complaint Form
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|-
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|>>> Last update of WHOIS database
|style="border: 1px solid #E0E0E0;background-color: #b2ffb2;|Display
|}
===Accreditation Model===
===Accreditation Model===


==References==
==References==

Latest revision as of 19:12, 9 April 2018

GDPR and WHOIS[edit | edit source]

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 | edit source]

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 | edit source]

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.

Despite years of work on the WHOIS reform, the opportunity for

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]

Calzone Model[edit | edit source]

Accreditation Model[edit | edit source]

References[edit | edit source]

  1. ↑ ICANN Contractual Compliance Statement Accessed 2 February 2018
  2. ↑ Data Protection/Privacy Issues: ICANN61 Wrap-up and Next Steps
  3. ↑ [1]
Retrieved from "https://icannwiki.org/index.php?title=GDPR_AND_WHOIS&oldid=1104437"