File: rfc8718.html

package info (click to toggle)
doc-rfc 20201128-1
links: PTS, VCS
area: non-free
in suites: bullseye
size: 1,307,124 kB
file content (1860 lines) | stat: -rw-r--r-- 67,964 bytes
parent folder | download | duplicates (2)
<!DOCTYPE html>
<html lang="en" class="RFC BCP">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 8718: IETF Plenary Meeting Venue Selection Process</title>
<meta content="Eliot Lear" name="author">
<meta content="
       
      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. 
    " name="description">
<meta content="xml2rfc 2.40.0" name="generator">
<meta content="Meeting Venues" name="keyword">
<meta content="Meeting selection process" name="keyword">
<meta content="IASA" name="keyword">
<meta content="8718" name="rfc.number">
<link href="rfc8718.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

  NOTE: Changes at the bottom of this file overrides some earlier settings.

  Once the style has stabilized and has been adopted as an official RFC style,
  this can be consolidated so that style settings occur only in one place, but
  for now the contents of this file consists first of the initial CSS work as
  provided to the RFC Formatter (xml2rfc) work, followed by itemized and
  commented changes found necssary during the development of the v3
  formatters.

*/

/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */

@viewport {
  zoom: 1.0;
  width: extend-to-zoom;
}
@-ms-viewport {
  width: extend-to-zoom;
  zoom: 1.0;
}
/* general and mobile first */
html {
}
body {
  max-width: 90%;
  margin: 1.5em auto;
  color: #222;
  background-color: #fff;
  font-size: 14px;
  font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
  line-height: 1.6;
  scroll-behavior: smooth;
}
.ears {
  display: none;
}

/* headings */
#title, h1, h2, h3, h4, h5, h6 {
  margin: 1em 0 0.5em;
  font-weight: bold;
  line-height: 1.3;
}
#title {
  clear: both;
  border-bottom: 1px solid #ddd;
  margin: 0 0 0.5em 0;
  padding: 1em 0 0.5em;
}
.author {
  padding-bottom: 4px;
}
h1 {
  font-size: 26px;
  margin: 1em 0;
}
h2 {
  font-size: 22px;
  margin-top: -20px;  /* provide offset for in-page anchors */
  padding-top: 33px;
}
h3 {
  font-size: 18px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h4 {
  font-size: 16px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h5, h6 {
  font-size: 14px;
}
#n-copyright-notice {
  border-bottom: 1px solid #ddd;
  padding-bottom: 1em;
  margin-bottom: 1em;
}
/* general structure */
p {
  padding: 0;
  margin: 0 0 1em 0;
  text-align: left;
}
div, span {
  position: relative;
}
div {
  margin: 0;
}
.alignRight.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignRight.art-text pre {
  padding: 0;
}
.alignRight {
  margin: 1em 0;
}
.alignRight > *:first-child {
  border: none;
  margin: 0;
  float: right;
  clear: both;
}
.alignRight > *:nth-child(2) {
  clear: both;
  display: block;
  border: none;
}
svg {
  display: block;
}
.alignCenter.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignCenter.art-text pre {
  padding: 0;
}
.alignCenter {
  margin: 1em 0;
}
.alignCenter > *:first-child {
  border: none;
  /* this isn't optimal, but it's an existence proof.  PrinceXML doesn't
     support flexbox yet.
  */
  display: table;
  margin: 0 auto;
}

/* lists */
ol, ul {
  padding: 0;
  margin: 0 0 1em 2em;
}
ol ol, ul ul, ol ul, ul ol {
  margin-left: 1em;
}
li {
  margin: 0 0 0.25em 0;
}
.ulCompact li {
  margin: 0;
}
ul.empty, .ulEmpty {
  list-style-type: none;
}
ul.empty li, .ulEmpty li {
  margin-top: 0.5em;
}
ul.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: 100%;
  margin: 0 0 0 2em;
}

/* definition lists */
dl {
}
dl > dt {
  float: left;
  margin-right: 1em;
}
/* 
dl.nohang > dt {
  float: none;
}
*/
dl > dd {
  margin-bottom: .8em;
  min-height: 1.3em;
}
dl.compact > dd, .dlCompact > dd {
  margin-bottom: 0em;
}
dl > dd > dl {
  margin-top: 0.5em;
  margin-bottom: 0em;
}

/* links */
a {
  text-decoration: none;
}
a[href] {
  color: #22e; /* Arlen: WCAG 2019 */
}
a[href]:hover {
  background-color: #f2f2f2;
}
figcaption a[href],
a[href].selfRef {
  color: #222;
}
/* XXX probably not this:
a.selfRef:hover {
  background-color: transparent;
  cursor: default;
} */

/* Figures */
tt, code, pre, code {
  background-color: #f9f9f9;
  font-family: 'Roboto Mono', monospace;
}
pre {
  border: 1px solid #eee;
  margin: 0;
  padding: 1em;
}
img {
  max-width: 100%;
}
figure {
  margin: 0;
}
figure blockquote {
  margin: 0.8em 0.4em 0.4em;
}
figcaption {
  font-style: italic;
  margin: 0 0 1em 0;
}
@media screen {
  pre {
    overflow-x: auto;
    max-width: 100%;
    max-width: calc(100% - 22px);
  }
}

/* aside, blockquote */
aside, blockquote {
  margin-left: 0;
  padding: 1.2em 2em;
}
blockquote {
  background-color: #f9f9f9;
  color: #111; /* Arlen: WCAG 2019 */
  border: 1px solid #ddd;
  border-radius: 3px;
  margin: 1em 0;
}
cite {
  display: block;
  text-align: right;
  font-style: italic;
}

/* tables */
table {
  width: 100%;
  margin: 0 0 1em;
  border-collapse: collapse;
  border: 1px solid #eee;
}
th, td {
  text-align: left;
  vertical-align: top;
  padding: 0.5em 0.75em;
}
th {
  text-align: left;
  background-color: #e9e9e9;
}
tr:nth-child(2n+1) > td {
  background-color: #f5f5f5;
}
table caption {
  font-style: italic;
  margin: 0;
  padding: 0;
  text-align: left;
}
table p {
  /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
     be allowed within tables more generally, it would be far better to select on a class. */
  margin: 0;
}

