Hi Anne, Thank you for the very detailed and helpful response. I have provided responses below. Kind regards, Caitlin From: Anne ICANN <anneicanngnso@gmail.com> Date: Tuesday, February 18, 2025 at 7:25 PM To: Caitlin Tubergen <caitlin.tubergen@icann.org> Cc: "council@gnso.icann.org" <council@gnso.icann.org> Subject: [Ext] Re: [council] For your review: 2025 SPS Outcomes + Actions Hi Caitlin, Thank you for this summary. Regarding Item #8 - our Internet Governance group met via Zoom yesterday - a couple of observations on the "Outcomes" notes. 1. Jennifer Chung is also a volunteer on this group. Noted. Jennifer’s name is now added to the Google Doc. Thank you, Jennifer (and Anne)! 2. Doubt we should be called a "small team" since there is no charter and we aren't following small team protocols. The term "Ancillary" is used in Item 8 and that might be a good term - e.g. "GNSO Ancillary Topic Team"? (Others may have better ideas.) We note that the GAC has identified for Sebastien some designated members who are working at staying abreast of developments in this area and they are called "Topic Leads." Instead of creating new terminology, perhaps we can describe what this group will be doing. As Support Staff understands it, this is a group of councilors interested in and independently tracking internet governance updates (including WSIS+20, GDC, etc.) The important point is that this is not a formal small team and is not designed to be a heavy resource lift that requires additional full Council or ICANN org support. Is that understanding correct? 3. Several of us thought the authorized Topic was Internet Governance, not just WSIS+20, although we had a heavy focus on WSIS+20 and related deadlines in our meeting yesterday. (Farzaneh took detailed notes.) IG would include not only the mandate of IGF, but also the Global Digital Compact and related IG work that is apparently occurring in a Cross-Community Discussion Group which Bruna identified for us. So we probably need to classify the Ancillary Topic for this group as Internet Governance in the notes. Noted. We have updated the Google Doc to say: “GNSO Council’s Ancillary Work Management: Committees, Small Teams (both formal and informal), Liaisons: Internet Governance (WSIS + 20, GDC, etc.) ACTION: GNSO Council to form an informal small team to track the progress of Internet Governance Work (WSIS + 20, GDC, etc.) and provide ad hoc updates to the Council as needed. Small team volunteers: Anne Aikman-Scalese, Farzaneh Badii, Jennifer Chung, Sebastien Ducos, Bruna Martins de Santo, Desiree Miloshevic.” Does this work? 4. Re: the Global Digital Compact, I recall that Paul had a question as to why ICANN did not endorse the GDC. We noted this question in our meeting but do you have any records as to other questions or comments posed by Paul or others in terms of expectations for our group to assist Council to stay informed? We plan to expand on all of the outcomes in the SPS Outcomes Report, and we will share the more detailed notes once the Council has confirmed that the Outcomes List is correct. 5. There are several action items from our first meeting where others will be following up. I agreed to track down the notes from the SPS and report back to the group for our next Zoom and so your update is very helpful. If you have follow-up questions or terminology changes, we can certainly discuss in the smaller group rather than the Council list. Thank you! If you prefer to respond to only the Ancillary Topic team members rather than cluttering the list, please do. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, Feb 18, 2025 at 7:10 AM Caitlin Tubergen via council <council@icann.org<mailto:council@icann.org>> wrote: Dear Councilors, We ran out of time to discuss the 2025 Strategic Planning Session (SPS) Outcomes (Agenda Item 8) during the last Council meeting, so we have moved this item to the list. What is this about? Approximately one month ago, many of us were together in chilly Washington, DC, and during our final session, we reviewed a short, bulleted list of outcomes from the SPS. Support Staff took the short list and added some detail to these outcomes and action items. Following Council review, Support Staff will produce a more detailed SPS Outcomes Report and develop a more detailed plan, including identifying volunteers, to begin work on these outcomes and actions. What am I being asked to do now? Councilors are asked to perform a quick review the SPS Outcomes List and confirm if the outcomes and actions were captured correctly. We realize this is a busy time as we head into ICANN82, so there will be more time for thorough review once the draft Outcomes Report is distributed. (For those of you who appreciate a beautiful Oxford comma, your time is coming.) Where can I find the draft SPS Outcomes? Here is a link to the SPS Outcomes Google Doc: https://docs.google.com/document/d/1xsVKRbtJVsJg3V7opTpJr5T0-4LFafuYaojq44ik... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1xsVKRbtJVsJg3...>. For ease of reference, the outcomes are also included below. Due date? Tuesday, 25 February As we are asking for a cursory review only so that we can identify anything that may need to be discussed further in person at ICANN82, please provide feedback in the document or on list by Tuesday, 25 February. Thank you! Please let me know if you have any questions. Best regards, Caitlin -- DRAFT SPS OUTCOMES 1. GNSO Council’s Role as Manager of the PDP vis-a-vis previously-adopted GNSO PDP recommendations that the Board may “un-adopt”: * OUTCOME: GNSO Council discussed and crystallized their ideas for a proposed process for the ICANN Board to “un-adopt” a previously-adopted GNSO PDP policy recommendation: * ACTION: GNSO Support Staff and Council leadership to propose questions to ICANN org (and possibly others) regarding the preferred method to capture the process for the Board to un-adopt a GNSO recommendation, e.g., advisory, correspondence, et.al [et.al]<https://urldefense.com/v3/__http:/et.al__;!!PtGJab4!_-8v41OlPOgfE_lDI285HNHE...>. 1. GNSO Council’s Role as Manager of the PDP vis-a-vis non-consensus recommendations: · ACTION: Support Staff to collect metrics from at least the last five years regarding consensus designations and Council voting outcomes to inform the current Council on how non-consensus recommendations have been treated in the most recent PDPs. · ACTION: GNSO Council to communicate the ideas identified during the SPS for how the Council could potentially handle non-consensus recommendations (e.g., scorecard, remanding, reengaging when circumstances change) with the Board Readiness team. 1. GNSO Council’s Role as Manager of the PDP: · OUTCOME: During its discussion of the Council’s unique role with respect to policy development, the Council discussed the “picket fence”. Following a discussion of the picket fence and the relevant language in the Bylaws, the Council requested additional background to develop an increased understanding. · ACTION: Support Staff to consolidate the relevant Bylaws language related to the picket fence and circulate it to the Council to ensure the Council has a shared understanding 1. GNSO Council’s Role as Manager of the PDP vis-a-vis an Aspirational Statement: · ACTION: GNSO Council to reconsider an aspirational statement, which is a statement designed (i) to reinforce the Council’s role as manager of the PDP and (ii) to help councilors socialize the unique role of councilors to their respective Stakeholder Groups and Constituencies. The Council agreed the aspirational statement is NOT binding, a voting directive, or intended to limit the actions of Councilors. 1. GNSO Council’s Role as Manager of the PDP vis-a-vis its Tools: · ACTION: GNSO Council agreed to participate in two comprehensive reviews of the GNSO Projects List, the first to occur prior to the Community Forum (ICANN82) and second to occur prior to the Annual General Meeting (ICANN84). · ACTION: The first comprehensive review will occur during the Pre-ICANN82 GNSO Council webinar. · OUTCOME: GNSO Councilors expressed an interest in understanding how the Projects List could better show interrelated projects. · ACTION: GNSO Support Staff to highlight interrelated projects by calling out interdependencies and including anchor links into the Projects List. 1. GNSO Council’s Ancillary Work Management: Committees, Small Teams, Liaisons - (GNSO Council Standing Committee on Continuous Improvements (“SCCI”): · ACTION: In an effort for the GNSO Council to better understand the portfolio of upcoming work for the SCCI, GNSO Support Staff to provide a detailed presentation during a future Council meeting. 1. GNSO Council’s Ancillary Work Management: Committees, Small Teams, Liaisons - Role of GNSO Council Liaison to the GAC: · ACTION: GNSO Council Liaison to the GAC to perform a review of mutual topics of interest to both the GAC and GNSO and identify potential subject matter expert volunteers that could assist with capacity building, knowledge sharing, and improved communication between the GNSO and GAC. · ACTION: GNSO Council Liaison to the GAC to provide a progress report to the Council on the enhanced communication efforts in six months. 1. GNSO Council’s Ancillary Work Management: Committees, Small Teams, Liaisons - WSIS + 20: · ACTION: GNSO Council to form an informal small team to track the progress of this work and provide ad hoc updates to the Council as needed. Small team volunteers: Anne Aikman-Scalese, Farzaneh Badii, Sebastien Ducos, Bruna Martins de Santo, Desiree Miloshevic. _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto:council-leave@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.