Updating References to the IETF FTP Service
updates
- rfc-2077 — The Model Primary Content Type for Multipurpose Internet Mail Extensions
- rfc-2418 — IETF Working Group Guidelines and Procedures
- rfc-2648 — A URN Namespace for IETF Documents
- rfc-2954 — Definitions of Managed Objects for Frame Relay Service
- rfc-2955 — Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function
- rfc-3020 — Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function
- rfc-3083 — Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems
- rfc-3201 — Definitions of Managed Objects for Circuit to Interface Translation
- rfc-3202 — Definitions of Managed Objects for Frame Relay Service Level Definitions
- rfc-3295 — Definitions of Managed Objects for the General Switch Management Protocol (GSMP)
- rfc-3684 — Topology Dissemination Based on Reverse-Path Forwarding (TBRPF)
- rfc-3962 — Advanced Encryption Standard (AES) Encryption for Kerberos 5
- rfc-3970 — A Traffic Engineering (TE) MIB
- rfc-4036 — Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management
- rfc-4131 — Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modems and Cable Modem Termination Systems for Baseline Privacy Plus
- rfc-4251 — The Secure Shell (SSH) Protocol Architecture
- rfc-4323 — Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB)
- rfc-4546 — Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF Interfaces
- rfc-4547 — Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination Systems
- rfc-4639 — Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems
- rfc-4682 — Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices
- rfc-5098 — Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)
- rfc-5428 — Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices
- rfc-6756 — Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines
- rfc-7241 — The IEEE 802/IETF Relationship
Extracted elements (12)
After community consultation in late 2020, the IETF decided to retire the FTP service at ftp.ietf.org, ops.ietf.org, and ietf.org. This document formally updates the 25 RFCs (published 1997–2006) that contained explicit FTP-based references to ensure continued availability of the referenced materials.
HTTPS replacements were chosen rather than simply letting FTP URIs become dead links because the referenced materials (RFC copies, Internet-Draft listings, mail archives, MIB CONTACT-INFO) remain in active use by implementors. Availability and security were both motivating factors.
MIB CONTACT-INFO blocks in RFCs 2954, 2955, 3020, 3083, 3201, 3202, 3295, 3970, 4036, 4131, 4323, 4546, 4547, 4639, 4682, 5098, and 5428 all contained FTP-based email archive references; each is replaced with an equivalent HTTPS URI pointing to the same archived content.
RFC 2077 Section 3 references for RFC copies (ftp://ftp.isi.edu/in-notes/) and Internet-Drafts (ftp://ftp.ietf.org/internet-drafts/) are replaced with https://www.rfc-editor.org/rfc/ and https://www.ietf.org/id/ respectively.
RFC 2418 Section 2.2 reference to the IETF mail archive at ftp://ftp.ietf.org/ietf-mail-archive is replaced with https://www.ietf.org/ietf-ftp/ietf-mail-archive/.
RFC 2648 Section 2 (URN namespace for IETF documents) reference to ftp://ietf.org/ietf/ as the definitive assignment source for working group minutes URNs is replaced with https://www.ietf.org/how/meetings/proceedings/. The Appendix A scripts referencing FTP were not updated.
RFC 3684 Section 14.2 informative references to the MANET WG mail archive (ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-02.mail and 2002-03.mail) are replaced with equivalent HTTPS URIs.
RFC 4251 (SSH Protocol Architecture) informative reference [DAI] pointing to the SECSH working group mail archive via FTP is updated to the equivalent HTTPS URI, preserving traceability to the cited security analysis.
RFC 6756 (IETF/ITU-T collaboration guidelines) Section 2.8.1 references to the RFC index (ftp://ftp.ietf.org/rfc/rfc-index.txt) and I-D abstracts (ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt) are replaced with https://www.rfc-editor.org/rfc/rfc-index.txt and https://www.ietf.org/id/1id-abstracts.txt. Updated with IAB permission.
RFC 7241 (IEEE 802/IETF relationship) Appendix B.2 reference to I-D abstracts via FTP is replaced with https://www.ietf.org/id/1id-abstracts.txt. Updated with IAB permission.
Any RFC not explicitly updated in Section 3 that contains a reference of the form 'ftp://ftp.ietf.org/<path>' MUST replace it with 'https://www.ietf.org/ietf-ftp/<path>'.
Replacing cleartext FTP URIs with HTTPS ensures resources on the IETF infrastructure can be accessed securely. HTTPS provides an encrypted channel including server identity verification via certificate validation and integrity/confidentiality protections commensurate with the negotiated TLS version and ciphersuite.