File: rfc9280.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 (3167 lines) | stat: -rw-r--r-- 159,970 bytes
<!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 9280: RFC Editor Model (Version 3)</title>
<meta content="Peter Saint-Andre" name="author">
<meta content="
       This document specifies version 3 of the RFC Editor Model. The model 
defines two high-level tasks related to the RFC Series. First, policy 
definition is the joint responsibility of the RFC Series Working Group 
(RSWG), which produces policy proposals, and the RFC Series Approval 
Board (RSAB), which approves such proposals. Second, policy 
implementation is primarily the responsibility of the RFC Production 
Center (RPC) as contractually overseen by the IETF Administration
Limited Liability Company (IETF LLC).  In addition, various 
responsibilities of the RFC Editor function are now performed alone
or in combination by the RSWG, RSAB, RPC, RFC Series Consulting Editor 
(RSCE), and IETF LLC. Finally, this document establishes the Editorial 
Stream for publication of future policy definition documents produced 
through the processes defined herein. 
       This document obsoletes RFC 8728. This document updates RFCs 7841,
8729, and 8730. 
    " name="description">
<meta content="xml2rfc 3.12.10" name="generator">
<meta content="9280" 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="rfc9280.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/rfc9280" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-iab-rfcefdp-rfced-model-13" 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 9280</td>
<td class="center">RFC Editor Model</td>
<td class="right">June 2022</td>
</tr></thead>
<tfoot><tr>
<td class="left">Saint-Andre</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 Architecture Board (IAB)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9280" class="eref">9280</a></dd>
<dt class="label-obsoletes">Obsoletes:</dt>
<dd class="obsoletes">
<a href="https://www.rfc-editor.org/rfc/rfc8728" class="eref">8728</a> </dd>
<dt class="label-updates">Updates:</dt>
<dd class="updates">
<a href="https://www.rfc-editor.org/rfc/rfc7841" class="eref">7841</a>, <a href="https://www.rfc-editor.org/rfc/rfc8729" class="eref">8729</a>, <a href="https://www.rfc-editor.org/rfc/rfc8730" class="eref">8730</a> </dd>
<dt class="label-category">Category:</dt>
<dd class="category">Informational</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">P. Saint-Andre, <span class="editor">Ed.</span>
</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9280</h1>
<h1 id="title">RFC Editor Model (Version 3)</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document specifies version 3 of the RFC Editor Model. The model 
defines two high-level tasks related to the RFC Series. First, policy 
definition is the joint responsibility of the RFC Series Working Group 
(RSWG), which produces policy proposals, and the RFC Series Approval 
Board (RSAB), which approves such proposals. Second, policy 
implementation is primarily the responsibility of the RFC Production 
Center (RPC) as contractually overseen by the IETF Administration
Limited Liability Company (IETF LLC).  In addition, various 
responsibilities of the RFC Editor function are now performed alone
or in combination by the RSWG, RSAB, RPC, RFC Series Consulting Editor 
(RSCE), and IETF LLC. Finally, this document establishes the Editorial 
Stream for publication of future policy definition documents produced 
through the processes defined herein.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
<p id="section-abstract-2">This document obsoletes RFC 8728. This document updates RFCs 7841,
8729, and 8730.<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 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 Architecture Board
            (IAB) and represents information that the IAB has deemed valuable
            to provide for permanent record.  It represents the consensus of the Internet
            Architecture Board (IAB).  Documents approved for publication
            by the IAB are not 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/rfc9280">https://www.rfc-editor.org/info/rfc9280</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.<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>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-overview-of-the-model" class="xref">Overview of the Model</a></p>
</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-policy-definition" class="xref">Policy Definition</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-structure-and-roles" class="xref">Structure and Roles</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.1">
                    <p id="section-toc.1-1.3.2.1.2.1.1" class="keepWithNext"><a href="#section-3.1.1" class="xref">3.1.1</a>.  <a href="#name-rfc-series-working-group-rs" class="xref">RFC Series Working Group (RSWG)</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.2">
                    <p id="section-toc.1-1.3.2.1.2.2.1"><a href="#section-3.1.2" class="xref">3.1.2</a>.  <a href="#name-rfc-series-approval-board-r" class="xref">RFC Series Approval Board (RSAB)</a></p>
</li>
                </ul>
</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-process" class="xref">Process</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.1">
                    <p id="section-toc.1-1.3.2.2.2.1.1"><a href="#section-3.2.1" class="xref">3.2.1</a>.  <a href="#name-intent" class="xref">Intent</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.2">
                    <p id="section-toc.1-1.3.2.2.2.2.1"><a href="#section-3.2.2" class="xref">3.2.2</a>.  <a href="#name-workflow" class="xref">Workflow</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.3">
                    <p id="section-toc.1-1.3.2.2.2.3.1"><a href="#section-3.2.3" class="xref">3.2.3</a>.  <a href="#name-community-calls-for-comment" class="xref">Community Calls for Comment</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.4">
                    <p id="section-toc.1-1.3.2.2.2.4.1"><a href="#section-3.2.4" class="xref">3.2.4</a>.  <a href="#name-appeals" class="xref">Appeals</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.5">
                    <p id="section-toc.1-1.3.2.2.2.5.1"><a href="#section-3.2.5" class="xref">3.2.5</a>.  <a href="#name-anti-harassment-policy" class="xref">Anti-Harassment Policy</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.6">
                    <p id="section-toc.1-1.3.2.2.2.6.1"><a href="#section-3.2.6" class="xref">3.2.6</a>.  <a href="#name-rfc-boilerplates" class="xref">RFC Boilerplates</a></p>
</li>
                </ul>
</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-policy-implementation" class="xref">Policy Implementation</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1">
                <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-roles-and-processes" class="xref">Roles and Processes</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
                <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-working-practices" class="xref">Working Practices</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3">
                <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-rpc-responsibilities" class="xref">RPC Responsibilities</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.4">
                <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-resolution-of-disagreements" class="xref">Resolution of Disagreements between Authors and the RPC</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.5">
                <p id="section-toc.1-1.4.2.5.1"><a href="#section-4.5" class="xref">4.5</a>.  <a href="#name-point-of-contact" class="xref">Point of Contact</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.6">
                <p id="section-toc.1-1.4.2.6.1"><a href="#section-4.6" class="xref">4.6</a>.  <a href="#name-administrative-implementati" class="xref">Administrative Implementation</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.6.2.1">
                    <p id="section-toc.1-1.4.2.6.2.1.1"><a href="#section-4.6.1" class="xref">4.6.1</a>.  <a href="#name-vendor-selection-for-the-rp" class="xref">Vendor Selection for the RPC</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.6.2.2">
                    <p id="section-toc.1-1.4.2.6.2.2.1"><a href="#section-4.6.2" class="xref">4.6.2</a>.  <a href="#name-budget" class="xref">Budget</a></p>
</li>
                </ul>
</li>
            </ul>
</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-rfc-series-consulting-edito" class="xref">RFC Series Consulting Editor (RSCE)</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1">
                <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-rsce-selection" class="xref">RSCE Selection</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.2">
                <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-rsce-performance-evaluation" class="xref">RSCE Performance Evaluation</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.3">
                <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-temporary-rsce-appointment" class="xref">Temporary RSCE Appointment</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.4">
                <p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-conflict-of-interest" class="xref">Conflict of Interest</a></p>
</li>
            </ul>
</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-editorial-stream" class="xref">Editorial Stream</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1">
                <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-procedures-request-of-the-i" class="xref">Procedures Request of the IETF Trust</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2">
                <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-patent-and-trademark-rules-" class="xref">Patent and Trademark Rules for the Editorial Stream</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.3">
                <p id="section-toc.1-1.6.2.3.1"><a href="#section-6.3" class="xref">6.3</a>.  <a href="#name-editorial-stream-boilerplat" class="xref">Editorial Stream Boilerplate</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare 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-historical-properties-of-th" class="xref">Historical Properties of the RFC Series</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1">
                <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-availability" class="xref">Availability</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2">
                <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-accessibility" class="xref">Accessibility</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3">
                <p id="section-toc.1-1.7.2.3.1"><a href="#section-7.3" class="xref">7.3</a>.  <a href="#name-language" class="xref">Language</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.4">
                <p id="section-toc.1-1.7.2.4.1"><a href="#section-7.4" class="xref">7.4</a>.  <a href="#name-diversity" class="xref">Diversity</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.5">
                <p id="section-toc.1-1.7.2.5.1"><a href="#section-7.5" class="xref">7.5</a>.  <a href="#name-quality" class="xref">Quality</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.6">
                <p id="section-toc.1-1.7.2.6.1"><a href="#section-7.6" class="xref">7.6</a>.  <a href="#name-stability" class="xref">Stability</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.7">
                <p id="section-toc.1-1.7.2.7.1"><a href="#section-7.7" class="xref">7.7</a>.  <a href="#name-longevity" class="xref">Longevity</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare 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-updates-to-this-document" class="xref">Updates to This Document</a></p>
</li>
          <li class="compact toc ulBare 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-changes-from-version-2-of-t" class="xref">Changes from Version 2 of the RFC Editor Model</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.1">
                <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-rfc-editor-function" class="xref">RFC Editor Function</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.2">
                <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-rfc-series-editor" class="xref">RFC Series Editor</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.3">
                <p id="section-toc.1-1.9.2.3.1"><a href="#section-9.3" class="xref">9.3</a>.  <a href="#name-rfc-publisher" class="xref">RFC Publisher</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.4">
                <p id="section-toc.1-1.9.2.4.1"><a href="#section-9.4" class="xref">9.4</a>.  <a href="#name-iab" class="xref">IAB</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.5">
                <p id="section-toc.1-1.9.2.5.1"><a href="#section-9.5" class="xref">9.5</a>.  <a href="#name-rfc-series-oversight-commit" class="xref">RFC Series Oversight Committee (RSOC)</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.6">
                <p id="section-toc.1-1.9.2.6.1"><a href="#section-9.6" class="xref">9.6</a>.  <a href="#name-rfc-series-advisory-group-r" class="xref">RFC Series Advisory Group (RSAG)</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.7">
                <p id="section-toc.1-1.9.2.7.1"><a href="#section-9.7" class="xref">9.7</a>.  <a href="#name-editorial-stream-2" class="xref">Editorial Stream</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare 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-security-considerations" class="xref">Security Considerations</a></p>
</li>
          <li class="compact toc ulBare 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-iana-considerations" class="xref">IANA Considerations</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-references" class="xref">References</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.1">
                <p id="section-toc.1-1.12.2.1.1"><a href="#section-12.1" class="xref">12.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.2">
                <p id="section-toc.1-1.12.2.2.1"><a href="#section-12.2" class="xref">12.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13">
            <p id="section-toc.1-1.13.1"><a href="#appendix-A" class="xref"></a><a href="#name-iab-members-at-the-time-of-" class="xref">IAB Members at the Time of Approval</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.14">
            <p id="section-toc.1-1.14.1"><a href="#appendix-B" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.15">
            <p id="section-toc.1-1.15.1"><a href="#appendix-C" 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 Request for Comments (RFC) Series is the archival series
dedicated to documenting Internet technical specifications,
including general contributions from the Internet research and
engineering community as well as standards documents. RFCs are 
available free of charge to anyone via the Internet. As described
in <span>[<a href="#RFC8700" class="xref">RFC8700</a>]</span>, RFCs have been published continually since 1969.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">RFCs are generated and approved by multiple document streams. 
Whereas the stream approving body <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span> for each stream is 
responsible for the content of that stream, the RFC Editor function 
is responsible for the production and distribution of all RFCs. 
The four existing streams are described in <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span>. This 
document adds a fifth stream, the Editorial Stream, for publication
of policies governing the RFC Series as a whole.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">The overall framework for the RFC Series and the RFC Editor
function is described in <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span> and is updated by this 
document, which defines version 3 of the RFC Editor Model. 
Under this version, various responsibilities of the RFC Editor 
function are performed alone or in combination by the RFC Series
Working Group (RSWG), RFC Series Advisory Board (RSAB), RFC
Production Center (RPC), RFC Series Consulting Editor (RSCE), and 
IETF Administration Limited Liability Company (IETF LLC) <span>[<a href="#RFC8711" class="xref">RFC8711</a>]</span>, 
which collectively comprise the RFC Editor function. The intent 
is to ensure sustainable maintenance and support of the RFC Series 
based on the principles of expert implementation, clear management 
and direction, and appropriate community input <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span>.<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4">This document obsoletes <span>[<a href="#RFC8728" class="xref">RFC8728</a>]</span> by defining version 3 
of the RFC Editor Model. This document updates <span>[<a href="#RFC7841" class="xref">RFC7841</a>]</span> 
by defining boilerplate text for the Editorial Stream. This 
document updates <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span> by replacing the RFC Editor role
with the RSWG, RSAB, and RSCE. This document updates <span>[<a href="#RFC8730" class="xref">RFC8730</a>]</span>
by removing the dependency on certain policies specified by the
IAB and RFC Series Editor (RSE). More detailed information about changes from 
version 2 of the RFC Editor Model can be found in <a href="#changes" class="xref">Section 9</a>.<a href="#section-1-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="overview-of-the-model">
<section id="section-2">
      <h2 id="name-overview-of-the-model">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-overview-of-the-model" class="section-name selfRef">Overview of the Model</a>
      </h2>
