wdiff rfc9141xml2.original.xml rfc9141.xml

<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.3.21 -->

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<?rfc rfcedstyle="yes"?>
<?rfc toc="yes"?>
<?rfc tocindent="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc docmapping="yes"?>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-danyliw-replace-ftp-pointers-06" category="std" number="9141" updates="2077, 2418, 2648, 2954, 2955, 3020, 3083, 3201, 3202, 3295, 3684, 3962, 3970, 4036, 4131, 4251, 4323, 4546, 4547, 4639, 4682, 5098, 5428, 6756, 7241"> 7241" obsoletes="" submissionType="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3">

  <!-- xml2rfc v2v3 conversion 3.10.0 -->
  <front>

    <title abbrev="Updating References to the IETF FTP Service">Updating FTP">Updating References to the IETF FTP Service</title>
    <seriesInfo name="RFC" value="9141"/>
    <author initials="R." surname="Danyliw" fullname="Roman Danyliw">
      <organization>Software Engineering Institute</organization>
      <address>
        <email>rdd@cert.org</email>
      </address>
    </author>
    <date year="2021" month="October" day="22"/> month="November"/>
    <area>General</area>
    <workgroup>Network Working Group</workgroup>
    <keyword>Internet-Draft</keyword>

    <abstract>
      <t>The IETF FTP service running at ftp.ietf.org, ops.ietf.org ops.ietf.org, and ietf.org will be retired.  A number of published RFCs in the IETF and IAB streams include URIs that reference this FTP service.  To ensure that the materials referenced using the IETF FTP service can still be found, this document updates the FTP-based references in these affected documents with HTTPS URIs.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro" title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>After community consultation in late 2020, it was decided to retire the IETF FTP service running at ftp.ietf.org, ops.ietf.org ops.ietf.org, and ietf.org <xref target="FTP-RETIREMENT"/>. target="FTP-RETIREMENT" format="default"/>.  Appendix B of <xref target="FTP-RETIREMENT-PLAN"/> identified target="FTP-RETIREMENT-PLAN" format="default"/> identifies 30 RFCs published in the IETF and IAB streams between 1997-2006 that had have at least one explicit or inline reference to a URI pointing to the IETF FTP service.   To ensure that the materials referenced using the IETF FTP service can still be found, this document formally updates those RFCs that had not been updated by other
documents with HTTPS URIs to the same materials.</t>
      <t><xref target="updates"/> target="updates" format="default"/> enumerates each of the affected RFCs and provides replacement text.</t>
    </section>
    <section anchor="conventions-and-definitions" title="Conventions numbered="true" toc="default">
      <name>Conventions and Definitions">

<t>The Definitions</name>
              <t>
    The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and “OPTIONAL” "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
    described in BCP 14 BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/>
    when, and only when, they appear in all capitals, as shown here.</t> here.
        </t>

      <t>The original text from an RFC to be updated will be quoted with “OLD” "OLD", and the replacement text will be quoted with “NEW”.</t> "NEW".</t>
    </section>
    <section anchor="updates" title="Updated References"> numbered="true" toc="default">
      <name>Updated References</name>
      <t>This document updates the following RFCs.</t>
      <t><xref target="RFC2077"/> target="RFC2077" format="default"/> <xref target="RFC2418"/> target="RFC2418" format="default"/> <xref target="RFC2648"/> target="RFC2648" format="default"/> <xref target="RFC2954"/> target="RFC2954" format="default"/> <xref target="RFC2955"/> target="RFC2955" format="default"/> <xref target="RFC3020"/> target="RFC3020" format="default"/> <xref target="RFC3083"/> target="RFC3083" format="default"/> <xref target="RFC3201"/> target="RFC3201" format="default"/> <xref target="RFC3202"/> target="RFC3202" format="default"/> <xref target="RFC3295"/> target="RFC3295" format="default"/> <xref target="RFC3684"/> target="RFC3684" format="default"/> <xref target="RFC3962"/> target="RFC3962" format="default"/> <xref target="RFC3970"/> target="RFC3970" format="default"/> <xref target="RFC4036"/> target="RFC4036" format="default"/> <xref target="RFC4131"/> target="RFC4131" format="default"/> <xref target="RFC4251"/> target="RFC4251" format="default"/> <xref target="RFC4323"/> target="RFC4323" format="default"/> <xref target="RFC4546"/> target="RFC4546" format="default"/> <xref target="RFC4547"/> target="RFC4547" format="default"/> <xref target="RFC4639"/> target="RFC4639" format="default"/> <xref target="RFC4682"/> target="RFC4682" format="default"/> <xref target="RFC5098"/> target="RFC5098" format="default"/> <xref target="RFC5428"/></t> target="RFC5428" format="default"/></t>
      <t>Additionally, with permission of the IAB, <xref target="RFC6756"/> target="RFC6756" format="default"/> and <xref target="RFC7241"/> target="RFC7241" format="default"/> are also updated.</t>
      <section anchor="rfc2077" title="RFC2077">

<t>Section 3 of <xref target="RFC2077"/> numbered="true" toc="default">
        <name>RFC 2077</name>
        <t><xref target="RFC2077" sectionFormat="of" section="3"/> is updated as follows:</t>

<figure><artwork><![CDATA[
	<t>
OLD:
</t>
<blockquote>
  <t>
Copies of RFCs are available on:
</t>
<t indent="3">
               ftp://ftp.isi.edu/in-notes/
</t>
<t>

Copies of Internet-Drafts are available on:

                    ftp://ftp.ietf.org/internet-drafts/

NEW:
</t>
<t indent="3">
               ftp://ftp.ietf.org/internet-drafts/</t>
</blockquote>
	       <t>

NEW:
	       </t>
	       <blockquote>
<t>

Copies of RFCs are available on:
</t>
<t indent="3">
              https://www.rfc-editor.org/rfc/
</t>
<t>

Copies of Internet-Drafts are available on:
</t>
<t indent="3">
               https://www.ietf.org/id/
]]></artwork></figure>
</t>
	     </blockquote>
      </section>
      <section anchor="rfc2418" title="RFC2418">

<t>Section 2.2 of <xref target="RFC2418"/> numbered="true" toc="default">
        <name>RFC 2418</name>
        <t><xref target="RFC2418" sectionFormat="of" section="2.2"/> is updated as follows:</t>

