Re: IETF 107 and Corona Virus?

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 13 February 2020 20:37 UTC

Return-Path: <kathleen.moriarty.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 14A711201CE for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 12:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
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: 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 D1vv0P0BOhUO for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2020 12:37:12 -0800 (PST)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (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 03B991200C1 for <ietf@ietf.org>; Thu, 13 Feb 2020 12:37:11 -0800 (PST)
Received: by mail-oi1-x235.google.com with SMTP id i1so7170759oie.8 for <ietf@ietf.org>; Thu, 13 Feb 2020 12:37:11 -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=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; d=1e100.net; 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: <VE1PR03MB54220BB50CB38B6F4A72FC58EE1A0@VE1PR03MB5422.eurprd03.prod.outlook.com> <eb39f2cd-7a27-e0ff-3be4-6d03d13f31b8@gmail.com> <DACFBEF8-93A6-429C-AF16-19E01A0BEA50@consulintel.es> <CAHbuEH42ZYRZfjVTSnAHnBaVM+9M1Bt843U37F+2Y97Sdx1iQg@mail.gmail.com> <6E1C07A9-AF8A-4ACD-A299-E7D0E757F8C4@tzi.org>
In-Reply-To: <6E1C07A9-AF8A-4ACD-A299-E7D0E757F8C4@tzi.org>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 13 Feb 2020 15:36:35 -0500
Message-ID: <CAHbuEH5Z0TAdj1Y4UUArsLv1M6JHAqqdm27f-MD3rJXKWbGU9w@mail.gmail.com>
Subject: Re: IETF 107 and Corona Virus?
To: Carsten Bormann <cabo@tzi.org>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ad438f059e7b0d07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JYJ95ju_pOI39XiG6de8-MA0ia4>
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: 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 <cabo@tzi.org> wrote:

> On 2020-02-13, at 15:55, Kathleen Moriarty <
> Kathleen.Moriarty.ietf@gmail.com> 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,
Kathleen

>
> 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,
Kathleen