File: rfc8713.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: bookworm, forky, sid, trixie
size: 1,609,944 kB
file content (3731 lines) | stat: -rw-r--r-- 175,357 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 8713: IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees</title>
<meta content="Murray S. Kucherawy" name="author">
<meta content="Robert M. Hinden" name="author">
<meta content="Jason Livingood" name="author">
<meta content="
       The process by which the members of the IAB and IESG, some
 Trustees of the IETF Trust, and some Directors of the IETF
 Administration LLC (IETF LLC)
 are selected, confirmed, and recalled is specified in this
 document.  
        This document is based on RFC 7437.  Only
 those updates required to reflect the changes introduced
 by IETF Administrative Support Activity (IASA) 2.0 have been included.
        Any other changes will be addressed in future documents. 
       This document obsoletes RFC 7437 and RFC 8318. 
    " name="description">
<meta content="xml2rfc 2.40.0" name="generator">
<meta content="IASA" name="keyword">
<meta content="IASA 2.0" name="keyword">
<meta content="IASA2" name="keyword">
<meta content="8713" name="rfc.number">
<link href="rfc8713.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/rfc8713" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc7437bis-09" 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 8713</td>
<td class="center">NomCom</td>
<td class="right">February 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Kucherawy, et al.</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/rfc8713" class="eref">8713</a></dd>
<dt class="label-bcp">BCP:</dt>
<dd class="bcp">10</dd>
<dt class="label-obsoletes">Obsoletes:</dt>
<dd class="obsoletes">
<a href="https://www.rfc-editor.org/rfc/rfc7437" class="eref">7437</a>, <a href="https://www.rfc-editor.org/rfc/rfc8318" class="eref">8318</a> </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">Authors:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">M. Kucherawy, <span class="editor">Ed.</span>
</div>
</div>
<div class="author">
      <div class="author-name">R. Hinden, <span class="editor">Ed.</span>
</div>
<div class="org">Check Point Software</div>
</div>
<div class="author">
      <div class="author-name">J. Livingood, <span class="editor">Ed.</span>
</div>
<div class="org">Comcast</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8713</h1>
<h1 id="title">IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">The process by which the members of the IAB and IESG, some
 Trustees of the IETF Trust, and some Directors of the IETF
 Administration LLC (IETF LLC)
 are selected, confirmed, and recalled is specified in this
 document.  
        This document is based on RFC 7437.  Only
 those updates required to reflect the changes introduced
 by IETF Administrative Support Activity (IASA) 2.0 have been included.
        Any other changes will be addressed in future documents.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
<p id="section-abstract-2">This document obsoletes RFC 7437 and RFC 8318.<a href="#section-abstract-2" 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/rfc8713">https://www.rfc-editor.org/info/rfc8713</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-definitions" class="xref">Definitions</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
</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-general" class="xref">General</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-completion-due" class="xref">Completion Due</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-nominating-committee-princi" class="xref">Nominating Committee Principal Functions</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-positions-to-be-reviewed" class="xref">Positions to Be Reviewed</a><a href="#section-toc.1-1.3.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.4">
                <p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-term-lengths" class="xref">Term Lengths</a><a href="#section-toc.1-1.3.2.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.5">
                <p id="section-toc.1-1.3.2.5.1"><a href="#section-3.5" class="xref">3.5</a>.  <a href="#name-mid-term-vacancies" class="xref">Mid-term Vacancies</a><a href="#section-toc.1-1.3.2.5.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.6">
                <p id="section-toc.1-1.3.2.6.1"><a href="#section-3.6" class="xref">3.6</a>.  <a href="#name-confidentiality" class="xref">Confidentiality</a><a href="#section-toc.1-1.3.2.6.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.7">
                <p id="section-toc.1-1.3.2.7.1"><a href="#section-3.7" class="xref">3.7</a>.  <a href="#name-advice-and-consent-model" class="xref">Advice and Consent Model</a><a href="#section-toc.1-1.3.2.7.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.3.2.7.2.1">
                    <p id="section-toc.1-1.3.2.7.2.1.1"><a href="#section-3.7.1" class="xref">3.7.1</a>.  <a href="#name-positions-to-be-reviewed-2" class="xref">Positions to Be Reviewed</a><a href="#section-toc.1-1.3.2.7.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.7.2.2">
                    <p id="section-toc.1-1.3.2.7.2.2.1"><a href="#section-3.7.2" class="xref">3.7.2</a>.  <a href="#name-candidate-selection" class="xref">Candidate Selection</a><a href="#section-toc.1-1.3.2.7.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.7.2.3">
                    <p id="section-toc.1-1.3.2.7.2.3.1"><a href="#section-3.7.3" class="xref">3.7.3</a>.  <a href="#name-candidate-review" class="xref">Candidate Review</a><a href="#section-toc.1-1.3.2.7.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.7.2.4">
                    <p id="section-toc.1-1.3.2.7.2.4.1"><a href="#section-3.7.4" class="xref">3.7.4</a>.  <a href="#name-confirmation" class="xref">Confirmation</a><a href="#section-toc.1-1.3.2.7.2.4.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.8">
                <p id="section-toc.1-1.3.2.8.1"><a href="#section-3.8" class="xref">3.8</a>.  <a href="#name-sitting-members-directors-a" class="xref">Sitting Members, Directors, and Trustees</a><a href="#section-toc.1-1.3.2.8.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.9">
                <p id="section-toc.1-1.3.2.9.1"><a href="#section-3.9" class="xref">3.9</a>.  <a href="#name-announcements" class="xref">Announcements</a><a href="#section-toc.1-1.3.2.9.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-nominating-committee-select" class="xref">Nominating Committee Selection</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.4.2.1">
                <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-timeline" class="xref">Timeline</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.2">
                <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-term" class="xref">Term</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.3">
                <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-structure" class="xref">Structure</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.4">
                <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-chair-duties" class="xref">Chair Duties</a><a href="#section-toc.1-1.4.2.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.5">
                <p id="section-toc.1-1.4.2.5.1"><a href="#section-4.5" class="xref">4.5</a>.  <a href="#name-chair-selection" class="xref">Chair Selection</a><a href="#section-toc.1-1.4.2.5.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.6">
                <p id="section-toc.1-1.4.2.6.1"><a href="#section-4.6" class="xref">4.6</a>.  <a href="#name-temporary-chair" class="xref">Temporary Chair</a><a href="#section-toc.1-1.4.2.6.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.7">
                <p id="section-toc.1-1.4.2.7.1"><a href="#section-4.7" class="xref">4.7</a>.  <a href="#name-liaisons" class="xref">Liaisons</a><a href="#section-toc.1-1.4.2.7.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.8">
                <p id="section-toc.1-1.4.2.8.1"><a href="#section-4.8" class="xref">4.8</a>.  <a href="#name-liaison-appointment" class="xref">Liaison Appointment</a><a href="#section-toc.1-1.4.2.8.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.9">
                <p id="section-toc.1-1.4.2.9.1"><a href="#section-4.9" class="xref">4.9</a>.  <a href="#name-advisors" class="xref">Advisors</a><a href="#section-toc.1-1.4.2.9.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.10">
                <p id="section-toc.1-1.4.2.10.1"><a href="#section-4.10" class="xref">4.10</a>. <a href="#name-past-chair" class="xref">Past Chair</a><a href="#section-toc.1-1.4.2.10.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.11">
                <p id="section-toc.1-1.4.2.11.1"><a href="#section-4.11" class="xref">4.11</a>. <a href="#name-voting-volunteers" class="xref">Voting Volunteers</a><a href="#section-toc.1-1.4.2.11.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.12">
                <p id="section-toc.1-1.4.2.12.1"><a href="#section-4.12" class="xref">4.12</a>. <a href="#name-milestones" class="xref">Milestones</a><a href="#section-toc.1-1.4.2.12.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.13">
                <p id="section-toc.1-1.4.2.13.1"><a href="#section-4.13" class="xref">4.13</a>. <a href="#name-open-positions" class="xref">Open Positions</a><a href="#section-toc.1-1.4.2.13.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.14">
                <p id="section-toc.1-1.4.2.14.1"><a href="#section-4.14" class="xref">4.14</a>. <a href="#name-volunteer-qualification" class="xref">Volunteer Qualification</a><a href="#section-toc.1-1.4.2.14.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.15">
                <p id="section-toc.1-1.4.2.15.1"><a href="#section-4.15" class="xref">4.15</a>. <a href="#name-not-qualified" class="xref">Not Qualified</a><a href="#section-toc.1-1.4.2.15.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.16">
                <p id="section-toc.1-1.4.2.16.1"><a href="#section-4.16" class="xref">4.16</a>. <a href="#name-selection-process" class="xref">Selection Process</a><a href="#section-toc.1-1.4.2.16.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.17">
                <p id="section-toc.1-1.4.2.17.1"><a href="#section-4.17" class="xref">4.17</a>. <a href="#name-announcement-of-selection-r" class="xref">Announcement of Selection Results</a><a href="#section-toc.1-1.4.2.17.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4.2.18">
                <p id="section-toc.1-1.4.2.18.1"><a href="#section-4.18" class="xref">4.18</a>. <a href="#name-committee-organization" class="xref">Committee Organization</a><a href="#section-toc.1-1.4.2.18.1" class="pilcrow">¶</a></p>
</li>
</ul>
</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-nominating-committee-operat" class="xref">Nominating Committee Operation</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.5.2.1">
                <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-discretion" class="xref">Discretion</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.2">
                <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-selection-timeline" class="xref">Selection Timeline</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.3">
                <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-confirmation-timeline" class="xref">Confirmation Timeline</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.4">
                <p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-milestones-2" class="xref">Milestones</a><a href="#section-toc.1-1.5.2.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.5">
                <p id="section-toc.1-1.5.2.5.1"><a href="#section-5.5" class="xref">5.5</a>.  <a href="#name-voting-mechanism" class="xref">Voting Mechanism</a><a href="#section-toc.1-1.5.2.5.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.6">
                <p id="section-toc.1-1.5.2.6.1"><a href="#section-5.6" class="xref">5.6</a>.  <a href="#name-voting-quorum" class="xref">Voting Quorum</a><a href="#section-toc.1-1.5.2.6.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.7">
                <p id="section-toc.1-1.5.2.7.1"><a href="#section-5.7" class="xref">5.7</a>.  <a href="#name-voting-member-recall" class="xref">Voting Member Recall</a><a href="#section-toc.1-1.5.2.7.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.8">
                <p id="section-toc.1-1.5.2.8.1"><a href="#section-5.8" class="xref">5.8</a>.  <a href="#name-chair-recall" class="xref">Chair Recall</a><a href="#section-toc.1-1.5.2.8.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.9">
                <p id="section-toc.1-1.5.2.9.1"><a href="#section-5.9" class="xref">5.9</a>.  <a href="#name-deliberations" class="xref">Deliberations</a><a href="#section-toc.1-1.5.2.9.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.10">
                <p id="section-toc.1-1.5.2.10.1"><a href="#section-5.10" class="xref">5.10</a>. <a href="#name-call-for-nominees" class="xref">Call for Nominees</a><a href="#section-toc.1-1.5.2.10.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.11">
                <p id="section-toc.1-1.5.2.11.1"><a href="#section-5.11" class="xref">5.11</a>. <a href="#name-nominations" class="xref">Nominations</a><a href="#section-toc.1-1.5.2.11.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.12">
                <p id="section-toc.1-1.5.2.12.1"><a href="#section-5.12" class="xref">5.12</a>. <a href="#name-candidate-selection-2" class="xref">Candidate Selection</a><a href="#section-toc.1-1.5.2.12.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.13">
                <p id="section-toc.1-1.5.2.13.1"><a href="#section-5.13" class="xref">5.13</a>. <a href="#name-consent-to-nomination" class="xref">Consent to Nomination</a><a href="#section-toc.1-1.5.2.13.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.14">
                <p id="section-toc.1-1.5.2.14.1"><a href="#section-5.14" class="xref">5.14</a>. <a href="#name-notifying-confirming-bodies" class="xref">Notifying Confirming Bodies</a><a href="#section-toc.1-1.5.2.14.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.15">
                <p id="section-toc.1-1.5.2.15.1"><a href="#section-5.15" class="xref">5.15</a>. <a href="#name-confirming-candidates" class="xref">Confirming Candidates</a><a href="#section-toc.1-1.5.2.15.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.16">
                <p id="section-toc.1-1.5.2.16.1"><a href="#section-5.16" class="xref">5.16</a>. <a href="#name-archives" class="xref">Archives</a><a href="#section-toc.1-1.5.2.16.1" class="pilcrow">¶</a></p>
</li>
</ul>
</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-dispute-resolution-process" class="xref">Dispute Resolution Process</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-member-trustee-and-director" class="xref">Member, Trustee, and Director Recall</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.7.2.1">
                <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-petition" class="xref">Petition</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.7.2.1.2.1">
                    <p id="section-toc.1-1.7.2.1.2.1.1"><a href="#section-7.1.1" class="xref">7.1.1</a>.  <a href="#name-community-petition" class="xref">Community Petition</a><a href="#section-toc.1-1.7.2.1.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7.2.1.2.2">
                    <p id="section-toc.1-1.7.2.1.2.2.1"><a href="#section-7.1.2" class="xref">7.1.2</a>.  <a href="#name-ombudsteam-petition" class="xref">Ombudsteam Petition</a><a href="#section-toc.1-1.7.2.1.2.2.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7.2.2">
                <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-recall-committee-chair" class="xref">Recall Committee Chair</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7.2.3">
                <p id="section-toc.1-1.7.2.3.1"><a href="#section-7.3" class="xref">7.3</a>.  <a href="#name-recall-committee-creation" class="xref">Recall Committee Creation</a><a href="#section-toc.1-1.7.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7.2.4">
                <p id="section-toc.1-1.7.2.4.1"><a href="#section-7.4" class="xref">7.4</a>.  <a href="#name-recall-committee-rules" class="xref">Recall Committee Rules</a><a href="#section-toc.1-1.7.2.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7.2.5">
                <p id="section-toc.1-1.7.2.5.1"><a href="#section-7.5" class="xref">7.5</a>.  <a href="#name-recall-committee-operation" class="xref">Recall Committee Operation</a><a href="#section-toc.1-1.7.2.5.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7.2.6">
                <p id="section-toc.1-1.7.2.6.1"><a href="#section-7.6" class="xref">7.6</a>.  <a href="#name-3-4-majority" class="xref">3/4 Majority</a><a href="#section-toc.1-1.7.2.6.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7.2.7">
                <p id="section-toc.1-1.7.2.7.1"><a href="#section-7.7" class="xref">7.7</a>.  <a href="#name-position-to-be-filled" class="xref">Position to Be Filled</a><a href="#section-toc.1-1.7.2.7.1" class="pilcrow">¶</a></p>
</li>
</ul>
</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-iana-considerations" class="xref">IANA Considerations</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-security-considerations" class="xref">Security Considerations</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-10" class="xref">10</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.10.2.1">
                <p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.10.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.10.2.2">
                <p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.10.2.2.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-appendix.a" class="xref">Appendix A</a>.  <a href="#name-changes-since-rfc-3777" class="xref">Changes Since RFC 3777</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.b" class="xref">Appendix B</a>.  <a href="#name-changes-since-rfc-7437" class="xref">Changes Since RFC 7437</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.13">
            <p id="section-toc.1-1.13.1"><a href="#section-appendix.c" class="xref">Appendix C</a>.  <a href="#name-oral-tradition" class="xref">Oral Tradition</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.14">
            <p id="section-toc.1-1.14.1"><a href="#section-appendix.d" class="xref">Appendix D</a>.  <a href="#name-nominating-committee-timeli" class="xref">Nominating Committee Timeline</a><a href="#section-toc.1-1.14.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.15">
            <p id="section-toc.1-1.15.1"><a href="#section-appendix.e" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a><a href="#section-toc.1-1.15.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.16">
            <p id="section-toc.1-1.16.1"><a href="#section-appendix.f" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.16.1" class="pilcrow">¶</a></p>
