Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 26 February 2020 19:17 UTC
Return-Path: <spencerdawkins.ietf@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 D925E3A1265; Wed, 26 Feb 2020 11:17:19 -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 NSPZEqWKi8fy; Wed, 26 Feb 2020 11:17:14 -0800 (PST)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 4CF223A124D; Wed, 26 Feb 2020 11:17:14 -0800 (PST)
Received: by mail-il1-x135.google.com with SMTP id i7so118745ilr.7; Wed, 26 Feb 2020 11:17:14 -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=pYhmpc45BwdystKkMkYqchH5S+BqS98Rwv3gedLTPxk=; b=aWTzlAYX/ygYix2NGnwmpEnjRQIhcV8jmQvdopyda3YeM/W1Mg6jZ9VyeyUoC3P2qC YxPKIP2duA3ODIrzBwZnUOSlQMqWLYxu4D05t7hmoR/kb8fnus929AdVHqf/gYoHlk8h 1dpe7dNXrCcB32GzOeHuWYWHg/H74mDBQeNIkKjlgAHcvrYGBePu8LIm2VcDYt1hDdOM 0Mvm6ag2RVRfBHNvuCV/xfisb651G4OnXCBdgnK+YiqA/QrjHEDIpPS8Al65gHPyejcs 1DGXAdm37ttiWw86LfTZrsbZDYjy/HaLy1kNXXMTY9Mw9dhXZLS3HBKgPnEyYm5tJ+9K yrkg==
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=pYhmpc45BwdystKkMkYqchH5S+BqS98Rwv3gedLTPxk=; b=NI/vpJ/VdoVIAthZXcYcyhQ/pLHGrMzSnRpKcXDr6ArrYAQK0xQ8VPzqUv9gijL66G Um+mnhKLMdIpGovy8N9iYq22S3QUr8jOHdo2qL4yickRp85GC6gltCg8ks1Jfg4gEsPE gzSr6zrCzfuM7D1Dyxg7Usog4IFZmf7TnnxhsXeBWym2i9MeYLJksJsobVYClMAhKXJy fMejmNeEnaSRuFM4OufkcCfFdeYMN7NaMjcTYlb504jbGv/MIabD3OjwHdvINzIABISE Uap+vzTSldPe5ucEpN3pR0euwb9xC2vmbMGA/V9ytg6DXOObgUyzXSXv3ylQVNRZUo1Z fwsA==
X-Gm-Message-State: APjAAAVFIpPdJW8cYJ43N2a0bYmWvcKBvz357TlJGiVCiDF3shiA9sh3 GUklXP8Fzs/mwyfQatNfxFxyq+ZcZsiSCBoVJp4=
X-Google-Smtp-Source: APXvYqyj3eIZhuZ0Kh6+GSSJtCUKDUBvXFUr0z4OeD0qVxaTXT2olpF5FCvK9ayp3OG8vB1gJUTyctu5rU9/i9X60bQ=
X-Received: by 2002:a92:cc04:: with SMTP id s4mr118861ilp.193.1582744632607; Wed, 26 Feb 2020 11:17:12 -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> <CAAuWHCKRhe-ct2tP5TqBaCn_fSTBoFSkrppTKOyhoP_xW6Ydag@mail.gmail.com>
In-Reply-To: <CAAuWHCKRhe-ct2tP5TqBaCn_fSTBoFSkrppTKOyhoP_xW6Ydag@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 26 Feb 2020 13:16:45 -0600
Message-ID: <CAKKJt-eDGSd+B=Taf8Q=AoE=_mHj542PT1ChvqO3485oVKSWtw@mail.gmail.com>
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
To: Joseph Potvin <jpotvin@xalgorithms.org>
Cc: Andrew Alston <Andrew.Alston@liquidtelecom.com>, IETF Announcement List <ietf-announce@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary="00000000000098c9f5059f7f730a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fASxgX83pvg9EUqKdQcuLw6D2JU>
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 19:17:23 -0000
Keeping in mind that none of us can speak for anyone else - I can certainly fly to Vancouver and see who else shows up to talk, and no one is going to make any of us show up against our will... On Wed, Feb 26, 2020 at 10:10 AM Joseph Potvin <jpotvin@xalgorithms.org> wrote: > +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? > I'm currently participating in an all-virtual meeting in another SDO, and their e-mail server is running about 20 minutes behind direct mail to participants, so nobody is quite sure what the current discussion state is, depending on whether or not you're addressed directly in the e-mail. Canceling completely now is also an excellent way to find out that we are nowhere near able to go Plan B full-online successfully. If someone in this thread can speak authoritatively about how well prepared we are, I'd love to hear from them. Until we hear from them ... I'm OK with where we are right now - if things are still going well in three weeks, some of us can meet in person, and other people can participate remotely, and that's what we do, anyway. If Canada closes its borders, we'll still have an opportunity to find out how well we have prepared for Plan B, and how much work we have to do to achieve success. Make good choices, of course. And do be safe, according to your own informed definition of "safe". Best, Spencer > "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