[ALAC] [CCWG-ACCT] Fwd: FW: Adopted motion
Holly Raiche
h.raiche at internode.on.net
Wed Oct 5 22:44:24 UTC 2016
Replies interspersed
Holly
On 6 Oct 2016, at 4:42 am, Alan Greenberg <alan.greenberg at mcgill.ca> wrote:
> There is an ongoing ALAC consensus call regarding approval of the FY17 CCWG Accountability WS2 budget and process which ends tomorrow. Based on the comments received to date, it will be approved.
>
> Below is the GNSO Motion approving the budget and process. I thank Sébastien for calling my attention to it. My assumption is that:
>
> - Resolved 1-4 were implied in the proposal, but there is no harm in reiterating them;
Agreed
>
> - I think that we cannot stop the issue of jurisdiction/organization (Resolved 5) from being discussed, but I would not want to see an explicit funding (as in legal costs) going into this.
Agreed
>
> Should we take any action? For example:
>
> a) Support 1-5 as noted above;
I think we do already, but no harm in saying so
>
> b) explicitly not support one or more of the points;
>
> c) be silent;
The danger in saying nothing is that we look as if we are in some way backing out of the process - we aren’t but saying nothing could look that way
>
> d) some other variant?
>
> Alan
>
>> From: Marika Konings
>> Sent: Thursday, September 29, 2016 11:33 PM
>> To: Glen de Saint Géry <Glen at icann.org>
>> Subject: Adopted motion
>>
>> Motion - GNSO Validation of CCWG-Accountability Budget Request
>>
>> Made By: James Bladel
>> Seconded by: Julf Helsingius, Keith Drazek
>>
>> WHEREAS,
>>
>> 1. Per its Charter, the Project Cost Support Team (PCST) has supported the CCWG-Accountability in developing a draft budget and cost-control processes for the CCWG-Accountability activities for FY17, and has also developed a historical analysis of all the transition costs to date (see https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf ).
>>
>> 2. The CCWG-Accountability FY17 budget was presented at its plenary meeting of June 21st and approved for transmission to the Chartering Organizations for validation as per the process agreed with the PCST. This request for validation was received on 23 June.
>>
>> 3. Following review and discussion during ICANN56, the GNSO Council requested a webinar on this topic which was held on 23 August (see transcript at https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-23aug16-en.pdf , recording at http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3 and AC recording at https://icann.adobeconnect.com/p8fu99qpt7d/).
>>
>> 4. The GNSO Council notes that many members of the GNSO community have expressed the view that the projected budget does not likely support revisiting the topic of the jurisdiction of ICANN’s organization in that such exploration would likely require substantial independent legal advice on alternative jurisdictions and their potential impact on the text and structure of ICANN’s Bylaws.
>>
>> 5. The GNSO Council has discussed and reviewed all the relevant materials.
>>
>> RESOLVED,
>>
>> 1. The GNSO Council hereby accepts the proposed CCWG-Accountability FY17 budget, as well as the cost-control processes presented in conjunction with the CCWG budget, expects the working groups to be restrained and judicious in their use of outside legal assistance, and believes that the Legal Committee should exercise reasonable and effective controls in evaluating requests for outside legal assistance and should approve them only when deemed essential to assist a working group to fully and objectively understand and develop a particular course of action for which the group has reached a substantial degree of consensus and requires legal advice on its risks and feasibility.
>>
>> 2. The GNSO Council expects to receive regular updates on actual expenditures as tracked against this adopted budget, and reserves the right to provide further input on the budget allocation in relation to the CCWG-Accountability related activities.
>>
>> 3. The GNSO Council expects ICANN staff, including its office of General Counsel, to provide the assistance requested by the CCWG and its working groups in an expeditious, comprehensive, and unbiased manner.
>>
>> 4. The GNSO Council expects the CCWG-Accountability and staff to work within the constraints of this approved budget, and that excess costs or requests for additional funding beyond said budget should be recommended by the Legal Committee only when deemed essential to completion of the CCWG’s work and objectives. .
>>
>> 5. It is the position of the GNSO Council that revisiting the jurisdiction or organization of the ICANN legal entity, as established by CCWG-Accountability Work Stream 1, would not likely be supported by this projected budget and, further, that such inquiry should not be undertaken at this time because the new accountability measures are all premised and dependent on California jurisdiction for their effective operation, and any near-term changes in organizational jurisdiction could be extremely destabilizing for ICANN and its community.
>>
>> 6. The GNSO Council requests the GNSO Secretariat to communicate this resolution to the CCWG-Accountability Chairs, and to the office of the ICANN CFO.
> <smime257.p7s>_______________________________________________
> ALAC mailing list
> ALAC at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/alac
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20161006/c0911613/attachment.html>
More information about the ALAC
mailing list