January 2025 - council - lists.icann.org

Notice | Official appointment of the GNSO Representative to the Empowered Community Administration
by Terri Agnew Dec. 11, 2025

Dec. 11, 2025

Dear Council, Please find attached the letter on the official appointment of the GNSO representative to the Empowered Community administration. This will posted on the Correspondence page [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/correspondence…> on the GNSO website shortly. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 1

Reminder: Input welcome on GNSO Council agenda for 2025 meetings
by Terri Agnew Nov. 17, 2025

Nov. 17, 2025

Dear councilors, A reminder to all that a Google doc<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> is open for all to add their suggestions and comments to the upcoming GNSO Council meeting agendas. This does not have to be in the form of a full agenda item proposal, simple comments and questions are equally welcome! You are welcome to add to the document<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> via the comments feature. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

10 48

FW: Interim appointment of the GNSO Representative to the Empowered Community Administration
by Terri Agnew Oct. 30, 2025

Oct. 30, 2025

Dear Council, Please find attached the letter informing you of the interim appointment of the GNSO representative to the Empowered Community administration. This was sent to John Jeffrey, ICANN Secretary and posted on the Correspondence page<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> of the GNSO website. Thank you. With kind regards, Terri --- Terri Agnew Policy Team Supporting the GNSO Policy Operations Senior Specialist (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 1

A suggested LinkedIn post for GNSO Comms
by farzaneh badii Feb. 4, 2025

Feb. 4, 2025

Hello GNSO Councillors and Comms team. I mentioned this already during our strategy meeting and wanted to raise it here on the mailing list: I wanted to suggest doing a LinkedIn post about the important human rights check-list that CCOICI suggested in 2023 to be included during each PDP and council approved it. Your LinkedIn post can read as: At the GNSO (ICANN), we care about human rights during policy development and we help ICANN and its community to respect human rights. In 2023, we approved a recommendation by a Council group which supported building a lightweight mechanism throughout the different stages of policy development to facilitate the consideration of the possible impact of our policies on Human Rights! A human rights check-list on its way for all new Policy Development Processes. Stay tuned! Page 45, https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-ccoici-w… And then maybe a screenshot of this section? The CCOICI supports building in a lightweight mechanism throughout the different stages of the GNSO PDP to facilitate the consideration of the possible impact on human rights. Such a mechanism could consist of a check-list of questions that help guide staff support as well as community members involved in the PDP or other GNSO policy processes to identify whether there is an expected impact on human rights which could in turn trigger further focus on this topic. Example questions for such a check-list are: 1) Is there a likely human rights impact, 2) who are the groups expected to be impacted, 3) what is the expected severity of the impact (high / medium / low). The CCOICI wants to emphasize that even if an impact is anticipated, it does not mean that work cannot proceed, it just means that further attention will need to be paid to this issue through questions such as: 1) is the proposed action necessary, 2) is the proposed action proportionate, 3) is the proposed action legitimate. Farzaneh

8 18

Proposed Agenda | GNSO Council Meeting | Thursday, 13 February 2025
by Terri Agnew Feb. 3, 2025

Feb. 3, 2025

