<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] [Soac-infoalert] ICANN57 Hyderabad: What You Need to Know (Part 2) - ICANN
Dear All,
Please see the response from the Meeting Team responsible for Hotel Support to
the issue that Heather raised:
The email appears to be a generated standard email that is sent to funded
travelers and not one unique to ICANN Hyderabad. The process to provide hotel
confirmations would usually take as long, but we have taken great measures to
ensure hotel confirmations for Hyderabad will be provided in a timely manner.
The goal is to have them all distributed by the end of the month (August 31).
Thank you and we will keep you informed.
Kind regards,
Glen
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On
Behalf Of Amr Elsadr
Sent: Wednesday, August 24, 2016 1:03 PM
To: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
Cc: Heather Forrest <Heather.Forrest@xxxxxxxxxx>; Phil Corwin
<psc@xxxxxxxxxxx>; Rubens Kuhl <rubensk@xxxxxx>; James M. Bladel
<jbladel@xxxxxxxxxxx>; GNSO Council List <council@xxxxxxxxxxxxxx>
Subject: Re: [council] [Soac-infoalert] ICANN57 Hyderabad: What You Need to
Know (Part 2) - ICANN
Hi,
Not exactly. Both reservations are usually from the same hotel. Sometimes, the
earlier one for visa purposes is just a letter from the hotel with a long list
of ICANN-funded travelers, letting the embassy know these folks (including the
applicant) are staying there.
Thanks.
Amr
Sent from mobile
On Aug 24, 2016, at 11:53 AM, Volker Greimann
<vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>> wrote:
So they are asking us to lie in our visa application about where we will be
staying? That is going to go down well if caught...
Best,
Volker
Am 24.08.2016 um 11:16 schrieb Amr Elsadr:
Hi Heather,
In my experience, Constituency Travel provides hotel reservations solely for
the purpose of visa acquisition at a time early enough to apply for one.
At a later time, they provide the actual confirmed reservation details for the
hotel in which we should be staying.
It works. At least I've never had a problem because of this. You may want to
confirm this with CT yourself.
Hope this helps.
Thanks.
Amr
Sent from mobile
On Aug 24, 2016, at 5:40 AM, Heather Forrest
<Heather.Forrest@xxxxxxxxxx<mailto:Heather.Forrest@xxxxxxxxxx>> wrote:
Colleagues,
Following up on Phil's point below about timely notification of hotel, I noted
with some alarm the following in the standard email we all received from ICANN
travel this week (see highlighted bit below). What can we do about this? The
Council table will be pretty empty if this is indeed what will happen.
Best wishes,
Heather
TRAVEL BOOKING:
AIR:
Primary contact for booking air travel reservations:
FCM: galaxy@xxxxxx.travel<mailto:galaxy@xxxxxx.travel>
ICANN: constituency-travel@xxxxxxxxx<mailto:constituency-travel@xxxxxxxxx> or
via private fax at +1-310-578-8652.
Air Self-booking: You must receive approval from ICANN prior to making your
self-arranged trip. Please notify ICANN in writing and prior to booking at
constituency-travel@xxxxxxxxx<mailto:constituency-travel@xxxxxxxxx>.
HOTEL:
Hotel confirmations (if supported) will be provided one week before the meeting.
Hotel extensions: If you plan on extending your travel, before or after your
approved dates of arrival and departure and want to stay at the same ICANN
hotel, please let us know by Friday, October 7, 2016, 17:00 UTC. We will do our
best to accommodate your request based on the hotel’s availability.
Kindly note that you will be financially responsible for any additional days of
travel before or after your approved dates, including hotel and living
allowances.
MISC. OTHER:
If you have any change in your banking details, please re-submit a completed
Travel Vendor Form via: https://travelrequestform.icann.org/
If there are any last minute changes, if you cannot travel due to illness,
personal or professional events, you MUST contact ICANN Constituency Travel at
constituency-travel@xxxxxxxxx<mailto:constituency-travel@xxxxxxxxx>
________________________________
From: owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>
<owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>> on behalf
of Phil Corwin <psc@xxxxxxxxxxx<mailto:psc@xxxxxxxxxxx>>
Sent: Thursday, August 18, 2016 2:19:41 AM
To: Rubens Kuhl; James M. Bladel
Cc: GNSO Council List
Subject: RE: [council] [Soac-infoalert] ICANN57 Hyderabad: What You Need to
Know (Part 2) - ICANN
That looks like a significant impediment to getting the required visa.
I’ll be making my own flight arrangements so no issue there.
But we all need ICANN Travel to tell us by the end of this month what hotel
Councilors will be placed in. We simply can’t wait until the week or two before
the meeting starts if we are to secure the required visa.
Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/Cell
Twitter: @VlawDC
"Luck is the residue of design" -- Branch Rickey
From: owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Rubens Kuhl
Sent: Wednesday, August 17, 2016 12:10 PM
To: James M. Bladel
Cc: GNSO Council List
Subject: Re: [council] [Soac-infoalert] ICANN57 Hyderabad: What You Need to
Know (Part 2) - ICANN
Considering both hotel and flight information is required for the Conference
Visa, and Constituency Travel usually defines the hotel just a week before the
conference, this edition will likely be a lot of fun for councillors relying on
ICANN funding.
Rubens
Em 17 de ago de 2016, à(s) 12:29:000, James M. Bladel
<jbladel@xxxxxxxxxxx<mailto:jbladel@xxxxxxxxxxx>> escreveu:
Council Colleagues -
Please note the announcement & blog post below. In most cases, attendees will
need a “Conference Visa” for ICANN57 Hyderabad, and an “eTourist" Visa may not
be accepted for entry to India. ICANN has also provided a link to request an
Invitation Letter.
Thanks—
J.
From:
<soac-infoalert-bounces@xxxxxxxxx<mailto:soac-infoalert-bounces@xxxxxxxxx>> on
behalf of David Olive <david.olive@xxxxxxxxx<mailto:david.olive@xxxxxxxxx>>
Date: Wednesday, August 17, 2016 at 8:55
Subject: [Soac-infoalert] ICANN57 Hyderabad: What You Need to Know (Part 2) -
ICANN
https://www.icann.org/news/blog/icann57-hyderabad-what-you-need-to-know-part-2
? Author: Nick Tomasso | Vice President, Meetings
Further to my
blog<https://www.icann.org/news/blog/icann57-hyderabad-what-you-need-to-know>
on 25 July 2016, I would like to share details on visa applications to assist
all who are attending ICANN57 Annual General Meeting in Hyderabad with your
travel planning.
We have worked extensively with the India government to ensure a clear and
smooth process for all Indian visa applications. They have also assured us that
all ICANN57 visa applications will be treated as priority.
All delegates requiring visas to India should visit
here<http://www.mea.gov.in/indian-missions-abroad.htm> to find the nearest
India diplomatic mission to apply for your visa. You must apply for a
Conference Visa. Please refer to the
guide<https://meetings.icann.org/en/hyderabad57/visa-application-guide-india>
we have put together for reference. Apply early as the process could take up to
two weeks. You will also need invitation
letters<https://invitationletters.icann.org/> from ICANN and the local host,
which may take another two weeks to generate.
Do take note that the e-Tourist Visa will not be applicable for our ICANN
meeting. Any traveler trying to enter India with the e-Tourist Visa may be
denied entry. If you have an existing valid Business Visa, you need not apply
for the Conference Visa.
We have set up a dedicated email
(icann57visasupport@xxxxxxxxx)<mailto:icann57visasupport@xxxxxxxxx%29> that you
can contact should you need any further clarification about the visa.
Remember to
register<https://registration.icann.org/register.php?id=Hyderabad57> for
ICANN57 and check our meeting site<https://meetings.icann.org/en/hyderabad57>
for regular updates. Lastly, don't forget to attend the webinar on 7 September
2016 (1500 UTC) where we will share more information on ICANN57, logistics,
accommodations and travel. Look out for our announcement and join us then.
Sent from my iPhone
David A. Olive
Senior Vice President, Policy Development Support
General Manager, ICANN Regional Headquarters –Istanbul
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7752 / Virus Database: 4633/12811 - Release Date: 08/15/16
--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>
Web: www.key-systems.net<http://www.key-systems.net> /
www.RRPproxy.net<http://www.RRPproxy.net>
www.domaindiscount24.com<http://www.domaindiscount24.com> /
www.BrandShelter.com<http://www.BrandShelter.com>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>
www.twitter.com/key_systems<http://www.twitter.com/key_systems>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu<http://www.keydrive.lu>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen
Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder
Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht
nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder
telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>
Web: www.key-systems.net<http://www.key-systems.net> /
www.RRPproxy.net<http://www.RRPproxy.net>
www.domaindiscount24.com<http://www.domaindiscount24.com> /
www.BrandShelter.com<http://www.BrandShelter.com>
Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>
www.twitter.com/key_systems<http://www.twitter.com/key_systems>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu<http://www.keydrive.lu>
This e-mail and its attachments is intended only for the person to whom it is
addressed. Furthermore it is not permitted to publish any content of this
email. You must not use, disclose, copy, print or rely on this e-mail. If an
addressing or transmission error has misdirected this e-mail, kindly notify the
author by replying to this e-mail or contacting us by telephone.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|