Conclusion of consultation on IETF-specific COVID management for IETF 117 and beyond

IETF Executive Director <exec-director@ietf.org> Mon, 24 April 2023 16:29 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B97C13AE30 for <ietf-announce@ietfa.amsl.com>; Mon, 24 Apr 2023 09:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf-org.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58Q0yie2bMOK for <ietf-announce@ietfa.amsl.com>; Mon, 24 Apr 2023 09:29:56 -0700 (PDT)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FA3BC13AE33 for <ietf-announce@ietf.org>; Mon, 24 Apr 2023 09:29:54 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id 5b1f17b1804b1-3f1cfed93e2so18414705e9.3 for <ietf-announce@ietf.org>; Mon, 24 Apr 2023 09:29:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20221208.gappssmtp.com; s=20221208; t=1682353792; x=1684945792; h=to:cc:date:message-id:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=WEBlChZ9paWu81x++Ec4fL++xLSjRoXcLV7VdkCFHl0=; b=Ud9HuHwsNQLoUmGo9odJ3DAB1pjNAeyT+rJKM0deQ9bWNn22wl46MAJTZ6F7auKWyT sgv99xkEBx+BkpMGXHe3u2wQbPDNo899BupOA61nPHYRhgqnjgF2mEjn6gRhEpiktKip fc0v0NzIhnsJRTce8GnQEJLVyjdNF+txBnoQsfKAqpSsLzBrNAgpzNrAkFrMarFaoPqt yklxC+2ivrvq/FQg+tpACrrmVBiyw8JZaqD0mlPsxM02gZ8i4nYKhxaL4k2ca/8iW58i J7ArlnkAXfZRIt5dF6D7wLP1mUrpSJ99XCHezYlGde96J1weMx1IcU5PJCsmNNbHcKXQ sigw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682353792; x=1684945792; h=to:cc:date:message-id:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=WEBlChZ9paWu81x++Ec4fL++xLSjRoXcLV7VdkCFHl0=; b=jIrZFX0rxjcG8WQf74CN1KnIV5tj9Pq/jz0E+cXqqQSkXfkmFfVvo4dtHY7lnfAcy7 6ZURSGOSUD56xlmQR3VCeqJTSs5TDItjGMuNPqx1L0o02OVQI9Joiu6uxtbeSIKbBqgY cC6caqXo0H7BmwyZGOV2LsSIZqmCrR+r52r5eBT4bmcV4zkSOEGKHs8hOrQNCpUi+sYj 0wMJ+ENWxKVqe/oZjApu1VL03w/CY0gMqpk4vFmgeoxc75/69iA3AjkcrVpPKLUDBhRs VJCe409I18PTi7x5i4Px3j+t2P6RCjCLyW6qGA4ZOZcfReK9UuQwIvbSZf/V/giHkOJb u4Mw==
X-Gm-Message-State: AAQBX9dmdqTnHamGwElZbNTlsYbpwOIBk4kW1xspzE9U6ADJ/Y3ID9H0 7cSwZo7Zyt9whQhYUiW6OUhbZrvpXoUrd0E0ya9mg4yw
X-Google-Smtp-Source: AKy350aPCrdSSh6Tkv3W/h/0iGyXl/lN/6hS6Bt8KEMKhLfvkRlqd7QFaVbk25P7f8nZn2pY1cA2VQ==
X-Received: by 2002:a1c:7318:0:b0:3f1:7eaa:e2c3 with SMTP id d24-20020a1c7318000000b003f17eaae2c3mr7741256wmb.24.1682353791411; Mon, 24 Apr 2023 09:29:51 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id i3-20020adff303000000b002f4cf72fce6sm11149891wro.46.2023.04.24.09.29.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Apr 2023 09:29:51 -0700 (PDT)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Subject: Conclusion of consultation on IETF-specific COVID management for IETF 117 and beyond
Message-Id: <1DCF80CD-EE2C-49B3-A9A1-8E233F1726BC@ietf.org>
Date: Mon, 24 Apr 2023 17:29:44 +0100
Cc: admin-discuss@ietf.org
To: IETF Announcement List <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/NVmH5Dp0PGngGrjttEgOzDpnHrg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2023 16:29:58 -0000

