RFC 2266 (rfc2266) - Page 2 of 56

Definitions of Managed Objects for IEEE 802

Alternative Format: Original Text Document


RFC 2266                IEEE 802.12 Repeater MIB            January 1998


   2.7.  Mapping of IEEE 802.12 Managed Objects ...................    9
   3.  Definitions ................................................   12
   4.  Acknowledgements ...........................................   53
   5.  References .................................................   53
   6.  Security Considerations ....................................   54
   7.  Author's Address ...........................................   55
   8.  Full Copyright Statement ...................................   56

1.  The SNMP Network Management Framework

   The SNMP Network Management Framework consists of several components.
   For the purpose of this specification, the applicable components of
   the Framework are the SMI and related documents [2, 3, 4], which
   define the mechanisms used for describing and naming objects for the
   purpose of management.

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

1.1.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base (MIB).  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1) [1]
   defined in the SMI [2].  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.

2.  Overview

   Instances of these object types represent attributes of an IEEE
   802.12 repeater, as defined by Section 12, "RMAC Protocol" in IEEE
   Standard 802.12-1995 [6].

   The definitions presented here are based on Section 13, "Layer
   management functions and services", and Annex C, "GDMO Specifications
   for Demand Priority Managed Objects" of IEEE Standard 802.12-1995
   [6].

   Implementors of these MIB objects should note that the IEEE document
   explicitly describes (in the form of Pascal pseudocode) when, where,
   and how various repeater attributes are measured.  The IEEE document
   also describes the effects of repeater actions that may be invoked by
   manipulating instances of the MIB objects defined here.




Flick                       Standards Track

Web Standards & Support: