idnits 2.17.1 draft-danyliw-replace-ftp-pointers-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. -- The draft header indicates that this document updates RFC2077, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2954, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2955, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2648, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2418, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC2077, updated by this document, for RFC5378 checks: 1995-10-23) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 08, 2021) is 1138 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '7' on line 298 -- Looks like a reference, but probably isn't: '9' on line 309 == Missing Reference: 'LEACH' is mentioned on line 325, but not defined == Missing Reference: 'DAI' is mentioned on line 378, but not defined ** Downref: Normative reference to an Informational RFC: RFC 2648 ** Downref: Normative reference to an Informational RFC: RFC 3083 ** Downref: Normative reference to an Experimental RFC: RFC 3684 ** Downref: Normative reference to an Informational RFC: RFC 6756 ** Downref: Normative reference to an Informational RFC: RFC 7241 Summary: 5 errors (**), 0 flaws (~~), 4 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Danyliw 3 Internet-Draft Software Engineering Institute 4 Updates: 2077, 2418, 2648, 2954, 2955, March 08, 2021 5 3020, 3083, 3201, 3202, 3295, 6 3684, 3962, 3970, 4036, 4131, 7 4251, 4323, 4546, 4547, 4639, 8 4682, 5098, 5428, 6756, 7241 9 (if approved) 10 Intended status: Standards Track 11 Expires: September 9, 2021 13 Updating References to the IETF FTP Service 14 draft-danyliw-replace-ftp-pointers-00 16 Abstract 18 The IETF FTP service running at ftp.ietf.org, ops.ietf.org and 19 ietf.org will be retired. A number of published RFCs in the IETF and 20 IAB streams include URIs that reference this FTP service. To ensure 21 that the materials referenced using the IETF FTP service can still be 22 found, this document updates the FTP-based references in these 23 affected documents with HTTPS URIs. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on September 9, 2021. 42 Copyright Notice 44 Copyright (c) 2021 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (https://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3 61 3. Updated References . . . . . . . . . . . . . . . . . . . . . 3 62 3.1. RFC2077 . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 3.2. RFC2418 . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 3.3. RFC2648 . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 3.4. RFC2954 . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 3.5. RFC2955 . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 3.6. RFC3020 . . . . . . . . . . . . . . . . . . . . . . . . . 5 68 3.7. RFC3083 . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 3.8. RFC3201 . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 3.9. RFC3202 . . . . . . . . . . . . . . . . . . . . . . . . . 6 71 3.10. RFC3295 . . . . . . . . . . . . . . . . . . . . . . . . . 6 72 3.11. RFC3684 . . . . . . . . . . . . . . . . . . . . . . . . . 7 73 3.12. RFC3962 . . . . . . . . . . . . . . . . . . . . . . . . . 7 74 3.13. RFC3970 . . . . . . . . . . . . . . . . . . . . . . . . . 8 75 3.14. RFC4036 . . . . . . . . . . . . . . . . . . . . . . . . . 8 76 3.15. RFC4131 . . . . . . . . . . . . . . . . . . . . . . . . . 8 77 3.16. RFC4251 . . . . . . . . . . . . . . . . . . . . . . . . . 8 78 3.17. RFC4323 . . . . . . . . . . . . . . . . . . . . . . . . . 9 79 3.18. RFC4546 . . . . . . . . . . . . . . . . . . . . . . . . . 9 80 3.19. RFC4547 . . . . . . . . . . . . . . . . . . . . . . . . . 9 81 3.20. RFC4639 . . . . . . . . . . . . . . . . . . . . . . . . . 9 82 3.21. RFC4682 . . . . . . . . . . . . . . . . . . . . . . . . . 10 83 3.22. RFC5098 . . . . . . . . . . . . . . . . . . . . . . . . . 10 84 3.23. RFC5428 . . . . . . . . . . . . . . . . . . . . . . . . . 10 85 3.24. RFC6756 . . . . . . . . . . . . . . . . . . . . . . . . . 10 86 3.25. RFC7241 . . . . . . . . . . . . . . . . . . . . . . . . . 11 87 3.26. Generic Guidance . . . . . . . . . . . . . . . . . . . . 11 88 4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 89 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 90 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 91 6.1. Normative References . . . . . . . . . . . . . . . . . . 12 92 6.2. Informative References . . . . . . . . . . . . . . . . . 15 93 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 16 94 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16 96 1. Introduction 98 In CY2021Q1, after community consultation, it was decided to retire 99 the IETF FTP service running at ftp.ietf.org, ops.ietf.org and 100 ietf.org [FTP-RETIREMENT]. Appendix B of [FTP-RETIREMENT-PLAN] 101 identified 30 RFCs published in the IETF and IAB streams between 102 1997-2006 that had at least one explicit or inline reference to a URI 103 pointing to the IETF FTP service. To ensure that the materials 104 referenced using the IETF FTP service can still be found, this 105 document formally updates the subset (25) of these documents, which 106 have not been updated by other documents, with HTTPS URIs to the same 107 materials. 109 Section 3 enumerates each of the affected RFCs and provides 110 replacement text. 112 2. Conventions and Definitions 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 116 "OPTIONAL" in this document are to be interpreted as described in BCP 117 14 [RFC2119] [RFC8174] when, and only when, they appear in all 118 capitals, as shown here. 120 The original text from an RFC to be updated will be quotes with "OLD" 121 and the replacement text will be quoted with "NEW". 123 3. Updated References 125 This document updates the following RFCs. 127 [RFC2077] [RFC2418] [RFC2648] [RFC2954] [RFC2955] [RFC3020] [RFC3083] 128 [RFC3201] [RFC3202] [RFC3295] [RFC3684] [RFC3962] [RFC3970] [RFC4036] 129 [RFC4131] [RFC4251] [RFC4323] [RFC4546] [RFC4547] [RFC4639] [RFC4682] 130 [RFC5098] [RFC5428] 132 Additionally, with permission of the IAB stream editor, [RFC6756] and 133 [RFC7241] are also updated. 135 3.1. RFC2077 137 Section 3 of [RFC2077] is updated as follows: 139 OLD: 141 Copies of RFCs are available on: 143 ftp://ftp.isi.edu/in-notes/ 145 Copies of Internet-Drafts are available on: 147 ftp://ftp.ietf.org/internet-drafts/ 149 NEW: 151 Copies of RFCs are available on: 153 https://www.rfc-editor.org/in-notes/ 155 Copies of Internet-Drafts are available on: 157 https://www.ietf.org/id/ 159 3.2. RFC2418 161 Section 2.2 of [RFC2418] is updated as follows: 163 OLD: 165 Those archives are located at ftp://ftp.ietf.org/ietf-mail-archive. 167 NEW: 169 Those archives are located at https://www.ietf.org/ietf-ftp/ietf- 170 mail-archive/ 172 3.3. RFC2648 174 Section 2 of [RFC2648] is updated as follows: 176 OLD: 178 The list of minutes maintained by the IETF for each working group and 179 conference in the subtree pointed at by the URL ftp://ietf.org/ietf/ 180 is considered the definitive assignment of URNs for working group or 181 birds of a feather minutes. 183 NEW: 185 The list of minutes maintained by the IETF for each working group and 186 conference in the subtree pointed at by the URL 187 https://www.ietf.org/how/meetings/proceedings/ is considered the 188 definitive assignment of URNs for working group or birds of a feather 189 minutes. 191 TODO: consider approach to Appendix A scripts 193 3.4. RFC2954 195 The MIB in Section 3 of [RFC2954] is updated as follows: 197 OLD: 199 Email Archive: 200 ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 202 NEW: 204 Email Archive: 205 https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ 207 3.5. RFC2955 209 The MIB in Section 4 of [RFC2955] is updated as follows: 211 OLD: 213 Email Archive: 214 ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 216 NEW: 218 Email Archive: 219 https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ 221 3.6. RFC3020 223 The MIB in Section 3 of [RFC3020] is updated as follows: 225 OLD: 227 Email Archive: 228 ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 230 NEW: 232 Email Archive: 233 https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ 235 3.7. RFC3083 237 The MIB in Section 4 of [RFC3083] is updated as follows: 239 OLD: 241 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 243 NEW: 245 Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 247 3.8. RFC3201 249 The MIB in Section 6 of [RFC3201] is updated as follows: 251 OLD: 253 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 255 NEW: 257 Email Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ 259 3.9. RFC3202 261 The MIB in Section 7 of [RFC3202] is updated as follows: 263 OLD: 265 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 267 NEW: 269 Email Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/frnetmib/ 271 3.10. RFC3295 273 The MIB in Section 4 of [RFC3295] is updated as follows: 275 OLD: 277 Email Archive: 278 ftp://ftp.ietf.org/ietf-mail-archive/gsmp/ 280 NEW: 282 Email Archive: 283 https://www.ietf.org/ietf-ftp/ietf-mail-archive/gsmp/ 285 3.11. RFC3684 287 The informative references in Section 14.2 of [RFC3684] are updated 288 as follows: 290 OLD: 292 [7] Ogier, R., Message in IETF email archive for MANET, 293 ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-02.mail, February 294 2002. 296 NEW: 298 [7] Ogier, R., Message in IETF email archive for MANET, 299 https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/2002-02.mail, 300 February 2002. 302 OLD: 304 [9] Ogier, R., Message in IETF email archive for MANET, 305 ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-03.mail, March 2002. 307 NEW: 309 [9] Ogier, R., Message in IETF email archive for MANET, 310 https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/2002-02.mail, 311 March 002. 313 3.12. RFC3962 315 The informative reference of [RFC3962] is updated as follows: 317 OLD: 319 [LEACH] Leach, P., email to IETF Kerberos working group mailing list, 320 5 May 2003, ftp://ftp.ietf.org/ietf-mail- archive/krb- 321 wg/2003-05.mail. 323 NEW: 325 [LEACH] Leach, P., email to IETF Kerberos working group mailing list, 326 5 May 2003, https://www.ietf.org/ietf-ftp/ietf-mail- 327 archive/krb-wg/2003-05.mail. 329 3.13. RFC3970 331 The MIB in Section 5 of [RFC3970] is updated as follows: 333 OLD: 335 Archive: ftp://ops.ietf.org/pub/lists 337 NEW: 339 Archive: 340 https://www.ietf.org/ietf-ftp/concluded-wg-ietf-mail-archive/tewg/ 342 3.14. RFC4036 344 The MIB in Section 4 of [RFC4036] is updated as follows: 346 OLD: 348 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 350 NEW: 352 Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 354 3.15. RFC4131 356 The MIB in Section 3 of [RFC4131] is updated as follows: 358 OLD: 360 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn. 362 NEW: 364 Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/. 366 3.16. RFC4251 368 The informative reference of [RFC4251] is updated as follows: 370 OLD: 372 [DAI] Dai, W., "An attack against SSH2 protocol", Email to the SECSH 373 Working Group ietf-ssh@netbsd.org ftp:// ftp.ietf.org/ietf-mail- 374 archive/secsh/2002- 02.mail, Feb 2002. 376 NEW: 378 [DAI] Dai, W., "An attack against SSH2 protocol", Email to the SECSH 379 Working Group ietf-ssh@netbsd.org https://www.ietf.org/ietf-ftp/ietf- 380 mail-archive/ secsh/2002-02.mail, Feb 2002. 382 3.17. RFC4323 384 The MIB in Section 5 of [RFC4323] is updated as follows: 386 OLD: 388 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 390 NEW: 392 Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 394 3.18. RFC4546 396 The MIB in Section 5 of [RFC4546] is updated as follows: 398 OLD: 400 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 402 NEW: 404 Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 406 3.19. RFC4547 408 The MIB in Section 4 of [RFC4547] is updated as follows: 410 OLD: 412 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 414 NEW: 416 Archive: 417 https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 419 3.20. RFC4639 421 The MIB in Section 4 of [RFC4639] is updated as follows: 423 OLD: 425 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 427 NEW: 429 Archive: 430 https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 432 3.21. RFC4682 434 The MIB in Section 4 of [RFC4682] is updated as follows: 436 OLD: 438 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 440 NEW: 442 Archive: 443 https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 445 3.22. RFC5098 447 The MIB in Section 5 of [RFC5098] is updated as follows: 449 OLD: 451 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 453 NEW: 455 Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 457 3.23. RFC5428 459 The MIB in Section 5 of [RFC5428] is updated as follows: 461 OLD: 463 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 465 NEW: 467 Archive: https://www.ietf.org/ietf-ftp/ietf-mail-archive/ipcdn/ 469 3.24. RFC6756 471 Section 2.8.1 of [RFC6756] is updated as follows: 473 OLD: 475 Current list and status of all IETF RFCs: ftp://ftp.ietf.org/rfc/rfc- 476 index.txt 478 Current list and description of all IETF Internet-Drafts: 479 ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt 481 NEW: 483 Current list and status of all IETF RFCs: https://www.rfc- 484 editor.org/rfc/rfc-index.txt 486 Current list and description of all IETF Internet-Drafts: 487 https://www.ietf.org/id/1id-abstracts.txt 489 3.25. RFC7241 491 Section B.2 of [RFC7241] is updated as follows: 493 OLD: 495 Current list and description of all IETF Internet-Drafts: 496 498 NEW: 500 Current list and description of all IETF Internet-Drafts: 501 503 3.26. Generic Guidance 505 If any other RFC not explicitly mentioned in an earlier section 506 contains a reference of the form, "ftp://ftp.ietf.org/", this 507 reference MUST be replaced with a URI of the form, 508 "https://www.ietf.org/ietf-ftp/". 510 4. Security Considerations 512 This document presents no new security consideration beyond those 513 described in the updated documents. 515 5. IANA Considerations 517 This document has no IANA actions. 519 6. References 521 6.1. Normative References 523 [RFC2077] Nelson, S., Parks, C., and , "The Model Primary Content 524 Type for Multipurpose Internet Mail Extensions", RFC 2077, 525 DOI 10.17487/RFC2077, January 1997, 526 . 528 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 529 Requirement Levels", BCP 14, RFC 2119, 530 DOI 10.17487/RFC2119, March 1997, 531 . 533 [RFC2418] Bradner, S., "IETF Working Group Guidelines and 534 Procedures", BCP 25, RFC 2418, DOI 10.17487/RFC2418, 535 September 1998, . 537 [RFC2648] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, 538 DOI 10.17487/RFC2648, August 1999, 539 . 541 [RFC2954] Rehbehn, K. and D. Fowler, "Definitions of Managed Objects 542 for Frame Relay Service", RFC 2954, DOI 10.17487/RFC2954, 543 October 2000, . 545 [RFC2955] Rehbehn, K., Nicklass, O., and G. Mouradian, "Definitions 546 of Managed Objects for Monitoring and Controlling the 547 Frame Relay/ATM PVC Service Interworking Function", 548 RFC 2955, DOI 10.17487/RFC2955, October 2000, 549 . 551 [RFC3020] Pate, P., Lynch, B., and K. Rehbehn, "Definitions of 552 Managed Objects for Monitoring and Controlling the UNI/NNI 553 Multilink Frame Relay Function", RFC 3020, 554 DOI 10.17487/RFC3020, December 2000, 555 . 557 [RFC3083] Woundy, R., "Baseline Privacy Interface Management 558 Information Base for DOCSIS Compliant Cable Modems and 559 Cable Modem Termination Systems", RFC 3083, 560 DOI 10.17487/RFC3083, March 2001, 561 . 563 [RFC3201] Steinberger, R. and O. Nicklass, "Definitions of Managed 564 Objects for Circuit to Interface Translation", RFC 3201, 565 DOI 10.17487/RFC3201, January 2002, 566 . 568 [RFC3202] Steinberger, R. and O. Nicklass, "Definitions of Managed 569 Objects for Frame Relay Service Level Definitions", 570 RFC 3202, DOI 10.17487/RFC3202, January 2002, 571 . 573 [RFC3295] Sjostrand, H., Buerkle, J., and B. Srinivasan, 574 "Definitions of Managed Objects for the General Switch 575 Management Protocol (GSMP)", RFC 3295, 576 DOI 10.17487/RFC3295, June 2002, 577 . 579 [RFC3684] Ogier, R., Templin, F., and M. Lewis, "Topology 580 Dissemination Based on Reverse-Path Forwarding (TBRPF)", 581 RFC 3684, DOI 10.17487/RFC3684, February 2004, 582 . 584 [RFC3962] Raeburn, K., "Advanced Encryption Standard (AES) 585 Encryption for Kerberos 5", RFC 3962, 586 DOI 10.17487/RFC3962, February 2005, 587 . 589 [RFC3970] Kompella, K., "A Traffic Engineering (TE) MIB", RFC 3970, 590 DOI 10.17487/RFC3970, January 2005, 591 . 593 [RFC4036] Sawyer, W., "Management Information Base for Data Over 594 Cable Service Interface Specification (DOCSIS) Cable Modem 595 Termination Systems for Subscriber Management", RFC 4036, 596 DOI 10.17487/RFC4036, April 2005, 597 . 599 [RFC4131] Green, S., Ozawa, K., Cardona, E., Ed., and A. Katsnelson, 600 "Management Information Base for Data Over Cable Service 601 Interface Specification (DOCSIS) Cable Modems and Cable 602 Modem Termination Systems for Baseline Privacy Plus", 603 RFC 4131, DOI 10.17487/RFC4131, September 2005, 604 . 606 [RFC4251] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH) 607 Protocol Architecture", RFC 4251, DOI 10.17487/RFC4251, 608 January 2006, . 610 [RFC4323] Patrick, M. and W. Murwin, "Data Over Cable System 611 Interface Specification Quality of Service Management 612 Information Base (DOCSIS-QoS MIB)", RFC 4323, 613 DOI 10.17487/RFC4323, January 2006, 614 . 616 [RFC4546] Raftus, D. and E. Cardona, "Radio Frequency (RF) Interface 617 Management Information Base for Data over Cable Service 618 Interface Specifications (DOCSIS) 2.0 Compliant RF 619 Interfaces", RFC 4546, DOI 10.17487/RFC4546, June 2006, 620 . 622 [RFC4547] Ahmad, A. and G. Nakanishi, "Event Notification Management 623 Information Base for Data over Cable Service Interface 624 Specifications (DOCSIS)-Compliant Cable Modems and Cable 625 Modem Termination Systems", RFC 4547, 626 DOI 10.17487/RFC4547, June 2006, 627 . 629 [RFC4639] Woundy, R. and K. Marez, "Cable Device Management 630 Information Base for Data-Over-Cable Service Interface 631 Specification (DOCSIS) Compliant Cable Modems and Cable 632 Modem Termination Systems", RFC 4639, 633 DOI 10.17487/RFC4639, December 2006, 634 . 636 [RFC4682] Nechamkin, E. and J-F. Mule, "Multimedia Terminal Adapter 637 (MTA) Management Information Base for PacketCable- and 638 IPCablecom-Compliant Devices", RFC 4682, 639 DOI 10.17487/RFC4682, December 2006, 640 . 642 [RFC5098] Beacham, G., Kumar, S., and S. Channabasappa, "Signaling 643 MIB for PacketCable and IPCablecom Multimedia Terminal 644 Adapters (MTAs)", RFC 5098, DOI 10.17487/RFC5098, February 645 2008, . 647 [RFC5428] Channabasappa, S., De Ketelaere, W., and E. Nechamkin, 648 "Management Event Management Information Base (MIB) for 649 PacketCable- and IPCablecom-Compliant Devices", RFC 5428, 650 DOI 10.17487/RFC5428, April 2009, 651 . 653 [RFC6756] Trowbridge, S., Ed., Lear, E., Ed., Fishman, G., Ed., and 654 S. Bradner, Ed., "Internet Engineering Task Force and 655 International Telecommunication Union - Telecommunication 656 Standardization Sector Collaboration Guidelines", 657 RFC 6756, DOI 10.17487/RFC6756, September 2012, 658 . 660 [RFC7241] Dawkins, S., Thaler, P., Romascanu, D., and B. Aboba, Ed., 661 "The IEEE 802/IETF Relationship", RFC 7241, 662 DOI 10.17487/RFC7241, July 2014, 663 . 665 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 666 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 667 May 2017, . 669 6.2. Informative References 671 [FTP-RETIREMENT] 672 "Retirement of the IETF FTP Service", March 2021, 673 . 676 [FTP-RETIREMENT-PLAN] 677 "(Revised Plan) Retiring the IETF FTP Service", March 678 2021, . 681 Acknowledgments 683 Thank you to Robert Sparks, Glen Barney, Henrik Levkowetz and Russ 684 Housley on the IETF Tools Team for the operations and maintenance 685 information which informed the community discussion with resulted in 686 [FTP-RETIREMENT]. 688 Additionally, thank you to XXX for their contributions and valuable 689 feedback. 691 Author's Address 693 Roman Danyliw 694 Software Engineering Institute 696 EMail: rdd@cert.org