<?xml version="1.0" encoding="US-ASCII"?> version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

<!ENTITY RFC4071 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4071.xml">
<!ENTITY I-D.ietf-mtgvenue-iaoc-venue-selection-process SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-mtgvenue-iaoc-venue-selection-process.xml">
]>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?> "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" number="8719" category="bcp"
     seriesNo="226" docName="draft-ietf-mtgvenue-meeting-policy-07" ipr="trust200902">
     ipr="trust200902" submissionType="IETF" consensus="true" xml:lang="en"
     obsoletes="" updates="" tocInclude="true" tocDepth="4" symRefs="true"
     sortRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 2.37.1 -->
  <front>
    <title abbrev="IETF Meeting Policy">High level guidance Policy">High-Level Guidance for the meeting policy Meeting
    Policy of the IETF</title>
    <seriesInfo name="RFC" value="8719"/>
    <seriesInfo name="BCP" value="226"/>
    <author fullname="Suresh Krishnan" initials="S." surname="Krishnan">
      <organization>Kaloom</organization>
      <address>
        <postal>
          <street></street>

          <city></city>

          <region></region>

          <code></code>

          <country></country>
          <street/>
          <city/>
          <region/>
          <code/>
          <country/>
        </postal>
        <email>suresh@kaloom.com</email>
      </address>
    </author>

    <date/>
    <date month="January" year="2020"/>
    <area>General</area>

    <workgroup>Internet Engineering Task Force</workgroup>
    <workgroup>Meeting Venue Working Group</workgroup>
    <keyword>geographic distribution location</keyword>
    <keyword>IASA</keyword>
    <abstract>
      <t>This document describes a meeting location policy for the IETF and
      the various stakeholders for realizing such a required to realize this policy.</t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>
The work of the IETF is primarily conducted on the working group (WG)
mailing lists, while face-to-face WG meetings mainly provide a high
bandwidth high-bandwidth
mechanism for working out unresolved issues. The IETF
currently strives to have a 1-1-1 meeting policy
<xref target="IETFMEET"/>
where the goal is to distribute the meetings equally between North America,
Europe, and Asia. Asia (see "Meeting Location Distribution" (slides 14 and 15) of
<xref target="IETFMEET" format="default"/> for details). These are the
locations from which most of the IETF participants have come from in the recent past.
This meeting rotation is mainly aimed at distributing the travel effort for
the existing IETF participants who physically attend meetings and for
distributing the timezone difficulty for those who participate remotely.
This policy has neither been neither defined precisely nor documented in an
IETF consensus document until now. This document BCP RFC is meant to serve as a
consensus-backed statement of this policy published as a BCP. policy.
      </t>
    </section>
    <section title="The numbered="true" toc="default">
      <name>The 1-1-1-* meeting policy"> Meeting Policy</name>
      <t>Given that the majority of the current meeting participants come from
   North America, Europe, and Asia <xref target="CONT-DIST"/>, target="CONT-DIST" format="default"/>, the
   IETF policy is that our the meetings should primarily be held in those
   regions. i.e., That is, the meeting policy (let's call this the "1-1-1"
   policy) is that meetings should rotate between North America,
   Europe, and Asia. Please note Note that the boundaries between those
   regions has have been purposefully left undefined. It
   is important to note that such rotation and any effects to
   distributing travel pain should be considered from a long-term
   perspective. While a potential cycle in an IETF year may be a
   meeting in North America in March, a meeting in Europe in July, and
   a meeting in Asia on November, the 1-1-1 policy does not imply
   such a cycle, as long as the distribution to these regions over
   multiple years is roughly equal. There are many reasons why meetings
   might be distributed differently in a given year. Meeting locations in
   subsequent years should seek to re-balance rebalance the distribution distribution, if
   possible.</t>
      <t>While this meeting rotation caters to the current set of IETF
   participants, it is important to recognize that due to the dynamic and
   evolving nature of participation, there may be significant changes
   to the regions that provide a major share of participants in the
   future. The Therefore, the 1-1-1-* meeting policy is a slightly modified version
   of the aforementioned 1-1-1 meeting policy that allows for
   additional flexibility in the form of an exploratory meeting denoted as
   a "*". This exploratory meeting (denoted with
   an "*"). Exploratory meetings can be used to experiment with
   exceptional meetings without extensively impacting the regular
   meetings. e.g. For example, these exploratory meetings can include meetings in
   other geographical regions, virtual meetings meetings, and additional
   meetings past beyond the three regular meetings in a calendar year.
      </t>
      <t>
  The timing and frequency of future exploratory meetings will be based
  on IETF consensus as determined by the IETF chair.
<!-- [rfced] Note that we have updated "in consultation with the Internet
Administrative Support Activity (IASA) [RFC4071]" to be "in consultation with
the IETF Administration LLC (IETF LLC)" and we have added a citation to
RFC-to-be 8711.  Perhaps the text should refer to the "IETF LLC Board"?

Original:
   Once a meeting
   proposal is initiated, the IESG will make a decision in consultation
   with the Internet Administrative Support Activity (IASA) to ensure
   that the proposal can be realistically implemented.

