1. Implementation Review Team Meeting
Thick WHOIS Policy
Implementation Review Team Meeting
15 March 2017

2. Agenda 1 2 3 4 5 6 Project Background Project Status Project Schedule
Project Deliverables
Next Steps

3. Thick Whois Thick WHOIS Policy Recommendations – Background
ICANN board adopted GNSO Consensus Policy recommendations requiring all gTLD registries to provide thick WHOIS services with a consistent labeling and display (February 2014).
GNSO PDP Working Group concluded requiring Thick WHOIS:
Would improve stability of and access to WHOIS data
May reduce acquisition and processing costs for consumers of WHOIS data
Would provide a more level playing field between registry providers

4. Thick Whois Thick WHOIS Policy Recommendation – Three Parts
The “thick” WHOIS Consensus Policy recommendations state three deliverables:
Part 1: All gTLDs must provide thick WHOIS. Currently only 3 registries, COM, .NET and .JOBS, are thin.
Part 2: The consistent labeling and display of Whois output for all gTLDs.
Part 3: A legal review of law applicable to the transition of data from thin to thick that wasn’t considered by the Expert Working

5. Thick Whois Thick WHOIS – Thin v. Thick
WHOIS has two sets of data; domain name data which is technical information such as name servers and expiry date; and registrant data which contains registrant contact information. Registrars collect domain name data and registrant data.
Thin registries only collect, store and manage domain name data from the registrar.
Thick registries collect, store and manage both domain name and registrant contact data from the registrar.

6. Thick Whois Thick WHOIS – Implementation Timeline
April 2014 – ICANN org began implementation with support from the Implementation Review Team.
June 2015 – Part 3, the Legal Review Memorandum, was published.
October Two Consensus Policies were published for public comment.
February Both Policies have been published as agreed with the Implementation Review Team.
Registry Registration Data Directory Services Consistent Labeling and Display Policy
Thick RDDS (Whois) Transition Policy for .COM, .NET and .JOBS

7. Thick Whois Thick WHOIS Policy Effective Dates
Implementation activities have begun since the announcement on 1 February 2017 to meet the following effective dates
1 August 2017: Consistent Labeling and Display must be implemented
1 May 2018: Thick WHOIS for new registrations must be implemented
1 February 2019: The transition of thick registration data for existing registrations must be implemented

8. CL&D Implementation – Timeline
Policy effective date announced
6 months
Policy Implementation
Policy effective date
12 months
6 months
18 months
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
2017
2018
2019

9. CL&D Policy Implementation Key Deliverables
By 1 August 2017
Registry Operator MUST update the name of keys in the output of the domain name, name server, and registrar objects
Registrar provides additional CL&D data elements
Registrar Abuse Contact
Registrar Abuse Contact Phone
ICANN updates WHOIS output verification tool used by PDT and Compliance
Registries to notify registrars on next steps

10. Transition Policy Implementation – Timeline
Policy effective date announced
6 months
Registries update Registry systems
New Registrations
Registry OT&E opens
Optional thick (Registry production systems)
12 months
Registrars transition new registrations from thin to thick
Required thick (Registry production systems)
Policy effective date for new registrations
6 months
Registries prepare for transition
Existing Registrations
Registry OT&E opens
Registrars
transition data
from thin to
thick
3 months
Registrars prepare for transition
18 months
Policy effective date for existing registrations
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
2017
2018
2019

11. Transition Policy Implementation Key Deliverables
From 1 February 2017 to 1 May 2017
Registry Operator provides
Documentation reflecting the system changes necessary to support registrars to migrate registration data for Existing Domain Names
Operating Test Environments (OT&E)
An EPP mechanism
An alternative bulk transfer mechanism
Define and design the Transition Progress Metrics with the IRT
ICANN reports progress status to the IRT