<p id="section-2-1">This document divides the responsibilities for the RFC Series 
into two high-level tasks:<a href="#section-2-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-2-2">
<li id="section-2-2.1">Policy definition governing the RFC Series as a whole. This is
the joint responsibility of two entities. First, the RFC Series Working 
Group (RSWG) is an open working group independent of the IETF that 
generates policy proposals. Second, the RFC Series Approval Board (RSAB) 
is an appointed body that approves such proposals for publication 
in the Editorial Stream. The RSAB includes representatives of the 
streams <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span> as well as an expert in technical publishing, 
the RFC Series Consulting Editor (RSCE).<a href="#section-2-2.1" class="pilcrow">¶</a>
</li>
        <li id="section-2-2.2">Policy implementation through publication of RFCs in all of the 
streams that form the RFC Series. This is primarily the responsibility 
of the RFC Production Center (RPC) as contractually overseen by the 
IETF Administration Limited Liability Company (IETF LLC) <span>[<a href="#RFC8711" class="xref">RFC8711</a>]</span>.<a href="#section-2-2.2" class="pilcrow">¶</a>
</li>
      </ol>
<p id="section-2-3">As described more fully in the remainder of this document, the core
activities and responsibilities are as follows:<a href="#section-2-3" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-2-4.1">The RSWG proposes policies that govern the RFC Series as a whole, with
input from the community, the RSAB, and the RSCE.<a href="#section-2-4.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-4.2">The RSAB considers those proposals and either approves them or returns 
them to the RSWG, which may make further changes or remove them from
further consideration.<a href="#section-2-4.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-4.3">If approved, such proposals are published as RFCs in the Editorial
Stream and thus define the policies to be followed by the RSWG, RSAB,
RSCE, and RPC.<a href="#section-2-4.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-4.4">The RSCE provides expert advice to the RPC and RSAB on how to implement
established policies on an ongoing and operational basis, which can include
raising issues or initiating proposed policy changes within the RSWG.<a href="#section-2-4.4" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-4.5">The RPC implements the policies defined by the Editorial Stream in its
day-to-day editing and publication of RFCs from all of the streams.<a href="#section-2-4.5" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-4.6">If issues arise with the implementation of particular policies, the RPC
brings those issues to the RSAB, which interprets the policies and provides
interim guidance to the RPC, informing the RSWG of those interpretations.<a href="#section-2-4.6" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-2-5">This model is designed to ensure public processes and policy documents,
clear lines of responsibility and authority, transparent mechanisms for updates and changes to policies
governing the RFC Series as a whole, and effective operational implementation of the
RFC Series, thus meeting the requirements specified in <span><a href="https://www.rfc-editor.org/rfc/rfc8729#section-4" class="relref">Section 4</a> of [<a href="#RFC8729" class="xref">RFC8729</a>]</span>.<a href="#section-2-5" class="pilcrow">¶</a></p>
<p id="section-2-6">The remainder of this document describes the model in greater detail.<a href="#section-2-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="policy-definition">
<section id="section-3">
      <h2 id="name-policy-definition">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-policy-definition" class="section-name selfRef">Policy Definition</a>
      </h2>
<p id="section-3-1">Policies governing the RFC Series as a whole are defined through the 
following high-level process:<a href="#section-3-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-3-2">
<li id="section-3-2.1">Proposals must be submitted to, adopted by, and discussed within the RFC
Series Working Group (RSWG).<a href="#section-3-2.1" class="pilcrow">¶</a>
</li>
        <li id="section-3-2.2">Proposals must pass a Last Call for comments in the working group and 
a community call for comments (see <a href="#cfc" class="xref">Section 3.2.3</a>).<a href="#section-3-2.2" class="pilcrow">¶</a>
</li>
        <li id="section-3-2.3">Proposals must be approved by the RFC Series Approval Board (RSAB).<a href="#section-3-2.3" class="pilcrow">¶</a>
</li>
      </ol>
<p id="section-3-3">Policies under the purview of the RSWG and RSAB might include, but are
not limited to, document formats, processes for publication and
dissemination of RFCs, and overall management of the RFC Series.<a href="#section-3-3" class="pilcrow">¶</a></p>
<div id="structure-and-roles">
<section id="section-3.1">
        <h3 id="name-structure-and-roles">
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-structure-and-roles" class="section-name selfRef">Structure and Roles</a>
        </h3>
<div id="wg">
<section id="section-3.1.1">
          <h4 id="name-rfc-series-working-group-rs">
<a href="#section-3.1.1" class="section-number selfRef">3.1.1. </a><a href="#name-rfc-series-working-group-rs" class="section-name selfRef">RFC Series Working Group (RSWG)</a>
          </h4>
<div id="purpose">
<section id="section-3.1.1.1">
            <h5 id="name-purpose">
<a href="#section-3.1.1.1" class="section-number selfRef">3.1.1.1. </a><a href="#name-purpose" class="section-name selfRef">Purpose</a>
            </h5>
<p id="section-3.1.1.1-1">The RFC Series Working Group (RSWG) is the primary venue in which 
members of the community collaborate regarding the policies that 
govern the RFC Series.<a href="#section-3.1.1.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="participation">
<section id="section-3.1.1.2">
            <h5 id="name-participation">
<a href="#section-3.1.1.2" class="section-number selfRef">3.1.1.2. </a><a href="#name-participation" class="section-name selfRef">Participation</a>
            </h5>
<p id="section-3.1.1.2-1">All interested individuals are welcome to participate in the RSWG;
participants are subject to anti-harassment policies as described in <a href="#coc" class="xref">Section 3.2.5</a>.  This includes but is not limited to participants in the IETF
and IRTF, members of the IAB and IESG, developers of software or hardware
systems that implement RFCs, authors of RFCs and Internet-Drafts, developers
of tools used to author or edit RFCs and Internet-Drafts, individuals who use
RFCs in procurement decisions, scholarly researchers, and representatives of
standards development organizations other than the IETF and IRTF. The IETF LLC
Board members, staff and contractors (especially representatives of the RFC
Production Center), and the IETF Executive Director are invited to participate
as community members in the RSWG to the extent permitted by any relevant IETF
LLC policies. Members of the RSAB are also expected to participate
actively.<a href="#section-3.1.1.2-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="chairs">
<section id="section-3.1.1.3">
            <h5 id="name-chairs">
<a href="#section-3.1.1.3" class="section-number selfRef">3.1.1.3. </a><a href="#name-chairs" class="section-name selfRef">Chairs</a>
            </h5>
<p id="section-3.1.1.3-1">The RSWG shall have two chairs, one appointed by the IESG and the
other appointed by the IAB. When the RSWG is formed, the chair
appointed by the IESG shall serve for a term of one (1) year and
the chair appointed by the IAB shall serve for a term of two (2)
years; thereafter, chairs shall serve for a term of two (2)
years, with no term limits on renewal. The IESG and IAB shall
determine their own processes for making these appointments, making
sure to take account of any potential conflicts of interest.
Community members who have concerns about the performance of an
RSWG Chair should direct their feedback to the appropriate appointing 
body via mechanisms such bodies shall specify at the time that the
RSWG is formed. The IESG and IAB shall have the power to remove their
appointed chairs at their discretion at any time and to name a
replacement who shall serve the remainder of the original chair's
term.<a href="#section-3.1.1.3-1" class="pilcrow">¶</a></p>
<p id="section-3.1.1.3-2">It is the responsibility of the chairs to encourage rough consensus
within the RSWG and to follow that consensus in their decision making,
for instance, regarding acceptance of new proposals and advancement of
proposals to the RSAB.<a href="#section-3.1.1.3-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="mode-of-operation">
<section id="section-3.1.1.4">
            <h5 id="name-mode-of-operation">
<a href="#section-3.1.1.4" class="section-number selfRef">3.1.1.4. </a><a href="#name-mode-of-operation" class="section-name selfRef">Mode of Operation</a>
            </h5>
<p id="section-3.1.1.4-1">The intent is that the RSWG shall operate in a way similar to that of working 
groups in the IETF. Therefore, all 
RSWG meetings and discussion venues shall be open to all interested 
individuals, and all RSWG contributions shall be subject to intellectual 
property policies, which must be consistent with those of the IETF as 
specified in <span>[<a href="#BCP78" class="xref">BCP78</a>]</span> and <span>[<a href="#BCP79" class="xref">BCP79</a>]</span>.<a href="#section-3.1.1.4-1" class="pilcrow">¶</a></p>
<p id="section-3.1.1.4-2">When the RSWG is formed, all discussions shall take place on an
open email discussion list, which shall be publicly archived.<a href="#section-3.1.1.4-2" class="pilcrow">¶</a></p>
<p id="section-3.1.1.4-3">The RSWG is empowered to hold in-person, online-only, or hybrid meetings,
which should be announced with sufficient notice to enable broad
participation; the <a href="https://www.ietf.org/about/groups/iesg/statements/interim-meetings-guidance-2016-01-16/">IESG Guidance on Face-to-Face and Virtual Interim
Meetings</a> 
provides a reasonable baseline. In-person meetings should include
provision for effective online participation for those unable to
attend in person.<a href="#section-3.1.1.4-3" class="pilcrow">¶</a></p>
<p id="section-3.1.1.4-4">The RSWG shall operate by rough consensus, a mode of operation
informally described in <span>[<a href="#RFC2418" class="xref">RFC2418</a>]</span>.<a href="#section-3.1.1.4-4" class="pilcrow">¶</a></p>
<p id="section-3.1.1.4-5">The RSWG may decide by rough consensus to use additional tooling 
(e.g., GitHub as specified in <span>[<a href="#RFC8874" class="xref">RFC8874</a>]</span>), forms of communication, 
and working methods (e.g., design teams) as long as they are consistent 
with this document and with <span>[<a href="#RFC2418" class="xref">RFC2418</a>]</span> or its successors.<a href="#section-3.1.1.4-5" class="pilcrow">¶</a></p>
<p id="section-3.1.1.4-6">Absent specific guidance in this document regarding the operation
of the RSWG, the general guidance provided in <span><a href="https://www.rfc-editor.org/rfc/rfc2418#section-6" class="relref">Section 6</a> of [<a href="#RFC2418" class="xref">RFC2418</a>]</span> 
should be considered appropriate.<a href="#section-3.1.1.4-6" class="pilcrow">¶</a></p>
<p id="section-3.1.1.4-7">The IETF LLC is requested to provide necessary tooling to support 
RSWG communication, decision processes, and policies.<a href="#section-3.1.1.4-7" class="pilcrow">¶</a></p>
<p id="section-3.1.1.4-8">The IAB is requested to convene the RSWG when it is first formed in
order to formalize the IAB's transfer of authority over the RFC Editor 
Model.<a href="#section-3.1.1.4-8" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="rfc-series-approval-board-rsab">
<section id="section-3.1.2">
          <h4 id="name-rfc-series-approval-board-r">
<a href="#section-3.1.2" class="section-number selfRef">3.1.2. </a><a href="#name-rfc-series-approval-board-r" class="section-name selfRef">RFC Series Approval Board (RSAB)</a>
          </h4>
<div id="purpose-1">
<section id="section-3.1.2.1">
            <h5 id="name-purpose-2">
<a href="#section-3.1.2.1" class="section-number selfRef">3.1.2.1. </a><a href="#name-purpose-2" class="section-name selfRef">Purpose</a>
            </h5>
<p id="section-3.1.2.1-1">The RFC Series Approval Board (RSAB), which includes representatives 
of all of the streams, shall act as the approving body for proposals 
generated within the RSWG, thus providing an appropriate set of checks 
and balances on the output of the RSWG. The only policy-making role
of the RSAB is to review policy proposals generated by the RSWG; it shall
have no independent authority to formulate policy on its own. It is
expected that the RSAB will respect the rough consensus of the
RSWG wherever possible, without ceding its responsibility to 
review RSWG proposals, as further described in <a href="#workflow" class="xref">Section 3.2.2</a>.<a href="#section-3.1.2.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="members">
<section id="section-3.1.2.2">
            <h5 id="name-members">
<a href="#section-3.1.2.2" class="section-number selfRef">3.1.2.2. </a><a href="#name-members" class="section-name selfRef">Members</a>
            </h5>