/* pilcrow */
a.pilcrow {
  color: #666; /* Arlen: AHDJ 2019 */
  text-decoration: none;
  visibility: hidden;
  user-select: none;
  -ms-user-select: none;
  -o-user-select:none;
  -moz-user-select: none;
  -khtml-user-select: none;
  -webkit-user-select: none;
  -webkit-touch-callout: none;
}
@media screen {
  aside:hover > a.pilcrow,
  p:hover > a.pilcrow,
  blockquote:hover > a.pilcrow,
  div:hover > a.pilcrow,
  li:hover > a.pilcrow,
  pre:hover > a.pilcrow {
    visibility: visible;
  }
  a.pilcrow:hover {
    background-color: transparent;
  }
}

/* misc */
hr {
  border: 0;
  border-top: 1px solid #eee;
}
.bcp14 {
  font-variant: small-caps;
}

.role {
  font-variant: all-small-caps;
}

/* info block */
#identifiers {
  margin: 0;
  font-size: 0.9em;
}
#identifiers dt {
  width: 3em;
  clear: left;
}
#identifiers dd {
  float: left;
  margin-bottom: 0;
}
#identifiers .authors .author {
  display: inline-block;
  margin-right: 1.5em;
}
#identifiers .authors .org {
  font-style: italic;
}

/* The prepared/rendered info at the very bottom of the page */
.docInfo {
  color: #666; /* Arlen: WCAG 2019 */
  font-size: 0.9em;
  font-style: italic;
  margin-top: 2em;
}
.docInfo .prepared {
  float: left;
}
.docInfo .prepared {
  float: right;
}

/* table of contents */
#toc  {
  padding: 0.75em 0 2em 0;
  margin-bottom: 1em;
}
nav.toc ul {
  margin: 0 0.5em 0 0;
  padding: 0;
  list-style: none;
}
nav.toc li {
  line-height: 1.3em;
  margin: 0.75em 0;
  padding-left: 1.2em;
  text-indent: -1.2em;
}
/* references */
.references dt {
  text-align: right;
  font-weight: bold;
  min-width: 7em;
}
.references dd {
  margin-left: 8em;
  overflow: auto;
}

.refInstance {
  margin-bottom: 1.25em;
}

.references .ascii {
  margin-bottom: 0.25em;
}

/* index */
.index ul {
  margin: 0 0 0 1em;
  padding: 0;
  list-style: none;
}
.index ul ul {
  margin: 0;
}
.index li {
  margin: 0;
  text-indent: -2em;
  padding-left: 2em;
  padding-bottom: 5px;
}
.indexIndex {
  margin: 0.5em 0 1em;
}
.index a {
  font-weight: 700;
}
/* make the index two-column on all but the smallest screens */
@media (min-width: 600px) {
  .index ul {
    -moz-column-count: 2;
    -moz-column-gap: 20px;
  }
  .index ul ul {
    -moz-column-count: 1;
    -moz-column-gap: 0;
  }
}

/* authors */
address.vcard {
  font-style: normal;
  margin: 1em 0;
}

address.vcard .nameRole {
  font-weight: 700;
  margin-left: 0;
}
address.vcard .label {
  font-family: "Noto Sans",Arial,Helvetica,sans-serif;
  margin: 0.5em 0;
}
address.vcard .type {
  display: none;
}
.alternative-contact {
  margin: 1.5em 0 1em;
}
hr.addr {
  border-top: 1px dashed;
  margin: 0;
  color: #ddd;
  max-width: calc(100% - 16px);
}

/* temporary notes */
.rfcEditorRemove::before {
  position: absolute;
  top: 0.2em;
  right: 0.2em;
  padding: 0.2em;
  content: "The RFC Editor will remove this note";
  color: #9e2a00; /* Arlen: WCAG 2019 */
  background-color: #ffd; /* Arlen: WCAG 2019 */
}
.rfcEditorRemove {
  position: relative;
  padding-top: 1.8em;
  background-color: #ffd; /* Arlen: WCAG 2019 */
  border-radius: 3px;
}
.cref {
  background-color: #ffd; /* Arlen: WCAG 2019 */
  padding: 2px 4px;
}
.crefSource {
  font-style: italic;
}
/* alternative layout for smaller screens */
@media screen and (max-width: 1023px) {
  body {
    padding-top: 2em;
  }
  #title {
    padding: 1em 0;
  }
  h1 {
    font-size: 24px;
  }
  h2 {
    font-size: 20px;
    margin-top: -18px;  /* provide offset for in-page anchors */
    padding-top: 38px;
  }
  #identifiers dd {
    max-width: 60%;
  }
  #toc {
    position: fixed;
    z-index: 2;
    top: 0;
    right: 0;
    padding: 0;
    margin: 0;
    background-color: inherit;
    border-bottom: 1px solid #ccc;
  }
  #toc h2 {
    margin: -1px 0 0 0;
    padding: 4px 0 4px 6px;
    padding-right: 1em;
    min-width: 190px;
    font-size: 1.1em;
    text-align: right;
    background-color: #444;
    color: white;
    cursor: pointer;
  }
  #toc h2::before { /* css hamburger */
    float: right;
    position: relative;
    width: 1em;
    height: 1px;
    left: -164px;
    margin: 6px 0 0 0;
    background: white none repeat scroll 0 0;
    box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
    content: "";
  }
  #toc nav {
    display: none;
    padding: 0.5em 1em 1em;
    overflow: auto;
    height: calc(100vh - 48px);
    border-left: 1px solid #ddd;
  }
}

/* alternative layout for wide screens */
@media screen and (min-width: 1024px) {
  body {
    max-width: 724px;
    margin: 42px auto;
    padding-left: 1.5em;
    padding-right: 29em;
  }
  #toc {
    position: fixed;
    top: 42px;
    right: 42px;
    width: 25%;
    margin: 0;
    padding: 0 1em;
    z-index: 1;
  }
  #toc h2 {
    border-top: none;
    border-bottom: 1px solid #ddd;
    font-size: 1em;
    font-weight: normal;
    margin: 0;
    padding: 0.25em 1em 1em 0;
  }
  #toc nav {
    display: block;
    height: calc(90vh - 84px);
    bottom: 0;
    padding: 0.5em 0 0;
    overflow: auto;
  }
  img { /* future proofing */
    max-width: 100%;
    height: auto;
  }
}

