Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
Joseph Potvin <jpotvin@xalgorithms.org> Wed, 26 February 2020 16:05 UTC
Return-Path: <jpotvin@xalgorithms.org>
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 73F663A0A13 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 08:05:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=xalgorithms-org.20150623.gappssmtp.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 6-KpKrVC7-j9 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 08:05:24 -0800 (PST)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 CE7343A0AEE for <ietf@ietf.org>; Wed, 26 Feb 2020 08:00:54 -0800 (PST)
Received: by mail-qt1-x829.google.com with SMTP id v25so2591268qto.7 for <ietf@ietf.org>; Wed, 26 Feb 2020 08:00:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xalgorithms-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mjGNEH4k+Fd78UjZbdr4WpfoCOgHnzCCNj4cem5VsrY=; b=QYabhhFfhW26g6SgYQi1boUSmT8zp8Z0q44ygccdsJgrHvpO/qutWFwMfPJL9Y4+NH Z4NOyx6/5enC1MSpv9+BPN61m7mBQcfsr8IRurRWvxWPdcY7BOmNLxnjRDOeqw7PW7XV 8AthHwwK6NDS/+whXM6IsjtmuF0eIOhG5xyAf6M5SYw4kIYppTs5bn9wQOCWvGYhnoa6 +xmgidgph32ZRVOlPYYSyVYFG6I4bnjb2JSbKPiHIZI4BtCHqUL9wKdUNfOPV/WbO+Xj zqA7qJtzGRaBHn6yyKLhPDNyMTmGqMhCglmsY0TTF/5NxXbqjlKxP/esKy9x+Febb5AP qwTg==
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=mjGNEH4k+Fd78UjZbdr4WpfoCOgHnzCCNj4cem5VsrY=; b=bph7bxhJFexk1KOZ3Na1DUyaWUxXTFYKGDFwozyeUjc44WVEr/sG8JoJQ+Y3WphQ46 TsC5Nv52oOP7WCVc+LXmtmcGJ5oQfuTEXYw+a0FB+zXOz66f5V3iyYGRgZw8IXXWRqiU bj0fEX1O7CSVdWkhDUrvBy5yIZ78i2LeiwWMILb9/F/cwc7t/2I4ttCxjgeDhEkdxsZG DaS7DVk8kDfrXnC67sVbxxNdPUFDY6md6Oz9p8XzMybrU5vF6bMvMQGuAG+gahPM9RAP 84yfFk9ozOPxGQwe/k7b+E7AGzjWBa0JfdQFmRZdnwKwhLRI+dBEmkIMiXA2TuJ0HqsH uXRQ==
X-Gm-Message-State: APjAAAXM+321GBkK0vGl6sHtF/+VX2evAGRCtFoiEhzetzVCN9McWuA3 pvNAxvRLVFesz1vDxEEbNHVRKvtpRD9uMq2eAfg5Hg==
X-Google-Smtp-Source: APXvYqyKkSDn2JVSpRFxfkzD//nE+zDQhO4HroOYNArnNzcWp549zGbF7WNH2TLFqd+dmeZOwUpq0MECDXHaOQ5qQCg=
X-Received: by 2002:ac8:4659:: with SMTP id f25mr5724991qto.273.1582732843050; Wed, 26 Feb 2020 08:00:43 -0800 (PST)
MIME-Version: 1.0
References: <158258721017.24319.9082233711977122647.idtracker@ietfa.amsl.com> <CAAObRXJ=NnrxLAGgtas8Cs_jw-AJ0YsgYpMmYtrHy+PjKsfqvg@mail.gmail.com> <CAMm+Lwh17iOi_8qZ7at8gHQ6R38YwVuUZ8O1cpsJU7MKh+nMmA@mail.gmail.com> <DBBPR03MB5415B842B32E90BF91D0C361EEEA0@DBBPR03MB5415.eurprd03.prod.outlook.com>
In-Reply-To: <DBBPR03MB5415B842B32E90BF91D0C361EEEA0@DBBPR03MB5415.eurprd03.prod.outlook.com>
From: Joseph Potvin <jpotvin@xalgorithms.org>
Date: Wed, 26 Feb 2020 11:00:16 -0500
Message-ID: <CAAuWHCKRhe-ct2tP5TqBaCn_fSTBoFSkrppTKOyhoP_xW6Ydag@mail.gmail.com>
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
To: Andrew Alston <Andrew.Alston@liquidtelecom.com>, IETF Announcement List <ietf-announce@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Davey Song <songlinjian@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000e28bb6059f7cb4a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RdqQBfoe7MS_Oc_0aXo5s9Ffp-I>
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: Wed, 26 Feb 2020 16:05:36 -0000
+1 In my assessment, IETF107 presents a rare but valuable opportunity for the most Internet-knowledgeable community there is, to competently demonstrate to the world how to calmly but rapidly shift a large in-person+online conference to a successful Plan B full-online conference. Any weaknesses in performance would be worth addressing as guidance (and as practical utilities) for other international events that are otherwise facing outright cancellation. What better community than this to illustrate how to minimize the negative impacts? "Precaution ... simply urges that time and space be found to get things right ... the crux of precaution lies in the rigour of taking similar care in avoiding the scientific error of mistakenly assuming safety, to avoiding mistakenly assuming harm." (The Guardian: "Why the precautionary principle matters" https://www.theguardian.com/science/political-science/2013/jul/08/ precautionary-principle-science-policy ) This article is helpful because it clearly distinguishes "risk" from "uncertainty". Regular flu has known risk factors. Several key characteristics of COVID-19 remain uncertain. At minimum, prompt work towards a Plan B also provides a way "to pressure-test preparedness and emergency response plans" (Emergency Preparedness Partnerships https://emergencypreparednesspartnerships.com/a-blast-from-the-past-influenza/ ) Business continuity plans prioritize resilience, not rigidity. Joseph Potvin Executive Director, Xalgorithms Foundation Mobile: 819-593-5983 jpotvin@xalgorithms.org https://www.xalgorithms.org On Wed, Feb 26, 2020 at 10:21 AM Andrew Alston < Andrew.Alston@liquidtelecom.com> wrote: > Personally, I think that holding this meeting is a risky move – and I’m > not sure it’s a responsible one. > > > > Yes – it can be argued that the individuals who are travelling to the > meeting are taking the risk knowingly and be it on their heads – the > problem is – it goes far beyond those individuals. Multiple > multi-nationals are shutting down offices in various places, there are > corporate travel bans going into effect (and the current statement says > that if you register and want a refund, it has to be a government imposed > travel ban) > > > > Right now from my perspective – we’ve been lucky over here in Africa where > it hasn’t arrived yet – but – if it does – there is no real infrastructure > to deal with something like this – and it could be absolutely disastrous – > and so – I certainly don’t want to be anywhere near anyone that has been in > a large conference, with people all over the world, when the virus can be > carried without any symptoms – transmitted – and you can be all the way > back home again before you even know you have it. > > > > So – I question if holding a meeting like this at this point in time – > rather than using the technology we have available and going entirely > remote – is really a responsible choice. > > > > Andrew > > > > > > *From:* ietf <ietf-bounces@ietf.org> *On Behalf Of *Phillip Hallam-Baker > *Sent:* Wednesday, 26 February 2020 16:56 > *To:* Davey Song <songlinjian@gmail.com> > *Cc:* IETF Rinse Repeat <ietf@ietf.org>; IETF Announcement List < > ietf-announce@ietf.org> > *Subject:* Re: Further update on COVID-19 (Coronavirus) and IETF 107 > Vancouver > > > > On Wed, Feb 26, 2020 at 8:42 AM Davey Song <songlinjian@gmail.com> wrote: > > What I can do to help the situation as a Chinese IETFer, is to cancel all > travel and stay at home.... > > > > Thanks to the Internet, I can participate IETF remotely. Good luck! > > > > Davey > > > > Exactly. The point I am not seeing raised here is whether it is a good > idea to hold an international meeting and potentially spread the virus > further. This is not just about us. > > > > This may not turn out to be a re-run of SARS. A large amount of the > infrastructure that existed to deal with pandemics has been shuttered > since. The way our political elites manage risk is to observe when disaster > has been avoided and conclude that this shows the controls intended to > mitigate those risks were unnecessary. > > > > A question that we may well have to consider is the possibility that > Madrid is cancelled by government fiat. We are currently in the complacency > phase, what will follow if matters continue is panic. >
- 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