IETF Plenary Meeting Venue Selection Process
draft-ietf-mtgvenue-iaoc-venue-selection-process-16

Document Type Active Internet-Draft (mtgvenue WG)
Last updated 2018-10-08 (latest revision 2018-06-14)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Pete Resnick
Shepherd write-up Show (last changed 2017-12-20)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state AUTH48
mtgvenue                                                    E. Lear, Ed.
Internet-Draft                                             Cisco Systems
Intended status: Best Current Practice                     June 14, 2018
Expires: December 16, 2018

              IETF Plenary Meeting Venue Selection Process
          draft-ietf-mtgvenue-iaoc-venue-selection-process-16

Abstract

   The IASA has responsibility for arranging IETF plenary meeting Venue
   selection and operation.  This memo specifies IETF community
   requirements for meeting venues, including hotels and meeting room
   space.  It directs the IASA to make available additional process
   documents that describe the current meeting selection process.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 16, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Lear                    Expires December 16, 2018               [Page 1]
Internet-Draft               Venue Selection                   June 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Venue Selection Objectives  . . . . . . . . . . . . . . . . .   3
     2.1.  Core Values . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Venue Selection Non-Objectives  . . . . . . . . . . . . .   5
   3.  Meeting Criteria  . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Mandatory Criteria  . . . . . . . . . . . . . . . . . . .   5
     3.2.  Important Criteria  . . . . . . . . . . . . . . . . . . .   6
     3.3.  Other Consideraitons  . . . . . . . . . . . . . . . . . .   9
   4.  Documentation Requirements  . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  10
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The Internet Administrative Support Activity (IASA) has
   responsibility for arranging IETF plenary meeting venue selection and
   operation.  The purpose of this document is to guide the IASA in
   their selection of regions, cities, facilities, and hotels.  The IASA
   applies this guidance at different points in the process in an
   attempt to faithfully meet the requirements of the IETF community.
   We specify a set of general criteria for venue selection and several
   requirements for transparency and community consultation.

   It remains the responsibility of the IASA to apply their best
   judgment.  The IASA accepts input and feedback both during the
   consultation process and later (for instance when there are changes
   in the situation at a chosen location).  Any appeals remain subject
   to the provisions of BCP101 [RFC4071].  As always, the community is
   encouraged to provide direct feedback to the Nominations Committee
   (NOMCOM), Internet Engineering Steering Group (IESG), and IAB
   regarding the discharge of the IASA's performance.

   Four terms describe the places for which the IETF contracts services:

   Venue:
      This is an umbrella term for the city, meeting resources and guest
      room resources.

Lear                    Expires December 16, 2018               [Page 2]
Show full document text