<figure><artwork><![CDATA[

<t>
  OLD:
</t>
<blockquote>
<t>
Those archives are located at ftp://ftp.ietf.org/ietf-mail-archive.

NEW:
</t>
</blockquote>
<t>

NEW:
</t>
<blockquote>
<t>

Those archives are located at
https://www.ietf.org/ietf-ftp/ietf-mail-archive/.
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-&wj;mail-archive/. </t>
</blockquote>
      </section>
      <section anchor="rfc2648" title="RFC2648">

<t>Section 2 of <xref target="RFC2648"/> numbered="true" toc="default">
        <name>RFC 2648</name>
        <t><xref target="RFC2648" sectionFormat="of" section="2"/> is updated below.  Note that the scripts in Appendix A <xref target="RFC2648" sectionFormat="bare" section="A"/> have not been updated.</t>

        <t>OLD:</t>
<blockquote>
        <t>The list of minutes maintained by the IETF for each working group and conference in the subtree pointed at by the URL ftp://ietf.org/ietf/ is
considered the definitive assignment of URNs for working group or birds of a feather minutes.</t> minutes.</t></blockquote>
<t>NEW:</t>
<blockquote>
        <t>The list of minutes maintained by the IETF for each working group and conference in the subtree pointed at by the URL https://www.ietf.org/how/meetings/proceedings/ is considered the definitive assignment of URNs for working group or birds of a feather minutes.</t>
</blockquote>
      </section>
      <section anchor="rfc2954" title="RFC2954"> numbered="true" toc="default">
        <name>RFC 2954</name>
        <t>The CONTACT-INFO in the MIB in Section 3 of <xref target="RFC2954"/> target="RFC2954" sectionFormat="of" section="3"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
OLD:

<t>OLD:
</t>
<blockquote>
<t>
          Email Archive: Archive:</t>
<t indent="3" >

            ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
</t></blockquote>
<t>
NEW:
</t>
<blockquote>
<t>

          Email Archive:
            https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
]]></artwork></figure>
</t>
<t indent="3">
            https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/</t>
</blockquote>
      </section>
      <section anchor="rfc2955" title="RFC2955"> numbered="true" toc="default">
        <name>RFC 2955</name>
        <t>The CONTACT-INFO in the MIB in Section 4 of <xref target="RFC2955"/> target="RFC2955" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>

          Email Archive: Archive:</t>
	  <t indent="3">

            ftp://ftp.ietf.org/ietf-mail-archive/frnetmib

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

          Email Archive:
            https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
]]></artwork></figure>
</t>
<t indent="3">

          https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/</t>
</blockquote>
      </section>
      <section anchor="rfc3020" title="RFC3020"> numbered="true" toc="default">
        <name>RFC 3020</name>
        <t>The CONTACT-INFO in the MIB in Section 3 of <xref target="RFC3020"/> target="RFC3020" sectionFormat="of" section="3"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
<t>

OLD:
</t>
<blockquote>
<t>

          Email Archive:
            ftp://ftp.ietf.org/ietf-mail-archive/frnetmib

            ftp://ftp.ietf.org/ietf-mail-archive/frnetmib</t></blockquote>
<t>

NEW:
</t>
<blockquote>
<t>

          Email Archive:
            https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
]]></artwork></figure>

            https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/</t>
</blockquote>
      </section>
      <section anchor="rfc3083" title="RFC3083"> numbered="true" toc="default">
        <name>RFC 3083</name>
        <t>The CONTACT-INFO in the MIB in Section 4 of <xref target="RFC3083"/> target="RFC3083" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[

<t>

OLD:
</t>
	<blockquote>
<t>

      Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
</t></blockquote>
<t>
NEW:
</t>
	<blockquote>
<t>
      Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/</t>
</blockquote>
      </section>
      <section anchor="rfc3201" title="RFC3201"> numbered="true" toc="default">
        <name>RFC 3201</name>
        <t>The CONTACT-INFO in the MIB in Section 6 of <xref target="RFC3201"/> target="RFC3201" sectionFormat="of" section="6"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[

<t>

OLD:
</t>
	<blockquote>
<t>

    Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib

NEW:
</t>	</blockquote>
<t>

NEW:
</t>	<blockquote>
<t>

    Email Archive:
    https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/</t>
</blockquote>
      </section>
      <section anchor="rfc3202" title="RFC3202"> numbered="true" toc="default">
        <name>RFC 3202</name>
        <t>The CONTACT-INFO in the MIB in Section 7 of <xref target="RFC3202"/> target="RFC3202" sectionFormat="of" section="7"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
<t>

OLD:
</t>
	<blockquote>
<t>

    Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

  Email Archive:
    https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/</t>
</blockquote>
      </section>
      <section anchor="rfc3295" title="RFC3295"> numbered="true" toc="default">
        <name>RFC 3295</name>
        <t>The CONTACT-INFO in the MIB in Section 4 of <xref target="RFC3295"/> target="RFC3295" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>

Email Archive: Archive:</t><t indent="3"> ftp://ftp.ietf.org/ietf-mail-archive/gsmp/

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

Email Archive:
               https://www.ietf.org/ietf-ftp/ietf-mail-archive/gsmp/
]]></artwork></figure> Archive:</t><t indent="3">         https://www.ietf.org/ietf-ftp/ietf-mail-archive/gsmp/</t>
</blockquote>
      </section>
      <section anchor="rfc3684" title="RFC3684">

<t>The numbered="true" toc="default">
        <name>RFC 3684</name>
        <t>Two informative references in Section 14.2 of <xref target="RFC3684"/> target="RFC3684" sectionFormat="of" section="14.2"/> are updated as follows:</t>

<figure><artwork><![CDATA[
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>
[7]  Ogier, R., Message in IETF email archive for MANET,
     ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-02.mail, February 2002.

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>
[7]  Ogier, R., Message in IETF email archive for MANET,
     https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/
     2002-02.mail,
     https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/2002-02.mail, February 2002.
]]></artwork></figure>
<figure><artwork><![CDATA[
OLD:
</t>
</blockquote>

<t>OLD:</t>
<blockquote>
<t>
[9] Ogier, R., Message in IETF email archive for MANET,
ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-03.mail,
March 2002.
</t></blockquote>
<t>

NEW:
</t>
<blockquote>
<t>

[9] Ogier, R., Message in IETF email archive for MANET,
    https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/
    2002-03.mail,
    https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/2002-03.mail,
     March 2002.
]]></artwork></figure> 2002.</t>
</blockquote>
      </section>
      <section anchor="rfc3962" title="RFC3962">

<t>The numbered="true" toc="default">
        <name>RFC 3962</name>
        <t>An informative reference of in <xref target="RFC3962"/> target="RFC3962" format="default"/> is updated as follows:</t>

<figure><artwork><![CDATA[
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>

[LEACH]    Leach, P., email to IETF Kerberos working group mailing
           list, 5 May 2003, ftp://ftp.ietf.org/ietf-mail-
           archive/krb-wg/2003-05.mail.

NEW: ftp://ftp.ietf.org/ietf-mail-archive/krb-wg/2003-05.mail.
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

[LEACH]    Leach, P., email to IETF Kerberos working group mailing
           list, 5 May 2003, https://www.ietf.org/ietf-ftp/
           ietf-mail-archive/krb-wg/2003-05.mail.
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-mail-archive/krb-wg/2003-05.mail.
</t>
	 </blockquote>
      </section>
      <section anchor="rfc3970" title="RFC3970"> numbered="true" toc="default">
        <name>RFC 3970</name>
        <t>The CONTACT-INFO in the MIB in Section 5 of <xref target="RFC3970"/> target="RFC3970" sectionFormat="of" section="5"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>

   Archive:          ftp://ops.ietf.org/pub/lists

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

   Archive:
   https://www.ietf.org/ietf-ftp/concluded-wg-ietf-mail-archive/tewg/
]]></artwork></figure>
   https://www.ietf.org/ietf-ftp/concluded-wg-ietf-mail-archive/tewg/</t>
