May 2024 - council - lists.icann.org

**Starting in 15 minutes | Meeting Invitation | GNSO Council Meeting | Thursday, 16 May 2024
by Terri Agnew May 16, 2024

May 16, 2024

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 16 May 2024 at 05:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/BYDyEg Check your time zone: https://tinyurl.com/4dthynkr [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4dthynkr__;!!PtGJab4!87RUV2F…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Passcode: f!Ym9!npfN If joining Zoom via Zoom App the following will be required: Webinar ID: 922 8356 5389 Passcode: 6981311025 Or One tap mobile : +13462487799,,92283565389#,,,,*6981311025# US (Houston) +16699006833,,92283565389#,,,,*6981311025# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/adGHfYeA3T [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/adGHfYeA3T__;!!PtGJab4!9…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/tQJyEw> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

2 1

Recordings | GNSO Council Meeting | Thursday, 16 May 2024
by Terri Agnew May 16, 2024

May 16, 2024

Dear all, Please find below the audio recording and zoom recording (audio, visual, rough transcript, and chat) of the GNSO Council Meeting that took place on Thursday, 16 May 2024 at 05:00 UTC. Audio only: https://icann.zoom.us/rec/play/LPi5KW5x9NmrKN00MBTfBckHjXreMoW2X77k8SX-oM8P… Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/share/wCk-Zmdzc4TuptOTtI9i11IPGjiXQMvS6s4wzmFshGz… The recordings and transcriptions of the calls are posted on the GNSO Calendar page. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

GNSO Council resolutions 16 May 2024
by Terri Agnew May 16, 2024