</li>
</ul>
</nav>
</section>
</div>
<div id="intro">
<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"> This document is a revision of <span>[<a href="#RFC7437" class="xref">RFC7437</a>]</span> that
 updates it to be consistent with the 
        IETF Administrative Support Activity (IASA) 2.0 changes.  RFC 7437
 was based on <span>[<a href="#RFC3777" class="xref">RFC3777</a>]</span> that consolidated and updated
 other RFCs that updated that document into a single
 specification.  The result is a complete specification of the
 process by which members of the Internet Architecture Board (IAB)
 and Internet Engineering Steering Group (IESG), some Trustees of
 the IETF Trust, and some Directors of the IETF Administration LLC
 (IETF LLC), are selected, confirmed, and recalled.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">This revision addresses only the changes required for IASA
 2.0; should the community agree on other changes, they will be
 addressed in future documents.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3"><span><a href="https://www.rfc-editor.org/rfc/rfc8714#section-2" class="relref">Section 2</a> of [<a href="#RFC8714" class="xref">RFC8714</a>]</span>
 provides further details about the IETF Trust Trustees
 positions that are filled by the IETF Nominating Committee
 (NomCom).<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4"><span><a href="https://www.rfc-editor.org/rfc/rfc8711#section-5" class="relref">Section 5</a> of [<a href="#RFC8711" class="xref">RFC8711</a>]</span>
 provides further details about the IETF LLC Director
 positions that are filled by the NomCom.<a href="#section-1-4" class="pilcrow">¶</a></p>
<p id="section-1-5">The following two assumptions continue to be true of this specification:<a href="#section-1-5" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-1-6">
        <li id="section-1-6.1"> The Internet Research Task Force (IRTF) and
     Internet Research Steering Group (IRSG) are not a
     part of the process described here.<a href="#section-1-6.1" class="pilcrow">¶</a>
</li>
<li id="section-1-6.2"> The organization (and reorganization) of the IESG
     is not a part of the process described here.<a href="#section-1-6.2" class="pilcrow">¶</a>
</li>
</ol>
<p id="section-1-7"> The time frames specified here use IETF meetings as
     a frame of reference.  The time frames assume that the
     IETF meets three times per calendar year with
     approximately equal amounts of time between them.  The
     meetings are referred to as the First IETF, Second IETF,
     or Third IETF as needed.<a href="#section-1-7" class="pilcrow">¶</a></p>
<p id="section-1-8"> The next section lists the words and phrases commonly used
     throughout this document with their intended meaning.<a href="#section-1-8" class="pilcrow">¶</a></p>
<p id="section-1-9"> The majority of this document is divided into four major
     topics as follows:<a href="#section-1-9" class="pilcrow">¶</a></p>
<dl class="dlParallel" id="section-1-10">
        <dt id="section-1-10.1">General:</dt>
<dd id="section-1-10.2"> This is a set of rules and
 constraints that apply to the selection and
 confirmation process as a whole.<a href="#section-1-10.2" class="pilcrow">¶</a>
</dd>
<dt id="section-1-10.3">Nominating Committee Selection:</dt>
<dd id="section-1-10.4"> This
 is the process by which the volunteers who
 will serve on the NomCom are
 selected.<a href="#section-1-10.4" class="pilcrow">¶</a>
</dd>
<dt id="section-1-10.5">Nominating Committee Operation:</dt>
<dd id="section-1-10.6"> This
 is the set of principles, rules, and
 constraints that guide the activities of
 the NomCom, including the
 confirmation process.<a href="#section-1-10.6" class="pilcrow">¶</a>
</dd>
<dt id="section-1-10.7">Member, Trustee, and Director Recall:</dt>
<dd id="section-1-10.8"> This is the process by
 which the behavior of a sitting member of the
 IESG, or IAB, or IETF Trust Trustee, or IETF
 LLC Director may be questioned, perhaps
 resulting in the removal of the sitting
 member. See <a href="#defs" class="xref">Section 2</a> for a description of 
 what a sitting member means for each of these groups.<a href="#section-1-10.8" class="pilcrow">¶</a>
</dd>
</dl>
<p id="section-1-11"> A final section describes how this document differs from <span>[<a href="#RFC3777" class="xref">RFC3777</a>]</span> 
 and <span>[<a href="#RFC7437" class="xref">RFC7437</a>]</span>.<a href="#section-1-11" class="pilcrow">¶</a></p>
<p id="section-1-12"> An appendix of useful facts and practices collected from
 previous NomComs is also included.<a href="#section-1-12" class="pilcrow">¶</a></p>
<p id="section-1-13">
       This document updates the IAB, IESG, and IAOC Selection, Confirmation, and Recall Process
       to be
       aligned with IASA 2.0 Model <span>[<a href="#RFC8711" class="xref">RFC8711</a>]</span>
      that creates an IETF Administration Limited Liability Company
      (IETF LLC) managed by a Board of Directors (IETF LLC Board).  
 
     This document obsoletes <span>[<a href="#RFC7437" class="xref">RFC7437</a>]</span> and <span>[<a href="#RFC8318" class="xref">RFC8318</a>]</span>.<a href="#section-1-13" class="pilcrow">¶</a></p>
</section>
</div>
<div id="defs">
<section id="section-2">
      <h2 id="name-definitions">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-definitions" class="section-name selfRef">Definitions</a>
      </h2>
<p id="section-2-1"> The following words and phrases are commonly used
     throughout this document.  They are listed here with
     their intended meaning for the convenience of the
     reader.<a href="#section-2-1" class="pilcrow">¶</a></p>
<dl class="dlParallel" id="section-2-2">
        <dt id="section-2-2.1">Candidate:</dt>
<dd id="section-2-2.2"> A nominee who has been
 selected to be considered for confirmation by
 a confirming body.<a href="#section-2-2.2" class="pilcrow">¶</a>
</dd>
<dt id="section-2-2.3">Confirmed Candidate:</dt>
<dd id="section-2-2.4"> A candidate that
 has been reviewed and approved by a
 confirming body.<a href="#section-2-2.4" class="pilcrow">¶</a>
</dd>
<dt id="section-2-2.5">Nominating Committee Term:</dt>
<dd id="section-2-2.6"> The term
 begins when its members are officially
 announced, which is expected to be prior to
 the Third IETF to ensure it is fully
 operational at the Third IETF.  The term ends
 at the Third IETF (not three meetings) after
 the next NomCom's term
 begins.<a href="#section-2-2.6" class="pilcrow">¶</a>
</dd>
<dt id="section-2-2.7">IETF Executive Director:</dt>
<dd id="section-2-2.8"> The person
 charged with day-to-day operation of the IETF's
 administrative functions.  (See 
 <span><a href="https://www.rfc-editor.org/rfc/rfc8711#section-4.1" class="relref">Section 4.1</a> of [<a href="#RFC8711" class="xref">RFC8711</a>]</span>).
         Note:  This was previously the name of
 the IETF Secretariat position that is
 now called the "Managing Director, IETF
 Secretariat".<a href="#section-2-2.8" class="pilcrow">¶</a>
</dd>
<dt id="section-2-2.9">Managing Director, IETF Secretariat:</dt>
<dd id="section-2-2.10">
         The person charged with
         operation of the IETF Secretariat function.  (See
         <span><a href="https://www.rfc-editor.org/rfc/rfc3710#section-2" class="relref">Section 2</a> of [<a href="#RFC3710" class="xref">RFC3710</a>]</span> and
         <span>[<a href="#RFC8717" class="xref">RFC8717</a>]</span>).<a href="#section-2-2.10" class="pilcrow">¶</a>
</dd>
<dt id="section-2-2.11">Nominee:</dt>
<dd id="section-2-2.12"> A person who is being or
 has been considered for one or more open
 positions of the IESG, IAB, IETF Trust Trustee, or
 IETF LLC.<a href="#section-2-2.12" class="pilcrow">¶</a>
</dd>
<dt id="section-2-2.13">Sitting Member:</dt>
<dd id="section-2-2.14"> A person who is
 currently serving as a member of the IESG or IAB.<a href="#section-2-2.14" class="pilcrow">¶</a>
</dd>
<dt id="section-2-2.15">Sitting Director:</dt>
<dd id="section-2-2.16"> A person who is
 currently serving as a Director of the
 IETF LLC.<a href="#section-2-2.16" class="pilcrow">¶</a>
</dd>
<dt id="section-2-2.17">Sitting IETF Trust Trustee:</dt>
<dd id="section-2-2.18"> A person who is
 currently serving as a Trustee of the IETF
 Trust.<a href="#section-2-2.18" class="pilcrow">¶</a>
</dd>
</dl>
</section>
</div>
<div id="general">
<section id="section-3">
      <h2 id="name-general">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-general" class="section-name selfRef">General</a>
      </h2>
<p id="section-3-1"> The following set of rules apply to the process as a
     whole.  If necessary, a paragraph discussing the
     interpretation of each rule is included.<a href="#section-3-1" class="pilcrow">¶</a></p>
<div id="gen_completion">
<section id="section-3.1">
        <h3 id="name-completion-due">
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-completion-due" class="section-name selfRef">Completion Due</a>
        </h3>
<p id="section-3.1-1"> The completion of the annual process is due
     within seven months.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
<p id="section-3.1-2"> The completion of the annual process is due
     one month prior to the Friday of the week
     before the First IETF.  It is expected to begin
     at least eight months prior to the Friday of the
     week before the First IETF.<a href="#section-3.1-2" class="pilcrow">¶</a></p>
<p id="section-3.1-3"> The process officially begins with the
     announcement of the Chair of the committee.
     The process officially ends when all confirmed
     candidates have been announced.<a href="#section-3.1-3" class="pilcrow">¶</a></p>
<p id="section-3.1-4"> The annual process is comprised of three major
     components as follows:<a href="#section-3.1-4" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-3.1-5">
          <li id="section-3.1-5.1"> The selection and organization of the
     NomCom members.<a href="#section-3.1-5.1" class="pilcrow">¶</a>
</li>
<li id="section-3.1-5.2"> The selection of candidates by the
     NomCom.<a href="#section-3.1-5.2" class="pilcrow">¶</a>
</li>
<li id="section-3.1-5.3"> The confirmation of the candidates.<a href="#section-3.1-5.3" class="pilcrow">¶</a>
</li>
</ol>
<p id="section-3.1-6"> There is an additional month set aside between
     when the annual process is expected to end and
     the term of the new candidates is to begin.  This
     time may be used during unusual circumstances to
     extend the time allocated for any of the
     components listed above.<a href="#section-3.1-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_func">
<section id="section-3.2">
        <h3 id="name-nominating-committee-princi">
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-nominating-committee-princi" class="section-name selfRef">Nominating Committee Principal Functions</a>
        </h3>
<p id="section-3.2-1"> The principal functions of the NomCom are to
 review each open IESG, IAB, IETF Trust, and IETF LLC Director position
 and to select either its incumbent or a
 superior candidate.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
<p id="section-3.2-2">Although there is no term limit for serving in any IESG, IAB, or IETF
                           Trust position, the NomCom may use length of service as
                           one of its criteria for evaluating an incumbent.<a href="#section-3.2-2" class="pilcrow">¶</a></p>
<p id="section-3.2-3"> The NomCom does not select the
     open positions to be reviewed; it is instructed
     as to which positions to review.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
<p id="section-3.2-4"> The NomCom will be given the titles
     of the positions to be reviewed and a brief
     summary of the desired expertise of the candidate
     that is selected to fill each position.<a href="#section-3.2-4" class="pilcrow">¶</a></p>
<p id="section-3.2-5"> Incumbents must notify the NomCom
     if they wish to be nominated.<a href="#section-3.2-5" class="pilcrow">¶</a></p>
<p id="section-3.2-6"> The NomCom does not confirm its
     candidates; it presents its candidates to the
     appropriate confirming body as indicated
     below.<a href="#section-3.2-6" class="pilcrow">¶</a></p>
<p id="section-3.2-7"> A superior candidate is one who the
     NomCom believes would contribute in such a
     way as to improve or enhance the body to which
     he or she is nominated.<a href="#section-3.2-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_positions">
<section id="section-3.3">
        <h3 id="name-positions-to-be-reviewed">
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-positions-to-be-reviewed" class="section-name selfRef">Positions to Be Reviewed</a>
        </h3>
<p id="section-3.3-1">Approximately one-half of each of the then
         current IESG and IAB positions, one IETF Trust
         position, and one IETF LLC Director position, is selected
         to be reviewed each year.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
<p id="section-3.3-2"> The intent of this rule is to ensure the
 review of approximately one-half of each of the
 IESG and IAB sitting members, one of the three
 NomCom-nominated IETF LLC Director
 positions, and one of the three nominated IETF Trust
 Trustee positions, each year.  It is recognized
 that circumstances may exist that will require
 the NomCom to review more or less
 than the usual number of positions, e.g., if the
 IESG, IAB, IETF Trust, or IETF LLC Board have reorganized prior to
 this process and created new positions, if there
 are an odd number of current positions, or if a
 member, a Director, or a Trustee unexpectedly resigns.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_terms">
<section id="section-3.4">
        <h3 id="name-term-lengths">
<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-term-lengths" class="section-name selfRef">Term Lengths</a>
        </h3>
<p id="section-3.4-1"> Confirmed IESG and IAB candidates are
 expected to serve at least a two-year term. The
 intent of this rule is to ensure that members of
 the IESG and IAB serve the number of years that
 best facilitates the review of one-half of the
 members each year.<a href="#section-3.4-1" class="pilcrow">¶</a></p>
<p id="section-3.4-2"> Confirmed IETF LLC Director candidates
 are expected to serve at least a three-year term,
 except if a nominating or selection body decides
 to use a shorter term to allow for initial
 staggered appointments. Please refer to 
 <span><a href="https://www.rfc-editor.org/rfc/rfc8711#section-6" class="relref">Section 6</a> of [<a href="#RFC8711" class="xref">RFC8711</a>]</span> for
 additional guidance on term length and term
 limits for the IETF LLC Board.<a href="#section-3.4-2" class="pilcrow">¶</a></p>
<p id="section-3.4-3">Confirmed IETF Trust Trustee candidates are expected to
 serve at least a three-year term, except if a
 nominating or selection body decides to use a
 shorter term to allow for initial staggered
 appointments. Please refer to 
                        <span><a href="https://www.rfc-editor.org/rfc/rfc8714#section-2" class="relref">Section 2</a> of [<a href="#RFC8714" class="xref">RFC8714</a>]</span> 
                        for additional
 guidance on term length and term limits for the
 IETF Trust.<a href="#section-3.4-3" class="pilcrow">¶</a></p>
<p id="section-3.4-4"> The term of a confirmed candidate selected
 according to the mid-term vacancy rules may be
 less than a full term (two years for IESG and
 IAB, three years for the IETF Trust and IETF
 LLC), as stated elsewhere in this document.<a href="#section-3.4-4" class="pilcrow">¶</a></p>
<p id="section-3.4-5"> It is consistent with this rule for the NomCom
     to choose one or more of the currently
     open positions to which it may assign a term of
     not more than three years in order to ensure the
     ideal application of this rule in the future.<a href="#section-3.4-5" class="pilcrow">¶</a></p>