<p id="section-3.1.2.2-1">The RSAB consists primarily of the following voting members:<a href="#section-3.1.2.2-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.1.2.2-2.1">A stream representative for the IETF Stream: either an IESG member
or someone appointed by the IESG<a href="#section-3.1.2.2-2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-3.1.2.2-2.2">A stream representative for the IAB Stream: either an IAB member
or someone appointed by the IAB<a href="#section-3.1.2.2-2.2" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-3.1.2.2-2.3">A stream representative for the IRTF Stream: either the IRTF Chair
or someone appointed by the IRTF Chair<a href="#section-3.1.2.2-2.3" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-3.1.2.2-2.4">A stream representative for the Independent Stream: either the
Independent Submissions Editor (ISE) <span>[<a href="#RFC8730" class="xref">RFC8730</a>]</span> or someone
appointed by the ISE<a href="#section-3.1.2.2-2.4" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-3.1.2.2-2.5">The RFC Series Consulting Editor (RSCE)<a href="#section-3.1.2.2-2.5" class="pilcrow">¶</a>
</li>
            </ul>
<p id="section-3.1.2.2-3">If and when a new stream is created, the document that
creates the stream shall specify if a voting member representing
that stream shall also be added to the RSAB, along with any rules
and processes related to that representative (e.g., whether the
representative is a member of the body responsible for the stream
or an appointed delegate thereof).<a href="#section-3.1.2.2-3" class="pilcrow">¶</a></p>
<p id="section-3.1.2.2-4">The RFC Series Consulting Editor (RSCE) is a voting member of the
RSAB but does not act as a representative of the Editorial Stream.<a href="#section-3.1.2.2-4" class="pilcrow">¶</a></p>
<p id="section-3.1.2.2-5">To ensure the smooth operation of the RFC Series, the RSAB shall
include the following non-voting, ex officio members:<a href="#section-3.1.2.2-5" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.1.2.2-6.1">The IETF Executive Director or their delegate (the rationale is 
that the IETF LLC is accountable for implementation of policies 
governing the RFC Series)<a href="#section-3.1.2.2-6.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-3.1.2.2-6.2">A representative of the RPC, named by the RPC (the rationale
is that the RPC is responsible for implementation of policies
governing the RFC Series)<a href="#section-3.1.2.2-6.2" class="pilcrow">¶</a>
</li>
            </ul>
<p id="section-3.1.2.2-7">In addition, the RSAB may include
other non-voting members at its discretion; these non-voting members may be ex officio members or liaisons from
groups or organizations with which the RSAB deems it necessary to
formally collaborate or coordinate.<a href="#section-3.1.2.2-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="appointment-and-removal-of-voting-members">
<section id="section-3.1.2.3">
            <h5 id="name-appointment-and-removal-of-">
<a href="#section-3.1.2.3" class="section-number selfRef">3.1.2.3. </a><a href="#name-appointment-and-removal-of-" class="section-name selfRef">Appointment and Removal of Voting Members</a>
            </h5>
<p id="section-3.1.2.3-1">The appointing bodies (i.e., IESG, IAB, 
IRTF Chair, and ISE) shall determine their own processes for 
appointing RSAB members (note that processes related to the RSCE 
are described in <a href="#rsce" class="xref">Section 5</a>). Each appointing body shall have the power 
to remove its appointed RSAB member at its discretion at any time. 
Appointing bodies should ensure that voting members are seated at 
all times and should fill any vacancies with all due speed, if 
necessary on a temporary basis.<a href="#section-3.1.2.3-1" class="pilcrow">¶</a></p>
<p id="section-3.1.2.3-2">In the case that the IRTF Chair or ISE is incapacitated or otherwise 
unable to appoint another person to serve as a delegate, 
the IAB (as the appointing body for the IRTF Chair and ISE)
shall act as the temporary appointing body for those 
streams and shall appoint a temporary member of the RSAB until the 
IAB has appointed an IRTF Chair or ISE, who can then act as an 
RSAB member or appoint a delegate through normal processes.<a href="#section-3.1.2.3-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="vacancies">
<section id="section-3.1.2.4">
            <h5 id="name-vacancies">
<a href="#section-3.1.2.4" class="section-number selfRef">3.1.2.4. </a><a href="#name-vacancies" class="section-name selfRef">Vacancies</a>
            </h5>
<p id="section-3.1.2.4-1">In the case of vacancies by voting members, the RSAB shall operate
as follows:<a href="#section-3.1.2.4-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.1.2.4-2.1">Activities related to implementation of policies already in force
shall continue as normal.<a href="#section-3.1.2.4-2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-3.1.2.4-2.2">Voting on approval of policy documents produced by the RSWG shall be
delayed until the vacancy or vacancies have been filled, up to a maximum of
three (3) months. If a further vacancy arises during this three-month period, the
delay should be extended by up to another three months.  After the delay
period expires, the RSAB should continue to process documents as described
below. Note that this method of handling vacancies does not apply to a vacancy
of the RSCE role; it only applies to vacancies of the stream representatives
enumerated in <a href="#members" class="xref">Section 3.1.2.2</a>.<a href="#section-3.1.2.4-2.2" class="pilcrow">¶</a>
</li>
            </ul>
</section>
</div>
<div id="chair">
<section id="section-3.1.2.5">
            <h5 id="name-chair">
<a href="#section-3.1.2.5" class="section-number selfRef">3.1.2.5. </a><a href="#name-chair" class="section-name selfRef">Chair</a>
            </h5>
<p id="section-3.1.2.5-1">The RSAB shall annually choose a chair from among its members using
a method of its choosing.  If the chair position is
vacated during the chair's term, the RSAB chooses a new chair
from among its members.<a href="#section-3.1.2.5-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="mode-of-operation-1">
<section id="section-3.1.2.6">
            <h5 id="name-mode-of-operation-2">
<a href="#section-3.1.2.6" class="section-number selfRef">3.1.2.6. </a><a href="#name-mode-of-operation-2" class="section-name selfRef">Mode of Operation</a>
            </h5>
<p id="section-3.1.2.6-1">The RSAB is expected to operate via an email discussion list, 
in-person meetings, teleconferencing systems, and any additional 
tooling it deems necessary.<a href="#section-3.1.2.6-1" class="pilcrow">¶</a></p>
<p id="section-3.1.2.6-2">The RSAB shall keep a public record of its proceedings, including
minutes of all meetings and a record of all decisions. The primary
email discussion list used by the RSAB shall be publicly archived, 
although topics that require confidentiality (e.g., personnel 
matters) may be omitted from such archives or discussed in private. 
Similarly, meeting minutes may exclude detailed information about 
topics discussed under executive session but should note that such 
topics were discussed.<a href="#section-3.1.2.6-2" class="pilcrow">¶</a></p>
<p id="section-3.1.2.6-3">The RSAB shall announce plans and agendas for their meetings on the
RFC Editor website and by email to the RSWG at least a week before
such meetings. The meetings shall be open for public attendance, and
the RSAB may consider allowing open participation. If the RSAB needs
to discuss a confidential matter in executive session, that part of
the meeting shall be private to the RSAB, but it must be noted on the
agenda and documented in the minutes with as much detail as
confidentiality requirements permit.<a href="#section-3.1.2.6-3" class="pilcrow">¶</a></p>
<p id="section-3.1.2.6-4">The IETF LLC is requested to provide necessary tooling and staff to support 
RSAB communication, decision processes, and policies.<a href="#section-3.1.2.6-4" class="pilcrow">¶</a></p>
<p id="section-3.1.2.6-5">The IAB is requested to convene the RSAB when it is first formed in
order to formalize the IAB's transfer of authority over the RFC Editor 
Model.<a href="#section-3.1.2.6-5" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
</section>
</div>
<div id="process">
<section id="section-3.2">
        <h3 id="name-process">
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-process" class="section-name selfRef">Process</a>
        </h3>
<p id="section-3.2-1"> This section specifies the RFC Series Policy Definition Process, which shall be followed in producing all Editorial Stream RFCs.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
<div id="intent">
<section id="section-3.2.1">
          <h4 id="name-intent">
<a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-intent" class="section-name selfRef">Intent</a>
          </h4>
<p id="section-3.2.1-1">The intent is to provide an open forum by which policies related to the
RFC Series are defined and evolved. The general expectation is that all
interested parties will participate in the RSWG and that only under
extreme circumstances should RSAB members need to hold CONCERN
positions (as described in <a href="#workflow" class="xref">Section 3.2.2</a>).<a href="#section-3.2.1-1" class="pilcrow">¶</a></p>
<p id="section-3.2.1-2">Because policy issues can be difficult and contentious, RSWG
participants and RSAB members are strongly encouraged to work together
in a spirit of good faith and mutual understanding to achieve rough
consensus (see <span>[<a href="#RFC2418" class="xref">RFC2418</a>]</span>). In particular, RSWG members are
encouraged to take RSAB concerns seriously, and RSAB members are
encouraged to clearly express their concerns early in the process and
to be responsive to the community. All parties are encouraged to respect
the value of each stream and the long-term health and viability of
the RFC Series.<a href="#section-3.2.1-2" class="pilcrow">¶</a></p>
<p id="section-3.2.1-3">This process is intended to be one of continuous consultation. RSAB
members should consult with their constituent stakeholders (e.g.,
authors, editors, tool developers, and consumers of RFCs) on an ongoing
basis, so that when the time comes to consider the approval of a proposal, there should
be no surprises. Appointing bodies are expected to establish whatever
processes they deem appropriate to facilitate this goal.<a href="#section-3.2.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="workflow">
<section id="section-3.2.2">
          <h4 id="name-workflow">
<a href="#section-3.2.2" class="section-number selfRef">3.2.2. </a><a href="#name-workflow" class="section-name selfRef">Workflow</a>
          </h4>
<p id="section-3.2.2-1">The following process shall be used to formulate or modify policies
related to the RFC Series:<a href="#section-3.2.2-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-3.2.2-2">
<li id="section-3.2.2-2.1">An individual or set of individuals generates a proposal in the form 
of an Internet-Draft (which must be submitted in full conformance
with the provisions of <span>[<a href="#BCP78" class="xref">BCP78</a>]</span> and <span>[<a href="#BCP79" class="xref">BCP79</a>]</span>)
and asks the RSWG to adopt the proposal as a working group item.<a href="#section-3.2.2-2.1" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.2">The RSWG may adopt the proposal as a working group item if 
the chairs determine (by following working group procedures for rough 
consensus) that there is sufficient interest in the proposal; this
is similar to the way a working group of the IETF would operate 
(see <span>[<a href="#RFC2418" class="xref">RFC2418</a>]</span>).<a href="#section-3.2.2-2.2" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.3">The RSWG shall then further discuss and develop the proposal. All
participants, but especially RSAB members, should pay special
attention to any aspects of the proposal that have the potential
to significantly modify long-standing policies or historical
characteristics of the RFC Series as described in <a href="#properties" class="xref">Section 7</a>.
Members of the RSAB are expected to participate as individuals in 
all discussions relating to RSWG proposals. This should help to 
ensure that they are fully aware of proposals early in the 
RFC Series Policy Definition Process. It should also help to ensure that RSAB members
will raise any issues or concerns during the development of the 
proposal and not wait until the RSAB review period. The RSWG Chairs 
are also expected to participate as individuals.<a href="#section-3.2.2-2.3" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.4">At some point, if the RSWG Chairs believe there may be rough
consensus for the proposal to advance, they will issue a Last Call
for comments within the working group.<a href="#section-3.2.2-2.4" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.5">After a comment period of suitable length, the RSWG Chairs will
determine whether rough consensus for the proposal exists (taking
their own feedback as individuals into account along with feedback
from other participants). If comments have been received and
substantial changes have been made, additional Last Calls may be
necessary. Once the chairs determine that consensus has been 
reached, they shall announce their determination on the RSWG
email discussion list and forward the document to the RSAB.<a href="#section-3.2.2-2.5" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.6">Once consensus is established in the RSWG, the RSAB shall issue a
community call for comments as further described in <a href="#cfc" class="xref">Section 3.2.3</a>. If 
substantial comments are received in response to the community 
call for comments, the RSAB may return the proposal to the RSWG to 
consider those comments and make revisions to address the feedback
received. In parallel with the community call for comments, the RSAB
itself shall also consider the proposal.<a href="#section-3.2.2-2.6" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.7">If the scope of the revisions made in the previous step is substantial, an 
additional community call for comments should be issued by the RSAB, 
and the feedback received should be considered by the RSWG.<a href="#section-3.2.2-2.7" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.8">Once the RSWG Chairs confirm that concerns received during the
community call(s) for comments have been addressed, they shall
inform the RSAB that the document is ready for balloting by the
RSAB.<a href="#section-3.2.2-2.8" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.9">
              <div id="step9">
