- council - lists.icann.org

Meeting Invitation | GNSO Council Meeting | Thursday, 19 December 2024
by Terri Agnew 10 Dec '24

10 Dec '24

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

1 0

UPDATED Agenda | Proposed Agenda | GNSO Council Meeting | Thursday, 19 December 2024
by Terri Agnew 10 Dec '24

10 Dec '24

**Updated below. 1. Removed (this will be added to the Jan 2025 meeting): Item 10 DISCUSSION ITEM - Request for Guidance from the Rights Protection Mechanisms (RPMs) PDP IRT on the Scope of Uniform Rapid Suspension (URS) Recommendation 1 (15 minutes) 2. Adjusted topic item numbers 3. Updated allocated time for some topics Dear all, Please find below the final proposed agenda for the GNSO Council Meeting taking place on Thursday, 19 December 2024 at 21:00 UTC for 2 hours This has been posted on the agenda wiki page<https://community.icann.org/x/E4DyEg>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO GNSO Council Agenda 19 December 2024 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/CICeFw. 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, 19 December 2024 at 21:00 UTC: https://tinyurl.com/ybse6rda 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/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 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 17 October 2024 were posted on 01 November 2024. 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. 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) * GNSO Review of the GAC Communiqué * Recommendations Report for the Expedited Policy Development Process (EPDP) on Internationalized Domain Names (IDNs) Phase 2 * Confirmation of GNSO Empowered Community Representative (Tomslin Samme-NIar) Item 4: COUNCIL VOTE - Empowered Community Approval Action on Fundamental Bylaws Amendments to Article 4 Accountability and Review, 4.2 Reconsideration (10 minutes) Pursuant to Section 25.2(e) of the ICANN Bylaws, the ICANN Board approved Fundamental Bylaws Amendments to Article 4, Sections 4.2 and 4.3<https://itp.cdn.icann.org/en/files/governance/uppdates-to-article-4-icann-g…> of the ICANN Bylaws. The ICANN Board took a series of actions and communications to move forward with the ICANN Grant Program while in some cases, trying to address issues presented by the original language of Recommendation 7, including: * 26 October 2023 resolutions<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> revisiting the Board's prior approval of Recommendation 7 and directing the development of a more general process for the ICANN community to indicate when ICANN's Accountability Mechanisms should not be available; * 21 January 2024 initiation<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> of a Fundamental Bylaws amendment process setting forth the general process for the ICANN community to limit access to ICANN's Accountability Mechanisms; and, * 2 March 2024 letter<https://www.icann.org/files/correspondence/sinha-to-clemente-et-al-02mar24-…> to the CCWG-AP’s Chartering Organizations specifying a proposed change to Recommendation 7 to remove a reference to the “Independent Application Assessment Panel” so that Recommendation 7 could better achieve its goal of preserving auction proceeds for grants instead of funding challenges to decisions on grant applications; and the On 7 August 2024, ICANN opened a Public Comment Forum<https://www.icann.org/en/public-comment/proceeding/proposed-fundamental-byl…> on the updated Fundamental Bylaws Proposal, with the proposed amendments being limited and in line with Recommendation 7. Nine submissions were received, and all commenters were supportive of the proposal as posted for Public Comment. Commenters noted that the updated proposal was better aligned to the intention of Recommendation 7 and was a more appropriate means of implementation than the prior proposal. Concurrently, ICANN finalized confirmation with the Chartering Organizations of the CCWG-AP their support or non-objection to the proposal to update Recommendation 7, including confirmation with the GAC that it too is in a position to support or not object to the updating of Recommendation 7, in light of the Board's acceptance of this alternate path. The Board has formally confirmed its adoption of the updated Recommendation 7 and the respective Fundamental Bylaws Amendments. At ICANN81, ICANN Org held an Empowered Community Approval Action<https://www.icann.org/en/ec/fundamental-bylaws-amendment-to-accountability-…> on Fundamental Bylaws Amendments to Article 4 Accountability and Review, 4.2 Reconsideration.<https://www.icann.org/en/ec/fundamental-bylaws-amendment-to-accountability-…> The Fundamental Bylaws Amendments will only become effective if approved by the Empowered Community using the process set forth at Section 25.2(f)<https://www.icann.org/resources/pages/governance/bylaws-en/#article25> and Annex D<https://www.icann.org/resources/pages/governance/bylaws-en/#annexD>, Article 1 of the ICANN Bylaws. The convening of the Approval Action Community Forum is part of this process. Following the Approval Action Community Forum, the GNSO Stakeholder Groups and Constituencies are asked to provide feedback, opinions or comments on their support for, objection to, or abstention from the Approval Action under consideration. The GNSO Council must decide and inform the EC Administration of its decision within twenty-one (21) days after the expiration of the Community Forum whether to support, object to, or abstain from the Approval Action by affirmative vote of a GNSO Supermajority. A discussion and vote on the Approval Action is scheduled for this GNSO Council meeting. If more time is needed, a placeholder for an email vote will be scheduled to initiate on Monday, 23 December. Here, the Council will vote on the Fundamental Bylaw amendments. 4.1 - Presentation of Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-12-19> (Tomslin Samme-NIar, GNSO Council Vice Chair) 4.2 - Council Discussion 4.3 - Council Vote (voting threshold: Supermajority) Item 5: COUNCIL VOTE - Charter for Policy Development Process on Latin Script Diacritics (15 minutes) On 13 November 2024, the GNSO Council passed a motion<https://gnso.icann.org/en/council/resolutions/2020-current#202405> to initiate a Policy Development Process (PDP) on requesting Latin Script Diacritics. The objective of the Preliminary Issue Report<https://gnso.icann.org/sites/default/files/policy/2024/draft/preliminary-is…> was for ICANN org to assess all relevant issues related to the GNSO Council request, and, following Community Input during the Public Comment<https://www.icann.org/en/public-comment/proceeding/preliminary-issue-report…> phase, to recommend a course of action to the GNSO Council. The PDP will be focused on the circumstance when an ASCII gTLD and the Latin script diacritic version of the gTLD are not variants of each other AND may be found to be visually similar to each other. The issue is theoretically possible for any existing ASCII or Latin script IDN gTLD pairs, and is essentially infinite for future applied-for ASCII or Latin script IDN gTLDs, where diacritics are involved. The Final Issue Report<https://gnso.icann.org/sites/default/files/policy/2024/draft/final-issue-re…> includes a draft charter prepared by ICANN org supporting the GNSO Council. Having discussed the draft charter, the Council determined that edits were needed with respect to, but not limited to, the membership structure. Here, the Council will vote on the updated charter. 5.1 - Presentation of Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-12-19> (Jennifer Chung) 5.2 - Council Discussion 5.3 - Council Vote (voting threshold: affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House) Item 6: COUNCIL DISCUSSION - EPDP Temporary Specification Phase 1, Recommendation 18 - Urgent Requests (15 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. Here, the Council will discuss the GAC’s proposal and determine next steps. 6.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - Request for Guidance from the New gTLD Subsequent Procedures / IDNs EPDP Phase 1 IRT (10 minutes) The New gTLD Subsequent Procedures (SubPro) PDP provided a recommendation to allow single character gTLDs in the next round, which was expanded upon by the IDNs EPDP Phase 1 Final Report. The IDNs EPDP Phase 1 Final Report put forth important detail and limitations on the SubPro recommendation, prescribing that the single character gTLDs be limited to the Han script and that relevant guidelines must be developed and put in place by the Chinese, Japanese, and Korean (CJK) Generation Panels (GPs). In a public comment<https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-scr…> proceeding, the CJK GPs noted their opposition to moving forward with single character Han script gTLDs. And in a subsequent public comment<https://www.icann.org/en/public-comment/proceeding/second-proceeding-for-pr…> proceeding on relevant Applicant Guidebook (AGB) sections, a number of commenters also expressed their opposition. This opposition was discussed with the IDN Sub-Track, a sub-track to the SubPro IRT, where it was agreed to not move forward with single character Han script gTLDs. That decision was then discussed with the main SubPro IRT, where it was determined that this decision should be shared with the GNSO Council. A write-up was shared with the Council on [date]. Here, the Council will be briefed on the tentative decision from the SubPro IRT and to discuss the appropriate next steps, if any. 7.1 - Introduction of Topic (Anne Aikman-Scalese & Susan Payne, Council co-liaisons to the SubPro IRT) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL UPDATE: EPDP Temporary Specification Phase 1 - 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 on the following questions: 1. Does your group believe that billing contact data was in scope for the EPDP Temp Spec policy development? 2. If yes, does your group believe 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. Here, the Council will discuss the above questions and determine next steps. 8.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: COUNCIL UPDATE - 2025 Council Strategic Planning Session (SPS) (15 minutes) The GNSO Council will hold its annual Strategic Planning Session (SPS) in Washington, DC on 14-15 January 2025. The SPS is a dedicated meeting during which the Council will discuss and identify its priorities and goals for the upcoming year. Council Leadership has been developing the agenda, and has identified, et.al., the following themes for discussion: Overview of the Council’s Role and Remit and the Role of Councilors * Evolution of the Council’s role in managing PDPs, including improvements derived from previous SPS * Review of work for the upcoming year (including targeted review of project management tools) * Consideration of recent projects that did not follow the typical path after Council adoption (e.g., delayed implementation, challenges in implementing recommendations) * Continuous improvement of the GNSO (board readiness, GNSO Standing Committee on Continuous Improvement (SCCI), Five Year Strategic Plan) Here, the Council will receive an update from Leadership and Support Staff on SPS planning and important information to know ahead of the SPS. 9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 9.2 - Council Discussion 9.3 - Next Steps Item 10: COUNCIL DISCUSSION - GNSO Council PR Officer Update (15 minutes) During the GNSO Council Strategic Planning Session (SPS) that was held from 14-16 December 2022, the GNSO Council identified the need to enhance its communication efforts to promote its work and outcomes to a broader audience, as well as to counterbalance negative stories and misinformation about GNSO policy work that seemed to have gained prominence on social media and industry blogs. A GNSO Council small team<https://community.icann.org/display/gnsocouncilmeetings/Communications+Smal…> was formed in April 2023 to develop a strategic communications plan<https://gnso.icann.org/sites/default/files/policy/2024/draft/gnso-council-c…> for the GNSO Council. Within its report, the small team put forward two substantive recommendations for new mechanisms to enhance GNSO Council’s communications practice: 1) appoint a member in the GNSO Council to serve as the “PR officer” to guide / support policy staff in implementing the communications strategy and proposed improvements; and 2) establish a LinkedIn page for the GNSO Council. Following the first recommendation, Lawrence Olawale-Roberts agreed to assume the role of PR Officer. Here, the Council will hear an update from Lawrence Olawale-Roberts on his work in this role. 10.1 - Introduction of Topic (Lawrence Olawale-Roberts, GNSO Council PR Officer) 10.2 - Council Discussion 10.3 - Next Steps Item 11: Any Other Business (10 minutes) 11.1 - GNSO Liaison to the GAC update 11.2 - ICANN82 - funded travel emails were sent out, please action as past deadline _______________________________ 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/ybse6rda.

