January 2025 - council - lists.icann.org

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

Jan. 8, 2025

Dear all, Please find below the agenda for the GNSO Council Meeting on 09 January 2025 at 05:00 UTC This is posted on the agenda wiki page<https://community.icann.org/x/dwByG>. Happy New Year! Terri [Happy New Year" Images – Browse 10,379 ...] GNSO Council Agenda 09 January 2025 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/AgBbGQ. This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 15 March 2023. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Thursday, 09 January 2025 at 05:00 UTC: https://tinyurl.com/p69xapak 21:00 Los Angeles (Wednesday); 00:00 Washington DC; 05:00 London; 06:00 Paris; 08:00 Moscow; 16:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (5 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes <https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> (Part 1) Minutes<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> (Part 2) of the GNSO Council Meeting on 13 November 2024 were posted on 02 December 2024. Minutes of the GNSO Council Meeting on 19 December were posted on 30 December 2024 Item 2: Opening Remarks / Review of Projects & Action List (0 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * Confirmation of Standing Selection Committee (SSC) Leadership and Members Item 4: COUNCIL DISCUSSION - Board Readiness Small Team Update (10 minutes) During the 2023 GNSO Council Strategic Planning Session (SPS), the GNSO Council agreed that it should seek to limit the likelihood of the Council approving PDP recommendations that the ICANN Board is ultimately unable to adopt. To that end, the Council discussed the desire to ensure it submits “board-ready policy recommendations” to the Board, to the extent possible. Generally speaking, a policy recommendation is considered board ready when: the recommendation is likely to achieve board adoption, i.e., the recommendation has been approved by a GNSO Supermajority Vote and will most likely be considered by the Board to be in the best interests of ICANN Community and ICANN org. In August 2024, a Council Small Team began meeting to further discuss the topic of board readiness. Specifically, the Small Team was tasked by GNSO Council to: * Develop a survey/questionnaire related to the Board’s rejection/non-adoption of policy recommendations, which may be administered to relevant PDP Chairs, PDP WG members, ICANN org Support Staff, and Board members. (Examples: EPDP Temp Spec Phase 1 and 2; Subsequent Procedures) * Administer the survey/questionnaire and conduct interviews with relevant PDP Chairs, PDP WG members, ICANN org Support Staff, and Board members. * Synthesize the findings from the survey/questionnaire and interviews into a set of findings and develop a set of recommendations intended to inform Council work on improving Board readiness. Over the past few months, the Small Team has been conducting interviews with community members, beginning with EPDP (Temp Spec) Phase 1. Here, the Council will hear an update on the Small Team’s progress. 4.1 - Introduction of Topic (Jennifer Chung, Board Readiness Small Team Member) 4.2 - Council Discussion 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Update on ICANN’s Enforcement of DNS Abuse Mitigation Requirements - Six Month Progress Update (20 minutes) On 8 November 2024, ICANN announced the release of a six-month report, "ICANN's Enforcement of DNS Abuse Mitigation Requirements<https://www.icann.org/en/system/files/files/icann-enforcement-of-dns-abuse-…>," detailing its enforcement actions under the new Domain Name System (DNS) Abuse mitigation requirements. The requirements, which became effective on 5 April 2024, require generic top-level domain registry operators (ROs) and registrars to take mitigation steps to address well-evidenced DNS Abuse, which, for the purposes of ICANN agreements, is limited to malware, botnets, phishing, pharming, and spam used as a vector for delivering the other forms of DNS Abuse. During the initial six months of enforcement, from 5 April to 5 October 2024, ICANN's Contractual Compliance team launched 192 DNS Abuse investigations involving contracted parties. This enforcement effort led to impactful results, including: - Issuing formal Notices of Breach to an RO and a registrar for noncompliance with DNS Abuse mitigation requirements. - Resolving 154 cases that resulted in the suspension of over 2,700 abusive domain names and the disabling of more than 350 phishing websites. The six-month report provides additional context and details about the specific actions taken to keep the ICANN community informed and enhance transparency around the enforcement of DNS Abuse requirements. Here, the Council will hear an update from ICANN Compliance and have an opportunity to ask questions. 5.1 - Introduction of Topic (Leticia Castillo, ICANN org Compliance) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - EPDP Temporary Specification Phase 1, Recommendation 18 - Urgent Requests Trilateral Meeting Preparation (10 minutes) ICANN org convened an Implementation Review Team to assist ICANN in implementing the EPDP on the Temporary Specification Phase 1 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…>, which began meeting in May 2019. ICANN org published the draft Registration Data Policy for public comment<https://www.icann.org/en/public-comment/proceeding/registration-data-consen…> on 24 August 2022. Several commenters expressed dissatisfaction with the implementation of Recommendation 18, specifically around the issue of the response timeline for urgent requests. The relevant portion of Recommendation 18 reads, “A separate timeline of [less than X business days] will considered for the response to ‘Urgent’ Reasonable Disclosure Requests, those Requests for which evidence is supplied to show an immediate need for disclosure [time frame to be finalized and criteria set for Urgent requests during implementation].” On 3 June 2024<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/tsinh…>, the Board wrote to the GNSO Council, noting concerns with the proposed urgent request timeline of business days as not fit for purpose, as truly urgent requests should be responded to within minutes or hours rather than business days. Recognizing this, the Board also noted there is no universal mechanism for registrars to authenticate law enforcement entities. The GNSO Council responded on 29 August 2024<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/dibia…>, agreeing with the Board’s concerns and suggesting a trilateral meeting between the Board, GNSO Council, and GAC to discuss a potential path forward in light of the concerns. On 15 October 2024<https://gac.icann.org/contentMigrated/gac-follow-up-on-urgent-requests-gac-…>, the GAC wrote to the Board, recommending, “[f]or the work on authentication, we would support the establishment of a joint PSWG/CPH task force. For the work on the response time for authenticated requests, we invite the Board and the GNSO Council to identify an expedited procedure for addressing this workstream. We strongly suggest resuming the work of the IRT, which was halted last summer.” A trilateral meeting was held on 4 November 2024<https://community.icann.org/display/gnsocouncilmeetings/Dialogue+with+GAC%2…> and the Board, GAC, and GNSO Council discussed next steps, including potentially resuming discussions with the IRT. The Council discussed this issue in detail during its meeting on 19 December 2024<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>. Here, the Council will prepare for the next trilateral meeting with the ICANN Board, GAC, and GNSO Council. 6.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - EPDP Phase 1 on the Temporary Specification - Implementation Question re: Billing Contact (20 minutes) During the ICANN81 GNSO Council Wrap-Up<https://icann81.sched.com/event/1p2Gu/gnso-council-wrap-up>, Thomas Rickert provided an update regarding the implementation of EPDP Temp Spec Phase 1 recommendations. Thomas is the current GNSO Council Liaison to the EPDP Temp Spec Phase 1 Implementation Review Team (IRT). Thomas noted that the IRT expressed the view that the absence of a reference to billing contact data was a drafting error, and the EPDP Team intended for the collection of billing contact data to be optional and not mandatory. The Registration Data Policy<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> was published on 21 February 2024, and the policy has an effective date of 21 August 2025. The EPDP Phase 1 policy recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> do not reference billing contact data, and the Registration Data Policy<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> also makes no reference to billing contact data. In the interest of transparency, Thomas requested that all Councilors consult with their respective groups to ensure that others are properly informed and agree with the interpretation raised by the registrars within the IRT. Accordingly, Councilors were asked to consult with their groups. The Council discussed this topic during its meeting on 19 December 2024<https://icann.zoom.us/rec/play/wMLdawWw7g5mSvuAbgKmzJKUiRDCBU1sSYKHcwg3nb8O…> and asked for additional background information on the topic. The Council is being asked to consider the questions below: 1. Does the Council confirm billing contact was in scope for the EPDP on the Temp Spec - Phase 1 Team? 2. Does the Council confirm: a. the collection of billing contacts by registrars should continue to be required as per current RAA requirements because EPDP Phase 1, by being silent on this, did not mean to change this requirement, OR b. the collection of billing contacts by registrars should become optional because EPDP Phase 1, by being silent on this, meant to change the RAA requirement? Here, the Council will discuss the above questions and determine next steps. 7.1 - Introduction of Topic (Thomas Rickert, GNSO Council Liaison to the EPDP (Temp Spec) Phase 1 IRT) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL DISCUSSION: Review of Projects List and Action Decision Radar (35 minutes) During the GNSO Council’s 2023 strategic planning session, the Council discussed the topic of how to be an effective manager of the GNSO’s Policy Development Process (PDP). In recognition of the importance of regularly reviewing the Council’s portfolio of work, the Council agreed to the following action item, “During a session at ICANN79, Council to prepare for a careful review of the work captured in the Program Management Tool (PMT) that will conclude or initiate prior to the next AGM, or continue beyond the next AGM[.]” The Council conducted this inaugural review of the Projects List during its Working Session at ICANN79<https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Workin…> on Sunday, 3 March 2024, and continued its review of the Action Decision Radar (“ADR”) during the 16 May 2024 meeting due to time constraints. Here, the Council will continue this practice and review the contents of the Projects List and ADR and discuss next steps in preparation for the upcoming Strategic Planning Session. 8.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Vice-Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: Any Other Business (15 minutes) 9.1 - GNSO Liaison to the ccNSO update 9.2 - ICANN82 - update on planning and draft GNSO schedule 9.3 - SPS reminders 9.4 - Public Comment Opportunities * ICANN FY26–30 Operating & Financial Plan, ICANN/IANA FY26 Op Plans & Budgets<https://www.icann.org/en/public-comment/proceeding/icann-fy2630-operating-f…> * Draft PTI FY26 Operating Plan and Budget<https://www.icann.org/en/public-comment/proceeding/iana-2030-strategy-draft…> 9.5 - IGF/WSIS+20 Small Team _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 05:00 UTC Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 21:00 (Wednesday) San José, Costa Rica (CST) UTC-6 23:00 (Wednesday) New York/Washington DC, USA (EDT) UTC-5 00:00 Buenos Aires, Argentina (ART) UTC-3 02:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:00 Paris, France (CEST) UTC+1 06:00 Moscow, Russia (MSK) UTC+3 08:00 Singapore (SGT) UTC+8 13:00 Melbourne, Australia (AEST) UTC+11 16:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/p69xapak.