<p id="section-3.4-6"> It is consistent with this rule for the
 NomCom to choose one or more of the
 currently open positions that share
 responsibilities with other positions (both those
 being reviewed and those sitting) to which it may
 assign a term of not more than three years to
 ensure that all such members, Directors, or Trustees will
 not be reviewed at the same time.<a href="#section-3.4-6" class="pilcrow">¶</a></p>
<p id="section-3.4-7"> All sitting member terms end during the First IETF
     meeting corresponding to the end of the term for
     which they were confirmed.  All confirmed
     candidate terms begin during the First IETF
     meeting corresponding to the beginning of the term
     for which they were confirmed.<a href="#section-3.4-7" class="pilcrow">¶</a></p>
<p id="section-3.4-8"> For confirmed candidates of the IESG, the terms
     begin no later than when the currently sitting
     members' terms end on the last day of the meeting.
     A term may begin or end no sooner than the first
     day of the meeting and no later than the last day
     of the meeting as determined by the mutual
     agreement of the currently sitting member and the 
     confirmed candidate.  A confirmed candidate's term
     may overlap the sitting member's term during the
     meeting as determined by their mutual
     agreement.<a href="#section-3.4-8" class="pilcrow">¶</a></p>
<p id="section-3.4-9"> For confirmed candidates of the IAB, the
     terms overlap with the terms of the sitting
     members for the entire week of the meeting.<a href="#section-3.4-9" class="pilcrow">¶</a></p>
<p id="section-3.4-10"> For confirmed Trustee candidates of the IETF
 Trust, the term begins at the next IETF Trust
 meeting or as dictated by the policies and
 procedures of the IETF Trust.<a href="#section-3.4-10" class="pilcrow">¶</a></p>
<p id="section-3.4-11"> For confirmed Director candidates of the IETF
 LLC, the term begins at the next appropriate IETF
 LLC Board meeting or as dictated by the policies
 and procedures of the IETF LLC Board.<a href="#section-3.4-11" class="pilcrow">¶</a></p>
<p id="section-3.4-12"> For candidates confirmed under the mid-term
     vacancy rules, the term begins as soon as possible
     after the confirmation.<a href="#section-3.4-12" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_vacancies">
<section id="section-3.5">
        <h3 id="name-mid-term-vacancies">
<a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-mid-term-vacancies" class="section-name selfRef">Mid-term Vacancies</a>
        </h3>
<p id="section-3.5-1"> Mid-term vacancies are filled by the same rules
     as documented here with four qualifications,
     namely:<a href="#section-3.5-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-3.5-2">
          <li id="section-3.5-2.1"> When there is only one official NomCom,
     the body with the mid-term
     vacancy relegates the responsibility to
     fill the vacancy to it.  If the mid-term
     vacancy occurs during the period of time
     that the term of the prior year's
     NomCom overlaps with the
     term of the current year's
     NomCom, the body with the mid-term
     vacancy must relegate the responsibility
     to fill the vacancy to the prior year's
     NomCom.<a href="#section-3.5-2.1" class="pilcrow">¶</a>
</li>
<li id="section-3.5-2.2"> If it is the case that the NomCom
     is reconvening to fill the
     mid-term vacancy, then the completion of
     the candidate selection and confirmation
     process is due within six weeks, with all
     other time periods otherwise unspecified
     prorated accordingly.<a href="#section-3.5-2.2" class="pilcrow">¶</a>
</li>
<li id="section-3.5-2.3"> The confirming body has two weeks from the
     day it is notified of a candidate to
     reject the candidate, otherwise the
     candidate is assumed to have been
     confirmed.<a href="#section-3.5-2.3" class="pilcrow">¶</a>
</li>
<li id="section-3.5-2.4">
            <p id="section-3.5-2.4.1"> The term of the confirmed candidate will
     be either:<a href="#section-3.5-2.4.1" class="pilcrow">¶</a></p>
<ol start="1" type="A" class="normal type-A" id="section-3.5-2.4.2">
              <li id="section-3.5-2.4.2.1"> the remainder of the term of the
     open position if that remainder
     is not less than one year or<a href="#section-3.5-2.4.2.1" class="pilcrow">¶</a>
</li>
<li id="section-3.5-2.4.2.2"> the remainder of the term of the open
 position plus the next two-year term for
 IESG and IAB positions or three-year term
 for IETF LLC Director and IETF Trust
 positions if that remainder is less than
 one year.<a href="#section-3.5-2.4.2.2" class="pilcrow">¶</a>
</li>
</ol>
</li>
</ol>
<p id="section-3.5-3"> In both cases, a year is the period of time from a
     First IETF meeting to the next First IETF
     meeting.<a href="#section-3.5-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_confidential">
<section id="section-3.6">
        <h3 id="name-confidentiality">
<a href="#section-3.6" class="section-number selfRef">3.6. </a><a href="#name-confidentiality" class="section-name selfRef">Confidentiality</a>
        </h3>
<p id="section-3.6-1"> All deliberations and supporting information that
     relate to specific nominees, candidates, and
     confirmed candidates are confidential.<a href="#section-3.6-1" class="pilcrow">¶</a></p>
<p id="section-3.6-2"> The NomCom and confirming body
     members will be exposed to confidential
     information as a result of their deliberations,
     their interactions with those they consult, and
     from those who provide requested supporting
     information.  All members and all other
     participants are expected to handle this
     information in a manner consistent with its
     sensitivity.<a href="#section-3.6-2" class="pilcrow">¶</a></p>
<p id="section-3.6-3"> It is consistent with this rule for current
     NomCom members who have served on
     prior NomComs to advise the current
     committee on deliberations and results of the
     prior committee, as necessary and appropriate.<a href="#section-3.6-3" class="pilcrow">¶</a></p>
<p id="section-3.6-4"> The list of nominees willing to be considered for
     positions under review in the current NomCom
     cycle is not confidential.  The NomCom
     may disclose a list of names of nominees
     who are willing to be considered for positions under
     review to the community, in order to obtain feedback
     from the community on these nominees.<a href="#section-3.6-4" class="pilcrow">¶</a></p>
<p id="section-3.6-5"> The list of nominees disclosed for a specific
     position should contain only the names of nominees
     who are willing to be considered for the position
     under review.<a href="#section-3.6-5" class="pilcrow">¶</a></p>
<p id="section-3.6-6"> The NomCom may choose not to include
     some names in the disclosed list, at their
     discretion.<a href="#section-3.6-6" class="pilcrow">¶</a></p>
<p id="section-3.6-7"> The NomCom may disclose an updated
     list, at its discretion.  For example, the
     NomCom might disclose an updated list
     if it identifies errors/omissions in a previously
     disclosed version of the disclosed list, or if the
     NomCom finds it necessary to call for
     additional nominees, and these nominees indicate a
     willingness to be considered before the NomCom
     has completed its deliberations.<a href="#section-3.6-7" class="pilcrow">¶</a></p>
<p id="section-3.6-8"> Nominees may choose to ask people to provide
     feedback to the NomCom but should
     not encourage any public statements of support.
     NomComs should consider
     nominee-encouraged lobbying and campaigning to be
     unacceptable behavior.<a href="#section-3.6-8" class="pilcrow">¶</a></p>
<p id="section-3.6-9"> IETF community members are encouraged to provide
     feedback on nominees to the NomCom
     but should not post statements of support/non-support
     for nominees in any public forum.<a href="#section-3.6-9" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_model">
<section id="section-3.7">
        <h3 id="name-advice-and-consent-model">
<a href="#section-3.7" class="section-number selfRef">3.7. </a><a href="#name-advice-and-consent-model" class="section-name selfRef">Advice and Consent Model</a>
        </h3>
<p id="section-3.7-1"> Unless otherwise specified, the advice and
     consent model is used throughout the process.
     This model is characterized as follows.<a href="#section-3.7-1" class="pilcrow">¶</a></p>
<div id="gen_model_1">
<section id="section-3.7.1">
          <h4 id="name-positions-to-be-reviewed-2">
<a href="#section-3.7.1" class="section-number selfRef">3.7.1. </a><a href="#name-positions-to-be-reviewed-2" class="section-name selfRef">Positions to Be Reviewed</a>
          </h4>
<p id="section-3.7.1-1"> The Chairs of the IESG, IAB, IETF
 Trust, and IETF LLC Board each informs the
 NomCom of their respective
 positions to be reviewed.<a href="#section-3.7.1-1" class="pilcrow">¶</a></p>
<p id="section-3.7.1-2"> The IESG, IAB, IETF Trust, and IETF
 LLC are responsible for providing a
 summary of the expertise desired of the
 candidates selected for their respective
 open positions. The summaries are
 provided to the NomCom for
 its consideration.<a href="#section-3.7.1-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_model_2">
<section id="section-3.7.2">
          <h4 id="name-candidate-selection">
<a href="#section-3.7.2" class="section-number selfRef">3.7.2. </a><a href="#name-candidate-selection" class="section-name selfRef">Candidate Selection</a>
          </h4>
<p id="section-3.7.2-1"> The NomCom selects
     candidates based on its understanding of
     the IETF community's consensus of the
     qualifications required and advises each
     confirming body of its respective
     candidates.<a href="#section-3.7.2-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_model_3">
<section id="section-3.7.3">
          <h4 id="name-candidate-review">
<a href="#section-3.7.3" class="section-number selfRef">3.7.3. </a><a href="#name-candidate-review" class="section-name selfRef">Candidate Review</a>
          </h4>
<p id="section-3.7.3-1"> The confirming bodies review their
     respective candidates; they may at their
     discretion communicate with the NomCom,
     and then consent to some, all,
     or none of the candidates.<a href="#section-3.7.3-1" class="pilcrow">¶</a></p>
<p id="section-3.7.3-2"> The sitting IAB members review the IESG
     candidates.<a href="#section-3.7.3-2" class="pilcrow">¶</a></p>
<p id="section-3.7.3-3"> The Internet Society Board of Trustees
 reviews the IAB candidates.<a href="#section-3.7.3-3" class="pilcrow">¶</a></p>
<p id="section-3.7.3-4">The sitting IESG members review the
 IETF Trust Trustee candidates.<a href="#section-3.7.3-4" class="pilcrow">¶</a></p>
<p id="section-3.7.3-5"> The IETF LLC Director candidate is reviewed as
     specified in <span>[<a href="#RFC8711" class="xref">RFC8711</a>]</span>.<a href="#section-3.7.3-5" class="pilcrow">¶</a></p>
<p id="section-3.7.3-6"> The confirming bodies conduct their reviews
     using all information and any means
     acceptable to them, including but not
     limited to the supporting information
     provided by the NomCom,
     information known personally to members of
     the confirming bodies and shared within
     the confirming body, the results of
     interactions within the confirming bodies,
     and the confirming bodies' interpretation
     of what is in the best interests of the
     IETF community.<a href="#section-3.7.3-6" class="pilcrow">¶</a></p>
<p id="section-3.7.3-7"> If all of the candidates are confirmed,
     the job of the NomCom with
     respect to those open positions is
     complete.<a href="#section-3.7.3-7" class="pilcrow">¶</a></p>
<p id="section-3.7.3-8"> If some or none of the candidates
     submitted to a confirming body are
     confirmed, the confirming body should
     communicate with the NomCom
     both to explain the reason why all the
     candidates were not confirmed and to
     understand the NomCom's
     rationale for its candidates.<a href="#section-3.7.3-8" class="pilcrow">¶</a></p>
<p id="section-3.7.3-9"> The confirming body may reject individual
     candidates, in which case the NomCom
     must select alternate candidates
     for the rejected candidates.<a href="#section-3.7.3-9" class="pilcrow">¶</a></p>
<p id="section-3.7.3-10"> Any additional time required by the
     NomCom should not exceed its
     maximum time allotment.<a href="#section-3.7.3-10" class="pilcrow">¶</a></p>
</section>
</div>
<div id="gen_model_4">
<section id="section-3.7.4">
          <h4 id="name-confirmation">
<a href="#section-3.7.4" class="section-number selfRef">3.7.4. </a><a href="#name-confirmation" class="section-name selfRef">Confirmation</a>
          </h4>
<p id="section-3.7.4-1"> A confirming body decides whether it
     confirms each candidate using a
     confirmation decision rule chosen by the
     confirming body.<a href="#section-3.7.4-1" class="pilcrow">¶</a></p>
<p id="section-3.7.4-2"> If a confirming body has no specific
     confirmation decision rule, then
     confirming a given candidate should
     require at least one-half of the
     confirming body's sitting members to
     agree to that confirmation.<a href="#section-3.7.4-2" class="pilcrow">¶</a></p>
<p id="section-3.7.4-3"> The decision may be made by conducting a
     formal vote, by asserting consensus based
     on informal exchanges (e.g., email), or
     by any other mechanism that is used to
     conduct the normal business of the
     confirming body.<a href="#section-3.7.4-3" class="pilcrow">¶</a></p>
<p id="section-3.7.4-4"> Regardless of which decision rule the
     confirming body uses, any candidate that
     is not confirmed under that rule is
     considered to be rejected.<a href="#section-3.7.4-4" class="pilcrow">¶</a></p>
<p id="section-3.7.4-5"> The confirming body must make its decision
     within a reasonable time frame.  The
     results from the confirming body must be
     reported promptly to the NomCom.<a href="#section-3.7.4-5" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="gen_sitting">
<section id="section-3.8">
        <h3 id="name-sitting-members-directors-a">
<a href="#section-3.8" class="section-number selfRef">3.8. </a><a href="#name-sitting-members-directors-a" class="section-name selfRef">Sitting Members, Directors, and Trustees</a>
        </h3>
<p id="section-3.8-1"> The following rules apply to nominees and
 candidates who are currently sitting members of
 the IESG or IAB,
                       IETF Trust Trustees,
                       or IETF LLC Directors, and who are not sitting in an open
 position being filled by the NomCom.<a href="#section-3.8-1" class="pilcrow">¶</a></p>
<p id="section-3.8-2"> The confirmation of a candidate to an open
 position does not automatically create a vacancy
 in the IESG, IAB, IETF Trust, or IETF LLC Board
 position currently occupied by the candidate.
 The mid-term vacancy cannot exist until, first,
 the candidate formally resigns from the current
 position and, second, the body with the vacancy
 formally decides for itself that it wants the
 NomCom to fill the mid-term vacancy according to
 the rules for a mid-term vacancy documented
 elsewhere in this document.<a href="#section-3.8-2" class="pilcrow">¶</a></p>
<p id="section-3.8-3"> The resignation should be effective as of when
     the term of the new position begins.  The
     resignation may remain confidential to the IESG,
     IAB, IETF Trust, IETF LLC Board, and NomCom until the
     confirmed candidate is announced for the new
     position.  The process, according to rules set out
     elsewhere in this document, of filling the seat
     vacated by the confirmed candidate may begin as
     soon as the vacancy is publicly announced.<a href="#section-3.8-3" class="pilcrow">¶</a></p>
<p id="section-3.8-4"> Filling a mid-term vacancy is a separate and
     independent action from the customary action of
     filling open positions.  In particular, a
     NomCom must complete its job with
     respect to filling the open positions and then
     separately proceed with the task of filling the
     mid-term vacancy according to the rules for a
     mid-term vacancy documented elsewhere in this
     document.<a href="#section-3.8-4" class="pilcrow">¶</a></p>
