Consultation on removing IETF-specific COVID management rules for IETF 117 San Francisco and beyond

IETF Executive Director <exec-director@ietf.org> Wed, 22 March 2023 14:26 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 56C2CC1524D3 for <ietf-announce@ietfa.amsl.com>; Wed, 22 Mar 2023 07:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf-org.20210112.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 WnXSDdBmqQnc for <ietf-announce@ietfa.amsl.com>; Wed, 22 Mar 2023 07:26:43 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 23E5CC153CA8 for <ietf-announce@ietf.org>; Wed, 22 Mar 2023 07:26:43 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id i9so17275743wrp.3 for <ietf-announce@ietf.org>; Wed, 22 Mar 2023 07:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20210112.gappssmtp.com; s=20210112; t=1679495201; h=to:date:message-id:subject:mime-version:reply-to :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=u4am+Y3n+Q3c0EK8y37GaQflvr8ANBhd6zZx9F8qp50=; b=e8xQfY27Vsy8aq/9dJSvseuo9Q3cCBP24IfXQ7+FkSMnh3DFmmGPKVP8ICfhzaoXcv SduhSI8+LM9BovfdVbJDPTc52s9D4wc+o/XZm9Esb5dTc6o4+Gvz6UVLeHjJJ09LgLZD V4qweqSNky5H5pWyM2sgkoDnBxcjRn7gMVGz5U8guLg28GiRwZ5VC5vaO0bWTT7fIcWE NjP6CWgfgehTVza6lt+krQv/zZtU6YmFRzdv3mrleAL+RQ0pg3D41k7eGrxcCw5S5/Yj JDxhjyu3+jMre47KdL0Pbi50+NdcTVbwV2JCKzoaHFTiar2QnPi0lFCK2DyRa+1VYt1+ ZVqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679495201; h=to:date:message-id:subject:mime-version:reply-to :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=u4am+Y3n+Q3c0EK8y37GaQflvr8ANBhd6zZx9F8qp50=; b=K1ia+k/nirrohLHLOzFmj4h6Ph00Nlg98Rcvh0Ax1pCrqgahv/35+BfiIPuoCgsj8e aM4WqnpnVOOXIZlXljLOeFn+URmz33C+zhqgNdyDqkaPXgGwmpjldfYqZFOcInAIT+gK 0j+H93qfSaYsC2lAyLqo5PBHrVEfUQpzeteu9PgqB0YjrefcrdIQ94Rxhx59shDTMP1j K6UuEnnmOJiNzmgRsdWFGVVsWsCZVCXbf+pgUUcA9gQFI3oPGxcooFUMRayz1R86f2I4 XjyLey0y/uRHe1qnn2snCriNE41mTJqrUIIQJOn8Gq6Bjv7LfMzxN7CNtWAL/GVR1cNB 2ujw==
X-Gm-Message-State: AO0yUKXzFEMWdcgmtWTMnAPvoCeyPl9U8NAUMXSBY2zp9135p16ssvgW tvxb1SyVmpC9bsEkOO3f7TMemwf9s/kd3G9HvCUsK38X
X-Google-Smtp-Source: AK7set9Xu01wx+v0M6jEXcSMzvzsCL2QjgdRgbllPulwlqS/5+xDMcfosUPCvDuIulMwHjWIEDZPOg==
X-Received: by 2002:a5d:510b:0:b0:2c8:c667:1bb4 with SMTP id s11-20020a5d510b000000b002c8c6671bb4mr5310963wrt.48.1679495200994; Wed, 22 Mar 2023 07:26:40 -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 f18-20020adff452000000b002c5d3f0f737sm13996825wrp.30.2023.03.22.07.26.40 for <ietf-announce@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Mar 2023 07:26:40 -0700 (PDT)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Reply-To: admin-discuss@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
Subject: Consultation on removing IETF-specific COVID management rules for IETF 117 San Francisco and beyond
Message-Id: <5D041DF7-361B-45BD-923E-D677CFB1A287@ietf.org>
Date: Wed, 22 Mar 2023 14:26:29 +0000
To: IETF Announcement List <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/usQEwqk9iFPmLm9awlwOCun7y7g>
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: Wed, 22 Mar 2023 14:26:45 -0000

Since IETF 113 Vienna, when the IETF first returned to onsite meetings following the outbreak of COVID, onsite participants at IETF meetings have been required to confirm their vaccination status and wear masks.  Initially this was a local legal requirement, but since IETF 114 Philadelphia this has been an IETF-specific requirement, decided upon after community consultation.  The IETF Administration LLC and the IESG now wish to revisit these IETF-specific requirements for COVID management, for implementation for IETF 117 San Francisco and beyond.

We start from the general principle that we should not impose out-of-the-ordinary restrictions on participants and the meeting process, without compelling reasons to do so.  While we would strongly prefer to start from a neutral position and have an evidence-based and people-centred discussion to determine if such compelling reasons exist, that is clearly not possible as views have become entrenched in both the IETF community and society in general.  

Instead, we make a judgement call that the trade-off between the risk to vulnerable participants, and the effects of out-of-the-ordinary restrictions on participants and the meeting process, will have reached a point by IETF 117 San Francisco where these IETF-specific restrictions should not be sustained.

We therefore propose to drop all of the IETF-specific COVID management requirements for IETF 117 San Francisco and beyond, unless we are required to impose them or the circumstances of COVID significantly change.  We intend to continue to provide free masks and COVID tests for IETF 117 San Francisco and IETF 118 Prague, and will review this practice after that.

We understand that this proposed change will exclude some from participating onsite at IETF Meetings for at least the near future, and we do not make this proposal lightly.  We will continue to invest in our remote participation services so that those who participate remotely have as good an experience as possible. We will also ensure that IETF meetings remain a safe and welcoming environment for those who choose to wear masks and we will not tolerate any actions aimed at dissuading people from doing so.

While we have made this judgement call, we are willing to listen to the community and willing to reconsider this proposal.  This is by no means a clear or simple decision to make.  So please tell us what you think.

We now welcome community feedback on this proposal.  Please provide your feedback either to the public list admin-discuss@ietf.org or to me directly at exec-director@ietf.org, before 17 April 2023.  We would like to avoid this feedback process becoming a heated and intractable debate, so if possible please avoid responding directly to feedback you disagree with. 

To reiterate, IETF 116 Yokohama continues under the existing policy and is unaffected by this consultation.

-- 
Lars Eggert, IETF Chair
Jay Daley, IETF Executive Director