<p id="section-3.2.2-2.9.1">Within a reasonable period of time, the RSAB will poll its members 
for their positions on the proposal. Positions may be as follows:<a href="#section-3.2.2-2.9.1" class="pilcrow">¶</a></p>
</div>
<ul class="normal">
<li class="normal" id="section-3.2.2-2.9.2.1">YES: the proposal should be approved<a href="#section-3.2.2-2.9.2.1" class="pilcrow">¶</a>
</li>
                <li class="normal" id="section-3.2.2-2.9.2.2">CONCERN: the proposal raises substantial concerns that must be
addressed<a href="#section-3.2.2-2.9.2.2" class="pilcrow">¶</a>
</li>
                <li class="normal" id="section-3.2.2-2.9.2.3">RECUSE: the person holding the position has a conflict of
interest<a href="#section-3.2.2-2.9.2.3" class="pilcrow">¶</a>
</li>
              </ul>
<p id="section-3.2.2-2.9.3">
Any RSAB member holding a CONCERN position must explain their concern
to the community in detail. Nevertheless, the RSWG might not be able to 
come to consensus on modifications that will address the RSAB member's 
concern.<a href="#section-3.2.2-2.9.3" class="pilcrow">¶</a></p>
<p id="section-3.2.2-2.9.4">
There are three reasons why an RSAB member may file a position of CONCERN:<a href="#section-3.2.2-2.9.4" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.2.2-2.9.5.1">The RSAB member believes that the proposal represents a serious 
problem for one or more of the individual streams.<a href="#section-3.2.2-2.9.5.1" class="pilcrow">¶</a>
</li>
                <li class="normal" id="section-3.2.2-2.9.5.2">The RSAB member believes that the proposal would cause serious harm
to the overall RFC Series, including harm to the long-term health and
viability of the Series.<a href="#section-3.2.2-2.9.5.2" class="pilcrow">¶</a>
</li>
                <li class="normal" id="section-3.2.2-2.9.5.3">The RSAB member believes, based on the results of the community 
call(s) for comments (<a href="#cfc" class="xref">Section 3.2.3</a>), that rough consensus to advance
the proposal is lacking.<a href="#section-3.2.2-2.9.5.3" class="pilcrow">¶</a>
</li>
              </ul>
<p id="section-3.2.2-2.9.6">
Because RSAB members are expected to participate in the discussions 
within the RSWG and to raise any concerns and issues during those 
discussions, most CONCERN positions should not come as a surprise to 
the RSWG. Notwithstanding, late CONCERN positions are always possible
if issues are identified during RSAB review or the community call(s) for comments.<a href="#section-3.2.2-2.9.6" class="pilcrow">¶</a></p>
</li>
            <li id="section-3.2.2-2.10">If a CONCERN exists, discussion will take place within the RSWG.
Again, all RSAB members are expected to participate. If substantial 
changes are made in order to address CONCERN positions, an additional 
community call for comments might be needed.<a href="#section-3.2.2-2.10" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.11">A proposal without any CONCERN positions is approved.<a href="#section-3.2.2-2.11" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.12">If, after a suitable period of time, any CONCERN positions remain,
a vote of the RSAB is taken. If at least three voting members vote
YES, the proposal is approved.<a href="#section-3.2.2-2.12" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.13">If the proposal is not approved, it is returned to the RSWG. The RSWG 
can then consider making further changes.<a href="#section-3.2.2-2.13" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.14">If the proposal is approved, a notification is sent to the community,
and the document enters the queue for publication as an RFC within
the Editorial Stream.<a href="#section-3.2.2-2.14" class="pilcrow">¶</a>
</li>
            <li id="section-3.2.2-2.15">Policies may take effect immediately upon approval by the RSAB and 
before publication of the relevant RFC, unless they are delayed 
while the IETF LLC resolves pending resource or contract issues.<a href="#section-3.2.2-2.15" class="pilcrow">¶</a>
</li>
          </ol>
</section>
</div>
<div id="cfc">
<section id="section-3.2.3">
          <h4 id="name-community-calls-for-comment">
<a href="#section-3.2.3" class="section-number selfRef">3.2.3. </a><a href="#name-community-calls-for-comment" class="section-name selfRef">Community Calls for Comment</a>
          </h4>
<p id="section-3.2.3-1">The RSAB is responsible for initiating and managing community calls
for comments on proposals that have gained consensus within the RSWG.
The RSAB should actively seek a wide range of input. The RSAB seeks
such input by, at a minimum, sending a notice to the <a href="mailto:rfc-interest@rfc-editor.org">rfc‑interest@rfc‑editor.org</a>
email discussion list or to its successor or future equivalent. RSAB members
should also send a notice to the communities they directly represent
(e.g., the IETF and IRTF). Notices are also to be made available and
archived on the RFC Editor website. In addition, other communication
channels can be established for notices (e.g., via an RSS feed or by
posting to social media venues).<a href="#section-3.2.3-1" class="pilcrow">¶</a></p>
<p id="section-3.2.3-2">In cases where a proposal has the potential to significantly modify
long-standing policies or historical characteristics of the RFC
Series as described in <a href="#properties" class="xref">Section 7</a>, the RSAB should take extra 
care to reach out to a very wide range of communities that make use of 
RFCs (as described in <a href="#participation" class="xref">Section 3.1.1.2</a>) since such communities
might not be actively engaged in the RSWG directly. The RSAB should 
work with the stream approving bodies and the IETF LLC to identify and 
establish contacts in such communities, assisted by the 
RSCE in particular.<a href="#section-3.2.3-2" class="pilcrow">¶</a></p>
<p id="section-3.2.3-3">The RSAB should maintain a public list of communities that are
contacted during calls for comments.<a href="#section-3.2.3-3" class="pilcrow">¶</a></p>
<p id="section-3.2.3-4">A notice of a community call for comments contains the following:<a href="#section-3.2.3-4" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.2.3-5.1">A subject line beginning with 'Call for Comments:'<a href="#section-3.2.3-5.1" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.2.3-5.2">A clear, concise summary of the proposal<a href="#section-3.2.3-5.2" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.2.3-5.3">A URL pointing to the Internet-Draft that defines the proposal<a href="#section-3.2.3-5.3" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.2.3-5.4">Any explanations or questions for the community that the RSAB deems
necessary (using their usual decision-making procedures)<a href="#section-3.2.3-5.4" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.2.3-5.5">Clear instructions on how to provide public comments<a href="#section-3.2.3-5.5" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.2.3-5.6">A deadline for comments<a href="#section-3.2.3-5.6" class="pilcrow">¶</a>
</li>
          </ul>
<p id="section-3.2.3-6">A comment period will last not less than two weeks and should be
longer if wide outreach is required. Comments will be publicly
archived on the RFC Editor website.<a href="#section-3.2.3-6" class="pilcrow">¶</a></p>
<p id="section-3.2.3-7">The RSAB is responsible for considering comments received during 
a community call for comments. If RSAB members conclude that such
comments raise important issues that need to be addressed, they 
should do so by discussing those issues within the RSWG or (if 
the issues meet the criteria specified in <a href="#step9" class="xref">Step 9</a> of <a href="#workflow" class="xref">Section 3.2.2</a>) 
lodging a position of CONCERN during RSAB balloting.<a href="#section-3.2.3-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="appeals">
<section id="section-3.2.4">
          <h4 id="name-appeals">
<a href="#section-3.2.4" class="section-number selfRef">3.2.4. </a><a href="#name-appeals" class="section-name selfRef">Appeals</a>
          </h4>
<p id="section-3.2.4-1">Appeals of RSWG Chair decisions shall be made to the RSAB. Decisions of the
RSWG Chairs can be appealed only on grounds of failure to follow the correct
process. Appeals should be made within thirty (30) days of any action or, in
the case of failure to act, of notice having been given to the RSWG Chairs.
The RSAB will then decide if the process was followed and will direct
the RSWG Chairs as to what procedural actions are required.<a href="#section-3.2.4-1" class="pilcrow">¶</a></p>
<p id="section-3.2.4-2">Decisions of the RSAB can be appealed on grounds of failure to follow 
the correct process. In addition, if the RSAB makes a decision in order to resolve 
a disagreement between authors and the RPC (as described in <a href="#disagreements" class="xref">Section 4.4</a>), appeals can 
be filed on the basis that the RSAB misinterpreted an approved policy. 
Aside from these two cases, disagreements about the conduct of the RSAB are not 
subject to appeal. Appeals of RSAB decisions shall be made to the IAB 
and should be made within thirty (30) days of public notice of the 
relevant RSAB decision (typically, when minutes are posted). The IAB 
shall decide whether a process failure occurred and what (if any)
corrective action should take place.<a href="#section-3.2.4-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="coc">
<section id="section-3.2.5">
          <h4 id="name-anti-harassment-policy">
<a href="#section-3.2.5" class="section-number selfRef">3.2.5. </a><a href="#name-anti-harassment-policy" class="section-name selfRef">Anti-Harassment Policy</a>
          </h4>
<p id="section-3.2.5-1">The <a href="https://www.ietf.org/about/groups/iesg/statements/anti-harassment-policy/">IETF anti-harassment policy</a> also applies to the RSWG and RSAB,
which strive to create and maintain an environment in which people
of many different backgrounds are treated with dignity, decency,
and respect. Participants are expected to behave according to
professional standards and to demonstrate appropriate workplace
behavior. For further information about these policies, see
<span>[<a href="#RFC7154" class="xref">RFC7154</a>]</span>, <span>[<a href="#RFC7776" class="xref">RFC7776</a>]</span>, and <span>[<a href="#RFC8716" class="xref">RFC8716</a>]</span>.<a href="#section-3.2.5-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="rfc-boilerplates">
<section id="section-3.2.6">
          <h4 id="name-rfc-boilerplates">
<a href="#section-3.2.6" class="section-number selfRef">3.2.6. </a><a href="#name-rfc-boilerplates" class="section-name selfRef">RFC Boilerplates</a>
          </h4>
<p id="section-3.2.6-1">RFC boilerplates (see <span>[<a href="#RFC7841" class="xref">RFC7841</a>]</span>) are part of the RFC Style Guide, 
as defined in <a href="#practices" class="xref">Section 4.2</a>. New or modified boilerplates
considered under version 3 of the RFC Editor Model must be approved 
by the following parties, each of which has a separate area of 
responsibility with respect to boilerplates:<a href="#section-3.2.6-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.2.6-2.1">The applicable stream, which approves that the boilerplate meets its 
needs<a href="#section-3.2.6-2.1" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.2.6-2.2">The RSAB, which approves that the boilerplate is not in conflict with
the boilerplate used in the other streams<a href="#section-3.2.6-2.2" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.2.6-2.3">The RPC, which approves that the language of the boilerplate is consistent 
with the RFC Style Guide<a href="#section-3.2.6-2.3" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.2.6-2.4">The IETF Trust, which approves that the boilerplate correctly states
the Trust's position regarding rights and ownership<a href="#section-3.2.6-2.4" class="pilcrow">¶</a>
</li>
          </ul>
</section>
</div>
</section>
</div>
</section>
</div>
<div id="policy-implementation">
<section id="section-4">
      <h2 id="name-policy-implementation">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-policy-implementation" class="section-name selfRef">Policy Implementation</a>
      </h2>
<div id="roles-and-processes">
<section id="section-4.1">
        <h3 id="name-roles-and-processes">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-roles-and-processes" class="section-name selfRef">Roles and Processes</a>
        </h3>
