March 2025 - council - lists.icann.org

CORRECTION! Re: Re: Consent Agenda motions for April meeting
by Julie Bisland March 31, 2025

March 31, 2025

Happy Monday! This will actually be posted on the MOTIONS wiki page<https://icann-community.atlassian.net/wiki/x/JKifBg?atlOrigin=eyJpIjoiNmI3N…> (not agenda)! -- Julie Bisland Policy Team Supporting the GNSO From: Julie Bisland via council <council(a)icann.org> Reply-To: Julie Bisland <julie.bisland(a)icann.org> Date: Monday, March 31, 2025 at 10:50 AM To: Nacho Amadoz <nacho(a)amadoz.cat>, GNSO Council <council(a)gnso.icann.org> Subject: [council] Re: Consent Agenda motions for April meeting Thank you, Nacho! This will be posted to the Agenda wiki page [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/EKa…> shortly. Thank you. Kind regards, Julie -- Julie Bisland Policy Team Supporting the GNSO From: Nacho Amadoz via council <council(a)icann.org> Reply-To: Nacho Amadoz <nacho(a)amadoz.cat> Date: Monday, March 31, 2025 at 10:44 AM To: GNSO Council <council(a)gnso.icann.org> Subject: [council] Consent Agenda motions for April meeting Councillors, See attached the proposed motions for the consent agenda for our April meeting. This includes the following two motions: - The motion to Adopt the GNSO Council Review of ICANN82 GAC Communiqué - The Motion to Approve the GNSO Council Recommendations Report to the ICANN Board regarding the Transfer Policy Review Policy Development Process Working Group Thanks Nacho

1 0

Consent Agenda motions for April meeting
by Nacho Amadoz March 31, 2025

March 31, 2025

Councillors, See attached the proposed motions for the consent agenda for our April meeting. This includes the following two motions: - The motion to Adopt the GNSO Council Review of ICANN82 GAC Communiqué - The Motion to Approve the GNSO Council Recommendations Report to the ICANN Board regarding the Transfer Policy Review Policy Development Process Working Group Thanks Nacho

2 1

Proposed Agenda | GNSO Council Meeting | Thursday, 10 April 2025
by Terri Agnew March 28, 2025

March 28, 2025

