May 2025 - council - lists.icann.org

GNSO Council Portfolio Management Tool Suite - 15 May 2025 Meeting
by Caitlin Tubergen May 6, 2025

May 6, 2025

Dear all, Please see links below to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 15 May 2025. Agenda: * https://icann-community.atlassian.net/wiki/x/GKafBg Motions: * https://icann-community.atlassian.net/wiki/x/LKifBg Links to the Program Suite: * Program/Project Management Framework (PPMF): https://icann-community.atlassian.net/wiki/x/TgyfBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/Tgy…> * Portfolio Management Tool (PMT): https://icann-community.atlassian.net/wiki/x/WQyfBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/WQy…> * **Action/Decision Radar (ADR): https://icann-community.atlassian.net/wiki/x/cAyfBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/cAy…> * **Project List (PL): https://icann-community.atlassian.net/wiki/x/ZAyfBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/ZAy…> * **Action Items (AIs): https://icann-community.atlassian.net/wiki/x/64OeBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/64O…> * Council Small Teams (CSTs): https://icann-community.atlassian.net/wiki/x/JS6fBg [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/JS6…> * ** denotes the required three work products for review by Councilors in preparation for monthly meetings Key Program Suite Structural Changes for this Period: * None for this period Key Project Changes or Milestones for this Period: * GNSO Council to consider an additional six month deferral for RPMs_P2 policy work on a review of the UDRP * IRT Status Page: https://www.icann.org/policy/implementation Key Project Activities for June/July 2025: * GNSO Council to consider next steps regarding Registration Data Accuracy * GNSO Council to initiate Expression of Interest for non-CPH candidate to CSC * GNSO Council to consider next steps in consideration of a review of the Expiration Policy * GNSO Council to consider next steps on Whois Implementation Advisory Group * GNSO Council to consider findings from Board Readiness Recommendations small team * GNSO Council to consider 2026 CSC slate * Portfolio Management Tool (PMT) reset for FY26-FY30 Please let staff know if you have any questions. Best regards, Caitlin

1 0

Re: Motion to Defer RPMs Phase 2 for 15 May 2025 Council Meeting
by Terri Agnew May 5, 2025

May 5, 2025

Hello, Thank you, we will get this posted on the motions wiki page shortly: https://icann-community.atlassian.net/wiki/x/LKifBg Kind regards, Terri From: Caitlin Tubergen via council <council(a)icann.org> Reply-To: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Monday, May 5, 2025 at 6:41 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Motion to Defer RPMs Phase 2 for 15 May 2025 Council Meeting SENT ON BEHALF OF GREG DIBIASE WHO IS CURRENTLY UNABLE TO SEND Dear Councilors, Please find attached (i) the Motion to Defer for a Further 6 Months the Next Steps of Phase Two of the RPMs in All New gTLDs PDP and (ii) the supporting documents. Thank you. Best regards, Caitlin

1 0

Re: Consent Agenda motion for 15 May 2025 GNSO Council meeting
by Terri Agnew May 5, 2025

May 5, 2025

Hello, Thank you, we will get this posted on the motions wiki page shortly: https://icann-community.atlassian.net/wiki/x/LKifBg Kind regards, Terri From: Caitlin Tubergen via council <council(a)icann.org> Reply-To: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Monday, May 5, 2025 at 6:34 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Consent Agenda motion for 15 May 2025 GNSO Council meeting SENT ON BEHALF OF TOMSLIN SAMME-NLAR WHO IS CURRENTLY UNABLE TO SEND Dear Councilors, Please find attached the consent agenda motion (aspirational statement) for the upcoming May GNSO Council meeting. Thank you. Best regards, Caitlin

1 0

Motion to Defer RPMs Phase 2 for 15 May 2025 Council Meeting
by Caitlin Tubergen May 5, 2025

May 5, 2025

SENT ON BEHALF OF GREG DIBIASE WHO IS CURRENTLY UNABLE TO SEND Dear Councilors, Please find attached (i) the Motion to Defer for a Further 6 Months the Next Steps of Phase Two of the RPMs in All New gTLDs PDP and (ii) the supporting documents. Thank you. Best regards, Caitlin

