<HTML>
<HEAD>
<TITLE>Re: [council] Travel support draft text</TITLE>
</HEAD>
<BODY>
<FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:7pt'>All,<BR>
I’ll process the various points on this thread and respond no later than this weekend. Am on the road with a full schedule; hope that timing is good enough.<BR>
<BR>
Thanks,<BR>
Doug<BR>
<BR>
<BR>
On 12/10/08 11:57 PM, "Tim Ruiz" <<a href="tim@godaddy.com">tim@godaddy.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:7pt'><BR>
<BR>
> meetings allocations are fast approaching.<BR>
<BR>
Right, that's my concern. Regardless of my personal feelings, if we're<BR>
going to do this there needs to be time for the constituencies to make<BR>
decisions/arrangements.<BR>
<BR>
The response from Doug was that it was still all or nothing for now, but<BR>
the Staff would see if they could work something different out. That's<BR>
why we went with the somewhat highlevel principles below. So for now<BR>
there may be accompanying instructions that fit the current situation,<BR>
but they could be modified later if there is more flexibility without<BR>
having to modify the Council approved principles.<BR>
<BR>
So once the principles are approved, we just need to know how much is<BR>
available to split between the constituencies and draft an explanatory<BR>
note on how they indicate how (or for whom) they are going to use the<BR>
funds.<BR>
<BR>
Tim<BR>
<BR>
-------- Original Message --------<BR>
Subject: Re: [council] Travel support draft text<BR>
From: Avri Doria <<a href="avri@psg.com">avri@psg.com</a>><BR>
Date: Wed, December 10, 2008 4:21 pm<BR>
To: Council GNSO <<a href="council@gnso.icann.org">council@gnso.icann.org</a>><BR>
<BR>
<BR>
Hi,<BR>
<BR>
I believe the next step, once we have a document that is stable from<BR>
the drafting team and has all the edits people on the council want to<BR>
contribute, is to have a motion on making this the GNSO policy on<BR>
distributing the funds. I also think it would probably be good to get<BR>
constituency and public feedback on this motion and the document<BR>
before we vote.<BR>
<BR>
We also need to make sure that we understand the conditions under<BR>
which the staff will allow the constituencies to:<BR>
<BR>
> The use of travel support funds is to be solely determined by each<BR>
> constituency independently as it sees fit to most effectively<BR>
> progress the work of the GNSO.<BR>
<BR>
Ie. are we still under the all or nothing regime or has the staff<BR>
decided to allow room, expense and travel to be allocated separately<BR>
by the constituencies. I understand they have not accepted a proposal<BR>
to allow the funds to be allocated directly by the constituencies (or<BR>
do I misunderstand).<BR>
<BR>
We also need to get this done soon, as the next meetings allocations<BR>
are fast approaching.<BR>
<BR>
a.<BR>
<BR>
<BR>
On 10 Dec 2008, at 17:01, Tim Ruiz wrote:<BR>
<BR>
><BR>
> Agree. So what are the next steps?<BR>
><BR>
> Tim<BR>
><BR>
> -------- Original Message --------<BR>
> Subject: Re: [council] Travel support draft text<BR>
> From: Robin Gross <<a href="robin@ipjustice.org">robin@ipjustice.org</a>><BR>
> Date: Wed, December 10, 2008 12:34 pm<BR>
> To: Greg Ruth <<a href="greg_ruth@yahoo.com">greg_ruth@yahoo.com</a>><BR>
> Cc: Olga Cavalli <<a href="olgac@fibertel.com.ar">olgac@fibertel.com.ar</a>>, Philip Sheppard<BR>
> <<a href="philip.sheppard@aim.be">philip.sheppard@aim.be</a>>, Council GNSO <<a href="council@gnso.icann.org">council@gnso.icann.org</a>><BR>
><BR>
> Yes, this change makes sense.<BR>
><BR>
><BR>
> On Dec 10, 2008, at 10:19 AM, Greg Ruth wrote:<BR>
><BR>
> I agree with this change.<BR>
><BR>
> Greg<BR>
> From: Olga Cavalli <<a href="olgac@fibertel.com.ar">olgac@fibertel.com.ar</a>><BR>
> To: Philip Sheppard <<a href="philip.sheppard@aim.be">philip.sheppard@aim.be</a>><BR>
> Cc: Council GNSO <<a href="council@gnso.icann.org">council@gnso.icann.org</a>><BR>
> Sent: Wednesday, December 10, 2008 1:11:12 PM<BR>
> Subject: Re: [council] Travel support draft text<BR>
><BR>
> Phillip,<BR>
> yo make a good suggestion.<BR>
> I personally agree. If I do not hear any other comments I will rewrite<BR>
> the draft document.<BR>
> We should review this issue during our next conference call.<BR>
> Best<BR>
> Olga<BR>
><BR>
> 2008/12/8 Philip Sheppard <<a href="philip.sheppard@aim.be">philip.sheppard@aim.be</a>><BR>
> Olga, thanks for circulating this.<BR>
> Seems fine.<BR>
> On reporting I think we can be transparent without being bureaucratic<BR>
> and burdensome on volunteers.<BR>
> There is no merit in 15 Council members all writing a report saying "I<BR>
> attended a Council meeting".<BR>
> Moreover, I presume the system is that Constituencies nominate who<BR>
> gets<BR>
> the support but then the individual still needs to apply to ICANN<BR>
> staff<BR>
> for that support ?<BR>
> If so staff is fully informed of who gets what and other staff is<BR>
> fully<BR>
> informed of who attended what.<BR>
> Suggest the following instead:<BR>
> Philip<BR>
><BR>
> --------------------<BR>
> Transparency and Reporting:<BR>
> ICANN staff will publish the names of all those who receive travel<BR>
> support together with a list of the relevant meeting(s) for which the<BR>
> support was given and which were attended by the support recipient.<BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
> IP JUSTICE<BR>
> Robin Gross, Executive Director<BR>
> 1192 Haight Street, San Francisco, CA 94117 USA<BR>
> p: +1-415-553-6261 f: +1-415-462-6451<BR>
> w: <a href="http://www.ipjustice.org">http://www.ipjustice.org</a> e: <a href="robin@ipjustice.org">robin@ipjustice.org</a><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:7pt'><BR>
-- <BR>
Doug Brent<BR>
Chief Operating Officer<BR>
ICANN<BR>
Voice: +1 310.301.3871<BR>
Mobile: +1 650.996.4447<BR>
Fax: +1 310.823.8649<BR>
<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>