</blockquote>
      </section>
      <section anchor="rfc4036" title="RFC4036"> numbered="true" toc="default">
        <name>RFC 4036</name>
        <t>The CONTACT-INFO in the MIB in Section 4 of <xref target="RFC4036"/> target="RFC4036" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
<t>
OLD:
</t>
<blockquote>
<t>

          Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn

NEW:
</t>
</blockquote>
<t>

NEW:
</t>
<blockquote>
<t>

          Archive:
          https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure>
</t>
</blockquote>
      </section>
      <section anchor="rfc4131" title="RFC4131"> numbered="true" toc="default">
        <name>RFC 4131</name>
        <t>The CONTACT-INFO in the MIB in Section 3 of <xref target="RFC4131"/> target="RFC4131" sectionFormat="of" section="3"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
OLD:

<t>OLD:
</t>
<blockquote>
<t>

         Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn.
</t></blockquote>
<t>

NEW:
</t>
<blockquote>
<t>

         Archive:
         https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/.
]]></artwork></figure>
</t>
</blockquote>
      </section>
      <section anchor="rfc4251" title="RFC4251">

<t>The numbered="true" toc="default">
        <name>RFC 4251</name>
        <t>An informative reference of in <xref target="RFC4251"/> target="RFC4251" format="default"/> is updated as follows:</t>

<figure><artwork><![CDATA[

	  <t>
OLD:
</t>
	<blockquote>
<t>

[DAI]              Dai, W., "An attack against SSH2 protocol", Email
                   to the SECSH Working Group ietf-ssh@netbsd.org
                   ftp:// ftp.ietf.org/ietf-mail-archive/secsh/2002-
                   02.mail, ftp.ietf.org/ietf-mail-archive/secsh/2002-02.mail, Feb 2002.

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

[DAI]              Dai, W., "An attack against SSH2 protocol", Email
                   to the SECSH Working Group ietf-ssh@netbsd.org
                   https://www.ietf.org/ietf-ftp/ietf-mail-archive/
                   secsh/2002-02.mail, Feb 2002.
]]></artwork></figure>
</t>
		 </blockquote>
      </section>
      <section anchor="rfc4323" title="RFC4323"> numbered="true" toc="default">
        <name>RFC 4323</name>
        <t>The CONTACT-INFO in the MIB in Section 5 of <xref target="RFC4323"/> target="RFC4323" sectionFormat="of" section="5"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
	<t>
OLD:
	</t>
		<blockquote>
<t>

      Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

      Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure>
</t>
    </blockquote>
      </section>
      <section anchor="rfc4546" title="RFC4546"> numbered="true" toc="default">
        <name>RFC 4546</name>
        <t>The CONTACT-INFO in the MIB in Section 4 of <xref target="RFC4546"/> target="RFC4546" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
OLD:
	  <t>
	  OLD:</t>
	  	<blockquote>
<t>

      Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

      Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure>
