Wolf-Ulrich - This is one of the key questions we should discuss and resolve. The thinking behind a “standing committee” was that we were trying to address a lack of available volunteers to review & prepare feedback on the ICANN budget. So naturally we shouldn’t say no to anyone wishing to participate, simply because they aren’t on Council. On the other hand, this group would be focused only on cross-GNSO considerations in the ICANN budget. Anything that is specific to a Stakeholder Group or Constituency would more appropriately be raised by the SG/C submitting their own comment on the budget. Thank you for getting this discussion kicked off. I’ve attached the Standing Committee Charter (clean and redline) and a draft Call for Volunteers (thanks to Berry for preparing both!) from our discussion during the last GNSO Council call. Let’s continue the discussion, and seek to answer two key questions: (1) Should this group exist, and (2) if so, who should participate? Thanks— J. From: <council-bounces@gnso.icann.org> on behalf of "Wolf-Ulrich.Knoben" <wolf-ulrich.knoben@t-online.de> Date: Wednesday, October 11, 2017 at 16:14 To: Berry Cobb <mail@berrycobb.com>, GNSO Council List <council@gnso.icann.org> Subject: Re: [council] GNSO Council Agenda Item: ICANN FY Budget and Ops Plan Standing Committee Thanks Berry! With respect to the draft charter I'd like to hear on the call the rationale to limiting committee membership just to council members. Best regards Wolf-Ulrich Am 10.10.2017 um 16:15 schrieb Berry Cobb: Dear Council Members, Staff wanted to draw your attention to one of the agenda items in preparation for the Council call on 12 October. You might recall discussions at ICANN59 about the possible formation of a standing committee to assist the GNSO Council’s participation in the annual ICANN Fiscal Year Budget and Operating Plan process and to become more proactive in preparation of public comments on behalf of the Council. Attached, you will find a draft document that first contains a call for volunteers within the Council and secondly the document contains a proposed draft charter for the standing committee activities. Should the Council support the standing committee formation and with adequate volunteers, the charter can then be further refined and later approved by the Council. In related news, you just saw a note sent by the Council Chair with the announcement of the public comment period for the PTI FY19 draft budget. In the past, the Council has not submitted public comments because it is more to do with operations that affect registry operators and less to do with policy development. However, that does not prevent the Council from submitting comments for this cycle. The comment period will close 26 November. The target for PTI budget approval is 9 January 2018. There will also be two sessions at ICANN60 relating to the FY19 Budget: · ICANN Budget Basics (30 Oct, 1515-1645) http://sched.co/CbEv · Budget Working Group (1 Nov, 1030-1400) http://sched.co/CbGT Also, ICANN Finance held an FY19 Planning webinar in September<https://community.icann.org/display/projfinadhocws/FY19+Planning+Process>. The public comment window for the ICANN Org budget is set to begin on 15 January until 4 March 2018. You might notice this schedule is earlier than prior years to allow the ICANN Board to approve the budget and still provide adequate time for review by the Empowered Community (EC). The earlier process cycle and Board approval is to mitigate ICANN Org from having to enter into the “care-taker budget” process should the EC choose not to reject the budget. Staff will remind the Council often as key milestones on the budget process draw near. Thank you for your attention and staff looks forward to assisting the Council on this process. B Berry A. Cobb 720.839.5735 mail@berrycobb.com<mailto:mail@berrycobb.com> @berrycobb _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council

Thanks James, I assume the formal call for volunteers shall follow soon. I understand the different context of SG/C and council related budget matters. From my personal experience it is of advantage to keep the entire work on constituency level within the same hands which in addition would address the lack of volunteers in the communities. In the charter we could set a requirement for the chair (and maybe vicechair) of the standing committee being a council member. We'll continue discussion in our constituency. Best regards Wolf-Ulrich Am 17.10.2017 um 23:47 schrieb James M. Bladel:

Wolf-Ulrich -

This is one of the key questions we should discuss and resolve.  The thinking behind a “standing committee” was that we were trying to address a lack of available volunteers to review & prepare feedback on the ICANN budget. So naturally we shouldn’t say no to anyone wishing to participate, simply because they aren’t on Council.

On the other hand, this group would be focused only on cross-GNSO considerations in the ICANN budget.  Anything that is specific to a Stakeholder Group or Constituency would more appropriately be raised by the SG/C submitting their own comment on the budget.

Thank you for getting this discussion kicked off.  I’ve attached the Standing Committee Charter (clean and redline) and a draft Call for Volunteers (thanks to Berry for preparing both!) from our discussion during the last GNSO Council call.  Let’s continue the discussion, and seek to answer two key questions: (1) Should this group exist, and (2) if so, who should participate?

Thanks—

J.

*From: *<council-bounces@gnso.icann.org> on behalf of "Wolf-Ulrich.Knoben" <wolf-ulrich.knoben@t-online.de> *Date: *Wednesday, October 11, 2017 at 16:14 *To: *Berry Cobb <mail@berrycobb.com>, GNSO Council List <council@gnso.icann.org> *Subject: *Re: [council] GNSO Council Agenda Item: ICANN FY Budget and Ops Plan Standing Committee

Thanks Berry!

With respect to the draft charter I'd like to hear on the call the rationale to limiting committee membership just to council members.

Best regards

Wolf-Ulrich

Am 10.10.2017 um 16:15 schrieb Berry Cobb:

Dear Council Members,

Staff wanted to draw your attention to one of the agenda items in preparation for the Council call on 12 October.

You might recall discussions at ICANN59 about the possible formation of a standing committee to assist the GNSO Council’s participation in the annual ICANN Fiscal Year Budget and Operating Plan process and to become more proactive in preparation of public comments on behalf of the Council.  Attached, you will find a draft document that first contains a call for volunteers within the Council and secondly the document contains a proposed draft charter for the standing committee activities. Should the Council support the standing committee formation and with adequate volunteers, the charter can then be further refined and later approved by the Council.

In related news, you just saw a note sent by the Council Chair with the announcement of the public comment period for the PTI FY19 draft budget.  In the past, the Council has not submitted public comments because it is more to do with operations that affect registry operators and less to do with policy development.  However, that does not prevent the Council from submitting comments for this cycle.  The comment period will close *_26 November_*.  The target for PTI budget approval is *_9 January 2018_*.  There will also be two sessions at ICANN60 relating to the FY19 Budget:

·         ICANN Budget Basics (30 Oct, 1515-1645) http://sched.co/CbEv <http://sched.co/CbEv>

·         Budget Working Group (1 Nov, 1030-1400) http://sched.co/CbGT <http://sched.co/CbGT>

Also, ICANN Finance held an FY19 Planning webinar in September <https://community.icann.org/display/projfinadhocws/FY19+Planning+Process>.  The public comment window for the ICANN Org budget is set to begin on *_15 January_* until *_4 March 2018_*. You might notice this schedule is earlier than prior years to allow the ICANN Board to approve the budget and still provide adequate time for review by the Empowered Community (EC).  The earlier process cycle and Board approval is to mitigate ICANN Org from having to enter into the “care-taker budget” process should the EC choose not to reject the budget.  Staff will remind the Council often as key milestones on the budget process draw near.

Thank you for your attention and staff looks forward to assisting the Council on this process.

B

Berry A. Cobb

720.839.5735

mail@berrycobb.com <mailto:mail@berrycobb.com>

@berrycobb

_______________________________________________

council mailing list

council@gnso.icann.org <mailto:council@gnso.icann.org>

https://mm.icann.org/mailman/listinfo/council