Dear all, Please find below the agenda for the GNSO Council Meeting on 10 April 2025 at 21:00 UTC. This will be posted on the agenda wiki page<https://icann-community.atlassian.net/wiki/x/EKafBg> shortly. Thank you. Kind regards, Terri Policy Team Supporting the GNSO GNSO Council Agenda 10 April 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/yKefBg 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, 10 April 2025 at 21:00 UTC: https://tinyurl.com/5bsuykt5 14:00 Los Angeles; 17:00 Washington DC; 22:00 London; 23:00 Paris; 00:00 Moscow; 07:00 Melbourne (Friday) 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 13 February 2025 were posted on 03 March 2025 Minutes of the GNSO Council Meeting on 12 March 2025 will be posted on 01 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) * GNSO Review of the GAC Communiqué * Recommendations Report for the Transfer Policy Review PDP Item 4: COUNCIL VOTE - Confirmation of EPDP on Temporary Specification Team’s Intent to Modify RAA Requirements Related to Billing Contact (20 minutes) During the ICANN81 GNSO Council Wrap-Up<https://icann81.sched.com/event/1p2Gu/gnso-council-wrap-up>, Thomas Rickert provided an update regarding the implementation of EPDP Temp Spec Phase 1 recommendations. Thomas is the current GNSO Council Liaison to the EPDP Temp Spec Phase 1 Implementation Review Team (IRT). Thomas noted that the IRT expressed the view that the absence of a reference to billing contact data was a drafting error, and the EPDP Team intended for the collection of billing contact data to be optional and not mandatory. The Registration Data Policy<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> was published on 21 February 2024, and the policy has an effective date of 21 August 2025. The EPDP Phase 1 policy recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> do not reference billing contact data, and the Registration Data Policy<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> also makes no reference to billing contact data. In the interest of transparency, Thomas requested that all Councilors consult with their respective groups to ensure that others are properly informed and agree with the interpretation raised by the IRT. Accordingly, Councilors were asked to consult with their groups. The Council discussed this topic during its meeting on 19 December 2024<https://icann.zoom.us/rec/play/wMLdawWw7g5mSvuAbgKmzJKUiRDCBU1sSYKHcwg3nb8O…> and asked for additional background information on the topic. During its February and March meetings, the Council considered the questions below: 1. Does the Council confirm billing contact was in scope for the EPDP on the Temp Spec - Phase 1 Team? 2. Does the Council confirm: * the collection of billing contacts by registrars should continue to be required as per current RAA requirements because EPDP Phase 1, by being silent on this, did not mean to change this requirement, OR * the collection of billing contacts by registrars should become optional because EPDP Phase 1, by being silent on this, meant to change the RAA requirement? The Council discussed potential options during its February 2025 meeting<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> and continued discussing options during its GNSO Working Session at ICANN82<https://icann79.sched.com/event/1a165/gnso-council-working-session-2-of-3>. Here, the Council will vote to confirm the EPDP Team did intend to modify the current RAA requirements with respect to the Billing Contact. 4.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 4.2 - Council Vote (voting threshold: simple majority) 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Aspirational Statement Review (15 minutes) During the Council’s 2023 and 2025 Strategic Planning Sessions, the Council agreed to discuss the creation of an aspirational statement, or a statement that is designed to (i) reinforce the Council’s role as manager of PDP and (ii) help socialize the unique role of GNSO councilors with its Stakeholder Groups and Constituencies. In contrast, the aspirational statement is not designed to limit the actions of Councilors, nor is it meant to be binding or a voting directive. Here, the Council will discuss the draft aspirational statement<https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-gnso-cou…> and determine next steps. 5.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Han Script Single 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 Hoffman 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. The Council requested that GNSO staff provide an analysis of the two potential options to address this issue, the GGP and the EWG. Staff will brief the Council on those potential mechanisms, including another approach for Council consideration. Here, the Council will discuss potential options and seek to agree on next steps. 6.1 - Introduction of Topic (Policy Team Supporting the GNSO) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL UPDATE: Registration Data Request Service (10 minutes) In June 2023, the GNSO Council approved a Charter for the Registration Data Request Service Standing Committee, which outlines the Standing Committee’s tasks. Specifically, the Standing Committee is tasked to review the data that will be produced by ICANN org on a monthly basis following the launch of the RDRS (see data points outlined here). The Scoping Team is expected to analyze the data and consider: * Assignment #1. Trends that can be identified over a month-by-month period; * Assignment #2. Possible technical updates that should be considered to RDRS and/or related messaging and promotion (recognizing that the RDRS will only be running for a two-year period and limited resources may be available to implement such updates); * Assignment #3. Specific lessons learned that should be factored into the consideration of how to proceed with the SSAD recommendations; * Assignment #4. Suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations. The Standing Committee has been reviewing monthly data since the inception of the RDRS in November 2023. After one year of reviewing RDRS metrics, the Standing Committee determined it had enough information to begin compiling its Findings Report to the Council, and it began work on its report in January 2025. Here, the Council will receive an update on the RDRS Standing Committee’s progress to date. 7.1 - Introduction of Topic (Sebastien Ducos, Chair of RDRS Standing Committee) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL DISCUSSION: Next Steps for Whois Implementation Advisory Group (15 minutes) The ICANN Procedure For Handling WHOIS Conflicts with Privacy Law Implementation Advisory Group (WHOIS Procedure IAG) is tasked to provide the GNSO Council with recommendations on how to address the comments and input that has been received in response to the public comment forum on the Revised ICANN Procedure for Handling WHOIS Conflicts with Privacy Law: Process and Next Steps. The project has been on hold since September 2021, when ICANN org informed<https://gnso.icann.org/sites/default/files/file/field-file-attach/swinehart…> the GNSO Council that it mutually agreed with Contracted Parties to focus on the completion of data processing agreements associated with the EPDP on the Temporary Specification before further developing the Whois Conflicts Procedure. ICANN org published the Data Processing Specification<https://www.icann.org/resources/pages/data-processing-specification-request…> in January 2025. Here, the Council will discuss next steps for the Whois Procedure Implementation Advisory Group. 8.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: Any Other Business (25 minutes) 9.1 - Update on ICANN83 Planning and GNSO Draft Schedule 9.2 - WSIS+20<https://docs.google.com/document/d/1fM5b8tZX1APSUhEovc0qHWXc_wg3HzJ8__mJuvZ…> and internet governance discussions 9.3 - Latin Diacritics PDP Working Group - Review of Project Plan<https://gnso.icann.org/sites/default/files/policy/2025/presentation/project…> 9.4 - Standing Committee on Continuous Improvements - Review of Project Plan 9.5 - Council review of Assignment Forms for DNS Abuse and Accuracy Small Teams _______________________________ 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 14:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CEST) UTC+2 23:00 Moscow, Russia (MSK) UTC+3 00:00 Singapore (SGT) UTC+8 05:00 (Friday) Melbourne, Australia (AEST) UTC+10 07:00 (Friday) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/5bsuykt5

