Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver

Mary B <mary.h.barnes@gmail.com> Tue, 25 February 2020 14:49 UTC

Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4BB33A0E2C for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2020 06:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lKpabCCLZjDL for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2020 06:49:24 -0800 (PST)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 034A73A0EA1 for <ietf@ietf.org>; Tue, 25 Feb 2020 06:49:24 -0800 (PST)
Received: by mail-io1-xd2f.google.com with SMTP id e7so4302805ioe.13 for <ietf@ietf.org>; Tue, 25 Feb 2020 06:49:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j/iya8XSXwhIJdiUtkghfSkwIvJSP35sq8NvZSO4qbg=; b=hWIqlIh9SxRQhFOTrBQTyn21hUNT/l9nL5UsIxdocMrdOSHIAmjUuOuc4Kv1/9Qo8x 80SPw8gngqt03Yb78uupkHtCmEKh7qiHUB7/Xy6dGxe4S7/gOz26eIKBsXRO5NOQ8Oyn G/Dyn5Qz7wy3sBR0N3xC07wKXWQsJ8HyvqeaptgBsGMHOZHXNIns8RKku1+L7AOgASI8 jTYdSo2j32qzkkNGfAwx1hEi8+n7ThKZV9uypFDTTzmyUG1oA5IbYUj5KOw1hJsgGzlW g/wtT03P7iSMzf0YkEEWgDj4hEGVRYIRVaH4iLyKjC7Oi8d4h/ekLtSzUf1JT0ySXWS7 iIdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j/iya8XSXwhIJdiUtkghfSkwIvJSP35sq8NvZSO4qbg=; b=SqqT29W3n+v0GWIKD95tf6FZ+SvKhiIs5sl7C6OstkN4pl4mvP2HS06fc3RrwTbzcc Q2ca9rULf9Rh646TzeFt8MpiThNoWtvM3rFk6cSxswjyzMArX1cDyZr2UMnky8tp/24+ eVvdLekU1XMiU+T09G7F933pnDkFMJ1VG2hyCMkEpbN9rs2wTOYLCHk8KI8BKfQUdM8z CqBKddLzc4v83LGurSE5f+KQeVbX1/JXvqmG8Y7oiqcKUBXL6cYeoLIm26UieM+miEnt JBeZ6OoQrDUW5bULiUNQmJNCcZXZx0hpjXchXbSb4TAA/CLpz4B5ti8UmwwV0oBrh1Da vyXw==
X-Gm-Message-State: APjAAAWPlcaco+HtGURg+lbKGKGtwoQ8tTWguUluH3gUL76JEy06rVbE V58iA1TMWjt8BJiUglGcvpRRMff+AOumHf24xys=
X-Google-Smtp-Source: APXvYqxwSgdW9T4sHiBkG7xntyv2KYDOkZ0UUBeQ48Im0d5qW5fK3QJI9u8lr/eSGoYViO+Hi3S5I+ioS+oF7EWILiQ=
X-Received: by 2002:a05:6638:a4a:: with SMTP id 10mr59386540jap.44.1582642163257; Tue, 25 Feb 2020 06:49:23 -0800 (PST)
MIME-Version: 1.0
References: <158258721017.24319.9082233711977122647.idtracker@ietfa.amsl.com> <huvor7s4wdpy5cgqtxgx1v4k.1582587718389@email.android.com> <253b29f1-f11f-92da-855c-9ac3b01e76a3@gmail.com> <CABmDk8=AiGQX71yDxuVYt4+GESpfWFW5+WyC_Pd3V+zXZ8d1nw@mail.gmail.com> <a91e7a44-b7f3-fdae-5c97-7b5ac8791a00@gmail.com>
In-Reply-To: <a91e7a44-b7f3-fdae-5c97-7b5ac8791a00@gmail.com>
From: Mary B <mary.h.barnes@gmail.com>
Date: Tue, 25 Feb 2020 08:49:12 -0600
Message-ID: <CABmDk8kbrRWMces4-YDa1TH6f9sJaVSg-10LO1hiQ2rzMT3+EQ@mail.gmail.com>
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f29674059f67972a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KEKZwbpqx-Gib4Q_VjWy3oGz2lI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2020 14:49:32 -0000

And, you know that how?    AFAIK, these numbers are based on confirmed,
positive tests.

On Tue, Feb 25, 2020 at 8:44 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

