Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver

Fred Baker <fredbaker.ietf@gmail.com> Thu, 27 February 2020 17:08 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 7EEFC3A0CF1 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 09:08:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 GJzeUF1dQsGE for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 09:08:29 -0800 (PST)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 AC8EC3A0CEF for <ietf@ietf.org>; Thu, 27 Feb 2020 09:08:29 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id g6so40274plp.6 for <ietf@ietf.org>; Thu, 27 Feb 2020 09:08:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YQD43IULBy7m6UYtBfOwOE7O6VDr/ICa47oBSfSZfEY=; b=FGj76+FBiS/N3A1kqkRJhFJtGVioAedbZ5z0zZz3Q7Nes94Sy/3wi8y/FtolOJT8OB debBNqr5jle+0flIBBYHZC3shrifjfqfvC56ObFGM0uNHterX3BsZjfwfNiiSKyGtFGc 0NpYv5QyC9rXMrRs2HaIX9y/x+89ouPD0Fz8S/nyUvqWp746115uWnEDWup+9wiTpZlC Yo7R04DtrFR+vRFPkoq1fLEMteYtVzm05pTHcDPpB7fv9Iwb7cRMa8xnnHG8vgkzevWZ 4OJ9bGI8q68YdTapj7i0795GEboWrku9zICe8Ewx1QwNdeLNXqMjuSNBcGVIiytuXkXA ZeSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YQD43IULBy7m6UYtBfOwOE7O6VDr/ICa47oBSfSZfEY=; b=lMn5KqR2xyFcFn5CKULOEVKe2QY4ZkYN4dlUvcS8kcPTw1Wj48iXQMmlHeIyIrVCCc ljravnNZmhrNcjMVc4Soh90tfS/97qM/aeOyQMLpgB0b9nwrb36NXg9LEk3yKvRywUZF IvYd/tpsSBRZnk8PHCYSbcgBLUZwqElW97zqaj0n+TQXGDAs0kDyqGFiOa4z04wVDQeG Qu9rqJWP5fOuznF9sm/rSwF7Oo9rXsMn0tGeOf+/tIGZrwSXGSavpoPYJswDmCf6QA1k cjEJym3snBeVj+K9ZGS+9C2C6Q9GWcTXCfb0iQKa2n9kiQz7io+bhjMd6R00DYp9yVnX nFKA==
X-Gm-Message-State: APjAAAUF5AQrXfqr58DbadQxoIM1ImQupEoV5zZdCMNPnQx7xcdOYmN7 jKtw9AjA7a6kjSNvmUg3ZAI=
X-Google-Smtp-Source: APXvYqw6NiPaB+38XJ7EOq9j2Zb+XOwexFVlzlz9AFH91pwnMeb0hRmvPNeKonXVnW/FSCQpu/ctDQ==
X-Received: by 2002:a17:90b:4396:: with SMTP id in22mr664473pjb.83.1582823308864; Thu, 27 Feb 2020 09:08:28 -0800 (PST)
Received: from ?IPv6:2600:8801:d004:600:dd00:2b55:a1d9:c31a? ([2600:8801:d004:600:dd00:2b55:a1d9:c31a]) by smtp.gmail.com with ESMTPSA id d2sm7050560pjv.18.2020.02.27.09.08.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Feb 2020 09:08:27 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <2CCBC832-B17B-45A9-B215-8CF4021D2E5C@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_93987E84-7EB2-49D3-8DA4-40471CA9E30C"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.19\))
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
Date: Thu, 27 Feb 2020 09:08:26 -0800
In-Reply-To: <CAHw9_iJu_LWD1czbksQWV+8+FUiuOCyn8HEJcf2DCEOH3zV73w@mail.gmail.com>
Cc: Jared Mauch <jared@puck.nether.net>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Best Practices <ietf@ietf.org>
To: Warren Kumari <warren@kumari.net>
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> <DM6PR05MB634809ED4CD6D49036B47A25AEEA0@DM6PR05MB6348.namprd05.prod.outlook.com> <7FE2757F-F4A1-4134-A5FF-9E203754DD07@puck.nether.net> <CAHw9_iJu_LWD1czbksQWV+8+FUiuOCyn8HEJcf2DCEOH3zV73w@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.80.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/md-bs_rPlgX-5xZKTXhB4uSigt8>
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, 27 Feb 2020 17:08:32 -0000

On Feb 26, 2020, at 11:28 AM, Warren Kumari <warren@kumari.net> wrote:
> I've participated in a bunch of them, and have found them to be not
> very effective -- more effective than not meeting at all, but not by
> much.

On this point, I would agree.

As a ICANN Advisory Committee chair, I have been watching the ICANN process of developing a meeting, and I'm underwhelmed. Something that sees to drive it pretty hard is that some of the groups need translation, so every group has resolve translation questions. Each SO or AC comes in with a set of meetings it would like to have (for the RSSAC, that's four), and a number of other meetings that other folks would like it to have - which may or may not be important. "Could you please give us a report on your progress?" The opening question is "what do you *have* to do", which for us means that we have whittled a nine day meeting down to four hours, the rest of which was meetings of opportunity - "we're in the same place, could we talk?" Or "we need to have a community-wide XXX discussion". If anything, I have had confirmed my existing estimation of ICANN meetings, which is not high.

Attending IETF interims, what I tend to observe is that there is a presentation but often not much discussion. The value of an IETF meeting is, in my view, in the discussion. As others have noted, that discussion is often in the hallway, over a meal, or in a bar, and a remote meeting makes all of that close to impossible.

So I don't view "let's become completely virtual" as a realistic or viable destination. It's a reasonable plan B when we need one, but it's very much "plan B".

As to canceling this meeting, the best argument I can formulate for doing so is that we don't know much about COVID-19 and giving it no chance is conservative.

If the meeting is held, I plan to attend.