Please find below the details for the Standing Committee on ICANNs Budget & Operations Planning call on Wednesday, 05 January 2022 at 14:00 UTC for 1 hour. 

For other times: https://tinyurl.com/3byc33kk

PROPOSED AGENDA

  • Roll Call & SOI Updates (2 minutes)
  • Welcome & Chair updates (Chair) (5 minutes)
  • Review & determine comments to pull forward to FY23 via working document [docs.google.com] (40 minutes)
  • Discuss and document any clarifying questions via working document [docs.google.com] (10 minutes)
  • Next steps & closing (3 minutes)
    • Next meeting 12 January 2022 @ 14:00 UTC

Schedule:

  • 15 Dec 2021 – SCBO meeting #01 @14:00 UTC to conduct initial review of draft documents
  • 05 Jan 2022 – SCBO meeting #02 @14:00 UTC
  • 07 Jan 2022 – Deadline to submit clarifying questions
  • 12 Jan 2022 – SCBO meeting #03 @14:00 UTC
  • 19 Jan 2022 – SCBO meeting #04 @14:00 UTC (joint session with the CCNSO’s SOPC???)
  • 20 Jan 2022 – GNSO Council Meeting (update to Council)
  • 26 Jan 2022 – SCBO meeting #05 @14:00 UTC
  • 02 Feb 2022 – SCBO meeting #06 @14:00 UTC (as required)
  • 06 Feb 2022 – Close of public comments on FY23 draft documents; due by 23:59 UTC
  • 17 Feb 2022 – GNSO Council Meeting
  • 05 Mar 2022 – ICANN73

BACKGROUND DOCUMENT

Links to Relevant Documents:

RECORDINGS

Audio Recording

Zoom Recording

Chat Transcript

PARTICIPATION

Attendance-CRM

Apologies: Maxim Alzoba, Sam Lanfranco, Osvaldo Novoa, Sebastien Ducos

 

Notes/ Action Items

Roll Call & SOI Updates

  • Kristian Ormen has changed jobs, effective in May. RrSG will replace him.


Welcome & Chair updates (Chair)

  • None

 

Review & determine comments to pull forward to FY23 via working document [docs.google.com]

  • Will use the previous comment as the basis to identify issues and clarifying comments for ICANN finance
  • In the General Comments, the 3rd bullet asks for resource allocations per SG, SO, AC, this level of detail seems to be unavailable in FY23 and is instead per Functional Activity (spread across the various expenses and groups supported). Breaking out funding in this manner is likely challenging. Funded travelers is however divided per SO/AC. Previous versions of the proposed budget (e.g. FY20) included more granular breakouts per group. Generally in section 1.3 regarding evolving policy development.
    • This concern was more a focus of previous SCBO leadership.
    • Some believe it is interesting information and helpful to determine adequate funding for the GNSO. Therefore, some support to bring the comment forward for FY23.
    • As noted, the structure now is completely different as it is captured by Functional Activity.
  • Suggestion that this may be helpful as clarifying question by 7 Jan, and potentially focus it around PDP support. The question could be written to highlight why the information is important.

Action Item: John to propose text

  • Bullet 4 regarding low, medium, high estimates to stay
  • Bullet 5 regarding year round engagement, potentially out. However, some thoughts from Strategic Planning Session that the SCBO could be leveraged for Council meeting planning. Can explain expectations in comment.
  • OFP Issue 1: Requested additional budget, FTEs for the next five years, based on FY22 budget. FY22 Forecast includes an additional FTE (35) and FY23 is at 36 and the budget has increased $1.3 m. There are two job postings live now. The request for additional resources seems to be reconciled.
  • Important to note that policy research, contracted parties, and technical services have policy touchpoints (as it relates to policy implementation). And this may be important to acknowledge given concerns from the SPS about implementation.

Action Item: John to find a volunteer to acknowledge changes.

  • OFP Issue 2: This appears to at least be partially met. There is an enterprise project mgmt. platform deployed, now used for all GNSO program and project mgmt. tools. Could focus on the collaboration around planning and prioritization. Could frame it around future planning for the SCBO, once the prioritization framework goes beyond pilot/beta.

Action Item: John

  • OFP Issue 3: Benefits of F2F meetings, which is relevant to the pandemic. Not certain there is specific relevance to the Council and does not seem to be a budget issue even. There appears to be a course of action nevertheless to try and return to F2F. And in fact, 3 F2F meetings are included in the proposed budget. Can probably drop this comment.
  • OFP Issue 4: Regarding resources for tools and support. Seems like it stays, but needs to be made current as it regards to tools and FTE (e.g., project manager open rec).
  • OFP Issue 5: Regarding budget for planning and project mgmt. oversight, this issue may be duplicative to general comment above (e.g., pivot to implementation concerns).

Discuss and document any clarifying questions via working document [docs.google.com]

  • John has three clarifying questions which he will add.

 

Next steps & closing

  • Meeting with the SOPC expected for the 26th. Change in SOPC leadership with Giovanni Seppia joining ICANN org. New leadership is new chair Andreas Musielak (.de) and vice-chair, Irina Daniela (.ru) . Irina is also a Councilor.
  • One item could be to refamiliarize groups with each other, understand purpose of meeting jointly.
  • This group should target end of Jan to provide draft to the Council. Draft will not be subject to vote, given timelines. Subject to non-objection at Council level.
  • There will likely be an ICANN73 prep week webinar for the budget.
  • No labels