December 2024 - council - lists.icann.org

Reminder: Input welcome on GNSO Council agenda for 2025 meetings
by Terri Agnew April 14, 2025

April 14, 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

1 4

EPDP Phase 1 RegData Implementation - Billing Contact Issue Summary
by Caitlin Tubergen Jan. 17, 2025

Jan. 17, 2025

Dear Councilors, 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). For background, 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. Billing contact data, however, is referenced in the Registrar Accreditation Agreement<https://www.icann.org/en/system/files/files/registrar-accreditation-agreeme…> (RAA) in § 3.4.1.3 and in the Data Retention Specification<https://www.icann.org/en/system/files/files/registrar-accreditation-agreeme…> in §1.1.2 – §1.1.5. The billing contact data is also referenced in the existing Registrar Data Escrow Specifications<https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf>. ICANN’s publication of updated Registrar Data Escrow Specifications<https://www.icann.org/en/system/files/files/rde-specs-14aug24-en.pdf> in August triggered a discussion within the EPDP Phase 1 IRT regarding the Registration Data Policy’s intended impact on the RAA requirements concerning the billing contact data fields. Generally speaking, unless in conflict with or otherwise modified by a policy recommendation, current contractual requirements and consensus policy requirements remain in place following the publication of a new policy. For that reason, ICANN org informed the IRT on 8 August 2024 that billing contact data must still be collected and retained pursuant to current RAA requirements. In response, some registrar members of 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 registrar IRT members noted the reference to “billing contact” within charter question b1, which provides, “b1) What data should registrars be required to collect for each of the following contacts: Registrant, Tech, Admin, Billing?” Because billing contact is referenced in this charter question but the EPDP Team did not provide a recommendation regarding mandatory (or optional) collection of the billing contact, the registrar position is that the billing contact is no longer required to be collected. On 25 September 2024, there was a special meeting of the IRT<https://community.icann.org/display/RDPIRT/2024-09-25+Registration+Data+Pol…> to discuss the topic of billing contact. While no objection to the registrar view was raised during the special meeting, it is unclear at this stage whether this is a broadly supported view of the IRT, as the majority of stakeholder groups did not have IRT members present at the special meeting. Specifically, members from the BC, GAC, IPC, ISPCP, IPC, NCSG, and SSAC were not in attendance<https://community.icann.org/display/RDPIRT/2024-09-25+Registration+Data+Pol…>. It is worth noting that billing contact information is not referenced in the Temporary Specification, nor is it part of the RDDS specification in the RAA, so it could be argued that billing contact data was not in scope for EPDP Temp Spec Phase 1 policy development. It could also be argued that the drafting error was in the EPDP charter, as billing contact should not have been referenced since it is not part of the Temporary Specification. It is also worth noting that there are other elements within the RAA and Data Retention Specification that were not part of the Temporary Specification and are still required. Thomas provided a high-level overview during the wrap-up session, and noted that some IRT members believe this drafting error is noncontroversial. However, Thomas noted that in the interest of transparency, all Councilors should consult with their respective groups to ensure that others are properly informed and agree with the interpretation raised by the registrars within the IRT. Thomas has also requested that further discussion of billing contact data within the Registration Data Policy be added as a discussion item to the GNSO Council’s December meeting. Accordingly, please check in with your groups regarding the treatment of billing contact data in the Registration Data Policy<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>. Specifically, does your group believe that (1) billing contact data was in scope for the EPDP Temp Spec policy development? If yes, does your group agree that because billing contact data was within the EPDP Team’s scope, (2) there was a drafting error in the EPDP Phase 1 Final Report because the intention of the recommendations, by not including a recommendation concerning the collection, escrow, etc of billing contact data was that the collection and retention of billing contact data should be optional and not mandatory? Note: If, as a matter of ICANN Consensus Policy this was the intended outcome, this interpretation would change current contractual requirements for registrars. We invite Thomas and other councilors to provide additional context. Please feel free to provide thoughts via the list in advance of the December meeting, and please be prepared to discuss next steps during the 19 December Council meeting. Kind regards, and Happy Thanksgiving to those who celebrate, Caitlin

3 4

