CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542)
RFC 1238

Document Type RFC - Experimental (June 1991; No errata)
Obsoletes RFC 1162
Last updated 2013-03-02
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1238 (Experimental)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          G. Satz
Request for Comments: 1238                         cisco Systems, Inc.
Obsoletes: RFC 1162                                          June 1991

                                CLNS MIB
                              for use with
               Connectionless Network Protocol (ISO 8473)
                                  and
              End System to Intermediate System (ISO 9542)

Status of this Memo

   This memo defines an experimental portion of the Management
   Information Base (MIB) for use with network management protocols in
   TCP/IP-based internets.  This is an Experimental Protocol for the
   Internet community.  Discussion and suggestions for improvement are
   requested.  Please refer to the current edition of the "IAB Official
   Protocol Standards" for the standardization state and status of this
   protocol.  Distribution of this memo is unlimited.

Table of Contents

   1. The Network Management Framework.......................    1
   2. Objects ...............................................    2
   2.1 Format of Definitions ................................    2
   3. Overview ..............................................    2
   3.1 Textual Conventions ..................................    3
   3.2 Changes from RFC 1162 ................................    3
   4. Definitions ...........................................    4
   4.1 Textual Conventions ..................................    4
   4.2 Groups in the CLNS MIB ...............................    4
   4.3 The CLNP Group .......................................    4
   4.4 The CLNP Error Group .................................   21
   4.5 The ES-IS Group ......................................   30
   5. References ............................................   31
   6. Security Considerations ...............................   32
   7. Author's Address.......................................   32

1.  The Network Management Framework

   The Internet-standard Network Management Framework consists of three
   components.  They are:

      RFC 1155 which defines the SMI, the mechanisms used for describing
      and naming objects for the purpose of management.  RFC 1212
      defines a more concise description mechanism, which is wholly
      consistent with the SMI.

Satz                                                            [Page 1]
RFC 1238                        CLNS MIB                       June 1991

      RFC 1156 which defines MIB-I, the core set of managed objects for
      the Internet suite of protocols.  RFC 1213, defines MIB-II, an
      evolution of MIB-I based on implementation experience and new
      operational requirements.

      RFC 1157 which defines the SNMP, 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.  Objects

   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) [7]
   defined in the SMI.  In particular, each object has a name, a syntax,
   and an encoding.  The name is an object identifier, an
   administratively assigned name, which specifies an object type.  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 OBJECT
   DESCRIPTOR, to also refer to the object type.

   The syntax of an object type defines the abstract data structure
   corresponding to that object type.  The ASN.1 language is used for
   this purpose.  However, the SMI [3] purposely restricts the ASN.1
   constructs which may be used.  These restrictions are explicitly made
   for simplicity.

   The encoding of an object type is simply how that object type is
   represented using the object type's syntax.  Implicitly tied to the
   notion of an object type's syntax and encoding is how the object type
   is represented when being transmitted on the network.

   The SMI specifies the use of the basic encoding rules of ASN.1 [8],
   subject to the additional requirements imposed by the SNMP.

2.1.  Format of Definitions

   Section 4 contains the specification of all object types contained in
   this MIB module.  The object types are defined using the conventions
   defined in the SMI, as amended by the extensions specified in [9].

3.  Overview

   The objects defined in this MIB module are be used when the ISO
   Connectionless-mode Network Protocol [10] and End System to

Satz                                                            [Page 2]
RFC 1238                        CLNS MIB                       June 1991

   Intermediate System [11] protocols are present.  No assumptions are
   made as to what underlying protocol is being used to carry the SNMP.
Show full document text