/* pagination */
@media print {
  body {

    width: 100%;
  }
  p {
    orphans: 3;
    widows: 3;
  }
  #n-copyright-notice {
    border-bottom: none;
  }
  #toc, #n-introduction {
    page-break-before: always;
  }
  #toc {
    border-top: none;
    padding-top: 0;
  }
  figure, pre {
    page-break-inside: avoid;
  }
  figure {
    overflow: scroll;
  }
  h1, h2, h3, h4, h5, h6 {
    page-break-after: avoid;
  }
  h2+*, h3+*, h4+*, h5+*, h6+* {
    page-break-before: avoid;
  }
  pre {
    white-space: pre-wrap;
    word-wrap: break-word;
    font-size: 10pt;
  }
  table {
    border: 1px solid #ddd;
  }
  td {
    border-top: 1px solid #ddd;
  }
}

/* This is commented out here, as the string-set: doesn't
   pass W3C validation currently */
/*
.ears thead .left {
  string-set: ears-top-left content();
}

.ears thead .center {
  string-set: ears-top-center content();
}

.ears thead .right {
  string-set: ears-top-right content();
}

.ears tfoot .left {
  string-set: ears-bottom-left content();
}

.ears tfoot .center {
  string-set: ears-bottom-center content();
}

.ears tfoot .right {
  string-set: ears-bottom-right content();
}
*/

@page :first {
  padding-top: 0;
  @top-left {
    content: normal;
    border: none;
  }
  @top-center {
    content: normal;
    border: none;
  }
  @top-right {
    content: normal;
    border: none;
  }
}

@page {
  size: A4;
  margin-bottom: 45mm;
  padding-top: 20px;
  /* The follwing is commented out here, but set appropriately by in code, as
     the content depends on the document */
  /*
  @top-left {
    content: 'Internet-Draft';
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-left {
    content: string(ears-top-left);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-center {
    content: string(ears-top-center);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-right {
    content: string(ears-top-right);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @bottom-left {
    content: string(ears-bottom-left);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-center {
    content: string(ears-bottom-center);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-right {
      content: '[Page ' counter(page) ']';
      vertical-align: top;
      border-top: solid 1px #ccc;
  }
  */

}

/* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
  z-index: 2;
}
/* Separate body from document info even without intervening H1 */
section {
  clear: both;
}


/* Top align author divs, to avoid names without organization dropping level with org names */
.author {
  vertical-align: top;
}

/* Leave room in document info to show Internet-Draft on one line */
#identifiers dt {
  width: 8em;
}

/* Don't waste quite as much whitespace between label and value in doc info */
#identifiers dd {
  margin-left: 1em;
}

/* Give floating toc a background color (needed when it's a div inside section */
#toc {
  background-color: white;
}

/* Make the collapsed ToC header render white on gray also when it's a link */
@media screen and (max-width: 1023px) {
  #toc h2 a,
  #toc h2 a:link,
  #toc h2 a:focus,
  #toc h2 a:hover,
  #toc a.toplink,
  #toc a.toplink:hover {
    color: white;
    background-color: #444;
    text-decoration: none;
  }
}

/* Give the bottom of the ToC some whitespace */
@media screen and (min-width: 1024px) {
  #toc {
    padding: 0 0 1em 1em;
  }
}

/* Style section numbers with more space between number and title */
.section-number {
  padding-right: 0.5em;
}

/* prevent monospace from becoming overly large */
tt, code, pre, code {
  font-size: 95%;
}

/* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre {
  line-height: 1.12;
}


/* Add styling for a link in the ToC that points to the top of the document */
a.toplink {
  float: right;
  margin-right: 0.5em;
}

/* Fix the dl styling to match the RFC 7992 attributes */
dl > dt,
dl.dlParallel > dt {
  float: left;
  margin-right: 1em;
}
dl.dlNewline > dt {
  float: none;
}

/* Provide styling for table cell text alignment */
table td.text-left,
table th.text-left {
  text-align: left;
}
table td.text-center,
table th.text-center {
  text-align: center;
}
table td.text-right,
table th.text-right {
  text-align: right;
}

/* Make the alternative author contact informatio look less like just another
   author, and group it closer with the primary author contact information */
.alternative-contact {
  margin: 0.5em 0 0.25em 0;
}
address .non-ascii {
  margin: 0 0 0 2em;
}

/* With it being possible to set tables with alignment
  left, center, and right, { width: 100%; } does not make sense */
table {
  width: auto;
}

/* Avoid reference text that sits in a block with very wide left margin,
   because of a long floating dt label.*/
.references dd {
  overflow: visible;
}

/* Control caption placement */
caption {
  caption-side: bottom;
}

/* Limit the width of the author address vcard, so names in right-to-left
   script don't end up on the other side of the page. */

address.vcard {
  max-width: 30em;
  margin-right: auto;
}

/* For address alignment dependent on LTR or RTL scripts */
address div.left {
  text-align: left;
}
address div.right {
  text-align: right;
}

/* Provide table alignment support.  We can't use the alignX classes above
   since they do unwanted things with caption and other styling. */
table.right {
 margin-left: auto;
 margin-right: 0;
}
table.center {
 margin-left: auto;
 margin-right: auto;
}
table.left {
 margin-left: 0;
 margin-right: auto;
}

/* Give the table caption label the same styling as the figcaption */
caption a[href] {
  color: #222;
}