Proposed Agenda | GNSO Council Meeting | Thursday, 09 January 2025
by Terri Agnew Jan. 9, 2025

Jan. 9, 2025

Dear all, Please find below the agenda for the GNSO Council Meeting on 09 January 2025 at 05:00 UTC This is posted on the agenda wiki page<https://community.icann.org/x/dwByG>. Happy New Year! Terri [Happy New Year" Images – Browse 10,379 ...] GNSO Council Agenda 09 January 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/AgBbGQ. 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, 09 January 2025 at 05:00 UTC: https://tinyurl.com/p69xapak 21:00 Los Angeles (Wednesday); 00:00 Washington DC; 05:00 London; 06:00 Paris; 08:00 Moscow; 16: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/2024/minutes/minutes-gnso…> (Part 1) Minutes<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> (Part 2) of the GNSO Council Meeting on 13 November 2024 were posted on 02 December 2024. Minutes of the GNSO Council Meeting on 19 December were posted on 30 December 2024 Item 2: Opening Remarks / Review of Projects & Action List (0 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Confirmation of Standing Selection Committee (SSC) Leadership and Members Item 4: COUNCIL DISCUSSION - Board Readiness Small Team Update (10 minutes) During the 2023 GNSO Council Strategic Planning Session (SPS), the GNSO Council agreed that it should seek to limit the likelihood of the Council approving PDP recommendations that the ICANN Board is ultimately unable to adopt. To that end, the Council discussed the desire to ensure it submits “board-ready policy recommendations” to the Board, to the extent possible. Generally speaking, a policy recommendation is considered board ready when: the recommendation is likely to achieve board adoption, i.e., the recommendation has been approved by a GNSO Supermajority Vote and will most likely be considered by the Board to be in the best interests of ICANN Community and ICANN org. In August 2024, a Council Small Team began meeting to further discuss the topic of board readiness. Specifically, the Small Team was tasked by GNSO Council to: * Develop a survey/questionnaire related to the Board’s rejection/non-adoption of policy recommendations, which may be administered to relevant PDP Chairs, PDP WG members, ICANN org Support Staff, and Board members. (Examples: EPDP Temp Spec Phase 1 and 2; Subsequent Procedures) * Administer the survey/questionnaire and conduct interviews with relevant PDP Chairs, PDP WG members, ICANN org Support Staff, and Board members. * Synthesize the findings from the survey/questionnaire and interviews into a set of findings and develop a set of recommendations intended to inform Council work on improving Board readiness. Over the past few months, the Small Team has been conducting interviews with community members, beginning with EPDP (Temp Spec) Phase 1. Here, the Council will hear an update on the Small Team’s progress. 4.1 - Introduction of Topic (Jennifer Chung, Board Readiness Small Team Member) 4.2 - Council Discussion 4.3 - Next Steps Item 5: 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. 5.1 - Introduction of Topic (Leticia Castillo, ICANN org Compliance) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - EPDP Temporary Specification Phase 1, Recommendation 18 - Urgent Requests Trilateral Meeting Preparation (10 minutes) ICANN org convened an Implementation Review Team to assist ICANN in implementing the EPDP on the Temporary Specification Phase 1 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…>, which began meeting in May 2019. ICANN org published the draft Registration Data Policy for public comment<https://www.icann.org/en/public-comment/proceeding/registration-data-consen…> on 24 August 2022. Several commenters expressed dissatisfaction with the implementation of Recommendation 18, specifically around the issue of the response timeline for urgent requests. The relevant portion of Recommendation 18 reads, “A separate timeline of [less than X business days] will considered for the response to ‘Urgent’ Reasonable Disclosure Requests, those Requests for which evidence is supplied to show an immediate need for disclosure [time frame to be finalized and criteria set for Urgent requests during implementation].” On 3 June 2024<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/tsinh…>, the Board wrote to the GNSO Council, noting concerns with the proposed urgent request timeline of business days as not fit for purpose, as truly urgent requests should be responded to within minutes or hours rather than business days. Recognizing this, the Board also noted there is no universal mechanism for registrars to authenticate law enforcement entities. The GNSO Council responded on 29 August 2024<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/dibia…>, agreeing with the Board’s concerns and suggesting a trilateral meeting between the Board, GNSO Council, and GAC to discuss a potential path forward in light of the concerns. On 15 October 2024<https://gac.icann.org/contentMigrated/gac-follow-up-on-urgent-requests-gac-…>, the GAC wrote to the Board, recommending, “[f]or the work on authentication, we would support the establishment of a joint PSWG/CPH task force. For the work on the response time for authenticated requests, we invite the Board and the GNSO Council to identify an expedited procedure for addressing this workstream. We strongly suggest resuming the work of the IRT, which was halted last summer.” A trilateral meeting was held on 4 November 2024<https://community.icann.org/display/gnsocouncilmeetings/Dialogue+with+GAC%2…> and the Board, GAC, and GNSO Council discussed next steps, including potentially resuming discussions with the IRT. The Council discussed this issue in detail during its meeting on 19 December 2024<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>. Here, the Council will prepare for the next trilateral meeting with the ICANN Board, GAC, and GNSO Council. 6.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: 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. 7.1 - Introduction of Topic (Thomas Rickert, GNSO Council Liaison to the EPDP (Temp Spec) Phase 1 IRT) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL DISCUSSION: Review of Projects List and Action Decision Radar (35 minutes) During the GNSO Council’s 2023 strategic planning session, the Council discussed the topic of how to be an effective manager of the GNSO’s Policy Development Process (PDP). In recognition of the importance of regularly reviewing the Council’s portfolio of work, the Council agreed to the following action item, “During a session at ICANN79, Council to prepare for a careful review of the work captured in the Program Management Tool (PMT) that will conclude or initiate prior to the next AGM, or continue beyond the next AGM[.]” The Council conducted this inaugural review of the Projects List during its Working Session at ICANN79<https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Workin…> on Sunday, 3 March 2024, and continued its review of the Action Decision Radar (“ADR”) during the 16 May 2024 meeting due to time constraints. Here, the Council will continue this practice and review the contents of the Projects List and ADR and discuss next steps in preparation for the upcoming Strategic Planning Session. 8.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Vice-Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: Any Other Business (15 minutes) 9.1 - GNSO Liaison to the ccNSO update 9.2 - ICANN82 - update on planning and draft GNSO schedule 9.3 - SPS reminders 9.4 - Public Comment Opportunities * ICANN FY26–30 Operating & Financial Plan, ICANN/IANA FY26 Op Plans & Budgets<https://www.icann.org/en/public-comment/proceeding/icann-fy2630-operating-f…> * Draft PTI FY26 Operating Plan and Budget<https://www.icann.org/en/public-comment/proceeding/iana-2030-strategy-draft…> 9.5 - IGF/WSIS+20 Small Team _______________________________ 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 05: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 21:00 (Wednesday) San José, Costa Rica (CST) UTC-6 23:00 (Wednesday) New York/Washington DC, USA (EDT) UTC-5 00:00 Buenos Aires, Argentina (ART) UTC-3 02:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:00 Paris, France (CEST) UTC+1 06:00 Moscow, Russia (MSK) UTC+3 08:00 Singapore (SGT) UTC+8 13:00 Melbourne, Australia (AEST) UTC+11 16:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/p69xapak.

