RFC 9137: Considerations for Cancellation of IETF Meetings
In plain English — editorial summary, not part of the RFC
The IETF ordinarily holds three in-person meetings per year to discuss issues and advance the Internet. However, various events can make a planned in-person meeting infeasible. This document provides criteria to aid the IETF Administration LLC (IETF LLC), the Internet Engineering Steering Group (IESG), and the Chair of the Internet Research Task Force (IRTF) in deciding to relocate, virtualize, postpone, or cancel an in-person IETF meeting.
Document record
- Document ID
- RFC9137
- Published
- October 2021
- Authors
- M. Duke
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- gen
- Pages
- 7
- Also known as
- BCP226
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9311Running an IETF HackathonCurrent
September 2022
- RFC 9389Nominating Committee EligibilityCurrent
April 2023
- RFC 8875Working Group GitHub AdministrationCurrent
August 2020
- RFC 8874Working Group GitHub Usage GuidanceCurrent
August 2020
- RFC 9400Guidelines for the Organization of Fully Online MeetingsCurrent
June 2023
- RFC 9501Open Participation Principle regarding Remote Registration FeeCurrent
December 2023
- RFC 8721Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF DocumentsCurrent
February 2020
- RFC 8719High-Level Guidance for the Meeting Policy of the IETFUpdated
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?