Dear all, Please find below the agenda for the GNSO Council Meeting on 13 February 2025 at 21:00 UTC This is posted on the agenda wiki page<https://community.icann.org/x/eQByG>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO GNSO Council Agenda 13 February 2025 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/HgBbGQ 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, 13 February 2025 at 21:00 UTC: https://tinyurl.com/5zh8rb2v 13:00 Los Angeles; 16:00 Washington DC; 21:00 London; 22:00 Paris; 00:00 Moscow (Friday); 08: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/2024/minutes/minutes-gnso…> of the GNSO Council Meeting on 19 December were posted on 30 December 2024. Minutes<https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 09 January 2025 were posted on 26 January 2025. 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<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Confirm the GNSO-nominated ICANN Fellowship Program Mentor and Selection Committee Member positions * Mentor: Glen De Saint Géry * Selection Committee Member: Maud Adjeley Ashong Elliot * Confirm the Latin Script Diacritics PDP WG Chair * Michael Bauland Item 4: COUNCIL DISCUSSION - Update on ICANN’s Enforcement of DNS Abuse Mitigation Requirements - Six Month Progress Update (20 minutes) On 8 November 2024, ICANN announced the release of a six-month report, "ICANN's Enforcement of DNS Abuse Mitigation Requirements<https://www.icann.org/en/system/files/files/icann-enforcement-of-dns-abuse-…>," detailing its enforcement actions under the new Domain Name System (DNS) Abuse mitigation requirements. The requirements, which became effective on 5 April 2024, require generic top-level domain registry operators (ROs) and registrars to take mitigation steps to address well-evidenced DNS Abuse, which, for the purposes of ICANN agreements, is limited to malware, botnets, phishing, pharming, and spam used as a vector for delivering the other forms of DNS Abuse. During the initial six months of enforcement, from 5 April to 5 October 2024, ICANN's Contractual Compliance team launched 192 DNS Abuse investigations involving contracted parties. This enforcement effort led to impactful results, including: · Issuing formal Notices of Breach to an RO and a registrar for noncompliance with DNS Abuse mitigation requirements. · Resolving 154 cases that resulted in the suspension of over 2,700 abusive domain names and the disabling of more than 350 phishing websites. The six-month report provides additional context and details about the specific actions taken to keep the ICANN community informed and enhance transparency around the enforcement of DNS Abuse requirements. Here, the Council will hear an update from ICANN Compliance and have an opportunity to ask questions. 4.1 - Introduction of Topic (Leticia Castillo, ICANN org Compliance) 4.2 - Council Discussion 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Next Steps for Policy and Implementation Policy Status Report (10 minutes) ICANN org published a Policy Status Report (PSR) on the Policy and Implementation Working Group Final Report<https://gnso.icann.org/sites/default/files/filefield_47703/policy-implement…> to support the GNSO Council in its assessment of the effectiveness of its recommendations in achieving their intention of supporting and improving the effectiveness of GNSO Policy Development and Implementation processes. The PSR includes background on the Policy and Implementation Recommendations and their intended purpose, readily available data, staff observations and analysis, and performance against the stated objectives by the GNSO Council and the ICANN community. The PSR is intended to serve as input to the GNSO Council review of policy and implementation related efforts, notably in the assessment of the following GNSO processes introduced in light of the recommendations of the Final Report: * The GNSO Expedited Policy Development Process (EPDP) * The GNSO Guidance Process (GGP) * The GNSO Input Process (GIP) * The Implementation Review Team (IRT) Principles & Guidelines, as well as the requirement to form an IRT following the adoption by the ICANN Board of GNSO Policy recommendations * The Consensus Policy Implementation Framework (CPIF) In summary, the PSR finds that these processes have proved effective in supporting and enhancing GNSO Policy and Implementation efforts, but also identifies a number of caveats and possible improvements. Here, the Council will hear an overview of the updated PSR and determine next steps for the recommendations in the Report. 5.1 - Introduction of Topic (Peter Eakin, ICANN org) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - EPDP Phase 1 on the Temporary Specification - Implementation Question re: 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 registrars within 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. The Council is being asked to consider 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: a. 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 b. 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? Here, the Council will discuss the above questions and determine next steps. 6.1 - Introduction of Topic (Thomas Rickert, GNSO Council Liaison to the EPDP (Temp Spec) Phase 1 IRT) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION: Final Report of the Transfer Policy Review PDP Working Group (40 minutes) On 18 February 2021, the GNSO Council <https://gnso.icann.org/en/council/resolutions/2021#202102> initiated<https://gnso.icann.org/en/council/resolutions/2020-current#20210218-2> a PDP to review the Transfer Policy<https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en>, the policy that governs the process of transferring a domain name from one registrar to another. This PDP is tasked to determine if changes to the policy are needed to improve the ease, security, and efficacy of inter-registrar and inter-registrant transfers. The Transfer Policy Review (TPR) working group began meeting in May 2021, and while it initially divided its work into three distinct groups/phases, the working group ultimately agreed that the topics within its charter needed to be considered together due to overlapping dependencies. Accordingly, the working group worked toward a comprehensive Initial Report<https://community.icann.org/pages/viewpage.action?pageId=347734037&preview=…>, which it published on 1 August 2024. The Initial Report covers all topics in the working group’s charter, including inter-registrar transfers, change of registrant, the Transfer Dispute Resolution Policy, ICANN-approved transfers, and others. The TPR Working Group introduced a new format to its Initial and Final Report, where it endeavors to indicate the “Policy Impact Level” of each policy recommendation. The Policy Impact Indicator is a new feature to help the reader understand the degree of change being proposed by the Working Group, i.e., how much does this recommendation differ from the current Transfer Policy? Here, the Chair of the TPR Working Group will present an overview of the forty-seven (47) policy recommendations to the Council. 7.1 - Introduction of Topic (Roger Carney, TPR Working Group Chair) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL DISCUSSION: Outcomes of Strategic Planning Session (15 minutes) Beginning in 2018, the GNSO Council has held an annual Strategic Planning Session (SPS). The SPS is the Council’s dedicated meeting designed to (i) understand and review the GNSO’s portfolio of work for the coming year, (ii) align on the GNSO’s work priorities for the coming year, (iii) consider whether the GNSO Council has the correct resources and tools to conduct its work as manager of the PDP efficiently, effectively, and comprehensively, and (iv) discuss how to best prepare for emerging and upcoming challenges the Council could face in the coming year and beyond. This year’s SPS was held in Washington, D.C. on 14-15 January 2025. Here, the Council will review the outcomes of the SPS and discuss next steps. 8.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: Any Other Business (5 minutes) 9.1 - ICANN82 planning update * Reminder: Pre-ICANN82 GNSO Council Webinar is mandatory for GNSO Council members - additional details will be provided when available. _______________________________ 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-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CEST) UTC+1 22:00 Moscow, Russia (MSK) UTC+3 00:00 (Friday) Singapore (SGT) UTC+8 05:00 (Friday) Melbourne, Australia (AEST) UTC+11 08:00 (Friday) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/5zh8rb2v

