Changes

The Board approved the implementation plan in January 2020.<ref>[https://www.icann.org/resources/board-material/resolutions-2020-01-26-en#1.e ICAN Board Resolution - CCT Implementation Plan], January 26, 2020</ref> Updates on the implementation of those recommendations were provided by [[Maarten Botterman]] on the ICANN Blog in August 2020<ref>[https://www.icann.org/en/blogs/details/an-update-on-the-competition-consumer-trust-and-consumer-choice-cct-review-20-8-2020-en ICANN.org Blog - An Update on the CCT Review], August 20, 2020</ref> As of May 2021, there were not a proposed implementation plan for the recommendations approved in the October 2020 board resolution.<ref>[https://www.icann.org/resources/reviews/specific-reviews/cct#Implementation%20of%20CCT%20Recommendations ICANN.org - CCT Home: Implementation of Recommendations]</ref>

The Board approved the implementation plan in January 2020.<ref>[https://www.icann.org/resources/board-material/resolutions-2020-01-26-en#1.e ICAN Board Resolution - CCT Implementation Plan], January 26, 2020</ref> Updates on the implementation of those recommendations were provided by [[Maarten Botterman]] on the ICANN Blog in August 2020<ref>[https://www.icann.org/en/blogs/details/an-update-on-the-competition-consumer-trust-and-consumer-choice-cct-review-20-8-2020-en ICANN.org Blog - An Update on the CCT Review], August 20, 2020</ref> As of May 2021, there were not a proposed implementation plan for the recommendations approved in the October 2020 board resolution.<ref>[https://www.icann.org/resources/reviews/specific-reviews/cct#Implementation%20of%20CCT%20Recommendations ICANN.org - CCT Home: Implementation of Recommendations]</ref>

By April 2023, five out of the 17 Board-approved CCT Recommendations were considered complete. Recommendation 16 called for ongoing data collection on the relationship between registry operators, registrars, and DNS security abuse. ICANN org operates the Domain Abuse Activity Reporting ([[DAAR]]) and publishes the results monthly. Recommendation 17 called for collecting and publicizing data regarding a chain of parties responsible for gTLD domain name registrations. Reseller information is already displayed within the WHOIS. Recommendation 18 called for specific data about the RDS-WHOIS2 review effort on data accuracy, which ICANN org's [[Contractual Compliance]]. Recommendation 30 recommended improving outreach for underserved regions and Recommendation 31 prompted ICANN org to coordinate a pro-bono assistance program. Both nTLD-related recommendations were superseded with the Board’s approval of the [[Sub Pro|next round]] of the [[New gTLD Program]] in March 2023.<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> CCT components considered complete come from CCT Recommendations 21, 23, and 24. CCT Recommendation 21 items 1, 3, 4, 5, and 6 data points were already available on ICANN Contractual Compliance’s reporting page at the time of Board action on the CCT Final Report, and the data point on the resolution status of complaints was added in August 2019. ICANN Contractual Compliance started publishing the volume and nature of complaints monthly, thereby addressing part of CCT Recommendation 23 item C. ICANN Contractual Compliance conducts audits twice a year (per the [[Registry Agreement]] and [[Registrar Accreditation Agreement]]), addressing CCT Recommendation 23 item E. ICANN currently reports monthly on complaints about a registry operator's failure to comply with safeguards on governmental functions or cyberbullying, addressing CCT Recommendation 24 item A.<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>

By April 2023, five out of the 17 Board-approved CCT Recommendations were considered complete. Recommendation 16 called for ongoing data collection on the relationship between registry operators, registrars, and DNS security abuse. ICANN org operates the Domain Abuse Activity Reporting ([[DAAR]]) and publishes the results monthly. Recommendation 17 called for collecting and publicizing data regarding a chain of parties responsible for gTLD domain name registrations. Reseller information is already displayed within the WHOIS. Recommendation 18 called for specific data about the RDS-WHOIS2 review effort on data accuracy, which ICANN org's [[Contractual Compliance]]. Recommendation 30 recommended improving outreach for underserved regions and Recommendation 31 prompted ICANN org to coordinate a pro-bono assistance program. Both nTLD-related recommendations were superseded with the Board’s approval of the [[Sub Pro|next round]] of the [[New gTLD Program]] in March 2023.<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> CCT components considered complete come from CCT Recommendations 21, 23, and 24. CCT Recommendation 21 items 1, 3, 4, 5, and 6 data points were already available on ICANN Contractual Compliance’s reporting page at the time of Board action on the CCT Final Report, and the data point on the resolution status of complaints was added in August 2019. ICANN Contractual Compliance started publishing the volume and nature of complaints monthly, thereby addressing part of CCT Recommendation 23 item C. ICANN Contractual Compliance conducts audits twice a year (per the [[Registry Agreement]] and [[Registrar Accreditation Agreement]]), addressing CCT Recommendation 23 item E. ICANN currently reports monthly on complaints about a registry operator's failure to comply with safeguards on governmental functions or cyberbullying, addressing CCT Recommendation 24 item A.<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> Org is developing a model for ongoing data collection to inform future community work; expected completion for Rec 1: Q4 2023. ICANN org plans to partner with gTLD and ccTLD registration data providers to obtain requested data; expected completion for Rec 6: Q4 2023. Org is evaluating resources and defining parking for data collection on parked domains. Expected completion for Rec 7: Q3 2023. Org is conducting a survey on consumer choice and trust in new gTLDs; expected completion for Recs 8, 11, and 13: Q3 2023. Org explored potential data sources for the correlation between abuse rates and stricter registration policies and conducted a voluntary pilot survey; expected completion of parts of Recs 13, 5, 20, 23, 24: Q3 2023.

==References==

==References==

{{reflist}}

{{reflist}}

[[Category:Specific Reviews]]

[[Category:Specific Reviews]]