1 1

**Starting in 15 minutes | Meeting Invitation | GNSO Council Meeting | Thursday, 09 January 2025
by Terri Agnew Jan. 8, 2025

Jan. 8, 2025

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 09 January 2025 at 05: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/dwByG Check your time zone: https://tinyurl.com/p69xapak 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/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Passcode: mkt7*ULa9b If joining Zoom via Zoom App the following will be required: Webinar ID: 910 4823 5847 Passcode: 9213420189 Or One tap mobile : +13462487799,,91048235847#,,,,*9213420189# US (Houston) +16699006833,,91048235847#,,,,*9213420189# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/a6JrPP2u5 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/MgBbGQ> 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

FYI | GNSO Council Absence Notification Form: Gregory DiBiase
by Terri Agnew Jan. 8, 2025

Jan. 8, 2025

FYI Full Name of Officer: Prudence Malinki Officer Email Address: ppm(a)markmonitor.com Date Prepared: 08 January 2025 GNSO Organization: Registrars Stakeholder Group Officer Position or Title: ExCom Member- GNSO Councilor Name of Absent Councilor: Gregory DiBiase Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Greg is unable to attend the meeting in person, due to exceptional circumstances, and has appointed a proxy to vote of the below motion. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: Confirmation of Standing Selection Committee (SSC) Leadership and Members motion. Date upon which the remedy will expire or terminate: 10 January 2025 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: Prudence Malinki 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

