RFC 1559 (rfc1559) - Page 3 of 69

DECnet Phase IV MIB Extensions

RFC 1559                  DECnet Phase IV MIB              December 1993


   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.  Selected Objects

   The objects included in this memo have been created from the DIGITAL
   Network Architecture Network Management Functional Specification
   Version 4.0.0, dated July 1983. An attempt has been made to provide a
   reasonable ordering of these variables into groups. These groups are:

        System Group
        Network Management Group
        Session Group
        End Group
        Routing Group
        Circuit Group
        DDCMP Group
        DDCMP Multipoint Control Group
        Ethernet Group
        Counters Group
        Adjacency Group
        Line Group
        Non Broadcast Line Group
        Area Group

   An effort has also been made to preserve the original syntax of each
   object wherever possible, for example, a DECnet Phase IV object is
   Executor State. This was originally coded as a NICE (Network
   Information and Control Exchange) data type which is a coded single
   field object of 1 byte in length. When converted for inclusion into
   the Internet MIB using the Internet SMI, it became an enumerated
   integer.

   All objects in this memo are described using the standard Internet
   SMI and BER of STD 16, RFC 1155. A complete description of an object
   will include the name, syntax and encoding. Just as with objects
   supported in the MIB (STD 17, RFC 1213), an object name is identified
   with an object identifier which has been administratively assigned.
   This identifies an Object Type. When an object type is combined with
   a specific instance, the particular object is uniquely identified.
   The use of Object Descriptors in this memo is consistent with that of
   STD 17, RFC 1213 - they are text strings meant to be read by humans.
   The descriptors have been taken from the original DIGITAL Network
   Architecture Network Management Functional Specification Version
   4.0.0 Dated July 1983 which defined DECnet Phase IV objects. These



DECnet Phase IV MIB Working Group