Thanks, Greg. 

I am anticipating that more will be revealed by staff/Steve on Agenda  Item 5: COUNCIL DISCUSSION - Diacritics in Latin Script and Singular/Plurals (20 minutes) at (tomorrow's) Council meeting, and I echo Jen's remark about Sarmad being likely the best person to explain the deliberations of the Latin GP which produced the Latin LGR. 

Separately, I have made a couple of suggestions (in the googledoc) to round off your proposed Amended Motion: https://docs.google.com/document/d/1B-OYl6PvxQA1wSG3y9rXrQfwDWFfNZ7DXow1PXSokyQ/edit for consistency with  Amended Explainer Document: https://docs.google.com/document/d/1YwInQ8hSaosKDBbXMyPbmbChGoGyRBGqzjOQmg_85zU/edit#heading=h.w653gx6mijb0, in the event Council decides to consider the Amended Motion.

Hope this is helpful.

Kind regards,
Justine



On Thu, 18 Apr 2024 at 09:13, Anne ICANN via council <council@icann.org> wrote:
Thanks Greg. In the amended Motion (which makes a lot of sense to me as a non-voting Councilor), shouldn't the RESOLVED clause refer specifically to the topics listed in Paragraph 14?  (The current language of the RESOLVED clause is a bit general.)

I certainly think it's worthwhile for the Small Team Plus to have its assignment form amended to study the ICANN Org proposal on singulars and plurals.  A lot of thought has been given by staff regarding how to try to address the singulars/plurals issue and we know that the Board Caucus reps are not prepared to recommend the existing revised Supplemental Recommendation to the Board.  If the existing String Similarity Supplemental Recommendation is forwarded to the Board and non-adopted, that will simply cause further delay.  I certainly applaud the Board Caucus reps and ICANN Org for their willingness to conduct further work on this issue in collaboration with the Council (and hopefully other members of the Community via the Small Team Plus.)  I note that Lars has volunteered to participate in the Council meeting to discuss this and I think that is a good idea.  (I think Lars is in LA this week.) 

As to the diacritics issue,  perhaps we should hear from Sarmad as Jennifer suggests.   I had understood that ICANN Org, in consultation with the Board or the Board Caucus, believed it might be able to supply a solution without proceeding with the study that had previously been requested by Council - in Hamburg I think.  This study was deferred because Council was advised that Board and Org might have a way to address the diacritics issue and would propose that shortly after the San Juan meeting.   Then there was a hint on the list that this issue might also be able to be address via the String Similarity Supplemental Recommendations or a Section 16 policy process.

Although the Sub Pro Co-Chairs (Jeff and Cheryl)  and Council Sub-Pro IRT Council Co-Liaisons (Susan and me) were provided with a background briefing on Org's proposal and the opportunity to ask questions on the singulars/plurals issue, it is not clear to me what Org is proposing in relation to diacritics or why the study requested by Council in Hamburg was deferred.

Thank you,
Anne

Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2024


On Wed, Apr 17, 2024 at 10:56 AM DiBiase, Gregory via council <council@icann.org> wrote:

Hi All,

 

Thanks to everyone for the initial feedback on the new proposals regarding Latin Diacritics and Singulars vs. Plurals.

 

I would like to clarify that the new question before Council at April’s meeting is: should we defer consideration of the Topic 24 Supplemental Recommendation in order to evaluate these new proposals (and consider modifying this Supplemental Recommendation based on Org’s proposal or a different version of Org’s proposal).

 

To that end, the below link has a proposed amendment to Paul’s motion to accept the SubPro Supplemental Recommendations. The amendment removes the Topic 24 Supplemental Recommendation so it can be further considered. I’ve also proposed an amendment to the Explainer Doc which follows the same logic.

 

Amended Motion: https://docs.google.com/document/d/1B-OYl6PvxQA1wSG3y9rXrQfwDWFfNZ7DXow1PXSokyQ/edit

 

Amended Explainer Document: https://docs.google.com/document/d/1YwInQ8hSaosKDBbXMyPbmbChGoGyRBGqzjOQmg_85zU/edit#heading=h.w653gx6mijb0

 

If Council decides deferral of the Topic 24 Supplemental Recommendation is warranted, I’ll propose these amendments. If not, we can proceed with Paul’s original motion.

 

I hope this is clear. I look forward to the discussion.

 

Thanks,

Greg

 

 

From: council <council-bounces@gnso.icann.org> On Behalf Of Tomslin Samme-Nlar via council
Sent: Tuesday, April 16, 2024 9:06 PM
To: kurt kjpritz.com <kurt@kjpritz.com>
Cc: GNSO Council List <council@gnso.icann.org>
Subject: RE: [EXTERNAL] [council] Additional Considerations Regarding Supplemental Recommendations 24.3A, 24.3B, and 24.3C (Singular/Plural)

 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.

 

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

 

 

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/

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.

_______________________________________________
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@icann.org
To unsubscribe send an email to council-leave@icann.org

_______________________________________________
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@icann.org
To unsubscribe send an email to council-leave@icann.org

_______________________________________________
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.