@media print {
  .toplink {
    display: none;
  }

  /* avoid overwriting the top border line with the ToC header */
  #toc {
    padding-top: 1px;
  }

  /* Avoid page breaks inside dl and author address entries */
  .vcard {
    page-break-inside: avoid;
  }

}
/* Avoid wrapping of URLs in references */
@media screen {
  .references a {
    white-space: nowrap;
  }
}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin: 0 0 0.25em 0;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/*
  The margin-left: 0 on <dd> removes all distinction
  between levels from nested <dl>s.  Undo that.
*/
dl.olPercent > dd,
dd {
  margin-left: revert;
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc8718" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-mtgvenue-iaoc-venue-selection-process-16" rel="prev">
  </head>
<body>
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">RFC 8718</td>
<td class="center">Venue Selection</td>
<td class="right">February 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Lear</td>
<td class="center">Best Current Practice</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Internet Engineering Task Force (IETF)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8718" class="eref">8718</a></dd>
<dt class="label-bcp">BCP:</dt>
<dd class="bcp">226</dd>
<dt class="label-category">Category:</dt>
<dd class="category">Best Current Practice</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2020-02" class="published">February 2020</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Author:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">E. Lear, <span class="editor">Ed.</span>
</div>
<div class="org">Cisco Systems</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8718</h1>
<h1 id="title">IETF Plenary Meeting Venue Selection Process</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">
      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.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This memo documents an Internet Best Current Practice.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="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.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="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
            <span><a href="https://www.rfc-editor.org/info/rfc8718">https://www.rfc-editor.org/info/rfc8718</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2020 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) 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.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-venue-selection-objectives" class="xref">Venue Selection Objectives</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.2.2.1">
                <p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>.  <a href="#name-core-values" class="xref">Core Values</a><a href="#section-toc.1-1.2.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.2.2.2">
                <p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="xref">2.2</a>.  <a href="#name-venue-selection-non-objecti" class="xref">Venue Selection Non-objectives</a><a href="#section-toc.1-1.2.2.2.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-meeting-criteria" class="xref">Meeting Criteria</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.3.2.1">
                <p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-mandatory-criteria" class="xref">Mandatory Criteria</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.2">
                <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-important-criteria" class="xref">Important Criteria</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.3">
                <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-other-considerations" class="xref">Other Considerations</a><a href="#section-toc.1-1.3.2.3.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-documentation-requirements" class="xref">Documentation Requirements</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-privacy-considerations" class="xref">Privacy Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#section-appendix.c" class="xref"></a><a href="#name-authors-address" class="xref">Author's Address</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
</li>
</ul>
</nav>
</section>
</div>
<div id="Introduction">
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">The IETF Administrative Support Activity (IASA) <span>[<a href="#RFC8711" class="xref">RFC8711</a>]</span> is
        responsible for arranging the selection and operation of the IETF
 plenary meeting venue.  The purpose of this document is to
        guide the IASA in their selection of regions, cities, 
        facilities, and hotels.  The IASA should apply this guidance at
        different points in the process in an attempt to faithfully
        meet the requirements of the IETF community.  We specify a set
        of general criteria for venue selection and several requirements for
 transparency and community consultation.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">It remains the responsibility of the IASA to apply their best judgment. The
IASA accepts input and feedback during the consultation process and later (for
instance, when there are changes in the situation at a chosen location).
The community is encouraged to provide direct feedback about the IASA's
performance to the IETF Administration LLC, the Nominations Committee (NOMCOM),
or the Internet Engineering Steering Group (IESG). Any reviews of IASA
decisions remain subject to the provisions of <span><a href="https://www.rfc-editor.org/rfc/rfc8711#section-4.7" class="relref">Section 4.7</a> of [<a href="#RFC8711" class="xref">RFC8711</a>]</span> (BCP 101).<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">The following four terms describe the places for which the IETF contracts
          services:<a href="#section-1-3" class="pilcrow">¶</a></p>
<dl class="dlNewline" id="section-1-4">
        <dt id="section-1-4.1">Venue:</dt>
<dd id="section-1-4.2">An umbrella term for the
            city, meeting resources, and guest room resources.<a href="#section-1-4.2" class="pilcrow">¶</a>
</dd>
<dt id="section-1-4.3">Facility:</dt>
<dd id="section-1-4.4">The building that houses
            meeting rooms and associated resources. It may also
            house an IETF Hotel.<a href="#section-1-4.4" class="pilcrow">¶</a>
</dd>
<dt id="section-1-4.5">IETF Hotels:</dt>
<dd id="section-1-4.6">One or more hotels, in close
            proximity to the Facility, where the IETF guest room block
            allocations are
            negotiated and where network services managed by the IASA
            (e.g., the "IETF" SSID) are in use.<a href="#section-1-4.6" class="pilcrow">¶</a>
</dd>
<dt id="section-1-4.7">Overflow Hotels:</dt>
<dd id="section-1-4.8">One or more
            hotels, usually in close proximity to the Facility,
            where the IETF has negotiated a group room rate for the purposes of
            the meeting.  Of particular note is that Overflow Hotels
            are not usually connected to the IETF network and do not
            use network services managed by the IASA.<a href="#section-1-4.8" class="pilcrow">¶</a>
</dd>
</dl>
<p id="section-1-5">
    The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
    "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
    described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> 
    when, and only when, they appear in all capitals, as shown here.<a href="#section-1-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="objectives">
<section id="section-2">
      <h2 id="name-venue-selection-objectives">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-venue-selection-objectives" class="section-name selfRef">Venue Selection Objectives</a>
      </h2>
<div id="core">
<section id="section-2.1">
        <h3 id="name-core-values">
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-core-values" class="section-name selfRef">Core Values</a>
        </h3>
<p id="section-2.1-1">Some IETF values pervade the selection process. These are often
          applicable to multiple requirements listed in this document. At a
   minimum, they include the following:<a href="#section-2.1-1" class="pilcrow">¶</a></p>
<dl class="dlNewline" id="section-2.1-2">
          <dt id="section-2.1-2.1">Why we meet:</dt>
<dd id="section-2.1-2.2">We meet to pursue the IETF's
              mission <span>[<a href="#RFC3935" class="xref">RFC3935</a>]</span>. This is partly done by
       advancing the development of Internet-Drafts and RFCs. We also seek to
              facilitate attendee participation in multiple topics and to enable
              cross-pollination of ideas and technologies.<a href="#section-2.1-2.2" class="pilcrow">¶</a>
</dd>
<dt id="section-2.1-2.3">Inclusiveness:</dt>
<dd id="section-2.1-2.4">
            <p id="section-2.1-2.4.1">We would like to facilitate
              the on-site or remote participation of anyone who wants to be
              involved.  Widespread participation contributes to the
              diversity of perspectives represented in the 
              working sessions.<a href="#section-2.1-2.4.1" class="pilcrow">¶</a></p>
<p id="section-2.1-2.4.2">Every country has limits on who it will permit within its
       borders. However, the IETF seeks to:<a href="#section-2.1-2.4.2" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-2.1-2.4.3">
              <li id="section-2.1-2.4.3.1">Minimize situations in which onerous entry regulations
                  inhibit, discourage, or prevent participants from
                  attending meetings; failing that, meeting locations are to
   be distributed such that onerous entry
                  regulations are not always experienced by the same
                  attendees; and<a href="#section-2.1-2.4.3.1" class="pilcrow">¶</a>
</li>
<li id="section-2.1-2.4.3.2">Avoid meeting in countries with laws that effectively exclude
                  people on the basis of race, ethnicity, religion, gender, sexual
                  orientation, national origin, citizenship, or gender
                  identity.<a href="#section-2.1-2.4.3.2" class="pilcrow">¶</a>
</li>
</ol>
</dd>
<dt id="section-2.1-2.5">Where we meet:</dt>
<dd id="section-2.1-2.6">We meet in different
              global locations, in order to spread the difficulty and cost of
              travel among active participants, balancing travel time and
              expense across participants based in various regions.  Our
       regional location policy is articulated in
              <span>[<a href="#RFC8719" class="xref">RFC8719</a>]</span>.<a href="#section-2.1-2.6" class="pilcrow">¶</a>
</dd>
<dt id="section-2.1-2.7">Internet Access:</dt>
<dd id="section-2.1-2.8">As an organization, we
              write specifications for the Internet, and we use it heavily.
              Meeting attendees need unfiltered access to the general Internet
              and their corporate networks.  "Unfiltered access", in this
              case, means that all forms of communication are allowed.
              This includes, but is not limited to, access to corporate networks
              via encrypted VPNs from the meeting Facility and Hotels, including
              Overflow Hotels. We also need open network access available at
              high enough data rates, at the meeting Facility, to support our
              work, which includes support of remote
              participation. Beyond this, we are the first users of
              our own technology. Any filtering may cause a problem
              with that technology development.  In some cases,
              local laws may require some filtering.  We seek to
              avoid such locales without reducing the
              pool of cities to an unacceptable level by stating a
              number of criteria below, one mandatory and others
              important, to allow for the case where local laws may
              require filtering in some circumstances.<a href="#section-2.1-2.8" class="pilcrow">¶</a>
</dd>
<dt id="section-2.1-2.9">Focus:</dt>
<dd id="section-2.1-2.10">We meet to have focused
              technical discussions. These are not limited to
              scheduled breakout sessions, although of course those
              are important. They also happen over meals or drinks,
              through a specific type of non-session that we call a
              "Bar BOF", or in side meetings. Environments that are
              noisy or distracting prevent or reduce the
              effectiveness of these sessions and are therefore less desirable as a
              meeting Facility <span>[<a href="#RFC6771" class="xref">RFC6771</a>]</span>.<a href="#section-2.1-2.10" class="pilcrow">¶</a>
</dd>
<dt id="section-2.1-2.11">Economics:</dt>
<dd id="section-2.1-2.12">Meeting attendees participate as
              individuals. While many are underwritten by employers or sponsors,
              many are self-funded. In order to reduce participation costs and
              travel effort, we therefore seek locations that provide convenient
              budget alternatives for food and lodging, and that minimize
              travel segments from major airports to the Venue. Within reason,
              one's budget should not be a barrier to accommodation.<a href="#section-2.1-2.12" class="pilcrow">¶</a>
</dd>
<dt id="section-2.1-2.13">Least Astonishment and Openness:</dt>
<dd id="section-2.1-2.14">Regular participants
              should not be surprised by meeting Venue selections, particularly
              when it comes to locales. To avoid surprise, the venue
              selection process, as with all other IETF processes,
              should be as open as practicable.  It should be possible
              for the community to engage in discussion early to express its views
              on prospective selections, so that the community and the
              IASA can exchange views as to appropriateness long 
              before a venue contract is considered.<a href="#section-2.1-2.14" class="pilcrow">¶</a>
</dd>
</dl>
</section>
</div>
<div id="nonobjectives">
<section id="section-2.2">
        <h3 id="name-venue-selection-non-objecti">
<a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-venue-selection-non-objecti" class="section-name selfRef">Venue Selection Non-objectives</a>
        </h3>
<p id="section-2.2-1">IETF meeting Venues are not selected or declined with the explicit
          purposes of:<a href="#section-2.2-1" class="pilcrow">¶</a></p>
<dl class="dlNewline" id="section-2.2-2">
          <dt id="section-2.2-2.1">Politics:</dt>
<dd id="section-2.2-2.2">Endorsing or condemning
              particular countries, political paradigms, laws, regulations, or
              policies.<a href="#section-2.2-2.2" class="pilcrow">¶</a>
</dd>
<dt id="section-2.2-2.3">Maximal attendance:</dt>
<dd id="section-2.2-2.4">While the IETF strives to be as inclusive as possible,
              both online and in person, maximal
              meeting attendance in and of itself is not a goal. It
              would defeat a key goal of meeting if
              active contributors with differing
              points of view did not have the opportunity to resolve their
              disagreements, no matter how full the rooms.<a href="#section-2.2-2.4" class="pilcrow">¶</a>
</dd>
<dt id="section-2.2-2.5">Tourism:</dt>
<dd id="section-2.2-2.6">Variety in site-seeing
              experiences.<a href="#section-2.2-2.6" class="pilcrow">¶</a>
</dd>
</dl>
</section>
</div>
</section>
</div>
<div id="criteria">
<section id="section-3">
      <h2 id="name-meeting-criteria">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-meeting-criteria" class="section-name selfRef">Meeting Criteria</a>
      </h2>
<p id="section-3-1">This section contains the criteria for IETF meetings.  It is
      broken down into three subsections: <span><a href="#mandatories" class="xref">mandatory criteria</a> (<a href="#mandatories" class="xref">Section 3.1</a>)</span>,
      <span><a href="#importants" class="xref">important criteria</a> (<a href="#importants" class="xref">Section 3.2</a>)</span>, and <span><a href="#otherconsiderations" class="xref">other considerations</a> (<a href="#otherconsiderations" class="xref">Section 3.3</a>)</span>, each as explained
      below.<a href="#section-3-1" class="pilcrow">¶</a></p>
<div id="mandatories">
<section id="section-3.1">
        <h3 id="name-mandatory-criteria">
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-mandatory-criteria" class="section-name selfRef">Mandatory Criteria</a>
        </h3>
<p id="section-3.1-1">If criteria in this subsection cannot be met, a particular
       location is unacceptable for selection, and the IASA <span class="bcp14">MUST NOT</span> 
       enter into a contract.  Should the IASA learn that a location
       can no longer meet a mandatory requirement after having entered
       into a contract, it will inform the community and address the
       matter on a case-by-case basis.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-3.1-2.1">The Facility <span class="bcp14">MUST</span> provide sufficient
         space in an appropriate layout to accommodate the 
         number of participants, leadership, and support staff expected to
         attend that meeting.<a href="#section-3.1-2.1" class="pilcrow">¶</a>
</li>
<li id="section-3.1-2.2">The Facility and IETF Hotels <span class="bcp14">MUST</span> provide wheelchair access
  to accommodate the number of people who are anticipated to
  require it.<a href="#section-3.1-2.2" class="pilcrow">¶</a>
</li>
<li id="section-3.1-2.3">It <span class="bcp14">MUST</span> be possible to provision
  Internet Access to the Facility and IETF Hotels 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 <span class="bcp14">MUST</span> be possible to provision redundant paths to the
  Internet.<a href="#section-3.1-2.3" class="pilcrow">¶</a>
</li>
</ul>
</section>
</div>
<div id="importants">
<section id="section-3.2">
        <h3 id="name-important-criteria">
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-important-criteria" class="section-name selfRef">Important Criteria</a>
        </h3>
<p id="section-3.2-1">The criteria in this subsection are not mandatory,
              but they are still highly significant. It may be necessary to
              trade-off one or more of these criteria against others.
              A Venue that meets more of these criteria is, on the
              whole, preferable to another that meets fewer of
              these criteria. Requirements classed as Important can
              also be balanced across Venue selections for multiple
              meetings. When a particular requirement in this section
              cannot be met but the Venue is selected anyway, the IASA <span class="bcp14">MUST</span> notify the community at the
              time of the venue announcement.  Furthermore, it may be
              appropriate for the IASA to assist those who, as a
              result, have been inconvenienced in some way.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
<section id="section-3.2.1">
          <h4 id="name-venue-city-criteria">
<a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-venue-city-criteria" class="section-name selfRef">Venue City Criteria</a>
          </h4>
<p id="section-3.2.1-1">The following requirements relate to the Venue city.<a href="#section-3.2.1-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-3.2.1-2.1">Travel to the Venue is acceptable based on cost, time, and burden
            for participants traveling from multiple regions. It is anticipated
            that the burden borne will generally be shared over the course of
            multiple years.<a href="#section-3.2.1-2.1" class="pilcrow">¶</a>
</li>
<li id="section-3.2.1-2.2">The Venue is assessed as favorable for obtaining a host and
            sponsors. That is, the Meeting is in a location in which
            it is possible and probable to find a host and sponsors.<a href="#section-3.2.1-2.2" class="pilcrow">¶</a>
</li>
<li id="section-3.2.1-2.3">Travel barriers to entry, including visa requirements, are
     likely to be such that an overwhelming majority of
     participants who wish to do so can attend.  The term "travel
     barriers" is to be read 
     broadly by the IASA in the context of whether a
     successful meeting can be had.<a href="#section-3.2.1-2.3" class="pilcrow">¶</a>
</li>
<li id="section-3.2.1-2.4">Economic, safety, and health risks associated with this Venue are
            acceptable.<a href="#section-3.2.1-2.4" class="pilcrow">¶</a>
</li>
<li id="section-3.2.1-2.5">The selection of the venue comports with the practices described in
              <span>[<a href="#RFC8719" class="xref">RFC8719</a>]</span>.<a href="#section-3.2.1-2.5" class="pilcrow">¶</a>
</li>
</ul>
</section>
<section id="section-3.2.2">
          <h4 id="name-basic-venue-criteria">
<a href="#section-3.2.2" class="section-number selfRef">3.2.2. </a><a href="#name-basic-venue-criteria" class="section-name selfRef">Basic Venue Criteria</a>
          </h4>
<p id="section-3.2.2-1">The following requirements relate to the Venue and Facilities.<a href="#section-3.2.2-1" class="pilcrow">¶</a></p>
<p id="section-3.2.2-2">The IETF operates internationally and adjusts to
          local requirements. Facilities selected for IETF meetings <span class="bcp14">SHALL</span>
   have provided written assurance that they are in compliance with
          local health, safety, and accessibility laws and regulations,
          and that they will remain in compliance throughout our stay.<a href="#section-3.2.2-2" class="pilcrow">¶</a></p>
<p id="section-3.2.2-3">In addition:<a href="#section-3.2.2-3" class="pilcrow">¶</a></p>
<ul>
<li id="section-3.2.2-4.1">There are sufficient places (e.g., a mix of hallways, bars, meeting
     rooms, and restaurants) for people to hold ad hoc
     conversations and group discussions in the combination of
     spaces offered by the facilities, hotels, and
     bars/restaurants in the surrounding area, within walking
     distance (5-10 minutes).<a href="#section-3.2.2-4.1" class="pilcrow">¶</a>
</li>
<li id="section-3.2.2-4.2">The cost of guest rooms, meeting space, meeting food and beverage
            is affordable, within the norms of business travel.<a href="#section-3.2.2-4.2" class="pilcrow">¶</a>
</li>
<li id="section-3.2.2-4.3">The Facility is accessible, or
   reasonable accommodations can be made to allow access, by people with
   disabilities.<a href="#section-3.2.2-4.3" class="pilcrow">¶</a>
</li>
</ul>
</section>
<section id="section-3.2.3">
          <h4 id="name-technical-meeting-needs">
<a href="#section-3.2.3" class="section-number selfRef">3.2.3. </a><a href="#name-technical-meeting-needs" class="section-name selfRef">Technical Meeting Needs</a>
          </h4>
<p id="section-3.2.3-1">The following criteria relate to technical meeting needs.<a href="#section-3.2.3-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-3.2.3-2.1">The Facility's support technologies and services -- network,
            audio-video, etc. -- are sufficient for the anticipated activities
            at the meeting, or the Facility is willing to add such
            infrastructure, or these support technologies and services might be
            provided by a third party, all at no -- or at an acceptable -- cost
            to the IETF.<a href="#section-3.2.3-2.1" class="pilcrow">¶</a>
</li>
<li id="section-3.2.3-2.2">The IETF Hotels directly provide, or else permit and facilitate,
            the delivery of a high performance, robust, unfiltered, and
            unmodified Internet service for the public areas and guest
            rooms; this service is to be included in the cost of
            the room.<a href="#section-3.2.3-2.2" class="pilcrow">¶</a>
</li>
</ul>
</section>
<section id="section-3.2.4">
          <h4 id="name-hotel-needs">
<a href="#section-3.2.4" class="section-number selfRef">3.2.4. </a><a href="#name-hotel-needs" class="section-name selfRef">Hotel Needs</a>
          </h4>
<p id="section-3.2.4-1">The following criteria relate to IETF Hotels.<a href="#section-3.2.4-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-3.2.4-2.1">The IETF Hotels are within close proximity to each other and the
            Facility.<a href="#section-3.2.4-2.1" class="pilcrow">¶</a>
</li>
<li id="section-3.2.4-2.2">The guest rooms at the IETF Hotels are sufficient in number to
            house one-third or more of projected meeting attendees.<a href="#section-3.2.4-2.2" class="pilcrow">¶</a>
</li>
<li id="section-3.2.4-2.3">Overflow Hotels can be placed under contract, within convenient
            travel time to and from the Facility and at a variety of guest room
            rates.<a href="#section-3.2.4-2.3" class="pilcrow">¶</a>
</li>
<li id="section-3.2.4-2.4">The Facility environs include budget hotels within convenient travel
            time, cost, and effort.<a href="#section-3.2.4-2.4" class="pilcrow">¶</a>
</li>
<li id="section-3.2.4-2.5">The IETF Hotels are accessible by people with disabilities.
          While we mandate wheelchair accessibility, other forms are
          important and should be provided for to the extent possible
          based on anticipated needs of the community.<a href="#section-3.2.4-2.5" class="pilcrow">¶</a>
</li>
<li id="section-3.2.4-2.6">At least one IETF Hotel or the Facility has a space for use as a
   lounge, conducive to planned and ad hoc meetings and chatting, as well
            as a space for working online. There are tables with seating, convenient for
            small meetings with laptops. These can be at an open bar or casual
            restaurant. Preferably the lounge area is centrally
            located, permitting easy access to participants.<a href="#section-3.2.4-2.6" class="pilcrow">¶</a>
</li>
</ul>
</section>
<section id="section-3.2.5">
          <h4 id="name-food-and-beverage">
<a href="#section-3.2.5" class="section-number selfRef">3.2.5. </a><a href="#name-food-and-beverage" class="section-name selfRef">Food and Beverage</a>
          </h4>
<p id="section-3.2.5-1">The following criteria relate to food and
 beverage.<a href="#section-3.2.5-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-3.2.5-2.1">The Facility environs, which include both on-site as well as areas
            within a reasonable walking distance or conveniently
            accessible by a short taxi ride or by local
            public transportation, have convenient and inexpensive
            choices for meals that can accommodate a wide range of dietary
            requirements.<a href="#section-3.2.5-2.1" class="pilcrow">¶</a>
</li>
<li id="section-3.2.5-2.2">A range of attendees' health-related and religion-related dietary
            requirements can be satisfied with robust and flexible on-site
            service or through access to an adequate grocery store.<a href="#section-3.2.5-2.2" class="pilcrow">¶</a>
</li>
<li id="section-3.2.5-2.3">The Facility environs include grocery shopping that will accommodate a
            wide range of dietary requirements, within a reasonable walking
            distance or conveniently accessible by a short taxi, bus, or subway
            ride from the Facility and IETF Hotels.<a href="#section-3.2.5-2.3" class="pilcrow">¶</a>
</li>
</ul>
</section>
</section>
</div>
<div id="otherconsiderations">
<section id="section-3.3">
        <h3 id="name-other-considerations">
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-other-considerations" class="section-name selfRef">Other Considerations</a>
        </h3>
<p id="section-3.3-1">The following considerations are desirable, but they are not as
      important as the preceding requirements and thus should not be
      traded-off for them.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-3.3-2.1">We have something of a preference for an IETF meeting to
            be under "One Roof"; that is, qualified meeting space and guest rooms are available in the
            same facility.<a href="#section-3.3-2.1" class="pilcrow">¶</a>
</li>
<li id="section-3.3-2.2">It is desirable for Overflow Hotels to provide reasonable,
            reliable, unfiltered Internet service for the public areas
            and guest rooms, and for this service be included in the
            cost of the room.<a href="#section-3.3-2.2" class="pilcrow">¶</a>
</li>
<li id="section-3.3-2.3">It is desirable to enter into a multi-event contract with the
     Facility and IETF Hotels or associated hotel chains in
     case such a contract will reduce 
     administrative costs, reduce direct attendee costs, or both.<a href="#section-3.3-2.3" class="pilcrow">¶</a>
</li>
<li id="section-3.3-2.4">When we are considering a city for the first
     time, it is particularly desirable to have someone familiar with
     both the locale and the IETF participate in the site
     visit. Such a person can provide guidance 
     regarding safety, location of local services, 
     the best ways to get to and from the Venue, and
     local customs, as well as how our requirements are
     met.<a href="#section-3.3-2.4" class="pilcrow">¶</a>
</li>
</ul>
</section>
</div>
</section>
</div>
<section id="section-4">
      <h2 id="name-documentation-requirements">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-documentation-requirements" class="section-name selfRef">Documentation Requirements</a>
      </h2>
<p id="section-4-1">The IETF Community works best when it is well informed.  This
      memo does not specify processes nor who has responsibility for
      fulfilling our requirements for meetings.  Nevertheless, both of
      these aspects are important.  Therefore, the IASA <span class="bcp14">SHALL</span> publicly
      document and keep current both a list of roles and
      responsibilities relating to IETF meetings, as well as the
      selection processes they use in order to fulfill the
      requirements of the community.<a href="#section-4-1" class="pilcrow">¶</a></p>
</section>
<div id="IANA">
<section id="section-5">
      <h2 id="name-iana-considerations">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-5-1">This document has no IANA actions.<a href="#section-5-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="Security">
<section id="section-6">
      <h2 id="name-security-considerations">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-6-1">This note proposes no protocols and therefore introduces no new protocol
        insecurities.<a href="#section-6-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="Privacy">
<section id="section-7">
      <h2 id="name-privacy-considerations">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-privacy-considerations" class="section-name selfRef">Privacy Considerations</a>
      </h2>
<p id="section-7-1">Different places have different constraints on individual
 privacy.  The requirements in this memo are intended to
 provide for some limited protections.
 As meetings are announced, the IASA <span class="bcp14">SHALL</span> inform the IETF of
 any limitations to privacy they have become aware of in their
 investigations.  For example, participants would be informed
 of any regulatory authentication or logging requirements.<a href="#section-7-1" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-8">
      <h2 id="name-normative-references">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
      </h2>
<dl class="references">
<dt id="RFC2119">[RFC2119]</dt>
<dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
<dt id="RFC8174">[RFC8174]</dt>
<dd>
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
<dt id="RFC8719">[RFC8719]</dt>
<dd>
<span class="refAuthor">Krishnan, S.</span>, <span class="refTitle">"High-Level Guidance for the Meeting Policy of the IETF"</span>, <span class="seriesInfo">BCP 226</span>, <span class="seriesInfo">RFC 8719</span>, <span class="seriesInfo">DOI 10.17487/RFC8719</span>, <time datetime="2020-02">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8719">https://www.rfc-editor.org/info/rfc8719</a>&gt;</span>. </dd>
</dl>
</section>
<section id="section-9">
      <h2 id="name-informative-references">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
      </h2>
<dl class="references">
<dt id="RFC3935">[RFC3935]</dt>
<dd>
<span class="refAuthor">Alvestrand, H.</span>, <span class="refTitle">"A Mission Statement for the IETF"</span>, <span class="seriesInfo">BCP 95</span>, <span class="seriesInfo">RFC 3935</span>, <span class="seriesInfo">DOI 10.17487/RFC3935</span>, <time datetime="2004-10">October 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3935">https://www.rfc-editor.org/info/rfc3935</a>&gt;</span>. </dd>
<dt id="RFC6771">[RFC6771]</dt>
<dd>
<span class="refAuthor">Eggert, L.</span><span class="refAuthor"> and G. Camarillo</span>, <span class="refTitle">"Considerations for Having a Successful "Bar BOF" Side Meeting"</span>, <span class="seriesInfo">RFC 6771</span>, <span class="seriesInfo">DOI 10.17487/RFC6771</span>, <time datetime="2012-10">October 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6771">https://www.rfc-editor.org/info/rfc6771</a>&gt;</span>. </dd>
<dt id="RFC8711">[RFC8711]</dt>
<dd>
<span class="refAuthor">Haberman, B.</span><span class="refAuthor">, Hall, J.</span><span class="refAuthor">, and J. Livingood</span>, <span class="refTitle">"Structure of the IETF Administrative Support Activity, Version 2.0"</span>, <span class="seriesInfo">BCP 101</span>, <span class="seriesInfo">RFC 8711</span>, <span class="seriesInfo">DOI 10.17487/RFC8711</span>, <time datetime="2020-02">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8711">https://www.rfc-editor.org/info/rfc8711</a>&gt;</span>. </dd>
</dl>
</section>
<div id="Acknowledgements">
<section id="section-appendix.a">
      <h2 id="name-acknowledgements">
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
      </h2>
<p id="section-appendix.a-1">Contributions came from <span class="contact-name">Jari Arkko</span>, <span class="contact-name">Scott Bradner</span>,
        <span class="contact-name">Alissa Cooper</span>, <span class="contact-name">Dave  Crocker</span>, <span class="contact-name">Jordi Palet Martinez</span>, <span class="contact-name">Andrew         Sullivan</span>, and other participants in the MTGVENUE Working
        Group. Those listed in this section or as contributors may or
        may not agree with the content of this memo.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="Contributors">
<section id="section-appendix.b">
      <h2 id="name-contributors">
<a href="#name-contributors" class="section-name selfRef">Contributors</a>
      </h2>
<p id="section-appendix.b-1">The following people provided substantial text contributions
 to this memo. Specifically, Fred Baker originated this work.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Fred Baker</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:fred.ietf@gmail.com" class="email">fred.ietf@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Ray Pelletier</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:Rpelletier13@gmail.com" class="email">Rpelletier13@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Laura Nugent</span></div>
<div dir="auto" class="left"><span class="org">Association Management Solutions</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:lnugent@amsl.com" class="email">lnugent@amsl.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Lou Berger</span></div>
<div dir="auto" class="left"><span class="org">LabN Consulting, L.L.C.</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:lberger@labn.net" class="email">lberger@labn.net</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Ole Jacobsen</span></div>
<div dir="auto" class="left"><span class="org">The Internet Protocol Journal</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:olejacobsen@me.com" class="email">olejacobsen@me.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Jim Martin</span></div>
<div dir="auto" class="left"><span class="org">INOC</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:jim@inoc.com" class="email">jim@inoc.com</a>
</div>
</address>
</section>
</div>
<div id="authors-addresses">
<section id="section-appendix.c">
      <h2 id="name-authors-address">
<a href="#name-authors-address" class="section-name selfRef">Author's Address</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Eliot Lear (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
<div dir="auto" class="left"><span class="street-address">Richtistrasse 7</span></div>
<div dir="auto" class="left">
<span class="postal-code">CH-8304</span> <span class="locality">Wallisellen</span>
</div>
<div dir="auto" class="left"><span class="country-name">Switzerland</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+41%2044%20878%209200" class="tel">+41 44 878 9200</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:lear@cisco.com" class="email">lear@cisco.com</a>
</div>
</address>
</section>
</div>
<script>var toc = document.getElementById("toc");
var tocToggle = toc.querySelector("h2");
var tocNav = toc.querySelector("nav");

// mobile menu toggle
tocToggle.onclick = function(event) {
    if (window.innerWidth < 1024) {
 var tocNavDisplay = tocNav.currentStyle ? tocNav.currentStyle.display : getComputedStyle(tocNav, null).display;
 if (tocNavDisplay == "none") {
     tocNav.style.display = "block";
 } else {
     tocNav.style.display = "none";
 }
    }
}

// toc anchor scroll to anchor
tocNav.addEventListener("click", function (event) {
    event.preventDefault();
    if (event.target.nodeName == 'A') {
 if (window.innerWidth < 1024) {
     tocNav.style.display = "none";
 }
 var href = event.target.getAttribute("href");
 var anchorId = href.substr(1);
 var anchor =  document.getElementById(anchorId);
 anchor.scrollIntoView(true);
 window.history.pushState("","",href);
    }
});

// switch toc mode when window resized
window.onresize = function () {
    if (window.innerWidth < 1024) {
 tocNav.style.display = "none";
    } else {
 tocNav.style.display = "block";
    }
}
</script>
</body>
</html>