REMINDER | Meeting Invitation | GNSO Council Meeting | Thursday, 09 January 2025
by Terri Agnew Jan. 8, 2025

Jan. 8, 2025

Dear all, The GNSO Council meeting is scheduled on Thursday, 09 January 2025 at 05: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/dwByG Check your time zone: https://tinyurl.com/p69xapak 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/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Passcode: mkt7*ULa9b If joining Zoom via Zoom App the following will be required: Webinar ID: 910 4823 5847 Passcode: 9213420189 Or One tap mobile : +13462487799,,91048235847#,,,,*9213420189# US (Houston) +16699006833,,91048235847#,,,,*9213420189# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/a6JrPP2u5 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/MgBbGQ> 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

Re: Consent Agenda Motion - GNSO Standing Selection Committee Members and Leadership for 2025
by Julie Hedlund Jan. 7, 2025

Jan. 7, 2025

Dear Nacho, Terri, and GNSO Councilors, Following yesterday’s SSC meeting where the members agreed to Karen Day and Segunfunmi Olajide serving second terms as SSC Chair and Vice-Chair respectively, please see the attached updated motion. Kind regards, Julie From: Terri Agnew via council <council(a)icann.org> Reply-To: Terri Agnew <terri.agnew(a)icann.org> Date: Tuesday, December 24, 2024 at 10:32 AM To: Nacho Amadoz <nacho(a)amadoz.cat>, GNSO Council <council(a)gnso.icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [council] Re: Consent Agenda Motion - GNSO Standing Selection Committee Members and Leadership for 2025 Hello Nacho, This has been received and posted on the Jan 2025 motions wiki page: https://community.icann.org/x/BABbGQ Thank you. Kind regards, Terri From: Nacho Amadoz <nacho(a)amadoz.cat> Date: Tuesday, December 24, 2024 at 9:15 AM To: GNSO Council <council(a)gnso.icann.org> Cc: GNSO SECS <gnso-secs(a)icann.org> Subject: Consent Agenda Motion - GNSO Standing Selection Committee Members and Leadership for 2025 Dear Councillors, Please find attached the draft motion for the single consent agenda item - the GNSO Standing Selection Committee (SSC) Members and Leadership for 2025. Merry Christmas and Happy New Year! - when appropriate :D Nacho

