<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-carpenter-gendispatch-anachronisms-08" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="Process Document Anachronisms">Some Anachronisms and Gaps in IETF Standards Process Documents</title>
    <seriesInfo name="Internet-Draft" value="draft-carpenter-gendispatch-anachronisms-08"/>
    <author initials="B. E." surname="Carpenter" fullname="Brian E. Carpenter">
      <organization abbrev="Univ. of Auckland">The University of Auckland</organization>
      <address>
        <postal>
          <postalLine>School of Computer Science</postalLine>
          <postalLine>The University of Auckland</postalLine>
          <postalLine>PB 92019</postalLine>
          <postalLine>Auckland 1142</postalLine>
          <postalLine>New Zealand</postalLine>
        </postal>
        <email>brian.e.carpenter@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="20"/>
    <area>General</area>
    <workgroup>GenDispatch</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 58?>

<t>This document discusses some aspects of documents describing
the IETF standards process that have been overtaken by events,
as well as identifying some gaps.
It covers the six-month expiry of Internet-Drafts, the reality of
the two-stage standards process, and various other issues.
This draft is posted only to open a discussion.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-carpenter-gendispatch-anachronisms/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        GenDispatch Working Group mailing list (<eref target="mailto:GenDispatch@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/gendispatch/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/GenDispatch/"/>.
      </t>
    </note>
  </front>
  <middle>
    <?line 67?>

<section anchor="intro">
      <name>Introduction</name>
      <t>This draft is posted only to open a discussion and to record known issues.
If there is interest in the issues
raised, they should probably be split out into separate, more focussed, drafts.
Each of the following sections considers a specific issue.</t>
      <t>Note that <xref target="I-D.ietf-procon-2026bis"/> and <xref target="I-D.ietf-procon-2418bis"/>
already touch on some of these issues. An open question is whether the
PROCON WG should be rechartered to consider formal rule changes for
such issues.</t>
      <t>The issues below are arranged in no particular order and with varying
amounts of detail.</t>
    </section>
    <section anchor="making-internet-drafts-inactive">
      <name>Making Internet-Drafts Inactive</name>
      <t>Experience has shown that the expiry after six months of Internet-Drafts,
as described in <xref target="RFC2026"/>, is illusory and often leads to wasted effort.
It is illusory because drafts, once posted on line, never disappear; indeed
the IETF maintains a public archive of them. It leads to wasted effort since
some authors feel obliged to refresh a draft every six months with no
significant change. This wastes effort and resources for the authors themselves,
the IETF's own computing resources, and potentially the resources and time
of innumerable others. Additional arguments can be found in
<xref target="I-D.thomson-gendispatch-no-expiry"/>.</t>
      <t>The following sentence is in Section 2.2 of <xref target="RFC2026"/>:</t>
      <artwork><![CDATA[
  An Internet-Draft that is published as an RFC, or that has remained
  unchanged in the Internet-Drafts directory for more than six months
  without being recommended by the IESG for publication as an RFC, is
  simply removed from the Internet-Drafts directory.
]]></artwork>
      <t>In <xref target="I-D.ietf-procon-2026bis"/>) this is changed to:</t>
      <artwork><![CDATA[
  A Internet-Draft that has been not been changed for more than six
  months will be marked as Expired and may be removed from some views
  of the collection.
]]></artwork>
      <t>What really happens today is closer to the following:</t>
      <artwork><![CDATA[
  An Internet-Draft that is published as an RFC, or that has remained
  unchanged for more than six months without being approved for
  publication as an RFC and is not under active discussion in a working
  group, is marked as "inactive" in tooling maintained by the IETF
  (such as the Datatracker).
]]></artwork>
      <t>In other words, nothing really "expires" after six months; either the draft is 
actively developed, or it simply remains in the archive.
The expiry of Internet-Drafts is not mentioned in <xref target="I-D.ietf-procon-2418bis"/>,
but it is prominent in the header and boilerplate of Internet-Drafts.</t>
    </section>
    <section anchor="single-step-standards-process-and-std-numbers">
      <name>Single-step Standards Process and STD numbers</name>
      <t>Experience has shown that the process for elevating a Proposed Standard
(or a residual Draft Standard) to Internet Standard is so similar to the 
process for approving a Proposed Standard that there is now no practical 
difference between the two. In reality, the Proposed Standard process
is more stringent in practice than the description in <xref target="RFC2026"/>,
with in-depth reviews during the IETF Last Call and IESG discussion
stages. This is underlined by the Implementation Status Section recommended
by <xref target="RFC7942"/>, and echoes the arguments used in <xref target="RFC6410"/> to reduce 
the standards process to two stages. Additional arguments can be found in
<xref target="I-D.loughney-newtrk-one-size-fits-all"/>.</t>
      <t>Another perspective -- the confusion caused by STD numbers -- is covered
by <xref target="I-D.klensin-std-numbers"/>, and those arguments are not repeated here,
except to note that when a Proposed Standard updates or obsoletes an
Internet Standard, the STD number loses it legitimacy. Also the issue
was already hinted at in <xref target="RFC1311"/>, which has never been updated
(but may be obsoleted by <xref target="I-D.ietf-procon-2026bis"/>).</t>
      <t>(This problem does not arise for BCP numbers, which already follow
a single-step process. But for both STD and BCP numbers, it is undocumented
who is responsible for choosing the numbers and deciding which documents
are grouped together under a single number.)</t>
      <t>It has long been observed that "The Internet runs on Proposed Standards."
What harm to the Internet would result if we
replaced the two-tier maturity ladder defined in
<xref target="RFC6410"/> with a single level of maturity, namely "Internet Standard"?
This maturity level would be a merger of Proposed Standard, Draft Standard,
and Standard as they are described in <xref target="RFC2026"/>. The characterization of an
Internet Standard could remain as stated in RFC 2026:</t>
      <artwork><![CDATA[
  An Internet Standard is characterized by a high degree of
  technical maturity and by a generally held belief that the
  specified protocol or service provides significant benefit to the
  Internet community.
]]></artwork>
      <t>In effect those criteria have long been applied by the IESG for the
