Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org> Reply-To: Julie Hedlund <julie.hedlund@icann.org> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" <dibiase@amazon.com> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org> Reply-To: Terri Agnew <terri.agnew@icann.org> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (see https://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO
Many thanks Devan. Kind regards, Julie From: Devan Reed via council <council@icann.org> Reply-To: Devan Reed <devan.reed@icann.org> Date: Monday, May 6, 2024 at 3:41 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org> Reply-To: Julie Hedlund <julie.hedlund@icann.org> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" <dibiase@amazon.com> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org> Reply-To: Terri Agnew <terri.agnew@icann.org> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (see https://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO
Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (see https://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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.
Hi Tomslin! Thank you so much. This is noted. Kind regards, Devan From: Tomslin Samme-Nlar <mesumbeslin@gmail.com> Date: Tuesday, May 7, 2024 at 4:07 AM To: Devan Reed <devan.reed@icann.org> Cc: GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org<mailto:council@icann.org>> wrote: Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Reply-To: Julie Hedlund <julie.hedlund@icann.org<mailto:julie.hedlund@icann.org>> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "DiBiase, Gregory" <dibiase@amazon.com<mailto:dibiase@amazon.com>> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (see https://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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.
Hi All: 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. Best regards, Kurt On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Tomslin! Thank you so much. This is noted. Kind regards, Devan From: Tomslin Samme-Nlar <mesumbeslin@gmail.com<mailto:mesumbeslin@gmail.com>> Date: Tuesday, May 7, 2024 at 4:07 AM To: Devan Reed <devan.reed@icann.org<mailto:devan.reed@icann.org>> Cc: GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>>, Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org<mailto:council@icann.org>> wrote: Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Reply-To: Julie Hedlund <julie.hedlund@icann.org<mailto:julie.hedlund@icann.org>> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "DiBiase, Gregory" <dibiase@amazon.com<mailto:dibiase@amazon.com>> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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.
All, 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 <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/zuck-t...> Kind regards, Justine On Tue, 7 May 2024 at 22:41, kurt kjpritz.com via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards, Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you! Kind regards, Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards, Julie Hedlund, GNSO Support Staff *Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items:
1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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) Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri 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.
Dear Councilors, 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. To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context. Best, Steve From: Justine Chew via council <council@icann.org> Reply-To: Justine Chew <justine.chew.icann@gmail.com> Date: Wednesday, May 8, 2024 at 1:51 AM To: "kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List <council@gnso.icann.org> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org> Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 All, 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]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> Kind regards, Justine On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com]<https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org<mailto:council@icann.org>> wrote: Hi All: 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. Best regards, Kurt On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Tomslin! Thank you so much. This is noted. Kind regards, Devan From: Tomslin Samme-Nlar <mesumbeslin@gmail.com<mailto:mesumbeslin@gmail.com>> Date: Tuesday, May 7, 2024 at 4:07 AM To: Devan Reed <devan.reed@icann.org<mailto:devan.reed@icann.org>> Cc: GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>>, Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org<mailto:council@icann.org>> wrote: Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Reply-To: Julie Hedlund <julie.hedlund@icann.org<mailto:julie.hedlund@icann.org>> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "DiBiase, Gregory" <dibiase@amazon.com<mailto:dibiase@amazon.com>> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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.
Hi Steve, I did read beforehand the proposed Request for Issue Report form circulated by Julie and had noted mention of the said line of research. To be clear, I expressed support for Kurt's suggestion pertaining to the proposed motion, which I thought was useful to support what's in the proposed Request for Issue Report form. But as with Kurt, I don't see it as deal breaker. Thanks for the reminder re: GAC notification. Justine On Wed, 8 May 2024 at 18:14, Steve Chan <steve.chan@icann.org> wrote:
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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.
Thanks all for your careful attention to this motion. One thing I have noted is that Root Zone Label Generation Rules as described in the upcoming AGB Request for Public Comment include a "challenge" provision as noted below. A question, after reading the ALAC letter to the Council sent by Jonathan Zuck, would be whether the issue could be successfully addressed through a potential change to the rules to be applied in connection with the challenge mechanism. Hopefully this can be addressed in the Issues Report. Below is what i understand to be the current version of the RZ-LGR language re challenge in the AGB draft: Challenging the RZ-LGR Tool calculation An applicant may challenge the validity or variant calculation of its applied-for string(s). The applicant’s ground to challenge is limited to a demonstration that its applied-for gTLD string is valid and allocatable (for variant strings) as per the RZ-LGR and that the disqualification was due to an incorrect assessment of the technical implementation of the RZ-LGR. For details see [Section xx - challenge mechanisms]. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Wed, May 8, 2024 at 3:47 AM Justine Chew via council <council@icann.org> wrote:
Hi Steve,
I did read beforehand the proposed Request for Issue Report form circulated by Julie and had noted mention of the said line of research. To be clear, I expressed support for Kurt's suggestion pertaining to the proposed motion, which I thought was useful to support what's in the proposed Request for Issue Report form. But as with Kurt, I don't see it as deal breaker.
Thanks for the reminder re: GAC notification.
Justine
On Wed, 8 May 2024 at 18:14, Steve Chan <steve.chan@icann.org> wrote:
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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.
Dear Anne, Please note that the challenge mechanism which you mentioned arises from a Phase 1 recommendation by the EPDP on IDNs. This challenge (still subject to adoption by the Board) relates only to a claimed incorrect implementation of the RZ-LGR Tool and NOT the RZ-LGR itself. In other words, the RZ-LGR itself would NOT be affected by any contemplated challenge. The RZ-LGR-5 (which incorporates the Latin LGR that has determined that labels with diacritics are not variant labels of "same" labels without diacritics and vice versa) can only be updated through the LGR and RZ-LGR processes which involve script Generation Panels and the Integration Panel. Kind regards, Justine --------- On Fri, 10 May 2024, 21:54 Anne ICANN, <anneicanngnso@gmail.com> wrote:
Thanks all for your careful attention to this motion. One thing I have noted is that Root Zone Label Generation Rules as described in the upcoming AGB Request for Public Comment include a "challenge" provision as noted below. A question, after reading the ALAC letter to the Council sent by Jonathan Zuck, would be whether the issue could be successfully addressed through a potential change to the rules to be applied in connection with the challenge mechanism.
Hopefully this can be addressed in the Issues Report. Below is what i understand to be the current version of the RZ-LGR language re challenge in the AGB draft:
Challenging the RZ-LGR Tool calculation
An applicant may challenge the validity or variant calculation of its applied-for string(s). The applicant’s ground to challenge is limited to a demonstration that its applied-for gTLD string is valid and allocatable (for variant strings) as per the RZ-LGR and that the disqualification was due to an incorrect assessment of the technical implementation of the RZ-LGR. For details see [Section xx - challenge mechanisms].
Thank you, Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Wed, May 8, 2024 at 3:47 AM Justine Chew via council <council@icann.org> wrote:
Hi Steve,
I did read beforehand the proposed Request for Issue Report form circulated by Julie and had noted mention of the said line of research. To be clear, I expressed support for Kurt's suggestion pertaining to the proposed motion, which I thought was useful to support what's in the proposed Request for Issue Report form. But as with Kurt, I don't see it as deal breaker.
Thanks for the reminder re: GAC notification.
Justine
On Wed, 8 May 2024 at 18:14, Steve Chan <steve.chan@icann.org> wrote:
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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.
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. Thanks, Greg From: Steve Chan via council <council@icann.org> Sent: Wednesday, May 8, 2024 3:14 AM To: Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com <kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org> Subject: [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 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. Dear Councilors, 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. To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context. Best, Steve From: Justine Chew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>> Date: Wednesday, May 8, 2024 at 1:51 AM To: "kurt kjpritz.com" <kurt@kjpritz.com<mailto:kurt@kjpritz.com>>, GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 All, 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]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> Kind regards, Justine On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com]<https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org<mailto:council@icann.org>> wrote: Hi All: 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. Best regards, Kurt On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Tomslin! Thank you so much. This is noted. Kind regards, Devan From: Tomslin Samme-Nlar <mesumbeslin@gmail.com<mailto:mesumbeslin@gmail.com>> Date: Tuesday, May 7, 2024 at 4:07 AM To: Devan Reed <devan.reed@icann.org<mailto:devan.reed@icann.org>> Cc: GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>>, Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org<mailto:council@icann.org>> wrote: Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Reply-To: Julie Hedlund <julie.hedlund@icann.org<mailto:julie.hedlund@icann.org>> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "DiBiase, Gregory" <dibiase@amazon.com<mailto:dibiase@amazon.com>> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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.
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. Best regards, Kurt On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com<mailto:dibiase@amazon.com>> wrote: 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. Thanks, Greg From: Steve Chan via council <council@icann.org<mailto:council@icann.org>> Sent: Wednesday, May 8, 2024 3:14 AM To: Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>>; kurt kjpritz.com<http://kjpritz.com/> <kurt@kjpritz.com<mailto:kurt@kjpritz.com>>; GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 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. Dear Councilors, 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. To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual:https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context. Best, Steve From: Justine Chew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>> Date: Wednesday, May 8, 2024 at 1:51 AM To: "kurt kjpritz.com<http://kjpritz.com>" <kurt@kjpritz.com<mailto:kurt@kjpritz.com>>, GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 All, 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]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> Kind regards, Justine On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com]<https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org<mailto:council@icann.org>> wrote: Hi All: 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. Best regards, Kurt On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Tomslin! Thank you so much. This is noted. Kind regards, Devan From: Tomslin Samme-Nlar <mesumbeslin@gmail.com<mailto:mesumbeslin@gmail.com>> Date: Tuesday, May 7, 2024 at 4:07 AM To: Devan Reed <devan.reed@icann.org<mailto:devan.reed@icann.org>> Cc: GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>>, Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org<mailto:council@icann.org>> wrote: Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Reply-To: Julie Hedlund <julie.hedlund@icann.org<mailto:julie.hedlund@icann.org>> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "DiBiase, Gregory" <dibiase@amazon.com<mailto:dibiase@amazon.com>> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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.
Hearing no conflicting views, I accept Kurt’s proposed addition (the below Whereas clause) as a friendly amendment. Thanks Kurt. Thanks, Greg From: kurt kjpritz.com <kurt@kjpritz.com> Sent: Monday, May 13, 2024 10:43 PM To: DiBiase, Gregory <dibiase@amazon.com> Cc: Steve Chan <steve.chan@icann.org>; Justine Chew <justine.chew.icann@gmail.com>; GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> Subject: RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 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. Best regards, Kurt On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com<mailto:dibiase@amazon.com>> wrote: 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. Thanks, Greg From: Steve Chan via council <council@icann.org<mailto:council@icann.org>> Sent: Wednesday, May 8, 2024 3:14 AM To: Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>>; kurt kjpritz.com<http://kjpritz.com/> <kurt@kjpritz.com<mailto:kurt@kjpritz.com>>; GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 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. Dear Councilors, 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. To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual:https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context. Best, Steve From: Justine Chew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>> Date: Wednesday, May 8, 2024 at 1:51 AM To: "kurt kjpritz.com<http://kjpritz.com>" <kurt@kjpritz.com<mailto:kurt@kjpritz.com>>, GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 All, 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]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> Kind regards, Justine On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com]<https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org<mailto:council@icann.org>> wrote: Hi All: 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. Best regards, Kurt On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Tomslin! Thank you so much. This is noted. Kind regards, Devan From: Tomslin Samme-Nlar <mesumbeslin@gmail.com<mailto:mesumbeslin@gmail.com>> Date: Tuesday, May 7, 2024 at 4:07 AM To: Devan Reed <devan.reed@icann.org<mailto:devan.reed@icann.org>> Cc: GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>>, Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org<mailto:council@icann.org>> wrote: Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Reply-To: Julie Hedlund <julie.hedlund@icann.org<mailto:julie.hedlund@icann.org>> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "DiBiase, Gregory" <dibiase@amazon.com<mailto:dibiase@amazon.com>> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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.
Agree. Warmly, Tomslin On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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
*From:* kurt kjpritz.com <kurt@kjpritz.com> *Sent:* Monday, May 13, 2024 10:43 PM *To:* DiBiase, Gregory <dibiase@amazon.com> *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < justine.chew.icann@gmail.com>; GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Best regards,
Kurt
On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> wrote:
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.
Thanks,
Greg
*From:* Steve Chan via council <council@icann.org> *Sent:* Wednesday, May 8, 2024 3:14 AM *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com < kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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.
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 anneicanngnso@gmail.com On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council < council@icann.org> wrote:
Agree.
Warmly, Tomslin
On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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
*From:* kurt kjpritz.com <kurt@kjpritz.com> *Sent:* Monday, May 13, 2024 10:43 PM *To:* DiBiase, Gregory <dibiase@amazon.com> *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < justine.chew.icann@gmail.com>; GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Best regards,
Kurt
On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> wrote:
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.
Thanks,
Greg
*From:* Steve Chan via council <council@icann.org> *Sent:* Wednesday, May 8, 2024 3:14 AM *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com < kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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.
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 On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council <council@icann.org> wrote:
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 anneicanngnso@gmail.com
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council < council@icann.org> wrote:
Agree.
Warmly, Tomslin
On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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
*From:* kurt kjpritz.com <kurt@kjpritz.com> *Sent:* Monday, May 13, 2024 10:43 PM *To:* DiBiase, Gregory <dibiase@amazon.com> *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < justine.chew.icann@gmail.com>; GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Best regards,
Kurt
On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> wrote:
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.
Thanks,
Greg
*From:* Steve Chan via council <council@icann.org> *Sent:* Wednesday, May 8, 2024 3:14 AM *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com < kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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.
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 Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: 陳曼茹 Manju Chen via council <council@icann.org> Sent: Thursday, May 16, 2024 3:25 AM To: Anne ICANN <anneicanngnso@gmail.com> Cc: GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 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 On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council <council@icann.org<mailto:council@icann.org>> wrote: 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 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council <council@icann.org<mailto:council@icann.org>> wrote: Agree. Warmly, Tomslin On Wed, 15 May 2024, 08:06 DiBiase, Gregory via council, <council@icann.org<mailto: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 From: kurt kjpritz.com<http://kjpritz.com/> <kurt@kjpritz.com<mailto:kurt@kjpritz.com>> Sent: Monday, May 13, 2024 10:43 PM To: DiBiase, Gregory <dibiase@amazon.com<mailto:dibiase@amazon.com>> Cc: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>>; Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>>; GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>>; Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 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. Best regards, Kurt On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com<mailto:dibiase@amazon.com>> wrote: 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. Thanks, Greg From: Steve Chan via council <council@icann.org<mailto:council@icann.org>> Sent: Wednesday, May 8, 2024 3:14 AM To: Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>>; kurt kjpritz.com<http://kjpritz.com/> <kurt@kjpritz.com<mailto:kurt@kjpritz.com>>; GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 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. Dear Councilors, 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. To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual:https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context. Best, Steve From: Justine Chew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>> Date: Wednesday, May 8, 2024 at 1:51 AM To: "kurt kjpritz.com<http://kjpritz.com/>" <kurt@kjpritz.com<mailto:kurt@kjpritz.com>>, GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 All, 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]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> Kind regards, Justine On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com]<https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org<mailto:council@icann.org>> wrote: Hi All: 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. Best regards, Kurt On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Tomslin! Thank you so much. This is noted. Kind regards, Devan From: Tomslin Samme-Nlar <mesumbeslin@gmail.com<mailto:mesumbeslin@gmail.com>> Date: Tuesday, May 7, 2024 at 4:07 AM To: Devan Reed <devan.reed@icann.org<mailto:devan.reed@icann.org>> Cc: GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>>, Julie Bisland via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org<mailto:council@icann.org>> wrote: Thank you for submitting this motion. It will be posted shortly to the motions<https://community.icann.org/x/tAJyEw> wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Reply-To: Julie Hedlund <julie.hedlund@icann.org<mailto:julie.hedlund@icann.org>> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, "DiBiase, Gregory" <dibiase@amazon.com<mailto:dibiase@amazon.com>> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org<mailto:council@icann.org>> Reply-To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items: 1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site. 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) Action Items: 1. 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. 2. 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. Thank you. Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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<https://comlaude.com/>
Hi Susan, Thank you for the clarification. I have no problems using existing definition and rationale if they've acquired community consensus. I'd therefore suggest we clearly list the references in the Issue Report and avoid paraphrasing but stick to the original wording that has community consensus. Thank you! Best, Manju On Thu, May 16, 2024 at 12:21 PM Susan Payne <susan.payne@comlaude.com> wrote:
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
Get Outlook for iOS <https://aka.ms/o0ukef> ------------------------------ *From:* 陳曼茹 Manju Chen via council <council@icann.org> *Sent:* Thursday, May 16, 2024 3:25 AM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
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
On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council <council@icann.org> wrote:
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 anneicanngnso@gmail.com
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council < council@icann.org> wrote:
Agree.
Warmly, Tomslin
On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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
*From:* kurt kjpritz.com <kurt@kjpritz.com> *Sent:* Monday, May 13, 2024 10:43 PM *To:* DiBiase, Gregory <dibiase@amazon.com> *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < justine.chew.icann@gmail.com>; GNSO Council List < council@gnso.icann.org>; Julie Bisland via Gnso-secs < gnso-secs@icann.org> *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Best regards,
Kurt
On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> wrote:
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.
Thanks,
Greg
*From:* Steve Chan via council <council@icann.org> *Sent:* Wednesday, May 8, 2024 3:14 AM *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com < kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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 <https://comlaude.com/>
I'm not at all clear on similarity of strings in the context of determination of variants or the rule which states that the same Registry Operator cannot be awarded a string which is deemed similar unless that string is a "variant". The String Contention process was identified in Module 4 of the 2012 AGB. The language there says: In this Applicant Guidebook, “similar” means strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone. The link to Module 4 is here: https://newgtlds.icann.org/sites/default/files/string-contention-procedures-... Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Wed, May 15, 2024 at 9:35 PM 陳曼茹 Manju Chen <manju@nii.org.tw> wrote:
Hi Susan,
Thank you for the clarification. I have no problems using existing definition and rationale if they've acquired community consensus. I'd therefore suggest we clearly list the references in the Issue Report and avoid paraphrasing but stick to the original wording that has community consensus.
Thank you!
Best, Manju
On Thu, May 16, 2024 at 12:21 PM Susan Payne <susan.payne@comlaude.com> wrote:
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
Get Outlook for iOS <https://aka.ms/o0ukef> ------------------------------ *From:* 陳曼茹 Manju Chen via council <council@icann.org> *Sent:* Thursday, May 16, 2024 3:25 AM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
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
On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council <council@icann.org> wrote:
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 anneicanngnso@gmail.com
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council < council@icann.org> wrote:
Agree.
Warmly, Tomslin
On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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
*From:* kurt kjpritz.com <kurt@kjpritz.com> *Sent:* Monday, May 13, 2024 10:43 PM *To:* DiBiase, Gregory <dibiase@amazon.com> *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < justine.chew.icann@gmail.com>; GNSO Council List < council@gnso.icann.org>; Julie Bisland via Gnso-secs < gnso-secs@icann.org> *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Best regards,
Kurt
On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> wrote:
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.
Thanks,
Greg
*From:* Steve Chan via council <council@icann.org> *Sent:* Wednesday, May 8, 2024 3:14 AM *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com < kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" <dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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 <https://comlaude.com/>
Dear Anne, Variants at the Top-Level (variant labels) are planned to be introduced for the first time in the Next Round, hence there is no reference to it in the 2012 AGB. The "rule" that proposes to that variant labels must, if they are allocatable and applied-for, go to the same registry operator, is the "Same-Entity" rule captured in a number of recommendations out of the IDNs-EPDP Phase 1 report, which are still pending Board approval. Variant labels, by definition, are labels that mean the same. I think you're seeing variants and confusingly similar strings as the same, but by definition they aren't the same thing, though both serve the goal of lowering the risk of end user confusion. Hope this helps. Kind regards, Justine On Thu, 16 May 2024 at 12:52, Anne ICANN via council <council@icann.org> wrote:
I'm not at all clear on similarity of strings in the context of determination of variants or the rule which states that the same Registry Operator cannot be awarded a string which is deemed similar unless that string is a "variant".
The String Contention process was identified in Module 4 of the 2012 AGB. The language there says:
In this Applicant Guidebook, “similar” means strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone.
The link to Module 4 is here: https://newgtlds.icann.org/sites/default/files/string-contention-procedures-...
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Wed, May 15, 2024 at 9:35 PM 陳曼茹 Manju Chen <manju@nii.org.tw> wrote:
Hi Susan,
Thank you for the clarification. I have no problems using existing definition and rationale if they've acquired community consensus. I'd therefore suggest we clearly list the references in the Issue Report and avoid paraphrasing but stick to the original wording that has community consensus.
Thank you!
Best, Manju
On Thu, May 16, 2024 at 12:21 PM Susan Payne <susan.payne@comlaude.com> wrote:
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
Get Outlook for iOS <https://aka.ms/o0ukef> ------------------------------ *From:* 陳曼茹 Manju Chen via council <council@icann.org> *Sent:* Thursday, May 16, 2024 3:25 AM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
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
On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council < council@icann.org> wrote:
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 anneicanngnso@gmail.com
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council < council@icann.org> wrote:
Agree.
Warmly, Tomslin
On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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
*From:* kurt kjpritz.com <kurt@kjpritz.com> *Sent:* Monday, May 13, 2024 10:43 PM *To:* DiBiase, Gregory <dibiase@amazon.com> *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < justine.chew.icann@gmail.com>; GNSO Council List < council@gnso.icann.org>; Julie Bisland via Gnso-secs < gnso-secs@icann.org> *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Best regards,
Kurt
On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> wrote:
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.
Thanks,
Greg
*From:* Steve Chan via council <council@icann.org> *Sent:* Wednesday, May 8, 2024 3:14 AM *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com < kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
*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.
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" <dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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 <https://comlaude.com/>
_______________________________________________ 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.
Makes sense, Justine. And here again Latin proves to be a specific script that needs further attention, given that it both is and isn't in that category of carrying the same meaning. So... it does fit, depending on interpretation. --- Mark W. Datysgeld from Governance Primer ________________________________ From: Justine Chew via council <council@icann.org> Sent: Thursday, May 16, 2024 04:13 To: Anne ICANN Cc: GNSO Council List; Julie Bisland via Gnso-secs Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Dear Anne, Variants at the Top-Level (variant labels) are planned to be introduced for the first time in the Next Round, hence there is no reference to it in the 2012 AGB. The "rule" that proposes to that variant labels must, if they are allocatable and applied-for, go to the same registry operator, is the "Same-Entity" rule captured in a number of recommendations out of the IDNs-EPDP Phase 1 report, which are still pending Board approval. Variant labels, by definition, are labels that mean the same. I think you're seeing variants and confusingly similar strings as the same, but by definition they aren't the same thing, though both serve the goal of lowering the risk of end user confusion. Hope this helps. Kind regards, Justine On Thu, 16 May 2024 at 12:52, Anne ICANN via council <council@icann.org> wrote:
I'm not at all clear on similarity of strings in the context of determination of variants or the rule which states that the same Registry Operator cannot be awarded a string which is deemed similar unless that string is a "variant".
The String Contention process was identified in Module 4 of the 2012 AGB. The language there says:
In this Applicant Guidebook, “similar” means strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone.
The link to Module 4 is here: https://newgtlds.icann.org/sites/default/files/string-contention-procedures-...
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Wed, May 15, 2024 at 9:35 PM 陳曼茹 Manju Chen <manju@nii.org.tw> wrote:
Hi Susan,
Thank you for the clarification. I have no problems using existing definition and rationale if they've acquired community consensus. I'd therefore suggest we clearly list the references in the Issue Report and avoid paraphrasing but stick to the original wording that has community consensus.
Thank you!
Best, Manju
On Thu, May 16, 2024 at 12:21 PM Susan Payne <susan.payne@comlaude.com> wrote:
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
Get Outlook for iOS ________________________________ From: 陳曼茹 Manju Chen via council <council@icann.org> Sent: Thursday, May 16, 2024 3:25 AM To: Anne ICANN <anneicanngnso@gmail.com> Cc: GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 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
On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council <council@icann.org> wrote:
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 anneicanngnso@gmail.com
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council <council@icann.org> wrote:
Agree.
Warmly, Tomslin
On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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 From: kurt kjpritz.com <kurt@kjpritz.com> Sent: Monday, May 13, 2024 10:43 PM To: DiBiase, Gregory <dibiase@amazon.com> Cc: Steve Chan <steve.chan@icann.org>; Justine Chew <justine.chew.icann@gmail.com>; GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> Subject: RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
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. Best regards, Kurt
> On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> wrote: > > 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. > > Thanks, > Greg > > From: Steve Chan via council <council@icann.org> > Sent: Wednesday, May 8, 2024 3:14 AM > To: Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com <kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> > Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org> > Subject: [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 > > 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. > > Dear Councilors, > > 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. > > To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual:https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context. > > Best, > Steve > > From: Justine Chew via council <council@icann.org> > Reply-To: Justine Chew <justine.chew.icann@gmail.com> > Date: Wednesday, May 8, 2024 at 1:51 AM > To: "kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List <council@gnso.icann.org> > Cc: Julie Bisland via Gnso-secs <gnso-secs@icann.org> > Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 > > All, > 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] > > Kind regards, > Justine > > > On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] via council <council@icann.org> wrote: >> >> Hi All: >> >> 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. >> >> Best regards, >> >> Kurt >> >> >>> >>> On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote: >>> >>> Hi Tomslin! >>> >>> Thank you so much. This is noted. >>> >>> Kind regards, >>> Devan >>> >>> From: Tomslin Samme-Nlar <mesumbeslin@gmail.com> >>> Date: Tuesday, May 7, 2024 at 4:07 AM >>> To: Devan Reed <devan.reed@icann.org> >>> Cc: GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> >>> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 >>> >>> Hi Devan, >>> >>> I second the motion. >>> >>> Warmly, >>> Tomslin >>> >>> On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote: >>>> >>>> Thank you for submitting this motion. It will be posted shortly to the motions wiki page. >>>> >>>> Reminder, this motion will need a second. >>>> >>>> Thank you! >>>> Kind regards, >>>> Devan >>>> >>>> From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org> >>>> Reply-To: Julie Hedlund <julie.hedlund@icann.org> >>>> Date: Monday, May 6, 2024 at 2:21 PM >>>> To: "council@gnso.icann.org" <council@gnso.icann.org> >>>> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" <dibiase@amazon.com> >>>> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 >>>> >>>> Dear Councilors, >>>> >>>> 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. >>>> >>>> Kind regards, >>>> Julie Hedlund, GNSO Support Staff >>>> Sent on behalf of Greg DiBiase, GNSO Chair >>>> >>>> From: Terri Agnew via council <council@icann.org> >>>> Reply-To: Terri Agnew <terri.agnew@icann.org> >>>> Date: Monday, April 22, 2024 at 5:11 PM >>>> To: "council@gnso.icann.org" <council@gnso.icann.org> >>>> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> >>>> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 >>>> >>>> Dear Councilors, >>>> >>>> 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é >>>> Action Items: >>>> 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 >>>> Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]) to the GNSO site. >>>> >>>> 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) >>>> Action Items: >>>> 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. >>>> >>>> Thank you. >>>> >>>> Kind regards, >>>> >>>> Terri >>>> 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
_______________________________________________ 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.
Thanks Justine. With this background, can you provide more info on the deliberations in the IDNs work that resulted in the requirement that the similar string be classified as a variant by RZ-LGR before it could be awarded to an applicant already operating a pre-existing similar string? Many thanks for the additional info provided below. i think we now understand that the rule requiring the similar string to be a variant before it can be awarded to the operator of the pre-existing string came out of IDN policy work. Is that correct? Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Thu, May 16, 2024 at 12:14 AM Justine Chew <justine.chew.icann@gmail.com> wrote:
Dear Anne,
Variants at the Top-Level (variant labels) are planned to be introduced for the first time in the Next Round, hence there is no reference to it in the 2012 AGB. The "rule" that proposes to that variant labels must, if they are allocatable and applied-for, go to the same registry operator, is the "Same-Entity" rule captured in a number of recommendations out of the IDNs-EPDP Phase 1 report, which are still pending Board approval.
Variant labels, by definition, are labels that mean the same.
I think you're seeing variants and confusingly similar strings as the same, but by definition they aren't the same thing, though both serve the goal of lowering the risk of end user confusion.
Hope this helps.
Kind regards, Justine
On Thu, 16 May 2024 at 12:52, Anne ICANN via council <council@icann.org> wrote:
I'm not at all clear on similarity of strings in the context of determination of variants or the rule which states that the same Registry Operator cannot be awarded a string which is deemed similar unless that string is a "variant".
The String Contention process was identified in Module 4 of the 2012 AGB. The language there says:
In this Applicant Guidebook, “similar” means strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone.
The link to Module 4 is here: https://newgtlds.icann.org/sites/default/files/string-contention-procedures-...
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Wed, May 15, 2024 at 9:35 PM 陳曼茹 Manju Chen <manju@nii.org.tw> wrote:
Hi Susan,
Thank you for the clarification. I have no problems using existing definition and rationale if they've acquired community consensus. I'd therefore suggest we clearly list the references in the Issue Report and avoid paraphrasing but stick to the original wording that has community consensus.
Thank you!
Best, Manju
On Thu, May 16, 2024 at 12:21 PM Susan Payne <susan.payne@comlaude.com> wrote:
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
Get Outlook for iOS <https://aka.ms/o0ukef> ------------------------------ *From:* 陳曼茹 Manju Chen via council <council@icann.org> *Sent:* Thursday, May 16, 2024 3:25 AM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
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
On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council < council@icann.org> wrote:
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 anneicanngnso@gmail.com
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council < council@icann.org> wrote:
Agree.
Warmly, Tomslin
On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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 > > > > *From:* kurt kjpritz.com <kurt@kjpritz.com> > *Sent:* Monday, May 13, 2024 10:43 PM > *To:* DiBiase, Gregory <dibiase@amazon.com> > *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < > justine.chew.icann@gmail.com>; GNSO Council List < > council@gnso.icann.org>; Julie Bisland via Gnso-secs < > gnso-secs@icann.org> > *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] > Motion & Request for Issue Report Re: Action Items | GNSO Council meeting > 18 April 2024 > > > > *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. > > > > Best regards, > > > > Kurt > > > > > > > > On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> > wrote: > > > > 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. > > > > Thanks, > > Greg > > > > *From:* Steve Chan via council <council@icann.org> > *Sent:* Wednesday, May 8, 2024 3:14 AM > *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com > <kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> > *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> > *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] > Motion & Request for Issue Report Re: Action Items | GNSO Council meeting > 18 April 2024 > > > > *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. > > > > Dear Councilors, > > > > 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. > > > > To Justine’s comment, the action identified in Resolved para 2 of > the motion comes from section 5 of the PDP Manual: > https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... > If any Councilors wishes to add more context about Resolved para 2, that is > the relevant context. > > > > Best, > > Steve > > > > *From: *Justine Chew via council <council@icann.org> > *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> > *Date: *Wednesday, May 8, 2024 at 1:51 AM > *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < > council@gnso.icann.org> > *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> > *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request > for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 > > > > All, > > 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] > <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> > > > Kind regards, > Justine > > > > > > On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] > <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> > via council <council@icann.org> wrote: > > Hi All: > > > > 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. > > > > Best regards, > > > > Kurt > > > > > > On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> > wrote: > > > > Hi Tomslin! > > > > Thank you so much. This is noted. > > > > Kind regards, > > Devan > > > > *From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> > *Date: *Tuesday, May 7, 2024 at 4:07 AM > *To: *Devan Reed <devan.reed@icann.org> > *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via > Gnso-secs <gnso-secs@icann.org> > *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for > Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 > > > > Hi Devan, > > > > I second the motion. > > > > Warmly, > Tomslin > > > > On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> > wrote: > > Thank you for submitting this motion. It will be posted shortly to > the motions <https://community.icann.org/x/tAJyEw> wiki page. > > > > Reminder, this motion will need a second. > > > > Thank you! > > Kind regards, > > Devan > > > > *From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> > *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> > *Date: *Monday, May 6, 2024 at 2:21 PM > *To: *"council@gnso.icann.org" <council@gnso.icann.org> > *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, > Gregory" <dibiase@amazon.com> > *Subject: *[gnso-secs] Motion & Request for Issue Report Re: > [council] Action Items | GNSO Council meeting 18 April 2024 > > > > Dear Councilors, > > > > 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. > > > > Kind regards, > > Julie Hedlund, GNSO Support Staff > > *Sent on behalf of Greg DiBiase, GNSO Chair* > > > > *From: *Terri Agnew via council <council@icann.org> > *Reply-To: *Terri Agnew <terri.agnew@icann.org> > *Date: *Monday, April 22, 2024 at 5:11 PM > *To: *"council@gnso.icann.org" <council@gnso.icann.org> > *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> > *Subject: *[council] Action Items | GNSO Council meeting 18 April > 2024 > > > > Dear Councilors, > > > > 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 > <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é > > Action Items: > > 1. 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. > 2. 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 > > Action Items: The Policy Support Staff posts the updated Small Team > Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... > [gnso.icann.org] > <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) > to the GNSO site. > > > > 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) > > Action Items: > > 1. 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. > 2. 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. > > > > Thank you. > > > > Kind regards, > > > > Terri > > 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 <https://comlaude.com/>
_______________________________________________ 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.
Dear Anne, Per the IDNs-EPDP Phase 1 Final Report <https://mm.icann.org/pipermail/council/attachments/20231108/fcbce142/Phase1F...> which was approved by Council on 18 Jan <https://community.icann.org/x/_IAvEQ> for onward submission to the ICANN Board, *4.1 RZ-LGR as the Sole Source* Final Recommendation 1.1: The RZ-LGR must be the sole source to calculate the variant labels and disposition values for all existing gTLDs. *4.2 Same Entity Principle* Final Recommendation 2.1: Any *allocatable* variant label of an existing gTLD, as calculated by the RZ-LGR, can only be allocated to the same registry operator or withheld for possible allocation only to that registry operator. I encourage you to read the rationale provided in the Report for these final recommendations, and I trust this answers your question(s) with finality. Kind regards, Justine On Fri, 17 May 2024 at 02:07, Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Justine. With this background, can you provide more info on the deliberations in the IDNs work that resulted in the requirement that the similar string be classified as a variant by RZ-LGR before it could be awarded to an applicant already operating a pre-existing similar string?
Many thanks for the additional info provided below. i think we now understand that the rule requiring the similar string to be a variant before it can be awarded to the operator of the pre-existing string came out of IDN policy work. Is that correct?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Thu, May 16, 2024 at 12:14 AM Justine Chew < justine.chew.icann@gmail.com> wrote:
Dear Anne,
Variants at the Top-Level (variant labels) are planned to be introduced for the first time in the Next Round, hence there is no reference to it in the 2012 AGB. The "rule" that proposes to that variant labels must, if they are allocatable and applied-for, go to the same registry operator, is the "Same-Entity" rule captured in a number of recommendations out of the IDNs-EPDP Phase 1 report, which are still pending Board approval.
Variant labels, by definition, are labels that mean the same.
I think you're seeing variants and confusingly similar strings as the same, but by definition they aren't the same thing, though both serve the goal of lowering the risk of end user confusion.
Hope this helps.
Kind regards, Justine
On Thu, 16 May 2024 at 12:52, Anne ICANN via council <council@icann.org> wrote:
I'm not at all clear on similarity of strings in the context of determination of variants or the rule which states that the same Registry Operator cannot be awarded a string which is deemed similar unless that string is a "variant".
The String Contention process was identified in Module 4 of the 2012 AGB. The language there says:
In this Applicant Guidebook, “similar” means strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone.
The link to Module 4 is here: https://newgtlds.icann.org/sites/default/files/string-contention-procedures-...
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Wed, May 15, 2024 at 9:35 PM 陳曼茹 Manju Chen <manju@nii.org.tw> wrote:
Hi Susan,
Thank you for the clarification. I have no problems using existing definition and rationale if they've acquired community consensus. I'd therefore suggest we clearly list the references in the Issue Report and avoid paraphrasing but stick to the original wording that has community consensus.
Thank you!
Best, Manju
On Thu, May 16, 2024 at 12:21 PM Susan Payne <susan.payne@comlaude.com> wrote:
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
Get Outlook for iOS <https://aka.ms/o0ukef> ------------------------------ *From:* 陳曼茹 Manju Chen via council <council@icann.org> *Sent:* Thursday, May 16, 2024 3:25 AM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
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
On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council < council@icann.org> wrote:
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 anneicanngnso@gmail.com
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council < council@icann.org> wrote:
> Agree. > > Warmly, > Tomslin > > On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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 >> >> >> >> *From:* kurt kjpritz.com <kurt@kjpritz.com> >> *Sent:* Monday, May 13, 2024 10:43 PM >> *To:* DiBiase, Gregory <dibiase@amazon.com> >> *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < >> justine.chew.icann@gmail.com>; GNSO Council List < >> council@gnso.icann.org>; Julie Bisland via Gnso-secs < >> gnso-secs@icann.org> >> *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] >> Motion & Request for Issue Report Re: Action Items | GNSO Council meeting >> 18 April 2024 >> >> >> >> *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. >> >> >> >> Best regards, >> >> >> >> Kurt >> >> >> >> >> >> >> >> On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> >> wrote: >> >> >> >> 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. >> >> >> >> Thanks, >> >> Greg >> >> >> >> *From:* Steve Chan via council <council@icann.org> >> *Sent:* Wednesday, May 8, 2024 3:14 AM >> *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com >> <kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> >> *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> >> *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] >> Motion & Request for Issue Report Re: Action Items | GNSO Council meeting >> 18 April 2024 >> >> >> >> *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. >> >> >> >> Dear Councilors, >> >> >> >> 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. >> >> >> >> To Justine’s comment, the action identified in Resolved para 2 of >> the motion comes from section 5 of the PDP Manual: >> https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... >> If any Councilors wishes to add more context about Resolved para 2, that is >> the relevant context. >> >> >> >> Best, >> >> Steve >> >> >> >> *From: *Justine Chew via council <council@icann.org> >> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> >> *Date: *Wednesday, May 8, 2024 at 1:51 AM >> *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < >> council@gnso.icann.org> >> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> >> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & >> Request for Issue Report Re: Action Items | GNSO Council meeting 18 April >> 2024 >> >> >> >> All, >> >> 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] >> <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> >> >> >> Kind regards, >> Justine >> >> >> >> >> >> On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] >> <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> >> via council <council@icann.org> wrote: >> >> Hi All: >> >> >> >> 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. >> >> >> >> Best regards, >> >> >> >> Kurt >> >> >> >> >> >> On 7 May 2024, at 2:31 pm, Devan Reed via council < >> council@icann.org> wrote: >> >> >> >> Hi Tomslin! >> >> >> >> Thank you so much. This is noted. >> >> >> >> Kind regards, >> >> Devan >> >> >> >> *From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> >> *Date: *Tuesday, May 7, 2024 at 4:07 AM >> *To: *Devan Reed <devan.reed@icann.org> >> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland >> via Gnso-secs <gnso-secs@icann.org> >> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request >> for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 >> >> >> >> Hi Devan, >> >> >> >> I second the motion. >> >> >> >> Warmly, >> Tomslin >> >> >> >> On Tue, 7 May 2024, 05:41 Devan Reed via council, < >> council@icann.org> wrote: >> >> Thank you for submitting this motion. It will be posted shortly to >> the motions <https://community.icann.org/x/tAJyEw> wiki page. >> >> >> >> Reminder, this motion will need a second. >> >> >> >> Thank you! >> >> Kind regards, >> >> Devan >> >> >> >> *From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> >> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> >> *Date: *Monday, May 6, 2024 at 2:21 PM >> *To: *"council@gnso.icann.org" <council@gnso.icann.org> >> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, >> Gregory" <dibiase@amazon.com> >> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: >> [council] Action Items | GNSO Council meeting 18 April 2024 >> >> >> >> Dear Councilors, >> >> >> >> 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. >> >> >> >> Kind regards, >> >> Julie Hedlund, GNSO Support Staff >> >> *Sent on behalf of Greg DiBiase, GNSO Chair* >> >> >> >> *From: *Terri Agnew via council <council@icann.org> >> *Reply-To: *Terri Agnew <terri.agnew@icann.org> >> *Date: *Monday, April 22, 2024 at 5:11 PM >> *To: *"council@gnso.icann.org" <council@gnso.icann.org> >> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> >> *Subject: *[council] Action Items | GNSO Council meeting 18 April >> 2024 >> >> >> >> Dear Councilors, >> >> >> >> 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 >> <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é >> >> Action Items: >> >> 1. 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. >> 2. 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 >> >> Action Items: The Policy Support Staff posts the updated Small Team >> Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... >> [gnso.icann.org] >> <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) >> to the GNSO site. >> >> >> >> 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) >> >> Action Items: >> >> 1. 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. >> 2. 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. >> >> >> >> Thank you. >> >> >> >> Kind regards, >> >> >> >> Terri >> >> 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 <https://comlaude.com/>
_______________________________________________ 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.
Hi Justine, So I'm thinking that the prohibition on the same entity acquiring the diacritic even if it is not a variant under the RZ-LGR rules actually comes out of the Affirmation of a 2007 policy that is contained in 24.1 of the Sub Pro Final Report stating that a string that is similar to a pre-existing string cannot proceed. But then the exception for officially designated variants applied for by the "same entity" must have come out of the IDN work in EPDP Phase 1. Is that your understanding? So it appears that the question of an application for a diacritic that is not a variant by the "same entity" that operates the pre-existing similar string has not been specifically addressed in policy work? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Thu, May 16, 2024 at 11:07 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Justine. With this background, can you provide more info on the deliberations in the IDNs work that resulted in the requirement that the similar string be classified as a variant by RZ-LGR before it could be awarded to an applicant already operating a pre-existing similar string?
Many thanks for the additional info provided below. i think we now understand that the rule requiring the similar string to be a variant before it can be awarded to the operator of the pre-existing string came out of IDN policy work. Is that correct?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Thu, May 16, 2024 at 12:14 AM Justine Chew < justine.chew.icann@gmail.com> wrote:
Dear Anne,
Variants at the Top-Level (variant labels) are planned to be introduced for the first time in the Next Round, hence there is no reference to it in the 2012 AGB. The "rule" that proposes to that variant labels must, if they are allocatable and applied-for, go to the same registry operator, is the "Same-Entity" rule captured in a number of recommendations out of the IDNs-EPDP Phase 1 report, which are still pending Board approval.
Variant labels, by definition, are labels that mean the same.
I think you're seeing variants and confusingly similar strings as the same, but by definition they aren't the same thing, though both serve the goal of lowering the risk of end user confusion.
Hope this helps.
Kind regards, Justine
On Thu, 16 May 2024 at 12:52, Anne ICANN via council <council@icann.org> wrote:
I'm not at all clear on similarity of strings in the context of determination of variants or the rule which states that the same Registry Operator cannot be awarded a string which is deemed similar unless that string is a "variant".
The String Contention process was identified in Module 4 of the 2012 AGB. The language there says:
In this Applicant Guidebook, “similar” means strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone.
The link to Module 4 is here: https://newgtlds.icann.org/sites/default/files/string-contention-procedures-...
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com
On Wed, May 15, 2024 at 9:35 PM 陳曼茹 Manju Chen <manju@nii.org.tw> wrote:
Hi Susan,
Thank you for the clarification. I have no problems using existing definition and rationale if they've acquired community consensus. I'd therefore suggest we clearly list the references in the Issue Report and avoid paraphrasing but stick to the original wording that has community consensus.
Thank you!
Best, Manju
On Thu, May 16, 2024 at 12:21 PM Susan Payne <susan.payne@comlaude.com> wrote:
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
Get Outlook for iOS <https://aka.ms/o0ukef> ------------------------------ *From:* 陳曼茹 Manju Chen via council <council@icann.org> *Sent:* Thursday, May 16, 2024 3:25 AM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject:* [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
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
On Thu, May 16, 2024 at 5:48 AM Anne ICANN via council < council@icann.org> wrote:
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 anneicanngnso@gmail.com
On Tue, May 14, 2024 at 3:11 PM Tomslin Samme-Nlar via council < council@icann.org> wrote:
> Agree. > > Warmly, > Tomslin > > On Wed, 15 May 2024, 08:06 DiBiase, Gregory 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 >> >> >> >> *From:* kurt kjpritz.com <kurt@kjpritz.com> >> *Sent:* Monday, May 13, 2024 10:43 PM >> *To:* DiBiase, Gregory <dibiase@amazon.com> >> *Cc:* Steve Chan <steve.chan@icann.org>; Justine Chew < >> justine.chew.icann@gmail.com>; GNSO Council List < >> council@gnso.icann.org>; Julie Bisland via Gnso-secs < >> gnso-secs@icann.org> >> *Subject:* RE: [EXTERNAL] [council] [Ext] Re: Re: [gnso-secs] >> Motion & Request for Issue Report Re: Action Items | GNSO Council meeting >> 18 April 2024 >> >> >> >> *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. >> >> >> >> Best regards, >> >> >> >> Kurt >> >> >> >> >> >> >> >> On 14 May 2024, at 3:24 am, DiBiase, Gregory <dibiase@amazon.com> >> wrote: >> >> >> >> 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. >> >> >> >> Thanks, >> >> Greg >> >> >> >> *From:* Steve Chan via council <council@icann.org> >> *Sent:* Wednesday, May 8, 2024 3:14 AM >> *To:* Justine Chew <justine.chew.icann@gmail.com>; kurt kjpritz.com >> <kurt@kjpritz.com>; GNSO Council List <council@gnso.icann.org> >> *Cc:* Julie Bisland via Gnso-secs <gnso-secs@icann.org> >> *Subject:* [EXTERNAL] [council] Re: [Ext] Re: Re: [gnso-secs] >> Motion & Request for Issue Report Re: Action Items | GNSO Council meeting >> 18 April 2024 >> >> >> >> *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. >> >> >> >> Dear Councilors, >> >> >> >> 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. >> >> >> >> To Justine’s comment, the action identified in Resolved para 2 of >> the motion comes from section 5 of the PDP Manual: >> https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... >> If any Councilors wishes to add more context about Resolved para 2, that is >> the relevant context. >> >> >> >> Best, >> >> Steve >> >> >> >> *From: *Justine Chew via council <council@icann.org> >> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> >> *Date: *Wednesday, May 8, 2024 at 1:51 AM >> *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < >> council@gnso.icann.org> >> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> >> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & >> Request for Issue Report Re: Action Items | GNSO Council meeting 18 April >> 2024 >> >> >> >> All, >> >> 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] >> <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> >> >> >> Kind regards, >> Justine >> >> >> >> >> >> On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] >> <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> >> via council <council@icann.org> wrote: >> >> Hi All: >> >> >> >> 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. >> >> >> >> Best regards, >> >> >> >> Kurt >> >> >> >> >> >> On 7 May 2024, at 2:31 pm, Devan Reed via council < >> council@icann.org> wrote: >> >> >> >> Hi Tomslin! >> >> >> >> Thank you so much. This is noted. >> >> >> >> Kind regards, >> >> Devan >> >> >> >> *From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> >> *Date: *Tuesday, May 7, 2024 at 4:07 AM >> *To: *Devan Reed <devan.reed@icann.org> >> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland >> via Gnso-secs <gnso-secs@icann.org> >> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request >> for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 >> >> >> >> Hi Devan, >> >> >> >> I second the motion. >> >> >> >> Warmly, >> Tomslin >> >> >> >> On Tue, 7 May 2024, 05:41 Devan Reed via council, < >> council@icann.org> wrote: >> >> Thank you for submitting this motion. It will be posted shortly to >> the motions <https://community.icann.org/x/tAJyEw> wiki page. >> >> >> >> Reminder, this motion will need a second. >> >> >> >> Thank you! >> >> Kind regards, >> >> Devan >> >> >> >> *From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> >> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> >> *Date: *Monday, May 6, 2024 at 2:21 PM >> *To: *"council@gnso.icann.org" <council@gnso.icann.org> >> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, >> Gregory" <dibiase@amazon.com> >> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: >> [council] Action Items | GNSO Council meeting 18 April 2024 >> >> >> >> Dear Councilors, >> >> >> >> 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. >> >> >> >> Kind regards, >> >> Julie Hedlund, GNSO Support Staff >> >> *Sent on behalf of Greg DiBiase, GNSO Chair* >> >> >> >> *From: *Terri Agnew via council <council@icann.org> >> *Reply-To: *Terri Agnew <terri.agnew@icann.org> >> *Date: *Monday, April 22, 2024 at 5:11 PM >> *To: *"council@gnso.icann.org" <council@gnso.icann.org> >> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> >> *Subject: *[council] Action Items | GNSO Council meeting 18 April >> 2024 >> >> >> >> Dear Councilors, >> >> >> >> 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 >> <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é >> >> Action Items: >> >> 1. 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. >> 2. 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 >> >> Action Items: The Policy Support Staff posts the updated Small Team >> Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... >> [gnso.icann.org] >> <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) >> to the GNSO site. >> >> >> >> 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) >> >> Action Items: >> >> 1. 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. >> 2. 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. >> >> >> >> Thank you. >> >> >> >> Kind regards, >> >> >> >> Terri >> >> 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 <https://comlaude.com/>
_______________________________________________ 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.
Hi Steve, Many thanks for this direction. I guess what I am wondering at this point has less to do with the issue of determination of variants and more to do with the policy regarding when a string can proceed if the same operator has applied for it and the string is determined to be similar but NOT a variant. In other words, why does an applied-for string have to be classified as a variant in order for the same operator to obtain an exception to allow the highly similar string to proceed? The current rule prevents the string from proceeding at all if is it deemed confusingly similar. The only exception is if the applicant is the same operator and the string is deemed a variant in the Root Zone Label Generation rules. Is there a way to address that rule in policy-making and why did that rule result from previous work? Is it possible that a similar string can actually be allowed to proceed if it's similar to a pre-existing TLD and the applicant is the same operator as the pre-existing TLD? Why would we want to prevent that? Eager to hear the rationale and comments from others more familiar with the history of this rule. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Wed, May 8, 2024 at 3:14 AM Steve Chan via council <council@icann.org> wrote:
Dear Councilors,
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.
To Justine’s comment, the action identified in Resolved para 2 of the motion comes from section 5 of the PDP Manual: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd.... If any Councilors wishes to add more context about Resolved para 2, that is the relevant context.
Best,
Steve
*From: *Justine Chew via council <council@icann.org> *Reply-To: *Justine Chew <justine.chew.icann@gmail.com> *Date: *Wednesday, May 8, 2024 at 1:51 AM *To: *"kurt kjpritz.com" <kurt@kjpritz.com>, GNSO Council List < council@gnso.icann.org> *Cc: *Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
All,
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] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>
Kind regards, Justine
On Tue, 7 May 2024 at 22:41, kurt kjpritz.com [kjpritz.com] <https://urldefense.com/v3/__http:/kjpritz.com__;!!PtGJab4!_KNTA8R-z3RPBVZHTZ...> via council <council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards,
Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you!
Kind regards,
Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards,
Julie Hedlund, GNSO Support Staff
*Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é
Action Items:
1. 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. 2. 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
Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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)
Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri
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.
Thanks Kurt. I agree that these questions need to be answered in the Issues Report. Thanks for pointing this out! Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Tue, May 7, 2024 at 7:41 AM kurt kjpritz.com via council < council@icann.org> wrote:
Hi All:
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.
Best regards,
Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin!
Thank you so much. This is noted.
Kind regards, Devan
*From: *Tomslin Samme-Nlar <mesumbeslin@gmail.com> *Date: *Tuesday, May 7, 2024 at 4:07 AM *To: *Devan Reed <devan.reed@icann.org> *Cc: *GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> *Subject: *[Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024
Hi Devan,
I second the motion.
Warmly, Tomslin
On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions <https://community.icann.org/x/tAJyEw> wiki page.
Reminder, this motion will need a second.
Thank you! Kind regards, Devan
*From: *Julie Hedlund via Gnso-secs <gnso-secs@icann.org> *Reply-To: *Julie Hedlund <julie.hedlund@icann.org> *Date: *Monday, May 6, 2024 at 2:21 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" < dibiase@amazon.com> *Subject: *[gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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.
Kind regards, Julie Hedlund, GNSO Support Staff *Sent on behalf of Greg DiBiase, GNSO Chair*
*From: *Terri Agnew via council <council@icann.org> *Reply-To: *Terri Agnew <terri.agnew@icann.org> *Date: *Monday, April 22, 2024 at 5:11 PM *To: *"council@gnso.icann.org" <council@gnso.icann.org> *Cc: *"gnso-secs@icann.org" <gnso-secs@icann.org> *Subject: *[council] Action Items | GNSO Council meeting 18 April 2024
Dear Councilors,
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 <https://community.icann.org/display/gnsocouncilmeetings/Action+Items> 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é Action Items:
1. 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. 2. 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...>) to the GNSO site.
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) Action Items:
1. 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. 2. 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.
Thank you.
Kind regards,
Terri 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.
I agree with Kurt's point. I have been independently reaching out to people involved in the generation of the rules and I honestly think we need some clarity as to whether it was clear to them how the outcome of their work would be used. The Latin script is unique in its reach and it's difficult/impossible to make it conform with other scripts in which there is much more rigidity. The Issue Report should ask: "The differentiation between Latin script languages in which accented characters are interchangeable versus those in which they are not is not accounted for in the rules. Was this a deliberate decision or is this an artifact of how rules need to be written within the scope of the work?" Or something along those general lines. Best, --- Mark W. Datysgeld from Governance Primer ________________________________ From: "kurt kjpritz.com via council" <council@icann.org> Sent: Tuesday, May 7, 2024 11:41 To: GNSO Council List Cc: Julie Bisland via Gnso-secs Subject: [council] Re: [Ext] Re: Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi All: 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. Best regards, Kurt
On 7 May 2024, at 2:31 pm, Devan Reed via council <council@icann.org> wrote:
Hi Tomslin! Thank you so much. This is noted. Kind regards, Devan From: Tomslin Samme-Nlar <mesumbeslin@gmail.com> Date: Tuesday, May 7, 2024 at 4:07 AM To: Devan Reed <devan.reed@icann.org> Cc: GNSO Council List <council@gnso.icann.org>, Julie Bisland via Gnso-secs <gnso-secs@icann.org> Subject: [Ext] Re: [council] Re: [gnso-secs] Motion & Request for Issue Report Re: Action Items | GNSO Council meeting 18 April 2024 Hi Devan, I second the motion. Warmly, Tomslin On Tue, 7 May 2024, 05:41 Devan Reed via council, <council@icann.org> wrote:
Thank you for submitting this motion. It will be posted shortly to the motions wiki page. Reminder, this motion will need a second. Thank you! Kind regards, Devan From: Julie Hedlund via Gnso-secs <gnso-secs@icann.org> Reply-To: Julie Hedlund <julie.hedlund@icann.org> Date: Monday, May 6, 2024 at 2:21 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "DiBiase, Gregory" <dibiase@amazon.com> Subject: [gnso-secs] Motion & Request for Issue Report Re: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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. Kind regards, Julie Hedlund, GNSO Support Staff Sent on behalf of Greg DiBiase, GNSO Chair From: Terri Agnew via council <council@icann.org> Reply-To: Terri Agnew <terri.agnew@icann.org> Date: Monday, April 22, 2024 at 5:11 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] Action Items | GNSO Council meeting 18 April 2024 Dear Councilors, 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é Action Items: 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 Action Items: The Policy Support Staff posts the updated Small Team Guidelines (seehttps://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-t... [gnso.icann.org]) to the GNSO site. 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) Action Items: 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. Thank you. Kind regards, Terri 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.
participants (11)
-
Anne ICANN -
Devan Reed -
DiBiase, Gregory -
Julie Hedlund -
Justine Chew -
kurt kjpritz.com -
Mark W. Datysgeld -
Steve Chan -
Susan Payne -
Tomslin Samme-Nlar -
陳曼茹 Manju Chen