<p id="section-4.1-1">Publication of RFCs is handled by the RFC Production Center (RPC).<a href="#section-4.1-1" class="pilcrow">¶</a></p>
<p id="section-4.1-2">A few general considerations apply:<a href="#section-4.1-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4.1-3.1">The general roles and responsibilities of the RPC are defined by
RFCs published in the Editorial Stream (i.e., not directly by the
RSWG, RSAB, or RSCE), by existing RFCs that apply to the 
RPC and have not yet been superseded by Editorial Stream 
RFCs, and by the requisite contracts.<a href="#section-4.1-3.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.1-3.2">The RPC is advised by the RSCE and RSAB, and it has a duty to
consult with them under specific circumstances, such as those
relating to disagreements between authors and the RPC as
described in <a href="#disagreements" class="xref">Section 4.4</a>.<a href="#section-4.1-3.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.1-3.3">The RPC is overseen by the IETF LLC to ensure that
it performs in accordance with contracts in place.<a href="#section-4.1-3.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-4.1-4">All matters of budget, timetable, and impact on its performance
targets are between the RPC and IETF LLC.<a href="#section-4.1-4" class="pilcrow">¶</a></p>
<p id="section-4.1-5">The RPC shall regularly provide reports to the IETF LLC, RSAB, RSWG,
and broader community regarding its activities and any key risks or
issues affecting it.<a href="#section-4.1-5" class="pilcrow">¶</a></p>
<p id="section-4.1-6">In the event that the RPC is required to make a decision without
consultation that would normally deserve consultation, or makes a
decision against the advice of the RSAB, the RPC must notify the
RSAB.<a href="#section-4.1-6" class="pilcrow">¶</a></p>
<p id="section-4.1-7">This document does not specify the exact relationship between the
IETF LLC and the RPC; for example, the work of the RPC could be
performed by a separate corporate entity under contract to the
IETF LLC, it could be performed by employees of the IETF LLC, or
the IETF LLC could engage with independent contractors for some or
all aspects of such work. The exact relationship is a matter for
the IETF LLC to determine.<a href="#section-4.1-7" class="pilcrow">¶</a></p>
<p id="section-4.1-8">The IETF LLC is responsible for the method and management of the
engagement of the RPC. Therefore, the IETF LLC has authority over
negotiating performance targets for the RPC and also has
responsibility for ensuring that those targets are met.  Such
performance targets are set based on the RPC's publication load and
additional efforts required to implement policies specified in
Editorial Stream RFCs, in existing RFCs that apply to the RPC and have
not yet been superseded by Editorial Stream RFCs, and in the requisite
contracts.  The IETF LLC may consult with the community regarding
these targets. The IETF LLC is empowered to appoint a manager or to
convene a committee to complete these activities.<a href="#section-4.1-8" class="pilcrow">¶</a></p>
<p id="section-4.1-9">If individuals or groups within the community have concerns about the
performance of the RPC, they can request that the matter be investigated
by the IETF LLC Board, the IETF Executive Director, or a point of 
contact designated by the IETF LLC Board. Even if the IETF LLC opts to 
delegate this activity, concerns should be raised with the IETF LLC. 
The IETF LLC is ultimately answerable to the community via the mechanisms 
outlined in <span>[<a href="#RFC8711" class="xref">RFC8711</a>]</span>.<a href="#section-4.1-9" class="pilcrow">¶</a></p>
</section>
</div>
<div id="practices">
<section id="section-4.2">
        <h3 id="name-working-practices">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-working-practices" class="section-name selfRef">Working Practices</a>
        </h3>
<p id="section-4.2-1">In the absence of a high-level policy documented in an RFC or in the 
interest of specifying the detail of its implementation of such policies, the RPC can 
document working practices regarding the editorial preparation,
final publication, and dissemination of RFCs. Examples include:<a href="#section-4.2-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4.2-2.1">Maintenance of a style guide that defines editorial standards for 
RFCs; specifically, the RFC Style Guide consists of <span>[<a href="#RFC7322" class="xref">RFC7322</a>]</span> and
the other documents and resources listed at <span>[<a href="#STYLEGUIDE" class="xref">STYLEGUIDE</a>]</span>.<a href="#section-4.2-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.2-2.2">Instructions regarding the file formats that are accepted as input to the
editing and publication process.<a href="#section-4.2-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.2-2.3">Guidelines regarding the final structure and layout of published documents.
In the context of the XML vocabulary <span>[<a href="#RFC7991" class="xref">RFC7991</a>]</span>, such guidelines could
include clarifications regarding the preferred XML elements and attributes used to
capture the semantic content of RFCs.<a href="#section-4.2-2.3" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
<div id="rpc">
<section id="section-4.3">
        <h3 id="name-rpc-responsibilities">
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-rpc-responsibilities" class="section-name selfRef">RPC Responsibilities</a>
        </h3>
<p id="section-4.3-1">The core responsibility of the RPC is the implementation of RFC Series 
policies through publication of RFCs (including the dimensions of document
quality, timeliness of publication, and accessibility of results), while
taking into account issues raised by the community through the RSWG and
by the stream approving bodies. More specifically, the RPC's responsibilities
at the time of writing include the following:<a href="#section-4.3-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-4.3-2">
<li id="section-4.3-2.1">Editing documents originating from all RFC streams to ensure that
they are consistent with the editorial standards specified in the 
RFC Style Guide.<a href="#section-4.3-2.1" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.2">Creating and preserving records of edits performed on documents.<a href="#section-4.3-2.2" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.3">Identifying where editorial changes might have technical impact
and seeking necessary clarification.<a href="#section-4.3-2.3" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.4">Establishing the publication readiness of each document through
communication with the authors, IANA, or stream-specific contacts, 
supplemented if needed by the RSAB and RSCE.<a href="#section-4.3-2.4" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.5">Creating and preserving records of dialogue with document authors.<a href="#section-4.3-2.5" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.6">Requesting advice from the RSAB and RSCE as needed.<a href="#section-4.3-2.6" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.7">Providing suggestions to the RSAB and RSCE as needed.<a href="#section-4.3-2.7" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.8">Participating within the RSWG in the creation of new Editorial 
Stream RFCs that impact the RPC, specifically with respect to any 
challenges the RPC might foresee with regard to implementation of 
proposed policies.<a href="#section-4.3-2.8" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.9">Identifying topics and issues while processing 
documents or carrying out other responsibilities on this list for 
which they lack sufficient expertise, and identifying and conferring 
with relevant experts as needed.<a href="#section-4.3-2.9" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.10">Providing reports to the community on its performance and plans.<a href="#section-4.3-2.10" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.11">Consulting with the community on its plans.<a href="#section-4.3-2.11" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.12">Negotiating its specific plans and resources with the IETF LLC.<a href="#section-4.3-2.12" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.13">Providing sufficient resources to support reviews of RPC
performance by the IETF LLC.<a href="#section-4.3-2.13" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.14">Coordinating with IANA to ensure that RFCs accurately document 
registration processes and assigned values for IANA registries.<a href="#section-4.3-2.14" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.15">Assigning RFC numbers.<a href="#section-4.3-2.15" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.16">Liaising with stream approving bodies and other representatives of the
streams as needed.<a href="#section-4.3-2.16" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.17">
            <p id="section-4.3-2.17.1">Publishing RFCs, which includes:<a href="#section-4.3-2.17.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4.3-2.17.2.1">posting copies to the RFC Editor site both individually and in collections<a href="#section-4.3-2.17.2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-4.3-2.17.2.2">depositing copies with external archives<a href="#section-4.3-2.17.2.2" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-4.3-2.17.2.3">creating catalogs and catalog entries<a href="#section-4.3-2.17.2.3" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-4.3-2.17.2.4">announcing the publication to interested parties<a href="#section-4.3-2.17.2.4" class="pilcrow">¶</a>
</li>
            </ul>
</li>
          <li id="section-4.3-2.18">Providing online access to RFCs.<a href="#section-4.3-2.18" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.19">Providing an online system to facilitate the submission, management,
and display of errata to RFCs.<a href="#section-4.3-2.19" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.20">Maintaining the RFC Editor website.<a href="#section-4.3-2.20" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.21">Providing for the backup of RFCs.<a href="#section-4.3-2.21" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.22">Ensuring the storage and preservation of records.<a href="#section-4.3-2.22" class="pilcrow">¶</a>
</li>
          <li id="section-4.3-2.23">Authenticating RFCs for legal proceedings.<a href="#section-4.3-2.23" class="pilcrow">¶</a>
</li>
        </ol>
</section>
</div>
<div id="disagreements">
<section id="section-4.4">
        <h3 id="name-resolution-of-disagreements">
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-resolution-of-disagreements" class="section-name selfRef">Resolution of Disagreements between Authors and the RPC</a>
        </h3>
<p id="section-4.4-1">During the process of editorial preparation and publication, disagreements
can arise between the authors of an RFC-to-be and the RPC. Where an existing
policy clearly applies, typically such disagreements are handled in a
straightforward manner through direct consultation between the authors and
the RPC, sometimes in collaboration with stream-specific contacts.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
<p id="section-4.4-2">However, if it is unclear whether an existing policy applies or if it is 
unclear how to interpret an existing policy, the parties may need to
consult with additional individuals or bodies (e.g., RSAB, IESG, IRSG, or
stream approving bodies) to help achieve a resolution. The following points are
intended to provide more specific guidance.<a href="#section-4.4-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4.4-3.1">If there is a conflict with a policy for a particular stream, to help 
achieve a resolution, the RPC should consult with the relevant stream 
approving body (such as the IESG or IRSG) and other representatives of 
the relevant stream as appropriate.<a href="#section-4.4-3.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.4-3.2">If there is a conflict with a cross-stream policy, the RPC should consult
with the RSAB to achieve a resolution.<a href="#section-4.4-3.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.4-3.3">The disagreement might raise a new issue that is not covered by an existing
policy or that cannot be resolved through consultation between the RPC and
other relevant individuals and bodies, as described above. In this case,
the RSAB is responsible for (a) resolving the disagreement in a timely manner
if necessary so that the relevant stream document(s) can be published before a 
new policy is defined and (b) bringing the issue to the RSWG so that a new policy 
can be defined.<a href="#section-4.4-3.3" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
<div id="point-of-contact">
<section id="section-4.5">
        <h3 id="name-point-of-contact">
<a href="#section-4.5" class="section-number selfRef">4.5. </a><a href="#name-point-of-contact" class="section-name selfRef">Point of Contact</a>
        </h3>
<p id="section-4.5-1">From time to time, individuals or organizations external to the IETF and
the broader RFC Series community may have questions about the RFC Series.
Such inquiries should be directed to the
<a href="mailto:rfc-editor@rfc-editor.org">rfc‑editor@rfc‑editor.org</a> email
alias or to its successor or future equivalent and then handled by the 
appropriate bodies (e.g., RSAB and RPC) or individuals (e.g., RSWG Chairs and RSCE).<a href="#section-4.5-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="administrative-implementation">
<section id="section-4.6">
        <h3 id="name-administrative-implementati">
<a href="#section-4.6" class="section-number selfRef">4.6. </a><a href="#name-administrative-implementati" class="section-name selfRef">Administrative Implementation</a>
        </h3>
<p id="section-4.6-1">The exact implementation of the administrative and contractual
activities described here are a responsibility of the IETF LLC. This
section provides general guidance regarding several aspects of such
activities.<a href="#section-4.6-1" class="pilcrow">¶</a></p>
<div id="vendor-selection-for-the-rfc-production-center">
<section id="section-4.6.1">
          <h4 id="name-vendor-selection-for-the-rp">
<a href="#section-4.6.1" class="section-number selfRef">4.6.1. </a><a href="#name-vendor-selection-for-the-rp" class="section-name selfRef">Vendor Selection for the RPC</a>
          </h4>
<p id="section-4.6.1-1">Vendor selection is done in cooperation with the streams and
under the final authority of the IETF LLC.<a href="#section-4.6.1-1" class="pilcrow">¶</a></p>
<p id="section-4.6.1-2">The IETF LLC develops the work definition (the Statement of Work)
for the RPC and manages the vendor-selection process.  The work
definition is created within the IETF LLC budget and takes into
account the RPC responsibilities (as described in <a href="#rpc" class="xref">Section 4.3</a>), 
the needs of the streams, and community input.<a href="#section-4.6.1-2" class="pilcrow">¶</a></p>
<p id="section-4.6.1-3">The process to select and contract for the RPC
and other RFC-related services is as follows:<a href="#section-4.6.1-3" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4.6.1-4.1">The IETF LLC establishes the contract process, including the steps
necessary to issue a Request for Proposal (RFP) when necessary, the timing, and the
contracting procedures.<a href="#section-4.6.1-4.1" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-4.6.1-4.2">The IETF LLC establishes a selection committee, which will
consist of the IETF Executive Director and other
members selected by the IETF LLC in consultation with the
stream approving bodies. The committee shall select a chair from
among its members.<a href="#section-4.6.1-4.2" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-4.6.1-4.3">The selection committee selects the vendor, subject to the
successful negotiation of a contract approved by the IETF LLC.  In
the event that a contract cannot be signed, the matter shall be
referred to the selection committee for further action.<a href="#section-4.6.1-4.3" class="pilcrow">¶</a>
</li>
          </ul>
</section>
</div>
<div id="budget">
<section id="section-4.6.2">
          <h4 id="name-budget">
<a href="#section-4.6.2" class="section-number selfRef">4.6.2. </a><a href="#name-budget" class="section-name selfRef">Budget</a>
          </h4>
<p id="section-4.6.2-1">Most expenses discussed in this document are not new expenses. They
have been and remain part of the IETF LLC budget.<a href="#section-4.6.2-1" class="pilcrow">¶</a></p>
<p id="section-4.6.2-2">The RFC Series portion of the IETF LLC budget shall include funding
to support the RSCE, the RFC Production Center, and the Independent
Stream.<a href="#section-4.6.2-2" class="pilcrow">¶</a></p>
<p id="section-4.6.2-3">The IETF LLC has the responsibility to approve the total RFC Editor
budget (and the authority to deny it). All relevant parties must work
within the IETF LLC budgetary process.<a href="#section-4.6.2-3" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
</section>
</div>
<div id="rsce">
<section id="section-5">
      <h2 id="name-rfc-series-consulting-edito">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-rfc-series-consulting-edito" class="section-name selfRef">RFC Series Consulting Editor (RSCE)</a>
      </h2>
