Issue

‘Thick’ Whois Policy Development Process

Upcoming Important Dates

Board consideration of Thick Whois PDP recommendations (expected to take place early February 2014)

Summary

ICANN specifies Whois service requirements through its agreements with gTLD Registries and Registrars. Registries have historically satisfied their Whois obligations under two different models, characterized as “thin” and “thick” Whois registries. In a thin registration model the Registry only collects and publishes the minimal information associated with the domain name from the Registrar (such as DNS technical information).  All of the registrant’s contact information is maintained by the Registrar, which publishes it via their own Whois services. In a thick registration model the Registry collects both sets of data (domain name and registrant) from the Registrar and in turn publishes that data via Whois.  The Council initiated a Policy Development Process (PDP) to consider a possible requirement of "thick" Whois for all gTLDs. This issue is one that also affects access to Whois data, which is a law-enforcement-related issue.  The GAC has indicated its interest in both Whois and law enforcement-related issues in previous GAC Communiqués. The PDP WG published its Initial Report for public comment prior to the ICANN Meeting in Durban, which recommended requiring thick Whois for all gTLD registries. Following review of the comments received, the WG finalized its report and submitted it to the GNSO Council on 21 October 2013. The GNSO Council unanimously adopted the recommendation to require Thick Whois for all gTLD registries at its meeting on 31 October 2013.

ALAC Engagement Opportunity Status

The forthcoming WG will be open to all interested parties. Additional opportunities for input will occur through the outreach from the WG to the different SO/ACs for substantive input as well as later on following the publication of the Initial Report for public comment.

 

A public comment forum on the policy recommendations prior to Board consideration was held. Four comments in support of the recommendations were submitted. 

Additional Information

ALAC Related Documents

  • No labels