Current:
   Once a meeting
   proposal is initiated, the IESG will make a decision in consultation
   with the IETF Administration LLC (IETF LLC) [RFC8711] to ensure
   that the proposal can be realistically implemented.

In general, we have replaced "IASA" with "IETF LLC".  Please review and let us
know if any updates are needed.
-->
Once a meeting
  proposal is initiated, the IESG will make a decision in consultation with
  the IETF Administration LLC (IETF LLC) <xref target="RFC8711"
  format="default"/> to ensure that the proposal can be realistically
  implemented. The final decision will be communicated back to the
   community to ensure that there is adequate opportunity to comment.
      </t>
   <t>NOTE:

<!-- [rfced] Note that we have deleted "current" because it is confusing
here.  We believe "1-1-1" (without an asterisk) is clear.  Please let us know
if you have any concerns.

   NOTE: There have not been a large number of meetings that would qualify as
   exploratory meetings under the current 1-1-1-* 1-1-1 policy (with
IETF95 IETF 95 in Buenos
   Aires and IETF47 IETF 47 in Adelaide being the exceptional instances). IETF27
-->
      <aside><t>NOTE: There have not been a large number of meetings that would
qualify as exploratory meetings under the 1-1-1 policy (with
IETF 95 in Buenos Aires and IETF 47 in Adelaide being the exceptional
instances). IETF 27 (Amsterdam) and IETF54(Yokohama) IETF 54 (Yokohama) were earlier
examples of exploratory meetings that pioneered Europe and Asia as
regular IETF destinations.</t> destinations.</t></aside>
    </section>
    <section title="Implementation numbered="true" toc="default">
      <name>Implementation of the policy">
   <t>IASA Policy</name>
      <t>The IETF Administration LLC (IETF LLC) should understand the policy
      written in this document to be the aspiration of the IETF community. Similarly, any
   exploratory meeting decisions will also be communicated to the IASA IETF LLC to
   be implemented. The actual selection of the venue would be
   performed by the IASA IETF LLC following the process described in <xref
   target="I-D.ietf-mtgvenue-iaoc-venue-selection-process"/>.
   target="RFC8718" format="default"/>.
      </t>
      <t>As mentioned in <xref
   target="I-D.ietf-mtgvenue-iaoc-venue-selection-process"/>, target="RFC8718" format="default"/>, the IASA IETF
      LLC will also be responsible
   <list style="symbols">
     <t>to assist for the following:
      </t>
      <ul spacing="normal">
        <li>assisting the community in the development of detailed meeting
     criteria that are feasible and implementable, and </t>
     <t>to provide </li>
        <li>for providing sufficient transparency in a timely manner
     concerning planned meetings so that community feedback can be
     collected and acted upon.</t>
   </list>
   </t> upon.</li>
      </ul>
      <t>Given that the geographical location of the venue has a
   significant influence on the venue selection process, it needs to
   be considered at the same level as the other Important Criteria
   specified in Section 3.2 of <xref
   target="I-D.ietf-mtgvenue-iaoc-venue-selection-process"/> target="RFC8718" sectionFormat="of" section="3.2" format="default"/> (including
   potentially trading off trading-off the geographical region to meet other
   criteria,
   criteria and notifying the community if the geographical region
   requirement cannot be met)</t> met).</t>
    </section>
    <section title="Procedure numbered="true" toc="default">
      <name>Procedure for initiating proposals Initiating Proposals for exploratory meetings"> Exploratory Meetings</name>
      <t>Someone who is interested in pursuing an exploratory venue
      proposes it on the IETF discussion list or on a future
      discussion list expressly setup set up and announced for this
      purpose. The community gets to comment on the venue and to offer
      their opinions. If the IETF chair determines that there is
      community consensus to pursue the venue further, the venue will
      be put up for discussion on the venue-selection mailing
      list.
      list &lt;<eref target="https://www.ietf.org/mailman/listinfo/venue-selection"/>&gt;.
      This would allow the interested party(ies) to refine their proposal with those tasked with evaluating it and providing
      further insightful
      based on insighful feedback regarding the logistics of the
      venue. venue
      from those tasked with evaluating it. Once the venue selection process
      takes place, the final decision will be communicated back to the
      community to ensure that there is adequate opportunity to comment.</t> comment.
