Network Working Group R. Danyliw Internet-Draft Software Engineering Institute Updates: 2077, 2418, 2648, 2954, 2955, July 06, 2021 3020, 3083, 3201, 3202, 3295, 3684, 3962, 3970, 4036, 4131, 4251, 4323, 4546, 4547, 4639, 4682, 5098, 5428, 6756, 7241 (if approved) Intended status: Standards Track Expires: January 7, 2022 Updating References to the IETF FTP Service draft-danyliw-replace-ftp-pointers-01 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 Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on January 7, 2022. 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 Danyliw Expires January 7, 2022 [Page 1]
Internet-Draft Updating References to the IETF FTP Service July 2021 (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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3 3. Updated References . . . . . . . . . . . . . . . . . . . . . 3 3.1. RFC2077 . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. RFC2418 . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. RFC2648 . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. RFC2954 . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.5. RFC2955 . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.6. RFC3020 . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.7. RFC3083 . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.8. RFC3201 . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.9. RFC3202 . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.10. RFC3295 . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.11. RFC3684 . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.12. RFC3962 . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.13. RFC3970 . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.14. RFC4036 . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.15. RFC4131 . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.16. RFC4251 . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.17. RFC4323 . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.18. RFC4546 . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.19. RFC4547 . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.20. RFC4639 . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.21. RFC4682 . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.22. RFC5098 . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.23. RFC5428 . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.24. RFC6756 . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.25. RFC7241 . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.26. Generic Guidance . . . . . . . . . . . . . . . . . . . . 11 4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.1. Normative References . . . . . . . . . . . . . . . . . . 12 6.2. Informative References . . . . . . . . . . . . . . . . . 15 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16 Danyliw Expires January 7, 2022 [Page 2]
Internet-Draft Updating References to the IETF FTP Service July 2021 1. Introduction 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 [FTP-RETIREMENT]. Appendix B of [FTP-RETIREMENT-PLAN] 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. 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 quotes 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 stream editor, [RFC6756] and [RFC7241] are also updated. 3.1. RFC2077 Section 3 of [RFC2077] is updated as follows: OLD: Copies of RFCs are available on: ftp://ftp.isi.edu/in-notes/ Danyliw Expires January 7, 2022 [Page 3]
Internet-Draft Updating References to the IETF FTP Service July 2021 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/in-notes/ Copies of Internet-Drafts are available on: https://www.ietf.org/id/ 3.2. RFC2418 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. RFC2648 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. Danyliw Expires January 7, 2022 [Page 4]
Internet-Draft Updating References to the IETF FTP Service July 2021 3.4. RFC2954 The MIB in Section 3 of [RFC2954] is updated 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. RFC2955 The MIB in Section 4 of [RFC2955] is updated 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. RFC3020 The MIB in Section 3 of [RFC3020] is updated 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. RFC3083 The MIB in Section 4 of [RFC3083] is updated as follows: OLD: Danyliw Expires January 7, 2022 [Page 5]
Internet-Draft Updating References to the IETF FTP Service July 2021 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn NEW: Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 3.8. RFC3201 The MIB in Section 6 of [RFC3201] is updated 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. RFC3202 The MIB in Section 7 of [RFC3202] is updated 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. RFC3295 The MIB in Section 4 of [RFC3295] is updated 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/ Danyliw Expires January 7, 2022 [Page 6]
Internet-Draft Updating References to the IETF FTP Service July 2021 3.11. RFC3684 The 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. 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. 3.12. RFC3962 The informative reference of [RFC3962] is updated as follows: OLD: [