<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><P>Avri et al,</P>
<P> The solution to a problem depends heavily on the framing of that problem. Is it really 10 travel slots we have to allocate or a budget? If the latter, then perhaps the money can be divided up among the constituencies and then each constituency can use the travel funds as it sees fit.</P>
<DIV> </DIV>
<DIV>Greg</DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"><BR>
<DIV style="FONT-SIZE: 13px; FONT-FAMILY: arial, helvetica, sans-serif">----- Original Message ----<BR>From: Avri Doria <avri@psg.com><BR>To: Council GNSO <council@gnso.icann.org><BR>Sent: Thursday, August 14, 2008 7:36:08 AM<BR>Subject: Re: [council] Revised Community Travel Support Procedure for FY09<BR><BR><BR>Hi,<BR><BR>Now that this has been released, we need to determine rather soon, how <BR>the available travel slots (10) for Cairo will be allocated. Once the <BR>bi-cameral approach is approved, if it is, this might be easy, for <BR>now we have 6 constituencies and 10 slots and that means they do not <BR>divide equally.<BR><BR> Some questions that need to be answered (there may be more):<BR><BR>- do all constituencies wish to take part in the allocation?<BR><BR>- should allocation be based on need?<BR>- - if so how is need determined?<BR>-- is self declaration of need sufficient?<BR>-- and what
if more then 10 indicate need?<BR><BR>- do individual council members request support or should the request <BR>come from the constituency?<BR><BR>We may also want to provide feedback on the policy, but that is less <BR>critical at this point then of making sure we have the names in time <BR>for 60 days prior to the meeting. My assumption is that we need to <BR>provide our list of names by the end of August.<BR><BR>a.<BR><BR><BR>On 14 Aug 2008, at 05:54, Glen de Saint Géry wrote:<BR><BR>><BR>> [To: council[at]<A href="http://gnso.icann.org/" target=_blank>gnso.icann.org</A>; liaison6c[at]gnso.icann.org]<BR>> [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org]<BR>> [To: regional-liaisons[at]<A href="http://icann.org/" target=_blank>icann.org</A>]<BR>><BR>> <A href="http://www.icann.org/en/announcements/announcement-13aug08-en.htm"
target=_blank>http://www.icann.org/en/announcements/announcement-13aug08-en.htm</A><BR>><BR>> Please note that ICANN Posts Revised Community Travel Support <BR>> Procedure for FY09<BR>><BR>> 13 August 2008<BR>><BR>> The work to create a community travel support procedure began with a <BR>> specific call for travel support in late 2007 by some in the <BR>> community (though this issue has been discussed for some time). <BR>> There has been extensive consultation on community travel support. <BR>> It began as a workshop in Delhi, with comments received and an <BR>> analysis posted. Further, a draft was posted in June, discussed in <BR>> budget meetings in Paris, and again with fairly extensive comment in <BR>> person, via email and on the web. These second round of comments <BR>> were summarized and analyzed. This last summary is available
at:<BR>><BR>> <A href="http://forum.icann.org/lists/travel-support-draft/msg00013.html" target=_blank>http://forum.icann.org/lists/travel-support-draft/msg00013.html</A><BR>><BR>> The revised Community Travel Support Procedure for FY09 document<BR>> <A href="http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08-en.htm" target=_blank>http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08-en.htm</A><BR>> strives to accommodate the community feedback. Of course, this is a <BR>> subject about which complete agreement is not possible. However, <BR>> there is strong agreement within the community that a procedure <BR>> exist that is documented, transparent, consistent, adhered-to, and <BR>> reviewed/revised for efficacy.<BR>><BR>> Comparing the final procedure with the draft discussed in Paris, <BR>> some key changes include:<BR>><BR>> - Guarantees
travel support for NomCom-nominated counselors<BR>> - Stresses transparency in application and post-meeting reporting<BR>> - Allows for some flexibility in the allocation mechanism within a <BR>> SO without overburdening the Chair<BR>><BR>> The document strives to be complete without being overly-detailed. <BR>> This will leave many specific questions unanswered. ICANN staff will <BR>> develop and post a FAQ (frequently asked questions document) to <BR>> capture questions, and provide consistent answers to the entire <BR>> community. If you have questions, please send them to the ICANN <BR>> staff member with whom you work most closely, or send them to <A href="mailto:travel-support@icann.org" ymailto="mailto:travel-support@icann.org">travel-support@icann.org</A> <BR>> .<BR>><BR>> Staff will collect feedback on issues that arise in the first <BR>> implementation of
this procedure, now through the Cairo meeting, and <BR>> Staff will make clarifications, as needed. Additionally, Staff will <BR>> conduct a complete review of the Community Travel Support Procedure <BR>> at year end with a public consultation at the June ICANN meeting, <BR>> and this will be an opportunity for RSSAC to provide additional <BR>> input if desired.<BR>><BR>> Glen de Saint Géry<BR>> GNSO Secretariat<BR>> <A href="mailto:gnso.secretariat@gnso.icann.org" ymailto="mailto:gnso.secretariat@gnso.icann.org">gnso.secretariat@gnso.icann.org</A><BR>> <A href="http://gnso.icann.org/" target=_blank>http://gnso.icann.org</A><BR>><BR>><BR>><BR>><BR><BR><BR></DIV></DIV></div><br>
</body></html>