2 2

FYI | FW: [CORRESPONDENCE] Tripti Sinha to Greg DiBiase - Contention Sets
by Devan Reed Jan. 30, 2025

Jan. 30, 2025

FYI – this will be published shortly on the GNSO Correspondence page for 2025. https://gnso.icann.org/en/council/correspondence From: Wendy Profit <wendy.profit(a)icann.org> Date: Wednesday, January 29, 2025 at 4:33 PM To: "DiBiase, Gregory" <dibiase(a)amazon.com>, "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org>, GNSO-Secs <gnso-secs(a)icann.org> Cc: Tripti Sinha <tripti.sinha(a)board.icann.org>, Correspondence <Correspondence(a)icann.org>, Board Ops Team <board-ops-team(a)icann.org>, Secretary <secretary(a)icann.org> Subject: [CORRESPONDENCE] Tripti Sinha to Greg DiBiase - Contention Sets Dear Greg DiBiase, Please find the attached letter from ICANN Board Chair Tripti Sinha in response to your letter of 11 November 2024 regarding contention sets in the New gTLD Program. Thank you and best regards, Wendy Profit Board Operations Senior Manager ICANN

1 0

FW: [Ext] NEW: ICANN Grant Program Reaches Major Milestone
by Julie Bisland Jan. 30, 2025

Jan. 30, 2025

