Public Comment

Public Comment is a vital part of our multistakeholder model. It provides a mechanism for stakeholders to have their opinions and recommendations formally and publicly documented. It is an opportunity for the ICANN community to effect change and improve policies and operations.

Контент доступен только на следующих языках

  • English

Name: JORGE CARLOS CANTO ESQUIVEL
Date: 13 Feb 2026
Preliminary Recommendation 1
No opinion
Preliminary Recommendation 2
No opinion
Preliminary Recommendation 3
No opinion
Preliminary Recommendation 4
No opinion
Preliminary Recommendation 5
No opinion
Preliminary Recommendation 6
No opinion
Preliminary Recommendation 7
No opinion
Implementation Guidance 8
No opinion
Preliminary Recommendation 9
No opinion
Implementation Guidance 10
No opinion
Implementation Guidance 11
No opinion
Preliminary Recommendation 12
No opinion
Preliminary Recommendation 13
No opinion
Preliminary Recommendation 14
No opinion
Preliminary Recommendation 15
No opinion
Implementation Guidance 16
No opinion
Preliminary Recommendation 17
No opinion
Preliminary Recommendation 18
No opinion
Preliminary Recommendation 19
No opinion
Preliminary Recommendation 20
No opinion
Preliminary Recommendation 21
No opinion
Preliminary Recommendation 22
No opinion
Preliminary Recommendation 23
No opinion
Preliminary Recommendation 24
No opinion
Preliminary Recommendation 25
No opinion
Preliminary Recommendation 26
No opinion
Implementation Guidance 27
No opinion
Preliminary Recommendation 28
No opinion
Preliminary Recommendation 29
No opinion
Preliminary Recommendation 30
No opinion
Preliminary Recommendation 31
No opinion
Preliminary Recommendation 32
No opinion
Preliminary Recommendation 33
No opinion
Implementation Guidance 34
No opinion
Preliminary Recommendation 35
No opinion
Preliminary Recommendation 36
No opinion
Implementation Guidance 37
No opinion
Preliminary Recommendation 38
No opinion
Preliminary Recommendation 39
No opinion
Preliminary Recommendation 40
No opinion
Implementation Guidance 41
No opinion
Preliminary Recommendation 42
No opinion
Other Comments

I appreciate the Working Group’s effort to address the identified regulatory gap concerning ASCII and Latin script diacritic gTLDs that are not variants but may be visually confusingly similar. The narrow technical scope, reliance on Unicode decomposition, alignment with the RZ-LGR framework, and the application of the “Same Entity” principle provide a coherent and stability-oriented structure.

To further strengthen the proposal, I would suggest consideration of the following points:

Evidence of Practical Demand

While the policy addresses a structural gap, additional clarity regarding demonstrated or projected demand would reinforce its justification. Data or illustrative cases indicating the scale of need could provide helpful context for evaluating proportionality and long-term impact.

Differentiated Risk Considerations

Although eligibility is based on Unicode decomposition, not all diacritic usages may present equivalent degrees of visual similarity or user confusion. Future implementation guidance or periodic review mechanisms could assess whether differentiated monitoring is warranted based on observed patterns.

Post-Implementation Review

Given the intersection of technical governance and linguistic representation, a structured review (e.g., after 3–5 years) evaluating adoption, security implications, and practical usage would enhance policy resilience. From an academic and research perspective, such data would also contribute to a clearer understanding of how technical inclusion translates into effective multilingual participation online.

Overall, the proposed mechanism appears technically sound and appropriately limited in scope. Strengthening its empirical grounding and incorporating structured monitoring would further enhance its long-term legitimacy and effectiveness.

Thank you for the opportunity to comment.