SSAC Advisory Regarding Access to Domain Name Registration Data (R-1C)
| Date Issued | Document | Reference ID | Current Phase | ||||||
|---|---|---|---|---|---|---|---|---|---|
| SSAC Advisory Regarding Access to Domain Name Registration Data (R-1C) | SAC101v2 |
|
DESCRIPTION
The ICANN Board, ICANN Organization, and ICANN community must solve long-deferred problems regarding domain registration data and access to it. SSAC recommends that the ICANN Board oversee the creation and execution of a plan that accomplishes the following interconnected tasks in a coordinated fashion, with timely deadlines. The creation and execution of this plan should be a top priority of the ICANN Board, ICANN Organization, and ICANN community.
C. The remaining thin gTLD registries should be required to move to thick status, per the Thick WHOIS Consensus Policy and Board Resolution 2014.02.07.08.
DEPENDENCIES
Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations. Deferred pending work in the Implementation Review Team.
STATUS UPDATES
| Date | Phase | Type | Status Updates |
|---|---|---|---|
| Phase 4 | Dependencies | Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations. Deferred pending work in the Implementation Review Team. |
| Phase 4 | Phase Change | Now in Phase 4: Deferred |
| Phase 2 | Phase Update | Deferred pending work in the Implementation Review Team. |
| Phase 4 | Phase Update | This item continues to be deferred. It is also subject of correspondence (https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-29jan21-en.pdf) between the GNSO Council and the Board, following a motion (https://community.icann.org/display/gnsocouncilmeetings/Motions+21+January+2021) passed by the GNSO Council. The topic will be parsed and placed in Phase 4 | Deferred. |
| Phase 4 | Phase Update | On 7 November 2019, the Board passed a resolution deferring contractual compliance enforcement of the Thick WHOIS Consensus Policy, pending: - the gTLD Registration Data Policy Implementation Review Team (IRT) completes its review and establishes an implementation timeline estimate of the Expedited Policy Development Process (EPDP) Team's recommendations as adopted by the ICANN Board on 15 May 2019; - ICANN org and the IRT provide the GNSO Council with the required information on the impacts of the EPDP Team's recommendations on existing policies and procedures (including the Thick WHOIS Transition policy), and - the GNSO Council makes a determination on whether to take action on updates to relevant policies and procedures (which could include additional policy work, guidance, or other actions to be determined) impacting the Thick WHOIS Transition Policy. Based on this, item (c) can be deferred pending the above. |
| Phase 4 | AP Feedback | SSAC acknowledged the June 2019 notification and agreed with the ARR Team's classification of moving this item to "Phase 4 | Implement". |
| Phase 4 | Phase Update | On 23 June 2019 the ICANN Board considered SAC101v2 and accepted Recommendation 1 and directed the ICANN President and CEO, or his designee(s), to create a plan that reports on ICANN org's and the community's progress toward the four objectives identified in the advice (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "In accepting advice item one, the Board further notes that the creation of an "accredited RDDS access program," is a topic under discussion in the EPDP Phase 2. The Board cannot dictate outcomes of PDPs. Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations." This advice item is now in Phase 4 | Implement as of 23 June 2019. |
| Phase 4 | Phase Change | Now in Phase 4: Implement |
| Phase 3 | Board Update | Resolved (2019.06.23.04), the Board accepts advice item one in SAC101 version 2 relating to creation and execution of a plan to accomplish four objectives identified in the advice, and directs the ICANN President and CEO, or his designee(s), to create a plan that reports on ICANN org's and the community's progress toward the four objectives identified in the advice. See full resolution at https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-open-session-23-06-2019-en#1.c. |
| Phase 3 | Phase Change | Now in Phase 3: Evaluate & Consider |
| Phase 2 | AP Feedback | SSAC confirmed understanding. |
| Phase 2 | Board Understanding | The ICANN organization understands SAC101v2 Recommendation 1 to mean that the ICANN Board should oversee the creation and execution of a plan by the ICANN Board, ICANN org and ICANN community that accomplishes the following tasks in a coordinated way and with timely deadlines: A. A domain registration data policy that includes statements of purposes for the collection and publication of the data. B. The ICANN Board and the ICANN Organization should require contracted parties to migrate from using the WHOIS protocol to using the RDAP protocol. C. The ICANN Board and the ICANN Organization should require the remaining thin gTLD registries to move to thick status per the Thick WHOIS Consensus Policy and Board Resolution 2014.02.07.08. D. The ICANN Board should support the creation of an accredited RDDS access program, with the ICANN Organization ensuring the creation, support of, and oversight of the supporting technical access mechanism. |
| Phase 2 | Phase Change | Now in Phase 2: Understand |
| Phase 1 | Phase Update | ICANN org acknowledged receipt of SAC101v2. |
| Phase 1 | Phase Update | SSAC published SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data Link: https://www.icann.org/en/system/files/files/sac-101-v2-en.pdf Version 2 of SAC101 was published to reflect evolving circumstances related to ICANN’s Temporary Specification for gTLD Registration Data, and the ongoing Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Version 1 of SAC101 has been retired and version 2 is authoritative. |