Proposed Standard maturity level, including when a Proposed Standard
is updated without promotion to Internet Standard. Merging the two
levels would not change much at all, except for making things simpler.
Clarification of the scope of STD numbers is also needed.</t>
      <t>It would be good if all standards-track drafts <em>required</em>
an Implementation Status section <xref target="RFC7942"/> (noting that this
section will not be included in the published RFC). Then
the IESG could consider the following issues if they
are applicable, especially when the new document replaces or updates
a previous one:</t>
      <ol spacing="normal" type="1"><li>
          <t>Are there at least two independent interoperating implementations with widespread deployment and successful operational experience?</t>
        </li>
        <li>
          <t>Are there changes, including corrected errata, in the specification that would cause a new implementation to fail to interoperate with older ones?</t>
        </li>
        <li>
          <t>Are there non-essential features in the specification that might increase implementation complexity?</t>
        </li>
        <li>
          <t>If the technology required to implement the specification requires patented or otherwise controlled technology, do existing implementations demonstrate at least two independent, separate and successful uses of the licensing process?</t>
        </li>
      </ol>
    </section>
    <section anchor="deprecation-etc">
      <name>Deprecation, etc</name>
      <t>There's a lack of clarity around the meanings of "deprecate", "obsolete", "update" and "extend" and the related RFC metadata. See also <xref target="I-D.kuehlewind-rswg-updates-tag"/>.</t>
    </section>
    <section anchor="how-many-bofs">
      <name>How many BOFs?</name>
      <t>Another issue is the number of BOFs allowed. We are currently somewhat inconsistent
with our own rules. <xref target="RFC2418"/> and <xref target="I-D.ietf-procon-2418bis"/> seem to limit
the number of Birds of a Feather (BOF) sessions to one per new working group:</t>
      <artwork><![CDATA[
 Note that an Area
 Director MAY require holding an exploratory Birds of a Feather (BOF)
 meeting, as described below, to gage the level of support for a
 working group before submitting the charter to the IESG and IAB for
 approval.   
]]></artwork>
      <t>Or they don't:</t>
      <artwork><![CDATA[
 To facilitate exploration of the issues the IETF
 offers the possibility of a Birds of a Feather (BOF) session, as well
 as the early formation of an email list for preliminary discussion.
 ...
 Under unusual circumstances Area Directors may, at their discretion,
 allow a BOF to meet for a second time. BOFs are not permitted to meet
 three times.
]]></artwork>
      <t>In reality the IESG has interpreted this to allow "non-WG-forming" BOFs,
possibly followed by a "WG-forming BOF", and occasionally a second
one. Also there is a practice of creating non-WG mailing lists which
may or may not be associated with a BOF.</t>
      <t>The current documentation does not really decribe the current practice.
<xref target="RFC5434"/> is realistic but only Informational. At the time of writing
<xref target="I-D.ietf-procon-2418bis"/> does not resolve this concern.</t>
    </section>
    <section anchor="area-director-for-individual-submissions">
      <name>Area Director for Individual Submissions</name>
      <t>Section 6.1.1 of <xref target="RFC2026"/> and Section 8.1 of <xref target="I-D.ietf-procon-2026bis"/>
mention individual submissions quite briefly:</t>
      <artwork><![CDATA[
 A standards action is initiated by a recommendation by the IETF
 Working group responsible for a specification to its Area Director,
 copied to the IETF Secretariat or, in the case of a specification not
 associated with a Working Group, a recommendation by an individual to
 the IESG.
]]></artwork>
      <t>This leaves it open which IESG member shepherds such a document.</t>
      <t>Section 4.2 of <xref target="RFC2026"/> on non-standards track documents also leaves this open, as does
Section 5 on BCPs.</t>
      <t>It seems necessary to state that a specific AD needs to sponsor and shepherd
such a submission, which is today's current practice.</t>
      <t><xref target="I-D.ietf-procon-2026bis"/> partially clarifies this by citing <eref target="https://datatracker.ietf.org/doc/statement-iesg-guidance-on-area-director-sponsoring-of-documents-20070320/">an IESG Statement</eref>.</t>
    </section>
    <section anchor="defining-the-ietf">
      <name>Defining the IETF</name>
      <t><xref target="RFC3233"/> (BCP 58) offers a slightly out-of-date definition of the IETF. Should this be resolved by</t>
      <ol spacing="normal" type="1"><li>
          <t>updating BCP 58,</t>
        </li>
        <li>
          <t>adding a sentence or two to the definition of the IETF in Section 3.1 of <xref target="RFC9281"/> (BCP 11), or</t>
        </li>
        <li>
          <t>leaving this matter for the IETF web site?</t>
        </li>
      </ol>
      <t>Suggested text is along the lines of:</t>
      <artwork><![CDATA[
 The IETF is an unincorporated, freestanding organization composed
 of volunteers who are independent, bound only by policy, not by any
 membership agreement.
]]></artwork>
      <t>(Note that there is a sentence on this topic in the Introduction of
<xref target="RFC2418"/> and <xref target="I-D.ietf-procon-2418bis"/>, but it is incidental to the
purpose of the document.)</t>
    </section>
    <section anchor="force-majeure">
      <name>Force Majeure</name>
      <t>"Force Majeure" is the phrase used in many contexts to indicate that
normal rules may be broken when an event entirely outside the control
of those involved occurs and makes those rules unworkable. A recent example
in the IETF's history is the COVID-19 pandemic. Another example could
be an urgent need to temporarily replace a person much more quickly than the NomCom
can act.</t>
      <t>At the moment, the IETF's process documents do not tackle this issue, yet the
