BCP 226, RFC 8719 on High-Level Guidance for the Meeting Policy of the IETF
rfc-editor@rfc-editor.org Thu, 27 February 2020 18:18 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC8E43A03F3; Thu, 27 Feb 2020 10:18:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U5ywQZxuUlfX; Thu, 27 Feb 2020 10:18:53 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E7AE3A0778; Thu, 27 Feb 2020 10:18:53 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3B131F40752; Thu, 27 Feb 2020 10:18:39 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 226, RFC 8719 on High-Level Guidance for the Meeting Policy of the IETF
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mtgvenue@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200227181839.3B131F40752@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:18:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/n44Y0DrDM7jWvu2uqgMG2bHCwq8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 18:19:00 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 226
RFC 8719
Title: High-Level Guidance for the Meeting Policy
of the IETF
Author: S. Krishnan
Status: Best Current Practice
Stream: IETF
Date: February 2020
Mailbox: suresh@kaloom.com
Pages: 5
See Also: BCP 226
I-D Tag: draft-ietf-mtgvenue-meeting-policy-07.txt
URL: https://www.rfc-editor.org/info/rfc8719
DOI: 10.17487/RFC8719
This document describes a meeting location policy for the IETF and
the various stakeholders required to realize this policy.
This document is a product of the Meeting Venue Working Group 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
Association Management Solutions, LLC