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

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/