Versions Compared

Old Version 5

changes.mady.by.user Alice Jansen

Saved on

compared with

New Version Current

changes.mady.by.user Alice Jansen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image Removed


RDS-WHOIS2 Implementation - Status

:

<<included in the Pilot for Prioritization>> - see https://www.icann.org/en/blogs/details/now-published--icanns-draft-planning-prioritization-framework-02-03-2022-en for more information

of 15 Recommendations

Complete 

14 Recommendations

3 Recommendations for which implementation is complete

: 1.1, 1.2,

CC

1.3

3 Recommendation for which implementation is partially complete:3.

, 3.1, 3.2, 10.2, 12.1, 11.2, 15.1, 

6 Recommendations which are in Implementation design: 1.3, 3.2,

LE.1, LE.2, SG.1, CC

.12 Recommendations for which implementation is on hold: 10

.2,

12.1

CC.3

In progress  

1 Recommendation

to be handled through EPDP Phase 1 Implementation: CC.2

: CC.1 

Not started 

N/A


Quarterly Updates


Status
colourGrey
titleAUG 24

Image Added

Progress by Quarter


Status
colourGrey
titleAPR 2022

Status
titleJUN 2022

Status
colourGrey
titleSept 2022

Status
colourGrey
titleDEC 22
Q4 2022

Status
colourGrey
titleMar 23
Q1 2023

Status
colourGrey
titleJUNE 23
Q2 2023

Status
colourGrey
titleSEPT 23
Q3 2023

Status
colourGrey
titleDEC 23
Q4 2023

Status
colourGrey
titleMAR 24
Q1 2024

Status
colourGrey
titleJUn 24
Q2 2024

Status
colourGrey
titleSEPT 24
Q3 2024

Complete37788888121214
In progress62222333331
Not Started66655444000



Rec #

Implementation Status

Priority level assigned by the community

(where P1 corresponds to the highest priority and P4 to the lowest - see here for more information)

Description

Notes


R1.1

Complete

n/a

Rec #

Status

Description

Implementation Update as of 17 February 2022

R1.1

Completed

To ensure that RDS (WHOIS) is treated as a strategic priority,

the ICANN Board

the ICANN Board should put into place a forward-looking mechanism to monitor possible impacts on the RDS (WHOIS) from legislative and policy developments around the world.

The corresponding activities are already part of ICANN's plans

See implementation documentation.

R1.2

Complete

Completed

n/a

To support this mechanism,

the ICANN Board

the ICANN Board should instruct

the ICANN org

the ICANN org to assign responsibility for monitoring legislative and policy developments around the world and to provide regular updates to

the ICANN Board.

the ICANN Board.

See implementation documentation

ICANN org has already assigned responsibility for monitoring legislative and policy developments around the world and for providing regular updates to the ICANN Board

.

R1.3

In Progress

Complete

P4

The ICANN Board

The ICANN Board

, in drafting the charter of a Board working group on RDS, should ensure the necessary transparency of the

group’s

group's work, such as providing records of meetings and meeting minutes, to enable future review of its activities.

The work of the previously chartered Board Working Group on Registration Directory Services has been integrated into the work of the Board Caucus on General Data Protection Regulation (GDPR) / Expedited Policy Development Process (ePDP). Work is underway to determine which measures are needed to ensure that appropriate information on Caucus group activities is provided to the community

See implementation documentation.

R3.1

Partially Completed

Complete

P4

The ICANN Board should direct ICANN org

The ICANN Board should direct ICANN org

to update all of the information related to RDS (WHOIS) and by implication other information related to the registration of second-level gTLDs. The content should be revised to make the information readily accessible and understandable, and it should provide details of when and how to interact

with ICANN org

with ICANN org or contracted parties. [...]

ICANN has updated the content and navigation of the registration data look up tool (i.e., the WHOIS Portal referred to in the RDS-WHOIS2 Review Team Final Report). The information formerly contained on that page has been reorganized and now appears on the Domain Name Registration Data Policies and Related Requirements page, which contains information regarding existing policies and requirements and ongoing policy development work. ICANN Contractual Compliance has included the links to this information on their Complaint Submission page found here https://www.icann.org/compliance/complaint.

See implementation documentation.

R3.2

In Progress

Complete

N/A

With community input,

the ICANN Board should instruct ICANN org

the ICANN Board should instruct ICANN org to identify groups outside of those that routinely engage

with ICANN org

with ICANN org, and these should be targeted through RDS (WHOIS) outreach. An RDS (WHOIS) outreach plan should then be developed, executed, and documented. [...]

As the GNSO’s Expedited Policy Development Process on Temporary Specification for gTLD Registration Data (EPDP) and the Registration Data Access Protocol (RDAP) phased implementation could impact the information or the messaging to be delivered by ICANN to new target groups, work will begin as soon as the dependency on outcomes of the EPDP has been resolved.

See implementation documentation. 

R10.2

On Hold

Complete

N/A

Reviewing the effectiveness of the implementation of WHOIS1 Recommendation 10 should be deferred.

The ICANN Board

The ICANN Board should recommend that review be carried out by the next RDS (WHOIS) Review Team after the Privacy and Proxy Services Accreditation Issues (PPSAI) policy is implemented.

The Board approved the ATRT3 recommendation to suspend any further RDS Reviews pending the outcome of the next ATRT, subject to prioritization and community agreement to the related Bylaw changes

See implementation documentation.

R11.2

Complete

Partially Completed

The ICANN Board should direct ICANN org

P4

