<?xml version="1.0" encoding="UTF-8"?>

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

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-danyliw-replace-ftp-pointers-06" 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" obsoletes="" submissionType="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  
  <front>  
    <title abbrev="Updating References to IETF 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="November"/>
    <area>General</area>
    <workgroup>Network Working Group</workgroup>

    <abstract>
      <t>The IETF FTP service running at ftp.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" 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, and ietf.org <xref target="FTP-RETIREMENT" format="default"/>.  Appendix B of <xref target="FTP-RETIREMENT-PLAN" format="default"/> identifies 30 RFCs published in the IETF and IAB streams between 1997-2006 that 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" format="default"/> enumerates each of the affected RFCs and provides replacement text.</t>
    </section>
    <section anchor="conventions-and-definitions" numbered="true" toc="default">
      <name>Conventions and Definitions</name>
              <t>
    The key words "<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 "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
    described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/> 
    when, and only when, they appear in all capitals, as shown here.
        </t>

      <t>The original text from an RFC to be updated will be quoted with "OLD", and the replacement text will be quoted with "NEW".</t>
    </section>
    <section anchor="updates" numbered="true" toc="default">
      <name>Updated References</name>
      <t>This document updates the following RFCs.</t>
      <t><xref target="RFC2077" format="default"/> <xref target="RFC2418" format="default"/> <xref target="RFC2648" format="default"/> <xref target="RFC2954" format="default"/> <xref target="RFC2955" format="default"/> <xref target="RFC3020" format="default"/> <xref target="RFC3083" format="default"/> <xref target="RFC3201" format="default"/> <xref target="RFC3202" format="default"/> <xref target="RFC3295" format="default"/> <xref target="RFC3684" format="default"/> <xref target="RFC3962" format="default"/> <xref target="RFC3970" format="default"/> <xref target="RFC4036" format="default"/> <xref target="RFC4131" format="default"/> <xref target="RFC4251" format="default"/> <xref target="RFC4323" format="default"/> <xref target="RFC4546" format="default"/> <xref target="RFC4547" format="default"/> <xref target="RFC4639" format="default"/> <xref target="RFC4682" format="default"/> <xref target="RFC5098" format="default"/> <xref target="RFC5428" format="default"/></t>
      <t>Additionally, with permission of the IAB, <xref target="RFC6756" format="default"/> and <xref target="RFC7241" format="default"/> are also updated.</t>
      <section anchor="rfc2077" numbered="true" toc="default">
        <name>RFC 2077</name>
        <t><xref target="RFC2077" sectionFormat="of" section="3"/> is updated as follows:</t>
	<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:
</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/
</t>
	     </blockquote>
      </section>
      <section anchor="rfc2418" numbered="true" toc="default">
        <name>RFC 2418</name>
        <t><xref target="RFC2418" sectionFormat="of" section="2.2"/> is updated as follows:</t>

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

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

Those archives are located at https://www.ietf.org/ietf-ftp/ietf-&wj;mail-archive/. </t>
</blockquote>
      </section>
      <section anchor="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 <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></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" numbered="true" toc="default">
        <name>RFC 2954</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC2954" sectionFormat="of" section="3"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

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

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

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

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

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

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

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

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

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

          Email Archive:

            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/</t>
</blockquote>
      </section>
      <section anchor="rfc3083" numbered="true" toc="default">
        <name>RFC 3083</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC3083" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<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/</t>
</blockquote>
      </section>
      <section anchor="rfc3201" numbered="true" toc="default">
        <name>RFC 3201</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC3201" sectionFormat="of" section="6"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

	 
<t>

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

    Email Archive: 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/</t>
</blockquote>
      </section>
      <section anchor="rfc3202" numbered="true" toc="default">
        <name>RFC 3202</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC3202" sectionFormat="of" section="7"/> contains an outdated email archive reference.  The revised reference is as follows:</t>
<t>

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

    Email Archive: 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/</t>
</blockquote>
      </section>
      <section anchor="rfc3295" numbered="true" toc="default">
        <name>RFC 3295</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC3295" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>

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

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

Email Archive:</t><t indent="3">         https://www.ietf.org/ietf-ftp/ietf-mail-archive/gsmp/</t>
</blockquote>
      </section>
      <section anchor="rfc3684" numbered="true" toc="default">
        <name>RFC 3684</name>
        <t>Two informative references in <xref target="RFC3684" sectionFormat="of" section="14.2"/> are updated as follows:</t>
	  <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.
</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, February 2002.
</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,
     March 2002.</t>
</blockquote>
      </section>
      <section anchor="rfc3962" numbered="true" toc="default">
        <name>RFC 3962</name>
        <t>An informative reference in <xref target="RFC3962" format="default"/> is updated as follows:</t>
	  <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.
