Follow up on consultation on IETF 112 and COVID-related restrictions

IETF Executive Director <exec-director@ietf.org> Mon, 02 August 2021 23:49 UTC

Return-Path: <exec-director@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 A4C4C3A21B1; Mon, 2 Aug 2021 16:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Mk6x-QDbX07M; Mon, 2 Aug 2021 16:49:12 -0700 (PDT)
Received: from smtpclient.apple (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 150B33A21B3; Mon, 2 Aug 2021 16:49:11 -0700 (PDT)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Reply-To: manycouches@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Subject: Follow up on consultation on IETF 112 and COVID-related restrictions
Date: Tue, 03 Aug 2021 11:49:08 +1200
Message-Id: <0AD65B7F-38BB-4AD6-B11B-226E01EDA1BC@ietf.org>
Cc: manycouches@ietf.org
To: IETF Announcement List <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/O7fmfHzSfR-b-QlpBhCitD45iO4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Aug 2021 23:49:17 -0000

The IESG, IETF Administration LLC and IRTF Chair recently sought feedback [1] to assist in the decisions on whether to go ahead in-person for IETF 112 Madrid or switch to a fully online meeting.  This consultation has now closed and the feedback received is reported on below:

1.  Survey of possible onsite participants
 
The results are available in an interactive dashboard https://ql.tc/c7Td95  This survey shows that there are people who will definitely attend in person and that they will attend with the known restrictions of mask wearing, social distancing and vaccines or negative tests.  Estimating the number of likely participants is going to take more work.

2.  Assessment criteria

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:

- Sufficient critical support staff and contractors can be at the venue and available remotely as needed 
- The meeting will not result in a significant unbudgeted financial loss for the IETF LLC

3.  Interim planning guidelines and conditional plan for IETF meetings in a COVID-impacted venue

There was significant discussion on this topic, though only a small amount was directly relevant.  The following feedback will be incorporated somehow:

- Use a lottery instead of FCFS if onsite registrations are limited
- Contingency planning in the event of a major change in circumstances, such as a lockdown being imposed during the week
- Understanding the implications of holding a meeting where people from certain countries cannot attend.

The following feedback has not been incorporated

- the IETF should only allow vaccinated people to participate in-person.  This requires community consensus.
- 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.
- the IETF should specify the least invasive testing method.  The IETF will not be doing any testing itself and any requirements will be based solely on local laws/regulations.


Work has begun on assessing if IETF 112 Madrid can go ahead as an in-person meeting with an announcement due next Monday 9 August or earlier.


[1]  https://mailarchive.ietf.org/arch/msg/ietf-announce/R-1NLlYaYrZ7ldFZ0oPQWCFKfZg/
[2]  https://datatracker.ietf.org/doc/draft-ietf-shmoo-cancel-meeting/

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