idnits 2.17.1 draft-ietf-hubmib-1643-to-historic-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (May 2002) is 8011 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) ** Obsolete normative reference: RFC 1643 (Obsoleted by RFC 3638) ** Obsolete normative reference: RFC 2358 (Obsoleted by RFC 2665) ** Obsolete normative reference: RFC 2665 (Obsoleted by RFC 3635) -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCxxxx' Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Ethernet Interfaces and Hub MIB Working Group John Flick 3 INTERNET DRAFT Hewlett-Packard Company 4 C. M. Heard 5 Consultant 6 May 2002 8 Request to Move RFC 1643 to Historic Status 10 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. Internet-Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its areas, 17 and its working groups. Note that other groups may also distribute 18 working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html 31 Copyright Notice 33 Copyright (C) The Internet Society (2002). All Rights Reserved. 35 Abstract 37 RFC 1643, "Definitions of Managed Objects for the Ethernet-like 38 Interface Types", currently STD 50, is inadequate for managing the 39 Ethernet interface types that have been developed since 1994. The 40 most up-to-date version of that specification, RFC xxxx, is currently 41 a Proposed Standard. In order to encourage implementors to use that 42 version of the specification instead of RFC 1643, this document 43 requests that RFC 1643 be moved to Historic status. 45 1. Details 47 STD 50, RFC 1643 [RFC1643], "Definitions of Managed Objects for the 48 Ethernet-like Interface Types", covers only 10 Mb/s Ethernet 49 interfaces. Since its publication in 1994, 100 Mb/s, 1000 Mb/s, and 50 10 Gb/s Ethernet interface types have been developed, and updates to 51 the specification have been developed to encompass these new 52 technologies [RFC2358] [RFC2665] [RFCxxxx]. These updates define new 53 MIB objects to supplement those originally defined in RFC 1643 and in 54 addition deprecate some of the objects defined in RFC 1643 that are 55 no longer useful. 57 RFC 1643 is an obsolete specification, overtaken by events. Having 58 it remain an Internet Standard while the replacement RFCs make their 59 way through the standards track serves no useful purpose and may even 60 have the undesirable effect of encouraging vendors to implement it 61 instead of its more up-to-date replacements. It is therefore 62 recommended that it be reclassified as Historic. 64 2. Effect on Other Standards Track Documents 66 Reclassification of RFC 1643 will have no impact on the status of any 67 standards track RFC because no standards track RFC cites it as a 68 normative reference. An RFC content search made with the tools 69 available at http://www.rfc-editor.org reveals the following 70 standards track documents that cite RFC 1643: 72 RFC 2020 IEEE 802.12 Interface MIB J. Flick 74 RFC 2358 Definitions of Managed Objects for the Ethernet-like 75 Interface Types J. Flick, J. Johnson 77 RFC 2665 Definitions of Managed Objects for the Ethernet-like 78 Interface Types J. Flick, J. Johnson 80 RFC 2720 Traffic Flow Measurement: Meter MIB N. Brownlee 82 RFC xxxx Definitions of Managed Objects for the Ethernet-like 83 Interface Types J. Flick 85 RFC 2020 [RFC2020] contains DOT12-IF-MIB, which is the MIB module for 86 managing IEEE 802.12 100VG-AnyLAN interfaces. It refers to RFC 1643 87 in the context of an admonition not to implement the EthernetLike-MIB 88 for any interface where the DOT12-IF-MIB is implemented. 90 RFC 2358 [RFC2358], RFC 2665 [RFC2665], and RFC xxxx [RFCxxxx] all 91 contain updated versions of the EthernetLike-MIB. They refer to RFC 92 1643 in the context of explaining the history of the EthernetLike- 93 MIB, and the citation in [RFCxxxx] is explicitly listed as a non- 94 normative reference. 96 RFC 2720 [RFC2720] contains the FLOW-METER-MIB. It refers to RFC 97 1643 only in an ASN.1 comment in the MIB module. Omission of that 98 comment would not preclude correct implementation of the MIB module. 100 Clearly, none of these citations is normative. 102 3. Security Considerations 104 Reclassification of RFC 1643 will not, in and of itself, have any 105 effect on the security of the Internet. 107 4. References 109 [RFC1643] Kastenholz, F., "Definitions of Managed Objects for the 110 Ethernet-like Interface Types", STD 50, RFC 1643, July 1994. 112 [RFC2020] Flick, J., "IEEE 802.12 Interface MIB", RFC 2020, October 113 1996. 115 [RFC2358] Flick, J. and J. Johnson, "Definitions of Managed Objects 116 for the Ethernet-like Interface Types", RFC 2358, June 1998. 118 [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed Objects 119 for the Ethernet-like Interface Types", RFC 2665, August 120 1999. 122 [RFC2720] Brownlee, N., "Traffic Flow Measurement: Meter MIB", RFC 123 2720, October 1999. 125 [RFCxxxx] Flick, J., "Definitions of Managed Objects for the Ethernet- 126 like Interface Types", , work in progress. 129 5. Authors' Addresses 131 John Flick 132 Hewlett-Packard Company 133 8000 Foothills Blvd. M/S 5557 134 Roseville, CA 95747-5557 135 USA 137 Phone: +1 916 785 4018 138 Fax: +1 916 785 1199 139 EMail: johnf@rose.hp.com 141 C. M. Heard 142 600 Rainbow Dr. #141 143 Mountain View, CA 94041-2542 144 USA 146 Phone: +1 650 964 8391 147 EMail: heard@pobox.com 149 Full Copyright Statement 151 Copyright (C) The Internet Society (2002). All Rights Reserved. 153 This document and translations of it may be copied and furnished to 154 others, and derivative works that comment on or otherwise explain it 155 or assist in its implementation may be prepared, copied, published 156 and distributed, in whole or in part, without restriction of any 157 kind, provided that the above copyright notice and this paragraph are 158 included on all such copies and derivative works. However, this 159 document itself may not be modified in any way, such as by removing 160 the copyright notice or references to the Internet Society or other 161 Internet organizations, except as needed for the purpose of 162 developing Internet standards in which case the procedures for 163 copyrights defined in the Internet Standards process must be 164 followed, or as required to translate it into languages other than 165 English. 167 The limited permissions granted above are perpetual and will not be 168 revoked by the Internet Society or its successors or assigns. 170 This document and the information contained herein is provided on an 171 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 172 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 173 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 174 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 175 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 177 Acknowledgement 179 Funding for the RFC Editor function is currently provided by the 180 Internet Society.