defined to be:                      enterpriseID * 256 +                           messageProcessingModel within enterprise                      For example, the fourth Message Processing Model                      defined by the enterprise whose enterpriseID                      is 1 would be 260.                    This scheme for allocating messageProcessingModel                    values allows for a maximum of 255 standards-                    based Message Processing Models, and for a                    maximum of 255 Message Processing Models per                    enterprise.                    It is believed that the assignment of new                    messageProcessingModel values will be rare                    in practice because the larger the number of                    simultaneously utilized Message Processing Models,                    the larger the chance that interoperability                    will suffer. It is believed that such a range                    will be sufficient.  In the unlikely event that                    the standards committee finds this number to be                    insufficient over time, an enterprise number                    can be allocated to obtain an additional 256                    possible values.                    Note that the most significant bit must be zero;                    hence, there are 23 bits allocated for various                    organizations to design and define non-standard                    messageProcessingModels.  This limits the ability                    to define new proprietary implementations of                    Message Processing Models to the first 8,388,608                    enterprises.                    It is worthwhile to note that, in its encoded                    form, the messageProcessingModel value will                    normally require only a single byte since, in                    practice, the leftmost bits will be zero for                    most messages and sign extension is suppressed                    by the encoding rules.                    As of this writing, there are several values of                    messageProcessingModel defined for use with SNMP.                    They are as follows:                        0  reserved for SNMPv1                        1  reserved for SNMPv2c                        2  reserved for SNMPv2u and SNMPv2*                        3  reserved for SNMPv3                   "       SYNTAX       INTEGER(0 .. 2147483647)   SnmpSecurityLevel ::= TEXTUAL-CONVENTION       STATUS       current       DESCRIPTION "A Level of Security at which SNMP messages can be                    sent or with which operations are being processed;                    in particular, one of:                      noAuthNoPriv - without authentication and                                     without privacy,                      authNoPriv   - with authentication but                                     without privacy,                      authPriv     - with authentication and                                     with privacy.                    These three values are ordered such that                    noAuthNoPriv is less than authNoPriv and                    authNoPriv is less than authPriv.                   "       SYNTAX       INTEGER { noAuthNoPriv(1),                              authNoPriv(2),                              authPriv(3)                            }   SnmpAdminString ::= TEXTUAL-CONVENTION       DISPLAY-HINT "255a"       STATUS       current       DESCRIPTION "An octet string containing administrative                    information, preferably in human-readable form.                    To facilitate internationalization, this                    information is represented using the ISO/IEC                    IS 10646-1 character set, encoded as an octet                    string using the UTF-8 transformation format                    described in [RFC2279].                    Since additional code points are added by                    amendments to the 10646 standard from time                    to time, implementations must be prepared to                    encounter any code point from 0x00000000 to                    0x7fffffff.  Byte sequences that do not                    correspond to the valid UTF-8 encoding of a                    code point or are outside this range are                    prohibited.                    The use of control codes should be avoided.                    When it is necessary to represent a newline,                    the control code sequence CR LF should be used.                    The use of leading or trailing white space should                    be avoided.                    For code points not directly supported by user                    interface hardware or software, an alternative                    means of entry and display, such as hexadecimal,                    may be provided.                    For information encoded in 7-bit US-ASCII,                    the UTF-8 encoding is identical to the                    US-ASCII encoding.                    UTF-8 may require multiple bytes to represent a                    single character / code point; thus the length                    of this object in octets may be different from                    the number of characters encoded.  Similarly,                    size constraints refer to the number of encoded                    octets, not the number of characters represented                    by an encoding.                    Note that when this TC is used for an object that                    is used or envisioned to be used as an index, then                    a SIZE restriction MUST be specified so that the                    number of sub-identifiers for any object instance                    does not exceed the limit of 128, as defined by                    [RFC1905].                    Note that the size of an SnmpAdminString object is                    measured in octets, not characters.                   "       SYNTAX       OCTET STRING (SIZE (0..255))   -- Administrative assignments ***************************************   snmpFrameworkAdmin       OBJECT IDENTIFIER ::= { snmpFrameworkMIB 1 }   snmpFrameworkMIBObjects       OBJECT IDENTIFIER ::= { snmpFrameworkMIB 2 }   snmpFrameworkMIBConformance       OBJECT IDENTIFIER ::= { snmpFrameworkMIB 3 }   -- the snmpEngine Group ********************************************   snmpEngine OBJECT IDENTIFIER ::= { snmpFrameworkMIBObjects 1 }   snmpEngineID     OBJECT-TYPE       SYNTAX       SnmpEngineID       MAX-ACCESS   read-only       STATUS       current       DESCRIPTION "An SNMP engine's administratively-unique identifier.                   "       ::= { snmpEngine 1 }   snmpEngineBoots  OBJECT-TYPE       SYNTAX       INTEGER (1..2147483647)       MAX-ACCESS   read-only       STATUS       current       DESCRIPTION "The number of times that the SNMP engine has                    (re-)initialized itself since snmpEngineID                    was last configured.                   "       ::= { snmpEngine 2 }   snmpEngineTime   OBJECT-TYPE       SYNTAX       INTEGER (0..2147483647)       UNITS        "seconds"       MAX-ACCESS   read-only       STATUS       current       DESCRIPTION "The number of seconds since the value of                    the snmpEngineBoots object last changed.                    When incrementing this object's value would                    cause it to exceed its maximum,                    snmpEngineBoots is incremented as if a                    re-initialization had occurred, and this                    object's value consequently reverts to zero.                   "       ::= { snmpEngine 3 }   snmpEngineMaxMessageSize OBJECT-TYPE       SYNTAX       INTEGER (484..2147483647)       MAX-ACCESS   read-only       STATUS       current       DESCRIPTION "The maximum length in octets of an SNMP message                    which this SNMP engine can send or receive and                    process, determined as the minimum of the maximum                    message size values supported among all of the                    transports available to and supported by the engine.                   "       ::= { snmpEngine 4 }   -- Registration Points for Authentication and Privacy Protocols **   snmpAuthProtocols OBJECT-IDENTITY       STATUS        current       DESCRIPTION  "Registration point for standards-track                     authentication protocols used in SNMP Management                     Frameworks.                    "       ::= { snmpFrameworkAdmin 1 }   snmpPrivProtocols OBJECT-IDENTITY       STATUS        current       DESCRIPTION  "Registration point for standards-track privacy                     protocols used in SNMP Management Frameworks.                    "       ::= { snmpFrameworkAdmin 2 }   -- Conformance information ******************************************   snmpFrameworkMIBCompliances                  OBJECT IDENTIFIER ::= {snmpFrameworkMIBConformance 1}   snmpFrameworkMIBGroups                  OBJECT IDENTIFIER ::= {snmpFrameworkMIBConformance 2}   -- compliance statements   snmpFrameworkMIBCompliance MODULE-COMPLIANCE       STATUS       current       DESCRIPTION "The compliance statement for SNMP engines which                    implement the SNMP Management Framework MIB.                   "       MODULE    -- this module           MANDATORY-GROUPS { snmpEngineGroup }       ::= { snmpFrameworkMIBCompliances 1 }   -- units of conformance   snmpEngineGroup OBJECT-GROUP       OBJECTS {                 snmpEngineID,                 snmpEngineBoots,                 snmpEngineTime,                 snmpEngineMaxMessageSize               }       STATUS       current       DESCRIPTION "A collection of objects for identifying and                    determining the configuration and current timeliness                    values of an SNMP engine.                   "       ::= { snmpFrameworkMIBGroups 1 }   END