May 16, 2024

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday, 16 May 2024, which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. 20240516-1 Consent Agenda Motion to Adopt the Revised Description of the Role of the GNSO Liaison to the Governmental Advisory Committee (GAC) Submitted by: Greg Dibiase WHEREAS, 1. The GNSO Liaison to the GAC role was first piloted in FY15-16 (1 July 2014 to 30 June 2016) as part of a broader initiative of the GAC-GNSO Consultation Group to facilitate early engagement of the GAC in GNSO policy development activities. 2. Due to the success of the pilot, the GNSO Liaison to the GAC is now a permanent role and an integral part of communications between the GAC and GNSO. 3. On 23 September 2021, the GNSO Council decided to extend each term of the GNSO Council Liaison to the GAC to two years and to impose a term limit of two consecutive two-year terms. 4. At the ICANN79 GNSO Council Wrap-up Session, the Council agreed to review the description of the GNSO Liaison to the GAC role prior to initiating the Standing Selection Committee’s (SSC) process to open an Expression of Interest (EOI) and subsequently select a new liaison to assume the role at the 2024 Annual General Meeting (ICANN81). 5. Post ICANN79, the Council reviewed the liaison role description and suggested several revisions. 6. After allowing time for Council to review the revisions, staff incorporated them into a final clean version<https://gnso.icann.org/sites/default/files/policy/2024/draft/final-gnso-lia…> as well as a redlined version<https://gnso.icann.org/sites/default/files/policy/2024/draft/redline-gnso-l…> for Council’s consideration at its meeting on 16 May. RESOLVED, 1. The GNSO Council adopts the revised description of the GNSO Liaison to the GAC role and directs staff to post it on the Council activities procedures page<https://gnso.icann.org/en/council/procedures>. 2. The GNSO Council directs staff to notify the GAC leadership of the revised description of the 3. GNSO Liaison to the GAC role. Vote results<https://gnso.icann.org/sites/default/files/policy/2024/vote-result/gnso-cou…> 20240516-2 Consent Agenda Motion to Approve the ICANN Board’s Proposed Amendment to Cross-Community Working Group on Auction Proceeds Recommendation 7 Submitted by: Greg Dibiase WHEREAS, 1. On 2 March 2024<https://www.icann.org/en/system/files/correspondence/sinha-to-clemente-et-a…>, the ICANN Board wrote to the Chartering Organizations of the Cross-Community Working Group on Auction Proceeds (“CCWG-AP”), which includes the GNSO; 2. The CCWG-AP’s Recommendation 7 sets out limitations on the use of ICANN accountability mechanisms (namely, the Independent Review Process, IRP, and Reconsideration process) to challenge decisions made on individual applications within the Grant Program; 3. The CCWG-AP provided Recommendation 7 to minimize use of the proceeds for purposes other than grants, such as administrative costs or legal fees; 4. The ICANN Board noted that it supports the CCWG AP’s goal in making this recommendation, but ICANN org identified challenges in implementing Recommendation 7 as written; 5. The Board considered whether there are further ways to meet the community’s broader intention with Recommendation 7, and asked the relevant Chartering Organizations to consider the removal of the phrase “from the Independent Project Applications Panel” from Recommendation 7, noting that many of the Board’s concerns that supported the October 2023 action<https://www.icann.org/en/board-activities-and-meetings/materials/minutes-re…> would be addressed. RESOLVED, 1. The GNSO Council accepts the Board’s suggestion to remove the phrase “from the Independent Project Applications Panel” from CCWG-AP Recommendation 7. The GNSO Council would like to clarify that this approval only applies to CCWG-AP Recommendation 7 and does not extend to the proposed new ByLaw restricting access to Accountability Mechanisms. 2. The GNSO Council requests the GNSO Secretariat to inform the Board of its acceptance of the Board’s suggestion for CCWG-AP Recommendation 7. Vote results<https://gnso.icann.org/sites/default/files/policy/2024/vote-result/gnso-cou…> 20240516-3 **WITHDRAWN UNTIL JUNE 2024** Motion to Defer Request for Policy Status Report on Expiration Policies Submitted by: Greg Dibiase Seconded by: Tomslin Samme-Nlar WHEREAS, 1. In October 2020, the GNSO Council considered the timing to request a Policy Status Report (PSR) to conduct a review of the two Expiration Policies, the Expired Domain Deletion Policy<https://www.icann.org/resources/pages/registars/accreditation/eddp-en> (EDDP) and the Expired Registration Recovery Policy<https://www.icann.org/en/resources/registrars/consensus-policies/errp> (ERRP) and <https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso…> agreed to defer<https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso…> consideration for 24 months given concerns about capacity; 2. In July 2022, the Council revisited the question of when to request a PSR and <https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso…> agreed<https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso…> that, prior to proceeding with a PSR or deferral, the GNSO Council should consult with registrars and ICANN Compliance to determine if there are any known issues or concerns with the two Expiration Policies that could warrant requesting a PSR; 3. On 1 November 2022, ICANN org provided a <https://mm.icann.org/pipermail/council/2022-November/026164.html> report<https://mm.icann.org/pipermail/council/2022-November/026164.html> on the Expiration Policies and presented the report to the GNSO Council during its <https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso…> November 2022 meeting<https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso…>; 4. Following discussion of the ICANN org <https://mm.icann.org/pipermail/council/2022-November/026164.html> report<https://mm.icann.org/pipermail/council/2022-November/026164.html>, a small team of Councilors reviewed the report and the previous feedback from registrars and presented its <https://docs.google.com/document/d/1zxxyIsg7HVGtAK7HsaTfw3nMX_zZfY3hUrdiDoa…> recommendation<https://docs.google.com/document/d/1zxxyIsg7HVGtAK7HsaTfw3nMX_zZfY3hUrdiDoa…> to the GNSO Council during its <https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso…> March 2023 meeting<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso…>; 5. The GNSO Council agreed to the small team’s recommendation to request additional information from ICANN org regarding what expiration-related educational materials are currently published and whether additional information can be provided; 6. On 14 February 2024, ICANN org delivered a <https://mm.icann.org/pipermail/council/2024-February/027778.html> summary<https://mm.icann.org/pipermail/council/2024-February/027778.html> of the current educational materials on domain name renewal and expiration and presented it during the February 2024 meeting<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>; 7. Having considered (i) the input from the Registrar Stakeholder Group, who was asked to flag substantial issues with the policies that would warrant a near team request for policy status report and did not note any issues, (ii) the <https://mm.icann.org/pipermail/council/2022-November/026164.html> report<https://mm.icann.org/pipermail/council/2022-November/026164.html> from ICANN org, which noted confusion with key terms in the policy and registrant confusion with the auto-renew grace period and aftermarket activities, et.al<http://et.al>., and (iii) the <https://mm.icann.org/pipermail/council/2024-February/027778.html> catalog<https://mm.icann.org/pipermail/council/2024-February/027778.html> of available educational resources on domain name expiration and renewal, the GNSO Council determined that the Expiration Policies present no urgent need for policy work, and, accordingly, the Council will revisit the timing for a PSR request in two years, or sooner if the Council is informed that further policy work is needed before the conclusion of two years. RESOLVED, 1. The GNSO Council adopts the motion to defer consideration of a Policy Status Report (PSR) for the Expedited Domain Deletion Policy (EDDP) and Expedited Registration Recovery Policy (ERRP) for two years, noting, however, that if the Council is informed that further policy work is needed before the conclusion of two years, the Council will reconsider the PSR request at that time. 2. The GNSO Council leadership directs GNSO Policy Support Staff to notify ICANN org Global Domains & Services of the deferral of the PSR request on the Expiration Policies. Vote results<https://gnso.icann.org/sites/default/files/policy/2024/vote-result/gnso-cou…> 20240516-4 (Updated with the friendly amendment proposed by Kurt Pritz and Manju Chen, accepted by Greg DiBiase and Tomslin Samme-Nlar) Motion to Request an Issue Report for Diacritics in Latin Script with Friendly Amendment Submitted by: Greg DiBiase Seconded by: Tomslin Samme-Nlar WHEREAS, 1. The GNSO Council agreed during the 18 April 2023 meeting<https://gnso.icann.org/sites/default/files/policy/2024/transcript/transcrip…> to request an Issue Report on diacritics in Latin script. 2. Per the ICANN Bylaws Section 11.3(i)(i)<https://www.icann.org/resources/pages/governance/bylaws-en/#article11>, the request for an Issue Report will require an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. 3. The GNSO Council was made aware of a potential issue whereby future applied-for strings in the Latin script containing diacritics may be visually confusingly similar to American Standard Code for Information Interchange (ASCII) strings, are non-variants, and the same entity wishes to operate both strings. 4. During the GNSO Council Meeting at ICANN78 in Hamburg on 25 October 2023<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>, the GNSO Council received a detailed briefing on this issue and agreed to request a study from ICANN org to help inform the GNSO Council on the issue of diacritics in Latin Script. Prior to the request being made to ICANN org, the org volunteered to investigate what mechanism or mechanisms might be appropriate to address this issue. 5. Following the discussion during its April 2024 meeting<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/NSXhHFF5NVqRpg6rU…>, the Council discussed requesting an Issue Report on diacritics in the Latin Script. On 06 May 2024, the request for an Issue Report<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/C33MSZ3YSG…> was circulated to the Council mailing list. 6. 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. RESOLVED, 1. The GNSO Council adopts the request for an Issue Report and directs staff to create the Report. 2. The GNSO Council requests that the GNSO Liaison to the GAC notifies the GAC Secretariat of this request. Vote results<https://gnso.icann.org/sites/default/files/policy/2024/vote-result/gnso-cou…> Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | Pre-ICANN80 GNSO Council Webinar | Tuesday, 21 May 2024 at 21:00 UTC
by Terri Agnew May 16, 2024

