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.

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 (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.

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.

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 [RFC 2119] [RFC 8174] 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".

This document updates the following RFCs. [RFC 2077] [RFC 2418] [RFC 2648] [RFC 2954] [RFC 2955] [RFC 3020] [RFC 3083] [RFC 3201] [RFC 3202] [RFC 3295] [RFC 3684] [RFC 3962] [RFC 3970] [RFC 4036] [RFC 4131] [RFC 4251] [RFC 4323] [RFC 4546] [RFC 4547] [RFC 4639] [RFC 4682] [RFC 5098] [RFC 5428] Additionally, with permission of the IAB, [RFC 6756] and [RFC 7241] are also updated.

Section 3 of RFC 2077 is updated as follows: OLD:

---

---

NEW:

---

---

Section 2.2 of RFC 2418 is updated as follows: OLD:

---

---

NEW:

---

---

Section 2 of RFC 2648 is updated below. Note that the scripts in Appendix A have not been updated. OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 3 of RFC 2954 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 4 of RFC 2955 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 3 of RFC 3020 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 4 of RFC 3083 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 6 of RFC 3201 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 7 of RFC 3202 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 4 of RFC 3295 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

Two informative references in Section 14.2 of RFC 3684 are updated as follows: OLD:

---

---

NEW:

---

---

OLD:

---

---

NEW:

---

---

An informative reference in [RFC 3962] is updated as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 5 of RFC 3970 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 4 of RFC 4036 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 3 of RFC 4131 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

An informative reference in [RFC 4251] is updated as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 5 of RFC 4323 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 4 of RFC 4546 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 4 of RFC 4547 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 4 of RFC 4639 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 4 of RFC 4682 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 5 of RFC 5098 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

The CONTACT-INFO in the MIB in Section 6 of RFC 5428 contains an outdated email archive reference. The revised reference is as follows: OLD:

---

---

NEW:

---

---

Section 2.8.1 of RFC 6756 is updated as follows: OLD:

---

---

NEW:

---

---

Appendix B.2 of RFC 7241 is updated as follows: OLD:

---

---

NEW:

---

---

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>".

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.

This document has no IANA actions.

[RFC2077]

S. Nelson, C. Parks, and M. Ardron, "The Model Primary Content Type for Multipurpose Internet Mail Extensions", RFC 2077, DOI 10.17487/RFC2077, January 1997,
<https://www.rfc-editor.org/info/rfc2077>.

[RFC2119]

S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.

[RFC2418]

S. Bradner, "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418, September 1998,
<https://www.rfc-editor.org/info/rfc2418>.

[RFC2648]

R. Moats, "A URN Namespace for IETF Documents", RFC 2648, DOI 10.17487/RFC2648, August 1999,
<https://www.rfc-editor.org/info/rfc2648>.

[RFC2954]

K. Rehbehn, and D. Fowler, "Definitions of Managed Objects for Frame Relay Service", RFC 2954, DOI 10.17487/RFC2954, October 2000,
<https://www.rfc-editor.org/info/rfc2954>.

[RFC2955]

K. Rehbehn, O. Nicklass, and G. Mouradian, "Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function", RFC 2955, DOI 10.17487/RFC2955, October 2000,
<https://www.rfc-editor.org/info/rfc2955>.

[RFC3020]

P. Pate, B. Lynch, and K. Rehbehn, "Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function", RFC 3020, DOI 10.17487/RFC3020, December 2000,
<https://www.rfc-editor.org/info/rfc3020>.

[RFC3083]

R. Woundy, "Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems", RFC 3083, DOI 10.17487/RFC3083, March 2001,
<https://www.rfc-editor.org/info/rfc3083>.

[RFC3201]

R. Steinberger, and O. Nicklass, "Definitions of Managed Objects for Circuit to Interface Translation", RFC 3201, DOI 10.17487/RFC3201, January 2002,
<https://www.rfc-editor.org/info/rfc3201>.

[RFC3202]

R. Steinberger, and O. Nicklass, "Definitions of Managed Objects for Frame Relay Service Level Definitions", RFC 3202, DOI 10.17487/RFC3202, January 2002,
<https://www.rfc-editor.org/info/rfc3202>.

[RFC3295]

H. Sjostrand, J. Buerkle, and B. Srinivasan, "Definitions of Managed Objects for the General Switch Management Protocol (GSMP)", RFC 3295, DOI 10.17487/RFC3295, June 2002,
<https://www.rfc-editor.org/info/rfc3295>.

[RFC3684]

R. Ogier, F. Templin, and M. Lewis, "Topology Dissemination Based on Reverse-Path Forwarding (TBRPF)", RFC 3684, DOI 10.17487/RFC3684, February 2004,
<https://www.rfc-editor.org/info/rfc3684>.

[RFC3962]

K. Raeburn, "Advanced Encryption Standard (AES) Encryption for Kerberos 5", RFC 3962, DOI 10.17487/RFC3962, February 2005,
<https://www.rfc-editor.org/info/rfc3962>.

[RFC3970]

K. Kompella, "A Traffic Engineering (TE) MIB", RFC 3970, DOI 10.17487/RFC3970, January 2005,
<https://www.rfc-editor.org/info/rfc3970>.

[RFC4036]

W. Sawyer, "Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management", RFC 4036, DOI 10.17487/RFC4036, April 2005,
<https://www.rfc-editor.org/info/rfc4036>.

[RFC4131]

S. Green, K. Ozawa, E. Cardona, and A. Katsnelson, "Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modems and Cable Modem Termination Systems for Baseline Privacy Plus", RFC 4131, DOI 10.17487/RFC4131, September 2005,
<https://www.rfc-editor.org/info/rfc4131>.

[RFC4251]

T. Ylonen, and C. Lonvick, "The Secure Shell (SSH) Protocol Architecture", RFC 4251, DOI 10.17487/RFC4251, January 2006,
<https://www.rfc-editor.org/info/rfc4251>.

[RFC4323]

M. Patrick, and W. Murwin, "Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB)", RFC 4323, DOI 10.17487/RFC4323, January 2006,
<https://www.rfc-editor.org/info/rfc4323>.

[RFC4546]

D. Raftus, and E. Cardona, "Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF Interfaces", RFC 4546, DOI 10.17487/RFC4546, June 2006,
<https://www.rfc-editor.org/info/rfc4546>.

[RFC4547]

A. Ahmad, and G. Nakanishi, "Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination Systems", RFC 4547, DOI 10.17487/RFC4547, June 2006,
<https://www.rfc-editor.org/info/rfc4547>.

[RFC4639]

R. Woundy, and K. Marez, "Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems", RFC 4639, DOI 10.17487/RFC4639, December 2006,
<https://www.rfc-editor.org/info/rfc4639>.

[RFC4682]

E. Nechamkin, and J-F. Mule, "Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices", RFC 4682, DOI 10.17487/RFC4682, December 2006,
<https://www.rfc-editor.org/info/rfc4682>.

[RFC5098]

G. Beacham, S. Kumar, and S. Channabasappa, "Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)", RFC 5098, DOI 10.17487/RFC5098, February 2008,
<https://www.rfc-editor.org/info/rfc5098>.

[RFC5428]

S. Channabasappa, W. De Ketelaere, and E. Nechamkin, "Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices", RFC 5428, DOI 10.17487/RFC5428, April 2009,
<https://www.rfc-editor.org/info/rfc5428>.

[RFC6756]

S. Trowbridge, E. Lear, G. Fishman, and S. Bradner, "Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines", RFC 6756, DOI 10.17487/RFC6756, September 2012,
<https://www.rfc-editor.org/info/rfc6756>.

[RFC7241]

S. Dawkins, P. Thaler, D. Romascanu, and B. Aboba, "The IEEE 802/IETF Relationship", RFC 7241, DOI 10.17487/RFC7241, July 2014,
<https://www.rfc-editor.org/info/rfc7241>.

[RFC8174]

B. Leiba, "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017,
<https://www.rfc-editor.org/info/rfc8174>.

[FTP-RETIREMENT]

R. Danyliw, "Retirement of the IETF FTP Service", March 2021,
<https://mailarchive.ietf.org/arch/msg/ietf/vi-8bFqlgBFjB2jJ1SIAGHiNRdg/>.

[FTP-RETIREMENT-PLAN]

"Retiring the IETF FTP Service (Revised Plan)", March 2021,
<https://www.ietf.org/media/documents/Revised-Retiring-IETF-FTP-Service-2021-03.pdf>.

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.

Roman Danyliw