[NCUC-EC] ICANN65 | Marrakech - EC Travelers Application Due15 February 2019
Antonella Perini
antomperini at gmail.com
Mon Feb 4 21:50:14 CET 2019
Hi all,
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.
Best,
Antonella
On Mon, 4 Feb 2019 at 17:04, Michael Karanicolas <mkaranicolas at gmail.com>
wrote:
> Hi all,
>
> I would like to apply for a Marrakech slot. I haven't asked for EC
> support for Kobe, and since ICANN66 will be in Canada, this will be
> the only meeting in 2019 where I request support.
>
> I'm heavily involved in a number of aspects of ICANN policy work
> representing the NCUC, including in the RPMs group, as most recently
> as a member of the ATRT3 review team. Happy to develop an engagement
> plan, as needed, and to complete the reporting requirements, as I've
> done for previous meetings.
>
> Best,
>
> Michael
>
> On Mon, Feb 4, 2019 at 3:48 PM Bruna Martins dos Santos
> <bruna.mrtns at gmail.com> wrote:
> >
> > Dear EC,
> >
> > 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.
> >
> > Please see below the procedures for EC funding allocation from our
> travel policy and send your application to the EC list until February 15th.
> >
> > Best,
> > --
> > Bruna Martins dos Santos
> >
> > Skype ID: bruna.martinsantos
> > @boomartins
> >
> >
> > _______________________________________________________
> > Procedures for EC funding allocation
> >
> > – ICANN Meetings funding allocation for Executive Committee
> representatives
> >
> > – Executive Committee representatives travel support allocations
> >
> > 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:
> >
> > 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.
> >
> > 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;
> >
> > 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;
> >
> > As described in Eligibility criteria, EC who have received travel
> support for the previous meeting cannot apply again.
> >
> > 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.
> >
> > References:
> > * NCUC Operating Procedures:
> https://www.ncuc.org/wp-content/uploads/2017/09/NCUC-Operating-Procedures-Sept-2017.pdf
> > (Noting item III Travel support selection and VI Outreach and VII
> Funding)
> >
> > *NCUC Bylaws (Esp. Item XI.A on Transparency):
> https://www.ncuc.org/bylaws/
> >
> >
> > ---------- Forwarded message ---------
> > From: Terri Agnew <terri.agnew at icann.org>
> > Date: seg, 4 de fev de 2019 às 17:21
> > Subject: ICANN65 | Marrakech- Supported Travelers/Contractor Travelers
> Database Due // Friday, 22 February 2019
> > To: bruna.mrtns at gmail.com <bruna.mrtns at gmail.com>, Maryam Bakoshi <
> maryam.bakoshi at icann.org>
> > Cc: gnso-secs at icann.org <gnso-secs at icann.org>
> >
> >
> > Dear all,
> >
> >
> >
> > In order to service your travel needs for ICANN65 in Marrakech in a
> timely fashion, please submit your ICANN65 Meeting database to
> gnso-secs at icann.org by Friday, 22 February 2019.
> >
> > 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.
> >
> > 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).
> >
> >
> >
> > Benefits of having the list 120 Days Before the Meeting:
> >
> > Allow ICANN to gather the documentation required (hotel and flight
> confirmations) for funded travelers to apply for their visa.
> > Allow enough time for funded travelers to complete and submit their visa
> application, which often vary per ICANN Meeting location.
> > Allow enough time for funded travelers to apply for a transit visa (if
> required), which often vary per ICANN Meeting location.
> > Allow ICANN to purchase less expensive airfares.
> > Allow the travelers to plan their pre-and-post Meeting Travel in advance.
> > 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.
> >
> >
> >
> > Please note:
> >
> > 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.
> > 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 [icann.org]. Should you have
> any questions or concerns about this Privacy Policy and our privacy
> practices, you may contact us at privacy at icann.org.
> >
> >
> >
> > 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:
> >
> >
> >
> > 1. Respond timely to ICANN Travel regarding your upcoming
> travel.
> >
> > 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.
> >
> > 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.
> >
> > 4. If possible please book direct travel requests. Detours
> and multi-stop trips are unfortunately not guaranteed.
> >
> > 5. Strictly limit your travel from your home to the ICANN
> meeting venue.
> >
> > 6. Approved date of arrival/departure for this meeting is
> Sunday, 23 June – Friday, 28 June 2019
> >
> > 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.
> >
> > 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.
> >
> >
> >
> > Many thanks for your cooperation!
> >
> >
> >
> > With kind regards,
> >
> > Terri
> >
> > ---
> >
> > Terri Agnew
> >
> > Operations Support - GNSO Lead Administrator
> >
> > Internet Corporation for Assigned Names and Numbers (ICANN)
> >
> > Email: terri.agnew at icann.org
> >
> > Skype ID: terri.agnew.icann
> >
> >
> >
> > Find out more about the GNSO by taking our interactive courses and
> visiting the GNSO Newcomer pages [gnso.icann.org]
> >
> > Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO [twitter.com]
> >
> > Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ [
> facebook.com]
> >
> > http://gnso.icann.org/en/ [gnso.icann.org]
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Bruna Martins dos Santos
> >
> > Skype ID: bruna.martinsantos
> > @boomartins
> > _______________________________________________
> > NCUC-EC mailing list
> > NCUC-EC at lists.ncuc.org
> > https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
> _______________________________________________
> NCUC-EC mailing list
> NCUC-EC at lists.ncuc.org
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20190204/5c97673b/attachment.html>
More information about the NCUC-EC
mailing list