December 2024 - council - lists.icann.org

FYI | FW: GNSO Council Absence Notification Form: Bruna Martins
by Terri Agnew Dec. 19, 2024

Dec. 19, 2024

Full Name of Officer: Rafik Dammak Officer Email Address: Rafik.dammak(a)gmail.com Date Prepared: 19 December 2024 GNSO Organization: Non-Commercial Stakeholder Group Officer Position or Title: Chair Name of Absent Councilor: Bruna Martins Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Unable to join this month council call since she is attending IGF meeting Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: For all matters in council meeting Date upon which the remedy will expire or terminate: 20 December 2024 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). Yes Full Name of GNSO Councilor Serving as Voting Proxy: Farzaneh Badii By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy<https://www.icann.org/privacy/policy>, and agree to abide by the website Terms of Service<https://www.icann.org/privacy/tos>. I Agree

1 0

Fellowship Mentor and Selection Committee
by Julie Bisland Dec. 18, 2024

Dec. 18, 2024

Dear Councilors, We hope this email finds you well. This is a friendly reminder that the GNSO is currently accepting Expressions of Interest from individuals interested in serving as: 1) a Fellowship Program mentor; and 2) as a member of the Fellowship Program Selection Committee. 1. Important information regarding the Fellowship Program Mentor includes: • 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. • Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN84 (ICANN84 - ICANN86 inclusive). • Mentors are expected to follow Fellowship Program guidelines<https://www.icann.org/resources/pages/fellowship-mentoring-guidelines-2018-…> 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). 1. Important information regarding the Fellowship Selection Committee Members: • Members should plan on a time commitment of approximately 30-40 hours over four (4) to five (5) weeks for each Public Meeting. • Selection Committee members will typically serve for two (2) years, which encompasses six (6) 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. • Mentors cannot serve on the Selection Committee while serving their terms as mentors. The GNSO may nominate one individual for each role. Individual self-nominations will not be considered. Additional information and details about the opportunities can be found here<https://gnso.icann.org/en/announcements/announcement-18dec24-en.htm> for the Fellowship Program mentor, and here<https://gnso.icann.org/en/announcements/announcement-2-18dec24-en.htm> for the Fellowship Program Selection Committee. Important links related to the Fellowship Program<https://www.icann.org/fellowshipprogram> can also be found here<https://www.icann.org/fellowshipprogram/#important-links>. Interested individuals should apply by filling out the Expression of Interest (see attached for each EOI form) and submitting it to gnso-secs(a)icann.org by 9 January 2025 at 23:59 UTC. Please feel free to share this message with those who may be interested. Thank you. Kind regards, Julie H. and Saewon, on behalf of the GNSO staff support team

1 0

council@icann.org: Please confirm to Continue.
by icann.org Administrator Dec. 18, 2024

Dec. 18, 2024

1 0

REMINDER | Meeting Invitation | GNSO Council Meeting | Thursday, 19 December 2024
by Terri Agnew Dec. 18, 2024

Dec. 18, 2024

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

2nd update to agenda | Proposed Agenda | GNSO Council Meeting | Thursday, 19 December 2024
by Terri Agnew Dec. 17, 2024

Dec. 17, 2024

