Network Working Group | A. Cooper |
Internet-Draft | Cisco |
Intended status: Informational | R. Housley |
Expires: November 14, 2020 | Vigil Security |
S. Krishnan | |
Kaloom | |
May 13, 2020 |
Questions Arising Concerning In-Person Meeting Cancellation
draft-cooper-shmo-questions-00
The COVID-19 pandemic has required the IETF community to confront complicated questions about the cancellation and replacement of in-person meetings. This document lists some general questions that have come up for discussion in the community as the IESG, the IRTF Chair, and the IETF LLC have been faced with making decisions about IETF 107 and IETF 108.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 14, 2020.
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
The COVID-19 pandemic has required the IETF community to confront complicated questions about the cancellation and replacement of in-person meetings. This document lists some general questions that have come up for discussion as the IESG, the IRTF Chair, and the IETF LLC have been faced with making decisions about whether IETF 107 and IETF 108 should be held as in-person meetings. In many places, inspiration was drawn from [RFC8718] and [RFC8719].
This document is focused solely on questions concerning in-person meeting cancellation and it intentionally does not address planning for fully online meetings. This document is offered purely to frame discussion, and it is not intended to be published as an RFC.
[RFC8719] summarized the goal for face-to-face meetings of IETF WGs as mainly to provide a high-bandwidth mechanism for working out unresolved issues. Historically, these are held in locations from which most of the IETF participants have come in the recent past, with a goal of distributing the travel effort for the participants who attend in person and distributing the timezone difficulty for those who participate remotely. In the current climate, the IETF leadership, in consultation with the community, needs to determine whether an in-person meeting will be safe and effective.
Questions that have come up about participation and attendance include:
[RFC8718] includes the following criteria related to travel and entry:
"Travel to the Venue is acceptable based on cost, time, and burden for participants traveling from multiple regions. "Travel barriers to entry, including visa requirements, are likely to be such that an overwhelming majority of participants who wish to do so can attend. The term "travel barriers" is to be read broadly by the IASA in the context of whether a successful meeting can be had."
Questions that have come up related to travel and entry include:
[RFC8718] includes the following criteria related to safety and health:
"Economic, safety, and health risks associated with this Venue are acceptable."
Questions related to safety and health have centered around multiple dimensions:
[RFC8718] includes a criterion that says:
"The Venue is assessed as favorable for obtaining a host and sponsors."
While communication with IETF 107 and IETF 108 hosts and sponsors has been frequent, criteria related to host and sponsorship availability have not currently been used for determining cancellation plans for IETF 107 and IETF 108. We are thankful for the unconditional support of hosts and sponsors during these uncertain times, but we need to determine whether host and sponsor availability related criteria need to be included in the future.
Discussions about IETF 107 and IETF 108 have assumed that the meetings would be cancelled if the venues where the meetings were scheduled to be held were closed or otherwise unable to provide the contracted meeting services. Similarly, if mass gatherings in the venue city or country are banned, then it has been assumed our meetings would be cancelled.
Questions have arisen about how far in advance of a meeting a cancellation decision needs to be made. The level of flexibility around this depends on the circumstances, but when there is some flexibility, there has been discussion about whether a cancellation date should be chosen to give participants higher certainty further in advance or to be able to evaluate circumstances as close to the original meeting date as possible, or somewhere in between.
This note proposes no protocols and therefore introduces no new protocol insecurities.
This document has no IANA actions.
[RFC8718] | Lear, E., "IETF Plenary Meeting Venue Selection Process", BCP 226, RFC 8718, DOI 10.17487/RFC8718, February 2020. |
[RFC8719] | Krishnan, S., "High-Level Guidance for the Meeting Policy of the IETF", BCP 226, RFC 8719, DOI 10.17487/RFC8719, February 2020. |