<p id="section-3.8-5"> However, the following exception is permitted in
     the case where the candidate for an open position
     is currently a sitting member of the IAB.  It is
     consistent with these rules for the announcements
     of a resignation of a sitting member of the IAB
     and of the confirmed candidate for the mid-term
     vacancy created by that sitting member on the IAB
     to all occur at the same time as long as the
     actual sequence of events that occurred did so in
     the following order:<a href="#section-3.8-5" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-3.8-6">
          <li id="section-3.8-6.1"> The NomCom completes the
     advice and consent process for the open
     position being filled by the candidate
     currently sitting on the IAB.<a href="#section-3.8-6.1" class="pilcrow">¶</a>
</li>
<li id="section-3.8-6.2"> The newly confirmed candidate resigns
     from their current position on the
     IAB.<a href="#section-3.8-6.2" class="pilcrow">¶</a>
</li>
<li id="section-3.8-6.3"> The IAB Chair (or the Managing Director, 
 IETF Secretariat, if no Chair has been named 
 or the vacancy was created via the departure 
 of the IAB Chair) informs the NomCom 
 of the mid-term vacancy.<a href="#section-3.8-6.3" class="pilcrow">¶</a>
</li>
<li id="section-3.8-6.4"> The NomCom acts on the
     request to fill the mid-term vacancy.<a href="#section-3.8-6.4" class="pilcrow">¶</a>
</li>
</ol>
</section>
</div>
<div id="gen_announce">
<section id="section-3.9">
        <h3 id="name-announcements">
<a href="#section-3.9" class="section-number selfRef">3.9. </a><a href="#name-announcements" class="section-name selfRef">Announcements</a>
        </h3>
<p id="section-3.9-1"> All announcements must be made using at least
     the mechanism used by the IETF Secretariat for
     its announcements, including a notice on the
     IETF web site.<a href="#section-3.9-1" class="pilcrow">¶</a></p>
<p id="section-3.9-2"> As of the publication of this document, the
     current mechanism is an email message to both
     the "ietf" and the "ietf-announce" mailing
     lists.<a href="#section-3.9-2" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="selection">
<section id="section-4">
      <h2 id="name-nominating-committee-select">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-nominating-committee-select" class="section-name selfRef">Nominating Committee Selection</a>
      </h2>
<p id="section-4-1"> The following set of rules apply to the creation of the
     NomCom and the selection of its members.<a href="#section-4-1" class="pilcrow">¶</a></p>
<div id="sel_timeline">
<section id="section-4.1">
        <h3 id="name-timeline">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-timeline" class="section-name selfRef">Timeline</a>
        </h3>
<p id="section-4.1-1"> The completion of the process of selecting and
     organizing the members of the NomCom
     is due within three months.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
<p id="section-4.1-2"> The completion of the selection and organization
     process is due at least one month prior to the
     Third IETF.  This ensures the NomCom
     is fully operational and available for interviews
     and consultation during the Third IETF.<a href="#section-4.1-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_term">
<section id="section-4.2">
        <h3 id="name-term">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-term" class="section-name selfRef">Term</a>
        </h3>
<p id="section-4.2-1"> The term of a NomCom is expected to
     be 15 months.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
<p id="section-4.2-2"> It is the intent of this rule that the end of a
     NomCom's term overlap by
     approximately three months the beginning of the
     term of the next NomCom.<a href="#section-4.2-2" class="pilcrow">¶</a></p>
<p id="section-4.2-3"> The term of a NomCom begins when its
     members are officially announced.  The term ends
     at the Third IETF (not three meetings), i.e., the
     IETF meeting after the next NomCom's
     term begins.<a href="#section-4.2-3" class="pilcrow">¶</a></p>
<p id="section-4.2-4"> A term is expected to begin at least two months
     prior to the Third IETF to ensure the NomCom
     has at least one month to get organized
     before preparing for the Third IETF.<a href="#section-4.2-4" class="pilcrow">¶</a></p>
<p id="section-4.2-5"> A NomCom is expected to complete
     any work in progress before it is dissolved at
     the end of its term.<a href="#section-4.2-5" class="pilcrow">¶</a></p>
<p id="section-4.2-6"> During the period of time when the terms of
 the NomComs overlap, all mid-term vacancies are
 to be relegated to the prior year's NomCom.  The
 prior year's NomCom has no other responsibilities
 during the overlap period.  At all times other
 than the overlap period, there is exactly one
 official NomCom and it is responsible for all
 mid-term vacancies.<a href="#section-4.2-6" class="pilcrow">¶</a></p>
<p id="section-4.2-7"> When the prior year's NomCom is filling a
 mid-term vacancy during the period of time that
 the terms overlap, the NomComs operate
 independently.  However, some coordination is
 needed between them.  Since the prior year's
 Chair is a non-voting advisor to the current
 NomCom, the coordination is expected to be
 straightforward.<a href="#section-4.2-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_structure">
<section id="section-4.3">
        <h3 id="name-structure">
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-structure" class="section-name selfRef">Structure</a>
        </h3>
<p id="section-4.3-1"> The NomCom comprises at least a
     Chair, 10 voting volunteers, two liaisons,
     and an advisor.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
<p id="section-4.3-2"> Any committee member may propose the addition
 of an advisor to participate in some or all of
 the deliberations of the committee.  The addition
 must be approved by the committee according to
 its established voting mechanism.  Advisors
 participate as individuals.<a href="#section-4.3-2" class="pilcrow">¶</a></p>
<p id="section-4.3-3">Committee members are encouraged to propose
                        the addition of advisor(s) who are
                        knowledgeable about the operations of the IETF
                        Trust and/or IETF LLC Board, whether or not that NomCom
                        is reviewing an IETF Trust Trustee or IETF LLC Director
                        position.  The NomCom may choose to ask
                        the IETF Trust and/or IETF LLC Board to suggest
                        advisors who are knowledgeable about their
                        operations but may select any advisor they vote
                        to approve.<a href="#section-4.3-3" class="pilcrow">¶</a></p>
<p id="section-4.3-4"> Any committee member may propose the addition of a
     liaison from other unrepresented organizations to
     participate in some or all of the deliberations of
     the committee.  The addition must be approved by
     the committee according to its established voting
     mechanism.  Liaisons participate as
     representatives of their respective
     organizations.<a href="#section-4.3-4" class="pilcrow">¶</a></p>
<p id="section-4.3-5"> The Chair is selected according to rules stated
     elsewhere in this document.<a href="#section-4.3-5" class="pilcrow">¶</a></p>
<p id="section-4.3-6"> The 10 voting volunteers are selected according
     to rules stated elsewhere in this document.<a href="#section-4.3-6" class="pilcrow">¶</a></p>
<p id="section-4.3-7"> The IESG and IAB liaisons are selected
     according to rules stated elsewhere in this
     document.<a href="#section-4.3-7" class="pilcrow">¶</a></p>
<p id="section-4.3-8"> The Internet Society Board of Trustees may appoint
     a liaison to the NomCom at its own
     discretion.<a href="#section-4.3-8" class="pilcrow">¶</a></p>
<p id="section-4.3-9"> The IETF Trust may appoint
     a liaison to the NomCom at its own
     discretion.<a href="#section-4.3-9" class="pilcrow">¶</a></p>
<p id="section-4.3-10"> The IETF LLC Board may appoint
     a liaison to the NomCom at its own
     discretion.<a href="#section-4.3-10" class="pilcrow">¶</a></p>
<p id="section-4.3-11"> The Chair of the prior year's NomCom
     serves as an advisor according to rules stated
     elsewhere in this document.<a href="#section-4.3-11" class="pilcrow">¶</a></p>
<p id="section-4.3-12"> The Chair, liaisons, and advisors do not vote on
     the selection of candidates.  They do vote on all
     other issues before the committee unless otherwise
     specified in this document.<a href="#section-4.3-12" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_chair_duties">
<section id="section-4.4">
        <h3 id="name-chair-duties">
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-chair-duties" class="section-name selfRef">Chair Duties</a>
        </h3>
<p id="section-4.4-1"> The Chair of the NomCom is
     responsible for ensuring the NomCom
     completes its assigned duties in a timely fashion
     and performs in the best interests of the IETF
     community.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
<p id="section-4.4-2"> The Chair must be thoroughly familiar with
 the rules and guidance indicated throughout this
 document.  The Chair must ensure the NomCom
 completes its assigned duties in a manner that is
 consistent with this document.<a href="#section-4.4-2" class="pilcrow">¶</a></p>
<p id="section-4.4-3"> The Chair must attest by proclamation at a plenary
     session of the First IETF that the results of
     the committee represent its best effort and the
     best interests of the IETF community.<a href="#section-4.4-3" class="pilcrow">¶</a></p>
<p id="section-4.4-4"> The Chair does not vote on the selection of
     candidates.<a href="#section-4.4-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_chair_selection">
<section id="section-4.5">
        <h3 id="name-chair-selection">
<a href="#section-4.5" class="section-number selfRef">4.5. </a><a href="#name-chair-selection" class="section-name selfRef">Chair Selection</a>
        </h3>
<p id="section-4.5-1"> The Internet Society President appoints the
     Chair, who must meet the same requirements for
     membership in the NomCom as a
     voting volunteer.<a href="#section-4.5-1" class="pilcrow">¶</a></p>
<p id="section-4.5-2"> The NomCom Chair must agree to
     invest the time necessary to ensure that the
     NomCom completes its assigned duties
     and to perform in the best interests of the
     IETF community in that role.<a href="#section-4.5-2" class="pilcrow">¶</a></p>
<p id="section-4.5-3"> The appointment is due no later than the Second
     IETF meeting to ensure it can be announced during
     a plenary session at that meeting.  The completion
     of the appointment is necessary to ensure the
     annual process can complete at the time specified
     elsewhere in this document.<a href="#section-4.5-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_chair_temp">
<section id="section-4.6">
        <h3 id="name-temporary-chair">
<a href="#section-4.6" class="section-number selfRef">4.6. </a><a href="#name-temporary-chair" class="section-name selfRef">Temporary Chair</a>
        </h3>
<p id="section-4.6-1"> A Chair, in consultation with the Internet
     Society President, may appoint a temporary
     substitute for the Chair position.<a href="#section-4.6-1" class="pilcrow">¶</a></p>
<p id="section-4.6-2"> There are a variety of ordinary circumstances
     that may arise from time to time that could
     result in a Chair being unavailable to oversee
     the activities of the committee.  The Chair, in
     consultation with the Internet Society President,
     may appoint a substitute from a pool comprised of
     the liaisons currently serving on the committee
     and the prior year's Chair or designee.<a href="#section-4.6-2" class="pilcrow">¶</a></p>
<p id="section-4.6-3"> Any such appointment must be temporary and does
     not absolve the Chair of any or all responsibility
     for ensuring the NomCom completes
     its assigned duties in a timely fashion.<a href="#section-4.6-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_liaisons_1">
<section id="section-4.7">
        <h3 id="name-liaisons">
<a href="#section-4.7" class="section-number selfRef">4.7. </a><a href="#name-liaisons" class="section-name selfRef">Liaisons</a>
        </h3>
<p id="section-4.7-1"> Liaisons are responsible for ensuring the
     NomCom in general and the Chair in
     particular execute their assigned duties in the
     best interests of the IETF community.<a href="#section-4.7-1" class="pilcrow">¶</a></p>
<p id="section-4.7-2"> Liaisons are expected to represent the views of
     their respective organizations during the
     deliberations of the committee.  They should
     provide information as requested or when they
     believe it would be helpful to the committee.<a href="#section-4.7-2" class="pilcrow">¶</a></p>
<p id="section-4.7-3"> Liaisons
     are expected to provide information to the
     NomCom regarding the operation,
     responsibility, and composition of their
     respective bodies.<a href="#section-4.7-3" class="pilcrow">¶</a></p>
<p id="section-4.7-4"> Liaisons are expected to convey questions from the
     committee to their respective organizations and
     responses to those questions to the committee, as
     requested by the committee.<a href="#section-4.7-4" class="pilcrow">¶</a></p>
<p id="section-4.7-5">Liaisons
     are expected to review the operation and executing
     process of the NomCom and to report
     any concerns or issues to the Chair of the
     NomCom immediately.  If they cannot
     resolve the issue between themselves, liaisons must
     report it according to the dispute resolution
     process stated elsewhere in this document.<a href="#section-4.7-5" class="pilcrow">¶</a></p>
<p id="section-4.7-6"> Liaisons from confirming bodies are expected to
     assist the committee in preparing the testimony it
     is required to provide with its candidates.<a href="#section-4.7-6" class="pilcrow">¶</a></p>
<p id="section-4.7-7"> Liaisons may have other NomCom
 responsibilities as required by their respective
 organizations or requested by the NomCom, except
 that such responsibilities may not conflict with
 any other provisions of this document.<a href="#section-4.7-7" class="pilcrow">¶</a></p>
<p id="section-4.7-8"> Liaisons do not vote on the selection of
     candidates.<a href="#section-4.7-8" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_liaisons_2">
<section id="section-4.8">
        <h3 id="name-liaison-appointment">
<a href="#section-4.8" class="section-number selfRef">4.8. </a><a href="#name-liaison-appointment" class="section-name selfRef">Liaison Appointment</a>
        </h3>
<p id="section-4.8-1">The sitting IAB and IESG members each appoint someone from 
   their current membership who is not sitting in an open position 
   to serve as a liaison to the NomCom.<a href="#section-4.8-1" class="pilcrow">¶</a></p>
<p id="section-4.8-2"> The sitting IETF Trust Trustees and IETF LLC
 Directors each may appoint a liaison from their
 current membership, someone who is not sitting in
 an open position, to serve on the NomCom.<a href="#section-4.8-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_advisors">
<section id="section-4.9">
        <h3 id="name-advisors">
<a href="#section-4.9" class="section-number selfRef">4.9. </a><a href="#name-advisors" class="section-name selfRef">Advisors</a>
        </h3>
<p id="section-4.9-1"> An advisor is responsible for such duties as
     specified by the invitation that resulted in
     the appointment.<a href="#section-4.9-1" class="pilcrow">¶</a></p>
<p id="section-4.9-2"> Advisors do not vote on the selection of
     candidates.<a href="#section-4.9-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_chair_past">
<section id="section-4.10">
        <h3 id="name-past-chair">
<a href="#section-4.10" class="section-number selfRef">4.10. </a><a href="#name-past-chair" class="section-name selfRef">Past Chair</a>
        </h3>
<p id="section-4.10-1"> The Chair of the prior year's NomCom
     serves as an advisor to the current committee.<a href="#section-4.10-1" class="pilcrow">¶</a></p>
<p id="section-4.10-2"> The prior year's Chair is expected to review
 the actions and activities of the current Chair
 and to report any concerns or issues to the
 NomCom Chair immediately.  If they cannot
 resolve the issue between themselves, the prior
 year's Chair must report it according to the
 dispute resolution process stated elsewhere in
 this document.<a href="#section-4.10-2" class="pilcrow">¶</a></p>
<p id="section-4.10-3"> The prior year's Chair may select a designee from
     a pool composed of the voting volunteers of the
     prior year's committee and all prior Chairs if the
     Chair is unavailable.  If the prior year's Chair is
     unavailable or is unable or unwilling to make such a
     designation in a timely fashion, the Chair of the
     current year's committee may select a designee in
     consultation with the Internet Society
     President.<a href="#section-4.10-3" class="pilcrow">¶</a></p>
<p id="section-4.10-4"> Selecting a prior year's committee member as the
     designee permits the experience of the prior year's
     deliberations to be readily available to the current
     committee.  Selecting an earlier prior year Chair
     as the designee permits the experience of being a
     Chair as well as that Chair's committee
     deliberations to be readily available to the current
     committee.<a href="#section-4.10-4" class="pilcrow">¶</a></p>
<p id="section-4.10-5"> All references to "prior year's Chair" in this
     document refer to the person serving in that role,
     whether it is the actual prior year's Chair or a
     designee.<a href="#section-4.10-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_volunteers">