pandemic obliged both the IESG and IETF LLC to take urgent decisions
regardless of process rules and normal practice.</t>
    </section>
    <section anchor="iesg-statements">
      <name>IESG Statements</name>
      <t>Sometimes it occurs that a procedural issue of some kind is not covered,
or is ambiguously covered, by any formal document (typically a BCP). In
this case the established practice is that the IESG publishes a statement
to settle the procedural issue, possibly in conjunction with or embedded
in an appeal response. Such statements become part of the IETF process unless
negated or replaced by a new formal document.</t>
      <t>At the moment the IETF's process documents do not describe this mechanism.</t>
    </section>
    <section anchor="consensus-about-consensus">
      <name>Consensus about consensus</name>
      <t><xref target="I-D.nottnick-ietf-decisions"/> proposes a formal framework for reaching WG consensus.
Some older material can be found in <xref target="RFC3929"/> and <xref target="RFC7282"/>.</t>
    </section>
    <section anchor="conflicts-of-interest">
      <name>Conflicts of interest</name>
      <t>Occasionally, allegations of "conflict of interest" are made on
IETF mailing lists. The IETF has no generally agreed definition
of "conflict of interest" and no general policy on this topic.
(There are such policies for IETF LLC staff, IESG members, and the IPMC.)</t>
    </section>
    <section anchor="other-issues">
      <name>Other issues</name>
      <t>Issues identified during the consolidation of RFC 2026
and RFC 2418 can be found at
<eref target="https://github.com/ietf-wg-procon/2026bis/issues"/> and 
<eref target="https://github.com/ietf-wg-procon/2418bis/issues"/>.
There is some overlap with this document.</t>
      <t>Numerous other process-related RFCs are mentioned at
<eref target="https://www.ietf.org/process/informal/"/>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>No IANA actions are needed.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This document does not directly affect the security of the Internet.</t>
    </section>
    <section anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>Useful comments were received from
