[council] Relocating ICANN57 - Blog by Akram Atallah
Phil Corwin
psc at vlaw-dc.com
Wed May 18 13:47:27 UTC 2016
The shifting of the meeting schedule has created a challenge for those of us who are members of INTA leadership. The INTA Leadership meeting starts on Tuesday, November 15th in Florida, just six days after the conclusion of the ICANN meeting on November 9th. Given the distance, even leaving Hyderabad on the 10th may not get one home to the U.S. until Friday the 11th, giving just three non-travel days before departure for INTA. So I may have to opt out of any strategy session that would cut that interval even shorter.
I've also received communications noting that the new dates mean that U.S. participants will be out of the country on our election day.
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
-----Original Message-----
From: Carlos Raúl Gutiérrez G. [mailto:crg at isoc-cr.org]
Sent: Wednesday, May 18, 2016 7:34 AM
To: Mary Wong
Cc: Phil Corwin; James M. Bladel; GNSO Council List
Subject: Re: [council] Relocating ICANN57 - Blog by Akram Atallah
Thank you Mary!
2 questions
will the GNSO have its traditional preliminary session? previously Saturday-Friday before the meeting will the GNSO have its traditional strategy session afterwards?
previously Friday after the meeting
Best regards
Carlos Raúl Gutiérrez
+506 8837 7176
Skype: carlos.raulg
Current UTC offset: -6.00 (Costa Rica)
On 18 May 2016, at 3:35, Mary Wong wrote:
> Hello Phil and everyone,
>
> As the ICANN57 meeting in Hyderabad will be the first iteration of
> “Meeting C” under the new ICANN meeting strategy, incorporating (among
> other things) two Public Forums and spanning 7 days, presumably the
> Council will need to begin discussions on how and when best to
> schedule the GNSO working sessions and the Council meeting and wrap up
> so as to maximize the opportunities for interaction presented by the
> Meeting C format. As such, staff will make a note to ensure that this
> topic is included on the agenda of one of the forthcoming Council
> meetings.
>
> Thanks for highlighting the possible change!
>
> Cheers
> Mary
>
>
> Mary Wong
> Senior Policy Director
> Internet Corporation for Assigned Names and Numbers (ICANN)
> Email: mary.wong at icann.org
> Telephone: +1-603-5744889
>
>
> From: <owner-council at gnso.icann.org> on behalf of Phil Corwin
> <psc at vlaw-dc.com>
> Date: Wednesday, May 18, 2016 at 04:44
> To: "James M. Bladel" <jbladel at godaddy.com>, GNSO Council List
> <council at gnso.icann.org>
> Subject: [council] RE: Relocating ICANN57 - Blog by Akram Atallah
>
> Councilors:
>
> November 3rd is a Thursday, rather than the usual Opening Ceremony day
> of Monday. I am guessing this means that the usual advance Council
> meeting will occur Tuesday-Wednesday.
>
> Best, Philip
>
> 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 at gnso.icann.org
> [mailto:owner-council at gnso.icann.org] On Behalf Of James M. Bladel
> Sent: Tuesday, May 17, 2016 3:26 PM
> To: GNSO Council List
> Subject: [council] Fwd: Relocating ICANN57 - Blog by Akram Atallah
>
> Councilors, FYI.
>
> Sent via iPhone. Blame Siri.
>
>
> Begin forwarded message:
> From: David Olive
> <david.olive at icann.org<mailto:david.olive at icann.org>>
> Date: May 17, 2016 at 21:13:35 GMT+2
> To: "jbladel at godaddy.com<mailto:jbladel at godaddy.com>"
> <jbladel at godaddy.com<mailto:jbladel at godaddy.com>>,
> "katrina at nic.lv<mailto:katrina at nic.lv>"
> <katrina at nic.lv<mailto:katrina at nic.lv>>,
> "oscar at lacnic.net<mailto:oscar at lacnic.net>"
> <oscar at lacnic.net<mailto:oscar at lacnic.net>>,
> "louie at louie.net<mailto:louie at louie.net>"
> <louie at louie.net<mailto:louie at louie.net>>,
> "patrik at frobbit.se<mailto:patrik at frobbit.se>"
> <patrik at frobbit.se<mailto:patrik at frobbit.se>>,
> "Thomas.Schneider at bakom.admin.ch<mailto:Thomas.Schneider at bakom.admin.ch>"
> <Thomas.Schneider at bakom.admin.ch<mailto:Thomas.Schneider at bakom.admin.c
> h>>, "alan.greenberg at mcgill.ca<mailto:alan.greenberg at mcgill.ca>"
> <alan.greenberg at mcgill.ca<mailto:alan.greenberg at mcgill.ca>>,
> "tsinha at umd.edu<mailto:tsinha at umd.edu>"
> <tsinha at umd.edu<mailto:tsinha at umd.edu>>,
> "bverd at verisign.com<mailto:bverd at verisign.com>"
> <bverd at verisign.com<mailto:bverd at verisign.com>>,
> "gregshatanipc at gmail.com<mailto:gregshatanipc at gmail.com>"
> <gregshatanipc at gmail.com<mailto:gregshatanipc at gmail.com>>,
> "Michele at blacknight.com<mailto:Michele at blacknight.com>"
> <Michele at blacknight.com<mailto:Michele at blacknight.com>>,
> "pdiaz at pir.org<mailto:pdiaz at pir.org>"
> <pdiaz at pir.org<mailto:pdiaz at pir.org>>,
> "ncsg at tapani.tarvainen.info<mailto:ncsg at tapani.tarvainen.info>"
> <ncsg at tapani.tarvainen.info<mailto:ncsg at tapani.tarvainen.info>>,
> "rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>"
> <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>,
> "rudi.vansnick at isoc.be<mailto:rudi.vansnick at isoc.be>"
> <rudi.vansnick at isoc.be<mailto:rudi.vansnick at isoc.be>>,
> "tonyarholmes at btinternet.com<mailto:tonyarholmes at btinternet.com>"
> <tonyarholmes at btinternet.com<mailto:tonyarholmes at btinternet.com>>,
> "cwilson at 21cf.com<mailto:cwilson at 21cf.com>"
> <cwilson at 21cf.com<mailto:cwilson at 21cf.com>>,
> "mcknight.glenn at gmail.com<mailto:mcknight.glenn at gmail.com>"
> <mcknight.glenn at gmail.com<mailto:mcknight.glenn at gmail.com>>,
> "hilaliaziz at yahoo.fr<mailto:hilaliaziz at yahoo.fr>"
> <hilaliaziz at yahoo.fr<mailto:hilaliaziz at yahoo.fr>>,
> "hcarrascob at gmail.com<mailto:hcarrascob at gmail.com>"
> <hcarrascob at gmail.com<mailto:hcarrascob at gmail.com>>,
> "ocl at gih.com<mailto:ocl at gih.com>" <ocl at gih.com<mailto:ocl at gih.com>>,
> "siranush_vardanyan at hotmail.com<mailto:siranush_vardanyan at hotmail.com>"
> <siranush_vardanyan at hotmail.com<mailto:siranush_vardanyan at hotmail.com>
> >
> Cc: Global Leadership
> <global_leadership at icann.org<mailto:global_leadership at icann.org>>,
> Melissa King <melissa.king at icann.org<mailto:melissa.king at icann.org>>,
> Duncan Burns <duncan.burns at icann.org<mailto:duncan.burns at icann.org>>,
> Nick Tomasso <nick.tomasso at icann.org<mailto:nick.tomasso at icann.org>>
> Subject: Relocating ICANN57 - Blog by Akram Atallah Dear Community
> Leaders:
> This blog will be posted to the ICANN website in a few hours.
> We are sharing this note with you in advance of the public
> announcement.
> Please do not circulate this information until after it is posted (
> 0100 UTC 18 May /1800 PST, 17 May)
> Best regards,
> David
> —————————————————————-
> Relocating ICANN57
> By Akram Atallah
> Earlier this year, we announced that ICANN56 was going to be
> relocated from Panama City, Panama, to Helsinki, Finland, due to
> concerns related to the Zika virus. Following a great deal of internal
> debate and discussion, and taking into consideration the continued
> spread of Zika, we have decided that we will be relocating ICANN57
> from San Juan, Puerto Rico, to Hyderabad, India. Due to highly limited
> space availabilities, this relocation has necessitated changing the
> date of the meeting from 29 October – 4 November 2016, to 3 – 9
> November 2016.
> We did not arrive at this decision easily. We would much rather
> remain in Puerto Rico – the excellent location we had originally
> chosen. Moving the meeting venue creates a lot of additional work and
> challenges, and we understand and recognize that moving an ICANN
> meeting affects many groups within the community. However, we have
> come to the conclusion that we must postpone going to Puerto Rico
> after a lengthy discussion with and feedback from SO/AC leaders, the
> Board, and within our management team. This decision was based on
> available research and information and the fact that Puerto Rico has
> declared a state of emergency due to the ongoing Zika virus outbreak.
> We believe that the Zika virus poses a significant enough threat that
> we need to postpone going to Puerto Rico for the health and safety of
> our community and our ICANN team, just as we had to postpone ICANN52
> and relocate from Marrakech to Singapore due to the Ebola virus
> outbreak in 2014.
> Choosing a location for an ICANN meeting that meets the needs of the
> community is an incredibly complex task. Few venues in the world are
> able to satisfy all of our
> requirements<https://meetings.icann.org/en/host>, especially as the
> community continues to grow and more and more sessions are held in
> parallel. San Juan offered outstanding facilities capable of hosting a
> successful ICANN meeting, which is why we originally selected it as
> the location for ICANN57. In choosing an alternate location for
> ICANN57, we explored options all around the globe. A North American
> venue would have been our preference given our meeting rotation
> schedule, but due to the time of the year, a very busy conference
> season and our extremely demanding requirements, we weren’t presented
> with any ideal options. Fortunately, the Government of India offered
> to host ICANN57. We are very grateful for their proposal and their
> willingness to meet our extensive requirements in such a short amount
> of time.
> We are therefore pleased to announce that ICANN57 will be held at the
> Hyderabad International Convention Centre<http://www.hicc.com/>, a
> state-of-the-art convention center capable of handling an ICANN
> meeting’s extensive conference space and network infrastructure
> requirements. Hyderabad itself is home to a booming tech sector,
> earning itself the nickname “Cyberabad,” and we’re looking forward to
> hosting a successful ICANN meeting in this wonderful city.
> We fully understand that by relocating ICANN57, regional
> organizations and stakeholders will miss out on an opportunity to meet
> with their communities, as well as a chance to reach out to new
> community members. We are postponing not cancelling this meeting and
> we will return to the region as soon as possible.
> ICANN’s Global Stakeholder Engagement (GSE) team will be working
> closely with the leaders of the different stakeholder groups in the
> region to try to mitigate the impact of this decision. We will be
> providing our increased support to meetings and events scheduled in
> the region, remote hubs in the region’s strategic points during the
> next two ICANN meetings, read-out sessions, capacity building
> webinars, activities in our Montevideo engagement center, support for
> our community to attend relevant regional and global events, and
> providing as much senior management and Board support on the ground as
> required.
> I want to stress again that the decision to relocate ICANN57 was not
> made lightly, and that we feel it is extremely unfortunate the
> situation required us to postpone the meeting in San Juan. We
> understand how important it is to maintain the global rotation of
> ICANN meetings, as it allows local and regional communities to attend
> and participate, and we are committed to returning to Puerto Rico and
> Panama City as soon as possible, however the welfare of community
> members and staff is our top priority.
> We thank you all for understanding this difficult situation and the
> choice we have had to make.
> ———————————————
>
> David A. Olive
> Senior Vice President, Policy Development Support General Manager,
> ICANN Regional Headquarters –Istanbul Hakki Yeten Cad. Selenium Plaza
> No:10/C K:10 34349 Fulya, Besiktas, Istanbul Internet Corporation for
> Assigned Names and Numbers (ICANN)
>
> Direct Line: +90.212.999.6212
> Mobile: + 1. 202.341.3611
> Mobile: +90.533.341.6550
> Email: david.olive at icann.org<mailto:david.olive at icann.org>
> www.icann.org<http://www.icann.org>
>
> ________________________________
> No virus found in this message.
> Checked by AVG - www.avg.com<http://www.avg.com>
> Version: 2016.0.7497 / Virus Database: 4568/12245 - Release Date:
> 05/16/16
More information about the council
mailing list