<section id="section-4.11">
        <h3 id="name-voting-volunteers">
<a href="#section-4.11" class="section-number selfRef">4.11. </a><a href="#name-voting-volunteers" class="section-name selfRef">Voting Volunteers</a>
        </h3>
<p id="section-4.11-1"> Voting volunteers are responsible for completing the
     tasks of the NomCom in a timely
     fashion.<a href="#section-4.11-1" class="pilcrow">¶</a></p>
<p id="section-4.11-2"> Each voting volunteer is expected to participate in
     all activities of the NomCom with a
     level of effort approximately equal to all other
     voting volunteers.  Specific tasks to be completed
     are established and managed by the Chair according
     to rules stated elsewhere in this document.<a href="#section-4.11-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_milestones">
<section id="section-4.12">
        <h3 id="name-milestones">
<a href="#section-4.12" class="section-number selfRef">4.12. </a><a href="#name-milestones" class="section-name selfRef">Milestones</a>
        </h3>
<p id="section-4.12-1"> The Chair must establish and announce milestones for
     the selection of the NomCom
     members.<a href="#section-4.12-1" class="pilcrow">¶</a></p>
<p id="section-4.12-2"> There is a defined time period during which the
     selection process is due to be completed.  The
     Chair must establish a set of milestones which,
     if met in a timely fashion, will result in the
     completion of the process on time.<a href="#section-4.12-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_positions">
<section id="section-4.13">
        <h3 id="name-open-positions">
<a href="#section-4.13" class="section-number selfRef">4.13. </a><a href="#name-open-positions" class="section-name selfRef">Open Positions</a>
        </h3>
<p id="section-4.13-1"> The Chair (or the Managing Director, IETF Secretariat, if no
     Chair has been named four weeks after the First IETF
     meeting of the year) obtains the list of positions
     to be reviewed and announces it along with a
     solicitation for names of volunteers from the IETF
     community willing to serve on the NomCom.<a href="#section-4.13-1" class="pilcrow">¶</a></p>
<p id="section-4.13-2"> If the Managing Director, IETF Secretariat, issues the
     solicitation for volunteers, the Managing Director, IETF Secretariat,
     must also collect responses to the
     solicitation and provide the names of volunteers to
     the incoming NomCom Chair when the
     incoming NomCom Chair is named.<a href="#section-4.13-2" class="pilcrow">¶</a></p>
<p id="section-4.13-3"> At the Chair's request, the IETF Secretariat may
     perform other clerical support tasks, as long as
     the task being performed does not require NomCom
     Chair judgment, in the NomCom
     Chair's opinion, and as long as the
     community is appropriately notified that this
     request is being made.  This request may come from
     the incoming NomCom Chair (if one has
     been selected for this NomCom cycle)
     or the previous NomCom Chair (if the
     search for an incoming NomCom Chair is
     still underway).<a href="#section-4.13-3" class="pilcrow">¶</a></p>
<p id="section-4.13-4"> The solicitation must permit the community at
     least 30 days during which they may choose to
     volunteer to be selected for the NomCom.<a href="#section-4.13-4" class="pilcrow">¶</a></p>
<p id="section-4.13-5"> The list of open positions is published with the
     solicitation to facilitate community members
     choosing between volunteering for an open position
     and volunteering for the NomCom.<a href="#section-4.13-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_qualify">
<section id="section-4.14">
        <h3 id="name-volunteer-qualification">
<a href="#section-4.14" class="section-number selfRef">4.14. </a><a href="#name-volunteer-qualification" class="section-name selfRef">Volunteer Qualification</a>
        </h3>
<p id="section-4.14-1"> Members of the IETF community must have attended at
     least three of the last five IETF meetings in order
     to volunteer.<a href="#section-4.14-1" class="pilcrow">¶</a></p>
<p id="section-4.14-2"> The five meetings are the five most recent meetings
     that ended prior to the date on which the
     solicitation for NomCom volunteers
     was submitted for distribution to the IETF
     community.<a href="#section-4.14-2" class="pilcrow">¶</a></p>
<p id="section-4.14-3"> The IETF Secretariat is responsible for confirming
     that volunteers have met the attendance
     requirement.<a href="#section-4.14-3" class="pilcrow">¶</a></p>
<p id="section-4.14-4"> Volunteers must provide their full name, email
     address, and primary company or organization
     affiliation (if any) when volunteering.<a href="#section-4.14-4" class="pilcrow">¶</a></p>
<p id="section-4.14-5"> Volunteers are expected to be familiar with the
     IETF processes and procedures, which are readily
     learned by active participation in a working group
     and especially by serving as a document editor
     or working group chair.<a href="#section-4.14-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_disqualify">
<section id="section-4.15">
        <h3 id="name-not-qualified">
<a href="#section-4.15" class="section-number selfRef">4.15. </a><a href="#name-not-qualified" class="section-name selfRef">Not Qualified</a>
        </h3>
<p id="section-4.15-1"> Any person who serves on the Internet Society
 Board of Trustees, the IETF Trust, the IETF LLC Board of
 Directors, the IAB, or the IESG, including those
 who serve on these bodies in ex officio
 positions, may not volunteer to serve as voting
 members of the NomCom. In addition,
 employees or contractors of the IETF LLC
 may not volunteer to serve as voting members of
 the NomCom.  Liaisons to these
 bodies from other bodies or organizations are not
 excluded by this rule.<a href="#section-4.15-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_process">
<section id="section-4.16">
        <h3 id="name-selection-process">
<a href="#section-4.16" class="section-number selfRef">4.16. </a><a href="#name-selection-process" class="section-name selfRef">Selection Process</a>
        </h3>
<p id="section-4.16-1"> The Chair announces both the list of the pool
     of volunteers from which the 10 voting volunteers
     will be randomly selected and the method with which
     the selection will be completed.<a href="#section-4.16-1" class="pilcrow">¶</a></p>
<p id="section-4.16-2"> The announcement should be made at least one week
     prior to the date on which the random selection will
     occur.<a href="#section-4.16-2" class="pilcrow">¶</a></p>
<p id="section-4.16-3"> The pool of volunteers must be enumerated or
     otherwise indicated according to the needs of the
     selection method to be used.<a href="#section-4.16-3" class="pilcrow">¶</a></p>
<p id="section-4.16-4"> The announcement must specify the data that will be
     used as input to the selection method.  The method
     must depend on random data whose value is not
     known or available until the date on which the
     random selection will occur.<a href="#section-4.16-4" class="pilcrow">¶</a></p>
<p id="section-4.16-5"> It must be possible to independently verify that
     the selection method used is both fair and
     unbiased.  A method is fair if each eligible
     volunteer is equally likely to be selected.  A
     method is unbiased if no one can influence its
     outcome in favor of a specific outcome.<a href="#section-4.16-5" class="pilcrow">¶</a></p>
<p id="section-4.16-6"> It must be possible to repeat the selection method,
     either through iteration or by restarting in such a
     way as to remain fair and unbiased.  This is
     necessary to replace selected volunteers should they
     become unavailable after selection.<a href="#section-4.16-6" class="pilcrow">¶</a></p>
<p id="section-4.16-7"> The selection method must produce an ordered list
     of volunteers.<a href="#section-4.16-7" class="pilcrow">¶</a></p>
<p id="section-4.16-8"> One possible selection method is described in
     <span>[<a href="#RFC3797" class="xref">RFC3797</a>]</span>.<a href="#section-4.16-8" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_announce">
<section id="section-4.17">
        <h3 id="name-announcement-of-selection-r">
<a href="#section-4.17" class="section-number selfRef">4.17. </a><a href="#name-announcement-of-selection-r" class="section-name selfRef">Announcement of Selection Results</a>
        </h3>
<p id="section-4.17-1"> The Chair randomly selects the 10 voting
     volunteers from the pool of names of volunteers and
     announces the members of the NomCom.<a href="#section-4.17-1" class="pilcrow">¶</a></p>
<p id="section-4.17-2"> No more than two volunteers with the same
 primary affiliation may be selected for the
 NomCom.  The Chair reviews the primary
 affiliation of each volunteer selected by the
 method in turn.  If the primary affiliation for a
 volunteer is the same as two previously selected
 volunteers, that volunteer is removed from
 consideration and the method is repeated to
 identify the next eligible volunteer.<a href="#section-4.17-2" class="pilcrow">¶</a></p>
<p id="section-4.17-3"> There must be at least two announcements of all
     members of the NomCom.<a href="#section-4.17-3" class="pilcrow">¶</a></p>
<p id="section-4.17-4"> The first announcement should occur as soon after
     the random selection as is reasonable for the
     Chair.  The community must have at least one week
     during which any member may challenge the results of
     the random selection.<a href="#section-4.17-4" class="pilcrow">¶</a></p>
<p id="section-4.17-5"> The challenge must be made in writing (email is
     acceptable) to the Chair.  The Chair has 48 hours to
     review the challenge and offer a resolution to the
     member.  If the resolution is not accepted by the
     member, that member may report the challenge
     according to the dispute resolution process stated
     elsewhere in this document.<a href="#section-4.17-5" class="pilcrow">¶</a></p>
<p id="section-4.17-6"> If a selected volunteer, upon reading the
     announcement with the list of selected volunteers,
     finds that two or more other volunteers have the
     same affiliation, then the volunteer should notify
     the Chair who will determine the appropriate
     action.<a href="#section-4.17-6" class="pilcrow">¶</a></p>
<p id="section-4.17-7"> During at least the one week challenge period, the
     Chair must contact each of the members and confirm
     their willingness and availability to serve.  The
     Chair should make every reasonable effort to contact
     each member.<a href="#section-4.17-7" class="pilcrow">¶</a></p>
<ul>
<li id="section-4.17-8.1"> If the Chair is unable to contact a liaison,
     the problem is referred to the respective
     organization to resolve.  The Chair should
     allow a reasonable amount of time for the
     organization to resolve the problem and then
     may proceed without the liaison.<a href="#section-4.17-8.1" class="pilcrow">¶</a>
</li>
<li id="section-4.17-8.2"> If the Chair is unable to contact an advisor,
     the Chair may elect to proceed without the
     advisor, except for the prior year's Chair
     for whom the Chair must consult with the
     Internet Society President as stated
     elsewhere in this document.<a href="#section-4.17-8.2" class="pilcrow">¶</a>
</li>
<li id="section-4.17-8.3"> If the Chair is unable to contact a voting
     volunteer, the Chair must repeat the random
     selection process in order to replace the
     unavailable volunteer.  There should be at
     least one day between the announcement of
     the iteration and the selection process.<a href="#section-4.17-8.3" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-4.17-9"> After at least one week and confirming that 10
     voting volunteers are ready to serve, the Chair
     makes the second announcement of the members of the
     NomCom, which officially begins the
     term of the NomCom.<a href="#section-4.17-9" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sel_organize">
<section id="section-4.18">
        <h3 id="name-committee-organization">
<a href="#section-4.18" class="section-number selfRef">4.18. </a><a href="#name-committee-organization" class="section-name selfRef">Committee Organization</a>
        </h3>
<p id="section-4.18-1"> The Chair works with the members of the committee to
     organize itself in preparation for completing its
     assigned duties.<a href="#section-4.18-1" class="pilcrow">¶</a></p>
<p id="section-4.18-2"> The committee has approximately one month during
     which it can self-organize.  Its responsibilities
     during this time include but are not limited to the
     following:<a href="#section-4.18-2" class="pilcrow">¶</a></p>
<ul>
<li id="section-4.18-3.1"> Setting up a regular teleconference
     schedule.<a href="#section-4.18-3.1" class="pilcrow">¶</a>
</li>
<li id="section-4.18-3.2"> Setting up an internal web site.<a href="#section-4.18-3.2" class="pilcrow">¶</a>
</li>
<li id="section-4.18-3.3"> Setting up a mailing list for internal
     discussions.<a href="#section-4.18-3.3" class="pilcrow">¶</a>
</li>
<li id="section-4.18-3.4"> Setting up an email address for receiving
     community input.<a href="#section-4.18-3.4" class="pilcrow">¶</a>
</li>
<li id="section-4.18-3.5"> Establishing operational procedures.<a href="#section-4.18-3.5" class="pilcrow">¶</a>
</li>
<li id="section-4.18-3.6"> Establishing milestones in order to monitor
     the progress of the selection process.<a href="#section-4.18-3.6" class="pilcrow">¶</a>
</li>
</ul>
</section>
</div>
</section>
</div>
<div id="operation">
<section id="section-5">
      <h2 id="name-nominating-committee-operat">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-nominating-committee-operat" class="section-name selfRef">Nominating Committee Operation</a>
      </h2>
<p id="section-5-1"> The following rules apply to the operation of the
     NomCom.  If necessary, a paragraph
     discussing the interpretation of each rule is
     included.<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2"> The rules are organized approximately in the order
     in which they would be invoked.<a href="#section-5-2" class="pilcrow">¶</a></p>
<div id="op_discretion">
<section id="section-5.1">
        <h3 id="name-discretion">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-discretion" class="section-name selfRef">Discretion</a>
        </h3>
<p id="section-5.1-1"> All rules and special circumstances not otherwise
     specified are at the discretion of the
     committee.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<p id="section-5.1-2"> Exceptional circumstances will occasionally arise
     during the normal operation of the NomCom.
     This rule is intended to foster the
     continued forward progress of the committee.<a href="#section-5.1-2" class="pilcrow">¶</a></p>
<p id="section-5.1-3"> Any member of the committee may propose a rule for
     adoption by the committee.  The rule must be
     approved by the committee according to its
     established voting mechanism.<a href="#section-5.1-3" class="pilcrow">¶</a></p>
<p id="section-5.1-4"> All members of the committee should consider whether
     the exception is worthy of mention in the next
     revision of this document and follow up
     accordingly.<a href="#section-5.1-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_timeline_1">
<section id="section-5.2">
        <h3 id="name-selection-timeline">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-selection-timeline" class="section-name selfRef">Selection Timeline</a>
        </h3>
<p id="section-5.2-1"> The completion of the process of selecting
     candidates to be confirmed by their respective
     confirming body is due within three months.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
<p id="section-5.2-2"> The completion of the selection process is due at
     least two months prior to the First IETF.  This
     ensures the NomCom has sufficient time
     to complete the confirmation process.<a href="#section-5.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_timeline_2">
<section id="section-5.3">
        <h3 id="name-confirmation-timeline">
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-confirmation-timeline" class="section-name selfRef">Confirmation Timeline</a>
        </h3>
<p id="section-5.3-1"> The completion of the process of confirming the
     candidates is due within one month.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
<p id="section-5.3-2"> The completion of the confirmation process is due
     at least one month prior to the First IETF.<a href="#section-5.3-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_milestones">
<section id="section-5.4">
        <h3 id="name-milestones-2">
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-milestones-2" class="section-name selfRef">Milestones</a>
        </h3>
<p id="section-5.4-1"> The Chair must establish
     a set of NomCom milestones for the candidate
     selection and confirmation process.<a href="#section-5.4-1" class="pilcrow">¶</a></p>
<p id="section-5.4-2"> There is a defined time period during which the
     candidate selection and confirmation process must be
     completed.  The Chair must establish a set of
     milestones that, if met in a timely fashion, will
     result in the completion of the process on time.
     The Chair should allow time for iterating the
     activities of the committee if one or more
     candidates are not confirmed.<a href="#section-5.4-2" class="pilcrow">¶</a></p>
<p id="section-5.4-3"> The Chair should ensure that all committee members
     are aware of the milestones.<a href="#section-5.4-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_voting">
