File: rfc8712.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 (1561 lines) | stat: -rw-r--r-- 55,258 bytes
parent folder | download | duplicates (2)
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 8712: The IETF-ISOC Relationship</title>
<meta content="Gonzalo Camarillo" name="author">
<meta content="Jason Livingood" name="author">
<meta content="
       
This document summarizes the Internet Engineering Task Force (IETF) -
Internet Society (ISOC) relationship, following a major revision to
the structure of the IETF Administrative Support Activity (IASA) in
2018. The IASA was revised under a new &quot;IASA 2.0&quot; structure by the
IASA2 Working Group, which changed the IETF's administrative, legal,
and financial structure. As a result, it also changed the relationship
between the IETF and ISOC, which made it necessary to revise RFC 2031.
       
    " name="description">
<meta content="xml2rfc 2.40.0" name="generator">
<meta content="IASA" name="keyword">
<meta content="8712" name="rfc.number">
<link href="rfc8712.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/rfc8712" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc2031bis-08" 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 8712</td>
<td class="center">The IETF-ISOC Relationship</td>
<td class="right">February 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Camarillo &amp; Livingood</td>
<td class="center">Informational</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/rfc8712" class="eref">8712</a></dd>
<dt class="label-obsoletes">Obsoletes:</dt>
<dd class="obsoletes">
<a href="https://www.rfc-editor.org/rfc/rfc2031" class="eref">2031</a> </dd>
<dt class="label-category">Category:</dt>
<dd class="category">Informational</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">G. Camarillo</div>
<div class="org">Ericsson</div>
</div>
<div class="author">
      <div class="author-name">J. Livingood</div>
<div class="org">Comcast</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8712</h1>
<h1 id="title">The IETF-ISOC Relationship</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">
This document summarizes the Internet Engineering Task Force (IETF) -
Internet Society (ISOC) relationship, following a major revision to
the structure of the IETF Administrative Support Activity (IASA) in
2018. The IASA was revised under a new "IASA 2.0" structure by the
IASA2 Working Group, which changed the IETF's administrative, legal,
and financial structure. As a result, it also changed the relationship
between the IETF and ISOC, which made it necessary to revise RFC 2031.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This document is not an Internet Standards Track specification; it is
            published for informational purposes.<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).  Not all documents
            approved by the IESG are candidates for any level of Internet
            Standard; see 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/rfc8712">https://www.rfc-editor.org/info/rfc8712</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-and-history" class="xref">Introduction and History</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-philosophical-relationship-" class="xref">Philosophical Relationship with ISOC</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-main-division-of-responsibi" class="xref">Main Division of Responsibilities between IETF and ISOC</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
</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-isocs-role-in-the-ietf-stan" class="xref">ISOC's Role in the IETF Standards Process</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-the-ietfs-role-in-isoc" class="xref">The IETF's Role in ISOC</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-legal-relationship-with-iso" class="xref">Legal Relationship with ISOC</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-financial-and-administrativ" class="xref">Financial and Administrative Relationship with ISOC</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-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-privacy-considerations" class="xref">Privacy Considerations</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.11.2.1">
                <p id="section-toc.1-1.11.2.1.1"><a href="#section-11.1" class="xref">11.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.11.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.11.2.2">
                <p id="section-toc.1-1.11.2.2.1"><a href="#section-11.2" class="xref">11.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.11.2.2.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</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.b" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p>
</li>
</ul>
</nav>
</section>
</div>
<section id="section-1">
      <h2 id="name-introduction-and-history">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction-and-history" class="section-name selfRef">Introduction and History</a>
      </h2>
