RFC 2856 (rfc2856) - Page 2 of 10

Textual Conventions for Additional High Capacity Data Types

RFC 2856                High Capacity Data Types               June 2000


1.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o   An overall architecture, described in RFC 2571 [RFC 2571].

   o   Mechanisms for describing and naming objects and events for the
       purpose of management. The first version of this Structure of
       Management Information (SMI) is called SMIv1 and described in STD
       16, RFC 1155 [RFC 1155], STD 16, RFC 1212 [RFC 1212] and RFC 1215
       [RFC 1215].  The second version, called SMIv2, is described in STD
       58, RFC 2578 [RFC 2578], STD 58, RFC 2579 [RFC 2579] and STD 58,
       RFC 2580 [RFC 2580].

   o   Message protocols for transferring management information. The
       first version of the SNMP message protocol is called SNMPv1 and
       described in STD 15, RFC 1157 [RFC 1157].  A second version of the
       SNMP message protocol, which is not an Internet standards track
       protocol, is called SNMPv2c and described in RFC 1901 [RFC 1901]
       and RFC 1906 [RFC 1906].  The third version of the message
       protocol is called SNMPv3 and described in RFC 1906 [RFC 1906],
       RFC 2572 [RFC 2572] and RFC 2574 [RFC 2574].

   o   Protocol operations for accessing management information. The
       first set of protocol operations and associated PDU formats is
       described in STD 15, RFC 1157 [RFC 1157].  A second set of
       protocol operations and associated PDU formats is described in
       RFC 1905 [RFC 1905].

   o   A set of fundamental applications described in RFC 2573 [RFC 2573]
       and the view-based access control mechanism described in RFC 2575
       [RFC 2575].

   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [RFC 2570].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2.  The
   textual conventions defined in this MIB module cannot be translated
   to SMIv1 since the Counter64 type does not exist in SMIv1.







Bierman, et al.             Standards Track