May 16, 2024

Dear all, The Pre-ICANN80 GNSO Council Webinar is scheduled on Tuesday, 21 May 2024 at 21:00 UTC for 60 minutes. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/DIC5Ew Check your time zone: https://tinyurl.com/2s3cekkr GNSO Council members are expected to join and will be panelists. Questions will be taken from GNSO Council only. Observers are welcome and will be in listen-only mode. Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Passcode: f!Ym9!npfN If joining Zoom via Zoom App the following will be required: Webinar ID: 922 8356 5389 Passcode: 6981311025 Or One tap mobile : +13462487799,,92283565389#,,,,*6981311025# US (Houston) +16699006833,,92283565389#,,,,*6981311025# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/adGHfYeA3T <https://urldefense.com/v3/__https:/icann.zoom.us/u/adGHfYeA3T__;!!PtGJab4!5…> Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | Informal Joint Meeting with ICANN Board and GNSO Council | Monday, 20 May 2024
by Terri Agnew May 15, 2024

May 15, 2024

Dear all, The Informal Joint Meeting with ICANN Board and GNSO Council is scheduled on Monday, 20 May 2024 at 13:00 UTC for 1 hour. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/eoGfEw Check your time zone: https://tinyurl.com/yfpa56ud [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yfpa56ud__;!!PtGJab4!7peq6yf…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Passcode: f!Ym9!npfN If joining Zoom via Zoom App the following will be required: Webinar ID: 922 8356 5389 Passcode: 6981311025 Or One tap mobile : +13462487799,,92283565389#,,,,*6981311025# US (Houston) +16699006833,,92283565389#,,,,*6981311025# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/adGHfYeA3T <https://urldefense.com/v3/__https:/icann.zoom.us/u/adGHfYeA3T__;!!PtGJab4!9…> Observers are welcome to join, they will be in a read-only and listen-only mode. Thank you. Kind regards, Devan Policy Team Supporting the GNSO

