rfc9141.original   rfc9141.txt 
Network Working Group R. Danyliw Internet Engineering Task Force (IETF) R. Danyliw
Internet-Draft Software Engineering Institute Request for Comments: 9141 Software Engineering Institute
Updates: 2077, 2418, 2648, 2954, 2955, October 22, 2021 Updates: 2077, 2418, 2648, 2954, 2955, 3020, November 2021
3020, 3083, 3201, 3202, 3295, 3083, 3201, 3202, 3295, 3684, 3962,
3684, 3962, 3970, 4036, 4131, 3970, 4036, 4131, 4251, 4323, 4546,
4251, 4323, 4546, 4547, 4639, 4547, 4639, 4682, 5098, 5428, 6756,
4682, 5098, 5428, 6756, 7241 7241
(if approved) Category: Standards Track
Intended status: Standards Track ISSN: 2070-1721
Expires: April 25, 2022
Updating References to the IETF FTP Service Updating References to the IETF FTP Service
draft-danyliw-replace-ftp-pointers-06
Abstract Abstract
The IETF FTP service running at ftp.ietf.org, ops.ietf.org and 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 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 IAB streams include URIs that reference this FTP service. To ensure
that the materials referenced using the IETF FTP service can still be that the materials referenced using the IETF FTP service can still be
found, this document updates the FTP-based references in these found, this document updates the FTP-based references in these
affected documents with HTTPS URIs. affected documents with HTTPS URIs.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on April 25, 2022. 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 Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Revised BSD License text as described in Section 4.e of the
the Trust Legal Provisions and are provided without warranty as Trust Legal Provisions and are provided without warranty as described
described in the Simplified BSD License. in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3 2. Conventions and Definitions
3. Updated References . . . . . . . . . . . . . . . . . . . . . 3 3. Updated References
3.1. RFC2077 . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. RFC 2077
3.2. RFC2418 . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. RFC 2418
3.3. RFC2648 . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. RFC 2648
3.4. RFC2954 . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.4. RFC 2954
3.5. RFC2955 . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.5. RFC 2955
3.6. RFC3020 . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.6. RFC 3020
3.7. RFC3083 . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.7. RFC 3083
3.8. RFC3201 . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.8. RFC 3201
3.9. RFC3202 . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.9. RFC 3202
3.10. RFC3295 . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.10. RFC 3295
3.11. RFC3684 . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.11. RFC 3684
3.12. RFC3962 . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.12. RFC 3962
3.13. RFC3970 . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.13. RFC 3970
3.14. RFC4036 . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.14. RFC 4036
3.15. RFC4131 . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.15. RFC 4131
3.16. RFC4251 . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.16. RFC 4251
3.17. RFC4323 . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.17. RFC 4323
3.18. RFC4546 . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.18. RFC 4546
3.19. RFC4547 . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.19. RFC 4547
3.20. RFC4639 . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.20. RFC 4639
3.21. RFC4682 . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.21. RFC 4682
3.22. RFC5098 . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.22. RFC 5098
3.23. RFC5428 . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.23. RFC 5428
3.24. RFC6756 . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.24. RFC 6756
3.25. RFC7241 . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.25. RFC 7241
3.26. Generic Guidance . . . . . . . . . . . . . . . . . . . . 13 3.26. Generic Guidance
4. Security Considerations . . . . . . . . . . . . . . . . . . . 13 4. Security Considerations
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. IANA Considerations
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. References
6.1. Normative References . . . . . . . . . . . . . . . . . . 13 6.1. Normative References
6.2. Informative References . . . . . . . . . . . . . . . . . 16 6.2. Informative References
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 18 Acknowledgments
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18 Author's Address
1. Introduction 1. Introduction
After community consultation in late 2020, it was decided to retire After community consultation in late 2020, it was decided to retire
the IETF FTP service running at ftp.ietf.org, ops.ietf.org and the IETF FTP service running at ftp.ietf.org, ops.ietf.org, and
ietf.org [FTP-RETIREMENT]. Appendix B of [FTP-RETIREMENT-PLAN] ietf.org [FTP-RETIREMENT]. Appendix B of [FTP-RETIREMENT-PLAN]
identified 30 RFCs published in the IETF and IAB streams between identifies 30 RFCs published in the IETF and IAB streams between
1997-2006 that had at least one explicit or inline reference to a URI 1997-2006 that have at least one explicit or inline reference to a
pointing to the IETF FTP service. To ensure that the materials URI pointing to the IETF FTP service. To ensure that the materials
referenced using the IETF FTP service can still be found, this referenced using the IETF FTP service can still be found, this
document formally updates those RFCs that had not been updated by document formally updates those RFCs that had not been updated by
other documents with HTTPS URIs to the same materials. other documents with HTTPS URIs to the same materials.
Section 3 enumerates each of the affected RFCs and provides Section 3 enumerates each of the affected RFCs and provides
replacement text. replacement text.
2. Conventions and Definitions 2. Conventions and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
The original text from an RFC to be updated will be quoted with "OLD" The original text from an RFC to be updated will be quoted with
and the replacement text will be quoted with "NEW". "OLD", and the replacement text will be quoted with "NEW".
3. Updated References 3. Updated References
This document updates the following RFCs. This document updates the following RFCs.
[RFC2077] [RFC2418] [RFC2648] [RFC2954] [RFC2955] [RFC3020] [RFC3083] [RFC2077] [RFC2418] [RFC2648] [RFC2954] [RFC2955] [RFC3020] [RFC3083]
[RFC3201] [RFC3202] [RFC3295] [RFC3684] [RFC3962] [RFC3970] [RFC4036] [RFC3201] [RFC3202] [RFC3295] [RFC3684] [RFC3962] [RFC3970] [RFC4036]
[RFC4131] [RFC4251] [RFC4323] [RFC4546] [RFC4547] [RFC4639] [RFC4682] [RFC4131] [RFC4251] [RFC4323] [RFC4546] [RFC4547] [RFC4639] [RFC4682]
[RFC5098] [RFC5428] [RFC5098] [RFC5428]
Additionally, with permission of the IAB, [RFC6756] and [RFC7241] are Additionally, with permission of the IAB, [RFC6756] and [RFC7241] are
also updated. also updated.
3.1. RFC2077 3.1. RFC 2077
Section 3 of [RFC2077] is updated as follows: Section 3 of [RFC2077] is updated as follows:
OLD: OLD:
Copies of RFCs are available on: | Copies of RFCs are available on:
|
ftp://ftp.isi.edu/in-notes/ | ftp://ftp.isi.edu/in-notes/
|
Copies of Internet-Drafts are available on: | Copies of Internet-Drafts are available on:
|
ftp://ftp.ietf.org/internet-drafts/ | ftp://ftp.ietf.org/internet-drafts/
NEW: NEW:
Copies of RFCs are available on: | Copies of RFCs are available on:
|
https://www.rfc-editor.org/rfc/ | https://www.rfc-editor.org/rfc/
|
Copies of Internet-Drafts are available on: | Copies of Internet-Drafts are available on:
|
https://www.ietf.org/id/ | https://www.ietf.org/id/
3.2. RFC2418 3.2. RFC 2418
Section 2.2 of [RFC2418] is updated as follows: Section 2.2 of [RFC2418] is updated as follows:
OLD: OLD:
Those archives are located at ftp://ftp.ietf.org/ietf-mail-archive. | Those archives are located at ftp://ftp.ietf.org/ietf-mail-
| archive.
NEW: NEW:
Those archives are located at | Those archives are located at https://www.ietf.org/ietf-ftp/ietf-
https://www.ietf.org/ietf-ftp/ietf-mail-archive/. | mail-archive/.
3.3. RFC2648 3.3. RFC 2648
Section 2 of [RFC2648] is updated below. Note that the scripts in Section 2 of [RFC2648] is updated below. Note that the scripts in
Appendix A have not been updated. Appendix A have not been updated.
OLD: OLD:
The list of minutes maintained by the IETF for each working group and | The list of minutes maintained by the IETF for each working group
conference in the subtree pointed at by the URL ftp://ietf.org/ietf/ | and conference in the subtree pointed at by the URL
is considered the definitive assignment of URNs for working group or | ftp://ietf.org/ietf/ is considered the definitive assignment of
birds of a feather minutes. | URNs for working group or birds of a feather minutes.
NEW: NEW:
The list of minutes maintained by the IETF for each working group and | The list of minutes maintained by the IETF for each working group
conference in the subtree pointed at by the URL | and conference in the subtree pointed at by the URL
https://www.ietf.org/how/meetings/proceedings/ is considered the | https://www.ietf.org/how/meetings/proceedings/ is considered the
definitive assignment of URNs for working group or birds of a feather | definitive assignment of URNs for working group or birds of a
minutes. | feather minutes.
3.4. RFC2954 3.4. RFC 2954
The CONTACT-INFO in the MIB in Section 3 of [RFC2954] contains an The CONTACT-INFO in the MIB in Section 3 of [RFC2954] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Email Archive: | Email Archive:
ftp://ftp.ietf.org/ietf-mail-archive/frnetmib |
| ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW: NEW:
Email Archive: | Email Archive:
https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ |
| https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
3.5. RFC2955 3.5. RFC 2955
The CONTACT-INFO in the MIB in Section 4 of [RFC2955] contains an The CONTACT-INFO in the MIB in Section 4 of [RFC2955] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Email Archive: | Email Archive:
ftp://ftp.ietf.org/ietf-mail-archive/frnetmib |
| ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW: NEW:
Email Archive: | Email Archive:
https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ |
| https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/
3.6. RFC3020 3.6. RFC 3020
The CONTACT-INFO in the MIB in Section 3 of [RFC3020] contains an The CONTACT-INFO in the MIB in Section 3 of [RFC3020] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Email Archive: | Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW: NEW:
Email Archive: | Email Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/
https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ | frnetmib/
3.7. RFC3083 3.7. RFC 3083
The CONTACT-INFO in the MIB in Section 4 of [RFC3083] contains an The CONTACT-INFO in the MIB in Section 4 of [RFC3083] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.8. RFC3201 3.8. RFC 3201
The CONTACT-INFO in the MIB in Section 6 of [RFC3201] contains an The CONTACT-INFO in the MIB in Section 6 of [RFC3201] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib | Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW: NEW:
Email Archive: | Email Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/
https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ | frnetmib/
3.9. RFC3202 3.9. RFC 3202
The CONTACT-INFO in the MIB in Section 7 of [RFC3202] contains an The CONTACT-INFO in the MIB in Section 7 of [RFC3202] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib | Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
NEW: NEW:
Email Archive: | Email Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/
https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ | frnetmib/
3.10. RFC3295 3.10. RFC 3295
The CONTACT-INFO in the MIB in Section 4 of [RFC3295] contains an The CONTACT-INFO in the MIB in Section 4 of [RFC3295] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Email Archive: | Email Archive:
ftp://ftp.ietf.org/ietf-mail-archive/gsmp/ |
| ftp://ftp.ietf.org/ietf-mail-archive/gsmp/
NEW: NEW:
Email Archive: | Email Archive:
https://www.ietf.org/ietf-ftp/ietf-mail-archive/gsmp/ |
| https://www.ietf.org/ietf-ftp/ietf-mail-archive/gsmp/
3.11. RFC3684 3.11. RFC 3684
The informative references in Section 14.2 of [RFC3684] are updated Two informative references in Section 14.2 of [RFC3684] are updated
as follows: as follows:
OLD: OLD:
[7] Ogier, R., Message in IETF email archive for MANET, | [7] Ogier, R., Message in IETF email archive for MANET,
ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-02.mail, | ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-02.mail, February
February 2002. | 2002.
NEW: NEW:
[7] Ogier, R., Message in IETF email archive for MANET, | [7] Ogier, R., Message in IETF email archive for MANET,
https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/ | https://www.ietf.org/ietf-ftp/ietf-mail-archive/
2002-02.mail, February 2002. | manet/2002-02.mail, February 2002.
OLD: OLD:
[9] Ogier, R., Message in IETF email archive for MANET, | [9] Ogier, R., Message in IETF email archive for MANET,
ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-03.mail, March | ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-03.mail, March
2002. | 2002.
NEW: NEW:
[9] Ogier, R., Message in IETF email archive for MANET, | [9] Ogier, R., Message in IETF email archive for MANET,
https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/ | https://www.ietf.org/ietf-ftp/ietf-mail-archive/
2002-03.mail, March 2002. | manet/2002-03.mail, March 2002.
3.12. RFC3962 3.12. RFC 3962
The informative reference of [RFC3962] is updated as follows: An informative reference in [RFC3962] is updated as follows:
OLD: OLD:
[LEACH] Leach, P., email to IETF Kerberos working group mailing | [LEACH] Leach, P., email to IETF Kerberos working group mailing
list, 5 May 2003, ftp://ftp.ietf.org/ietf-mail- | list, 5 May 2003, ftp://ftp.ietf.org/ietf-mail-archive/krb-
archive/krb-wg/2003-05.mail. | wg/2003-05.mail.
NEW: NEW:
[LEACH] Leach, P., email to IETF Kerberos working group mailing | [LEACH] Leach, P., email to IETF Kerberos working group mailing
list, 5 May 2003, https://www.ietf.org/ietf-ftp/ | list, 5 May 2003, https://www.ietf.org/ietf-ftp/ietf-mail-archive/
ietf-mail-archive/krb-wg/2003-05.mail. | krb-wg/2003-05.mail.
3.13. RFC3970 3.13. RFC 3970
The CONTACT-INFO in the MIB in Section 5 of [RFC3970] contains an The CONTACT-INFO in the MIB in Section 5 of [RFC3970] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ops.ietf.org/pub/lists | Archive: ftp://ops.ietf.org/pub/lists
NEW: NEW:
Archive: | Archive: https://www.ietf.org/ietf-ftp/concluded-wg-ietf-mail-
https://www.ietf.org/ietf-ftp/concluded-wg-ietf-mail-archive/tewg/ | archive/tewg/
3.14. RFC4036 3.14. RFC 4036
The CONTACT-INFO in the MIB in Section 4 of [RFC4036] contains an The CONTACT-INFO in the MIB in Section 4 of [RFC4036] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.15. RFC4131 3.15. RFC 4131
The CONTACT-INFO in the MIB in Section 3 of [RFC4131] contains an The CONTACT-INFO in the MIB in Section 3 of [RFC4131] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn. | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn.
NEW: NEW:
Archive: | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/.
https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/.
3.16. RFC4251 3.16. RFC 4251
The informative reference of [RFC4251] is updated as follows: An informative reference in [RFC4251] is updated as follows:
OLD: OLD:
[DAI] Dai, W., "An attack against SSH2 protocol", Email | [DAI] Dai, W., "An attack against SSH2 protocol", Email to the
to the SECSH Working Group ietf-ssh@netbsd.org | SECSH Working Group ietf-ssh@netbsd.org ftp:// ftp.ietf.org/ietf-
ftp:// ftp.ietf.org/ietf-mail-archive/secsh/2002- | mail-archive/secsh/2002-02.mail, Feb 2002.
02.mail, Feb 2002.
NEW: NEW:
[DAI] Dai, W., "An attack against SSH2 protocol", Email | [DAI] Dai, W., "An attack against SSH2 protocol", Email to the
to the SECSH Working Group ietf-ssh@netbsd.org | SECSH Working Group ietf-ssh@netbsd.org https://www.ietf.org/ietf-
https://www.ietf.org/ietf-ftp/ietf-mail-archive/ | ftp/ietf-mail-archive/ secsh/2002-02.mail, Feb 2002.
secsh/2002-02.mail, Feb 2002.
3.17. RFC4323 3.17. RFC 4323
The CONTACT-INFO in the MIB in Section 5 of [RFC4323] contains an The CONTACT-INFO in the MIB in Section 5 of [RFC4323] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.18. RFC4546 3.18. RFC 4546
The CONTACT-INFO in the MIB in Section 4 of [RFC4546] contains an The CONTACT-INFO in the MIB in Section 4 of [RFC4546] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.19. RFC4547 3.19. RFC 4547
The CONTACT-INFO in the MIB in Section 4 of [RFC4547] contains an The CONTACT-INFO in the MIB in Section 4 of [RFC4547] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.20. RFC4639 3.20. RFC 4639
The CONTACT-INFO in the MIB in Section 4 of [RFC4639] contains an The CONTACT-INFO in the MIB in Section 4 of [RFC4639] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.21. RFC4682 3.21. RFC 4682
The CONTACT-INFO in the MIB in Section 4 of [RFC4682] contains an The CONTACT-INFO in the MIB in Section 4 of [RFC4682] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.22. RFC5098 3.22. RFC 5098
The CONTACT-INFO in the MIB in Section 5 of [RFC5098] contains an The CONTACT-INFO in the MIB in Section 5 of [RFC5098] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.23. RFC5428 3.23. RFC 5428
The CONTACT-INFO in the MIB in Section 6 of [RFC5428] contains an The CONTACT-INFO in the MIB in Section 6 of [RFC5428] contains an
outdated email archive reference. The revised reference is as outdated email archive reference. The revised reference is as
follows: follows:
OLD: OLD:
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn | Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
NEW: NEW:
Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ | Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/
3.24. RFC6756 3.24. RFC 6756
Section 2.8.1 of [RFC6756] is updated as follows: Section 2.8.1 of [RFC6756] is updated as follows:
OLD: OLD:
Current list and status of all IETF RFCs: | Current list and status of all IETF RFCs:
ftp://ftp.ietf.org/rfc/rfc-index.txt |
| 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 | Current list and description of all IETF Internet-Drafts:
|
| ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt
NEW: NEW:
Current list and status of all IETF RFCs: | Current list and status of all IETF RFCs:
https://www.rfc-editor.org/rfc/rfc-index.txt |
| 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 | Current list and description of all IETF Internet-Drafts:
|
| https://www.ietf.org/id/1id-abstracts.txt
3.25. RFC7241 3.25. RFC 7241
Section B.2 of [RFC7241] is updated as follows: Appendix B.2 of [RFC7241] is updated as follows:
OLD: OLD:
Current list and description of all IETF Internet-Drafts: | Current list and description of all IETF Internet-Drafts:
<ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt> |
| <ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt>
NEW: NEW:
Current list and description of all IETF Internet-Drafts: | Current list and description of all IETF Internet-Drafts:
<https://www.ietf.org/id/1id-abstracts.txt> |
| <https://www.ietf.org/id/1id-abstracts.txt>
3.26. Generic Guidance 3.26. Generic Guidance
If any other RFC not explicitly mentioned in an earlier section If any other RFC not explicitly mentioned in an earlier section
contains a reference of the form, "ftp://ftp.ietf.org/<path>", this contains a reference of the form "ftp://ftp.ietf.org/<path>", the
reference MUST be replaced with a URI of the form, reference MUST be replaced with a URI of the form
"https://www.ietf.org/ietf-ftp/<path>". "https://www.ietf.org/ietf-ftp/<path>".
4. Security Considerations 4. Security Considerations
This document does not alter the security consideration of the This document does not alter the security considerations of the
updated documents. updated documents.
This document replaces URIs using an FTP scheme with equivalent URIs This document replaces URIs to the IETF infrastructure that use an
to the IETF infrastructure (i.e., www.ietf.org) that use HTTPS. FTP scheme with equivalent HTTPS scheme URIs. These updates ensure
These updates ensure the continued availability of content referenced the continued availability of content referenced in previously
in previously published RFCs when the IETF FTP service is retired. published RFCs when the IETF FTP service is retired. Additionally,
Additionally, the replacement of the clear-text FTP with HTTPS will the replacement of the cleartext FTP with HTTPS will ensure that
ensure that resources on the IETF infrastructure can be accessed in a resources on the IETF infrastructure can be accessed in a more secure
more secure way. For example, HTTPS provides an encrypted channel way. For example, HTTPS provides an encrypted channel that includes
that includes protections such as verifying the server's identity per protections, such as verifying the server's identity per the
the certificate verification behavior of the client, and integrity certificate verification behavior of the client and integrity and
and confidentiality protection commensurate with the negotiated TLS confidentiality protection commensurate with the negotiated TLS
protocol version and ciphersuite. protocol version and ciphersuite.
5. IANA Considerations 5. IANA Considerations
This document has no IANA actions. This document has no IANA actions.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2077] Nelson, S., Parks, C., and , "The Model Primary Content [RFC2077] Nelson, S., Parks, C., and M. Ardron, "The Model Primary
Type for Multipurpose Internet Mail Extensions", RFC 2077, Content Type for Multipurpose Internet Mail Extensions",
DOI 10.17487/RFC2077, January 1997, RFC 2077, DOI 10.17487/RFC2077, January 1997,
<https://www.rfc-editor.org/info/rfc2077>. <https://www.rfc-editor.org/info/rfc2077>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2418] Bradner, S., "IETF Working Group Guidelines and [RFC2418] Bradner, S., "IETF Working Group Guidelines and
Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418, Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418,
September 1998, <https://www.rfc-editor.org/info/rfc2418>. September 1998, <https://www.rfc-editor.org/info/rfc2418>.
skipping to change at page 16, line 48 skipping to change at line 723
DOI 10.17487/RFC7241, July 2014, DOI 10.17487/RFC7241, July 2014,
<https://www.rfc-editor.org/info/rfc7241>. <https://www.rfc-editor.org/info/rfc7241>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
6.2. Informative References 6.2. Informative References
[FTP-RETIREMENT] [FTP-RETIREMENT]
"Retirement of the IETF FTP Service", March 2021, Danyliw, R., "Retirement of the IETF FTP Service", message
to the IETF mailing list, 3 March 2021,
<https://mailarchive.ietf.org/arch/msg/ietf/vi- <https://mailarchive.ietf.org/arch/msg/ietf/vi-
8bFqlgBFjB2jJ1SIAGHiNRdg/>. 8bFqlgBFjB2jJ1SIAGHiNRdg/>.
[FTP-RETIREMENT-PLAN] [FTP-RETIREMENT-PLAN]
"(Revised Plan) Retiring the IETF FTP Service", March "Retiring the IETF FTP Service (Revised Plan)", March
2021, <https://www.ietf.org/media/documents/Revised- 2021, <https://www.ietf.org/media/documents/Revised-
Retiring-IETF-FTP-Service-2021-03.pdf>. Retiring-IETF-FTP-Service-2021-03.pdf>.
Acknowledgments Acknowledgments
Thank you to Robert Sparks, Glen Barney, Henrik Levkowetz and Russ Thank you to Robert Sparks, Glen Barney, Henrik Levkowetz, and Russ
Housley on the IETF Tools Team for the operations and maintenance Housley on the IETF Tools Team for the operations and maintenance
information that informed the community discussion at information that informed the community discussion at
[FTP-RETIREMENT]. [FTP-RETIREMENT].
Additionally, thank you to Brian Carpenter, Martin Duke, Russ Additionally, thank you to Brian Carpenter, Martin Duke, Russ
Housley, Benjamin Kaduk, Eric Kline, Murray Kucherawy, Mirja Housley, Benjamin Kaduk, Eric Kline, Murray Kucherawy, Mirja
Kuehlewind, Scott Mansfield, Tom Petch, John Scudder, and Rob Wilton Kühlewind, Scott Mansfield, Tom Petch, John Scudder, and Rob Wilton
for their valuable feedback and reviews of the specific document for their valuable feedback and reviews of the specific document
updates. updates.
Finally, thank you to Eric Vynke for the sponsoring this document and Finally, thank you to Éric Vyncke for the sponsoring this document
the AD review. and the AD review.
Author's Address Author's Address
Roman Danyliw Roman Danyliw
Software Engineering Institute Software Engineering Institute
EMail: rdd@cert.org Email: rdd@cert.org
 End of changes. 103 change blocks. 
235 lines changed or deleted 239 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/