<?xml version="1.0" encoding="UTF-8"?>


<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>


<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

  <!ENTITY rfc2119 PUBLIC '' 
  'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'> 


]>

  <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
  <?rfc toc="yes" ?>
  <?rfc symrefs="yes" ?>
  <?rfc sortrefs="yes"?>
  <?rfc iprnotified="no" ?>
  <?rfc strict="yes" ?>
  <?rfc compact="yes" ?>
  <?rfc subcompact="no"?>
  <?rfc comments="yes"?>
  <?rfc inline="yes"?>


<rfc category="info" ipr="trust200902"
     docName="draft-sullivan-mtgvenue-decisions-00">

  <front>

    <title abbrev="Meeting Selection Decision-making Principles">
      Prioritized Objectives for Making Decisions in Selecting a Meeting Venue
    </title>
    
    <author initials="A." surname="Sullivan" fullname="Andrew Sullivan">
      <organization>Dyn, Inc.</organization>
      <address>
        <postal>
          <street>150 Dow St</street>
          <city>Manchester</city>
          <region>NH</region>
          <code>03101</code>
          <country>U.S.A.</country>
        </postal>
        <email>asullivan@dyn.com</email>
      </address>
    </author>
    
        <author initials="A." surname="Cooper" fullname="Alissa Cooper">
        <organization>Cisco Systems</organization>
      <address>
        <postal>
          <street>707 Tasman Drive</street>
          <city>Milpitas</city>
          <region>CA</region>
          <code>95305</code>
          <country>U.S.A.</country>
        </postal>
        <email>alcoop@cisco.com</email>
      </address>
    </author>

    <date />

    <workgroup>MTGVENUE</workgroup>

    <abstract>
      <t>
        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.
      </t>
    </abstract>

  </front>

  <middle>
    <section title="Introduction" anchor="sec_intro">
      <t>As <xref
      target="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.</t>

      <t>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.</t>

      <t>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.</t>
    </section>

    <section title="Objectives" anchor="sec_principles">
      <section title="Inclusiveness"
               anchor="sec_max_include">
        <t>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:
        
        <list style="hanging">
            <t hangText="Legal exclusions:">Formal legal exclusions or
            differential treatment by authorities in a candidate
            destination, on the basis of age, gender or gender
            identity, sexuality, marital status, political views,
            racial background, nationality, countries previously
            visited, or any other category of irrelevant
            discrimination, in general ought to disqualify a site from
            candidacy.  Informal but widely-experienced (or
            widely-announced) persistent discrimination of the same
            sort, particularly at the point of immigration, should
            also be treated as an extremely negative
            consideration, but is not the same as formal legal
            sanction against an identifiable group.</t>
        
            <t hangText="Accessibility:">IETF contributors have
            different physical abilities.  An acceptable venue must
            accommodate the ranges of physical ability found across the
            community.  This means that attendance at every session
            and accommodation in meeting hotels must be a practical
            possibility for those using a variety of assistive
            devices.</t>
        
            <t hangText="Distribution of travel difficulty and cost:">The composition of IETF contributors changes over time, and the
            difficulty and cost of travel ought to be shared
            throughout the community.  This includes difficulties
            relating to long journeys, different customs in modes of
            travel, and cultural adjustment to local norms of visitor
            behaviour.</t>

            <t hangText="Predictions are hard, especially about the future:">Legal, political, and economic realities
            sometimes change after an agreement is signed, and nobody
            expects infallible predictions.  The goal is still maximal
            inclusiveness, even if that goal can be only imperfectly
            realised.</t>
        </list>
        </t>
      </section>

      <section title="Co-location of attendees"
               anchor="sec_meeting_not_list">
        <t>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.</t>
        <t>Accordingly, sites to be selected must provide the
        necessary support for informal interaction and random group
        work.  In practice, this means that: 
        
        <list style="symbols">
        <t>Venues need to be in urban areas in order to accommodate a wide range of
        opportunities for these kinds of interaction.</t>
        <t>Meeting hotels need to be in close proximity to each other and the venue.</t>
        </list>
        </t>
      </section>
      
      <section title="Network access"
               anchor="sec_net_critical">
        <t>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.</t>
      </section>

      <section title="Safety and security"
               anchor="sec_personal_security">
        <t>In keeping with the objective of inclusiveness noted in
        <xref target="sec_max_include" />, 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.</t>
      </section>

      <section title="Affordability" anchor="sec_cost">
        <t>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.</t>
      </section>
    </section>
    
    <section title="Non-Objectives" anchor="sec_non_objectives">

     <section title="One roof" anchor="sec_one_roof">
        <t>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 <xref target="sec_principles" />.</t>
      </section>

      <section title="Maximal attendance" anchor="sec_max_attendance">
        <t>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".</t>
      </section>
      
      <section title="Geographic outreach" anchor="sec_global_org">
        <t>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.</t>
      </section>
     
    </section>
     
  </middle>

  <back>
    <references title="Informative References">
      <?rfc include="reference.I-D.baker-mtgvenue-iaoc-venue-selection-process.xml"?>
    </references>

    <section title="Discussion Venue">
      <t>This Internet-Draft is offered for discussion in the IETF
      MTGVENUE working group, and on its mailing list
      &lt;mtgvenue@ietf.org&gt;</t>
    </section>

    <section title="Change History">
      <t><list style="hanging">
        <t hangText="00:">
          <list style="symbols">
            <t>Initial version</t>
          </list>
        </t></list></t>
    </section>
  </back>
</rfc>