1 0

GNSO Council Portfolio Management Tool Suite - 19 December 2024 Meeting
by Steve Chan 10 Dec '24

10 Dec '24

Dear all, Please see links below to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 19 December 2024. Agenda: * https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen… Motions: * https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-12-19 Links to the Program Suite: * Program/Project Management Framework (PPMF): https://community.icann.org/x/0YvzC * Portfolio Management Tool (PMT): https://community.icann.org/x/04vzC * **Action/Decision Radar (ADR): https://community.icann.org/x/14vzC * **Project List (PL): https://community.icann.org/x/1YvzC * **Action Items (AIs): https://community.icann.org/x/RgZlAg * Council Small Teams (CSTs): https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Small+… * ** denotes the required three work products for review by Councilors in preparation for monthly meetings Key Program Suite Structural Changes for this Period: * None for this period. Key Project Changes or Milestones for this Period: * GNSO Council to consider the proposed charter for the initiated PDP on Latin Diacritics * GNSO Council to consider the Recommendations Report to the Board on the EPDP IDN – Phase 2 * GNSO Council to produce a response to GAC Advice, if any, from ICANN81 (Istanbul) * GNSO Council to consider next steps on EPDP_IDN – Phase 1 single character gTLDs * GNSO Council to consider next steps on EPDP_P1 Billing Contact * GNSO Council to consider next steps on EPDP_P1 Urgent Requests * GNSO Council to consider next steps on RPMs_P1 Scope of URS Recommendations * Active Project Packages: * GNSO_TPR: https://community.icann.org/x/MQDQCQ (last published for November 2024) * IRT Status Page: https://www.icann.org/policy/implementation Key Project Activities for January/February 2025: * GNSO – Strategic Planning Session in Washington DC * GNSO Council to consider next steps on Policy & Implementation – Policy Status Report * GNSO Council to consider submitting comments on ICANN’s Draft FY26 Budget and Operating Plan * GNSO Council to consider submitting comments on the CIP-CCG Continuous Improvement Framework * GNSO Council to consider submitting comments on Revised Operating Standards for Specific Reviews * Refresh of the SSC and Mentor to Fellowship Program Please let staff know if you have any questions. Best, Steve Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 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 0

