[NCSG-PC] [Ext] Re: [NCSG-EC] Fwd: ICANN68 | Kuala Lumpur - Supported Travelers/
Tatiana Tropina
tatiana.tropina at gmail.com
Fri Feb 7 16:57:29 EET 2020
Oh. Hi :-)
Yes, am planning to go, so am in!
Cheers,
Tanya
On Fri, 7 Feb 2020 at 14:46, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> wrote:
> oops, no wonder it is quiet! Thanks for catching that :-D
> Please see below, councilors!
>
> On 2020-02-07 09:37, Maryam Bakoshi wrote:
>
> Hi Stephanie,
>
> You forgot to cc the Policy committee :)
>
> —
> Many thanks,
>
>
> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator
> *ICANN* | Internet Corporation for Assigned Names and Numbers
> *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777
>
> On 7 Feb 2020, at 14:17, Stephanie Perrin via NCSG-EC
> <ncsg-ec at lists.ncsg.is> <ncsg-ec at lists.ncsg.is> wrote:
>
>
>
> Thanks Juan, I will get that going right away if possible. So far, I have
> Rafik, Yourself, Raphael, could the remaining councilors please confirm
> (and apologies if I have missed anyone who already confirmed). James,
> Tatiana, Farell, Elsa???
>
> Cheers Steph
> On 2020-02-06 10:41, Juan Manuel Rojas wrote:
>
> Dear Stephanie,
> I am going to Kuala Lumpur and I will also need to confirm my name as soon
> as we can due to I will have to start my visa process in a Consular office
> in another country, and I would like to start soon to avoid any further
> issue.
>
> Best Regards
> Juan Manuel Rojas
>
> Sent from Yahoo Mail on Android [go.onelink.me]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__go.onelink.me_107872968-3Fpid-3DInProduct-26c-3DGlobal-5FInternal-5FYGrowth-5FAndroidEmailSig-5F-5FAndroidUsers-26af-5Fwl-3Dym-26af-5Fsub1-3DInternal-26af-5Fsub2-3DGlobal-5FYGrowth-26af-5Fsub3-3DEmailSignature&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=1A9IIOkJia11FXDmJ1R4Jn7wGT4ExHiVuBF89mvNt_Q&m=uxIN3ieMAP4PMC7cqBEV4wB8j1_kRAfIF0LtzmR6zt0&s=PV1Fbek-6u2xQ4jbVdKs9CcEKwm50ERcbUsmnSvQDk4&e=>
>
> On Tue, Feb 4, 2020 at 10:06, Stephanie Perrin via NCSG-EC
> <ncsg-ec at lists.ncsg.is> <ncsg-ec at lists.ncsg.is> wrote:
>
> Please note below the deadline for Kuala Lumpur travel. Let me know all
> confirmed travellers, I would ike to get our stuff in early for a change.
>
> cheers Steph
>
>
> -------- Forwarded Message --------
> Subject: ICANN68 | Kuala Lumpur - Supported Travelers/Contractor
> Travelers Database Due // Friday, 21 February 2020
> Date: Mon, 3 Feb 2020 21:02:29 +0000
> From: Terri Agnew <terri.agnew at icann.org> <terri.agnew at icann.org>
> To: Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>
> <stephanie.perrin at mail.utoronto.ca>, Maryam Bakoshi
> <maryam.bakoshi at icann.org> <maryam.bakoshi at icann.org>
> CC: gnso-secs at icann.org <gnso-secs at icann.org> <gnso-secs at icann.org>
>
> Dear all,
>
>
>
> In order to service your travel needs for ICANN68 in Kuala Lumpur in a
> timely fashion, please submit your ICANN68 Meeting database to
> gnso-secs at icann.org by *Friday, 21 February 2020 *in order to be
> submitted by deadline of Monday, 24 February 2020.
>
>
>
> As a reminder, for the AGM meeting only, incoming Councilors get funding,
> as well as the then-incumbent Councilors.
>
>
>
> 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.
>
> All tri-annual meeting *funded traveler lists are due 120 days* prior to
> the next ICANN meeting.
>
>
>
> *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]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
> 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,
> 21 June 2020 – Friday, 26 June 2020*
>
> 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 visiting: https://learn.icann.org/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=>
>
> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=>
>
> Transcripts and recordings of GNSO Working Group and Council events are
> located on the GNSO Master Calendar
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ncsg.is_mailman_listinfo_ncsg-2Dec&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=1A9IIOkJia11FXDmJ1R4Jn7wGT4ExHiVuBF89mvNt_Q&m=uxIN3ieMAP4PMC7cqBEV4wB8j1_kRAfIF0LtzmR6zt0&s=it1nr_XCwrRe4R1_itjRKWSJeYITXF--OBxA9uPaM0Y&e=>
>
> --> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ncsg.is_mailman_listinfo_ncsg-2Dec&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=1A9IIOkJia11FXDmJ1R4Jn7wGT4ExHiVuBF89mvNt_Q&m=uxIN3ieMAP4PMC7cqBEV4wB8j1_kRAfIF0LtzmR6zt0&s=it1nr_XCwrRe4R1_itjRKWSJeYITXF--OBxA9uPaM0Y&e=
>
> -->
>
> --> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20200207/d33261c4/attachment.htm>
More information about the NCSG-PC
mailing list