Dear All, Regarding Item 8 and our dialogue with GDS of next week's council meeting agenda, feel free to share questions you may have in advance. They will certainly address the specifics of the EPDP ph1 IRT and the ODPs but would also welcome some discussion on broader aspects such as process improvements and potential engagement with Council for this. Regards, Philippe Orange Restricted From: council <council-bounces@gnso.icann.org> On Behalf Of Terri Agnew via council Sent: Friday, February 25, 2022 10:05 PM To: council@gnso.icann.org Cc: gnso-secs@icann.org Subject: [council] Proposed Agenda | GNSO Council Meeting | Wednesday, 09 March 2022 at 16:30 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on Wednesday, 09 March 2022 at 16:30 UTC for 2 hours. Make sure all have registered for ICANN73 Participation Links Zoom participation links will be published 24 hours before the session starts. For more information on how to participate, visit: https://73.schedule.icann.org/attend Draft GNSO Council Agenda 09 March 2022 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/09MGCw. This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedu...> 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 held 16:30 UTC (12:30 local time): https://tinyurl.com/yck4ykvp 08:30 Los Angeles; 11:30 Washington DC; 16:30 London; 17:30 Paris; 19:30 Moscow; (Thursday) 03:30 Melbourne GNSO Council Meeting Remote Participation: (See ICANN73 schedule for Zoom URL link) 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 (10 mins) 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/2022/minutes/minutes-gnso-...> of the GNSO Council meeting on 20 January 2022 were posted on 03 February 2022. Minutes of the GNSO Council meeting on 17 February 2022 were posted on 07 March 2022. Item 2: Opening Remarks / Review of Projects & Action List (5 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) * Reappointment of Becky Burr to seat 13 on the ICANN Board. The CPH has reappointed Becky Burr for Seat 13 on the ICANN Board of Directors. This agenda item is intended to acknowledge the selection and confirm that the notification process as outlined in Section 7.25 of the ICANN Bylaws will be completed subsequently. * Motion<https://community.icann.org/x/2NMGCw> to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items. Item 4: COUNCIL DISCUSSION - Nominating Committee Outreach Subcommittee Outreach (10 minutes) The Nominating Committee (NomCom) initiated<https://www.icann.org/en/announcements/details/apply-now-for-icann-and-pti-l...> its application process on 15 December 2021. For this cycle, the NomCom will be selecting one member of the GNSO Council, a non-voting appointee. The GNSO Council provided updated criteria<https://www.icann.org/resources/pages/nomcom2022-positions-2021-12-15-en#gns...> to the NomCom to be used in the recruitment and selection processes. Here, the NomCom Outreach Subcommittee will provide information about the NomCom panel, about the position being filled for the GNSO Council, and answer questions that the Council might have. 4.1 - Introduction of topic (NomCom Outreach Subcommittee) 4.2 - Council discussion 4.3 - Next steps Item 5: COUNCIL DISCUSSION - Small Team Reviewing the System for Standardized Access/Disclosure (SSAD) Operational Design Assessment / Debrief From Meeting With the ICANN Board (25 minutes) On 25 January 2022, the Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> (ODA), the final output of the System for Standardized Access/ Disclosure (SSAD) to Nonpublic generic Top-Level Domain Registration Data Operational Design Phase (ODP) was published. Just prior to the publication of the ODA, the ICANN Board sent a letter<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/botter...> to the GNSO Council, outlining some of its concerns as well as questions it hoped to receive input on from the Council. The Council agreed to establish a small team to review the ODA in detail, focusing on the following elements as identified in the assignment form<https://community.icann.org/download/attachments/178587048/Small%20Team%20As...>: * Whether the ODA has correctly interpreted the intent of the SSAD recommendations in the proposed implementation; * Whether the ODA has overlooked any key aspects of the SSAD recommendations that should be factored in by the ICANN Board when it considers the recommendations; * Its view on the concerns identified by the ICANN Board and potential options that could be considered, either in the form of changes to the proposed implementation or the policy recommendations themselves, to address these concerns(note, these are expected to be high level suggestions at this stage); * Any other aspects that help inform the Council's deliberations and consultation with the ICANN Board. The GNSO Council will have met with the ICANN Board on 8 March, just prior to the March Council meeting, and will have discussed the ODA and the efforts of the small team with the Board. Here, the Council will receive an update on the status of the small team and hold a debrief from the meeting with the ICANN Board. 5.1 - Introduction of topic (Council leadership) 5.2 - Council discussion 5.3 - Next steps Item 6: COUNCIL DISCUSSION - Update on the SubPro ODP / Debrief From Meeting With the ICANN Board (20 Minutes) On 12 September 2021 the ICANN Board directed<https://www.icann.org/resources/board-material/resolutions-2021-09-12-en#1.a> the ICANN President and CEO to organize the resources required to begin work on the Operational Design Phase (ODP) for the GNSO's New gTLD Subsequent Procedures Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-repo...> and the Affirmations, Recommendations, and Implementation Guidance contained in that report. On 27 November 2021, the Council appointed Jeff Neuman to serve as its liaison to the SubPro ODP. On 20 December 2021, ICANN org announced<https://www.icann.org/en/announcements/details/icann-launches-new-gtld-subse...> that the SubPro ODP had formally launched, starting at the beginning of January 2022. ICANN org shared question set #2<https://mm.icann.org/pipermail/subpro-odp/attachments/20220211/93bd5c93/SubP...> with the GNSO Council's liaison to ODP on 11 February 2022, who subsequently shared the questions and an update<https://mm.icann.org/pipermail/council/2022-February/025440.html> with the Council. While the question set was specifically about the topic of Applicant Support, it introduced broader procedural concerns, about whether the level of substantive work recommended by SubPro to be conducted by an IRT, would be beyond the commonly understood scope of the IRT. As with the above item, the Council will have met with the ICANN Board just prior to the March Council meeting, and will have discussed the broader question of the Council conducting additional SubPro related work concurrent with the ODP and in advance of a Board vote on the recommendations. Here, the Council will receive an update from the liaison, as well as hold a debrief from the meeting with the ICANN Board. 6.1 - Introduction of topic (Council leadership) 6.2 - Update (GNSO Council liaison to the SubPro ODP, Jeff Neuman) 6.3 - Council discussion 6.4 - Next steps Item 7: COUNCIL DISCUSSION - DNS Abuse Small Team (15 minutes) At ICANN72, the GNSO Council agreed to establish a small team to consider and recommend next steps for the Council related to DNS abuse, if any. An assignment form<https://community.icann.org/download/attachments/178587048/Small%20Team%20As...> was drafted and the team held its first meeting 9 February 2022. The team agreed that as a first step, the Council should conduct outreach to interested community groups to better understand what DNS abuse related issues need to be addressed specifically via gTLD policy development. The small team expects to consider this same question amongst its members. Here, the small team will provide an update on its efforts. 7.1 - Introduction of topic (Small team co-leads: Mark Datysgeld & Paul McGrady) 7.2 - Council discussion 7.3 - Next steps Item 8: COUNCIL DISCUSSION - Dialogue With ICANN's Global Domains and Strategy (GDS) Department (20 Minutes) The GNSO Council and ICANN's Global Domains and Strategy (GDS) team share a very important relationship. The GDS team, in coordination with the GNSO policy support staff, track and support the policy development process. Recently, especially where the PDP charters call for it specifically, GDS has appointed liaisons to PDPs to help provide background information, channel feedback and input from the Org, and to closely monitor the deliberations of the PDP. Once the Council adopts the recommendations and they are adopted by the ICANN Board, GDS is responsible for implementing the recommendations. Given this important relationship, it is helpful for the Council and GDS to regularly communicate with each other. Here, the Council will receive a high-level update on GNSO-related work being performed by GDS, as well as look ahead to work on the horizon, including the impact on resources. The dialogue is also expected to include discussion on how the shared portfolio of work can be executed more effectively and efficiently. 8.1 - Introduction of topic (ICANN Org staff - GDS) 8.2 - Council discussion 8.3 - Next steps Item 9: ANY OTHER BUSINESS (10 minutes) 9.1 - Open microphone _______________________________ 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 16:30 UTC (12:30 local time) Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 08:30 San José, Costa Rica (CST) UTC-4 12:30 New York/Washington DC, USA (EST) UTC-5 11:30 Buenos Aires, Argentina (ART) UTC-3 13:30 Rio de Janeiro, Brazil (BRT) UTC-3 13:30 London, United Kingdom (GMT) UTC+0 16:30 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 17:30 Paris, France (CET) UTC+1 17:30 Moscow, Russia (MSK) UTC+3 19:30 Singapore (SGT) UTC+8 (Thursday) 00:30 Melbourne, Australia (AEDT) UTC+11 (Thursday) 03:30 ---------------------------------------------------------------------------- DST starts/ends on Sunday 27 March 2022, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 13 March 2022 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/yck4ykvp _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.