[Gnso-sc-budget] Next Meeting(s) - ICANN's Reserve Fund Replinishment

[Berry Cobb]

Hi All,

 

Rafik informed me that next Monday 2 April 2018 is an Easter holiday for
Europe.  Should we still try and have this call to discuss the Reserve Fund
Replenishment?  Or, can we take care of discussion for the 9 April 2018
scheduled meeting?  The Monday 14UTC time slot seemed to work well in the
past, and I suspect it might be difficult to navigate around other meetings
if we attempt to reschedule the 2 April session for that week.

 

Thoughts?

 

Thank you.

 

B

 

Berry A. Cobb

720.839.5735

 <mailto:mail at berrycobb.com> mail at berrycobb.com

@berrycobb

 

From: Gnso-sc-budget [mailto:gnso-sc-budget-bounces at icann.org] On Behalf Of
Berry Cobb
Sent: Wednesday, March 21, 2018 08:16
To: gnso-sc-budget at icann.org
Subject: [Gnso-sc-budget] Next Meeting(s) - ICANN's Reserve Fund
Replinishment

 

Hi All,

 

Welcome back from San Juan for those that travelled.  As noted by Ayden
regarding the open public comment on the Replenishment of ICANN's Reserve
Fund, it seemed as though there is support to provide the Council with a
draft of comments for their consideration and submission.  

 

The public comment closes on 25 April
(https://www.icann.org/public-comments/reserve-fund-replenishment-2018-03-06
-en ) and the next GNSO Council meeting is scheduled for 26 April.  Thus,
the Council's consideration will have to occur via the email list.

 

Here's a link to the comment submitted by the Council regarding the Reserve
Fund Target Level:
https://mm.icann.org/pipermail/comments-reserve-fund-12oct17/2017q4/000013.h
tml

 

In preparation for discussions on this topic, you will see shortly two SCBO
meetings invitations for April 2nd and 9th at 14:00UTC, each for 60 minutes.


 

Thank you.

 

B

 

Berry A. Cobb

720.839.5735

mail at berrycobb.com

@berrycobb

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-sc-budget/attachments/20180326/afc6302c/attachment.html>