Toerless Eckert,
Paul Hoffman,
John Klensin,
Michael Richardson,
Rich Salz,
Martin Thomson,
and others.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-informative-references">
      <name>Informative References</name>
      <reference anchor="RFC1311">
        <front>
          <title>Introduction to the STD Notes</title>
          <author fullname="J. Postel" initials="J." surname="Postel"/>
          <date month="March" year="1992"/>
          <abstract>
            <t>The STDs are a subseries of notes within the RFC series that are the Internet standards. The intent is to identify clearly for the Internet community those RFCs which document Internet standards. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="1311"/>
        <seriesInfo name="DOI" value="10.17487/RFC1311"/>
      </reference>
      <reference anchor="RFC2026">
        <front>
          <title>The Internet Standards Process -- Revision 3</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="October" year="1996"/>
          <abstract>
            <t>This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion 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 anchor="RFC2418">
        <front>
          <title>IETF Working Group Guidelines and Procedures</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="September" year="1998"/>
          <abstract>
            <t>This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="25"/>
        <seriesInfo name="RFC" value="2418"/>
        <seriesInfo name="DOI" value="10.17487/RFC2418"/>
      </reference>
      <reference anchor="RFC3233">
        <front>
          <title>Defining the IETF</title>
          <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="February" year="2002"/>
          <abstract>
            <t>This document gives a more concrete definition of "the IETF" as it understood today. Many RFCs refer to "the IETF". Many important IETF documents speak of the IETF as if it were an already-defined entity. However, no IETF document correctly defines what the IETF is. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="58"/>
        <seriesInfo name="RFC" value="3233"/>
        <seriesInfo name="DOI" value="10.17487/RFC3233"/>
      </reference>
      <reference anchor="RFC3929">
        <front>
          <title>Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF</title>
          <author fullname="T. Hardie" initials="T." surname="Hardie"/>
          <date month="October" year="2004"/>
          <abstract>
            <t>This document proposes an experimental set of alternative decision-making processes for use in IETF working groups. There are a small number of cases in IETF working groups in which the group has come to consensus that a particular decision must be made but cannot agree on the decision itself. This document describes alternative mechanisms for reaching a decision in those cases. This is not meant to provide an exhaustive list, but to provide a known set of tools that can be used when needed. This memo defines an Experimental Protocol for the Internet community.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="3929"/>
        <seriesInfo name="DOI" value="10.17487/RFC3929"/>
      </reference>
      <reference anchor="RFC5434">
        <front>
          <title>Considerations for Having a Successful Birds-of-a-Feather (BOF) Session</title>
          <author fullname="T. Narten" initials="T." surname="Narten"/>
          <date month="February" year="2009"/>
          <abstract>
            <t>This document discusses tactics and strategy for hosting a successful IETF Birds-of-a-Feather (BOF) session, especially one oriented at the formation of an IETF Working Group. It is based on the experiences of having participated in numerous BOFs, both successful and unsuccessful. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="5434"/>
        <seriesInfo name="DOI" value="10.17487/RFC5434"/>
      </reference>
      <reference anchor="RFC6410">
        <front>
          <title>Reducing the Standards Track to Two Maturity Levels</title>
          <author fullname="R. Housley" initials="R." surname="Housley"/>
          <author fullname="D. Crocker" initials="D." surname="Crocker"/>
          <author fullname="E. Burger" initials="E." surname="Burger"/>
          <date month="October" year="2011"/>
          <abstract>
            <t>This document updates the Internet Engineering Task Force (IETF) Standards Process defined in RFC 2026. Primarily, it reduces the Standards Process from three Standards Track maturity levels to two. This memo documents an 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 anchor="RFC7282">
        <front>
          <title>On Consensus and Humming in the IETF</title>
          <author fullname="P. Resnick" initials="P." surname="Resnick"/>
          <date month="June" year="2014"/>
          <abstract>
            <t>The IETF has had a long tradition of doing its technical work through a consensus process, taking into account the different views among IETF participants and coming to (at least rough) consensus on technical matters. In particular, the IETF is supposed not to be run by a "majority rule" philosophy. This is why we engage in rituals like "humming" instead of voting. However, more and more of our actions are now indistinguishable from voting, and quite often we are letting the majority win the day without consideration of minority concerns. This document explains some features of rough consensus, what is not rough consensus, how we have gotten away from it, how we might think about it differently, and the things we can do in order to really achieve rough consensus.</t>
            <t>Note: This document is quite consciously being put forward as Informational. It does not propose to change any IETF processes and is therefore not a BCP. It is simply a collection of principles, hopefully around which the IETF can come to (at least rough) consensus.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="7282"/>
        <seriesInfo name="DOI" value="10.17487/RFC7282"/>
      </reference>
      <reference anchor="RFC7942">
        <front>
          <title>Improving Awareness of Running Code: The Implementation Status Section</title>
          <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
          <author fullname="A. Farrel" initials="A." surname="Farrel"/>
          <date month="July" year="2016"/>
          <abstract>
            <t>This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.</t>
            <t>This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="205"/>
        <seriesInfo name="RFC" value="7942"/>
        <seriesInfo name="DOI" value="10.17487/RFC7942"/>
      </reference>
      <reference anchor="RFC9281">
        <front>
          <title>Entities Involved in the IETF Standards Process</title>
          <author fullname="R. Salz" initials="R." surname="Salz"/>
          <date month="June" year="2022"/>
          <abstract>
            <t>This document describes the individuals and organizations involved in the IETF standards process, as described in BCP 9. It includes brief descriptions of the entities involved and the role they play in the standards process.</t>
            <t>The IETF and its structure have undergone many changes since RFC 2028 was published in 1996. This document reflects the changed organizational structure of the IETF and obsoletes RFC 2028.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="11"/>
        <seriesInfo name="RFC" value="9281"/>
        <seriesInfo name="DOI" value="10.17487/RFC9281"/>
      </reference>
      <reference anchor="I-D.ietf-procon-2026bis">
        <front>
          <title>The Internet Standards Process</title>
          <author fullname="Rich Salz" initials="R." surname="Salz">
            <organization>Akamai Technologies</organization>
          </author>
          <author fullname="Scott O. Bradner" initials="S. O." surname="Bradner">
            <organization>Harvard University (retired)</organization>
          </author>
          <date day="29" month="October" year="2026"/>
          <abstract>
            <t>   This memo documents the process used by the Internet community for
   the standardization of protocols and procedures.  It defines the
   stages in the standardization process, the requirements for moving a
   document between stages, and the types of documents used during this
   process.  It also addresses the intellectual property rights and
   copyright issues associated with the standards process.

   This document obsoletes RFC 2026, RFC 5657, RFC 6410, RFC 7100, RFC
   7127, RFC 8789, and RFC 9282.  It also includes the changes from RFC
   7475.  If this document and [_2418bis] are published as RFCs, then
   taken together the two of them make RFC 7475 obsolete.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-procon-2026bis-12"/>
      </reference>
      <reference anchor="I-D.ietf-procon-2418bis">
        <front>
          <title>IETF Working Group Guidelines and Procedures</title>
          <author fullname="Rich Salz" initials="R." surname="Salz">
            <organization>Akamai Technologies</organization>
          </author>
          <author fullname="David Schinazi" initials="D." surname="Schinazi">
            <organization>Google LLC</organization>
          </author>
          <author fullname="Scott O. Bradner" initials="S. O." surname="Bradner">
            <organization>Harvard University (retired)</organization>
          </author>
          <date day="17" month="August" year="2026"/>
          <abstract>
            <t>   The Internet Engineering Task Force (IETF) has responsibility for
   developing and reviewing specifications intended as Internet
   Standards.  IETF activities are organized into working groups (WGs).
   This document describes the guidelines and procedures for formation
   and operation of IETF working groups.  It also describes the formal
   relationship between IETF participants WG and the Internet
   Engineering Steering Group (IESG) and the basic duties of IETF
   participants, including WG Chairs, WG participants, and IETF Area
   Directors.

   This document obsoletes RFC2418, and RFC3934.  It also includes the
   changes from RFC7475, and with [_2026bis], obsoletes it.  It also
   includes a summary of the changes implied in RFC7776 and incorporates
   the changes from RFC8717 and RFC9141.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-procon-2418bis-04"/>
      </reference>
      <reference anchor="I-D.loughney-newtrk-one-size-fits-all">
        <front>
          <title>A Single-Stage Standards Process</title>
          <author fullname="Spencer Dawkins" initials="S." surname="Dawkins">
            <organization>Futurewei</organization>
          </author>
          <author fullname="John A. Loughney" initials="J. A." surname="Loughney">
            <organization>Nokia</organization>
          </author>
          <date day="6" month="March" year="2006"/>
          <abstract>
            <t>This document proposes several changes of principle to the Internet
   standards process, specifically a reduction from three stages to a
   single stage in the standards track.  This does not effect the
   Informational, Experimental or BCP designations.
            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-loughney-newtrk-one-size-fits-all-01"/>
      </reference>
      <reference anchor="I-D.thomson-gendispatch-no-expiry">
        <front>
          <title>Removing Expiration Notices from Internet-Drafts</title>
          <author fullname="Martin Thomson" initials="M." surname="Thomson">
            <organization>Mozilla</organization>
          </author>
          <author fullname="Paul E. Hoffman" initials="P. E." surname="Hoffman">
            <organization>ICANN</organization>
          </author>
          <date day="16" month="January" year="2024"/>
          <abstract>
            <t>   The long-standing policy of requiring that Internet-Drafts bear an
   expiration date is no longer necessary.  This document removes
   requirements for expiration for Internet-Drafts from RFC 2026/BCP 9
   and RFC 2418/BCP 25.  In place of expiration, this document
   introduces Internet-Drafts being labeled "active" and "inactive" in
   the IETF tooling.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-thomson-gendispatch-no-expiry-03"/>
      </reference>
      <reference anchor="I-D.klensin-std-numbers">
        <front>
          <title>STD Numbers and the IETF Standards Track</title>
          <author fullname="Dr. John C. Klensin" initials="J. C." surname="Klensin">
         </author>
          <date day="18" month="March" year="2026"/>
          <abstract>
            <t>   STD numbers are assigned to IETF Standards Track specifications in
   order to provide a stable reference even when RFCs are revised and
   the underlying documents change.  However, the numbers are only
   assigned when the specifications reach Internet Standard maturity
   level, significantly reducing their utility in the contemporary world
   in which few specifications advance beyond the first standardization
   maturity level.  For that reason, one proposal, more than a decade
   ago, suggested eliminating the numbers entirely.  Others, including
   more recent ones, have suggested eliminating maturity levels
   entirely, in part as a way to solve the numbering problem.  This
   document argues that stable references for Standards Track
   specifications are actually useful and that the solution is not to
   abolish the numbers or maturity levels but to change the point at
   which they are assigned.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-klensin-std-numbers-03"/>
      </reference>
      <reference anchor="I-D.nottnick-ietf-decisions">
        <front>
          <title>Making Decisions in IETF Working Groups</title>
          <author fullname="Mark Nottingham" initials="M." surname="Nottingham">
         </author>
          <author fullname="Pete Resnick" initials="P." surname="Resnick">
         </author>
          <date day="20" month="August" year="2026"/>
          <abstract>
            <t>   This document specifies Best Current Practice for making decisions in
   IETF Working Groups.

   It updates Section 3.3 of [RFC2418].

