Network Working Group J. Flick
Request for Comments: 3638 Hewlett-Packard Company
Obsoletes: 1643 C. Heard
Category: Informational Consultant
September 2003
Applicability Statement for Reclassification of RFC 1643 to Historic Status
1. Details
STD 50, RFC 1643 [RFC1643], "Definitions of Managed Objects for the Ethernet-like Interface Types", and its SMIv2 equivalent, RFC 1650 [RFC1650], are applicable to half-duplex 10 Mb/s Ethernet interfaces only. Subsequent to the 1994 publication of these documents, 100 Mb/s, 1000 Mb/s, and 10 Gb/s Ethernet interface types have been developed, and full-duplex operation at 10 Mb/s has been standardized. Updates to RFC 1650 have been produced to accommodate these new technologies [RFC2358] [RFC2665] [RFC2666] [RFC3635]. These updates define new MIB objects to supplement those defined in RFC 1643 and RFC 1650 and in addition deprecate some of the objects in 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] [RFC3636] as well. RFC 1643 is an obsolete specification, overtaken by events. Its SMIv2 equivalent, RFC 1650, was officially retired in 1998. New implementations -- even those that support only half-duplex 10 Mb/s interfaces -- should comply with in the latest version of the specification, currently RFC 3635 [RFC3635] and RFC 2666 [RFC2666], instead of RFC 1643. It is therefore recommended that RFC 1643 be reclassified as an Historic document.
Flick & Heard Informational [Page 1]
RFC 3638 RFC 1643 to Historic Status September 2003 2. Effect on Other Standards Track DocumentsReclassification 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:
Document Title
-------- -----
RFC 2020 IEEE 802.12 Interface MIB
Flick & Heard Informational [Page 2]
RFC 3638 RFC 1643 to Historic Status September 2003 3. Security ConsiderationsReclassification 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
Flick & Heard Informational [Page 3]
RFC 3638 RFC 1643 to Historic Status September 2003
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3
5. Authors' Addresses
John Flick Hewlett-Packard Company 8000 Foothills Blvd. M/S 5557 Roseville, CA 95747-5557 USA
Flick & Heard Informational [Page 4]
RFC 3638 RFC 1643 to Historic Status September 2003 6. Full Copyright StatementCopyright (C) The Internet Society (2003). All Rights Reserved.