FYI-- From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, January 30, 2025 at 10:01 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: ICANN Grant Program Reaches Major Milestone [https://danh45uab.cc.rs6.net/on.jsp?ca=ed815b7f-5662-4971-8b0c-96c37c5d2f92…] Thursday, 30 January 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=001RdPA7XW…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> 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 ICANN82 · Register Now for ICANN82 Information Sharing · NEW: ICANN Grant Program Reaches Major Milestone · NEW: Approved Resolutions | Regular Meeting of the ICANN Board | 26 January 2025 · NEW: The ICANN MEA Region: 2024 Highlights and 2025 Road Map · 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: ICANN Webinar Series Europe - Meet Kurtis Lindqvist: ICANN's President & CEO · DNS Training Webinars for ISPs · Webinar - DNS Training Session for ISPs: ICANN & ISPCP · Webinar - DNS Training Session for ISPs: DNS related threats 🚨 Action Items 🚨 · TOMORROW: Call for SOs/ACs: Nominate Fellowship Mentors and Selection Committee Members · Apply Now for ICANN Leadership Positions Public Comment · NEW: Public Comment Summary Report: Proposed Revisions to Community Anti-Harassment Policy · MONDAY: Phase 2 Final Report on the EPDP-TDNs for ICANN Board Consideration · NEXT WEEK: Third Proceeding for Proposed Language for Draft Sections of Next Round AGB · Proposed Updates to the Operating Standards for Specific Reviews · ICANN FY26-30 Operating & Financial Plan, ICANN/IANA FY26 Op Plans & Budgets · Draft PTI FY26 Operating Plan and Budget Events · These events occur in January and February 2025. ICANN82 Register Now for ICANN82 ICANN82 will be held 8 - 13 March 2025 at the Hyatt Regency Seattle Hotel. Prep Week (Online Only): 24 - 26 February 2025 Read more and register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> Information Sharing NEW: ICANN Grant Program Reaches Major Milestone On 26 January 2025, the ICANN Board approved the final slate of applications to be funded in the first cycle of the program, and authorized the ICANN organization (org) to proceed to contract negotiations with all applicants identified in the final slate. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> NEW: Approved Resolutions | Regular Meeting of the ICANN Board | 26 January 2025 Please find the Approved Resolutions from the 26 January 2025 Regular Meeting of the ICANN Board here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…>. NEW: The ICANN MEA Region: 2024 Highlights and 2025 Road Map The accomplishments of 2024 were made possible through the unwavering dedication and collaboration of community members across the MEA region. Your efforts are the cornerstone of ICANN's success. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> ICANN Opens Application Period for New gTLD Applicant Support Program ICANN has opened the application submission period for the Applicant Support Program (ASP), part the New Generic Top-Level Domains (gTLD) Program: Next Round. The ASP provides financial and nonfinancial assistance to qualified, eligible entities who plan to apply for a new gTLD. The application window will be open for 12 months. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> ICANN Opens Application Period for New gTLD Applicant Support Program ICANN has opened the application submission period for the Applicant Support Program (ASP), part the New Generic Top-Level Domains (gTLD) Program: Next Round. The ASP provides financial and nonfinancial assistance to qualified, eligible entities who plan to apply for a new gTLD. The application window will be open for 12 months. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> 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=001RdPA7XW…> 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=001RdPA7XW…>. 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=001RdPA7XW…>. 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=001RdPA7XW…> 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=001RdPA7XW…> on where to find reliable data. Happy editing! Webinars NEW: ICANN Webinar Series Europe - Meet Kurtis Lindqvist: ICANN's President & CEO Date: Wednesday, 12 February 2025 (12:00 - 13:00 UTC) Read more and Register now. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> 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: ICANN & ISPCP Date: Thursday, February 20, 2025, 15:00 UTC to 16:00 UTC Learn more and Register now. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> 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=001RdPA7XW…> Action Items TOMORROW: Call for SO/ACs to Nominate Fellowship Program Mentors and Selection Committee Members ICANN invites its Supporting Organizations (SOs) and Advisory Committees (ACs) to nominate volunteers to serve as mentors in its Fellowship Program and to serve on the Fellowship Program Selection Committee. Each group is welcome to nominate one individual for each role. Interested SOs/ACs should select their respective Fellowship Program mentor and Selection Committee representative no later than 31 January 2025 and notify ICANN Fellowship Program Manager Siranush Vardanyan at siranush.vardanyan(a)icann.org. Individual self-nominations will not be considered. Mentors: • Mentors generally must plan on a time commitment of approximately 30-40 hours before, during, and immediately after each ICANN Public Meeting. This includes extensive pre-meeting preparation, on-site support for their assigned fellows, and post-meeting reporting. • Each mentor will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN84 (from ICANN84 - ICANN86 inclusive). • Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows and to help fellows actively participate in ICANN's work. • Mentors will receive travel funding support (if applicable). Selection Committee Members: • Members should plan on a time commitment of approximately 30-40 hours over four to five weeks for each Public Meeting. • Selection Committee members will typically serve for two years, which encompasses six Public Meetings. • Work for this role will begin in April 2025 to select fellows for ICANN84. • Selection Committee members will not receive travel funding support. For more information on the guidelines and expectations, please go here for additional details on the Mentorship program and here for additional details on the Selection Committee. Mentors cannot serve on the Selection Committee while serving their terms as mentors. TOMORROW: Call for SOs/ACs: Nominate Fellowship Mentors and Selection Committee Members ICANN is seeking Expressions of Interest for members of the 2025 NomCom Standing Committee. Deadline: 31 January 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> 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=001RdPA7XW…> Public Comment NEW: Public Comment Summary Report: Proposed Revisions to Community Anti-Harassment Policy [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> MONDAY: Phase 2 Final Report on the EPDP-TDNs for ICANN Board Consideration [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> Open for Submissions: 23 December 2024 Closed for Submissions: 03 February 2025 NEXT WEEK: Third 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=001RdPA7XW…> Open for Submissions: 19 December 2024 Closed for Submissions: 07 February 2025 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=001RdPA7XW…> Open for Submissions: 23 December 2024 Closed for Submissions: 10 February 2025 ICANN FY26-30 Operating & Financial Plan, ICANN/IANA FY26 Op Plans & Budgets [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> Open for Submissions: 17 December 2024 Closed for Submissions: 14 February 2025 Draft PTI FY26 Operating Plan and Budget [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> Open for Submissions: 17 December 2024 Closed for Submissions: 14 February 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…>. Events These events occur in January and February 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=001RdPA7XW…>. · 9th annual Trinidad and tobago Internet Governance Forum (TTIGF) · Partner2Connect Annual Meeting · NANOG 93 · 2-Day DNSSEC Training at University of Iceland · Afternoon on Internet Security · UTMessan · IIC Annual Asia Digital Communications and Media Forum 2025 · Kenya’s Internet Resilience Post June internet Disruption: Roundtable on Business and Human Rights · 2025 State of the Net · ICANN Webinar Series Europe - Meet Kurtis Lindqvist: ICANN's President & CEO Volume 7, Issue 09 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> | Next Issue: Monday, 03 February 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001RdPA7XW…> ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 US Unsubscribe [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=un&m=00…> | Update Profile [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=oo&m=00…> | Constant Contact Data Notice [constantcontact.com]<https://urldefense.com/v3/__https:/www.constantcontact.com/legal/customer-c…> [Constant Contact][constantcontact.com]<https://urldefense.com/v3/__https:/www.constantcontact.com/landing1/vr/home…>

1 0

Extension of Deadline for Accuracy Assignment
by Feodora Hamza Jan. 29, 2025

Jan. 29, 2025

Sent on behalf of Greg DiBiase Dear GNSO Council Members, First, I would like to thank you for taking the time to review and complete the accuracy assignment. On 25 October, we shared the proposed accuracy assignment<https://lists.icann.org/hyperkitty/list/council@icann.org/message/DPFGXG6WT…>, which included questions for ICANN org and the community. After ICANN org had provided responses to the Council’s questions, we sent the remaining questions in the proposal<https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-…> to interested SG/C/ACs for their input on 12 December 2024 with the deadline of 31 January 2025. Based on the feedback received and in response to multiple requests, we will grant an extension of two more weeks, with the revised deadline now set for Friday, 14 February. As noted during the Council’s previous discussions on the topic of accuracy, the Council recognizes the importance of accuracy and is committed to making progress on this issue. We appreciate your contributions on this matter, and we look forward to receiving your valuable insights. Should you have any questions or require further clarification, please do not hesitate to reach out. Kind regards, Greg DiBiase GNSO Chair

1 0

REMINDER | FW: Re: Follow-up GNSO Council Accuracy Assignment
by Devan Reed Jan. 28, 2025

Jan. 28, 2025

Dear all, Please see the invitation from GNSO Council to provide input to the Accuracy Assignment<https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-…> and ICANN Org input to that assignment attached. We would appreciate your input by 31 January 2025. Thank you. Kind regards, Devan From: Feodora Hamza via council <council(a)icann.org> Reply-To: Feodora Hamza <feodora.hamza(a)icann.org> Date: Thursday, December 12, 2024 at 2:12 PM To: "DiBiase, Gregory" <dibiase(a)amazon.com>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Re: Follow-up GNSO Council Accuracy Assignment Dear Councilors, due to technical issues, please see accuracy assignment attached and linked below. Accuracy Assignment: https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-… [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Kind regards, Feodora Hamza From: "DiBiase, Gregory via council" <council(a)icann.org> Reply to: "DiBiase, Gregory" <dibiase(a)amazon.com> Date: Thursday, 12 December 2024 at 20:57 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Follow-up GNSO Council Accuracy Assignment Dear Councilors, I am following up on the attached email from ICANN Org in which they provided their input on the accuracy assignment. On 25 October, we shared the proposed accuracy assignment, which included questions for ICANN org and the community. Now that ICANN org has provided responses to the Council’s questions, we are now sending the remaining questions in the attached proposal to interested SG/C/ACs for their input. Given the proximity to the holidays, we propose giving groups until Friday, 31 January 2025 to provide their input to the Council. As noted during the Council’s previous discussions on the topic of accuracy, the Council recognizes the importance of accuracy and is committed to making progress on this issue. Your group’s responses to these questions are very important for the Council’s future discussion, and we strongly encourage your groups to think about these questions and provide candid responses. Thank you in advance for your input. Thanks, Greg

2 1

Additional information request - billing contact - EPDP (Temp Spec) Phase 1
by Caitlin Tubergen Jan. 28, 2025

Jan. 28, 2025

Dear Councilors, During the December Council meeting, the Council requested ICANN org to provide additional background on the question from the EPDP Phase 1 Implementation Review Team (IRT) concerning the billing contact. In addition to the background provided in the email of 27 November<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/3Z4MLHGICU…>, it might be helpful to highlight how billing contact is distinct from some of the other contact elements - namely the contact elements in RDDS (formerly referred to as Whois). In what way(s) is the billing contact treated differently than other contacts including administrative, technical, etc.? * Billing contact is referenced in the RAA only with respect to the retention of data, not the display (or publication) of data via RDDS or RDAP. This is distinct from other data elements referenced in the RAA, e.g., administrative contact and technical contact, both of which were required to be displayed as part of the RDDS specification of the RAA. (See Section 3.3 and 3.4 of the RAA.) * Additionally, the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en>, which the EPDP Team was chartered to review, includes no mention of billing contact, but it does include references to registrant contact, administrative contact, and technical contact details. (“Consistent with ICANN's stated objective to comply with the GDPR, while maintaining the existing WHOIS system to the greatest extent possible, the Temporary Specification maintains robust collection of Registration Data (including Registrant, Administrative, and Technical contact information), but restricts most Personal Data to layered/tiered access.”) Was billing contact in scope for the EPDP Phase 1 (Temp Spec) to provide policy recs on? Some have noted that YES, this was in scope because the EPDP Phase 1 (Temp Spec) Charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…> included the following charter question, “b1) What data should registrars be required to collect for each of the following contacts: Registrant, Tech, Admin, Billing?” Some have noted that NO, this data element was not in scope as billing contact was neither part of the Temporary Specification, nor was it part of RDDS data as defined in the RAA. Was the omission of a reference to billing contact data a drafting error of the EPDP (Temp Spec) Team? In other words, did the EPDP Team intend to change the current required retention of billing contact data and make it optional? During a dedicated meeting on this topic, some IRT members expressed an opinion that YES, it was the intention of the EPDP Team to remove this current requirement (of collecting and retaining billing contact data) and make it optional. However, it is unclear to ICANN org whether this is a broadly supported view of the IRT and/or if this is a position supported by the GNSO Council. What is the Council being asked to do now? The Council is being asked to provide guidance to ICANN org on two questions: 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: a. 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 b. 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? What happens next? If the Council answers YES to Questions 1 and 2(b), the Council is advised to acknowledge its guidance and conclusion in writing to ICANN org. If ICANN org receives this confirmation from the Council that it concludes that billing contact data is no longer required to be collected, retained, or transferred to the data escrow agent, ICANN org will begin the process of updating (removing) current requirements related to billing contact. If the Council answers NO to either Question 1 or 2(b), the current RAA requirement for registrars to collect, retain, and transfer billing contact data to the data escrow agent will remain in place. Please let us know if we can be of further assistance by addressing any additional questions or concerns. Best regards, Caitlin

2 2