<div dir="ltr">
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;color:rgb(69,69,69)">Hi all,</p>
<p class="gmail-p2" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;color:rgb(69,69,69);min-height:14px"><br></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;color:rgb(69,69,69)">I'd like to express my interest in the slot. I will be working on the application and plan in order to deliver it in time before the 15th.<span class="gmail-Apple-converted-space"> </span></p>
<p class="gmail-p2" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;color:rgb(69,69,69);min-height:14px"><br></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;color:rgb(69,69,69)">Best,</p><p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;color:rgb(69,69,69)"><br></p><p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:12px;line-height:normal;font-family:Helvetica;color:rgb(69,69,69)">Antonella</p></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 4 Feb 2019 at 17:04, Michael Karanicolas <<a href="mailto:mkaranicolas@gmail.com">mkaranicolas@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
I would like to apply for a Marrakech slot. I haven't asked for EC<br>
support for Kobe, and since ICANN66 will be in Canada, this will be<br>
the only meeting in 2019 where I request support.<br>
<br>
I'm heavily involved in a number of aspects of ICANN policy work<br>
representing the NCUC, including in the RPMs group, as most recently<br>
as a member of the ATRT3 review team. Happy to develop an engagement<br>
plan, as needed, and to complete the reporting requirements, as I've<br>
done for previous meetings.<br>
<br>
Best,<br>
<br>
Michael<br>
<br>
On Mon, Feb 4, 2019 at 3:48 PM Bruna Martins dos Santos<br>
<<a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a>> wrote:<br>
><br>
> Dear EC,<br>
><br>
> FYI - we need to indicate who will be the Marrakech travelers until Friday, 22 February 2019. Therefore, I will be accepting applications for the two EC funded slots available for EC members who wish to attend ICANN 65 and are not otherwise funded.<br>
><br>
> Please see below the procedures for EC funding allocation from our travel policy and send your application to the EC list until February 15th.<br>
><br>
> Best,<br>
> --<br>
> Bruna Martins dos Santos<br>
><br>
> Skype ID: bruna.martinsantos<br>
> @boomartins<br>
><br>
><br>
> _______________________________________________________<br>
> Procedures for EC funding allocation<br>
><br>
> – ICANN Meetings funding allocation for Executive Committee representatives<br>
><br>
> – Executive Committee representatives travel support allocations<br>
><br>
> For each ICANN Meeting, the NCUC leadership team is allocated three travel slots. One of these travel slots must be assigned to the NCUC Chair. The remaining two travel slots, or a reallocation of the Chair’s travel slot if he or she relinquishes it, will be assigned to representatives who fulfill the following criteria:<br>
><br>
> The representative develops an activity plan that he or she will carry out in the ICANN meeting. This plan must contain a detailed account of the representative’s current engagement in ICANN activities, their plan of engagement at the face-to-face meeting, and explain why and how their physical presence in that meeting is important for achieving the NCUC’s objectives and mission. The timeline for the submission of this application will follow the procedure described in the NCUC Travel Support Policy unless initiated sooner by the NCUC Chair at his or her discretion. The EC travel funding allocation should precede NCUC travel support programme.<br>
><br>
> The representative must observe all criteria for eligibility as described in the NCUC Travel policy session above, highlighting the participation on NCSG and NCUC activities. In case of a tie between applicants, the Chair will ask representatives to make reasonable efforts to find an alternative source of funding. Evidence must be provided to the Chair of these attempts. If a representative seeks alternative funding but is declined or rejected, this will not be held against them. Representatives who make no reasonable efforts to find alternative funding will receive lower priority for NCUC resources than those who make reasonable efforts;<br>
><br>
> Where there are more candidates for a slot than there are slots available, the regional designation of the EC representative may be a factor weighing in its allocation. The EC representative must send a detailed action plan outlining their plans for inreach/outreach of membership within their region;<br>
><br>
> As described in Eligibility criteria, EC who have received travel support for the previous meeting cannot apply again.<br>
><br>
> In receiving funding for a meeting, travellers agree to write daily reports during the meeting to update the membership on the proceedings. At his or her discretion, the NCUC Chair may choose to publish these reports as a blog post, or may request that the representative convert their report into a blog post.If a representative receives support, and does not meet their commitments as outlined above, they will be ineligible to receive further NCUC resources.<br>
><br>
> References:<br>
> * NCUC Operating Procedures: <a href="https://www.ncuc.org/wp-content/uploads/2017/09/NCUC-Operating-Procedures-Sept-2017.pdf" rel="noreferrer" target="_blank">https://www.ncuc.org/wp-content/uploads/2017/09/NCUC-Operating-Procedures-Sept-2017.pdf</a><br>
> (Noting item III Travel support selection and VI Outreach and VII Funding)<br>
><br>
> *NCUC Bylaws (Esp. Item XI.A on Transparency): <a href="https://www.ncuc.org/bylaws/" rel="noreferrer" target="_blank">https://www.ncuc.org/bylaws/</a><br>
><br>
><br>
> ---------- Forwarded message ---------<br>
> From: Terri Agnew <<a href="mailto:terri.agnew@icann.org" target="_blank">terri.agnew@icann.org</a>><br>
> Date: seg, 4 de fev de 2019 às 17:21<br>
> Subject: ICANN65 | Marrakech- Supported Travelers/Contractor Travelers Database Due // Friday, 22 February 2019<br>
> To: <a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a> <<a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a>>, Maryam Bakoshi <<a href="mailto:maryam.bakoshi@icann.org" target="_blank">maryam.bakoshi@icann.org</a>><br>
> Cc: <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a> <<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>><br>
><br>
><br>
> Dear all,<br>
><br>
><br>
><br>
> In order to service your travel needs for ICANN65 in Marrakech in a timely fashion, please submit your ICANN65 Meeting database to <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a> by Friday, 22 February 2019.<br>
><br>
> A timely response would be appreciated in view of visa issues and the OFAC review. The deadline for submissions is critical to allow for confirmed reservation numbers as required for visa and travel arrangements.<br>
><br>
> Moving forward, all tri-annual meeting funded traveler lists are due 120 days prior to the next ICANN meeting. (This was formerly 90 days prior).<br>
><br>
><br>
><br>
> Benefits of having the list 120 Days Before the Meeting:<br>
><br>
> Allow ICANN to gather the documentation required (hotel and flight confirmations) for funded travelers to apply for their visa.<br>
> Allow enough time for funded travelers to complete and submit their visa application, which often vary per ICANN Meeting location.<br>
> Allow enough time for funded travelers to apply for a transit visa (if required), which often vary per ICANN Meeting location.<br>
> Allow ICANN to purchase less expensive airfares.<br>
> Allow the travelers to plan their pre-and-post Meeting Travel in advance.<br>
> Allow ICANN to set-up funded travelers in advance as vendors with Finance allowing us to wire their per diem funds in a timelier manner.<br>
><br>
><br>
><br>
> Please note:<br>
><br>
> GNSO supported traveler with a designated hotel accommodation funding, a hotel room is automatically secured for you, please DO NOT book your own hotel as it is un-reimbursable.<br>
> All personal data provided to ICANN org in for purposes of providing travel support for participants related to ICANN events will be processed in accordance with the ICANN Privacy Policy [<a href="http://icann.org" rel="noreferrer" target="_blank">icann.org</a>]. Should you have any questions or concerns about this Privacy Policy and our privacy practices, you may contact us at <a href="mailto:privacy@icann.org" target="_blank">privacy@icann.org</a>.<br>
><br>
><br>
><br>
> Please note that when requesting travel support, in the interest of fairness and in light of budget restrictions we would like you to take the following into consideration:<br>
><br>
><br>
><br>
> 1. Respond timely to ICANN Travel regarding your upcoming travel.<br>
><br>
> 2. If you require a visa to enter the country, please make sure to acquire your visa immediately. Please contact the ICANN travel team to let them know you will need a visa.<br>
><br>
> 3. Requests past the deadline will be handled on a case by case basis by ICANN. All additional travelers added after the 90-day deadline are subject to availability, may NOT be placed in the same hotel as their funded traveler groups, and may not be able to attend due to visa issues.<br>
><br>
> 4. If possible please book direct travel requests. Detours and multi-stop trips are unfortunately not guaranteed.<br>
><br>
> 5. Strictly limit your travel from your home to the ICANN meeting venue.<br>
><br>
> 6. Approved date of arrival/departure for this meeting is Sunday, 23 June – Friday, 28 June 2019<br>
><br>
> 7. If travelers want to extend their stay this must be done at their own expense and should contact the hotel directly once the ICANN hotel confirmation has be sent to them.<br>
><br>
> 8. Privately Booked Reservations: ICANN will not refund or take over accommodations directly booked by the funded traveler. If a replacement has an existing hotel reservation, they will need to cancel their reservation and ICANN will not be able to take over their reservation.<br>
><br>
><br>
><br>
> Many thanks for your cooperation!<br>
><br>
><br>
><br>
> With kind regards,<br>
><br>
> Terri<br>
><br>
> ---<br>
><br>
> Terri Agnew<br>
><br>
> Operations Support - GNSO Lead Administrator<br>
><br>
> Internet Corporation for Assigned Names and Numbers (ICANN)<br>
><br>
> Email: <a href="mailto:terri.agnew@icann.org" target="_blank">terri.agnew@icann.org</a><br>
><br>
> Skype ID: terri.agnew.icann<br>
><br>
><br>
><br>
> Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages [<a href="http://gnso.icann.org" rel="noreferrer" target="_blank">gnso.icann.org</a>]<br>
><br>
> Follow @GNSO on Twitter: <a href="https://twitter.com/ICANN_GNSO" rel="noreferrer" target="_blank">https://twitter.com/ICANN_GNSO</a> [<a href="http://twitter.com" rel="noreferrer" target="_blank">twitter.com</a>]<br>
><br>
> Follow the GNSO on Facebook: <a href="https://www.facebook.com/icanngnso/" rel="noreferrer" target="_blank">https://www.facebook.com/icanngnso/</a> [<a href="http://facebook.com" rel="noreferrer" target="_blank">facebook.com</a>]<br>
><br>
> <a href="http://gnso.icann.org/en/" rel="noreferrer" target="_blank">http://gnso.icann.org/en/</a> [<a href="http://gnso.icann.org" rel="noreferrer" target="_blank">gnso.icann.org</a>]<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> Bruna Martins dos Santos<br>
><br>
> Skype ID: bruna.martinsantos<br>
> @boomartins<br>
> _______________________________________________<br>
> NCUC-EC mailing list<br>
> <a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank">NCUC-EC@lists.ncuc.org</a><br>
> <a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><br>
_______________________________________________<br>
NCUC-EC mailing list<br>
<a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank">NCUC-EC@lists.ncuc.org</a><br>
<a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><br>
</blockquote></div>