About This Document

   This note is to be removed before publishing as an RFC.

   Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-nottnick-ietf-decisions/.

   information can be found at https://projects.mnot.net/I-D/.

   Source for this draft and an issue tracker can be found at
   https://github.com/mnot/I-D/labels/ietf-decisions.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-nottnick-ietf-decisions-01"/>
      </reference>
      <reference anchor="I-D.kuehlewind-rswg-updates-tag">
        <front>
          <title>Definition of new tags for relations between RFCs</title>
          <author fullname="Mirja Kühlewind" initials="M." surname="Kühlewind">
            <organization>Ericsson</organization>
          </author>
          <author fullname="Suresh Krishnan" initials="S." surname="Krishnan">
            <organization>Cisco</organization>
          </author>
          <date day="3" month="July" year="2026"/>
          <abstract>
            <t>   An RFC can include a tag called "Updates" which can be used to link a
   new RFC to an existing RFC.  On publication of such an RFC, the
   existing RFC will include an additional metadata tag called "Updated
   by" which provides a link to the new RFC.  However, this tag pair is
   not well-defined and therefore it is currently used for multiple
   different purposes, which leads to confusion about the actual meaning
   of this tag and inconsistency in its use.

   This document recommends the discontinuation of the use of the
   updates/updated by tag pair, and instead proposes three new tag pairs
   that have well-defined meanings and use cases.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-kuehlewind-rswg-updates-tag-03"/>
      </reference>
    </references>
    <?line 323?>

<section anchor="change-log-rfc-editor-please-remove">
      <name>Change Log [RFC Editor: please remove]</name>
      <section anchor="draft-00">
        <name>Draft-00</name>
        <ul spacing="normal">
          <li>
            <t>Original version</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-01">
        <name>Draft-01</name>
        <ul spacing="normal">
          <li>
            <t>Added individual submission issue</t>
          </li>
          <li>
            <t>Simplified Introduction</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-02">
        <name>Draft-02</name>
        <ul spacing="normal">
          <li>
            <t>Clarified that Implementation Status sections are removed before RFC publication</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-03">
        <name>Draft-03</name>
        <ul spacing="normal">
          <li>
            <t>Added "Defining the IETF"</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-04">
        <name>Draft-04</name>
        <ul spacing="normal">
          <li>
            <t>Mentioned STD number issue</t>
          </li>
          <li>
            <t>Added "Force majeure"</t>
          </li>
          <li>
            <t>Note on IANA citing I-Ds</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-05">
        <name>Draft-05</name>
        <ul spacing="normal">
          <li>
            <t>Added IESG Statements issue</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-06">
        <name>Draft-06</name>
        <ul spacing="normal">
          <li>
            <t>Noted that assignment of STD and BCP numbers is undocumented</t>
          </li>
          <li>
            <t>RFC1311 lives!</t>
          </li>
          <li>
            <t>Who determines consensus?</t>
          </li>
          <li>
            <t>Added pointers to PROCON open issues</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-07">
        <name>Draft-07</name>
        <ul spacing="normal">
          <li>
            <t>Added conflict of interest</t>
          </li>
          <li>
            <t>Cited the -bis documents where appropriate</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-08">
        <name>Draft-08</name>
        <ul spacing="normal">
          <li>
            <t>Removed "Citing Internet-Drafts" which is now handled by 2026bis</t>
          </li>
          <li>
            <t>Removed "Who determines IETF (rough) consensus?" which is now handled by 2026bis</t>
          </li>
          <li>
            <t>Added deprecate, etc., terminology question</t>
          </li>
          <li>
            <t>Added WG consensus issue</t>
          </li>
          <li>
            <t>Aligned with latest versions of 2026bis and 2418bis</t>
          </li>
          <li>
            <t>Minor editorial changes, added some references.</t>
          </li>
        </ul>
      </section>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA7VbXXPbRpZ9V5X+Qy/9EKtKpD7sJLbmIWPLjke7ceyKnHXt
