Hi Manju
I couldn’t support that addition. The term used in the Request for an Issues Report is “visually confusingly similar”, which paraphrases the standard applied in the 2012 round and affirmed by SubPro recommendations 24.1 and 24.2. There is therefore
a clear definition and rationale for the use of the term.
Susan
Hi all,
During NCSG's discussion regarding this topic, some of our members raised the concerns that 'confusing similarity' is a legal term that can be interpreted in many ways. They want to caution against using the term without clear definition and rationale.
To reflect this concern, can we add 'definition and evaluating criteria in ICANN regarding confusing similarity concerning gTLD strings' in the 'suggestions on specific items to be addressed' in the request form?
Thank you!
Best,
Manju
I also support Kurt's clause and wonder whether we can get clarity on the history of the determination that only the variant of the pre-existing string is eligible to be awarded to the same RO, whereas the rule says that the similar string which is not
a variant may not proceed even if applied for by the holder of the pre-existing TLD.
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2024
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council <
council@icann.org> wrote:
Hearing no conflicting views, I accept Kurt’s proposed addition (the below Whereas clause) as a friendly amendment. Thanks Kurt.
Thanks,
Greg
|
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 Greg:
I think it would be good to signal in the motion that the Council, in its investigation to date, understands that this issue had been considered in the past and that a set of rules governing the handling of diacritics exists, i.e., that
we are not considering a new issue or that it is one of “first impression." With that goal of ‘completeness’ in mind, I suggested the additional Whereas clause in my earlier email that I repeat here:
4.5 During these discussions the Council came to understand that a set of clear rules exists regarding the delegation of TLDs including diacritics, resulting from the considered work of the Latin LGR panel, and the Council sought to learn
more concerning the rationale for those conclusions and the scope of authority of the LGR Panels and of the GNSO in considering these questions.
If the prevailing view is that the motion is better without this additional clause, that’s fine too.
Hi All- noting Steve’s clarification that may address Kurt’s concern below, do we feel that the motion needs to be amended? If so, please suggest a specific amendment that we can consider for Thursday’s meeting.
|
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.
|
I just wanted to call attention to one of the documents that Julie attached in submitting the motion on behalf of Greg. There is a proposed Request for Issue Report form which includes a section titled: Suggestions on specific items to
be addressed in the Issue Report (if any). In that section, amongst other items, it suggests the line of research mentioned by Kurt. I would encourage you all to review the request form and provide your input on whether it is captured adequately.
Good proposition, Kurt.
I'd also like to ask that if the GAC secretariat is to be informed in the Resolved para 2, then perhaps a reference as to why could be added as to a Whereas para. Otherwise, Resolved para 2 seems odd.
And while we are at it, I'd like to point out that the ALAC Chair Jonathan Zuck had sent a letter to (now former) GNSO Chair Sebastien Ducos on this Diacritics issue too, in August last year. See: Jonathan
Zuck, ALAC Chair to Sebastien Ducos, GNSO Chair [gnso.icann.org]
I’d like to add some language that ensures the Issue Report includes an explanation and rationale for the conclusions by the Latin LGR Panel that these characters should be treated as diacritics and not variant characters (if I said that
right). We should also understand where authority and restrictions lie, with the LGR as a technical body and the GNSO as a policy making body.
Maybe we could add an additional Whereas clause:
4.5 During these discussions the Council came to understand that a set of clear rules exists regarding the delegation of TLDs including diacritics, resulting from the considered work of the Latin LGR panel, and the Council sought to learn
more concerning the rationale for those conclusions and the scope of authority of the LGR Panels and of the GNSO in considering these questions.
So not a deal breaker but I am seeking to ensure that certain questions are specifically considered in the Issues Report.
Thank you so much. This is noted.
Thank you for submitting this motion. It will be posted shortly to the motions wiki
page.
Reminder, this motion will need a second.
On behalf of Greg DiBiase, GNSO Chair, who is unable to send this message at this time, please see the attached draft motion and Request for Issue Report relating to the following action per the message below:
Item 5: COUNCIL DISCUSSION - Diacritics in Latin Script and Singular/Plurals (20 minutes)
Action Items: The GNSO Council agreed to request an Issues Report on diacritics in Latin script. This request will require a vote to be scheduled
at the 16 May Council meeting.
Julie Hedlund, GNSO Support Staff
Sent on behalf of Greg DiBiase, GNSO Chair
Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday, 18 April 2024. Please refer to the Action
Item page for updates on item completion progress.
Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions.
Please refer to this page for the recent status updates on the Action items.
Please note that actions for all councilors are highlighted below.
GNSO Council meeting on 18 April 2024
Item 3: Consent Agenda (5 minutes)
GNSO Council Review of the GAC Communiqué
-
On behalf of the GNSO Chair, staff informs the ICANN Board that the GNSO Council has adopted the GNSO Council Review of the ICANN79 San Juan, Puerto Rico Communiqué Advice.
- The GNSO Liaison to the GAC informs the GAC that the GNSO Chair has informed the ICANN Board that the GNSO Council has adopted
the GNSO Council Review of the ICANN79 San Juan, Puerto Rico Communiqué Advice.
GNSO Council Small Team Guidance Document
Confirmation of Standing Predictability Implementation Review Team (SPIRT) Charter Drafting Team Leadership (Chair - Nitan Walia; Vice-chair - Alan Greenberg; GNSO Council liaison - Anne
Aikman-Scalese)
Action Items: On behalf of the GNSO Council, ICANN org support staff informs the SPIRT Charter Drafting Team and leadership team that they have been confirmed, and thanks the members, Chair
and Vice-Chair for volunteering to serve on the SPIRT Charter Drafting Team.
Item 4: COUNCIL DISCUSSION - Deferral of Policy Status Report Request - Expiration Policies (10 minutes)
Action Items: IPC Councilors to provide a suggested proposal for how to proceed with the Deferral of Policy Status Report Request - Expiration Policies
by 06 May for consideration at the 16 May Council meeting.
Item 5: COUNCIL DISCUSSION - Diacritics in Latin Script and Singular/Plurals (20 minutes)
Action Items: The GNSO Council agreed to request an Issues Report on diacritics in Latin script. This request will require a vote to be scheduled
at the 16 May Council meeting.
Item 6: COUNCIL VOTE - SubPro Supplemental Recommendations (20 minutes)
-
On behalf of the GNSO Council, the GNSO Secretariat transmits the Supplemental Recommendations to the ICANN Board, with the exception of the Topic 24 recommendation.
- GNSO Council to consider 1) a proposal from Leadership for the Small Team Plus to revisit Topic 24 and, accordingly, 2) a revised Small Team Plus assignment form.
Item 7: COUNCIL DISCUSSION - New gTLD Auction Proceeds Cross Community Working Group - Auction Proceeds (CCWG-AP) - Proposed Update to Recommendation 7 (20 minutes)
Action Items: Anne-Aikman Scalese volunteered to draft a unified response for GNSO Council review by 03 May.
Item 9: Update on Status of Privacy and Proxy Services Accreditation Implementation (15 minutes)
Action Items: None. Paul McGrady and Stephanie Perrin as Liaisons to monitor and report to Council as necessary.
Item 10: Any Other Business (10 minutes)
10.1 - IPC’s RFR decision and Council’s subsequent letter (Damon Ashcraft)
Action Items: Staff to add as a potential discussion item for the 16 May meeting.
10.3 - Replacement of Council representative to the Continuous Improvement Program Community Coordination Group (CIP-CCG)
Action Items: On behalf of the GNSO Council, the GNSO Secretariat notifies the staff support for the CIP-CCG that Damon Ashcraft has assumed the role of GNSO Council representative, replacing
Manju Chen, and thanks Damon for volunteering.
Policy Team Supporting the GNSO
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the
sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to
scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company
registered in England and Wales with company number 10689074 and registered office at 30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number
5047655 and registered office at 30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 30 Little Russell Street, London, WC1A 2HN England; Demys
Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington
and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033,
Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see
www.comlaude.com