File: rfc9281.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 (1938 lines) | stat: -rw-r--r-- 77,919 bytes
<!DOCTYPE html>
<html lang="en" class="BCP RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 9281: Entities Involved in the IETF Standards Process</title>
<meta content="Rich Salz" name="author">
<meta content="
       This document describes the individuals and organizations involved in
the IETF standards process, as described in BCP 9.
It includes brief descriptions of the entities involved
and the role they play in the standards process. 
       The IETF and its structure have undergone many changes since RFC
2028 was published in 1996.  This document reflects the changed organizational
structure of the IETF and obsoletes RFC 2028. 
    " name="description">
<meta content="xml2rfc 3.12.10" name="generator">
<meta content="IESG" name="keyword">
<meta content="RFC Editor" name="keyword">
<meta content="IRTF" name="keyword">
<meta content="IETF LLC" name="keyword">
<meta content="ISOC" name="keyword">
<meta content="registries" name="keyword">
<meta content="IANA" name="keyword">
<meta content="9281" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.12.10
    Python 3.6.15
    appdirs 1.4.4
    ConfigArgParse 1.4.1
    google-i18n-address 2.4.0
    html5lib 1.0.1
    intervaltree 3.0.2
    Jinja2 2.11.3
    kitchen 1.2.6
    lxml 4.7.1
    MarkupSafe 2.0.1
    pycairo 1.15.1
    pycountry 19.8.18
    pyflakes 2.1.1
    PyYAML 5.4.1
    requests 2.24.0
    setuptools 40.5.0
    six 1.14.0
    WeasyPrint 52.5
