ICANN/GNSO GNSO Email List Archives

[council]


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

Re: [council] Proposed Comment on FY17 Budget and Operating Plan


Hello Amr and everyone,

There is no motion to be voted on with respect to this topic. This was also the 
case last year, when the Council also submitted a comment on the FY16 Budget. 
The idea here is that the Council will discuss the draft that was prepared by 
the small team at this call, with a view toward finalizing any comments and 
changes via the email list subsequently but in good enough time to submit the 
final comment by the 30 April deadline.

FYI, while the GNSO Council will need a motion on any matter for which it is 
required to vote (e.g. PDP-related topics), the Council does have the ability 
to take action without a motion or voting on other matters. As you may recall, 
this has been done a number of times with respect to non-PDP and such topics 
for which is vote is not specifically required.

I hope this helps.

Thanks and cheers
Mary

Mary Wong
Senior Policy Director
Internet Corporation for Assigned Names and Numbers (ICANN)
Email: mary.wong@xxxxxxxxx
Telephone: +1-603-5744889










On 4/14/16, 05:44, "owner-council@xxxxxxxxxxxxxx on behalf of Amr Elsadr" 
<owner-council@xxxxxxxxxxxxxx on behalf of aelsadr@xxxxxxxxxxx> wrote:

>
>Hi,
>
>Ed, James, Carlos and Keith…, thank you very much for this. I can’t imagine 
>that getting this done was particularly easy.
>
>I was wondering how we would be handling this on tonight’s Council call. It is 
>listed as an agenda item for Council approval on on the Council meeting agenda 
>(https://community.icann.org/display/gnsocouncilmeetings/Agenda+14+April+2016),
> but not listed as a motion to be voted on 
>(https://community.icann.org/display/gnsocouncilmeetings/Motions+14+April+2016).
> So I’m not entirely clear on what the outcome of this agenda item is meant to 
>be. Any insight would be appreciated.
>
>Thanks.
>
>Amr
>
>> On Apr 13, 2016, at 10:19 PM, Edward Morris <egmorris1@xxxxxxxxx> wrote:
>> 
>> My Fellow Councillors,
>>  
>> You will recall at our ICANN55 Council meeting, a small team (James, Carlos, 
>> Keith, myself) volunteered to formulate draft comments relating to ICANN's 
>> proposed Draft FY17 operating plan and budget.  Attached you will find a 
>> starter draft of comments for the Council to consider.  Track changes are 
>> enabled should any member of the Council wish to suggest edits. Please feel 
>> to do so and then send them back over the list. This small team with 
>> assistance from staff will maintain a master copy to ready for submission.
>>  
>> The Public Comments are due by 30 April 2016, and thus we have just over two 
>> weeks to make edits and then determine if the Council wishes to submit them. 
>>  This topic is currently on the GNSO Council agenda for tomorrow.  The small 
>> team also recognizes that likely all SGs & Cs will be submitting their own 
>> comments.  In that regard and because we are managers of the policy process, 
>> this draft of comments attempted to only focus at a higher level of how the 
>> proposed budget impacts the GNSO and its policy development activities.
>>  
>> This process for submitting comments mimics what occurred last year for the 
>> FY16 draft budget.  Once that draft was completed over the Council list, the 
>> comments were submitted without objection.  As we will likely discuss 
>> tomorrow and based on this current experience, the Council should consider 
>> formalizing this process especially in the light of a future empowered 
>> community.
>>  
>> In addition to thanking James, Carlos and Keith with whom it has been a 
>> pleasure to work with, special thanks go out from all of us  to Berry and 
>> Marika for their exceptional input and dedicated effort on this comment. We 
>> are extraordinarily lucky to have such fine staff assigned to help us on 
>> Council.
>>  
>> We looks forward to everyone's input.
>>  
>> Kind Regards,
>>  
>> Ed Morris
>> <Budget Comment.docx>
>
>




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