<p id="section-5-1">The RFC Series Consulting Editor (RSCE) is a senior technical
publishing professional who will apply their deep knowledge of
technical publishing processes to the RFC Series.<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2">The primary responsibilities of the RSCE are as follows:<a href="#section-5-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5-3.1">Serve as a voting member on the RSAB<a href="#section-5-3.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-3.2">Identify problems with the RFC publication process and
opportunities for improvement<a href="#section-5-3.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-3.3">Provide expert advice within the RSWG regarding policy proposals<a href="#section-5-3.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-3.4">Provide expert advice to the RPC and IETF LLC<a href="#section-5-3.4" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-5-4">Matters on which the RSCE might provide guidance could include the
following (see also <span><a href="https://www.rfc-editor.org/rfc/rfc8729#section-4" class="relref">Section 4</a> of [<a href="#RFC8729" class="xref">RFC8729</a>]</span>):<a href="#section-5-4" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5-5.1">Editing, processing, and publication of RFCs<a href="#section-5-5.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-5.2">Publication formats for the RFC Series<a href="#section-5-5.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-5.3">Changes to the RFC Style Guide<a href="#section-5-5.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-5.4">Series-wide guidelines regarding document content and quality<a href="#section-5-5.4" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-5.5">Web presence for the RFC Series<a href="#section-5-5.5" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-5.6">Copyright matters related to the RFC Series<a href="#section-5-5.6" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-5.7">Archiving, indexing, and accessibility of RFCs<a href="#section-5-5.7" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-5-6">The IETF LLC is responsible for the method and management of the
engagement of the RSCE, including selection, evaluation, and the timely
filling of any vacancy. Therefore, whether the RSCE role is structured
as a contractual or employee relationship is a matter for the IETF LLC
to determine.<a href="#section-5-6" class="pilcrow">¶</a></p>
<div id="rsce-selection">
<section id="section-5.1">
        <h3 id="name-rsce-selection">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-rsce-selection" class="section-name selfRef">RSCE Selection</a>
        </h3>
<p id="section-5.1-1">Responsibility for making a recommendation to the IETF LLC regarding
the RSCE role will lie with a selection committee.  The IETF LLC should
propose an initial slate of members for this committee, making sure
to include community members with diverse perspectives, and consult with the stream
representatives regarding the final membership of the committee.  In
making its recommendation for the role of RSCE, the selection
committee will take into account the definition of the role as well
as any other information that the committee deems necessary or
helpful in making its decision.  The IETF LLC is responsible for
contracting or employment of the RSCE.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="rsce-performance-evaluation">
<section id="section-5.2">
        <h3 id="name-rsce-performance-evaluation">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-rsce-performance-evaluation" class="section-name selfRef">RSCE Performance Evaluation</a>
        </h3>
<p id="section-5.2-1">Periodically, the IETF LLC will evaluate the performance of the 
RSCE, including a call for confidential input from the community. 
The IETF LLC will produce a draft evaluation of the RSCE's 
performance for review by RSAB members (other than the RSCE), 
who will provide feedback to the IETF LLC.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="temporary-rsce-appointment">
<section id="section-5.3">
        <h3 id="name-temporary-rsce-appointment">
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-temporary-rsce-appointment" class="section-name selfRef">Temporary RSCE Appointment</a>
        </h3>
<p id="section-5.3-1">In the case that the currently appointed RSCE is expected to be 
unavailable for an extended period, the IETF LLC may appoint a 
Temporary RSCE through whatever recruitment process it considers 
appropriate. A Temporary RSCE acts as the RSCE in all aspects 
during their term of appointment.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="conflict-of-interest">
<section id="section-5.4">
        <h3 id="name-conflict-of-interest">
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-conflict-of-interest" class="section-name selfRef">Conflict of Interest</a>
        </h3>
<p id="section-5.4-1">The RSCE is expected to avoid even the appearance of conflict of
interest or judgment in performing their role.  To ensure this, the
RSCE will be subject to a conflict-of-interest policy established by
the IETF LLC.<a href="#section-5.4-1" class="pilcrow">¶</a></p>
<p id="section-5.4-2">The RPC service provider may contract services from the RSCE service 
provider, and vice versa, including services provided to the IETF 
LLC.  All contracts between the two must be disclosed to the IETF LLC.
Where those services are related to services provided to the IETF LLC, 
IETF LLC policies shall apply, including publication of relevant parts 
of the contract.<a href="#section-5.4-2" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="editorial-stream">
<section id="section-6">
      <h2 id="name-editorial-stream">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-editorial-stream" class="section-name selfRef">Editorial Stream</a>
      </h2>
<p id="section-6-1">This document creates the Editorial Stream as a separate space for
publication of policies, procedures, guidelines, rules, and related
information regarding the RFC Series as a whole.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">The Editorial Stream shall be used only to specify and update policies,
procedures, guidelines, rules, and related information regarding the
RFC Series as a whole; no other use of the Editorial Stream is authorized
by this memo, and no other streams are so authorized. This policy may be
changed only by agreement of the IAB, IESG, and IETF LLC.<a href="#section-6-2" class="pilcrow">¶</a></p>
<p id="section-6-3">All documents produced by the RSWG and approved by the RSAB shall be
published as RFCs in the Editorial Stream with a status of Informational.
(Note that the Editorial Stream is not authorized to publish RFCs that
are Standards Track or Best Current Practice, since such RFCs are
reserved for the IETF Stream <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span>.) Notwithstanding the status
of Informational, it should be understood that documents published
in the Editorial Stream define policies for the RFC Series as a whole.<a href="#section-6-3" class="pilcrow">¶</a></p>
<p id="section-6-4">The requirements and process for creating any additional RFC streams are
outside the scope of this document.<a href="#section-6-4" class="pilcrow">¶</a></p>
<div id="procedures-request-of-the-ietf-trust">
<section id="section-6.1">
        <h3 id="name-procedures-request-of-the-i">
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-procedures-request-of-the-i" class="section-name selfRef">Procedures Request of the IETF Trust</a>
        </h3>
<p id="section-6.1-1">The IAB requests that the IETF Trust and its Trustees assist in
meeting the goals and procedures set forth in this document.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
<p id="section-6.1-2">The Trustees are requested to publicly confirm their willingness and
ability to accept responsibility for the Intellectual Property Rights
(IPR) for the Editorial Stream.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
<p id="section-6.1-3">Specifically, the Trustees are asked to develop the necessary
boilerplate to enable the suitable marking of documents so that the
IETF Trust receives the rights as specified in <span>[<a href="#BCP78" class="xref">BCP78</a>]</span>.  These
procedures need to also allow authors to indicate either no rights to
make derivative works or, preferentially, the right to make unlimited
derivative works from the documents.  It is left to the Trust to
specify exactly how this shall be clearly indicated in each document.<a href="#section-6.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="patent-and-trademark-rules-for-the-editorial-stream">
<section id="section-6.2">
        <h3 id="name-patent-and-trademark-rules-">
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-patent-and-trademark-rules-" class="section-name selfRef">Patent and Trademark Rules for the Editorial Stream</a>
        </h3>
<p id="section-6.2-1">As specified above, contributors of documents for the Editorial Stream 
are expected to use the IETF Internet-Draft process, complying therein
with the rules specified in <span>[<a href="#BCP9" class="xref">BCP9</a>]</span>. This includes 
the disclosure of patent and trademark issues that are known, or can be
reasonably expected to be known, to the contributor.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
<p id="section-6.2-2">Disclosure of license terms for patents is also requested, as
specified in <span>[<a href="#BCP79" class="xref">BCP79</a>]</span>. The Editorial 
Stream has chosen to use the <a href="https://www.ietf.org/ipr/">IETF's IPR disclosure mechanism</a> for this purpose.  The IAB would prefer that
the most liberal terms possible be made available for Editorial Stream 
documents. Terms that do not require fees or licensing are preferable.
Non-discriminatory terms are strongly preferred over those that
discriminate among users.  However, although disclosure is required
and the RSWG and the RSAB may consider disclosures and terms in making 
a decision as to whether to submit a document for publication, there 
are no specific requirements on the licensing terms for intellectual
property related to Editorial Stream publication.<a href="#section-6.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="editorial-stream-boilerplate">
<section id="section-6.3">
        <h3 id="name-editorial-stream-boilerplat">
<a href="#section-6.3" class="section-number selfRef">6.3. </a><a href="#name-editorial-stream-boilerplat" class="section-name selfRef">Editorial Stream Boilerplate</a>
        </h3>
<p id="section-6.3-1">This document specifies the following text for the "Status of This Memo"
section of RFCs published in the Editorial Stream. Any changes to this
boilerplate must be made through the RFC Series Policy Definition Process
specified in <a href="#policy-definition" class="xref">Section 3</a> of this document.<a href="#section-6.3-1" class="pilcrow">¶</a></p>
<p id="section-6.3-2">Because all Editorial Stream RFCs have a status of Informational,
the first paragraph of the "Status of This Memo" section shall be
as specified in <span><a href="https://www.rfc-editor.org/rfc/rfc7841#appendix-A.2.1" class="relref">Appendix A.2.1</a> of [<a href="#RFC7841" class="xref">RFC7841</a>]</span>.<a href="#section-6.3-2" class="pilcrow">¶</a></p>
<p id="section-6.3-3">The second paragraph of the "Status of This Memo" section shall be
as follows:<a href="#section-6.3-3" class="pilcrow">¶</a></p>
<p style="margin-left: 1.5em" id="section-6.3-4">This document is a product of the RFC Series Policy Definition Process.
It represents the consensus of the RFC Series Working Group approved by
the RFC Series Approval Board. Such documents are not candidates for any
level of Internet Standard; see Section 2 of RFC 7841.<a href="#section-6.3-4" class="pilcrow">¶</a></p>
<p id="section-6.3-5">The third paragraph of the "Status of This Memo" section shall be
as specified in <span><a href="https://www.rfc-editor.org/rfc/rfc7841#section-3.5" class="relref">Section 3.5</a> of [<a href="#RFC7841" class="xref">RFC7841</a>]</span>.<a href="#section-6.3-5" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="properties">
<section id="section-7">
      <h2 id="name-historical-properties-of-th">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-historical-properties-of-th" class="section-name selfRef">Historical Properties of the RFC Series</a>
      </h2>
<p id="section-7-1">This section lists some of the properties that have been 
historically regarded as important to the RFC Series. Proposals 
that affect these properties are possible within the processes 
defined in this document. As described in Sections <a href="#workflow" class="xref">3.2.2</a> and <a href="#cfc" class="xref">3.2.3</a>,
proposals that might have a detrimental effect on these properties
should receive heightened scrutiny during RSWG discussion and RSAB 
review. The purpose of this scrutiny is to ensure that all changes are 
deliberate and that the consequences of a proposal, as far as they can be
identified, have been carefully considered.<a href="#section-7-1" class="pilcrow">¶</a></p>
<div id="availability">
<section id="section-7.1">
        <h3 id="name-availability">
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-availability" class="section-name selfRef">Availability</a>
        </h3>
<p id="section-7.1-1">Documents in the RFC Series have been available for many decades, 
with no restrictions on access or distribution.<a href="#section-7.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="accessibility">
<section id="section-7.2">
        <h3 id="name-accessibility">
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-accessibility" class="section-name selfRef">Accessibility</a>
        </h3>
<p id="section-7.2-1">RFC Series documents have been published in a format that was intended 
to be as accessible as possible to people with disabilities, e.g., 
people with impaired sight.<a href="#section-7.2-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="language">
<section id="section-7.3">
        <h3 id="name-language">
<a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-language" class="section-name selfRef">Language</a>
        </h3>
<p id="section-7.3-1">All existing RFC Series documents have been published in English. 
However, since the beginning of the RFC Series, documents have been
published under terms that explicitly allow translation into 
languages other than English without asking for permission.<a href="#section-7.3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="diversity">
<section id="section-7.4">
        <h3 id="name-diversity">
<a href="#section-7.4" class="section-number selfRef">7.4. </a><a href="#name-diversity" class="section-name selfRef">Diversity</a>
        </h3>
<p id="section-7.4-1">The RFC Series has included many types of documents including standards for
the Internet, procedural and informational documents, thought experiments,
speculative ideas, research papers, histories, humor, and even eulogies.<a href="#section-7.4-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="quality">
<section id="section-7.5">
        <h3 id="name-quality">
<a href="#section-7.5" class="section-number selfRef">7.5. </a><a href="#name-quality" class="section-name selfRef">Quality</a>
        </h3>
<p id="section-7.5-1">RFC Series documents have been reviewed for subject matter quality and 
edited by professionals with a goal of ensuring that documents are clear, 
consistent, and readable <span>[<a href="#RFC7322" class="xref">RFC7322</a>]</span>.<a href="#section-7.5-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="stability">
<section id="section-7.6">
        <h3 id="name-stability">
