2025-11-12 Latin Script Diacritics - Meeting #24

The call for the Latin Script Diacritics team will take place on Wednesday, 12 November 2025 at 13:15 UTC for 75 minutes.

PROPOSED AGENDA

Welcome and SOIs
Recap of Working Sessions at ICANN84- Key Outcomes and Action Items- Update on EPDP-IDNs
Stress Test- Continue with Unresolved Cases
Continue with Charter Topic Deliberations- Charter Question 4- GPI/HR Impact Assessment
Table of Contents for Initial Report
Next Steps
AOB

BACKGROUND DOCUMENTS

Zoom Recording (including audio, visual, rough transcript and chat)

GNSO transcripts are located on the GNSO Calendar

Notes/ Action Items

[OUTCOMES]

[ACTION ITEMS]

Leadership and staff to look at PR #45 add to the footnote that the source domain must be from the domain set
Update footnotes 34 & 36 as we were waiting for the outcome of the ICANN Board decision
Leadership and Staff to look at case study 6 to determine the impact of both option1 and option 2 on other recommendations. Gather data on possible changes required to present to WG.
All in WG to review the existing consensus policies and the LT/Staff Analysis [docs.google.com] for CQ4

[NOTES]

a. Key Outcomes and Action Items – Update on EPDP-IDNs

Reviewed the slides [icann-community.atlassian.net] and discussed sessions from ICANN84
Updated PR revisions which will be discussed in the meeting later today
PR #39 previous wording had some issues and this was reworded with consensus at ICANN84
PR #45 discussed for how to update and determined options outlined on slide [icann-community.atlassian.net] 8
Sarmad: suggested the wording itself if there is a need to say where the source domain names are different they must come from the same variant set?
Since all domains must be within our ASCII/LD set it would be obvious that the source domain must also come from this set. But if it is not totally obvious it should be footnoted that it must be from within this domain set
Agreement to go with option 2 and the updated footnote language
Updated overall preliminary recommendations with 8 topics and 54 outputs
EPDP-IDNs Recommendations 7.4 and 7.5 adopted by Board at ICANN84 and the relation to LD PDP outlined in slide [icann-community.atlassian.net] 10

Reviewed stress tests and case study 5
Case study 6 discussed and a small consensus emerged around option 2 and all recs must be reviewed in consensus with this with the case of variant TLDs included in this TLD set
However, discussion went on as this option 2 could have a broader impact on a variety of recommendations. This could require more changes and so there was group hesitation to reach consensus there.
Sarmad: Option 1 in the other direction that if the TLD label has variants, why should the be a deterrent to LD sets? Does motivation for LDs go away with variants? Not likely. Is it possible for the diacritized version to have variants as well?
Not possible with current LGR as there are no allocatable variants
Option 1 has clearer implications, but checking recommendations for options 1 and 2

Discussion of GPI and HRIA from Charter question 4 this is new to all future PDPs and ours is the first
List of existing consensus policies found here
There are existing consensus policies listed and outlined here [docs.google.com]
Template was created for this particular PDP and all our recommendations on this have been noted to be no or low impact for existing policies