Hi Steve: 

Let me add my thanks to that of the others. 

To build on what Justine stated, I think it will be important to understand the rationale for the current regime guiding the handling of diacritics. As we learned through earlier Council discussions, there are a set of rules in place that govern the handling of applications for the delegation of .quebec and .québec. Why were those rules adopted given the options and what has changed to caused the reconsideration of the existing rule set? (I hope I put that clearly.)

Thanks and regards to all,

Kurt


On 9 Apr 2024, at 9:50 am, Justine Chew via council <council@gnso.icann.org> wrote:

Dear Steve,

Likewise, thank you for your update. Notwithstanding your preview of the paths available to Council to consider pursuing as you have set out below, I look forward to understanding the research and analysis ICANN org has performed to scope the breadth and depth of the problem with Latin diacritics, even if on a preliminary basis, to enable Council to consider what action needs to be taken in conjunction with selecting any path to pursue.

Kind regards,
Justine



On Tue, 9 Apr 2024 at 07:25, Mark Datysgeld via council <council@gnso.icann.org> wrote:

Thank you for the update, Steve.

Having a more detailed overview concerning the different paths this may take will be incredibly important for us to move forward.

Best,

On 8 Apr 2024 18:15, Steve Chan via council wrote:

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 (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/

Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO

Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar 


_______________________________________________
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.
--
Mark W. Datysgeld [markwd.website]
Director at Governance Primer [governanceprimer.com]
ICANN GNSO Councilor
_______________________________________________
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.
_______________________________________________
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.