1 0

Latin Diacritics PDP Project Plan
by John Emery March 28, 2025

March 28, 2025

Dear Councilors, Please find attached a PDF and link below of the proposed Latin Script Diacritics PDP project plan. This will be presented in AOB for non-objection by Prudence Malinki, GNSO liaison to the PDP, during the upcoming Council meeting on 10 April. https://gnso.icann.org/sites/default/files/policy/2025/presentation/project… Thank you, John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

FYI | FW: [Ext] NEW: ICANN Publishes U.S. Tax Returns for Fiscal Year Ending 30 June 2024
by Terri Agnew March 27, 2025

March 27, 2025

FYI [https://danh45uab.cc.rs6.net/on.jsp?ca=24c2310b-5c3b-4add-8a10-ccff65d9751a…] Thursday, 27 March 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=001k_lMFRz…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> 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 · NEW: A Look Back at ICANN82 · NEW: ICANN Publishes U.S. Tax Returns for Fiscal Year Ending 30 June 2024 · NEW: ICANN Seeks Input on Proposal for Thaana Script Root Zone Label Generation Rules · NEW: Elizabeth “Jake” Feinler: The Woman Behind WHOIS · NEW: Publication: A Verifiable and Reproducible Random Candidate Selection Process · ICANN83 Community Childcare Grants Program: Apply Now · ICANN Opens Application Period for New gTLD Applicant Support Program · ICANN Opens New gTLD Registry Service Provider Evaluation Program · Next Round Champions Toolkit Available in the Six ICANN Languages · ICANNWiki Seeking Volunteers Webinars · NEW: ICANN82 Multi lingual read-out (by EURALO) · DNS Training Webinars for ISPs · Webinar - DNS Training Session for ISPs: DNS related threats 🚨 Action Items 🚨 · Call for ASP Mentors · Apply Now for ICANN Leadership Positions Public Comment · NEW: Proposal for Thaana script Root Zone Label Generation Rules · TOMORROW: Proposed Updates to the Operating Standards for Specific Reviews · Fourth Proceeding for Proposed Language for Draft Sections of Next Round AGB · Second IANA Naming Function Review Team (IFR2) Initial Report Events · These events occur in March and April 2025. Information Sharing NEW: A Look Back at ICANN82 Over six days and 175 public sessions, members of the ICANN community, Board, and org gathered at ICANN82 to advance discussions and policymaking on essential issues for ICANN. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> NEW: ICANN Publishes U.S. Tax Returns for Fiscal Year Ending 30 June 2024 The publication of ICANN's financial and tax information is part of ICANN's fundamental commitment to accountability and transparency. The community and the public are invited to review these tax returns and send any questions to planning(a)icann.org<mailto:planning@icann.org>. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> NEW: ICANN Seeks Input on Proposal for Thaana Script Root Zone Label Generation Rules The Thaana Script Generation Panel has worked on this proposal and invites comments regarding the code point repertoire, variant code point definitions, and the rules proposed in the proposal. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> Public Comment. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> NEW: Elizabeth “Jake” Feinler: The Woman Behind WHOIS Jake is recognized not only as an Internet pioneer and advocate for women in technology but also a champion of inclusivity. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> NEW: Publication: A Verifiable and Reproducible Random Candidate Selection Process This paper describes a process to randomly select a subset of named candidates from a larger set of candidates in a manner that cannot be tampered with by the entity administering the process. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> ICANN83 Community Childcare Grants Program: Apply Now Grants of up to $750 per family are available for ICANN Public Meeting participants who meet the criteria, are bringing children, and will incur expenses associated with babysitting or local childcare services. There will be no on-site meeting or conference-sponsored childcare services during ICANN83. Deadline: Friday, 21 April 2025, at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> ICANN Opens New gTLD Registry Service Provider Evaluation Program ICANN has opened the Registry Service Provider (RSP) Evaluation Program for the New Generic TopLevel Domains (gTLD) Program: Next Round. The RSP Evaluation Program was created to streamline the evaluation of gTLD applications by separating the evaluation of the technical aspects of operating the gTLD from the application for the name. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> 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=001k_lMFRz…>. 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=001k_lMFRz…>. 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=001k_lMFRz…> 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=001k_lMFRz…> on where to find reliable data. Happy editing! Webinars NEW: ICANN82 Multi lingual read-out (by EURALO) This readout webinar, in a pitch tour format, is to summarize and discuss selected topics from the ICANN82 Meeting. Speakers from ICANN Board, ICANN org and the different constituencies will provide an overview of the highlights and key take-aways. Date: Tuesday, 01 April 2025, 17:00 - 19:00 UTC Read more and Register now. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> DNS Training Webinars for ISPs ICANN's Technical Engagement team from the Office of the Chief Technology Officer, in collaboration with the Internet Service Providers and Connectivity Providers (ISPCP) constituency, is excited to announce a series of training sessions focusing on topics related to the Domain Name System (DNS). These sessions are intended for all Internet Service Providers (ISPs) globally. Please see the Sessions for ISPs below. Webinar - DNS Training Session for ISPs: DNS related threats Date: Thursday, April 10, 2025, 15:00 UTC to 16:30 UTC Learn more and Register now. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> Action Items 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=001k_lMFRz…>. 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=001k_lMFRz…> 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>. Apply Now for ICANN Leadership Positions The Nominating Committee (NomCom) of ICANN is accepting applications for key leadership positions within ICANN's Supporting Organizations and Advisory Committees, Public Technical Identifiers (PTI), and the ICANN Board of Directors. The deadline to submit applications is 28 March 2025 at 23:59 Coordinated Universal Time (UTC). Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> Public Comment NEW: 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=001k_lMFRz…> Submissions Opening Date: Thursday, 27 March 2025 Submissions Closing Date: Wednesday, 7 May 2025 TOMORROW: Proposed Updates to the Operating Standards for Specific Reviews [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> Open for Submissions: 23 December 2024 Closed for Submissions: 28 March 2025 Fourth Proceeding for Proposed Language for Draft Sections of Next Round AGB [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> Open for Submissions: 14 February 2025 Closed for Submissions: 02 April 2025 Second IANA Naming Function Review Team (IFR2) Initial Report [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> Submissions Opening Date: Thursday, 20 March 2025 Submissions Closing Date: Monday, 28 April 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…>. Events These events occur in March and April 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=001k_lMFRz…>. · Zambia Digital Week 2025 · ICANN Webinar Series Europe: ICANN Domain Metrica - What Are We Seeing and How Can It Be Used? · Capacity Development Sessions at EDP University · ICANN Stakeholder Engagement Meeting: Next Round of New gTLDs - South Africa (Cape Town) · The Prague Dialogue: Internet Governance & Disinformation Challenges · GITEX Africa 2025 Volume 7, Issue 23 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…> | Next Issue: Monday, 31 March 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k_lMFRz…>

1 0

Aspirational Statement
by DiBiase, Gregory March 27, 2025

March 27, 2025

Attachment protected by Amazon: [GNSO Council Aspirational Statement - March 2025 Draft.docx] https://us-west-2.secure-attach.amazon.com/eaef6938-8530-45d2-91ef-b3a3a38b… Amazon has replaced the attachment in this email with a download link. Downloads will be available until April 26, 2025, 14:48 (UTC+00:00). [Tell us what you think] https://amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK [For more information click here] https://docs.secure-attach.amazon.com/guide Hello All, Attached is an updated Aspirational Statement for Council's review. After our SPS session, Sam Demetriou drafted this version taking into account concerns expressed from various councilors (thanks Sam!). To be clear, this statement does not direct Councilors how to vote, it merely clarifies our role in the policy development process. This will be an agenda item in our April meeting, and Leadership is hopeful we can approve this wording. Thanks, Greg

1 0

For your review: Draft message to ICANN org re: IRT restart (urgent request timeline)
by Caitlin Tubergen March 26, 2025

March 26, 2025

Dear Councilors, During the Council’s public meeting at ICANN82, Support Staff captured the following action item: GNSO Council leadership directs staff to draft a letter for review requesting ICANN org to reconvene the IRT to review the Urgent Requests timeline. Please find a draft letter to ICANN org regarding restarting the EPDP – Temp Spec Phase 1 IRT to review the timeline associated with urgent requests: https://docs.google.com/document/d/1uyTIUY4W_6eYE3kUJpejcelnQJHK4HlUFlFnV-d…. The text of the letter has also been included below for ease of reference. If you have any comments or concerns, please provide them by Wednesday, 26 March. Thank you! Kind regards, Caitlin -- Re: Restart of EPDP - Temp Spec - Phase 1 Implementation Review Team - Urgent request timeline Dear ICANN org colleagues, Following our discussion at ICANN82, the GNSO Council wanted to provide a short update on recent discussions around urgent requests and the associated timeline from EPDP - Temp Spec Phase 1. As you may recall, the GAC recommended proceeding with urgent request discussions in two parallel tracks: (i) authentication of requestors and (ii) response time for urgent requests. With respect to the response time for urgent requests, in its October 2024 letter<https://gac.icann.org/advice/correspondence/outgoing/public/2024-10-15%20Ni…>, the GAC invited the Board and the GNSO Council to identify an expedited procedure for addressing this workstream and “strongly suggest[ed] resuming the work of the IRT, which was halted last summer.” Following two productive trilateral discussions, the Council acknowledged and agreed with the GAC’s suggestion that the discussion regarding the response time for urgent requests could continue within the EPDP - Temp Spec Phase 1 Implementation Review Team. The Council confirmed this understanding during its public meeting at ICANN82<https://icann.zoom.us/rec/play/KvHQ3sylRiqPo_nkfTL_s284vhiZ-LrnBzMB_iuCD5om…> and encourages ICANN org to resume IRT meetings in the near term. The Council also discussed the authentication of requestors, and some councilors have attended the recent meetings organized by the Public Safety Working Group. The Council understands the importance of this work and looks forward to supporting this group’s progress. At this time, it does not appear that the authentication mechanism is appropriate or ripe for discussion within the IRT, so the Council recommends limiting the upcoming IRT discussions to timeline discussions only. The Council stands ready to assist should there be any additional questions or concerns. Best regards, Greg DiBiase GNSO Chair

3 3

REMINDER | Document and Motion deadline | Monday, 31 March 2025 at 23:59 UTC for GNSO Council Meeting 10 April 2025 at 21:00 UTC
by Terri Agnew March 25, 2025

March 25, 2025

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 31 March 2025 at 23:59 UTC) for the GNSO Council Meeting on Thursday, 10 April 2025 15 21: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/JKifBg Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Preliminary research on EPDP discussion on billing contact
by farzaneh badii March 24, 2025

