<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks James,</p>
<p>I assume the formal call for volunteers shall follow soon.</p>
<p>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.</p>
<p>We'll continue discussion in our constituency.</p>
<p>Best regards</p>
<p>Wolf-Ulrich<br>
</p>
<br>
<div class="moz-cite-prefix">Am 17.10.2017 um 23:47 schrieb James M.
Bladel:<br>
</div>
<blockquote type="cite"
cite="mid:B4DAC366-01CA-418A-A541-C4AC6B8E2712@godaddy.com">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<div class="WordSection1">
<p class="MsoNormal">Wolf-Ulrich -<br>
<br>
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. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks—</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">J.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><b><span>From: </span></b><span><a class="moz-txt-link-rfc2396E" href="mailto:council-bounces@gnso.icann.org"><council-bounces@gnso.icann.org></a>
on behalf of "Wolf-Ulrich.Knoben"
<a class="moz-txt-link-rfc2396E" href="mailto:wolf-ulrich.knoben@t-online.de"><wolf-ulrich.knoben@t-online.de></a><br>
<b>Date: </b>Wednesday, October 11, 2017 at 16:14 <br>
<b>To: </b>Berry Cobb <a class="moz-txt-link-rfc2396E" href="mailto:mail@berrycobb.com"><mail@berrycobb.com></a>, GNSO
Council List <a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a><br>
<b>Subject: </b>Re: [council] GNSO Council Agenda Item:
ICANN FY Budget and Ops Plan Standing Committee</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p>Thanks Berry!</p>
<p>With respect to the draft charter I'd like to hear on the
call the rationale to limiting committee membership just to
council members.</p>
<p>Best regards</p>
<p>Wolf-Ulrich</p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Am 10.10.2017 um 16:15 schrieb Berry
Cobb:</p>
</div>
<blockquote>
<div>
<p class="MsoNormal">Dear Council Members,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Staff wanted to draw your attention to
one of the agenda items in preparation for the Council
call on 12 October.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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
<b><u>26 November</u></b>. The target for PTI budget
approval is <b><u>9 January 2018</u></b>. There will
also be two sessions at ICANN60 relating to the FY19
Budget:</p>
<p class="MsoListParagraph">· ICANN Budget Basics
(30 Oct, 1515-1645) <a href="http://sched.co/CbEv"
moz-do-not-send="true">
http://sched.co/CbEv</a></p>
<p class="MsoListParagraph">· Budget Working Group
(1 Nov, 1030-1400) <a href="http://sched.co/CbGT"
moz-do-not-send="true">
http://sched.co/CbGT</a></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Also, ICANN Finance held an
<a
href="https://community.icann.org/display/projfinadhocws/FY19+Planning+Process"
moz-do-not-send="true">
FY19 Planning webinar in September</a>. The public
comment window for the ICANN Org budget is set to begin on
<b><u>15 January</u></b> until <b><u>4 March 2018</u></b>.
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.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thank you for your attention and staff
looks forward to assisting the Council on this process.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">B</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Berry A. Cobb</p>
<p class="MsoNormal">720.839.5735</p>
<p class="MsoNormal"><a href="mailto:mail@berrycobb.com"
moz-do-not-send="true">mail@berrycobb.com</a></p>
<p class="MsoNormal">@berrycobb</p>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"><br>
<br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre>council mailing list</pre>
<pre><a href="mailto:council@gnso.icann.org" moz-do-not-send="true">council@gnso.icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/council" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/council</a></pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
</p>
</div>
</blockquote>
<br>
</body>
</html>