<section id="section-5.5">
        <h3 id="name-voting-mechanism">
<a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-voting-mechanism" class="section-name selfRef">Voting Mechanism</a>
        </h3>
<p id="section-5.5-1"> The Chair must establish a voting mechanism.<a href="#section-5.5-1" class="pilcrow">¶</a></p>
<p id="section-5.5-2"> The committee must be able to objectively determine
     when a decision has been made during its
     deliberations.  The criteria for determining closure
     must be established and known to all members of the
     NomCom.<a href="#section-5.5-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_quorum">
<section id="section-5.6">
        <h3 id="name-voting-quorum">
<a href="#section-5.6" class="section-number selfRef">5.6. </a><a href="#name-voting-quorum" class="section-name selfRef">Voting Quorum</a>
        </h3>
<p id="section-5.6-1"> At least a quorum of committee members must
     participate in a vote.<a href="#section-5.6-1" class="pilcrow">¶</a></p>
<p id="section-5.6-2"> Only voting volunteers vote on a candidate
     selection.  For a candidate selection vote, a
     quorum is comprised of at least seven of the
     voting volunteers.<a href="#section-5.6-2" class="pilcrow">¶</a></p>
<p id="section-5.6-3"> At all other times, a quorum is present if at
     least 75% of the NomCom members are
     participating.<a href="#section-5.6-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_recall_1">
<section id="section-5.7">
        <h3 id="name-voting-member-recall">
<a href="#section-5.7" class="section-number selfRef">5.7. </a><a href="#name-voting-member-recall" class="section-name selfRef">Voting Member Recall</a>
        </h3>
<p id="section-5.7-1"> Any member of the NomCom may propose
     to the committee that any other member except the
     Chair be recalled.  The process for recalling the
     Chair is defined elsewhere in this document.<a href="#section-5.7-1" class="pilcrow">¶</a></p>
<p id="section-5.7-2"> There are a variety of ordinary circumstances that
     may arise that could result in one or more members
     of the committee being unavailable to complete their
     assigned duties, for example, health concerns, family
     issues, or a change of priorities at work.  A
     committee member may choose to resign for
     unspecified personal reasons.  In addition, the
     committee may not function well as a group because
     a member may be disruptive or otherwise
     uncooperative.<a href="#section-5.7-2" class="pilcrow">¶</a></p>
<p id="section-5.7-3"> Regardless of the circumstances, if individual
     committee members cannot work out their differences
     between themselves, the entire committee may be
     called upon to discuss and review the
     circumstances.  If a resolution is not forthcoming, a
     vote may be conducted.  A member may be recalled if
     at least a quorum of all committee members agree,
     including the vote of the member being recalled.<a href="#section-5.7-3" class="pilcrow">¶</a></p>
<p id="section-5.7-4"> If a liaison member is recalled, the committee must
     notify the affected organization and must allow a
     reasonable amount of time for a replacement to be
     identified by the organization before
     proceeding.<a href="#section-5.7-4" class="pilcrow">¶</a></p>
<p id="section-5.7-5"> If an advisor member other than the prior year's
     Chair is recalled, the committee may choose to
     proceed without the advisor.  In the case of the
     prior year's Chair, the Internet Society President
     must be notified and the current Chair must be
     allowed a reasonable amount of time to consult with
     the Internet Society President to identify a
     replacement before proceeding.<a href="#section-5.7-5" class="pilcrow">¶</a></p>
<p id="section-5.7-6"> If a single voting volunteer position on the
     NomCom is vacated, regardless of the
     circumstances, the committee may choose to proceed
     with only nine voting volunteers at its own
     discretion.  In all other cases, a new voting member
     must be selected, and the Chair must repeat the
     random selection process including an announcement
     of the iteration prior to the actual selection as
     stated elsewhere in this document.<a href="#section-5.7-6" class="pilcrow">¶</a></p>
<p id="section-5.7-7"> A change in the primary affiliation of a
 voting volunteer during the term of the NomCom is
 not a cause to request the recall of that
 volunteer, even if the change would result in
 more than two voting volunteers with the same
 affiliation.<a href="#section-5.7-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_recall_2">
<section id="section-5.8">
        <h3 id="name-chair-recall">
<a href="#section-5.8" class="section-number selfRef">5.8. </a><a href="#name-chair-recall" class="section-name selfRef">Chair Recall</a>
        </h3>
<p id="section-5.8-1"> Only the prior year's Chair may request the
     recall of the current Chair.<a href="#section-5.8-1" class="pilcrow">¶</a></p>
<p id="section-5.8-2"> It is the responsibility of the prior year's
     Chair to ensure the current Chair completes the
     assigned tasks in a manner consistent with this
     document and in the best interests of the IETF
     community.<a href="#section-5.8-2" class="pilcrow">¶</a></p>
<p id="section-5.8-3"> Any member of the committee who has an issue or
     concern regarding the Chair should report it to
     the prior year's Chair immediately.  The prior
     year's Chair is expected to report it to the Chair
     immediately.  If they cannot resolve the issue
     between themselves, the prior year's Chair must
     report it according to the dispute resolution
     process stated elsewhere in this document.<a href="#section-5.8-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_deliberations">
<section id="section-5.9">
        <h3 id="name-deliberations">
<a href="#section-5.9" class="section-number selfRef">5.9. </a><a href="#name-deliberations" class="section-name selfRef">Deliberations</a>
        </h3>
<p id="section-5.9-1"> All members of the NomCom may
     participate in all deliberations.<a href="#section-5.9-1" class="pilcrow">¶</a></p>
<p id="section-5.9-2"> The emphasis of this rule is that no member can be
     explicitly excluded from any deliberation.  However,
     a member may individually choose not to participate
     in a deliberation.<a href="#section-5.9-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_call">
<section id="section-5.10">
        <h3 id="name-call-for-nominees">
<a href="#section-5.10" class="section-number selfRef">5.10. </a><a href="#name-call-for-nominees" class="section-name selfRef">Call for Nominees</a>
        </h3>
<p id="section-5.10-1"> The Chair announces the open positions to be
     reviewed, the desired expertise provided by the
     Managing Director, IETF Secretariat, and the call for
     nominees.<a href="#section-5.10-1" class="pilcrow">¶</a></p>
<p id="section-5.10-2"> The call for nominees must include a request for
     comments regarding the past performance of
     incumbents, which will be considered during the
     deliberations of the NomCom.<a href="#section-5.10-2" class="pilcrow">¶</a></p>
<p id="section-5.10-3"> The call must request that a nomination include a
     valid, working email address, a telephone number,
     or both for the nominee.  The nomination must
     include the set of skills or expertise the nominator
     believes the nominee has that would be
     desirable.<a href="#section-5.10-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_nominations">
<section id="section-5.11">
        <h3 id="name-nominations">
<a href="#section-5.11" class="section-number selfRef">5.11. </a><a href="#name-nominations" class="section-name selfRef">Nominations</a>
        </h3>
<p id="section-5.11-1"> Any member of the IETF community may nominate any
     member of the IETF community for any open position,
     whose eligibility to serve will be confirmed by the
     NomCom.<a href="#section-5.11-1" class="pilcrow">¶</a></p>
<p id="section-5.11-2"> A self-nomination is permitted.<a href="#section-5.11-2" class="pilcrow">¶</a></p>
<p id="section-5.11-3"> NomCom members are not eligible to
     be considered for filling any open position by
     the NomCom on which they serve.  They
     become ineligible as soon as the term of the
     NomCom on which they serve officially
     begins.  They remain ineligible for the duration of
     that NomCom's term.<a href="#section-5.11-3" class="pilcrow">¶</a></p>
<p id="section-5.11-4"> Although each NomCom's term overlaps
     with the following NomCom's term,
     NomCom members are eligible for
     nomination by the following committee if not
     otherwise disqualified.<a href="#section-5.11-4" class="pilcrow">¶</a></p>
<p id="section-5.11-5"> Members of the IETF community who were
      recalled from any IESG, IAB, IETF Trust, or
     IETF LLC Board position during the previous two
     years are not eligible to be considered for
     filling any open position.<a href="#section-5.11-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_candidates">
<section id="section-5.12">
        <h3 id="name-candidate-selection-2">
<a href="#section-5.12" class="section-number selfRef">5.12. </a><a href="#name-candidate-selection-2" class="section-name selfRef">Candidate Selection</a>
        </h3>
<p id="section-5.12-1"> The NomCom selects candidates based
     on its understanding of the IETF community's
     consensus of the qualifications required to fill
     the open positions.<a href="#section-5.12-1" class="pilcrow">¶</a></p>
<p id="section-5.12-2"> The intent of this rule is to ensure that the
     NomCom consults with a broad base of
     the IETF community for input to its deliberations.
     In particular, the NomCom must
     determine if the desired expertise for the open
     positions matches its understanding of the
     qualifications desired by the IETF community.<a href="#section-5.12-2" class="pilcrow">¶</a></p>
<p id="section-5.12-3"> The consultations are permitted to include names
     of nominees, if all parties to the consultation
     agree to observe the same confidentiality rules as
     the NomCom itself, or the names are
     public as discussed in
     <a href="#gen_confidential" class="xref">Section 3.6</a>.  Feedback on
     individual nominees should always be
     confidential.<a href="#section-5.12-3" class="pilcrow">¶</a></p>
<p id="section-5.12-4"> A broad base of the community should include the
     existing members of the IESG and IAB, IETF
     Trust Trustees, and
     IETF LLC Directors,
     especially sitting members who share
     responsibilities with open positions, e.g.,
     co-Area Directors, and working group chairs,
     especially those in the areas with open
     positions.<a href="#section-5.12-4" class="pilcrow">¶</a></p>
<p id="section-5.12-5"> Only voting volunteer members vote to select
     candidates.<a href="#section-5.12-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_consent">
<section id="section-5.13">
        <h3 id="name-consent-to-nomination">
<a href="#section-5.13" class="section-number selfRef">5.13. </a><a href="#name-consent-to-nomination" class="section-name selfRef">Consent to Nomination</a>
        </h3>
<p id="section-5.13-1"> Nominees should be advised that they are being
     considered and must consent to their nomination
     prior to being chosen as candidates.<a href="#section-5.13-1" class="pilcrow">¶</a></p>
<p id="section-5.13-2"> Although the NomCom will make every
     reasonable effort to contact and to remain in
     contact with nominees, any nominee whose contact
     information changes during the process and who
     wishes to still be considered should inform the
     NomCom of the changes.<a href="#section-5.13-2" class="pilcrow">¶</a></p>
<p id="section-5.13-3"> A nominee's consent must be written (email is
     acceptable) and must include a commitment to provide
     the resources necessary to fill the open position
     and an assurance that the nominee will perform the
     duties of the position for which they are being
     considered in the best interests of the IETF
     community.<a href="#section-5.13-3" class="pilcrow">¶</a></p>
<p id="section-5.13-4"> Consenting to a nomination must occur prior to a
     nominee being a candidate and may occur as soon
     after the nomination as needed by the NomCom.<a href="#section-5.13-4" class="pilcrow">¶</a></p>
<p id="section-5.13-5"> Consenting to a nomination must not imply the
     nominee will be a candidate.<a href="#section-5.13-5" class="pilcrow">¶</a></p>
<p id="section-5.13-6"> The NomCom should help nominees
     provide justification to their employers.<a href="#section-5.13-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_announce_1">
<section id="section-5.14">
        <h3 id="name-notifying-confirming-bodies">
<a href="#section-5.14" class="section-number selfRef">5.14. </a><a href="#name-notifying-confirming-bodies" class="section-name selfRef">Notifying Confirming Bodies</a>
        </h3>
<p id="section-5.14-1"> The NomCom advises the confirming
     bodies of their candidates, specifying a single
     candidate for each open position and testifying as
     to how each candidate meets the qualifications of
     an open position.<a href="#section-5.14-1" class="pilcrow">¶</a></p>
<p id="section-5.14-2"> For each candidate, the testimony must include a
     brief statement of the qualifications for the
     position that is being filled, which may be exactly
     the expertise that was requested.  If the
     qualifications differ from the expertise originally
     requested, a brief statement explaining the
     difference must be included.<a href="#section-5.14-2" class="pilcrow">¶</a></p>
<p id="section-5.14-3"> The testimony may include a brief
     resume of the candidate and/or a brief summary of the
     deliberations of the NomCom.<a href="#section-5.14-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_announce_2">
<section id="section-5.15">
        <h3 id="name-confirming-candidates">
<a href="#section-5.15" class="section-number selfRef">5.15. </a><a href="#name-confirming-candidates" class="section-name selfRef">Confirming Candidates</a>
        </h3>
<p id="section-5.15-1"> Confirmed candidates must consent to their
     confirmation, and rejected candidates and nominees
     must be notified before confirmed candidates are
     announced.<a href="#section-5.15-1" class="pilcrow">¶</a></p>
<p id="section-5.15-2"> It is not necessary to notify and get consent from
     all confirmed candidates together.<a href="#section-5.15-2" class="pilcrow">¶</a></p>
<p id="section-5.15-3"> A nominee may not know they were a candidate.  This
     permits a candidate to be rejected by a confirming
     body without the nominee knowing about the
     rejection.<a href="#section-5.15-3" class="pilcrow">¶</a></p>
<p id="section-5.15-4"> Rejected nominees, who consented to their
     nomination, and rejected candidates must be notified
     prior to announcing the confirmed candidates.<a href="#section-5.15-4" class="pilcrow">¶</a></p>
<p id="section-5.15-5"> It is not necessary to announce all confirmed
     candidates together.<a href="#section-5.15-5" class="pilcrow">¶</a></p>
<p id="section-5.15-6"> The NomCom must ensure that all
     confirmed candidates are prepared to serve prior to
     announcing their confirmation.<a href="#section-5.15-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="op_archive">
<section id="section-5.16">
        <h3 id="name-archives">
<a href="#section-5.16" class="section-number selfRef">5.16. </a><a href="#name-archives" class="section-name selfRef">Archives</a>
        </h3>
<p id="section-5.16-1"> The NomCom should archive the
     information it has collected or produced for a
     period of time but not to exceed its term.<a href="#section-5.16-1" class="pilcrow">¶</a></p>
<p id="section-5.16-2"> The purpose of the archive is to assist the
     NomCom should it be necessary for it
     to fill a mid-term vacancy.<a href="#section-5.16-2" class="pilcrow">¶</a></p>
<p id="section-5.16-3"> The existence of an archive, how it is implemented,
     and what information to archive is at the discretion
     of the committee.  The decision must be approved by
     a quorum of the voting volunteer members.<a href="#section-5.16-3" class="pilcrow">¶</a></p>
<p id="section-5.16-4"> The implementation of the archive should make every
     reasonable effort to ensure that the confidentiality
     of the information it contains is maintained.<a href="#section-5.16-4" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="dispute">
<section id="section-6">
      <h2 id="name-dispute-resolution-process">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-dispute-resolution-process" class="section-name selfRef">Dispute Resolution Process</a>
      </h2>
<p id="section-6-1"> The dispute resolution process described here is to be used
     as indicated elsewhere in this document.  Its applicability
     in other circumstances is beyond the scope of this
     document.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2"> The NomCom operates under a strict rule of
     confidentiality.  For this reason, when process issues arise,
     it is best to make every reasonable effort to resolve them
     within the committee.  However, when circumstances do not
     permit this, or no resolution is forthcoming, the process
     described here is to be used.<a href="#section-6-2" class="pilcrow">¶</a></p>
<p id="section-6-3">The following rules apply to the process:<a href="#section-6-3" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-6-4">
        <li id="section-6-4.1"> The results of this process are final and binding.
     There is no appeal.<a href="#section-6-4.1" class="pilcrow">¶</a>
