RFC 1748 (rfc1748) - Page 2 of 25

IEEE 802

RFC 1748               IEEE 802.5 MIB using SMIv2          December 1994


2.  The SNMPv2 Network Management Framework

   The SNMPv2 Network Management Framework consists of four major
   components.  They are:

      o    RFC 1442 [1] which defines the SMI, the mechanisms used for
           describing and naming objects for the purpose of management.

      o    STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
           objects for the Internet suite of protocols.

      o    RFC 1445 [3] which defines the administrative and other
           architectural aspects of the framework.

      o    RFC 1448 [4] which defines the protocol used for network
           access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

2.1.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object type is named by an
   OBJECT IDENTIFIER, an administratively assigned name.  The object
   type together with an object instance serves to uniquely identify a
   specific instantiation of the object.  For human convenience, we
   often use a textual string, termed the descriptor, to refer to the
   object type.

3.  Overview

   This memo defines three tables: the 802.5 Interface Table, which
   contains state and parameter information which is specific to 802.5
   interfaces, the 802.5 Statistics Table, which contains 802.5
   interface statistics, and the 802.5 Timer Table, which contains the
   values of 802.5-defined timers. A managed system will have one entry
   in the 802.5 Interface Table and one entry in the 802.5 Statistics
   Table for each of its 802.5 interfaces.  The 802.5 Timer Table is
   obsolete, but its definition has been retained in this memo for
   backward compatibility.

   This memo also defines OBJECT IDENTIFIERs, some to identify interface
   tests for use with the ifTestTable [6], and some to identify Token
   Ring interface Chip Sets.




McCloghrie & Decker