</t>
    </blockquote>
      </section>
      <section anchor="rfc4547" title="RFC4547"> numbered="true" toc="default">
        <name>RFC 4547</name>
        <t>The CONTACT-INFO in the MIB in Section 4 of <xref target="RFC4547"/> target="RFC4547" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[

	  <t>
OLD:
</t>
	<blockquote>
<t>

      Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

      Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/</t>
</blockquote>
      </section>
      <section anchor="rfc4639" title="RFC4639"> numbered="true" toc="default">
        <name>RFC 4639</name>
        <t>The CONTACT-INFO in the MIB in Section 4 of <xref target="RFC4639"/> target="RFC4639" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>
      Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

      Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure>
</t>
    </blockquote>
      </section>
      <section anchor="rfc4682" title="RFC4682"> numbered="true" toc="default">
        <name>RFC 4682</name>
        <t>The CONTACT-INFO in the MIB in Section 4 of <xref target="RFC4682"/> target="RFC4682" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[

	  <t>
OLD:
</t>
	<blockquote>
<t>

      Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
</t></blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

      Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/</t>
</blockquote>
      </section>
      <section anchor="rfc5098" title="RFC5098"> numbered="true" toc="default">
        <name>RFC 5098</name>
        <t>The CONTACT-INFO in the MIB in Section 5 of <xref target="RFC5098"/> target="RFC5098" sectionFormat="of" section="5"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[

	  <t>
OLD:
</t>
	<blockquote>
<t>

      Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

      Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/</t>
</blockquote>
      </section>
      <section anchor="rfc5428" title="RFC5428"> numbered="true" toc="default">
        <name>RFC 5428</name>
        <t>The CONTACT-INFO in the MIB in Section 6 of <xref target="RFC5428"/> target="RFC5428" sectionFormat="of" section="6"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<figure><artwork><![CDATA[
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>

      Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

      Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
]]></artwork></figure> https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/</t>
</blockquote>
      </section>
      <section anchor="rfc6756" title="RFC6756">

<t>Section 2.8.1 of <xref target="RFC6756"/> numbered="true" toc="default">
        <name>RFC 6756</name>
        <t><xref target="RFC6756" sectionFormat="of" section="2.8.1"/> is updated as follows:</t>

<figure><artwork><![CDATA[

	  <t>
OLD:
</t>
	<blockquote>
<t>

   Current list and status of all IETF RFCs:
</t>
<t indent="3">
      ftp://ftp.ietf.org/rfc/rfc-index.txt

</t>
<t>

   Current list and description of all IETF Internet-Drafts:
</t>
<t indent="3">
      ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt

NEW:
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

   Current list and status of all IETF RFCs:
</t>
<t indent="3">
      https://www.rfc-editor.org/rfc/rfc-index.txt

</t>
<t>

   Current list and description of all IETF Internet-Drafts:
      https://www.ietf.org/id/1id-abstracts.txt
]]></artwork></figure>
</t>
<t indent="3">
      https://www.ietf.org/id/1id-abstracts.txt</t>
</blockquote>
      </section>
      <section anchor="rfc7241" title="RFC7241">

<t>Section B.2 of <xref target="RFC7241"/> numbered="true" toc="default">
        <name>RFC 7241</name>
        <t><xref target="RFC7241" sectionFormat="of" section="B.2"/> is updated as follows:</t>

<figure><artwork><![CDATA[

	  <t>
OLD:
</t>
	<blockquote>
<t>

   Current list and description of all IETF Internet-Drafts:
   <ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt>

NEW:
</t>
<t>
    &lt;ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt&gt;
</t>	</blockquote>
<t>

NEW:
</t>
	<blockquote>
<t>

   Current list and description of all IETF Internet-Drafts:
   <https://www.ietf.org/id/1id-abstracts.txt>
]]></artwork></figure>
</t>
<t>
    &lt;https://www.ietf.org/id/1id-abstracts.txt&gt;</t>
</blockquote>
      </section>
      <section anchor="generic-guidance" title="Generic Guidance"> numbered="true" toc="default">
        <name>Generic Guidance</name>
        <t>If any other RFC not explicitly mentioned in an earlier section contains a reference of the form, “ftp://ftp.ietf.org/&lt;path&gt;”, this form "ftp://ftp.ietf.org/&lt;path&gt;", the reference MUST <bcp14>MUST</bcp14> be replaced with a URI of the form, “https://www.ietf.org/ietf-ftp/&lt;path&gt;”.</t> form "https://www.ietf.org/ietf-ftp/&lt;path&gt;".</t>
      </section>
    </section>
    <section anchor="seccons" title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This document does not alter the security consideration considerations of the updated documents.</t>
      <t>This document replaces URIs using an FTP scheme with equivalent URIs to the IETF infrastructure (i.e., www.ietf.org) that use HTTPS. an FTP scheme with equivalent HTTPS scheme URIs.  These updates  ensure the continued availability of content referenced in previously published RFCs when the IETF FTP service is retired.  Additionally, the replacement of the clear-text cleartext FTP with HTTPS will ensure that resources on the IETF infrastructure can be accessed in a more secure way.  For example, HTTPS provides an encrypted channel that includes protections protections, such as verifying the server’s server's identity per the certificate verification behavior of the client, client and integrity and confidentiality protection commensurate with the negotiated TLS protocol version and ciphersuite.</t>
    </section>
    <section anchor="iana" title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>

    <references title='Normative References'>

<reference  anchor="RFC2119" target='https://www.rfc-editor.org/info/rfc2119'>
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1997' month='March' />
<abstract><t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  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='14'/>
<seriesInfo name='RFC' value='2119'/>
<seriesInfo name='DOI' value='10.17487/RFC2119'/>
</reference>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>

<reference  anchor="RFC2077"  anchor='RFC2077' target='https://www.rfc-editor.org/info/rfc2077'>
<front>
<title>The Model Primary Content Type for Multipurpose Internet Mail Extensions</title>
<author initials='S.' surname='Nelson' fullname='S. Nelson'><organization /></author>
<author initials='C.' surname='Parks' fullname='C. Parks'><organization /></author>
<author initials='Mitra' surname='' fullname='Mitra'><organization initials='M.' surname='Ardron' fullname='M. Ardron'><organization /></author>
<date year='1997' month='January' />
<abstract><t>The purpose of this memo is to propose an update to Internet RFC 2045 to include a new primary content-type to be known as &quot;model&quot;.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2077'/>
<seriesInfo name='DOI' value='10.17487/RFC2077'/>
</reference>

<reference  anchor="RFC2418" target='https://www.rfc-editor.org/info/rfc2418'>
<front>
<title>IETF Working Group Guidelines and Procedures</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1998' month='September' />
<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="RFC2648" target='https://www.rfc-editor.org/info/rfc2648'>
<front>
<title>A URN Namespace for IETF Documents</title>
<author initials='R.' surname='Moats' fullname='R. Moats'><organization /></author>
<date year='1999' month='August' />
<abstract><t>This document proposes the &quot;ietf&quot; namespace, which consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC Editor and the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2648'/>
<seriesInfo name='DOI' value='10.17487/RFC2648'/>
</reference>

<reference  anchor="RFC2954" target='https://www.rfc-editor.org/info/rfc2954'>
<front>
<title>Definitions of Managed Objects for Frame Relay Service</title>
<author initials='K.' surname='Rehbehn' fullname='K. Rehbehn'><organization /></author>
<author initials='D.' surname='Fowler' fullname='D. Fowler'><organization /></author>
<date year='2000' month='October' />
<abstract><t>This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in Transmission Control Protocol/Internet Protocol-based (TCP/IP) internets.  In particular, it defines objects for managing the frame relay service.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2954'/>
<seriesInfo name='DOI' value='10.17487/RFC2954'/>
</reference>

<reference  anchor="RFC2955" target='https://www.rfc-editor.org/info/rfc2955'>
<front>
<title>Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function</title>
<author initials='K.' surname='Rehbehn' fullname='K. Rehbehn'><organization /></author>
<author initials='O.' surname='Nicklass' fullname='O. Nicklass'><organization /></author>
<author initials='G.' surname='Mouradian' fullname='G. Mouradian'><organization /></author>
<date year='2000' month='October' />
<abstract><t>This memo defines a Management Information Base (MIB) to configure, monitor, and control a service interworking function (IWF) for Permanent Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer Mode (ATM) technologies.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2955'/>
<seriesInfo name='DOI' value='10.17487/RFC2955'/>
</reference>

<reference  anchor="RFC3020" target='https://www.rfc-editor.org/info/rfc3020'>
<front>
<title>Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function</title>
<author initials='P.' surname='Pate' fullname='P. Pate'><organization /></author>
<author initials='B.' surname='Lynch' fullname='B. Lynch'><organization /></author>
<author initials='K.' surname='Rehbehn' fullname='K. Rehbehn'><organization /></author>
<date year='2000' month='December' />
<abstract><t>This memo defines a Management Information Base (MIB) for monitoring and controlling a UNI/NNI Multilink Frame Relay Function as defined in Frame Relay Forum FRF.16.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3020'/>
<seriesInfo name='DOI' value='10.17487/RFC3020'/>
</reference>

<reference  anchor="RFC3083" target='https://www.rfc-editor.org/info/rfc3083'>
<front>
<title>Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems</title>
<author initials='R.' surname='Woundy' fullname='R. Woundy'><organization /></author>
<date year='2001' month='March' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.  In particular, it defines a basic set of managed objects for SNMP-based (Simple Network Management Protocol) management of the Baseline Privacy Interface (BPI), which provides data privacy for DOCSIS 1.0 (Data-Over- Cable Service Interface Specifications) compliant Cable Modems and Cable Modem Termination Systems.  This MIB is defined as an extension to the DOCSIS Radio Frequency Interface MIB, RFC 2670.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='3083'/>
<seriesInfo name='DOI' value='10.17487/RFC3083'/>
</reference>

<reference  anchor="RFC3201" target='https://www.rfc-editor.org/info/rfc3201'>
<front>
<title>Definitions of Managed Objects for Circuit to Interface Translation</title>
<author initials='R.' surname='Steinberger' fullname='R. Steinberger'><organization /></author>
<author initials='O.' surname='Nicklass' fullname='O. Nicklass'><organization /></author>
<date year='2002' month='January' />
<abstract><t>This memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.  In particular, it defines objects for managing the insertion of interesting Circuit Interfaces into the ifTable.  This is important for circuits that must be used within other MIB modules which require an ifEntry.  It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3201'/>
<seriesInfo name='DOI' value='10.17487/RFC3201'/>
</reference>

<reference  anchor="RFC3202" target='https://www.rfc-editor.org/info/rfc3202'>
<front>
<title>Definitions of Managed Objects for Frame Relay Service Level Definitions</title>
<author initials='R.' surname='Steinberger' fullname='R. Steinberger'><organization /></author>
<author initials='O.' surname='Nicklass' fullname='O. Nicklass'><organization /></author>
<date year='2002' month='January' />
<abstract><t>This memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.  In particular, it defines objects for managing the Frame Relay Service Level Definitions.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3202'/>
<seriesInfo name='DOI' value='10.17487/RFC3202'/>
</reference>

<reference  anchor="RFC3295" target='https://www.rfc-editor.org/info/rfc3295'>
<front>
<title>Definitions of Managed Objects for the General Switch Management Protocol (GSMP)</title>
<author initials='H.' surname='Sjostrand' fullname='H. Sjostrand'><organization /></author>
<author initials='J.' surname='Buerkle' fullname='J. Buerkle'><organization /></author>
<author initials='B.' surname='Srinivasan' fullname='B. Srinivasan'><organization /></author>
<date year='2002' month='June' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for the use with the network management protocols in the Internet community. In particular, it describes managed objects for the General Switch Management Protocol (GSMP).  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3295'/>
<seriesInfo name='DOI' value='10.17487/RFC3295'/>
</reference>

<reference  anchor="RFC3684" target='https://www.rfc-editor.org/info/rfc3684'>
<front>
<title>Topology Dissemination Based on Reverse-Path Forwarding (TBRPF)</title>
<author initials='R.' surname='Ogier' fullname='R. Ogier'><organization /></author>
<author initials='F.' surname='Templin' fullname='F. Templin'><organization /></author>
<author initials='M.' surname='Lewis' fullname='M. Lewis'><organization /></author>
<date year='2004' month='February' />
<abstract><t>Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) is a proactive, link-state routing protocol designed for mobile ad-hoc networks, which provides hop-by-hop routing along shortest paths to each destination.  Each node running TBRPF computes a source tree (providing paths to all reachable nodes) based on partial topology information stored in its topology table, using a modification of Dijkstra's algorithm.  To minimize overhead, each node reports only *part* of its source tree to neighbors.  TBRPF uses a combination of periodic and differential updates to keep all neighbors informed of the reported part of its source tree.  Each node also has the option to report additional topology information (up to the full topology), to provide improved robustness in highly mobile networks.  TBRPF performs neighbor discovery using &quot;differential&quot; HELLO messages which report only *changes* in the status of neighbors.  This results in HELLO messages that are much smaller than those of other link-state routing protocols such as OSPF.  This memo defines an Experimental Protocol for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='3684'/>
<seriesInfo name='DOI' value='10.17487/RFC3684'/>
</reference>

<reference  anchor="RFC3962" target='https://www.rfc-editor.org/info/rfc3962'>
<front>
<title>Advanced Encryption Standard (AES) Encryption for Kerberos 5</title>
<author initials='K.' surname='Raeburn' fullname='K. Raeburn'><organization /></author>
<date year='2005' month='February' />
<abstract><t>The United States National Institute of Standards and Technology (NIST) has chosen a new Advanced Encryption Standard (AES), which is significantly faster and (it is believed) more secure than the old Data Encryption Standard (DES) algorithm.  This document is a specification for the addition of this algorithm to the Kerberos cryptosystem suite.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3962'/>
<seriesInfo name='DOI' value='10.17487/RFC3962'/>
</reference>

<reference  anchor="RFC3970" target='https://www.rfc-editor.org/info/rfc3970'>
<front>
<title>A Traffic Engineering (TE) MIB</title>
<author initials='K.' surname='Kompella' fullname='K. Kompella'><organization /></author>
<date year='2005' month='January' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.  In particular, it describes managed objects for Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3970'/>
<seriesInfo name='DOI' value='10.17487/RFC3970'/>
</reference>

<reference  anchor="RFC4036" target='https://www.rfc-editor.org/info/rfc4036'>
<front>
<title>Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management</title>
<author initials='W.' surname='Sawyer' fullname='W. Sawyer'><organization /></author>
<date year='2005' month='April' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for Simple Network Management Protocol (SNMP)-based management of Data-over-Cable Service Interface Specification (DOCSIS)-compliant Cable Modem Termination Systems.  These managed objects facilitate protection of the cable network from misuse by subscribers.  The Differentiated Services MIB (RFC 3289) provides the filtering functions needed here, making use of classification items defined in this specification.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4036'/>
<seriesInfo name='DOI' value='10.17487/RFC4036'/>
</reference>

<reference  anchor="RFC4131" target='https://www.rfc-editor.org/info/rfc4131'>
<front>
<title>Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modems and Cable Modem Termination Systems for Baseline Privacy Plus</title>
<author initials='S.' surname='Green' fullname='S. Green'><organization /></author>
<author initials='K.' surname='Ozawa' fullname='K. Ozawa'><organization /></author>
<author initials='E.' surname='Cardona' fullname='E. Cardona' role='editor'><organization /></author>
<author initials='A.' surname='Katsnelson' fullname='A. Katsnelson'><organization /></author>
<date year='2005' month='September' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for Simple Network Management Protocol (SNMP) based management of the Baseline Privacy Plus features of DOCSIS 1.1 and DOCSIS 2.0 (Data-over-Cable Service Interface Specification) compliant Cable Modems and Cable Modem Termination Systems.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4131'/>
<seriesInfo name='DOI' value='10.17487/RFC4131'/>
</reference>

<reference  anchor="RFC4251" target='https://www.rfc-editor.org/info/rfc4251'>
<front>
<title>The Secure Shell (SSH) Protocol Architecture</title>
<author initials='T.' surname='Ylonen' fullname='T. Ylonen'><organization /></author>
<author initials='C.' surname='Lonvick' fullname='C. Lonvick' role='editor'><organization /></author>
<date year='2006' month='January' />
<abstract><t>The Secure Shell (SSH) Protocol is a protocol for secure remote login and other secure network services over an insecure network.  This document describes the architecture of the SSH protocol, as well as the notation and terminology used in SSH protocol documents.  It also discusses the SSH algorithm naming system that allows local extensions.  The SSH protocol consists of three major components: The Transport Layer Protocol provides server authentication, confidentiality, and integrity with perfect forward secrecy.  The User Authentication Protocol authenticates the client to the server.  The Connection Protocol multiplexes the encrypted tunnel into several logical channels.  Details of these protocols are described in separate documents.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4251'/>
<seriesInfo name='DOI' value='10.17487/RFC4251'/>
</reference>

<reference  anchor="RFC4323" target='https://www.rfc-editor.org/info/rfc4323'>
<front>
<title>Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB)</title>
<author initials='M.' surname='Patrick' fullname='M. Patrick'><organization /></author>
<author initials='W.' surname='Murwin' fullname='W. Murwin'><organization /></author>
<date year='2006' month='January' />
<abstract><t>This document defines a basic set of managed objects for SNMP-based management of extended QoS features of Cable Modems (CMs) and Cable Modem Termination Systems (CMTSs) conforming to the Data over Cable System (DOCSIS) specifications versions 1.1 and 2.0.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4323'/>
<seriesInfo name='DOI' value='10.17487/RFC4323'/>
</reference>

<reference  anchor="RFC4546" target='https://www.rfc-editor.org/info/rfc4546'>
<front>
<title>Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF Interfaces</title>
<author initials='D.' surname='Raftus' fullname='D. Raftus'><organization /></author>
<author initials='E.' surname='Cardona' fullname='E. Cardona'><organization /></author>
<date year='2006' month='June' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for Simple Network Management Protocol (SNMP) based management of the Radio Frequency (RF) interfaces for systems compliant with the Data Over Cable Service Interface Specifications (DOCSIS).  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4546'/>
<seriesInfo name='DOI' value='10.17487/RFC4546'/>
</reference>

<reference  anchor="RFC4547" target='https://www.rfc-editor.org/info/rfc4547'>
<front>
<title>Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination Systems</title>
<author initials='A.' surname='Ahmad' fullname='A. Ahmad'><organization /></author>
<author initials='G.' surname='Nakanishi' fullname='G. Nakanishi'><organization /></author>
<date year='2006' month='June' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP) based event notification management of Data Over Cable Service Interface Specification (DOCSIS) compliant Cable Modems and Cable Modem Termination Systems.  This MIB is defined as an extension to the DOCSIS Cable Device MIB.</t><t>This memo specifies a MIB module in a manner that is compliant to the Structure of Management Information Version 2 (SMIv2).  The set of objects is consistent with the SNMP framework and existing SNMP standards.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4547'/>
<seriesInfo name='DOI' value='10.17487/RFC4547'/>
</reference>

