Additional Considerations Regarding Supplemental Recommendations 24.3A, 24.3B, and 24.3C (Singular/Plural)
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<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...>
Many thanks Steve, Definitely the appropriate way forward from my point of view as a member of the Sub Pro Small Team Plus. This would hopefully also give us more time to consider the issue in relation to diacritics and the suggestion by Board and Org that the diacritics issue could be addressed in a further modification to the String Similarity Supplemental Recommendations. Reminder that I am non-voting, but I think the Council should vote to send all other Sub Pro Supplemental Recommendations to the Board, but should amend the Small Team Plus assignment form to conduct further work on String Similarity with a rapid timeline for a return recommendation from the Small Team Plus to the Council. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Fri, Apr 12, 2024 at 1:46 PM Steve Chan via council < council@gnso.icann.org> wrote:
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.
Hi Everyone: I think the diacritics issue is complex and should not be placed on the critical path for the next round. 1. As indicated by others, the identification and handling of both variants and diacritics has been considered and there is a well-settled set of rules governing them. 2. After careful consideration, the Latin LGR Group decided that Latin diacritics were not variants and, therefore their co-existence in the root was effectively banned (even if variants were permitted). Before deciding whether to re-visit the issue, I’d want the Council to understand why the LGR group arrived at those conclusions. 3. I think we should not delay in any way, the completion of the five-year sub-pro policy development process and subsequent multi-year implementation process for this issue. This could have been raised at any time during the sub-pro policy process, 4. If, after understanding why the Latin LGR is written the way is has been, a policy process similar to the recently completed IDN EPDP could be initiated. For example, the .quebec registry could use its RySG membership (or some other means) as an appropriate avenue to raise a well-defined broad policy issue. As I think we all agree, the policy issue does not concern one specific TLD, it is the reconsideration of the Latin LGR. I believe we should put Latin LGR consideration in line with our other works and assign it a priority according to the wishes of the Council. That said I’m uncertain whether there is a specified process for changing the RZ-LGRs that have been developed through a community process and ratified by the ICANN Board. As usual, my mind can be changed and I hope there are responses to this. Best regards, Kurt On 14 Apr 2024, at 4:57 am, Anne ICANN via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Many thanks Steve, Definitely the appropriate way forward from my point of view as a member of the Sub Pro Small Team Plus. This would hopefully also give us more time to consider the issue in relation to diacritics and the suggestion by Board and Org that the diacritics issue could be addressed in a further modification to the String Similarity Supplemental Recommendations. Reminder that I am non-voting, but I think the Council should vote to send all other Sub Pro Supplemental Recommendations to the Board, but should amend the Small Team Plus assignment form to conduct further work on String Similarity with a rapid timeline for a return recommendation from the Small Team Plus to the Council. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Fri, Apr 12, 2024 at 1:46 PM Steve Chan via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: 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<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...> _______________________________________________ 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.
Hi all, I agree with Kurt's points. NCSG discussed this as well yesterday and would like clarity whether the diacritics issue is a technical issue or a policy issue. Especially considering the fact that it was the LGR panel that decided that Latin diacritics were not variants, not a PDP. Warmly, Tomslin On Wed, 17 Apr 2024, 12:49 kurt kjpritz.com via council, < council@gnso.icann.org> wrote:
Hi Everyone:
I think the diacritics issue is complex and should not be placed on the critical path for the next round.
1. As indicated by others, the identification and handling of both variants and diacritics has been considered and there is a well-settled set of rules governing them. 2. After careful consideration, the Latin LGR Group decided that Latin diacritics were not variants and, therefore their co-existence in the root was effectively banned (even if variants were permitted). Before deciding whether to re-visit the issue, I’d want the Council to understand why the LGR group arrived at those conclusions. 3. I think we should not delay in any way, the completion of the five-year sub-pro policy development process and subsequent multi-year implementation process for this issue. This could have been raised at any time during the sub-pro policy process, 4. If, after understanding why the Latin LGR is written the way is has been, a policy process similar to the recently completed IDN EPDP could be initiated. For example, the .quebec registry could use its RySG membership (or some other means) as an appropriate avenue to raise a well-defined broad policy issue. As I think we all agree, the policy issue does not concern one specific TLD, it is the reconsideration of the Latin LGR.
I believe we should put Latin LGR consideration in line with our other works and assign it a priority according to the wishes of the Council. That said I’m uncertain whether there is a specified process for changing the RZ-LGRs that have been developed through a community process and ratified by the ICANN Board.
As usual, my mind can be changed and I hope there are responses to this.
Best regards,
Kurt
On 14 Apr 2024, at 4:57 am, Anne ICANN via council <council@gnso.icann.org> wrote:
Many thanks Steve, Definitely the appropriate way forward from my point of view as a member of the Sub Pro Small Team Plus. This would hopefully also give us more time to consider the issue in relation to diacritics and the suggestion by Board and Org that the diacritics issue could be addressed in a further modification to the String Similarity Supplemental Recommendations.
Reminder that I am non-voting, but I think the Council should vote to send all other Sub Pro Supplemental Recommendations to the Board, but should amend the Small Team Plus assignment form to conduct further work on String Similarity with a rapid timeline for a return recommendation from the Small Team Plus to the Council.
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Fri, Apr 12, 2024 at 1:46 PM Steve Chan via council < council@gnso.icann.org> wrote:
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.
_______________________________________________ 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.
participants (4)
-
Anne ICANN -
kurt kjpritz.com -
Steve Chan -
Tomslin Samme-Nlar