| RFC 9141 | Updating References to IETF FTP | November 2021 |
| Danyliw | Standards Track | [Page] |
RFC 9141
Updating References to the IETF FTP Service
Abstract
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.¶
Status of This Memo
This is an Internet Standards Track document.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc9141.¶
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
1. 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.¶
2. 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".¶
3. 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.¶
3.1. 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/¶
3.2. 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/.¶
3.3. 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.¶
3.4. 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/¶
3.5. 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/¶
3.6. 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/¶
3.7. 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/¶
3.8. 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/¶
3.9. 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/¶
3.10. 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/¶
3.11. 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.