- Gnso-latin-diacritics - lists.icann.org

Revised ASCII-Unicode Diacritics Analyzer Tool
by Mark W. Datysgeld Sept. 15, 2025

Sept. 15, 2025

Everyone, Following a question that came up during the review of the recommendations document, I have revised the tool that generates the list of characters that are within our scope. I am happy to report that the methodology still holds strong, resulting in 106 characters with one diacritic mark, 30 characters with two diacritic marks, and 14 "other occurrences". However, to clarify matters further, I have now added a list titled: "Appendix: Latin repertoire not canonically decomposable to ASCII base", which holds the major examples that *seem* like they might be within scope, but actually aren't due to being precomposed. I am attaching the new report to this email for your convenience. Nevertheless, you can inspect the new code it in the same repository as before: https://github.com/mark-wd/ASCII-Unicode-Diacritics-Analyzer-Tool Best, -- Mark W. Datysgeld Director at Governance Primer [governanceprimer.com <https://governanceprimer.com>] Project Lead Developer at ICANNWiki [icannwiki.org <https://icannwiki.org/>]

1 0

Proposed Agenda for Meeting #19
by Saewon Lee Sept. 15, 2025

Sept. 15, 2025

Dear LD PDP WG, Thank you to everyone who provided input on the draft preliminary recommendations document. The Leadership Team and Staff will consider your comments and incorporate them as appropriate. Kindly note that only substantive comments requiring further attention or discussion will be reviewed at the meeting (Meeting #19). Please find below the proposed agenda for LD PDP WG Meeting #19 on Wednesday, 17 September 2025 at 13:15 UTC: 1. Welcome and SOIs 2. Recap of Meeting #18 * Key Outcomes and Action Items 1. Review of Draft Preliminary Recommendations 2. Next Steps 3. AOB Looking forward to seeing you again all soon! Kind regards, Saewon Saewon Lee Policy Development Support Manager for GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 463-5541 Email: saewon.lee(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org>

1 0

FINAL REMINDER: Request for Review and Feedback on Preliminary Recs.
by Saewon Lee Sept. 15, 2025

Sept. 15, 2025

***FINAL REMINDER: Please review and provide feedback on the draft preliminary recommendations below if you haven’t already done so. The assignment is due on Sunday, 14 September at 23:59 UTC*** Dear LD PDP WG, As announced during last week’s meeting (Meeting #18), please review and provide feedback (sidebar comments only) on the following draft preliminary recommendations by Sunday, 14 September at 23:59 UTC: https://docs.google.com/document/d/10PiKG0grWcN2Q2UKKjz0WpuElJ3gLb9tY4JYgdu… For your reference, a mapping spreadsheet is provided in the following link, which outlines the relationship between the draft recommendations and the existing body of work previously reviewed by the WG—mostly centered on SubPro and EPDP-IDNs: https://docs.google.com/spreadsheets/d/1cp19yVCxJ7k8Wf5dW7kvHTT27NvXM2vV2M2… Please note that the draft documents (preliminary recs. doc. as well as the mapping doc.) do not allow edits within the main body of the text. Therefore, we ask that you submit all feedback via sidebar comments only. The Leadership Team (LT) and Staff will review your input and incorporate it accordingly in preparation for our next meeting (Meeting #19). Should you have any questions or concerns, please don’t hesitate to reach out. Much appreciated, Saewon Saewon Lee Policy Development Support Manager for GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 463-5541 Email: saewon.lee(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org>

2 2

REMINDER: Request for Review and Feedback on Preliminary Recs.
by Saewon Lee Sept. 8, 2025

Sept. 8, 2025

***REMINDER: Please review and provide feedback on the draft preliminary recommendations below if you haven’t already done so. The assignment is due on Sunday, 14 September at 23:59 UTC*** Dear LD PDP WG, As announced during last week’s meeting (Meeting #18), please review and provide feedback (sidebar comments only) on the following draft preliminary recommendations by Sunday, 14 September at 23:59 UTC: https://docs.google.com/document/d/10PiKG0grWcN2Q2UKKjz0WpuElJ3gLb9tY4JYgdu… For your reference, a mapping spreadsheet is provided in the following link, which outlines the relationship between the draft recommendations and the existing body of work previously reviewed by the WG—mostly centered on SubPro and EPDP-IDNs: https://docs.google.com/spreadsheets/d/1cp19yVCxJ7k8Wf5dW7kvHTT27NvXM2vV2M2… Please note that the draft documents (preliminary recs. doc. as well as the mapping doc.) do not allow edits within the main body of the text. Therefore, we ask that you submit all feedback via sidebar comments only. The Leadership Team (LT) and Staff will review your input and incorporate it accordingly in preparation for our next meeting (Meeting #19). Should you have any questions or concerns, please don’t hesitate to reach out. Much appreciated, Saewon Saewon Lee Policy Development Support Manager for GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 463-5541 Email: saewon.lee(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org>

1 0

Request for Review and Feedback on Preliminary Recs.
by Saewon Lee Sept. 2, 2025

Sept. 2, 2025

Dear LD PDP WG, As announced during last week’s meeting (Meeting #18), please review and provide feedback (sidebar comments only) on the following draft preliminary recommendations by Sunday, 14 September at 23:59 UTC: https://docs.google.com/document/d/10PiKG0grWcN2Q2UKKjz0WpuElJ3gLb9tY4JYgdu… For your reference, a mapping spreadsheet is provided in the following link, which outlines the relationship between the draft recommendations and the existing body of work previously reviewed by the WG—mostly centered on SubPro and EPDP-IDNs: https://docs.google.com/spreadsheets/d/1cp19yVCxJ7k8Wf5dW7kvHTT27NvXM2vV2M2… Please note that the draft documents (preliminary recs. doc. as well as the mapping doc.) do not allow edits within the main body of the text. Therefore, we ask that you submit all feedback via sidebar comments only. The Leadership Team (LT) and Staff will review your input and incorporate it accordingly in preparation for our next meeting (Meeting #19). Should you have any questions or concerns, please don’t hesitate to reach out. Much appreciated, Saewon Saewon Lee Policy Development Support Manager for GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 463-5541 Email: saewon.lee(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org>

1 0

Post Call | Latin Script Diacritics PDP | Wednesday, 27 August 2025
by Julie Bisland Aug. 27, 2025

Aug. 27, 2025

Dear all, All recordings for the Latin Script Diacritics PDP call held on Wednesday, 27 August 2025 at 13:15 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AYAnG> (attendance included) and the GNSO Master calendar<https://gnso.icann.org/en/group-activities/calendar/2025>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Transcript * Agenda and Notes/Action Items For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-latin-diacritics@icann.org/> and the main wiki page<https://icann-community.atlassian.net/wiki/x/EwDVBg?atlOrigin=eyJpIjoiMWI2M…>. Thank you. With kind regards, Julie

1 0

Outcomes, Action Items, and Notes from Meeting #18
by John Emery Aug. 27, 2025

Aug. 27, 2025

Dear LD PDP WG, CONGRATULATIONS! We have finished the TBD items in the spreadsheet and will have no meetings for the next two weeks to allow time for the WG to review the preliminary recommendations document (to be sent in the next few days). Please see below the Outcomes, Action Items, and Notes from Meeting #18<https://icann-community.atlassian.net/wiki/x/AYAnG> on Wednesday, 27 August 2025: Meeting #18 Slides<https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/40524185…> [OUTCOMES] 1. 7.4 and 7.5 Decision to proceed in accordance with the outcome of the Board decision on EPDP-IDNs to be reviewed when Board makes a decision 2. Filled in Spreadsheet <https://docs.google.com/spreadsheets/d/1vA4BoEHaGJBpVJ4oJcEgvzJlu5zEhF9cOQO…> of relevant TBD recommendations and wrote the consensus in the decision tab [ACTION ITEMS] * The WG members need to review the Preliminary Recommendation language by 14 September [NOTES] 1. Welcome and SOIs 2. Recap of Meeting #17 * Agreement on pricing for no fees recommended and follow cost recovery principle via implementation as guided by AGB * Ariel from ICANN org for recommendations 7.4 and 7.5 Board is still in process deliberating these recommendations, they have not been formally adopted yet. ICANN finance has to conduct analysis and understand their impact. Without that, the Board cannot take action. There is some discussion on this recently, so there will hopefully be movement, but that is the reason why these have not been adopted yet. 7.4 is complicated for analysis and 7.5 is less complicated. Once that is received the WG will be updated 3. Charter Question 3 <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> * EPDP-IDNs P2 TBD items i.Filled in worksheet<https://docs.google.com/spreadsheets/d/1vA4BoEHaGJBpVJ4oJcEgvzJlu5zEhF9cOQO…> * 7.4 Four possibilities to decide: 1. Proceed in accordance with the outcome of the Board decision. 2. Same as a single TLD 3. Treat as separate TLDs 4. Should not be more than 2 separate TLDs (less than) * Broad discussion of options with some consensus emerging with that EPDP IDNs has been the consensus so far around number 1 * Solution 1 Vote: 5, Solution 2 Vote: 1; Solution 3 Vote 0; Solution 4 Vote: 3 * Voted for 1 for wisdom of EPDP IDNs should be the rule for this. * Steve Chan, ICANN org, In terms of drafting, maybe we could just retrofit 7.4 and 7.5 and add a clause that says, unless determined differently. Path forward could be we want to pursue 7.4 and 7.5 unless the Board determines differently for these recommendations acknowledging there is uncertainty. * No precedent set here since it was in name collisions so agreement was reached to go with option 1, but should the Board adoption happen prior to that, then we can follow up when that decision is made * 7.5 registry level transaction fee. Follow same principle as 7.4 for same outcome of EPDP-IDNs * Single contract between ICANN and registries containing more than 1 TLD suggestion is to have the same calculation for registry level transaction fees * Implementation Guidance 2: number of variants activated to the same registrant. Restrict manually activated variants, and automatically activated. There is not a suggestion to have a hard coded number here, but registries should set some upper limit for this * Registries normally set that to 4 or 5 and almost none that have more than 1-2. Should be limited to 4-5 and beyond that only gaming is possible in real terms. There is some kind of confusion among registrants. * Second level, there could be Arabic script at 2nd level together with Latin TLDs then in that case the same variant rules that exist for EPDP-IDNs. * Underlying concern here is clear that there should not be too many instances of variants. Capping the maximum and the automatic activation. Instinct to go with EPDP-IDNs as it would likely be a bigger problem there than here * Want to not allocate too many domain names to the same entity as not all are variants but some are based on the diacritic groupings * In variant case it would be a maximum of 5 with IDNs and 5 with diacritics. It would make sense to have a corresponding version here with adjusted wording. 4. Preliminary Recommendations * Back to Slides<https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/40524185…>: Charter questions Summary and Tracking overview * Saewon Lee introduced the layout of draft preliminary recommendations from the Slides<https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/40524185…>. Simply each relevant recommendation was mapped out advised by ICANN legal leading to 54 preliminary recommendations and implementation guidance. * The draft recommendations for “certain TLD types” refers to not limiting boundaries to “real words” geoTLDs and BrandTLDs and the style will talk about applications for existing TLDs applied for and new applications. * No Meetings for the following 2 weeks to complete homework on reviewing the preliminary recommendations Thank you, John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Proposed Agenda for Meeting #18
by Saewon Lee Aug. 25, 2025

Aug. 25, 2025

Dear LD PDP WG, Please find below the proposed agenda for LD PDP WG Meeting #18 on Wednesday, 27 August 2025 at 13:15 UTC: 1. Welcome and SOIs 2. Recap of Meeting #17 * Key Outcomes and Action Items 1. Charter Question 3 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> * Review of TBD Items 1. Initial Report: Overview of Preliminary Recommendations 2. Next Steps 3. AOB As always, the LD PDP WG Charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> and the Worksheet with SubPro/EPDP-IDNs Outputs [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1vA4BoEHa…> have been hyperlinked for your reference and the Charter Questions can be viewed on page 2. Please also see all relevant/background documents to this PDP on wiki here [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/2wP…>. Looking forward to wrapping up TBD Items/CQ3 with you all tomorrow! Kind regards, Saewon Saewon Lee Policy Development Support Manager for GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 463-5541 Email: saewon.lee(a)icann.org<mailto:saewon.lee@icann.org> Skype: saewon.lee.icann Website: www.icann.org<http://www.icann.org>

1 0

Post Call | Latin Script Diacritics PDP | Wednesday, 20 August 2025
by Devan Reed Aug. 20, 2025

Aug. 20, 2025

Dear all, All recordings for the Latin Script Diacritics PDP call held on Wednesday, 20 August 2025 at 13:15 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AQAnG> (attendance included) and the GNSO Master calendar<https://gnso.icann.org/en/group-activities/calendar/2025>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Transcript * Agenda and Notes/Action Items For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-latin-diacritics@icann.org/> and the main wiki page<https://icann-community.atlassian.net/wiki/x/EwDVBg?atlOrigin=eyJpIjoiMWI2M…>. Thank you. With kind regards, Devan

1 0

Outcomes, Action Items, and Notes from Meeting #17
by John Emery Aug. 20, 2025

Aug. 20, 2025

Dear LD PDP WG, Please see attached: Outcomes, Action Items, and Notes from Meeting #17<https://icann-community.atlassian.net/wiki/x/AQAnG> on Wednesday, 20 August 2025 Meeting #17 Slides<https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/40520908…> [OUTCOMES] 1. Agreement on pricing that there would be no output/recommendation on fees and would be based on an ICANN cost recovery principle 2. Filled in Spreadsheet <https://docs.google.com/spreadsheets/d/1vA4BoEHaGJBpVJ4oJcEgvzJlu5zEhF9cOQO…> of relevant TBD recommendations and wrote the consensus in the decision tab [ACTION ITEMS] * WG to review upcoming TBD items in the worksheet <https://docs.google.com/spreadsheets/d/1vA4BoEHaGJBpVJ4oJcEgvzJlu5zEhF9cOQO…> * Ariel Liang to get information on recommendations 7.4 and 7.5 from GDS colleagues [NOTES] 1. Welcome and SOIs 2. Recap of Meeting #16 * Not necessary to give an interim update to SO/ACs on progress. Most people are reporting back to their groups * Main goal is to avoid rejection and using the LD PDP exceptions process. In contrast, the goal of EPDP-IDNs was IDN promotion. Goal of this PDP is not IDN promotion. * Reviewed three facts on cost recovery * Slide #8 summarized discussion for the three main solutions to pricing including advantages and disadvantages for each solution * Rationale for evaluation fee estimation based on EPDP IDNs and the cost subsidy involved * Discussion on application fees: some support for options 3, 2 * Number 2 would make sense in fairness. But, applying for free could assume that we are not in a position to set the price. GNSO will not set the prices. We should not create an obstacle to preventing the PDP from working. If we want this to succeed, if feasible, what are the real cost of the evaluation? Need to bundle, but if we go the free way, it could prevent the next round * If we were to go for #2 there would have to be limits set. * To help provide some insight into what the evaluation fees covers, I would recommend reading Section 2.3.1 of the AGB: https://itp.cdn.icann.org/en/files/policy-development/new-gtld-program-next… * There is a set of FAQ related to fees for program (to be updated with new info), but this is the current info: https://newgtldprogram.icann.org/en/resources/gtld-evaluation-fee-faqs * Background: for variants it is the scripts that have allocatable variants (7 scripts) all scripts had a low allocatable (up to 4 for IDNs). Based on this understanding the estimation was made. It will be hard to make a limited estimation for Latin. Cannot make this estimation for Latin diacritic cases, 1000 latin TLDs and could have multiple diacritic versions. How many applications could come in would be much higher * Potential to add diacritics to existing Latin are exponentially more than IDNs * Current discussion shows it is difficult to apply IDNs it is a technical issue. Not the same a Latin diacritics. In Latin it is a social need, not a technical question. Applying some rules here could lead to the world being possible. Same TLD in 7 ways potential for confusion would be higher. * Agreement with Amadeu, it would be nice for more IDNs. This is a narrow exception process, not a goal to make this an encouragement. If it is free, why not? Goal is a narrow exceptions process. Avoid people willing to pay full price to get an application rejected because of current rules. Due to this problem we are making an exception that avoids this. This is not meant to be free or encouraged * It could give a slight advantage if it is based on cost recovery, if you combine the labels you don’t have to evaluate the applicant twice, there is likely to be some cost reduction to make it more attractive, but not doing something to encourage massive amounts of diacritics * Not comfortable with unlimited TLDs free from the Board perspective. Number 3 would make more sense in pricing. * Vote: Option 1 – 0; Option 2 – 2; Option 3 – 8 Consensus to move toward number 3 1. Charter Question 3 <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> * EPDP-IDNs P2 TBD items * Filled in worksheet<https://docs.google.com/spreadsheets/d/1vA4BoEHaGJBpVJ4oJcEgvzJlu5zEhF9cOQO…> * 3.12 Not applicable for LD PDP based on previous decision * 3.13 Makes sense to offer a discount fee and allow ICANN org to decide the discount * 3.14 Not applicable based on previous decision * 8.1 Upper limit of Latin diacritics that can be bundled together with one TLD? There may be valid reasons for variations for different languages. Should be a linguistic reason for more than one diacritic. Similar recommendation 3.5 addresses this must be a justification * This should apply to multiple diacritics. There will be requirements for justification for diacritics * 7.4 and 7.5 are still pending status at the Board deliberation level, they have not yet been adopted. Consider whether these have an impact. All the best, John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0