1 1

Consent Agenda Motion - GNSO Standing Selection Committee Members and Leadership for 2025
by Nacho Amadoz Dec. 24, 2024

Dec. 24, 2024

Dear Councillors, Please find attached the draft motion for the single consent agenda item - the GNSO Standing Selection Committee (SSC) Members and Leadership for 2025. Merry Christmas and Happy New Year! - when appropriate :D Nacho

2 1

Draft Minutes of the 19 December GNSO Council Meeting
by John Emery Dec. 23, 2024

Dec. 23, 2024

Dear Councilors, Attached, please find the draft minutes of the GNSO Council Meeting held on 19 December 2024. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure section 3.5: "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 30 December. Thank you and enjoy your holidays! Sincerely, 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

Action Items | GNSO Council meeting 19 December 2024
by Terri Agnew Dec. 23, 2024

Dec. 23, 2024

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday, 19 December 2024 Please refer to the Action Item page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> for updates on item completion progress. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. GNSO Council meeting on 19 December 2024 Item 3: Consent Agenda (5 minutes) * GNSO Review of the GAC Communiqué Action Items: 1. On behalf of the GNSO Council Chair, the GNSO Secretariat communicates the GNSO Council Review of ICANN81 GAC Communiqué on Issues of Importance to the ICANN Board. 2. The GNSO Secretariat, on behalf of the GNSO Council, requests that the GNSO Liaison to the GAC also informs the GAC of the communication between the GNSO Council and the ICANN Board. * Recommendations Report for the Expedited Policy Development Process (EPDP) on Internationalized Domain Names (IDNs) Phase 2 Action Items: The GNSO Secretariat transmits the Recommendations Report to the ICANN Board regarding the Phase 2 Final Recommendations<https://gnso.icann.org/sites/default/files/policy/2024/presentation/epdp-id…> from the EPDP on IDNs and communicates the outcomes from the GNSO Council's decision as appropriate. * Confirmation of GNSO Empowered Community Representative (Tomslin Samme-NIar) Action Items: On behalf of the GNSO Council the GNSO Secretariat communicates that Tomslin Samme-Nlar is the EC Representative to the ICANN Secretary which will serve as the required written certification from the GNSO Chair designating the individual who shall represent the Decisional Participant on the EC Administration. Item 4: COUNCIL VOTE - Empowered Community Approval Action on Fundamental Bylaws Amendments to Article 4 Accountability and Review, 4.2 Reconsideration (10 minutes) Action Items: GNSO Representative on the EC Administration to promptly inform the EC Administration, the other Decisional Participants, and the ICANN Corporate Secretary about the GNSO Council’s decision with respect to the Approval Action. Item 5: COUNCIL VOTE - Charter for Policy Development Process on Latin Script Diacritics (15 minutes) Action Items: The GNSO Council requests that the GNSO Secretariat publish the Call for Volunteers for Members, Observers, and relevant liaisons per the membership structure within the PDP WG charter. Item 6: COUNCIL DISCUSSION - EPDP Temporary Specification Phase 1, Recommendation 18 - Urgent Requests (20 minutes) Action Items: GNSO Council leadership to draft a letter to the GAC for Council review to better understand the GAC proposal from 15 October. The letter will focus on questions regarding the potential authentication methods for law enforcement and to further understand the expected policy work by GAC or other activities relating to urgent requests, in preparation for the meeting with the GAC and the Board. Item 7: COUNCIL DISCUSSION - Request for Guidance from the New gTLD Subsequent Procedures / IDNs EPDP Phase 1 IRT (10 minutes) Action Items: Staff on behalf of the GNSO Council leadership to call for volunteers for a small team to develop the scope of work for the issue and to explore the options of GNSO Guidance Process (GGP) or Expert Working Group (EWG). Item 8: COUNCIL UPDATE: EPDP Temporary Specification Phase 1 - Billing Contact (25 minutes) Action Items: Staff to provide additional information as background and Council to revisit in January. Item 10: COUNCIL DISCUSSION - GNSO Council PR Officer Update (10 minutes) Action Items: GNSO Councilors to provide guidance on the type of content that should be posted on the LinkedIn page by the PR Officer. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Document and Motion deadline | Monday, 30 December 2024 at 23:59 UTC for GNSO Council Meeting 09 January 2025 at 05:00 UTC
by Terri Agnew Dec. 23, 2024