<p id="section-1-1">
The Internet Society provides a corporate home for the administrative
entity that supports the Internet Engineering Task Force (IETF), the
Internet Architecture Board (IAB), and the Internet Research Task
Force (IRTF), and supports the work of these groups through a variety
of programs.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">
The Internet Engineering Task Force (IETF) is the body that is
responsible for the development and maintenance of the Internet
Standards. The IETF is primarily a volunteer organization. Its driving
force is a group of dedicated, high-quality engineers from all over the
world. In a structure of working groups, these engineers exchange
ideas and experience, and through discussion and collaboration (both
electronically and face-to-face), they strive to achieve rough
consensus and implement the standards through running code.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">
The growth of the Internet over several decades has also led to the
growth of the IETF. More and more people, organizations, and companies
rely on Internet Standards. Nontechnical issues, such as legal,
administrative, and financial issues had long been an undesirable but
unavoidable part of the IETF. To address these issues, the IETF
established the Poised95 Working Group in 1995. Its goal was to structure and
document the IETF processes in order to maximize the flexibility and
freedom of IETF engineers so that they could work in the way the IETF
had always been most successful and to honor the IETF credo: "Rough
consensus and running code".<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4">
The Poised95 Working Group concluded that the Internet Society (ISOC),
which was formed in 1992, was the best organization to handle all of
these legal, administrative, and financial tasks on behalf of, and in
close cooperation with, the IETF. This led to documenting things such
as the IETF standards process <span>[<a href="#RFC2026" class="xref">RFC2026</a>]</span>, the IETF
organizational structure <span>[<a href="#RFC2028" class="xref">RFC2028</a>]</span>, the IETF Nominating
Committee (NomCom) procedures <span>[<a href="#RFC2027" class="xref">RFC2027</a>]</span>, and the IETF-ISOC
relationship <span>[<a href="#RFC2031" class="xref">RFC2031</a>]</span>.<a href="#section-1-4" class="pilcrow">¶</a></p>
<p id="section-1-5">
As time passed and operational experience accumulated, additional
structure was necessary. As a result, the Internet Administrative
Support Activity (IASA) was defined in 2005 and documented in <span>[<a href="#RFC4071" class="xref">RFC4071</a>]</span> and <span>[<a href="#RFC4371" class="xref">RFC4371</a>]</span>.<a href="#section-1-5" class="pilcrow">¶</a></p>
<p id="section-1-6">
In 2018, the IASA was revised under a new "IASA 2.0" structure by the
IASA2 Working Group, which made significant revisions to the IETF's
administrative, legal, and financial structure. One critical outcome
was the formation, in close cooperation between the IETF and
ISOC, of the IETF Administration Limited Liability Company (IETF LLC)
as a subsidiary of ISOC.<a href="#section-1-6" class="pilcrow">¶</a></p>
<p id="section-1-7">
As a result of the IASA 2.0 structure <span>[<a href="#RFC8711" class="xref">RFC8711</a>]</span> and formation of the IETF LLC, the
relationship between the IETF and ISOC has changed. This document
summarizes the current state of the IETF-ISOC relationship at a high
level and replaces <span>[<a href="#RFC2031" class="xref">RFC2031</a>]</span>.<a href="#section-1-7" class="pilcrow">¶</a></p>
</section>
<section id="section-2">
      <h2 id="name-philosophical-relationship-">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-philosophical-relationship-" class="section-name selfRef">Philosophical Relationship with ISOC</a>
      </h2>
<p id="section-2-1">
ISOC and the IETF have historically been philosophically
aligned. ISOC's connection with the IETF community has always played
an important role in its policy work, which has not changed. ISOC has always been and 
   continues to be an advocate
for multistakeholder processes, which includes the technical
community. Open standards are an explicit part of one of the focus
areas in ISOC's mission: advancing the development and application of
Internet infrastructure, technologies, and open standards <span>[<a href="#ISOC-Mission" class="xref">ISOC-Mission</a>]</span>.<a href="#section-2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-3">
      <h2 id="name-main-division-of-responsibi">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-main-division-of-responsibi" class="section-name selfRef">Main Division of Responsibilities between IETF and ISOC</a>
      </h2>
<p id="section-3-1">
The IETF remains responsible for the development and quality of the
Internet Standards. Apart from the roles described below, the IETF and
ISOC acknowledge that ISOC as an organization has no direct influence whatsoever on the
technical content of Internet Standards (though ISOC employees may independently continue to 
make technical contributions as individuals).<a href="#section-3-1" class="pilcrow">¶</a></p>
</section>
<div id="standards">
<section id="section-4">
      <h2 id="name-isocs-role-in-the-ietf-stan">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-isocs-role-in-the-ietf-stan" class="section-name selfRef">ISOC's Role in the IETF Standards Process</a>
      </h2>
