MTGVENUE | A. Sullivan |
Internet-Draft | Dyn, Inc. |
Intended status: Informational | A. Cooper |
Expires: January 9, 2017 | Cisco Systems |
July 8, 2016 |
Prioritized Objectives for Making Decisions in Selecting a Meeting Venue
draft-sullivan-mtgvenue-decisions-00
Selecting a site for an IETF meeting necessarily involves balancing various factors about the site and the goals of the IETF meeting. Those who are faced with choosing a site need guidance on how to prioritize objectives in making such decisions, since no algorithm is possible. This memo provides a set of such objectives in order of importance.
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 January 9, 2017.
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.
As [I-D.baker-mtgvenue-iaoc-venue-selection-process] makes clear, there are myriad factors to balance in choosing an IETF meeting venue. While that document outlines some important principles at work in considering the factors, it offers only guidance about how to decide among competing considerations.
This memo offers a list of objectives, in descending order of importance, in an attempt to guide decision-makers. These are objectives, not rules, and are intended to guide decisions in a way that encourages the productivity and comity of the IETF community.
It is expected that the list will be initially controversial. It is offered as a proposal in order to determine whether the community has collective preferences. Expression of such collective preferences can help those who are making venue selections be confident that they understand what the community is likely to want. If it becomes clear that the community cannot really come to a conclusion about how to order these sorts of objectives, that too is information for those undertaking venue selection.
The purpose of an IETF meeting is above all to support the standards-development work that is undertaken by IETF participants. Therefore, when selecting venues, maximal inclusiveness is paramount, and must trump other considerations. Maximizing inclusiveness carries a number of implications:
The IETF does not meet to make decisions: those are made on mailing lists. The reason for the in-person meetings is twofold. First, it is to address issues that can be better solved in person because of the way in-person communication can often dissolve misunderstanding more quickly than written communication can. Second, it is to encourage the development of social bonds and informal understanding so that later written communication can be easier.
Accordingly, sites to be selected must provide the necessary support for informal interaction and random group work. In practice, this means that:
Unfettered high-bandwidth access to the entire Internet, from all the hotels associated with the meeting, is a necessary criterion for a successful meeting. It should be treated as an extremely negative consideration were mobile networks outside the hotels to be subject to significant filtering or interference.
In keeping with the objective of inclusiveness noted in Section 2.1, an acceptable venue will be in general safe for individuals. Health risks and issues of safety from violence or personal crime are to be regarded as worse than issues of crimes against property.
Many IETF participants fund their own way to meetings, and many others have limited employer support for travel. With the understanding that the facilities necessary to achieve the goals of meeting in person at all cannot be sacrificed, the cost to meeting attendees for accommodation should be minimized.
While it can be convenient to hold a meeting in a venue under "one roof" (e.g. a conference centre with an attached hotel, or a large hotel with many meeting rooms), it is a secondary goal and may be sacrificed whenever it is in tension with goals in Section 2.
Because the IETF garners a significant portion of its revenue from IETF meeting fees, there is considerable incentive for decision-makers to prefer a venue that will attract more attendees. It is important to resist this temptation: a larger meeting in which key contributors could not make it is not a better meeting; neither is one with a lot of "tourists".
The IETF moves its meetings around to ensure that those who can participate in person at the meetings share the difficulty and cost of travel. The point of such moving is emphatically not to find new or interesting places to visit, or to undertake outreach to new communities who would not otherwise participate in the IETF.
[I-D.baker-mtgvenue-iaoc-venue-selection-process] | Baker, F., "IAOC Plenary Meeting Venue Selection Process", Internet-Draft draft-baker-mtgvenue-iaoc-venue-selection-process-03, July 2016. |
This Internet-Draft is offered for discussion in the IETF MTGVENUE working group, and on its mailing list <mtgvenue@ietf.org>