<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="bcp" consensus="true" docName="draft-ietf-shmoo-cancel-meeting-06" indexInclude="true" ipr="trust200902" number="9137" prepTime="2021-10-11T23:21:40" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-shmoo-cancel-meeting-06" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9137" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="Cancellation of IETF Meetings">Considerations for Cancellation of IETF Meetings</title>
    <seriesInfo name="RFC" value="9137" stream="IETF"/>
    <seriesInfo name="BCP" value="226" stream="IETF"/>
    <author initials="M." surname="Duke" fullname="Martin Duke">
      <organization showOnFrontPage="true">F5 Networks, Inc.</organization>
      <address>
        <email>martin.h.duke@gmail.com</email>
      </address>
    </author>
    <date month="10" year="2021"/>
    <area>General</area>
    <workgroup>shmoo</workgroup>
    <keyword>virtualize</keyword>
    <keyword>postpone</keyword>
    <keyword>move</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">The IETF ordinarily holds three in-person meetings per year to discuss issues
      and advance the Internet. However, various events can make a planned
      in-person meeting infeasible. This document provides criteria to aid the IETF
      Administration LLC (IETF LLC), the Internet Engineering Steering
      Group (IESG), and the Chair of the 
      Internet Research Task Force (IRTF) in deciding to relocate, virtualize, postpone, or
      cancel an in-person IETF meeting.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This memo documents an Internet Best Current Practice.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further information
            on BCPs is available in Section 2 of RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9137" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2021 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) 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.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions">Conventions</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-decision-criteria-and-roles">Decision Criteria and Roles</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2">
              <li pn="section-toc.1-1.3.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-ietf-llc">IETF LLC</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.2">
                <t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-the-iesg-and-the-chair-of-t">The IESG and the Chair of the IRTF</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-remedies">Remedies</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-relocation">Relocation</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.2">
                <t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-virtualization">Virtualization</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.3">
                <t indent="0" pn="section-toc.1-1.4.2.3.1"><xref derivedContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-postponement">Postponement</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.4">
                <t indent="0" pn="section-toc.1-1.4.2.4.1"><xref derivedContent="4.4" format="counter" sectionFormat="of" target="section-4.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-cancellation">Cancellation</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-refunds">Refunds</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-address">Author's Address</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">Among the highlights of the IETF calendar are in-person general meetings, which
      happen three times a year at various locations around the world.</t>
      <t indent="0" pn="section-1-2">Various major events may affect the suitability of a scheduled in-person IETF
      meeting, though this may not be immediately obvious for some events. Examples of such events include the following:
      </t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1-3">
        <li pn="section-1-3.1">A meeting venue itself may unexpectedly close or otherwise be unable to meet
	IETF meeting requirements due to a health issue, legal violation, or other
	localized problem.</li>
        <li pn="section-1-3.2">A natural disaster could degrade the travel and meeting infrastructure in a
	planned location and make it unethical to further burden that infrastructure
	with a meeting.</li>
        <li pn="section-1-3.3">War, civil unrest, or a public health crisis could make a meeting unsafe and/or
	result in widespread national or corporate travel bans.</li>
        <li pn="section-1-3.4">An economic crisis could sharply reduce resources available for travel,
	resulting in lower expected attendance.</li>
        <li pn="section-1-3.5">Changes in visa policies or other unexpected governmental restrictions might
	make the venue inaccessible to numerous attendees.</li>
      </ul>
      <t indent="0" pn="section-1-4">This document provides criteria to aid the IETF Administration
      LLC (IETF LLC), the Internet Engineering Steering Group (IESG), and the Chair of the
      Internet Research Task Force (IRTF) in deciding to relocate, virtualize, postpone, or
      cancel an in-person IETF meeting.</t>
    </section>
    <section anchor="conventions" numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-conventions">Conventions</name>
      <t indent="0" pn="section-2-1">The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
      "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
      "<bcp14>SHOULD</bcp14>",
      "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this
      document are to be interpreted as described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/>
      when, and only when, they appear in all capitals, as shown here.</t>
      <t indent="0" pn="section-2-2">In this document, the term "venue" refers to both the facility that houses the
      sessions and the official meeting hotel(s), as defined in <xref target="RFC8718" format="default" sectionFormat="of" derivedContent="RFC8718"/>.</t>
    </section>
    <section anchor="decision-criteria-and-roles" numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-decision-criteria-and-roles">Decision Criteria and Roles</name>
      <t indent="0" pn="section-3-1">The IETF LLC assesses whether an in-person meeting is logistically and financially
      viable in light of events and assembles information about various travel
      restrictions that might impact attendance. The
      IESG and the Chair of the IRTF assess if the
      projected attendance is sufficient for a viable in-person meeting.</t>
      <section anchor="ietf-llc" numbered="true" toc="include" removeInRFC="false" pn="section-3.1">
        <name slugifiedName="name-ietf-llc">IETF LLC</name>
        <t indent="0" pn="section-3.1-1">The IETF LLC is responsible for assessing the suitability of a venue for an IETF
	meeting and is responsible for any reassessment in response to a major event
	that leaves the prior conclusion in doubt. If such an event occurs more than
	fourteen weeks before the start of the scheduled meeting, it is deemed a
	non-emergency situation. Later events, up to and including the week of a meeting
	itself, are deemed emergency situations.</t>
        <t indent="0" pn="section-3.1-2">In non-emergency situations, if the IETF LLC determines the scheduled meeting
	clearly
	cannot proceed (e.g., the venue has permanently closed), then it <bcp14>MUST</bcp14>
	share the reason(s) with the community and <bcp14>MUST</bcp14> consult on its
	proposed remedy. In less clear cases, the IETF LLC <bcp14>SHOULD</bcp14> conduct a
	formal reassessment process that includes:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.1-3">
          <li pn="section-3.1-3.1">Consulting with the community on the timetable of the decision process.</li>
          <li pn="section-3.1-3.2">Consulting with the community on criteria to assess the impact of new
	  developments.</li>
          <li pn="section-3.1-3.3">Publishing an assessment report and recommended remedy.</li>
          <li pn="section-3.1-3.4">Seeking approval of the IESG and the Chair of the IRTF for the
	  recommendation.</li>
        </ul>
        <t indent="0" pn="section-3.1-4">In emergency situations, which lack the time for a consultation process, this
	document provides criteria that have IETF consensus and that the IETF LLC
	<bcp14>MUST</bcp14> apply in its assessment.</t>
        <t indent="0" pn="section-3.1-5">The IETF LLC will collect information about the likely impact to in-person
	attendance of national travel advisories, national and corporate travel bans,
	availability of transportation, quarantine requirements, etc., and report the
	results to the IESG and the Chair of the IRTF.</t>
        <t indent="0" pn="section-3.1-6">These criteria, some of which are derived from <xref target="RFC8718" sectionFormat="of" section="3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8718#section-3" derivedContent="RFC8718"/>, apply
	to venues that are re-evaluated due to an emergency:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.1-7">
          <li pn="section-3.1-7.1">Local safety guidelines allow the venue and hotels to host a meeting with the
	  expected number of participants and staff.</li>
          <li pn="section-3.1-7.2">It is possible to provision Internet access to the venue that allows those
	  attending in person to utilize the Internet for all their IETF, business, and
	  day-to-day needs; in addition, there must be sufficient bandwidth and access for
	  remote attendees.  Provisions include, but are not limited to, native and
	  unmodified IPv4 and IPv6 connectivity and global reachability; there may be no
	  additional limitation that would materially impact their Internet use.  To
	  ensure availability, it <bcp14>MUST</bcp14> be possible to provision redundant
	  paths to the Internet.</li>
          <li pn="section-3.1-7.3">A reasonable number of food and drink establishments are open and available
	  within walking distance to provide for the expected number of participants and
	  staff.</li>
          <li pn="section-3.1-7.4">Local health and public safety infrastructure expects to have adequate
	  capacity to support an influx of visitors during the meeting week.</li>
        </ul>
        <t indent="0" pn="section-3.1-8">Finally, the IETF LLC <bcp14>MUST</bcp14> assess the impact on its own operations,
	including:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.1-9">
          <li pn="section-3.1-9.1">The number of critical support staff, contractors, and volunteers who can be
	  at the venue.</li>
          <li pn="section-3.1-9.2">The financial impact of continuing a meeting or implementing any of the
	  possible remedies.</li>
        </ul>
        <t indent="0" pn="section-3.1-10">The IETF LLC <bcp14>SHOULD</bcp14> cancel an in-person meeting and explore
	potential
	remedies if it judges a meeting to be logistically impossible or inconsistent with its
	fiduciary responsibilities.</t>
        <t indent="0" pn="section-3.1-11">In the event of considerations this document does not foresee, the IETF LLC should
	protect the health and safety of attendees and staff, as well as the fiscal
	health of the organization, with approval from the IESG and the Chair of the IRTF. The
	IESG should pursue a later update of this document.</t>
      </section>
      <section anchor="iesg-and-irtf-chair" numbered="true" toc="include" removeInRFC="false" pn="section-3.2">
        <name slugifiedName="name-the-iesg-and-the-chair-of-t">The IESG and the Chair of the IRTF</name>
        <t indent="0" pn="section-3.2-1">If the IETF LLC assesses there are no fundamental logistical or financial obstacles
	to holding a meeting in an emergency situation, the IESG and the Chair of the IRTF
	assess
	if projected attendance is high enough to achieve the benefit of an in-person
	meeting. The IESG and the Chair of the IRTF <bcp14>SHOULD</bcp14> cancel the in-person
	meeting if that benefit is insufficient.</t>
        <t indent="0" pn="section-3.2-2">The IESG and the Chair of the IRTF are discouraged from relying on a simple head
	count of
	expected meeting attendance. Even dramatically smaller meetings with large
	remote participation may be successful.  In addition to the IETF LLC's estimate, the
	IESG and the Chair of the IRTF might consider:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.2-3">
          <li pn="section-3.2-3.1">Are many working groups and research groups largely unaffected by the
	  restrictions, so that they can operate effectively?</li>
          <li pn="section-3.2-3.2">Is there a critical mass of key personnel at most working group meetings to
	  leverage the advantages of in-person meetings, even if many participants are
	  remote?</li>
        </ul>
      </section>
    </section>
    <section anchor="remedies" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-remedies">Remedies</name>
      <t indent="0" pn="section-4-1">If a meeting cannot be held at the scheduled time and place, the IETF LLC, IESG, and
      Chair of the IRTF have several options. The remedies in this section should be
      considered in light of four principles (presented in no particular order):</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4-2">
        <li pn="section-4-2.1">Hold the scheduled sessions of a meeting in some format.</li>
        <li pn="section-4-2.2">Provide benefits of in-person interactions when possible.</li>
        <li pn="section-4-2.3">Avoid exorbitant additional travel expenses due to last-minute flight changes,
	etc.</li>
        <li pn="section-4-2.4">Ensure sufficient time and resources to adequately prepare an alternative.</li>
      </ul>
      <t indent="0" pn="section-4-3">The following remedies are listed in approximate declining order of preference.</t>
      <section anchor="relocation" numbered="true" toc="include" removeInRFC="false" pn="section-4.1">
        <name slugifiedName="name-relocation">Relocation</name>
        <t indent="0" pn="section-4.1-1">For attendees, the least disruptive response is to retain the meeting week but
	move it to a more-accessible venue. To the maximum extent possible, this will be
	geographically close to the original venue. In particular, the IETF LLC
	<bcp14>SHOULD</bcp14> meet the criteria in <xref target="RFC8718" format="default" sectionFormat="of" derivedContent="RFC8718"/>
	and <xref target="RFC8719" format="default" sectionFormat="of" derivedContent="RFC8719"/>.</t>
        <t indent="0" pn="section-4.1-2">Relocation that requires new air travel arrangements for attendees <bcp14>SHOULD NOT</bcp14> occur less than one month prior to the start of the meeting.</t>
      </section>
      <section anchor="virtualization" numbered="true" toc="include" removeInRFC="false" pn="section-4.2">
        <name slugifiedName="name-virtualization">Virtualization</name>
        <t indent="0" pn="section-4.2-1">The second option, and one that has fewer issues with venue availability, is to
	make a meeting fully online. This requires different IETF processes and
	logistical operations that are outside the scope of this document.</t>
      </section>
      <section anchor="postponement" numbered="true" toc="include" removeInRFC="false" pn="section-4.3">
        <name slugifiedName="name-postponement">Postponement</name>
        <t indent="0" pn="section-4.3-1">Although it is more disruptive to the schedules of participants, the next best
	option is to delay a meeting until a specific date, at the same venue, at
	which conditions are expected to improve. The new end date of a meeting must
	be at least 30 days before the beginning of the following IETF meeting, and a
	meeting <bcp14>MUST</bcp14> begin no earlier than 30 days after the postponement
	announcement.</t>
        <t indent="0" pn="section-4.3-2">Due to scheduling constraints at the venue, this will usually not be feasible.
	However, it is more likely to allow attendees to recover at least some of their
	travel expenses than other options.</t>
        <t indent="0" pn="section-4.3-3">Note that it is possible to both postpone and relocate a meeting, though this
	has the disadvantages of both.</t>
      </section>
      <section anchor="cancellation" numbered="true" toc="include" removeInRFC="false" pn="section-4.4">
        <name slugifiedName="name-cancellation">Cancellation</name>
        <t indent="0" pn="section-4.4-1">The IETF LLC, IESG, and Chair of the IRTF may cancel a meeting entirely in the
	event that
	worldwide conditions make it difficult for attendees to even attend online. Not
	holding a meeting at all can have wide implications, such as effects on the
	nomination process and seating of new officers.</t>
        <t indent="0" pn="section-4.4-2">Cancellation is likely the only practical alternative when emergencies occur
	immediately before or during a meeting, so that there is no opportunity to
	make other arrangements.</t>
      </section>
    </section>
    <section anchor="refunds" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-refunds">Refunds</name>
      <t indent="0" pn="section-5-1">The IETF <bcp14>SHOULD NOT</bcp14> reimburse registered attendees for unrecoverable
      travel expenses (airfare, hotel deposits, etc.).</t>
      <t indent="0" pn="section-5-2">However, there are several cases where full or partial refund of registration
      fees are appropriate:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5-3">
        <li pn="section-5-3.1">Cancellation <bcp14>SHOULD</bcp14> result in a full refund to all participants.
	It <bcp14>MAY</bcp14> be prorated if some portion of the sessions completed without
	incident.</li>
        <li pn="section-5-3.2">Upon postponement, the IETF LLC <bcp14>SHOULD</bcp14> offer refunds to registered
	attendees who claim they cannot attend at the newly scheduled time. Attendees can opt
	out of receiving a refund.</li>
        <li pn="section-5-3.3">When a meeting is virtualized, the IETF LLC <bcp14>MUST</bcp14> offer to refund
	registered attendees the difference between their paid registration fee and the
	equivalent fee for an online meeting. The IETF LLC <bcp14>SHOULD</bcp14> offer
	refunds to
	registered attendees who do not wish to attend an online meeting.</li>
        <li pn="section-5-3.4">The IETF LLC <bcp14>SHOULD</bcp14> offer refunds to attendees whose government
	forbids, or has issued a safety advisory against, visits to the host venue, even if
	the in-person meeting will continue. It <bcp14>SHOULD NOT</bcp14> refund
	cancellations due to employer policy or personal risk assessments.</li>
      </ul>
      <t indent="0" pn="section-5-4">These provisions intend to maintain trust between the IETF and its participants.
      However, under extraordinary threats to the solvency of the organization, the
      IETF LLC may suspend them.</t>
    </section>
    <section anchor="security-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-6-1">This document introduces no new concerns for the security of Internet protocols.</t>
    </section>
    <section anchor="iana-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-7">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-7-1">This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references pn="section-8">
      <name slugifiedName="name-normative-references">Normative References</name>
      <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author initials="S." surname="Bradner" fullname="S. Bradner">
            <organization showOnFrontPage="true"/>
          </author>
          <date year="1997" month="March"/>
          <abstract>
            <t indent="0">In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author initials="B." surname="Leiba" fullname="B. Leiba">
            <organization showOnFrontPage="true"/>
          </author>
          <date year="2017" month="May"/>
          <abstract>
            <t indent="0">RFC 2119 specifies common key words that may be used in protocol  specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the  defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
      <reference anchor="RFC8718" target="https://www.rfc-editor.org/info/rfc8718" quoteTitle="true" derivedAnchor="RFC8718">
        <front>
          <title>IETF Plenary Meeting Venue Selection Process</title>
          <author initials="E." surname="Lear" fullname="E. Lear" role="editor">
            <organization showOnFrontPage="true"/>
          </author>
          <date year="2020" month="February"/>
          <abstract>
            <t indent="0">The IETF Administration Support Activity (IASA) is responsible for arranging the selection and operation of the IETF plenary meeting venue. This memo specifies IETF community requirements for meeting venues, including hotels and meeting space.  It also directs the IASA to make available additional process documents that describe the current meeting selection process.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="226"/>
        <seriesInfo name="RFC" value="8718"/>
        <seriesInfo name="DOI" value="10.17487/RFC8718"/>
      </reference>
      <reference anchor="RFC8719" target="https://www.rfc-editor.org/info/rfc8719" quoteTitle="true" derivedAnchor="RFC8719">
        <front>
          <title>High-Level Guidance for the Meeting Policy of the IETF</title>
          <author initials="S." surname="Krishnan" fullname="S. Krishnan">
            <organization showOnFrontPage="true"/>
          </author>
          <date year="2020" month="February"/>
          <abstract>
            <t indent="0">This document describes a meeting location policy for the IETF and the various stakeholders required to realize this policy.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="226"/>
        <seriesInfo name="RFC" value="8719"/>
        <seriesInfo name="DOI" value="10.17487/RFC8719"/>
      </reference>
    </references>
    <section anchor="acknowledgments" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1"><contact fullname="Jay Daley"/> provided extensive input to make this document more
      usable by the IETF LLC. Many members of the IESG and the
      SHMOO Working Group also provided useful comments.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-address">Author's Address</name>
      <author initials="M." surname="Duke" fullname="Martin Duke">
        <organization showOnFrontPage="true">F5 Networks, Inc.</organization>
        <address>
          <email>martin.h.duke@gmail.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