</li>
<li id="section-6-4.2"> The process begins with the submission of a request
     as described below to the Internet Society
     President.<a href="#section-6-4.2" class="pilcrow">¶</a>
</li>
<li id="section-6-4.3"> As soon as the process begins, the NomCom
     may continue those activities that are
     unrelated to the issue to be resolved except that
     it must not submit any candidates to a confirming
     body until the issue is resolved.<a href="#section-6-4.3" class="pilcrow">¶</a>
</li>
<li id="section-6-4.4"> All parties to the process are subject to the
     same confidentiality rules as each member of the
     NomCom.<a href="#section-6-4.4" class="pilcrow">¶</a>
</li>
<li id="section-6-4.5"> The process should be completed within two
     weeks.<a href="#section-6-4.5" class="pilcrow">¶</a>
</li>
</ol>
<p id="section-6-5"> The process is as follows:<a href="#section-6-5" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-6-6">
        <li id="section-6-6.1"> The party seeking resolution submits a written
     request (email is acceptable) to the Internet
     Society President detailing the issue to be
     resolved.<a href="#section-6-6.1" class="pilcrow">¶</a>
</li>
<li id="section-6-6.2"> The Internet Society President appoints an arbiter
     to investigate and resolve the issue.  A
     self-appointment is permitted.<a href="#section-6-6.2" class="pilcrow">¶</a>
</li>
<li id="section-6-6.3"> The arbiter investigates the issue making every
     reasonable effort to understand both sides of the
     issue.  Since the arbiter is subject to the same
     confidentiality obligations as all NomCom
     members, all members are expected to
     cooperate fully with the arbiter and to provide all
     relevant information to the arbiter for review.<a href="#section-6-6.3" class="pilcrow">¶</a>
</li>
<li id="section-6-6.4"> After consultation with the two principal parties
     to the issue, the arbiter decides on a resolution.
     Whatever actions are necessary to execute the
     resolution are immediately begun and completed as
     quickly as possible.<a href="#section-6-6.4" class="pilcrow">¶</a>
</li>
<li id="section-6-6.5"> The arbiter summarizes the issue, the resolution,
     and the rationale for the resolution for the
     Internet Society President.<a href="#section-6-6.5" class="pilcrow">¶</a>
</li>
<li id="section-6-6.6"> In consultation with the Internet Society President,
     the arbiter prepares a report of the dispute and
     its resolution.  The report should include all
     information that in the judgment of the arbiter
     does not violate the confidentiality requirements
     of the NomCom.<a href="#section-6-6.6" class="pilcrow">¶</a>
</li>
<li id="section-6-6.7"> The Chair includes the dispute report when
 reporting on the activities of the NomCom to the
 IETF community.<a href="#section-6-6.7" class="pilcrow">¶</a>
</li>
</ol>
</section>
</div>
<div id="recall">
<section id="section-7">
      <h2 id="name-member-trustee-and-director">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-member-trustee-and-director" class="section-name selfRef">Member, Trustee, and Director Recall</a>
      </h2>
<p id="section-7-1"> The following rules apply to the recall process.  If
     necessary, a paragraph discussing the interpretation of
     each rule is included.<a href="#section-7-1" class="pilcrow">¶</a></p>
<p id="section-7-2">It applies to IESG and IAB Members, the NomCom-appointed 
         IETF Trust Trustees, and the NomCom-appointed IETF LLC Directors.<a href="#section-7-2" class="pilcrow">¶</a></p>
<div id="recall_petition">
<section id="section-7.1">
        <h3 id="name-petition">
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-petition" class="section-name selfRef">Petition</a>
        </h3>
<p id="section-7.1-1">At any time, a signed petition (email is acceptable) may be
        submitted to the Internet Society President to request the recall
        of any sitting IESG or IAB member, or NomCom-appointed IETF Trust
        Trustee, or NomCom-appointed IETF LLC Director. There are two
        different types of petitions: a petition by participants of the IETF
        community, and a petition by the Ombudsteam as described in <span>[<a href="#RFC7776" class="xref">RFC7776</a>]</span>.<a href="#section-7.1-1" class="pilcrow">¶</a></p>
<div id="c_petition">
<section id="section-7.1.1">
          <h4 id="name-community-petition">
<a href="#section-7.1.1" class="section-number selfRef">7.1.1. </a><a href="#name-community-petition" class="section-name selfRef">Community Petition</a>
          </h4>
<p id="section-7.1.1-1">A recall petition can be made by at least 20 members of the
         IETF community who are qualified to be voting members of a
         NomCom. All individual and collective qualifications of NomCom
         eligibility are applicable, including that no more than two
         signatories may have the same primary affiliation.<a href="#section-7.1.1-1" class="pilcrow">¶</a></p>
<p id="section-7.1.1-2">Each signature must include a full name, email address, and
         primary company or organization affiliation.<a href="#section-7.1.1-2" class="pilcrow">¶</a></p>
<p id="section-7.1.1-3">The IETF Secretariat is responsible for confirming that each
         signatory is qualified to be a voting member of a NomCom.  A
         valid petition must be signed by at least 20 qualified
         signatories.<a href="#section-7.1.1-3" class="pilcrow">¶</a></p>
<p id="section-7.1.1-4">The petition must include a statement of justification for
         the recall and all relevant and appropriate supporting
         documentation.<a href="#section-7.1.1-4" class="pilcrow">¶</a></p>
<p id="section-7.1.1-5">The petition and its signatories must be announced to the
         IETF community.<a href="#section-7.1.1-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="o_petition">
<section id="section-7.1.2">
          <h4 id="name-ombudsteam-petition">
<a href="#section-7.1.2" class="section-number selfRef">7.1.2. </a><a href="#name-ombudsteam-petition" class="section-name selfRef">Ombudsteam Petition</a>
          </h4>
<p id="section-7.1.2-1">The Ombudsteam process allows the Ombudsteam to form a recall
        petition on its own without requiring 20 signatories from the
        community.  As defined in <span>[<a href="#RFC7776" class="xref">RFC7776</a>]</span>, the petition
        and its signatories (the Ombudsteam) shall be announced to the
        IETF community, and a Recall Committee Chair shall be appointed
        to complete the recall committee process.  It is expected that
        the recall committee will receive a briefing from the Ombudsteam
        explaining why recall is considered an appropriate remedy.<a href="#section-7.1.2-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="recall_chair">
<section id="section-7.2">
        <h3 id="name-recall-committee-chair">
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-recall-committee-chair" class="section-name selfRef">Recall Committee Chair</a>
        </h3>
<p id="section-7.2-1"> The Internet Society President shall appoint a Recall
     Committee Chair.<a href="#section-7.2-1" class="pilcrow">¶</a></p>
<p id="section-7.2-2"> The Internet Society President must not evaluate the
     recall request.  It is explicitly the responsibility
     of the IETF community to evaluate the behavior of
     its leaders.<a href="#section-7.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="recall_cmte">
<section id="section-7.3">
        <h3 id="name-recall-committee-creation">
<a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-recall-committee-creation" class="section-name selfRef">Recall Committee Creation</a>
        </h3>
<p id="section-7.3-1"> The recall committee is created according to the
     same rules as is the NomCom with the
     qualifications that both the person being
     investigated and the parties requesting the recall
     must not be a member of the recall committee in any
     capacity.<a href="#section-7.3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="recall_rules">
<section id="section-7.4">
        <h3 id="name-recall-committee-rules">
<a href="#section-7.4" class="section-number selfRef">7.4. </a><a href="#name-recall-committee-rules" class="section-name selfRef">Recall Committee Rules</a>
        </h3>
<p id="section-7.4-1"> The recall committee operates according to the same
     rules as the NomCom with the
     qualification that there is no confirmation
     process.<a href="#section-7.4-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="recall_ops">
<section id="section-7.5">
        <h3 id="name-recall-committee-operation">
<a href="#section-7.5" class="section-number selfRef">7.5. </a><a href="#name-recall-committee-operation" class="section-name selfRef">Recall Committee Operation</a>
        </h3>
<p id="section-7.5-1"> The recall committee investigates the circumstances
     of the justification for the recall and votes on
     its findings.<a href="#section-7.5-1" class="pilcrow">¶</a></p>
<p id="section-7.5-2"> The investigation must include at least both an
     opportunity for the member being recalled to present
     a written statement and consultation with third
     parties.<a href="#section-7.5-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="recall_maj">
<section id="section-7.6">
        <h3 id="name-3-4-majority">
<a href="#section-7.6" class="section-number selfRef">7.6. </a><a href="#name-3-4-majority" class="section-name selfRef">3/4 Majority</a>
        </h3>
<p id="section-7.6-1"> A 3/4 majority of the members who vote on the
     question is required for a recall.<a href="#section-7.6-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="recall_position">
<section id="section-7.7">
        <h3 id="name-position-to-be-filled">
<a href="#section-7.7" class="section-number selfRef">7.7. </a><a href="#name-position-to-be-filled" class="section-name selfRef">Position to Be Filled</a>
        </h3>
<p id="section-7.7-1"> If a sitting member is recalled, the open position is
     to be filled according to the mid-term vacancy
     rules.<a href="#section-7.7-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="IANA">
<section id="section-8">
      <h2 id="name-iana-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-8-1">This document has no IANA actions.<a href="#section-8-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="security">
<section id="section-9">
      <h2 id="name-security-considerations">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-9-1"> Any selection, confirmation, or recall process
     necessarily involves investigation into the qualifications
     and activities of prospective candidates.  The
     investigation may reveal confidential or otherwise private
     information about candidates to those participating in the
     process.  Each person who participates in any aspect of
     the process must maintain the confidentiality of any and
     all information not explicitly identified as suitable for
     public dissemination.<a href="#section-9-1" class="pilcrow">¶</a></p>
<p id="section-9-2"> When the NomCom decides it is necessary to share
 confidential or otherwise private information with
 others, the dissemination must be minimal and must
 include a prior commitment from all persons consulted to
 observe the same confidentiality rules as the NomCom
 itself.<a href="#section-9-2" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-10">
      <h2 id="name-references">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-10.1">
        <h3 id="name-normative-references">
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="RFC3777">[RFC3777]</dt>
<dd>
<span class="refAuthor">Galvin, J., Ed.</span>, <span class="refTitle">"IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees"</span>, <span class="seriesInfo">RFC 3777</span>, <span class="seriesInfo">DOI 10.17487/RFC3777</span>, <time datetime="2004-06">June 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3777">https://www.rfc-editor.org/info/rfc3777</a>&gt;</span>. </dd>
<dt id="RFC7437">[RFC7437]</dt>
<dd>
<span class="refAuthor">Kucherawy, M., Ed.</span>, <span class="refTitle">"IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees"</span>, <span class="seriesInfo">BCP 10</span>, <span class="seriesInfo">RFC 7437</span>, <span class="seriesInfo">DOI 10.17487/RFC7437</span>, <time datetime="2015-01">January 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7437">https://www.rfc-editor.org/info/rfc7437</a>&gt;</span>. </dd>
<dt id="RFC7776">[RFC7776]</dt>
<dd>
<span class="refAuthor">Resnick, P.</span><span class="refAuthor"> and A. Farrel</span>, <span class="refTitle">"IETF Anti-Harassment Procedures"</span>, <span class="seriesInfo">BCP 25</span>, <span class="seriesInfo">RFC 7776</span>, <span class="seriesInfo">DOI 10.17487/RFC7776</span>, <time datetime="2016-03">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7776">https://www.rfc-editor.org/info/rfc7776</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>
<dt id="RFC8714">[RFC8714]</dt>
<dd>
<span class="refAuthor">Arkko, J.</span><span class="refAuthor"> and T. Hardie</span>, <span class="refTitle">"Update to the Process for Selection of Trustees for the IETF Trust"</span>, <span class="seriesInfo">BCP 101</span>, <span class="seriesInfo">RFC 8714</span>, <span class="seriesInfo">DOI 10.17487/RFC8714</span>, <time datetime="2020-02">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8714">https://www.rfc-editor.org/info/rfc8714</a>&gt;</span>. </dd>
<dt id="RFC8717">[RFC8717]</dt>
<dd>
<span class="refAuthor">Klensin, J., Ed.</span>, <span class="refTitle">"IETF Administrative Support Activity 2.0: Consolidated Updates to IETF Administrative Terminology"</span>, <span class="seriesInfo">BCP 101</span>, <span class="seriesInfo">RFC 8717</span>, <span class="seriesInfo">DOI 10.17487/RFC8717</span>, <time datetime="2020-02">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8717">https://www.rfc-editor.org/info/rfc8717</a>&gt;</span>. </dd>
</dl>
</section>
<section id="section-10.2">
        <h3 id="name-informative-references">
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="Err232">[Err232]</dt>
<dd>
<span class="refAuthor">RFC Errata</span>, <span class="refTitle">Erratum ID 232</span>, <span class="refContent">RFC 3777</span>, <span>&lt;<a href="https://www.rfc-editor.org/errata/eid232">https://www.rfc-editor.org/errata/eid232</a>&gt;</span>. </dd>
<dt id="Err4179">[Err4179]</dt>
<dd>
<span class="refAuthor">RFC Errata</span>, <span class="refTitle">Erratum ID 4179</span>, <span class="refContent">RFC 3777</span>, <span>&lt;<a href="https://www.rfc-editor.org/errata/eid4179">https://www.rfc-editor.org/errata/eid4179</a>&gt;</span>. </dd>
<dt id="RFC3710">[RFC3710]</dt>
<dd>
<span class="refAuthor">Alvestrand, H.</span>, <span class="refTitle">"An IESG charter"</span>, <span class="seriesInfo">RFC 3710</span>, <span class="seriesInfo">DOI 10.17487/RFC3710</span>, <time datetime="2004-02">February 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3710">https://www.rfc-editor.org/info/rfc3710</a>&gt;</span>. </dd>
<dt id="RFC3797">[RFC3797]</dt>
<dd>
<span class="refAuthor">Eastlake 3rd, D.</span>, <span class="refTitle">"Publicly Verifiable Nominations Committee (NomCom) Random Selection"</span>, <span class="seriesInfo">RFC 3797</span>, <span class="seriesInfo">DOI 10.17487/RFC3797</span>, <time datetime="2004-06">June 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3797">https://www.rfc-editor.org/info/rfc3797</a>&gt;</span>. </dd>
<dt id="RFC8318">[RFC8318]</dt>
<dd>
<span class="refAuthor">Dawkins, S.</span>, <span class="refTitle">"IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating Committee"</span>, <span class="seriesInfo">BCP 10</span>, <span class="seriesInfo">RFC 8318</span>, <span class="seriesInfo">DOI 10.17487/RFC8318</span>, <time datetime="2018-01">January 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8318">https://www.rfc-editor.org/info/rfc8318</a>&gt;</span>. </dd>
</dl>
</section>
</section>
<div id="changes">
<section id="section-appendix.a">
      <h2 id="name-changes-since-rfc-3777">
<a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-changes-since-rfc-3777" class="section-name selfRef">Changes Since RFC 3777</a>
      </h2>
<ul>
<li id="section-appendix.a-1.1">  Converted source file from nroff to XML,
 resulting in some reformatting.<a href="#section-appendix.a-1.1" class="pilcrow">¶</a>
</li>
<li id="section-appendix.a-1.2"> Applied errata for RFC 3777 (<span>[<a href="#Err232" class="xref">Err232</a>]</span>
     and <span>[<a href="#Err4179" class="xref">Err4179</a>]</span>).<a href="#section-appendix.a-1.2" class="pilcrow">¶</a>
