closed Name Collision Procedure Documentation

Outcome

ICANN org extends its thanks to all commenters for their engagement with the Name Collision Procedure documentation and values the community's contribution to this important aspect of the New gTLD Program: 2026 Round. Having carefully considered all submissions received, ICANN org has determined that no specific changes to the Name Collision Procedure documentation are required at this time. The Operating Procedures and the High-Risk String Classification Model faithfully implement recommendations from the Name Collision Analysis Project (NCAP) Study 2 recommendations that were approved by the ICANN Board on 7 September 2024 (Resolutions 2024.09.07.10–12). ICANN is of the view that the framework already incorporates the safeguards and transparency measures sought by commenters.

One area has been noted for further consideration: ICANN org will examine what additional information should be included in public status updates when a string remains in Temporary Delegation beyond the expected 90-day period, including if an explanation for the extended assessment can be included.

What We Received Input On

As part of the New Generic Top-Level Domains (gTLD) Program: 2026 Round, ICANN is preparing procedures that outline how Name Collision assessments will be carried out for applied-for strings. ICANN org seeks input on the Name Collision Procedure documentation for Initial Assessment, Temporary Delegation, and High-Risk String Mitigation Plan Assessment, including the impact-based classification model for identifying high-risk strings.

Background

Each applied-for string, including variant strings, will be subject to name collision assessments to identify strings that present a high risk of causing harmful name collisions. If unmitigated, name collisions are likely to result in severe adverse consequences for stakeholders.

These procedures, together with the impact-based High-Risk String Classification Model, will be applied as part of these assessments to determine whether a string is categorized as a High-Risk String and to evaluate whether a submitted High-Risk String Mitigation Plan is likely to be effective.

Supporting Information