</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.
</t>
	 </blockquote>
      </section>
      <section anchor="rfc3970" numbered="true" toc="default">
        <name>RFC 3970</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC3970" sectionFormat="of" section="5"/> contains an outdated email archive reference.  The revised reference is as follows:</t>
	  <t>
OLD:
	  </t>
	  	<blockquote>
<t>

   Archive:          ftp://ops.ietf.org/pub/lists
</t>	</blockquote>
<t>

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

   Archive: 
   https://www.ietf.org/ietf-ftp/concluded-wg-ietf-mail-archive/tewg/</t>
</blockquote>
      </section>
      <section anchor="rfc4036" numbered="true" toc="default">
        <name>RFC 4036</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC4036" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>
<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/
</t>
</blockquote>
      </section>
      <section anchor="rfc4131" numbered="true" toc="default">
        <name>RFC 4131</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC4131" sectionFormat="of" section="3"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

<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/.
</t>
</blockquote>
      </section>
      <section anchor="rfc4251" numbered="true" toc="default">
        <name>RFC 4251</name>
        <t>An informative reference in <xref target="RFC4251" format="default"/> is updated as follows:</t>

	  <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, Feb 2002.
</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.
</t>
		 </blockquote>
      </section>
      <section anchor="rfc4323" numbered="true" toc="default">
        <name>RFC 4323</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC4323" sectionFormat="of" section="5"/> contains an outdated email archive reference.  The revised reference is as follows:</t>
	<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/
</t>
    </blockquote>
      </section>
      <section anchor="rfc4546" numbered="true" toc="default">
        <name>RFC 4546</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC4546" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>
	  <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/
</t>
    </blockquote>
      </section>
      <section anchor="rfc4547" numbered="true" toc="default">
        <name>RFC 4547</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC4547" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

	  <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/</t>
</blockquote>
      </section>
      <section anchor="rfc4639" numbered="true" toc="default">
        <name>RFC 4639</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC4639" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>
	  <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/
</t>
    </blockquote>
      </section>
      <section anchor="rfc4682" numbered="true" toc="default">
        <name>RFC 4682</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC4682" sectionFormat="of" section="4"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

	  <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/</t>
</blockquote>
      </section>
      <section anchor="rfc5098" numbered="true" toc="default">
        <name>RFC 5098</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC5098" sectionFormat="of" section="5"/> contains an outdated email archive reference.  The revised reference is as follows:</t>

	  <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/</t>
</blockquote>
      </section>
      <section anchor="rfc5428" numbered="true" toc="default">
        <name>RFC 5428</name>
        <t>The CONTACT-INFO in the MIB in <xref target="RFC5428" sectionFormat="of" section="6"/> contains an outdated email archive reference.  The revised reference is as follows:</t>
	  <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/</t>
</blockquote>
      </section>
      <section anchor="rfc6756" numbered="true" toc="default">
        <name>RFC 6756</name>
        <t><xref target="RFC6756" sectionFormat="of" section="2.8.1"/> is updated as follows:</t>

	  <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
</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:
</t>
<t indent="3">
      https://www.ietf.org/id/1id-abstracts.txt</t>
</blockquote>
      </section>
      <section anchor="rfc7241" numbered="true" toc="default">
        <name>RFC 7241</name>
        <t><xref target="RFC7241" sectionFormat="of" section="B.2"/> is updated as follows:</t>

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

   Current list and description of all IETF Internet-Drafts:
</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:
</t>
<t>
    &lt;https://www.ietf.org/id/1id-abstracts.txt&gt;</t>
</blockquote>
      </section>
      <section anchor="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;", the reference <bcp14>MUST</bcp14> be replaced with a URI of the form "https://www.ietf.org/ietf-ftp/&lt;path&gt;".</t>
      </section>
    </section>
    <section anchor="seccons" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This document does not alter the security considerations of the updated documents.</t>
      <t>This document replaces URIs to the IETF infrastructure that use 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 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, such as verifying the server's identity per the certificate verification behavior of the client and integrity and confidentiality protection commensurate with the negotiated TLS protocol version and ciphersuite.</t>
    </section>
    <section anchor="iana" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <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' 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='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>
        <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>
        <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 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>Retiring the IETF FTP Service (Revised Plan)</title>
            <author>
              <organization/>
            </author>
            <date year="2021" month="March"/>
          </front>
	  
        </reference>
      </references>
    </references>
    <section numbered="false" anchor="acknowledgments" toc="default">
      <name>Acknowledgments</name>
      <t>Thank you to <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" format="default"/>.</t>
      <t>Additionally, thank you to <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 <contact fullname="Éric Vyncke"/> for the sponsoring this document and the AD review.</t>
    </section>  
  </back>
</rfc>