-->
<link href="rfc9281.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;
  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.ulBare, li.ulBare {
  margin-left: 0em !important;
}
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;
}
/* Fix PDF info block run off issue */
@media print {
  #identifiers dd {
    float: none;
  }
}
#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;
  }
  pre.breakable {
    break-inside: auto;
  }
  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;
  }

}
/* 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-bottom: 0.25em;
  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;
  }
}
/* 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; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: auto;
  break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
  break-before: auto;
  break-inside: auto;
}
dt {
  break-before: auto;
  break-after: avoid-page;
}
dd {
  break-before: avoid-page;
  break-after: auto;
  orphans: 3;
  widows: 3
}
span.break, dd.break {
  margin-bottom: 0;
  min-height: 0;
  break-before: auto;
  break-inside: auto;
  break-after: auto;
}
/* Undo break-before ToC */
@media print {
  #toc {
    break-before: auto;
  }
}
/* Text in compact lists should not get extra bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
  clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
  content: "\00a0";
}
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
li > p {
  margin-bottom: 0.5em
}
/* Don't let p margin spill out from inside list items */
li > p:last-of-type {
  margin-bottom: 0;
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc9281" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-rsalz-2028bis-07" 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 9281</td>
<td class="center">Entities in IETF Standards Process</td>
<td class="right">June 2022</td>
</tr></thead>
<tfoot><tr>
<td class="left">Salz</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/rfc9281" class="eref">9281</a></dd>
<dt class="label-bcp">BCP:</dt>
<dd class="bcp">11</dd>
<dt class="label-obsoletes">Obsoletes:</dt>
<dd class="obsoletes">
<a href="https://www.rfc-editor.org/rfc/rfc2028" class="eref">2028</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="2022-06" class="published">June 2022</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Author:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">R. Salz</div>
<div class="org">Akamai Technologies</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9281</h1>
<h1 id="title">Entities Involved in the IETF Standards Process</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document describes the individuals and organizations involved in
the IETF standards process, as described in BCP 9.
It includes brief descriptions of the entities involved
and the role they play in the standards process.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
<p id="section-abstract-2">The IETF and its structure have undergone many changes since RFC
2028 was published in 1996.  This document reflects the changed organizational
structure of the IETF and obsoletes RFC 2028.<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/rfc9281">https://www.rfc-editor.org/info/rfc9281</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) 2022 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 Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised 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="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1">
                <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.2">
                <p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="xref">1.2</a>.  <a href="#name-changes-since-rfc-2028" class="xref">Changes since RFC 2028</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare 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-key-individuals-in-the-proc" class="xref">Key Individuals in the Process</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.1">
                <p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>.  <a href="#name-document-editor-or-author" class="xref">Document Editor or Author</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.2">
                <p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="xref">2.2</a>.  <a href="#name-working-group-chair" class="xref">Working Group Chair</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.3">
                <p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="xref">2.3</a>.  <a href="#name-area-director" class="xref">Area Director</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare 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-key-organizations-in-the-pr" class="xref">Key Organizations in the Process</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare 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-internet-engineering-task-f" class="xref">Internet Engineering Task Force (IETF)</a></p>
</li>
              <li class="compact toc ulBare 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-working-groups-wgs" class="xref">Working Groups (WGs)</a></p>
</li>
              <li class="compact toc ulBare 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-internet-engineering-steeri" class="xref">Internet Engineering Steering Group (IESG)</a></p>
</li>
              <li class="compact toc ulBare 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-internet-architecture-board" class="xref">Internet Architecture Board (IAB)</a></p>
</li>
              <li class="compact toc ulBare 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-rfc-production-center-rpc" class="xref">RFC Production Center (RPC)</a></p>
</li>
              <li class="compact toc ulBare 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-internet-assigned-numbers-a" class="xref">Internet Assigned Numbers Authority (IANA)</a></p>
</li>
              <li class="compact toc ulBare 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-internet-research-task-forc" class="xref">Internet Research Task Force (IRTF)</a></p>
</li>
              <li class="compact toc ulBare 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-ietf-trust" class="xref">IETF Trust</a></p>
</li>
              <li class="compact toc ulBare 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-ietf-administration-llc-iet" class="xref">IETF Administration LLC (IETF LLC)</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.10">
                <p id="section-toc.1-1.3.2.10.1"><a href="#section-3.10" class="xref">3.10</a>. <a href="#name-ietf-secretariat" class="xref">IETF Secretariat</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.11">
                <p id="section-toc.1-1.3.2.11.1"><a href="#section-3.11" class="xref">3.11</a>. <a href="#name-internet-society-isoc" class="xref">Internet Society (ISOC)</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare 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-security-considerations" class="xref">Security Considerations</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
</li>
          <li class="compact toc ulBare 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-informative-references" class="xref">Informative References</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#appendix-B" class="xref"></a><a href="#name-authors-address" class="xref">Author's Address</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<div id="introduction">
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">The process used by the IETF community for the standardization of
protocols and procedures is described in BCP 9 <span>[<a href="#IETFPROCS" class="xref">IETFPROCS</a>]</span>.
BCP 9 defines
the stages in the standardization process, the requirements for
moving a document between stages, and the types of documents used
during this process.
This document identifies some of the key individual roles and organizations
in that process.<a href="#section-1-1" class="pilcrow">¶</a></p>
<div id="terminology">
<section id="section-1.1">
        <h3 id="name-terminology">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
        </h3>
<p id="section-1.1-1">This document refers to individual roles in the singular,
such as "a document editor."
In reality, many roles are filled by more than one person at the same
time.
For clarity, this document does not use phrases like "chair (or co-chair)."<a href="#section-1.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="changes-since-rfc-2028">
<section id="section-1.2">
        <h3 id="name-changes-since-rfc-2028">
<a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-changes-since-rfc-2028" class="section-name selfRef">Changes since RFC 2028</a>
        </h3>
<p id="section-1.2-1">The following changes have been made, in no particular order:<a href="#section-1.2-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-1.2-2.1">Added the role of responsible area director (AD) and
reordered <a href="#individuals" class="xref">Section 2</a> to follow the typical workflow.<a href="#section-1.2-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.2">Added the IETF Administration LLC and the IETF Trust to <a href="#organizations" class="xref">Section 3</a>.<a href="#section-1.2-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.3">Changed "RFC Editor" to "RFC Production Center" to reflect the changes
made by <span>[<a href="#RFC9280" class="xref">RFCEDMODEL</a>]</span>.<a href="#section-1.2-2.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.4">Added the <a href="#terminology" class="xref">Terminology</a> and <a href="#acknowledgements" class="xref">Acknowledgements</a> sections.<a href="#section-1.2-2.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.5">Cleaned up some wording
throughout the document.<a href="#section-1.2-2.5" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
</section>
</div>
<div id="individuals">
<section id="section-2">
      <h2 id="name-key-individuals-in-the-proc">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-key-individuals-in-the-proc" class="section-name selfRef">Key Individuals in the Process</a>
      </h2>
<p id="section-2-1">This section describes the individual roles involved in the process.
It attempts to list the roles in the order in which they are involved
in the process, without otherwise expressing significance.<a href="#section-2-1" class="pilcrow">¶</a></p>
<div id="doceditor">
<section id="section-2.1">
        <h3 id="name-document-editor-or-author">
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-document-editor-or-author" class="section-name selfRef">Document Editor or Author</a>
        </h3>
<p id="section-2.1-1">Most working groups (WGs) focus their efforts on one or more documents
that capture their work results.  The WG chair designates one or more people
to serve as the editor(s)
for a particular document.  The editor is responsible for
ensuring that the contents of the document accurately reflect the
decisions that have been made by the WG.<a href="#section-2.1-1" class="pilcrow">¶</a></p>
<p id="section-2.1-2">When a document is composed and edited mainly by one or more individuals,
they may be referred to as "document authors". The distinction is
not significant for the standards process.
This document uses the term "document editor".<a href="#section-2.1-2" class="pilcrow">¶</a></p>
<p id="section-2.1-3">When a document editor is a chair of the same WG, another
chair should manage the process around the document. If another chair is not
available, the WG and AD must monitor the process especially carefully to ensure that the
resulting documents accurately reflect the consensus of the WG and
that all processes are followed. This is the collective obligation
of all parties involved in the document.<a href="#section-2.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="wgchair">
<section id="section-2.2">
        <h3 id="name-working-group-chair">
<a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-working-group-chair" class="section-name selfRef">Working Group Chair</a>
        </h3>
<p id="section-2.2-1">Each WG is headed by a chair who has
the responsibility for facilitating the group's activities, presiding
over the group's meetings, and ensuring that the commitments of the
group with respect to its role in the Internet standards process are
met. In particular, the WG chair is the formal point of contact
between the WG and the Internet Engineering Steering Group (IESG), via the AD of the area to
which the WG belongs.<a href="#section-2.2-1" class="pilcrow">¶</a></p>
<p id="section-2.2-2">The details on the selection and responsibilities of a WG
chair can be found in <span>[<a href="#WGPROCS" class="xref">WGPROCS</a>]</span>.<a href="#section-2.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="the-area-director">
<section id="section-2.3">
        <h3 id="name-area-director">
<a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-area-director" class="section-name selfRef">Area Director</a>
        </h3>
<p id="section-2.3-1">Each WG is assigned a single responsible area director (AD).
The AD can
assist the WG chair in assessing consensus and executing process.
The AD also reviews documents after the WG has approved them, and
when satisfied, the AD
coordinates the IESG review and IETF Last Call of
the document.<a href="#section-2.3-1" class="pilcrow">¶</a></p>
<p id="section-2.3-2">An AD can also sponsor an Internet-Draft directly, but this is not very common.
When this is done, a WG is not involved.<a href="#section-2.3-2" class="pilcrow">¶</a></p>
<p id="section-2.3-3">Except for the General Area,
IETF areas traditionally have multiple ADs.<a href="#section-2.3-3" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="organizations">
<section id="section-3">
      <h2 id="name-key-organizations-in-the-pr">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-key-organizations-in-the-pr" class="section-name selfRef">Key Organizations in the Process</a>
      </h2>
<p id="section-3-1">The following organizations and organizational roles are involved in
the Internet standards process.<a href="#section-3-1" class="pilcrow">¶</a></p>
<div id="internet-engineering-task-force-ietf">
<section id="section-3.1">
        <h3 id="name-internet-engineering-task-f">
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-internet-engineering-task-f" class="section-name selfRef">Internet Engineering Task Force (IETF)</a>
        </h3>
<p id="section-3.1-1">The IETF is an open international
community of network designers, operators, implementors, researchers,
and other interested parties who are
concerned with the evolution of the Internet architecture and the
smooth operation of the Internet.  It is the principal body engaged
in the development of new Internet Standard specifications and related documents.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="working-groups-wgs">
<section id="section-3.2">
        <h3 id="name-working-groups-wgs">
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-working-groups-wgs" class="section-name selfRef">Working Groups (WGs)</a>
        </h3>
<p id="section-3.2-1">The technical work of the IETF is done in its WGs, which
are organized by topics into several
<a href="https://www.ietf.org/topics/areas/">areas</a>,
each under the coordination of an AD.
WGs typically have a narrow focus and a lifetime bounded
by completion of specific tasks as defined in their charter
and milestones. Some WGs are long-lived and intended to conduct
ongoing maintenance on IETF protocol(s). There are also "dispatch" WGs
that assess where new work in the IETF should be done but do
not directly produce standards.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
<p id="section-3.2-2">For all purposes relevant to the Internet Standards development
process, membership in the IETF and its WGs is defined to
be established solely and entirely by individuals who
participate in
IETF and WG activities.
These individuals do not formally represent any organizations they may be affiliated with,
although affiliations are often used for identification.<a href="#section-3.2-2" class="pilcrow">¶</a></p>
<p id="section-3.2-3">Anyone with the time and interest to do so is entitled and urged to
participate actively in one or more WGs and to attend
IETF meetings, which are usually held
three times a year <span>[<a href="#RFC8719" class="xref">MEETINGS</a>]</span>.
A WG may also schedule interim meetings (virtual, in-person, or hybrid).
These are scheduled and announced to the entire WG.
Active WG participation is possible without attending
any in-person meetings.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
<p id="section-3.2-4">Participants in the IETF and its WGs must disclose
any relevant current or pending intellectual
property rights that are reasonably and personally known to the
participant if they participate in discussions about a specific
technology.
The full intellectual property policy is defined in <span>[<a href="#IPRRIGHTS1" class="xref">IPRRIGHTS1</a>]</span> and
<span>[<a href="#IPRRIGHTS2" class="xref">IPRRIGHTS2</a>]</span>.<a href="#section-3.2-4" class="pilcrow">¶</a></p>
<p id="section-3.2-5">New WGs are established by the IESG
and almost always have a specific and explicit charter.
The charter can be modified as the WG progresses.
The guidelines and procedures for the formation and
operation of WGs are described in detail in <span>[<a href="#WGPROCS" class="xref">WGPROCS</a>]</span>.<a href="#section-3.2-5" class="pilcrow">¶</a></p>
<p id="section-3.2-6">A WG is managed by a WG chair, as described in
<a href="#wgchair" class="xref">Section 2.2</a>.  Documents produced by the group have an editor, as
described in <a href="#doceditor" class="xref">Section 2.1</a>.  Further details of WG operation can
be found in <span>[<a href="#WGPROCS" class="xref">WGPROCS</a>]</span>.<a href="#section-3.2-6" class="pilcrow">¶</a></p>
<p id="section-3.2-7">WGs ideally display a spirit of cooperation as well as a high
degree of technical maturity; IETF participants recognize that the
greatest benefit for all members of the Internet community results
from cooperative development of technically excellent protocols and
services.<a href="#section-3.2-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="internet-engineering-steering-group-iesg">
<section id="section-3.3">
        <h3 id="name-internet-engineering-steeri">
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-internet-engineering-steeri" class="section-name selfRef">Internet Engineering Steering Group (IESG)</a>
        </h3>
<p id="section-3.3-1">The IESG is
responsible for the management of the IETF technical
activities.  It administers the Internet Standards process according
to the rules and procedures defined in <span>[<a href="#IETFPROCS" class="xref">IETFPROCS</a>]</span>.  The IESG is responsible
for the actions associated with the progression of documents
along the IETF Stream, including the initial
approval of new WGs, any subsequent
rechartering, and the final approval of
documents.  The IESG is composed of the
ADs and the IETF Chair. The IETF Chair also chairs the IESG and
is the AD for the General Area.
The Chair of the Internet Architecture Board (IAB) is an ex officio member of the IESG.
  Various other bodies have liaisons with the IESG;
  the full list can be found at
 <span>&lt;<a href="https://www.ietf.org/about/groups/iesg/members/">https://www.ietf.org/about/groups/iesg/members/</a>&gt;</span>.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
<p id="section-3.3-2">All members of the IESG are nominated by a Nominations Committee
(colloquially, "NomCom")
and are confirmed by the IAB.  See <span>[<a href="#NOMCOM" class="xref">NOMCOM</a>]</span> for a detailed
description of the NomCom procedures. Other matters concerning the
organization and operation of the NomCom are described in the IESG Charter <span>[<a href="#RFC3710" class="xref">IESG</a>]</span>.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="internet-architecture-board-iab">
<section id="section-3.4">
        <h3 id="name-internet-architecture-board">
<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-internet-architecture-board" class="section-name selfRef">Internet Architecture Board (IAB)</a>
        </h3>
<p id="section-3.4-1">The IAB provides oversight of the architecture of the Internet and its
protocols.  The IAB approves IESG candidates put forward by the
NomCom. It also reviews all proposed IETF WG charters.<a href="#section-3.4-1" class="pilcrow">¶</a></p>
<p id="section-3.4-2">The IAB provides oversight of the standards process
and serves as an appeal board for related complaints about improper
execution <span>[<a href="#IETFPROCS" class="xref">IETFPROCS</a>]</span>. In general, it acts as a source
of advice about
technical, architectural, procedural, and policy matters
pertaining to the Internet and its enabling technologies.<a href="#section-3.4-2" class="pilcrow">¶</a></p>
<p id="section-3.4-3">The members of the IAB are nominated by the NomCom
and are confirmed by the Board of the Internet Society (ISOC).
The IETF Chair is also a member of the IAB, and the
Chair of the Internet Research Task Force (IRTF) is an ex officio member.
Other
matters concerning the IAB's organization and operation are described in the IAB
Charter <span>[<a href="#IAB" class="xref">IAB</a>]</span>.<a href="#section-3.4-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="the-rfc-production-center-rpc">
<section id="section-3.5">
        <h3 id="name-rfc-production-center-rpc">
<a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-rfc-production-center-rpc" class="section-name selfRef">RFC Production Center (RPC)</a>
        </h3>
<p id="section-3.5-1">Editorial preparation and publication of RFCs are handled by the RFC
   Production Center (RPC).
RFC policy is defined by the RFC
Series Working Group (RSWG), an open group (similar to IETF WGs),
and approved by the RFC Series Advisory
Board (RSAB), which has appointed members.  The RFC Series Consulting Editor
   (RSCE) is a position funded by the IETF Administration LLC, with responsibilities defined in <span>[<a href="#RFC9280" class="xref">RFCEDMODEL</a>]</span>.<a href="#section-3.5-1" class="pilcrow">¶</a></p>
<p id="section-3.5-2">Full details on the roles and responsibilities of the RPC are specified in
<span>[<a href="#RFC9280" class="xref">RFCEDMODEL</a>]</span>, in particular Section <a href="https://www.rfc-editor.org/rfc/rfc9280#section-4" class="relref">4</a>.<a href="#section-3.5-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="internet-assigned-numbers-authority-iana">
<section id="section-3.6">
        <h3 id="name-internet-assigned-numbers-a">
<a href="#section-3.6" class="section-number selfRef">3.6. </a><a href="#name-internet-assigned-numbers-a" class="section-name selfRef">Internet Assigned Numbers Authority (IANA)</a>
        </h3>
<p id="section-3.6-1">Many protocol specifications include parameters that must be
        uniquely assigned.  Examples of this include port numbers, option
        identifiers within a protocol, and so on. The Internet Assigned
        Numbers Authority (IANA) is responsible for assigning values to these
        protocol parameters and maintaining parameter registries online (<span><a href="https://www.iana.org/protocols">https://www.iana.org/protocols</a></span>). Assignments are coordinated
        by writing an "IANA Considerations" section for a given document, as
        described in <span>[<a href="#IANADOCS" class="xref">IANADOCS</a>]</span>.  The IETF's
        relationship with IANA is defined by formal agreements, including
        <span>[<a href="#RFC2860" class="xref">IANAMOU</a>]</span>.<a href="#section-3.6-1" class="pilcrow">¶</a></p>
<p id="section-3.6-2">IANA is also responsible for operating and maintaining
<a href="https://www.iana.org/domains">several aspects of the DNS</a> and
<a href="https://www.iana.org/numbers">coordinating of IP address assignments</a>.<a href="#section-3.6-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="internet-research-task-force-irtf">
<section id="section-3.7">
        <h3 id="name-internet-research-task-forc">
<a href="#section-3.7" class="section-number selfRef">3.7. </a><a href="#name-internet-research-task-forc" class="section-name selfRef">Internet Research Task Force (IRTF)</a>
        </h3>
<p id="section-3.7-1">The IRTF focuses on longer-term research issues related to the Internet as a
parallel organization to the IETF, which
focuses on the shorter-term issues of engineering, operations, and
specification of standards.<a href="#section-3.7-1" class="pilcrow">¶</a></p>
<p id="section-3.7-2">The IRTF consists of a number of research groups (RGs) chartered to research
various aspects related to the broader Internet.
The products of these RGs are typically research results that are
often published in scholarly conferences and journals, but they can also be published
as RFCs on the IRTF Stream. RGs also
sometimes develop experimental protocols or technologies, some of which may be suitable
for possible standardization in IETF. Similarly, IETF WGs
sometimes ask RGs for advice or other input.  However, contributions from
RGs generally
carry no more weight in the IETF than other community input
and go through the same standards-setting process as any other proposal.<a href="#section-3.7-2" class="pilcrow">¶</a></p>
<p id="section-3.7-3">The IRTF is managed by the IRTF Chair in consultation with the Internet
Research Steering Group (IRSG).  The IRSG membership includes the IRTF Chair,
the chairs of the various RGs, and possibly other individuals
("members at large") from the community. Details of the organization
and operation of the IRTF, the ISRG, and its RGs may be found in
<span>[<a href="#RFC2014" class="xref">IRTF</a>]</span>, <span>[<a href="#RFC4440" class="xref">IABIRTF</a>]</span>, <span>[<a href="#RFC7418" class="xref">IRTFPRIMER</a>]</span>, and <span>[<a href="#RFC7827" class="xref">IRTFCHAIR</a>]</span>.<a href="#section-3.7-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="the-ietf-trust">
<section id="section-3.8">
        <h3 id="name-ietf-trust">
<a href="#section-3.8" class="section-number selfRef">3.8. </a><a href="#name-ietf-trust" class="section-name selfRef">IETF Trust</a>
        </h3>
<p id="section-3.8-1">The IETF Trust is the legal owner of intellectual
property for the IETF, IRTF, and IAB.
This includes their trademarks, the copyrights to RFCs and to works
of the IETF such as the IETF website, and
copyright licenses for IETF contributions including Internet-Drafts.
The principles for the copyright licenses granted to and from the
Trust are described in <span>[<a href="#IPRRIGHTS1" class="xref">IPRRIGHTS1</a>]</span>
and <span>[<a href="#RFC8721" class="xref">COPYRIGHT</a>]</span>, and the licenses themselves are in the
<a href="https://trustee.ietf.org/documents/trust-legal-provisions/">Trust Legal Provisions</a>.<a href="#section-3.8-1" class="pilcrow">¶</a></p>
<p id="section-3.8-2">The Trust also currently owns IANA's domain names and trademarks through an
agreement with IANA.<a href="#section-3.8-2" class="pilcrow">¶</a></p>
<p id="section-3.8-3">The Trustees that govern the Trust are selected from the IETF community, as
described in <span>[<a href="#RFC8714" class="xref">TRUSTEES</a>]</span> and the rationale given in <span>[<a href="#RFC8715" class="xref">TRUSTRAT</a>]</span>.<a href="#section-3.8-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="ietf-administration-llc-ietf-llc">
<section id="section-3.9">
        <h3 id="name-ietf-administration-llc-iet">
<a href="#section-3.9" class="section-number selfRef">3.9. </a><a href="#name-ietf-administration-llc-iet" class="section-name selfRef">IETF Administration LLC (IETF LLC)</a>
        </h3>
<p id="section-3.9-1">The IETF Administration Limited Liability Company
(colloquially, the "IETF LLC") provides
the corporate legal home for the IETF, the IAB, and the IRTF.<a href="#section-3.9-1" class="pilcrow">¶</a></p>
<p id="section-3.9-2">The IETF LLC is responsible for supporting the ongoing operations
of the IETF, managing its finances and budget, and raising money.
It regularly reports to the community.
The IETF LLC is the legal entity that signs contracts for the IETF
Secretariat, meeting hotels, tools development contractors, among many others.
The IETF LLC also responds to legal requests; these are often subpoenas
in patent lawsuits.<a href="#section-3.9-2" class="pilcrow">¶</a></p>
<p id="section-3.9-3">Selection of the IETF LLC Board of Directors is defined in <span>[<a href="#NOMCOM" class="xref">NOMCOM</a>]</span>.<a href="#section-3.9-3" class="pilcrow">¶</a></p>
<p id="section-3.9-4">The IETF Executive Director handles the IETF's daily tasks and management
and is overseen by the IETF LLC Board of Directors.<a href="#section-3.9-4" class="pilcrow">¶</a></p>
<p id="section-3.9-5"><span><a href="https://www.rfc-editor.org/rfc/rfc8712#section-6" class="relref">Section 6</a> of [<a href="#RFC8712" class="xref">ISOCIETF</a>]</span> describes the legal relationship between the IETF
LLC and the Internet Society.<a href="#section-3.9-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="ietf-secretariat">
<section id="section-3.10">
        <h3 id="name-ietf-secretariat">
<a href="#section-3.10" class="section-number selfRef">3.10. </a><a href="#name-ietf-secretariat" class="section-name selfRef">IETF Secretariat</a>
        </h3>
<p id="section-3.10-1">The administrative functions necessary to support the activities of
the IETF and its various related boards and organizations
are performed by a Secretariat contracted by the IETF LLC.
The IETF Secretariat handles much of the logistics of running the in-person
meetings and is responsible for
maintaining the formal public record of the Internet standards
process <span>[<a href="#IETFPROCS" class="xref">IETFPROCS</a>]</span>.<a href="#section-3.10-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="internet-society-isoc">
<section id="section-3.11">
        <h3 id="name-internet-society-isoc">
<a href="#section-3.11" class="section-number selfRef">3.11. </a><a href="#name-internet-society-isoc" class="section-name selfRef">Internet Society (ISOC)</a>
        </h3>
<p id="section-3.11-1">ISOC plays an important role in the standards process.
In addition to being the legal entity that hosts the IETF LLC,
ISOC appoints the NomCom Chair, confirms IAB candidates selected by the NomCom,
and acts as the final authority in the appeals process.
This is described in <span>[<a href="#RFC8712" class="xref">ISOCIETF</a>]</span>.<a href="#section-3.11-1" class="pilcrow">¶</a></p>
<p id="section-3.11-2">The way in which the ISOC leadership is
selected and other matters concerning the operation of the Internet
Society are described in <span>[<a href="#ISOC" class="xref">ISOC</a>]</span>.<a href="#section-3.11-2" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="security-considerations">
<section id="section-4">
      <h2 id="name-security-considerations">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-4-1">This document introduces no new security considerations.<a href="#section-4-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="iana-considerations">
<section id="section-5">
      <h2 id="name-iana-considerations">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-5-1">This document has no IANA actions.<a href="#section-5-1" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-6">
      <h2 id="name-informative-references">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
      </h2>
<dl class="references">
<dt id="RFC8721">[COPYRIGHT]</dt>
      <dd>
<span class="refAuthor">Halpern, J., Ed.</span>, <span class="refTitle">"Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents"</span>, <span class="seriesInfo">RFC 8721</span>, <span class="seriesInfo">DOI 10.17487/RFC8721</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8721">https://www.rfc-editor.org/info/rfc8721</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="IAB">[IAB]</dt>
      <dd>
<div class="refInstance" id="RFC2850">
          <span class="refAuthor">Internet Architecture Board</span> and <span class="refAuthor">B. Carpenter, Ed.</span>, <span class="refTitle">"Charter of the Internet Architecture Board (IAB)"</span>, <span class="seriesInfo">BCP 39</span>, <span class="seriesInfo">RFC 2850</span>, <time datetime="2000-05" class="refDate">May 2000</time>. </div>
<span>&lt;<a href="https://www.rfc-editor.org/info/bcp39">https://www.rfc-editor.org/info/bcp39</a>&gt;</span>
</dd>
<dd class="break"></dd>
<dt id="RFC4440">[IABIRTF]</dt>
      <dd>
<span class="refAuthor">Floyd, S., Ed.</span>, <span class="refAuthor">Paxson, V., Ed.</span>, <span class="refAuthor">Falk, A., Ed.</span>, and <span class="refAuthor">IAB</span>, <span class="refTitle">"IAB Thoughts on the Role of the Internet Research Task Force (IRTF)"</span>, <span class="seriesInfo">RFC 4440</span>, <span class="seriesInfo">DOI 10.17487/RFC4440</span>, <time datetime="2006-03" class="refDate">March 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4440">https://www.rfc-editor.org/info/rfc4440</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="IANADOCS">[IANADOCS]</dt>
      <dd>
<div class="refInstance" id="RFC8126">
          <span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>. </div>
<span>&lt;<a href="https://www.rfc-editor.org/info/bcp26">https://www.rfc-editor.org/info/bcp26</a>&gt;</span>
</dd>
<dd class="break"></dd>
<dt id="RFC2860">[IANAMOU]</dt>
      <dd>
<span class="refAuthor">Carpenter, B.</span>, <span class="refAuthor">Baker, F.</span>, and <span class="refAuthor">M. Roberts</span>, <span class="refTitle">"Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority"</span>, <span class="seriesInfo">RFC 2860</span>, <span class="seriesInfo">DOI 10.17487/RFC2860</span>, <time datetime="2000-06" class="refDate">June 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2860">https://www.rfc-editor.org/info/rfc2860</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3710">[IESG]</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" class="refDate">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>
<dd class="break"></dd>
<dt id="IETFPROCS">[IETFPROCS]</dt>
      <dd>
<div class="refInstance" id="RFC2026">
          <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"The Internet Standards Process -- Revision 3"</span>, <span class="seriesInfo">BCP 9</span>, <span class="seriesInfo">RFC 2026</span>, <time datetime="1996-10" class="refDate">October 1996</time>. </div>
<div class="refInstance" id="RFC5657">
          <span class="refAuthor">Dusseault, L.</span> and <span class="refAuthor">R. Sparks</span>, <span class="refTitle">"Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard"</span>, <span class="seriesInfo">BCP 9</span>, <span class="seriesInfo">RFC 5657</span>, <time datetime="2009-09" class="refDate">September 2009</time>. </div>
<div class="refInstance" id="RFC6410">
          <span class="refAuthor">Housley, R.</span>, <span class="refAuthor">Crocker, D.</span>, and <span class="refAuthor">E. Burger</span>, <span class="refTitle">"Reducing the Standards Track to Two Maturity Levels"</span>, <span class="seriesInfo">BCP 9</span>, <span class="seriesInfo">RFC 6410</span>, <time datetime="2011-10" class="refDate">October 2011</time>. </div>
<div class="refInstance" id="RFC7100">
          <span class="refAuthor">Resnick, P.</span>, <span class="refTitle">"Retirement of the "Internet Official Protocol Standards" Summary Document"</span>, <span class="seriesInfo">BCP 9</span>, <span class="seriesInfo">RFC 7100</span>, <time datetime="2013-12" class="refDate">December 2013</time>. </div>
<div class="refInstance" id="RFC7127">
          <span class="refAuthor">Kolkman, O.</span>, <span class="refAuthor">Bradner, S.</span>, and <span class="refAuthor">S. Turner</span>, <span class="refTitle">"Characterization of Proposed Standards"</span>, <span class="seriesInfo">BCP 9</span>, <span class="seriesInfo">RFC 7127</span>, <time datetime="2014-01" class="refDate">January 2014</time>. </div>
<div class="refInstance" id="RFC7475">
          <span class="refAuthor">Dawkins, S.</span>, <span class="refTitle">"Increasing the Number of Area Directors in an IETF Area"</span>, <span class="seriesInfo">BCP 9</span>, <span class="seriesInfo">RFC 7475</span>, <time datetime="2015-03" class="refDate">March 2015</time>. </div>
<div class="refInstance" id="RFC8789">
          <span class="refAuthor">Halpern, J., Ed.</span> and <span class="refAuthor">E. Rescorla, Ed.</span>, <span class="refTitle">"IETF Stream Documents Require IETF Rough Consensus"</span>, <span class="seriesInfo">BCP 9</span>, <span class="seriesInfo">RFC 8789</span>, <time datetime="2020-06" class="refDate">June 2020</time>. </div>
<span>&lt;<a href="https://www.rfc-editor.org/info/bcp9">https://www.rfc-editor.org/info/bcp9</a>&gt;</span>
</dd>
<dd class="break"></dd>
<dt id="IPRRIGHTS1">[IPRRIGHTS1]</dt>
      <dd>
<div class="refInstance" id="RFC5378">
          <span class="refAuthor">Bradner, S., Ed.</span> and <span class="refAuthor">J. Contreras, Ed.</span>, <span class="refTitle">"Rights Contributors Provide to the IETF Trust"</span>, <span class="seriesInfo">BCP 78</span>, <span class="seriesInfo">RFC 5378</span>, <time datetime="2008-11" class="refDate">November 2008</time>. </div>
<span>&lt;<a href="https://www.rfc-editor.org/info/bcp78">https://www.rfc-editor.org/info/bcp78</a>&gt;</span>
</dd>
<dd class="break"></dd>
<dt id="IPRRIGHTS2">[IPRRIGHTS2]</dt>
      <dd>
<div class="refInstance" id="RFC8179">
          <span class="refAuthor">Bradner, S.</span> and <span class="refAuthor">J. Contreras</span>, <span class="refTitle">"Intellectual Property Rights in IETF Technology"</span>, <span class="seriesInfo">BCP 79</span>, <span class="seriesInfo">RFC 8179</span>, <time datetime="2017-05" class="refDate">May 2017</time>. </div>
<span>&lt;<a href="https://www.rfc-editor.org/info/bcp79">https://www.rfc-editor.org/info/bcp79</a>&gt;</span>
</dd>
<dd class="break"></dd>
<dt id="RFC2014">[IRTF]</dt>
      <dd>
<span class="refAuthor">Weinrib, A.</span> and <span class="refAuthor">J. Postel</span>, <span class="refTitle">"IRTF Research Group Guidelines and Procedures"</span>, <span class="seriesInfo">BCP 8</span>, <span class="seriesInfo">RFC 2014</span>, <span class="seriesInfo">DOI 10.17487/RFC2014</span>, <time datetime="1996-10" class="refDate">October 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2014">https://www.rfc-editor.org/info/rfc2014</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7827">[IRTFCHAIR]</dt>
      <dd>
<span class="refAuthor">Eggert, L.</span>, <span class="refTitle">"The Role of the IRTF Chair"</span>, <span class="seriesInfo">RFC 7827</span>, <span class="seriesInfo">DOI 10.17487/RFC7827</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7827">https://www.rfc-editor.org/info/rfc7827</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7418">[IRTFPRIMER]</dt>
      <dd>
<span class="refAuthor">Dawkins, S., Ed.</span>, <span class="refTitle">"An IRTF Primer for IETF Participants"</span>, <span class="seriesInfo">RFC 7418</span>, <span class="seriesInfo">DOI 10.17487/RFC7418</span>, <time datetime="2014-12" class="refDate">December 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7418">https://www.rfc-editor.org/info/rfc7418</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="ISOC">[ISOC]</dt>
      <dd>
<span class="refAuthor">Internet Society</span>, <span class="refTitle">"Amended and restated By-Laws of the Internet Society"</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span>&lt;<a href="https://www.internetsociety.org/about-internet-society/governance-policies/by-laws/">https://www.internetsociety.org/about-internet-society/governance-policies/by-laws/</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8712">[ISOCIETF]</dt>
      <dd>
<span class="refAuthor">Camarillo, G.</span> and <span class="refAuthor">J. Livingood</span>, <span class="refTitle">"The IETF-ISOC Relationship"</span>, <span class="seriesInfo">RFC 8712</span>, <span class="seriesInfo">DOI 10.17487/RFC8712</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8712">https://www.rfc-editor.org/info/rfc8712</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8719">[MEETINGS]</dt>
      <dd>
<span class="refAuthor">Krishnan, S.</span>, <span class="refTitle">"High-Level Guidance for the Meeting Policy of the IETF"</span>, <span class="seriesInfo">BCP 226</span>, <span class="seriesInfo">RFC 8719</span>, <span class="seriesInfo">DOI 10.17487/RFC8719</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8719">https://www.rfc-editor.org/info/rfc8719</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="NOMCOM">[NOMCOM]</dt>
      <dd>
<div class="refInstance" id="RFC8713">
          <span class="refAuthor">Kucherawy, M., Ed.</span>, <span class="refAuthor">Hinden, R., Ed.</span>, and <span class="refAuthor">J. Livingood, Ed.</span>, <span class="refTitle">"IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees"</span>, <span class="seriesInfo">BCP 10</span>, <span class="seriesInfo">RFC 8713</span>, <time datetime="2020-02" class="refDate">February 2020</time>. </div>
<div class="refInstance" id="RFC8788">
          <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Eligibility for the 2020-2021 Nominating Committee"</span>, <span class="seriesInfo">BCP 10</span>, <span class="seriesInfo">RFC 8788</span>, <time datetime="2020-05" class="refDate">May 2020</time>. </div>
<span>&lt;<a href="https://www.rfc-editor.org/info/bcp10">https://www.rfc-editor.org/info/bcp10</a>&gt;</span>
</dd>
<dd class="break"></dd>
<dt id="RFC2028">[RFC2028]</dt>
      <dd>
<span class="refAuthor">Hovey, R.</span> and <span class="refAuthor">S. Bradner</span>, <span class="refTitle">"The Organizations Involved in the IETF Standards Process"</span>, <span class="seriesInfo">BCP 11</span>, <span class="seriesInfo">RFC 2028</span>, <span class="seriesInfo">DOI 10.17487/RFC2028</span>, <time datetime="1996-10" class="refDate">October 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2028">https://www.rfc-editor.org/info/rfc2028</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC9280">[RFCEDMODEL]</dt>
      <dd>
<span class="refAuthor">Saint-Andre, P., Ed.</span>, <span class="refTitle">"RFC Editor Model (Version 3)"</span>, <span class="seriesInfo">RFC 9280</span>, <span class="seriesInfo">DOI 10.17487/RFC9280</span>, <time datetime="2022-06" class="refDate">June 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9280">https://www.rfc-editor.org/info/rfc9280</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8714">[TRUSTEES]</dt>
      <dd>
<span class="refAuthor">Arkko, J.</span> and <span class="refAuthor">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" class="refDate">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>
<dd class="break"></dd>
<dt id="RFC8715">[TRUSTRAT]</dt>
      <dd>
<span class="refAuthor">Arkko, J.</span>, <span class="refTitle">"IETF Administrative Support Activity 2.0: Update to the Process for Selection of Trustees for the IETF Trust"</span>, <span class="seriesInfo">RFC 8715</span>, <span class="seriesInfo">DOI 10.17487/RFC8715</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8715">https://www.rfc-editor.org/info/rfc8715</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="WGPROCS">[WGPROCS]</dt>
    <dd>
<div class="refInstance" id="RFC2418">
          <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"IETF Working Group Guidelines and Procedures"</span>, <span class="seriesInfo">BCP 25</span>, <span class="seriesInfo">RFC 2418</span>, <time datetime="1998-09" class="refDate">September 1998</time>. </div>
<div class="refInstance" id="RFC3934">
          <span class="refAuthor">Wasserman, M.</span>, <span class="refTitle">"Updates to RFC 2418 Regarding the Management of IETF Mailing Lists"</span>, <span class="seriesInfo">BCP 25</span>, <span class="seriesInfo">RFC 3934</span>, <time datetime="2004-10" class="refDate">October 2004</time>. </div>
<div class="refInstance" id="RFC7776">
          <span class="refAuthor">Resnick, P.</span> and <span class="refAuthor">A. Farrel</span>, <span class="refTitle">"IETF Anti-Harassment Procedures"</span>, <span class="seriesInfo">BCP 25</span>, <span class="seriesInfo">RFC 7776</span>, <time datetime="2016-03" class="refDate">March 2016</time>. </div>
<div class="refInstance" id="RFC8716">
          <span class="refAuthor">Resnick, P.</span> and <span class="refAuthor">A. Farrel</span>, <span class="refTitle">"Update to the IETF Anti-Harassment Procedures for the Replacement of the IETF Administrative Oversight Committee (IAOC) with the IETF Administration LLC"</span>, <span class="seriesInfo">BCP 25</span>, <span class="seriesInfo">RFC 8716</span>, <time datetime="2020-02" class="refDate">February 2020</time>. </div>
<span>&lt;<a href="https://www.rfc-editor.org/info/bcp25">https://www.rfc-editor.org/info/bcp25</a>&gt;</span>
</dd>
<dd class="break"></dd>
</dl>
</section>
<div id="acknowledgements">
<section id="appendix-A">
      <h2 id="name-acknowledgements">
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
      </h2>
<p id="appendix-A-1">We are grateful to the authors of <span>[<a href="#RFC2028" class="xref">RFC2028</a>]</span> -- <span class="contact-name">Richard Hovey</span> and <span class="contact-name">Scott Bradner</span>.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
<p id="appendix-A-2"><span class="contact-name">Barry Leiba</span>, <span class="contact-name">Colin Perkins</span>, <span class="contact-name">Eric Auerswald</span>, <span class="contact-name">John Levine</span>, and <span class="contact-name">Lars Eggert</span>
provided useful feedback and corrections to this document.<a href="#appendix-A-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="appendix-B">
      <h2 id="name-authors-address">
<a href="#name-authors-address" class="section-name selfRef">Author's Address</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Rich Salz</span></div>
<div dir="auto" class="left"><span class="org">Akamai Technologies</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:rsalz@akamai.com" class="email">rsalz@akamai.com</a>
</div>
</address>
</section>
</div>
<script>const toc = document.getElementById("toc");
toc.querySelector("h2").addEventListener("click", e => {
  toc.classList.toggle("active");
});
toc.querySelector("nav").addEventListener("click", e => {
  toc.classList.remove("active");
});
</script>
</body>
</html>