Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 25 February 2020 14:49 UTC
Return-Path: <alexandre.petrescu@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 EB90D3A0E2F for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2020 06:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.67
X-Spam-Level:
X-Spam-Status: No, score=0.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 pr0PGBNJ1Z9G for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2020 06:49:07 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 488153A0E2D for <ietf@ietf.org>; Tue, 25 Feb 2020 06:49:07 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 01PEn4t5019225; Tue, 25 Feb 2020 15:49:04 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 97568205660; Tue, 25 Feb 2020 15:49:04 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 878662054C5; Tue, 25 Feb 2020 15:49:04 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 01PEn42i021688; Tue, 25 Feb 2020 15:49:04 +0100
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: Mary B <mary.h.barnes@gmail.com>
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
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>
Message-ID: <beb0cb8f-bee2-f1ac-ac59-85b5e6338a9b@gmail.com>
Date: Tue, 25 Feb 2020 15:49:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <a91e7a44-b7f3-fdae-5c97-7b5ac8791a00@gmail.com>
Content-Type: multipart/alternative; boundary="------------3BBFB89208D429AF25955A9D"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vF4CbXOXPhRC5leGiUxhx7swv_E>
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:10 -0000
Le 25/02/2020 à 15:44, Alexandre Petrescu a écrit : > the numbers are much higher than the Authority reports in France I mean, just higher, not 'much' higher. Also, I would like to suggest ncob.bii.virginia.edu to delete the number in the middle - that of people who were most affected. I can not stand read statistics like that. That particular number, together with its tag, should be much deeper behind some deeper buttons and acks of Age consentment. One cant talk like that about that number. Also, in France, they say that people who were once infected, and recovered, might get it again and again recover. That would make add a 4th row and so on. It would not be scaleable with GUIs. Alex > > 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> >>
- Re: Further update on COVID-19 (Coronavirus) and … Arleen Elliott
- Re: Further update on COVID-19 (Coronavirus) and … JORDI PALET MARTINEZ
- Re: Further update on COVID-19 (Coronavirus) and … Stephane Bortzmeyer
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- RE: Further update on COVID-19 (Coronavirus) and … Belotti, Sergio (Nokia - IT/Vimercate)
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- RE: Further update on COVID-19 (Coronavirus) and … Belotti, Sergio (Nokia - IT/Vimercate)
- Re: Further update on COVID-19 (Coronavirus) and … Stewart Bryant
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Mary B
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Mary B
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Stephane Bortzmeyer
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Kathleen Moriarty
- Re: Further update on COVID-19 (Coronavirus) and … John C Klensin
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Tim Bray
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Kathleen Moriarty
- Re: Further update on COVID-19 (Coronavirus) and … Nico Williams
- Re: Further update on COVID-19 (Coronavirus) and … Michael StJohns
- Re: Further update on COVID-19 (Coronavirus) and … Nico Williams
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Davey Song
- Re: Further update on COVID-19 (Coronavirus) and … Phillip Hallam-Baker
- RE: Further update on COVID-19 (Coronavirus) and … Andrew Alston
- RE: Further update on COVID-19 (Coronavirus) and … Belotti, Sergio (Nokia - IT/Vimercate)
- Re: Further update on COVID-19 (Coronavirus) and … tom petch
- Re: Further update on COVID-19 (Coronavirus) and … Marc Petit-Huguenin
- Re: Further update on COVID-19 (Coronavirus) and … Joseph Potvin
- What can IETF do? Re: Further update on COVID-19 Phillip Hallam-Baker
- Re: What can IETF do? Re: Further update on COVID… Joel M. Halpern
- RE: What can IETF do? Re: Further update on COVID… Larry Masinter
- Re: What can IETF do? Re: Further update on COVID… Spencer Dawkins at IETF
- Re: What can IETF do? Re: Further update on COVID… Phillip Hallam-Baker
- RE: Further update on COVID-19 (Coronavirus) and … Ron Bonica
- Re: Further update on COVID-19 (Coronavirus) and … Spencer Dawkins at IETF
- Re: Further update on COVID-19 (Coronavirus) and … Jared Mauch
- Re: Further update on COVID-19 (Coronavirus) and … Warren Kumari
- Re: Further update on COVID-19 (Coronavirus) and … Robert Raszuk
- Re: Further update on COVID-19 (Coronavirus) and … Kathleen Moriarty
- Re: Further update on COVID-19 (Coronavirus) and … Carlos M. Martinez
- Re: What can IETF do? Re: Further update on COVID… Nick Hilliard
- Re: What can IETF do? Re: Further update on COVID… Joseph Potvin
- Re: What can IETF do? Re: Further update on COVID… Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Victor Kuarsingh
- Re: What can IETF do? Re: Further update on COVID… Jay Daley
- Re: What can IETF do? Re: Further update on COVID… Keith Moore
- Re: What can IETF do? Re: Further update on COVID… Richard Barnes
- Re: What can IETF do? Re: Further update on COVID… Phillip Hallam-Baker
- Re: What can IETF do? Re: Further update on COVID… Andrew G. Malis
- Re: What can IETF do? Re: Further update on COVID… Melinda Shore
- Re: Further update on COVID-19 (Coronavirus) and … Spencer Dawkins at IETF
- Re: What can IETF do? Re: Further update on COVID… Joseph Potvin
- Re: Further update on COVID-19 (Coronavirus) and … Jay Daley
- Re: What can IETF do? Re: Further update on COVID… Spencer Dawkins at IETF
- Re: What can IETF do? Re: Further update on COVID… Phillip Hallam-Baker
- Re: What can IETF do? Re: Further update on COVID… Joseph Potvin
- RE: Further update on COVID-19 (Coronavirus) and … Roni Even (A)
- RE: Further update on COVID-19 (Coronavirus) and … Vittorio Bertola
- Re: Further update on COVID-19 (Coronavirus) and … Alexander Pelov
- Re: Further update on COVID-19 (Coronavirus) and … Spencer Dawkins at IETF
- Re: Further update on COVID-19 (Coronavirus) and … Rich Kulawiec
- Re: Further update on COVID-19 (Coronavirus) and … Livingood, Jason
- Re: Further update on COVID-19 (Coronavirus) and … Stewart Bryant
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Nick Hilliard
- Re: Further update on COVID-19 (Coronavirus) and … Carlos M. Martinez
- Re: Further update on COVID-19 (Coronavirus) and … Fred Baker
- Re: Further update on COVID-19 (Coronavirus) and … Phillip Hallam-Baker
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Christian Hopps
- Re: Further update on COVID-19 (Coronavirus) and … Donald Eastlake
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Spencer Dawkins at IETF
- Re: Further update on COVID-19 (Coronavirus) and … Phillip Hallam-Baker
- Re: Further update on COVID-19 (Coronavirus) and … Christian Hopps
- Cookies as a transmission vector [was: Re: Furthe… John Scudder
- Re: Further update on COVID-19 (Coronavirus) and … Joseph Potvin
- Re: Further update on COVID-19 (Coronavirus) and … Bob Hinden
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Joseph Potvin
- RE: Cookies as a transmission vector [was: Re: Fu… Ron Bonica
- Re: Cookies as a transmission vector [was: Re: Fu… Kathleen Moriarty