1 0

GNSO Council Absence Notification Form: Damon Ashcraft
by GNSO Council via ICANN May 15, 2024

May 15, 2024

Full Name of Officer: Lori Schulman Officer Email Address: lschulman(a)inta.org Date Prepared: 15 May 2024 GNSO Organization: Intellectual Property Constituency Officer Position or Title: President Name of Absent Councilor: Damon Ashcraft Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Damon Ashcraft has a family emergency. His father passed away last night. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: Proxy may vote on all matters and decisions before the Council in its May 16th 2024 Meeting.and any other meetings or decisions taken through June 30th 2024. Date upon which the remedy will expire or terminate: 30 June 2024 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). Yes Full Name of GNSO Councilor Serving as Voting Proxy: Susan Payne By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0

2nd update on agenda | Proposed Agenda | GNSO Council Meeting | Thursday, 16 May 2024
by Terri Agnew May 15, 2024

May 15, 2024

Hello all, One more item has been added to AOB. 10.7 - Informal meeting with ICANN Board <https://community.icann.org/x/eoGfEw> on Monday, 20 May at 13:00 UTC Thanks! Terri From: Terri Agnew <terri.agnew(a)icann.org> Date: Tuesday, May 14, 2024 at 6:13 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: UPDATED agenda | Proposed Agenda | GNSO Council Meeting | Thursday, 16 May 2024 Dear all, The GNSO Council agenda has been updated with the following. 1. Item 1.4: Minutes<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> of the GNSO Council Meeting on 18 April 2024 were posted on 03 May 2024. 2. With Greg’s email to the council mailing list a short time ago, the Deferral of Policy Status Report Request - Expiration Policies item has now been changed from [vote] to [discussion] and moved from item 4 to 5. 3. Added two additional AOB to item 10: * 10.5 - Transfer Policy Working Group Letter<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/JFZMG4D7AR…> from Chair * 10.6 - Pre-ICANN80 GNSO Policy Webinar on Tuesday, 21 May at 21:00 UTC - Note: GNSO Councilor Attendance is mandatory All updates are on the wiki agenda page: https://community.icann.org/x/BYDyEg Thank you. Kind regards, Terri From: Terri Agnew via Gnso-secs <gnso-secs(a)icann.org> Reply-To: Terri Agnew <terri.agnew(a)icann.org> Date: Thursday, May 2, 2024 at 3:45 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Proposed Agenda | GNSO Council Meeting | Thursday, 16 May 2024 Dear all, Please find below the final proposed agenda for the GNSO Council Meeting taking place on Thursday, 16 May 2024 at 05:00 UTC for 2 hours This has been posted on the agenda wiki page<https://community.icann.org/x/BYDyEg>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO GNSO Council Agenda 16 May 2024 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/tQJyEw. This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> v3.5, updated on 15 March 2023. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Thursday, 16 May 2024 at 05:00 UTC: https://tinyurl.com/4dthynkr [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4dthynkr__;!!PtGJab4!_QP42ZK…> 22:00 Los Angeles (Wednesday); 01:00 Washington DC; 22:00 London; 06:00 Paris; 08:00 Moscow; 15:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (5 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council Meeting on 06 March 2024 were posted on 23 March 2024. Minutes<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> of the GNSO Council Meeting on 18 April 2024 were posted on 03 May 2024. Item 2: Opening Remarks / Review of Projects & Action List (0 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/project__;!!Pt…> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * GNSO Liaison to the Governmental Advisory Committee * Council Response to Board Letter on CCWG Auction Proceeds Recommendation 7 Item 4: COUNCIL VOTE - Request for Preliminary Issue Report for Diacritics in Latin Script (15 minutes) The GNSO Council was made aware of a potential issue whereby future applied-for strings in the Latin script containing diacritics may be confusingly similar to ASCII strings, are non-variants, and the same entity wishes to operate both strings. For background, an applied-for IDN gTLD string in the Latin script containing diacritics, which is NOT an allocatable variant label of the base ASCII string (existing or applied-for) according to RZ-LGR, are sometimes seen as equivalents. In some instances, however, the base ASCII string is seen as a workaround and not necessarily “correct”. The base ASCII string and the Latin diacritic string may be determined to be confusingly similar (i.e., in which case, the strings would be placed in a contention set or if an existing gTLD is involved, the applied-for label would not pass the String Similarity Review). During the GNSO Council Meeting at ICANN78 in Hamburg on 25 October 2023 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>, the GNSO Council received a detailed briefing on this issue and agreed to request a study from ICANN org to help inform the GNSO Council on the issue of diacritics in Latin Script. Prior to the request being made to ICANN org, the org volunteered to investigate what mechanism or mechanisms might be appropriate to address this issue. Following the discussion during its April 2024 meeting [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/NSXhHFF5NVqRpg6rU…>, the Council discussed requesting a Preliminary Issue Report on diacritics in the Latin Script. On 06 May<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/C33MSZ3YSG…>, the request for an Issue Report was circulated to the Council mailing list. Here, the Council will vote to request ICANN org to deliver a Preliminary Issue Report on diacritics in the Latin Script. 4.1 - Introduction of Motion (Greg DiBiase, GNSO Chair) 4.2 - Council Discussion 4.3 - Council Vote (Voting threshold: simple majority) Item 5: COUNCIL DISCUSSION - Deferral of Policy Status Report Request - Expiration Policies (15 minutes) The GNSO Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the Expired Domain Name Deletion Policy (“EDDP”) and the Expired Registration Recovery Policy (“ERRP”). In November 2020, given concerns about its capacity and no known issues with the policies, the Council agreed to delay the request for the Policy Status Report (PSR) for a period of 24 months. After 24 months had passed, the Council reconsidered whether it was an appropriate time to request a PSR. To that end, in July 2022, the Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. In making its decision whether to request to a PSR at this time, the Council consulted: 1. Registrars, who were asked to flag substantial issues with the policies that would warrant a near-term request for PSR and did not note any issues 2. ICANN Compliance, who provided a write-up<https://mm.icann.org/pipermail/council/2022-November/026164.html>, noting confusion with key terms in the policy and persistent registrant confusion with the auto-renew grace period and aftermarket activities, et al. 3. ICANN org Registrant Program, which provided a catalog of the available educational resources on domain name expiration and renewal (Brian Gutterman’s update at Council) In reviewing these materials, the Council determined that the EDDP and ERRP seem to have been implemented as intended and imminent policy work is not needed at this time. Accordingly, the GNSO Council will reconsider a PSR on the Expiration Policies in two years time, or earlier, if a need is determined and it is requested. Here, the Council will vote to consider a PSR on the Expiration Policies in two years. 5.1 - Presentation of Motion (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Council vote (voting threshold: simple majority) Item 6: COUNCIL DISCUSSION - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (“CCOICI”) Pilot Survey Results (20 minutes) Over the course of several months in 2021, the GNSO Council discussed how it could best approach the GNSO’s work that is focused on structural, procedural, and process improvements, and specifically not policy development. Notably, this work affects the GNSO community more broadly, and not just the GNSO Council. Given concerns about workload and the efficacy of the approach to this portfolio of work, the GNSO Council resolved [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> on 16 June 2021 to initiate the Council Committee for Overseeing and Implementing Continuous Improvement (“CCOICI”) Framework as a pilot and to reevaluate the Framework after the conclusion of its tasks. The pilot handled the following assigned tasks: 1) GNSO Working Group Self-Assessment Requirements; 2) GNSO Statement of Interest (SOI) Requirements; and 3) Assessment of Accountability Work Stream 2 Requirements. To conclude the pilot, the CCOICI administered a survey<https://community.icann.org/display/CCFOICI/c.+CCOICI+Pilot+Survey?preview=…> to all relevant ICANN Community Stakeholder Groups and Constituencies during 1 February-5 March 2024. In administering this survey, the CCOICI assessed the views of each SG/C to evaluate if the Council and GNSO community see value in continuing the use of the CCOICI Framework and if needed, determine how it could be improved. If the survey results noted a significant issue, this should be the trigger to initiate appropriate measures to deal with such issues. Here, the Council will receive an overview of the results of the survey and discuss the next steps for the CCOICI. 6.1 - Introduction of Topic (Manju Chen, Chair of CCOICI) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - Intellectual Property Constituency Request for Reconsideration (15 minutes) On 22 November 2023, the Intellectual Property Constituency (IPC) filed a Request for Reconsideration<https://www.icann.org/en/system/files/files/reconsideration-23-2-ipc-reques…> of the ICANN Board Resolutions 2023.10.26.11 and 2023.10.26.122<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…>, regarding (i) the actions and inactions that led to (a) the ICANN Board’s public comment of 6 December 2018 on the Initial Report<https://www.icann.org/en/system/files/files/new-gtld-auction-proceeds-initi…> of the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP), (b) the organization of the public comment phase<https://www.icann.org/en/public-comment/proceeding/proposed-final-report-of…> on the Proposed Final Report<https://www.icann.org/en/system/files/files/proposed-new-gtld-auction-proce…> of the New gTLD Auction Proceeds Cross Community Working Group, (c) the ICANN Board Resolutions 2022.06.12.13 to 2022.06.12.16 , and (ii) the actions and inactions involving the implementation of the ICANN Grant Giving Program. Here, the Council will hear an update on the Request for Consideration and discuss potential next steps for the Council, if any. 7.1 - Introduction of Topic (Damon Ashcraft, GNSO Councilor for IPC) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar (20 minutes) During the GNSO Council’s most recent strategic planning session, the Council discussed the topic of how to be an effective manager of the GNSO’s Policy Development Process (PDP). In recognition of the importance of regularly reviewing the Council’s portfolio of work, the Council agreed to the following action item, “During a session at ICANN79, Council to prepare for a careful review of the work captured in the Program Management Tool (PMT) that will conclude or initiate prior to the next AGM, or continue beyond the next AGM[.]” The Council conducted this inaugural review of the Projects List during its Working Session at ICANN79<https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Workin…> on Sunday, 3 March 2024. The review also intended to include an overview of the Action Decision Radar<https://community.icann.org/display/gnsocouncilmeetings/Action+Decision+Rad…> (“ADR”); however, due to time constraints, the Council agreed to review the ADR at an upcoming Council meeting. The ADR is a tool designed to assist the Council by highlighting imminent decisions or actions that need to be taken by the GNSO Council. The ADR contains a series of range markers, e.g., 0-1 month, 1-3 months, etc., to alert the Council to the timing of the upcoming action or decision. Here, the Council will review the contents of the ADR and discuss next steps. 8.1 - Introduction of Topic (Tomslin Samme-NIar, GNSO Vice-Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: GNSO Council Aspirational Statement (10 minutes) During its most recent strategic planning session, the GNSO Council discussed the desire to have a common understanding of how outputs from the bottom-up multistakeholder model should be voted on at the Council level. Specifically, the Council agreed to the following action items coming out of the SPS: Proposed Action Item 4.1: Council to develop an aspirational (non-binding) statement to reflect that Councilors should not seek to undo bottom-up consensus-driven outcomes of GNSO WGs. Proposed Action Item 4.2: Once action item 4.1 is complete, Councilors to leverage the aspirational statement to build awareness within their respective SG/Cs. Here, the Council will discuss the most recent iteration of the aspirational statement [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1QioeB3MAWb9J…>, which seeks to incorporate the previous feedback from Councilors and discuss next steps. 9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 9.2 - Council Discussion 9.3 - Next Steps Item 10: Any Other Business (15 minutes) 10.1 - Update on ICANN80 planning and GNSO Draft schedule [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> 10.2 - ccNSO & GAC Liaison updates (every three months) 10.3 - SPS Action Item Updates: Recommendation Reports and GNSO Liaisons to WGs 10.4 - Call for Volunteers [lists.icann.org]<https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/council@…>- Privacy and Proxy Services Accreditation Implementation Review Team (PPSAI) 10.5 - Transfer Policy Working Group Letter<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/JFZMG4D7AR…> from Chair 10.6 - Pre-ICANN80 GNSO Policy Webinar<https://community.icann.org/x/DIC5Ew> on Tuesday, 21 May at 21:00 UTC - Note: GNSO Councilor Attendance is mandatory 10.7 - Informal meeting with ICANN Board <https://community.icann.org/x/eoGfEw> on Monday, 20 May at 13:00 UTC _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> References for Coordinated Universal Time of 05:00 UTC Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ [timeanddate.com]<https://urldefense.com/v3/__https:/www.timeanddate.com/time/change/__;!!PtG…> for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 22:00 (Wednesday) San José, Costa Rica (CST) UTC-6 23:00 (Wednesday) New York/Washington DC, USA (EDT) UTC-4 01:00 Buenos Aires, Argentina (ART) UTC-3 02:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:00 Paris, France (CEST) UTC+2 07:00 Moscow, Russia (MSK) UTC+3 08:00 Singapore (SGT) UTC+8 13:00 Melbourne, Australia (AEST) UTC+10 15:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.com/v3/__http:/www.timeanddate.com/__;!!PtGJab4!_QP42ZKm…> and https://tinyurl.com/4dthynkr [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4dthynkr__;!!PtGJab4!_QP42ZK…>