ZqZSTaBJYgSiMWhANJPyf99z7u0GQIlyMg/rB5skGt2378e5595uT6fTw4O2
aEt3Ya792pkXlc1Wja+KsA7GVrl5Y+tgispcvf7wvblu8ZNt8mDeNz5zIZhX
PuvWrmrD4YGdzxt3e3Hv0e6chwe5zyq7xoJ5YxftNLNNjVGumS5dlRehtm22
mtrRO9PTZ4cHhweBi/9qS1/h3bbp3OFBUTfyMbTnp6fPT88hROPshXnjKtfY
8vBgs5Qvr+K0hwc3mwtzxdUq105fUYDDg8y2F9jiwmONbr4uQih89WFbYxnu
mmvXxcXhgTGtzy7M1gV+Dr5pG7cIF8aYRyZ3C9uVbcCQfsB2rc/lO0Tr2pVv
ZB7+maYPBmtj1MuZeT0zl0kbw1NV1sumsNUDI3yDbX5YOfNzVdy6JhTt1viF
edFlNyV0NgxMJuK42f4htYeey4vhh6m5zlbelxx+6dd1h6XxU+GqzI1H/Zn1
p+b9S/P8/PTs+fi3NM6cnT09Hx5kvqvaZnthfnQb87/O7k7l1rYoL8ycapm5
We9Ff13ywSzza+r81lWdk80sG9/VF2Yy8oaJmFTsPPnom5uiWpo3HCYPdP7x
+L8Wrl3MoGx5bptsheertq3DxckJh/MnKGCWxp3wh5N54zfBnYy8+2RC2ehx
zdq2eEMk/On7y7MnZ2fp8/np+Tf956dnz9LnJ+dPnvSfn58/T5+/fvrkafr8
zdOz0/T52/Nn5/3n50/7z8/Pn+laV9NXIvG0RuD6asqF50XY/wyCjJ+Vvluu
KredVm7TNjdTxOY0FL+56aJow9SWZT8Svr8OmGEc5JWfuk91ARunUTelq0JR
TUObT6tuPYcz9c8q37ZVkd1MRaDcZQXjdHh+07lV6TZFlU+bsFlOuzq3rQvT
1i4vqO/pdIoACG1js5bfP6yKYPIEUhAq60JwAYENHLShdhnCGW6chmCwC1lT
zOEnAE24u2Bi6DGxjsDXrmxrVvbWmblzlfEIidbe4NN8a9wtZzoGGgSzcWWJ
hUyR47disaX/yeJLYO7s8OCqRQwwngwXC8Wn6dpX7cqozijaLpKFYxkIBCw1
AlXKduOhT7t090U9Foi/tU3hO+wVoxsD+Oscl1f9cGL8JrjgcuOrckuM84g2
Y5PWYIdZUvG6yPPS8dsjytf4vMtaDEiB+/ujgr9+HkzwZ5cQYfGgcZlvcnNT
+U01iHu14O4bx5kK6sWFlomLKtBBhweNLYLLRU1bE1a+K3OqYm7nWHIOBdXQ
nPEdX8RCwdW2gQ8dm7XHxAsvHoL3RWQu+hpZiobgIgtfln4jRnSy4wDzwZtz
WtAaOlSxKDIVRtT1o2+desvvvz8QhZ8/y673PNdI/Aw92hImz6mzjtJU6kQq
VUibnyENq0r/hW9iEChqs3JidPx1ePD+p3eX7340H98k1czpTNnKNtSmqD5t
yAh0labpSmcwoloicPAbMyhk6I1CEycJMB30A9xEdDUNX8lpn8obaLktsg74
iVTG2bnlTQFXh2tuJdzsmtlA49G1RHj1sLdWYPtOIOA7ghzAykGvP9WukXSF
oAzc26ZSrdNqMZjwFtZFjBmJsbAvuiRoIwao7L//HoH68+dj8buy7MALtrIB
jykrU8I0wgo2VrzbLaCmVqN7/MbcZbaDtfIYyZ7y9hFhyqKCG1aAj4YRYeva
2eYvkCF3Lh+hEdJQBfVU9Li6m5fwt5iVokOsZwYr75cK+5ekrggodAVWdQ65
HzMtXYy+BUJrxciUwKVI27HmxHAVyVSxrOjxFvCqPjIzEvGyaEiLUleY0XdN
pk4kdknLU+TgyltH/adtfgX7wIiZ0BHav39fEa1GYAFSkX+2ERLT9AIhxRqb
hDqKCjkGRHEOJxbwY5TkecHogHPbZhmBH1tgMCzgg7T74YHG4xdz2ufPvf+P
kQE+RcsKSJlrBQpzPjuneUbuJBlLARNxu+uJ6rwETBo4rGAXy50xq8NxmpSA
AvZNf3A9beoqtUOegPFu3OQFAr6lP9IOgnqYrBqZN01FKxMo5071D1tAVzmm
nqvOr15fv5FZ1A2tbHQkZ9FPFYp1DUNBWGS73Cwav/6ycKLYq+pLqHmEGajj
YNKOWz/W6V6VUmWSskE19EN6+Z420kS9zyOVw0PWtrlRc7ymE/AjPGZtt4ql
ow1KjN0WbtOrIaaRDM6ibiHb/EjBmNKhoRXDvmLc5piReyt9IHr73QT0/+08
D/nGHaeAtI1u2PfFyl5nECVBJKodEcYEIOg9zv0FucBGWXqaTDi9AO+g90kR
oX8iPo7ChaIkWBy7Jys7neexJC2rPOuVbS054o1rjpKjKTPC6jkABlKu1OfF
KBMJdxcm93LIX4wrUnYdWA6yiMiHV3NgZ4mcnIvii3YUCQLhMUhTWaFg8iD7
SxokZEFjKUM9SByAp3MyHfUG+CTUU/WUaYUMETPx3Bela+oSTGjPsjERX0Ml
Jch/6+o9bQJOc/3hlYmc/o/TcuLSdDVXulsrMG85IZIi9pbWODx4jCGWEF/k
HVBbvTw9PmJwJIn7X7nj4KluFm0pflDmj1ZV731g1V5Q5ZtgosJjWFrAu0t2
OYrFAk+5vblrNwSTSMaRgKtE0pWx358+CoIiMWikoWyBKNE+cZ0Yf+Jdwkrq
NkbKmJccHkhCRlGVuxofGieoY/KOM/axYH5AUjaXliUJjCXoPYSfdF+WZJEf
IqxKnJY7EQXfdXQ+jW7spUVRkVLcKEPA77YqIutRUieuCKLpXYgOnxJvF0ZE
i1Ut+LBwEBQVNJgURvcLME89myTyv5PS/7CgRVo3dN8XlYICnFhKRcIVqh9F
8GrRCWgJpRMFjZyfw4jdLO16ZTxQ/CblAFbDWC8k0Yz1xoEHksDRE2Fq9ymD
kamAqq8twPGrvT4cC2Rij58HX7pWCBIR7068qJsOezDMO4HQUboldLu22RZ6
LoMfyi34HQE+1iYrlmQA6La3Jnsd3N5mVQB8CQHKbiXvqmgMbkJUzJ9JSFHo
l3K/QNJj8VRWd/BKFPFO0RG1bnAS4C8v3yeTJCmStJpJgdRkxD2sRfeamZeQ
iTPM4QKiFZpoZzoFVbhW7B1wK5uV548AqppVFEknJ2FzLaRITC7CCdnhyPlA
ZctHnVZYX3Kf0JqllnAxcUaJ40yzI8lgmtBLj8m0JTEHbWBmFgeZfBiRLZR0
yDzw3Xv+EmaTSEdQEa4TaPbvbaRkxO66EptfmA08AO5Z2kzW0T5EW0DGNYCh
YYeitDllzt2i0HTFKBwCXXCr31DJZMn8k14/ls4oM/A9f518F3sLw1Ly9iaV
tRZZsllibcx3b6PHd3IIC79qFDdKFLYShA+VgzPph7J2BlQjz/2moIjl9gYY
m52iPSZ+LgDsanVS8qPYC9xD6nZS2mg5DRKLuFvCddyycU4aQjpBC7CtJFH1
CpJEzzeW2jsn3XSirLJwiz7f9ZxduxlOUlWL+CsJI/Qq5iXJnDl7aaMScI6J
gaLRcdJE/UaYHroKoiTShfIQuBqhD0rmvqz21QZPRpYuiz1FhzY07kHerj8g
Tqus7GKQ7UdJScERjnp+S7bkxaD72MXMvIVzpZCG2x8eyHIh+h9hSKm0WQvx
BCqVECaCt7BrbWsI0QxKCxHMhweXoCuiz+RNkgAzcEh+GSeZgtgLPK6cQ8qd
RRjoA2Dpfc4oZb7vE+hUeG9sQZhfG/evjjXMr/T/B9J7bHWN07l5jA2q9OIz
LPTSMKmTtLqKuh9q0aEgwVRHEkBVKvlhVY2QvgG123GLHaZCFLJVhBTXyFjc
Q7Xir+LVYmjBWrcZ2r8RqSQZxrxI+K/JlqQ3WjkNwDPkOal8SP2sdFLAm0g3
2IupSXCEpMEnYJVGeWuxo7vYItkwQmomHARoXfqtCMI4RDnCRLPoShPnEPLi
esb8nYhyPhYlNuHGLp35hgUz2zsNJrHHSdOpFamWVJKg2pUWlBXV7MpMR1/Y
ouS/o8053YovaRLoKKhkT8aSVcjN2I02ZMzCMQRd+IIsa2AWVZhBN+xf7grC
pk/pPiGIda2n4NMaB4JqvvRLVlDquiJuen/PenEceIJtJU0LGaLcG9IEeFvb
sB7PR5Mfw2tgiyLsNW2OIr/iIUP7sHsc953lu+buSKtiWMN5hQ8uE/H4Tiut
Vw5Oo/LDsdssdpka9xWbfiUjGDNkRArieiMMlxOuna0ET/B4ksdZ3OTYTBKz
4mf1/olIhtoWasknkYOyhVEKEDIprV1rMdTOwPGdgk3ksQ8fxMSm2CPzN1RM
a1ttzct33+vGEqGWUCZ8DXyIAnMc0cpvgGbmo5Psm3Xw8KpFVLOdspHORiUQ
EWjOWPr4rpF2IZvVYG+apVEF/3FvHXZywnRKVIqtgtFIpIJFB1O6+R5eTeEf
Q8wjvCVFkxQiCArWCBJSsX0RzyL7fD4cAwBmETc2/v4q9rvM2xf/kzzVrBBr
UpRWxIPSw4vYrntIljjV2jl667HZ6WBLQ/6YUi55PCROl1hW6Oqa3VkpheMs
O/Lj7YVUpjwyb9uU7uJxQU8PCd1SUL54OeoDaXFtyxk+Uw/vGqVUua++agfN
fCDoZAUqZcZK2u8o9UXcv9PQ8Sy99Vckc1DtIh6IQTt/ZDRREU/mkqQ6j7NN
uTXxwDYROT2EhnME1RMiio5SWRhk52RMZprN0qefhap3VRfYsMiKBkmISZj5
h/bvLU8CC7xR6lVI5x+gKJGfxCvlTIXhQZXTzmoyZmYfm92zGD2xaIQ70mKK
jnwjztWuyBL5QkgcLJ0l9qZkHSH4j73KDGTZmEblmBDrP76ZUk9wiImsC1HV
CmUqrBI5nQxDOXKita7PMhsk45Xbfh+HBwikocTUtosdOiFEPAgrbqhCyAE+
v9I8QYuowwOWksKvtomG2BA8qEGid6rLvnUfEaYnCmr9vpqMPUCUaowoDYD4
RhJtFosans8DUaQCtJSpyAyLWznuvKp612JQvNBcRVNwZxsgubQ9vwRVI5kA
5rdOTZPxHKmpIuruOJf4yVWVF7faOLvu775Ify41br6Znc3O7pxOaD8vDniW
Hj9YkEPt2pNkEkzLDVdtggG0Ib7nIDeLcjuE/4tRb8dm6cyyQJGg9hIn6htL
apr77d2PO6h1t/y2dxkIMnV7JwxTsIFnFxo1fdcMSkAgINUiRjEwsZqMxEVA
Znd22KfHlbtut3MF5XjvzuyOBlvfB65G56w/UwftuNUGjRz5agdBAnjtJH2B
Z9cIIyhWe9+9g8/Gtn9671zKyCbYo0qGiTVDf0lCiEBcX1yQEmji8STVae6v
OdXLy/ch1SbMtWwCkeoQQVuvVXBMjcMB+otXUtUI7ogxvfap057iIbQduVhq
8BTx8ARUaU+c7g2w/hxeTqkl3DOtwtIGYZhMAtT8wjqJWmZ1JKzwH4/TBaF8
OFcYLghBbSchjZ1ixuV02RU5U8EUi/M22zQde03jXrHQ1C+mvcYh4um3p0/O
T0+OZokhLopq3NzVrcXLQ6zQ2Kz6+tlRypRQVUnSjb2hvJXZqXhpzBTjfMvJ
wPf0eoBu3iXAkXhMNZJwPsF1Wek4FSw2V/YynISyWAc9jkG1f8nxWemTERrx
DlPaztnZEY9RUv1BD4wltLSBWr20MEy5cXMU1q3WUtfdEsWTJDRQXi2efVQg
m9xkDCNa0oslJ1hdRdLZ1OQmPMtZII1KfHB9WBms+7ehdmF3oecp5taXHRRB
I7A/yBS9UyjMhb1LjoB2a4+iYHusqYtwsO35nVT9q6I2lr2ePpIfD+RylDYH
5Vcpg9e8mdIfCg+3dtg0+jcY87EZzpSgFbnaJFClHZm6a6iAZNsedI7Ucb/3
DYR6a//pUCLyp8nOL5NUFtSrhgCbTgekkGCtBtsFrVBzIq5u/PCgGi6rhNRM
njf+RpCRbZ9K72UZZqnGaRSwzZDa+SwC5caANqOK6lYdHlSli93atb0RPOBz
XairyJfZf0BCJ5jLCp8sC0be/utdEWAEGwiNj/u7fPffV6+mZ8+BOfCDdZHx
9o6WR3ECbYccHpDAwAMbORoiKoqq3ZrO2BRyliiNDXIlOAgMKi0nOVNC1s1u
5IZEPEX60a8veW+SZyMARXGgSEXWfi3+OJI5nbaM7sfJsYNpAXKlSwfwIOjH
Zuti9zBtqL9RIj303UpBTqN+uJSdQKtpd/2NP/aVl8g9JVeHUZIgqnZOEQ3e
Q7uJ19F2oFlZDvYljFdypZoz5huZNu8aTKQ1KasintojS/fH1fEUB/jGE1ys
vp4Xy853gWkiPouhmu5M9T2nx+22ZhNWaC4g7Igngywyydvo31J4AElSX6xn
u0UYTkplU6l3JsGdNoipeIetbUs3nKmONnRsel5eEJuqf3ZVatOxbIazAVVy
ObErJErk2lGZOBT0ek1n6hdkNsioIabKHfxOJuqqUo41Kxgwdlv6MwJhcyyT
7+jpvhv+KS9MZW7MALzHxtvkMUVeUv4qdFDYnB3dLH0fWMAD903JBLRJTGVH
WReNXTuGu+QYZO1Mrgh8fDNMPFNni70yZCS2s8u755Ca13ivt8faeIe3b51A
9AXSgF6GSzcdpYgeFU7HrMioZOHXbPhk8bXxWxNJOGubMxOAhMUbZEPZNBty
nZzQ+dHxgCSafJSxBSEfWkeiMr0dE9lu+pnJmZ20VaWtAM+SYUW8FdbjAvxt
sTge09lw3Heort6/vUzp5N3QUBK7XsUusd63JZUfHYLTUFgu7+v7dPCipz/y
DVlu12DMLr8MHG+JuOnmvHx+Ik6zWcYEeRJp5IkKcyTi/tlXNbemV2ex26d3
GOhQQJnS1hq07fhSs14y5RW34XpvjJfpqJOnnYHh2sidTW02m4GwxtdP4uX1
suecVy9+fCFRxe68up1ecdUnNt6IlR7EcCTxiLROT2Tuv3vngnaqb5UP0wHT
AZFjk0BnSaATz2RS3ZvxsnDp8uWA/D8Hx46rllhsEFCnzNJFuqMFCTxUS3R5
TdreAuXfW7zzN9BmcA58/U+/qsx/6bk9vr5FjWFdaX7ivyiOpE/DL+balr9x
AGuICkElFwfjwWK8epguUM+RPmOk6yHRD35p/v4LHfB1XoAmXJi6lM64Xij7
+z9k9CM9tZyenspE5l1TLAseG8j/yGB0jged6aAXuR7A7KnK0yn+1Fyzx63x
MqaGuxOe64TxgCodLX/x0Ei9Id2Ki+1EbnN0SWx3kSdjqSf3ypzJ7uinOvpt
79ijCwz95uJcyjPXkWfygRBnyCzuG+s7pIWwu8bXY4nu8Iu0yHj8Nzqek0cV
2cBDUnHxeIR35zbB/ZsE0/R/RQDSKLP/g798RPWQu5atPZYrfdr5bhCv9oLH
wpDjXW/pDgwAOcj57Xhf+yBdjF208Wx/Oi/GKXijMM4mb83WyB0lPNPJf4qW
n1xG7e5eLJsMNTvvVyEW8lJpQgTTnTnu7F+SxeOGt3mORsr4wznNsOv+hERO
WWbgvjK5HjClS/TD8HGuH7kXWG6VejxE3NCmgJS0nJalzSPQi89iHdAvCXdh
Cel0z8pagvuNixfMwuzg/wDU9XNCyDcAAA==

-->

</rfc>
