BCP 226, RFC 9712 on IETF Meeting Venue Requirements Review
rfc-editor@rfc-editor.org Mon, 27 January 2025 18:40 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59E2CC1D52FF; Mon, 27 Jan 2025 10:40:04 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id A59A91F4A61; Mon, 27 Jan 2025 10:40:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 226, RFC 9712 on IETF Meeting Venue Requirements Review
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250127184003.A59A91F4A61@rfcpa.rfc-editor.org>
Date: Mon, 27 Jan 2025 10:40:03 -0800
Message-ID-Hash: ZTMXPIOL75GQNUAJDGXP5IAOISPMLJB2
X-Message-ID-Hash: ZTMXPIOL75GQNUAJDGXP5IAOISPMLJB2
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/V87iWTfEGdIzUBpvpoOBhMhHcvY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
BCP 226
RFC 9712
Title: IETF Meeting Venue Requirements Review
Author: J. Daley,
S. Turner
Status: Best Current Practice
Stream: IETF
Date: January 2025
Mailbox: jay@staff.ietf.org,
sean@sn3rd.com
Pages: 10
Updates: RFC 8718, RFC 8719
See Also: BCP 226
I-D Tag: draft-daley-gendispatch-venue-requirements-03.txt
URL: https://www.rfc-editor.org/info/rfc9712
DOI: 10.17487/RFC9712
Following a review of the IETF meeting venue requirements, this
document updates RFC 8718 ("IETF Plenary Meeting Venue Selection
Process"), clarifies how the IETF Administration Support Activity
(IASA) should interpret some elements of RFC 8718, and specifies a
replacement exploratory meeting process, thereby updating RFC 8719
("High-Level Guidance for the Meeting Policy of the IETF").
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team