CL&D implementation only specifies one date, there is no early bound stated for when registries can implement the requirements, other than that it must be done by August 1. Is there an "earliest by" date for implementation or are all registries expected to implement the requirements on exactly August 1?
There is no “earliest by” or “not to be deployed before” date for the CL&D policy implementation. The policy effective date is 1 August 2017 but registries may implement before this date.
Do the Registrar Abuse Contact Email and Registrar Abuse Contact phone number fields need to be populated or just presented/included? Can null or empty fields be displayed and still be considered compliant?
The Registry Registration Data Directory Services Consistent Labeling and Display Policy requires that Registrar Abuse Contact Email and Registrar Abuse Contact Phone fields be displayed with data. They cannot be empty.
The CL&D Policy, allows registry operators to use additional RDDS fields but the list of these additional fields need to be first submitted to ICANN. How should this list be provided to ICANN?
Per section 12 in the CL&D Policy, prior to deployment, if additional fields are used in the RDDS output the Registry Operator SHALL provide the list of all additional RDDS fields to ICANN. Registry Operator SHALL provide to ICANN any changes to the list of additional RDDS fields prior to deploying such changes. Please use this template to the template provided in the Documentation section to list each additional RDDS field and indicate the corresponding data type and provide the completed document to ICANN by creating a new case in the GDD Portal or email to email@example.com.
Who should I contact if I have questions?
Submit questions via firstname.lastname@example.org with the following subject heading “Inquiry – Thick Whois Transition Policy.”