</li>
<li id="section-appendix.a-1.3"> Applied RFC 5078 update.<a href="#section-appendix.a-1.3" class="pilcrow">¶</a>
</li>
<li id="section-appendix.a-1.4"> Applied RFC 5633 update.<a href="#section-appendix.a-1.4" class="pilcrow">¶</a>
</li>
<li id="section-appendix.a-1.5"> Applied RFC 5680 update.<a href="#section-appendix.a-1.5" class="pilcrow">¶</a>
</li>
<li id="section-appendix.a-1.6"> Applied RFC 6859 update.<a href="#section-appendix.a-1.6" class="pilcrow">¶</a>
</li>
<li id="section-appendix.a-1.7"> Corrected a few grammatical errors.<a href="#section-appendix.a-1.7" class="pilcrow">¶</a>
</li>
<li id="section-appendix.a-1.8"> Added a reference to RFC 3710.<a href="#section-appendix.a-1.8" class="pilcrow">¶</a>
</li>
</ul>
</section>
</div>
<div id="changes7437">
<section id="section-appendix.b">
      <h2 id="name-changes-since-rfc-7437">
<a href="#section-appendix.b" class="section-number selfRef">Appendix B. </a><a href="#name-changes-since-rfc-7437" class="section-name selfRef">Changes Since RFC 7437</a>
      </h2>
<ul>
<li id="section-appendix.b-1.1"> Changed all mentions of the Internet Administrative
 Oversight committee (IAOC), and replaced it with the
 appropriate references to the IETF Administration LLC
 (IETF LLC).  This included making changes on an as needed
 basis to some aspects of the process for the IETF LLC, in
 accordance with IASA2.<a href="#section-appendix.b-1.1" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.2">Revised definition of IETF Executive Director, and
               added definition of "Managing Director, IETF Secretariat".
               Changed text to "Managing Director, IETF Secretariat"
               where appropriate.<a href="#section-appendix.b-1.2" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.3">Added references to appropriate IASA2 documents.<a href="#section-appendix.b-1.3" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.4">Modified the Advice and Consent model to enable IESG,
 IAB, and IETF LLC to communicate directly with the NomCom
 rather than via the Managing Director, IETF
 Secretariat.<a href="#section-appendix.b-1.4" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.5">Updated removal text to reflect the new LLC rules, which 
 enables removal via the LLC or the IETF recall process, except for 
 the ISOC-appointed Director.<a href="#section-appendix.b-1.5" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.6">Updated the document to clarify that there are members
                of the IAB and IESG, Trustees of the IETF Trust, and
                Director of the IETF LLC.<a href="#section-appendix.b-1.6" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.7">Updated document to also specify procedures for the
          NomCom-appointed IETF Trust Trustees.<a href="#section-appendix.b-1.7" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.8">Revised Abstract and Introduction to provide current
 context.<a href="#section-appendix.b-1.8" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.9">Changed "nominating committee" to "NomCom" throughout
               the document because it is what most use to describe the
               IETF Nominating Committee.<a href="#section-appendix.b-1.9" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.10">Added that the IETF Trust Trustees and IETF LLC
               Directors, each may appoint a liaison to the NomCom.<a href="#section-appendix.b-1.10" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.11">Incorporated the update to RFC 7437 done by <span>[<a href="#RFC7776" class="xref">RFC7776</a>]</span>.<a href="#section-appendix.b-1.11" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.12">Incorporated the update to RFC 7437 done by <span>[<a href="#RFC8318" class="xref">RFC8318</a>]</span> 
               and updated it to refer to the IETF
               Trust and IETF LLC, instead of the IAOC.<a href="#section-appendix.b-1.12" class="pilcrow">¶</a>
</li>
<li id="section-appendix.b-1.13">Editorial changes.<a href="#section-appendix.b-1.13" class="pilcrow">¶</a>
</li>
</ul>
</section>
</div>
<div id="oral">
<section id="section-appendix.c">
      <h2 id="name-oral-tradition">
<a href="#section-appendix.c" class="section-number selfRef">Appendix C. </a><a href="#name-oral-tradition" class="section-name selfRef">Oral Tradition</a>
      </h2>
<p id="section-appendix.c-1"> Over the years, various NomComs have learned
     through oral tradition passed on by liaisons that there are
     certain consistencies in the process and information
     considered during deliberations.  Some items from that oral
     tradition are collected here to facilitate its consideration
     by future NomComs.<a href="#section-appendix.c-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-appendix.c-2">
        <li id="section-appendix.c-2.1"> It has been found that experience as an IETF
     Working Group Chair or an IRTF Research Group Chair
     is helpful in giving a nominee experience of what
     the job of an Area Director involves.  It also
     helps a NomCom judge the technical,
     people, and process management skills of the
     nominee.<a href="#section-appendix.c-2.1" class="pilcrow">¶</a>
</li>
<li id="section-appendix.c-2.2"> No person should serve both on the IAB and as an
     Area Director, except the IETF Chair whose roles as
     an IAB member and Area Director of the General Area
     are set out elsewhere.<a href="#section-appendix.c-2.2" class="pilcrow">¶</a>
</li>
<li id="section-appendix.c-2.3"> The strength of the IAB is found in part in the
     balance of the demographics of its members (e.g.,
     national distribution, years of experience, gender,
     etc.), the combined skill set of its members, and
     the combined sectors (e.g., industry, academia,
     etc.) represented by its members.<a href="#section-appendix.c-2.3" class="pilcrow">¶</a>
</li>
<li id="section-appendix.c-2.4"> There are no term limits for IAB and IESG
 members explicitly because the issue of
 continuity versus turnover should be evaluated
 each year according to the expectations of the
 IETF community, as it is understood by each
 NomCom.<a href="#section-appendix.c-2.4" class="pilcrow">¶</a>
</li>
<li id="section-appendix.c-2.5"> The number of NomCom members with the
     same primary affiliation is limited in order to
     avoid the appearance of improper bias in choosing
     the leadership of the IETF.  Rather than defining
     precise rules for how to define "affiliation", the
     IETF community depends on the honor and integrity of
     the participants to make the process work.<a href="#section-appendix.c-2.5" class="pilcrow">¶</a>
</li>
</ol>
</section>
</div>
<div id="timeline">
<section id="section-appendix.d">
      <h2 id="name-nominating-committee-timeli">
<a href="#section-appendix.d" class="section-number selfRef">Appendix D. </a><a href="#name-nominating-committee-timeli" class="section-name selfRef">Nominating Committee Timeline</a>
      </h2>
<p id="section-appendix.d-1"> This appendix is included for the convenience of the reader
     and is not to be interpreted as the definitive timeline.
     It is intended to capture the detail described elsewhere in
     this document in one place.  Although every effort has been
     made to ensure the description here is consistent with the
     description elsewhere, if there are any conflicts the
     definitive rule is the one in the main body of this
     document.<a href="#section-appendix.d-1" class="pilcrow">¶</a></p>
<p id="section-appendix.d-2"> The only absolute in the timeline rules for the annual
     process is that its completion is due by the First IETF of
     the year after the NomCom begins its term.
     This is supported by the fact that the confirmed candidate
     terms begin during the week of the First IETF.<a href="#section-appendix.d-2" class="pilcrow">¶</a></p>
<p id="section-appendix.d-3"> The overall annual process is designed to be completed in
     seven months.  It is expected to start nine months prior to
     the First IETF.  The time is split between three
     major components of the process roughly as follows:<a href="#section-appendix.d-3" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-appendix.d-4">
        <li id="section-appendix.d-4.1"> First is the selection and organization of the
     committee members.  Three months are allotted for
     this process.<a href="#section-appendix.d-4.1" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-4.2"> Second is the selection of the candidates by the
     NomCom.  Four months are allotted
     for this process.<a href="#section-appendix.d-4.2" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-4.3"> Third is the confirmation of the candidates by
     their respective confirming bodies.  Two months are
     allotted for this process.<a href="#section-appendix.d-4.3" class="pilcrow">¶</a>
</li>
</ol>
<p id="section-appendix.d-5"> The following list captures the details of the milestones
     within each component.  For illustrative purposes, the
     list presumes the Friday before the First IETF is
     March 1.  Numbers shown in square brackets indicate the
     expected number of weeks at each step.<a href="#section-appendix.d-5" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-appendix.d-6">
        <li id="section-appendix.d-6.1"> BEGIN Eight Months Prior to First
 IETF (approx. June 1); Internet Society
 President appoints the Chair.  The appointment
 must be done no later than the Second IETF or
 eight months prior to the First IETF, whichever
 comes first.  The Chair must be announced and
 recognized during a plenary session of the
 Second IETF. [0]<a href="#section-appendix.d-6.1" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.2"> The Chair establishes and announces
 milestones to ensure the timely selection of the
 NomCom members. [1]<a href="#section-appendix.d-6.2" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.3"> The Chair contacts the IESG, IAB,
 and Internet Society Board of Trustees,
                                IETF Trust, and IETF LLC
 and requests a liaison.  The Chair contacts
 the prior year's Chair and requests an
 advisor.  The Chair obtains the list of IESG,
 IAB, IETF Trust, and IETF LLC open positions and descriptions
 from the chairs of each group. [0]<a href="#section-appendix.d-6.3" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.4"> The Chair announces the solicitation
 for voting volunteer members that must remain
 open for at least 30 days.  The announcement
 must be done no later than seven months and two
 weeks prior to the First IETF (approx. June
 15). [6]<a href="#section-appendix.d-6.4" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.5"> After the solicitation closes, the
 Chair announces the pool of volunteers and the
 date of the random selection, which must be at
 least one week in the future.  The announcement
 must be done no later than six months and two
 weeks prior to the First IETF (approx. July
 15). [1]<a href="#section-appendix.d-6.5" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.6"> On the appointed day, the random
 selection occurs and the Chair announces the
 members of the committee and the one week
 challenge period.  The announcement must be done
 no later than six months and one week prior to
 the First IETF (approx. July 22). [1]<a href="#section-appendix.d-6.6" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.7"> During the challenge period, the Chair
 contacts each of the committee members and
 confirms their availability to participate.
 [0]<a href="#section-appendix.d-6.7" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.8"> After the challenge period closes, the
 Chair announces the members of the committee and
 its term begins.  The announcement must be done
 no later than six months prior to the First
 IETF (approx. August 1). [1]<a href="#section-appendix.d-6.8" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.9"> The committee has one month during
 which it is to self-organize in preparation for
 completing its assigned duties.  This must be
 done no later than five months prior to the
 First IETF (approx. September 15). [6]<a href="#section-appendix.d-6.9" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.10"> END the Committee Member Selection
 Process; BEGIN the Selection of Candidates; Time
 is at least five months prior to the First IETF
 (approx. September 22). [0]<a href="#section-appendix.d-6.10" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.11"> The Chair establishes and announces
 the milestones to ensure the timely selection of
 the candidates, including a call for nominations
 for the open positions.  The announcement must
 be done no later than five months prior to the
 First IETF (approx. October 1). [1]<a href="#section-appendix.d-6.11" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.12"> Over the next three months, the
 NomCom collects input and
 deliberates.  It should plan to conduct
 interviews and other consultations during the
 Third IETF.  The committee is due to complete
 its candidate selection no later than two
 months prior to the First IETF (approx. January
 1). [17]<a href="#section-appendix.d-6.12" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.13"> END the Selection of Candidates;
 BEGIN the Confirmation of Candidates; Time is
 at least two months prior to the First IETF
 (approx. January 1). [0]<a href="#section-appendix.d-6.13" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.14"> The committee presents its candidates
 to their respective confirming bodies.  The
 presentation must be done no later than two
 months prior to the First IETF (approx.
 January 1). [0]<a href="#section-appendix.d-6.14" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.15"> The confirming bodies have one month
 to deliberate and, in communication with the
 NomCom, accept or reject
 candidates. [4]<a href="#section-appendix.d-6.15" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.16"> The Chair notifies and advises
 unsuccessful nominees that they have not been
 selected. [1]<a href="#section-appendix.d-6.16" class="pilcrow">¶</a>
</li>
<li id="section-appendix.d-6.17"> The Chair announces the confirmed
 candidates.  The announcement must be done no
 later than one month prior to the First IETF
 (approx. February 1). [4]<a href="#section-appendix.d-6.17" class="pilcrow">¶</a>
</li>
</ol>
</section>
</div>
<div id="thanks">
<section id="section-appendix.e">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="section-appendix.e-1"> A great deal of work went into the RFCs that preceded
     this one.  The 2014 NomCom and this editor
     would like to thank all of them once again for the time
     and energy it took to get us to where we are now.  In
     no particular order, we acknowledge:<a href="#section-appendix.e-1" class="pilcrow">¶</a></p>
<p id="section-appendix.e-2">
<span class="contact-name">Jeff Case</span>,
<span class="contact-name">Fred Baker</span>,
<span class="contact-name">John Curran</span>,
<span class="contact-name">Guy Almes</span>,
<span class="contact-name">Geoff Huston</span>,
<span class="contact-name">Michael StJohns</span>,
<span class="contact-name">Donald Eastlake</span>,
<span class="contact-name">Avri Doria</span>,
<span class="contact-name">Bernard Aboba</span>,
<span class="contact-name">Ted T'so</span>,
<span class="contact-name">Phil Roberts</span>,
<span class="contact-name">Jim Galvin</span>,
<span class="contact-name">Harald Alvestrand</span>,
<span class="contact-name">Leslie Daigle</span>,
<span class="contact-name">Joel Halpern</span>,
<span class="contact-name">Thomas Narten</span>,
<span class="contact-name">Spencer Dawkins</span>,
<span class="contact-name">Barry Leiba</span>,
<span class="contact-name">Lars Eggert</span>,
<span class="contact-name">Ross Callon</span>,
<span class="contact-name">Brian Carpenter</span>,
<span class="contact-name">Robert Elz</span>,
<span class="contact-name">Bernie Hoeneisen</span>,
<span class="contact-name">John Klensin</span>,
<span class="contact-name">Danny McPherson</span>,
<span class="contact-name">S. Moonesamy</span>,
<span class="contact-name">Scott Bradner</span>,
<span class="contact-name">Ralph Droms</span>, and
<span class="contact-name">Pekka Savola</span>.<a href="#section-appendix.e-2" class="pilcrow">¶</a></p>
<p id="section-appendix.e-3"><span class="contact-name">Allison Mankin</span> and <span class="contact-name">Russ White</span> provided early reviews
     and feedback about this document.<a href="#section-appendix.e-3" class="pilcrow">¶</a></p>
<p id="section-appendix.e-4"><span class="contact-name">Jari Arkko</span> was very helpful by independently verifying
     that the previous text from all the merged documents was
     marshaled correctly into this one, and <span class="contact-name">Adrian Farrel</span>
     and <span class="contact-name">Brian Carpenter</span> caught the nits that fell through
     the cracks.<a href="#section-appendix.e-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="section-appendix.f">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Murray S. Kucherawy (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="street-address">270 Upland Drive</span></div>
<div dir="auto" class="left">
<span class="locality">San Francisco</span>, <span class="region">CA</span> <span class="postal-code">94127</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:superuser@gmail.com" class="email">superuser@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Robert M. Hinden (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Check Point Software</span></div>
<div dir="auto" class="left">
<span class="locality">San Carlos</span>, <span class="region">CA</span> </div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:bob.hinden@gmail.com" class="email">bob.hinden@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Jason Livingood (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Comcast</span></div>
<div dir="auto" class="left">
<span class="locality">Philadelphia</span>, <span class="region">PA</span> </div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:jason_livingood@comcast.com" class="email">jason_livingood@comcast.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>