[rfc-dist] BCP 226, RFC 8718 on IETF Plenary Meeting Venue Selection Process

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Thu Feb 27 10:18:29 PST 2020


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 at 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 at 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


More information about the rfc-dist mailing list