rfc9280.original.xml   rfc9280.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.6.2 (Ruby 2 .7.0) --> <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.6.2 (Ruby 2 .7.0) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
-iab-rfcefdp-rfced-model-13" category="info" obsoletes="8728" updates="7841, 872 <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
9, 8730" tocInclude="true" sortRefs="true" symRefs="true" version="3"> -iab-rfcefdp-rfced-model-13" number="9280" submissionType="IAB" category="info"
<!-- xml2rfc v2v3 conversion 3.12.3 --> consensus="true" xml:lang="en" obsoletes="8728" updates="7841, 8729, 8730" tocIn
clude="true" sortRefs="false" symRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 3.12.3 -->
<front> <front>
<title abbrev="RFC Editor Model">RFC Editor Model (Version 3)</title> <title abbrev="RFC Editor Model">RFC Editor Model (Version 3)</title>
<seriesInfo name="Internet-Draft" value="draft-iab-rfcefdp-rfced-model-13"/> <seriesInfo name="RFC" value="9280"/>
<author initials="P." surname="Saint-Andre" fullname="Peter Saint-Andre" rol e="editor"> <author initials="P." surname="Saint-Andre" fullname="Peter Saint-Andre" rol e="editor">
<organization/> <organization/>
<address> <address>
<email>stpeter@stpeter.im</email> <email>stpeter@stpeter.im</email>
</address> </address>
</author> </author>
<date year="2022" month="March" day="16"/> <date year="2022" month="June" />
<area>Internet</area>
<keyword>Internet-Draft</keyword>
<abstract> <abstract>
<t>This document specifies version 3 of the RFC Editor Model. The Model <t>This document specifies version 3 of the RFC Editor Model. The model
defines two high-level tasks related to the RFC Series. First, policy defines two high-level tasks related to the RFC Series. First, policy
definition is the joint responsibility of the RFC Series Working Group definition is the joint responsibility of the RFC Series Working Group
(RSWG), which produces policy proposals, and the RFC Series Approval (RSWG), which produces policy proposals, and the RFC Series Approval
Board (RSAB), which approves such proposals. Second, policy Board (RSAB), which approves such proposals. Second, policy
implementation is primarily the responsibility of the RFC Production implementation is primarily the responsibility of the RFC Production
Center (RPC) as contractually overseen by the IETF Administration Center (RPC) as contractually overseen by the IETF Administration
Limited Liability Company (IETF LLC). In addition, various Limited Liability Company (IETF LLC). In addition, various
responsibilities of the "RFC Editor Function" are now performed alone responsibilities of the RFC Editor function are now performed alone
or in combination by the RSWG, RSAB, RPC, RFC Series Consulting Editor or in combination by the RSWG, RSAB, RPC, RFC Series Consulting Editor
(RSCE), and IETF LLC. Finally, this document establishes the Editorial (RSCE), and IETF LLC. Finally, this document establishes the Editorial
Stream for publication of future policy definition documents produced Stream for publication of future policy definition documents produced
through the processes defined herein.</t> through the processes defined herein.</t>
<t>This document obsoletes RFC 8728. This document updates RFC 7841, <t>This document obsoletes RFC 8728. This document updates RFCs 7841,
RFC 8729, and RFC 8730.</t> 8729, and 8730.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="introduction"> <section anchor="introduction">
<name>Introduction</name> <name>Introduction</name>
<t>The Request for Comments (RFC) Series is the archival series <t>The Request for Comments (RFC) Series is the archival series
dedicated to documenting Internet technical specifications, dedicated to documenting Internet technical specifications,
including general contributions from the Internet research and including general contributions from the Internet research and
engineering community as well as standards documents. RFCs are engineering community as well as standards documents. RFCs are
available free of charge to anyone via the Internet. As described available free of charge to anyone via the Internet. As described
in <xref target="RFC8700"/>, RFCs have been published continually since 1969.</t > in <xref target="RFC8700"/>, RFCs have been published continually since 1969.</t >
<t>RFCs are generated and approved by multiple document streams. <t>RFCs are generated and approved by multiple document streams.
Whereas the stream approving body <xref target="RFC8729"/> for each stream is Whereas the stream approving body <xref target="RFC8729"/> for each stream is
responsible for the content of that stream, the RFC Editor Function responsible for the content of that stream, the RFC Editor function
is responsible for the production and distribution of all RFCs. is responsible for the production and distribution of all RFCs.
The four existing streams are described in <xref target="RFC8729"/>. This The four existing streams are described in <xref target="RFC8729"/>. This
document adds a fifth stream, the Editorial Stream, for publication document adds a fifth stream, the Editorial Stream, for publication
of policies governing the RFC Series as a whole.</t> of policies governing the RFC Series as a whole.</t>
<t>The overall framework for the RFC Series and the RFC Editor <t>The overall framework for the RFC Series and the RFC Editor
Function is described in <xref target="RFC8729"/> and is updated by this function is described in <xref target="RFC8729"/> and is updated by this
document, which defines version 3 of the RFC Editor Model. document, which defines version 3 of the RFC Editor Model.
Under this version, various responsibilities of the RFC Editor Under this version, various responsibilities of the RFC Editor
Function are performed alone or in combination by the RFC Series function are performed alone or in combination by the RFC Series
Working Group (RSWG), RFC Series Advisory Board (RSAB), RFC Working Group (RSWG), RFC Series Advisory Board (RSAB), RFC
Production Center (RPC), RFC Series Consulting Editor (RSCE), and Production Center (RPC), RFC Series Consulting Editor (RSCE), and
IETF Administration Limited Liability Company (IETF LLC) <xref target="RFC8711"/ >, IETF Administration Limited Liability Company (IETF LLC) <xref target="RFC8711"/ >,
which collectively comprise the RFC Editor Function. The intent which collectively comprise the RFC Editor function. The intent
is to ensure sustainable maintenance and support of the RFC Series is to ensure sustainable maintenance and support of the RFC Series
based on the principles of expert implementation, clear management based on the principles of expert implementation, clear management
and direction, and appropriate community input <xref target="RFC8729"/>.</t> and direction, and appropriate community input <xref target="RFC8729"/>.</t>
<t>This document obsoletes <xref target="RFC8728"/> by defining version 3 <t>This document obsoletes <xref target="RFC8728"/> by defining version 3
of the RFC Editor Model. This document updates <xref target="RFC7841"/> of the RFC Editor Model. This document updates <xref target="RFC7841"/>
by defining boilerplate text for the Editorial Stream. This by defining boilerplate text for the Editorial Stream. This
document updates <xref target="RFC8729"/> by replacing the RFC Editor role document updates <xref target="RFC8729"/> by replacing the RFC Editor role
with the RSWG, RSAB, and RSCE. This document updates <xref target="RFC8730"/> with the RSWG, RSAB, and RSCE. This document updates <xref target="RFC8730"/>
by removing the dependency on certain policies specified by the by removing the dependency on certain policies specified by the
IAB and RFC Series Editor (RSE). More detailed information about changes from IAB and RFC Series Editor (RSE). More detailed information about changes from
version 2 of the Model can be found under <xref target="changes"/>.</t> version 2 of the RFC Editor Model can be found in <xref target="changes"/>.</t>
</section> </section>
<section anchor="overview-of-the-model"> <section anchor="overview-of-the-model">
<name>Overview of the Model</name> <name>Overview of the Model</name>
<t>This document divides the responsibilities for the RFC Series <t>This document divides the responsibilities for the RFC Series
into two high-level tasks:</t> into two high-level tasks:</t>
<ol spacing="normal" type="1"><li>Policy definition governing the Series a s a whole. This is <ol spacing="normal" type="1"><li>Policy definition governing the RFC Seri es as a whole. This is
the joint responsibility of two entities. First, the RFC Series Working the joint responsibility of two entities. First, the RFC Series Working
Group (RSWG) is an open working group independent of the IETF that Group (RSWG) is an open working group independent of the IETF that
generates policy proposals. Second, the RFC Series Approval Board (RSAB) generates policy proposals. Second, the RFC Series Approval Board (RSAB)
is an appointed body that approves such proposals for publication is an appointed body that approves such proposals for publication
in the Editorial Stream. The RSAB includes representatives of the in the Editorial Stream. The RSAB includes representatives of the
streams <xref target="RFC8729"/> as well as an expert in technical publishing, streams <xref target="RFC8729"/> as well as an expert in technical publishing,
the RFC Series Consulting Editor (RSCE).</li> the RFC Series Consulting Editor (RSCE).</li>
<li>Policy implementation through publication of RFCs in all of the <li>Policy implementation through publication of RFCs in all of the
streams that form the Series. This is primarily the responsibility streams that form the RFC Series. This is primarily the responsibility
of the RFC Production Center (RPC) as contractually overseen by the of the RFC Production Center (RPC) as contractually overseen by the
IETF Administration Limited Liability Company (IETF LLC) <xref target="RFC8711"/ >.</li> IETF Administration Limited Liability Company (IETF LLC) <xref target="RFC8711"/ >.</li>
</ol> </ol>
<t>As described more fully in the remainder of this document, the core <t>As described more fully in the remainder of this document, the core
activities and responsibilities are as follows:</t> activities and responsibilities are as follows:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>The RSWG proposes policies that govern the RFC Series as a whole, wi th <li>The RSWG proposes policies that govern the RFC Series as a whole, wi th
input from the community, the RSAB, and the RSCE.</li> input from the community, the RSAB, and the RSCE.</li>
<li>The RSAB considers those proposals and either approves them or retur ns <li>The RSAB considers those proposals and either approves them or retur ns
them to the RSWG, which may make further changes or remove them from them to the RSWG, which may make further changes or remove them from
skipping to change at line 119 skipping to change at line 122
raising issues or initiating proposed policy changes within the RSWG.</li> raising issues or initiating proposed policy changes within the RSWG.</li>
<li>The RPC implements the policies defined by the Editorial Stream in i ts <li>The RPC implements the policies defined by the Editorial Stream in i ts
day-to-day editing and publication of RFCs from all of the streams.</li> day-to-day editing and publication of RFCs from all of the streams.</li>
<li>If issues arise with the implementation of particular policies, the RPC <li>If issues arise with the implementation of particular policies, the RPC
brings those issues to the RSAB, which interprets the policies and provides brings those issues to the RSAB, which interprets the policies and provides
interim guidance to the RPC, informing the RSWG of those interpretations.</li> interim guidance to the RPC, informing the RSWG of those interpretations.</li>
</ul> </ul>
<t>This model is designed to ensure public processes and policy documents, <t>This model is designed to ensure public processes and policy documents,
clear lines of responsibility and authority, transparent mechanisms for updates and changes to policies clear lines of responsibility and authority, transparent mechanisms for updates and changes to policies
governing the RFC Series as a whole, and effective operational implementation of the governing the RFC Series as a whole, and effective operational implementation of the
RFC Series, thus meeting the requirements specified in Section 4 of <xref target ="RFC8729"/>.</t> RFC Series, thus meeting the requirements specified in <xref target="RFC8729" se ctionFormat="of" section="4"/>.</t>
<t>The remainder of this document describes the model in greater detail.</ t> <t>The remainder of this document describes the model in greater detail.</ t>
</section> </section>
<section anchor="policy-definition"> <section anchor="policy-definition">
<name>Policy Definition</name> <name>Policy Definition</name>
<t>Policies governing the RFC Series as a whole are defined through the <t>Policies governing the RFC Series as a whole are defined through the
following high-level process:</t> following high-level process:</t>
<ol spacing="normal" type="1"><li>Proposals must be submitted to, adopted by, and discussed within the RFC <ol spacing="normal" type="1"><li>Proposals must be submitted to, adopted by, and discussed within the RFC
Series Working Group (RSWG).</li> Series Working Group (RSWG).</li>
<li>Proposals must pass a last call for comments in the working group an d <li>Proposals must pass a Last Call for comments in the working group an d
a community call for comments (see <xref target="cfc"/>).</li> a community call for comments (see <xref target="cfc"/>).</li>
<li>Proposals must be approved by the RFC Series Approval Board (RSAB).< /li> <li>Proposals must be approved by the RFC Series Approval Board (RSAB).< /li>
</ol> </ol>
<t>Policies under the purview of the RSWG and RSAB might include, but are <t>Policies under the purview of the RSWG and RSAB might include, but are
not limited to, document formats, processes for publication and not limited to, document formats, processes for publication and
dissemination of RFCs, and overall management of the RFC Series.</t> dissemination of RFCs, and overall management of the RFC Series.</t>
<section anchor="structure-and-roles"> <section anchor="structure-and-roles">
<name>Structure and Roles</name> <name>Structure and Roles</name>
<section anchor="wg"> <section anchor="wg">
<name>RFC Series Working Group (RSWG)</name> <name>RFC Series Working Group (RSWG)</name>
<section anchor="purpose"> <section anchor="purpose">
<name>Purpose</name> <name>Purpose</name>
<t>The RFC Series Working Group (RSWG) is the primary venue in which <t>The RFC Series Working Group (RSWG) is the primary venue in which
members of the community collaborate regarding the policies that members of the community collaborate regarding the policies that
govern the RFC Series.</t> govern the RFC Series.</t>
</section> </section>
<section anchor="participation"> <section anchor="participation">
<name>Participation</name> <name>Participation</name>
<t>All interested individuals are welcome to participate in the RSWG <t>All interested individuals are welcome to participate in the RSWG;
(subject to anti-harassment policies as described under <xref target="coc"/>). participants are subject to anti-harassment policies as described in <xref
This includes but is not limited to participants in the IETF and target="coc"/>. This includes but is not limited to participants in the IETF
IRTF, members of the IAB and IESG, developers of software or hardware and IRTF, members of the IAB and IESG, developers of software or hardware
systems that implement RFCs, authors of RFCs and Internet-Drafts, systems that implement RFCs, authors of RFCs and Internet-Drafts, developers
developers of tools used to author or edit RFCs, individuals who of tools used to author or edit RFCs and Internet-Drafts, individuals who use
use RFCs in procurement decisions, scholarly researchers, and RFCs in procurement decisions, scholarly researchers, and representatives of
representatives of standards development organizations other than standards development organizations other than the IETF and IRTF. The IETF LLC
the IETF and IRTF. The IETF LLC Board members, staff and contractors Board members, staff and contractors (especially representatives of the RFC
(especially representatives of the RFC Production Center), and the Production Center), and the IETF Executive Director are invited to participate
IETF Executive Director are invited to participate as community as community members in the RSWG to the extent permitted by any relevant IETF
members in the RSWG to the extent permitted by any relevant IETF LLC LLC policies. Members of the RSAB are also expected to participate
policies. Members of the RSAB are also expected to participate
actively.</t> actively.</t>
</section> </section>
<section anchor="chairs"> <section anchor="chairs">
<name>Chairs</name> <name>Chairs</name>
<t>The RSWG shall have two chairs, one appointed by the IESG and the <t>The RSWG shall have two chairs, one appointed by the IESG and the
other appointed by the IAB. When the RSWG is formed, the chair other appointed by the IAB. When the RSWG is formed, the chair
appointed by the IESG shall serve for a term of one (1) year and appointed by the IESG shall serve for a term of one (1) year and
the chair appointed by the IAB shall serve for a term of two (2) the chair appointed by the IAB shall serve for a term of two (2)
years; thereafter, chairs shall serve for a term of two (2) years; thereafter, chairs shall serve for a term of two (2)
years, with no term limits on renewal. The IESG and IAB shall years, with no term limits on renewal. The IESG and IAB shall
determine their own processes for making these appointments, making determine their own processes for making these appointments, making
sure to take account of any potential conflicts of interest. sure to take account of any potential conflicts of interest.
Community members who have concerns about the performance of an Community members who have concerns about the performance of an
RSWG chair should direct their feedback to the appropriate appointing RSWG Chair should direct their feedback to the appropriate appointing
body via mechanisms such bodies shall specify at the time that the body via mechanisms such bodies shall specify at the time that the
RSWG is formed. The IESG and IAB shall have the power to remove their RSWG is formed. The IESG and IAB shall have the power to remove their
appointed chairs at their discretion at any time, and to name a appointed chairs at their discretion at any time and to name a
replacement who shall serve the remainder of the original chair's replacement who shall serve the remainder of the original chair's
term.</t> term.</t>
<t>It is the responsibility of the chairs to encourage rough consens us <t>It is the responsibility of the chairs to encourage rough consens us
within the RSWG and to follow that consensus in their decision making, within the RSWG and to follow that consensus in their decision making,
for instance regarding acceptance of new proposals and advancement of for instance, regarding acceptance of new proposals and advancement of
proposals to the RSAB.</t> proposals to the RSAB.</t>
</section> </section>
<section anchor="mode-of-operation"> <section anchor="mode-of-operation">
<name>Mode of Operation</name> <name>Mode of Operation</name>
<t>The intent is that the RSWG shall operate in a way similar to tha t of working <t>The intent is that the RSWG shall operate in a way similar to tha t of working
groups in the IETF. Therefore, all groups in the IETF. Therefore, all
RSWG meetings and discussion venues shall be open to all interested RSWG meetings and discussion venues shall be open to all interested
individuals, and all RSWG contributions shall be subject to intellectual individuals, and all RSWG contributions shall be subject to intellectual
property policies, which must be consistent with those of the IETF as property policies, which must be consistent with those of the IETF as
specified in <xref target="BCP78"/> and <xref target="BCP79"/>.</t> specified in <xref target="BCP78"/> and <xref target="BCP79"/>.</t>
skipping to change at line 208 skipping to change at line 210
provides a reasonable baseline. In-person meetings should include provides a reasonable baseline. In-person meetings should include
provision for effective online participation for those unable to provision for effective online participation for those unable to
attend in person.</t> attend in person.</t>
<t>The RSWG shall operate by rough consensus, a mode of operation <t>The RSWG shall operate by rough consensus, a mode of operation
informally described in <xref target="RFC2418"/>.</t> informally described in <xref target="RFC2418"/>.</t>
<t>The RSWG may decide by rough consensus to use additional tooling <t>The RSWG may decide by rough consensus to use additional tooling
(e.g., GitHub as specified in <xref target="RFC8874"/>), forms of communication, (e.g., GitHub as specified in <xref target="RFC8874"/>), forms of communication,
and working methods (e.g., design teams) as long as they are consistent and working methods (e.g., design teams) as long as they are consistent
with this document and with <xref target="RFC2418"/> or its successors.</t> with this document and with <xref target="RFC2418"/> or its successors.</t>
<t>Absent specific guidance in this document regarding the operation <t>Absent specific guidance in this document regarding the operation
of the RSWG, the general guidance provided in Section 6 of <xref target="RFC2418 "/> of the RSWG, the general guidance provided in <xref target="RFC2418" sectionForm at="of" section="6"/>
should be considered appropriate.</t> should be considered appropriate.</t>
<t>The IETF LLC is requested to provide necessary tooling to support <t>The IETF LLC is requested to provide necessary tooling to support
RSWG communication, decision processes, and policies.</t> RSWG communication, decision processes, and policies.</t>
<t>The IAB is requested to convene the RSWG when it is first formed in <t>The IAB is requested to convene the RSWG when it is first formed in
order to formalize the IAB's transfer of authority over the RFC Editor order to formalize the IAB's transfer of authority over the RFC Editor
Model.</t> Model.</t>
</section> </section>
</section> </section>
<section anchor="rfc-series-approval-board-rsab"> <section anchor="rfc-series-approval-board-rsab">
<name>RFC Series Approval Board (RSAB)</name> <name>RFC Series Approval Board (RSAB)</name>
<section anchor="purpose-1"> <section anchor="purpose-1">
<name>Purpose</name> <name>Purpose</name>
<t>The RFC Series Approval Board (RSAB), which includes representati ves <t>The RFC Series Approval Board (RSAB), which includes representati ves
of all of the streams, shall act as the approving body for proposals of all of the streams, shall act as the approving body for proposals
generated within the RSWG, thus providing an appropriate set of "checks generated within the RSWG, thus providing an appropriate set of checks
and balances" on the output of the RSWG. The only policy-making role and balances on the output of the RSWG. The only policy-making role
of the RSAB is to review policy proposals generated by the RSWG; it shall of the RSAB is to review policy proposals generated by the RSWG; it shall
have no independent authority to formulate policy on its own. It is have no independent authority to formulate policy on its own. It is
expected that the RSAB will respect the rough consensus of the expected that the RSAB will respect the rough consensus of the
RSWG wherever possible, without ceding its responsibility to RSWG wherever possible, without ceding its responsibility to
review RSWG proposals as further described under <xref target="workflow"/>.</t> review RSWG proposals, as further described in <xref target="workflow"/>.</t>
</section> </section>
<section anchor="members"> <section anchor="members">
<name>Members</name> <name>Members</name>
<t>The RSAB consists primarily of the following voting members:</t> <t>The RSAB consists primarily of the following voting members:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>As the stream representative for the IETF stream, an IESG memb <li>A stream representative for the IETF Stream: either an IESG me
er mber
or other person appointed by the IESG</li> or someone appointed by the IESG</li>
<li>As the stream representative for the IAB stream, an IAB member <li>A stream representative for the IAB Stream: either an IAB memb
or other person appointed by the IAB</li> er
<li>As the stream representative for the IRTF stream, the IRTF cha or someone appointed by the IAB</li>
ir <li>A stream representative for the IRTF Stream: either the IRTF C
or other person appointed by the IRTF Chair</li> hair
<li>As the stream representative for the Independent stream, the or someone appointed by the IRTF Chair</li>
Independent Submissions Editor (ISE) <xref target="RFC8730"/> or other person <li>A stream representative for the Independent Stream: either the
Independent Submissions Editor (ISE) <xref target="RFC8730"/> or someone
appointed by the ISE</li> appointed by the ISE</li>
<li>The RFC Series Consulting Editor (RSCE)</li> <li>The RFC Series Consulting Editor (RSCE)</li>
</ul> </ul>
<t>If and when a new stream is created, the document that <t>If and when a new stream is created, the document that
creates the stream shall specify if a voting member representing creates the stream shall specify if a voting member representing
that stream shall also be added to the RSAB, along with any rules that stream shall also be added to the RSAB, along with any rules
and processes related to that representative (e.g., whether the and processes related to that representative (e.g., whether the
representative is a member of the body responsible for the stream representative is a member of the body responsible for the stream
or an appointed delegate thereof).</t> or an appointed delegate thereof).</t>
<t>The RFC Series Consulting Editor (RSCE) is a voting member of the <t>The RFC Series Consulting Editor (RSCE) is a voting member of the
RSAB but does not act as a representative of the Editorial Stream.</t> RSAB but does not act as a representative of the Editorial Stream.</t>
<t>To ensure the smooth operation of the RFC Series, the RSAB shall <t>To ensure the smooth operation of the RFC Series, the RSAB shall
include the following non-voting, ex-officio members:</t> include the following non-voting, ex officio members:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>The IETF Executive Director or their delegate; the rationale i s <li>The IETF Executive Director or their delegate (the rationale i s
that the IETF LLC is accountable for implementation of policies that the IETF LLC is accountable for implementation of policies
governing the RFC Series</li> governing the RFC Series)</li>
<li>A representative of the RPC, named by the RPC; the rationale <li>A representative of the RPC, named by the RPC (the rationale
is that the RPC is responsible for implementation of policies is that the RPC is responsible for implementation of policies
governing the RFC Series</li> governing the RFC Series)</li>
</ul> </ul>
<t>In addition to the foregoing, the RSAB may at its discretion incl <t>In addition, the RSAB may include
ude other non-voting members at its discretion; these non-voting members may be ex o
other non-voting members, whether ex-officio members or liaisons from fficio members or liaisons from
groups or organizations with which the RSAB deems it necessary to groups or organizations with which the RSAB deems it necessary to
formally collaborate or coordinate.</t> formally collaborate or coordinate.</t>
</section> </section>
<section anchor="appointment-and-removal-of-voting-members"> <section anchor="appointment-and-removal-of-voting-members">
<name>Appointment and Removal of Voting Members</name> <name>Appointment and Removal of Voting Members</name>
<t>The appointing bodies, i.e., the stream approving bodies (IESG, I <t>The appointing bodies (i.e., IESG, IAB,
AB, IRTF Chair, and ISE) shall determine their own processes for
IRTF chair, and ISE), shall determine their own processes for
appointing RSAB members (note that processes related to the RSCE appointing RSAB members (note that processes related to the RSCE
are described under <xref target="rsce"/>). Each appointing body shall have the power are described in <xref target="rsce"/>). Each appointing body shall have the pow er
to remove its appointed RSAB member at its discretion at any time. to remove its appointed RSAB member at its discretion at any time.
Appointing bodies should ensure that voting members are seated at Appointing bodies should ensure that voting members are seated at
all times and should fill any vacancies with all due speed, if all times and should fill any vacancies with all due speed, if
necessary on a temporary basis.</t> necessary on a temporary basis.</t>
<t>In the case that the IRTF chair or ISE is incapacitated or otherw ise <t>In the case that the IRTF Chair or ISE is incapacitated or otherw ise
unable to appoint another person to serve as a delegate, unable to appoint another person to serve as a delegate,
the IAB (as the appointing body for the IRTF chair and ISE) the IAB (as the appointing body for the IRTF Chair and ISE)
shall act as the temporary appointing body for those shall act as the temporary appointing body for those
streams and shall appoint a temporary member of the RSAB until the streams and shall appoint a temporary member of the RSAB until the
IAB has appointed an IRTF chair or ISE, who can then act as an IAB has appointed an IRTF Chair or ISE, who can then act as an
RSAB member or appoint a delegate through normal processes.</t> RSAB member or appoint a delegate through normal processes.</t>
</section> </section>
<section anchor="vacancies"> <section anchor="vacancies">
<name>Vacancies</name> <name>Vacancies</name>
<t>In the case of vacancies by voting members, the RSAB shall operat e <t>In the case of vacancies by voting members, the RSAB shall operat e
as follows:</t> as follows:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>Activities related to implementation of policies already in fo rce <li>Activities related to implementation of policies already in fo rce
shall continue as normal.</li> shall continue as normal.</li>
<li>Voting on approval of policy documents produced by the RSWG sh <li>Voting on approval of policy documents produced by the RSWG shall be
all delayed until the vacancy or vacancies have been filled, up to a maximum of
be delayed until the vacancy or vacancies have been filled, up to a three (3) months. If a further vacancy arises during this three-month period, th
maximum of 3 months. If during this 3-month period a further vacancy e
arises, the delay should be extended by up to another 3 months. delay should be extended by up to another three months. After the delay
After the delay period expires, the RSAB should continue to process period expires, the RSAB should continue to process documents as described
documents as described below. Note: this method of handling vacancies below. Note that this method of handling vacancies does not apply to a vacancy
does not apply to a vacancy of the RSCE role, only of the stream of the RSCE role; it only applies to vacancies of the stream representatives
representatives enumerated above.</li> enumerated in <xref target="members"/>.
</li>
</ul> </ul>
</section> </section>
<section anchor="chair"> <section anchor="chair">
<name>Chair</name> <name>Chair</name>
<t>The RSAB shall annually choose a chair from among its members usi ng <t>The RSAB shall annually choose a chair from among its members usi ng
a method of its choosing. If the chair position is a method of its choosing. If the chair position is
vacated during the chair's term, the RSAB chooses a new chair vacated during the chair's term, the RSAB chooses a new chair
from among its members.</t> from among its members.</t>
</section> </section>
<section anchor="mode-of-operation-1"> <section anchor="mode-of-operation-1">
<name>Mode of Operation</name> <name>Mode of Operation</name>
<t>The RSAB is expected to operate via an email discussion list, <t>The RSAB is expected to operate via an email discussion list,
in-person meetings, teleconferencing systems, and any additional in-person meetings, teleconferencing systems, and any additional
tooling it deems necessary.</t> tooling it deems necessary.</t>
<t>The RSAB shall keep a public record of its proceedings, including <t>The RSAB shall keep a public record of its proceedings, including
minutes of all meetings and a record of all decisions. The primary minutes of all meetings and a record of all decisions. The primary
email discussion list used by the RSAB shall be publicly archived, email discussion list used by the RSAB shall be publicly archived,
although topics that require confidentiality (e.g., personnel although topics that require confidentiality (e.g., personnel
matters) may be omitted from such archives or discussed in private. matters) may be omitted from such archives or discussed in private.
Similarly, meeting minutes may exclude detailed information about Similarly, meeting minutes may exclude detailed information about
topics discussed under executive session, but should note that such topics discussed under executive session but should note that such
topics were discussed.</t> topics were discussed.</t>
<t>The RSAB shall announce plans and agendas for their meetings on t he <t>The RSAB shall announce plans and agendas for their meetings on t he
RFC Editor website and by email to the RSWG at least a week before RFC Editor website and by email to the RSWG at least a week before
such meetings. The meetings shall be open for public attendance and such meetings. The meetings shall be open for public attendance, and
the RSAB may consider allowing open participation. If the RSAB needs the RSAB may consider allowing open participation. If the RSAB needs
to discuss a confidential matter in executive session, that part of to discuss a confidential matter in executive session, that part of
the meeting shall be private to the RSAB, but must be noted on the the meeting shall be private to the RSAB, but it must be noted on the
agenda, and must be documented in the minutes with as much detail as agenda and documented in the minutes with as much detail as
confidentiality requirements permit.</t> confidentiality requirements permit.</t>
<t>The IETF LLC is requested to provide necessary tooling and staff to support <t>The IETF LLC is requested to provide necessary tooling and staff to support
RSAB communication, decision processes, and policies.</t> RSAB communication, decision processes, and policies.</t>
<t>The IAB is requested to convene the RSAB when it is first formed in <t>The IAB is requested to convene the RSAB when it is first formed in
order to formalize the IAB's transfer of authority over the RFC Editor order to formalize the IAB's transfer of authority over the RFC Editor
Model.</t> Model.</t>
</section> </section>
</section> </section>
</section> </section>
<section anchor="process"> <section anchor="process">
<name>Process</name> <name>Process</name>
<t> This section specifies the RFC Series Policy Definition Process, whic h shall be followed in producing all Editorial Stream RFCs.</t>
<section anchor="intent"> <section anchor="intent">
<name>Intent</name> <name>Intent</name>
<t>The intent is to provide an open forum by which policies related to the <t>The intent is to provide an open forum by which policies related to the
RFC Series are defined and evolved. The general expectation is that all RFC Series are defined and evolved. The general expectation is that all
interested parties will participate in the RSWG, and that only under interested parties will participate in the RSWG and that only under
extreme circumstances should RSAB members need to hold "CONCERN" extreme circumstances should RSAB members need to hold CONCERN
positions (as described under <xref target="workflow"/>).</t> positions (as described in <xref target="workflow"/>).</t>
<t>Because policy issues can be difficult and contentious, RSWG <t>Because policy issues can be difficult and contentious, RSWG
participants and RSAB members are strongly encouraged to work together participants and RSAB members are strongly encouraged to work together
in a spirit of good faith and mutual understanding to achieve rough in a spirit of good faith and mutual understanding to achieve rough
consensus (see <xref target="RFC2418"/>). In particular, RSWG members are consensus (see <xref target="RFC2418"/>). In particular, RSWG members are
encouraged to take RSAB concerns seriously, and RSAB members are encouraged to take RSAB concerns seriously, and RSAB members are
encouraged to clearly express their concerns early in the process and encouraged to clearly express their concerns early in the process and
to be responsive to the community. All parties are encouraged to respect to be responsive to the community. All parties are encouraged to respect
the value of each stream and the long-term health and viability of the value of each stream and the long-term health and viability of
the RFC Series.</t> the RFC Series.</t>
<t>This process is intended to be one of continuous consultation. RSAB <t>This process is intended to be one of continuous consultation. RSAB
skipping to change at line 373 skipping to change at line 377
processes they deem appropriate to facilitate this goal.</t> processes they deem appropriate to facilitate this goal.</t>
</section> </section>
<section anchor="workflow"> <section anchor="workflow">
<name>Workflow</name> <name>Workflow</name>
<t>The following process shall be used to formulate or modify policies <t>The following process shall be used to formulate or modify policies
related to the RFC Series:</t> related to the RFC Series:</t>
<ol spacing="normal" type="1"><li>An individual or set of individuals generates a proposal in the form <ol spacing="normal" type="1"><li>An individual or set of individuals generates a proposal in the form
of an Internet-Draft (which must be submitted in full conformance of an Internet-Draft (which must be submitted in full conformance
with the provisions of <xref target="BCP78"/> and <xref target="BCP79"/>) with the provisions of <xref target="BCP78"/> and <xref target="BCP79"/>)
and asks the RSWG to adopt the proposal as a working group item.</li> and asks the RSWG to adopt the proposal as a working group item.</li>
<li>The RSWG may adopt the proposal as a draft proposal of the RSWG, if <li>The RSWG may adopt the proposal as a working group item if
the chairs determine (by following working group procedures for rough the chairs determine (by following working group procedures for rough
consensus) that there is sufficient interest in the proposal; this consensus) that there is sufficient interest in the proposal; this
is similar to the way a working group of the IETF would operate is similar to the way a working group of the IETF would operate
(see <xref target="RFC2418"/>).</li> (see <xref target="RFC2418"/>).</li>
<li>The RSWG shall then further discuss and develop the proposal. Al l <li>The RSWG shall then further discuss and develop the proposal. Al l
participants, but especially RSAB members, should pay special participants, but especially RSAB members, should pay special
attention to any aspects of the proposal that have the potential attention to any aspects of the proposal that have the potential
to significantly modify policies of long standing or historical to significantly modify long-standing policies or historical
characteristics of the Series as described under <xref target="properties"/>. characteristics of the RFC Series as described in <xref target="properties"/>.
Members of the RSAB are expected to participate as individuals in Members of the RSAB are expected to participate as individuals in
all discussions relating to RSWG proposals. This should help to all discussions relating to RSWG proposals. This should help to
ensure that they are fully aware of proposals early in the policy ensure that they are fully aware of proposals early in the
definition process. It should also help to ensure that RSAB members RFC Series Policy Definition Process. It should also help to ensure that RSAB me
mbers
will raise any issues or concerns during the development of the will raise any issues or concerns during the development of the
proposal, and not wait until the RSAB review period. The RSWG chairs proposal and not wait until the RSAB review period. The RSWG Chairs
are also expected to participate as individuals.</li> are also expected to participate as individuals.</li>
<li>At some point, if the RSWG chairs believe there may be rough <li>At some point, if the RSWG Chairs believe there may be rough
consensus for the proposal to advance, they will issue a last call consensus for the proposal to advance, they will issue a Last Call
for comments within the working group.</li> for comments within the working group.</li>
<li>After a comment period of suitable length, the RSWG chairs will <li>After a comment period of suitable length, the RSWG Chairs will
determine whether rough consensus for the proposal exists (taking determine whether rough consensus for the proposal exists (taking
their own feedback as individuals into account along with feedback their own feedback as individuals into account along with feedback
from other participants). If comments have been received and from other participants). If comments have been received and
substantial changes have been made, additional last calls may be substantial changes have been made, additional Last Calls may be
necessary. Once the chairs determine that consensus has been necessary. Once the chairs determine that consensus has been
reached, they shall announce their determination on the RSWG reached, they shall announce their determination on the RSWG
discussion list and forward the document to the RSAB.</li> email discussion list and forward the document to the RSAB.</li>
<li>Once consensus is established in the RSWG, the RSAB shall issue a <li>Once consensus is established in the RSWG, the RSAB shall issue a
community call for comments as further described under <xref target="cfc"/>. If community call for comments as further described in <xref target="cfc"/>. If
substantial comments are received in response to the community substantial comments are received in response to the community
call for comments, the RSAB may return the draft to the RSWG to call for comments, the RSAB may return the proposal to the RSWG to
consider those comments and make revisions to address the feedback consider those comments and make revisions to address the feedback
received. In parallel with the community call for comments, the RSAB received. In parallel with the community call for comments, the RSAB
itself shall also consider the proposal.</li> itself shall also consider the proposal.</li>
<li>If the scope of the revisions made in the previous step is subst antial, an <li>If the scope of the revisions made in the previous step is subst antial, an
additional community call for comments should be issued by the RSAB, additional community call for comments should be issued by the RSAB,
and the feedback received should be considered by the RSWG.</li> and the feedback received should be considered by the RSWG.</li>
<li>Once the RSWG chairs confirm that concerns received during the <li>Once the RSWG Chairs confirm that concerns received during the
community call(s) for comments have been addressed, they shall community call(s) for comments have been addressed, they shall
inform the RSAB that the document is ready for balloting by the inform the RSAB that the document is ready for balloting by the
RSAB.</li> RSAB.</li>
<li> <li>
<t>Within a reasonable period of time, the RSAB will then poll its members <t anchor="step9">Within a reasonable period of time, the RSAB wil l poll its members
for their positions on the proposal. Positions may be as follows: </t> for their positions on the proposal. Positions may be as follows: </t>
<ul spacing="normal"> <ul spacing="normal">
<li>"YES": the proposal should be approved</li> <li>YES: the proposal should be approved</li>
<li>"CONCERN": the proposal raises substantial concerns that mus <li>CONCERN: the proposal raises substantial concerns that must
t be be
addressed</li> addressed</li>
<li>"RECUSE": the person holding the position has a conflict of <li>RECUSE: the person holding the position has a conflict of
interest</li> interest</li>
</ul> </ul>
<t> <t>
Any RSAB member holding a "CONCERN" position must explain their concern Any RSAB member holding a CONCERN position must explain their concern
to the community in detail. Nevertheless, the RSWG might not be able to to the community in detail. Nevertheless, the RSWG might not be able to
come to consensus on modifications that will address the RSAB member's come to consensus on modifications that will address the RSAB member's
concern. </t> concern. </t>
<t> <t>
There are three reasons why an RSAB member may file a position of CONCERN: </t> There are three reasons why an RSAB member may file a position of CONCERN: </t>
<ul spacing="normal"> <ul spacing="normal">
<li>The RSAB member believes that the proposal represents a seri ous <li>The RSAB member believes that the proposal represents a seri ous
problem for one or more of the individual streams.</li> problem for one or more of the individual streams.</li>
<li>The RSAB member believes that the proposal would cause serio us harm <li>The RSAB member believes that the proposal would cause serio us harm
to the overall Series, including harm to the long-term health and to the overall RFC Series, including harm to the long-term health and
viability of the Series.</li> viability of the Series.</li>
<li>The RSAB member believes, based on the results of the commun ity <li>The RSAB member believes, based on the results of the commun ity
call(s) for comments <xref target="cfc"/>, that rough consensus to advance call(s) for comments (<xref target="cfc"/>), that rough consensus to advance
the proposal is lacking.</li> the proposal is lacking.</li>
</ul> </ul>
<t> <t>
Because RSAB members are expected to participate in the discussions Because RSAB members are expected to participate in the discussions
within the RSWG and to raise any concerns and issues during those within the RSWG and to raise any concerns and issues during those
discussions, most CONCERN positions should not come as a surprise to discussions, most CONCERN positions should not come as a surprise to
the RSWG. Notwithstanding, late CONCERN positions are always possible the RSWG. Notwithstanding, late CONCERN positions are always possible
if issues are identified during RSAB review or the community call(s) for comment s.</t> if issues are identified during RSAB review or the community call(s) for comment s.</t>
</li> </li>
<li>If a CONCERN exists, discussion will take place within the RSWG. <li>If a CONCERN exists, discussion will take place within the RSWG.
skipping to change at line 472 skipping to change at line 476
<li>Policies may take effect immediately upon approval by the RSAB a nd <li>Policies may take effect immediately upon approval by the RSAB a nd
before publication of the relevant RFC, unless they are delayed before publication of the relevant RFC, unless they are delayed
while the IETF LLC resolves pending resource or contract issues.</li> while the IETF LLC resolves pending resource or contract issues.</li>
</ol> </ol>
</section> </section>
<section anchor="cfc"> <section anchor="cfc">
<name>Community Calls for Comment</name> <name>Community Calls for Comment</name>
<t>The RSAB is responsible for initiating and managing community calls <t>The RSAB is responsible for initiating and managing community calls
for comments on proposals that have gained consensus within the RSWG. for comments on proposals that have gained consensus within the RSWG.
The RSAB should actively seek a wide range of input. The RSAB seeks The RSAB should actively seek a wide range of input. The RSAB seeks
such input by, at a minimum, sending a notice to the "rfc-interest" such input by, at a minimum, sending a notice to the <eref target="mailto:rfc-in
email list or to its successor or future equivalent. RSAB members terest@rfc-editor.org">rfc&nbhy;interest@rfc&nbhy;editor.org</eref>
email discussion list or to its successor or future equivalent. RSAB members
should also send a notice to the communities they directly represent should also send a notice to the communities they directly represent
(e.g., the IETF and IRTF). Notices are also to be made available and (e.g., the IETF and IRTF). Notices are also to be made available and
archived on the RFC Editor website. In addition, other communication archived on the RFC Editor website. In addition, other communication
channels can be established for notices (e.g., via an RSS feed or by channels can be established for notices (e.g., via an RSS feed or by
posting to social media venues).</t> posting to social media venues).</t>
<t>In cases where a proposal has the potential to significantly modify <t>In cases where a proposal has the potential to significantly modify
policies of long standing or historical characteristics of the long-standing policies or historical characteristics of the RFC
Series as described under <xref target="properties"/>, the RSAB should take extr Series as described in <xref target="properties"/>, the RSAB should take extra
a
care to reach out to a very wide range of communities that make use of care to reach out to a very wide range of communities that make use of
RFCs (as described under <xref target="participation"/>) since such communities RFCs (as described in <xref target="participation"/>) since such communities
might not be actively engaged in the RSWG directly. The RSAB should might not be actively engaged in the RSWG directly. The RSAB should
work with the stream approving bodies and the IETF LLC to identify and work with the stream approving bodies and the IETF LLC to identify and
establish contacts in such communities, assisted in particular by the establish contacts in such communities, assisted by the
RSCE.</t> RSCE in particular.</t>
<t>The RSAB should maintain a public list of communities that are <t>The RSAB should maintain a public list of communities that are
contacted during calls for comments.</t> contacted during calls for comments.</t>
<t>A notice of a community call for comments contains the following:</ t> <t>A notice of a community call for comments contains the following:</ t>
<ul spacing="normal"> <ul spacing="normal">
<li>A subject line beginning with 'Call for Comments:'</li> <li>A subject line beginning with 'Call for Comments:'</li>
<li>A clear, concise summary of the proposal</li> <li>A clear, concise summary of the proposal</li>
<li>A URL pointing to the Internet-Draft that defines the proposal</ li> <li>A URL pointing to the Internet-Draft that defines the proposal</ li>
<li>Any explanations or questions for the community that the RSAB de ems <li>Any explanations or questions for the community that the RSAB de ems
necessary (using their usual decision-making procedures)</li> necessary (using their usual decision-making procedures)</li>
<li>Clear instructions on how to provide public comments</li> <li>Clear instructions on how to provide public comments</li>
<li>A deadline for comments</li> <li>A deadline for comments</li>
</ul> </ul>
<t>A comment period will last not less than two weeks and should be <t>A comment period will last not less than two weeks and should be
longer if wide outreach is required. Comments will be publicly longer if wide outreach is required. Comments will be publicly
archived on the RFC Editor website.</t> archived on the RFC Editor website.</t>
<t>The RSAB is responsible for considering comments received during <t>The RSAB is responsible for considering comments received during
a community call for comments. If RSAB members conclude that such a community call for comments. If RSAB members conclude that such
comments raise important issues that need to be addressed, they comments raise important issues that need to be addressed, they
should do so by discussing those issues within the RSWG or (if should do so by discussing those issues within the RSWG or (if
the issues meet the criteria specified under Step 9 of <xref target="workflow"/> the issues meet the criteria specified in <xref target="step9" format="none">Ste
) p 9</xref> of <xref target="workflow"/>)
lodging a position of "CONCERN" during RSAB balloting.</t> lodging a position of CONCERN during RSAB balloting.</t>
</section> </section>
<section anchor="appeals"> <section anchor="appeals">
<name>Appeals</name> <name>Appeals</name>
<t>Appeals of RSWG chair decisions shall be made to the RSAB. Decision <t>Appeals of RSWG Chair decisions shall be made to the RSAB. Decision
s of the s of the
RSWG chairs can be appealed only on grounds of failure to follow the correct RSWG Chairs can be appealed only on grounds of failure to follow the correct
process. Appeals should be made within thirty (30) days of any action, or in process. Appeals should be made within thirty (30) days of any action or, in
the case of failure to act, of notice having been given to the RSWG chairs. the case of failure to act, of notice having been given to the RSWG Chairs.
The RSAB will then decide if the process was followed and will direct The RSAB will then decide if the process was followed and will direct
the RSWG chairs as to what procedural actions are required.</t> the RSWG Chairs as to what procedural actions are required.</t>
<t>Decisions of the RSAB can be appealed on grounds of failure to foll ow <t>Decisions of the RSAB can be appealed on grounds of failure to foll ow
the correct process. Where the RSAB makes a decision in order to resolve the correct process. In addition, if the RSAB makes a decision in order to resol
a disagreement between authors and the RPC (as described under <xref target="dis ve
agreements"/>), appeals can a disagreement between authors and the RPC (as described in <xref target="disagr
eements"/>), appeals can
be filed on the basis that the RSAB misinterpreted an approved policy. be filed on the basis that the RSAB misinterpreted an approved policy.
Aside from these two cases, disagreements about the conduct of the RSAB are not Aside from these two cases, disagreements about the conduct of the RSAB are not
subject to appeal. Appeals of RSAB decisions shall be made to the IAB subject to appeal. Appeals of RSAB decisions shall be made to the IAB
and should be made within thirty (30) days of public notice of the and should be made within thirty (30) days of public notice of the
relevant RSAB decision (typically, when minutes are posted). The IAB relevant RSAB decision (typically, when minutes are posted). The IAB
shall decide whether a process failure occurred and what if any shall decide whether a process failure occurred and what (if any)
corrective action should take place.</t> corrective action should take place.</t>
</section> </section>
<section anchor="coc"> <section anchor="coc">
<name>Anti-Harassment Policy</name> <name>Anti-Harassment Policy</name>
<t>The <eref target="https://www.ietf.org/about/groups/iesg/statements /anti-harassment-policy/">IETF anti-harassment policy</eref> also applies to the RSWG and RSAB, <t>The <eref target="https://www.ietf.org/about/groups/iesg/statements /anti-harassment-policy/">IETF anti-harassment policy</eref> also applies to the RSWG and RSAB,
which strive to create and maintain an environment in which people which strive to create and maintain an environment in which people
of many different backgrounds are treated with dignity, decency, of many different backgrounds are treated with dignity, decency,
and respect. Participants are expected to behave according to and respect. Participants are expected to behave according to
professional standards and to demonstrate appropriate workplace professional standards and to demonstrate appropriate workplace
behavior. For further information about these policies, see behavior. For further information about these policies, see
<xref target="RFC7154"/>, <xref target="RFC7776"/>, and <xref target="RFC8716"/> .</t> <xref target="RFC7154"/>, <xref target="RFC7776"/>, and <xref target="RFC8716"/> .</t>
</section> </section>
<section anchor="rfc-boilerplates"> <section anchor="rfc-boilerplates">
<name>RFC Boilerplates</name> <name>RFC Boilerplates</name>
<t>RFC boilerplates (see <xref target="RFC7841"/>) are part of the RFC Style Guide, <t>RFC boilerplates (see <xref target="RFC7841"/>) are part of the RFC Style Guide,
as defined below under <xref target="practices"/>. New or modified boilerplates as defined in <xref target="practices"/>. New or modified boilerplates
considered under version 3 of the RFC Editor Model must be approved considered under version 3 of the RFC Editor Model must be approved
by the following parties, each of which has a separate area of by the following parties, each of which has a separate area of
responsibility with respect to boilerplates:</t> responsibility with respect to boilerplates:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>Each applicable stream, which approves that the boilerplate meet <li>The applicable stream, which approves that the boilerplate meets
s its its
needs</li> needs</li>
<li>The RSAB, which approves that the boilerplate is not in conflict with <li>The RSAB, which approves that the boilerplate is not in conflict with
the boilerplate used in the other streams</li> the boilerplate used in the other streams</li>
<li>The RPC, which approves that the language of the boilerplate is consistent <li>The RPC, which approves that the language of the boilerplate is consistent
with the RFC Style Guide</li> with the RFC Style Guide</li>
<li>The IETF Trust, which approves that the boilerplate correctly st ates <li>The IETF Trust, which approves that the boilerplate correctly st ates
the Trust's position regarding rights and ownership</li> the Trust's position regarding rights and ownership</li>
</ul> </ul>
</section> </section>
</section> </section>
</section> </section>
<section anchor="policy-implementation"> <section anchor="policy-implementation">
<name>Policy Implementation</name> <name>Policy Implementation</name>
<section anchor="roles-and-processes"> <section anchor="roles-and-processes">
<name>Roles and Processes</name> <name>Roles and Processes</name>
<t>Publication of RFCs is handled by the RFC Production Center (RPC).</t > <t>Publication of RFCs is handled by the RFC Production Center (RPC).</t >
<t>A few general considerations apply:</t> <t>A few general considerations apply:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>The general roles and responsibilities of the RPC are defined by <li>The general roles and responsibilities of the RPC are defined by
RFCs published in the Editorial Stream (i.e., not directly by the RFCs published in the Editorial Stream (i.e., not directly by the
RSWG, RSAB, or RSCE), by existing RFCs which apply to the RSWG, RSAB, or RSCE), by existing RFCs that apply to the
RPC and which have not yet been superseded by Editorial Stream RPC and have not yet been superseded by Editorial Stream
RFCs, and by the requisite contracts.</li> RFCs, and by the requisite contracts.</li>
<li>The RPC is advised by the RSCE and RSAB, and has a duty to <li>The RPC is advised by the RSCE and RSAB, and it has a duty to
consult with them under specific circumstances, such as those consult with them under specific circumstances, such as those
relating to disagreements between authors and the RPC as relating to disagreements between authors and the RPC as
described under <xref target="disagreements"/>.</li> described in <xref target="disagreements"/>.</li>
<li>The RPC is overseen by the IETF LLC to ensure that <li>The RPC is overseen by the IETF LLC to ensure that
it performs in accordance with contracts in place.</li> it performs in accordance with contracts in place.</li>
</ul> </ul>
<t>All matters of budget, timetable, and impact on its performance <t>All matters of budget, timetable, and impact on its performance
targets, are between the RPC and IETF LLC.</t> targets are between the RPC and IETF LLC.</t>
<t>The RPC shall regularly provide reports to the IETF LLC, RSAB, RSWG, <t>The RPC shall regularly provide reports to the IETF LLC, RSAB, RSWG,
and broader community regarding its activities and any key risks or and broader community regarding its activities and any key risks or
issues affecting it.</t> issues affecting it.</t>
<t>In the event that the RPC is required to make a decision without <t>In the event that the RPC is required to make a decision without
consultation that would normally deserve consultation, or makes a consultation that would normally deserve consultation, or makes a
decision against the advice of the RSAB, the RPC must notify the decision against the advice of the RSAB, the RPC must notify the
RSAB.</t> RSAB.</t>
<t>This document does not specify the exact relationship between the <t>This document does not specify the exact relationship between the
IETF LLC and the RPC; for example, the work of the RPC could be IETF LLC and the RPC; for example, the work of the RPC could be
performed by a separate corporate entity under contract to the performed by a separate corporate entity under contract to the
IETF LLC, it could be performed by employees of the IETF LLC, or IETF LLC, it could be performed by employees of the IETF LLC, or
the IETF LLC could engage with independent contractors for some or the IETF LLC could engage with independent contractors for some or
all aspects of such work. The exact relationship is a matter for all aspects of such work. The exact relationship is a matter for
the IETF LLC to determine.</t> the IETF LLC to determine.</t>
<t>The IETF LLC is responsible for the method of and management of the <t>The IETF LLC is responsible for the method and management of the
engagement of the RPC. Therefore, the IETF LLC has authority over engagement of the RPC. Therefore, the IETF LLC has authority over
negotiating performance targets for the RPC and also has responsibility negotiating performance targets for the RPC and also has
for ensuring that those targets are met. Such performance targets responsibility for ensuring that those targets are met. Such
are set based on the RPC's publication load and additional efforts performance targets are set based on the RPC's publication load and
required to implement policies specified in the Editorial Stream, in existing RF additional efforts required to implement policies specified in
Cs Editorial Stream RFCs, in existing RFCs that apply to the RPC and have
which apply to the RPC and which have not yet been superseded by not yet been superseded by Editorial Stream RFCs, and in the requisite
Editorial Stream RFCs, and in the requisite contracts. The IETF LLC may contracts. The IETF LLC may consult with the community regarding
consult with the community regarding these targets. The IETF LLC is these targets. The IETF LLC is empowered to appoint a manager or to
empowered to appoint a manager or to convene a committee to complete convene a committee to complete these activities.</t>
these activities.</t> <t>If individuals or groups within the community have concerns about the
<t>If individuals or groups within the community have concerns about the
performance of the RPC, they can request that the matter be investigated performance of the RPC, they can request that the matter be investigated
by the IETF LLC Board, the IETF LLC Executive Director, or a point of by the IETF LLC Board, the IETF Executive Director, or a point of
contact designated by the IETF LLC Board. Even if the IETF LLC opts to contact designated by the IETF LLC Board. Even if the IETF LLC opts to
delegate this activity, concerns should be raised with the IETF LLC. delegate this activity, concerns should be raised with the IETF LLC.
The IETF LLC is ultimately answerable to the community via the mechanisms The IETF LLC is ultimately answerable to the community via the mechanisms
outlined in its charter <xref target="RFC8711"/>.</t> outlined in <xref target="RFC8711"/>.</t>
</section> </section>
<section anchor="practices"> <section anchor="practices">
<name>Working Practices</name> <name>Working Practices</name>
<t>In the absence of a high-level policy documented in an RFC, or in the <t>In the absence of a high-level policy documented in an RFC or in the
interest of specifying the detail of its implementation of such policies, the RP C can interest of specifying the detail of its implementation of such policies, the RP C can
document working practices regarding the editorial preparation document working practices regarding the editorial preparation,
and final publication and dissemination of RFCs. Examples include:</t> final publication, and dissemination of RFCs. Examples include:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>Maintenance of a style guide that defines editorial standards for <li>Maintenance of a style guide that defines editorial standards for
RFCs; specifically, the RFC Style Guide consists of <xref target="RFC7322"/> and RFCs; specifically, the RFC Style Guide consists of <xref target="RFC7322"/> and
the other documents and resources listed at <xref target="STYLEGUIDE"/>.</li> the other documents and resources listed at <xref target="STYLEGUIDE"/>.</li>
<li>Instructions regarding the file formats that are accepted as input to the <li>Instructions regarding the file formats that are accepted as input to the
editing and publication process.</li> editing and publication process.</li>
<li>Guidelines regarding the final structure and layout of published d ocuments. <li>Guidelines regarding the final structure and layout of published d ocuments.
In the context of the XML vocabulary <xref target="RFC7991"/>, such guidelines c ould In the context of the XML vocabulary <xref target="RFC7991"/>, such guidelines c ould
include clarifications regarding the preferred XML elements and attributes used to include clarifications regarding the preferred XML elements and attributes used to
capture the semantic content of RFCs.</li> capture the semantic content of RFCs.</li>
skipping to change at line 655 skipping to change at line 659
<li>Establishing the publication readiness of each document through <li>Establishing the publication readiness of each document through
communication with the authors, IANA, or stream-specific contacts, communication with the authors, IANA, or stream-specific contacts,
supplemented if needed by the RSAB and RSCE.</li> supplemented if needed by the RSAB and RSCE.</li>
<li>Creating and preserving records of dialogue with document authors. </li> <li>Creating and preserving records of dialogue with document authors. </li>
<li>Requesting advice from the RSAB and RSCE as needed.</li> <li>Requesting advice from the RSAB and RSCE as needed.</li>
<li>Providing suggestions to the RSAB and RSCE as needed.</li> <li>Providing suggestions to the RSAB and RSCE as needed.</li>
<li>Participating within the RSWG in the creation of new Editorial <li>Participating within the RSWG in the creation of new Editorial
Stream RFCs that impact the RPC, specifically with respect to any Stream RFCs that impact the RPC, specifically with respect to any
challenges the RPC might foresee with regard to implementation of challenges the RPC might foresee with regard to implementation of
proposed policies.</li> proposed policies.</li>
<li>Identifying topics and issues that they encounter while processing <li>Identifying topics and issues while processing
documents or carrying out other responsibilities on this list for documents or carrying out other responsibilities on this list for
which they lack sufficient expertise, and identifying and conferring which they lack sufficient expertise, and identifying and conferring
with relevant experts as needed.</li> with relevant experts as needed.</li>
<li>Providing reports to the community on its performance and plans.</ li> <li>Providing reports to the community on its performance and plans.</ li>
<li>Consulting with the community on its plans.</li> <li>Consulting with the community on its plans.</li>
<li>Negotiating its specific plans and resources with the IETF LLC.</l i> <li>Negotiating its specific plans and resources with the IETF LLC.</l i>
<li>Providing sufficient resources to support reviews of RPC <li>Providing sufficient resources to support reviews of RPC
performance by the IETF LLC.</li> performance by the IETF LLC.</li>
<li>Coordinating with IANA to ensure that RFCs accurately document <li>Coordinating with IANA to ensure that RFCs accurately document
registration processes and assigned values for IANA registries.</li> registration processes and assigned values for IANA registries.</li>
skipping to change at line 694 skipping to change at line 698
<li>Authenticating RFCs for legal proceedings.</li> <li>Authenticating RFCs for legal proceedings.</li>
</ol> </ol>
</section> </section>
<section anchor="disagreements"> <section anchor="disagreements">
<name>Resolution of Disagreements between Authors and the RPC</name> <name>Resolution of Disagreements between Authors and the RPC</name>
<t>During the process of editorial preparation and publication, disagree ments <t>During the process of editorial preparation and publication, disagree ments
can arise between the authors of an RFC-to-be and the RPC. Where an existing can arise between the authors of an RFC-to-be and the RPC. Where an existing
policy clearly applies, typically such disagreements are handled in a policy clearly applies, typically such disagreements are handled in a
straightforward manner through direct consultation between the authors and straightforward manner through direct consultation between the authors and
the RPC, sometimes in collaboration with stream-specific contacts.</t> the RPC, sometimes in collaboration with stream-specific contacts.</t>
<t>However, if it is unclear whether an existing policy applies, or if i t is <t>However, if it is unclear whether an existing policy applies or if it is
unclear how to interpret an existing policy, the parties may need to unclear how to interpret an existing policy, the parties may need to
consult with additional individuals or bodies (e.g., RSAB, IESG, IRSG, or consult with additional individuals or bodies (e.g., RSAB, IESG, IRSG, or
stream approving bodies) to help achieve a resolution. The following points are stream approving bodies) to help achieve a resolution. The following points are
intended to provide more specific guidance.</t> intended to provide more specific guidance.</t>
<ul spacing="normal"> <ul spacing="normal">
<li>If there is a conflict with a policy for a particular stream, to h elp <li>If there is a conflict with a policy for a particular stream, to h elp
achieve a resolution the RPC should consult with the relevant stream achieve a resolution, the RPC should consult with the relevant stream
approving body (such as the IESG or IRSG) and other representatives of approving body (such as the IESG or IRSG) and other representatives of
the relevant stream as appropriate.</li> the relevant stream as appropriate.</li>
<li>If there is a conflict with a cross-stream policy, the RPC should consult <li>If there is a conflict with a cross-stream policy, the RPC should consult
with the RSAB to achieve a resolution.</li> with the RSAB to achieve a resolution.</li>
<li>The disagreement might raise a new issue that is not covered by an existing <li>The disagreement might raise a new issue that is not covered by an existing
policy or that cannot be resolved through consultation between the RPC and policy or that cannot be resolved through consultation between the RPC and
other relevant individuals and bodies, as described above. In this case, other relevant individuals and bodies, as described above. In this case,
the RSAB is responsible for (a) resolving the disagreement in a timely manner the RSAB is responsible for (a) resolving the disagreement in a timely manner
if necessary so that the relevant stream document(s) can be published before a if necessary so that the relevant stream document(s) can be published before a
new policy is defined and (b) bringing the issue to the RSWG so that a new polic y new policy is defined and (b) bringing the issue to the RSWG so that a new polic y
can be defined.</li> can be defined.</li>
</ul> </ul>
</section> </section>
<section anchor="point-of-contact"> <section anchor="point-of-contact">
<name>Point of Contact</name> <name>Point of Contact</name>
<t>From time to time, individuals or organizations external to the IETF and <t>From time to time, individuals or organizations external to the IETF and
the broader RFC Series community may have questions about the RFC Series. the broader RFC Series community may have questions about the RFC Series.
Such inquiries should be directed to the Such inquiries should be directed to the
<eref target="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</eref> email <eref target="mailto:rfc-editor@rfc-editor.org">rfc&nbhy;editor@rfc&nbhy;editor. org</eref> email
alias or to its successor or future equivalent and then handled by the alias or to its successor or future equivalent and then handled by the
appropriate bodies (e.g., RSAB, RPC) or individuals (e.g., RSWG chairs, RSCE).</ t> appropriate bodies (e.g., RSAB and RPC) or individuals (e.g., RSWG Chairs and RS CE).</t>
</section> </section>
<section anchor="administrative-implementation"> <section anchor="administrative-implementation">
<name>Administrative Implementation</name> <name>Administrative Implementation</name>
<t>The exact implementation of the administrative and contractual <t>The exact implementation of the administrative and contractual
activities described here are a responsibility of the IETF LLC. This activities described here are a responsibility of the IETF LLC. This
section provides general guidance regarding several aspects of such section provides general guidance regarding several aspects of such
activities.</t> activities.</t>
<section anchor="vendor-selection-for-the-rfc-production-center"> <section anchor="vendor-selection-for-the-rfc-production-center">
<name>Vendor Selection for the RFC Production Center</name> <name>Vendor Selection for the RPC</name>
<t>Vendor selection is done in cooperation with the streams and <t>Vendor selection is done in cooperation with the streams and
under the final authority of the IETF LLC.</t> under the final authority of the IETF LLC.</t>
<t>The IETF LLC develops the work definition (the Statement of Work) <t>The IETF LLC develops the work definition (the Statement of Work)
for the RPC and manages the vendor selection process. The work for the RPC and manages the vendor-selection process. The work
definition is created within the IETF LLC budget and takes into definition is created within the IETF LLC budget and takes into
account the RPC responsibilities (as described under <xref target="rpc"/>), account the RPC responsibilities (as described in <xref target="rpc"/>),
the needs of the streams, and community input.</t> the needs of the streams, and community input.</t>
<t>The process to select and contract for the RFC Production Center <t>The process to select and contract for the RPC
and other RFC-related services is as follows:</t> and other RFC-related services is as follows:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>The IETF LLC establishes the contract process, including the ste ps <li>The IETF LLC establishes the contract process, including the ste ps
necessary to issue an RFP when necessary, the timing, and the necessary to issue a Request for Proposal (RFP) when necessary, the timing, and the
contracting procedures.</li> contracting procedures.</li>
<li>The IETF LLC establishes a selection committee, which will <li>The IETF LLC establishes a selection committee, which will
consist of the IETF Executive Director and other consist of the IETF Executive Director and other
members selected by the IETF LLC in consultation with the members selected by the IETF LLC in consultation with the
stream approving bodies. The committee shall select a chair from stream approving bodies. The committee shall select a chair from
among its members.</li> among its members.</li>
<li>The selection committee selects the vendor, subject to the <li>The selection committee selects the vendor, subject to the
successful negotiation of a contract approved by the IETF LLC. In successful negotiation of a contract approved by the IETF LLC. In
the event that a contract cannot be signed, the matter shall be the event that a contract cannot be signed, the matter shall be
referred to the selection committee for further action.</li> referred to the selection committee for further action.</li>
skipping to change at line 783 skipping to change at line 787
technical publishing processes to the RFC Series.</t> technical publishing processes to the RFC Series.</t>
<t>The primary responsibilities of the RSCE are as follows:</t> <t>The primary responsibilities of the RSCE are as follows:</t>
<ul spacing="normal"> <ul spacing="normal">
<li>Serve as a voting member on the RSAB</li> <li>Serve as a voting member on the RSAB</li>
<li>Identify problems with the RFC publication process and <li>Identify problems with the RFC publication process and
opportunities for improvement</li> opportunities for improvement</li>
<li>Provide expert advice within the RSWG regarding policy proposals</li > <li>Provide expert advice within the RSWG regarding policy proposals</li >
<li>Provide expert advice to the RPC and IETF LLC</li> <li>Provide expert advice to the RPC and IETF LLC</li>
</ul> </ul>
<t>Matters on which the RSCE might provide guidance could include the <t>Matters on which the RSCE might provide guidance could include the
following (see also Section 4 of <xref target="RFC8729"/>):</t> following (see also <xref target="RFC8729" sectionFormat="of" section="4"/>):</t >
<ul spacing="normal"> <ul spacing="normal">
<li>Editing, processing, and publication of RFCs</li> <li>Editing, processing, and publication of RFCs</li>
<li>Publication formats for the RFC Series</li> <li>Publication formats for the RFC Series</li>
<li>Changes to the RFC Style Guide</li> <li>Changes to the RFC Style Guide</li>
<li>Series-wide guidelines regarding document content and quality</li> <li>Series-wide guidelines regarding document content and quality</li>
<li>Web presence for the RFC Series</li> <li>Web presence for the RFC Series</li>
<li>Copyright matters related to the RFC Series</li> <li>Copyright matters related to the RFC Series</li>
<li>Archiving, indexing, and accessibility of RFCs</li> <li>Archiving, indexing, and accessibility of RFCs</li>
</ul> </ul>
<t>The IETF LLC is responsible for the method of and management of the <t>The IETF LLC is responsible for the method and management of the
engagement of the RSCE, including selection, evaluation, and the timely engagement of the RSCE, including selection, evaluation, and the timely
filling of any vacancy. Therefore, whether the RSCE role is structured filling of any vacancy. Therefore, whether the RSCE role is structured
as a contractual or employee relationship is a matter for the IETF LLC as a contractual or employee relationship is a matter for the IETF LLC
to determine.</t> to determine.</t>
<section anchor="rsce-selection"> <section anchor="rsce-selection">
<name>RSCE Selection</name> <name>RSCE Selection</name>
<t>Responsibility for making a recommendation to the IETF LLC regarding <t>Responsibility for making a recommendation to the IETF LLC regarding
the RSCE role will lie with a selection committee. The IETF LLC should the RSCE role will lie with a selection committee. The IETF LLC should
propose an initial slate of members for this committee, making sure propose an initial slate of members for this committee, making sure
to include community members with diverse perspectives, and consult with the str eam to include community members with diverse perspectives, and consult with the str eam
skipping to change at line 816 skipping to change at line 820
committee will take into account the definition of the role as well committee will take into account the definition of the role as well
as any other information that the committee deems necessary or as any other information that the committee deems necessary or
helpful in making its decision. The IETF LLC is responsible for helpful in making its decision. The IETF LLC is responsible for
contracting or employment of the RSCE.</t> contracting or employment of the RSCE.</t>
</section> </section>
<section anchor="rsce-performance-evaluation"> <section anchor="rsce-performance-evaluation">
<name>RSCE Performance Evaluation</name> <name>RSCE Performance Evaluation</name>
<t>Periodically, the IETF LLC will evaluate the performance of the <t>Periodically, the IETF LLC will evaluate the performance of the
RSCE, including a call for confidential input from the community. RSCE, including a call for confidential input from the community.
The IETF LLC will produce a draft evaluation of the RSCE's The IETF LLC will produce a draft evaluation of the RSCE's
performance for review by RSAB members other than the RSCE, performance for review by RSAB members (other than the RSCE),
who will provide feedback to the IETF LLC.</t> who will provide feedback to the IETF LLC.</t>
</section> </section>
<section anchor="temporary-rsce-appointment"> <section anchor="temporary-rsce-appointment">
<name>Temporary RSCE Appointment</name> <name>Temporary RSCE Appointment</name>
<t>In the case that the currently appointed RSCE is expected to be <t>In the case that the currently appointed RSCE is expected to be
unavailable for an extended period, the IETF LLC may appoint a unavailable for an extended period, the IETF LLC may appoint a
Temporary RSCE through whatever recruitment process it considers Temporary RSCE through whatever recruitment process it considers
appropriate. A Temporary RSCE acts as the RSCE in all aspects appropriate. A Temporary RSCE acts as the RSCE in all aspects
during their term of appointment.</t> during their term of appointment.</t>
</section> </section>
<section anchor="conflict-of-interest"> <section anchor="conflict-of-interest">
<name>Conflict of Interest</name> <name>Conflict of Interest</name>
<t>The RSCE is expected to avoid even the appearance of conflict of <t>The RSCE is expected to avoid even the appearance of conflict of
interest or judgment in performing their role. To ensure this, the interest or judgment in performing their role. To ensure this, the
RSCE will be subject to a conflict of interest policy established by RSCE will be subject to a conflict-of-interest policy established by
the IETF LLC.</t> the IETF LLC.</t>
<t>The RPC service provider may contract services from the RSCE service <t>The RPC service provider may contract services from the RSCE service
provider, and vice versa including for services provided to the IETF provider, and vice versa, including services provided to the IETF
LLC. All contracts between the two must be disclosed to the IETF LLC.<br/> LLC. All contracts between the two must be disclosed to the IETF LLC.
Where those services are related to services provided to the IETF LLC, Where those services are related to services provided to the IETF LLC,
IETF LLC policies shall apply, including publication of relevant parts IETF LLC policies shall apply, including publication of relevant parts
of the contract.</t> of the contract.</t>
</section> </section>
</section> </section>
<section anchor="editorial-stream"> <section anchor="editorial-stream">
<name>Editorial Stream</name> <name>Editorial Stream</name>
<t>This document creates the Editorial Stream as a separate space for <t>This document creates the Editorial Stream as a separate space for
publication of policies, procedures, guidelines, rules, and related publication of policies, procedures, guidelines, rules, and related
information regarding the RFC Series as a whole.</t> information regarding the RFC Series as a whole.</t>
<t>The Editorial Stream shall be used only to specify and update policies, <t>The Editorial Stream shall be used only to specify and update policies,
procedures, guidelines, rules, and related information regarding the procedures, guidelines, rules, and related information regarding the
RFC Series as a whole; no other use of the Editorial Stream is authorized RFC Series as a whole; no other use of the Editorial Stream is authorized
by this memo and no other streams are so authorized. This policy may be by this memo, and no other streams are so authorized. This policy may be
changed only by agreement of the IAB, IESG, and IETF LLC.</t> changed only by agreement of the IAB, IESG, and IETF LLC.</t>
<t>All documents produced by the RSWG and approved by the RSAB shall be <t>All documents produced by the RSWG and approved by the RSAB shall be
published as RFCs in the Editorial Stream with a status of Informational. published as RFCs in the Editorial Stream with a status of Informational.
(Note that the Editorial Stream is not authorized to publish RFCs that (Note that the Editorial Stream is not authorized to publish RFCs that
are Standards Track or Best Current Practice, since such RFCs are are Standards Track or Best Current Practice, since such RFCs are
reserved to the IETF Stream <xref target="RFC8729"/>.) Notwithstanding the statu reserved for the IETF Stream <xref target="RFC8729"/>.) Notwithstanding the stat
s us
of "Informational", it should be understood that documents published of Informational, it should be understood that documents published
in the Editorial Stream define policies for the RFC Series as a whole.</t> in the Editorial Stream define policies for the RFC Series as a whole.</t>
<t>The requirements and process for creating any additional RFC streams ar e <t>The requirements and process for creating any additional RFC streams ar e
outside the scope of this document.</t> outside the scope of this document.</t>
<section anchor="procedures-request-of-the-ietf-trust"> <section anchor="procedures-request-of-the-ietf-trust">
<name>Procedures Request of the IETF Trust</name> <name>Procedures Request of the IETF Trust</name>
<t>The IAB requests that the IETF Trust and its Trustees assist in <t>The IAB requests that the IETF Trust and its Trustees assist in
meeting the goals and procedures set forth in this document.</t> meeting the goals and procedures set forth in this document.</t>
<t>The Trustees are requested to publicly confirm their willingness and <t>The Trustees are requested to publicly confirm their willingness and
ability to accept responsibility for the Intellectual Property Rights ability to accept responsibility for the Intellectual Property Rights
(IPR) for the Editorial Stream.</t> (IPR) for the Editorial Stream.</t>
<t>Specifically, the Trustees are asked to develop the necessary <t>Specifically, the Trustees are asked to develop the necessary
boilerplate to enable the suitable marking of documents so that the boilerplate to enable the suitable marking of documents so that the
IETF Trust receives the rights as specified in <xref target="BCP78"/>. These IETF Trust receives the rights as specified in <xref target="BCP78"/>. These
procedures need to also allow authors to indicate either no rights to procedures need to also allow authors to indicate either no rights to
make derivative works, or preferentially, the right to make unlimited make derivative works or, preferentially, the right to make unlimited
derivative works from the documents. It is left to the Trust to derivative works from the documents. It is left to the Trust to
specify exactly how this shall be clearly indicated in each document.</t> specify exactly how this shall be clearly indicated in each document.</t>
</section> </section>
<section anchor="patent-and-trademark-rules-for-the-editorial-stream"> <section anchor="patent-and-trademark-rules-for-the-editorial-stream">
<name>Patent and Trademark Rules for the Editorial Stream</name> <name>Patent and Trademark Rules for the Editorial Stream</name>
<t>As specified above, contributors of documents for the Editorial Strea m <t>As specified above, contributors of documents for the Editorial Strea m
are expected to use the IETF Internet-Draft process, complying therein are expected to use the IETF Internet-Draft process, complying therein
with the rules specified in the latest version of <xref target="BCP9"/>. This in with the rules specified in <xref target="BCP9"/>. This includes
cludes the disclosure of patent and trademark issues that are known, or can be
the disclosure of Patent and Trademark issues that are known, or can be
reasonably expected to be known, to the contributor.</t> reasonably expected to be known, to the contributor.</t>
<t>Disclosure of license terms for patents is also requested, as <t>Disclosure of license terms for patents is also requested, as
specified in the most recent version of <xref target="BCP79"/>. The Editorial specified in <xref target="BCP79"/>. The Editorial
Stream has chosen to use the IETF's IPR disclosure mechanism, Stream has chosen to use the <eref target="https://www.ietf.org/ipr/">IETF's IPR
https://www.ietf.org/ipr/, for this purpose. The IAB would prefer that disclosure mechanism</eref> for this purpose. The IAB would prefer that
the most liberal terms possible be made available for Editorial Stream the most liberal terms possible be made available for Editorial Stream
documents. Terms that do not require fees or licensing are preferable.<br/> documents. Terms that do not require fees or licensing are preferable.
Non-discriminatory terms are strongly preferred over those that Non-discriminatory terms are strongly preferred over those that
discriminate among users. However, although disclosure is required discriminate among users. However, although disclosure is required
and the RSWG and the RSAB may consider disclosures and terms in making and the RSWG and the RSAB may consider disclosures and terms in making
a decision as to whether to submit a document for publication, there a decision as to whether to submit a document for publication, there
are no specific requirements on the licensing terms for intellectual are no specific requirements on the licensing terms for intellectual
property related to Editorial Stream publication.</t> property related to Editorial Stream publication.</t>
</section> </section>
<section anchor="editorial-stream-boilerplate"> <section anchor="editorial-stream-boilerplate">
<name>Editorial Stream Boilerplate</name> <name>Editorial Stream Boilerplate</name>
<t>This document specifies the following text for the "Status of This Me mo" <t>This document specifies the following text for the "Status of This Me mo"
section of RFCs published in the Editorial Stream. Any changes to this section of RFCs published in the Editorial Stream. Any changes to this
boilerplate must be made through the RFC Series Policy Definition process boilerplate must be made through the RFC Series Policy Definition Process
specified in this document.</t> specified in <xref target="policy-definition"/> of this document.</t>
<t>Because all Editorial Stream RFCs have a status of Informational, <t>Because all Editorial Stream RFCs have a status of Informational,
the first paragraph of the "Status of This Memo" section shall be the first paragraph of the "Status of This Memo" section shall be
as specified in Appendix A.2.1 of <xref target="RFC7841"/>.</t> as specified in <xref target="RFC7841" sectionFormat="of" section="A.2.1"/>.</t>
<t>The second paragraph of the "Status of This Memo" section shall be <t>The second paragraph of the "Status of This Memo" section shall be
as follows:</t> as follows:</t>
<ul empty="true">
<li> <t indent="3">This document is a product of the RFC Series Policy De
<t>This document is a product of the RFC Series Policy Definition pr finition Process.
ocess.
It represents the consensus of the RFC Series Working Group approved by It represents the consensus of the RFC Series Working Group approved by
the RFC Series Approval Board. Such documents are not candidates for any the RFC Series Approval Board. Such documents are not candidates for any
level of Internet Standard; see Section 2 of RFC 7841.</t> level of Internet Standard; see Section 2 of RFC 7841.</t>
</li>
</ul>
<t>The third paragraph of the "Status of This Memo" section shall be <t>The third paragraph of the "Status of This Memo" section shall be
as specified in Section 3.5 of <xref target="RFC7841"/>.</t> as specified in <xref target="RFC7841" sectionFormat="of" section="3.5"/>.</t>
</section> </section>
</section> </section>
<section anchor="properties"> <section anchor="properties">
<name>Historical Properties of the RFC Series</name> <name>Historical Properties of the RFC Series</name>
<t>This section lists some of the properties that have been <t>This section lists some of the properties that have been
historically regarded as important to the RFC Series. Proposals historically regarded as important to the RFC Series. Proposals
that affect these properties are possible within the processes that affect these properties are possible within the processes
defined in this document. As described under <xref target="workflow"/> and <xref target="cfc"/>, defined in this document. As described in Sections <xref target="workflow" forma t="counter"/> and <xref target="cfc" format="counter"/>,
proposals that might have a detrimental effect on these properties proposals that might have a detrimental effect on these properties
should receive heightened scrutiny during RSWG discussion and RSAB should receive heightened scrutiny during RSWG discussion and RSAB
review. The purpose of this scrutiny is to ensure that all changes are review. The purpose of this scrutiny is to ensure that all changes are
deliberate and that the consequences of a proposal, as far as they can be deliberate and that the consequences of a proposal, as far as they can be
identified, have been carefully considered.</t> identified, have been carefully considered.</t>
<section anchor="availability"> <section anchor="availability">
<name>Availability</name> <name>Availability</name>
<t>Documents in the RFC Series have been available for many decades, <t>Documents in the RFC Series have been available for many decades,
with no restrictions on access or distribution.</t> with no restrictions on access or distribution.</t>
</section> </section>
<section anchor="accessibility"> <section anchor="accessibility">
<name>Accessibility</name> <name>Accessibility</name>
<t>RFC Series documents have been published in a format that was intende d <t>RFC Series documents have been published in a format that was intende d
to be as accessible as possible to people with disabilities, e.g., to be as accessible as possible to people with disabilities, e.g.,
people with impaired sight.</t> people with impaired sight.</t>
</section> </section>
<section anchor="language"> <section anchor="language">
<name>Language</name> <name>Language</name>
<t>All existing RFC Series documents have been published in English. <t>All existing RFC Series documents have been published in English.
However, since the beginning of the RFC series, documents have been However, since the beginning of the RFC Series, documents have been
published under terms that explicitly allow translation into published under terms that explicitly allow translation into
languages other than English without asking for permission.</t> languages other than English without asking for permission.</t>
</section> </section>
<section anchor="diversity"> <section anchor="diversity">
<name>Diversity</name> <name>Diversity</name>
<t>The RFC series has included many types of documents including standar ds for <t>The RFC Series has included many types of documents including standar ds for
the Internet, procedural and informational documents, thought experiments, the Internet, procedural and informational documents, thought experiments,
speculative ideas, research papers, histories, humor, and even eulogies.</t> speculative ideas, research papers, histories, humor, and even eulogies.</t>
</section> </section>
<section anchor="quality"> <section anchor="quality">
<name>Quality</name> <name>Quality</name>
<t>RFC Series documents have been reviewed for subject matter quality an d <t>RFC Series documents have been reviewed for subject matter quality an d
edited by professionals with a goal of ensuring that documents are clear, edited by professionals with a goal of ensuring that documents are clear,
consistent, and readable <xref target="RFC7322"/>.</t> consistent, and readable <xref target="RFC7322"/>.</t>
</section> </section>
<section anchor="stability"> <section anchor="stability">
<name>Stability</name> <name>Stability</name>
<t>Once published, RFC Series documents have not changed.</t> <t>Once published, RFC Series documents are not changed.</t>
</section> </section>
<section anchor="longevity"> <section anchor="longevity">
<name>Longevity</name> <name>Longevity</name>
<t>RFC Series documents have been published in a form intended to be <t>RFC Series documents have been published in a form intended to be
comprehensible to humans for decades or longer.</t> comprehensible to humans for decades or longer.</t>
</section> </section>
</section> </section>
<section anchor="updates-to-this-document"> <section anchor="updates-to-this-document">
<name>Updates to This Document</name> <name>Updates to This Document</name>
<t>Updates, amendments, and refinements to this document can be produced <t>Updates, amendments, and refinements to this document can be produced
using the process documented herein, but shall be published and operative only a using the process documented herein but shall be published and operative only af
fter ter
(a) obtaining the agreement of the IAB and the IESG, and (b) ensuring (a) obtaining the agreement of the IAB and the IESG and (b) ensuring
that the IETF LLC has no objections regarding its ability to implement that the IETF LLC has no objections regarding its ability to implement
any proposed changes.</t> any proposed changes.</t>
</section> </section>
<section anchor="changes"> <section anchor="changes">
<name>Changes from Version 2 of the RFC Editor Model</name> <name>Changes from Version 2 of the RFC Editor Model</name>
<t>The processes and organizational models for publication of RFCs <t>The processes and organizational models for publication of RFCs
have changed significantly over the years. Most recently, in 2009 have changed significantly over the years. Most recently, in 2009,
<xref target="RFC5620"/> defined the RFC Editor Model (Version 1) and in 2012 <xref target="RFC5620"/> defined the RFC Editor Model (Version 1), and in 2012,
<xref target="RFC6635"/> defined the RFC Editor Model (Version 2), since <xref target="RFC6635"/> defined the RFC Editor Model (Version 2), which was the
n
modified slightly in 2020 by <xref target="RFC8728"/>.</t> modified slightly in 2020 by <xref target="RFC8728"/>.</t>
<t>However, the community experienced several problems with version 1 <t>However, the community experienced several problems with versions 1
and version 2, including a lack of transparency, a lack of avenues and 2, including a lack of transparency, a lack of avenues
for community input into policy definition, and unclear lines of for community input into policy definition, and unclear lines of
authority and responsibility.</t> authority and responsibility.</t>
<t>To address these problems, in 2020 the IAB formed the RFC Editor <t>To address these problems, in 2020, the IAB formed the RFC Editor
Future Development Program to conduct a community discussion and Future Development Program to conduct a community discussion and
consensus process for the further evolution of the RFC Editor Model. consensus process for the further evolution of the RFC Editor Model.
Under the auspices of this Program, the community considered changes Under the auspices of this Program, the community considered changes
that would increase transparency and community input regarding the that would increase transparency and community input regarding the
definition of policies for the RFC Series as a whole, while at definition of policies for the RFC Series as a whole, while at
the same time ensuring the continuity of the RFC Series, the same time ensuring the continuity of the RFC Series,
maintaining the quality and timely publication of RFCs, maintaining the quality and timely publication of RFCs,
ensuring document accessibility, and clarifying lines of ensuring document accessibility, and clarifying lines of
authority and responsibility.</t> authority and responsibility.</t>
<t>This document is the result of discussion within the Program and <t>This document is the result of discussion within the Program and
describes version 3 of the RFC Editor Model while remaining describes version 3 of the RFC Editor Model while remaining
consistent with <xref target="RFC8729"/>.</t> consistent with <xref target="RFC8729"/>.</t>
<t>The following sections describe the changes from version 2 in <t>The following sections describe the changes from version 2 in
more detail.</t> more detail.</t>
<section anchor="rfc-editor-function"> <section anchor="rfc-editor-function">
<name>RFC Editor Function</name> <name>RFC Editor Function</name>
<t>Several responsibilities previously assigned to the "RFC Editor" <t>Several responsibilities previously assigned to the RFC Editor
or, more precisely, the "RFC Editor Function" are now performed or, more precisely, the RFC Editor function, are now performed
by the RSWG, RSAB, RPC, RSCE, and IETF LLC (alone or in combination). by the RSWG, RSAB, RPC, RSCE, and IETF LLC (alone or in combination).
These include various aspects of strategic leadership These include various aspects of strategic leadership
(Section 2.1.1 of <xref target="RFC8728"/>), representation of the RFC Series (<xref target="RFC8728" sectionFormat="of" section="2.1.1"/>), representation of
(Section 2.1.2 of <xref target="RFC8728"/>), development of RFC production and the RFC Series
publication (Section 2.1.3 of <xref target="RFC8728"/>), development of the (<xref target="RFC8728" sectionFormat="of" section="2.1.2"/>), development of RF
RFC Series (Section 2.1.4 of <xref target="RFC8728"/>), operational oversight C production and
(Section 3.3 of <xref target="RFC8729"/>), policy oversight publication (<xref target="RFC8728" sectionFormat="of" section="2.1.3"/>), devel
(Section 3.4 of <xref target="RFC8729"/>), the editing, processing, and publicat opment of the
ion of RFC Series (<xref target="RFC8728" sectionFormat="of" section="2.1.4"/>), operat
documents (Section 4.2 of <xref target="RFC8729"/>), and development and ional oversight
maintenance of Series-wide guidelines and rules (<xref target="RFC8729" sectionFormat="of" section="3.3"/>), policy oversight
(Section 4.4 of <xref target="RFC8729"/>). Among other things this changes the d (<xref target="RFC8729" sectionFormat="of" section="3.4"/>), the editing, proces
ependency on sing, and publication of
the RFC Series Editor (RSE) included in Section 2.2 of <xref target="RFC8730"/> documents (<xref target="RFC8729" sectionFormat="of" section="4.2"/>), and devel
with regard to opment and
maintenance of guidelines and rules that apply to the RFC Series
(<xref target="RFC8729" sectionFormat="of" section="4.4"/>). Among other things,
this changes the dependency on
the RFC Series Editor (RSE) included in <xref target="RFC8730" sectionFormat="of
" section="2.2"/> with regard to
"coordinating work and conforming to general RFC Series policies "coordinating work and conforming to general RFC Series policies
as specified by the IAB and RSE." In addition, various details as specified by the IAB and RSE." In addition, various details
regarding these responsibilities have been modified to accord with regarding these responsibilities have been modified to accord with
the framework defined in this document.</t> the framework defined in this document.</t>
</section> </section>
<section anchor="rfc-series-editor"> <section anchor="rfc-series-editor">
<name>RFC Series Editor</name> <name>RFC Series Editor</name>
<t>Implied by the changes outlined in the previous section, the <t>Implied by the changes outlined in the previous section, the
responsibilities of the RFC Series Editor (RSE) as a person or responsibilities of the RFC Series Editor (RSE) as a person or
role (contrasted with the overall "RFC Editor Function") are now role (contrasted with the overall RFC Editor function) are now
split or shared among the RSWG, RSAB, RSCE, RPC, and IETF LLC (alone split or shared among the RSWG, RSAB, RSCE, RPC, and IETF LLC (alone
or in combination). More specifically, the responsibilities of or in combination). More specifically, the responsibilities of
the RFC Series Consulting Editor (RSCE) under version 3 of the RFC the RFC Series Consulting Editor (RSCE) under version 3 of the RFC
Editor Model differ in many ways from the responsibilities of the Editor Model differ in many ways from the responsibilities of the
RFC Series Editor under version 2 of the Model. In general, RFC Series Editor under version 2 of the RFC Editor Model. In general,
references in existing documents to the RSE can be taken as references in existing documents to the RSE can be taken as
referring to the "RFC Editor Function" as described herein, but referring to the RFC Editor function as described herein but
should not be taken as referring to the RSCE.</t> should not be taken as referring to the RSCE.</t>
</section> </section>
<section anchor="rfc-publisher"> <section anchor="rfc-publisher">
<name>RFC Publisher</name> <name>RFC Publisher</name>
<t>In practice the RFC Production Center (RPC) and RFC Publisher roles <t>In practice, the RFC Production Center (RPC) and RFC Publisher roles
have been performed by the same entity and this practice is expected have been performed by the same entity, and this practice is expected
to continue; therefore this document dispenses with the distinction to continue; therefore, this document dispenses with the distinction
between these roles and refers only to the RPC.</t> between these roles and refers only to the RPC.</t>
</section> </section>
<section anchor="iab"> <section anchor="iab">
<name>IAB</name> <name>IAB</name>
<t>Under earlier versions of the RFC Editor Model, the IAB was <t>Under earlier versions of the RFC Editor Model, the IAB was
responsible for oversight of the RFC Series and acted as a body responsible for oversight of the RFC Series and acted as a body
for final conflict resolution regarding the Series. The IAB's for final conflict resolution regarding the RFC Series. The IAB's
authority in these matters is described in the IAB's charter authority in these matters is described in the IAB Charter
(<xref target="RFC2850"/> as updated by <xref target="I-D.draft-carpenter-rfced- (<xref target="RFC2850"/>, as updated by <xref target="RFC9283"/>).
iab-charter"/>). Under version 2 of the RFC Editor Model, the IAB delegated some
Under version 2 of the Model, the IAB delegated some
of its authority to the RFC Series Oversight Committee (see <xref target="rsoc"/ >). of its authority to the RFC Series Oversight Committee (see <xref target="rsoc"/ >).
Under version 3 of the Model, authority for policy definition Under version 3 of the RFC Editor Model, authority for policy definition
resides with the RSWG as an independent venue for work by members resides with the RSWG as an independent venue for work by members
of the community (with approval of policy proposals as the of the community (with approval of policy proposals being the
responsibility of the RSAB, representing the streams and including responsibility of the RSAB, which represents the streams and includes
the RSCE), whereas authority for policy implementation resides with the RSCE), whereas authority for policy implementation resides with
the IETF LLC.</t> the IETF LLC.</t>
</section> </section>
<section anchor="rsoc"> <section anchor="rsoc">
<name>RFC Series Oversight Committee (RSOC)</name> <name>RFC Series Oversight Committee (RSOC)</name>
<t>In practice, the relationships and lines of authority and responsibil ity <t>In practice, the relationships and lines of authority and responsibil ity
between the IAB, RSOC, and RSE have proved unwieldy and somewhat opaque. between the IAB, RSOC, and RSE have proved unwieldy and somewhat opaque.
To overcome some of these issues, this document dispenses with the RSOC. To overcome some of these issues, this document dispenses with the RSOC.
References to the RSOC in documents such as <xref target="RFC8730"/> are obsolet e References to the RSOC in documents such as <xref target="RFC8730"/> are obsolet e
because this document disbands the RSOC.</t> because this document disbands the RSOC.</t>
</section> </section>
<section anchor="rfc-series-advisory-group-rsag"> <section anchor="rfc-series-advisory-group-rsag">
<name>RFC Series Advisory Group (RSAG)</name> <name>RFC Series Advisory Group (RSAG)</name>
<t>Version 1 of the RFC Editor Model <xref target="RFC5620"/> specified the existence of <t>Version 1 of the RFC Editor Model <xref target="RFC5620"/> specified the existence of
the RFC Series Advisory Group (RSAG), which was no longer specified in the RFC Series Advisory Group (RSAG), which was no longer specified in
version 2 of the Model. For the avoidance of doubt, this document affirms version 2 of the RFC Editor Model. For the avoidance of doubt, this document aff irms
that the RSAG has been disbanded. (The RSAG is not to be confused with the that the RSAG has been disbanded. (The RSAG is not to be confused with the
RFC Series Approval Board (RSAB), which this document establishes.)</t> RFC Series Approval Board (RSAB), which this document establishes.)</t>
</section> </section>
<section anchor="editorial-stream-1"> <section anchor="editorial-stream-1">
<name>Editorial Stream</name> <name>Editorial Stream</name>
<t>This document creates the Editorial Stream in addition to the streams <t>This document creates the Editorial Stream in addition to the streams
already described in <xref target="RFC8729"/>.</t> already described in <xref target="RFC8729"/>.</t>
</section> </section>
</section> </section>
<section anchor="security-considerations"> <section anchor="security-considerations">
skipping to change at line 1117 skipping to change at line 1118
<t>This document does not create a new registry nor does it register any <t>This document does not create a new registry nor does it register any
values in existing registries, and no IANA action is required.</t> values in existing registries, and no IANA action is required.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references> <references>
<name>References</name> <name>References</name>
<references> <references>
<name>Normative References</name> <name>Normative References</name>
<referencegroup anchor="BCP9" target="https://www.rfc-editor.org/info/bc p9"> <referencegroup anchor="BCP9" target="https://www.rfc-editor.org/info/bc p9">
<!-- reference.RFC.2026.xml --> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2026.
<reference anchor="RFC2026" target="https://www.rfc-editor.org/info/rfc2026"> xml"/>
<front> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5657.
<title>The Internet Standards Process -- Revision 3</title> xml"/>
<author fullname="S. Bradner" initials="S." surname="Bradner"> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6410.
<organization/> xml"/>
</author> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7100.
<date month="October" year="1996"/> xml"/>
<abstract> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7127.
<t>This memo documents the process used by the Internet communit xml"/>
y for the standardization of protocols and procedures. It defines the stages in <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7475.
the standardization process, the requirements for moving a document between sta xml"/>
ges and the types of documents used during this process. This document specifies <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8789.
an Internet Best Current Practices for the Internet Community, and requests dis xml"/>
cussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="9"/>
<seriesInfo name="RFC" value="2026"/>
<seriesInfo name="DOI" value="10.17487/RFC2026"/>
</reference>
<!-- reference.RFC.5657.xml -->
<reference anchor="RFC5657" target="https://www.rfc-editor.org/info/rfc5657">
<front>
<title>Guidance on Interoperation and Implementation Reports for A
dvancement to Draft Standard</title>
<author fullname="L. Dusseault" initials="L." surname="Dusseault">
<organization/>
</author>
<author fullname="R. Sparks" initials="R." surname="Sparks">
<organization/>
</author>
<date month="September" year="2009"/>
<abstract>
<t>Advancing a protocol to Draft Standard requires documentation
of the interoperation and implementation of the protocol. Historic reports hav
e varied widely in form and level of content and there is little guidance availa
ble to new report preparers. This document updates the existing processes and p
rovides more detail on what is appropriate in an interoperability and implementa
tion report. This document specifies an Internet Best Current Practices for th
e Internet Community, and requests discussion and suggestions for improvements.<
/t>
</abstract>
</front>
<seriesInfo name="BCP" value="9"/>
<seriesInfo name="RFC" value="5657"/>
<seriesInfo name="DOI" value="10.17487/RFC5657"/>
</reference>
<!-- reference.RFC.6410.xml -->
<reference anchor="RFC6410" target="https://www.rfc-editor.org/info/rfc6410">
<front>
<title>Reducing the Standards Track to Two Maturity Levels</title>
<author fullname="R. Housley" initials="R." surname="Housley">
<organization/>
</author>
<author fullname="D. Crocker" initials="D." surname="Crocker">
<organization/>
</author>
<author fullname="E. Burger" initials="E." surname="Burger">
<organization/>
</author>
<date month="October" year="2011"/>
<abstract>
<t>This document updates the Internet Engineering Task Force (IE
TF) Standards Process defined in RFC 2026. Primarily, it reduces the Standards
Process from three Standards Track maturity levels to two. This memo documents a
n Internet Best Current Practice.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="9"/>
<seriesInfo name="RFC" value="6410"/>
<seriesInfo name="DOI" value="10.17487/RFC6410"/>
</reference>
<!-- reference.RFC.7100.xml -->
<reference anchor="RFC7100" target="https://www.rfc-editor.org/info/rfc7100">
<front>
<title>Retirement of the "Internet Official Protocol Standards" Su
mmary Document</title>
<author fullname="P. Resnick" initials="P." surname="Resnick">
<organization/>
</author>
<date month="December" year="2013"/>
<abstract>
<t>This document updates RFC 2026 to no longer use STD 1 as a su
mmary of "Internet Official Protocol Standards". It obsoletes RFC 5000 and requ
ests the IESG to move RFC 5000 (and therefore STD 1) to Historic status.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="9"/>
<seriesInfo name="RFC" value="7100"/>
<seriesInfo name="DOI" value="10.17487/RFC7100"/>
</reference>
<!-- reference.RFC.7127.xml -->
<reference anchor="RFC7127" target="https://www.rfc-editor.org/info/rfc7127">
<front>
<title>Characterization of Proposed Standards</title>
<author fullname="O. Kolkman" initials="O." surname="Kolkman">
<organization/>
</author>
<author fullname="S. Bradner" initials="S." surname="Bradner">
<organization/>
</author>
<author fullname="S. Turner" initials="S." surname="Turner">
<organization/>
</author>
<date month="January" year="2014"/>
<abstract>
<t>RFC 2026 describes the review performed by the Internet Engin
eering Steering Group (IESG) on IETF Proposed Standard RFCs and characterizes th
e maturity level of those documents. This document updates RFC 2026 by providin
g a current and more accurate characterization of Proposed Standards.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="9"/>
<seriesInfo name="RFC" value="7127"/>
<seriesInfo name="DOI" value="10.17487/RFC7127"/>
</reference>
<!-- reference.RFC.7475.xml -->
<reference anchor="RFC7475" target="https://www.rfc-editor.org/info/rfc7475">
<front>
<title>Increasing the Number of Area Directors in an IETF Area</ti
tle>
<author fullname="S. Dawkins" initials="S." surname="Dawkins">
<organization/>
</author>
<date month="March" year="2015"/>
<abstract>
<t>This document removes a limit on the number of Area Directors
who manage an Area in the definition of "IETF Area". This document updates RFC
2026 (BCP 9) and RFC 2418 (BCP 25).</t>
</abstract>
</front>
<seriesInfo name="BCP" value="9"/>
<seriesInfo name="RFC" value="7475"/>
<seriesInfo name="DOI" value="10.17487/RFC7475"/>
</reference>
<!-- reference.RFC.8789.xml -->
<reference anchor="RFC8789" target="https://www.rfc-editor.org/info/rfc8789">
<front>
<title>IETF Stream Documents Require IETF Rough Consensus</title>
<author fullname="J. Halpern" initials="J." role="editor" surname=
"Halpern">
<organization/>
</author>
<author fullname="E. Rescorla" initials="E." role="editor" surname
="Rescorla">
<organization/>
</author>
<date month="June" year="2020"/>
<abstract>
<t>This document requires that the IETF never publish any IETF S
tream RFCs without IETF rough consensus. This updates RFC 2026.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="9"/>
<seriesInfo name="RFC" value="8789"/>
<seriesInfo name="DOI" value="10.17487/RFC8789"/>
</reference>
</referencegroup> </referencegroup>
<referencegroup anchor="BCP78" target="https://www.rfc-editor.org/info/b cp78"> <referencegroup anchor="BCP78" target="https://www.rfc-editor.org/info/b cp78">
<!-- reference.RFC.5378.xml --> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5378.
<reference anchor="RFC5378" target="https://www.rfc-editor.org/info/rfc5378"> xml"/>
<front>
<title>Rights Contributors Provide to the IETF Trust</title>
<author fullname="S. Bradner" initials="S." role="editor" surname=
"Bradner">
<organization/>
</author>
<author fullname="J. Contreras" initials="J." role="editor" surnam
e="Contreras">
<organization/>
</author>
<date month="November" year="2008"/>
<abstract>
<t>The IETF policies about rights in Contributions to the IETF a
re designed to ensure that such Contributions can be made available to the IETF
and Internet communities while permitting the authors to retain as many rights a
s possible. This memo details the IETF policies on rights in Contributions to t
he IETF. It also describes the objectives that the policies are designed to mee
t. This memo obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, replac
es Section 10 of RFC 2026. This document specifies an Internet Best Current Pr
actices for the Internet Community, and requests discussion and suggestions for
improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="78"/>
<seriesInfo name="RFC" value="5378"/>
<seriesInfo name="DOI" value="10.17487/RFC5378"/>
</reference>
</referencegroup> </referencegroup>
<referencegroup anchor="BCP79" target="https://www.rfc-editor.org/info/b cp79"> <referencegroup anchor="BCP79" target="https://www.rfc-editor.org/info/b cp79">
<!-- reference.RFC.8179.xml --> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8179.
<reference anchor="RFC8179" target="https://www.rfc-editor.org/info/rfc8179"> xml"/>
<front>
<title>Intellectual Property Rights in IETF Technology</title>
<author fullname="S. Bradner" initials="S." surname="Bradner">
<organization/>
</author>
<author fullname="J. Contreras" initials="J." surname="Contreras">
<organization/>
</author>
<date month="May" year="2017"/>
<abstract>
<t>The IETF policies about Intellectual Property Rights (IPR), s
uch as patent rights, relative to technologies developed in the IETF are designe
d to ensure that IETF working groups and participants have as much information a
s possible about any IPR constraints on a technical proposal as early as possibl
e in the development process. The policies are intended to benefit the Internet
community and the public at large, while respecting the legitimate rights of IP
R holders. This document sets out the IETF policies concerning IPR related to t
echnology worked on within the IETF. It also describes the objectives that the
policies are designed to meet. This document updates RFC 2026 and, with RFC 5378
, replaces Section 10 of RFC 2026. This document also obsoletes RFCs 3979 and 4
879.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="79"/>
<seriesInfo name="RFC" value="8179"/>
<seriesInfo name="DOI" value="10.17487/RFC8179"/>
</reference>
</referencegroup> </referencegroup>
<reference anchor="RFC2418" target="https://www.rfc-editor.org/info/rfc2
418"> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2418.
<front> xml"/>
<title>IETF Working Group Guidelines and Procedures</title> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7154.
<author fullname="S. Bradner" initials="S." surname="Bradner"> xml"/>
<organization/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7322.
</author> xml"/>
<date month="September" year="1998"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7776.
<abstract> xml"/>
<t>This document describes the guidelines and procedures for forma <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7841.
tion and operation of IETF working groups. This document specifies an Internet xml"/>
Best Current Practices for the Internet Community, and requests discussion and s <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8716.
uggestions for improvements.</t> xml"/>
</abstract> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8729.
</front> xml"/>
<seriesInfo name="BCP" value="25"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8730.
<seriesInfo name="RFC" value="2418"/> xml"/>
<seriesInfo name="DOI" value="10.17487/RFC2418"/>
</reference>
<reference anchor="RFC7154" target="https://www.rfc-editor.org/info/rfc7
154">
<front>
<title>IETF Guidelines for Conduct</title>
<author fullname="S. Moonesamy" initials="S." role="editor" surname=
"Moonesamy">
<organization/>
</author>
<date month="March" year="2014"/>
<abstract>
<t>This document provides a set of guidelines for personal interac
tion in the Internet Engineering Task Force. The guidelines recognize the diver
sity of IETF participants, emphasize the value of mutual respect, and stress the
broad applicability of our work.</t>
<t>This document is an updated version of the guidelines for condu
ct originally published in RFC 3184.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="54"/>
<seriesInfo name="RFC" value="7154"/>
<seriesInfo name="DOI" value="10.17487/RFC7154"/>
</reference>
<reference anchor="RFC7322" target="https://www.rfc-editor.org/info/rfc7
322">
<front>
<title>RFC Style Guide</title>
<author fullname="H. Flanagan" initials="H." surname="Flanagan">
<organization/>
</author>
<author fullname="S. Ginoza" initials="S." surname="Ginoza">
<organization/>
</author>
<date month="September" year="2014"/>
<abstract>
<t>This document describes the fundamental and unique style conven
tions and editorial policies currently in use for the RFC Series. It captures t
he RFC Editor's basic requirements and offers guidance regarding the style and s
tructure of an RFC. Additional guidance is captured on a website that reflects
the experimental nature of that guidance and prepares it for future inclusion in
the RFC Style Guide. This document obsoletes RFC 2223, "Instructions to RFC Au
thors".</t>
</abstract>
</front>
<seriesInfo name="RFC" value="7322"/>
<seriesInfo name="DOI" value="10.17487/RFC7322"/>
</reference>
<reference anchor="RFC7776" target="https://www.rfc-editor.org/info/rfc7
776">
<front>
<title>IETF Anti-Harassment Procedures</title>
<author fullname="P. Resnick" initials="P." surname="Resnick">
<organization/>
</author>
<author fullname="A. Farrel" initials="A." surname="Farrel">
<organization/>
</author>
<date month="March" year="2016"/>
<abstract>
<t>IETF Participants must not engage in harassment while at IETF m
eetings, virtual meetings, or social events or while participating in mailing li
sts. This document lays out procedures for managing and enforcing this policy.<
/t>
<t>This document updates RFC 2418 by defining new working group gu
idelines and procedures. This document updates RFC 7437 by allowing the Ombudst
eam to form a recall petition without further signatories.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="25"/>
<seriesInfo name="RFC" value="7776"/>
<seriesInfo name="DOI" value="10.17487/RFC7776"/>
</reference>
<reference anchor="RFC7841" target="https://www.rfc-editor.org/info/rfc7
841">
<front>
<title>RFC Streams, Headers, and Boilerplates</title>
<author fullname="J. Halpern" initials="J." role="editor" surname="H
alpern">
<organization/>
</author>
<author fullname="L. Daigle" initials="L." role="editor" surname="Da
igle">
<organization/>
</author>
<author fullname="O. Kolkman" initials="O." role="editor" surname="K
olkman">
<organization/>
</author>
<date month="May" year="2016"/>
<abstract>
<t>RFC documents contain a number of fixed elements such as the ti
tle page header, standard boilerplates, and copyright/IPR statements. This docum
ent describes them and introduces some updates to reflect current usage and requ
irements of RFC publication. In particular, this updated structure is intended
to communicate clearly the source of RFC creation and review. This document obs
oletes RFC 5741, moving detailed content to an IAB web page and preparing for mo
re flexible output formats.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="7841"/>
<seriesInfo name="DOI" value="10.17487/RFC7841"/>
</reference>
<reference anchor="RFC8716" target="https://www.rfc-editor.org/info/rfc8
716">
<front>
<title>Update to the IETF Anti-Harassment Procedures for the Replace
ment of the IETF Administrative Oversight Committee (IAOC) with the IETF Adminis
tration LLC</title>
<author fullname="P. Resnick" initials="P." surname="Resnick">
<organization/>
</author>
<author fullname="A. Farrel" initials="A." surname="Farrel">
<organization/>
</author>
<date month="February" year="2020"/>
<abstract>
<t>The IETF Anti-Harassment Procedures are described in RFC 7776.<
/t>
<t>The IETF Administrative Oversight Committee (IAOC) has been rep
laced by the IETF Administration LLC, and the IETF Administrative Director has b
een replaced by the IETF LLC Executive Director. This document updates RFC 7776
to amend these terms.</t>
<t>RFC 7776 contained updates to RFC 7437. RFC 8713 has incorpora
ted those updates, so this document also updates RFC 7776 to remove those update
s.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="25"/>
<seriesInfo name="RFC" value="8716"/>
<seriesInfo name="DOI" value="10.17487/RFC8716"/>
</reference>
<reference anchor="RFC8729" target="https://www.rfc-editor.org/info/rfc8
729">
<front>
<title>The RFC Series and RFC Editor</title>
<author fullname="R. Housley" initials="R." role="editor" surname="H
ousley">
<organization/>
</author>
<author fullname="L. Daigle" initials="L." role="editor" surname="Da
igle">
<organization/>
</author>
<date month="February" year="2020"/>
<abstract>
<t>This document describes the framework for an RFC Series and an
RFC Editor function that incorporate the principles of organized community invol
vement and accountability that has become necessary as the Internet technical co
mmunity has grown, thereby enabling the RFC Series to continue to fulfill its ma
ndate. This document obsoletes RFC 4844.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8729"/>
<seriesInfo name="DOI" value="10.17487/RFC8729"/>
</reference>
<reference anchor="RFC8730" target="https://www.rfc-editor.org/info/rfc8
730">
<front>
<title>Independent Submission Editor Model</title>
<author fullname="N. Brownlee" initials="N." role="editor" surname="
Brownlee">
<organization/>
</author>
<author fullname="B. Hinden" initials="B." role="editor" surname="Hi
nden">
<organization/>
</author>
<date month="February" year="2020"/>
<abstract>
<t>This document describes the function and responsibilities of th
e RFC Independent Submission Editor (ISE). The Independent Submission stream is
one of the stream producers that create draft RFCs, with the ISE as its stream a
pprover. The ISE is overall responsible for activities within the Independent Su
bmission stream, working with draft editors and reviewers, and interacts with th
e RFC Production Center and Publisher, and the RFC Series Editor (RSE). The ISE
is appointed by the IAB, and also interacts with the IETF Administration Limited
Liability Company (LLC).</t>
<t>This version obsoletes RFC 6548 to replace all references to th
e Internet Administrative Support Activity (IASA) and related structures with th
ose defined by the IASA 2.0 structure.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8730"/>
<seriesInfo name="DOI" value="10.17487/RFC8730"/>
</reference>
</references> </references>
<references> <references>
<name>Informative References</name> <name>Informative References</name>
<reference anchor="I-D.draft-carpenter-rfced-iab-charter" target="https:
//www.ietf.org/archive/id/draft-carpenter-rfced-iab-charter-08.txt">
<front>
<title>IAB Charter Update for RFC Editor Model</title>
<author fullname="Brian E. Carpenter">
<organization>The University of Auckland</organization>
</author>
<date day="15" month="March" year="2022"/>
<abstract>
<t> This document updates the IAB Charter (RFC 2850) to be consi
stent
with version 3 of the RFC Editor Model (draft-iab-rfcefdp-rfced-
model).
</t> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2850.
</abstract> xml"/>
</front> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5620.
<seriesInfo name="Internet-Draft" value="draft-carpenter-rfced-iab-cha xml"/>
rter-08"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6635.
</reference> xml"/>
<reference anchor="RFC2850" target="https://www.rfc-editor.org/info/rfc2 <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7991.
850"> xml"/>
<front> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8700.
<title>Charter of the Internet Architecture Board (IAB)</title> xml"/>
<author> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8711.
<organization>Internet Architecture Board</organization> xml"/>
</author> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8728.
<author fullname="B. Carpenter" initials="B." role="editor" surname= xml"/>
"Carpenter"> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8874.
<organization/> xml"/>
</author>
<date month="May" year="2000"/> <!-- [I-D.draft-carpenter-rfced-iab-charter] RFC 9283 -->
<abstract>
<t>This memo documents the composition, selection, roles, and orga <reference anchor="RFC9283" target="https://www.rfc-editor.org/info/rfc9283">
nization of the Internet Architecture Board. It replaces RFC 1601. This docume <front>
nt specifies an Internet Best Current Practices for the Internet Community, and <title>IAB Charter Update for RFC Editor Model</title>
requests discussion and suggestions for improvements.</t> <author fullname="Brian E. Carpenter" initials="B" surname="Carpenter" role="edi
</abstract> tor">
</front> <organization>The University of Auckland</organization>
<seriesInfo name="BCP" value="39"/> </author>
<seriesInfo name="RFC" value="2850"/> <date month="June" year="2022"/>
<seriesInfo name="DOI" value="10.17487/RFC2850"/> </front>
</reference> <seriesInfo name="BCP" value="39"/>
<reference anchor="RFC5620" target="https://www.rfc-editor.org/info/rfc5 <seriesInfo name="RFC" value="9283"/>
620"> <seriesInfo name="DOI" value="10.17487/RFC9283"/>
<front> </reference>
<title>RFC Editor Model (Version 1)</title>
<author fullname="O. Kolkman" initials="O." role="editor" surname="K
olkman">
<organization/>
</author>
<author>
<organization>IAB</organization>
</author>
<date month="August" year="2009"/>
<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="RFC6635" target="https://www.rfc-editor.org/info/rfc6
635">
<front>
<title>RFC Editor Model (Version 2)</title>
<author fullname="O. Kolkman" initials="O." role="editor" surname="K
olkman">
<organization/>
</author>
<author fullname="J. Halpern" initials="J." role="editor" surname="H
alpern">
<organization/>
</author>
<author>
<organization>IAB</organization>
</author>
<date month="June" year="2012"/>
<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="RFC7991" target="https://www.rfc-editor.org/info/rfc7
991">
<front>
<title>The "xml2rfc" Version 3 Vocabulary</title>
<author fullname="P. Hoffman" initials="P." surname="Hoffman">
<organization/>
</author>
<date month="December" year="2016"/>
<abstract>
<t>This document defines the "xml2rfc" version 3 vocabulary: an XM
L-based language used for writing RFCs and Internet-Drafts. It is heavily deriv
ed from the version 2 vocabulary that is also under discussion. This document o
bsoletes the v2 grammar described in RFC 7749.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="7991"/>
<seriesInfo name="DOI" value="10.17487/RFC7991"/>
</reference>
<reference anchor="RFC8700" target="https://www.rfc-editor.org/info/rfc8
700">
<front>
<title>Fifty Years of RFCs</title>
<author fullname="H. Flanagan" initials="H." role="editor" surname="
Flanagan">
<organization/>
</author>
<date month="December" year="2019"/>
<abstract>
<t>This RFC marks the fiftieth anniversary for the RFC Series. It
includes both retrospective material from individuals involved at key inflection
points as well as a review of the current state of affairs. It concludes with t
houghts on possibilities for the next fifty years for the Series. This document
updates the perspectives offered in RFCs 2555 and 5540.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8700"/>
<seriesInfo name="DOI" value="10.17487/RFC8700"/>
</reference>
<reference anchor="RFC8711" target="https://www.rfc-editor.org/info/rfc8
711">
<front>
<title>Structure of the IETF Administrative Support Activity, Versio
n 2.0</title>
<author fullname="B. Haberman" initials="B." surname="Haberman">
<organization/>
</author>
<author fullname="J. Hall" initials="J." surname="Hall">
<organization/>
</author>
<author fullname="J. Livingood" initials="J." surname="Livingood">
<organization/>
</author>
<date month="February" year="2020"/>
<abstract>
<t>The IETF Administrative Support Activity (IASA) was originally
established in 2005. In the years since then, the needs of the IETF evolved in w
ays that required changes to its administrative structure. The purpose of this R
FC is to document and describe the IETF Administrative Support Activity, version
2.0 (IASA 2.0). It defines the roles and responsibilities of the IETF Administr
ation LLC Board (IETF LLC Board), the IETF Executive Director, and the Internet
Society in the fiscal and administrative support of the IETF standards process.
It also defines the membership and selection rules for the IETF LLC Board.</t>
<t>This document obsoletes RFC 4071, RFC 4333, and RFC 7691.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="101"/>
<seriesInfo name="RFC" value="8711"/>
<seriesInfo name="DOI" value="10.17487/RFC8711"/>
</reference>
<reference anchor="RFC8728" target="https://www.rfc-editor.org/info/rfc8
728">
<front>
<title>RFC Editor Model (Version 2)</title>
<author fullname="O. Kolkman" initials="O." role="editor" surname="K
olkman">
<organization/>
</author>
<author fullname="J. Halpern" initials="J." role="editor" surname="H
alpern">
<organization/>
</author>
<author fullname="R. Hinden" initials="R." role="editor" surname="Hi
nden">
<organization/>
</author>
<date month="February" year="2020"/>
<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 Administration Limited Liability Company and the
RSOC. This document reflects the experience gained with "RFC Editor Model (Ver
sion 1)", documented in RFC 5620; and obsoletes RFC 6635 to replace all referenc
es to the IETF Administrative Support Activity (IASA) and related structures wit
h those defined by the IASA 2.0 Model.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8728"/>
<seriesInfo name="DOI" value="10.17487/RFC8728"/>
</reference>
<reference anchor="RFC8874" target="https://www.rfc-editor.org/info/rfc8
874">
<front>
<title>Working Group GitHub Usage Guidance</title>
<author fullname="M. Thomson" initials="M." surname="Thomson">
<organization/>
</author>
<author fullname="B. Stark" initials="B." surname="Stark">
<organization/>
</author>
<date month="August" year="2020"/>
<abstract>
<t>This document provides a set of guidelines for working groups t
hat choose to use GitHub for their work.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8874"/>
<seriesInfo name="DOI" value="10.17487/RFC8874"/>
</reference>
<reference anchor="STYLEGUIDE" target="https://www.rfc-editor.org/styleg uide/"> <reference anchor="STYLEGUIDE" target="https://www.rfc-editor.org/styleg uide/">
<front> <front>
<title>Style Guide</title> <title>Style Guide</title>
<author> <author>
<organization>RFC Editor</organization> <organization>RFC Editor</organization>
</author> </author>
<date year="2021" month="October" day="26"/>
</front> </front>
</reference> </reference>
</references> </references>
</references> </references>
<section numbered="false" anchor="acknowledgments">
<section numbered="false">
<name>IAB Members at the Time of Approval</name>
<t>
Internet Architecture Board members at the time this document was
approved for publication were:
</t>
<ul empty="true" spacing="compact" bare="false">
<li>
<t><contact fullname="Jari Arkko"/></t>
</li>
<li>
<t><contact fullname="Deborah Brungard"/></t>
</li>
<li>
<t><contact fullname="Lars Eggert"/></t>
</li>
<li>
<t><contact fullname="Wes Hardaker"/></t>
</li>
<li >
<t><contact fullname="Cullen Jennings"/></t>
</li>
<li>
<t><contact fullname="Mallory Knodel"/></t>
</li>
<li>
<t><contact fullname="Mirja Kühlewind"/></t>
</li>
<li>
<t><contact fullname="Zhenbin Li"/></t>
</li>
<li>
<t><contact fullname="Tommy Pauly"/></t>
</li>
<li>
<t><contact fullname="David Schinazi"/></t>
</li>
<li>
<t><contact fullname="Russ White"/></t>
</li>
<li>
<t><contact fullname="Qin Wu"/></t>
</li>
<li>
<t><contact fullname="Jiankang Yao"/></t>
</li>
</ul>
<t>This document is the product of the IAB's RFC Editor Future Development
Program. The RFC Editor Future Development Program allowed for open
participation and used a rough consensus model for decision making.
</t>
</section>
<section numbered="false" anchor="acknowledgments">
<name>Acknowledgments</name> <name>Acknowledgments</name>
<t>Portions of this document were borrowed from <xref target="RFC5620"/>, <t>Portions of this document were borrowed from <xref target="RFC5620"/>,
<xref target="RFC6635"/>, <xref target="RFC8728"/>, <xref target="RFC8729"/>, th e Frequently Asked <xref target="RFC6635"/>, <xref target="RFC8728"/>, <xref target="RFC8729"/>, th e Frequently Asked
Questions of the IETF Trust, and earlier proposals Questions of the IETF Trust, and earlier proposals
submitted within the IAB's RFC Editor Future Development Program submitted within the IAB's RFC Editor Future Development Program
by Martin Thomson, Brian Carpenter, and Michael StJohns. Thanks by <contact fullname="Brian Carpenter"/>, <contact fullname="Michael StJohns"/>,
to Eliot Lear and Brian Rosen in their role as chairs of the Program and <contact fullname="Martin Thomson"/>. Thanks
to <contact fullname="Eliot Lear"/> and <contact fullname="Brian Rosen"/> in the
ir role as chairs of the Program
for their leadership and assistance. Thanks also for feedback and for their leadership and assistance. Thanks also for feedback and
proposed text to proposed text to
Jari Arkko, <contact fullname="Jari Arkko"/>,
Sarah Banks, <contact fullname="Sarah Banks"/>,
Carsten Bormann, <contact fullname="Carsten Bormann"/>,
Scott Bradner, <contact fullname="Scott Bradner"/>,
Nevil Brownlee, <contact fullname="Nevil Brownlee"/>,
Ben Campbell, <contact fullname="Ben Campbell"/>,
Jay Daley, <contact fullname="Jay Daley"/>,
Martin Duerst (note: replace "ue" with U+00FC before publication), <contact fullname="Martin Dürst"/>,
Wesley Eddy, <contact fullname="Wesley Eddy"/>,
Lars Eggert, <contact fullname="Lars Eggert"/>,
Adrian Farrel, <contact fullname="Adrian Farrel"/>,
Stephen Farrell, <contact fullname="Stephen Farrell"/>,
Sandy Ginoza, <contact fullname="Sandy Ginoza"/>,
Bron Gondwana, <contact fullname="Bron Gondwana"/>,
Joel Halpern, <contact fullname="Joel Halpern"/>,
Wes Hardaker, <contact fullname="Wes Hardaker"/>,
Bob Hinden, <contact fullname="Bob Hinden"/>,
Russ Housley, <contact fullname="Russ Housley"/>,
Christian Huitema, <contact fullname="Christian Huitema"/>,
Ole Jacobsen, <contact fullname="Ole Jacobsen"/>,
Sheng Jiang, <contact fullname="Sheng Jiang"/>,
Benjamin Kaduk, <contact fullname="Benjamin Kaduk"/>,
John Klensin, <contact fullname="John Klensin"/>,
Murray Kucherawy, <contact fullname="Murray Kucherawy"/>,
Mirja Kuehlewind, <contact fullname="Mirja Kühlewind"/>,
Ted Lemon, <contact fullname="Ted Lemon"/>,
John Levine, <contact fullname="John Levine"/>,
Lucy Lynch, <contact fullname="Lucy Lynch"/>,
Jean Mahoney, <contact fullname="Jean Mahoney"/>,
Andrew Malis, <contact fullname="Andrew Malis"/>,
Larry Masinter, <contact fullname="Larry Masinter"/>,
S. Moonesamy, <contact fullname="S. Moonesamy"/>,
Russ Mundy, <contact fullname="Russ Mundy"/>,
Mark Nottingham, <contact fullname="Mark Nottingham"/>,
Tommy Pauly, <contact fullname="Tommy Pauly"/>,
Colin Perkins, <contact fullname="Colin Perkins"/>,
Julian Reschke, <contact fullname="Julian Reschke"/>,
Eric Rescorla, <contact fullname="Eric Rescorla"/>,
Alvaro Retana, <contact fullname="Alvaro Retana"/>,
Adam Roach, <contact fullname="Adam Roach"/>,
Dan Romascanu, <contact fullname="Dan Romascanu"/>,
Alice Russo, <contact fullname="Doug Royer"/>,
Doug Royer, <contact fullname="Alice Russo"/>,
Rich Salz, <contact fullname="Rich Salz"/>,
John Scudder, <contact fullname="John Scudder"/>,
Stig Venaas, <contact fullname="Stig Venaas"/>,
Tim Wicinski, <contact fullname="Tim Wicinski"/>,
and Nico Williams.</t> and <contact fullname="Nico Williams"/>.</t>
</section> </section>
</back> </back>
<!-- ##markdown-source:
H4sIABxDMmIAA71923LcRpbge34FQnow2Vssi5Stm2M3hqJoWz2SrRHl9k50
TGxkVWWRaFUB1biQqlb43/dcM08CKEo9s7P90BZJIJF58tyvJycnriu7TXhR
PHj/40VxuSq7uine1quwKY7+Epq2rKvi8fED5xeLJtxOPPbArepl5bewxKrx
6+6k9IuTZr0M69WO/rs62eJzJ6eP3dJ34bpu9i+KslrXrl609SZ0oX1RPHt6
9sz1u5Wnn54+++50hr97jv//+JErd82Lomv6tjt79Oj5ozPnm+BfFK+rLjRV
6NzHsL+rm1X6zckr3ItrO1+t/o/f1BVsbx9atytfFH/t6uWsaOuma8K6hX/t
t/iP/3DO991N3bxwxYkr4H9NjYAJdFj6RVnB5t7NiytfVt3JebVqAv2ej/8O
jtKM/ha2vty8KNpuh3/+F/nvvNw6V9XN1nflbYAvFi8v3j2X/z59pv+g3wDE
z747fSb/fHr6/Xf6z8dnZ/rPp0+f6D8BePLPZ09Pn8R/nj2P/3z86IVzeAXm
+69PXs35Ape+2QWEo1wfXujyxjfwG93Os+8fyT+/f3Km/3zy5PH3uofnz9Me
Hj1K20m/PdMDPXv2lA509eHf31z+9NvrV5cvCHCCl1fdfhOKn/pyxfBEFHlR
nD06Oz05fXRy9oSf9c116F4UN123a198++3d3d0cNn/Cdzevm+tvW1znGpf5
ll6Jdw3/OyngCV+V/wBo1NWLIuG4c+7k5KTwi7Zr/LJz7sNN2RaA8f0WQFS0
u7As12Voi1ullaJeF91NKIZ0Mi8+wG+ZstwqrMsK3uru6uKmvL452YRb+H3n
249t0YQNnHFVdHVc6Co08JF58WPZtN2s2NWbcrmXZUrccwG7wof/VgP2wQrt
rq7aclFuym5vd8QLFb/Xzceyui5+aup+V7ij91e//3Q8K+5uyuVNsWvqVb+E
p+Qz8POubv0GSAWoabjU+Q7+fuvhUC9r36wKWOv8ZVzL01/hsbbnlXklIKGw
rKtVOkq53W0CwtTrcXZNufVNudnTFw8f6R1tl95yF4S3sId3F8eFbwv4Bt1b
7zewTo2XFEJVLHjN15cffizOV1uAIV4vLuHelNsSgf8GsJ4/dVFvd77aF0f0
+Js3F8dzoJaq8KsVgX5W3MI2674tXLZJBI5s0zLNH/uKNvugAB5WVPVdsQsN
UiJ8lBiVg4fKCra+XZQVQ0P2i7c0KxC+8P/vLmb2Gi7gu/2mw0uVD+GtXlwe
86Xp3hGFKgTGDFa0mByAVS42ZXsTGJF4kRLv9Qr4pN8WsMdi18MzS94UnG3d
dz0cQu7QYKMu2yoyrQrX3QCyXd/Q6vBbQLAWvsWUsCpuQhPKaj4ksCgi6KzI
NZCO7BMiNOjvJDecPPmcT84/PX40Z0relqvVJjj3EEVFxBz8LMA3/L0HONBJ
4db5AEewwLFCWajMN8ubEnG+pV8DHa4QKkyzujO8ChVHRReWNxU8s1GWwUBs
Z8CGl5t+hQ9fhyo08AQhbbno6YFi3dRbxlZdC7As4A7weC5U1wA/2AYsACiz
7SvEWUD9u7DZ4H9JBAJhJpAB9cGZWsI/529BPMHNB/hQCHipyOqvA54EsB7w
sbgtfbaBeXGO99YuYZNhBQcoPn8WRv/HHzNe+8bfhmKBtEYoA2i1onOVFZNi
C8cOxenzJ8/hXuJuGAIIR7w54R0rRP8t4jZwCMN6CSvhLO53xB3PN8O/lVcR
Jot6tdf9nT3/4w+63OABevJoaekWwQB/x5Vwt4SBSMJevzcb8nYlZ+BgbTG1
zi6xJzzUClmNXC6uDdAgiME5EAXXdQ/b+wQP4ebljASbCPAiARwPJPTgImCA
L8EbxbpcdzfZrhNJX8lvByTtYD9Ey4jq18gtK9zFgOF7XP3uBshyzmSDD+Ix
1g2oQaCGfYxnt28ZySGiNYKubA+ejt6DvzOVr5gT2uOqoFGJ+hVy2P1WrULD
68jjiYcfYuFmmbRxvJcB9y4Oc+8IDJeLX5W+VqiubktQUPdFLlPhCWfEnZV2
XxAGVha4CblXfI3c04s5PUU6dwz4Zb3ZhCVqkUDWcGwQ2204RCWsBJVMWUgx
wGUC7BXg2IJyD6ozsaKtp0c88gjccdvvdqCuTygybuFb2DUcgGkN2AqyCbq2
8AnupityzWJWLDfAPeETlb+mXwMPJLpswpIfiLwHlgOkM2y1rHZ9lxPfYYGl
jz0DLF6odIQbSRjq7lEVp0QcrYgyDlZ0dslFXW5Cs0O1ESTNpy4S4JDkR8wi
W1pIDlZuAiy2tMQv+0OTyN2V3c1IISFZC0h27+ZREP/xh6MvbJlB4zqrAAbH
KlSgRABglnBrgACJFamWLeQf3Ovzl1G2CyIkPL8E/extTRwTltkQSxFLB0l2
UcMVgoyrroMIV6c3cqYIxlr60gPtEkuGT/XEMz5/ljfh6lGH+BVevS3DXfbi
ECVW5S1YHe1YjcV9T7BKkKio+k+YBmC1nc6LdyN1K+fVYz7NV1K27l4T4Q5p
saNtRUvjgN3gLOdC/gygquEOizt54Jr+XlZ6s5F2iZmQQHUq7ceGRjIPDhkb
li8SI4ENAM3i0RBNUOjTRw7YHyNlFrWYQwQTCMMLVtQCiogdqmDEUG6ThHAq
rTPxlRQx2KFypMrog6IfAdBmhRsc9xAfB9w7i3gwsJxUzR6o6qRjwYdRUA83
TJBCEjHoE3HmfjvMTRti/5wd9v9EIAFMrFpabJEFrHv8ntxtg64YImPatCHR
mWh8TXAeRRmTJnKYEb2iyPeIP5tNfYcE+SfBkN9/EvRSfC6DQJap87AaBSoM
MFRXiHiJCn+UO0IGkc3yT8Bq48cBPZe4TTgcfhQ2YXAdXwnwBTh4JAf4aYuq
ShPAggMrA75Ov1KfAzF2FvBbD+q3/4jAbGgRZZ70OnDxwK/ivmGZ+JTsh24T
d/p6HTX62ZAcSZGKhoJvI7pmNIlOItHvCQq9mo8s/CPQa2bbeENRZlhZhX4n
AJ/IrHcXCY4XlwUZDkjmQqweVLFliIB5dyGSDkAOWHoD9jv8KdIgLJ0s6VXa
E2n/8P/XNRIzrgDskmEDPACUmLJVeKPYEV4DqzW+bPGVsm17hjkxfU9MQRBu
pQxUbwbxSYCHx47ng83HnbY50NQOF2gN+SDeRdm1Dv1v+5OuPoH/kGdUjzPF
bgiTDcNRk42RQU7kSV+MKsWAm6FF4puuXPYbUNp0tzO9C9jPAk1fRXpZM2Ix
UgxDFQVDA3x7eG7au1w5kSA8Vm4LdBSS+pnufSZ6RNSKkOTpZPRlXZ/tenVk
kOtbDJzyumIPgWi8DDLjC6G9iHBXW33mWF/dkHUDnxswYFJWyZXJjKLxVQsQ
Q4m7DYgPZbtlcaeKGL6hiAKbUUi4rzD4mGLCes0Kf4bD44tDTS0tM2OC3YbQ
6Tea8Pce1G7GxqTkAapdsS5efIfrWH2bLc7DnDwKAL5mAT9oSIB5KJFYJyTd
TcTnq6hGOffunzB+xShnqrG+LcecB182+pvcsmhwkfFtwepBbtX2CxB37EEC
KK/qHVu7M3UaLPsWCd1SNhiDk+5c1spER8i/tPMtHmDj4d9LstnrhuQMXYEs
nOtwZDF6YwSN3zsCYY6q8Xr5xx/HaBI9njqided8jVo3N/fRi8WORJMp3ESE
kSFvAd6dMs9ZsQBpCrfkqroD+mF1AsEbkYXNAkDNRINDxRB9bAD+NmzVnBfu
xjejvg9jTo6MVMS2h8hHQTlCuqftAga1+PuHh93yol1/fnh3/Qc9CjjbN8jw
xV35hRfFWcn62x7szqpHPiUM0W3DdoHqguzXXDDgL5hJqJoDpV3DjSgh5HqN
m1Rs8P55r8S3yx1D7fPDnf0ZDnS+2TDXBIFJVE92Uq/qAKjNsCViwOnNUBix
5o6Aav4GnIJ9lV15cuMbQHC6hcTgrVIYrbhaUJWVXNXsEWHg5xxf0ucNjZAK
ys6U9x9+nBUDYKqB+vryCpSOFXIA5JX097Zed3d4QsA02PCK/u3aPUBBdfHI
SxXTiMG3UbDS0lmkEx5y+We6ugZI9i2fgVfAT6LQlmUtyIGnFQ6ejpoXkkTP
zBkOsCxbclcX7RKYn282++iGhu+JX2nCMDLeZ94dk4iJtsFjpC/CwSs2gCJs
EbRsgKnGLwxCoD3D5ddrlmhiYQCY3FEgYUK2xgFjbdJeOU7qNZskl5/CsidJ
94rcQwA+vKyyuh3hRhfYzlEiiuRlEFaVifCJ/F9wU8LzFyjHca8gKwDL0nGd
ovG8eJtjGPE7MkY2bU266nJiS2zOhM1+LkR5cePBsBf+gVtqb5B9kbseHQBL
+vusQE+msac1Xnb1k0LI1WpQDJ45fzkvfr8J5tQlcdVtEHOePuGmF+fdtKG5
ZQe6B0MZzFI4M27o6PS42KMyhEw5LjW5h3tWwmMenR07XKn9AV8A3WANf53J
6b/2XbbbgFvwn4ljkKYP2le48xtFXQFa3BUQKr4gdgscoL6rBhII7C3huW28
B1YH5U+ONEjEJ7TM/HJZ9yx6EI92NeJXyaGkNSBQR2ijzHbuLiKaKpYi+RMS
wBvLgBYhO8qI67OHm9Rh+oKja2Xgtzd1v1H3qZxnHcJq4ZcfFd+tM1UOQ04k
ctNgdMloqmQYwh/I78f3QIohUAjvpitRKNzwTy5HsEMQF/wmCXaHvKY2lmuG
jIIBXo+Cmhco9aQJdARc/L7wiZoSPwrv2F3KvBIhaRFowvOArL+8xjgsf++b
1iFCAI2+7lRqT8e7ZXtkQ8CVN6BzFKx5ormNdkXrBsafbpW1UoZcfFi4Ex5U
WLzg18ytydRE/r20agCgWth1iguA5wNHA5jL+EfRhFz6o7HJlBmhtxRX+VXN
COZLEh4o23jNllWxzUGKAGjiHkOJ2xKNQ/qAJyJQDdaRCpsJbUKRJsDp8BZh
PUYhMUtaq24jNEhpUkxcBHZyojzNlRdnRKkEEDCuR2SSRXPjQkZ1wXUohtJj
tB0hFppub4xd8cOIHk2OlZZAJFYz2p/WvQqCyGXm1OfPlFUk4TT+ia2pg5wa
t5ngoBsnbkO4zh4NR/CgFCcLtU3ZxsBcPDFr1SCSOXqO1GrkEHw6bIk6WYqB
loFbP0F1BoMydYUW8An8B2wi1Jz2YPiv4r3NnH6N2BGaG1UFPHEpNhPAe71G
cALUQL0Tj07gcNOiqf3KZfopyYXir8RKflJfAJzsRzg6uj/wvwTMv5QN3dtr
dhy4t7Kh/ziyuUhl6NaUhURc9VtGy2/hcjEvCbCZePu34nw40UOdqBfi5OzR
6ZOTR6cnp0++PSYUYReVLzDwXcspfBsQRnPYi4AtobXARf1KtAJdFYXDk0FP
UC4yUEiIApGs5y91tfOgt1SEW/yl+UilUDrFWE/OoQC5yDAnsR5JX4I0qLON
g8GY/xatfyZYvyeetZr6At4t6rKaogP3g+owsYSjML+ez4qfyu7nfkEJEjml
SEYamAcUH9+S6BS9bikhRIoYKpPZBgAOKLiyMDt6QCXw25Z835sa2SZx9T1p
bIaANZRmPRi0Nv7anJz8fh1JR9QSQMlFd/eiNTloy+SzInZnl8ytuARzY0Sz
bqYpKHEpQbXMKfMkOmVkcy5RnXp9QxZClYuLai2lSlCujais/BUQJ3g6NFb1
uuCPGvwVrSO/iSi2ov40S240tr0/iEY4/ChsFbh7SNzvDnlhSYJnjdEv4YVw
dFc3K1YbGEfLfwRVNL9p2ee2ZuEeXXHkGRhGTx2Hd0d2/6T/4wsm/+Q7ydt5
IFblJOUk98jOhGbBWhBMHWbQkFskynKXEnUG2oZ4+fhC2TecqX9tIAH9AMzG
5ceWCWnhN4hr7QMN4wOLxECIwU5W7JD5i4P0RDRkikdbk4hzCppATqJhXNEk
GJmowA946ayZk55Y1VngMl2p3H9PcXZZuya/OKrwwHcRd1yyxZL2Ahu7KwHA
DVmm/Nshz1KPqaAiHCGgx7uldCK2NSh0HQiu+NGBjgjbc3JwE44ixayNYZmx
LwT52BpUQw5pk17GRoFyWw0utZ0NBgrQk7Pztu6YHdLLLwoMjZ1nWVk5MsbQ
N7EFTVQCfCGhy8u4Ajkfm5oi0iYNx6/+FFoE5kvoM/z6D52//OrvvDdHir9g
y/drvoRPk6n+1R80CGu+i3nd5i9X6GUWhU4Dyq+vLo9tcsZwd7DEeH9XlxpS
+nKwGqwadtEQf/VkM6TcuyU55sU1EAUWko7jP2Wnzy3CEtbN0S6BB21kk7en
DA6dJQtSDEyCNQdWSU6T4CVfTI8OWokOiWWeJWb7bngXogDAMcWhFQYeMUqU
0J0K/RB3ncob5H1jMnCW2gDyA4R5F9hvUa+Poxb95Zvg7+cAi1wHSAHdn6s6
sANUZIEfnlL2PUqUgF3EyBbtf1sDGiVlY+wXT2Ft4b4itQZ8paqrE97zrAif
TmrS4+vIZzQCf8hhx+AkC5chx6q9xq3oUij6LczaKiniV/F6LxPBSXUzwxKH
gkZIwwegSGFFdCIkgfTuYrBBjEpaU/id6E85yhze2n07cyaPXckBTWMKU5v7
QW0b/dIgAYxHRK0JZhfpnpJ/VmlhfG94L5vSl63mOKutTldm3cNEkqzWxP2s
AvrKQWxbjdFFA8JGMChQVaP2y4ooSbjz5FLjcAx6gzypRX/hI2Qy0Dit2DU1
K8p5mM8sa8oUJsSII3b+v0bm4hL/l3z8K8zGZKb0ZXegMxvg+xAgHgGlijfs
AJuSrAaXpxCr7G/aZaBAyKXnYg1zzP2078wl5xmiQ+JMZmMTuGK8Z8CxzocA
VQM1MhB4PkcmMp3awNnhmLSJ7ghYjV028voalSz8zq1fgk5ZSi4EezP6gJID
ZQ0IDpcwB3cH9toWrAz8kZIxkKu+Zm106dtg2EO8SMQsuMaCA0h+55dlR7tT
AXqHiQ0u2swKKthfJv3RxCFPIXFb5VKSDIYaylFSybPryZQNcYULarmRPp/O
N70MmvcxIYwhSivons0CuQCjawcmWW4kcAI/3niLGKhoDaE2Iz8pprp0pBWI
sKkKZ9GobswGjORj1ZnK5zYJ8ZW4/6J3n18h7DdhBXDbIa/KhZH6L9wg2es8
5YcZOrtHMPgNwHRFSWgA6SWyc/6AlEPQvfNRMDFG2E8tZpMwpWFWSCqrMXaM
SNECFRwAlt8ToevF8Nn3CNMEhlSmgZSDpNHvCFVhla3/VG57Cns8Lraw2Rug
ClDlVn3DkgQQ//EJ/QFRuaxXWHUgZoZ+DbVHTPAR+NK2jJOOImErPoZ8WYgj
fRKWOMfwjFlAPgeWFkj5/Opo5Qha9i0gemDmUoReFhNeBLjcefFLjXWFdCr2
6ODBb4ASyA+RQEYLqY60223I7vIJvOvEdBtKmSGrNbO3cY2hYR4q2JvUviyA
ucYwOpsByRQTuqykkGZ5UyPpeqEuTrna1mIhKu/sMYfMeXMy/Cu9C3/AejYT
X0CjU4sKHZ6L9E699aAxC4p6GdjzTlrR8NnWmd7OF/z/asfboKZ6EzFa5A96
nF058nzCBoFvYBwM1OWKUtol1C5+ehAWxk3o1PFUdqJkRDkxH13CxxB2cFzJ
4wJ9E9QMhS2hHZnqFGiXGi8HYr7vOAxNaSM27ODNEqwXSNSdvR+Sx+Emz86B
/sgM4han/O7ov9ygMwETlupduWzVnKF0LAoaliuOIKJfQewaBmyF5atbdP82
7THphRgVkTg2XTdF8ORbpM6l7CVKKyhvUREr3BXHbdCfr0lhCh1cNnxiY+Ce
LH4nu08fYL0mRCsA8JHLe9C0EeaQVCbaqS6CkYe00viyNZ6A4Y9KLuwamJeP
OfxAOfE+2ZPljO/vLiyAqjhoAPfEt2jSbVGp2QRMzPLwbPgIcEVN3NEmdV3G
BOPVt2GplLpUsHte62dcpserixZxjC0sejvz+c+VIdBbFSByi3qfgAe5jcGR
gtEBb3cC8qyceqreoY3oZScEZZTIzXG8MI144Y1pjY9joDPx6gPK2RnF6COC
Saz9YRIa1YghKsGPbojiWSYi52X8533WpD1RYkruvSY/2n+P9xr9i/8/vdeY
O0NSlTzZrylgOwreJhhpdQh8HxQKwH4pNFcdKbdYnM23NEmWlHt6W29uNdCv
0QoWFLFwnAs/yJ8QA7SE3YQPgHMH8sk0+wdjyCiziZk4UFEQMYpl2QCScTw8
miuZMYZkEkOXDy5+/eXi8v0vD5xK05YU+fv8r5jy+DIsPYauROOThGYpRVqV
aET3my6mPCEK1xhSo4S4LFMtZUVaA6prQBjD4WL+AG2Zqja7+pqsdUeh9RZ0
q5Kc8Nc1qAxrz54xJDoKeNL2Kb1L4jRgQZbhVvzaLvm1JTs0houOMUBpsrpn
EtBLu3T55ijorG5oTk7Bums49mY/mzzmYAHKoMYzf0KdqxVeHRfjP5ZaQkiI
zWyTfIXqabmNHCpmec2Lc0UnwdX8w+Lud6x/b3rSdmzxsaaboe/xhLKIbgLK
ZvrDbax8Ec6ZpZRS5qLulmxQUaV511SKulZNGCtbl+wVFP6OIIs5akltxidi
Mj4Dqe3Krme/MlwEIjd5HkgpkI4pgH/caQPVLeCCJuNxpqjaon4bUxiP84oI
JxUQrXhW7zQtgbJ9MA+0FabHoitFqNg+8jHYMWPHqBzJkfQAJtxQWSrIz7Hn
ga7NqJqxfgN2ARwCGKFLvpUOg7ioGGZRLWStYP5vyAHANsR17TXQ97sQOGby
Kq07qfZWEawXGYWiJm6mgBOmhcGO1ykzxB3sFMJp5ueVSfHE9yX6ZvM+UxFe
gqHSApWEYYMUyvoaZJwWR3laSspgR0u3ZwNX88ZwkVjiEZMPWg4kT+amHOMr
pGRhS5SoJCGfweR4XYj3y1n5eekhqPicAv/Bpgwcepk636TfZYFx9BYVRTJ9
WuOxO1rszS3mW6A7BbtJnHjstMCVIm88jn6lhvzQJklFZZfhS7S1Hwi9cBV8
3qY+BcqGGsLB5gXdEZWrKYVrjHkzJe9HkEnWD1JjDCCqDoiJUkzm2QaJJ+La
VhixPmfSci3Hnin/2aFvgB+h2+9YvFXSiwJuCqk0psDG2yIgGjelZD/SpQHx
l9cVNdyoOvjwgIRwLQr8REmGuUVgUIEatOQlsB+GX2JmDnDCZfx6KggZi3TJ
4Sq5ThjWOJS8eyhv17cZkQIOEEAGOVlE/iJ984ivVG8KXG/ChnwruIZ1sHaa
kcJlkp6z0tcmcJyLRmnVg02YUu2xcC6Kfsv3KMqmH7UftLfOLAFj4h79pHi/
qcYtymbjdsgSyKWCFdEsMn7ESPTK3IGqYhxf9FFNCCDHkUFwIWiC7peSqfNL
AUr5DnAdDo1VCiRUiFV0g6UXYUNqERO5GMysI1lWYPuFCFbXmkw545siaBGM
bAkPrpJV45iMjIwVwIa/n4srzevj6krDVP2+5EjXJlTX3c1sdBL8Pl++cj8N
7wxTGUZnoY4moDR0nLzM3FRCHTFbeIT0pFRyZrOJzurzdHB0OIg33bCbY7Jf
I0SSl7MBYw1dIKTewfsgtJDwOVdaauLS01uPVUTGOxSB3spF4hrJQVT8ShWD
U3JikHaLDnL6BC7QoEYoIfD90NugsUteSNzLpgYG72PgCkI6gBu4w7SgLouq
Zym4T2S/Jhm4zYpXB2k9mTdE0JBR+HBl2L2JJ1QvRjc1uor4fhPSnZWV6uJj
TZzl6vD7gwgmFzszTEjeW/eL8EejYqJfNe0ELR80RJCTMPslAl2pRZHhpe5Z
TR3YWNgkDegekKUtk4zv2rBZ2+SFTAWOMte5p9Fl0y5B+CiHTLtFZE7KBPwa
bQKwjXeseETgU2IM8cOE9/ddcXLmE05kTshZoVqcBVC60cm8QRPRgHM9M1Rl
mRF5cKhjARMWi4u4cpIbYxQ9Ar0rO0KieLnPnBjpIqrYH4HQKcYDI3GRg8ZL
PG2BvjU2Mva6CSG75/Pid+bQWfZu4sNcYJD8OqVqYCB/N5lXX1k/84jkZ6hz
lRE7ReifRP5kQS1Y5U/Fg3+/vHrwIufaJplaajflWfVtDJ4nSd4OKFluhgAm
tgL1XEywlkXfX178dnWpa7IXH63NVHwoUQmKLsbSFjSOC27OyRozHei8ynTM
uJBPm08L0rZA6m98LIeQfYsKmdMsPCRlxMUvaB7CXzdwECMwuQ4VdRGEnYR/
BRGDGrKS9VexSqoN4cT+pTi2YS7mLN+0yqhwhxgngp8+kHbhSdHCPm6MWVjX
g6VlGSgQBdYlFjAnCADaCVgUHz7kH1U1xiSipGvXUBZei3hmCr4TeAZOz70D
pTkW9eUQ7mSs09gb4J/9Ohs17DTTj4PGvuUNyOVpma4mHqWme/ioPjXlheFl
rCvGaP9f2O2syLpTAZD6TTdRcMvfmGRNIiXFjT6R5i4qopzWAgYY0ga4Lcb3
6E7VszjyCR7Sd0VYWItD7fiJ+qKkxqcSMurdRjp95MeUZ5ApLVjTVgMBCgIa
PpYCNkw4RPfqy1GSirICI7i4N7XkZgW5TcbLsqIPxnIb02uJxZuWFHB4ig5Q
WYDs3doRsUfgfXIFwH76iMSyj7tgRXhmdTZm8KmwZtS8A2/2/Bp400yqir7u
/ujLlhfTQqrlejJGWCWI8QHlOCOYkVJgw6TFFxQ/5oDofQOhT+G0U3RIGbKV
dGZEmPEVlW0UOcjgTs/wMLAJMV6iqTKUmtOrcfndjNv+Yt5HyAxxDBkA+Dno
FaNwzEcHOUj4Li0D0nI2Ire4Zdjx46iP2SckaUCa4JSiNaBWavO1NN+dyItB
rYkyUf2T/PdBTx788neTX05f9VQApQKHtD9jHKSmQwyuamBDUKE0y6S/96EP
44YJlMaDrkhGZKeMaSJj9PR76WJVStCXyIDLkYoSUGmF7lUMxexsQowNc1Ph
OX6Cw6XDPjTMd6WsGjY1A+tjI0J1L9ElzpShRe5uUDBGhxnG/YAgMOSEYUF2
EOEv+mYpmYVcdS6cQxy+qbz2gmxF00+2+PwQGXqe6DDK5UwdftjsqPx13t+V
bFCXURy7YrTYMnrEkG9w71WRGSP2Enei3htt5thiFNrDCyvMRgX0Yt/xru9M
VzR8qOUgNbevop4lGMTGbl7bfjtD9BLdK1Xe4ecfYIdu1doeFJLYQCZsTewo
q3jC30m/YQzWAh7Asee5S8n6n/Cro08qBMvoyqc0YdsnQAvEIhJoJ4JjkjDl
UpuA4Uc41kJ8NDXSRa1Bcy2irT5KBJjnPaTZiZHFhx0SdRU2MfxnjXO8+0q2
IzuW3Jj3V1dkaiHAFnsMP6qPsK2XFK5HspLKVnT4wj4wQa7lqhMbB7jx2i1J
C8oP+FPdV/pTDzhT3dc6U8epXswxPgEVFm7puSaeHCoFla9TalZo9gMszvEA
LRNcpucsQe5HPB2szZuY/HEsjYwJ/82iLrcAlKJCdU2hQas+KQZamuKjOYrK
RqfBoTxjZdGRYyHlsPbC7aFcimghv/JLbmMy3DOQbUt1iZynk7puaZc+bjk3
4hfUrNWTPSvZJ0zCE1DG0KxsIelVy8gjjeJ0roRLwb37NA1ar6zEB6OhGMrV
BH1Dy6yprHURgI1SGjwB9ZsLXUybfb/4Rl6jiPGMNFlUNdt+Sy10BoEHefi3
92+KGFQURjOIldHpY9P/0RLVns3PSjuiNAWlenAD8JGymReWUZpa5ogsjijf
T0zZvkX7SlNNtHAuBaeOaQ8X1GUMC/4b7onSmvZ2msch96uwl/Ovgl8RfO29
4BUOfMyk6JILlRrssBRGxeaupoynLJN7ERzyEUwrWjPxAj0zYUsqDNANKIex
TzutbtLdvoYF3y+GVddS0UufGXqY7m+NRapYprAjSkmRi2SgubQ2mVAl5lmj
zh672eGTmlzCxUuZk0rF3go5PLUaFuMiGlyy0NByw8IgDG6SKc6PYHIWY1tT
Ipf2pjyaeeAVugyfc+TWpK4UcF2raxbz1q2Q3C3WjIr+MdGYznc7sLgRafgf
lCaQmozETMgUHyeZax3axav4kK2kVHchS1BPyxNObCjxHyMj1YpeWYP8lqYq
sVcGNQVF/uximEt3mJxjtJUI2xJ7Nxw9fnSMnRJbbcnipbc0aXfcu0Zy0s1n
4aEZddVg1gf6G7F5dExeA85Vmb+aD2bUt+QolLr4MnIrSi24i04/yaWiF1j8
uKF71ZNz4S4WlsDl+Y2cQt3yQoLODSEvyTojkN8PbWfAnaKK1NzfuvE/Bi6T
kMw5a76Kqo40CSTgr8GAI/6zCN0deXeljVbsofru4oCYt6+31ArAy7XjqTCr
ZF1uEmuh7JUBW95i307pCclFELEBHgdSsQwG+Uts+NpKCyZPeYDZFkw3HuyL
3C+7USgZeaqzDdFowwlf67WKi3tpCXMNXcaHv4jfIhWSwCZtIVld9qvFUbff
oSaIqVuU5aOZmtQCtkb141ja+OBOtEKKEFrDjT7itGJRvVz2TaN4TS3UmO6c
IBRmbzH2ZoojeVyUB2EHuZ9TBznpDwkGW60G21/FIJhoNbf/zzT8GKx0wit9
e8zGBVYXlLabqWl1GPuddI0kpnG1rBiMqpFVoHLelk1dcYhCe//tQr3juvkt
AgnTCgO1DMXwjBIpKdNcncv60goVf2wyCteBvdpnTjskA4Dnqd+fBu6sX2oR
yBrFcK40oqiRpa45S5j8v9ooTvyJq7DF3LNGmkbFXCuUOXRtjtYs62Ze/Ei2
IXtCxmniTFqpnQ6YrI5b6Z9+/x3aFPzD06dP8AfOQpLhWVoTT8rDy9Rlv6Wh
Jbbvvs1z5Bb9x4zSfjC3II2zwjx803gXy1CM0YPYuqQEkuIX9jhynAAftRsx
kTN++YsTMMYdOZ2o+CYfjXMaZ5ytiC2VCHE49NIGDGl2FG/wZDENOhEQusRe
B3W2YdLMtdwQXTWobmnJ+mBoVOSodsABqigt+QZcIanpyQX/dUuIJ47mdEgU
SVpwD5/s22SusYkugYrUUvnwJ0Ghv+79deSJgy3YPjAmPW6AJba8+QNOwPu6
IwrfQzdOR3jCZ6MVvmmTipZawzRosjL51XcVINFNuTN9cl9nJW6UBE5NTOmF
d5og6dy7qb7zLVdS5c1fD/SLJ+tvDShv5iGlTuItF13Fsm99qIl7OTjBBVt3
m3TyxZ7nz7Wm8/iBKQCgJlO5LyJN9BjFyK6dggE0JpNWsMZD5/jQV+KtcckY
CckiNhRX+rplSb4PHSt+bY+h0CA1cqONyRFmWlbC/k7QzKjWRN2TaFGbFuAt
NTXPCoYuLpNooX8xpa966iviilFu8Fa4Tew+lOXHS4N3L325qd4t5arlqs19
2pmnur0vqWfD003OeRPPiElHw8L6Trsb8nAEEk9UNkPnjPAjj4joCucbrXgh
1Fr0q+uAEwTKbaCgBMMPrDj0C0t7GNNC0fGsQryyJsTDxwPbWW1insKvWQ0C
Wu2596oa5E1AWzGqCPpmHBKHmMk9drDFWXIwUsmLEj6VcedjD1Ar+AimZVNi
9m3dOI2Mcacwemkey2vDrfbsiOcwNjpujtxrRmuX6I+zOekS+ZaQX2oFRrXR
9kGiMjEEXFzSo6e75R1Iz36jIseO8Sz8KAKyFyuR0jIGI1u0wlNbjdAxP+GN
MiLDdoA92utzEcsMAv/A/dU+eWSevAdy6hmWtFR3Rxokhe1gk5AFlNxxKwOa
ziJ1KSn0IEUz6e7LLi5aZIsG2EW9D4klpnfgijNKWUo1PvormRZsSyTTbJcO
SCmQsARlKaUkXeIBeF5W6Cfgxw1RuHxsPdwDKYGSQDdZjTVumpLqW2PgxDbl
dnygrE33u4usJWS2A2KCWU2Uq8J1HccvmMaoQtVpno8QM+fC+mGzJordEC9i
Lw2RDrpqdB2Kz+KsvSualDHxJccNEbo8yQC++02bRcE2QPnSmjPGb8N6TXzD
WSJNXacnJi8dkIwzrvqzcs5NCLp/Tsq5kZhLMi7OchnLuLxTNIYT3VBqTfI/
Mb0ZrINVsDlM1pcy9SNg7GokVqX1eOwOxEIISfRBoGK2PX8l8dk59UWyCa+w
kPRAMY66tOED7XndLm/P26lWSr5BdFdI3WBi0EJwC+pkjW5mbKuwckNpSY3l
BhQxbrBD3NizA5xsAXHwSyNE22wtX3leXKJPq8xZUVHvWJ450++hjAJqPzNF
YNFDQY7TVbrlNO10xDWwL9KWg8q+auFaNT0rB7bOvDSdiR0AfEOaI89CKWQm
8mAIkRT8IGK9UyMOu99Hgy6KTY/9GzXEYUdF5M0e+IMcUxcHIiuPsUQEWS3L
qZQrT5WuUos+7k7B43eG01TYuRWFoGaPx60P+kiGSKW7hoUVGgaUfUy9jQdj
FIrJMQqABSwdYxt+Uu3fmgmABB8a30x9KUMeTUm7SC4E6pnDmvEPaeCqTL0d
WVipu532tcTB2lyQJGYTm36mgQTbGZQH0FK8i7vSfP6cpliLXvrahlRyAFIW
nsygiAEy6bAcVpwPv+ujhC8ODtxRbyl+j47E02KGX2M/ix1DsfH7mjstJhso
jYml7nHqdKS5gsJf/vfbN8VtDaY7qqMyXhVHfqP/hFDrOm2CNAmarMNxjyW8
YtIdBwMmQAwHcuThJ4JOKiLp1XEb5RCHGqBV4nddbDgWtuhPW2pdbMQwtlUB
vd8PLcPPD5ud+vZw+tehKdOs0FKYZERKdnCfmY9xeAjbUUo+JFIFu6GK3nMF
vvt7T5XpbFcQJI2v1ZtBlZQeYTYsWYbcCnSD5gYRcVZNIdq8sE3hzja+mKbZ
qNdRpcOBKLSMXJygNdJHhja5s83c0bvUMGJPdoDjYsZLwf1EhNJEnX4bR03h
dcS5dkNzj2XioAdvlBpTnGSkAFEmd84/uMzwAl2lkTgbsls4XQhtSh5IujK2
IKtshtiw8O61xO0pRk2Rj7Qpzdzj1AIud4tTBNnc1Gx7TMqh1nkxIpxRHZcu
XWpWQCQ+g6yYyh6RjnyApjejqV4y6SoJkLEo+PX5L+cksvhGTpKzQPIQZlL6
sROqQjivJWdwlOYl+QfffxWsVwCy+roX4yU1V+atcfmLzPumhdhijLP3so9S
hybNY3xKs42ku23bX19rnN4EI6fffDa3M3EkC8HGY1Xlo9Mxx8BWOmYUe1FY
jbjQYTF+GS3vWUaDI08sxUQ4DXSDdV6SjkCGMeEVWkHoyJYXr6mIaKrBVaq9
C6ZhRUEFDhaNpb2KyQVOtYdULU+eP068EzlGcfWiyEgdWH3T0IIksEgejz19
0viaElBECUitA/eUD22LbHnEHzBBsS3MtqVqHaWRbkdAImEtfrfNbhjTfRNy
DJwzib+OnUKMyNhYRjJlTQvPCdtFF9AXzjBGkOzSMo1TW5p2NUlhGSvKnLFq
ETsCKb1m2plwHjRHFWkMX5EdZ6DwS1rqhfZhjMdCBjEqEqUJRxjQYzU90i59
BVAyzQjNR+dh+hKN2KNWC6wF0gfkHTa6MOf0nJ4Ui7Woeu1KdQpM4U0pExd5
bMA9SVeKhFMDhmivsZ2eRRHkH3Hkqxi2edNuLsEo/lRo6t4SSMjEAVM4hwzg
Rc3eGbEjN3u1k3UyN6CSLLgK7PdPa9IhsQtbg8qhdm2Sx5fKZoHBIzeV2YH8
A3qjmjI+KwWLU7JERlzknVgAEs8swsnkAVZnqKCZVbfT5/Yp6hhBD3ITr1Hn
BelDIL2HkgMoZTODFbLDHnIo1xrAI28+dgb0+1aCp3qSybShs1O7K/X5YPSU
S+51PSDMy+TkQe2pppktRm5FhirCC18DUjwHQYXcaOmTZwW/gzbxxnYXE/UW
Ux96XerVpIP9fMLB/vlh7kt37lXarUbZRXUZ2XpDO2SQtODQnOTxntbNbYaZ
sVGL8zQWwW5L0z588i05HXEqvVwkOA5KpuYTsOUxSJtoQow8oRGNHS49yjmt
j91ihm0TNV4ZY5S5paf2HptqkcCtt4E7kQrRcevZqBIdUn7g5n6u77CCjArH
uRoAaIgy8WKug3GvCQji0esmvef0RZ1Iq7knEytI5YK0rUFHmWSX5f4y4y8c
uKm0wy3nHbN/Xbrdvsf/rxt3gHEeU4MkbA2g7YI8p+303JbmQx6FRqcSd/Sx
7W00+rG1JkecWcFWN3HhRlpuZ1FeclYRIHm2l8l0jZ3TZY/YvXJim5F6DvTN
SUpC6vc4mKdwlOJjMrAKhRUA7/h+0SL+iOEHfDsYt/ElCCybum1P5G2LFeNj
ZbFpqn2tpy9Po3BZ7hVrlVIcRuosl46z6tpKcdetVv5aii/ijIWGH1+ikOmk
JxP1AYuEe5BixfMMiylMBXLZvMlqFRs7Z/lg0orzteiVmJo1c0UCxUQY4sgf
y/aShW/gQXnSZNPvhfm4gm0eNdW0B9LUPasuhKVmkl+XHDdSAeM5LyJOvyhT
jgme82hxzDOTdXtyHybJSHfg7TKuiF3IeDVpBKd+3wvmas79SDZUyYWuXJY1
YB95f++ofdggpjJYjVsaL0tSg5FzkR2ckqVTnpxtlnXF5SkY6jC9pqmhWhNT
lFBr+yuWpLCs+5f0T0zk+o8jrE7p6hcHnzjmno7Ob0rffnUFi4q9apgh4WzS
0xTDxVwJdgcn4MYHYibnjPMR+LLOV1iUw+ozgG2Y0pGCdJPDnEEgZK9rDzp0
D8PXnYkhJwqKdcn+gHMt+eoxBOtaGTIUZ1yNRhIlj2EbqKx3GHJ0WZCFOkKD
6ABIXQXRh1OUbioNxTl5vo3PU2y4Cizg00iDQW0G6wVpVjF7XE0AcXDiQUxT
Gty0KUxs2uwc4S+vNHUQl8Iow7EbxhtZ5eU1bofHiFm1xKfxE858Ik3jsJ6J
uD1OdGB8peA7uhSduhR1DyObfDrBFv2umFZLRE5JXHmL5Ng3LhXdY90ZQ0z1
UuqcjmfLUPELl5vEK6qe2kGNPEho45Zt3hzhT0UeEEw1WG30jNNXZVO2tpyP
E3aD6gzkC9w+BdXfd5wGG/88U8colTALd5CCf/pSXr0xv3+L3tx+DEyqwakN
fcQZmuHn1OhbhRy+E1sH0vITMT5OrktCWWnFRcN4won8QdwcHD/VMZp8xabD
Nfk5J7pKCyQmjiy/s3QxszMYdWPMq9f9poiBfuZ/Pt30cJB54mCgKGhJusmJ
Ma8mDYZdFTMbj9V8bG4gI3EQEYpTR1qbrFfObRZ295Io1bm3Nfe1CBW6SLI2
zIORc5I/juJen6fL2DvTG4VcSJhbnCW1DvjDfDSNBv1FRogM+Yn0ExLH/7qn
qkFnXE2sllxczg4TdZrbbKYduTSYZpjTwarVcHiW3CvTX935jbH9nez2SD+U
TQWDzwGH6o65H2hU2qKFhSlHxG0P81VkDCmMl02HOzjO5/NDmt/xT87/AYOi
RA6psQO3S+6oLCUbJzRwIxJO5ZBOVGFXfKzqO1BVKLPVpSBEvpB2zBz2poxM
nMfSH0zXJPd5E4bs+CrNyhhMMlJPOo3pUhe0tiBp8wTbieipmgmEdVq2KKN1
EC8oLPcncfsE8f9q4GDoyk9KynAG3cElBqkyih9AxppsWGVjcAA8bFypORw1
pKWd9UmsLZnUlKVOSUk6zvG7GPZ+9vQMO29yhjaH22bGJz8bxZ3F04VHMr/V
iLaVw3ES0oVEsSxaZMnO/OTJnZ5oFMuOXEvjvLgrCZfC+7+HBbvWEBLTW6h3
e0p2jmmcB/uo4sAP8onS8TEF7lMExCjySqD470pTIwaYVIsoD2YgafymNxFh
UR/AwHQ41IOcq1wMIzMqsnw3M60sDa2gphCaKLBy2m9JNX20OjSX8N58vozR
uUE+H3ot8YNRK3fufc6TzSR0no2AdZKr6FTOuGjED5efhItOy6COjwlBOh/o
T9I6WIJbqKVxQwZQRbgR7zpqP3zGsrW6lewYAxqOHHGS9zCeuc5FNZSsTA2v
dlyoZHsmW6+STIQbeoWmsjzkE3glptuQnha0FNkkT5HMAKvXRtCjojEVvRF0
LukgqXlNlmBAbo9kWWgjDlzS46gF0DupT8heVHFbtBOdH+krg0kc6F9E/xyq
aaVOLOeBU5INPLzSMR06q05HfB6SnEHTdya8dRlJzrl3VNxsUx7iVwk4Qp7S
m3acq+eGpO1tGbGZssC5QDFCbZqQ5zyHW9zzfKDY2TgxCXs8bCVmt0RtirnD
0SLv0Sv3xPXakR+5qCKoDIo9/gb0yYD8EGdIEUjNFLYD07aoqo/6TNg5YxeX
w/EwCx60FVtwrGvxnIvTmCvQB9dD/aBjOqcbbE49i9oEHOmk6UueGRf7rnex
OqXNPDbY62iwINUR+DZxWnQFmoRpl3oWlg0N1yG+nWDEMLxIfe+4ywC1vPsQ
F80B42/rckXGCGutWAzaKPrZFnopmbAp/gYaqTorBT3SxpCIkbxM0LbkFELC
5FiHb0tR7ZdSZ2vRjGxXk8XeDbDmg/qk2UBXRGt0lAnbVdF8NwkcsBd9SSem
i6FAv0O26w3ZUR67LrPTsdcWjR3beOcyu4sLQ6yvGat340gSsLY2dTtYgldw
WtRcc8+629hUxigi9++FkvZTyUFK2NapbciM0uEGSltmofBQaOvLIANkmIM9
LJGw01lH+dp5mWC788xc3GAfKQM1OTRmRuub8RjWmdieBBtnZUUu++zcEOoI
f4O4yjg02mLeaZ/6ASDUpd4DP9jvVnHQM27Sff0mi4ObdJOb/AGnFDCLlSY0
k2AtYznCPzRfm8aVbWtpfp3XKPLEj9q8I33BhfKkhzEnlgkMMAYTgxVqsqf4
3qA+CWnhC0PpSFUeeEyyAVUuRTAAIFwveKAMT3U4UH14YPbrBGbsgnv0S5zt
dAh+1IEtwoOiifz5lFFFhRVXMQXwQ4PyDLjDS2RaFyyRYm73zHYA4tSVBuf+
UtlSTrOyCWNqzY+HTQtF0cPzIVU+yA74YMaTyjV6ISNYcDwLp0Snm1CQukOg
5CBOYhxjS2lMQ9mUJJ9GI7OuknLysolqNiETQVP3XVtKiqdpVWxYi5kwxNMT
JE8v8yBRIWsajyQ1DqYYNj3F+TBdyz8FOhn5O0vQg2UYFb6BIzvMufjbWGCD
tTI3I6+ZACUtKk0x0oQoHbyWehWjAL1jo6xSl4M3HihK/R66ptKM7y5QRg+a
YO+4KxboFlS2645ev3t/HB+d6LV3NUrNzXbu249B6u7TTIeocTtbWkz5Wlw2
gXeovRi3nssFTBZza4OZztyIdNERT5wUHg+ybeNgEFbm22D4b2yHw40SqH+I
5maQzYUKOVbMlR2PJtaPdLWjWkRs63PLYSx0zHEyBWefs7qtQGJHgZYw9tWm
BJsE6Gq4QNI8UkpvgTMRMB0xpF7jfH7YhkoaCrgBklDeBg9tEMGkqS56GoJK
losrlOKjGwR41SrgRRTvUSYdxAfg3BbaFOaesfzHHHtJz0nXeGgdLkKzCmff
mv6Jgy5YMURCVVFarNIEoMOUOkH7HqVdU+uALvY2qGVuDPJQFmmaPMcRJdG+
em41PAkgm4yKh0CfJpeWcpjbxebc+6GpIY/GvM4INeyFk30Z6D9Qu/qAFcbU
KpP2wnEmxN3IMTDzwI3OTZ1xkVqq8eGfyunttYjTm7zcS9Qvq+GlgM0HrMJC
KNY4zdxkC5Ny13w7S66OXd+gX0RNbOw8xNNbiHpYgsatb8oFhWgZANpud6Jp
Ii4/xi5DSx9oBZFzJMZ1XuU6BBknjsAmEdRoKQmujRr3L3V1QtOoSypAqjEM
RwtmQ9FS+YnMv6vFGHXm3SChJwBqgzQec7jiUE0DW1MH7WKCW+yarKpQNpYx
vS2pekGq08XP4UwdtbZpEh9eLVOY0OxXPX3Qn1XnYzmO+aT0qUy4iy89QTQh
cGmkkNupFDKGy+gWzdeZYY2eMJ1VhmaGUsSgv19B5UjKlh5cRY2Q3n4LGvGD
mEqghTdfbPMwp058S+uhLttM9Kl1xx2TbJlMUpukX8ar0YicIXXnuoS250bm
P1n/yqkuB7XfmWP3H45+RLvruvG7G1WZJgFUKICiJj4Uwdg7CoTPp+J8fjY/
TeVx1N9G9J8Wh+uu/iufTNGd/1Xkl1/KVLKs4dVXQHoOK73ubGN6YdTadH+0
lJZs/kRDs4y9AisNHj3XNsRSxUrJRaY0UGKpS1ToV2QiszcKl+ICT/XcgGSM
dsYPWLQTYzJnWlmGoBZAY+ut/xKcs6vVLz2efz++14fFz6ll67vYf3UCbljY
GtuzCu3qtzdUU8m9AVLjTFkqdSjmOTipR+xGa7OlBDK2QxxHEmlv3PHYsSDn
1tEdd3xKX5PmYix8TKwuhSmd5siNSLM4v39qp3SM4j79btCD2RRrIdsGRYGy
qjba5JoZbbZZbecoOnIBRgOsEXBvsIkezJV96qVIDWRjK3lt4YJ1/ejFlcHR
LLCjnRVXKYclcsR8bId4LMImCd5pfnb0zQMtgeZCw1DrfAAjkrRvxNW5V3Uq
NdSfmXvHlr08fSz1sZJcNVYNuFuCexXpS6OsCQdNikKmTnBvM2CrK/TOsIpZ
UZdAuIbU41RKDnhQNWtyUVKd2xifs76bRPDp85mA8RIHZZjdeTOhUwaL+jbG
EDkuEjEUjUdq0aYxotZreHxWcIqfsw9gCRh1cWgRVXjrb6T5FDtpbIuGrz7C
JShF8MO8SHnq7OzAC0jNdA1XaGW+xsTSxs0jGXJJocPmt+WyJD8/d97EocQb
aVCPgSWnvbSySIRsMA0TaD+qK5eGOBNVMDheUZyNbvFDtllSlcV6WDHOdPtd
GBhAJvJqq8yd2uXIy5MXE7P+qswJ6I2fDFUwVBykhqzkX5J2gJM+keaBEDw6
FoEzYE0OcH2epSpcEkF8029r8WeTez/0m/paUx6Lf5N4+JdQlvmE9BNXl70E
cCWmLj2kV6VkedkcER2wTb4TqhPJWprkUlGaKrtUe6s+U78iojW193wKEG1K
ejQEKqLQ7B48JuHLLk2hBOwjfPufJODhXF2MfYJWcROqSKpwE176NAu3IWuE
uheTMP1tx3oAPEsCUpmZc/IXgAMGYAU7GCYojXh/ooga17tkfqu71cV2z9Ej
Z5pHsIXNEzjTzPXkc610JCgiHvmAecyGw0z2emFroaY8w6b/uDqIMcVcEcHl
DjnNwEJXNSHboAkA9aJKDrHUksYhYcZ6Ux13AZYdwFdzSsgF8xexks8Otj/8
/FBe/yNLJ9WqPpOcjpF0fKUdTbnQdA9uyiIO9Lwzfhyhvge0pwL5aMpzcKY4
e/ToOXei/P7J2SPQJFQHmdz2kZ7s9Fgr/M4enZ7xAk+ePP7+qxc4OxZG7mJL
yXaDkoNnfZ49OnuEhK6O6mdEjlEEZMFnYWGoB6xiPnaecqVui1PuK6s/nuUx
byrNxRtDzg9KLjUYNb/3PK+giEMvTFowiwhtmxKtAUZGrYviNCIsoUmpe6N2
gXvUtbOxfqya0XFmETiK+lLHP4C2+5GT/F+ZgaWgqILWvpVOQWTP2MbhAx3O
TE+3LnYy8CThM9yaer+p6wap/VvMRAfLclcuVYMHXiL7Gd6maSaqaqAzbdng
wtArFrJbmkrUHgTmXJ4L8nVBB2lggW1VSMy2fisNI4ItqZQJ57ZdR1wNhM12
UM5phZqU4UzQNbwYP5KyZK0yKDk61FaBPJlfj19DE5fcntS1gxsXmMlQ0VBR
/MGAgRoj7Ve0emUQctouOY+GjS9sNKoYTiVvlUHrJxnilt1GcqYhxVSRJ8Px
OHUmbehHoEROmbkSPjFK/dS5lCiDtJhbh8WklR44VHzoU/ACDmhQZ/2Dic89
EIv8LjXecCY+aappZpLVYmOcxRFOng3SdgmwfCH9i46p8zr21pf8rlvPs+ds
MQp1L77GiRgBq5goH8sdRSN/fmqcKsxoj2dZ1V9O3tpmJlvhbLzCYFIy5bum
lGlEIYvy2WqPv7jaIIadvf3d+O1YLIP6ISELyJl0gsf5F5/TO1r2p48X9vlR
uipfffi6fNXkUU47/y6HIa9JpeLm5Ai1bd6U6kCmKhE9RTGc+cRo2/PinNzI
as5gLTfz5uiAxECGZLMjOHhugIF9Su7G3G41YYxz5yw72WNUMQZ9PdyDZdaU
AauOtPWFpv3UsQYry+pnHp47lrQiIrZAuZw/yOccKZkwk6AOhHkfvhFTMPOY
VVuRTMNGWr6x5xPYY0hVU9NO1ocPx/BzDuvgzO4V/rbfG+vWOjVXU2+RFg7m
rx+4JxJwMt4UPk45kUecedPGVuu4gM6snGRqx8rVwGyE71KPnRtPHfAJq0bs
jTgbMbkJ9uYm2Nuhhk4T5x3i5cH6g8MNyl0mtbghPcc8QO2nUY0xvnoA4G4M
8Pxz0SAQ9QjQUvB65iTwu+Qa/ugsScwilsdeqvVFIwMxZscxI6GUe6TQsCpS
bDJnplyaZYvRsiYfFWtgxIBrKHNSW/RFzDvQW5up0r7OjbNNmU/WMTbqXdJ6
lm09DALqB02+oWPlFrWx8AOHmaggOTdesf8GFyRFTF8RuFk5MPl0bci6eq+5
BiJrKsrwAHbjRNnFiHmZLr09pBjNIp+6oyvMc/ST5BkTM6f+S38+T9X8ZJNw
4nVMdDTdAnJdWF3XEjz9pjX6Yqnn1sKE0iKNFg7hS9p80h0Rcz979j0yd9gR
J62t2H57ffJqTvm/J0vf7AgPTpo1mGonpV+cyBIoiwR606SSYKUtOVfk1ccE
JbLXbSnUAFq/RkhexGxuGZQAHHA58e3Hg2+n1ckGHxp5eHdUJ2x6FGB4teW8
/dSzmOxHWoOExCLm4afsRzVhjtippXEetVhMEY84t4dzD2JqNbLcqMeltK5Y
JGxM31ivQB37AtpX02ce1GTbcw+TZnMxN3kH769+veAKMppuYniIsvlU1sFb
jgbOffaNpV/OG8QPzVQbYGEuwbW+uivDZsXLIELR4JZ65//ehzma4UiGNPjX
xJDiNKvZl/kKfnru3ifeHjnpr1SfatKUpBuH1ZRQwNYLoOLQ4awRjs6Ovrnw
OCslfW0A+3NstI/ZBhxYBLCf/3SMBebqEznopDJuoaRfkab7iey3ZZiQvJOf
i+W+7HeTsWo2GugOycgfxUCnNHLVe1d1v+iG4PdrTHFrk7sPP02uPpIqAinM
QD36oH+VdEx2rCLn7G0XXyvQ85grnetlPFe+EVP9PD+eTDf4pzKZy6S8xlpc
mQDiN+i53ucc2trT6JsEVbwnWrnIplhI7BxFa6tPDOdcyPCEwaqc3D0feC7V
kzLwZSQMp8wF1GC5LJka6iQdAR7tqxj1jt5VzUnYojaH0SZSA0oOl2ZiycLz
iDJ/qOcgJdKpsD4eThcfGlT4HNXYEctNJ6FxErEfXYSXJmPobAaeKRRP2Iap
prasRy4CtTUTvy2N6uAmJE5qdlk+Sz80NaJNBAfVUhkDnJbmJm+OJpHJOCal
z+xVnq/gW5rHitJUOpmaGJGLDYI22pmYu5Vh2lm94WVmqfm+ZAp25KbU5YQa
NSNhi117qnCi8ZZjO1SQoIpKDY9RcCvsjKbtymTM1rCUmowHaZSXarkGhVX6
Y1hF7DmOIwupcozv6hAZ2LoyUyIzFIcUB0ObdRkDFLilWOlgR6E85LaAUxQZ
Z1cMR0EOOxeyfBt1L3QHuxd+feNCN924MAN9anrXjutHD86ooOORFx6XPzz1
QmeJUUMA2cQeh3LwI6WeJnBei/RbtJZT2vlMSxPoRD72UzHzA09OTqh3Ht7M
+VKLy5kOPr/g9oxh9T8frAGlwwPQVt5xS4Hkzk49yzG3bVE3DU05JFo3knRm
gyUz66maWRbLGtCPlJpJoZxzSo52/xbbDI0y0SUQK9ZHKvbmfLxhSxXS4DMr
8VDAAF2Vb5ElVcCQ6m2LXoeXIJ/ArFONnj/9FiShDyi2/lzfVMS/fPWxRWZ0
uSnhTt9gEASf5NffU24ob0iqugrKGaXxj3I+3YRIl7KxjkzFXB75ox/krFYy
iLQUkByOGrmjvD1g1H/2TVmcNx8/1jN35Rt/U7zE12cOzoXqDUh6LEqs4K/L
uutg134FxvrM/RJuS9AD4IKrTQgz9zIgLLa7RdiAIf9nvy9e+U3Yz5yA7VWP
NRLFEeB1eIFKOYmKB314wIT82/949AhHuY3Gxx/P3O+hhaXgllaw3hvYWHF5
DbpTN3PnK4Lij74BWoM9dmGHXVz4Z/wFHBq0sLKq/+Fhjw3g/E91tboDUoVN
1nBRP/sNmNoVfQR+aFbACuF4L+tF8TMKQfjL+76FP6E/HM9zcUNDs+GrP/fI
6GGhX+HS/uyXNQ4SgG/CDq6LP8MT1wSWv/ktnP9f/ar/iN+8gX9vKJ0TYNOD
MNkX/woyBvjfHUKrbP7m4RfhZhPu4Psz9wFu6w0O4ZOX3wDgKwD4mx6MkTf7
ankDfwiwnbf+pq5wh+fVqgGG8daDzCJ4NYi8PAYTtocuJXgQlJ69nO1tX634
pj5iIQxyjhu/hU+DnbIv3vl+g+cG86fC8tuPIJjgk/2G8Bf0j5uPsJ3LplzS
T3WzAZCcb259U8MvOgL1+QqzJ2uPm31FaL/17dJXPT6J/gvcB6Dgq7q/hj/u
caPvUam88pt/yMGvlv1qRSfoymvsJeU97ONDuS1+B5Wkaj+WPGPpl3JZw682
sL8tMOz/C+JXCw5c3QAA
</rfc> </rfc>
 End of changes. 138 change blocks. 
1340 lines changed or deleted 423 lines changed or added

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