ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [council] Call with ICANN Finance Team and Board Finance Committee - Tuesday 10 May at 17.00 UTC

  • To: "'GNSO Council List'" <council@xxxxxxxxxxxxxx>
  • Subject: RE: [council] Call with ICANN Finance Team and Board Finance Committee - Tuesday 10 May at 17.00 UTC
  • From: "Berry Cobb" <mail@xxxxxxxxxxxxx>
  • Date: Wed, 11 May 2016 23:25:35 -0700
  • Comment: DKIM? See http://www.dkim.org
  • Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berrycobb.com; s=dkim-shared; x=1463639157; h=Comment: DomainKey-Signature:Received:Received:From:To:References: In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type: Thread-Index:Content-Language; bh=WLSSTarOii142shEjGZUoAf00rn1FH b4b6PnEIqAayY=; b=m4pxQRN8l6TJQ/VYS31n0AxMwAw1wZV91poQP7fR2toCE2 RvLZhW/2eqtiyHnfoLwIO42GKEqg9lFmJDLHYtUoTndO7es9x7QO7arJWNvQ6poL 62Oh9tu/q134Kl4qcc/rm/hwMYrsXWUaaSuUJqmYStn/h4AlwKmVEE30zanhM=
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dkim-shared; d=berrycobb.com; h=Received:Received:X-Originating-IP:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language; b=G4sCcXJsAsRPILvcs4gJoZ7Lg7dlWxYl3UjJ0uiJeHEoupmzdt4CSbWSA7Tk1I hgPU3d0q4mFbTxLCSalyMRUHU/uq6M4MW8b5VPwO3V9wD5IqAlzZ68HRbud9u77U /uJTeIffHE0lkxeL1uKj2pTTo5wZW6BVQoreMmsxwClWc=;
  • In-reply-to: <D357E342.68530%marika.konings@icann.org>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <D3565B57.683BB%marika.konings@icann.org> <57309970.2040301@julf.com> <DB3PR05MB521D166ED901B95D407305EF7700@DB3PR05MB521.eurprd05.prod.outlook.com> <D3566925.683E8%marika.konings@icann.org> <D357E342.68530%marika.konings@icann.org>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AQG2DbG4YJ8a05V+MUnS4sKKlR5imQLeO/a+Air12hIBOwpqiAHRVoTMn6pU8KA=

All,

 

On Tuesday, James and a few staff met with ICANN?s Finance team to review
through the GNSO Council comments submitted in relation to ICANN's draft
FY17 Budget and Ops plan.  The recording can be found here:
https://community.icann.org/display/projfinadhocws/Calls+with+Community+on+P
ublic+Comments+Submitted+on+the+Draft+FY17+Operating+Plan+and+Budget.  

 

The GNSO Council?s comment submission can be reviewed among the others,
https://forum.icann.org/lists/comments-op-budget-fy17-five-year-05mar16/).
At rough count, eleven comments were submitted with submissions from ALAC,
GNSO (IPC, ISPCP, BC, RySG, Council), RSSAC, ccNSO, GAC, and a few
individuals.

 

We did not have enough time to review through the Council?s specific
comments related to Special Projects, but Xavier and his team committed to
preparing responses for each of the points made.  The call, however, was
devoted to reviewing the General Comments.  A high-level outline of the call
follows:

1.       Introduction by Leo Vegoda on collaborative process for engaging
the community about the draft FY 17 budget.

2.       Introduction by Xavier Calvez on the Council?s submission.

3.       A quick discussion in how the GNSO Council formulated its comments
with a small volunteer sub-team of Council members.

4.       Much of the discussion recognized the less than formal process in
how the GNSO Council currently handles comments and input into the budget
process.

5.       As with one of the points made in the Council?s submission, the
Council recognizes this process should be more formalized, especially in the
context of implementation of the IANA Stewardship to ICANN and the Empowered
Community.

6.       Xavier and his team offered to collaborate with the GNSO Council to
assist in enhanced exchanges, develop a sustainable process, and was
delighted to hear that the GNSO is already starting discussions in how it
might organize its role within the Empowered Community, at least as it
pertain to the budget process.

a.       The Council may wish to consider the formation of an SCI type of
function by chartering a standing finance committee that will work closely
with ICANN?s finance team, interested members of the GNSO, and SO/ACs.  This
can likely be further discussed and defined in the context of the GNSO?s
pending effort around IANA Stewardship Transition Planning that staff just
sent to the Council today. 

