Dear all, Please find below the final proposed agenda for the GNSO Council Meeting taking place on Wednesday, 12 2024 at 11:45 UTC for 2 hours This has been posted on the agenda wiki page<https://community.icann.org/x/B4DyEg>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO GNSO Council Agenda 12 June 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/igFkEw. This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-15mar23-en.pdf> 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 Wednesday, 12 June 2024 at 11:45 UTC: https://tinyurl.com/yeykc7fm 04:45 Los Angeles; 07:45 Washington DC; 12:45 London; 13:45 Paris; 14:45 Moscow; 21:0450 Melbourne GNSO Council Meeting Remote Participation: Zoom link to be shared 24 hours in advance 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-council-18apr24-en.pdf> of the GNSO Council Meeting on 18 April 2024 were posted on 03 May 2024. Minutes<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso-council-16may24-en.pdf> of the GNSO Council Meeting on 16 May 2024 were posted on 01 June 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 Council Aspirational Statement Item 4: COUNCIL VOTE - Request for Policy Status Report - Expiration Policies (10 minutes) The GNSO Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the Expired Domain Name Deletion Policy (“EDDP”) and the Expired Registration Recovery Policy (“ERRP”). In November 2020, given concerns about its capacity and no known issues with the policies, the Council agreed to delay the request for the Policy Status Report (PSR) for a period of 24 months. After 24 months had passed, the Council reconsidered whether it was an appropriate time to request a PSR. Before voting whether to further defer the request, the Council agreed that it would be helpful to consult with both registrars and ICANN org to assist in determining whether there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. During its 16 May 2024 meeting<https://icann.zoom.us/rec/play/KhcJ9a0WQIb66_oqrPekZLxdZcrYW409GFcjpzEvfW9KSYNtkR24QKzsxW_oOaqP67U9V6i_UdjTJaCF.Tq-DcBZuMTW-iwse?canPlayFromShare=true&from=share_recording_detail&startTime=1715835711000&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2FwCk-Zmdzc4TuptOTtI9i11IPGjiXQMvS6s4wzmFshGzSI8mNn-wo8DEtZ5SAiV4.WYIV7BTnbXm6-ygQ%3FstartTime%3D1715835711000>, the Council discussed the option of adding the PSR request to ICANN org’s queue of work instead of deferring the request for two years, noting the PSR analysis should be completed but not as an urgent priority. Here, the Council will vote to request ICANN org to deliver a PSR in one (1) year or to confirm that work on the PSR has begun and deliver an updated estimate on when the PSR should be delivered, in one (1) year. 4.1 - Presentation of Motion (Greg DiBiase, GNSO Chair) 4.2 - Council Discussion 4.3 - Council vote (voting threshold: simple majority) Item 5: COUNCIL DISCUSSION - Accuracy Check-in (20 minutes) The Registration Data Accuracy (RDA) Scoping Team was initiated by the GNSO Council in July 2021 per the formation instructions<https://gnso.icann.org/sites/default/files/file/field-file-attach/registration-data-accuracy-scoping-team-formation-instructions-09jul21-en.pdf>. The Scoping Team was tasked with considering a number of accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts before making a recommendation to the GNSO Council on whether any changes are recommended to improve accuracy levels, and, if so, how and by whom these changes would need to be developed (for example, if changes to existing contractual requirements are recommended, a PDP or contractual negotiations may be necessary to effect a change). The Scoping Team completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up<https://mm.icann.org/pipermail/council/2022-September/025950.html> to the Council on 5 September 2022. In its write up, the Scoping Team suggested moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3). On 19 October 2023, ICANN org provided an update<https://mm.icann.org/pipermail/council/2023-October/027397.html> on Registration Data Accuracy efforts, and the Council discussed the update during its 16 November 2023 meeting. During that meeting, some Councilors noted that, barring (i) completion of the Data Processing Agreement, (ii) implementation of the NIS2 directive, or (iii) publication of the Inferential Analysis of Maliciously Registered Domains (INFERMAL) Study, it may not be the appropriate time to reconvene the Accuracy Scoping Team. The Council voted to extend the deferral<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2024-02-15> of the Accuracy Scoping Team’s recommendations by another six months during its meeting on 15 February 2024. During this meeting, the Council agreed to check in on the progress of these items during its June 2024 meeting. Here, the Council will discuss the status of accuracy discussions and consider ICANN org’s proposed next steps for addressing the charter topics and informing further community discussions, factoring in the legal as well as resource limitations that exist. Specifically, ICANN org suggested (1) providing historical data via ICANN’s existing audit program and (2) engaging with contracted parties on current European ccTLD identity verification practices. 5.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - Standing Predictability Implementation Review Team (“SPIRT”) Draft Charter (20 minutes) The GNSO Council enlisted a Drafting Team to develop a draft charter for the SPIRT, which is a standing implementation review team recommended in the New gLTD Subsequent Procedures Final Report. When relevant issues arise during the course of the New gTLD Program that may need to be addressed, the Standing Predictability Implementation Review Team (“SPIRT”) will utilize the Predictability Framework. The GNSO Council shall be responsible for oversight of the SPIRT. In developing the draft charter, the Drafting Team considered elements such as the composition of the SPIRT, how issues are raised to the SPIRT procedurally, the operating principles and decision-making of the SPIRT, et.al. The New gTLD Subsequent Procedures Final Report included an annex[gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf*page=321__;Iw!!PtGJab4!_60ARbHmTCx7Xa-lP-7-1wrOen4B8alKcnpVdGsy6pu5UQt3p-q5TOSmfbUpt-fz-dYVADvoDfPDEkSwADbu4-brdg$> that provides detailed guidance on how the SPIRT should operate. Here, the Council will receive an update on the draft charter. 6.1 - Introduction of Topic (Anne Aikman-Scalese, GNSO Council Liaison) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - ICANN org Implementation Update - Second-Level International Governmental Organizations (IGO) Protections (15 minutes) During its meeting on 5 Mary 2024, the Board passed a resolution<https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-05-05-2024-en#section2.b> accepting the GAC’s advice from ICANN76 to maintain the current moratorium on second-level registrations which match the temporarily-reserved acronyms of those International Governmental Organizations (IGOs) on the list the GAC had submitted to ICANN in 2013, until implementation of the Board-adopted GNSO policy recommendations concerning IGO curative rights is complete. On 23 May 2024, ICANN org provided the current estimated timelines<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/RJ5RZYTJUJNI3NT5Z7VY3EFRS3HOZSLI/> for completing the following projects: (1) implementation of the GNSO’s policy recommendations on IGO curative rights; (2) completion of the development work on a permanent notification system for IGOs and the necessary updating of the current IGO Contact List for this system; and (3) other work necessary to achieve an orderly release of the temporarily-reserved IGO acronyms. Among other matters, ICANN org anticipates coming back to the GNSO Council when forming the planned Implementation Review Team for the policy implementation work, and to subsequently conduct early engagement with you and the community prior to launching the permanent notification system and releasing the reserved IGO acronyms. Here, the Council will have an opportunity to discuss the draft timelines and ask questions. 7.1 - Introduction of Topic (Tomslin Samme-Nlar, GNSO Council Chair) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL UPDATE - Update on the Internet Governance Forum Support Association (“IGFSA”) (10 minutes) The Internet Governance Forum Support Association<http://www.igfsa.org> is an independent membership association established in September 2014 to support the United Nations Internet Governance Forum (IGF) and to provide financial and other support for National and Regional IGFs (NRIs) around the world. Here, the IGFSA will provide an overview of its mission and recent work to the Council. 8.1 - Introduction of Topic (Chris Mondini, Managing Director, VP Stakeholder Engagement, Europe ICANN org) 8.2 - Council Discussion 8.3 - Next Steps Item 9: COUNCIL DISCUSSION: Updated Work from Council Strategic Planning Session (“SPS”) (20 minutes) During its most recent strategic planning session, the GNSO Council discussed its role as manager of the policy development process (PDP), and, to that end, it reviewed several stages of the PDP and discussed where improvements could be made. Among others, the Council discussed the GNSO Council Liaison to PDP Working Groups and Implementation Review Teams, the public comment period, and the Recommendations Reports and agreed to the following action items: Council Liaisons to PDP Working Groups Action Item 2.1: Staff to catalog all resources regarding the role of Council liaison to GNSO WGs. Action Item 2.2: Staff to investigate whether the latest version of the GNSO Council Liaison to GNSO WGs – Role Description is up-to-date and if not, update. Action Item 2.3: Once action items 2.1 and 2.2 are complete, Council to discuss whether gaps exist and changes are needed. Recommendations Reports Outcome 5: Recommendation Report format should be reviewed and if possible, amended in a manner that eliminates potential inconsistencies with the WG’s Final Report. Action Item 5.1: Staff to investigate origins of the format for Recommendation Reports and understand the process of making edits. Action Item 5.2: Assuming edits are feasible, staff to propose edits (and Council to review) to meet the objectives captured in Outcome 4. Public Comment Review Outcome 9: Some Councilors expressed concerns about how public comments are considered by PDPs. Action Item 9: Staff to document existing processes and if applicable, propose additional mechanisms to better ensure that commenters understand how their comments were considered by the WG. Council to then review staff outputs and amend as necessary. Here, the Council will receive updates on SPS actions items. 9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 9.2 - Council Discussion 9.3 - Next Steps Item 10: Any Other Business (15 minutes) 10.1 - ccNSO Liaison update (tentative) * Joint Meeting: ccNSO & GNSO Councils<https://community.icann.org/x/PgMZEw> on 11 July 2024 10.2 - PPSAI Call for Volunteers 10.3 - Open Mic _______________________________ 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-procedu... References for Coordinated Universal Time of 11:45 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-7 04:45 San José, Costa Rica (CST) UTC-6 05:45 New York/Washington DC, USA (EDT) UTC-4 07:45 Buenos Aires, Argentina (ART) UTC-3 08:45 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 12:45 Paris, France (CEST) UTC+2 13:45 Moscow, Russia (MSK) UTC+3 14:45 Singapore (SGT) UTC+8 19:45 Melbourne, Australia (AEST) UTC+10 21:45 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/yeykc7fm