Software Engineering Institute

rdd@cert.org

General Network Working Group Internet-Draft 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.

In CY2021Q1, after community consultation, it was decided to retire the IETF FTP service running at ftp.ietf.org, ops.ietf.org and ietf.org . Appendix B of identified 30 RFCs published in the IETF and IAB streams between 1997-2006 that had 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 the subset (25) of these documents, which have not been updated by other documents, with HTTPS URIs to the same materials. 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 when, and only when, they appear in all capitals, as shown here. The original text from an RFC to be updated will be quotes with “OLD” and the replacement text will be quoted with “NEW”.

This document updates the following RFCs. Additionally, with permission of the IAB stream editor, and are also updated.

Section 3 of is updated as follows: OLD: Copies of RFCs are available on:

Copies of Internet-Drafts are available on:

NEW: Copies of RFCs are available on:

Copies of Internet-Drafts are available on:

Section 2.2 of 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/

Section 2 of is updated as follows: 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. TODO: consider approach to Appendix A scripts

The MIB in Section 3 of is updated as follows: OLD:

NEW:

The MIB in Section 4 of is updated as follows: OLD:

NEW:

The MIB in Section 3 of is updated as follows: OLD:

NEW:

The MIB in Section 4 of is updated as follows: OLD:

NEW:

The MIB in Section 6 of is updated as follows: OLD:

NEW:

The MIB in Section 7 of is updated as follows: OLD:

NEW:

The MIB in Section 4 of is updated as follows: OLD:

NEW:

The informative references in Section 14.2 of 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-02.mail, March 002.

The informative reference of 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.

The MIB in Section 5 of is updated as follows: OLD:

NEW:

The MIB in Section 4 of is updated as follows: OLD:

NEW:

The MIB in Section 3 of is updated as follows: OLD:

NEW:

The informative reference of 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.

The MIB in Section 5 of is updated as follows: OLD:

NEW:

The MIB in Section 5 of is updated as follows: OLD:

NEW:

The MIB in Section 4 of is updated as follows: OLD:

NEW:

The MIB in Section 4 of is updated as follows: OLD:

NEW:

The MIB in Section 4 of is updated as follows: OLD:

NEW:

The MIB in Section 5 of is updated as follows: OLD:

NEW:

The MIB in Section 5 of is updated as follows: OLD:

NEW:

Section 2.8.1 of 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

Section B.2 of 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>

If any other RFC not explicitly mentioned in an earlier section contains a reference of the form, “ftp://ftp.ietf.org/<path>”, this reference MUST be replaced with a URI of the form, “https://www.ietf.org/ietf-ftp/<path>”.

This document presents no new security consideration beyond those described in the updated documents.

This document has no IANA actions.

In 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. The 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] This 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. This 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] This 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] This 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] This 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] 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 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. This 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] This 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] 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) 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. The 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] This 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] 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 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] 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 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 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] 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] 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 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] 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 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] 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 Data Over Cable Service Interface Specification (DOCSIS)-compliant Cable Modems and Cable Modem Termination Systems.This memo obsoletes RFC 2669. [STANDARDS-TRACK] 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] 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] 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 events that can be generated by PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS-TRACK] This 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. This 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. RFC 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.

Thank you to Robert Sparks, Glen Barney, Henrik Levkowetz and Russ Housley on the IETF Tools Team for the operations and maintenance information which informed the community discussion with resulted in . Additionally, thank you to XXX for their contributions and valuable feedback.