Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

Considerations for Cancellation of IETF Meetings
RFC 9137 part of BCP 226

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2023-12-12	(System)	Imported membership of rfc9137 in bcp226 via sync to the rfc-index
2023-12-12	(System)	No history of BCP226 is currently available in the datatracker before this point
2021-10-12	(System)	Received changes through RFC Editor sync (created alias RFC 9137, changed abstract to 'The IETF ordinarily holds three in-person meetings per year to discuss … Received changes through RFC Editor sync (created alias RFC 9137, changed abstract to '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.', changed pages to 7, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2021-10-12, changed IESG state to RFC Published)
2021-10-12	(System)	RFC published