<reference  anchor="RFC4639" target='https://www.rfc-editor.org/info/rfc4639'>
<front>
<title>Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems</title>
<author initials='R.' surname='Woundy' fullname='R. Woundy'><organization /></author>
<author initials='K.' surname='Marez' fullname='K. Marez'><organization /></author>
<date year='2006' month='December' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of Data Over Cable Service Interface Specification (DOCSIS)-compliant Cable Modems and Cable Modem Termination Systems.</t><t>This memo obsoletes RFC 2669.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4639'/>
<seriesInfo name='DOI' value='10.17487/RFC4639'/>
</reference>

<reference  anchor="RFC4682" target='https://www.rfc-editor.org/info/rfc4682'>
<front>
<title>Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices</title>
<author initials='E.' surname='Nechamkin' fullname='E. Nechamkin'><organization /></author>
<author initials='J-F.' surname='Mule' fullname='J-F. Mule'><organization /></author>
<date year='2006' month='December' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4682'/>
<seriesInfo name='DOI' value='10.17487/RFC4682'/>
</reference>

<reference  anchor="RFC5098" target='https://www.rfc-editor.org/info/rfc5098'>
<front>
<title>Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)</title>
<author initials='G.' surname='Beacham' fullname='G. Beacham'><organization /></author>
<author initials='S.' surname='Kumar' fullname='S. Kumar'><organization /></author>
<author initials='S.' surname='Channabasappa' fullname='S. Channabasappa'><organization /></author>
<date year='2008' month='February' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='5098'/>
<seriesInfo name='DOI' value='10.17487/RFC5098'/>
</reference>