The ICANN Board should direct ICANN org to ensure that the common interface displays all applicable output for

each gTLD domain

each gTLD domain name registration as available from contracted parties, including multiple versions when the outputs from registry and registrar differ. The common interface should be updated to address any policy or contractual changes to maintain full functionality.

Registration Data Access Protocol (RDAP) was designed with the ability to be updated to address any future policy or contractual changes. Regarding the common interface displays, ICANN org continues to review to determine resources required to make the recommended updates, including whether resources are required to program and/or build any necessary software.

See implementation documentation.

R12.1

On Hold

Complete

N/A

Reviewing the effectiveness of the implementation of Recs #12-14 should be deferred.

The ICANN Board

The ICANN Board should recommend that review to be carried out by the next RDS Review Team after RDAP is implemented, and the translation and transliteration of the registration data launches.

The Board approved the ATRT3 recommendation to suspend any further RDS Reviews pending the outcome of the next ATRT, subject to prioritization and community agreement to the related Bylaw changes

See implementation documentation.

R15.1

Complete

Partially Completed

The ICANN Board

P4

The ICANN Board should ensure that implementation of RDS-WHOIS2 Review Team recommendations is based on best practice project management methodology, ensuring that plans and implementation reports clearly address progress, and applicable metrics and tracking tools are used for effectiveness and impact evaluation.

ICANN org’s newly created Implementation Operations function is deploying a foundational structure that allows for the work of implementation to be carried out thoroughly, effectively, and in a sustainable manner. In addition to the use of an improved project management system, ICANN org’s Implementation Operations function has also designed enhanced tools for its implementation planning related work and is working on developing a more frequent and detailed reporting mechanism.

See implementation documentation.

LE.1

Complete

In Progress

P4

The ICANN Board should resolve that ICANN org

The ICANN Board should resolve that ICANN org

conduct regular data gathering through surveys and studies to inform a future assessment of the effectiveness of RDS (WHOIS) in meeting the needs of law enforcement. This will also aid future policy development (including the current Temporary Specification

for gTLD Registration

for gTLD Registration Data Expedited Policy Development Process and related efforts).

Implementation of this recommendation could not be completed in time to aid EPDP Phase 2, for which a final report was issued in August 2020. However, ICANN org, in consultation with the GNSO, will identify an appropriate timeline for any surveys and studies to inform future assessments of the effectiveness of RDS in meeting needs of law enforcement

See implementation documentation.

LE.2

In Progress

The ICANN Board

Complete

P4

The ICANN Board should consider conducting comparable surveys and/or studies (as described in LE.1) with other RDS (WHOIS) users working with law enforcement on a regular basis.

Implementation of this recommendation could not be completed in time to aid EPDP Phase 2, for which a final report was issued in August 2020. However, ICANN org, in consultation with the GNSO, will identify an appropriate timeline for any surveys and studies of users working with law enforcement on a regular basis. Additionally, ICANN org continues to review whether this recommendation could be paired with the use of other survey and feedback mechanisms across ICANN org to ensure there is a coordinated process for surveying the community and stakeholders.

See implementation documentation.

SG.1

Complete

In Progress

P2

The ICANN Board

The ICANN Board

should require that

the ICANN org

the ICANN org, in consultation with data security and privacy expert(s), ensure that all contracts with contracted parties (to include Privacy/Proxy services when such contracts exist) include uniform and strong requirements for the protection of registrant data and

for ICANN to

for ICANN to be notified in the event of any data breach. The data security expert(s) should also consider and advise on what level or magnitude of breach warrants such notification. [...]

This will be included in the next round of contractual negotiations with the contracted parties, insofar as it relates to ICANN receiving notification of data breaches in circumstances that threaten to undermine the stability, security, and resiliency of the Internet’s DNS

See implementation documentation.

CC.1

In

ProgressThe ICANN Board

progress

P4

The ICANN Board should initiate action intended to ensure

that gTLD domain

that gTLD domain names suspended due to RDS (WHOIS) contact data which the registrar knows to be incorrect, and that remains incorrect until the registration is due for deletion, should be treated as follows: (1) The RDS (WHOIS) record should include a notation that the domain name is suspended due to incorrect data; and (2) Domain names with this notation should not be unsuspended without correcting the data.

This recommendation was approved in part and is to be included in the next round of contractual negotiations with the contracted parties. The Board passed through this recommendation to the Generic Names Supporting Organization (GNSO) Council to consider as a future policy development process. In its 3 July 2020 response, GNSO Council indicated that: “it will ensure Recommendation CC.1 is included for consideration in due course, if this item has not been addressed in the next round of contractual negotiations between ICANN org and the Contracted Parties (as directed by the Board)”.

N/A

CC.2

In Progress

The ICANN Board

Complete

N/A

The ICANN Board should initiate action intended to ensure that

all gTLD domain

all gTLD domain name registration directory entries contain at least one full set of either registrant or admin contact details comparable to those required for new registrations under the 2013 Registrar Accreditation Agreement (RAA) (or any subsequent version thereof) or applicable policies.

This recommendation is part of EPDP Phase 1 implementation

See implementation documentation.

CC.3

Complete

Completed

n/a

The ICANN Board

The ICANN Board

should take steps to ensure

that ICANN Contractual

that ICANN Contractual Compliance is adequately resourced factoring in any increase in work due to additional work required due to compliance with GDPR or other legislation/regulation.

This recommendation is already included in the existing budgeting and planning process. Compliance will continue to request required resources as part of the existing planning process

See implementation documentation.