[Mtgvenue] BCP 226, RFC 8718 on IETF Plenary Meeting Venue Selection Process

rfc-editor@rfc-editor.org Thu, 27 February 2020 18:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 543433A058F; Thu, 27 Feb 2020 10:18:45 -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 eMAyxHHERm-4; Thu, 27 Feb 2020 10:18:43 -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 EB1733A07DD; Thu, 27 Feb 2020 10:18:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8EF71F40749; Thu, 27 Feb 2020 10:18:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20200227181829.8EF71F40749@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:18:29 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/1nyMmfwNj6lXKX69Wu3C9XZhhlg>
Subject: [Mtgvenue] =?utf-8?q?BCP_226=2C_RFC_8718_on_IETF_Plenary_Meeting?= =?utf-8?q?_Venue_Selection_Process?=
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 18:18:52 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 226        
        RFC 8718

        Title:      IETF Plenary Meeting Venue Selection 
                    Process 
        Author:     E. Lear, Ed.
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2020
        Mailbox:    lear@cisco.com
        Pages:      10
        See Also:   BCP 226

        I-D Tag:    draft-ietf-mtgvenue-iaoc-venue-selection-process-16.txt

        URL:        https://www.rfc-editor.org/info/rfc8718

        DOI:        10.17487/RFC8718

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.

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