Re: [Manycouches] Follow up on consultation on IETF 112 and COVID-related restrictions

Mark Nottingham <mnot@mnot.net> Tue, 03 August 2021 00:18 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1CA3A2287; Mon, 2 Aug 2021 17:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=mnot.net header.b=KjkUEVfQ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gkIfAyf/
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 t_ULYz7cpLcH; Mon, 2 Aug 2021 17:18:46 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ECF13A2286; Mon, 2 Aug 2021 17:18:46 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 92CC85C0101; Mon, 2 Aug 2021 20:18:45 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 02 Aug 2021 20:18:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :date:references:to:in-reply-to:message-id; s=fm3; bh=lgHWZRg6tW Jw6cZpCStfXRgTBrl9kvgqxNhWyF6bjKs=; b=KjkUEVfQLfE4/qqNatn2WJQdel fkvm/6qFOnsnYt1tXtidy1iMsCcwqCxKg/0v9aN2mhnIVPDEZvb4VTJ0nVI4kQy1 U59QvjQzf6+t434lMNnhttteQgRD8cJsfICe98SelnoUvHRn++vBn5u2du3YVGtd MoQ0bA0WlfOwShGtJlGvrJcQdKruAcGBXCgqc4EmOdevZXSC0MGJTWZiqiRUoTFL Hjz516eUliAGdA7FR8WeqozVCkB0PCn765y6Ce3LJpR43Vyd8RKB6PQd3BJP01o1 5i9yBrLDElImCRaJsuwrZkwMQ4MrlSPdOgM03skPORDINHOW+Ykx8JoWJ3AA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=lgHWZRg6tWJw6cZpCStfXRgTBrl9kvgqxNhWyF6bj Ks=; b=gkIfAyf/K4SDCYGQ0wvY7eCcuDn7vWzpcFKBK8hTC/YNTS9DcYMNKTTD9 v/LRUGjVeUYdA5Vg+rTmTGAaVW9HV8+5ivXfRMObiRYCLMAc758b+LVemLkY+pFs kzbzwjOKKhcTW903id9GmOZH+BaT4rD7TP3y897PHEnGCMLUiuZbvzBfqn8ksySj On3mLfpTC4CXTrsSmjf0/yNW5sN8w46LSjzoeO4MTmTE53ZTs/rgXDekyj/And0B +zWLGxUZbTQKh4J6j+Qpj+CQCfovYY/IktSa6fDs3O2doRycnxioA+HSm3ldBEMC rUGmktPsZBCdHJLOvdJFHccFG1Asw==
X-ME-Sender: <xms:ZIsIYXVPDZ8A55jPt4LX3tumUpjTeLk2rEEAsEcM49xH8SwaJqZMCg> <xme:ZIsIYfkO4Ks8-lP-mQenlAo4DPeSywKqXtVDrcEMgZPJqGW0YLPs5J1tieXYm33EA dwtepAa5VL5qYK8hw>
X-ME-Received: <xmr:ZIsIYTZuxi6yp_tRXfdAX47NaWMcYqdIuqmtdFppEK0iGYr-JXqylZL3hHLbSPO_4-3YERjAVlQe_VuLFf4mNL1xwhyNcJ70iEIaXZR3M_02PZ0zJxacOPn0>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrieefgddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephfgtgfgguffffhfvjgfkofesthhqmh dthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhn ohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeejfffgheekgfekkefgueejtddtueefgf ekheffteekkeejkeekjeejfeduhfdvfeenucffohhmrghinhepohhlhihmphhitghsrdgt ohhmpdhmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:ZIsIYSXdLOSQsD4CM6UDonsC4mwhv3BAK8L3tC_GxIhtmowNHOB5NA> <xmx:ZIsIYRkrKaZ1AeGJ6DTfe_pdOxskgeyt5S573nTH6Zpqu3PFGAe1Ew> <xmx:ZIsIYfdrMqZQ4BW9ka3XCJqeYVm-CkMYriuRUnBugYA8xN9RwfyavA> <xmx:ZYsIYXi56aZ-ee8BXEZMOtsyT5tXN317ov1B0oiQn_VOoEEEcE546Q>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 2 Aug 2021 20:18:43 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Tue, 03 Aug 2021 10:18:40 +1000
References: <0AD65B7F-38BB-4AD6-B11B-226E01EDA1BC@ietf.org>
To: manycouches@ietf.org, Jay Daley <jay@ietf.org>
In-Reply-To: <0AD65B7F-38BB-4AD6-B11B-226E01EDA1BC@ietf.org>
Message-Id: <4EE502CA-77CD-4198-87E3-868334358E02@mnot.net>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/oJKNeFfPjBd_rOhOdNij0urwZJ8>
Subject: Re: [Manycouches] Follow up on consultation on IETF 112 and COVID-related restrictions
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of remote meeting attendance and virtual IETF meetings, as well as for SHMOO working group" <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2021 00:18:52 -0000

Hi Jay,

> On 3 Aug 2021, at 9:49 am, IETF Executive Director <exec-director@ietf.org> wrote:
> 
> The assessment criteria have been amended based on feedback to align with draft-ietf-shmoo-cancel-meeting [2] with the inclusion of two new tests:
[...]
> - The meeting will not result in a significant unbudgeted financial loss for the IETF LLC

That can be read two ways:

1. The meeting will not go ahead on-site if there's an associated significant loss (e.g., due to less registration revenue, higher venue costs, etc.)
2. The meeting will be required to go on-site if there's an associated significant loss (e.g., due to contracts being broken, etc.)

Which is intended?

The text in the draft is somewhat different - it requires the LLC to *assess* the 'financial impact of continuing a meeting, or implementing any of the possible remedies', and that the 'LLC SHOULD cancel a meeting if it judges a meeting to be logistically impossible or inconsistent with its fiduciary responsibilities.' That SHOULD only stipulates cancellation, it doesn't impact a decision as to whether to go virtual or not.


> - the IETF should take on certain responsibilities should someone be infected.  While the IETF advises and supports participants and will continue to do so, the established practice is that participants are ultimately responsible for all health related matters.

Please elaborate on "the established practice." I'm aware of only one sizeable international event occurring now: the Olympics. Their playbook is here:
  https://stillmed.olympics.com/media/Documents/Olympic-Games/Tokyo-2020/Playbooks/The-Playbook-Athletes-and-Officials-V3.pdf
... and as you can see on page 32, they have a protocol for handling sick attendees.

If you mean the *IETF's* established practice, that may be true -- but every participant will need to think very carefully about the myriad of ways things could go wrong, and of the difficulty in obtaining international travel insurance that covers COVID-related situations. While participants who have sponsorship from large, well-resourced organisations are likely to shrug this off, it could be a serious impediment for participation by others -- thereby affecting our diversity on yet another axis.

I think the underlying issue here is worth considering explicitly: Is the IETF 'just another industry conference' or is it a community gathering? There's no 'right' answer, but the direction we choose is going to have significant effects on how we operate, and how we're perceived.

Cheers,


--
Mark Nottingham   https://www.mnot.net/