1 0

Human Rights checklist for Transfer Policy Review
by farzaneh badii May 5, 2025

May 5, 2025

Dear Council In ICANN Seattle meeting NCSG councilors asked to retroactively do a HR checklist for TPR. Council kindly accepted and NCSG was instructed along with the chair of TPR to do the exercise. This is an iterative exercise and the method is evolving, we submit to the council for review and feedback which can hopefully be turned into a council document. It was suggested that after the council provides feedback and approves the HR checklist perhaps we could send this to the Board for their information. After we agree in this document we can discuss what can happen to it. But there are also some interesting points that Roger pointed out and we have recorded it in the document: perhaps when we do the pDP scoping we should consider the human rights checklist because when we went through the exercise a few issues were uncovered. Here is the Google doc and I have asked to brief you on the document during our upcoming meeting: https://docs.google.com/document/d/1aQetWyuO0S_0FD0-cFlAFz4cm0km5bywoC7JYtc… Best regards Farzaneh

1 0

FYI | FW: [Ext] NEXT WEEK: Call for Expressions of Interest: ICANN 2026 NomCom Chair and Chair-Elect
by Terri Agnew May 5, 2025

May 5, 2025

FYI [https://danh45uab.cc.rs6.net/on.jsp?ca=1ccd3e8d-3bb6-4302-9905-85b5318b1061…] Monday, 05 May 2025 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] Click here to learn more about the New gTLD Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents Information Sharing · REMINDER: ICANN RSP Pre-Evaluation Program Closes 20 May 2025 · Next Round Champions Toolkit Available in the Six ICANN Languages · ICANNWiki Seeking Volunteers 🚨 Action Items 🚨 · FRIDAY: Call for Applications: NextGen@ICANN84 · NEXT WEEK: Call for Expressions of Interest: ICANN 2026 NomCom Chair and Chair-Elect · SUNDAY: ICANN Invites Applications for the Asia Pacific Internet Governance Academy 2025 · Call for ASP Mentors Public Comment · WEDNESDAY: Proposal for Thaana script Root Zone Label Generation Rules · ONE WEEK FROM TODAY: FY26-FY30 Middle East Regional Plan · How We Meet: Reviewing the Implementation of the ICANN Public Meetings Strategy · Governance Document for the Recognition, Maintenance, and Derecognition of RIRs · Customer Standing Committee (CSC) changes Process for Amending the IANA SLAs · Africa Regional Plan for Fiscal Years 2026-2030 · Transfer Policy Review Working Group Final Report for ICANN Board Consideration Events · These events occur in May 2025. Information Sharing REMINDER-ICANN RSP Pre-Evaluation Program Closes 20 May 2025 The pre-evaluation application submission period of the ICANN Registry Service Provider (RSP) Evaluation Program for the New Generic Top-level Domains (gTLD) Program: Next Round is set to close [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> at 18:00 UTC on 20 May 2025. Launched on 19 November 2024, the program streamlines gTLD applications by separately evaluating the technical aspects of operating the gTLD from the application for the gTLD label. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Next Round Champions Toolkit Available in the Six ICANN Languages ICANN is working with the community to identify potential Applicant Support Program (ASP) applicants – especially in regions that are currently under-represented in ICANN. If you are interested in helping to raise awareness among your own contacts or communities, please use the materials in the Next Round Champions Toolkit [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…>. To stay up to date on the New gTLD Program: Next Round and ASP, join the mailing list: nextroundinfo(a)icann.org. ASP leads, targets, and ideas can be sent to engagement.newgTLDprogram(a)icann.org<mailto:engagement.newgTLDprogram@icann.org>. ICANNWiki Seeking Volunteers ICANNWiki is seeking volunteers to assist with creating and editing articles and content for the site. Do you want to help? Getting started is as simple as requesting an account [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…>. Then, make sure to read the short content guide [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> on where to find reliable data. Happy editing! Action Items FRIDAY: Call for Applications: NextGen@ICANN84 ICANN wants to hear from university students living and studying in the Asia Pacific region who are interested in the future of the Internet and participating in the Public Meeting. Deadline: 09 May 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> NEXT WEEK: Call for Expressions of Interest: ICANN 2026 NomCom Chair and Chair-Elect The NomCom Chair is responsible for organizing the NomCom in its activities to select certain ICANN Board members and individuals who will serve in key leadership positions within ICANN's SOs and ACs in accordance with ICANN's Bylaws. Deadline: 13 May 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> SUNDAY: ICANN Invites Applications for the Asia Pacific Internet Governance Academy 2025 Launched in 2016, APIGA is a five-day capacity-development program focused on Internet governance (IG) targeting youths in the Asia-Pacific (APAC) region. Deadline: Sunday, 11 May, at 23:59 KST (14:00 UTC) Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Call for ASP Mentors ICANN is seeking volunteer mentors who would like to offer their expertise to supported applicants as part of the ASP in the new gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…>. ICANN is looking for mentors who can share insights and experience across ICANN Languages (Arabic, Chinese, English, French, Russian, or Spanish) to support diverse gTLD applicants. Mentors may play a role in: advising applicants on navigating the gTLD application process and DNS industry; identifying resources; providing guidance; sharing experiences as appropriate; and helping supported applicants navigate the ICANN community and Public Meetings. If you or someone in your network might be interested, please refer to the mentor registration announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> for more information. Questions about the ASP or becoming a supported applicant Mentor can be sent to globalsupport(a)icann.org<mailto:globalsupport@icann.org>. Public Comment WEDNESDAY: Proposal for Thaana script Root Zone Label Generation Rules [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Submissions Opening Date: Thursday, 27 March 2025 Submissions Closing Date: Wednesday, 7 May 2025 ONE WEEK FROM TODAY: FY26-FY30 Middle East Regional Plan [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Submissions Opening Date: Monday, 31 March 2025 Submissions Closing Date: Monday, 12 May 2025 How We Meet: Reviewing the Implementation of the ICANN Public Meetings Strategy [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Submissions Opening Date: Wednesday, 9 April 2025 Submissions Closing Date: Monday, 19 May 2025 Governance Document for the Recognition, Maintenance, and Derecognition of RIRs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Submissions Opening Date: 14 April 2025 Submissions Closing Date: 27 May 2025 Customer Standing Committee (CSC) changes Process for Amending the IANA SLAs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Submissions Opening Date: Tuesday, 22 April 2025 Submissions Closing Date: Monday, 02 June 2025 Africa Regional Plan for Fiscal Years 2026-2030 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Submissions Opening Date: Friday, 25 April 2025 Submissions Closing Date: Friday, 06 June 2025 Transfer Policy Review Working Group Final Report for ICANN Board Consideration [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> Submissions Opening Date: Monday, 28 April 2025 Submissions Closing Date: Monday, 16 June 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…>. Events These events occur in May 2025. To learn more, please visit our community engagement calendar [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…>. · CaribNOG29 · 2-Day DNSSEC Training at .PT · APAC DNS Forum 2025 · SALON OSIANE 2025 Volume 7, Issue 34 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…> | Next Issue: Thursday, 08 May 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001CEviKdd…>

1 0

Updates to share | Proposed Agenda | GNSO Council Meeting | Thursday, 15 May 2025
by Terri Agnew May 5, 2025

May 5, 2025

Hello all, Some updates to share on the 15 May 2025. See wiki page for updated GNSO Council agenda<https://icann-community.atlassian.net/wiki/x/GKafBg>. 1. Decreased time on both agenda items: 4 & 7 2. Updated AOB item 8.2 (removed ccNSO) 3. Added additional time item 8 – AOB (now total of 25 minutes) 4. Added two AOB items (8.3 and 8.6) Thank you. Kind regards, Terri From: Devan Reed <devan.reed(a)icann.org> Date: Friday, May 2, 2025 at 2:08 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "liaison6c(a)icann.org" <liaison6c(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: Proposed Agenda | GNSO Council Meeting | Thursday, 15 May 2025 Dear all, Please find below the agenda for the GNSO Council Meeting on 15 May 2025 at 05:00 UTC. This will be posted on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/GKafBg> shortly. Thank you. Kind regards, Devan Policy Team Supporting the GNSO GNSO Council Agenda 15 May 2025 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://icann-community.atlassian.net/wiki/x/0KefBg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> 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, 15 May 2025 at 05:00 UTC: https://tinyurl.com/knke3w 22:00 Los Angeles(Wednesday); 01:00 Washington DC; 06:00 London; 07:00 Paris; 08:00 Moscow; 15:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 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<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 12 March 2025 were posted on 01 April 2025 Minutes<https://gnso.icann.org/sites/default/files/policy/2025/transcript/transcrip…> of the GNSO Council Meeting on 10 April 2025 were posted on 24 April 2025 Item 2: Opening Remarks / Review of Projects & Action List (5 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Aspirational Statement Item 4: COUNCIL VOTE - Deferral of the Next Steps of Phase Two of the Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP) for an Additional Six Months (20 minutes) The Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP) was chartered to be conducted in two phases: Phase One focused on a review of all the RPMs that were developed for the 2012 New gTLD Program, and Phase Two will focus on issues identified in respect of the Uniform Dispute Resolution Policy (UDRP). Following the ICANN Board’s approval of the Phase 1 recommendations in January 2022, the GNSO Council discussed delaying Phase Two of the RPMs PDP until the completion of key milestones for the Implementation Review Team, once launched. The Phase One IRT was launched in December 2022 with a projected end date of December 2024. During its meeting on 16 February 2023<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, the GNSO Council agreed to defer next steps on the RPMs PDP Phase Two for 18 months. In October 2024, GNSO support staff advised the GNSO Council leadership of staff estimates that the implementation of RPMs Phase One would be delayed until the third quarter of 2025. In light of this, the Council voted to defer the next steps on Phase Two for an additional six months. Following the direction of the Councilors who reviewed the progress to date, the Council is voting to defer the consideration of next steps for Phase 2 for an additional six months. 4.1 - Introduction of Topic (Susan Payne, GNSO Councilor) 4.2 - Council Vote (voting threshold: simple majority) 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Han Script Character gTLDs (Recommendation 3.17) (20 minutes) The New gTLD Subsequent Procedures (SubPro) PDP provided Recommendation 25.4 (approved by the ICANN Board) to allow single character gTLDs for ideographic scripts in the next round, provided that they do not introduce confusion risks that rise above commonplace similarities. The IDNs EPDP Phase 1 Final Report put forth important additional detail and limitations on 25.4, prescribing that the single character gTLDs be limited to the Han script and that applications must not be accepted until relevant guidelines are developed and put in place by the Chinese, Japanese, and Korean (CJK) Generation Panels (GPs). Alternatively, the IDN EPDP concluded that if the CJK GPs determine that additional guidelines beyond the RZ-LGR are not needed, then the single character applications should proceed. The matter was put out for public comment by the CJK Generation Panels. Although the CJK GPs stated<https://www.icann.org/en/system/files/files/proposed-han-script-single-char…> that the work done in the Root Zone Label Generation Rules (RZ-LGRs<https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en>) sufficiently addresses the concerns around the risk of confusion for single character Han script gTLDs, the majority of the public comments<https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-scr…> on the CJK GPs’ statements opposed moving forward. Some commenters from the Chinese community expressed concerns about the lack of alignment with China’s linguistic laws and regulations, the complexities of Chinese character ideographs, and end-user confusion due to multiple meanings of many single characters. One such comment received from a co-Chair of the CGP argues that the CGP should not be and was not involved in "risk of confusion" policy considerations related to single Han characters as TLDs. Many of the comments call for further community work prior to proceeding. Similar concerns were received through the public comment<https://www.icann.org/en/public-comment/proceeding/second-proceeding-for-pr…> on the relevant draft AGB sections. This public comment was discussed with the Sub Pro IRT IDN Sub-Track which referred the matter to the main SubPro IRT. The main SubPro IRT was asked by ICANN staff whether Recommendation 25.4 should be modified as not implementable or whether the issue should be reviewed with Council for possible further work. It was agreed that the Liaisons should raise this with Council for direction on next steps. A background document<https://lists.icann.org/hyperkitty/list/council@icann.org/message/GLJ5RIOKH…> prepared by Lars Hoffmann was shared with the Council on December 9. The Council Liaisons to the IRT suggesting referring the issue to a GNSO Guidance Process (GGP) to determine the guidance necessary to allow Han single characters to proceed, with an acknowledgement that the GGP could well determine that Recommendation 25.4 and IDN EPDP recommendation 3.17 as approved may not be implementable. Due to time constraints, and the fact that both the SubPro and IDNs recommendations were conditional, the Liaisons believe that the recommended GGP process should not hold up the next round. During Council deliberations, some Councilors suggested an Expert Working Group (EWG), as an alternative to the GGP. Staff provided an update to the Council during its April meeting where an additional mechanism was identified - the External Expert Advice (EEA) process as captured in Article 13 of the ICANN Bylaws. Following the Council’s April meeting, GNSO support staff provided an analysis of the potential options to address this issue, the GGP,the EWG, and the EEA. Here, the Council will discuss the next steps for Han Script Character gTLDs. 5.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Council Alignment on the Future of Reviews (30 minutes) ICANN created Specific Reviews in 2009 as a way to measure how it was meeting its commitments in four specific areas: Accountability and Transparency; Security, Stability, and Resiliency of the Domain Name System; Registration Directory Service; and Competition, Consumer Trust, and Consumer Choice. These reviews were incorporated into ICANN's Bylaws in 2016. Specific Reviews are led by community review teams and operate according to Section 4.6<https://www.icann.org/resources/pages/governance/bylaws-en#article4.6> of the ICANN Bylaws and the Operating Standards for Specific Reviews. Upon completion of a review, the Board assesses the results and considers recommendations accordingly. With exception of the Competition, Consumer Trust and Consumer Choice review that is conducted “After a New gTLD Round has been in operation for one year”, Specific Reviews are conducted “no less frequently than every five years”, measured from the date the previous review effort was convened. The Accountability and Transparency Review Team 3 (ATRT3) recommended the establishment of a new Specific Review, the Holistic Review, to examine the continuous improvement, effectiveness, and accountability of the ICANN community structures as well as the collaboration among them. A Pilot Holistic Review Team<https://community.icann.org/display/PHR> was convened to develop the guidelines and methodologies for the future Holistic Review, recommended by the ATRT3. Following an introduction of the topic, the Council will discuss the potential options going forward, including: * Status Quo: Continue on the current path, kick off ATRT4 and bifurcate out the Pilot Holistic Review (structural review) and the Continuing Improvement process. * Change Option 1: Repurpose ATRT4 to have it undertake the structural review, and as a result wind down the Pilot Holistic Review (with the Continuing Improvement process independent and functioning). * Change Option 2: Suspend all reviews and kick off a Review of Reviews to determine what reviews are necessary at this time (including a structural review). Here, the Council will consider these options and determine which, if any, is most supported by councilors. 6.1 - Introduction of Topic (Paul McGrady, GNSO Councilor) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL UPDATE: Subsequent Procedures Implementation Review Team on Recommendation 36.4 (20 minutes) On 16 March 2023, the ICANN Board adopted<https://www.icann.org/en/system/files/files/scorecard-subpro-pdp-board-acti…>, et al., Recommendation 36.4 of the Subsequent Procedures PDP. Recommendation 36.4 provides: ICANN must add a contractual provision stating that the registry operator will not engage in fraudulent or deceptive practices. In the event that ICANN receives an order from a court that a registry has engaged in fraudulent or deceptive practices, ICANN may issue a notice of breach for such practices and allow the registry to cure such breach in accordance with the Registry Agreement. Further, in the event that there is a credible allegation by any third party of fraudulent or deceptive practices, other than as set forth in above, ICANN may, at its discretion, either commence dispute resolution actions under the Registry Agreement (Currently Article 5 of the Registry Agreement), or appoint a panel under the PICDRP. For the purposes of a credible claim of fraudulent or deceptive practices the reporter (as defined by the PICDRP) must only specifically state the grounds of the alleged non-compliance, but not that it personally has been harmed as a result of the registry operator’s act or omission. Here, the Council liaisons to the SubPro Implementation Review Team would like to discuss concerns regarding the proposed implementation of Recommendation 36.4. 7.1 - Introduction of Topic (Anne Aikman-Scalese and Susan Payne, Council Liaisons to SubPro IRT) 7.2 - Council Discussion 7.3 - Next Steps Item 8: Any Other Business (15 minutes) 8.1 - ICANN83 Planning 8.2 - ccNSO and GAC Liaison updates 8.3 - Whois Implementation Advisory Group update 8.4 - Registration Data Request Service (RDRS) Standing Committee Report - open question of public comment 8.5 - Chair update _______________________________ 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… References for Coordinated Universal Time of 21:00 UTC Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ 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<http://www.timeanddate.com/> and https://tinyurl.com/knke3w

1 0

Meeting Invitation | GNSO Council Meeting | Thursday, 15 May2025
by Terri Agnew May 5, 2025

May 5, 2025

Dear all, The GNSO Council meeting is scheduled on Thursday, 15 May 2025 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> Visit the Wiki Agenda page: https://icann-community.atlassian.net/wiki/x/GKafBg Check your time zone: https://tinyurl.com/knke3w 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/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Passcode: mkt7*ULa9b If joining Zoom via Zoom App the following will be required: Webinar ID: 910 4823 5847 Passcode: 9213420189 Or One tap mobile : +13462487799,,91048235847#,,,,*9213420189# US (Houston) +16699006833,,91048235847#,,,,*9213420189# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/a6JrPP2u5 Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://icann-community.atlassian.net/wiki/x/0KefBg> 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

FINAL REMINDER | Document and Motion deadline | Monday, 05 May 2025 at 23:59 UTC for GNSO Council Meeting 15 May 2025 at 05:00 UTC
by Terri Agnew May 5, 2025

May 5, 2025

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 05 May 2025 at 23:59 UTC) for the GNSO Council Meeting on Thursday, 15 May 2025 15 05:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Motions Wiki at: https://icann-community.atlassian.net/wiki/x/LKifBg Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Proposed Agenda | GNSO Council Meeting | Thursday, 15 May 2025
by Devan Reed May 2, 2025

