RFC 1452 (rfc1452) - Page 3 of 17

Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework

          RFC 1452    Coexistence between SNMPv1 and SNMPv2   April 1993


          2.  Management Information

          The SNMPv2 approach towards describing collections of managed
          objects is nearly a proper superset of the approach defined in
          the Internet-standard Network Management Framework.  For
          example, both approaches use ASN.1 [5] as the basis for a
          formal descriptive notation.  Indeed, one might note that the
          SNMPv2 approach largely codifies the existing practice for
          defining MIB modules, based on extensive experience with the
          current framework.

          The SNMPv2 documents which deal with information modules are:

               Structure of Management Information for SNMPv2 [6], which
               defines concise notations for describing information
               modules, managed objects and notifications;

               Textual Conventions for SNMPv2 [7], which defines a
               concise notation for describing textual conventions, and
               also defines some initial conventions; and,

               Conformance Statements for SNMPv2 [8], which defines
               concise notation for describing compliance and
               capabilities statements.

          The following sections consider the three areas: MIB modules,
          compliance statements, and capabilities statements.

          MIB modules defined using the current framework may continue
          to be used with the SNMPv2 protocol.  However, for the MIB
          modules to conform to the SNMPv2 framework, the following
          changes are required:


          2.1.  Object Definitions

          In general, conversion of a MIB module does not require the
          deprecation of the objects contained therein.  Only if the
          semantics of an object truly changes should deprecation be
          performed.

          (1)  The IMPORTS statement must reference SNMPv2-SMI, instead
               of RFC 1155-SMI and RFC-1212.







          Case, McCloghrie, Rose & Waldbusser