Dec. 23, 2024

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 30 December 2024 at 23:59 UTC) for the GNSO Council Meeting on Thursday, 09 January at 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://community.icann.org/x/BABbGQ Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

FYI | FW: [CORRESPONDENCE] Tripti Sinha to Greg DiBiase - Board Ready Recommendations
by Terri Agnew Dec. 23, 2024

Dec. 23, 2024

Hello all, This will be posted on the GNSO Correspondence page shortly: https://gnso.icann.org/en/council/correspondence/2024 Happy Holidays! Terri From: Wendy Profit <wendy.profit(a)icann.org> Date: Monday, December 23, 2024 at 9:56 AM 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 - Board Ready Recommendations Dear Greg, Please find the attached letter from ICANN Board Chair Tripti Sinha regarding the GNSO Initiative: Board-Ready Policy Recommendations. Thank you and best regards, Wendy Profit Board Operations Senior Manager ICANN

1 0

FYI | ] NEW: A Year of Progress: The New gTLD Program in 2024
by Terri Agnew Dec. 23, 2024

Dec. 23, 2024

FYI [https://danh45uab.cc.rs6.net/on.jsp?ca=7a7d16a9-1b35-43c6-b9a9-e4ebd30fec65…] Monday, 23 December 2024 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. Click Here to Learn More about the RDRS Pilot Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> 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 · ICANN82 Newcomers Session Sign-Up · ICANN82 Community Childcare Grants Program: Apply Now Information Sharing · NEW: Global Digital Compact Endorsement: ICANN's Position · NEW: A Year of Progress: The New gTLD Program in 2024 · NEW: Reflections on 2024 and a New Chapter for ICANN · NEW: ICANN Seeks Input on Updates to the Operating Standards for Specific Reviews · NEW: ICANN Board Seeks Input on EPDP-IDNs Phase 2 Final Report · NEW: Register for the IANA 2030 Strategy: PTI 2025-2030 Draft Strategic Plan Webinar · NEW: ICANN Seeks Input on Proposed Language for Next Round Applicant Guidebook · 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 🔥 Action Items 🔥 · TODAY: Call for Expressions of Interest: 2025 ICANN Nominating Committee Standing Committee Members · ICANN Community Excellence Award: Now Accepting Nominations · Call for SOs/ACs: Nominate Fellowship Mentors and Selection Committee Members Public Comment · NEW: Phase 2 Final Report on the EPDP-TDNs for ICANN Board Consideration · NEW: Proposed Updates to the Operating Standards for Specific Reviews · Continuous Improvement Program Framew [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…>ork [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> · IANA 2030 Strategy: Draft PTI Strategic Plan covering 2025 to 2030 · Third Proceeding for Proposed Language for Draft Sections of Next Round AGB · ICANN FY26-30 Operating & Financial Plan, ICANN/IANA FY26 Op Plans & Budgets · Draft PTI FY26 Operating Plan and Budget Events · These events occur on 23 December 2024 ICANN82 ICANN82 Newcomers Session Sign-Up Want to introduce your group’s work to ICANN82 Community Forum Meeting newcomers, including Fellowship and NextGen@ICANN Programs Participants? Sign up for a 30 minute session on 8-9 March, 2025. These outreach sessions are part of the ""Get To Know ICANN Community"" Onboarding Program for Newcomers and are the opportunity for every SO/AC to share information with the ICANN Meeting newcomers and highlight the important work that your group does within ICANN. Sign up for available slots here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…>. For any additional questions, please contact ICANN Fellowship Program Manager, Siranush Vardanyan at siranush.vardanyan(a)icann.org<mailto:siranush.vardanyan@icann.org>. The deadline to sign up for a slot is December 30th, 2024 ICANN82 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. Deadline: Friday, 24 January 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> Information Sharing NEW: Global Digital Compact Endorsement: ICANN's Position On 22 September 2024, the U.N. Summit of the Future adopted the Pact for the Future, including the Global Digital Compact [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> (GDC). The Office of the U.N. Secretary-General's Envoy on Technology states [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> that the vision of the GDC "refers to achieving the goal of 'an inclusive, open, sustainable, fair, safe and secure digital future for all'." This aligns with ICANN's mission to help ensure a stable, secure, and unified global Internet. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> NEW: A Year of Progress: The New gTLD Program in 2024 Over the past 12 months, the ICANN Board, community, and organization have collaborated to progress the implementation of the New gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> – projected to open for applications in April 2026. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> NEW: Reflections on 2024 and a New Chapter for ICANN As 2024 comes to an end, ICANN is beginning a new chapter with Kurtis Lindqvist, our new president and CEO [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…>, in the lead. This is a good time to reflect on all that ICANN has accomplished this year and look forward to the opportunities and challenges ahead. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> NEW: ICANN Seeks Input on Updates to the Operating Standards for Specific Reviews Over the course of recent Specific Review cycles, the ICANN community, Board, and organization (org) identified areas that posed challenges to the ability of the reviews to effectively fulfill their purpose. To address these areas, ICANN org developed a series of process improvements and integrated them into an updated Draft Operating Standards for Specific Reviews. Updates to the Draft Operating Standards are focused on improving review scope setting and planning, increasing the efficiency and effectiveness of review work, and incorporating best project management practices into the Specific Reviews process. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> NEW: ICANN Board Seeks Input on EPDP-IDNs Phase 2 Final Report Following the Generic Names Supporting Organization (GNSO) Council's approval of the Phase 2 Final Report on the Expedited Policy Development Process (EPDP) on Internationalized Domain Names (IDNs), the ICANN Board is seeking the community's input. The GNSO Council's approval of all 20 outputs, including 14 policy recommendations and six pieces of implementation guidance, obligates the Board to adopt the recommendations under the ICANN Bylaws, unless, by a vote of more than two-thirds, the Board determines that the policy is not in the best interests of the ICANN community or ICANN. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> NEW: Register for the IANA 2030 Strategy: PTI 2025-2030 Draft Strategic Plan Webinar We invite the community to join us for a public webinar on 14 January 2025 at 16:00 UTC to discuss the Internet Assigned Numbers Authority (IANA) functions strategy for 2025–2030. The webinar will review the IANA proposed strategic objectives designed to help Public Technical Identifiers (PTI) continue to provide secure and accountable management of the Internet's unique identifier systems. Register here. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> NEW: ICANN Seeks Input on Proposed Language for Next Round Applicant Guidebook Today, ICANN opened a new Public Comment proceeding. This is the third in a series of Public Comment proceedings that will gather input from the ICANN community on proposed language for selected sections of the Applicant Guidebook for the New gTLD Program: Next Round. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> 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=001x7Jd2gG…> 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=001x7Jd2gG…> 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=001x7Jd2gG…>. 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=001x7Jd2gG…>. 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=001x7Jd2gG…> 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=001x7Jd2gG…> on where to find reliable data. Happy editing! Action Items TODAY: Call for Expressions of Interest: 2025 ICANN Nominating Committee Standing Committee Members The NomCom Standing Committee shall be composed of five seats: four members and one ex-officio observer. The term of all four appointed members shall be three years. Deadline: 23 December 2024 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> ICANN Community Excellence Award: Now Accepting Nominations The nomination period will close on 9 January 2025 at 23:59 UTC. Read more [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…>. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> 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. 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=001x7Jd2gG…> Public Comment NEW: 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=001x7Jd2gG…> Open for Submissions: 23 December 2024 Closed for Submissions: 03 February 2025 NEW: [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…>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=001x7Jd2gG…> Open for Submissions: 23 December 2024 Closed for Submissions: 10 February 2025 Continuous Improvement Program Framework [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> Open for Submissions: 21 November 2024 Closed for Submissions: 17 January 2025 IANA 2030 Strategy: Draft PTI Strategic Plan covering 2025 to 2030 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> Open for Submissions: 26 November 2024 Closed for Submissions: 29 January 2025 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=001x7Jd2gG…> Open for Submissions: 19 December 2024 Closed for Submissions: 07 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=001x7Jd2gG…> 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=001x7Jd2gG…> 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=001x7Jd2gG…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…>. Events These events occur on Monday, 23 December 2024. 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=001x7Jd2gG…>. · FY26-FY30 Middle East Regional Plan Development-Kick-Off Call Volume 6, Issue 96 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…> | Next Issue: Thursday, 02 January 2025 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001x7Jd2gG…>

1 0

Document and Motion deadline | Monday, 30 December 2024 at 23:59 UTC for GNSO Council Meeting 09 January 2025 at 05:00 UTC
by Terri Agnew Dec. 20, 2024

Dec. 20, 2024

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 30 December 2024 at 23:59 UTC) for the GNSO Council Meeting on Thursday, 09 January at 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://community.icann.org/x/BABbGQ Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0