[CCWG-ACCT] Fwd: Draft Agenda & Papers - WP1 Meeting #22 (28 July at 19h UTC)

Tue Jul 28 16:57:27 UTC 2015

Greg - it's only a recommendation but will help the board. Let me assure
you as the chair of the audit committee that a late budget approval will
have implications on internal controls. But, otherwise, I'm fine with your
recommendation as well.

Thanks for looking into it!
Erika

On Tue, Jul 28, 2015 at 6:00 PM, Greg Shatan <gregshatanipc at gmail.com>
wrote:

> I don't think we need the language kindly recommended by Erika.  We are
> already proposing a "process" that will be "in place if the final budget is
> not approved prior to the beginning of the year", in paragraph 06:
>
> If the exercise of this power leads to no budget being in place at the
>> start of a new financial year, a caretaker budget struck at the same level
>> as the previous year’s budget will apply, to allow for continued operation
>> of ICANN or of the IANA functions while the budget disagreement is resolved.
>
>
> Thus, the first sentence is moot.  The last sentence seems not to be
> on-topic -- we have not brought up the issue of internal controls, and we
> have no idea whether a late approval of the budget will have any effect on
> internal controls.
>
> If we want, we can add a sentence after the above, stating: "This is
> consistent with the "best practice" that a process is in place in the event
> a final budget is not approved prior to the beginning of the fiscal year."
>  I think this may comfort some readers, but it is not strictly necessary.
>
> Greg
>
> On Tue, Jul 28, 2015 at 10:28 AM, Erika Mann <erika at erikamann.com> wrote:
>
>> Jordan - we received an answer back from ICANN's auditors concerning the
>> question whether a budget veto right will impact the audit process. Answer "The
>> Company should make sure there is a process in place by the Board if the
>> final budget is not approved prior to the beginning of the year for best
>> practice purposes."
>> Therefore I recommend the add the following sentence at section: 'Comm
>> Power - Budgets and Plans (5B1)' "The Board will setup a process in case
>> the final budget is not approved prior to the beginning of the year to
>> allow best budgeting practices to continue. Approving the budget on time
>> ensures that internal controls can work."
>>
>> Please let me know if need more information.
>> Thanks,
>> Erika
>>
>> On Tue, Jul 28, 2015 at 11:21 AM, Jordan Carter <jordan at internetnz.net.nz
>> > wrote:
>>
>>> Dear CCWG members
>>>
>>> Please find attached a number of papers up for discussion on today's
>>> call in about three hours - these are final drafts, the marked ups and
>>> background versions are on the Wiki at the link below.
>>>
>>> Also attached is a summary noting what the key most recent changes have
>>> been.
>>>
>>> I particularly draw your attention to the paper which starts 5A2 on
>>> voting power, updated following the WP1 call this morning and now
>>> allocating 5 votes per SO and AC, and with an opt-in mechanism proposed.
>>>
>>>
>>> Speak with you soon,
>>>
>>> Jordan
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Jordan Carter <jordan at internetnz.net.nz>
>>> Date: 28 July 2015 at 21:20
>>> Subject: Draft Agenda & Papers - WP1 Meeting #22 (28 July at 19h UTC)
>>> To: "wp1 at icann.org" <wp1 at icann.org>
>>>
>>>
>>> Hi all
>>>
>>> Here is the draft agenda and the documents for the WP1 call happening at
>>> 19-21h UTC on Tuesday 28 July 2015.
>>>
>>> Also attached is the summary of issues.
>>>
>>> *Please read these documents before the call - the working method will
>>> be an "Are There Any Final Comments To Make/Did Anything Decided at CCWG
>>> Affect This Draft" approach...*
>>>
>>> [the reason for this is that our meeting finishes only 3 hrs before the
>>> absolute Freeze date for the
>>>
>>> *1. Review of Agenda.*
>>>
>>> *2. Any outstanding issues from CCWG meeting* of 28 July (12h-14h)
>>>
>>> *3. Final Review of the Following Documents* (clean PDFs of "final
>>> drafts" attached - mark ups and Word versions to come on Wiki site at <
>>> https://community.icann.org/display/acctcrosscomm/WP1+Draft+Documents> )
>>>
>>>   Fundamental Bylaws (3B)
>>>
>>>   Community Mechanism description (5A1)
>>>   Community Mech - voting weights (5A2) -- NOTE *an update to come yet
>>> from Bernie and Alan re quorums etc)*
>>>   Community Mech - ICANN community forum (5A3)
>>>
>>>   Comm Power - Budgets and Plans (5B1)
>>>   Comm Power - Standard Bylaws (5B2)
>>>   Comm Power - Removal of ICANN directors (5B3)
>>>   Comm Power - Recall of ICANN Board (5B4)
>>>
>>> Note: Steve's paper on incorporating AOC reviews into the ICANN bylaws
>>> (6-2) had agreement to incorporate the text on document disclosure etc on
>>> 27 July, so that paper is done and dusted. It's attached just so there is a
>>> complete collection here, but is not for discussion.
>>>
>>>
>>> *4. Next Task: Finalising responses to Public Comments from PC1*
>>>
>>> *5. Any other matters*
>>>
>>>
>>> --
>>> Jordan Carter
>>>
>>> Chief Executive
>>> *InternetNZ*
>>>
>>> +64-495-2118 (office) | +64-21-442-649 (mob)
>>> Email: jordan at internetnz.net.nz
>>> Skype: jordancarter
>>>
>>> *A better world through a better Internet *
>>>
>>>
>>>
>>>
>>> --
>>> Jordan Carter
>>>
>>> Chief Executive
>>> *InternetNZ*
>>>
>>> +64-495-2118 (office) | +64-21-442-649 (mob)
>>> Email: jordan at internetnz.net.nz
>>> Skype: jordancarter
>>>
>>> *A better world through a better Internet *
>>>
>>>
>>> _______________________________________________
>>> Accountability-Cross-Community mailing list
>>> Accountability-Cross-Community at icann.org
>>> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>>>
>>>
>>
>> _______________________________________________
>> Accountability-Cross-Community mailing list
>> Accountability-Cross-Community at icann.org
>> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20150728/4ed1fa6b/attachment.html>