IAOC Plenary Meeting Venue Selection Process
draft-baker-mtgvenue-iaoc-venue-selection-process-00

Abstract

This documents the IAOC's IETF Meeting Venue 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 http://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 September 8, 2016.

Copyright Notice

Copyright (c) 2016 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 (http://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.

Table of Contents

• 1. Introduction
• 1.1. Requirements Language
• 2. Meeting Selection Participants and Responsibilities
• 2.1. The IETF Community
• 2.2. IESG and IETF Chair
• 2.3. The Internet Society
• 2.4. IETF Administrative Oversight Committee
• 2.5. IETF Administrative Support Activity
• 2.6. IETF Administrative Director
• 2.7. IAOC Meeting Committee
• 3. Venue Selection Process
• 3.1. Venue Selection Principles
• 3.2. Venue Selection Objectives
• 3.3. Venue Selection Criteria
• 3.3.1. Venue City Criteria
• 3.3.2. Basic Venue Criteria
• 3.3.3. Technical Services and Operations Criteria
• 3.3.4. Lodging
• 3.3.5. Food and Beverage
• 3.4. Non-criteria
• 3.5. Venue Selection Timeline
• 3.6. Experience Notes
• 4. Transparency
• 5. IANA Considerations
• 6. Security Considerations
• 7. Privacy Considerations
• 8. Contributors
• 9. References
• 9.1. Normative References
• 9.2. Informative References
• Appendix A. Change Log
• Author's Address

1. Introduction

This document describes the IETF Meeting Venue Selection Process. In December 2015 and January 2016, there was a discussion on the IETF list of the selection process and criteria for IETF meetings. In response to that discussion, the IAOC and the IAOC Meetings Committee took it upon themselves to create this document.

This document describes the process that is expected to be followed.

1.1. Requirements Language

Requirements called out in this document are identified as either "mandatory" or "desired". For clarity, the terms are defined here:

Mandatory:

If this requirement cannot be met, a location under consideration is unacceptable. We walk away.

Desired:

We would very much like to meet this requirement, but have frequently been unable to. The fact that we could not meet it is considered in comparison to other sites.

2. Meeting Selection Participants and Responsibilities

The formal structure of IETF administrative support functions is documented in BCP 101 [RFC4071][RFC4371][RFC7691]. The reader is expected to be familiar with the entities and roles defined by that document, in particular for the IASA, ISOC, IAOC and IAD. This section covers the meeting selection related roles of these and other parties that participate in the process. Note that roles beyond meeting selection, e.g., actually running and reporting on meetings, are outside the scope of this document.

2.1. The IETF Community

While somewhat obvious to most, it is important to note that IETF meetings serve all those who contribute to the development of IETF RFCs. This includes those who attend meetings, from newcomer to frequent attendee, to those who participate remotely, and to those who don't attend but contribute to new RFCs. Potential new contributors are also considered in the process.

IETF consensus with respect to the meeting venue selection process is judged via standard IETF process and not by any other means, e.g., surveys.

2.2. IESG and IETF Chair

The Internet Engineering Steering Group (IESG) is a group comprised of the IETF Area Directors and the IETF Chair. The IESG is responsible for the management, along with the IAB, of the IETF, and is the standards approval board for the IETF, as described in BCP9 [RFC2026]. This means that the IESG sets high level policies related to, among other things, meeting venues. The IETF Chair is a member of the IESG who, among other things, relays policies to the IAOC. The IETF Chair is also a member of the IAOC.

2.3. The Internet Society

The Internet Society (ISOC) executes all venue contracts on behalf of the IETF at the request of the IAOC; solicits meeting sponsorships; collects all meeting-related revenues, including registration fees, sponsorships, hotel commissions, and other miscellaneous revenues. ISOC also provides accounting services, such as invoicing and monthly financial statements. The meetings budget is managed by the IAD.

2.4. IETF Administrative Oversight Committee

The IETF Administrative Oversight Committee (IAOC) has the responsibility to oversee and select IETF meeting venues. It instructs the IAD to work with the Internet Society to write the relevant contracts. It approves the IETF meetings calendar.

2.5. IETF Administrative Support Activity

The IETF Administrative Support Activity (IASA) supports the meeting selection process. This includes identifying, qualifying and reporting on potential meeting sites, as well as supporting meeting venue contract negotiation. The IETF Secretariat is part of the IASA under the management of the IAD.

2.6. IETF Administrative Director

The IETF Administrative Director (IAD) coordinates and supports the activities of the IETF Secretariat, the IAOC Meetings Committee and the IAOC to ensure the timely execution of the meeting process. This includes participating in the IAOC Meeting Subcommittee and ensuring its efforts are documented, leading venue contract negotiation, and coordinating contract execution with ISOC.

2.7. IAOC Meeting Committee

The IAOC Meeting Committee is generally referred to as the Meetings Committee.

The fundamental purpose of the committee is to participate in the venue selection process, and to formulate recommendations to the IAOC regarding meeting sites. It also tracks the meetings sponsorship program, recommends extraordinary meeting-related expenses, and recommends the IETF meetings calendar to the IAOC. The charter of the committee is located here: https://iaoc.ietf.org/committees.html#meetings.

Membership in the Meetings Committee is at the discretion of the IAOC; it includes an IAOC appointed chair, the IETF Administrative Director (IAD), IAOC members, representatives from the Secretariat, and interested members of the community.

3. Venue Selection Process

The process of selecting a venue is described below and is based on https://iaoc.ietf.org/venue-selection.html.

3.1. Venue Selection Principles

The IETF, and therefore the IAOC and its Meetings Committee, have some core values that pervade the selection process. These are not limited to the following, but at minimum include them.

Who are we?

We are computer scientists, engineers, network operators, academics, and other interested parties sharing the goal of making the Internet work better. At this time, the vast majority of attendees come from North America, Western and Central Europe, and Eastern Asia. We also have participants from other regions.

Why do we meet?

We meet to advance Internet standards development, to advance Internet Drafts and RFCs. We meet at one location to facilitate attendees participation in multiple topics and to enable cross-pollination of ideas and technology.

Where do we meet?

We meet in different locations globally in order to spread the pain and cost of travel among active participants, balancing travel time and expense across the regions from where IETF participants are based. We also aim to enhance inclusiveness and new contributions.

Inclusiveness:

We would like to facilitate the onsite or remote participation of anyone who wants to be involved. Every country has limits on who it will permit within its borders. This principle of inclusiveness militates against the selection of venues within countries that impose visa regulations and/or laws that effectively exclude people on the basis of race, religion, gender, sexual orientation, or national origin, and to a lesser extent, reduces the likelihood of selecting countries that use such attributes to make entry difficult.

Internet Access:

As an organization, we write specifications for the Internet, and we use it heavily. Meeting attendees need unfiltered access to the general Internet and our corporate networks, which are usually reached using encrypted VPNs from the meeting venue and hotels. We also need open network access available at high enough data rates to support our work, including the support of remote participation.

Focus:

We meet to have focused technical discussions. These are not limited to breakout sessions, although of course those are important; they also happen over meals or drinks (including a specific type of non-session that we call a "Bar BOF"), or in side meetings. Environments that are noisy or distracting prevent that or reduce its effectiveness, and are therefore less desirable as a meeting venue.

Economics:

Meeting attendees participate as individuals. While many have their participation underwritten by employers or sponsors, there are many who do not. Locations that do not provide convenient budget alternatives for food and lodging are therefore exclusionary, and violate our value of "Inclusiveness".

3.2. Venue Selection Objectives

Venues for meetings are selected to advance the objectives of the IETF, which are discussed in https://www.ietf.org/about/mission.html. The IAOC's supporting objectives include:

• Advancing standards development
• Facilitating participation by active contributors
• Sharing the travel pain; balancing travel time and expense across the regions from where IETF participants are based.
• Encouraging new contributors

There is an explicit intent to rotate meeting locations equally among North America, Europe/Africa, and Asia/ Australia regions in accordance with IETF policy. However, a consistent balance is sometimes difficult to achieve. The IAOC has an objective of setting the Regions 4 years in advance following the 1-1-1* model per year: 1 meeting in Europe, 1 in North America, and 1 in Asia/Pacific, with a possibility ("*") of a meeting outside those regions. This policy, which known as the 1-1-1* model, is set by the IESG, https://iaoc.ietf.org/minutes/2010-11-10-iaoc-minutes.txt. The reason for the multi-year timeframe is fundamentally maximization of opportunities; the smaller the time available to qualify and contract a conference venue, the more stress imposed on the qualification process, and the greater the risk of not finding a suitable venue or paying more for it.

There is no formal policy regarding the time of year for a meeting in a specific region or whether a meeting in a non-targeted region replaces a visit to one of the regions during that year.

The IETF chair drives selection of "*" locations, i.e., venues outside the usual 1-1-1 regions, and requires community input. These selections usually arise from evidence of growing interest and participation in the new region. Expressions of interest from possible hosts also factor into the meeting site selection process, both for the 1-1-1 regions and other regions.

Increased participation in the IETF from those other regions, electronically or in person, could result in basic changes to the overall pattern, and we encourage those who would like for that to occur to encourage participation from those regions.

3.3. Venue Selection Criteria

A number of criteria are considered during the site selection process. The list following is not sorted in any particular order, but includes the committee's major considerations.

The selection of a venue always requires trade-offs. There are no perfect venues. For example, a site may not have a single hotel that can accommodate a significant number of the attendees of a typical IETF. That doesn't disqualify it, but it may reduce its desirability in the presence of an alternative that does.

3.3.1. Venue City Criteria

• Travel to the venue is reasonably acceptable based on cost, time, and burden for participants traveling from multiple regions. It is anticipated that the burden borne will be generally shared over the course of the year. [Mandatory]
• Travel barriers to entry, e.g., visa requirements that can limit participation, are researched, noted, and carefully considered. [Mandatory]
• Economic, safety, and health risks associated with this venue are researched, reviewed and carefully considered, at the time the selection is made, and thereafter as the time for the meeting approaches. [Mandatory]
• Prior successful IETF experience with the Venue and Venue city will be considered as a positive factor when when deciding among multiple venues. [Desired]
• Consideration will be given to whether it makes sense to enter into a multi-event contract with the venue to optimize meeting and attendee benefits, i.e., reduce administrative costs and reduce direct attendee costs. [Desired]
• The venue is assessed as favorable for obtaining a host and sponsors. That is, the Meeting is in a location and at a price that it is possible and probable to find a host and sponsors. [Desired]

3.3.2. Basic Venue Criteria

• The Meeting Space is adequate in size and layout to accommodate the meeting and foster participant interaction. [Mandatory]
• The venue and hotels can be put under contract. The subsequent failure to put a selected venue under contract will result in a re-evaluation of the venues and selection for the meeting. [Mandatory]
• The cost of guest rooms, meeting space, meeting food and beverage is affordable (within the norms of business travel). [Mandatory]
• An Optimal Facility for an IETF meeting is held under "One Roof", that is, qualified meeting space and guest rooms are available in the same facility. [Desired]

3.3.3. Technical Services and Operations Criteria

• The Venue's support technologies and services -- network, audio- video, etc., are sufficient for the anticipated activities at the meeting, or the venue is willing to add such infrastructure at no or at an acceptable cost to the IETF. [Mandatory]
• The meeting venue must permit and facilitate the delivery of a high performance, robust, unfiltered and unmodified IETF Network. [Mandatory]
• The IETF hotel(s), which are one or more hotels in close proximity to the venue where the primary IETF room allocations are negotiated and the IETF SSIDs are in use, must provide, or permit and facilitate, the delivery of a high performance, robust, unfiltered and unmodified Internet service for the public areas and guest rooms. This service is typically included in the cost of the room. [Mandatory]
• The overflow hotels should provide reasonable, reliable, unfiltered Internet service for the public areas and guest rooms. This service is typically included in the cost of the room. [Desired]

3.3.4. Lodging

• The IETF hotel(s) is within close proximity to venue. [Mandatory]
• The Guest Rooms at the IETF hotel(s) are sufficient in number to house 1/3 or more of projected meeting attendees. [Mandatory]
• The Venue environs include budget hotels within convenient travel time, cost, and effort. [Mandatory]
• Overflow Hotels that can be placed under contract. They typically must be within convenient travel time of the venue and have a variety of guest room rates. [Mandatory]

3.3.5. Food and Beverage

• The Venue environs, which includes onsite, and the areas within a reasonable walking distance, or conveniently accessible by a short taxi, bus, or subway ride, has convenient and inexpensive choices for meals that can accommodate a wide range of dietary requirements. [Mandatory]
• The Venue environs include grocery shopping that will accommodate a wide range of dietary requirements, within a reasonable walking distance, or conveniently accessible by a short taxi, bus, or subway ride. [Desired]

3.4. Non-criteria

The following is specifically not among the selection criteria:

• Visiting new locations for the sake of variety in meeting locations.

3.5. Venue Selection Timeline

Commencing the process four years in advance of an event results in the following schedule as a guideline:

4 years out:

1. 4 years out, the IAOC selects regions for meetings
2. Meeting target cities per region are provided to the Secretariat based upon Meetings Committee input and, if known, host preferences.
3. Potential venues in preferred cities identified, investigated and pre-qualified Venue options are provided to the Meetings Committee for consideration.
4. Meetings Committee approves potential venues for site qualification visit.
5. Site qualification visits are arranged and preliminary negotiations are undertaken with selected potential sites
6. Site qualification visit is conducted and a site report is prepared. Recommendations of the site visit team are provided to Meetings Committee. The Meetings Committee reviews the venue options based on venue selection criteria and makes a recommendation to IAOC
7. IAOC reviews the Meetings Committee recommendation, and the selection criteria, and selects or rejects the recommended venue. If a venue is selected the IAOC requests the Internet Society to enter into agreements to effect the selection. If the recommendation is rejected the IAOC notifies the Meetings Committee of the rejection and the reasons why.

2.75-3 years out:

1. Contract negotiations with selected venue by Secretariat and IAD IAD reviews contract and requests IAOC and ISOC approval of contract and authority for Secretariat to execute contract on ISOC's behalf.
2. Contracts are executed.

3.6. Experience Notes

1. The foregoing process works with reasonable certainty in North America and Europe.
2. Experience to date for Asia and Latin America is that contracts take longer and often will not be executed more than two years in advance of the meeting. While the IETF will have the first option for the dates, for reasons not completely understood contracts won't be executed.

4. Transparency

BCP 101 requires transparency in IASA process and contracts, and thereby of the meetings committee. BCP 101 also states that the IAOC approves what information is to remain confidential. Therefore any information produced by the meetings committee or related to meetings that individuals believe is confidential, e.g., venue contracts, must be confirmed to be confidential by the IAOC.

5. IANA Considerations

This memo asks the IANA for no new parameters.

6. Security Considerations

This note proposes no protocols, and therefore no new protocol insecurities.

7. Privacy Considerations

This note reveals no personally identifying information apart from its authorship.

8. Contributors

This note was developed by Dave Crocker, Fred Baker, Jari Arkko, Jim Martin, Laura Nugent, Lou Berger, Ole Jacobsen, Ray Pelletier, and Scott Bradner.

9. References

9.1. Normative References

9.2. Informative References

Appendix A. Change Log

2016-01-12:

Initial version

2016-01-21:

Update to reflect https://iaoc.ietf.org/documents/VenueSelectionCriteriaJan2016.pdf and https://iaoc.ietf.org/documents/VenueSelectionProcess11Jan16.pdf, accessed from https://iaoc.ietf.org/private/privatemeetings.html.

2016-02-23:

Reorganize and capture IAOC Meetings Committee discussions.

2016-03-03:

Final from Design Team.

Author's Address