<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>Thanks for forwarding this, Bill. There is one significant improvement in this proposed travel policy from the staff: we can split the airfare and hotel between 2 different people if that works best (it was an all or nothing policy before). </div><div><br></div><div>But there is also one difference that burdens recipients: now ICANN staff is saying the participant will have to front their own "per diem" expenses and only after the participant submits a report and attendance records are checked will the per diem be transfered. (Before the per diem was given a few days ahead of the meeting to ensure the participant can meet expenses on the ground at the time they are incurred.) This was not a change the GNSO recommended, but something ICANN staff is trying to impose on us. I hope the proposed change will be brought to the attention of Counsel and resisted.</div><div><br></div><div>Thanks,</div><div>Robin</div><div><br></div><br><div><div>On Jan 10, 2009, at 8:57 AM, William Drake wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<div><br></div><div>Per Cheryl's request, below is the message on the travel policy. Sorry I didn't send it before, busy and losing track of things. The message arrived just before the council took up the matter Thursday, so it was a bit of surprise to at least some of us who were expecting something different, e.g the simpler and more bottom up approach endorsed by the council in December. Several people expressed opposition and asked Olga to convey their concerns to the group working on it. In addition, there have subsequently been requests on the GNSO list, including from us (Carlos), for staff clarification as to what happened and why. So it's not entirely clear to me what the status is now, whether we are awaiting a revision or should act on the basis of the below. Nevertheless, we are supposed to turn in the list of funding requests ASAP.</div><div><br></div><div>Maybe someone here is closer to this process and can elaborate?</div><div><br></div><div>Best,</div><div><br></div><div>Bill</div><div><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="5" color="#000000" style="font: 18.0px Helvetica; color: #000000"><b>From: </b></font><font face="Helvetica" size="5" style="font: 18.0px Helvetica">"Denise Michel" <<a href="mailto:michel.denise@gmail.com">michel.denise@gmail.com</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="5" color="#000000" style="font: 18.0px Helvetica; color: #000000"><b>Date: </b></font><font face="Helvetica" size="5" style="font: 18.0px Helvetica">January 8, 2009 9:13:58 PM GMT+01:00</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="5" color="#000000" style="font: 18.0px Helvetica; color: #000000"><b>To: </b></font><font face="Helvetica" size="5" style="font: 18.0px Helvetica">"<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>" <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>>, liaison6c <<a href="mailto:liaison6c@gnso.icann.org">liaison6c@gnso.icann.org</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="5" color="#000000" style="font: 18.0px Helvetica; color: #000000"><b>Subject: </b></font><font face="Helvetica" size="5" style="font: 18.0px Helvetica"><b>[council] Fwd: Community Travel support Procedure for Mexico City</b></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="5" color="#000000" style="font: 18.0px Helvetica; color: #000000"><b>Reply-To: </b></font><font face="Helvetica" size="5" style="font: 18.0px Helvetica"><a href="mailto:denise.michel@icann.org">denise.michel@icann.org</a></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div> </div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Kevin Wilson</b> <span dir="ltr"><<a href="mailto:kevin.wilson@icann.org">kevin.wilson@icann.org</a>></span><br> Date: Thu, Jan 8, 2009 at 12:06 PM<br>Subject: Community Travel support Procedure for Mexico City<br><br><br> <div link="blue" vlink="purple" lang="EN-US"> <div><p>Dear Supporting Organisation participants: </p><p>The following information is provided to help you take advantage of the travel funding made available for the ICANN Mexico City meeting through the new <a href="http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08-en.htm" target="_blank">Community Travel Support Procedure</a> (CTSP). Since travel arrangements for the Mexico City meeting need to be completed this month, your organisation may want to use a "temporary" process for providing a list of ICANN-funded travelers for this meeting. By <b>22 January 2009</b>, staff needs a list of supported travelers - 13 names from the GNSO and 12 names from the ccNSO including the chair and NomCom appointees. (Please note the additional important deadlines for Mexico City travel are included below.) </p><p>We look forward to receiving the final, proposed travel allocation procedure for your SO. Please email it to me and ICANN's travel coordinator at the following addresses: <a href="mailto:kevin.wilson@icann.org" target="_blank">kevin.wilson@icann.org</a> and <a href="mailto:travel-support@icann.org" target="_blank">travel-support@icann.org</a></p><p><b>1) Deadlines for ICANN-funded travel to the </b><b>Mexico City<b> meeting. </b></b></p><p><b> </b>To ensure all available travel funds can be used for the ICANN Mexico City meeting, which starts 2 November, the following schedule will apply: <b> </b></p> <ul type="disc"> <li><b>22 January (14:00 PDT) – </b>deadline for each Supporting Organisation Chair to provide ICANN Staff – <a href="mailto:travel-support@icann.org" target="_blank">travel-support@icann.org</a> – with the list of travelers who are to receive travel support under the CTSP. If your SO has named you as a recipient of support for Mexico City, you will be contacted by ICANN Travel Coordination Staff with complete information on how your arrangements will be made. <b> </b></li> </ul> <ul type="disc"> <li><b>28 January (14:00 PDT) – </b>deadline for room bookings. All travelers' arrival and departure dates need to be finalized by this date because this is the date by which all hotel room reservations must be contracted for or released. After this date, any additional cost for changes to travelers' arrival and departure details will be paid by the traveler, unless otherwise agreed to in advance, in writing, by ICANN Travel Staff.<b> </b></li> </ul> <ul type="disc"> <li><b>28 January (14:00 PDT) – </b>deadline for flight bookings. Any approved traveler who has not completed their flight on or before this time will no longer be eligible for sponsored air travel.<b> </b></li> </ul><p><b>2) Important change</b></p> <ul type="disc"> <li><span style="color: rgb(31, 73, 125);">I</span>n response to community requests for this meeting air fare and hotel support can now be split between two designated travelers (1 person would receive only hotel support and another person would receive only air fare support, and this would be counted as 1 funded traveler for the purposes of an SO's allocation.</li> </ul><p><b>3) Requirements for ICANN-funded travelers for the </b><b>Mexico City<b> include the following: </b></b></p> <ul type="disc"> <li>The names of all ICANN-supported travelers will be publicly posted on the ICANN community travel webpage (<a href="http://www.icann.org/en/topics/travel-support/" target="_blank">http://www.icann.org/en/topics/travel-support/</a>), along with the class of travel supported, and the amount of travel funding received. </li> <li>For newly supported travelers (excluding Chair and NomCom-appointees) people who receive travel support will be asked to complete a meeting attendance form<span style="color: rgb(31, 73, 125);"> </span>which will be publicly posted, and also will be required to attend all relevant, scheduled SO-related meetings in Mexico City (as identified by your SO). Each SO is encouraged to provide guidance on the general content requirements for travelers' reports. </li> <li>Per diem payments to funded travelers will be issued after their reports are received and attendance records verified. This is in response to the community requests to ensure transparency, accountability and efficacy for ICANN travel funding, and also is consistent with the approach used for ICANN's fellowship program participants. <b> </b></li> </ul><p><b>4) Individuals who are not members of an SO Council <u><span style="color: rgb(31, 73, 125);">can</span></u> be selected to receive travel support. </b>As stated, the goal of the CTSP is "to lower the barrier to participation, broaden the group of participants and, advance the work" of I<span style="color: rgb(31, 73, 125);"> </span>CANN. SO's are asked to provide a list of individuals to receive travel funding "based on best meeting the policy-making needs of the entity." Any SO member is eligible to receive travel funding. <b> </b></p><p>The GNSO has been asked to provide ICANN Staff with the names of 13 individuals (including chair and NomCom appointees) to receive travel funding, and the ccNSO has been asked to provide ICANN Staff with the names of 12 individuals (including chair and NomCom appointees) to receive travel funding. Although these numbers were based on the total number of Council members from each SO, travel funding is not restricted to Council members. </p><p><b>5) SO's should consider factoring "need" into selection of travelers. </b>This is one element which SOs may wish to consider when determining who should receive travel support. This supports ICANN's goal of lowering the barrier to participation. </p><p><b>6)</b> <b>If an SO does not use all of its available travel slots for a given meeting, they can be 'rolled over' to a subsequent meeting. </b>This applies until the end of each ICANN fiscal year, after which point the unused support is 'lost' and the new fiscal year – and a potentially revised CTSP applies.<br clear="all"> </p><p>Please don't hesitate to contact me if you need further information.<br><font color="#888888"> <br> Kevin Wilson</font></p> </div> </div> </div><br></blockquote></div><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Arial; font-size: 18px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Arial; font-size: 18px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Arial; font-size: 18px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">***********************************************************</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">William J. Drake </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Senior Associate</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Centre for International Governance</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Graduate Institute of International and</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> Development Studies</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Geneva, Switzerland</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="mailto:william.drake@graduateinstitute.ch">william.drake@graduateinstitute.ch</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">New book: <i>Governing Global Electronic Networks,</i></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://tinyurl.com/5mh9jj">http://tinyurl.com/5mh9jj</a></div></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">***********************************************************</div></div></div></div></div></div></span></span></div></span> </div><br></div></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div><br class="Apple-interchange-newline"><br class="khtml-block-placeholder"></div><div><br class="khtml-block-placeholder"></div><div>IP JUSTICE</div><div>Robin Gross, Executive Director</div><div>1192 Haight Street, San Francisco, CA 94117 USA</div><div>p: +1-415-553-6261 f: +1-415-462-6451</div><div>w: <a href="http://www.ipjustice.org">http://www.ipjustice.org</a> e: <a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a></div><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"> </div><br></body></html>