As per Relevance of the word ethernet, we have this rfc below:
Network Working Group J.
Request for Comments: 2666 Hewlett-Packard
Category: Informational August 1999
Definitions of Object Identifiers
Identifying Ethernet Chip
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This memo defines OBJECT IDENTIFIER values for use with
management protocols in the Internet community. In particular,
contains registered OID values for use with the dot3
object in the EtherLike-MIB [16]. These registrations have
split from [16] into a separate document for maintenance purposes
Table of
1. Introduction ............................................... 2
2. The SNMP Management Framework .............................. 2
3. Definitions ................................................ 3
4. Intellectual Property ...................................... 14
5. Acknowledgements ........................................... 15
6. References ................................................. 15
7. Security Considerations .................................... 16
8. Author's Address ........................................... 17
9. Full Copyright Statement ................................... 18
Flick Informational [Page 1]
RFC 2666 Ethernet Chipset MIB August 1999
1.
This memo defines OBJECT IDENTIFIER values for use with
management protocols in the Internet community. In particular,
contains registered OID values for use with the dot3
object in the EtherLike-MIB [16]. These registrations have
split from [16] into a separate document for maintenance purposes
The dot3StatsEtherChipSet object has recently been deprecated.
purpose of this document is to capture historic assignments made
the various IETF working groups that have been responsible
maintaining the EtherLike-MIB. Implementations which support
dot3StatsEtherChipSet object for backwards compatability may
to use the OBJECT IDENTIFIER values assigned in this document
For those chipsets not represented in this document,
should assign OBJECT IDENTIFIER values within that part of
registration tree delegated to individual enterprises
2. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described in
16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
second version, called SMIv2, is described in STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9] and
1906 [10]. The third version of the message protocol is
SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
Flick Informational [Page 2]
RFC 2666 Ethernet Chipset MIB August 1999
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
3.
ETHER-CHIPSET-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2
FROM SNMPv2-
dot
FROM EtherLike-MIB
etherChipsetMIB MODULE-
LAST-UPDATED "9908240400Z" -- August 24, 199
ORGANIZATION "IETF 802.3 Hub MIB Working Group
CONTACT-
"WG E-mail: hubmib@hprnd.rose.hp.
To subscribe: hubmib-request@hprnd.rose.hp.
Chair: Dan
Postal: Lucent
Atidum Technology Park, Bldg. 3
Tel Aviv 61131
Tel: +972 3 645 8414
E-mail: dromasca@lucent.
Editor: John
Postal: Hewlett-Packard
8000 Foothills Blvd. M/S 5556
Roseville, CA 95747-5556
Flick Informational [Page 3]
RFC 2666 Ethernet Chipset MIB August 1999
Tel: +1 916 785 4018
Fax: +1 916 785 3583
E-mail: johnf@rose.hp.com
DESCRIPTION "This MIB module contains registered values
use by the dot3StatsEtherChipSet object
the EtherLike-MIB. This object is used
identify the MAC hardware used to
on an interface
Note that the dot3StatsEtherChipSet
has been deprecated. The primary purpose
this module is to capture historic
made by the various IETF working groups
have been responsible for maintaining
EtherLike-MIB. Implementations which
the dot3StatsEtherChipSet object for
compatability may continue to use these values
For those chipsets not represented in
module, registration is required in
documentation, e.g., assignment within
part of the registration tree delegated
individual enterprises (see RFC 1155 and
1902)."
REVISION "9908240400Z" -- August 24, 1999
DESCRIPTION "Initial version of this module created
splitting the chipset registration
out from the EtherLike-MIB
Version published as RFC 2666."
::= { mib-2 70 }
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD7990 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am7990 Local Area
Controller for Ethernet (LANCE)."
::= { dot3ChipSetAMD 1 }
dot3ChipSetAMD79900 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79900 chip."
::= { dot3ChipSetAMD 2 }
Flick Informational [Page 4]
RFC 2666 Ethernet Chipset MIB August 1999
dot3ChipSetAMD79C940 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C940 Media Access
for Ethernet (MACE)."
::= { dot3ChipSetAMD 3 }
dot3ChipSetAMD79C90 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C90 CMOS Local Area
Controller for Ethernet (C-LANCE)."
::= { dot3ChipSetAMD 4 }
dot3ChipSetAMD79C960 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C960 PCnet-ISA Single
Ethernet Controller for ISA."
::= { dot3ChipSetAMD 5 }
dot3ChipSetAMD79C961 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C961 PCnet-ISA+ Single
Plug & Play Full-Duplex Ethernet
for ISA."
::= { dot3ChipSetAMD 6 }
dot3ChipSetAMD79C961A OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C961A PCnet-ISA II Single
Plug & Play Full-Duplex Ethernet
for ISA."
::= { dot3ChipSetAMD 7 }
dot3ChipSetAMD79C965 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C965 PCnet-32 Single
Ethernet Controller for PCI."
::= { dot3ChipSetAMD 8 }
dot3ChipSetAMD79C970 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C970 PCnet PCI Single
Flick Informational [Page 5]
RFC 2666 Ethernet Chipset MIB August 1999
Ethernet Controller for PCI Local Bus."
::= { dot3ChipSetAMD 9 }
dot3ChipSetAMD79C970A OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices AM79C970A PCnet PCI II Single
Full-Duplex Ethernet Controller for PCI
Bus."
::= { dot3ChipSetAMD 10 }
dot3ChipSetAMD79C971 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C971 PCnet-FAST Single
Full-Duplex 10/100 Mbps Ethernet Controller
PCI Local Bus."
::= { dot3ChipSetAMD 11 }
dot3ChipSetAMD79C972 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C972 PCnet-FAST+
10/100 Mbps PCI Ethernet Controller with
Support."
::= { dot3ChipSetAMD 12 }
dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
dot3ChipSetIntel82586 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82586 IEEE 802.3 Ethernet LAN Coprocessor."
::= { dot3ChipSetIntel 1 }
dot3ChipSetIntel82596 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82596 High-Performance 32-Bit Local Area
Coprocessor."
::= { dot3ChipSetIntel 2 }
dot3ChipSetIntel82595 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82595 High Integration Ethernet Controller."
::= { dot3ChipSetIntel 3 }
Flick Informational [Page 6]
RFC 2666 Ethernet Chipset MIB August 1999
dot3ChipSetIntel82557 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82557 Fast Ethernet PCI Bus Lan Controller."
::= { dot3ChipSetIntel 4 }
dot3ChipSetIntel82558 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82558 Fast Ethernet PCI Bus LAN Controller
Integrated PHY."
::= { dot3ChipSetIntel 5 }
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq8003 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
8003 chip set."
::= { dot3ChipSetSeeq 1 }
dot3ChipSetSeeq80C03 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
80C03 Full-Duplex CMOS Ethernet Data
Controller (MAC)."
::= { dot3ChipSetSeeq 2 }
dot3ChipSetSeeq84C30 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 84C30 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 3 }
dot3ChipSetSeeq8431 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 8431 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 4 }
dot3ChipSetSeeq80C300 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
80C300 Full-Duplex CMOS Ethernet 10/100
Mbit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 5 }
Flick Informational [Page 7]
RFC 2666 Ethernet Chipset MIB August 1999
dot3ChipSetSeeq84C300 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 84C300 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 6 }
dot3ChipSetSeeq84301 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 84301 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 7 }
dot3ChipSetSeeq84302 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 84302 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 8 }
dot3ChipSetSeeq8100 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
8100 Gigabit Ethernet Controller (MAC & PCS)."
::= { dot3ChipSetSeeq 9 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational8390 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP8390 Network
Controller."
::= { dot3ChipSetNational 1 }
dot3ChipSetNationalSonic OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83932 Systems-Oriented
Interface Controller (SONIC)."
::= { dot3ChipSetNational 2 }
dot3ChipSetNational83901 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83901 Serial Network
Controller (SNIC)."
::= { dot3ChipSetNational 3 }
dot3ChipSetNational83902 OBJECT-
Flick Informational [Page 8]
RFC 2666 Ethernet Chipset MIB August 1999
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83902 Serial Network
Controller for Twisted Pair (ST-NIC)."
::= { dot3ChipSetNational 4 }
dot3ChipSetNational83905 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83905 AT Local Area
Twisted-Pair Interface (AT/LANTIC)."
::= { dot3ChipSetNational 5 }
dot3ChipSetNational83907 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83907 AT Twisted-Pair
Coaxial Network Interface
(AT/LANTIC II)."
::= { dot3ChipSetNational 6 }
dot3ChipSetNational83916 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83916 Systems-Oriented
Interface Controller (SONIC-16)."
::= { dot3ChipSetNational 7 }
dot3ChipSetNational83934 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83934 Systems-Oriented
Interface Controller with Twisted Pair
(SONIC-T)."
::= { dot3ChipSetNational 8 }
dot3ChipSetNational83936 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83936AVUL Full-Duplex Systems
Oriented Network Interface Controller
Twisted Pair Interface (SONIC-T)."
::= { dot3ChipSetNational 9 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu86950 OBJECT-
STATUS
Flick Informational [Page 9]
RFC 2666 Ethernet Chipset MIB August 1999
DESCRIPTION "The authoritative identifier for the
86950 chip."
::= { dot3ChipSetFujitsu 1 }
dot3ChipSetFujitsu86960 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
MB86960 Network Interface Controller
Encoder/Decoder (NICE)."
::= { dot3ChipSetFujitsu 2 }
dot3ChipSetFujitsu86964 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
MB86964 Ethernet Controller with 10BASE-
Tranceiver."
::= { dot3ChipSetFujitsu 3 }
dot3ChipSetFujitsu86965A OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
MB86965A EtherCoupler Single-Chip
Controller."
::= { dot3ChipSetFujitsu 4 }
dot3ChipSetFujitsu86965B OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
MB86965B EtherCoupler Single-Chip
Controller (supports full-duplex)."
::= { dot3ChipSetFujitsu 5 }
dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
dot3ChipSetDigitalDC21040 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DC21040 chip."
::= { dot3ChipSetDigital 1 }
dot3ChipSetDigital21041 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21041 PCI Ethernet
Controller."
::= { dot3ChipSetDigital 2 }
dot3ChipSetDigital21140 OBJECT-
Flick Informational [Page 10]
RFC 2666 Ethernet Chipset MIB August 1999
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21140 PCI Fast Ethernet
Controller."
::= { dot3ChipSetDigital 3 }
dot3ChipSetDigital21143 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21143 PCI/CardBus 10/100-Mb/
Ethernet LAN Controller."
::= { dot3ChipSetDigital 4 }
dot3ChipSetDigital21340 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21340 10/100-MB/s managed
port switch."
::= { dot3ChipSetDigital 5 }
dot3ChipSetDigital21440 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21440 Multiport 10/100
Ethernet Controller."
::= { dot3ChipSetDigital 6 }
dot3ChipSetDigital21540 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21540 PCI/CardBus Ethernet
Controller with Modem Interface."
::= { dot3ChipSetDigital 7 }
dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 }
dot3ChipSetTIE100 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETE100 ThunderLAN PCI
Ethernet Controller."
::= { dot3ChipSetTI 1 }
dot3ChipSetTIE110 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETE110 ThunderLAN PCI 10BASE-
Ethernet Adapter."
Flick Informational [Page 11]
RFC 2666 Ethernet Chipset MIB August 1999
::= { dot3ChipSetTI 2 }
dot3ChipSetTIX3100 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETX3100 Desktop
8/2."
::= { dot3ChipSetTI 3 }
dot3ChipSetTIX3150 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETX3150 ThunderSWITCH 12/3."
::= { dot3ChipSetTI 4 }
dot3ChipSetTIX3270 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETX3270 ThunderSWITCH 24/3."
::= { dot3ChipSetTI 5 }
dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 }
dot3ChipSetToshibaTC35815F OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
TC35815F PCI-Based 100/10Mbps
Controller."
::= { dot3ChipSetToshiba 1 }
dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 }
dot3ChipSetLucentATT1MX10 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technologies ATT1MX10 (Spinnaker) Quad MAC
Tranceiver for Ethernet Frame Switching."
::= { dot3ChipSetLucent 1 }
dot3ChipSetLucentLUC3M08 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technologies LUC3M08 Eight Ethernet MACs
10/100 Mbits/s Frame Switching."
::= { dot3ChipSetLucent 2 }
dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 }
Flick Informational [Page 12]
RFC 2666 Ethernet Chipset MIB August 1999
dot3ChipSetGalileoGT48001 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48001A Switched
Controller."
::= { dot3ChipSetGalileo 1 }
dot3ChipSetGalileoGT48002 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48002A Switched Fast
Controller."
::= { dot3ChipSetGalileo 2 }
dot3ChipSetGalileoGT48004 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48004A Four Port Fast
Switch for Multiport 10/100BASE-X Systems."
::= { dot3ChipSetGalileo 3 }
dot3ChipSetGalileoGT48207 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48207 Low-Cost 10 Port
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 4 }
dot3ChipSetGalileoGT48208 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48208 Advanced 10 Port
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 5 }
dot3ChipSetGalileoGT48212 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48212 Advanced 14 Port
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 6 }
dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 }
dot3ChipSetJatoJT1001 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technologies JT1001 GigEMAC
Flick Informational [Page 13]
RFC 2666 Ethernet Chipset MIB August 1999
10/100/1000Mbps Ethernet Controller with
interface."
::= { dot3ChipSetJato 1 }
dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 }
dot3ChipSetXaQtiXQ11800FP OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
XQ11800FP XMAC II Gigabit Ethernet Media
Controller."
::= { dot3ChipSetXaQti 1 }
dot3ChipSetXaQtiXQ18110FP OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
XQ18110FP GigaPower Protocol Accelerator."
::= { dot3ChipSetXaQti 2 }
4. Intellectual
The IETF takes no position regarding the validity or scope of
intellectual property or other rights that might be claimed
pertain to the implementation or use of the technology described
this document or the extent to which any license under such
might or might not be available; neither does it represent that
has made any effort to identify any such rights. Information on
IETF's procedures with respect to rights in standards-track
standards-related documentation can be found in BCP-11. Copies
claims of rights made available for publication and any assurances
licenses to be made available, or the result of an attempt made
obtain a general license or permission for the use of
proprietary rights by implementors or users of this specification
be obtained from the IETF Secretariat
The IETF invites any interested party to bring to its attention
copyrights, patents or patent applications, or other
rights which may cover technology that may be required to
this standard. Please address the information to the IETF
Director
Flick Informational [Page 14]
RFC 2666 Ethernet Chipset MIB August 1999
5.
This document was produced by the Ethernet Interfaces and Hub
Working Group
6.
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
Describing SNMP Management Frameworks", RFC 2571, May 1999.
[2] Rose, M. and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based Internets", STD 16,
1155, May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[4] M. Rose, "A Convention for Defining Traps for use with
SNMP", RFC 1215, March 1991
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S Waldbusser, "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S Waldbusser, "Conformance Statements for SMIv2", STD 58,
RFC 2580, STD 58, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser
"Introduction to Community-based SNMPv2", RFC 1901,
1996.
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Mappings for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "
Processing and Dispatching for the Simple Network
Protocol (SNMP)", RFC 2572, May 1999.
Flick Informational [Page 15]
RFC 2666 Ethernet Chipset MIB August 1999
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM
for version 3 of the Simple Network Management
(SNMPv3)", RFC 2574, May 1999.
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Operations for Version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications",
2573, May 1999.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management
(SNMP)", RFC 2575, May 1999.
[16] Flick, J. and J. Johnson, "Definitions of Managed Objects
the Ethernet-like Interface Types", RFC 2665, August 1999.
7. Security
There are no management objects actually defined in this MIB module
It merely contains a list of OBJECT IDENTIFIER values for use
other MIB modules. As such, it does not, by itself, have any
on the security of the Internet
The values in this module are expected to be used only for
compatability with the deprecated dot3StatsEtherChipSet object in
EtherLike-MIB [16]. That object may be considered sensitive in
environments, since it would allow an intruder to obtain
about which vendor's equipment is in use on the network
Therefore, it may be important in some environments, where
dot3StatsEtherChipSet object is implemented for
compatability, to control read access to that object and possibly
even encrypt the values of that object when sending it over
network via SNMP. Not all versions of SNMP provide features for
a secure environment
SNMPv1 by itself is such an insecure environment. Even if
network itself is secure (for example by using IPSec), even then
there is no control as to who on the secure network is allowed
access and GET (read) the objects in this MIB
It is recommended that the implementors consider the
features as provided by the SNMPv3 framework. Specifically, the
of the User-based Security Model RFC 2574 [12] and the View-
Access Control Model RFC 2575 [15] is recommended
Flick Informational [Page 16]
RFC 2666 Ethernet Chipset MIB August 1999
It is then a customer/user responsibility to ensure that the
entity giving access to a managed object whose values are defined
this MIB, is properly configured to give access to those objects
to those principals (users) that have legitimate rights to
them
8. Author's
John
Hewlett-Packard
8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557
Phone: +1 916 785 4018
EMail: johnf@rose.hp.
Flick Informational [Page 17]
RFC 2666 Ethernet Chipset MIB August 1999
9. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Flick Informational [Page 18]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
