[NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported Travelers Database Due | Thursday, 11 July 2024
farell at benin2point0.org
farell at benin2point0.org
Fri Jun 21 14:46:11 EEST 2024
Hi
thanks Rafik,
I thought it was only for chairs, not vice chairs. I will ask the staff again
Am 21. Juni 2024 um 12:23:05 +02:00, hat Rafik Dammak <rafik.dammak at gmail.com> geschrieben:
>
>
> Hi,
>
> Not long ago, there was a budget previously for WG chairs and they applied for it before. Did it stop?
> maybe worthy to check with GNSO staff about its status.
>
> Best,
>
> Rafik
>
>
>
> Le ven. 21 juin 2024 à 04:24, Johan Helsingius via NCSG-EC <<ncsg-ec at lists.ncsg.is>> a écrit :
>
> > Noted - ICANN should really pay for travel for WG chairs, but
> > with the current budget climate that is not going to happen. :(
> >
> > Julf
> >
> > On 20/06/2024 19:51, <farell at benin2point0.org> wrote:
> > > Yes I totally understand,
> > >
> > >
> > > As a vice chair for the EPDP on IDN which would be presenting the final
> > > report, I intend to be there. If there is no funding available I would
> > > be there at my own expenses. It's in Europe and it won't cost that much.
> > > I replied to the mail just FYI and in case there is an opportunity.
> > >
> > > Thanks.
> > >
> > >
> > > Le 20 juin 2024 à 16:59 UTC+01:00, Johan Helsingius <julf at Julf.com> a
> > > écrit :
> > >
> > > Hi Farell,
> > >
> > > I am afraid the ICANN travel funding is only available to councilors
> > > (incoming and outgoing) and 2 EC members. If some of them can't attend,
> > > there might be travel slots available to suitable volunteers.
> > >
> > > Julf
> > >
> > > On 20/06/2024 17:34, <farell at benin2point0.org>
> > > <mailto:<farell at benin2point0.org>> wrote:
> > >
> > > Hello Julf,
> > > Yes, I would like to attend in person.
> > > Le 20 juin 2024 à 16:02 UTC+01:00, Johan Helsingius via
> > > NCSG-PC <<ncsg-pc at lists.ncsg.is> <mailto:<ncsg-pc at lists.ncsg.is>>> a
> > > écrit :
> > > Here we go again...
> > > Please let me know if you intend to be in Istanbul in person or not.
> > > Julf
> > > -------- Forwarded Message --------
> > > Subject: ICANN81 | Istanbul | Supported Travelers Database Due |
> > > Thursday, 11 July 2024
> > > Date: Thu, 20 Jun 2024 14:02:02 +0000
> > > From: Terri Agnew <<terri.agnew at icann.org>
> > > <mailto:<terri.agnew at icann.org>> <mailto:<terri.agnew at icann.org>
> > > <mailto:<terri.agnew at icann.org>>>>
> > > To: <julf at julf.com> <mailto:<julf at julf.com>> <<julf at julf.com>
> > > <mailto:<julf at julf.com>> <mailto:<julf at julf.com>
> > > <mailto:<julf at julf.com>>>>,
> > > <jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>>
> > > <mailto:<jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>>>
> > > <<jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>>
> > > <mailto:<jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>>>>,
> > > <benakin at gmail.com> <mailto:<benakin at gmail.com>>
> > > <mailto:<benakin at gmail.com> <mailto:<benakin at gmail.com>>>
> > > <<benakin at gmail.com> <mailto:<benakin at gmail.com>>
> > > <mailto:<benakin at gmail.com> <mailto:<benakin at gmail.com>>>>,
> > > <chair at rysg.info> <mailto:<chair at rysg.info>>
> > > <mailto:<chair at rysg.info> <mailto:<chair at rysg.info>>>
> > > <<chair at rysg.info> <mailto:<chair at rysg.info>>
> > > <mailto:<chair at rysg.info> <mailto:<chair at rysg.info>>>>,
> > > <aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>
> > > <mailto:<aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>>
> > > <<aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>
> > > <mailto:<aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>>>,
> > > <mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>
> > > <mailto:<mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>>
> > > <<mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>
> > > <mailto:<mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>>>,
> > > <lschulman at inta.org> <mailto:<lschulman at inta.org>>
> > > <mailto:<lschulman at inta.org> <mailto:<lschulman at inta.org>>>
> > > <<lschulman at inta.org> <mailto:<lschulman at inta.org>>
> > > <mailto:<lschulman at inta.org> <mailto:<lschulman at inta.org>>>>,
> > > <philippe.fouquart at orange.com> <mailto:<philippe.fouquart at orange.com>>
> > > <mailto:<philippe.fouquart at orange.com>
> > > <mailto:<philippe.fouquart at orange.com>>>
> > > <<philippe.fouquart at orange.com> <mailto:<philippe.fouquart at orange.com>>
> > > <mailto:<philippe.fouquart at orange.com>
> > > <mailto:<philippe.fouquart at orange.com>>>>, <sdemetriou at verisign.com>
> > > <mailto:<sdemetriou at verisign.com>>
> > > <mailto:<sdemetriou at verisign.com>
> > > <mailto:<sdemetriou at verisign.com>>> <<sdemetriou at verisign.com>
> > > <mailto:<sdemetriou at verisign.com>>
> > > <mailto:<sdemetriou at verisign.com>
> > > <mailto:<sdemetriou at verisign.com>>>>, John McElwaine
> > > <<john.mcelwaine at nelsonmullins.com>
> > > <mailto:<john.mcelwaine at nelsonmullins.com>>
> > > <mailto:<john.mcelwaine at nelsonmullins.com>
> > > <mailto:<john.mcelwaine at nelsonmullins.com>>>>, Karen Day
> > > <<Karen.Day at sas.com>>
> > > CC: Brenda Brewer <<brenda.brewer at icann.org>
> > > <mailto:<brenda.brewer at icann.org>>
> > > <mailto:<brenda.brewer at icann.org>
> > > <mailto:<brenda.brewer at icann.org>>>>, <gnso-secs at icann.org>
> > > <mailto:<gnso-secs at icann.org>>
> > > <mailto:<gnso-secs at icann.org> <mailto:<gnso-secs at icann.org>>>
> > > <<gnso-secs at icann.org> <mailto:<gnso-secs at icann.org>>
> > > <mailto:<gnso-secs at icann.org> <mailto:<gnso-secs at icann.org>>>>, Zoe
> > > Bonython
> > > <<secretariat at icannregistrars.org>
> > > <mailto:<secretariat at icannregistrars.org>>
> > > <mailto:<secretariat at icannregistrars.org>
> > > <mailto:<secretariat at icannregistrars.org>>>>, Andrea Glandon
> > > <<andrea.glandon at icann.org> <mailto:<andrea.glandon at icann.org>>
> > > <mailto:<andrea.glandon at icann.org>
> > > <mailto:<andrea.glandon at icann.org>>>>, Sue
> > > Schuler <<secretariat at rysg.info> <mailto:<secretariat at rysg.info>>
> > > <mailto:<secretariat at rysg.info> <mailto:<secretariat at rysg.info>>>>
> > > Dear all,
> > > In order to service your travel needs for ICANN81Istanbulin a timely
> > > fashion, please submit your meeting database
> > > <tognso-secs at icann.org> <mailto:<tognso-secs at icann.org>>
> > > <mailto:<tognso-secs at icann.org> <mailto:<tognso-secs at icann.org>>>
> > > <mailto:<gnso-secs at icann.org> <mailto:<gnso-secs at icann.org>>
> > > <mailto:<gnso-secs at icann.org>
> > > <mailto:<gnso-secs at icann.org>>>>by*Thursday, 11 July 2024. *It is
> > > important all funded travel air booking is completed by due date
> > > given in ICANN Travel emails.
> > > Please share with all funded travelers, the travel support
> > > guidelines wiki space: <https://community.icann.org/x/lgvxAg>
> > > <<https://community.icann.org/x/lgvxAg>>
> > > <<https://community.icann.org/x/lgvxAg>
> > > <<https://community.icann.org/x/lgvxAg>>>
> > > <<https://community.icann.org/x/lgvxAg>
> > > <<https://community.icann.org/x/lgvxAg>>
> > > <<https://community.icann.org/x/lgvxAg>
> > > <<https://community.icann.org/x/lgvxAg>>>> and highlight the
> > > communications responsibilities section:
> > > ICANN Travel Support attempts to reach a supported traveler four
> > > times before deeming the supported traveler unresponsive:
> > > 1. ICANN Travel Support sends “welcome email.”
> > > 2. If there is no response after seven business days, ICANN Travel
> > > Support sends a second email, copying ICANN support staff.
> > > 3. If there is no response five business days after the second
> > > email,
> > > ICANN Travel Support sends a third email, copying ICANN support
> > > staff and the community group chair.
> > > 4. If there is no response five business days after the third email,
> > > ICANN Travel Support sends a fourth email, copying ICANN support
> > > staff and the community group chair.
> > > If there is no response three days after the fourth attempt to reach
> > > the supported traveler, the community group may substitute another
> > > traveler.
> > > 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.
> > > *TRAVEL BOOKING PROCESS*
> > > In order for Funded Travelers to start booking travel, they MUST
> > > complete Steps 1, 2, and 3.
> > > *WHO*
> > > *WHAT*
> > > 1
> > > Funded Traveler
> > > Register for meeting using the Funded Traveler Registration Link
> > > provided by ICANN Travel Support
> > > 2
> > > Funded Traveler
> > > Approved for Trade Regulations Review
> > > 3
> > > Funded Traveler
> > > Receive Travel Funding Confirmation Email from ICANN Travel Support
> > > 4
> > > *Funded Traveler*
> > > *Book Air Travel for meeting*
> > > *Approved dates of Arrival and Departure*
> > > *ARRIVAL DATE*
> > > *DEPARTURE DATE*
> > > *Friday, 08 November *
> > > *Friday, 15 November*
> > > For air, this must be booked using either via our online booking
> > > platform (Concur) or official travel agency (FCM). ICANN org does
> > > not allow self-booking.
> > > 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 and
> > > book by deadline given in email.
> > > 2.If you require a visa to enter the country, please make sure to
> > > acquire your visa immediately.Follow link here
> > > <<https://community.icann.org/x/fSfxAg>
> > > <<https://community.icann.org/x/fSfxAg>>
> > > <<https://community.icann.org/x/fSfxAg>
> > > <<https://community.icann.org/x/fSfxAg>>>> for assistance.
> > > 3.Wednesday, 25 September 2024*(45 days before travel)*is the last
> > > day to submit additions/replacements.
> > > 4.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.
> > > 5.If possible, please book direct travel requests. Detours and
> > > multi-stop trips are unfortunately not guaranteed.
> > > 6.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.
> > > 7.*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.
> > > Reminder:
> > > * 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 [<http://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=> <<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=>> <<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=> <<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> <mailto:<privacy at icann.org>>
> > > <mailto:<privacy at icann.org> <mailto:<privacy at icann.org>>>
> > > <mailto:<privacy at icann.org> <mailto:<privacy at icann.org>>
> > > <mailto:<privacy at icann.org> <mailto:<privacy at icann.org>>>>.
> > > * As a reminder, for the AGM meeting only, incoming Councilors get
> > > funding, as well as the then-incumbent Councilors.
> > > Many thanks for your cooperation!
> > > Thank you.
> > > Kind regards,
> > > Terri
> > > Policy Team Supporting the GNSO
> > > _______________________________________________
> > > NCSG-PC mailing list
> > > <NCSG-PC at lists.ncsg.is>
> > > <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> > > <<https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
> > > <<https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> > > <<https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>>
> > >
> > _______________________________________________
> > NCSG-EC mailing list
> > <NCSG-EC at lists.ncsg.is>
> > <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240621/66d87d68/attachment-0001.htm>
More information about the NCSG-EC
mailing list