**Updated below. Adjusted meeting description for Item 7: COUNCIL DISCUSSION - Request for Guidance from the New gTLD Subsequent Procedures / IDNs EPDP Phase 1 IRT (10 minutes) Thank you. Kind regards, Terri From: Terri Agnew <terri.agnew(a)icann.org> Date: Tuesday, December 10, 2024 at 3:52 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: UPDATED Agenda | Proposed Agenda | GNSO Council Meeting | Thursday, 19 December 2024 **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 Recommendation 25.4 (approved by the ICANN Board) to allow single character gTLDs for ideographic scripts in the next round, provided that they do not introduce confusion risks that rise above commonplace similarities. The IDNs EPDP Phase 1 Final Report put forth important additional detail and limitations on 25.4, prescribing that the single character gTLDs be limited to the Han script and that applications must not be accepted until relevant guidelines are developed and put in place by the Chinese, Japanese, and Korean (CJK) Generation Panels (GPs). Alternatively, the IDN EPDP concluded that if the CJK GPs determine that additional guidelines beyond the RZ-LGR are not needed, then the single character applications should proceed. The matter was put out for public comment by the CJK Generation Panels. Although the CJK GPs stated<https://www.icann.org/en/system/files/files/proposed-han-script-single-char…> that the work done in the Root Zone Label Generation Rules (RZ-LGRs<https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en>) sufficiently addresses the concerns around the risk of confusion for single character Han script gTLDs, the majority of the public comments<https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-scr…> on the CJK GPs’ statements opposed moving forward. Commenters from the Chinese community expressed concerns about the lack of alignment with China’s linguistic laws and regulations, the complexities of Chinese character ideographs, and end-user confusion due to multiple meanings of manysingle characters. One such comment received from a co-Chair of the CGP argues that the CGP should not be and was not involved in "risk of confusion" policy considerations related to single Han characters as TLDs. Many of the comments call for further community work prior to proceeding. Similar concerns were received through the public comment<https://www.icann.org/en/public-comment/proceeding/second-proceeding-for-pr…> on the relevant draft AGB sections. This public comment was discussed with the Sub Pro IRT IDN Sub-Track which referred the matter to the main SubPro IRT. The main SubPro IRT was asked by ICANN staff whether Recommendation 25.4 should be modified as not implementable or whether the issue should be reviewed with Council for possible further work. It was agreed that the Liaisons should raise this with Council for direction on next steps. The attached background document prepared by Lars Hoffman was shared with the Council on December 9. Councillors are encouraged to review this write-up prior to the meeting. Here, the Council will be briefed on the options for next steps, including a recommendation from the IRT Liaisons to refer this complex matter to a GNSO Guidance Process to determine the guidance necessary to allow Han single characters to proceed, with an acknowledgement that the GGP could well determine that Recommendation 25.4 and IDN EPDP recommendation 3.17 as approved may not be implementable. Due to time constraints, and the fact that both the SubPro and IDNs recommendations were conditional, Liaisons believe that the recommended GGP process should not hold up the next round. 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

Please read | Upcoming GNSO Council meeting prep | 19 December 2024 at 21:00 UTC
by Terri Agnew Dec. 17, 2024

Dec. 17, 2024

Dear all, A few reminders of prep for the Council meeting on 19 December 2024 at 21:00 UTC. 1. Have question on prep materials for this meeting? Check out the Council Preparatory Materials Cheat Sheet found here<https://docs.google.com/document/d/1lQ9fqEjD-inZWpni7tx_EKij6_19oGvi/edit?u…>. 1. Question of the month and answer found on materials cheat sheet: What should I review in preparation for a Council meeting? 1. All documents mentioned on the Council agenda<https://community.icann.org/x/E4DyEg> will be listed on the Document wiki page<https://community.icann.org/x/CICeFw> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio<https://community.icann.org/pages/viewpage.action?pageId=150178769>, in particular the Action Decision Radar<https://community.icann.org/x/14vzC> and the Project List<https://community.icann.org/x/1YvzC> . 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. We do have several votes for the December 2024 meeting. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

FW: [Ext] NEW: The Adventure Begins
by Julie Bisland Dec. 16, 2024

Dec. 16, 2024

