CCT Implementation - Status of 17 Recommendations

Complete  (5 recs.)

Recommendations 16, 17, 18, 30, 31

In progress  (12 recs.)

Recommendations 1, 6, 7, 8, 11, 13, 20, 21, 22, 23, 24, 26

Not started  (0 recs.)

/

Quarterly Updates

JUN 24

 Progress by Quarter

APR 2022

JUN 2022

SEPT 2022

DEC 2022Q4 2022

MAR 23Q1 2023

JUNE 23Q2 2023

SEPT 23Q3 2023

DEC 23Q4 2023

MAR 24Q1 2024

JUN 24Q2 2024

SEPT 24Q3 2024

Complete33345555555
In progress4451112121212121212
Not started1010920000000

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

1

In progress

P1

Formalize and promote ongoing data collection.

N/A

6

Not started

P2

Partner with mechanisms and entities involved with the collection of TLD data. As feasible, collect TLD registration number data per TLD and registrar at a country-by-country level in order to perform analysis based on the same methods used in the Latin American and Caribbean DNS Marketplace (LAC) Study.

N/A

7

In progress

P4

Collect domain usage data to better understand the implications of parked domains.

N/A

8

In progress

P1

Conduct periodic surveys of registrants that gathers both objective and subjective information with a goal of creating more concrete and actionable information.

N/A

11

In progress

P1

Conduct periodic end-user consumer surveys. Future review teams should work with survey experts to conceive more behavioral measures of consumer trust that gather both objective and subjective data with a goal toward generating more concrete and actionable information.

N/A

13

In progress

Items 1, 2, 4 (in part) prioritized as P1

Items 3, 4 (in part), 5 prioritized as P2

ICANN should collect data in conjunction with its related data collection activities on the impact of restrictions on who can buy domains within certain new gTLDs (registration restrictions) to help regularly determine and report:

1. Whether consumers and registrants are aware that certain new gTLDs have registration restrictions;

2. Compare consumer trust levels between new gTLDs with varying degrees of registration restrictions; [...]

N/A

16

Complete

N/A

Further study the relationship between specific registry operators, registrars, and DNS Security Abuse by commissioning ongoing data collection, including but not limited to, ICANN DAAR initiatives.

See implementation documentation.

17

Complete

N/A

ICANN should collect data about and publicize the chain of parties responsible for gTLD domain name registrations.

See implementation documentation.

18

Complete

N/A

In order for the upcoming WHOIS Review Team to determine whether additional steps are needed to improve WHOIS accuracy, and whether to proceed with the identity phase of the Accuracy Reporting System (ARS) project, ICANN should gather data to assess whether a [...]

See implementation documentation.

20

In progress

P2

Assess whether mechanisms to report and handle complaints have led to more focused efforts to combat abuse by determining:

(1) the volume of reports of illegal conduct in connection with the use of the TLD that registries receive from governmental and quasi-governmental agencies;

(2) the volume of inquires that registries receive from the public related to malicious conduct in the TLD;

(3) whether more efforts are needed to publicize contact points to report complaints [...]

N/A

21

In progress

Item 2 prioritized as P2

Include more detailed information on the subject matter of complaints in ICANN publicly available compliance reports. Specifically, more precise data on the subject matter of complaints, particularly: (1) the class/type of abuse; (2) the gTLD that is target of the abuse; (3) the safeguard that is at risk; (4) an indication of whether complaints relate to the protection of sensitive health or financial information; (5) what type of contractual breach is being complained of; and (6) resolution status of the complaints, including action details. These details would assist future review teams in their assessment of these safeguards.

N/A

22

In progress

P2

Initiate engagement with relevant stakeholders to determine what best practices are being implemented to offer reasonable and appropriate security measures commensurate with the offering of services that involve the gathering of sensitive health and financial information. Such a discussion could include identifying what falls within the categories of "sensitive health and financial information" and what metrics could be used to measure compliance with this safeguard.

N/A

23

In progress

P2

ICANN should gather data on new gTLDs operating in highly-regulated sectors to include the following elements:

- A survey to determine:

1) the steps registry operators are taking to establish working relationships with relevant government or industry bodies; and

2) the volume of complaints received by registrants from government and regulatory bodies and their standard practices to respond to complaints. [...]

N/A

24

In progress

Item B prioritized as P2

a. Determine whether ICANN Contractual Compliance should report on a quarterly basis whether it has received complaints for a registry operator's failure to comply with either the safeguard related to gTLDs with inherent governmental functions or the safeguard related to cyberbullying.

b. Survey registries to determine:

1) whether they receive complaints related to cyberbullying and misrepresenting [...]

N/A

26

In progress

P2

A study to ascertain the impact of the New gTLD Program on the costs required to protect trademarks in the expanded DNS space should be repeated at regular intervals to see the evolution over time of those costs. The CCT Review Team recommends that the next study be completed within 18 months after issuance of the CCT Final Report, and that subsequent studies be repeated every 18 to 24 months. The CCT Review Team acknowledges [...]

N/A

30

Complete

N/A

Expand and improve outreach into the Global South.

N/A

31

Complete

N/A

The ICANN organization to coordinate the pro bono assistance program.

See implementation documentation.