Call for Volunteers for Small Team for RPMs P2 Next Steps re: Action Items | GNSO Council ICANN81 Istanbul 2024
by Julie Hedlund 10 Dec '24

10 Dec '24

Dear Councilors, On behalf of Council leadership and per the Action Item below, this is a Call for Volunteers as follows: Action Items: The GNSO Council leadership will post to the list a Call for Volunteers for a small team of Councilors to consider the path forward on a PSR or related work to inform the launch of RPMs Phase Two. Please respond to the Council list if you are interested in volunteering by Tuesday, 17 December. Kind regards Julie Hedlund Policy Director From: Terri Agnew via council <council(a)icann.org> Reply-To: Terri Agnew <terri.agnew(a)icann.org> Date: Thursday, November 21, 2024 at 4:38 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [council] Action Items | GNSO Council ICANN81 Istanbul 2024 Dear Councilors, Please find the action items, as stated during the meetings at ICANN81 Istanbul, 10 -14 November 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. Sunday, 10 November 2024 GNSO Working Session 1 of 2 | 09:00 - 10:00 IST (60 mins) Agenda 1. Joint SSAC and GNSO Council (45 minutes) a. SSAC’s Evergreen Topics b. DS Automation c. Registrar Name Management Action Items: Establish specific liaisons from the SSAC and explore other methods of engagement. 2. Dialogue about the new 5 Yr Strategy Plan (IANA Kim & Amy C) (30 minutes) Action Items: GNSO Councilors are encouraged to provide input on the 5-year plan and the engagement survey. Sunday, 10 November 2024 Joint session: GAC and GNSO Council | 15:00 - 16:00 IST (60 mins) - Applicant Support Program - The Board and GAC have been working on a compromised middle way solution in order to keep the expected efficiency of the ASP program while allowing more room and opportunity to promote awareness in less developed regions. The GAC would like to know whether GNSO is also agreeable to such a conclusion. Action Items: Paul McGrady will address the question on NGOs from the GAC representative from India. 6. Diacritics Action Items: GNSO Council to discuss how GAC participation is addressed in the charter. Monday, 11 November 2024 Joint session: ICANN Board and GNSO Council | 15:00 - 16:00 IST (60 mins) Agenda: 1. BOARD TOPIC: The Board has been continuing work on a Global Public Interest Framework in relation to ICANN policy making, and has recently finalized a draft GPI Framework Checklist [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1uVOXywoo…>. The Board is eager to hear feedback from the Council on this checklist, including whether the Council feels this will be a useful policy development tool and any thoughts on how it could be further developed. (20-30 minutes) Action Items: Councilors to review the GPI Framework/Checklist and explore ways it could be incorporated into PDPs. 1. Next steps for the Council letter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> re: Urgent requests Action Items: The GNSO Council to consider the GAC proposal and include this item for December meeting as a discussion point. Staff to schedule a trilateral meeting with the Board and GAC in January. Wednesday, 13 November 2024 GNSO Council Informal Meeting [C] | 09:00 - 10:00 IST (60 mins) 1. Urgent Request Dialogue with Board + PSWG + GNSO Council Action Items: 1. The SCCI charter to be updated prior to the Council Public Meeting, focusing on revisions to the Task Forces membership structure (deletion of all NCAs). 2. The resolved clause in the PDP motion for Latin Diacritics to be updated prior to the Council Public Meeting. Wednesday, 13 November 2024 GNSO Council Meeting Part 1 | 13:15 - 15:15 (120 mins) Item 3: Consent Agenda (5 minutes) · Motion to Defer the Rights Protection Mechanisms (RPMs) Policy Development Process (PDP) Phase 2 for an Additional Six Months Action Items: The GNSO Policy Support Staff to notify ICANN org Global Domains & Strategy of the deferral the Rights Protection Mechanisms (RPMs) Policy Development Process (PDP) Phase 2 for an Additional Six Months. Item 4: Motion to Adopt the Revised Charter for a Permanent Standing Committee on Continuous Improvements (SCCI) Action Items: 1. The GNSO Secretariat notifies the SCCI that the GNSO Council has adopted the SCCI charter. 2. The GNSO Secretariat publishes the Call for Volunteers for Members, Board Liaisons, and Observers per the membership structure in the SCCI charter. Item 5: COUNCIL VOTE - Expedited Policy Development Process on Internationalized Domain Names (EPDP-IDNs) Phase 2 Final Report (15 minutes) Action Items: The GNSO Secretariat, on behalf of Council, thanks the leadership, members, participants, and liaisons to the EPDP-IDNs Team for their commitment and hard work in completing the Phase 2 effort of this EPDP. Item 6: COUNCIL VOTE - Initiation of Policy Development Process for Latin Script Diacritics (15 minutes) Action Items: The GNSO Council requests that the PDP Working Group be convened as soon as possible after the adoption of the PDP Working Group Charter in order to fulfill the requirements of this PDP Item 7: COUNCIL DISCUSSION - Policy Status Report (PSR) on Rights Protection Mechanisms PDP Phase 2 (15 minutes) Action Items: The GNSO Council leadership will post to the list a Call for Volunteers for a small team of Councilors to consider the path forward on a PSR or related work to inform the launch of RPMs Phase Two. Item 8: COUNCIL DISCUSSION: Draft Charter on Latin Diacritics (20 minutes) Action Items: Councilors agreed to revise the charter, including changing the membership structure to an open model and updating the scope of work; Jennifer Chung volunteered to produce a revised charter for the Council to review. Item 12: Any Other Business (15 minutes) 12.2 - Review CIP-CCG’s proposed edits on continuous improvement: · The SO, AC, or NomCom is fulfilling its purpose · The structures of SO, AC, or NomCom are effective · The operations of SO, AC, or NomCom are efficient · The SO, AC, or NomCom is accountable internally to its stakeholders and substructures (where applicable), and externally to the wider ICANN community in benefit of the global Internet population · The SO, AC, or NomCom collaborates to further the mission of ICANN and the effectiveness of the ICANN bottom-up multistakeholder model Action Items: Damon Ashcraft suggested revising the language based on the GPI Framework review. Thursday, 14 November 2024 GNSO Council Wrap-Up | 13:15 - 14:30 IST (75 mins) 1. Confirm GNSO Empowered Community Rep Action Items: Tomslin Samme-Nlar will be the EC Rep until leadership chooses the next Rep to be confirmed by Council at the December meeting. 2. Call for volunteers for GAC Communique response Action Items: 1. Volunteers: Susan Payne, Osvaldo Novoa, Farzaneh Badiei, Samantha Demetriou, Bruna Martins dos Santos, Jennifer Chung, and Desiree Miloshevic. 2. Staff to schedule a small team meeting. 3. Staff to check on when GAC is scheduled to meet with the Board. [COMPLETE–as there is no GAC Advice a meeting will not be scheduled until February although the Council may wish to draft a response to Issues of Importance] 4. For the next meeting the call for volunteers should go out before the meeting so that the team can meet before the meeting 3. Update from GNSO Council Liaison to the Registration Data Policy Implementation Review Team Action Items: GNSO Council leadership with Thomas Rickert, and support staff to summarize the request for Council, and add this as a discussion item on the December agenda. a.Urgent Requests Action Items: GNSO Leadership to send a reminder of the need for Councilors to review the GAC response on Urgent Requests. b. New Councilors Onboarding Action Items: GNSO Councilors to consider methods to supplement the existing processes and materials. Jennifer Chung and Paul McGrady volunteered. c.SPS Action Items: Staff to schedule a meeting for SPS planning for the first week in December after which the GNSO Council leadership to provide an update on the SPS agenda. d.PR Officer Action Items: The PR Officer to provide an update at the December Council meeting. 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 0

Proposed Agenda | GNSO Council Meeting | Thursday, 19 December 2024
by Devan Reed 10 Dec '24

10 Dec '24

Dear all, Please find below the agenda for the GNSO Council Meeting on 19 December 2024 at 21:00 UTC. This is posted on the agenda wiki page<https://community.icann.org/x/E4DyEg>. Thank you! Kind regards, Devan Policy Team Supporting the GNSO GNSO Council Agenda 19 December 2024 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/CICeFw. 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, 19 December 2024 at 21:00 UTC: https://tinyurl.com/ybse6rda 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/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 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 17 October 2024 were posted on 01 November 2024. 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. 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) * GNSO Review of the GAC Communiqué * Recommendations Report for the Expedited Policy Development Process (EPDP) on Internationalized Domain Names (IDNs) Phase 2 * Confirmation of GNSO Empowered Community Representative (Tomslin Samme-NIar) Item 4: COUNCIL VOTE - Empowered Community Approval Action on Fundamental Bylaws Amendments to Article 4 Accountability and Review, 4.2 Reconsideration (10 minutes) Pursuant to Section 25.2(e) of the ICANN Bylaws, the ICANN Board approved Fundamental Bylaws Amendments to Article 4, Sections 4.2 and 4.3<https://itp.cdn.icann.org/en/files/governance/uppdates-to-article-4-icann-g…> of the ICANN Bylaws. The ICANN Board took a series of actions and communications to move forward with the ICANN Grant Program while in some cases, trying to address issues presented by the original language of Recommendation 7, including: * 26 October 2023 resolutions<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> revisiting the Board's prior approval of Recommendation 7 and directing the development of a more general process for the ICANN community to indicate when ICANN's Accountability Mechanisms should not be available; * 21 January 2024 initiation<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> of a Fundamental Bylaws amendment process setting forth the general process for the ICANN community to limit access to ICANN's Accountability Mechanisms; and, * 2 March 2024 letter<https://www.icann.org/files/correspondence/sinha-to-clemente-et-al-02mar24-…> to the CCWG-AP’s Chartering Organizations specifying a proposed change to Recommendation 7 to remove a reference to the “Independent Application Assessment Panel” so that Recommendation 7 could better achieve its goal of preserving auction proceeds for grants instead of funding challenges to decisions on grant applications; and the On 7 August 2024, ICANN opened a Public Comment Forum<https://www.icann.org/en/public-comment/proceeding/proposed-fundamental-byl…> on the updated Fundamental Bylaws Proposal, with the proposed amendments being limited and in line with Recommendation 7. Nine submissions were received, and all commenters were supportive of the proposal as posted for Public Comment. Commenters noted that the updated proposal was better aligned to the intention of Recommendation 7 and was a more appropriate means of implementation than the prior proposal. Concurrently, ICANN finalized confirmation with the Chartering Organizations of the CCWG-AP their support or non-objection to the proposal to update Recommendation 7, including confirmation with the GAC that it too is in a position to support or not object to the updating of Recommendation 7, in light of the Board's acceptance of this alternate path. The Board has formally confirmed its adoption of the updated Recommendation 7 and the respective Fundamental Bylaws Amendments. At ICANN81, ICANN Org held an Empowered Community Approval Action<https://www.icann.org/en/ec/fundamental-bylaws-amendment-to-accountability-…> on Fundamental Bylaws Amendments to Article 4 Accountability and Review, 4.2 Reconsideration.<https://www.icann.org/en/ec/fundamental-bylaws-amendment-to-accountability-…> The Fundamental Bylaws Amendments will only become effective if approved by the Empowered Community using the process set forth at Section 25.2(f)<https://www.icann.org/resources/pages/governance/bylaws-en/#article25> and Annex D<https://www.icann.org/resources/pages/governance/bylaws-en/#annexD>, Article 1 of the ICANN Bylaws. The convening of the Approval Action Community Forum is part of this process. Following the Approval Action Community Forum, the GNSO Stakeholder Groups and Constituencies are asked to provide feedback, opinions or comments on their support for, objection to, or abstention from the Approval Action under consideration. The GNSO Council must decide and inform the EC Administration of its decision within twenty-one (21) days after the expiration of the Community Forum whether to support, object to, or abstain from the Approval Action by affirmative vote of a GNSO Supermajority. A discussion and vote on the Approval Action is scheduled for this GNSO Council meeting. If more time is needed, a placeholder for an email vote will be scheduled to initiate on Monday, 23 December. Here, the Council will vote on the Fundamental Bylaw amendments. 4.1 - Presentation of Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-12-19> (Tomslin Samme-NIar, GNSO Council Vice Chair) 4.2 - Council Discussion 4.3 - Council Vote (voting threshold: Supermajority) Item 5: COUNCIL VOTE - Charter for Policy Development Process on Latin Script Diacritics (15 minutes) On 13 November 2024, the GNSO Council passed a motion<https://gnso.icann.org/en/council/resolutions/2020-current#202405> to initiate a Policy Development Process (PDP) on requesting Latin Script Diacritics. The objective of the Preliminary Issue Report<https://gnso.icann.org/sites/default/files/policy/2024/draft/preliminary-is…> was for ICANN org to assess all relevant issues related to the GNSO Council request, and, following Community Input during the Public Comment<https://www.icann.org/en/public-comment/proceeding/preliminary-issue-report…> phase, to recommend a course of action to the GNSO Council. The PDP will be focused on the circumstance when an ASCII gTLD and the Latin script diacritic version of the gTLD are not variants of each other AND may be found to be visually similar to each other. The issue is theoretically possible for any existing ASCII or Latin script IDN gTLD pairs, and is essentially infinite for future applied-for ASCII or Latin script IDN gTLDs, where diacritics are involved. The Final Issue Report<https://gnso.icann.org/sites/default/files/policy/2024/draft/final-issue-re…> includes a draft charter prepared by ICANN org supporting the GNSO Council. Having discussed the draft charter, the Council determined that edits were needed with respect to, but not limited to, the membership structure. Here, the Council will vote on the updated charter. 5.1 - Presentation of Motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-12-19> (Jennifer Chung) 5.2 - Council Discussion 5.3 - Council Vote (voting threshold: affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House) Item 6: COUNCIL DISCUSSION - EPDP Temporary Specification Phase 1, Recommendation 18 - Urgent Requests (15 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. Here, the Council will discuss the GAC’s proposal and determine next steps. 6.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - Request for Guidance from the New gTLD Subsequent Procedures / IDNs EPDP Phase 1 IRT (10 minutes) The New gTLD Subsequent Procedures (SubPro) PDP provided a recommendation to allow single character gTLDs in the next round, which was expanded upon by the IDNs EPDP Phase 1 Final Report. The IDNs EPDP Phase 1 Final Report put forth important detail and limitations on the SubPro recommendation, prescribing that the single character gTLDs be limited to the Han script and that relevant guidelines must be developed and put in place by the Chinese, Japanese, and Korean (CJK) Generation Panels (GPs). In a public comment<https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-scr…> proceeding, the CJK GPs noted their opposition to moving forward with single character Han script gTLDs. And in a subsequent public comment<https://www.icann.org/en/public-comment/proceeding/second-proceeding-for-pr…> proceeding on relevant Applicant Guidebook (AGB) sections, a number of commenters also expressed their opposition. This opposition was discussed with the IDN Sub-Track, a sub-track to the SubPro IRT, where it was agreed to not move forward with single character Han script gTLDs. That decision was then discussed with the main SubPro IRT, where it was determined that this decision should be shared with the GNSO Council. A write-up was shared with the Council on [date]. Here, the Council will be briefed on the tentative decision from the SubPro IRT and to discuss the appropriate next steps, if any. 7.1 - Introduction of Topic (Anne Aikman-Scalese & Susan Payne, Council co-liaisons to the SubPro IRT) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL UPDATE: EPDP Temporary Specification Phase 1 - 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 on the following questions: 1. Does your group believe that billing contact data was in scope for the EPDP Temp Spec policy development? 2. If yes, does your group believe 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. Here, the Council will discuss the above questions and determine next steps. 8.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: COUNCIL UPDATE - 2025 Council Strategic Planning Session (SPS) (10 minutes) The GNSO Council will hold its annual Strategic Planning Session (SPS) in Washington, DC on 14-15 January 2025. The SPS is a dedicated meeting during which the Council will discuss and identify its priorities and goals for the upcoming year. Council Leadership has been developing the agenda, and has identified, et.al., the following themes for discussion: Overview of the Council’s Role and Remit and the Role of Councilors * Evolution of the Council’s role in managing PDPs, including improvements derived from previous SPS * Review of work for the upcoming year (including targeted review of project management tools) * Consideration of recent projects that did not follow the typical path after Council adoption (e.g., delayed implementation, challenges in implementing recommendations) * Continuous improvement of the GNSO (board readiness, GNSO Standing Committee on Continuous Improvement (SCCI), Five Year Strategic Plan) Here, the Council will receive an update from Leadership and Support Staff on SPS planning and important information to know ahead of the SPS. 9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 9.2 - Council Discussion 9.3 - Next Steps Item 10: DISCUSSION ITEM - Request for Guidance from the Rights Protection Mechanisms (RPMs) PDP IRT on the Scope of Uniform Rapid Suspension (URS) Recommendation 1 (15 minutes) There are currently diverging views within the Implementation Review Team (IRT) concerning the implementation of the Uniform Rapid Suspension System (URS) Final Recommendation 1 in the RPM PDP Phase 1 Final Report. Specifically, there is disagreement regarding the scope of amendments to a complaint filed under the URS after the complainant receives the contact information from the URS Provider. As stated in URS Recommendation 1: The Working Group recommends that URS Rule 3(b), and, where necessary, a URS Provider’s Supplemental Rules be amended to clarify that a Complainant must only be required to insert the publicly-available WHOIS/Registration Data Directory Service (RDDS) data for the domain name(s) at issue in its initial Complaint. Furthermore, the Working Group recommends that URS Procedure paragraph 3.3 be amended to allow the Complainant to update the Complaint within 2-3 calendar days after the URS Provider provides updated registration data related to the disputed domain name(s). The draft language currently proposed by some IRT members to URS Rule 3(b)<https://docs.google.com/document/d/1dC3BIYxnIb2zZks1AOnrUNEkQJCzi8EKaCAbGMP…>, which has sparked disagreement within the IRT, pertains to the text in red below: “Pursuant to URS Procedure Section 3.3, Complainant shall have the opportunity to file an amended Complaint limited to adding additional contact details about the Registrant following disclosure of the relevant contact details of the Respondent.” According to some members of the IRT, the scope of amendments to a complaint should be “limited to adding additional contact details about the Registrant” as this is what was intended by URS Recommendation 1, and as such, this should be stated in the proposed amendment to URS Rule 3(b)(iii). Accordingly, these IRT members believe that the amended filing should be limited to including redacted data about the Registrant in the complaint, as this aligns with the expedited nature of the proceeding. No additional changes or amendments to the complaint should be allowed. However, other IRT members raised concerns about the current text in red, noting that URS Recommendation 1 does not impose a limit on the scope of possible amendments to the complaint. These IRT members pointed out that if new information providing greater clarity to a claim becomes available after the party's identity is revealed, the complainant should be permitted to amend the Complaint to include this information. These IRT members believe that there doesn't seem to be any substantial harm in allowing the complainant to amend the Complaint beyond just putting in the contact details of the registrant. A staff review of meeting transcripts suggests that the PDP Working Group did not discuss either expanding or limiting the scope of URS Recommendation 1. For further details on the PDP IRT and original Working Group discussions, see the background document at https://gnso.icann.org/sites/default/files/policy/2024/draft/staff-summary-…. The IRT has not come to agreement and the next step, per the IRT Principles and Guidelines<https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug…>, is to raise the issue with the GNSO Council liaison. Here, the Council will receive an introduction to the topic from the GNSO Council Liaison to the IRT. 10.1 - Introduction of Topic (Susan Payne, GNSO Council Liaison to the IRT) 10.2 - Council Discussion 10.3 - Next Steps Item 11: COUNCIL DISCUSSION - GNSO Council PR Officer Update (10 minutes) During the GNSO Council Strategic Planning Session (SPS) that was held from 14-16 December 2022, the GNSO Council identified the need to enhance its communication efforts to promote its work and outcomes to a broader audience, as well as to counterbalance negative stories and misinformation about GNSO policy work that seemed to have gained prominence on social media and industry blogs. A GNSO Council small team<https://community.icann.org/display/gnsocouncilmeetings/Communications+Smal…> was formed in April 2023 to develop a strategic communications plan<https://gnso.icann.org/sites/default/files/policy/2024/draft/gnso-council-c…> for the GNSO Council. Within its report, the small team put forward two substantive recommendations for new mechanisms to enhance GNSO Council’s communications practice: 1) appoint a member in the GNSO Council to serve as the “PR officer” to guide / support policy staff in implementing the communications strategy and proposed improvements; and 2) establish a LinkedIn page for the GNSO Council. Following the first recommendation, Lawrence Olawale-Roberts agreed to assume the role of PR Officer. Here, the Council will hear an update from Lawrence Olawale-Roberts on his work in this role. 11.1 - Introduction of Topic (Lawrence Olawale-Roberts, GNSO Council PR Officer) 11.2 - Council Discussion 11.3 - Next Steps Item 12: Any Other Business (5 minutes) 12.1 - GNSO Liaison to the GAC update 12.2 - ICANN82 - funded travel emails were sent out, please action as past deadline _______________________________ 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/ybse6rda.

4 3

Consent Agenda Motions to be approved
by Tomslin Samme-Nlar 10 Dec '24

10 Dec '24

Dear councillors, Please find attached the draft motions for the consent agenda items and their accompanying documentation for your review. Warmly, Tomslin

2 1

ICANN Org input to GNSO Council Accuracy Assignment
by Feodora Hamza 10 Dec '24

10 Dec '24

Sent on behalf of Elena Plexida Dear GNSO Council Members, Please find attached ICANN Org’s input on the accuracy assignment as requested by GNSO Council on 25 October. I also want to acknowledge and apologise for the delay in sharing this input. Thank you for your understanding, and we appreciate your patience as we finalised the details. Best regards, Elena Plexida

1 0

FW: [Ext] NEW: ICANN to Host Webinars on the Draft FY26–30 and FY26 Operating Plan and Budget
by Julie Bisland 09 Dec '24

09 Dec '24

FYI-- From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, December 9, 2024 at 10:03 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: ICANN to Host Webinars on the Draft FY26–30 and FY26 Operating Plan and Budget [https://danh45uab.cc.rs6.net/on.jsp?ca=ad99e2b2-11a8-4cf9-a392-118d96111f50…] Monday, 09 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=001nUR_Ots…> 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: Chair's Blog: November Board Workshop and ICANN81 Recap · NEW: ICANN to Host Webinars on the Draft FY26–30 and FY26 Operating Plan and Budget · 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 · ICANN Webinar Series - Europe: Blocking Ads and Trackers at the Domain Level · Webinar: Improving DNSSEC Validation in Nigeria 🔥 Action Items 🔥 · ICANN82 Community Childcare Grants Program: Apply Now · ICANN Community Excellence Award: Now Accepting Nominations Public Comment · NEW: Public Comment Summary Report: Recommendations for the (de-)selection of IDN ccTLDs and related variants · Proposed Revisions to Community Anti-Harassment Policy · Continuous Improvement Program Framew [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…>ork [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> · IANA 2030 Strategy: Draft PTI Strategic Plan covering 2025 to 2030 Events · These events occur between the dates of 09 December and 16 December 2024. Information Sharing NEW: Chair's Blog: November Board Workshop and ICANN81 Recap ICANN81 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…>, which took place 9–14 November in Istanbul and online, marked the conclusion of ICANN’s annual three-meeting cycle. This meeting provided an opportunity to take stock of the past year, while looking ahead to the next. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> NEW: ICANN to Host Webinars on the Draft FY26–30 and FY26 Operating Plan and Budget Both webinars will present identical information. 17 December 2024 at 17:00–18:30 UTC | Register [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> 18 December 2024 at 3:00–4:30 UTC | Register [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> 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=001nUR_Ots…> 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=001nUR_Ots…> 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=001nUR_Ots…>. 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=001nUR_Ots…>. 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=001nUR_Ots…> 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=001nUR_Ots…> on where to find reliable data. Happy editing! Webinars ICANN Webinar Series - Europe: Blocking Ads and Trackers at the Domain Level In this webinar, Peter Lowe will give a mix of history, technical details, policy, and interesting situations from his past 27 years of running a block list for ads and trackers. Date: Wednesday 11 December 2024 (12:00 - 12:45 UTC) Read more and Register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> Webinar: Improving DNSSEC Validation in Nigeria The objective of the webinar is to promote DNSSEC validation and ensure Nigeria achieves increased awareness by the end of the year and at least 50% DNSSEC validation rate by the first quarter of 2025. Date: Thursday 12 December 2024 Read more and Register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> Action Items 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=001nUR_Ots…>. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> 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=001nUR_Ots…> 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. Public Comment NEW: Public Comment Summary Report: Recommendations for the (de-)selection of IDN ccTLDs and related variants [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> Proposed Revisions to Community Anti-Harassment Policy [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> Open for Submissions: 04 November 2024 Closed for Submissions: 20 December 2024 Continuous Improvement Program Framework [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> Open for Submissions: 21 November 2024 Closed for Submissions: 09 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=001nUR_Ots…> Open for Submissions: 26 November 2024 Closed for Submissions: 29 January 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…>. Events These events occur between the dates of 09 December and 16 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=001nUR_Ots…>. · Connected Caribbean Summit · Global IGF 2024 Volume 6, Issue 92 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…> | Next Issue: Thursday, 12 December 2024 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001nUR_Ots…>

1 0

Motion to Adopt Charter for Latin Diacritics PDP
by jen＠dot.asia 09 Dec '24

09 Dec '24

Dear All, I would like to submit the attached Motion to Adopt Charter for Latin Diacritics PDP. The draft charter (also attached) has been edited per Council discussion in Istanbul. The changes to the draft charter are as follows: * Addition of language referencing Latin RZ LGR (section three: variants) to clarify scope * Addition of the Global Public Interest and the reference to the checklist * Adjustment of the WG membership structure to make it "Open model" Best, Jennifer

3 3

Motion - Empowered Community Approval Action on Fundamental Bylaws Amendments to Article 4 Accountability and Review
by Tomslin Samme-Nlar 09 Dec '24

09 Dec '24

Dear Councilors, As a follow up to my previous email and in preparation for this month's council meeting, please find the above mentioned motion to be discussed and possibly voted upon during our meeting. Warmly, Tomslin

3 2