1 0

Please read: Upcoming GNSO Council meeting prep 16 May 2024 at 05:00 UTC
by Terri Agnew May 15, 2024

May 15, 2024

Dear all, A few reminders of prep for the Council meeting 16 May 2024 at 05:00 UTC. 1. Please review the GNSO Council meeting Cheat Sheet <https://urldefense.com/v3/__https:/docs.google.com/document/d/1lQ9fqEjD-inZ…> in order to help you prepare for the session and also provide your input in suggestion mode. It is also attached to this email for your convenience. 1. All documents mentioned on the Council agenda<https://community.icann.org/x/BYDyEg> will be listed on the Document wiki page<https://community.icann.org/x/tQJyEw> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio<https://community.icann.org/pages/viewpage.action?pageId=150178769>, in particular the Action Decision Radar<https://community.icann.org/x/14vzC> and the Project List<https://community.icann.org/x/1YvzC> . 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | GNSO Council Meeting | Thursday, 16 May 2024
by Terri Agnew May 15, 2024

May 15, 2024

Dear all, The GNSO Council meeting is scheduled on Thursday, 16 May 2024 at 05:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/BYDyEg Check your time zone: https://tinyurl.com/4dthynkr [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4dthynkr__;!!PtGJab4!87RUV2F…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92283565389?pwd=QnlHK1JS…> Passcode: f!Ym9!npfN If joining Zoom via Zoom App the following will be required: Webinar ID: 922 8356 5389 Passcode: 6981311025 Or One tap mobile : +13462487799,,92283565389#,,,,*6981311025# US (Houston) +16699006833,,92283565389#,,,,*6981311025# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/adGHfYeA3T [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/adGHfYeA3T__;!!PtGJab4!9…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/tQJyEw> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Policy Status Report (PSR) on the Expedited Domain Deletion Policy (EDDP) and Expedited Registration Recovery Policy (ERRP)
by Susan Payne May 15, 2024

