Re: IETF 107 and Corona Virus?

Carsten Bormann <> Thu, 13 February 2020 20:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 60A57120219 for <>; Thu, 13 Feb 2020 12:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id R3kGj5tLweRr for <>; Thu, 13 Feb 2020 12:17:49 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EB1071201CE for <>; Thu, 13 Feb 2020 12:17:48 -0800 (PST)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 48JSVb4s7YzysZ; Thu, 13 Feb 2020 21:17:43 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.\))
Subject: Re: IETF 107 and Corona Virus?
From: Carsten Bormann <>
In-Reply-To: <>
Date: Thu, 13 Feb 2020 21:17:42 +0100
X-Mao-Original-Outgoing-Id: 603317862.664953-679a4bdb87786e08a84a9b72020f6e26
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: IETF <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 13 Feb 2020 20:17:52 -0000

On 2020-02-13, at 15:55, Kathleen Moriarty <> wrote:
> That said, my travel is mostly booked and I am planning to attend, but will watch to see what happens with any IETF pandemic planning.

Which is what is probably true for most of us.

We already know that companies’ and countries’ policies will place some limitations on the meeting (which actually is having some limited impact on planning for the meeting).  With the knowledge we have today (2020-02-13), we can assume that we will have a productive meeting, not the least because we have good remote attendance possibilities for those who can’t (or choose not to) make it.

On a health/responsibility level (and, again with the knowledge of today), there simply is no reason to cancel the meeting.  It is still way more likely for an IETF attendee to have a traffic accident than to be impacted by COVID-19.

Now that knowledge we have today may change (a.k.a. “surprises”), so the IETF leadership needs to stay in a position to make different decisions based on emerging situations, and new expert advice that may become available.

I still think of the plenary where it was announced that we would meet in Korea and somebody went to the microphone with the concern that North Korea could be attacking Seoul at any time.  Yes, COVID-19 can attack at any time, but it is just one of many risks that we have to juggle.

Grüße, Carsten