ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] [Soac-infoalert] ICANN57 Hyderabad: What You Need to Know (Part 2) - ICANN

  • To: Phil Corwin <psc@xxxxxxxxxxx>, Rubens Kuhl <rubensk@xxxxxx>, "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Subject: Re: [council] [Soac-infoalert] ICANN57 Hyderabad: What You Need to Know (Part 2) - ICANN
  • From: Heather Forrest <Heather.Forrest@xxxxxxxxxx>
  • Date: Wed, 24 Aug 2016 03:40:11 +0000
  • Accept-language: en-US
  • Cc: GNSO Council List <council@xxxxxxxxxxxxxx>
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=myacu.onmicrosoft.com; s=selector1-acu-edu-au; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=n9LyI2btlWcFVosq5PPQ2gv4lMn00nLkZPjoWtGcDok=; b=Kh1U+pIn+w54y50ZZCat7uYmyV5lqSHIGI3NJVyCie2OPQkulCP4JlXUJy5YI9BqZ5Dz5eRniGCirR9tMtF9Btm90BRBTmXaj18DtBxE1+TpIZ2Fasia6VZTs4V9JH68Z+IWa0Mia/9YFEwnHZtdl571K4X3sQVdeBKi5VsdT0c=
  • In-reply-to: <8E84A14FB84B8141B0E4713BAFF5B84E211F2B40@Exchange.sierracorporation.com>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <E80E8B2C-52D1-4FC6-B150-197ADF43D13F@icann.org> <D3D9EC19.D126F%jbladel@godaddy.com> <D3D9ECD3.D1275%jbladel@godaddy.com> <EDE2DC0F-AB0F-4F3E-8047-180DF5CB5608@nic.br>,<8E84A14FB84B8141B0E4713BAFF5B84E211F2B40@Exchange.sierracorporation.com>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
  • Thread-index: AQHR+Jw4H2Vbf/55lkyxuj9xEoqkqqBNUn0AgAACm4CACiue6Q==
  • Thread-topic: [council] [Soac-infoalert] ICANN57 Hyderabad: What You Need to Know (Part 2) - ICANN

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 <owner-council@xxxxxxxxxxxxxx> on behalf of 
Phil Corwin <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] 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)> 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


<<< Chronological Index >>>    <<< Thread Index >>>