</t>
    </section>
    <section title="Re-evaluation numbered="true" toc="default">
      <name>Re-evaluation and changes Changes to this policy">
      <t> Given This Policy</name>
      <t>Given the dynamic nature of participant distribution in the
      IETF, it is expected that this policy needs will need to be periodically
      evaluated and revised to ensure that the stated goals continue
      to be met. The criteria that are to be met need to be agreed upon by the
      community prior to initiating a revision of this document (e.g. (e.g., try to
      mirror draft author distribution over the preceding five years).
      </t>
    </section>

    <section title="Acknowledgments">

      <t>The author would like
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>

<!-- [rfced] Suresh previously mentioned potentially replacing the reference
to thank Jari Arkko, Alia Atlas, Fred
      Baker, Brian Carpenter, Alissa Cooper, Dave Crocker, Spencer
      Dawkins, Stephen Farrell, Tobias Gondrom, Eric Gray, Bob Hinden,
      Ole Jacobsen, Olaf Kolkman, Eliot Lear, Andrew Malis, Yoav Nir,
      Ray Pelletier, Melinda Shore, John Klensin, Charles Eckel, Russ
      Housley, Andrew Sullivan, Eric Rescorla, Richard Barnes, Cullen
      Jennings, Ted Lemon, Lou Berger, John Levine, Adam Roach, Mark
      Nottingham, Tom Petch, Randy Bush, Roni Even, Julien Meuric,
      Lloyd Wood, Alvaro Retana and Martin Vigoureux for their ideas
      and comments RFC 4071 with a reference to improve BCP 101.  Please let us know if this document. </t>

    </section>

  </middle>

  <back>

    <references title="Normative References">

      &RFC4071; is
preferred to the text pointing to RFC-to-be 8711.
-->
        <reference anchor="RFC8711"
		   target="https://rfc-editor.org/info/rfc8711">
          <front>
            <title>Structure of the IETF Administrative Support Activity,
            Version 2.0</title>
            <author initials="B." surname="Haberman">
              <organization/>
            </author>
            <author initials="J." surname="Hall">
              <organization/>
            </author>
            <author initials="J." surname="Livingood">
              <organization/>
            </author>
            <date month="January" year="2020"/>
          </front>
          <seriesInfo name="BCP" value="101"/>
          <seriesInfo name="RFC" value="8711"/>
          <seriesInfo name="DOI" value="10.17487/RFC8711"/>
        </reference>

      </references>

    <references title="Informative References">
      <references>
        <name>Informative References</name>
        <!--      &I-D.ietf-mtgvenue-iaoc-venue-selection-process; -->
        <reference anchor="RFC8718" target="https://www.rfc-editor.org/info/rfc8718">
          <front>
            <title>IETF Plenary Meeting Venue Selection Process</title>
            <seriesInfo name="DOI" value="10.17487/RFC8718"/>
            <seriesInfo name="RFC" value="8718"/>
            <seriesInfo name="BCP" value="226"/>
            <author initials="E" surname="Lear" fullname="Eliot Lear" role="editor">
              <organization/>
            </author>
            <date month="January" year="2020"/>
          </front>
        </reference>
        <reference anchor="CONT-DIST" target="https://datatracker.ietf.org/stats/meeting/continent/">
          <front>
            <title>Number of attendees per continent across meetings</title>
            <author>
              <organization>IETF</organization>
            </author>

          <date year="2016"/>
          </front>
        </reference>
        <reference anchor="IETFMEET" target="https://www.ietf.org/proceedings/79/slides/plenaryw-3.pdf">
          <front>
          <title>IETF 1-1-1 Meeting Policy</title>

          <author>
            <title>IAOC Report IETF79</title>
            <author initials="B." surname="Hinden" fullname="Bob Hinden">
              <organization>IAOC Plenary Presentation</organization>
            </author>
            <author initials="R" surname="Pelletier" fullname="R. Pelletier">
              <organization>IAOC Plenary Presentation</organization>
            </author>
            <date month="November" year="2010"/>
          </front>
        </reference>
      </references>
    </references>
    <section numbered="false" toc="default">
      <name>Acknowledgments</name>
      <t>The author would like to thank <contact fullname="Jari Arkko"/>,
      <contact fullname="Alia Atlas"/>, <contact fullname="Fred
      Baker"/>, <contact fullname="Brian Carpenter"/>, <contact fullname="Alissa
      Cooper"/>, <contact fullname="Dave Crocker"/>, <contact fullname="Spencer
      Dawkins"/>, <contact fullname="Stephen Farrell"/>, <contact fullname="Tobias
      Gondrom"/>, <contact fullname="Eric Gray"/>, <contact fullname="Bob Hinden"/>,
      <contact fullname="Ole Jacobsen"/>, <contact fullname="Olaf Kolkman"/>,
	<contact fullname="Eliot Lear"/>, <contact fullname="Andrew Malis"/>,
	  <contact fullname="Yoav Nir"/>,
      <contact fullname="Ray Pelletier"/>, <contact fullname="Melinda Shore"/>,
	<contact fullname="John Klensin"/>, <contact fullname="Charles Eckel"/>,
	  <contact fullname="Russ
      Housley"/>, <contact fullname="Andrew Sullivan"/>, <contact fullname="Eric
      Rescorla"/>, <contact fullname="Richard Barnes"/>, <contact fullname="Cullen
      Jennings"/>, <contact fullname="Ted Lemon"/>, <contact fullname="Lou Berger"/>,
      <contact fullname="John Levine"/>, <contact fullname="Adam Roach"/>, <contact fullname="Mark
      Nottingham"/>, <contact fullname="Tom Petch"/>, <contact fullname="Randy Bush"/>,
      <contact fullname="Roni Even"/>, <contact fullname="Julien Meuric"/>,
      <contact fullname="Lloyd Wood"/>, <contact fullname="Alvaro Retana"/>, and
	<contact fullname="Martin Vigoureux"/> for their ideas
      and comments to improve this document. </t>
    </section>
  </back>
</rfc>