Interim Update on Mechanism(s) to Address Latin Diacritics
![](https://secure.gravatar.com/avatar/14b7bc65e87f4adc97f645c2b02de9b2.jpg?s=120&d=mm&r=g)
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<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pdp-manual-15mar23-en_0.pdf#page=10> (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<mailto: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=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=> 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-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>
![](https://secure.gravatar.com/avatar/76a1f8e5f58cac351462046aebc54e12.jpg?s=120&d=mm&r=g)
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 thePDP Manual <https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pdp-manual-15mar23-en_0.pdf#page=10>(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 <mailto: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=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=>
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=>
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-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>
_______________________________________________ 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 <https://markwd.website>] Director at Governance Primer [governanceprimer.com <https://governanceprimer.com>] ICANN GNSO Councilor
![](https://secure.gravatar.com/avatar/9719a69c29ebf686df561511928b3f70.jpg?s=120&d=mm&r=g)
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 <https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pdp-manual-15mar23-en_0.pdf#page=10> (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=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=>
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=>
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-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>
_______________________________________________ council mailing listcouncil@gnso.icann.orghttps://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.
![](https://secure.gravatar.com/avatar/9728824825d8130ed546db9649e48f42.jpg?s=120&d=mm&r=g)
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<mailto: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<mailto: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<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pdp-manual-15mar23-en_0.pdf#page=10> (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<mailto: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=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=> 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-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=> _______________________________________________ council mailing list council@gnso.icann.org<mailto: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<https://markwd.website/>] Director at Governance Primer [governanceprimer.com<https://governanceprimer.com/>] ICANN GNSO Councilor _______________________________________________ council mailing list council@gnso.icann.org<mailto: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<mailto: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.
![](https://secure.gravatar.com/avatar/10883339163f2f9deaa9b315c080034b.jpg?s=120&d=mm&r=g)
Hi Steve, I wanted to add my thanks as well for you putting this update together- its sounding like we’re going to have a really interesting discussion on Latin Diacritics at our next Council meeting. Looking forward to understanding more about what led to where we are and engaging making some further decisions. Kind Regards, Prudence Malinki Head of Industry Relations, Markmonitor Skype: Malinkip T +44 207 433 4869 Time zone: GMT/BST [cid:image001.png@01DA8AED.B06EBAE0] From: council <council-bounces@gnso.icann.org> On Behalf Of kurt kjpritz.com via council Sent: Tuesday, April 9, 2024 1:00 AM To: Justine Chew <justine.chew.icann@gmail.com> Cc: council@gnso.icann.org Subject: Re: [council] Interim Update on Mechanism(s) to Address Latin Diacritics [CAUTION External Email] 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<mailto: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<mailto: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<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pdp-manual-15mar23-en_0.pdf#page=10> (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<mailto: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=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=> 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-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=> _______________________________________________ council mailing list council@gnso.icann.org<mailto: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<https://markwd.website/>] Director at Governance Primer [governanceprimer.com<https://governanceprimer.com/>] ICANN GNSO Councilor _______________________________________________ council mailing list council@gnso.icann.org<mailto: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<mailto: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.
![](https://secure.gravatar.com/avatar/969a94dd658fe1318210c671a6be45c9.jpg?s=120&d=mm&r=g)
HI Steve, I think the Council will need to know how the Supplemental Recommendations could be modified to address the diacritics issues. At present, we don't know why the Board and Org think this is possible. It may be that the Small team Plus assignment should be amended to study this potential modification and if so, it would be the only open issue in the Supplemental Recommendations that would not be voted on in our April meeting. In other words, the Supplemental Recommendations don't all have to be sent at once if this is something that can be studied and addressed by the Small Team Plus as a "dangling issue". Here I think it is important to include Small Team Plus member participation because you definitely want to avoid GAC Advice on this issue coming out of Kigali. Let's take an expeditious look but we need more info from staff as to the thinking behind the idea of addressing this with revised Supplemental Recommendations on String Similarity. Thank you! Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Mon, Apr 8, 2024 at 2:15 PM Steve Chan via council < council@gnso.icann.org> 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 <https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pdp-manual-15mar23-en_0.pdf#page=10> (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=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=>
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=>
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-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=> _______________________________________________ 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.
![](https://secure.gravatar.com/avatar/76a1f8e5f58cac351462046aebc54e12.jpg?s=120&d=mm&r=g)
My concern is aligned to some degree with Anne's. I am always a bit wary of how different processes integrate in a multistakeholder environment, and this is looking like something that will require very careful consideration for it to be adequately delegated and timed. Best, --- Mark W. Datysgeld from Governance Primer ________________________________ From: Anne ICANN via council <council@gnso.icann.org> Sent: Wednesday, April 10, 2024 11:54 To: Steve Chan Cc: council@gnso.icann.org Subject: Re: [council] Interim Update on Mechanism(s) to Address Latin Diacritics HI Steve, I think the Council will need to know how the Supplemental Recommendations could be modified to address the diacritics issues. At present, we don't know why the Board and Org think this is possible. It may be that the Small team Plus assignment should be amended to study this potential modification and if so, it would be the only open issue in the Supplemental Recommendations that would not be voted on in our April meeting. In other words, the Supplemental Recommendations don't all have to be sent at once if this is something that can be studied and addressed by the Small Team Plus as a "dangling issue". Here I think it is important to include Small Team Plus member participation because you definitely want to avoid GAC Advice on this issue coming out of Kigali. Let's take an expeditious look but we need more info from staff as to the thinking behind the idea of addressing this with revised Supplemental Recommendations on String Similarity. Thank you! Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Mon, Apr 8, 2024 at 2:15 PM Steve Chan via council <council@gnso.icann.org> 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: 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). 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.
participants (7)
-
Anne ICANN
-
Justine Chew
-
kurt kjpritz.com
-
Mark Datysgeld
-
Mark W. Datysgeld
-
Prudence Malinki
-
Steve Chan