Updating References to the IETF FTP ServiceSoftware Engineering Instituterdd@cert.org
General
Network Working GroupThe 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
.
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
() 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.
Table of Contents
. Introduction
. Conventions and Definitions
. Updated References
. 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
. RFC 6756
. RFC 7241
. Generic Guidance
. Security Considerations
. IANA Considerations
. References
. Normative References
. Informative References
Acknowledgments
Author's Address
IntroductionAfter 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 . Appendix B of 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. 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
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 ReferencesThis document updates the following RFCs.Additionally, with permission of the IAB, and are also updated.RFC 2077 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 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 is updated below. Note that the scripts in Appendix 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 2954The CONTACT-INFO in the MIB in contains an outdated email archive reference. The revised reference is as follows:OLD:
RFC 4251An informative reference in 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 4323The CONTACT-INFO in the MIB in contains an outdated email archive reference. The revised reference is 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 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 GuidanceIf 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 ConsiderationsThis 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 ConsiderationsThis document has no IANA actions.ReferencesNormative ReferencesThe Model Primary Content Type for Multipurpose Internet Mail ExtensionsThe purpose of this memo is to propose an update to Internet RFC 2045 to include a new primary content-type to be known as "model". [STANDARDS-TRACK]Key words for use in RFCs to Indicate Requirement LevelsIn many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.IETF Working Group Guidelines and ProceduresThis document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.A URN Namespace for IETF DocumentsThis document proposes the "ietf" namespace, which consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC Editor and the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences. [STANDARDS-TRACK]Definitions of Managed Objects for Frame Relay ServiceThis memo defines an extension to the Management Information Base (MIB) for use with network management protocols in Transmission Control Protocol/Internet Protocol-based (TCP/IP) internets. In particular, it defines objects for managing the frame relay service. [STANDARDS-TRACK]Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking FunctionThis memo defines a Management Information Base (MIB) to configure, monitor, and control a service interworking function (IWF) for Permanent Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer Mode (ATM) technologies. [STANDARDS-TRACK]Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay FunctionThis memo defines a Management Information Base (MIB) for monitoring and controlling a UNI/NNI Multilink Frame Relay Function as defined in Frame Relay Forum FRF.16. [STANDARDS-TRACK]Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination SystemsThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP-based (Simple Network Management Protocol) management of the Baseline Privacy Interface (BPI), which provides data privacy for DOCSIS 1.0 (Data-Over- Cable Service Interface Specifications) compliant Cable Modems and Cable Modem Termination Systems. This MIB is defined as an extension to the DOCSIS Radio Frequency Interface MIB, RFC 2670. This memo provides information for the Internet community.Definitions of Managed Objects for Circuit to Interface TranslationThis memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the insertion of interesting Circuit Interfaces into the ifTable. This is important for circuits that must be used within other MIB modules which require an ifEntry. It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules. [STANDARDS-TRACK]Definitions of Managed Objects for Frame Relay Service Level DefinitionsThis memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service Level Definitions. [STANDARDS-TRACK]Definitions of Managed Objects for the General Switch Management Protocol (GSMP)This memo defines a portion of the Management Information Base (MIB) for the use with the network management protocols in the Internet community. In particular, it describes managed objects for the General Switch Management Protocol (GSMP). [STANDARDS-TRACK]Topology Dissemination Based on Reverse-Path Forwarding (TBRPF)Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) is a proactive, link-state routing protocol designed for mobile ad-hoc networks, which provides hop-by-hop routing along shortest paths to each destination. Each node running TBRPF computes a source tree (providing paths to all reachable nodes) based on partial topology information stored in its topology table, using a modification of Dijkstra's algorithm. To minimize overhead, each node reports only *part* of its source tree to neighbors. TBRPF uses a combination of periodic and differential updates to keep all neighbors informed of the reported part of its source tree. Each node also has the option to report additional topology information (up to the full topology), to provide improved robustness in highly mobile networks. TBRPF performs neighbor discovery using "differential" HELLO messages which report only *changes* in the status of neighbors. This results in HELLO messages that are much smaller than those of other link-state routing protocols such as OSPF. This memo defines an Experimental Protocol for the Internet community.Advanced Encryption Standard (AES) Encryption for Kerberos 5The United States National Institute of Standards and Technology (NIST) has chosen a new Advanced Encryption Standard (AES), which is significantly faster and (it is believed) more secure than the old Data Encryption Standard (DES) algorithm. This document is a specification for the addition of this algorithm to the Kerberos cryptosystem suite. [STANDARDS-TRACK]A Traffic Engineering (TE) MIBThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths. [STANDARDS-TRACK]Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber ManagementThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for Simple Network Management Protocol (SNMP)-based management of Data-over-Cable Service Interface Specification (DOCSIS)-compliant Cable Modem Termination Systems. These managed objects facilitate protection of the cable network from misuse by subscribers. The Differentiated Services MIB (RFC 3289) provides the filtering functions needed here, making use of classification items defined in this specification. [STANDARDS-TRACK]Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modems and Cable Modem Termination Systems for Baseline Privacy PlusThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for Simple Network Management Protocol (SNMP) based management of the Baseline Privacy Plus features of DOCSIS 1.1 and DOCSIS 2.0 (Data-over-Cable Service Interface Specification) compliant Cable Modems and Cable Modem Termination Systems. [STANDARDS-TRACK]The Secure Shell (SSH) Protocol ArchitectureThe Secure Shell (SSH) Protocol is a protocol for secure remote login and other secure network services over an insecure network. This document describes the architecture of the SSH protocol, as well as the notation and terminology used in SSH protocol documents. It also discusses the SSH algorithm naming system that allows local extensions. The SSH protocol consists of three major components: The Transport Layer Protocol provides server authentication, confidentiality, and integrity with perfect forward secrecy. The User Authentication Protocol authenticates the client to the server. The Connection Protocol multiplexes the encrypted tunnel into several logical channels. Details of these protocols are described in separate documents. [STANDARDS-TRACK]Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB)This document defines a basic set of managed objects for SNMP-based management of extended QoS features of Cable Modems (CMs) and Cable Modem Termination Systems (CMTSs) conforming to the Data over Cable System (DOCSIS) specifications versions 1.1 and 2.0. [STANDARDS-TRACK]Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF InterfacesThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for Simple Network Management Protocol (SNMP) based management of the Radio Frequency (RF) interfaces for systems compliant with the Data Over Cable Service Interface Specifications (DOCSIS). [STANDARDS-TRACK]Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination SystemsThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP) based event notification management of Data Over Cable Service Interface Specification (DOCSIS) compliant Cable Modems and Cable Modem Termination Systems. This MIB is defined as an extension to the DOCSIS Cable Device MIB.This memo specifies a MIB module in a manner that is compliant to the Structure of Management Information Version 2 (SMIv2). The set of objects is consistent with the SNMP framework and existing SNMP standards. [STANDARDS-TRACK]Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination SystemsThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of Data Over Cable Service Interface Specification (DOCSIS)-compliant Cable Modems and Cable Modem Termination Systems.This memo obsoletes RFC 2669. [STANDARDS-TRACK]Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant DevicesThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS-TRACK]Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS-TRACK]Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant DevicesThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of events that can be generated by PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS-TRACK]Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration GuidelinesThis document provides guidance to aid in the understanding of collaboration on standards development between the Telecommunication Standardization Sector of the International Telecommunication Union (ITU-T) and the Internet Engineering Task Force (IETF) of the Internet Society (ISOC). It is an update of and obsoletes RFC 3356. The updates reflect changes in the IETF and ITU-T since RFC 3356 was written. The bulk of this document is common text with ITU-T A Series Supplement 3 (07/2012).Note: This was approved by TSAG on 4 July 2012 as Supplement 3 to the ITU-T A-Series of Recommendations. This document is not an Internet Standards Track specification; it is published for informational purposes.The IEEE 802/IETF RelationshipThis document describes the standardization cooperation between Project 802 of the Institute of Electrical and Electronics Engineers (IEEE) and the Internet Engineering Task Force (IETF). This document obsoletes RFC 4441.Note: This document was collaboratively developed by authors from both the IEEE 802 and IETF leadership and was reviewed and approved by the IEEE 802 Executive Committee prior to publication.Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsRFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.Informative ReferencesRetirement of the IETF FTP Servicemessage to the IETF mailing listRetiring the IETF FTP Service (Revised Plan)AcknowledgmentsThank you to , , , and on the IETF Tools Team for the operations and maintenance information that informed the community discussion at .Additionally, thank you to , , , , , , , , , , and for their valuable feedback and reviews of the specific document updates.Finally, thank you to for the sponsoring this document and the AD review.Author's AddressSoftware Engineering Instituterdd@cert.org