b.      One suggestion from Xavier for the Council to consider is that
perhaps a part of this finance committee could be more formally constituted
from appointed Treasurers of each SG & C without limiting others in the GNSO
that may take a special interest around ICANN budgets.

7.       ICANN Finance intends to hold a session in Helsinki regarding the
planning process for FY18, especially in the context of the transition
implementation.

8.       There was a discussion about summary or aggregate information of
the budget versus project level details and trying to find the right
balance.  Detail of 400+ projects is a challenge but still seek ways to
provide adequate information for analysis.  More specifically, FTE listing
at the project level has been produced at the project level, however, it is
now reverted back to the portfolio level due to confidentiality concerns in
that it starts to reveal individual compensation.  Finance suggests that it
may be possible to provide that detail, but confidential concerns will have
to be addressed.

9.       Special project comment responses will be provided in writing back
to the GNSO Council.

 

We will pass along additional information as we encounter it.

 

Thank you.

 

B

 

charter a "standing finance committee" or something

 

Berry A. Cobb

Internet Corporation for Assigned Names & Numbers

720.839.5735

mail@xxxxxxxxxxxxx

@berrycobb

 

-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On
Behalf Of Marika Konings
Sent: Tuesday, May 10, 2016 10:14
To: Marika Konings; Milan, Stefania; Johan Helsingius; GNSO Council List
Subject: Re: [council] Call with ICANN Finance Team and Board Finance
Committee - Tuesday 10 May at 17.00 UTC

 

For those that are interested in this topic, please note that the call is

starting now. You can join at  <https://icann.adobeconnect.com/planning>
https://icann.adobeconnect.com/planning.

 

Best regards,

 

Marika

 

 

 

On 09/05/16 16:20, "Marika Konings" <owner-council@xxxxxxxxxxxxxx on

behalf of  <mailto:marika.konings@xxxxxxxxx> marika.konings@xxxxxxxxx>
wrote:

 

>Yes, it looks like the recording for these meetings is made available on

>the same wiki page after the meeting.

> 

>Best regards,

> 

>Marika

> 

>On 09/05/16 16:13, "Milan, Stefania" < <mailto:Stefania.Milan@xxxxxx>
Stefania.Milan@xxxxxx> wrote:

> 

>>Same here. A recording would be very helpful

>>Stefania

>> 

>> 

>>________________________________________

>>Da:  <mailto:owner-council@xxxxxxxxxxxxxx> owner-council@xxxxxxxxxxxxxx <
<mailto:owner-council@xxxxxxxxxxxxxx> owner-council@xxxxxxxxxxxxxx> per
conto

>>di Johan Helsingius < <mailto:julf@xxxxxxxx> julf@xxxxxxxx>

>>Inviato: lunedì 9 maggio 2016 16.06.40

>>A: Marika Konings; GNSO Council List

>>Oggetto: Re: [council] Call with ICANN Finance Team and Board Finance

>>Committee - Tuesday 10 May at 17.00 UTC

>> 

>>Dear Marika,

>> 

>>Will a recording or transcript be available afterwards?

>>I a, very interested in this discussion, but unfortunately

>>I have a scheduling conflict for tomorrow.

>> 

>>        Julf

>> 

>>On 09-05-16 15:21, Marika Konings wrote:

>>> Dear All,

>>> 

>>> As a reminder, the ICANN Finance Team together with the Board Finance

>>> Committee has scheduled a call tomorrow (Tuesday 10 May) at 17.00 UTC

>>>to

>>> discuss the input that has been submitted by the GNSO Council (see

>>> 

>>>
<https://forum.icann.org/lists/comments-op-budget-fy17-five-year-05mar16/>
https://forum.icann.org/lists/comments-op-budget-fy17-five-year-05mar16/

>>>m

>>>sg00007.html).

>>> For details on how to join this meeting, please

>>> see  <https://community.icann.org/x/yjiAAw>
https://community.icann.org/x/yjiAAw.

>>> 

>>> Best regards,

>>> 

>>> Marika

>> 

>> 

>>The information transmitted is intended only for the person or entity to

>>which it is addressed and may contain confidential and/or privileged

>>material. Any review, retransmission, dissemination, distribution,

>>forwarding, or other use of, or taking of any action in reliance upon,

>>this information by persons or entities other than the intended recipient

>>is prohibited without the express permission of the sender. If you

>>received this communication in error, please contact the sender and

>>delete the material from any computer.



<<< Chronological Index >>>    <<< Thread Index >>>