Updating References to the IETF FTP Service
RFC 9141
Roman Danyliw
Software Engineering Institute
rdd@cert.org
November 2021
General
Network Working Group
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.
Introduction
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 [FTP-RETIREMENT]. Appendix B of [FTP-RETIREMENT-PLAN] 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.
Section 3 enumerates each of the affected RFCs and provides replacement text.
Conventions and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
The original text from an RFC to be updated will be quoted with "OLD", and the replacement text will be quoted with "NEW".
Updated References
This document updates the following RFCs.
[RFC2077] [RFC2418] [RFC2648] [RFC2954] [RFC2955] [RFC3020] [RFC3083] [RFC3201] [RFC3202] [RFC3295] [RFC3684] [RFC3962] [RFC3970] [RFC4036] [RFC4131] [RFC4251] [RFC4323] [RFC4546] [RFC4547] [RFC4639] [RFC4682] [RFC5098] [RFC5428]
Additionally, with permission of the IAB, [RFC6756] and [RFC7241] are also updated.
RFC 2077
Section 3 of [RFC2077] is updated as follows:
OLD:
Copies of RFCs are available on:
ftp://ftp.isi.edu/in-notes/
Copies of Internet-Drafts are available on:
ftp://ftp.ietf.org/internet-drafts/
NEW:
Copies of RFCs are available on:
https://www.rfc-editor.org/rfc/
Copies of Internet-Drafts are available on:
https://www.ietf.org/id/
RFC 2418
Section 2.2 of [RFC2418] is updated as follows:
OLD:
Those archives are located at ftp://ftp.ietf.org/ietf-mail-archive.
NEW:
Those archives are located at https://www.ietf.org/ietf-ftp/ietf- mail-archive/.
RFC 2648
Section 2 of [RFC2648] is updated below. Note that the scripts in Appendix A have not been updated.
OLD:
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.
NEW:
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.
RFC 2954
The CONTACT-INFO in the MIB in Section 3 of [RFC2954] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Email Archive:
ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW:
Email Archive:
https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
RFC 2955
The CONTACT-INFO in the MIB in Section 4 of [RFC2955] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Email Archive:
ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW:
Email Archive:
https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
RFC 3020
The CONTACT-INFO in the MIB in Section 3 of [RFC3020] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Email Archive:
ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW:
Email Archive:
https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
RFC 3083
The CONTACT-INFO in the MIB in Section 4 of [RFC3083] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 3201
The CONTACT-INFO in the MIB in Section 6 of [RFC3201] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW:
Email Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
RFC 3202
The CONTACT-INFO in the MIB in Section 7 of [RFC3202] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW:
Email Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
RFC 3295
The CONTACT-INFO in the MIB in Section 4 of [RFC3295] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Email Archive:
ftp://ftp.ietf.org/ietf-mail-archive/gsmp/
NEW:
Email Archive:
https://www.ietf.org/ietf-ftp/ietf-mail-archive/gsmp/
RFC 3684
Two informative references in Section 14.2 of [RFC3684] are updated as follows:
OLD:
[7] Ogier, R., Message in IETF email archive for MANET, ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-02.mail, February 2002.
NEW:
[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.
OLD:
[9] Ogier, R., Message in IETF email archive for MANET, ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-03.mail, March 2002.
NEW:
[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.
RFC 3962
An informative reference in [RFC3962] is updated as follows:
OLD:
[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:
[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.
RFC 3970
The CONTACT-INFO in the MIB in Section 5 of [RFC3970] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ops.ietf.org/pub/lists
NEW:
Archive: https://www.ietf.org/ietf-ftp/concluded-wg-ietf-mail-archive/tewg/
RFC 4036
The CONTACT-INFO in the MIB in Section 4 of [RFC4036] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 4131
The CONTACT-INFO in the MIB in Section 3 of [RFC4131] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn.
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/.
RFC 4251
An informative reference in [RFC4251] is updated as follows:
OLD:
[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.
NEW:
[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.
RFC 4323
The CONTACT-INFO in the MIB in Section 5 of [RFC4323] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 4546
The CONTACT-INFO in the MIB in Section 4 of [RFC4546] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 4547
The CONTACT-INFO in the MIB in Section 4 of [RFC4547] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 4639
The CONTACT-INFO in the MIB in Section 4 of [RFC4639] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 4682
The CONTACT-INFO in the MIB in Section 4 of [RFC4682] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 5098
The CONTACT-INFO in the MIB in Section 5 of [RFC5098] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 5428
The CONTACT-INFO in the MIB in Section 6 of [RFC5428] contains an outdated email archive reference. The revised reference is as follows:
OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
RFC 6756
Section 2.8.1 of [RFC6756] is updated as follows:
OLD:
Current list and status of all IETF RFCs:
ftp://ftp.ietf.org/rfc/rfc-index.txt
Current list and description of all IETF Internet-Drafts:
ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt
NEW:
Current list and status of all IETF RFCs:
https://www.rfc-editor.org/rfc/rfc-index.txt
Current list and description of all IETF Internet-Drafts:
https://www.ietf.org/id/1id-abstracts.txt
RFC 7241
Appendix B.2 of [RFC7241] is updated as follows:
OLD:
Current list and description of all IETF Internet-Drafts:
<ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt>
NEW:
Current list and description of all IETF Internet-Drafts:
<https://www.ietf.org/id/1id-abstracts.txt>
Generic Guidance
If any other RFC not explicitly mentioned in an earlier section contains a reference of the form "ftp://ftp.ietf.org/<path>", the reference MUST be replaced with a URI of the form "https://www.ietf.org/ietf-ftp/<path>".
Security Considerations
This document does not alter the security considerations of the updated documents.
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.
IANA Considerations
This document has no IANA actions.
References
Normative References
[RFC2077]

The Model Primary Content Type for Multipurpose Internet Mail Extensions
S. Nelson
C. Parks
M. Ardron
January 1997
RFC 2077
DOI 10.17487/RFC2077
Informative References
[FTP-RETIREMENT]

Retirement of the IETF FTP Service
R. Danyliw
03 March 2021
message to the IETF mailing list
[FTP-RETIREMENT-PLAN]

Retiring the IETF FTP Service (Revised Plan)
March 2021
[RFC2119]
[RFC8174]
[RFC2418]
[RFC2648]
[RFC2954]
[RFC2955]
[RFC3020]
[RFC3083]
[RFC3201]
[RFC3202]
[RFC3295]
[RFC3684]
[RFC3962]
[RFC3970]
[RFC4036]
[RFC4131]
[RFC4251]
[RFC4323]
[RFC4546]
[RFC4547]
[RFC4639]
[RFC4682]
[RFC5098]
[RFC5428]
[RFC6756]
[RFC7241]
Acknowledgments
Thank you to Robert Sparks, Glen Barney, Henrik Levkowetz, and Russ Housley on the IETF Tools Team for the operations and maintenance information that informed the community discussion at [FTP-RETIREMENT].
Additionally, thank you to Brian Carpenter, Martin Duke, Russ Housley, Benjamin Kaduk, Eric Kline, Murray Kucherawy, Mirja Kühlewind, Scott Mansfield, Tom Petch, John Scudder, and Rob Wilton for their valuable feedback and reviews of the specific document updates.
Finally, thank you to Éric Vyncke for the sponsoring this document and the AD review.