IAOC R. Pelletier
Internet-Draft Internet Society
Intended status: Best Current Practice L. Nugent
Expires: February 23, 2017 Association Management Solutions
D. Crocker
Brandenburg InternetWorking
L. Berger
LabN Consulting, L.L.C.
O. Jacobsen
The Internet Protocol Journal
J. Martin
F. Baker
August 22, 2016

IAOC Plenary Meeting Venue Selection Process


This documents the IAOC's IETF Meeting Venue Selection Process from the perspective of its goals and thought processes. It points to additional process documents on the IAOC Web Site that go into further detail and are subject to change with experience.

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 February 23, 2017.

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

This document describes the IETF Meeting Venue Selection Process from the perspective of goals and thought processes. Following IETF 94 and at IETF 95 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 more publicly document its process and involve community input.

This document describes the objectives and principles behind the venue selection process. It also discusses the actual selection process to one level of detail, and points to working documents used in execution.

1.1. Requirements Language

Requirements called out in this document are identified as either "mandatory" or "desired", and considerations are tagged as "Important" or "Would be nice". For clarity, the terms are defined here:

If this requirement cannot be met, a location under consideration is unacceptable. We walk away.
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.
Can be a make-or-break consideration, but can also be traded off against other considerations.
Would be nice:
Not make-or-break, but warrants additional consideration if found to be true.

2. Venue Selection Objectives

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.

Why do we meet?

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

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.
There may be other points from Section 6.1.1 to move here.

3. Venue Selection Non-Objectives

IETF meeting venues are not selected for the purposes of:

4. 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.

Each identified criterion is labeled with the terms defined above in Section 1.1, i.e., "Mandatory", "Desired", "Important" or "Would be nice". These terms guide the trade-off analysis portion of the selection process. All "Mandatory" labeled criteria must be met for a venue to be selected. The remaining terms may be viewed as weighting factors.

There are times where the evaluation of the criteria will be subjective. This is even the case for criteria labeled as "Mandatory". For this reason, the Meetings Committee will specifically review, and affirm to its satisfaction, that all "Mandatory" labeled criteria are satisfied by a particular venue and main IETF hotel as part of the process defined below in Section 5.8.

4.1. Venue City Criteria

Note that these considerations are not "make or break" but flexible enough to allow for trade-offs and judgement on the part of the IAOC. Ideally, a city will meet all criteria. If all criteria cannot be met, the IETF community needs to consider the trade-off acceptable.

4.2. Basic Venue Criteria

4.3. Technical Services and Operations Criteria

4.4. Lodging Criteria

4.5. Food and Beverage Criteria

5. Venue Selection Process

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.

5.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. Surveys are used to gather information related to meeting venues, but not to measure consensus.

5.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.

5.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.

5.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.

5.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.

5.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.

5.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.

5.8. Venue Selection Phases

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

Phase 1:
Identification and Preliminary Investigation
Four years out, a process identifies cities for meetings and initiates site selection.
  1. 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 and investigated, including reviews of Official Advisory Sources, consultation with specialty travel services, frequent travelers and local contacts to identify possible barriers to holding a successful meeting in the target cities.
  4. Investigated cities and findings are provided by the Secretariat to the Meetings Committee for review. Meetings Committee makes a recommendation to the IAOC of investigated/target cities to consider further as well as issues identified and the results of research conducted.
Phase 2:
Community Consultation
The IAOC asks the community whether there are any barriers to holding a successful meeting in the target cities. Community responses are reviewed and concerns investigated. IAOC provides a list of vetted cities to the Meetings Committee to pursue as potential meeting locations.
Phase 3:
Vetted Venues Evaluated for Site Qualification Visit
  1. Secretariat Assesses "vetted" target cities to determine availability and conformance to criteria
  2. Meetings Committee approves potential cities for site qualification visit.
  3. Site qualification visits are arranged by Secretariat and preliminary negotiations are undertaken with selected potential sites
  4. Site qualification visit is conducted using the checklist from https://iaoc.ietf.org/meetings-committee/venue-selection.html; The site visit team prepares a site report and discusses it with the Meetings Committee.
Phase 4:
Qualified Venues Evaluated for Contract
2.75 - 3 years out, initiate contract negotiations.
  1. The Meetings Committee reviews the venue options based on venue selection criteria and recommends a venue to the IAOC. Only options that meet all Mandatory labeled criteria may be recommended.
  2. IAOC selects a venue for contracting as well as a back-up contracting venue, if available.
  3. Secretariat negotiates with selected venue. IAD reviews contract and requests IAOC and ISOC approval of contract and authority for Secretariat to execute contract on ISOC's behalf.
  4. Contracts are executed.
