All, As reported by Andrew and Olivier at the CPWG call of 10 April regarding an update on addressing the Latin Diacritics issue; and in particular, where Olivier had verbally shared with you on the call, my note to him about the possibility of the ICANN Board not accepting the set of Supplemental Recommendations 24.3A, 24.3B, and 24.3C to do with String Similarity, please find below a further update from GNSO Support Staff to the GNSO Council on this. I'm happy to answer questions, if any, but only to the extent that answers are available, since Council's discussion of this matter is currently ongoing for consideration at its next meeting at 21:00 UTC on Thursday, 18 April 2024 <https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agend...> . Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct+...> ------ ---------- Forwarded message --------- From: Steve Chan via council <council@gnso.icann.org> Date: Sat, 13 Apr 2024 at 04:46 Subject: [council] Additional Considerations Regarding Supplemental Recommendations 24.3A, 24.3B, and 24.3C (Singular/Plural) To: council@gnso.icann.org <council@gnso.icann.org> Dear Councilors, I have another update that the Council may want to factor into its plans for considering Supplemental Recommendations 24.3A, 24.3B, and 24.3C. The Board Caucus on New gTLD on Subsequent Procedures, with the assistance of ICANN org, has looked into the feasibility of implementing Supplemental Recommendations 24.3A, 24.3B, and 24.3C. Some concerns remain, so the Caucus has worked with ICANN org to try and identify a potential approach that would accomplish the intent of the recommendations (i.e., no singulars/plurals of existing gTLDs in the same language and applied-for singulars/plurals in the same language placed into a contention set) while minimizing remaining concerns. The Caucus and org have identified an approach that they believe can achieve the objective of the Supplemental Recommendations. While further work is needed to fully document the approach (note, the approach will also need to be discussed with the full Board), my org colleagues are working on first drafting a high-level overview of the approach to be shared with the Council. If after considering the high-level overview, the Council wishes to work further on the relevant Supplemental Recommendations, I understand that the Caucus remains available and willing to continue building upon the collaborative relationship it shares with the Council. Best, Steve *Steven Chan* VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan@icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMG...> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group...> _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. On Thu, 11 Apr 2024 at 04:51, Andrew Chen via CPWG <cpwg@icann.org> wrote:
Dear CPWG Members,
As mentioned in today’s CWPG call, please see the forwarded email below for an update regarding Latin Diacritics from GNSO Support Staff to the GNSO Council. Please note that the GNSO Council will meet at 21:00 UTC on Thursday, 18 April 2024 <https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agend...> to discuss this under Agenda Item 5: Council Discussion - Diacritics in Latin Script.
Sincerely,
Andrew
--
Andrew Chen
Policy Development Support Sr. Specialist, Policy Development Support
Internet Corporation for Assigned Names and Numbers (ICANN)
Skype: atchen122
*From: *council <council-bounces@gnso.icann.org> on behalf of Steve Chan via council <council@gnso.icann.org> *Date: *Monday, April 8, 2024 at 2:15 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Subject: *[council] Interim Update on Mechanism(s) to Address Latin Diacritics
Dear Councilors,
As you may have seen, the April Council meeting is scheduled to have an update on the research and analysis ICANN org has performed to understand the mechanism(s) that might be available to progress the work related to Latin diacritics. While we will provide a more comprehensive update during the Council meeting, we wanted to share an early preview of the update, as it may have implications on the Council’s vote on a subset of the SubPro Supplemental Recommendations. In brief, our recommended approach is for the Council to consider modifying/amending the non-adopted recommendations related to string similarity (i.e., Recommendations 24.3 and 24.5) if it wants to take up the issue of Latin diacritics. Under the ICANN Bylaws and GNSO Operating Procedures, there are two avenues to pursue this path, which are either Section 16 of the PDP Manual [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> (see page 10) or the Supplemental Recommendation process, as employed by the Small Team Plus.
With the Council’s consideration and potential adoption of Supplemental Recommendations 24.3A, 24.3B, and 24.3C during its April meeting, there may be challenges to using either Section 16 or the Supplemental Recommendation process to progress the Latin diacritics issues:
1. Section 16: The PDP Manual states that, “approved GNSO Council policies may be modified or amended by the GNSO Council at any time prior to the final approval by the ICANN Board…”. If the Council approves Supplemental Recommendations 24.3A, 24.3B, and 24.3C AND they are adopted by the ICANN Board, this option would no longer be available (i.e., “final approval” will have occurred). 2. Supplemental Recommendations: If the Council approves Supplemental Recommendations 24.3A, 24.3B, and 24.3C, the Council would not be able to develop further Supplemental Recommendations related to Latin diacritics.
We understand the Council has committed to taking action on the Supplemental Recommendations during its April meeting, so we believe it is important to provide you with this information in advance of your meeting for effective planning and decision-making. Please let us know if you have any questions.
Best,
Steve
*Steven Chan*
VP, Policy Development Support & GNSO Relations
Internet Corporation for Assigned Names and Numbers (ICANN)
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Email: steve.chan@icann.org
Skype: steve.chan55
Mobile: +1.310.339.4410
Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMG...>
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...>
Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group...> _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.