Apologies for the premature email
Dear All,
As I raised yesterday, I would like to clarify the comment I proposed regarding section 6.7 (Name Collisions). The recommendation aims to address the risk of end user exploitation
that could result from delegating names to malicious registrants using TLDs used in alternative namespaces. The key issue is not simply whether the TLD exists in an alternative name space, but whether delegating that specific string into the DNS could potentially
expose users to harm. For example, if .eth were delegated as a gTLD and mywallet.eth were assigned to a malicious registrant, if users type that name in a DNS application they will be misdirected to a fraudulent site, leading to potential harm
We also need to keep in mind that applicants will be given the opportunity to submit mitigation plans. These plans will be used to address concerns related to potential harm,
this could also involve overlap with names in alternative namespaces. Therefore, applicants mitigation plans and proposed measures could also account for such scenarios.
The proposed recommendation opens the door to incorporate external intelligence when assessing applied for strings and does not clash with the definition to name collisions. I also note that the AGB already refers to using qualitative measures.
Proposed recommendation: Name Collision assessment should take into account potential collisions with well-known and widely used alternative namespaces., in order to identify and mitigate any foreseeable risks of harm to end users. And
we could use my above explanation in the rational.
Kind regards
Hadia Elminiawi
مهندسة/ هادية المنياوى
كبير خبراء - البنية التحتية والطيف الترددي
الجهاز القومي لتنظيم الاتصالات
القرية الذكية، طريق مصر اسكندرية الصحراوي
تليفون: 20235344392
Eng. Hadia Elminiawi, M.Sc.
Chief Expert - Infrastructure and Radio Spectrum Planning
National Telecom Regulatory Authority of Egypt (NTRA)
Tel: 202 3534-4392
Email: Hadia@tra.gov.eg
Smart Village, Cairo/Alex Desert Road, Giza, Egypt 12577
AFRALO Chairwoman & SSAC member
Internet Corporation for Assigned Names and Numbers (ICANN)
From: Hadia Abdelsalam Mokhtar EL miniawi
Sent: 17 July 2025 15:10
To: 'ICANN At-Large Staff' <staff@atlarge.icann.org>
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), 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-XR5ronFBA/edit?usp=sharing
Document Status and Color Coding:
Thank you.
Kind regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community