<reference  anchor="RFC5428" target='https://www.rfc-editor.org/info/rfc5428'>
<front>
<title>Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices</title>
<author initials='S.' surname='Channabasappa' fullname='S. Channabasappa'><organization /></author>
<author initials='W.' surname='De Ketelaere' fullname='W. De Ketelaere'><organization /></author>
<author initials='E.' surname='Nechamkin' fullname='E. Nechamkin'><organization /></author>
<date year='2009' month='April' />
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of events that can be generated by PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='5428'/>
<seriesInfo name='DOI' value='10.17487/RFC5428'/>
</reference>

<reference  anchor="RFC6756" target='https://www.rfc-editor.org/info/rfc6756'>
<front>
<title>Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines</title>
<author initials='S.' surname='Trowbridge' fullname='S. Trowbridge' role='editor'><organization /></author>
<author initials='E.' surname='Lear' fullname='E. Lear' role='editor'><organization /></author>
<author initials='G.' surname='Fishman' fullname='G. Fishman' role='editor'><organization /></author>
<author initials='S.' surname='Bradner' fullname='S. Bradner' role='editor'><organization /></author>
<date year='2012' month='September' />
<abstract><t>This document provides guidance to aid in the understanding of collaboration on standards development between the Telecommunication Standardization Sector of the International Telecommunication Union (ITU-T) and the Internet Engineering Task Force (IETF) of the Internet Society (ISOC).  It is an update of and obsoletes RFC 3356.  The updates reflect changes in the IETF and ITU-T since RFC 3356 was written.  The bulk of this document is common text with ITU-T A Series Supplement 3 (07/2012).</t><t>Note: This was approved by TSAG on 4 July 2012 as Supplement 3 to the ITU-T A-Series of Recommendations.  </t><t>This document is not an Internet Standards Track specification; it  is published for informational purposes.</t></abstract>
</front>
<seriesInfo name='RFC' value='6756'/>
<seriesInfo name='DOI' value='10.17487/RFC6756'/>
</reference>

<reference  anchor="RFC7241" target='https://www.rfc-editor.org/info/rfc7241'>
<front>
<title>The IEEE 802/IETF Relationship</title>
<author initials='S.' surname='Dawkins' fullname='S. Dawkins'><organization /></author>
<author initials='P.' surname='Thaler' fullname='P. Thaler'><organization /></author>
<author initials='D.' surname='Romascanu' fullname='D. Romascanu'><organization /></author>
<author initials='B.' surname='Aboba' fullname='B. Aboba' role='editor'><organization /></author>
<date year='2014' month='July' />
<abstract><t>This document describes the standardization cooperation between Project 802 of the Institute of Electrical and Electronics Engineers (IEEE) and the Internet Engineering Task Force (IETF).  This document obsoletes RFC 4441.</t><t>Note: This document was collaboratively developed by authors from both the IEEE 802 and IETF leadership and was reviewed and approved by the IEEE 802 Executive Committee prior to publication.</t></abstract>
</front>
<seriesInfo name='RFC' value='7241'/>
<seriesInfo name='DOI' value='10.17487/RFC7241'/>
</reference>

