Just to note the definition of Name Collision according to NCAP study Name Collision refers to the situation where a name that is defined and used in one namespace may also appear in another. Users and applications intending to use a name in one namespace may actually use it in a different one, and unexpected behavior may result where the intended use of the name is not the same in both namespaces. The circumstances that lead to a name collision could be accidental or malicious. In the context of top-level domains (TLDs), the conflicting namespaces are the global Internet Domain Name System (DNS) namespace reflected in the root zone as published by the Root Zone Management Partners and any other namespace, regardless of whether that other namespace is intended for use with the DNS or any other protocol [emphasis added in NCAP Study two report]. Name Collision Analysis Project Study Two Report'. ICANN, 5 April 2024. https://www.icann.org/en/system/files/files/ncap-study-2-report-05apr24-en.p.... Best Hadia ________________________________ From: Hadia Abdelsalam Mokhtar EL miniawi Sent: 17 July 2025 15:10 To: ICANN At-Large Staff Subject: RE: [CPWG] Final Review - Final Proceeding for Proposed Language for the Draft Next Round Applicant Guidebook (AGB) Draft Public Comment Statement Dear All, As I raised yesterday, I would like to clarify the comment I proposed yesterday on the AGB regarding section 6.7 (Name Collisions). The recommendation aims to address the risk of end user exploitation that could result from delegating names to maliciuos registrants using TLDs used in alternative names From: ICANN At-Large Staff via CPWG <cpwg@icann.org> Sent: 16 July 2025 19:57 To: CPWG <cpwg@icann.org> Subject: [External] [CPWG] Final Review - Final Proceeding for Proposed Language for the Draft Next Round Applicant Guidebook (AGB) Draft Public Comment Statement Dear CPWG Members, On behalf of the team working on the Final Proceeding for Proposed Language for the Draft Next Round Applicant Guidebook (AGB)<https://www.icann.org/en/public-comment/proceeding/final-proceeding-for-prop...>, we wanted to share the updated draft public comment statement with you for your final review. Instructions: Please review the text and let us know in the draft statement if you have concerns about the drafted language. Please provide your feedback before 00:00 UTC on 18 July 2025. To ensure we can finalize the public comment within the submission timeline, we would appreciate focusing comments on the current draft language rather than introducing new suggestions. Comments received will be reviewed and the ALAC will commence a vote in preparation for the 23 July 2025 submission deadline. Link to Draft Statement: https://docs.google.com/document/d/1dlUHsLdwQXITzO8_PkVKb7oEH43S69LOW-XR5ron... Document Status and Color Coding: * Purple text: New content added since our last review - these require your specific attention and feedback. Bullet review and text review will be conducted during tomorrow's CPWG meeting * Blue text: Content that was discussed during last week's call and is ready for final review Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org>