[NCSG-EC] Fwd: [ICANN Community Leaders] UPDATE: ICANN67 Cancun - Coronavirus (2019-nCOV)

Sat Feb 15 01:23:52 EET 2020

Same feeling here: a bit of an overreaction.

Bit with him mentioning 11 (not confirmed) in Brazil, I will be friendless
at this quarantine.

Em sex, 14 de fev de 2020 20:17, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> escreveu:

> Thanks Robin, for your quick response!  I will let them know you are
> replacing me.
>
> I do think there seems to be a bit of an over-reaction to this thing, but
> the thought of the "cruise ship" scenario which he describes, where we
> would be quarantined in an ICANN meeting for a couple of weeks is
> definitely nightmarish enough to capture my attention....:-P
>
> Let me know if you don't get the invitation to the meeting....cheers and
> thanks, Steph
> On 2020-02-14 18:14, Robin Gross wrote:
>
> I could make this call to cover for you, Steph.
>
> Thanks,
> Robin
>
> On Feb 14, 2020, at 3:12 PM, Stephanie Perrin via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
>
> Hi folks, I cannot take this call as I am in a meeting in London at that
> time.  Could I get a volunteer from the NCSG EC  to cover for me?
> Thanks.
> Steph
>
> -------- Forwarded Message --------
> Subject: [ICANN Community Leaders] UPDATE: ICANN67 Cancun - Coronavirus
> (2019-nCOV)
> Date: Fri, 14 Feb 2020 23:03:39 +0000
> From: Goran Marby <goran.marby at icann.org> <goran.marby at icann.org>
> To: so-ac-sg-cleaders at icann.org <so-ac-sg-cleaders at icann.org>
> <so-ac-sg-cleaders at icann.org>
> CC: Cassia Oliveira <cassia.oliveira at icann.org>
> <cassia.oliveira at icann.org>
>
> Cassia Oliveira on behalf of Goran Marby
>
>
> Dear Community Leaders and Representatives:
>
>
> Thank you for your prompt responses to my last email enquiring about your
> Community  members’ thoughts regarding travel to Cancun for ICANN67.
>
> Many of you have asked for more information about how we are assessing the
> situation. I’d like to hold a call with you to discuss the matter in
> detail, and propose that we hold the call this coming *Tuesday, 18
> February at 17:00 UTC.* A calendar invitation will follow shortly.
>
>
> In the meantime, I’d like to share with you what we know about the
> situation today.
>
>
> ICANN Org has convened a crisis management team to monitor the global
> situation related to the COVID-19 coronavirus and assess how it may impact
> the important work of the ICANN community, Board, and Org. To help you
> prepare for the call on Tuesday, I’d like to share what we know about the
> situation today.
>
>    - As of 13 February, the World Health Organization (WHO) reports there
>    are more than 60,000 confirmed cases in 25 countries. Approximately 450 of
>    those cases are outside China.
>    - At the time of this writing, there are no confirmed cases anywhere
>    in the LAC region.
>       - Mexico’s Ministry of Health is monitoring and testing two
>       suspected cases, one in Mexico City (800 miles from Cancún) and one in
>       Nuevo Leon (900 miles from Cancún). All 12 previously suspected cases in
>       Mexico tested negative and were cleared.
>       - The Brazilian Ministry of Health is currently monitoring and
>       testing 11 newly suspected cases.
>    - The incubation period for the virus is still unknown, and has ranged
>    from five days to 24 days.
>    - Once suspected, testing for the virus can take up to 14 days.
>    - As a result of the outbreak the GSMA Board
>    <https://www.businesswire.com/news/home/20200212005755/en/GSMA-Statement-MWC-Barcelona-2020-John-Hoffman>
>     has cancelled the Mobile World Congress in Barcelona, Spain; and
>    Cisco Australia has cancelled
>    <https://www.crn.com.au/news/cisco-live-cancelled-due-to-coronavirus-537916>
>     its Cisco Live event, scheduled for 3-6 March in Melbourne,
>    Australia. (We note that APRICOT2020/APNIC49 in Melbourne has not been
>    cancelled.)
>
>
> As we consider the potential impact for going ahead with ICANN67 as
> planned, we are closely monitoring a variety of factors, such as:
>
>    - The development of confirmed cases in Cancún.
>    - The ability of health authorities in Mexico to effectively mitigate
>    and respond to a case or outbreak. Examples:
>       - Clear testing and quarantine protocols, and determination of
>       whether patients can be managed in Cancún or must be transferred elsewhere.
>       - Concern over sufficiency of travel restrictions or health
>       screenings for travelers coming from affected countries.
>    - ICANN meetings are attended by contractors and participants from
>    more than 150 countries. With cases in at least 25 of those countries,
>    there is a risk of bringing the virus to Cancún and into the ICANN meeting
>    site.
>    - The potential a member of the Org presenting COVID-19 symptoms,
>    raising concerns that they may have potentially infected colleagues
>    scheduled to attend ICANN67.
>    - The potential of an attendee contracting the virus in Mexico, and
>    inadvertently bringing the virus back to their home country, organization,
>    and family.
>    - The risk of a “cruise ship” scenario in which a suspected or
>    confirmed case is identified during the meeting, necessitating the
>    mass-quarantine of all attendees and locals.
>    - Discrimination or harassment against any attendee perceived to come
>    from affected countries or regions (i.e., racial or ethnic stereotyping).
>
>
> I understand that this is short notice for a call. If you cannot make it
> to the call, I hope that you will forward the call information to your
> vice-chair or your designee.
>
>
> Thank you for your understanding. I look forward to our discussion and
> your feedback, which will enable ICANN org to make the best decision we
> possibly can, in the collective interests of our Board, staff and community.
>
>
> Best regards,
>
>
> Göran  Marby
> President & CEO ICANN
> +1(310) 578 8690
>
>
> Cássia Oliveira
> Sr. Manager, Office of the President & CEO
> cassia.oliveira at icann.org
> +1(310) 578 8656
>
>
> --> <Attached Message Part.txt>
> _______________________________________________
> 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/20200214/2df58e9e/attachment.htm>