<reference  anchor="RFC8174" target='https://www.rfc-editor.org/info/rfc8174'>
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
<author initials='B.' surname='Leiba' fullname='B. Leiba'><organization /></author>
<date year='2017' month='May' />
<abstract><t>RFC 2119 specifies common key words that may be used in protocol  specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the  defined special meanings.</t></abstract>
</front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='8174'/>
<seriesInfo name='DOI' value='10.17487/RFC8174'/>
</reference>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2418.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2648.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2954.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2955.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3020.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3083.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3201.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3202.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3295.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3684.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3962.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3970.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4036.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4131.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4251.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4323.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4546.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4547.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4639.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4682.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5098.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5428.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6756.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7241.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
      </references>

    <references title='Informative References'>
      <references>
        <name>Informative References</name>

        <reference anchor="FTP-RETIREMENT" target="https://mailarchive.ietf.org/arch/msg/ietf/vi-8bFqlgBFjB2jJ1SIAGHiNRdg/">
          <front>
            <title>Retirement of the IETF FTP Service</title>
            <author >
      <organization></organization> surname="Danyliw" initials="R.">
            </author>
            <date year="2021" month="March" day="03"/>
          </front>
	  <refcontent>message to the IETF mailing list</refcontent>
        </reference>

        <reference anchor="FTP-RETIREMENT-PLAN" target="https://www.ietf.org/media/documents/Revised-Retiring-IETF-FTP-Service-2021-03.pdf">
          <front>
    <title>(Revised Plan) Retiring
            <title>Retiring the IETF FTP Service</title>
    <author >
      <organization></organization> Service (Revised Plan)</title>
            <author>
              <organization/>
            </author>
            <date year="2021" month="March" day="03"/> month="March"/>
          </front>

        </reference>
      </references>
    </references>
    <section numbered="false" anchor="acknowledgments" title="Acknowledgments"> toc="default">
      <name>Acknowledgments</name>
      <t>Thank you to Robert Sparks, Glen Barney, Henrik Levkowetz and Russ Housley <contact fullname="Robert Sparks"/>, <contact fullname="Glen Barney"/>, <contact fullname="Henrik Levkowetz"/>, and <contact fullname="Russ Housley"/> on the IETF Tools Team for the operations and maintenance information that informed the community discussion at <xref target="FTP-RETIREMENT"/>.</t> target="FTP-RETIREMENT" format="default"/>.</t>
      <t>Additionally, thank you to Brian Carpenter, Martin Duke, Russ Housley, Benjamin Kaduk, Eric Kline, Murray Kucherawy, Mirja Kuehlewind, Scott Mansfield, Tom Petch, John Scudder, and Rob Wilton <contact fullname="Brian Carpenter"/>, <contact fullname="Martin Duke"/>, <contact fullname="Russ Housley"/>, <contact fullname="Benjamin Kaduk"/>, <contact fullname="Eric Kline"/>, <contact fullname="Murray Kucherawy"/>, <contact fullname="Mirja Kühlewind"/>, <contact fullname="Scott Mansfield"/>, <contact fullname="Tom Petch"/>, <contact fullname="John Scudder"/>, and <contact fullname="Rob Wilton"/> for their valuable feedback and reviews of the specific document updates.</t>
      <t>Finally, thank you to Éric Vynke <contact fullname="Éric Vyncke"/> for the sponsoring this document and the AD review.</t>
    </section>
  </back>

