Changes

Following the public comment period, the ICANN board resolved to act on fifteen recommendations, placed four recommendations in a pending status while an impact statement was prepared regarding overlapping or dependent policy development processes, referred two recommendations to the [[GNSO]], and rejected two recommendations.<ref name="boardres">[https://www.icann.org/resources/board-material/resolutions-2020-02-25-en#1.a Resolution of the Board], February 25, 2020</ref> One rejected recommendation was out of date, while the board rejected a recommendation to expand the scope of future RDS reviews on the basis that it could be prohibitively expensive, and challenging to find volunteers with the required expertise.<ref name="boardres" /> Following its common practice, the board issued a scorecard regarding the recommendations and the board's proposed response.<ref>[https://www.icann.org/en/system/files/files/resolutions-board-action-rds-whois2-final-recs-25feb20-en.pdf ICANN.org - RDS 2 Scorecard], February 25, 2020</ref>  

Following the public comment period, the ICANN board resolved to act on fifteen recommendations, placed four recommendations in a pending status while an impact statement was prepared regarding overlapping or dependent policy development processes, referred two recommendations to the [[GNSO]], and rejected two recommendations.<ref name="boardres">[https://www.icann.org/resources/board-material/resolutions-2020-02-25-en#1.a Resolution of the Board], February 25, 2020</ref> One rejected recommendation was out of date, while the board rejected a recommendation to expand the scope of future RDS reviews on the basis that it could be prohibitively expensive, and challenging to find volunteers with the required expertise.<ref name="boardres" /> Following its common practice, the board issued a scorecard regarding the recommendations and the board's proposed response.<ref>[https://www.icann.org/en/system/files/files/resolutions-board-action-rds-whois2-final-recs-25feb20-en.pdf ICANN.org - RDS 2 Scorecard], February 25, 2020</ref>  

As of April 2023, eight of the 15 recommendations have been completed. Recommendations 1.1 and 1.2, which call for a forward-looking mechanism to monitor legislative and policy developments, were already addressed by an ICANN org initiative. Recommendation 1.3, which requires demonstrating Board activity on RDS, is being addressed. Recommendation 11.2, which concerns the common interface display of information and updates, is addressed by the [[RDAP]] lookup tool and profiles. Recommendation 15.1, which calls for improvements to ICANN org's project management and implementation reports, was considered complete with the first quarterly report on Specific Reviews. Recommendations LE.1 and LE.2, which identify data gathering on RDS effectiveness for law enforcement agencies, were addressed via an EPDP Phase 2 study for the [[SSAD]] [[ODA]]. Recommendation CC.3 about funding ICANN Contractual Compliance is now part of ICANN’s budgeting and planning process.<ref>[https://www.icann.org/en/system/files/files/specific-reviews-q1-2023-report-31mar23-en.pdf Q1 2023 Specific Reviews Report, ICANN Files]</ref>

As of April 2023, eight of the 15 recommendations have been completed. Recommendations 1.1 and 1.2, which call for a forward-looking mechanism to monitor legislative and policy developments, were already addressed by an ICANN org initiative. Recommendation 1.3, which requires demonstrating Board activity on RDS, is being addressed. Recommendation 11.2, which concerns the common interface display of information and updates, is addressed by the [[RDAP]] lookup tool and profiles. Recommendation 15.1, which calls for improvements to ICANN org's project management and implementation reports, was considered complete with the first quarterly report on Specific Reviews. Recommendations LE.1 and LE.2, which identify data gathering on RDS effectiveness for law enforcement agencies, were addressed via an EPDP Phase 2 study for the [[SSAD]] [[ODA]]. Recommendation CC.3 about funding ICANN Contractual Compliance is now part of ICANN’s budgeting and planning process.<ref>[https://www.icann.org/en/system/files/files/specific-reviews-q1-2023-report-31mar23-en.pdf Q1 2023 Specific Reviews Report, ICANN Files]</ref> Recommendation 3.1 required improvements to web information and educational materials on RDS, and so ICANN updated the registration data look-up tool and the Domain Name Registration Data Policies page. Recommendation CC.2 will be addressed through the implementation of EPDP Phase 1 – Registration Data Policy for gTLDs with publication of the Registration Data Policy in Q2 2023. Recommendation 3.2 will begin as soon as the dependency on outcomes of the EPDP has been resolved. Two recommendations, 10.2 and 12.1, cannot be prioritized or implemented because of the subsequent review team's work (RDS3) and until the next ATRT determines future RDS reviews. Recommendation SG.1 will be implemented through a gap analysis in Q2 2023. The Board also directed ICANN org to include an element for gTLD domain names suspended due to incorrect RDS contact data in contract negotiations, in response to Recommendation 4.1.<ref>[https://www.icann.org/en/system/files/files/specific-reviews-q1-2023-report-31mar23-en.pdf Q1 2023 Specific Reviews Report, ICANN Files]</ref>

==References==

==References==