March 24, 2025

Hi all, Hope you are enjoying the opening ceremony. As promised I did some research on how and where billing contact was mentioned and discussed and so far have found the following: *Preliminary Research Background on Billing Contact at EPDP:* 1. *August 2018 – Initial Mentions of Billing Contact:* - Billing contact was first mentioned during EPDP calls. - Registrars discussed the utility of Admin/Tech contacts and their overlap with billing contacts. - A message from this period: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/S5…> mentions the duplicity of contact roles (admin, tech, billing) and questions the necessity of collecting and sharing redundant information. 2. *November 2018 – EPDP Team Meeting #26:* - A discussion on excluding billing contact, particularly in the context of ICANN’s involvement: - A message from this meeting: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/DZ…>, which includes discussions on billing being related to a processing activity between contracted parties and their customers, with no involvement of ICANN. 3. *January 2019 – Discussion on Deletion of RDS Elements:* - ICANN org sought input on deleting Administrative and Billing Contact information (note: billing contact data is not published). - Relevant email: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/CD…> - Another email in 2019 from ICANN org asking the group to address billing contact: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/K5…> 4. *Allan Woods’ Position (2019):* - Allan Woods argued against including billing contact in the EPDP discussions: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/7S…> 5. *Kristina Rosette (2019) – Discussion on Billing Contact and Registration Data:* 6. - Kristina Rosette argues that billing data should not be considered as part of registration data due to its vague connection with the domain registration process: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/BK…> - She also mentions a proposed revision of the definition of “Registration Data” to exclude such data. 7. *Sarah Wylde (2019) – Support for Allan Woods’ Argument:* - Sarah Wylde supports Allan Woods’ position and argues that billing is not a data collection purpose for ICANN: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/LT…> 8. *Trang’s Query on Recommendation 11 and RAA:* - Trang raised a question on whether the current text of Recommendation 11 would replace RAA Section 3.4 regarding billing contact: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/VH…> 9. *Allan Greenberg response:* - Allan Greenberg did not dispute the elimination of billing contact: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/P6…> 10. *Small Team B Discussion in 2019:* - Billing contact was briefly discussed by Small Team B, noting that it is not considered within the scope of processing data for ICANN purposes: Link <https://lists.icann.org/hyperkitty/list/gnso-epdp-team@icann.org/message/JH…> I hope this helps. Farzaneh

3 6

Call for volunteers: GNSO Council Small Team on Registration Data Accuracy
by Caitlin Tubergen March 24, 2025

March 24, 2025

Dear Councilors, During the GNSO Council’s public meeting at ICANN82 on Wednesday, 12 March<https://icann82.sched.com/event/1vpbt/gnso-council-meeting>, the Council discussed the next steps on Registration Data Accuracy and agreed to form a small team to closely review the results of the registration data accuracy input assignment and provide a recommendation to the Council on how to proceed. Specifically, Support Staff noted the following action item: GNSO Councilors direct staff to call for volunteers for a small team that looks into the registration data accuracy assignment input (and other relevant information) in more detail. Volunteers during the meeting were: Damon Ashcraft, Greg DiBiase and Lawrence Olawale-Roberts. If you would like to participate in the Council’s Small Team on Registration Data Accuracy, please let us know by responding to this message by Friday, 28 March. Thank you! Kind regards, Caitlin

9 8