Re: IETF in July

Fred Baker <fredbaker.ietf@gmail.com> Fri, 20 March 2020 21:13 UTC

Return-Path: <fredbaker.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 E5B993A0E92 for <ietf@ietfa.amsl.com>; Fri, 20 Mar 2020 14:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, MIME_QP_LONG_LINE=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 JPcLJKVsuvgO for <ietf@ietfa.amsl.com>; Fri, 20 Mar 2020 14:13:16 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (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 DEE0F3A0E5A for <ietf@ietf.org>; Fri, 20 Mar 2020 14:13:16 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id mj6so3039924pjb.5 for <ietf@ietf.org>; Fri, 20 Mar 2020 14:13:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=ZCucFKyUw09ifk5aa4QJN/60gY/iSqqm9yZoXtGAgOo=; b=TwD8YLEhG9grXIt26PgGYgWyBKLm55LRjiclZRZOOdchF14qyvnyoAAVicIF3ZJqaw PLIjENA0LtBEyM9skFc8xCC3dO+Duu5ReCTtPkg+2PjDSDP30bHXKFXE+YWwfr1N7Vyw 5DjmGkSMHNyFoNP0vW2ClZmVDcj2W+qpgUBckPzYPtNIZidLC3fl/qCcJo28hvr6WdbK XszhlPtoH+jc3b9zU5LPSD90YWN/OAjQJ7cGW3A5gkZHAUcLpKvACyROwqHU6P3j0ocw bcLTdkXR0Kay7WSlbGpKGnnioSXFOHbZ33ovoKQwpul8VFDuiLlALDyz0bNtNTXuJxYz 9rIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=ZCucFKyUw09ifk5aa4QJN/60gY/iSqqm9yZoXtGAgOo=; b=ghdhY7ReuraT3siACnSc9bVoNcdBcZHuZFo2qM182bmm3q4Cql0K3J2G2GZaCIpqAG 5YygplwmQrlcbyPeUvWkGnbtFY9HbrytJA0nK7GvcKbLxw/FAsUHf8M0EY9bo05uVvFc IL6A+uLVtVxky4jOiDo8GZz8MkDpbfS9mTTtl4BG5DeP7n/f0PDAtYlkn2B82TKH7kgV 415HRR9rd/240d/NIlZQRCMNUBUqVI7QfaTycQzK8yVrjKTjjV0uUIFOh5Wzu3ff4reF qR1GORUGaAAzKIagEd8G+ZPYsye3yaPneNx5siL2hM6DPFLeyYBpyzd96cxKT6V5DiPJ R0lQ==
X-Gm-Message-State: ANhLgQ3SMklL9KC+Acx+R0RQO1gQ7753ARxjnV87p8CTxad6qEw1c+lj pI/F4K4GoV7Tb29WvDoEITY=
X-Google-Smtp-Source: ADFU+vv1AazLF4W14aFwzaN27Im6Rn2nhy+ej3MsCaElNQZSdBB10pjH6iE07okhRQEKLLenuy30Hw==
X-Received: by 2002:a17:902:788b:: with SMTP id q11mr10478694pll.20.1584738796263; Fri, 20 Mar 2020 14:13:16 -0700 (PDT)
Received: from ?IPv6:2600:8802:5900:13c4::101f? ([2600:8802:5900:13c4::101f]) by smtp.gmail.com with ESMTPSA id w124sm6471697pfd.71.2020.03.20.14.13.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Mar 2020 14:13:15 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-0197DC18-7F23-4EE6-8D27-B86E16160218"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: Re: IETF in July
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <c857887d-7a50-147b-5ef6-e554c90a9104@network-heretics.com>
Date: Fri, 20 Mar 2020 14:13:15 -0700
Cc: ietf@ietf.org
Message-Id: <093A558A-A8C3-4578-B120-9F21010CF72A@gmail.com>
References: <c857887d-7a50-147b-5ef6-e554c90a9104@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2WWBwDU8E8oUed7D7v06IkK7tAc>
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: Fri, 20 Mar 2020 21:13:19 -0000

My first thoughts turn to A/V services like Zoom, and to mailing lists. I suppose I sound very traditional, but I don’t think this requires a lot of reinvention.

If there is one lesson I’d like us to collectively learn, it’s that delaying a decision to the last possible minute enhances the confusion and damage it causes. If we’re going to cancel IETF-108, I’d like to see that decision announced in mid-June. For IETF 107, we didn’t quite know what was coming, but we could observe that other bodies were canceling events. For IETF 108, we know that the statistics we know say either that it will be over - nobody is sick worldwide - or it will not be over, by then. If the latter is objectively true, not changing the meeting in some way in June is a matter of collectively kidding ourselves.

Sent using a machine that autocorrects in interesting ways...

> On Mar 20, 2020, at 1:48 PM, Keith Moore <moore@network-heretics.com> wrote:
> 
> 
>> On 3/20/20 4:42 PM, Ron Bonica wrote:
>> Is anybody planning contingencies for a fully remote IETF in July? (I don’t mean to be a pessimist, but planning for a worst-case scenario is never a bad idea).
>> 
> Don't stop at July 2020.   Plan contingencies through at least EOY 2021.    Until there's global herd immunity of one kind or another, continued restrictions on travel seem likely. 
> 
> Keith
> 
>