Re: IETF 107 and Corona Virus?

Kathleen Moriarty <> Thu, 13 February 2020 20:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 14A711201CE for <>; Thu, 13 Feb 2020 12:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id D1vv0P0BOhUO for <>; Thu, 13 Feb 2020 12:37:12 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 03B991200C1 for <>; Thu, 13 Feb 2020 12:37:11 -0800 (PST)
Received: by with SMTP id i1so7170759oie.8 for <>; Thu, 13 Feb 2020 12:37:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7Ma544O7/dIgGpI1pgvBv/RWbM/S+E2YqwqCZYVuNm4=; b=U+/sy9ki7XvWUtK/Kk4FJM3fwFZMibY31On5mZFyOvDyVIsD15VevS/orHg84JOF7Y nbRLjoqPHiNPwnhRFCrXvUz0zfE21oxxqDoGNXlySzWaHGzkG7NZY9GQmfBHN/eDzKRr IR4QmcWN0I1tBy5VBlhiicMykzc8lJxXBzEeVQ5nJQa7nV5DPQZYWvIVR24swBW9vHAI fQJ4q60ea6I3d3MwW/htQEirZJFQMLxLaE0KCW+VXZIvUVW8O61rmHTV5EkfyHgEPjtR u220ti5T176aCAEOGhxhe8olmETkPujlubTcRspsYyoPBdSXHLGsNxMmiXc4FbG6rRVU RwtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7Ma544O7/dIgGpI1pgvBv/RWbM/S+E2YqwqCZYVuNm4=; b=ZRz1pdkpW6ghZKTyz6kUVgO1azcmbOVFwCWtufaiAkybha6f34FFsvkA29zGqo+Ljp 1FVBJ6nAaJ07CdJndxG9Of2MDFKLhNeQHwiKwlZOG2jmn6E+UoGDwTLORn0VvwsbgVi9 TRccp0ZOtexNN1Aclw4uMt834CddPlUC0FsJILbXAzaBYWfjgkHROjOM3anP8c9Qmx46 T9fzNpTcvGk0ztW3d+aeWL2KZshGafAGeApPfp9Ulnbw7hZyVxYLHBGZtPgTiIU86I7L jr7fQjj9mPinjYAQVLSMO28JcOQnTiqhgXn+DK9fYPqjl0w73p/oHLTLQFjzH+GmAuH5 BIeg==
X-Gm-Message-State: APjAAAXtRw7jy6Mm1Ny0Vf+LBvjv0yttNC67C6Aw5LzqWwPO+IPfYkTB ykQOYqKwavL2n9r01eqOiEf91Mdi2ojIoTCGydg=
X-Google-Smtp-Source: APXvYqxk1LG67I8Z7aQ0zeI572wka59+VEyHd4eTrYkTsCU3kGOh22g+iOOeGvcE5yKcYUof8QuTPp33tFGQMUQ0KGQ=
X-Received: by 2002:aca:32c3:: with SMTP id y186mr4335732oiy.114.1581626231176; Thu, 13 Feb 2020 12:37:11 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <>
In-Reply-To: <>
From: Kathleen Moriarty <>
Date: Thu, 13 Feb 2020 15:36:35 -0500
Message-ID: <>
Subject: Re: IETF 107 and Corona Virus?
To: Carsten Bormann <>
Cc: IETF <>
Content-Type: multipart/alternative; boundary="000000000000ad438f059e7b0d07"
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:37:14 -0000

Hi Carsten,

There's one consideration you left out -

On Thu, Feb 13, 2020 at 3:18 PM Carsten Bormann <> wrote:

> 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.

Individuals from an entire nation likely cannot attend what is meant to be
a global meeting. This deserves some thought.

Best regards,

> 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


Best regards,