Proposed gTLD-Registration Data Access Protocol (RDAP) Profile
31 August 2018 23:59 UTC
13 October 2018 23:59 UTC
Staff Report Due
14 December 2018 23:59 UTC
Update (14 September 2018): ICANN organization would like to clarify that it worked with a discussion group of gTLD registries and registrars to create the proposal being put for public comment. In the course of this joint effort, there emerged certain provisions for which all sides could not achieve consensus within the allotted timeline. To that end, and to maintain a reasonable implementation timeline, ICANN org has compiled its view of those differences in a separate document [PDF, 3.19 MB], which is posted along with the proposal from the discussion group of gTLD registries and registrars. ICANN org and the discussion group of gTLD registries and registrars continue their dialogue during the course of the public comment period in an effort to achieve consensus on as many of the remaining issues as possible.
Purpose: The Temporary Specification for gTLD Registration Data adopted by the ICANN Board on 17 May 2018 directed the creation of a gTLD-RDAP Profile(s) as a prerequisite to launching the Registration Data Access Protocol (RDAP) service across the gTLD space. ICANN org has received a proposal from a discussion group of gTLD registries and registrars and is asking the community for input.
Current Status: ICANN org has received a proposal from a discussion group of gTLD registries and registrars for a gTLD-RDAP Profile and is asking the community for input in order to finalize it and proceed with the implementation of RDAP services in the gTLD space.
Next Steps: Following any updates based on input during the public comment period, the gTLD-RDAP Profile will be published and considered for adoption. The gTLD registries and registrars will receive a notice requesting them to implement RDAP according to the gTLD-RDAP Profile(s) and in compliance with SLA and registry reporting requirements within 135 days. The RDAP SLA and registry reporting requirements are still being negotiated.
Section I: Description and Explanation
The Temporary Specification for gTLD Registration Data [PDF, 736 KB] adopted by the ICANN Board on 17 May 2018 requires gTLD registries and registrars to implement a Registration Data Access Protocol (RDAP) service within 135 days of ICANN org requesting implementation. The Temporary Specification also called for a gTLD-RDAP Profile(s) to be developed prior to RDAP deployment.
A discussion group of gTLD registries and registrars (contracted parties) developed a proposal for a gTLD-RDAP Profile consisting of two documents: 1) RDAP Technical Implementation Guide; and 2) RDAP Response Profile. The former aims to provide technical instructions to gTLD registries and registrars on how to implement the RDAP service. The latter intends to map current policy requirements to the RDAP implementation with flexibility to incorporate future policy changes with minimal reengineering.
Although ICANN org provided input to the contracted parties in the development of the two documents, not all the issues raised by ICANN org were addressed. To that end ICANN org has compiled input to the contracted parties' proposal documents [PDF, 3.27 MB] and is making this available for the public to consider.
Section II: Background
Since the 1980s WHOIS has been used in directory services, first for ARPANET users, later for domain name registrant and other related registration data.
On 19 September 2011, the Security and Stability Advisory Committee issued SAC 051, which advised the ICANN community to evaluate and adopt a replacement for the existing domain name registration data access protocol (WHOIS).
On 28 October 2011, the ICANN Board adopted SAC 051 directing staff to produce, in consultation with the community, a roadmap for the coordination of the technical and policy discussions necessary to implement it.
On 4 June 2012, ICANN org published a Roadmap for the coordination of the technical and policy discussions necessary to implement the recommendations outlined in SAC 051.
Also in 2012, The Internet Engineering Task Force (IETF) chartered the Web Extensible Internet Registration Data Service (WEIRDS) working group to develop a protocol to replace WHOIS.
In March 2015, the Web Extensible Internet Registration Data Service (WEIRDS) working group finalized the RFCs defining the Registration Data Access Protocol (RDAP), a standardized replacement for WHOIS.
In September 2015, ICANN org published a proposed draft RDAP operational profile for gTLD registries and registrars for discussion with the community. These discussions took place over the next 10 months, including a public comment period.
On 26 July 2016, ICANN org published a gTLD RDAP profile that included service level and reporting requirements. Subsequently, the gTLD Registries Stakeholder Group requested that ICANN org not use that profile and instead work together on a modified plan to implement RDAP.
On 1 August 2017, the gTLD Registries Stakeholder Group with support from the Registrar Stakeholder Group submitted a proposal to the ICANN org to implement RDAP with a first phase in the form of an RDAP pilot.
On 1 September 2017, the ICANN org accepted the proposal for a voluntary pilot program for and started the first phase. The gTLD registries and registries formed a discussion group that began work on an updated gTLD RDAP profile.
On 17 May 2018, the ICANN Board passed a resolution adopting a Temporary Specification for gTLD Registration Data. As part of that Temporary Specification, gTLD registries and registrars are required to implement a Registration Data Access Protocol (RDAP) service within 135 days of ICANN org requesting implementation. The Temporary Specification also called for a gTLD-RDAP Profile.
In August 2018, ICANN org received a proposal a gTLD-RDAP Profile from the contracted parties.
Section III: Relevant Resources
Documents in the current public comment for community feedback:
Report of Public Comments