RFC 8718: IETF Plenary Meeting Venue Selection Process
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8718
- Published
- February 2020
- Authors
- E. Lear
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- gen
- Pages
- 10
- Also known as
- BCP226
- Updated by:
- RFC 9712
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8719High-Level Guidance for the Meeting Policy of the IETFUpdated
February 2020
- RFC 8717IETF Administrative Support Activity 2.0: Consolidated Updates to IETF Administrative TerminologyCurrent
February 2020
- RFC 8715IETF Administrative Support Activity 2.0: Update to the Process for Selection of Trustees for the IETF TrustCurrent
February 2020
- RFC 8721Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF DocumentsCurrent
February 2020
- RFC 8713IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall CommitteesUpdated
February 2020
- RFC 8712The IETF-ISOC RelationshipCurrent
February 2020
- RFC 8711Structure of the IETF Administrative Support Activity, Version 2.0Current
February 2020
- RFC 8716Update to the IETF Anti-Harassment Procedures for the Replacement of the IETF Administrative Oversight Committee (IAOC) with the IETF Administration LLCCurrent
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?