The consultation [1] on removing IETF-specific COVID management rules for IETF 117 San Francisco and beyond, has now finished.

There was some feedback to the admin-discuss list [2] and quite a bit privately offlist.  Thank you to all of you who responded to this consultation.  Most of the feedback was in support of the proposed new policy, though it is best in situations like this to follow the maxim that consultation responses are for reading not counting.  The key points raised in the feedback are as follows:

1.  People on both sides of the argument have stated that this will make it less likely that they participate onsite if the decision is not the way they hope.  (It is not feasible to estimate the relative "losses" in either direction as the variables are too complex.)

2.  Most of those in favour of masks have noted that this is a health issue, either related to them or a relative that they want to safeguard, that is a specific risk from being in a dense group of people in an enclosed space without good ventilation.  Others have countered that this situation is not unique to IETF meetings, and that anyone travelling too/from an IETF meeting will be unavoidably exposed to multiple similar situations where people will not be required to wear masks.  This counter-argument is disputed, particularly in regards to the impact of ventilation.

3.  Linked to the health concern has been the view that wearing masks is relatively low-impact, a irritation rather than a showstopper, and that requiring people to wear masks to protect the health of others is very little to ask.  Others have countered that people with a health concern should manage that by their own actions and not require others to do it for them.

4.  Some of those against masks have noted that masks have a strong, adverse impact on communication and that good communication is vital for onsite meetings.  Others have countered that this is not the case, and that we compensate for that by allowing masks to be removed at key times.

5.  Most of those against masks noted that there are no longer mask mandates from public health authorities and that if our meetings were situations of significantly higher risk such that masks were needed, then this would be for the public health authorities to decide and not us.  Others have countered that we should be looking at the specifics of our meetings and assessing the risk of those.

6.  There was very little discussion about vaccinations.

7.  There was general consensus that those who test positive should continue to isolate and not participate onsite, but not on how long that was for.

8.  There have been multiple discussions about whether or not masks work and whether or not mask mandates work

9.  There was a concrete proposal that if the local regulations *recommend* masks, then we should *mandate* masks.


The IESG and IETF LLC have considered the feedback and agreed that it is the best interest of the IETF to continue as proposed in the consultation and remove all mask/vaccine requirements for IETF 117 and beyond, unless required to by local regulation.  In making this decision, the IESG and IETF LLC want to explicitly recognise that there are some who will not wish to participate onsite and to assure those people and the rest of the community that this decision is not taken lightly.  The two key reasons that this is considered in the best interests for the IETF are:

a.  We should be a rational, evidence-led organisation and in the case of COVID, where public health authorities have extensive data on which to base their public health guidelines, that means supporting and following those guidelines.

b.  The practicalities will become increasingly difficult if we remain an an outlier and without any perceived "independent legitimacy" to our stance such as public health guidance.  It will quite quickly become more difficult to enforce, more confrontational and much more of a distraction during the meeting.  

On point 7 above, participants who test positive will be asked to follow the local guidelines for isolation after a positive test, accepting that in some countries there are only recommendations not regulations and so participants would be free to continue in the meeting.  If you have concerns about this point, then please raise them - it may be that further discussion/consultation is required on this specific point.

On point 9 above, if local public health authorities recommend masks in a setting like an IETF meeting, then we will also recommend them, but we will follow the public health advice and not mandate them.

Finally, as a reminder, the IETF continues to invest in improving the remote participation experience with the aim of making it as good as possible, and seeks feedback after each meeting to assess if that improvement is being achieved.


Thanks again for your feedback.


[1]  https://mailarchive.ietf.org/arch/msg/ietf-announce/usQEwqk9iFPmLm9awlwOCun7y7g/
[2]  https://mailarchive.ietf.org/arch/browse/admin-discuss/?q=COVID%20management%20IETF%20117


-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org