Phase 5:
Evaluation and Contingency Planning
3 Months Prior to the Meeting, the meeting site is checked for continued availability and conformance to expectations.
  1. Secretariat reviews current status of the contracted meeting location to confirm there is no change in the location status and to identify possible new barriers to holding a successful meeting in the contracted city and provides findings to the IAOC.
  2. IAOC considers the information provided and evaluates the risk - if significant risk is identified, the Contingency Planning Flow Chart (https://iaoc.ietf.org/meetings-committee/venue-selection.html) is followed, if current risk is not significant, the situation is monitored through the meeting to ensure there is no significant change.

6. Text carried forward

This document is being reorganized along an outline proposed by Alissa Cooper. In preceding sections, her comment is made explicit. That is intended to be removed when the reorganization is complete. Text in this section is left over and will potentially be moved to preceding sections.

6.1. Venue Selection Process

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

6.1.1. Venue Selection Principles

heading paragraph moved to Section 2.

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?
Moved to Section 2.
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.
Moved to Section 2.
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, including overflow hotels. We also need open network access available at high enough data rates to support our work, including the support of remote participation.

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.

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, or which are multiple travel segments from major airports, are therefore exclusionary, and violate our value of "Inclusiveness". Within reason, budget should not be a barrier to accommodation.
Political considerations:
moved to Section 3 and reworded per Alissa's suggested text.

6.1.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:

There is an explicit intent to rotate meeting locations equally among several places 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, meeting in Europe, North America, and Asia, with a possibility of occasionally meeting outside those regions. This policy, known as the 1-1-1* model, is set by the IESG, https://iaoc.ietf.org/minutes/2010-11-10-iaoc-minutes.txt, and is further discussed in [I-D.krishnan-ietf-meeting-policy]. The reason for the multi-year timeframe is 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 rotation of regions, 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 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, for any meeting.

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.

6.1.3. Venue Selection Criteria

Heading text moved to Section 4. Venue City Considerations Basic Venue Criteria

6.1.4. Venue Selection Phases

6.1.5. 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.

6.2. 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.

7. IANA Considerations

This memo asks the IANA for no new parameters.

8. Security Considerations

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

9. Privacy Considerations

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

10. Acknowledgements

Additional commentary came from Jari Arkko, Scott Bradner, and Alissa Cooper. It was discussed on mtgvenue@ietf.org.

11. References

11.1. Normative References

[I-D.krishnan-ietf-meeting-policy] Krishnan, S., "High level guidance for the meeting policy of the IETF", Internet-Draft draft-krishnan-ietf-meeting-policy-01, July 2016.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996.
[RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF Administrative Support Activity (IASA)", BCP 101, RFC 4071, DOI 10.17487/RFC4071, April 2005.
[RFC4371] Carpenter, B. and L. Lynch, "BCP 101 Update for IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, January 2006.
[RFC7691] Bradner, S., "Updating the Term Dates of IETF Administrative Oversight Committee (IAOC) Members", BCP 101, RFC 7691, DOI 10.17487/RFC7691, November 2015.

11.2. Informative References

[I-D.barnes-healthy-food] Barnes, M., "Healthy Food and Special Dietary Requirements for IETF meetings", Internet-Draft draft-barnes-healthy-food-07, July 2013.

Appendix A. Change Log

Initial version
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.
Reorganize and capture IAOC Meetings Committee discussions.
Final from Design Team.
First update incorporating mtgvenue@ietf.org comments
Updated in accordance with editing by Laura Nugent, Dave Crocker, Lou Berger, Fred Baker, and others.
posting as working group draft
August 2, 2016
Reorganized per Alissa Cooper outline
Work in progress. In addition, contributors were re-organized to be authors.

Authors' Addresses

Ray Pelletier Internet Society EMail: rpelletier@isoc.org
Laura Nugent Association Management Solutions EMail: lnugent@amsl.com
Dave Crocker Brandenburg InternetWorking EMail: dcrocker@bbiw.net
Lou Berger LabN Consulting, L.L.C. EMail: lberger@labn.net
Ole Jacobsen The Internet Protocol Journal EMail: olejacobsen@me.com
Jim Martin INOC EMail: jim@inoc.com
Fred Baker EMail: fred@cisco.com