RFC 1512 (rfc1512) - Page 3 of 51

FDDI Management Information Base

RFC 1512                        FDDI MIB                  September 1993


   MIB-II [4] has the OBJECT IDENTIFIER value:

               fddimib    OBJECT IDENTIFIER ::= { fddi 73 }

   The definitions of the objects presented here draws heavily from
   related work in the ANSI X3T9.5 committee and the SMT subcommittee of
   that committee [8].  In fact, the definitions of the managed objects
   in this document are, to the maximum extent possible, identical to
   those identified by the ANSI committee.  The semantics of each
   managed object should be the same with syntactic changes made as
   necessary to recast the objects in terms of the Internet-standard SMI
   and MIB so as to be compatible with the SNMP.  Examples of these
   syntactic changes include remapping booleans to enumerated integers,
   remapping bit strings to octet strings, and the like.  In addition,
   the naming of the objects was changed to achieve compatibility.

   These minimal syntactic changes with no semantic changes should allow
   implementations of SNMP manageable FDDI systems to share
   instrumentation with other network management schemes and thereby
   minimize implementation cost.  In addition, the translation of
   information conveyed by managed objects from one network management
   scheme to another is eased by these shared definitions.

   Only the essential variables, as indicated by their mandatory status
   in the ANSI specification, were retained in this document.  The
   importance of variables which have an optional status in the ANSI
   specification were perceived as being less widely accepted.

2.1.  Textual Conventions

   Several new datatypes are introduced as a textual convention in this
   MIB document.  These textual conventions enhance the readability of
   the document and ease comparisons with its ANSI counterpart.  It
   should be noted that the introduction of these textual conventions
   has no effect on either the syntax or the semantics of any managed
   objects.  The use of these is merely an artifact of the explanatory
   method used.  Objects defined in terms of one of these methods are
   always encoded by means of the rules that define the primitive type.
   Hence, no changes to the SMI or the SNMP are necessary to accommodate
   these textual conventions which are adopted merely for the
   convenience of readers and writers in pursuit of the elusive goal of
   clear, concise, and unambiguous MIB documents.

3.  Changes from RFC 1285

   The changes from RFC 1285 [2] to this document, based on changes from
   ANSI SMT 6.2 to SMT 7.3, were so numerous that the objects in this
   MIB module are located on a different branch of the MIB tree.  No



Case & Rijsinghani