Definitions of Object Identifiers for Identifying Ethernet Chip Sets
RFC 2666

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 02

Network Working Group                                           J. Flick
Request for Comments: 2666                       Hewlett-Packard Company
Category: Informational                                      August 1999

                 Definitions of Object Identifiers for
                     Identifying Ethernet Chip Sets

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

Abstract

   This memo defines OBJECT IDENTIFIER values for use with network
   management protocols in the Internet community.  In particular, it
   contains registered OID values for use with the dot3StatsEtherChipSet
   object in the EtherLike-MIB [16].  These registrations have been
   split from [16] into a separate document for maintenance purposes.

Table of Contents

   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.  Introduction

   This memo defines OBJECT IDENTIFIER values for use with network
   management protocols in the Internet community.  In particular, it
   contains registered OID values for use with the dot3StatsEtherChipSet
   object in the EtherLike-MIB [16].  These registrations have been
   split from [16] into a separate document for maintenance purposes.

   The dot3StatsEtherChipSet object has recently been deprecated.  The
   purpose of this document is to capture historic assignments made by
   the various IETF working groups that have been responsible for
   maintaining the EtherLike-MIB.  Implementations which support the
   dot3StatsEtherChipSet object for backwards compatability may continue
   to use the OBJECT IDENTIFIER values assigned in this document.

   For those chipsets not represented in this document, implementors
   should assign OBJECT IDENTIFIER values within that part of the
   registration tree delegated to individual enterprises.

2.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o  An overall architecture, described in RFC 2571 [1].

   o  Mechanisms for describing and naming objects and events for the
      purpose of management. The first version of this Structure of
      Management Information (SMI) is called SMIv1 and described in STD
      16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
      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. The
      first version of the SNMP message protocol is called SNMPv1 and
      described in STD 15, RFC 1157 [8]. A second version of the SNMP
      message protocol, which is not an Internet standards track
      protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
      1906 [10].  The third version of the message protocol is called
      SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
      [12].

   o  Protocol operations for accessing management information. The
      first set of protocol operations and associated PDU formats is
      described in STD 15, RFC 1157 [8]. A second set of protocol
      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] and
      the view-based access control mechanism described in RFC 2575
      [15].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2. A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations. The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64). Some machine readable
   information in SMIv2 will be converted into textual descriptions in