May 15, 2024

Hi all At our last Council meeting we discussed the proposed deferral of a Policy Status Report (PSR) on the Expedited Domain Deletion Policy (EDDP) and Expedited Registration Recovery Policy (ERRP) (together referred to here as the "Expired Domains Policies") and Damon and I noted that there was some concern from IPC members about deferring such a PSR. We would now like to formally propose that Council does ask staff to conduct a PSR, and that we do not defer this request. Our reasons are as follows: * A PSR is simply a review of whether the Expired Domains Policies are operating effectively, as intended, and whether there are any issues or unintended consequences. It would be a more formal review than has been done to date, with an opportunity for community review and input on the draft. A PSR does not necessarily mean that further action or policy work would then be required, although of course this could be an outcome. * IPC members do consider that there is an issue to be explored, and a need for data in order that the community can understand how the Expired Domains Policies operate in practice, when they are utilised and whether/how often domains never go through the EDDP process due to practices whereby domains do not actually expire, i.e. data on the number of domains that are: * recaptured, * re-registered, * monetized and * auctioned by registrars and their affiliates. * IPC members believe that such aftermarket practices have the potential to impact on competition as between registrars, since names are not allowed to lapse and thus are not available to other registrars to register. They also impact would-be registrants, who cannot work with their choice of registrar but must acquire such domains through specific registrars and their affiliate auction houses. * Further, when such domains do not expire, this can create legal problems with respect to the conjunctive bad faith registration requirements for cybersquatting claims in certain jurisdictions, which have viewed the date of initial registration (not the date of re-registration on transfer) as being the relevant date for assessment of bad faith. Thus, an initial good faith registration is carried forward (inappropriately) to shield all subsequent bad faith uses from liability. An example of this is GoPets Ltd, heard in the US 9th Circuit which held that registration is determined at the time of the initial registration and not re-registration. This holding creates a fairly big loophole that can cause serious harm to consumers. * At a minimum, therefore, we consider that it is now an appropriate time for review and the gathering of data, in order to better inform the community. * The PDP Manual (Annex 2 of the GNSO Operating Procedures) clearly recognises the importance of reviewing policies after they have been implemented for a period, in s17: Periodic Assessments of Approved Policies Periodic assessment of PDP recommendations and policies is an important tool to guard against unexpected results or inefficient processes arising from GNSO policies. PDP Teams are encouraged to include proposed timing, assessment tools, and metrics for review as part of their Final Report. In addition, the GNSO Council may at any time initiate reviews of past policy recommendations. * In the case of the Expired Domains Policies, both have been in operation for many years, decades in the case of the EDDP, without review. The EDDP became effective on 21 December 2004, the ERRP on 31 August 2013. The question of when to conduct a PSR came onto Council's agenda in October 2020 and was deferred for two years. It was discussed again in mid-2022, following which there were various actions undertaken by Org staff. It is now mid-2024. Given the age of these policies and the defacto 4-year deferral to date, a PSR is long overdue. Even leaving aside the specific questions about the aftermarket referred to above, as a matter of good practice, and in order to meet the expectations of the PDP Manual, we believe that the PSR ought now to be requested and not postponed any further. We do appreciate that staff, and indeed the community, have other important work on their plates, and thus that work on a PSR might not commence immediately. Requesting the PSR will at least put this into the prioritisation queue so that appropriate resources can be allocated to this work in due course. Deferring the request for a PSR would mean that this does not happen. Thanks Susan Payne Head of Legal Policy [cid:image001.png@01DAA2F3.712E66F0]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 Ext 255 comlaude.com<http://comlaude.com> Follow us on Linkedin<https://t-uk.xink.io/Tracking/Index/pRkAAFJfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAFJfAADw_RQA0> [cid:image002.png@01DAA2F3.712E66F0]<https://www.linkedin.com/company/com-laude> [cid:image003.png@01DAA2F3.712E66F0] <https://twitter.com/comlaude?lang=en> [cid:image004.png@01DAA2F3.712E66F0] <https://www.facebook.com/ComLaude/> [cid:image005.png@01DAA2F3.712E66F0] <https://www.youtube.com/@comlaude> [cid:image006.jpg@01DAA2F3.712E66F0] ________________________________ 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>

2 2