> the numbers are much higher than the Authority reports in France
>
> Le 25/02/2020 à 15:43, Mary B a écrit :
> > For people that are worried, you can follow the situation (based on real
> > reported numbers) here:
> > http://ncov.bii.virginia.edu/dashboard/
> >
> > Johns Hopkins has something similar but their's wasn't updated the last
> > I looked.
> >
> > Regards,
> > Mary.
> >
> > On Tue, Feb 25, 2020 at 7:14 AM Alexandre Petrescu
> > <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
> wrote:
> >
> >     These are my thoughts:
> >
> >     - has the situation improved since we last talked about this?
> >
> >     - have we absorbed the biggest?
> >
> >     - ...
> >
> >     Alex
> >
> >     Le 25/02/2020 à 00:41, Arleen Elliott a écrit :
> >      > Thoughts
> >      >
> >      >
> >      > -------- Original Message --------
> >      > Subject: Further update on COVID-19 (Coronavirus) and IETF 107
> >     Vancouver
> >      > From: IETF Executive Director <exec-director@ietf.org
> >     <mailto:exec-director@ietf.org>>
> >      > Date: Feb 24, 2020, 6:34 PM
> >      > To: IETF Announcement List <ietf-announce@ietf.org
> >     <mailto:ietf-announce@ietf.org>>
> >      > As IETF 107 Vancouver approaches we thought it would be useful to
> >     update
> >      > you on our planning around COVID-19 (Coronavirus) and the
> potential
> >      > impact on this meeting.
> >      >
> >      > Before that, it is worth noting that registrations for the
> >     meeting are
> >      > at a good level [1] and continue to grow in line with
> expectations.
> >      >
> >      > Our policy regarding the risk to health posed by COVID-19 is that
> we
> >      > will follow public health guidelines for events of this nature, in
> >      > particular those of the World Health Organisation [2] and the
> Public
> >      > Health Agency of Canada [3].  Neither of those bodies recommend
> >      > cancelling meetings of this nature but they do recommend some
> >     specific
> >      > planning [4] and we are following those recommendations.
> >      >
> >      > Accordingly, the following special measures are being put into
> >     place for
> >      > IETF 107 in Vancouver.
> >      >
> >      > 1. Measures to prevent transmission by surface contact:
> >      > - We will provide all in-person participants with hand sanitizer
> and
> >      > surface wipes free of charge.
> >      > - Surface wipes will be available in multiple rooms for cleaning
> any
> >      > shared equipment or surfaces, such as microphones and door
> handles.
> >      > - We are exploring changes to blue sheets, including online
> >      > alternatives, rather than pass a sheet and pen around.
> >      > - We’re going to ask that you do not feel obliged to shake hands
> >     with
> >      > anyone and also do not feel offended if anyone declines to do so.
> >      > - Buses for the social event (which is still being planned) will
> >     leave
> >      > at staggered intervals and also have wipes available.
> >      >
> >      > 2.  Measures for anyone who feels unwell to prevent them spreading
> >      > infection:
> >      > - We are setting aside a room as an isolation room supplied with
> >     masks
> >      > and a thermometer for anyone who feels ill during the meeting.
> >      > - We are making arrangements with a local clinic so that we can
> >     call a
> >      > doctor to attend to anyone in self-imposed isolation to minimise
> >     their
> >      > travel through communal areas.
> >      >
> >      > 3.  Voluntary travel guidelines for travellers from China (the
> >     meeting
> >      > host, Huawei, is discussing this topic with other companies based
> >     in China):
> >      > - Only staff from provinces where travel is allowed and on a
> >     whitelist
> >      > of those who have had their health monitored for a number of
> >     weeks will
> >      > participate in-person at the meeting.
> >      > - Some in-person participants, including the Huawei employees
> >     based in
> >      > China, plan to arrive 7 days early, monitoring any symptoms before
> >      > attending the meeting.
> >      > - The number of in-person participants will be reduced to
> essential
> >      > travellers with the rest participating remotely.
> >      >
> >      > 4.  (As previously advised) Changes to our cancellation policy
> >      > - Anyone who is unable to attend due to government imposed travel
> >      > restrictions will be eligible for a full refund.
> >      > - We will continue with the normal policy of providing a full
> >     refund to
> >      > anyone who is unable to travel due to visa issues.
> >      >
> >      >
> >      > We understand that some people are very concerned about the risk
> to
> >      > health, that some other events have been cancelled or switched to
> a
> >      > remote-only model and that some companies are putting corporate
> >     travel
> >      > restrictions into place.  However, it remains our view that there
> >     are
> >      > significant risks in both under-reacting and over-reacting to this
> >      > complex and developing situation, and as we are not
> >     epidemiologists or
> >      > public health experts we will follow the evidence-based advice of
> >     those
> >      > that are.
> >      >
> >      > Following the same reasoning, we will not be offering full
> >     refunds in
> >      > the event of someone being unable to travel due to corporate
> >      > restrictions and the cancellation fee will still apply. Full
> >     details of
> >      > our registration policy for IETF 107 Vancouver are available on
> our
> >      > website [5].
> >      >
> >      >
> >      > Finally, we are working on a backup plan for a fully remote
> meeting
> >      > should we need to cancel the in-person meeting, but there are a
> >     number
> >      > of logistical challenges to overcome.
> >      >
> >      > Please feel free to contact me directly if you have any questions
> or
> >      > comments.
> >      >
> >      >
> >      > [1] https://www.ietf.org/registration/ietf107/attendance.py
> >      > [2]
> https://www.who.int/emergencies/diseases/novel-coronavirus-2019
> >      > [3]
> >      >
> >
> https://www.canada.ca/en/public-health/services/diseases/2019-novel-coronavirus-infection.html
> >      > [4] https://apps.who.int/iris/rest/bitstreams/1269109/retrieve
> >      > [5]
> >      >
> >
> https://www.ietf.org/how/meetings/107/ietf107-special-registration-provisions/
> >      >
> >      > --
> >      > Jay Daley
> >      > IETF Executive Director
> >      > exec-director@ietf.org <mailto:exec-director@ietf.org>
> >      >
> >      > _______________________________________________
> >      > IETF-Announce mailing list
> >      > IETF-Announce@ietf.org <mailto:IETF-Announce@ietf.org>
> >      > https://www..ietf.org/mailman/listinfo/ietf-announce
> >     <http://ietf.org/mailman/listinfo/ietf-announce>
> >      > <https://www.ietf.org/mailman/listinfo/ietf-announce>
> >
>