Cite this BCP: TXT
BCP 226 contains the following RFCs:| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 8718, BCP 226 | IETF Plenary Meeting Venue Selection Process | E. Lear, Ed. | February 2020 | Best Current Practice | ||
| RFC 8719, BCP 226 | High-Level Guidance for the Meeting Policy of the IETF | S. Krishnan | February 2020 | Best Current Practice | ||
| RFC 9137, BCP 226 | Considerations for Cancellation of IETF Meetings | M. Duke | October 2021 | Best Current Practice |
Abstract of RFC 8718
The IETF Administration Support Activity (IASA) is responsible for arranging the selection and operation of the IETF plenary meeting venue. This memo specifies IETF community requirements for meeting venues, including hotels and meeting space. It also directs the IASA to make available additional process documents that describe the current meeting selection process.
Abstract of RFC 8719
This document describes a meeting location policy for the IETF and the various stakeholders required to realize this policy.
Abstract of RFC 9137
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.