<a href="#section-7.6" class="section-number selfRef">7.6. </a><a href="#name-stability" class="section-name selfRef">Stability</a>
        </h3>
<p id="section-7.6-1">Once published, RFC Series documents are not changed.<a href="#section-7.6-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="longevity">
<section id="section-7.7">
        <h3 id="name-longevity">
<a href="#section-7.7" class="section-number selfRef">7.7. </a><a href="#name-longevity" class="section-name selfRef">Longevity</a>
        </h3>
<p id="section-7.7-1">RFC Series documents have been published in a form intended to be 
comprehensible to humans for decades or longer.<a href="#section-7.7-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="updates-to-this-document">
<section id="section-8">
      <h2 id="name-updates-to-this-document">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-updates-to-this-document" class="section-name selfRef">Updates to This Document</a>
      </h2>
<p id="section-8-1">Updates, amendments, and refinements to this document can be produced 
using the process documented herein but shall be published and operative only after 
(a) obtaining the agreement of the IAB and the IESG and (b) ensuring
that the IETF LLC has no objections regarding its ability to implement 
any proposed changes.<a href="#section-8-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="changes">
<section id="section-9">
      <h2 id="name-changes-from-version-2-of-t">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-changes-from-version-2-of-t" class="section-name selfRef">Changes from Version 2 of the RFC Editor Model</a>
      </h2>
<p id="section-9-1">The processes and organizational models for publication of RFCs
have changed significantly over the years. Most recently, in 2009,
<span>[<a href="#RFC5620" class="xref">RFC5620</a>]</span> defined the RFC Editor Model (Version 1), and in 2012,
<span>[<a href="#RFC6635" class="xref">RFC6635</a>]</span> defined the RFC Editor Model (Version 2), which was then
modified slightly in 2020 by <span>[<a href="#RFC8728" class="xref">RFC8728</a>]</span>.<a href="#section-9-1" class="pilcrow">¶</a></p>
<p id="section-9-2">However, the community experienced several problems with versions 1 
and 2, including a lack of transparency, a lack of avenues 
for community input into policy definition, and unclear lines of 
authority and responsibility.<a href="#section-9-2" class="pilcrow">¶</a></p>
<p id="section-9-3">To address these problems, in 2020, the IAB formed the RFC Editor 
Future Development Program to conduct a community discussion and 
consensus process for the further evolution of the RFC Editor Model. 
Under the auspices of this Program, the community considered changes 
that would increase transparency and community input regarding the 
definition of policies for the RFC Series as a whole, while at 
the same time ensuring the continuity of the RFC Series, 
maintaining the quality and timely publication of RFCs, 
ensuring document accessibility, and clarifying lines of 
authority and responsibility.<a href="#section-9-3" class="pilcrow">¶</a></p>
<p id="section-9-4">This document is the result of discussion within the Program and
describes version 3 of the RFC Editor Model while remaining 
consistent with <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span>.<a href="#section-9-4" class="pilcrow">¶</a></p>
<p id="section-9-5">The following sections describe the changes from version 2 in 
more detail.<a href="#section-9-5" class="pilcrow">¶</a></p>
<div id="rfc-editor-function">
<section id="section-9.1">
        <h3 id="name-rfc-editor-function">
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-rfc-editor-function" class="section-name selfRef">RFC Editor Function</a>
        </h3>
<p id="section-9.1-1">Several responsibilities previously assigned to the RFC Editor
or, more precisely, the RFC Editor function, are now performed
by the RSWG, RSAB, RPC, RSCE, and IETF LLC (alone or in combination).
These include various aspects of strategic leadership 
(<span><a href="https://www.rfc-editor.org/rfc/rfc8728#section-2.1.1" class="relref">Section 2.1.1</a> of [<a href="#RFC8728" class="xref">RFC8728</a>]</span>), representation of the RFC Series 
(<span><a href="https://www.rfc-editor.org/rfc/rfc8728#section-2.1.2" class="relref">Section 2.1.2</a> of [<a href="#RFC8728" class="xref">RFC8728</a>]</span>), development of RFC production and
publication (<span><a href="https://www.rfc-editor.org/rfc/rfc8728#section-2.1.3" class="relref">Section 2.1.3</a> of [<a href="#RFC8728" class="xref">RFC8728</a>]</span>), development of the
RFC Series (<span><a href="https://www.rfc-editor.org/rfc/rfc8728#section-2.1.4" class="relref">Section 2.1.4</a> of [<a href="#RFC8728" class="xref">RFC8728</a>]</span>), operational oversight
(<span><a href="https://www.rfc-editor.org/rfc/rfc8729#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC8729" class="xref">RFC8729</a>]</span>), policy oversight 
(<span><a href="https://www.rfc-editor.org/rfc/rfc8729#section-3.4" class="relref">Section 3.4</a> of [<a href="#RFC8729" class="xref">RFC8729</a>]</span>), the editing, processing, and publication of
documents (<span><a href="https://www.rfc-editor.org/rfc/rfc8729#section-4.2" class="relref">Section 4.2</a> of [<a href="#RFC8729" class="xref">RFC8729</a>]</span>), and development and
maintenance of guidelines and rules that apply to the RFC Series
(<span><a href="https://www.rfc-editor.org/rfc/rfc8729#section-4.4" class="relref">Section 4.4</a> of [<a href="#RFC8729" class="xref">RFC8729</a>]</span>). Among other things, this changes the dependency on
the RFC Series Editor (RSE) included in <span><a href="https://www.rfc-editor.org/rfc/rfc8730#section-2.2" class="relref">Section 2.2</a> of [<a href="#RFC8730" class="xref">RFC8730</a>]</span> with regard to 
"coordinating work and conforming to general RFC Series policies
as specified by the IAB and RSE." In addition, various details 
regarding these responsibilities have been modified to accord with 
the framework defined in this document.<a href="#section-9.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="rfc-series-editor">
<section id="section-9.2">
        <h3 id="name-rfc-series-editor">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-rfc-series-editor" class="section-name selfRef">RFC Series Editor</a>
        </h3>
<p id="section-9.2-1">Implied by the changes outlined in the previous section, the
responsibilities of the RFC Series Editor (RSE) as a person or
role (contrasted with the overall RFC Editor function) are now
split or shared among the RSWG, RSAB, RSCE, RPC, and IETF LLC (alone
or in combination). More specifically, the responsibilities of
the RFC Series Consulting Editor (RSCE) under version 3 of the RFC
Editor Model differ in many ways from the responsibilities of the
RFC Series Editor under version 2 of the RFC Editor Model. In general,
references in existing documents to the RSE can be taken as
referring to the RFC Editor function as described herein but
should not be taken as referring to the RSCE.<a href="#section-9.2-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="rfc-publisher">
<section id="section-9.3">
        <h3 id="name-rfc-publisher">
<a href="#section-9.3" class="section-number selfRef">9.3. </a><a href="#name-rfc-publisher" class="section-name selfRef">RFC Publisher</a>
        </h3>
<p id="section-9.3-1">In practice, the RFC Production Center (RPC) and RFC Publisher roles
have been performed by the same entity, and this practice is expected
to continue; therefore, this document dispenses with the distinction
between these roles and refers only to the RPC.<a href="#section-9.3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="iab">
<section id="section-9.4">
        <h3 id="name-iab">
<a href="#section-9.4" class="section-number selfRef">9.4. </a><a href="#name-iab" class="section-name selfRef">IAB</a>
        </h3>
<p id="section-9.4-1">Under earlier versions of the RFC Editor Model, the IAB was
responsible for oversight of the RFC Series and acted as a body
for final conflict resolution regarding the RFC Series. The IAB's
authority in these matters is described in the IAB Charter
(<span>[<a href="#RFC2850" class="xref">RFC2850</a>]</span>, as updated by <span>[<a href="#RFC9283" class="xref">RFC9283</a>]</span>).
Under version 2 of the RFC Editor Model, the IAB delegated some
of its authority to the RFC Series Oversight Committee (see <a href="#rsoc" class="xref">Section 9.5</a>).
Under version 3 of the RFC Editor Model, authority for policy definition
resides with the RSWG as an independent venue for work by members
of the community (with approval of policy proposals being the
responsibility of the RSAB, which represents the streams and includes
the RSCE), whereas authority for policy implementation resides with
the IETF LLC.<a href="#section-9.4-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="rsoc">
<section id="section-9.5">
        <h3 id="name-rfc-series-oversight-commit">
<a href="#section-9.5" class="section-number selfRef">9.5. </a><a href="#name-rfc-series-oversight-commit" class="section-name selfRef">RFC Series Oversight Committee (RSOC)</a>
        </h3>
<p id="section-9.5-1">In practice, the relationships and lines of authority and responsibility
between the IAB, RSOC, and RSE have proved unwieldy and somewhat opaque.
To overcome some of these issues, this document dispenses with the RSOC.
References to the RSOC in documents such as <span>[<a href="#RFC8730" class="xref">RFC8730</a>]</span> are obsolete
because this document disbands the RSOC.<a href="#section-9.5-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="rfc-series-advisory-group-rsag">
<section id="section-9.6">
        <h3 id="name-rfc-series-advisory-group-r">
<a href="#section-9.6" class="section-number selfRef">9.6. </a><a href="#name-rfc-series-advisory-group-r" class="section-name selfRef">RFC Series Advisory Group (RSAG)</a>
        </h3>
<p id="section-9.6-1">Version 1 of the RFC Editor Model <span>[<a href="#RFC5620" class="xref">RFC5620</a>]</span> specified the existence of
the RFC Series Advisory Group (RSAG), which was no longer specified in
version 2 of the RFC Editor Model. For the avoidance of doubt, this document affirms
that the RSAG has been disbanded. (The RSAG is not to be confused with the
RFC Series Approval Board (RSAB), which this document establishes.)<a href="#section-9.6-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="editorial-stream-1">
<section id="section-9.7">
        <h3 id="name-editorial-stream-2">
<a href="#section-9.7" class="section-number selfRef">9.7. </a><a href="#name-editorial-stream-2" class="section-name selfRef">Editorial Stream</a>
        </h3>
<p id="section-9.7-1">This document creates the Editorial Stream in addition to the streams
already described in <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span>.<a href="#section-9.7-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="security-considerations">
<section id="section-10">
      <h2 id="name-security-considerations">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-10-1">The same security considerations as those in <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span> apply.
The processes for the publication of documents must prevent the
introduction of unapproved changes. Because multiple entities 
described in this document (most especially the RPC) participate in 
maintenance of the index of publications, sufficient security must be in place to
prevent these published documents from being changed by external
parties. The archive of RFC documents, any source documents needed
to recreate the RFC documents, and any associated original documents
(such as lists of errata, tools, and, for some early items, originals
that are not machine-readable) need to be secured against
data storage failure.<a href="#section-10-1" class="pilcrow">¶</a></p>
<p id="section-10-2">The IETF LLC (along with any other contracting or contracted entities) 
should take these security considerations into account
during the implementation and enforcement of any relevant contracts.<a href="#section-10-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="iana-considerations">
<section id="section-11">
      <h2 id="name-iana-considerations">
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-11-1">The RPC is responsible for coordinating with the IANA to ensure that
RFCs accurately document registration processes and assigned values
for IANA registries.<a href="#section-11-1" class="pilcrow">¶</a></p>
<p id="section-11-2">The IETF LLC facilitates management of the relationship between the RPC 
and IANA.<a href="#section-11-2" class="pilcrow">¶</a></p>
<p id="section-11-3">This document does not create a new registry nor does it register any
values in existing registries, and no IANA action is required.<a href="#section-11-3" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-12">
      <h2 id="name-references">
<a href="#section-12" class="section-number selfRef">12. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-12.1">
        <h3 id="name-normative-references">
<a href="#section-12.1" class="section-number selfRef">12.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="BCP9">[BCP9]</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="BCP78">[BCP78]</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="BCP79">[BCP79]</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="RFC2418">[RFC2418]</dt>
        <dd>
<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>, <span class="seriesInfo">DOI 10.17487/RFC2418</span>, <time datetime="1998-09" class="refDate">September 1998</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2418">https://www.rfc-editor.org/info/rfc2418</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7154">[RFC7154]</dt>
        <dd>
<span class="refAuthor">Moonesamy, S., Ed.</span>, <span class="refTitle">"IETF Guidelines for Conduct"</span>, <span class="seriesInfo">BCP 54</span>, <span class="seriesInfo">RFC 7154</span>, <span class="seriesInfo">DOI 10.17487/RFC7154</span>, <time datetime="2014-03" class="refDate">March 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7154">https://www.rfc-editor.org/info/rfc7154</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7322">[RFC7322]</dt>
        <dd>