3 2

Please read | Upcoming GNSO Council meeting prep | 09 January 2025 at 05:00 UTC
by Terri Agnew Jan. 7, 2025

Jan. 7, 2025

Dear all, A few reminders of prep for the Council meeting on 09 January 2025 at 05: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/dwByG> will be listed on the Document wiki page<https://community.icann.org/x/AgBbGQ> 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 a vote on 09 January 2025. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

For your review: draft response to GAC re: urgent request timeline and authentication
by Caitlin Tubergen Jan. 6, 2025

Jan. 6, 2025

Dear Councilors, During the December 2024 Council meeting, Support Staff captured the following action item: GNSO Council leadership to draft a letter to the GAC for Council review to better understand the GAC proposal from 15 October. The letter will focus on questions regarding the potential authentication methods for law enforcement and to further understand the expected policy work by GAC or other activities relating to urgent requests, in preparation for the meeting with the GAC and the Board. Leadership has developed a draft response for your review: https://docs.google.com/document/d/1jYmI4iiW_UTMMiRl7IrfowUvXVvaeBZv/edit?u…. Please review the draft in advance of the upcoming meeting and ensure the Council’s discussion and concerns are fully captured. You are welcome to provide comments directly in the draft. Thank you. Best regards, Caitlin

3 3

EXTENDED DEADLINE | Call for Volunteers for SCCI | Please Respond by 20 January
by Devan Reed Jan. 6, 2025

Jan. 6, 2025