<p id="section-4-1">
ISOC plays a small role in the IETF standards process. In particular,
ISOC assists the standards process by appointing the IETF NomCom chair
and by confirming IAB candidates who are put forward by the IETF
NomCom, as described in <span>[<a href="#RFC8713" class="xref">RFC8713</a>]</span>, and by acting as the
last resort in the appeals process, as described in <span>[<a href="#RFC2026" class="xref">RFC2026</a>]</span>.<a href="#section-4-1" class="pilcrow">¶</a></p>
<p id="section-4-2">
ISOC maintains liaison relationships and memberships in other
Standards Development Organizations (SDOs) and related organizations,
which directly benefits the IETF. For example, ISOC is a Sector Member
of the ITU-T. As a result, ISOC delegates are afforded the same rights
as other ITU-T Sector Members <span>[<a href="#RFC6756" class="xref">RFC6756</a>]</span>.<a href="#section-4-2" class="pilcrow">¶</a></p>
<p id="section-4-3">
ISOC also supports the IETF standards process indirectly (e.g.,
by promoting it in relevant communities) through several
programs.  For example, ISOC's Policymakers Programme to the IETF 
(usually referred to simply as ISOC's IETF Policy Program) gives
policy experts an opportunity to interact directly with the IETF
technical community. ISOC also performs technical work using the
standards developed in the IETF as its basis. An example of that is
ISOC's work in encouraging and supporting the deployment
of IETF standards.<a href="#section-4-3" class="pilcrow">¶</a></p>
<p id="section-4-4">
Otherwise, the involvement of ISOC's employees in the IETF standards
process (e.g., as document editors or in leadership positions) is as
individual contributors rather than on institutional grounds.<a href="#section-4-4" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-5">
      <h2 id="name-the-ietfs-role-in-isoc">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-the-ietfs-role-in-isoc" class="section-name selfRef">The IETF's Role in ISOC</a>
      </h2>
<p id="section-5-1">
The IETF plays a role in the governance of ISOC. Per ISOC's bylaws,
the IETF appoints a set of trustees to the ISOC Board. The process by
which the IETF makes those appointments is defined in <span>[<a href="#RFC3677" class="xref">RFC3677</a>]</span>.<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2">
The charter of the IAB (Internet Architecture Board) <span>[<a href="#RFC2850" class="xref">RFC2850</a>]</span> states that "the IAB acts as a source of advice and
guidance to the Board of Trustees and Officers of the Internet Society
concerning technical, architectural, procedural, and (where
appropriate) policy matters pertaining to the Internet and its
enabling technologies". This connection between the IAB and ISOC
ensures that ISOC's proposals in the policy area are based on a sound
understanding of the relevant technologies and architectures. ISOC's
strong connection to the Internet technical community has always been
one of its main strengths.<a href="#section-5-2" class="pilcrow">¶</a></p>
</section>
<section id="section-6">
      <h2 id="name-legal-relationship-with-iso">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-legal-relationship-with-iso" class="section-name selfRef">Legal Relationship with ISOC</a>
      </h2>
<p id="section-6-1">
The IETF LLC is a disregarded Limited Liability Company (LLC) of the Internet Society that was 
established to provide a corporate legal framework for facilitating current and 
future activities related to the IETF, IAB, and IRTF.  It was established by the 
ISOC / IETF LLC Agreement <span>[<a href="#OpAgreement" class="xref">OpAgreement</a>]</span> on August 27, 2018, and 
governs the relationship between the IETF LLC and ISOC.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">
The IETF Trust, documented in <span>[<a href="#RFC5378" class="xref">RFC5378</a>]</span>, and updated in
<span>[<a href="#RFC8714" class="xref">RFC8714</a>]</span> and <span>[<a href="#RFC8715" class="xref">RFC8715</a>]</span>, provides legal protection for
the RFC Series of documents and other aspects of the IETF. This
includes things such as protection for trademarks, copyrights, and
intellectual property rights. As part of the IETF Trust arrangement,
IETF standards documents can be freely downloaded, copied, and
distributed without financial or other distribution restrictions,
though all rights to change these documents lie with the IETF.  The
IETF Trust also provides legal protection in case of disputes over
intellectual property rights and other rights. The creation of the
IETF LLC has changed the way that the IETF Trust's trustees are
selected but did not change the purpose or operation of the Trust. One
of the IETF Trust's trustees is appointed by the ISOC's Board of
Trustees.<a href="#section-6-2" class="pilcrow">¶</a></p>
</section>
<section id="section-7">
      <h2 id="name-financial-and-administrativ">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-financial-and-administrativ" class="section-name selfRef">Financial and Administrative Relationship with ISOC</a>
      </h2>
<p id="section-7-1">
Under the terms of the Operating Agreement <span>[<a href="#OpAgreement" class="xref">OpAgreement</a>]</span> between ISOC and the IETF, ISOC has agreed to
provide significant funding support for the IETF.  In addition,
the IETF LLC is responsible for creating and
managing an annual operating budget for the IETF; for negotiating,
signing, and overseeing contracts; for fundraising; for maintaining
bank accounts; and for liability insurance. The IETF LLC is managed by
a Board of Directors, one of whom is appointed by the ISOC's Board of
Trustees. The intention is that ISOC and the IETF LLC operate at arm's
length.<a href="#section-7-1" class="pilcrow">¶</a></p>
<p id="section-7-2"> 
The IETF LLC establishes contracts with third parties to provide
different types of services to the IETF. Note that it is possible that
some of those services may be provided by ISOC or involve ISOC staff.<a href="#section-7-2" class="pilcrow">¶</a></p>
<p id="section-7-3">
Under the new IASA 2.0 structure, the IETF LLC is solely responsible for
its administration, including the IETF Trust, IAB, IESG, IETF
working groups, and other IETF processes. A further exploration of
this can be found in <span><a href="https://www.rfc-editor.org/rfc/rfc8711#section-4" class="relref">Section 4</a> of [<a href="#RFC8711" class="xref">RFC8711</a>]</span>.<a href="#section-7-3" class="pilcrow">¶</a></p>
</section>
<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>
<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">This document introduces no new security considerations.<a href="#section-9-1" class="pilcrow">¶</a></p>
</section>
<section id="section-10">
      <h2 id="name-privacy-considerations">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-privacy-considerations" class="section-name selfRef">Privacy Considerations</a>
      </h2>
<p id="section-10-1">This document introduces no new privacy considerations.<a href="#section-10-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11">
      <h2 id="name-references">
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-11.1">
        <h3 id="name-normative-references">
<a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="RFC8711">[RFC8711]</dt>
<dd>
<span class="refAuthor">Haberman, B.</span><span class="refAuthor">, Hall, J.</span><span class="refAuthor">, and J. Livingood</span>, <span class="refTitle">"Structure of the IETF Administrative Support Activity, Version 2.0"</span>, <span class="seriesInfo">BCP 101</span>, <span class="seriesInfo">RFC 8711</span>, <span class="seriesInfo">DOI 10.17487/RFC8711</span>, <time datetime="2020-02">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8711">https://www.rfc-editor.org/info/rfc8711</a>&gt;</span>. </dd>
</dl>
</section>
<section id="section-11.2">
        <h3 id="name-informative-references">
<a href="#section-11.2" class="section-number selfRef">11.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="ISOC-Mission">[ISOC-Mission]</dt>
<dd>
<span class="refAuthor">Internet Society</span>, <span class="refTitle">"Internet Society Mission"</span>, <span>&lt;<a href="https://www.internetsociety.org/mission/">https://www.internetsociety.org/mission/</a>&gt;</span>. </dd>
<dt id="OpAgreement">[OpAgreement]</dt>
<dd>
<span class="refTitle">"Limited Liability Company Agreement of IETF Administration LLC"</span>, <time datetime="2018-08">August 2018</time>, <span>&lt;<a href="https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf">https://www.ietf.org/documents/180/IETF-LLC-Agreement.pdf</a>&gt;</span>. </dd>
<dt id="RFC2026">[RFC2026]</dt>
<dd>
<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>, <span class="seriesInfo">DOI 10.17487/RFC2026</span>, <time datetime="1996-10">October 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2026">https://www.rfc-editor.org/info/rfc2026</a>&gt;</span>. </dd>
<dt id="RFC2027">[RFC2027]</dt>
<dd>
<span class="refAuthor">Galvin, J.</span>, <span class="refTitle">"IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees"</span>, <span class="seriesInfo">RFC 2027</span>, <span class="seriesInfo">DOI 10.17487/RFC2027</span>, <time datetime="1996-10">October 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2027">https://www.rfc-editor.org/info/rfc2027</a>&gt;</span>. </dd>
<dt id="RFC2028">[RFC2028]</dt>
<dd>
<span class="refAuthor">Hovey, R.</span><span class="refAuthor"> and 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">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>
<dt id="RFC2031">[RFC2031]</dt>
<dd>
<span class="refAuthor">Huizer, E.</span>, <span class="refTitle">"IETF-ISOC relationship"</span>, <span class="seriesInfo">RFC 2031</span>, <span class="seriesInfo">DOI 10.17487/RFC2031</span>, <time datetime="1996-10">October 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2031">https://www.rfc-editor.org/info/rfc2031</a>&gt;</span>. </dd>
<dt id="RFC2850">[RFC2850]</dt>
<dd>
<span class="refAuthor">Internet Architecture Board</span><span class="refAuthor"> and 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>, <span class="seriesInfo">DOI 10.17487/RFC2850</span>, <time datetime="2000-05">May 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2850">https://www.rfc-editor.org/info/rfc2850</a>&gt;</span>. </dd>
<dt id="RFC3677">[RFC3677]</dt>
<dd>
<span class="refAuthor">Daigle, L., Ed.</span><span class="refAuthor"> and Internet Architecture Board</span>, <span class="refTitle">"IETF ISOC Board of Trustee Appointment Procedures"</span>, <span class="seriesInfo">BCP 77</span>, <span class="seriesInfo">RFC 3677</span>, <span class="seriesInfo">DOI 10.17487/RFC3677</span>, <time datetime="2003-12">December 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3677">https://www.rfc-editor.org/info/rfc3677</a>&gt;</span>. </dd>
<dt id="RFC4071">[RFC4071]</dt>
<dd>
<span class="refAuthor">Austein, R., Ed.</span><span class="refAuthor"> and B. Wijnen, Ed.</span>, <span class="refTitle">"Structure of the IETF Administrative Support Activity (IASA)"</span>, <span class="seriesInfo">BCP 101</span>, <span class="seriesInfo">RFC 4071</span>, <span class="seriesInfo">DOI 10.17487/RFC4071</span>, <time datetime="2005-04">April 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4071">https://www.rfc-editor.org/info/rfc4071</a>&gt;</span>. </dd>
<dt id="RFC4371">[RFC4371]</dt>
<dd>
<span class="refAuthor">Carpenter, B., Ed.</span><span class="refAuthor"> and L. Lynch, Ed.</span>, <span class="refTitle">"BCP 101 Update for IPR Trust"</span>, <span class="seriesInfo">BCP 101</span>, <span class="seriesInfo">RFC 4371</span>, <span class="seriesInfo">DOI 10.17487/RFC4371</span>, <time datetime="2006-01">January 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4371">https://www.rfc-editor.org/info/rfc4371</a>&gt;</span>. </dd>
<dt id="RFC5378">[RFC5378]</dt>
<dd>
<span class="refAuthor">Bradner, S., Ed.</span><span class="refAuthor"> and 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>, <span class="seriesInfo">DOI 10.17487/RFC5378</span>, <time datetime="2008-11">November 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5378">https://www.rfc-editor.org/info/rfc5378</a>&gt;</span>. </dd>
<dt id="RFC6756">[RFC6756]</dt>
<dd>
<span class="refAuthor">Trowbridge, S., Ed.</span><span class="refAuthor">, Lear, E., Ed.</span><span class="refAuthor">, Fishman, G., Ed.</span><span class="refAuthor">, and S. Bradner, Ed.</span>, <span class="refTitle">"Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines"</span>, <span class="seriesInfo">RFC 6756</span>, <span class="seriesInfo">DOI 10.17487/RFC6756</span>, <time datetime="2012-09">September 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6756">https://www.rfc-editor.org/info/rfc6756</a>&gt;</span>. </dd>
<dt id="RFC8713">[RFC8713]</dt>
<dd>
<span class="refAuthor">Kucherawy, M., Ed.</span><span class="refAuthor">, Hinden, R., Ed.</span><span class="refAuthor">, and 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>, <span class="seriesInfo">DOI 10.17487/RFC8713</span>, <time datetime="2020-02">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8713">https://www.rfc-editor.org/info/rfc8713</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="RFC8715">[RFC8715]</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">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>
</dl>
</section>
</section>
<div id="ack">
<section id="section-appendix.a">
      <h2 id="name-acknowledgements">
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
      </h2>
<p id="section-appendix.a-1">
The authors would like to thank <span class="contact-name">Erik Huizer</span> for his contribution as
the author of <span>[<a href="#RFC2031" class="xref">RFC2031</a>]</span>, which this document
replaces.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="section-appendix.b">
      <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">Gonzalo Camarillo</span></div>
<div dir="auto" class="left"><span class="org">Ericsson</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:Gonzalo.Camarillo@ericsson.com" class="email">Gonzalo.Camarillo@ericsson.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Jason Livingood</span></div>
<div dir="auto" class="left"><span class="org">Comcast</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>