<!-- ##markdown-source:
H4sIAFK7cmEAA+1b23LjNhJ9d5X+Aat52KRKlGRJtiVXNrXybeyMbyvLO7WV
TG1BJCRhTBEMAFqjuGbf97v2x7YbAC+SaY9lJzN5sCvhgBTR6D590GiQTc/z
Khua65Dtkus4oJpHEzJgYyZZ5DNFtCB6ysjJ4fCIHA0vyRWTt9xnlQ06Gkl2
u2anQPgRncFQgaRj7QU0WoR87kkWh9Rn3ljHXix4pJlUXnO7spGgcKZ2Sau5
s1Mjrc5mF47bHTz2tjrmuFUj7WaricduG46t5qY5tvDYw1+3u3Bnu7eNV3o7
cGen2d6G42Yb7uy0tvDYbkHfzlZn2xxhrM52u4fHLvTaavZgxK1OC47bO1tw
zw6oUtnwQbmJkItdonRQ2ahs8FjuEi0TpVvNZq/ZApgko7vkLYuYpGFlYy7k
zUSKJN4l50zjGXkPB8TvLV6ubNywBVwOdskJwhAx7R0gVihdaRoF/6ahiADB
BVOVjZjvVjYIkWOfBUovwvQ6ARf4xTaPAhbp7IoSUks2VvmFxWzp3BezGXTI
L/Ao5FEuHhw5o3EMertLYGmip0KiPh7egV2ge3VQJwfWzVV72RKgOhAzGq38
JOSERvw34JOI4JYrMdZzAJAcRhMYnEmE6SRSQNdEM9eHzSgPd4kMgr/7TOo6
yEBtIiFnIOeWGYAGR/utzc1e1gY2ZW3gVNYGZmVt4FehvZW2kWt5u9vO2sC7
QruVt3t5X2Bi1gY+5u2dTCZyM2sDQ7M28DRrA1uzNnC20M7sQv7m7W42FnI5
awOj0zbyOm0ju3cNn6PxEo44m73B4fBkcHh2eD6014BgVE4YsKs61TpWu40G
+oRKfwr96pzpMXqlgRcaMzVp4JXGLfe6o6Nfw8ne0ce91sefNq9O+m+P+fkg
mDSqqVwbl6oDprlkSEgixqWhJe2B4QKjRWvTa7bhPzTintre5Wn//EHd5/N5
rvOMBZw2gO2JmQ6NAbvligWe0Qjo6KEiHop3inhu7HocjFfN+M71Jpchjb4n
qYw1DYKLlQ3P8wgdKS2pb0LDsChCWRFEJlGE8qkmEFkzo2pExCo7IxBTSHYy
52FIRtDVIB7UCemTKJmNmETk42QUcjUFC4AkCiZ4rjpKOenvQSCEgDfD3/ww
CRi5HpzAejAFFWS6PsApV0VFYZShICxSiWT2XhQLtIMZT0OV9wxIou4Bllrr
QziB0GD1H4skCmp2pNR7xK0mpju6bETRGTJft6xBihE6HjNfw4+Z5wEZPSXH
w+HllbGpThB2dMOMB0HI8OwNxmwpgsTHAEbu3nA8/Yw/9cdgjImqScT1Alpg
bahNpMNhQ1AMvQyLE9dkTkFr5vMANIC11Dqj3Opn+Pjubnk6fP6Mbo5jFgX8
E9lDR6/eYmbM58+E4yrCxxz0ajctCXJOPEaHESx2jEVks9fbgSnS3LZ+ntIA
NQ8ZVTC1I0bYpzjkPkAgpFtyirwRhCL4xOQIhgiiFBWw5+swykTHMFwUqCWA
PgaYzMBIaBAAxtubAjJaEAEDyofZlRqmYK3M1a4TQ7q7OzcaOITB5ITMAodm
1J+m4THjr9EEnRFLcQveQ9NNrmXU1+yTrlvm7ovoFn0LvDT3H7AxB6bieRpf
IDMhmJooUj27vhpWa/Zfcn5h2oPDf1wDXQ6wfXXcPz3NGukdV8cX16cHeSvv
uX9xBjQ7sJ3hKlm5dNb/F/yDelUvLocnF+f906rlW9EbmCoAcOAsk0LGMG8A
AjOXlC/5yHJ0b/+SbHaA4i4pABTv7v4CJ93NnQ6czKcssmOJCDxrTwHUBYGE
h1HkJQGfAztirsErNRxBTcU8IuBTVk/hEpJD1kJDgzIZSzEDoegQp2PKhjTk
/poIewpMqF4ATkYH9Oaqy8q7nB++rzpnXjvRhZT87k1KGqvfQ3FxLMJQzE0+
D9SpW765lMkg5VKmrA0pU9aGlKnQ3krbmDLl7W47a0PKVGi38nYv7wspU9aG
lClv72QyMWXK2pAyZW1ImbI2pExZG1KmQjuzC1OmvN3NxsKUKWtDyvTZhvQg
MPMD53/N+iBmcsaVwpie5in9vZrtiPkVCEGfmnPMsfAcOAskEikdrAffpFkq
nl0xu560bWTOnQE+TEkEFLSeUyZv+0/2V9kAKplr+yLm4GSQYYMCDnyLedoo
BLJGuy5VKvmDhQXyIrO8KF5nQdLgkQdRjanGsuDlLcsaYxRGSDMvnsoyW0U7
ElD8BaYUEzzYMXmQ2mkhzWBw+vuYUppE8qCx7JLMwzCRih5u1Vu5j+0kW8/H
Q7P8uMzbKh0K3/bWpShDw8Ns3UvTdRSTI/24wMpGub0oFIa5L72BaVMpEhBG
lpDIcbABpoDDiAEGsBaeAwPzxR0jfKxNDpflMn1Yf2/ZvQXY5m45ZmATV2Zr
MeNRgpEQdI40/G8X6yw5gOXeLrNzt2c3W3kzpyGhS9MUlwepZATJD7PJisXL
yboenDpfLEHWACMrG5gZwkItmY39gVuHwQwKkWUSpbug68G5Mgot6wIXRhzX
aLiFkjGjJtFwdtWXXfst7C4lDCyesNNimNKpBmQqPoO5iW10+x8OSMZBWL5S
YPYvzof9/aF3cn50kRp2drKHzZJwbNc9UBSxw/yJiERbsprHE+kEyvNO3PKY
ld1uCPMcFwx+wjzPA86hkd+38neXQ9JT5ntjjFFuxkdFajxN/LpzPx3poWAI
GcMa8HeK8G+9wv9S+DFJexb7XXb3Cv8L4e+2n8V+l1B/dfhTVJ6GM4/9ILoP
ciZkXTSNvBUoSYYl7CvWwHI7x9JuSL4ylsssexlvV2TZi783VVv4YuPJ8O4U
4W29wvtleHvPWwfdtvmbBOIvhsunBuSJmsWN8mj8lDHW9YUbrtQP290sHSy8
B1l5Xpy6YbNT2Lu5hxa4W1pj8/bzzgdCLiacyRoZ1GvkjClFJyavNln4sg8x
0z3rnx8Oaw6EJ8E7o8C9RqvZbHnNVh1/SrsfsZFMqFwQ/HFpo/BCvdZ1iVXR
dV7S9J6ORRRLEe19eL7ia+PZdlqe4Y9Wxn0sX6LRS5AsUbEMxYz8ve3Wo+TP
uW4fyq33nOLn08P+/vEHVOwUN5Y1cgloWOu1sFi8Y3LEpFAr+zm8B86WZj5u
Y2tkC8wy1GjXHnfeUt8UrBs58uYTdGXba24ZnJY990er/Lh3lzrfd3W59uWe
3Vknz98qOHrn6+f52VK7sooU32414mTUQDzVyrqxvE4/ji+YZV5YBgCjdx9f
zQDdckDx6fOz1mv32PqbrNe/S/ZO7mH8zFW4LJvP4N1sr5PM5/tS9ybgW8D7
DHTrpfCWofs8cB+IBviK5Glx3r1MWTPOH/RPPixnaAeU18h7CJ3VfkSo1tS/
IXSCHtLk6uq4hW8qtfBFWK3ZZK/0jYF7P3p1uH91vFxBZYOjUtO/w+I3UoEt
CCoRYX1DvuAcxXw1tQt8qZRiblKy3P+J7V+XR6VCCvCUIVHkREnvB/4ycrZb
6zwTyZcq97Lv9ZlIPs+3Os9cpOy70lcoi1DuPBfKnVcol6DcbveeB6V9U/8K
ZQHK7joP5YpQdr/BQ7k/M5RY7vGsZcfVibxCmUPZaa0DZf4k3pbZvEKZQ4n1
Q0sVEvVufTPDy1UXrZedg6r7iZT4/twUAuD7fKWpTuzL8jC0TzWwxiZ70lqC
CxbPYD0NfmPwqa4/aftSvUy6LcSLtauQyoZYqbZ5bLTVuqBNHnhpJbRKRy/4
Y20Lv1Am9AdZ+lDhUIl5Zeyw36Pk7NgrPI12lWYv58ZaNv3wHN/9+CXnrafC
k0H9sQRV880O98nbhAc08k2F9wkMGaXVu1jKiaVFac1yuCAzW0JrC00hZjEq
Qw63KueWPJ4t77Bt5aWcwa6wBLZffoipnv7yY9WVH+ddTf3tKKsQdaWgtkh6
WezjoSgbwRWQAo0SiXXq+674htrK4Ls3YAkW5JRUkQaCKYMHDbHW3ZQCpWL8
ophUs5SNWRW0q29eFutMU7Yu2lZrA7KmTtufshmzNrNfE35LQ+xRLKA25ODR
WFLwduJrrAf/jtcZ7L+LSHxv68gSxWwRtl1LFMtKY/NacmacyKME55EtCOQh
2ghW4S9W56y8HHgQ45IkEgX8WPmAAmuLy0vPjZezTzCWKk1XK4Idmn4IZPNM
eTAKKhSUm2rhYi28ZEokEjEV0YMoYfE7MIv6cJ9yhCYzIZ1XAXa6AN2OsDTs
E53FIau58bJSc5wAkS8XMXrZn9IoYqHVwH0doszDDjs3FFGJP8XQdAvTbrxI
q/IRESb/qty3BwB07NiFn3vxMcdqRNsHm8ivEZtSQFzm0HDoamu6MQRNDCfT
6jUrlxof5uq4L+AANBRv0ERREZsIuBkNGp5eZc9qcHxT9muE8hjCg0q4Zm46
nfTP+/enEqcRLZlHU4rTyPahFhojBr81GVH/xors+zeRmIcsmJipU9m427Xf
6bDgb9UxDRWrOtk0uiELkeCMGAi4QZOrmMobVSNvYbqQPQpxE2h1zCLJb8gp
u70Rc6Z/M6YMEqXIMXKXLZbIMhQiVGTI6My8pcLrIs5sw66mlJBF1FYGuieL
RoTxP15wFX35VzEBV35i66fhppLvVNCi1dlQsG9PAqZkn8qY4Xpg3nPBVCUH
yQ2ws2hMjeyx6COdwY/vaJDc1Mghxvp3+MUJdINlhy7IOyAk2DSHu8+4/Ejh
ApuGbM7xQ5ArX2gNA0RqzFkIF4ZiRi6ZxjdDP4kpJLV+EgSohAFSjMh7Hmqw
zOHFJYF4lZhy4jFjwcg8CIwCk8CyuUrJq2LmI7XvlesbMI54GQ7/+y8a889F
dMMy96gYPCPc92ZLX024rwz6B25oLI/9PxiwrkYXPAAA

-->
</rfc>