rfc8728xml2.original.xml   rfc8728.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!-- automatically generated by xml2rfc v1.34pre3 on 2009-12-15T11:43:14Z --> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" cons
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"> ensus="true" docName="draft-ietf-iasa2-rfc6635bis-04" indexInclude="true" ipr="t
rust200902" number="8728" obsoletes="6635" prepTime="2020-02-26T17:55:55" script
<!-- s="Common,Latin" sortRefs="true" submissionType="IAB" symRefs="true" tocDepth="4
<?rfc rfcedstyle="yes"?> " tocInclude="true" xml:lang="en">
<?rfc compact="yes"?> <link href="https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis-04" r
<?rfc subcompact="no"?> el="prev"/>
<?rfc toc="yes"?> <link href="https://dx.doi.org/10.17487/rfc8728" rel="alternate"/>
<?rfc tocdepth="5"?> <link href="urn:issn:2070-1721" rel="alternate"/>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="no" ?>
<rfc submissionType="IAB"
obsoletes="6635"
ipr="trust200902"
category="info"
docName="draft-ietf-iasa2-rfc6635bis-00"
>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc category="info" docName="draft-ietf-iasa2-rfc6635bis-04"
obsoletes="6635">
<front> <front>
<title>RFC Editor Model (Version 2)</title> <title abbrev="RFC Editor Model (Version 2)">RFC Editor Model (Version 2)</t
itle>
<author initials="O." surname="Kolkman" fullname="Olaf M. Kolkman" role="edi <seriesInfo name="RFC" value="8728" stream="IAB"/>
tor"> <author initials="O." surname="Kolkman" fullname="Olaf Kolkman" role="editor
<organization></organization> ">
<address><email>olaf@nlnetlabs.nl</email> <organization showOnFrontPage="true">Internet Society</organization>
<address>
<email>kolkman@isoc.org</email>
</address> </address>
</author> </author>
<author initials="J." surname="Halpern" fullname="Joel M. Halpern" role="edi
<author initials="J.M." surname="Halpern" fullname="Joel M. Halpern" role="e tor">
ditor"> <organization showOnFrontPage="true">Ericsson</organization>
<organization>Ericsson</organization> <address>
<address><email>joel.halpern@ericsson.com</email></address> <email>joel.halpern@ericsson.com</email>
</address>
</author> </author>
<author fullname="Robert M. Hinden" initials="R." surname="Hinden" role="edi
<author fullname="Robert M. Hinden" initials="R" tor">
surname="Hinden" <organization showOnFrontPage="true">Check Point Software</organization>
role="editor">
<organization>Check Point Software</organization>
<address> <address>
<postal> <postal>
<street>959 Skyway Road</street> <street>959 Skyway Road</street>
<!-- Reorder these if your country does things differently -->
<city>San Carlos</city> <city>San Carlos</city>
<region>CA</region> <region>CA</region>
<code>94070</code> <code>94070</code>
<country>USA</country> <country>USA</country>
</postal> </postal>
<phone></phone> <phone/>
<facsimile></facsimile>
<email>bob.hinden@gmail.com</email> <email>bob.hinden@gmail.com</email>
<!-- uri and facsimile elements may also be added -->
</address> </address>
</author> </author>
<date month="02" year="2020"/>
<date day="" month="" year="" /> <keyword>IAB</keyword>
<keyword>RSOC</keyword>
<keyword>RFC</keyword> <keyword>RSE</keyword>
<abstract> <keyword>IASA</keyword>
<t> <keyword>IASA2</keyword>
<abstract pn="section-abstract">
<t pn="section-abstract-1">
The RFC Editor model described in this document divides the The RFC Editor model described in this document divides the
responsibilities for the RFC Series into three functions: the RFC responsibilities for the RFC Series into three functions: the RFC
Series Editor, the RFC Production Center, and the RFC Publisher. Series Editor, the RFC Production Center, and the RFC Publisher.
Internet Architecture Board (IAB) oversight via the RFC Series Internet Architecture Board (IAB) oversight via the RFC Series
Oversight Committee (RSOC) is described, as is the relationship Oversight Committee (RSOC) is described, as is the relationship
between the IETF Administration Limited Liability Company between the IETF Administration Limited Liability Company
and the RSOC. This document reflects the experience gained and the RSOC. This document reflects the experience gained
with "RFC Editor Model (Version 1)", documented in RFC 5620; and with "RFC Editor Model (Version 1)", documented in RFC 5620; and
obsoletes RFC 6635 to replace all references to the IASA and obsoletes RFC 6635 to replace all references to the
IETF Administrative Support Activity (IASA) and
related structures with those defined by the IASA 2.0 Model.</t> related structures with those defined by the IASA 2.0 Model.</t>
<t>[RFC Editor: Please remove the following paragraph prior to
publication.]</t>
<t>The IASA2 WG requests that the IAB publish this replacement
for RFC 6635.</t>
</abstract> </abstract>
<boilerplate>
<section anchor="status-of-memo" numbered="false" removeInRFC="false" toc=
"exclude" pn="section-boilerplate.1">
<name slugifiedName="name-status-of-this-memo">Status of This Memo</name
>
<t pn="section-boilerplate.1-1">
This document is not an Internet Standards Track specification; it i
s
published for informational purposes.
</t>
<t pn="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; se
e
Section 2 of RFC 7841.
</t>
<t pn="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
<eref target="https://www.rfc-editor.org/info/rfc8728" brackets="non
e"/>.
</t>
</section>
<section anchor="copyright" numbered="false" removeInRFC="false" toc="excl
ude" pn="section-boilerplate.2">
<name slugifiedName="name-copyright-notice">Copyright Notice</name>
<t pn="section-boilerplate.2-1">
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
</t>
<t pn="section-boilerplate.2-2">
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<eref target="https://trustee.ietf.org/license-info" brackets="none
"/>) 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.
</t>
</section>
</boilerplate>
<toc>
<section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" p
n="section-toc.1">
<name slugifiedName="name-table-of-contents">Table of Contents</name>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-to
c.1-1">
<li pn="section-toc.1-1.1">
<t keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent
="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedCon
tent="" format="title" sectionFormat="of" target="name-introduction">Introductio
n</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.1.2">
<li pn="section-toc.1-1.1.2.1">
<t keepWithNext="true" pn="section-toc.1-1.1.2.1.1"><xref derive
dContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-the-rfc-edito
r-function">The RFC Editor Function</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.2">
<t keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent
="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedCon
tent="" format="title" sectionFormat="of" target="name-rfc-editor-model">RFC Edi
tor Model</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.2.2">
<li pn="section-toc.1-1.2.2.1">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.1"><xref derive
dContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-rfc-series-ed
itor">RFC Series Editor</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-toc.1-1.2.2.1.2">
<li pn="section-toc.1-1.2.2.1.2.1">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.1.1"><xre
f derivedContent="2.1.1" format="counter" sectionFormat="of" target="section-2.1
.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-s
trategic-leadership-and-ma">Strategic Leadership and Management of the Publicati
on and Production Functions</xref></t>
</li>
<li pn="section-toc.1-1.2.2.1.2.2">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.2.1"><xre
f derivedContent="2.1.2" format="counter" sectionFormat="of" target="section-2.1
.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-r
epresentation-of-the-rfc-s">Representation of the RFC Series</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn
="section-toc.1-1.2.2.1.2.2.2">
<li pn="section-toc.1-1.2.2.1.2.2.2.1">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.2.2.1
.1"><xref derivedContent="2.1.2.1" format="counter" sectionFormat="of" target="s
ection-2.1.2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
rget="name-representation-to-the-ietf">Representation to the IETF</xref></t>
</li>
<li pn="section-toc.1-1.2.2.1.2.2.2.2">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.2.2.2
.1"><xref derivedContent="2.1.2.2" format="counter" sectionFormat="of" target="s
ection-2.1.2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
rget="name-external-representation">External Representation</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.2.2.1.2.3">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.3.1"><xre
f derivedContent="2.1.3" format="counter" sectionFormat="of" target="section-2.1
.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-d
evelopment-of-rfc-producti">Development of RFC Production and Publication</xref>
</t>
</li>
<li pn="section-toc.1-1.2.2.1.2.4">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.4.1"><xre
f derivedContent="2.1.4" format="counter" sectionFormat="of" target="section-2.1
.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-d
evelopment-of-the-rfc-seri">Development of the RFC Series</xref></t>
</li>
<li pn="section-toc.1-1.2.2.1.2.5">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.5.1"><xre
f derivedContent="2.1.5" format="counter" sectionFormat="of" target="section-2.1
.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-w
orkload">Workload</xref></t>
</li>
<li pn="section-toc.1-1.2.2.1.2.6">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.6.1"><xre
f derivedContent="2.1.6" format="counter" sectionFormat="of" target="section-2.1
.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-q
ualifications">Qualifications</xref></t>
</li>
<li pn="section-toc.1-1.2.2.1.2.7">
<t keepWithNext="true" pn="section-toc.1-1.2.2.1.2.7.1"><xre
f derivedContent="2.1.7" format="counter" sectionFormat="of" target="section-2.1
.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-c
onflict-of-interest">Conflict of Interest</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.2.2.2">
<t keepWithNext="true" pn="section-toc.1-1.2.2.2.1"><xref derive
dContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-rfc-productio
n-center">RFC Production Center</xref></t>
</li>
<li pn="section-toc.1-1.2.2.3">
<t keepWithNext="true" pn="section-toc.1-1.2.2.3.1"><xref derive
dContent="2.3" format="counter" sectionFormat="of" target="section-2.3"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-rfc-publisher
">RFC Publisher</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.3">
<t keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent
="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedCon
tent="" format="title" sectionFormat="of" target="name-committees">Committees</x
ref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.3.2">
<li pn="section-toc.1-1.3.2.1">
<t keepWithNext="true" pn="section-toc.1-1.3.2.1.1"><xref derive
dContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-rfc-series-ov
ersight-commit">RFC Series Oversight Committee (RSOC)</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-toc.1-1.3.2.1.2">
<li pn="section-toc.1-1.3.2.1.2.1">
<t keepWithNext="true" pn="section-toc.1-1.3.2.1.2.1.1"><xre
f derivedContent="3.1.1" format="counter" sectionFormat="of" target="section-3.1
.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-r
soc-composition">RSOC Composition</xref></t>
</li>
</ul>
</li>
</ul>
</li>
<li pn="section-toc.1-1.4">
<t keepWithNext="true" pn="section-toc.1-1.4.1"><xref derivedContent
="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedCon
tent="" format="title" sectionFormat="of" target="name-administrative-implementa
ti">Administrative Implementation</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.4.2">
<li pn="section-toc.1-1.4.2.1">
<t keepWithNext="true" pn="section-toc.1-1.4.2.1.1"><xref derive
dContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-vendor-select
ion-for-the-pr">Vendor Selection for the Production and Publisher Functions</xre
f></t>
</li>
<li pn="section-toc.1-1.4.2.2">
<t keepWithNext="true" pn="section-toc.1-1.4.2.2.1"><xref derive
dContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-budget">Budge
t</xref></t>
</li>
<li pn="section-toc.1-1.4.2.3">
<t keepWithNext="true" pn="section-toc.1-1.4.2.3.1"><xref derive
dContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-disagreements
-among-entitie">Disagreements among Entities Related to the RFC Editor</xref></t
>
</li>
<li pn="section-toc.1-1.4.2.4">
<t keepWithNext="true" pn="section-toc.1-1.4.2.4.1"><xref derive
dContent="4.4" format="counter" sectionFormat="of" target="section-4.4"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-issues-with-c
ontractual-imp">Issues with Contractual Impact</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.5">
<t keepWithNext="true" pn="section-toc.1-1.5.1"><xref derivedContent
="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedCon
tent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA
Considerations</xref></t>
</li>
<li pn="section-toc.1-1.6">
<t keepWithNext="true" pn="section-toc.1-1.6.1"><xref derivedContent
="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedCon
tent="" format="title" sectionFormat="of" target="name-security-considerations">
Security Considerations</xref></t>
</li>
<li pn="section-toc.1-1.7">
<t keepWithNext="true" pn="section-toc.1-1.7.1"><xref derivedContent
="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedCon
tent="" format="title" sectionFormat="of" target="name-references">References</x
ref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-toc.1-1.7.2">
<li pn="section-toc.1-1.7.2.1">
<t keepWithNext="true" pn="section-toc.1-1.7.2.1.1"><xref derive
dContent="7.1" format="counter" sectionFormat="of" target="section-7.1"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-normative-ref
erences">Normative References</xref></t>
</li>
<li pn="section-toc.1-1.7.2.2">
<t keepWithNext="true" pn="section-toc.1-1.7.2.2.1"><xref derive
dContent="7.2" format="counter" sectionFormat="of" target="section-7.2"/>.  <xre
f derivedContent="" format="title" sectionFormat="of" target="name-informative-r
eferences">Informative References</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.8">
<t keepWithNext="true" pn="section-toc.1-1.8.1"><xref derivedContent
="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedC
ontent="" format="title" sectionFormat="of" target="name-iab-members-at-the-time
-of-">IAB Members at the Time of Approval</xref></t>
</li>
<li pn="section-toc.1-1.9">
<t keepWithNext="true" pn="section-toc.1-1.9.1"><xref derivedContent
="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedC
ontent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknow
ledgments</xref></t>
</li>
<li pn="section-toc.1-1.10">
<t keepWithNext="true" pn="section-toc.1-1.10.1"><xref derivedConten
t="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derived
Content="" format="title" sectionFormat="of" target="name-authors-addresses">Aut
hors' Addresses</xref></t>
</li>
</ul>
</section>
</toc>
</front> </front>
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<middle> <middle>
<section numbered="true" toc="include" removeInRFC="false" pn="section-1">
<section title="Introduction"> <name slugifiedName="name-introduction">Introduction</name>
<t pn="section-1-1">This document reflects the experience gained with "RFC
<t>This document reflects the experience gained with "RFC Editor Editor
Model (Version 1)", documented in <xref target="RFC5620"/>, and Model (Version 1)", documented in <xref target="RFC5620" format="default" se
ctionFormat="of" derivedContent="RFC5620"/>, and
updates the RFC Editor Model (Version 2) to be aligned with the new updates the RFC Editor Model (Version 2) to be aligned with the new
IASA 2.0 Model <xref target="I-D.ietf-iasa2-rfc4071bis"/> that creates a IASA 2.0 Model <xref target="RFC8711" format="default" sectionFormat="of" de
IETF Administration Limited Liability Company ("LLC") managed by rivedContent="RFC8711"/> that creates the
a board of directors ("LLC Board"). As part of the IASA 2.0 Model IETF Administration Limited Liability Company (IETF LLC) managed by
a board of directors (IETF LLC Board). As part of the IASA 2.0 Model,
the IETF Administrative Oversight Committee (IAOC) is eliminated, the IETF Administrative Oversight Committee (IAOC) is eliminated,
and its oversight and advising functions transferred to the new LLC. and its oversight and advising functions transferred to the new IETF LLC.
This document obsoletes <xref target="RFC6635"/> to replace all This document obsoletes <xref target="RFC6635" format="default" sectionForma
t="of" derivedContent="RFC6635"/> to replace all
references to the IASA and related structures with those defined by references to the IASA and related structures with those defined by
the IASA 2.0 Model.</t> the IASA 2.0 Model.</t>
<t pn="section-1-2">
<t>
The IAB, on behalf of the Internet technical community, is concerned The IAB, on behalf of the Internet technical community, is concerned
with ensuring the continuity of the RFC Series, orderly RFC Editor with ensuring the continuity of the RFC Series, orderly RFC Editor
succession, RFC quality, and RFC document accessibility. The IAB is succession, RFC quality, and RFC document accessibility. The IAB is
also sensitive to the concerns of the LLC about providing the also sensitive to the concerns of the IETF LLC about providing the
necessary services in a cost-effective and efficient manner. necessary services in a cost-effective and efficient manner.
</t> </t>
<t> <t pn="section-1-3">
The contemporary RFC Editor model <xref target="RFC5620"/> was first The previous RFC Editor model <xref target="RFC5620" format="default" secti
approved in October 2008, and our understanding of the model has onFormat="of" derivedContent="RFC5620"/> was first
approved by the IAB in October 2008, and our understanding of the model has
evolved with our experience since. During the implementation of evolved with our experience since. During the implementation of
version 1 of the model <xref target="RFC5620"/>, it was quickly version 1 of the model <xref target="RFC5620" format="default" sectionForma t="of" derivedContent="RFC5620"/>, it was quickly
realized that the role of the RFC Series Editor (RSE) and the realized that the role of the RFC Series Editor (RSE) and the
oversight responsibilities needed to be structured differently. In oversight responsibilities needed to be structured differently. In
order to gain experience with "running code", a transitional RSE was order to gain experience with "running code", a transitional RSE was
hired who analyzed the managerial environment and provided hired who analyzed the managerial environment and provided
recommendations. This was followed by the appointment of an acting recommendations. This was followed by the appointment of an acting
RSE, who ably managed the series while work was undertaken to select RSE, who ably managed the series while work was undertaken to select
and hire a permanent RSE. This version of the model is based on the and hire a permanent RSE. This version of the model is based on the
recommendations of both temporary RFC Series Editors and the recommendations of both temporary RFC Series Editors and the
extensive discussion in the IETF community, on the rfc-interest extensive discussion in the IETF community, on the rfc-interest
list, and within the IAB. list, and within the IAB.
</t> </t>
<t> <t pn="section-1-4">
This document, and the resulting structures, will be modified as This document, and the resulting structures, will be modified as
needed through normal procedures. The RSE, and the IAB, through the needed through normal procedures. The RSE, and the IAB, through the
RFC Oversight Committee (see <xref target="RSOC"/>), will continue RFC Series Oversight Committee (see <xref target="RSOC" format="default" se ctionFormat="of" derivedContent="Section 3.1"/>), will continue
to monitor discussions within the community about potential to monitor discussions within the community about potential
adjustments to the RFC Editor model and recognize that the process adjustments to the RFC Editor model and recognize that the process
described in this document may need to be adjusted to align with any described in this document may need to be adjusted to align with any
changes that result from such discussions; hence, the version number changes that result from such discussions; hence, the version number
in the title. in the title.
</t> </t>
<t> <t pn="section-1-5">
The IAB maintains its responsibilities as defined in <xref The IAB maintains its responsibilities as defined in <xref target="RFC2850"
target="RFC2850"/>. format="default" sectionFormat="of" derivedContent="RFC2850"/>.
</t>
<section title="The RFC Editor Function">
<t>
The RFC Series is described in <xref target="RFC4844"/>. Its
Section 3.1 defines "RFC Editor":
</t> </t>
<t> <section numbered="true" toc="include" removeInRFC="false" pn="section-1.1
">
<list style="empty"> <name slugifiedName="name-the-rfc-editor-function">The RFC Editor Functi
<t> on</name>
<t pn="section-1.1-1">
The RFC Series is described in <xref target="RFC8729" format="default" s
ectionFormat="of" derivedContent="RFC8729"/>. Its
Section <xref target="RFC8729" section="3.1" sectionFormat="bare" format
="default" derivedLink="https://rfc-editor.org/rfc/rfc8729#section-3.1" derivedC
ontent="RFC8729"/> defines "RFC Editor":
</t>
<blockquote pn="section-1.1-2">
<t pn="section-1.1-2.1">
Originally, there was a single person acting as editor of the RFC Originally, there was a single person acting as editor of the RFC
Series (the RFC Editor). The task has grown, and the work now Series (the RFC Editor). The task has grown, and the work now
requires the organized activity of several experts, so there are requires the organized activity of several experts, so there are
RFC Editors, or an RFC Editor organization. In time, there may be RFC Editors, or an RFC Editor organization. In time, there may be
multiple organizations working together to undertake the work multiple organizations working together to undertake the work
required by the RFC Series. For simplicity's sake, and without required by the RFC Series. For simplicity's sake, and without
attempting to predict how the role might be subdivided among them, attempting to predict how the role might be subdivided among them,
this document refers to this collection of experts and this document refers to this collection of experts and
organizations as the "RFC Editor".</t> organizations as the "RFC Editor".</t>
<t pn="section-1.1-2.2">
<t> The RFC Editor is an expert technical editor and series editor, The RFC Editor is an expert technical editor and series editor,
acting to support the mission of the RFC Series. As such, the RFC acting to support the mission of the RFC Series. As such, the RFC
Editor is the implementer handling the editorial management of the Editor is the implementer handling the editorial management of the
RFC Series, in accordance with the defined processes. In addition, RFC Series, in accordance with the defined processes. In addition,
the RFC Editor is expected to be the expert and prime mover in the RFC Editor is expected to be the expert and prime mover in
discussions about policies for editing, publishing, and archiving discussions about policies for editing, publishing, and archiving
RFCs.</t> RFCs.</t>
</list> </blockquote>
</t> <t pn="section-1.1-3">
<t> RFC 8729 does not explore the internal organization of the RFC
RFC 4844 does not explore the internal organization of the RFC Editor. However, RFC 8729 envisions changes in the RFC Editor
Editor. However, RFC 4844 envisions changes in the RFC Editor organizational structure. There have been several iterations on
organizational structure. There have been several iterations on efforts to improve and clarify this structure. These have been
efforts to improve and clarify this structure. These have been led by the IAB, in consultation with the community and many
led by the IAB, in consultation with the community and many leadership bodies within the community. This first resulted in
leadership bodies within the community. This first resulted in the publication of <xref target="RFC5620" format="default" sectionFormat="of" de
the publication of <xref target="RFC5620"/> and then in further rivedContent="RFC5620"/> and then in further
discussions leading to this document. Some of the details on discussions leading to the publication of <xref target="RFC6635" format="default
this evolution can be found below. In undertaking this " sectionFormat="of" derivedContent="RFC6635"/>. Some of the details on
evolution, the IAB considered changes that increase flexibility this evolution can be found below. In undertaking this
and operational support options, provide for the orderly evolution, the IAB considered changes that increase flexibility
succession of the RFC Editor, and ensure the continuity of the and operational support options, provide for the orderly
RFC Series, while maintaining RFC quality, maintaining timely succession of the RFC Editor, and ensure the continuity of the
processing, ensuring document accessibility, reducing costs, and RFC Series, while maintaining RFC quality, maintaining timely
increasing cost transparency. The model set forth below describes processing, ensuring document accessibility, reducing costs, and
the internal organization of the RFC Editor, while remaining increasing cost transparency. The model set forth below describes
consistent with RFC 4844. the internal organization of the RFC Editor, while remaining
</t> consistent with RFC 8729.
<t> </t>
Note that RFC 4844 uses the term "RFC Editor function" or "RFC <t pn="section-1.1-4">
Editor" as the collective set of responsibilities for which Note that RFC 8729 uses the term "RFC Editor function" or "RFC
this memo provides a model for internal organization. This Editor" as the collective set of responsibilities for which
memo defines the term "RFC Series Editor" or "Series this memo provides a model for internal organization. This
Editor" for one of the organizational components. memo defines the term "RFC Series Editor" or "Series
</t> Editor" for one of the organizational components.
</t>
</section> </section>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false" pn="section-2">
<section title="RFC Editor Model"> <name slugifiedName="name-rfc-editor-model">RFC Editor Model</name>
<t> <t pn="section-2-1">
The RFC Editor model divides the responsibilities for The RFC Editor model divides the responsibilities for
the RFC Series into the following components: the RFC Series into the following components:
</t>
<t>
<list style="symbols">
<t>RFC Series Editor (RSE)</t>
<t>RFC Production Center</t>
<t>RFC Publisher</t>
</list>
</t> </t>
<t> <ul spacing="normal" bare="false" empty="false" pn="section-2-2">
The structure and relationship of the components of the RFC <li pn="section-2-2.1">RFC Series Editor (RSE)</li>
Series production and process is schematically represented by the <li pn="section-2-2.2">RFC Production Center</li>
figure below. The picture does not depict oversight and <li pn="section-2-2.3">RFC Publisher</li>
escalation relations. It does include the streams and their </ul>
managers (which are not part of the RFC Series Editor, the RFC <t pn="section-2-3">
Production Center, or Publisher facilities) in order to more The structure and relationship of the components of the RFC
fully show the context in which the RFC Series Editor operates. Series production and process is schematically represented by
<xref target="model-figure" format="default" sectionFormat="of" derivedContent="
Figure 1"/>. The picture does not depict oversight and
escalation relations. It does include the streams and their
managers (which are not part of the RFC Series Editor, the RFC
Production Center, or Publisher facilities) in order to more
fully show the context in which the RFC Series Editor operates.
</t> </t>
<t> <figure anchor="model-figure" align="left" suppress-title="false" pn="figu
re-1">
<figure anchor="model-figure"> <name slugifiedName="name-structure-of-rfc-series-pro">Structure of RFC
<artwork> Series Production and Process</name>
<![CDATA[ <artwork name="" type="" align="left" alt="" pn="section-2-4.1">
+-------------+ +-------------+
| | | |
+--------------+ IAB <------------+ +--------------+ IAB &lt;----------+
| | | | | | | |
| |=============| | | |=============| |
| | | | | | | |
| | RSOC <------------+ | | RSOC &lt;----------+
| | | | | | | |
| +-------+-----+ +-----+-----+ | +-------+-----+ +----+----+
| | | | | | | |
| +...........|.........+ | Community | | +...........|.........+ |Community|
| . | . | at | | . | . | at |
| . +-------V-----+ . | Large | | . +-------V-----+ . | Large |
| . | | . | | | . | | . | |
| . | RFC | . +-----+-----+ | . | RFC | . +----+----+
| . | Series | . | | . | Series | . |
| . | Editor <------------+ | . | Editor &lt;----------+
| . | | . | . | | .
| . +-+---------+-+ . | . +-+---------+-+ .
| . | | . | . | | .
+-------------+ +-----V-------+ . +--V--+ +--V--+ . +-----+ +-------------+ +-----V-------+ . +--V--+ +--V--+ . +-----+
| | | | . | | | | . | | | | | | . | | | | . | |
| Independent | | Independent | . | RFC | | | . | E | | Independent | | Independent | . | RFC | | | . | E |
| Authors +--> Submission +-----&gt; | | | . | n | | Authors +--> Submission +-----&gt; | | | . | n |
| | | Editor | . | P | | | . | d | | | | Editor | . | P | | | . | d |
| | | | . | r | | RFC | . | | | | | | . | r | | RFC | . | |
+-------------+ +-------------+ . | o | | | . | U | +-------------+ +-------------+ . | o | | | . | U |
+-------------+ +-------------+ . | d | | P | . | s | +-------------+ +-------------+ . | d | | P | . | s |
| | | | . | u | | u | . | e | | | | | . | u | | u | . | e |
| IAB +--> IAB +-----&gt; c | | b | . | r | | IAB +--> IAB +-----&gt; c | | b | . | r |
| | | | . | t | | l | . | s | | | | | . | t | | l | . | s |
+-------------+ +-------------+ . | i +---> i +--------> | +-------------+ +-------------+ . | i +---&gt; i +--------&gt; |
+-------------+ +-------------+ . | o | | s | . | & | +-------------+ +-------------+ . | o | | s | . | &amp; |
| | | | . | n | | h | . | | | | | | . | n | | h | . | |
| IRTF +--> IRSG +---->| | | e | . | R | -------------+ +-------------+ . | o | | s | . | <span class="ins
ert">&amp;amp;</span> |
| IRTF +--&gt; IRSG +----&gt;| | | e | . | R |
| | | | . | C | | r | . | e | | | | | . | C | | r | . | e |
+-------------+ +-------------+ . | e | | | . | a | +-------------+ +-------------+ . | e | | | . | a |
+-------------+ +-------------+ . | n | | | . | d | +-------------+ +-------------+ . | n | | | . | d |
| | | | . | t | | | . | e | | | | | . | t | | | . | e |
| IETF +--> IESG +-----&gt; e | | | . | r | | IETF +--> IESG +-----&gt; e | | | . | r |
| | | | . | r | | | . | s | | | | | . | r | | | . | s |
+-------------+ +-------------+ . +-----+ +-----+ . +-----+ +-------------+ +-------------+ . +-----+ +-----+ . +-----+
. . . .
+..... RFC Editor ....+ +..... RFC Editor ....+
]]>
Structure of RFC Series Production and Process
</artwork> </artwork>
</figure> </figure>
</t> <t pn="section-2-5">
<t> In this model, documents are produced and approved through
In this model, documents are produced and approved through multiple document streams. The stream manager for each stream is
multiple document streams. The stream manager for each stream is responsible for the content of that stream. The four streams
responsible for the content of that stream. The four streams that now exist are described in <xref target="RFC8729" format="default" sectionF
that now exist are described in <xref target="RFC4844" />. The ormat="of" derivedContent="RFC8729"/>. The
RFC Editor function is responsible for the packaging and RFC Editor function is responsible for the packaging and
distribution of the documents. As such, documents from these distribution of the documents. As such, documents from these
streams are edited and processed by the Production Center and streams are edited and processed by the Production Center and
published by the Publisher. The RFC Series Editor will exercise published by the Publisher. The RFC Series Editor will exercise
strategic leadership and management over the activities of the strategic leadership and management over the activities of the
RFC Publisher and the RFC Production Center (both of which can be RFC Publisher and the RFC Production Center (both of which can be
seen as back-office functions) and will be the entity that: seen as back-office functions) and will be the entity that:
</t> </t>
<t> <ul spacing="normal" bare="false" empty="false" pn="section-2-6">
<list style="symbols"> <li pn="section-2-6.1">Represents the RFC Series and the RFC Editor func
<t>Represents the RFC Series and the RFC Editor Function within tion within
the IETF and externally.</t> the IETF and externally.</li>
<t>Leads the community in the design of improvements to the RFC <li pn="section-2-6.2">Leads the community in the design of improvements
Series.</t> to the RFC
<t>Is responsible for planning and seeing to the execution of Series.</li>
improvements in the RFC Editor production and access <li pn="section-2-6.3">Is responsible for planning and seeing to the exe
processes.</t> cution of
<t> Is responsible for the content of the rfc-editor.org web improvements in the RFC Editor production and access
processes.</li>
<li pn="section-2-6.4"> Is responsible for the content of the rfc-editor
.org web
site, which is operated and maintained by the RFC site, which is operated and maintained by the RFC
Publisher.</t> Publisher.</li>
<t>Is responsible for developing consensus versions of <li pn="section-2-6.5">Is responsible for developing consensus versions
of
vision and policy documents. These documents will be vision and policy documents. These documents will be
reviewed by the RFC Series Oversight Committee (<xref reviewed by the RFC Series Oversight Committee (<xref target="RSOC" fo
target="RSOC"/>) and subject to its approval before final rmat="default" sectionFormat="of" derivedContent="Section 3.1"/>) and subject to
its approval before final
publication. publication.
</t> </li>
</list> </ul>
</t> <t pn="section-2-7">These responsibilities are defined below, although the
<t>These responsibilities are defined below, although the specific specific
work items under them are a matter for the actual employment work items under them are a matter for the actual employment
contract and its Statement of Work (SOW).</t> contract and its Statement of Work (SOW).</t>
<t> <t pn="section-2-8">
The IAB maintain it's chartered The IAB maintain its chartered
responsibility as defined in <xref target="RFC2850"/>. responsibility as defined in <xref target="RFC2850" format="default" sectionForm
at="of" derivedContent="RFC2850"/>.
More details on the More details on the
oversight by the IAB via the RFC Series Oversight Committee oversight by the IAB via the RFC Series Oversight Committee
(RSOC) can be found in <xref target="RSOC"/>. For example, (RSOC) can be found in <xref target="RSOC" format="default" sectionForma
the RSE does not have the direct authority to t="of" derivedContent="Section 3.1"/>. For example,
the RSE does not have the direct authority to
hire or fire RFC Editor hire or fire RFC Editor
contractors or personnel. contractors or personnel.
</t> </t>
<section anchor="RSE" numbered="true" toc="include" removeInRFC="false" pn
<section anchor="RSE" title="RFC Series Editor"> ="section-2.1">
<t> <name slugifiedName="name-rfc-series-editor">RFC Series Editor</name>
The RFC Series Editor is the individual with overall <t pn="section-2.1-1">
responsibility for the quality, continuity, and evolution of The RFC Series Editor is the individual with overall
the RFC Series. responsibility for the quality, continuity, and evolution of
the RFC Series.
</t> </t>
<t pn="section-2.1-2">The RSE is appointed by the IAB, but formally hire
<t>The RSE is appointed by the IAB, but formally hired by the d by the
LLC. The IAB delegates the direct oversight over the RSE to the IETF LLC. The IAB delegates the direct oversight over the RSE to the
RSOC, which it appoints.</t> RSOC, which it appoints.</t>
<t pn="section-2.1-3">The RSE is expected to cooperate closely with the
<t>The RSE is expected to cooperate closely with the LLC and IETF LLC and
the stream managers.</t> the stream managers.</t>
<section anchor="ExecManage" numbered="true" toc="include" removeInRFC="
<section anchor="ExecManage" title="Strategic Leadership and false" pn="section-2.1.1">
Management of the Publication and Production Functions"> <name slugifiedName="name-strategic-leadership-and-ma">Strategic Leade
rship and Management of the Publication and Production Functions</name>
<t> With respect to the RFC Publisher and Production Center <t pn="section-2.1.1-1"> With respect to the RFC Publisher and Product
functions, the RSE provides input to the LLC budget, SOWs, and ion Center
functions, the RSE provides input to the IETF LLC budget, SOWs, and
manages vendor selection processes. The RSE performs annual manages vendor selection processes. The RSE performs annual
reviews of the RFC Production Center and Publisher function, reviews of the RFC Production Center and Publisher function,
which are then provided to the RSOC, the LLC, and the community. which are then provided to the RSOC, the IETF LLC, and the community.
Normally, private financial details would not be included in a Normally, private financial details would not be included in a
public version unless the LLC concludes it is necessary to public version unless the IETF LLC concludes it is necessary to
make such information public. make such information public.
</t> </t>
<t pn="section-2.1.1-2">The RSE is responsible for the performance of
<t>The RSE is responsible for the performance of the RFC Production the RFC Production
Center and Publisher. The RSE is responsible for issues that go Center and Publisher. The RSE is responsible for issues that go
beyond the RFC Production Center or Publisher functions, such as beyond the RFC Production Center or Publisher functions, such as
cross-stream coordination of priorities. Issues that require cross-stream coordination of priorities. Issues that require
changes to the budget or contracts shall be brought to the changes to the budget or contracts shall be brought to the
attention of the LLC by the RSE.</t> attention of the IETF LLC by the RSE.</t>
<t pn="section-2.1.1-3">The RSE is also responsible for creating docum
<t>The RSE is also responsible for creating documentation and entation and
structures that will allow for continuity of the RFC Series in the structures that will allow for continuity of the RFC Series in the
face of changes in contracts and personnel. </t> face of changes in contracts and personnel. </t>
<t pn="section-2.1.1-4">Vendor selection for the RFC Production Center
<t>Vendor selection for the RFC Production Center and Publisher and Publisher
functions is done in cooperation with the streams and under final functions is done in cooperation with the streams and under final
authority of the LLC. Details on this process can be found in authority of the IETF LLC. Details on this process can be found in
<xref target="vendorsel"/>.</t> <xref target="vendorsel" format="default" sectionFormat="of" derivedConten
t="Section 4.1"/>.</t>
</section> </section>
<section anchor="SeriesRep" numbered="true" toc="include" removeInRFC="f
<section anchor="SeriesRep" title="Representation of the RFC Series"> alse" pn="section-2.1.2">
<name slugifiedName="name-representation-of-the-rfc-s">Representation
<t>The RSE is the primary representative of the RFC Series. This of the RFC Series</name>
<t pn="section-2.1.2-1">The RSE is the primary representative of the R
FC Series. This
representation is important both internally, relative to the representation is important both internally, relative to the
IETF, and externally.</t> IETF, and externally.</t>
<section anchor="IETFRep" numbered="true" toc="include" removeInRFC="f
<section anchor="IETFRep" title="Representation to the IETF"> alse" pn="section-2.1.2.1">
<name slugifiedName="name-representation-to-the-ietf">Representation
<t>The RSE is the primary point of contact to the IETF on matters to the IETF</name>
<t pn="section-2.1.2.1-1">The RSE is the primary point of contact to
the IETF on matters
relating to the RFC Series in general, or policy matters relating relating to the RFC Series in general, or policy matters relating
to specific documents. Issues of practical details in the to specific documents. Issues of practical details in the
processing of specific documents are generally worked through processing of specific documents are generally worked through
directly with the RFC Production Center staff.</t> directly with the RFC Production Center staff.</t>
<t pn="section-2.1.2.1-2">This includes providing suitable reports t
<t>This includes providing suitable reports to the community at o the community at
large, providing email contact for policy questions and inputs, large, providing email contact for policy questions and inputs,
and enabling and participating in suitable on-line forums for and enabling and participating in suitable on-line forums for
discussion of issues related to the RFC Series.</t> discussion of issues related to the RFC Series.</t>
<t pn="section-2.1.2.1-3">Due to the history and nature of the inter
<t>Due to the history and nature of the interaction between the action between the
RSE and the IETF, certain principles, described in the following RSE and the IETF, certain principles, described in the following
subsections, must be understood and adhered to by the RSE in his subsections, must be understood and adhered to by the RSE in his
or her interactions with the community. These apply to the or her interactions with the community. These apply to the
representation function, as well as to the leadership the RSE representation function, as well as to the leadership the RSE
provides for production and series development.</t> provides for production and series development.</t>
<section numbered="true" toc="exclude" removeInRFC="false" pn="secti
<section title="Volunteerism"> on-2.1.2.1.1">
<t>The vast majority of Internet technical community work is <name slugifiedName="name-volunteerism">Volunteerism</name>
<t pn="section-2.1.2.1.1-1">The vast majority of Internet technica
l community work is
led, initiated, and done by community volunteers, including led, initiated, and done by community volunteers, including
oversight, policy making, and direct production of, for oversight, policy making, and direct production of, for
example, many software tools. The RSE, while not a volunteer, example, many software tools. The RSE, while not a volunteer,
is dependent upon these volunteer participants. Also, the is dependent upon these volunteer participants. Also, the
spirit of the community is heavily focused on and draws from spirit of the community is heavily focused on and draws from
these volunteers. As such, the RSE needs to support the these volunteers. As such, the RSE needs to support the
vitality and effectiveness of volunteer participation.</t> vitality and effectiveness of volunteer participation.</t>
</section> </section>
<section numbered="true" toc="exclude" removeInRFC="false" pn="secti
<section title="Policy Authority"> on-2.1.2.1.2">
<t>All decisions are to be made in the overall interest of the <name slugifiedName="name-policy-authority">Policy Authority</name
>
<t pn="section-2.1.2.1.2-1">All decisions are to be made in the ov
erall interest of the
broader Internet community. The RSE is responsible for identifying broader Internet community. The RSE is responsible for identifying
materially concerned interest groups within the Internet community materially concerned interest groups within the Internet community
and reaching out to them. Those interest groups include at least the and reaching out to them. Those interest groups include at least the
IETF community, the IRTF community, the network research community, IETF community, the IRTF community, the network research community,
and the network operations community. Other interest groups might and the network operations community. Other interest groups might
also be materially interested.</t> also be materially interested.</t>
<t pn="section-2.1.2.1.2-2">The RSE must consult with the communit
<t>The RSE must consult with the community on policy issues. The RSE y on policy issues. The RSE
works with the community to achieve policy that meets the overall works with the community to achieve policy that meets the overall
quality, continuity, and evolution goals the RSE is charged with quality, continuity, and evolution goals the RSE is charged with
meeting. As described in <xref target="RSOC"/>, the RSE reports the meeting. As described in <xref target="RSOC" format="default" sectionFormat ="of" derivedContent="Section 3.1"/>, the RSE reports the
results of such interactions to the RSOC, including a description of results of such interactions to the RSOC, including a description of
the outreach efforts and the specific recommendations on policy. the outreach efforts and the specific recommendations on policy.
This enables the RSOC to provide the oversight the IAB is required to This enables the RSOC to provide the oversight the IAB is required to
apply, as well as to confirm that the Internet community has been apply, as well as to confirm that the Internet community has been
properly consulted and considered in making policy.</t> properly consulted and considered in making policy.</t>
</section> </section>
</section>
</section> <section anchor="ExtRep" numbered="true" toc="include" removeInRFC="fa
lse" pn="section-2.1.2.2">
<section anchor="ExtRep" title="External Representation"> <name slugifiedName="name-external-representation">External Represen
<t>From time to time, individuals or organizations external to tation</name>
<t pn="section-2.1.2.2-1">From time to time, individuals or organiza
tions external to
the IETF need a contact person to talk to about the RFC Series. the IETF need a contact person to talk to about the RFC Series.
The RSE, or the RSE's designate, serves this role.</t> The RSE, or the RSE's designate, serves this role.</t>
<t pn="section-2.1.2.2-2">Over time, the RSE should determine what,
<t>Over time, the RSE should determine what, if any, means should if any, means should
be employed to increase end-user awareness of the series, to be employed to increase end-user awareness of the series, to
reinforce the stature of the series, and to provide the contact reinforce the stature of the series, and to provide the contact
point for outside parties seeking information on the series or point for outside parties seeking information on the series or
the Editor.</t> the Editor.</t>
</section>
</section> </section>
</section> <section anchor="ProdDev" numbered="true" toc="include" removeInRFC="fal
se" pn="section-2.1.3">
<section anchor="ProdDev" title="Development of RFC Production and Publi <name slugifiedName="name-development-of-rfc-producti">Development of
cation"> RFC Production and Publication</name>
<t pn="section-2.1.3-1">Closely related to providing strategic leaders
<t>Closely related to providing strategic leadership and hip and
management to the RFC Production Center and Publisher functions management to the RFC Production Center and Publisher functions
is the need to develop and improve those functions. The RSE is is the need to develop and improve those functions. The RSE is
responsible for ensuring that such ongoing development takes responsible for ensuring that such ongoing development takes
place.</t> place.</t>
<t>This effort must include the dimensions of document quality, <t pn="section-2.1.3-2">This effort must include the dimensions of doc ument quality,
timeliness of production, and accessibility of results. It timeliness of production, and accessibility of results. It
must also specifically take into account issues raised by the must also specifically take into account issues raised by the
IETF community, including all the streams feeding into the RFC IETF community, including all the streams feeding into the RFC
Editor function.</t> Editor function.</t>
</section> </section>
<section anchor="SeriesDev" numbered="true" toc="include" removeInRFC="f
<section anchor="SeriesDev" title="Development of the RFC Series"> alse" pn="section-2.1.4">
<name slugifiedName="name-development-of-the-rfc-seri">Development of
<t>In order to develop the RFC Series, the RSE is expected to the RFC Series</name>
<t pn="section-2.1.4-1">In order to develop the RFC Series, the RSE is
expected to
develop a relationship with the Internet technical community. The develop a relationship with the Internet technical community. The
Editor is expected to engage with the Internet technical community Editor is expected to engage with the Internet technical community
in a process of articulating and refining a vision for the series in a process of articulating and refining a vision for the series
and its continuous evolution. The RSE is also expected to engage and its continuous evolution. The RSE is also expected to engage
other users of the RFC Series, in particular, the consumers of other users of the RFC Series, in particular, the consumers of
these documents, such as those people who use them to specify these documents, such as those people who use them to specify
products, write code, test behaviors, or other related products, write code, test behaviors, or other related
activities.</t> activities.</t>
<t pn="section-2.1.4-2">Concretely:
<t>Concretely: </t>
<list style="hanging"> <ul empty="true" bare="false" spacing="normal" pn="section-2.1.4-3">
<t>The RSE is responsible for the coordination of discussion on <li pn="section-2.1.4-3.1">
series evolution among the series' stream participants and the <t pn="section-2.1.4-3.1.1">The RSE is responsible for the coordin
broader Internet technical community.</t> ation of discussion on
series evolution among the series' stream participants and the
<t>In time, the RSE is expected to develop and refine a vision for broader Internet technical community.</t>
the RFC Series, including examining: <t pn="section-2.1.4-3.1.2">In time, the RSE is expected to develo
<list style="symbols"> p and refine a vision for
<t>The RFC Series, as it continues to evolve. The RSE is the RFC Series, including examining:</t>
<ul spacing="normal" bare="false" empty="false" pn="section-2.1.4-
3.1.3">
<li pn="section-2.1.4-3.1.3.1">The RFC Series, as it continues t
o evolve. The RSE is
expected to take a broad view and look for the best ways to expected to take a broad view and look for the best ways to
evolve the series for the benefit of the entire Internet evolve the series for the benefit of the entire Internet
community. As such, the RSE may even consider evolution beyond community. As such, the RSE may even consider evolution beyond
the historical 'by engineers for engineers' emphasis; and</t> the historical 'by engineers for engineers' emphasis; and</li>
<li pn="section-2.1.4-3.1.3.2">Its publication-technical environ
<t>Its publication-technical environment, by looking at whether ment, by looking at whether
it should be slowly changing in terms of publishing and it should be slowly changing in terms of publishing and
archiving techniques -- particularly to better serve the archiving techniques -- particularly to better serve the
communities that produce and depend on the RFC Series. For communities that produce and depend on the RFC Series. For
example, all of those communities have been slowly changing to example, all of those communities have been slowly changing to
include a significant population of multi-lingual individuals or include a significant population of multi-lingual individuals or
non-native speakers of English. Another example is that some of non-native speakers of English. Another example is that some of
these constituencies also have shifted to include significant these constituencies also have shifted to include significant
groups whose primary focus is on the constraints and groups whose primary focus is on the constraints and
consequences of network engineering, rather than a primary consequences of network engineering, rather than a primary
interest in the engineering issues themselves.</t> interest in the engineering issues themselves.</li>
</list> </ul>
</t> </li>
</ul>
</list> <t pn="section-2.1.4-4">For this type of responsibility, the RSE coope
</t> rates closely with
<t>For this type of responsibility, the RSE cooperates closely with
the community, and operates under oversight of the RSOC: thus, the community, and operates under oversight of the RSOC: thus,
ultimately, under oversight of the IAB.</t> ultimately, under oversight of the IAB.</t>
</section> </section>
<section anchor="Workload" numbered="true" toc="include" removeInRFC="fa
<section anchor="Workload" title="Workload"> lse" pn="section-2.1.5">
<t>On average, the job is expected to take half of a full-time <name slugifiedName="name-workload">Workload</name>
equivalent position (FTE, thus approx 20 hrs per week), with the <t pn="section-2.1.5-1">On average, the job is expected to take half o
f a full-time
equivalent position (FTE, thus approximately 20 hrs per week), with the
workload per week nearing full time during IETF weeks. In workload per week nearing full time during IETF weeks. In
addition, the job is expected to take more than 20 hours per week addition, the job is expected to take more than 20 hours per week
in the first few months of the engagement and when involved in in the first few months of the engagement and when involved in
special projects. special projects.
</t> </t>
</section> </section>
<section anchor="Qualifications" numbered="true" toc="include" removeInR
<section anchor="Qualifications" title="Qualifications"> FC="false" pn="section-2.1.6">
<t> <name slugifiedName="name-qualifications">Qualifications</name>
The RFC Series Editor is a senior technology professional. <t pn="section-2.1.6-1">
The following qualifications are desired: The RFC Series Editor is a senior technology professional.
<list style="numbers"> The following qualifications are desired:
<t> Strategic leadership and management experience </t>
<ol spacing="normal" type="1" start="1" pn="section-2.1.6-2">
<li pn="section-2.1.6-2.1" derivedCounter="1."> Strategic leadership
and management experience
fulfilling the requirements outlined in this document, the fulfilling the requirements outlined in this document, the
many aspects of this role, and the coordination of the many aspects of this role, and the coordination of the
overall RFC Editor process.</t> overall RFC Editor process.</li>
<t>Good understanding of the English language and technical <li pn="section-2.1.6-2.2" derivedCounter="2.">Good understanding of
terminology related to the Internet.</t> the English language and technical
<t>Good communication skills.</t> terminology related to the Internet.</li>
<t>Experience with editorial processes.</t> <li pn="section-2.1.6-2.3" derivedCounter="3.">Good communication sk
<t>Ability to develop strong understanding of the IETF and ills.</li>
RFC process.</t> <li pn="section-2.1.6-2.4" derivedCounter="4.">Experience with edito
<t>Independent worker.</t> rial processes.</li>
<t>Willingness to, and availability for, travel.</t> <li pn="section-2.1.6-2.5" derivedCounter="5.">Ability to develop st
<t>The ability to work effectively in a multi-actor and rong understanding of the IETF and
RFC process.</li>
<li pn="section-2.1.6-2.6" derivedCounter="6.">Independent worker.</
li>
<li pn="section-2.1.6-2.7" derivedCounter="7.">Willingness to, and a
vailability for, travel.</li>
<li pn="section-2.1.6-2.8" derivedCounter="8.">The ability to work e
ffectively in a multi-actor and
matrixed environment with divided authority and responsibility similar matrixed environment with divided authority and responsibility similar
to that described in this document.</t> to that described in this document.</li>
<t>Experience with and ability to participate in, and <li pn="section-2.1.6-2.9" derivedCounter="9.">Experience with and a
bility to participate in, and
manage, activities by email and teleconferences, not just manage, activities by email and teleconferences, not just
face-to-face interactions.</t> face-to-face interactions.</li>
<t>Demonstrated experience in strategic planning and the <li pn="section-2.1.6-2.10" derivedCounter="10.">Demonstrated experi
management of entire operations.</t> ence in strategic planning and the
<t>Experience as an RFC author.</t> management of entire operations.</li>
</list> <li pn="section-2.1.6-2.11" derivedCounter="11.">Experience as an RF
</t> C author.</li>
</section> </ol>
</section>
<section title="Conflict of Interest"> <section numbered="true" toc="include" removeInRFC="false" pn="section-2
<!-- .1.7">
<t>The RSE is expected to avoid even the appearance of conflict <name slugifiedName="name-conflict-of-interest">Conflict of Interest</
of interest or judgment in performing these roles. As such, the name>
RSE is barred from having any ownership, advisory, or other <t pn="section-2.1.7-1">The RSE is expected to avoid even the appearan
relationship to the vendors executing the RFC Publisher or ce of conflict
Production Center functions except as specified elsewhere in this
document. If necessary, an exception can be made after public
disclosure of those relationships and with the explicit
permission of the IAB and LLC.</t>
<t>The RSE is expected to avoid even the appearance of conflict
of interest or judgment in performing these roles. To ensure of interest or judgment in performing these roles. To ensure
this, the RSE will be subject to a conflict of interest policy this, the RSE will be subject to a conflict of interest policy
established by the LLC. established by the IETF LLC.
</t> </t>
</section>
</section>
</section> </section>
<section anchor="production" numbered="true" toc="include" removeInRFC="fa
<section anchor="production" title="RFC Production Center"> lse" pn="section-2.2">
<t> <name slugifiedName="name-rfc-production-center">RFC Production Center</
The RFC Production Center function is performed by a paid contractor, a name>
nd the <t pn="section-2.2-1">
contractor's responsibilities include the following: The RFC Production Center function is performed by a paid contractor, and the
</t> contractor's responsibilities include the following:
<t> </t>
<list style="numbers"> <ol spacing="normal" type="1" start="1" pn="section-2.2-2">
<t>Editing inputs from all RFC streams to comply with the <li pn="section-2.2-2.1" derivedCounter="1.">Editing inputs from all R
RFC Style Manual, under the direction of the RSE;</t> FC streams to comply with the
<t>Creating records of edits performed on documents;</t> RFC Style Manual, under the direction of the RSE;</li>
<li pn="section-2.2-2.2" derivedCounter="2.">Creating records of edits
<t>Identifying where editorial changes might have technical performed on documents;</li>
impact and seeking necessary clarification;</t> <li pn="section-2.2-2.3" derivedCounter="3.">Identifying where editori
al changes might have technical
<t>Engaging in dialog with authors, document shepherds, impact and seeking necessary clarification;</li>
IANA, and/or stream-dependent contacts when clarification is <li pn="section-2.2-2.4" derivedCounter="4.">Engaging in dialog with a
needed; uthors, document shepherds,
</t> IANA, and/or stream-dependent contacts when clarification is
<t>Creating records of dialog with document authors;</t> needed;
<t>Requesting advice from the RFC Series Editor as needed;</t> </li>
<t>Providing suggestions to the RFC Series Editor as <li pn="section-2.2-2.5" derivedCounter="5.">Creating records of dialo
needed;</t> g with document authors;</li>
<t>Providing sufficient resources to support reviews of RFC <li pn="section-2.2-2.6" derivedCounter="6.">Requesting advice from th
e RFC Series Editor as needed;</li>
<li pn="section-2.2-2.7" derivedCounter="7.">Providing suggestions to
the RFC Series Editor as
needed;</li>
<li pn="section-2.2-2.8" derivedCounter="8.">Providing sufficient reso
urces to support reviews of RFC
Publisher performance by the RFC Series Editor and external Publisher performance by the RFC Series Editor and external
reviews of the RFC Editor function initiated by the IAB or LLC;</t> reviews of the RFC Editor function initiated by the IAB or IETF LLC;</
<t> Coordinating with IANA to ensure correct documentation of li>
IANA-performed protocol registry actions;</t> <li pn="section-2.2-2.9" derivedCounter="9."> Coordinating with IANA t
<t>Assigning RFC numbers;</t> o ensure correct documentation of
<t> Establishing publication readiness of each document IANA-performed protocol registry actions;</li>
through communication with the authors, document shepherds, <li pn="section-2.2-2.10" derivedCounter="10.">Assigning RFC numbers;<
IANA, and/or stream-dependent contacts, and, if needed, with /li>
the RFC Series Editor; </t> <li pn="section-2.2-2.11" derivedCounter="11."> Establishing publicati
<t>Forwarding documents that are ready for publication to the RFC on readiness of each document
Publisher;</t> through communication with the authors, document shepherds,
<t>Forwarding records of edits and author dialog to the RFC IANA, and/or stream-dependent contacts, and, if needed, with
Publisher so these can be preserved;</t> the RFC Series Editor; </li>
<t>Liaising with the streams as needed.</t> <li pn="section-2.2-2.12" derivedCounter="12.">Forwarding documents th
</list> at are ready for publication to the RFC
</t> Publisher;</li>
<t>All these activities will be done under the general direction, <li pn="section-2.2-2.13" derivedCounter="13.">Forwarding records of e
dits and author dialog to the RFC
Publisher so these can be preserved;</li>
<li pn="section-2.2-2.14" derivedCounter="14.">Liaising with the strea
ms as needed.</li>
</ol>
<t pn="section-2.2-3">All these activities will be done under the genera
l direction,
but not day-to-day management, of but not day-to-day management, of
the RSE and need some level of coordination with various the RSE and need some level of coordination with various
submission streams and the RSE. </t> submission streams and the RSE. </t>
<t> <t pn="section-2.2-4">
The RFC Production Center contractor is to be selected through The RFC Production Center contractor is to be selected through
an LLC Request for Proposal (RFP) process as described in <xref target="ve an IETF LLC Request for Proposal (RFP) process as described in <xref targe
ndorsel"/>. t="vendorsel" format="default" sectionFormat="of" derivedContent="Section 4.1"/>
</t> .
</section> </t>
</section>
<section title="RFC Publisher"> <section numbered="true" toc="include" removeInRFC="false" pn="section-2.3
<t> ">
The RFC Publisher responsibilities include the following: <name slugifiedName="name-rfc-publisher">RFC Publisher</name>
</t> <t pn="section-2.3-1">
<t> The RFC Publisher responsibilities include the following:
<list style="numbers"> </t>
<t>Announcing and providing on-line access to RFCs.</t> <ol spacing="normal" type="1" start="1" pn="section-2.3-2">
<t>Providing an on-line system to submit RFC Errata.</t> <li pn="section-2.3-2.1" derivedCounter="1.">Announcing and providing
<t>Providing on-line access to approved RFC Errata.</t> on-line access to RFCs.</li>
<t>Providing backups.</t> <li pn="section-2.3-2.2" derivedCounter="2.">Providing an on-line syst
<t>Providing storage and preservation of records.</t> em to submit RFC Errata.</li>
<t>Authenticating RFCs for legal proceedings.</t> <li pn="section-2.3-2.3" derivedCounter="3.">Providing on-line access
</list> to approved RFC Errata.</li>
</t> <li pn="section-2.3-2.4" derivedCounter="4.">Providing backups.</li>
<t>All these activities will be done under the general direction, but <li pn="section-2.3-2.5" derivedCounter="5.">Providing storage and pre
servation of records.</li>
<li pn="section-2.3-2.6" derivedCounter="6.">Authenticating RFCs for l
egal proceedings.</li>
</ol>
<t pn="section-2.3-3">All these activities will be done under the genera
l direction, but
not day-to-day management, of the RSE and need some level of not day-to-day management, of the RSE and need some level of
coordination with various submission streams and the RSE. </t> coordination with various submission streams and the RSE. </t>
<t> <t pn="section-2.3-4">
The RFC Publisher contractor is to be selected through The RFC Publisher contractor is to be selected through
an LLC RFP process as described in <xref target="vendorsel"/>. an IETF LLC RFP process as described in <xref target="vendorsel" format="d
</t> efault" sectionFormat="of" derivedContent="Section 4.1"/>.
</t>
</section>
</section> </section>
</section> <section numbered="true" toc="include" removeInRFC="false" pn="section-3">
<section title="Committees"> <name slugifiedName="name-committees">Committees</name>
<section title="RFC Series Oversight Committee (RSOC)" anchor="RSOC"> <section anchor="RSOC" numbered="true" toc="include" removeInRFC="false" p
<t>The IAB is responsible for the oversight of the RFC Series and n="section-3.1">
<name slugifiedName="name-rfc-series-oversight-commit">RFC Series Oversi
ght Committee (RSOC)</name>
<t pn="section-3.1-1">The IAB is responsible for the oversight of the RF
C Series and
acts as a body for final conflict resolution, including the acts as a body for final conflict resolution, including the
process described in <xref target="dispute"/>.</t> process described in <xref target="dispute" format="default" sectionFormat="
of" derivedContent="Section 4.3"/>.</t>
<t>In order to provide continuity over periods longer than the NomCom <t pn="section-3.1-2">In order to provide continuity over periods longer
appointment cycle <xref target="RFC3777"/> and assure that oversight include than the NomCom
s suitable appointment cycle <xref target="RFC8713" format="default" sectionFormat="of"
derivedContent="RFC8713"/> and assure that oversight includes suitable
subject matter expertise, the IAB will establish a group that implements subject matter expertise, the IAB will establish a group that implements
oversight for the IAB, the RFC Series Oversight Committee (RSOC).</t> oversight for the IAB, the RFC Series Oversight Committee (RSOC).</t>
<t pn="section-3.1-3">The RSOC will act with authority delegated from th
<t>The RSOC will act with authority delegated from the IAB: in general, e IAB: in general,
it will be the RSOC that will approve consensus policy and vision it will be the RSOC that will approve consensus policy and vision
documents as developed by the RSE in collaboration with the documents as developed by the RSE in collaboration with the
community. While it is expected that the IAB will exercise due community. While it is expected that the IAB will exercise due
diligence in its supervision of the RSOC, the RSOC should be diligence in its supervision of the RSOC, the RSOC should be
allowed the latitude to do its job without undue interference allowed the latitude to do its job without undue interference
from the IAB. Therefore, it is expected that the IAB from the IAB. Therefore, it is expected that the IAB
will accord RSOC reports and recommendations the benefit of will accord RSOC reports and recommendations the benefit of
the doubt.</t> the doubt.</t>
<t pn="section-3.1-4">
<t>
<!--
For all decisions that affect the RSE individually (e.g., hiring and firing),
the RSOC prepares recommendations for the IAB, but the final decision is
the responsibility of the IAB.
For all decisions that affect the RSE individually (e.g., hiring and For all decisions that affect the RSE individually (e.g., hiring and
firing), the RSOC prepares recommendations for the IAB, but approval firing), the RSOC prepares recommendations for the IAB. The final
of these recommendations is the responsibility of the IAB. recommendation to the IETF LLC is the responsibility of the IAB, after
discussion with RSOC on the recommendations.
For instance the RSOC would do the following: For instance the RSOC would do the following:
</t>
<list style="symbols"> <ul spacing="normal" bare="false" empty="false" pn="section-3.1-5">
<t>perform annual reviews of the RSE and report the result of <li pn="section-3.1-5.1">perform annual reviews of the RSE and report
these reviews to the IAB.</t> the result of
these reviews to the IAB.</li>
<t> manage RSE candidate selection and advise the IAB on candidate <li pn="section-3.1-5.2"> manage RSE candidate selection and advise th
e IAB on candidate
appointment (in other words, select the RSE subject to IAB appointment (in other words, select the RSE subject to IAB
approval).</t> approval).</li>
</list> </ul>
</t> <t pn="section-3.1-6">RSOC members are expected to recognize potential c
onflicts of
<t>RSOC members are expected to recognize potential conflicts of
interest and behave accordingly.</t> interest and behave accordingly.</t>
<t pn="section-3.1-7">For the actual recruitment and selection of the RS
<t>For the actual recruitment and selection of the RSE, the RSOC will E, the RSOC will
propose a budget for the search process. It will work with the LLC propose a budget for the search process. It will work with the IETF LLC
to refine that budget and develop remuneration criteria and an to refine that budget and develop remuneration criteria and an
employment agreement or contracting plans, as appropriate. employment agreement or contracting plans, as appropriate.
</t> </t>
<t pn="section-3.1-8">The RSOC will be responsible for ensuring that the
<t>The RSOC will be responsible for ensuring that the RFC Series is run in RFC Series is run in
a transparent and accountable manner.</t> a transparent and accountable manner.</t>
<t pn="section-3.1-9">The RSOC shall develop and publish its own rules o
<t>The RSOC shall develop and publish its own rules of order.</t> f order.</t>
<t pn="section-3.1-10">The initial RSOC was charged with designing and e
<t>The initial RSOC was charged with designing and executing a xecuting a
solicitation, search, and selection process for the first actual (not solicitation, search, and selection process for the first actual (not
transitional or "acting") RSE appointment. That process involved transitional or "acting") RSE appointment. That process involved
iteration on this and related documents and evaluation of various iteration on this and related documents and evaluation of various
strategies and options. During the creation of this document, it was strategies and options. During the creation of what became <xref target="RFC 6635" format="default" sectionFormat="of" derivedContent="RFC6635"/>, it was
expected that the RSOC would describe the process it ultimately expected that the RSOC would describe the process it ultimately
selected to the community. The RSOC did involve the community in selected to the community. The RSOC did involve the community in
interim considerations when that was likely to be of value. Following interim considerations when that was likely to be of value. Following
completion of the selection process, the RSOC will determine the best completion of the selection process, the RSOC will determine the best
way to share information learned and experience gained with the way to share information learned and experience gained with the
community and determine how to best preserve that information for community and determine how to best preserve that information for
future use. future use.
</t> </t>
<section anchor="RSOCCompose" numbered="true" toc="include" removeInRFC=
<section anchor="RSOCCompose" title="RSOC Composition"> "false" pn="section-3.1.1">
<name slugifiedName="name-rsoc-composition">RSOC Composition</name>
<t> <t pn="section-3.1.1-1">
The RSOC will operate under the authority of the IAB, with the IAB The RSOC will operate under the authority of the IAB, with the IAB
retaining final responsibility. The IAB will delegate authority and retaining final responsibility. The IAB will delegate authority and
responsibility to the RSOC as appropriate and as RSOC and RSE responsibility to the RSOC as appropriate and as RSOC and RSE
relationships evolve. The RSOC will include people who are not relationships evolve. The RSOC will include people who are not
current IAB members. Currently, this is aligned with the IAB current IAB members. Currently, this is aligned with the IAB
program structure. The IAB will designate the program structure. The IAB will designate the
membership of the RSOC with the following goals: preserving effective membership of the RSOC with the following goals: preserving effective
stability; keeping it small enough to be effective, and keeping it large enou gh stability; keeping it small enough to be effective, and keeping it large enou gh
to provide general Internet community expertise, specific IETF to provide general Internet community expertise, specific IETF
expertise, publication expertise, and stream expertise. Members expertise, publication expertise, and stream expertise. Members
serve at the pleasure of the IAB and are expected to bring a balance serve at the pleasure of the IAB and are expected to bring a balance
between short- and long-term perspectives. Specific input about, and between short- and long-term perspectives. Specific input about, and
recommendations of, members will be sought from the streams, the recommendations of, members will be sought from the streams, the
LLC, and the RSE.</t> IETF LLC, and the RSE.</t>
<t pn="section-3.1.1-2">In addition to the members from outside of the
<t>In addition to the members from outside of the IAB appointed to the IAB appointed to the
RSOC, IAB members may participate as full members of the RSOC. Under RSOC, IAB members may participate as full members of the RSOC. Under
most circumstances, there will be a specific individual IAB member most circumstances, there will be a specific individual IAB member
appointed by the IAB as the program lead, who will be a full member of appointed by the IAB as the program lead, who will be a full member of
the RSOC. This member's role is distinct from any RSOC-internal the RSOC. This member's role is distinct from any RSOC-internal
organizational roles, such as would be created by the RSOC choosing to organizational roles, such as would be created by the RSOC choosing to
appoint a chair from among its members. Other IAB members may choose appoint a chair from among its members. Other IAB members may choose
to be full members of the RSOC, with the consent of the IAB. This to be full members of the RSOC, with the consent of the IAB. This
consent is primarily concerned with avoiding overpopulating the RSOC consent is primarily concerned with avoiding overpopulating the RSOC
and providing it with relatively stable membership, which will work and providing it with relatively stable membership, which will work
best if it is not too large a committee.</t> best if it is not too large a committee.</t>
<t pn="section-3.1.1-3">The IETF LLC will appoint an individual to ser
<t>The LLC will appoint an individual to serve as its liaison to ve as its liaison to
the RSOC. The RSE and the LLC Liaison will serve as the RSOC. The RSE and the IETF LLC Liaison will serve as
non-voting ex officio members of the RSOC. Either or both can be non-voting ex officio members of the RSOC. Either or both can be
excluded from its discussions if necessary.</t> excluded from its discussions if necessary.</t>
</section> </section>
</section> </section>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false" pn="section-4">
<section title="Administrative Implementation"> <name slugifiedName="name-administrative-implementati">Administrative Impl
<t> ementation</name>
<t pn="section-4-1">
The exact implementation of the administrative and contractual The exact implementation of the administrative and contractual
activities described here are a responsibility of the IETF activities described here are a responsibility of the IETF
Administration Limited Liability Company <xref Administration Limited Liability Company <xref target="RFC8711" format="de
target="I-D.ietf-iasa2-rfc4071bis"/> in cooperation with the RFC Series fault" sectionFormat="of" derivedContent="RFC8711"/> in cooperation with the RFC
Editor. The authority structure is described in Figure 2 below. Series
Editor. The authority structure is described in <xref target="auth-figure
" format="default" sectionFormat="of" derivedContent="Figure 2"/>.
</t> </t>
<t> <figure anchor="auth-figure" align="left" suppress-title="false" pn="figur
<figure anchor="auth-figure"> e-2">
<artwork> <name slugifiedName="name-authority-structure-of-the-">Authority Structu
<![CDATA[ re of the RFC Series</name>
<artwork name="" type="" align="left" alt="" pn="section-4-2.1">
+----------------+ +----------------+ +----------------+ +----------------+
| | | | | | | |
| IAB | | LLC | | IAB | | IETF LLC |
| | | | | | | |
+==========+-----+ +-+--------------+ +==========+-----+ +-+--------------+
| | . | | .
| RSOC | . | RSOC | .
| | . | | .
+----+-----+ . +----+-----+ .
| . | .
| . | .
| ................... | ...................
| . . | . .
skipping to change at line 796 skipping to change at line 837
| . . | . .
+--+----------------+ . +--+----------------+ .
| . | . | . | .
| . | . | . | .
+---V-----V--+ +--V----V---+ +---V-----V--+ +--V----V---+
| RFC | | RFC | | RFC | | RFC |
| Production | | Publisher | | Production | | Publisher |
| Center | | | | Center | | |
+------------+ +-----------+ +------------+ +-----------+
Authority Structure of the RFC Series
Legend: Legend:
------- IAB RFC Series Oversight ------- IAB RFC Series Oversight
....... LLC Contract/Budget Oversight ....... IETF LLC Contract/Budget Oversight
]]>
</artwork> </artwork>
</figure> </figure>
</t> <section anchor="vendorsel" numbered="true" toc="include" removeInRFC="fal
se" pn="section-4.1">
<section anchor="vendorsel" title="Vendor Selection for the <name slugifiedName="name-vendor-selection-for-the-pr">Vendor Selection
Production and Publisher Functions"> for the Production and Publisher Functions</name>
<t pn="section-4.1-1">As stated earlier, vendor selection is done in coo
<t>As stated earlier, vendor selection is done in cooperation peration
with the streams and under the final authority of the LLC.</t> with the streams and under the final authority of the IETF LLC.</t>
<t pn="section-4.1-2">The RSE owns and develops the work definition (the
<t>The RSE owns and develops the work definition (the SOW) and SOW) and
participates in the LLC vendor selection process. participates in the IETF LLC vendor selection process.
The work definition is created within the LLC budget and The work definition is created within the IETF LLC budget and
takes into account the stream managers and community input.</t> takes into account the stream managers and community input.</t>
<t pn="section-4.1-3">The process to select and contract for an RFC Prod
<t>The process to select and contract for an RFC Production uction
Center, RFC Publisher, and other RFC-related services, is as Center, RFC Publisher, and other RFC-related services, is as
follows: </t> follows: </t>
<ul spacing="normal" bare="false" empty="false" pn="section-4.1-4">
<t> <li pn="section-4.1-4.1">The IETF LLC establishes the contract process
<list style="symbols"> , including
<t>The LLC establishes the contract process, including
the steps necessary to issue an RFP when necessary, the timing, the steps necessary to issue an RFP when necessary, the timing,
and the contracting procedures. and the contracting procedures.
</t> </li>
<li pn="section-4.1-4.2">The IETF LLC establishes the Selection Commit
<t>The LLC establishes the Selection Committee, which tee, which
will consist of the RSE, the LLC Executive Director, and other will consist of the RSE, the IETF LLC Executive Director, and other
members selected by the RSOC and the LLC. The Committee members selected by the RSOC and the IETF LLC. The Committee
shall be chaired by the RSE.</t> shall be chaired by the RSE.</li>
<li pn="section-4.1-4.3">The Selection Committee selects the vendor, s
<t>The Selection Committee selects the vendor, subject to the ubject to the
successful negotiation of a contract approved by the LLC. successful negotiation of a contract approved by the IETF LLC.
In the event that a contract cannot be reached, the matter In the event that a contract cannot be reached, the matter
shall be referred to the Selection Committee for further shall be referred to the Selection Committee for further
action.</t> action.</li>
<li pn="section-4.1-4.4">The Selection Committee may select an RFC Pub
<t>The Selection Committee may select an RFC Publisher either lisher either
through the LLC RFP process or, at the Committee's option, the through the IETF LLC RFP process or, at the Committee's option, the
Committee may select the IETF Secretariat to provide RFC Committee may select the IETF Secretariat to provide RFC
Publisher services, subject to negotiations in accordance with Publisher services, subject to negotiations in accordance with
the LLC procedures. </t> the IETF LLC procedures. </li>
</list> </ul>
</t>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false" pn="section-4.2
<section title="Budget"> ">
<t> <name slugifiedName="name-budget">Budget</name>
The expenses discussed in this document are not new <t pn="section-4.2-1">
expenses. They have been and remain part of the The expenses discussed in this document are not new
expenses. They have been and remain part of the
IETF Administration Limited Liability Company IETF Administration Limited Liability Company
<xref target="I-D.ietf-iasa2-rfc4071bis"/> budget. <xref target="RFC8711" format="default" sectionFormat="of" derivedConte
</t> nt="RFC8711"/> budget.
</t>
<t> <t pn="section-4.2-2">
<!-- The RFC Series portion of the IETF LLC budget shall include funding to
The RFC Series portion of the LLC budget shall include entries support the RSE, RFC Production Center, RFC Publisher, and the
for the RSOC, RSE, RFC Production Center, and the RFC Publisher. Independent Stream.
The LLC budget shall also include entries for the streams, </t>
including the independent stream. <t pn="section-4.2-3">The IETF LLC has the responsibility to approve the
--> total RFC
The RFC Series portion of the LLC budget shall include funding to
support the RSE, RFC Production Center, RFC Publisher, and the
Independent Stream.
</t>
<t>The LLC has the responsibility to approve the total RFC
Editor budget (and the authority to deny it). The RSE must work Editor budget (and the authority to deny it). The RSE must work
within the LLC budgetary process.</t> within the IETF LLC budgetary process.</t>
<t pn="section-4.2-4">The RSE is responsible for managing the RFC Editor
<t>The RSE is responsible for managing the RFC Editor function function
to operate within those budgets. If production needs change, to operate within those budgets. If production needs change,
the RSE is responsible for working with the Production Center, the RSE is responsible for working with the Production Center,
and where appropriate, other RFC Editor component institutions, and where appropriate, other RFC Editor component institutions,
relevant streams, and/or the RSOC to determine what the correct relevant streams, and/or the RSOC to determine what the correct
response should be. If they agree that a budgetary change is response should be. If they agree that a budgetary change is
needed, that decision needs to be taken to the LLC.</t> needed, that decision needs to be taken to the IETF LLC.</t>
</section> </section>
<section anchor="dispute" title="Disagreements among Entities Related to t <section anchor="dispute" numbered="true" toc="include" removeInRFC="false
he RFC Editor"> " pn="section-4.3">
<name slugifiedName="name-disagreements-among-entitie">Disagreements amo
<t>The RFC Series Editor and the RFC Production Center and ng Entities Related to the RFC Editor</name>
Publisher facilities work with the various streams to produce <t pn="section-4.3-1">The RFC Series Editor and the RFC Production Cente
RFCs. Disagreements may arise between these entities during the r and
execution of the RFC Editor operations. In particular, different Publisher facilities work with the various streams to produce
streams may disagree with each other, or disagree with the RFC RFCs. Disagreements may arise between these entities during the
Editor function. Potentially, even the RSOC or the LLC execution of the RFC Editor operations. In particular, different
could find themselves in disagreement with some aspect of the RFC streams may disagree with each other, or disagree with the RFC
Editor operations. Note that disagreements between an author and Editor function. Potentially, even the RSOC or the IETF LLC
the RFC Production Center are not cross-entity issues, and they could find themselves in disagreement with some aspect of the RFC
are to be resolved by the RSE, in accordance with the rest of Editor operations. Note that disagreements between an author and
this document. the RFC Production Center are not cross-entity issues, and they
are to be resolved by the RSE, in accordance with the rest of
this document.
</t> </t>
<t pn="section-4.3-2">
<t>
If such cross-entity disagreements arise, the community would If such cross-entity disagreements arise, the community would
generally hope that they can be resolved politely and directly. generally hope that they can be resolved politely and directly.
However, this is not always possible. At that point, any relevant However, this is not always possible. At that point, any relevant
party would first formally request a review and reconsideration party would first formally request a review and reconsideration
of the decision. If the party still disagrees after the of the decision. If the party still disagrees after the
reconsideration, that party may ask the RSE to decide or, reconsideration, that party may ask the RSE to decide or,
especially if the RSE is involved, the party may ask the IAB especially if the RSE is involved, the party may ask the IAB
Chair (for a technical or procedural matter) to mediate or Chair (for a technical or procedural matter) to mediate or
appoint a mediator to aid in the discussions, although he or she appoint a mediator to aid in the discussions, although he or she
not is obligated to do so. All parties should work informally and not is obligated to do so. All parties should work informally and
in good faith to reach a mutually agreeable conclusion. As noted in good faith to reach a mutually agreeable conclusion. As noted
below, any such issues that involve contractual matters must be below, any such issues that involve contractual matters must be
brought to the attention of the LLC. If the IAB Chair is brought to the attention of the IETF LLC. If the IAB Chair is
asked to assist in resolving the matter, the Chair may ask for asked to assist in resolving the matter, the Chair may ask for
advice or seek assistance from anyone the Chair deems helpful. advice or seek assistance from anyone the Chair deems helpful.
The Chair may also alert any appropriate individuals or The Chair may also alert any appropriate individuals or
organizations to the existence of the issue. organizations to the existence of the issue.
</t> </t>
<t pn="section-4.3-3">
<t> If such a conclusion is not possible through the above less formal
If such a conclusion is not possible through the above less formal processes, then the matter must be registered with the RFC
processes, then the matter must be registered with the RFC Series Oversight Committee. The RSOC may choose to offer advice
Series Oversight Committee. The RSOC may choose to offer advice to the RSE or more general advice to the parties involved
to the RSE or more general advice to the parties involved and may ask the RSE to defer a decision until it formulates
and may ask the RSE to defer a decision until it formulates its advice. However, if a timely decision cannot be reached
its advice. However, if a timely decision cannot be reached through discussion, mediation, and mutual agreement, the
through discussion, mediation, and mutual agreement, the RSE is expected to make whatever decisions are
RSE is expected to make whatever decisions are needed to ensure the smooth operation of the RFC Editor
needed to ensure the smooth operation of the RFC Editor function; those decisions are final.
function; those decisions are final. </t>
</t> <t pn="section-4.3-4">
The RSE may make final decisions unilaterally only to assure
<t> the functioning of the process, and only while there is an
The RSE may make final decisions unilaterally only to assure evaluation of current policies to determine whether they are
the functioning of the process, and only while there is an appropriately implemented in the decision or need
evaluation of current policies to determine whether they are adjustment. In particular, it should be noted that final
appropriately implemented in the decision or need decisions about the technical content of individual documents
adjustment. In particular, it should be noted that final are the exclusive responsibility of the stream approvers from
decisions about the technical content of individual documents which those documents originate, as shown in the illustration
are the exclusive responsibility of the stream approvers from in <xref target="model-figure" format="default" sectionFormat="of" derivedCont
which those documents originate, as shown in the illustration ent="Figure 1"/>.
in <xref target="model-figure"/>.
</t>
<t> </t>
If informal agreements cannot be reached, then formal RSOC <t pn="section-4.3-5">
review and decision making may be required. If so, the If informal agreements cannot be reached, then formal RSOC
RSE must present the issues involved to the community review and decision making may be required. If so, the
RSE must present the issues involved to the community
so that the community is aware of the situation. The RSE so that the community is aware of the situation. The RSE
will then report the issue to the RSOC for formal resolution will then report the issue to the RSOC for formal resolution
by the RSOC with confirmation by the IAB in its oversight by the RSOC with confirmation by the IAB in its oversight
capacity. capacity.
</t> </t>
<t> <t pn="section-4.3-6">
IAB and community discussion of any patterns of disputes are IAB and community discussion of any patterns of disputes are
expected to inform future changes to RFC Series policies, expected to inform future changes to RFC Series policies,
including possible updates to this document. including possible updates to this document.
</t> </t>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false" pn="section-4.4
<section title="Issues with Contractual Impact"> ">
<t> <name slugifiedName="name-issues-with-contractual-imp">Issues with Contr
<!-- actual Impact</name>
If a disagreement or decision has immediate or future <t pn="section-4.4-1">
contractual consequences, it falls under
<xref target="I-D.ietf-iasa2-rfc4071bis"/>;
thus, the RSE must identify
the issue and provide his or her advice to the LLC; additionally,
if the RSOC has provided advice,
forward that advice as well. The LLC must notify the RSOC
and IAB regarding the action it concludes is required to
resolve the issue based on its applicable procedures and
provisions in the relevant contracts.
If a disagreement or decision has immediate or future If a disagreement or decision has immediate or future
contractual consequences, it falls under contractual consequences, it falls under
<xref target="I-D.ietf-iasa2-rfc4071bis"/>. If this happens the RSE mus <xref target="RFC8711" format="default" sectionFormat="of" derivedContent="RFC8
t 711"/>. If this happens, the RSE must
identify the issue and provide advice to the LLC. identify the issue and provide advice to the IETF LLC.
Additionally, if the RSOC has also developed advice, it should Additionally, if the RSOC has also developed advice, it should
forward that advice to the LLC.</t> forward that advice to the IETF LLC.</t>
<t pn="section-4.4-2">The IETF LLC must notify the RSOC and IAB regardin
<t>The LLC must notify the RSOC and IAB regarding the action it g the action it
concludes is required to resolve the issue based on its concludes is required to resolve the issue based on its
applicable procedures and provisions in the relevant contracts. applicable procedures and provisions in the relevant contracts.
</t> </t>
</section>
</section> </section>
</section> <section numbered="true" toc="include" removeInRFC="false" pn="section-5">
<name slugifiedName="name-iana-considerations">IANA Considerations</name>
<section title="IANA Considerations"> <t pn="section-5-1">
<t>
This document defines several functions within the overall This document defines several functions within the overall
RFC Editor structure, and it places the responsibility for RFC Editor structure, and it places the responsibility for
coordination of registry value assignments with the RFC coordination of registry value assignments with the RFC
Production Center. The LLC will facilitate the establishment Production Center. The IETF LLC will facilitate the establishment
of the relationship between the RFC Production Center and IANA. of the relationship between the RFC Production Center and IANA.
</t> </t>
<t> <t pn="section-5-2">
This document does not create a new registry nor does it This document does not create a new registry nor does it
register any values in existing registries, and no IANA action register any values in existing registries, and no IANA action
is required. is required.
</t> </t>
</section>
</section> <section numbered="true" toc="include" removeInRFC="false" pn="section-6">
<section title="Security Considerations"> <name slugifiedName="name-security-considerations">Security Considerations
<t> </name>
The same security considerations as those in <xref target="RFC4844" /> app <t pn="section-6-1">
ly. The The same security considerations as those in <xref target="RFC8729" format
="default" sectionFormat="of" derivedContent="RFC8729"/> apply. The
processes for the publication of documents must prevent the processes for the publication of documents must prevent the
introduction of unapproved changes. Since the RFC Editor introduction of unapproved changes. Since the RFC Editor
maintains the index of publications, sufficient security must be maintains the index of publications, sufficient security must be
in place to prevent these published documents from being changed in place to prevent these published documents from being changed
by external parties. The archive of RFC documents, any source by external parties. The archive of RFC documents, any source
documents needed to recreate the RFC documents, and any documents needed to recreate the RFC documents, and any
associated original documents (such as lists of errata, tools, associated original documents (such as lists of errata, tools,
and, for some early items, originals that are not and, for some early items, originals that are not
machine readable) need to be secured against any kind of data machine readable) need to be secured against any kind of data
storage failure. storage failure.
</t> </t>
<t> <t pn="section-6-2">
The LLC should take these security considerations into The IETF LLC should take these security considerations into
account during the implementation and enforcement of the RFC account during the implementation and enforcement of the RFC
Editor component contracts. Editor component contracts.
</t> </t>
</section> </section>
</middle>
<section title="Acknowledgments"> <back>
<t> <references pn="section-7">
<name slugifiedName="name-references">References</name>
<references pn="section-7.1">
<name slugifiedName="name-normative-references">Normative References</na
me>
<reference anchor="RFC2850" target="https://www.rfc-editor.org/info/rfc2
850" quoteTitle="true" derivedAnchor="RFC2850">
<front>
<title>Charter of the Internet Architecture Board (IAB)</title>
<author>
<organization showOnFrontPage="true">Internet Architecture Board</
organization>
</author>
<author initials="B." surname="Carpenter" fullname="B. Carpenter" ro
le="editor">
<organization showOnFrontPage="true"/>
</author>
<date year="2000" month="May"/>
<abstract>
<t>This memo documents the composition, selection, roles, and orga
nization of the Internet Architecture Board. It replaces RFC 1601. This docume
nt specifies an Internet Best Current Practices for the Internet Community, and
requests discussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="39"/>
<seriesInfo name="RFC" value="2850"/>
<seriesInfo name="DOI" value="10.17487/RFC2850"/>
</reference>
<reference anchor="RFC6635" target="https://www.rfc-editor.org/info/rfc6
635" quoteTitle="true" derivedAnchor="RFC6635">
<front>
<title>RFC Editor Model (Version 2)</title>
<author initials="O." surname="Kolkman" fullname="O. Kolkman" role="
editor">
<organization showOnFrontPage="true"/>
</author>
<author initials="J." surname="Halpern" fullname="J. Halpern" role="
editor">
<organization showOnFrontPage="true"/>
</author>
<author>
<organization showOnFrontPage="true">IAB</organization>
</author>
<date year="2012" month="June"/>
<abstract>
<t>The RFC Editor model described in this document divides the res
ponsibilities for the RFC Series into three functions: the RFC Series Editor, th
e RFC Production Center, and the RFC Publisher. Internet Architecture Board (IAB
) oversight via the RFC Series Oversight Committee (RSOC) is described, as is th
e relationship between the IETF Administrative Oversight Committee (IAOC) and th
e RSOC. This document reflects the experience gained with "RFC Editor Model (Ve
rsion 1)", documented in RFC 5620, and obsoletes that document. This document i
s not an Internet Standards Track specification; it is published for informatio
nal purposes.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6635"/>
<seriesInfo name="DOI" value="10.17487/RFC6635"/>
</reference>
<reference anchor="RFC8711" target="https://www.rfc-editor.org/info/rfc8
711" quoteTitle="true" derivedAnchor="RFC8711">
<front>
<title>Structure of the IETF Administrative Support Activity, Versio
n 2.0</title>
<author initials="B." surname="Haberman">
<organization showOnFrontPage="true"/>
</author>
<author initials="J." surname="Hall">
<organization showOnFrontPage="true"/>
</author>
<author initials="J." surname="Livingood">
<organization showOnFrontPage="true"/>
</author>
<date year="2020" month="February"/>
</front>
<seriesInfo name="BCP" value="101"/>
<seriesInfo name="RFC" value="8711"/>
<seriesInfo name="DOI" value="10.17487/RFC8711"/>
</reference>
<reference anchor="RFC8729" target="https://www.rfc-editor.org/info/rfc8
729" quoteTitle="true" derivedAnchor="RFC8729">
<front>
<title>The RFC Series and RFC Editor</title>
<author initials="R." surname="Housley" role="editor">
<organization showOnFrontPage="true"/>
</author>
<author initials="L." surname="Daigle" role="editor">
<organization showOnFrontPage="true"/>
</author>
<date month="February" year="2020"/>
</front>
<seriesInfo name="RFC" value="8729"/>
<seriesInfo name="DOI" value="10.17487/RFC8729"/>
</reference>
</references>
<references pn="section-7.2">
<name slugifiedName="name-informative-references">Informative References
</name>
<reference anchor="RFC5620" target="https://www.rfc-editor.org/info/rfc5
620" quoteTitle="true" derivedAnchor="RFC5620">
<front>
<title>RFC Editor Model (Version 1)</title>
<author initials="O." surname="Kolkman" fullname="O. Kolkman" role="
editor">
<organization showOnFrontPage="true"/>
</author>
<author>
<organization showOnFrontPage="true">IAB</organization>
</author>
<date year="2009" month="August"/>
<abstract>
<t>The RFC Editor performs a number of functions that may be carri
ed out by various persons or entities. The RFC Editor model presented in this d
ocument divides the responsibilities for the RFC Series into four functions: The
RFC Series Editor, the Independent Submission Editor, the RFC Production Center
, and the RFC Publisher. It also introduces the RFC Series Advisory Group and a
n (optional) Independent Submission Stream Editorial Board. The model outlined
here is intended to increase flexibility and operational support options, provid
e for the orderly succession of the RFC Editor, and ensure the continuity of the
RFC series, while maintaining RFC quality and timely processing, ensuring docum
ent accessibility, reducing costs, and increasing cost transparency. This memo
provides information for the Internet community.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5620"/>
<seriesInfo name="DOI" value="10.17487/RFC5620"/>
</reference>
<reference anchor="RFC8713" target="https://www.rfc-editor.org/info/rfc8
713" quoteTitle="true" derivedAnchor="RFC8713">
<front>
<title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation,
and Recall Process: Operation of the IETF Nominating and Recall Committees</titl
e>
<author initials="M." surname="Kucherawy" role="editor">
<organization showOnFrontPage="true"/>
</author>
<author initials="R." surname="Hinden" role="editor">
<organization showOnFrontPage="true"/>
</author>
<author initials="J." surname="Livingood" role="editor">
<organization showOnFrontPage="true"/>
</author>
<date year="2020" month="February"/>
</front>
<seriesInfo name="BCP" value="10"/>
<seriesInfo name="RFC" value="8713"/>
<seriesInfo name="DOI" value="10.17487/RFC8713"/>
</reference>
</references>
</references>
<section numbered="false" toc="include" removeInRFC="false" pn="section-appe
ndix.a">
<name slugifiedName="name-iab-members-at-the-time-of-">IAB Members at the
Time of Approval</name>
<t pn="section-appendix.a-1">Internet Architecture Board Members at the ti
me this document
was approved for publication were:
</t>
<ul empty="true" spacing="compact" bare="false" pn="section-appendix.a-2">
<li pn="section-appendix.a-2.1">
<t pn="section-appendix.a-2.1.1"><contact fullname="Jari Arkko"/></t>
</li>
<li pn="section-appendix.a-2.2">
<t pn="section-appendix.a-2.2.1"><contact fullname="Alissa Cooper"/></
t>
</li>
<li pn="section-appendix.a-2.3">
<t pn="section-appendix.a-2.3.1"><contact fullname="Stephen Farrell"/>
</t>
</li>
<li pn="section-appendix.a-2.4">
<t pn="section-appendix.a-2.4.1"><contact fullname="Wes Hardaker"/></t
>
</li>
<li pn="section-appendix.a-2.5">
<t pn="section-appendix.a-2.5.1"><contact fullname="Ted Hardie"/></t>
</li>
<li pn="section-appendix.a-2.6">
<t pn="section-appendix.a-2.6.1"><contact fullname="Christian Huitema"
/></t>
</li>
<li pn="section-appendix.a-2.7">
<t pn="section-appendix.a-2.7.1"><contact fullname="Zhenbin Li"/></t>
</li>
<li pn="section-appendix.a-2.8">
<t pn="section-appendix.a-2.8.1"><contact fullname="Erik Nordmark"/></
t>
</li>
<li pn="section-appendix.a-2.9">
<t pn="section-appendix.a-2.9.1"><contact fullname="Mark Nottingham"/>
</t>
</li>
<li pn="section-appendix.a-2.10">
<t pn="section-appendix.a-2.10.1"><contact fullname="Melinda Shore"/><
/t>
</li>
<li pn="section-appendix.a-2.11">
<t pn="section-appendix.a-2.11.1"><contact fullname="Jeff Tantsura"/><
/t>
</li>
<li pn="section-appendix.a-2.12">
<t pn="section-appendix.a-2.12.1"><contact fullname="Martin Thomson"/>
</t>
</li>
<li pn="section-appendix.a-2.13">
<t pn="section-appendix.a-2.13.1"><contact fullname="Brian Trammell"/>
</t>
</li>
</ul>
</section>
<section numbered="false" toc="include" removeInRFC="false" pn="section-appe
ndix.b">
<name slugifiedName="name-acknowledgments">Acknowledgments</name>
<t pn="section-appendix.b-1">
The RFC Editor model was conceived and discussed in hallways and The RFC Editor model was conceived and discussed in hallways and
on mailing lists. The first iteration of the text on which this on mailing lists. The first iteration of the text on which this
document is based was first written by Leslie Daigle, Russ document is based was first written by Leslie Daigle, Russ
Housley, and Ray Pelletier. In addition to the members of the Housley, and Ray Pelletier. In addition to the members of the
IAOC and IAB in conjunction with those roles, major and minor IAOC and IAB in conjunction with those roles, major and minor
contributions were made by (in alphabetical order): Bob Braden, contributions were made by (in alphabetical order): <contact fullname="Bob
Brian Carpenter, Sandy Ginoza, Alice Russo, Joel M. Halpern, Braden"/>,
Alfred Hoenes, Paul Hoffman, John Klensin, Subramanian Moonesamy, and Jim <contact fullname="Brian Carpenter"/>, <contact fullname="Sandy Ginoza"/>,
Schaad. <contact fullname="Joel M. Halpern"/>, <contact fullname="Alfred Hoe
</t> nes"/>, <contact fullname="Paul Hoffman"/>, <contact fullname="John Klensi
<t> n"/>, <contact fullname="Subramanian Moonesamy"/>, <contact fullname="Alice Russ
The IAOC members at the time this RFC Editor model was approved o"/>, and <contact fullname="Jim Schaad"/>.
</t>
<t pn="section-appendix.b-2">
The IAOC members at the time RFC 6635 was approved
were (in alphabetical order): were (in alphabetical order):
Bernard Aboba (ex officio), <contact fullname="Bernard Aboba"/> (ex officio),
Eric Burger, <contact fullname="Eric Burger"/>,
Dave Crocker, <contact fullname="Dave Crocker"/>,
Marshall Eubanks, <contact fullname="Marshall Eubanks"/>,
Bob Hinden, <contact fullname="Bob Hinden"/>,
Russ Housley (ex officio), <contact fullname="Russ Housley"/> (ex officio),
Ole Jacobsen, <contact fullname="Ole Jacobsen"/>,
Ray Pelletier (non-voting), and <contact fullname="Ray Pelletier"/> (non-voting), and
Lynn St. Amour (ex officio). <contact fullname="Lynn St. Amour"/> (ex officio).
</t> </t>
<t> <t pn="section-appendix.b-3">
The IAB members at the time the initial RFC Editor model was approved The IAB members at the time the initial RFC Editor model (Version 1, RFC 5
620) was approved
were (in alphabetical order): were (in alphabetical order):
Loa Andersson, <contact fullname="Loa Andersson"/>,
Gonzalo Camarillo, <contact fullname="Gonzalo Camarillo"/>,
Stuart Cheshire, <contact fullname="Stuart Cheshire"/>,
Russ Housley, <contact fullname="Russ Housley"/>,
Olaf Kolkman, <contact fullname="Olaf Kolkman"/>,
Gregory Lebovitz, <contact fullname="Gregory Lebovitz"/>,
Barry Leiba, <contact fullname="Barry Leiba"/>,
Kurtis Lindqvist, <contact fullname="Kurtis Lindqvist"/>,
Andrew Malis, <contact fullname="Andrew Malis"/>,
Danny McPherson, <contact fullname="Danny McPherson"/>,
David Oran, <contact fullname="David Oran"/>,
Dave Thaler, and <contact fullname="Dave Thaler"/>, and
Lixia Zhang. <contact fullname="Lixia Zhang"/>.
In addition, the IAB included two ex officio members: Dow Street, who In addition, the IAB included two ex officio members: <contact fullname="D
was serving as the IAB Executive Director, and Aaron Falk, who was ow Street"/>, who
was serving as the IAB Executive Director, and <contact fullname="Aaron Fa
lk"/>, who was
serving as the IRTF Chair. serving as the IRTF Chair.
</t> </t>
<t> <t pn="section-appendix.b-4">
The IAB members at the time the this RFC was approved were (in alphabetica The IAB members at the time RFC 6635 was approved were (in alphabetical or
l order): der):
Bernard Aboba, <contact fullname="Bernard Aboba"/>,
Ross Callon, <contact fullname="Ross Callon"/>,
Alissa Cooper, <contact fullname="Alissa Cooper"/>,
Spencer Dawkins, <contact fullname="Spencer Dawkins"/>,
Joel Halpern, <contact fullname="Joel Halpern"/>,
Russ Housley, <contact fullname="Russ Housley"/>,
David Kessens, <contact fullname="David Kessens"/>,
Olaf Kolkman, <contact fullname="Olaf Kolkman"/>,
Danny McPherson, <contact fullname="Danny McPherson"/>,
Jon Peterson, <contact fullname="Jon Peterson"/>,
Andrei Robachevsky, <contact fullname="Andrei Robachevsky"/>,
Dave Thaler, and <contact fullname="Dave Thaler"/>, and
Hannes Tschofenig. <contact fullname="Hannes Tschofenig"/>.
In addition, at the time of approval, the IAB included two ex officio
members: Mary Barnes who was serving as the IAB Executive Director,
and Lars Eggert, who was serving as the IRTF Chair.
</t>
<t>Bob Hinden served as documented editor for this version of this document
that aligned it with the IASA 2.0 model.</t>
</section>
<section anchor="changes" title="Change log [RFC Editor: Please remove]">
<t><list>
<t>draft-ietf-iasa2-rfc6635bis-04, 2019-October-4</t>
<?rfc subcompact="yes" ?>
<t><list style="symbols">
<t>Changes relating to issues reaised during last call. Includes
changing conflict of interest text to point to LLC conflict
interest policy, and several editorial clarifications and
corrections. </t>
</list></t>
<?rfc subcompact="no" ?>
<t>draft-ietf-iasa2-rfc6635bis-03, 2019-January-7</t>
<?rfc subcompact="yes" ?>
<t><list style="symbols">
<t>Removed IAB as an author to follow current model for IAB
stream documents.</t>
<t>Added note to Abstract that the IAB (to be removed by the RFC
Editor), that the IAB is requested to publish this document as a
replacement for RFC 6635. </t>
<t>Editorial Changes.</t>
</list></t>
<?rfc subcompact="no" ?>
<t>draft-ietf-iasa2-rfc6635bis-02, 2019-January-3</t>
<?rfc subcompact="yes" ?>
<t><list style="symbols">
<t>Changed references to point to current IASA 2.0 structure
document <xref target="I-D.ietf-iasa2-rfc4071bis"/></t>
</list></t>
<?rfc subcompact="no" ?>
<t>draft-ietf-iasa2-rfc6635bis-01, 2018-August-23</t>
<?rfc subcompact="yes" ?>
<t><list style="symbols">
<t>Changed to Obsolete RFC6635 from Update.</t>
<t>Changed remaining occurrences of Board.</t>
<t>Changed IETF Administration Limited
Liability Corporation to IETF Administration Limited
Liability Company.</t>
<t>Editorial Changes.</t>
</list></t>
<?rfc subcompact="no" ?>
<t>draft-ietf-iasa2-rfc6635bis-00, 2018-August-22</t>
<?rfc subcompact="yes" ?>
<t><list style="symbols">
<t>Working Group draft.</t>
<t>Removed remaining references to RFC4071.</t>
<t>Changed most occurrences of LLC Board to LLC.</t>
<t>Editorial Changes.</t>
</list></t>
<?rfc subcompact="no" ?>
<t>draft-hinden-iasa2-rfc6635bis-01, 2018-August-6</t>
<?rfc subcompact="yes" ?>
<t><list style="symbols">
<t>Changed occurrences of IASA to IETF Administration Limited
Liability Corporation ("LLC").</t>
<t>Changed occurrences of IAOC to LLC Board.</t>
<t>Changed occurrences of IAD to LLC Executive Director.</t>
<t>Added paragraph to introduction about purpose of this version
of the document, and updated Abstract similarly.</t>
<t>Added new editor to acknowledgement section.</t>
<t>Changed document to now oboslete RFC6635.</t>
</list></t>
<?rfc subcompact="no" ?>
<t>draft-hinden-iasa2-rfc6635bis-00, 2018-August-6</t>
<?rfc subcompact="no" ?>
<?rfc subcompact="yes" ?>
<t><list style="symbols">
<t>Original version with only changes from RFC6635 were to convert
to ID format.</t>
</list></t>
</list></t>
<?rfc subcompact="no" ?>
</section>
</middle>
<back>
<references title='Normative References'>
<?rfc include="reference.RFC.4844"?>
<?rfc include="reference.RFC.2850"?>
<?rfc include="reference.RFC.6635"?>
<?rfc include="reference.I-D.ietf-iasa2-rfc4071bis.xml"?>
</references>
<references title='Informative References'>
<?rfc include="reference.RFC.5620"?>
<?rfc include="reference.RFC.3777"?>
</references>
</back>
In addition, at the time of approval of RFC 6635, the IAB included two ex of
ficio
members: <contact fullname="Mary Barnes"/> who was serving as the IAB Execut
ive Director,
and <contact fullname="Lars Eggert"/>, who was serving as the IRTF Chair.
</t>
<t pn="section-appendix.b-5"><contact fullname="Bob Hinden"/> served as do
cument editor for this RFC to
align it with the IASA 2.0 structure.</t>
</section>
<section anchor="authors-addresses" numbered="false" removeInRFC="false" toc
="include" pn="section-appendix.c">
<name slugifiedName="name-authors-addresses">Authors' Addresses</name>
<author initials="O." surname="Kolkman" fullname="Olaf Kolkman" role="edit
or">
<organization showOnFrontPage="true">Internet Society</organization>
<address>
<email>kolkman@isoc.org</email>
</address>
</author>
<author initials="J." surname="Halpern" fullname="Joel M. Halpern" role="e
ditor">
<organization showOnFrontPage="true">Ericsson</organization>
<address>
<email>joel.halpern@ericsson.com</email>
</address>
</author>
<author fullname="Robert M. Hinden" initials="R." surname="Hinden" role="e
ditor">
<organization showOnFrontPage="true">Check Point Software</organization>
<address>
<postal>
<street>959 Skyway Road</street>
<city>San Carlos</city>
<region>CA</region>
<code>94070</code>
<country>USA</country>
</postal>
<phone/>
<email>bob.hinden@gmail.com</email>
</address>
</author>
</section>
</back>
</rfc> </rfc>
 End of changes. 133 change blocks. 
871 lines changed or deleted 1250 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/