FYI--- From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, December 16, 2024 at 10:02 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: The Adventure Begins [https://danh45uab.cc.rs6.net/on.jsp?ca=ed7271d2-7e01-465a-8aff-b85468d9b8a6…] Monday, 16 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=001_ajFXQe…> 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: The Adventure Begins · NEW: Save the Date: ICANN to Host 2025 Middle East DNS Forum in Bahrain · NEW: Approved Resolutions | Special Meeting of the ICANN Board | 11 December 2024 · 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 to Host Webinars on the Draft FY26–30 and FY26 Operating Plan and Budget 🔥 Action Items 🔥 · ONE WEEK FROM 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 · FRIDAY: 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=001_ajFXQe…>ork [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…> · 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. 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=001_ajFXQe…>. 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=001_ajFXQe…> Information Sharing NEW: The Adventure Begins Please read Kurtis Lindqvist's first blog as ICANN CEO here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…>. NEW: Save the Date: ICANN to Host 2025 Middle East DNS Forum in Bahrain The gathering will take place on 29 and 30 April 2025 in Bahrain and will be held as a hybrid event. The Middle East DNS Forum continues to serve as a unique platform for fostering collaboration, exchanging ideas, and learning about the latest advancements in DNS technologies and policies. Read more [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…>. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…> NEW: Approved Resolutions | Special Meeting of the ICANN Board | 11 December 2024 Please find the Approved Resolutions from the 11 December 2024 Special Meeting of the ICANN Board here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…>. 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=001_ajFXQe…> 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=001_ajFXQe…> 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=001_ajFXQe…>. 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=001_ajFXQe…>. 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=001_ajFXQe…> 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=001_ajFXQe…> on where to find reliable data. Happy editing! Webinars 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=001_ajFXQe…> 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=001_ajFXQe…> Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…> Action Items ONE WEEK FROM 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=001_ajFXQe…> 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=001_ajFXQe…>. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…> 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=001_ajFXQe…> Public Comment FRIDAY: Proposed Revisions to Community Anti-Harassment Policy [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…> 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=001_ajFXQe…> 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=001_ajFXQe…> 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=001_ajFXQe…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…>. 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=001_ajFXQe…>. · NEW: ICANN's Open Forum at IGF24 · Connected Caribbean Summit · Global IGF 2024 Volume 6, Issue 94 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…> | Next Issue: Thursday, 19 December 2024 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001_ajFXQe…>

1 0

council@icann.org: Please confirm to Continue.
by icann.org Administrator Dec. 16, 2024

Dec. 16, 2024

1 0

Fwd: [ECAdmin] Initiation of Approval Action Decision Period
by Tomslin Samme-Nlar Dec. 15, 2024

Dec. 15, 2024

Hi Councilors, Please see below email regarding the Today, the official expiration of the Approval Action Community Forum Period, as well as the initiation of the 21-day Approval Action Decision Period. Warmly, Tomslin ---------- Forwarded message --------- From: Christian Wheeler via ECAdmin <ecadmin(a)icann.org> Date: Wed, 11 Dec 2024, 19:24 Subject: [ECAdmin] Initiation of Approval Action Decision Period To: ecadmin(a)icann.org <ecadmin(a)icann.org> Dear Empowered Community Administration representatives, This message is regarding the Empowered Community’s ongoing Approval Action <https://www.icann.org/en/ec/fundamental-bylaws-amendment-to-accountability-…> for the Fundamental Bylaws Amendment to Accountability Mechanisms. Today, 11 December 2024, marks the official expiration of the Approval Action Community Forum Period, as well as the initiation of the 21-day *Approval Action Decision Period*. You may refer to Article 1.2, Annex D of the ICANN Bylaws for details on the Empowered Community Approval Process: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD. Under normal circumstances, this Approval Action Decision Period would expire on Wednesday, 1 January 2025, however because this Decision Period is scheduled to conclude over a widely observed holiday period, ICANN has agreed to an extension of the expiration until *Wednesday, 8 January 2025 at 23:59 PST*. Before the Approval Action Decision Period expires on 8 January, each Decisional Participant has the responsibility to inform the EC Administration in writing as to whether it supports or objects to the Approval Action; or it has determined to abstain from the matter. If a Decisional Participant does not inform the EC Administration in time, it shall be deemed to have abstained. To approve an Approval Action, and for these Fundamental Bylaws Amendments to be effective, the following is required: - At least 3 Decisional Participants supporting the Approval Action, and - No more than 1 Decisional Participant objecting to the Approval Action We will be happy to assist with any questions you may have, please just let us know. Best regards, Christian Wheeler (on behalf of the staff supporting Empowered Community Administration) _______________________________________________ ECAdmin mailing list -- ecadmin(a)icann.org To unsubscribe send an email to ecadmin-leave(a)icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Motion to Adopt Charter for Latin Diacritics PDP
by jen＠dot.asia Dec. 15, 2024

Dec. 15, 2024

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

5 8