Ethernet Interfaces and Hub MIB Working Group John Flick INTERNET DRAFT Hewlett-Packard Company C. M. Heard Consultant
MayAugust 2002 Request to MoveApplicability Statement for Reclassification of RFC 1643 to Historic Status <draft-ietf-hubmib-1643-to-historic-00.txt><draft-ietf-hubmib-1643-to-historic-01.txt> Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright Notice Copyright (C) The Internet Society (2002). All Rights Reserved. Abstract RFC 1643, "Definitions of Managed Objects for the Ethernet-like Interface Types", currently STD 50, is inadequate for managing the Ethernet interface types that have been developed since 1994. The most up-to-date version of that specification, RFC xxxx, is currently a Proposed Standard. In order to encourage implementors to use that version of the specification instead of RFC 1643, this document requestsThis memo recommends that RFC 1643 be moved toreclassified as an Historic status.document and provides the supporting motivation for that recommendation. 1. Details STD 50, RFC 1643 [RFC1643], "Definitions of Managed Objects for the Ethernet-like Interface Types", covers onlyand its SMIv2 equivalent, RFC 1650 [RFC1650], are applicable to half-duplex 10 Mb/s Ethernet interfaces. Since itsinterfaces only. Subsequent to the 1994 publication in 1994,of these documents, 100 Mb/s, 1000 Mb/s, and 10 Gb/s Ethernet interface types have been developed, and updatesfull-duplex operation at 10 Mb/s has been standardized. Updates to the specificationRFC 1650 have been developedproduced to encompassaccomodate these new technologies [RFC2358] [RFC2665] [RFC2666] [RFCxxxx]. These updates define new MIB objects to supplement those originallydefined in RFC 1643 and RFC 1650 and in addition deprecate some of the objects definedin RFC 1643 and RFC 1650 that are no longer considered useful. They also levy a requirement for implementations of the EtherLike-MIB to support the MAU-MIB [RFC2239] [RFC2668] [RFCyyyy] as well. RFC 1643 is an obsolete specification, overtaken by events. Having it remain an Internet Standard while the replacement RFCs make their way through the standards track serves no useful purpose and mayIts SMIv2 equivalent, RFC 1650, was officially retired in 1998. New implementations -- even havethose that support only half-duplex 10 Mb/s interfaces -- should comply with in the undesirable effectlatest version of encouraging vendors to implement itthe specification, currently RFC xxxx [RFCxxxx] and RFC 2666 [RFC2666], instead of its more up-to-date replacements.RFC 1643. It is therefore recommended that itRFC 1643 be reclassified as Historic.an Historic document. 2. Effect on Other Standards Track Documents Reclassification of RFC 1643 will have no impact on the status of any standards track RFC because no standards track RFC cites it as a normative reference. An RFC content search made with the tools available at http://www.rfc-editor.org reveals the following standards track documents that cite RFC 1643: RFC 2020 IEEE 802.12 Interface MIB J. Flick RFC 2358 Definitions of Managed Objects for the Ethernet-like Interface Types J. Flick, J. Johnson RFC 2665 Definitions of Managed Objects for the Ethernet-like Interface Types J. Flick, J. Johnson RFC 2720 Traffic Flow Measurement: Meter MIB N. Brownlee RFC xxxx Definitions of Managed Objects for the Ethernet-like Interface Types J. Flick RFC 2020 [RFC2020] contains DOT12-IF-MIB, which is the MIB module for managing IEEE 802.12 100VG-AnyLAN interfaces. It refers to RFC 1643 in the context of an admonition not to implement the EthernetLike-MIBEtherLike-MIB for any interface where the DOT12-IF-MIB is implemented. RFC 2358 [RFC2358], RFC 2665 [RFC2665], and RFC xxxx [RFCxxxx] all contain updated versions of the EthernetLike-MIB.EtherLike-MIB. They refer to RFC 1643 in the context of explaining the history of the EthernetLike- MIB,EtherLike-MIB, and the citation in [RFCxxxx]RFC xxxx is explicitly listed as a non- normativenon-normative reference. RFC 2720 [RFC2720] contains the FLOW-METER-MIB. It refers to RFC 1643 only in an ASN.1 comment in the MIB module. Omission of that comment would not preclude correct implementation of the MIB module. Clearly, none of these citations is normative. 3. Security Considerations Reclassification of RFC 1643 will not, in and of itself, have any effect on the security of the Internet. 4. Normative References [RFC1643] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types", STD 50, RFC 1643, July 1994. [RFC1650] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2", RFC 1650, August 1994. [RFC2020] Flick, J., "IEEE 802.12 Interface MIB", RFC 2020, October 1996. [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and S. Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", RFC 2239, November 1997. [RFC2358] Flick, J. and J. Johnson, "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 2358, June 1998. [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 2665, August 1999. [RFC2666] Flick, J., "Definitions of Object Identifiers for Identifying Ethernet Chip Sets ", RFC 2666, August 1999. [RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and S. Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)", RFC 2668, August 1999. [RFC2720] Brownlee, N., "Traffic Flow Measurement: Meter MIB", RFC 2720, October 1999. [RFCxxxx] Flick, J., "Definitions of Managed Objects for the Ethernet- like Interface Types", <draft-ietf-hubmib-etherif-mib- v3-00.txt>,v3-02.txt>, work in progress. [RFCyyyy] Flick, J., "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)", <draft-ietf-hubmib-mau-mib- v3-02.txt>, work in progress. 5. Authors' Addresses John Flick Hewlett-Packard Company 8000 Foothills Blvd. M/S 5557 Roseville, CA 95747-5557 USA Phone: +1 916 785 4018 Fax: +1 916 785 1199 EMail: firstname.lastname@example.org C. M. Heard 600 Rainbow Dr. #141 Mountain View, CA 94041-2542 USA Phone: +1 650 964 8391 EMail: email@example.com Full Copyright Statement Copyright (C) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.