** GNSO community members who wish to join the Standing Committee should contact the GNSO Secretariat at gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> by Monday, 20 January 2025. Dear Councilors, The Generic Names Supporting Organization (GNSO) Council seeks volunteers to serve on the Standing Committee on Continuous Improvement (SCCI). The SCCI will be in charge of continuous improvement related projects that are focused on the GNSO’s structural, procedural, and process improvements to the Policy Development Process (PDP). This work originally commenced through a pilot under the Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Framework [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> (last updated 29 June 2021), which has now converted to a permanent standing committee following the GNSO Council’s adoption of the charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…>. What This Standing Committee Will Do The SCCI and its dedicated Task Forces (TFs), populated by the Councilors and representatives of each Stakeholder Group (SG) and Constituency (C) (hereafter “SG/C”), will execute a continuous improvement program that aims to improve the GNSO’s process and procedures over time through gradual changes. The goal is to achieve measurable improvements in the efficiency, effectiveness, performance, outcomes, accountability, transparency, and other indicators of quality for the GNSO. Notably, this work affects the GNSO community more broadly and is not limited to that of the Council. Considering that this is a permanent standing committee, the specific scope of work across the varying projects that the SCCI and TFs will execute is not overly prescribed within the charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>, as to avoid frequent edits and subsequent approvals. Previous efforts were initiated by the Council, while other changes were accomplished through Organizational Reviews anchored in Article 4.4. of the ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en#article4.4>. As the ICANN community evolves towards a larger continuous improvement program, the GNSO’s SCCI and its TFs will be heavily involved in these efforts. While broad, GNSO project assignments will be limited to any processes and procedures that would have a GNSO-wide impact only. For avoidance of doubt, all assignments of the SCCI and TFs shall be first approved by the Council. Subsequently, any outcomes of the SCCI and TFs’ project related work will be sent to the Council for their consideration and follow-up actions, if any. More details on the scope of projects can be found in Section II of the charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> and as new projects and/or assignments are distributed and in due course, completed, they will be managed via the GNSO’s Program Management Tool (PMT) Suite<https://community.icann.org/pages/viewpage.action?pageId=150178769>. Who Should Join SCCI is a representative model which shall consist of a total of 21 Members, 2 Board Liaisons, and 9 Observers. All those that join will serve in representative capacity, where applicable, and as such, be responsible for consulting with their respective groups on a regular basis: * A maximum of two members from each SG/C (14) * One Council member from the Registrar Stakeholder Group (RrSG) (1) * One Council member from the Registry Stakeholder Group (RySG) (1) * One Council member from the Commercial Stakeholder Group (CSG) (1) * One Council member from the Non-Commercial Stakeholder Group (NCSG) (1) * One Council NomCom Appointee (NCA) from each house (2) * One Council NomCom Appointee, non-voting (1) * Two GNSO Board Liaisons * One CPH Board seat #13 (1) * One NCPH Board seat #14 (1) * Nine Observers: * One Council Chair (1) * One Chair from each SG/C (8) Members that are not a part of the Council will not have terms. Councilors, Observers, and Liaisons will turn-over naturally as their terms, defined in the ICANN Bylaws, conclude and are replaced by new representatives. However, SG/Cs who nominate members to participate should frequently assess and refresh their designated representatives to ensure active participation. Members must be appointed and/or reconfirmed by the leadership of the appointing SG/C and notification to the SCCI Chair and support staff. How to Join GNSO community members who wish to join the Standing Committee should contact the GNSO Secretariat at gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> by Monday, 6 January 2025. Monday, 20 January 2025. Background For more information and to better prepare for participation on this Standing Committee, please read its charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>, as well as visiting the CCOICI wiki page<https://community.icann.org/display/CCFOICI>. Please do not hesitate to get in touch if you have any questions. Kind regards, Julie H., Berry, and Saewon SCCI Support Staff

1 0

GNSO Call for Volunteers | Latin Script Diacritics Policy Development Process (PDP) Working Group (WG)
by Devan Reed Jan. 6, 2025

Jan. 6, 2025

Dear Councilors, We hope this email finds you well. This is a friendly reminder that the GNSO is currently seeking volunteers<https://community.icann.org/display/soacabout/ICANN+Community+Digest?previe…> to serve on the Latin Script Diacritics Policy Development Process (PDP) Working Group (WG). Simultaneously, the GNSO is accepting Expressions of Interest (EOI) from those volunteers that are willing to serve as the WG Chair to this PDP. The objective of this PDP WG is to determine the limited circumstances in which a base ASCII generic top-level domain (gTLD) and the Latin script diacritic version of the gTLD can be simultaneously delegated. What This PDP WG Will Do The Latin Script Diacritics PDP WG will examine a single issue, seeking the appropriate mechanism in order to allow a single registry operator to simultaneously operate both ASCII gTLD and the Latin script diacritic version of the gTLD in circumstances where the gTLDs are NOT variants of each other. For clarification purposes, this PDP will use the Latin RZ-LGR<https://www.icann.org/sites/default/files/lgr/rz-lgr-5-latin-script-26may22…> as one of the relevant baseline foundational documents when delineating scope. This PDP must understand the work that was completed by the Latin Generation Panel, including the rationale and impact of the various exclusions of Section 3: Variant Sets<https://www.icann.org/sites/default/files/lgr/rz-lgr-5-latin-script-26may22…> within the aforementioned document. Who Should Join The GNSO Council invites interested parties within the GNSO community (i.e., GNSO's Stakeholder Groups and Constituencies), as well as parties from other Supporting Organizations and Advisory Committees to join the PDP WG. The Latin Script Diacritics PDP WG is structured as an Open Model where it will be open to all parties interested in participating. A detailed list of the WG Member skillset can be found here<https://gnso.icann.org/en/announcements/announcement-03jan25-en.htm>. WG Chair The GNSO Council will appoint one (1) qualified, independent, and neutral Chair for the WG. The GNSO Council leadership and the Standing Selection Committee (SSC) leadership will jointly review the responses and will propose a Chair to the GNSO Council for its consideration. A detailed list of the WG Chair’s responsibilities and expectations can be found in the attached EOI. How to Join Community members who wish to join the Latin Script Diacritics PDP WG should contact the GNSO Secretariat at gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> by Monday, 27 January 2025. An EOI (See attached) is requested for the role of Chair. Those who wish to serve as the Chair of the WG should complete the EOI and send it also to the GNSO Secretariat at gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> by Monday, 20 January 2025. Additional information and details about the opportunities can be found here<https://gnso.icann.org/en/announcements/announcement-03jan25-en.htm>. For more information and to better prepare for participation on this PDP WG, please read its charter<https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-charter-…>, as well as the Final Issue Report<https://gnso.icann.org/sites/default/files/policy/2024/draft/final-issue-re…> that was presented to the GNSO Council for the initiation of the PDP<https://gnso.icann.org/en/council/resolutions/2020-current#202411>. Please feel free to share this message with those who may be interested. Thank you. Kind regards, Saewon, John, and Steve on behalf of the GNSO staff support team

1 0

Invite: GNSO Council Meeting
by PolicyCalendar＠icann.org Jan. 6, 2025

Jan. 6, 2025

1 0