May 2, 2025

Dear all, Please find below the agenda for the GNSO Council Meeting on 15 May 2025 at 05:00 UTC. This will be posted on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/GKafBg> shortly. Thank you. Kind regards, Devan Policy Team Supporting the GNSO GNSO Council Agenda 15 May 2025 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://icann-community.atlassian.net/wiki/x/0KefBg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> 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, 15 May 2025 at 05:00 UTC: https://tinyurl.com/knke3w 22:00 Los Angeles(Wednesday); 01:00 Washington DC; 06:00 London; 07:00 Paris; 08:00 Moscow; 15:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 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<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 12 March 2025 were posted on 01 April 2025 Minutes<https://gnso.icann.org/sites/default/files/policy/2025/transcript/transcrip…> of the GNSO Council Meeting on 10 April 2025 were posted on 24 April 2025 Item 2: Opening Remarks / Review of Projects & Action List (5 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Aspirational Statement Item 4: COUNCIL VOTE - Deferral of the Next Steps of Phase Two of the Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP) for an Additional Six Months (20 minutes) The Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP) was chartered to be conducted in two phases: Phase One focused on a review of all the RPMs that were developed for the 2012 New gTLD Program, and Phase Two will focus on issues identified in respect of the Uniform Dispute Resolution Policy (UDRP). Following the ICANN Board’s approval of the Phase 1 recommendations in January 2022, the GNSO Council discussed delaying Phase Two of the RPMs PDP until the completion of key milestones for the Implementation Review Team, once launched. The Phase One IRT was launched in December 2022 with a projected end date of December 2024. During its meeting on 16 February 2023<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…>, the GNSO Council agreed to defer next steps on the RPMs PDP Phase Two for 18 months. In October 2024, GNSO support staff advised the GNSO Council leadership of staff estimates that the implementation of RPMs Phase One would be delayed until the third quarter of 2025. In light of this, the Council voted to defer the next steps on Phase Two for an additional six months. Following the direction of the Councilors who reviewed the progress to date, the Council is voting to defer the consideration of next steps for Phase 2 for an additional six months. 4.1 - Introduction of Topic (Susan Payne, GNSO Councilor) 4.2 - Council Vote (voting threshold: simple majority) 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Han Script Character gTLDs (Recommendation 3.17) (20 minutes) The New gTLD Subsequent Procedures (SubPro) PDP provided Recommendation 25.4 (approved by the ICANN Board) to allow single character gTLDs for ideographic scripts in the next round, provided that they do not introduce confusion risks that rise above commonplace similarities. The IDNs EPDP Phase 1 Final Report put forth important additional detail and limitations on 25.4, prescribing that the single character gTLDs be limited to the Han script and that applications must not be accepted until relevant guidelines are developed and put in place by the Chinese, Japanese, and Korean (CJK) Generation Panels (GPs). Alternatively, the IDN EPDP concluded that if the CJK GPs determine that additional guidelines beyond the RZ-LGR are not needed, then the single character applications should proceed. The matter was put out for public comment by the CJK Generation Panels. Although the CJK GPs stated<https://www.icann.org/en/system/files/files/proposed-han-script-single-char…> that the work done in the Root Zone Label Generation Rules (RZ-LGRs<https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en>) sufficiently addresses the concerns around the risk of confusion for single character Han script gTLDs, the majority of the public comments<https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-scr…> on the CJK GPs’ statements opposed moving forward. Some commenters from the Chinese community expressed concerns about the lack of alignment with China’s linguistic laws and regulations, the complexities of Chinese character ideographs, and end-user confusion due to multiple meanings of many single characters. One such comment received from a co-Chair of the CGP argues that the CGP should not be and was not involved in "risk of confusion" policy considerations related to single Han characters as TLDs. Many of the comments call for further community work prior to proceeding. Similar concerns were received through the public comment<https://www.icann.org/en/public-comment/proceeding/second-proceeding-for-pr…> on the relevant draft AGB sections. This public comment was discussed with the Sub Pro IRT IDN Sub-Track which referred the matter to the main SubPro IRT. The main SubPro IRT was asked by ICANN staff whether Recommendation 25.4 should be modified as not implementable or whether the issue should be reviewed with Council for possible further work. It was agreed that the Liaisons should raise this with Council for direction on next steps. A background document<https://lists.icann.org/hyperkitty/list/council@icann.org/message/GLJ5RIOKH…> prepared by Lars Hoffmann was shared with the Council on December 9. The Council Liaisons to the IRT suggesting referring the issue to a GNSO Guidance Process (GGP) to determine the guidance necessary to allow Han single characters to proceed, with an acknowledgement that the GGP could well determine that Recommendation 25.4 and IDN EPDP recommendation 3.17 as approved may not be implementable. Due to time constraints, and the fact that both the SubPro and IDNs recommendations were conditional, the Liaisons believe that the recommended GGP process should not hold up the next round. During Council deliberations, some Councilors suggested an Expert Working Group (EWG), as an alternative to the GGP. Staff provided an update to the Council during its April meeting where an additional mechanism was identified - the External Expert Advice (EEA) process as captured in Article 13 of the ICANN Bylaws. Following the Council’s April meeting, GNSO support staff provided an analysis of the potential options to address this issue, the GGP,the EWG, and the EEA. Here, the Council will discuss the next steps for Han Script Character gTLDs. 5.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Council Alignment on the Future of Reviews (30 minutes) ICANN created Specific Reviews in 2009 as a way to measure how it was meeting its commitments in four specific areas: Accountability and Transparency; Security, Stability, and Resiliency of the Domain Name System; Registration Directory Service; and Competition, Consumer Trust, and Consumer Choice. These reviews were incorporated into ICANN's Bylaws in 2016. Specific Reviews are led by community review teams and operate according to Section 4.6<https://www.icann.org/resources/pages/governance/bylaws-en#article4.6> of the ICANN Bylaws and the Operating Standards for Specific Reviews. Upon completion of a review, the Board assesses the results and considers recommendations accordingly. With exception of the Competition, Consumer Trust and Consumer Choice review that is conducted “After a New gTLD Round has been in operation for one year”, Specific Reviews are conducted “no less frequently than every five years”, measured from the date the previous review effort was convened. The Accountability and Transparency Review Team 3 (ATRT3) recommended the establishment of a new Specific Review, the Holistic Review, to examine the continuous improvement, effectiveness, and accountability of the ICANN community structures as well as the collaboration among them. A Pilot Holistic Review Team<https://community.icann.org/display/PHR> was convened to develop the guidelines and methodologies for the future Holistic Review, recommended by the ATRT3. Following an introduction of the topic, the Council will discuss the potential options going forward, including: * Status Quo: Continue on the current path, kick off ATRT4 and bifurcate out the Pilot Holistic Review (structural review) and the Continuing Improvement process. * Change Option 1: Repurpose ATRT4 to have it undertake the structural review, and as a result wind down the Pilot Holistic Review (with the Continuing Improvement process independent and functioning). * Change Option 2: Suspend all reviews and kick off a Review of Reviews to determine what reviews are necessary at this time (including a structural review). Here, the Council will consider these options and determine which, if any, is most supported by councilors. 6.1 - Introduction of Topic (Paul McGrady, GNSO Councilor) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL UPDATE: Subsequent Procedures Implementation Review Team on Recommendation 36.4 (20 minutes) On 16 March 2023, the ICANN Board adopted<https://www.icann.org/en/system/files/files/scorecard-subpro-pdp-board-acti…>, et al., Recommendation 36.4 of the Subsequent Procedures PDP. Recommendation 36.4 provides: ICANN must add a contractual provision stating that the registry operator will not engage in fraudulent or deceptive practices. In the event that ICANN receives an order from a court that a registry has engaged in fraudulent or deceptive practices, ICANN may issue a notice of breach for such practices and allow the registry to cure such breach in accordance with the Registry Agreement. Further, in the event that there is a credible allegation by any third party of fraudulent or deceptive practices, other than as set forth in above, ICANN may, at its discretion, either commence dispute resolution actions under the Registry Agreement (Currently Article 5 of the Registry Agreement), or appoint a panel under the PICDRP. For the purposes of a credible claim of fraudulent or deceptive practices the reporter (as defined by the PICDRP) must only specifically state the grounds of the alleged non-compliance, but not that it personally has been harmed as a result of the registry operator’s act or omission. Here, the Council liaisons to the SubPro Implementation Review Team would like to discuss concerns regarding the proposed implementation of Recommendation 36.4. 7.1 - Introduction of Topic (Anne Aikman-Scalese and Susan Payne, Council Liaisons to SubPro IRT) 7.2 - Council Discussion 7.3 - Next Steps Item 8: Any Other Business (15 minutes) 8.1 - ICANN83 Planning 8.2 - ccNSO and GAC Liaison updates 8.3 - Whois Implementation Advisory Group update 8.4 - Registration Data Request Service (RDRS) Standing Committee Report - open question of public comment 8.5 - Chair update _______________________________ 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… References for Coordinated Universal Time of 21:00 UTC Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ 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<http://www.timeanddate.com/> and https://tinyurl.com/knke3w

1 0