Hi Susan, Thank you for this, we will get this added to the 21 September agenda (and below). As a reminder, Leadership uses this anticipated topics for upcoming council meetings planning doc<https://docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0oi...> for meeting topics and councilors are encouraged to add topics to it at any time. All the best, Terri From: Susan Payne <susan.payne@comlaude.com> Date: Monday, September 11, 2023 at 1:47 PM To: Terri Agnew <terri.agnew@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, "liaison6c@gnso.icann.org" <liaison6c@gnso.icann.org> Subject: [Ext] RE: Proposed Agenda | GNSO Council Meeting | Thursday, 21 September 2023 at 21:00 UTC Terri would it be possible to add “IGO next steps” as another AOB please. Attaching my email from last month as background. Thanks Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01D9E4BB.5FE87F30][comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!-9Sdg_wAB89BtwR...> Follow us on Linkedin [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_...> and YouTube [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_...> From: council <council-bounces@gnso.icann.org> On Behalf Of Terri Agnew via council Sent: Monday, September 11, 2023 2:45 PM To: council@gnso.icann.org; liaison6c@gnso.icann.org Cc: gnso-secs@icann.org Subject: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 21 September 2023 at 21:00 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting taking place on Thursday, 21 September 2023 at 21:00 UTC for 2 hours. This has been posted on the agenda wiki page<https://community.icann.org/x/r4XxDg>. Thank you. Kind regards, Terri ************* 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/rIXxDg This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> v3.5, updated on 24 October 2019. 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, 21 September 2023 at 21:00 UTC: https://tinyurl.com/3h2a9edd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3h2a9edd__;!!PtGJab4!-9Sdg_wA...>. 14:00 Los Angeles; 17:00 Washington DC; 22:00 London; 23:00 Paris; 00:00 Moscow (Friday); 07:00 Melbourne (Friday) GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97891627902?pwd=RURCTitiN...> 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 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> of the GNSO Council meeting on 20 July were posted on 06 August 2023. Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> of the GNSO Council meeting on 24 August 2023 were posted on 09 September 2023. 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 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/project__;!!PtG...> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (0 minutes) Item 4: COUNCIL VOTE - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Recommendations Report on Review of the Statement of Interest (SOI) Requirements (10 minutes) The GNSO Framework for Continuous Improvement Pilot was initiated in June 2021 to determine whether the framework, as outlined here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/drafts/continuous-impro...>, could serve as an approach for dealing with the various projects that are focused on improvements to GNSO processes and procedures. The CCOICI tasked<https://community.icann.org/x/NAAiCw> the GNSO Statement of Interest (SOI) Task Force to address the following questions: 1. Is the original objective of the SOI, as stated in the BGC WG Report, still valid? If not, why not and what should the current objective be? 2. Based on the response to question 1), is the requested information to be provided as part of the SOI still fit for purpose? If not, why not, and what would need to be changed to make it fit for purpose? 3. Are there any further measures that should be considered from an enforcement / escalation perspective, in addition or instead of those already included in the requirements? The Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) submitted to the GNSO Council for consideration its Recommendations Report following its review of the Recommendations Report submitted to the CCOICI by the GNSO Statement of Interest Task Force based on their review of the GNSO Statement of Interest (SOI) Requirements as well as their review of the input received in response to the public comment forum. During the meeting in August 2023, Manju Chen presented an overview of the CCOICI Recommendations Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> on the SOI Requirements Here, the Council will vote on the CCOICI Recommendations Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> on the SOI Requirements. 4.1 – Presentation of motion<https://community.icann.org/x/sYXxDg> (Manju Chen, CCOICI Chair) 4.2 – Council discussion 4.3 – Council Vote (voting threshold: simple majority) Item 5: COUNCIL VOTE - Charter for Registration Data Request Service (RDRS) Standing Committee to help inform the next steps on the SSAD policy recommendations (10 minutes) On 13 September 2022, ICANN org published a WHOIS Disclosure System (System) Design Paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-p...> based on the "proof of concept" approach outlined by the Small Team. The GNSO Council informed the ICANN Board on 17 November 2022<https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-17nov22-...> that the Council unanimously accepted the Addendum to the Preliminary Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> (Addendum) prepared by the Small Team and supported the implementation of the System. On 27 February 2023, the ICANN Board directed<https://www.icann.org/en/board-activities-and-meetings/materials/approved-re...> ICANN org to “proceed to develop and launch the System as soon as possible”. The ICANN Board also “directed ICANN org to continue to engage with the Phase 2 Small Team throughout the development and operation of the System, and ensure periodic publication of the collected usage data, once operational". On 15 March 2023, GNSO Council instructed [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> the small team to continue working with ICANN org on the implementation of the System as well as “provide the Council with a recommendation on the approach and format through which, following implementation of the system, data should be reviewed and analyzed to help inform subsequent decisions on how to proceed with the SSAD recommendations”. On 8 September, the small team shared with the GNSO Council the proposed charter [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1IFmCY1xEtWy7I...> for a Registration Data Request Service (RDRS) Standing Committee to help inform the next steps on the SSAD policy recommendations. Here, the Council will vote on the charter for the Registration Data Request Service (RDRS) Standing Committee 5.1 - Presentation of motion<https://community.icann.org/x/sYXxDg> (Sebastien Ducos, Chair of EPDP Phase 2 Small Team) 5.2 - Council Discussion 5.3 - Council Vote (voting threshold: simple majority) Item 6: COUNCIL VOTE - SubPro Clarifying Statement on Registry Voluntary Commitments (RVCs) and Public Interest Commitments (PICs) (20 minutes) During its informal session at ICANN76 and the subsequent Council meeting, the Council discussed and agreed [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> to task a small team of interested councilors to review the recommendations that the Board placed in a pending status and suggest to the full Council how the underlying concerns that caused the pending status can be best addressed (i.e., a limited triage exercise). Since ICANN76, the Council SubPro Small Team has met several times and has completed a comprehensive review of the issues chart, with Board member input on why the Board placed specific recommendations into a pending status. The Council discussed the main output of that triage effort, the proposed paths forward for each pending recommendation, during an Extraordinary Meeting on 4 May. During that meeting, the Council agreed to further task the small team with taking interim steps (e.g., provision of clarifying information, developing speaking points) in order to support the Council’s dialogue with the ICANN Board on 22 May<https://community.icann.org/pages/viewpage.action?pageId=240617931>. The Council debriefed after the dialogue with the ICANN Board and discussed next steps. During the ICANN77 Day 0 Session, the Council heard from the members of the Board regarding the Board’s views on potential “landing spots” on the pending recommendations. During its August meeting, the Council approved a clarifying statement for a number of pending recommendations, though it removed text in the Clarifying Statement relating to the enforceability of PICs and RVCs and holding this over to a future Clarifying Statement, pending further feedback from the ICANN Board. Additional feedback was delivered to the small team and subsequently considered. Here, the Council will vote on the clarifying statement relating to the enforceability of PICs and RVCs. 6.1 – Presentation of motion<https://community.icann.org/x/sYXxDg> (Paul McGrady, SubPro Small Team Chair) 6.2 – Council discussion 6.3 - Council Vote (voting threshold: simple majority) Item 7: COUNCIL DISCUSSION - SubPro Small Team Updated Assignment Form (20 minutes) During its informal session at ICANN76 and the subsequent Council meeting, the Council discussed and agreed [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> to task a small team of interested councilors to review the recommendations that the Board placed in a pending status and suggest to the full Council how the underlying concerns that caused the pending status can be best addressed (i.e., a limited triage exercise). Since ICANN76, the Council SubPro Small Team has met several times and has completed a comprehensive review of the issues chart, with Board member input on why the Board placed specific recommendations into a pending status. The Council discussed the main output of that triage effort, the proposed paths forward for each pending recommendation, during an Extraordinary Meeting on 4 May. During that meeting, the Council agreed to further task the small team with taking interim steps (e.g., provision of clarifying information, developing speaking points) in order to support the Council’s dialogue with the ICANN Board on 22 May<https://community.icann.org/pages/viewpage.action?pageId=240617931>. The Council debriefed after the dialogue with the ICANN Board and discussed next steps. During the ICANN77 Day 0 Session, the Council heard from the members of the Board regarding the Board’s views on potential “landing spots” on the pending recommendations. As the triage exercise is now complete, the Small Team’s assignment form has been updated to reflect the updated assignment regarding how the non-adopted recommendations should be handled, e.g., supplemental recommendation, Section 16, etc. Here, the Council will hear an update on the proposed updated assignment form. 7.1 - Introduction of Topic (Paul McGrady, Chair of SubPro Small Team) 7.2 - Council Discussion 7.3 - Next Steps Item 8: ICANN78 Planning (15 minutes) During ICANN78, the GNSO Council has the following meetings and events scheduled: Saturday, 21 October * 13:15-14:30 - Joint At-Large & GNSO meeting * 15:00-16:00 - GNSO Council small team - SubPro Pending Recommendations * 16:30-18:00 - GNSO celebration session (16:30-17:30 event & 17:30-18:00 cocktail) * Time TBD: GNSO Council dinner Sunday, 22 October * 09:00-10:00 - GNSO Working Session 1 of 2 * 10:30-12:00 - GNSO Working Session 2 of 2 * 13:15-14:30 - Joint ccNSO & GNSO meeting Monday, 23 October * 15:00-16:00 - Joint GAC GNSO meeting Tuesday, 24 October * 17:45-18:45 - GNSO Council Informal meeting [closed] Wednesday, 25 October * 09:00-10:00 - ICANN Board & GNSO Council * 13:00-15:00- GNSO Council Meeting * 15:15-15:45 – GNSO Council Admin Thursday, 26 October * 13:15-14:30 – GNSO Council Wrap-up Here, the Council will receive an overview of the current block schedule and plan for its in-person meetings. 8.1 - Introduction of Topic (Greg DiBiase, Council Vice Chair) 8.2 - Council Discussion 8.3 - Next Steps Item 9: Cross Community Working Group - Auction Proceeds Response (20 minutes) On 17 July 2023, Xavier Calvez sent a written update<https://mm.icann.org/pipermail/council/2023-August/027220.html> on the progress of ICANN org’s implementation of the Cross Community Working Group’s - Auction Proceeds (CCWG-AP) Final Report. The update noted the implementation work will result in the launch of the ICANN Grant Program at the end of the first quarter of 2024. The program will distribute the 2012 New gTLD Program [newgtlds.icann.org]<https://urldefense.com/v3/__https:/newgtlds.icann.org/en/about/program__;!!P...> Auction Proceeds in line with the recommendations, as adopted by the ICANN Board<https://www.icann.org/en/board-activities-and-meetings/materials/approved-re...> in June 2022. As implementation progresses, ICANN org has considered organizing a meeting, with former members of the CCWG-AP, should any of the former members be interested and available to participate. This will help to ensure that implementation preserves the intent of the group’s recommendations. Here, the Council will discuss a response to this message. Specifically, the Council is asked to consider if it is comfortable with former CCWG-AP members engaging in a conversation with ICANN org or whether the discussion should be conducted differently . 9.1 - Introduction of Topic (John McElwaine, Council Vice Chair) 9.2 - Council Discussion 9.3 - Next Steps Item 10: ANY OTHER BUSINESS (20 minutes) 10.1 GNSO Prep Week Webinar - Tuesday - 10 October at 13:00 UTC 10.2 Planning for GNSO Council Strategic Planning Session 10.3 ccNSO [& GAC] Liaison updates 10.4 Review of CCOICI pilot 10.5 IGO next steps _______________________________ 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... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> References for Coordinated Universal Time of 21:00 UTC Local time between March and October in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ [timeanddate.com]<https://urldefense.com/v3/__https:/www.timeanddate.com/time/change/__;!!PtGJ...> for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 14:00 San José, Costa Rica (CDT) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CEST) UTC+2 23:00 Moscow, Russia (MSK) UTC+3 00:00 (Friday) Singapore (SGT) UTC+8 05:00 (Friday) Melbourne, Australia (AEST) UTC+10 07:00 ---------------------------------------------------------------------------- US and Canada: DST starts on Sunday 12 March 2023 (with exceptions) European countries: DST starts on Sunday 26 March 2023 (with exceptions) DST ends on Sunday 29 October 2023 for most European countries DST ends on Sunday 05 November 2023 for most of the US and Canada Some parts of Australia: DST ends on Sunday 02 April 2023 Some parts of Australia: DST starts on Sunday 01 October 2023 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.com/v3/__http:/www.timeanddate.com/__;!!PtGJab4!-9Sdg_wAB...> and https://tinyurl.com/3h2a9edd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3h2a9edd__;!!PtGJab4!-9Sdg_wA...>. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!-9Sdg_wAB89BtwR...>