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

For other times: https://tinyurl.com/2d3axjb9

PROPOSED AGENDA

  • Roll Call & SOI Updates (2 minutes)
  • Welcome & Chair updates (Chair) (5 minutes)
  • Finalize draft of comments for FY23 via working document [docs.google.com] (50 minutes)
  • Next steps & closing (3 minutes)
    • Next meeting: none

Links to Relevant Documents:

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
  • 20 Jan 2022 – GNSO Council Meeting (update to Council)
  • 26 Jan 2022 – SCBO meeting #05 @14:00 UTC (joint session with the CCNSO’s SOPC)
  • 31 Jan 2022 – Submit draft to GNSO Council for review
  • 02 Feb 2022 – SCBO meeting #06 @14:00 UTC (as required)
  • 07 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

RECORDINGS

Audio Recording

Zoom Recording

Chat Transcript

PARTICIPATION

Attendance

Apologies: Antonia Chu, Tom Barrett

 

Notes/ Action Items

Roll Call & SOI Updates

  • None

Welcome & Chair Updates

  • None

Finalize draft of comments for FY23 via working document

  • Goal is to finalize and share with Council. Submit by 7 Feb.
  • General Comments:
    • Understanding resource allocations for each SO/SC/SG/C has been an ongoing ask for several years. Suggestion that more detail is needed to better understand how the groups will be able to hold each other mutually accountable by having detailed information.
    • This question was submitted as a clarifying question in early January. Noted that the budget is broken out by operation initiatives and functional activities. The response from Org indicates their intention to understand breakout between SO/AC. The Council call should acknowledge the response from Org.
    • Having the numbers for each group will help to manage against that number. And the details may then help to understand where deficiencies might lie.
    • It may be more important to understand how resources are allocated for the GNSO, not necessarily across the group. So therefore, it may be more about holding ourselves accountable. The GNSO Council only has responsibility for gTLD policy development, so it might be better to just focus on that aspect, rather than other SO/ACs. The GNSO Council has no role in the financial accountability of the other SO/ACs.
    • Budget versus actuals may be a more useful metric to better understand if resource allocations are sufficient.
    • Add: Information is essential to hold the GNSO accountable to its responsibilities, effective performance, and being good stewards of the economy.
    • Maintained a marker for tools and support.
  • OFP Comments:
    • Also maintained a marker for staffing.
    • Included the work forecasted for the FY23 timeframe, to help demonstrate the impact on resources.
    • Suggested addition: Notes monitoring legislation. Is the existing report insufficient? Does not believe the reporting is sufficient about the local engagement on the ground. How can this concern be focused back on the budget? Can it possibly be more about clarity in allocation? The need is for progress reporting. Will move to where it would fall within the budget.
    • Another marker for planning and the SFICR, although requested more info about where the funds came from for the SFICR.
  • FY23 budget:
    • Another set of markers on PDP 3.0 and staffing.

 

Next steps & closing

  • John will make final edits before CoB today and provide to Council, to be submitted by the 7th.
  • Next step is for finance to incorporate changes as necessary. Will also publish report of public comments.
  • There will likely be a pre-ICANN73 webinar.
  • Updated budget likely completed in April/May, for adoption by the Board.
  • Staff will provide reference to responses to Council comments. The SCBO should review inputs and responses for other community groups.
  • Some exploration in the future for leveraging the SCBO for other activities, such as for prioritization.
  • Next meeting: none
  • No labels