12. Transition Policy Implementation Key Deliverables
From 1 May 2017 to 1 August 2017
Registrars review the documentation provided by RO and tests the migration of registration data for Existing Domain Names using the OT&E working closely with the RO
Complete definition of the Transition Progress Metrics with the IRT
By 1 August 2017
Registry Operators deploy transfer mechanism for registrars to migrate registration data for Existing Domain Names
an EPP mechanism
an alternative bulk transfer mechanism

13. Transition Policy Implementation Key Deliverables
From 1 August 2017 to 1 February 2019
Registrars migrate to the relevant Registry Operator all required fields of Existing Domain Names that are available in the Registrar database that enable the Registry Operator to comply with WHOIS (available via port 43) and web-based directory services requirements
Registry Operators provide Transition Progress Metrics to each registrar at minimum,
Monthly by 23:59 UTC of the first day of the next month.
The first metrics will be on 1 Sep. 2017
Registry Operators provide to ICANN all Transition Progress Metrics for all registrars at minimum,

14. Next Steps
Plan and execute the policy implementation working closely with the IRT to ensure successful implementation to meet the effective dates
Continued coordination and collaboration of near-term deliverables; may involve subgroup(s) to work out the details
Report project progress status to the IRT as needed
Next IRT Meetings:
Tuesday 18 April 2017
Monthly scheduled and adjusted; maintained on the Thick WHOIS IRT Community Wiki space

15. Registration Directory Service (RDS) Review: WHOIS
The RDS Review Team “Call for Volunteers” has been extended.
The new deadline for applications is March 20, 2017.
Visit ”Announcements on ICANN.org to learn how to apply or follow this link:  
This is a simpler agenda slide, the outline for your presentation.

16. Engage with ICANN Thank You and Questions Reach me at:
Website: icann.org
twitter.com/icann
gplus.to/icann
facebook.com/icannorg
weibo.com/ICANNorg
You can adjust the /web address to whichever or web address is best suited to your presentation. This should be your final slide.
linkedin.com/company/icann
flickr.com/photos/icann
youtube.com/user/icannnews
slideshare.net/icannpresentations

17. Thick Whois Thick WHOIS Policy Overview
Registries and registrars satisfy their WHOIS obligations using different service models: ”thin” and “thick” Whois registries.
A thin registries only stores and manages the information associate with the domain name
A thick registry includes information about the registrant and contacts also.
The ICANN board adopted a recommendation from the GNSO to make all gTLDs WHOIS data thick and consistent; henceforth the GDD policy implementation team working with the Implementation Review Team has published two policy implementations:
Registry Registration Data Directory Services Consistent Labeling and Display Policy
Thick RDDS (WHOIS) Transition Policy for .COM, .NET and .JOBS
Talking points and q&a
Who manages the thin and thick data?
Thin (Registration): domain name for which the Registry Operator maintains and provides only technical information (e.g., name servers, statuses, creation date) and the Sponsoring Registrar associated with the domain name. Contact information for these domain names is maintained by the sponsoring Registrar.
Thick (Registration): domain name for which the Registry Operator stores all the registration data elements (available via port 43) and web-based directory services requirements described in Section 1 of Specification 4 of the ("Base Registry Agreement") and the Registry Registration Data Directory Services Consistent Labeling and Display Policy.
When were the policy posted? Wasn’t there a RfR for CL&D?
Revised CL&D policy public comment: 21 October 2016 to 12 December 2016
Original policy was posted on 26 July 2016 but after receiving RfR in August 2016 from RySG the policy was revised to remove RDAP from the policy document per the request so the RDAP can be handled in a contractual avenue rather than policy
Transition policy public comment: 26 October 2016 to 15 December 2016
Where are these [policies effective?
Proposed policy effective dates are as follows but will depend on the comments received.
1 August 2017: Consistent Labeling and Display
1 May 2018: Thick Whois for new registration
1 February 2019: Transition from thin to thick for .com, .net and .jobs
Timeline
2012 March: PDP process launched
2013 June/Aug: PDP WG Initial Report public comment
2013 October: PDP WG final report, GNSO Council adapts
2014 February: Board resolution
2016 October: draft policies open for public comment