Thick WHOIS Migration Part two, The Draft V5

As I am on a roll this morning lets’ zoom in the Thick WG latest draft and provide it with some early comments and background detail. thick-transition-policy-draft-v5-20160929-clean-with-comment

Redline version in full:

Thick Whois Transition Policy for .COM, .NET and .JOBS

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, and “MAY” in this document are to be interpreted as described in RFC 2119, which is available at http://www.ietf.org/rfc/rfc2119.txt.

Scope:

This Policy SHALL apply to the Registry Operators for the .COM, .NET and .JOBS gTLDs, as well as all Registrars sponsoring domain name registrations in the .COM, .NET and .JOBS gTLDs.

Definitions:

  • 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 only by the sponsoring Registrar.
  • Thick (Registration): domain name for which the sponsoring Registrar provides a copy of the associated contact information to the Registry Operator. Registry Operator maintains the technical information (e.g., name servers, statuses, creation date) and the sponsoring Registrar associated with the domain name. Contact information for the domain name is maintained by the sponsoring Registrar.
  • Existing Domain Name: domain name created, or in pendingCreate status, before 1 May 2018.
  • Transition Progress Metrics: metrics created by Registry Operator and communicated regularly to Registrars and ICANN to allow measurement of progress of the transition from Thin to Thick, including at least the total number of domains managed by Registrar, number and percentage of domain with contact objects attached
  1. Effective Dates:
    1. All new domain name registrations MUST be submitted as Thick starting on 1 May 2018 at the latest.
    2. All registration data for Existing Domain Names MUST have been migrated from Thin to Thick by 1 February 2019.
  2. The following requirements apply to Registry Operators only:
    1. Registry Operator MUST deploy an EPP mechanism by 1 August 2017 for registrars to migrate registration data for Existing Domain Names (i.e., the transition from Thin to Thick).
    2. Registry Operator MUST upon request provide an alternative bulk transfer mechanism by 1 February 2018 for registrars to migrate data for Existing Domain Names (i.e., the transition from Thin to Thick). The request MUST be made by 1 August 2017.
    3. By 1 May 2017, Registry Operator MUST provide to applicable Registrars and ICANN, documentation reflecting the system changes necessary to support the requirements of Sections 2.1 concerning relevant Operating Test Environments (OT&E) available to Registrars and by 1 August 2017 for Section 2.2.
    4. Starting 1 August 2017, Registry Operator MUST support all contact commands specified in RFC5733 as described in this provision. The EPP contact fields <contact:id>, <contact:postalInfo>, and <contact:authInfo> will be REQUIRED by the Registry Operator. Registry Operator MUST accept but MUST NOT require all other registration data elements that enable it to comply with WHOIS (available via port 43) and web-based directory services requirements described in Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”) and the Registry Registration Data Directory Services Consistent Labeling and Display Policy.
    5. Starting 1 May 2018, Registry Operator MUST require Thick Registration data for an EPP domain object <create> command as described in this provision. Registry Operator MUST require all registration data elements that enable it to comply with WHOIS (available via port 43) and web-based directory services requirements described in Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”) and the Registry Registration Data Directory Services Consistent Labeling and Display Policy.
    6. Between 1 August 2017 and 1 February 2019, Registry Operator SHALL provide Transition Progress Metrics to each registrar at minimum Monthly by the first day of the next month at 23:59 UTC.
    7. Between 1 August 2017 and 1 February 2019, Registry Operator SHALL provide to ICANN all Transition Progress Metrics for all registrars at minimum Monthly by the first day of the next month at 23:59 UTC.
    8. Registry Operator SHALL implement the requirements of the Registry Registration Data Directory Services Consistent Labeling and Display Policy (“CL&D Policy”) in conjunction with Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”) by 1 August 2017.
    9. Starting 1 May 2018, Registry Operator MUST comply with WHOIS (available via port 43) and web-based directory services requirements described in Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”) and the Registry Registration Data Directory Services Consistent Labeling and Display Policy for other than Existing Domain Names.
    10. Between 1 August 2017 and 1 February 2019, for Existing Domain Names, for the following RDDS Output fields where no data exists in the Shared Registration System (SRS), the Registry Operator MAY treat the following RDDS fields as Optional as described in section 1.2 of the “RDAP Operational Profile for gTLD Registries and Registrars” if implementing RDAP, and in the case of Whois port 43 and Web-Whois, as described in clarification 1 of the “Advisory: Clarifications to the Registry Agreement, and the 2013 Registrar Accreditation Agreement (RAA) regarding applicable Registration Data Directory Service (Whois) Specifications”:
  • Registry Registrant/Admin/Tech ID
  • Registrant/Admin/Tech Name
  • Registrant/Admin/Tech Street
  • Registrant/Admin/Tech City
  • Registrant/Admin/Tech Country
  • Registrant/Admin/Tech Phone
  • Registrant/Admin/Tech Email
    1. The “Billing” contact is optional.  Registry Policy may define if it is required, optional or not supported.  If supported the Billing contact information must be displayed as described in the “Advisory: Clarifications to the Registry Agreement, and the 2013 Registrar Accreditation Agreement (RAA) regarding applicable Registration Data Directory Service (Whois) Specifications” (section 22).
  1. The following requirements apply to Registrars only:
    1. Between 1 August 2017 and 1 February 2019, Registrars MUST 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 described in Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”) and the Registry Registration Data Directory Services Consistent Labeling and Display Policy.
    2. Registrars MAY provide complete Thick Registration data to Registry Operator that enable it to comply with WHOIS (available via port 43) and web-based directory services requirements described in Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”) and the Registry Registration Data Directory Services Consistent Labeling and Display Policy, upon creation of new domain name registrations starting 1 August 2017.
    3. Registrars MUST provide complete Thick Registration data to Registry Operator that enable it to comply with WHOIS (available via port 43) and web-based directory services requirements described in Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”) and the Registry Registration Data Directory Services Consistent Labeling and Display Policy, upon creation of new domain name registrations starting 1 May 2018.

Implementation Notes

  1. Where a conflict exists between local privacy laws and requirements included in this Policy, ICANN’s Procedure for Handling WHOIS Conflicts with Privacy Laws is available for Registry Operators and Registrars

 

Theo Geurts ICANN IRT member

Completely and totally not related music video but still one helluva song.