<span class="refAuthor">Flanagan, H.</span> and <span class="refAuthor">S. Ginoza</span>, <span class="refTitle">"RFC Style Guide"</span>, <span class="seriesInfo">RFC 7322</span>, <span class="seriesInfo">DOI 10.17487/RFC7322</span>, <time datetime="2014-09" class="refDate">September 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7322">https://www.rfc-editor.org/info/rfc7322</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7776">[RFC7776]</dt>
        <dd>
<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>, <span class="seriesInfo">DOI 10.17487/RFC7776</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7776">https://www.rfc-editor.org/info/rfc7776</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7841">[RFC7841]</dt>
        <dd>
<span class="refAuthor">Halpern, J., Ed.</span>, <span class="refAuthor">Daigle, L., Ed.</span>, and <span class="refAuthor">O. Kolkman, Ed.</span>, <span class="refTitle">"RFC Streams, Headers, and Boilerplates"</span>, <span class="seriesInfo">RFC 7841</span>, <span class="seriesInfo">DOI 10.17487/RFC7841</span>, <time datetime="2016-05" class="refDate">May 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7841">https://www.rfc-editor.org/info/rfc7841</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8716">[RFC8716]</dt>
        <dd>
<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>, <span class="seriesInfo">DOI 10.17487/RFC8716</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8716">https://www.rfc-editor.org/info/rfc8716</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8729">[RFC8729]</dt>
        <dd>
<span class="refAuthor">Housley, R., Ed.</span> and <span class="refAuthor">L. Daigle, Ed.</span>, <span class="refTitle">"The RFC Series and RFC Editor"</span>, <span class="seriesInfo">RFC 8729</span>, <span class="seriesInfo">DOI 10.17487/RFC8729</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8729">https://www.rfc-editor.org/info/rfc8729</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8730">[RFC8730]</dt>
      <dd>
<span class="refAuthor">Brownlee, N., Ed.</span> and <span class="refAuthor">B. Hinden, Ed.</span>, <span class="refTitle">"Independent Submission Editor Model"</span>, <span class="seriesInfo">RFC 8730</span>, <span class="seriesInfo">DOI 10.17487/RFC8730</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8730">https://www.rfc-editor.org/info/rfc8730</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-12.2">
        <h3 id="name-informative-references">
<a href="#section-12.2" class="section-number selfRef">12.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="RFC2850">[RFC2850]</dt>
        <dd>
<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>, <span class="seriesInfo">DOI 10.17487/RFC2850</span>, <time datetime="2000-05" class="refDate">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>
<dd class="break"></dd>
<dt id="RFC5620">[RFC5620]</dt>
        <dd>
<span class="refAuthor">Kolkman, O., Ed.</span> and <span class="refAuthor">IAB</span>, <span class="refTitle">"RFC Editor Model (Version 1)"</span>, <span class="seriesInfo">RFC 5620</span>, <span class="seriesInfo">DOI 10.17487/RFC5620</span>, <time datetime="2009-08" class="refDate">August 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5620">https://www.rfc-editor.org/info/rfc5620</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6635">[RFC6635]</dt>
        <dd>
<span class="refAuthor">Kolkman, O., Ed.</span>, <span class="refAuthor">Halpern, J., Ed.</span>, and <span class="refAuthor">IAB</span>, <span class="refTitle">"RFC Editor Model (Version 2)"</span>, <span class="seriesInfo">RFC 6635</span>, <span class="seriesInfo">DOI 10.17487/RFC6635</span>, <time datetime="2012-06" class="refDate">June 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6635">https://www.rfc-editor.org/info/rfc6635</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7991">[RFC7991]</dt>
        <dd>
<span class="refAuthor">Hoffman, P.</span>, <span class="refTitle">"The "xml2rfc" Version 3 Vocabulary"</span>, <span class="seriesInfo">RFC 7991</span>, <span class="seriesInfo">DOI 10.17487/RFC7991</span>, <time datetime="2016-12" class="refDate">December 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7991">https://www.rfc-editor.org/info/rfc7991</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8700">[RFC8700]</dt>
        <dd>
<span class="refAuthor">Flanagan, H., Ed.</span>, <span class="refTitle">"Fifty Years of RFCs"</span>, <span class="seriesInfo">RFC 8700</span>, <span class="seriesInfo">DOI 10.17487/RFC8700</span>, <time datetime="2019-12" class="refDate">December 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8700">https://www.rfc-editor.org/info/rfc8700</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8711">[RFC8711]</dt>
        <dd>
<span class="refAuthor">Haberman, B.</span>, <span class="refAuthor">Hall, J.</span>, and <span class="refAuthor">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" class="refDate">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>
<dd class="break"></dd>
<dt id="RFC8728">[RFC8728]</dt>
        <dd>
<span class="refAuthor">Kolkman, O., Ed.</span>, <span class="refAuthor">Halpern, J., Ed.</span>, and <span class="refAuthor">R. Hinden, Ed.</span>, <span class="refTitle">"RFC Editor Model (Version 2)"</span>, <span class="seriesInfo">RFC 8728</span>, <span class="seriesInfo">DOI 10.17487/RFC8728</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8728">https://www.rfc-editor.org/info/rfc8728</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8874">[RFC8874]</dt>
        <dd>
<span class="refAuthor">Thomson, M.</span> and <span class="refAuthor">B. Stark</span>, <span class="refTitle">"Working Group GitHub Usage Guidance"</span>, <span class="seriesInfo">RFC 8874</span>, <span class="seriesInfo">DOI 10.17487/RFC8874</span>, <time datetime="2020-08" class="refDate">August 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8874">https://www.rfc-editor.org/info/rfc8874</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC9283">[RFC9283]</dt>
        <dd>
<span class="refAuthor">Carpenter, B., Ed.</span>, <span class="refTitle">"IAB Charter Update for RFC Editor Model"</span>, <span class="seriesInfo">BCP 39</span>, <span class="seriesInfo">RFC 9283</span>, <span class="seriesInfo">DOI 10.17487/RFC9283</span>, <time datetime="2022-06" class="refDate">June 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9283">https://www.rfc-editor.org/info/rfc9283</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="STYLEGUIDE">[STYLEGUIDE]</dt>
      <dd>
<span class="refAuthor">RFC Editor</span>, <span class="refTitle">"Style Guide"</span>, <span>&lt;<a href="https://www.rfc-editor.org/styleguide/">https://www.rfc-editor.org/styleguide/</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<section id="appendix-A">
      <h2 id="name-iab-members-at-the-time-of-">
<a href="#name-iab-members-at-the-time-of-" class="section-name selfRef">IAB Members at the Time of Approval</a>
      </h2>
<p id="appendix-A-1">                                                                                                               
Internet Architecture Board members at the time this document was
approved for publication were:<a href="#appendix-A-1" class="pilcrow">¶</a></p>
<ul class="compact ulEmpty">
<li class="compact ulEmpty" id="appendix-A-2.1">
          <p id="appendix-A-2.1.1"><span class="contact-name">Jari Arkko</span><a href="#appendix-A-2.1.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.2">
          <p id="appendix-A-2.2.1"><span class="contact-name">Deborah Brungard</span><a href="#appendix-A-2.2.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.3">
          <p id="appendix-A-2.3.1"><span class="contact-name">Lars Eggert</span><a href="#appendix-A-2.3.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.4">
          <p id="appendix-A-2.4.1"><span class="contact-name">Wes Hardaker</span><a href="#appendix-A-2.4.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.5">
          <p id="appendix-A-2.5.1"><span class="contact-name">Cullen Jennings</span><a href="#appendix-A-2.5.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.6">
          <p id="appendix-A-2.6.1"><span class="contact-name">Mallory Knodel</span><a href="#appendix-A-2.6.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.7">
          <p id="appendix-A-2.7.1"><span class="contact-name">Mirja Kühlewind</span><a href="#appendix-A-2.7.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.8">
          <p id="appendix-A-2.8.1"><span class="contact-name">Zhenbin Li</span><a href="#appendix-A-2.8.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.9">
          <p id="appendix-A-2.9.1"><span class="contact-name">Tommy Pauly</span><a href="#appendix-A-2.9.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.10">
          <p id="appendix-A-2.10.1"><span class="contact-name">David Schinazi</span><a href="#appendix-A-2.10.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.11">
          <p id="appendix-A-2.11.1"><span class="contact-name">Russ White</span><a href="#appendix-A-2.11.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.12">
          <p id="appendix-A-2.12.1"><span class="contact-name">Qin Wu</span><a href="#appendix-A-2.12.1" class="pilcrow">¶</a></p>
</li>
        <li class="compact ulEmpty" id="appendix-A-2.13">
          <p id="appendix-A-2.13.1"><span class="contact-name">Jiankang Yao</span><a href="#appendix-A-2.13.1" class="pilcrow">¶</a></p>
</li>
      </ul>
<p id="appendix-A-3">This document is the product of the IAB's RFC Editor Future Development
Program. The RFC Editor Future Development Program allowed for open
participation and used a rough consensus model for decision making.<a href="#appendix-A-3" class="pilcrow">¶</a></p>
</section>
<div id="acknowledgments">
<section id="appendix-B">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="appendix-B-1">Portions of this document were borrowed from <span>[<a href="#RFC5620" class="xref">RFC5620</a>]</span>,
<span>[<a href="#RFC6635" class="xref">RFC6635</a>]</span>, <span>[<a href="#RFC8728" class="xref">RFC8728</a>]</span>, <span>[<a href="#RFC8729" class="xref">RFC8729</a>]</span>, the Frequently Asked 
Questions of the IETF Trust, and earlier proposals
submitted within the IAB's RFC Editor Future Development Program
by <span class="contact-name">Brian Carpenter</span>, <span class="contact-name">Michael StJohns</span>, and <span class="contact-name">Martin Thomson</span>. Thanks
to <span class="contact-name">Eliot Lear</span> and <span class="contact-name">Brian Rosen</span> in their role as chairs of the Program
for their leadership and assistance. Thanks also for feedback and
proposed text to
<span class="contact-name">Jari Arkko</span>, 
<span class="contact-name">Sarah Banks</span>, 
<span class="contact-name">Carsten Bormann</span>, 
<span class="contact-name">Scott Bradner</span>, 
<span class="contact-name">Nevil Brownlee</span>, 
<span class="contact-name">Ben Campbell</span>, 
<span class="contact-name">Jay Daley</span>, 
<span class="contact-name">Martin Dürst</span>,
<span class="contact-name">Wesley Eddy</span>, 
<span class="contact-name">Lars Eggert</span>, 
<span class="contact-name">Adrian Farrel</span>, 
<span class="contact-name">Stephen Farrell</span>, 
<span class="contact-name">Sandy Ginoza</span>, 
<span class="contact-name">Bron Gondwana</span>, 
<span class="contact-name">Joel Halpern</span>, 
<span class="contact-name">Wes Hardaker</span>, 
<span class="contact-name">Bob Hinden</span>, 
<span class="contact-name">Russ Housley</span>, 
<span class="contact-name">Christian Huitema</span>, 
<span class="contact-name">Ole Jacobsen</span>, 
<span class="contact-name">Sheng Jiang</span>, 
<span class="contact-name">Benjamin Kaduk</span>, 
<span class="contact-name">John Klensin</span>, 
<span class="contact-name">Murray Kucherawy</span>, 
<span class="contact-name">Mirja Kühlewind</span>, 
<span class="contact-name">Ted Lemon</span>, 
<span class="contact-name">John Levine</span>, 
<span class="contact-name">Lucy Lynch</span>, 
<span class="contact-name">Jean Mahoney</span>, 
<span class="contact-name">Andrew Malis</span>, 
<span class="contact-name">Larry Masinter</span>, 
<span class="contact-name">S. Moonesamy</span>, 
<span class="contact-name">Russ Mundy</span>, 
<span class="contact-name">Mark Nottingham</span>,
<span class="contact-name">Tommy Pauly</span>,
<span class="contact-name">Colin Perkins</span>,
<span class="contact-name">Julian Reschke</span>,
<span class="contact-name">Eric Rescorla</span>,
<span class="contact-name">Alvaro Retana</span>,
<span class="contact-name">Adam Roach</span>,
<span class="contact-name">Dan Romascanu</span>,
<span class="contact-name">Doug Royer</span>,
<span class="contact-name">Alice Russo</span>,
<span class="contact-name">Rich Salz</span>,
<span class="contact-name">John Scudder</span>,
<span class="contact-name">Stig Venaas</span>,
<span class="contact-name">Tim Wicinski</span>,
and <span class="contact-name">Nico Williams</span>.<a href="#appendix-B-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="appendix-C">
      <h2 id="name-authors-address">
<a href="#name-authors-address" class="section-name selfRef">Author's Address</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Peter Saint-Andre (<span class="role">editor</span>)</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:stpeter@stpeter.im" class="email">stpeter@stpeter.im</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>