An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks

Entity MIB (Version 4)

“…There is a need for a standardized way of providing non-volatile, administratively assigned identifiers for physical components represented with the Entity MIB. There is also a need to align the Entity MIB with the SNMPv3 administrative framework (STD 62, [RFC3411]). Implementation experience has shown that additional physical component attributes are also desirable.…”

“…For SNMPv3, the term "context" is used instead of "naming scope". The complete definition of an SNMP context can be found in Section 3.3.1 of RFC 3411 [RFC3411].…”

Uniform Resource Identifier (URI) Scheme for the Simple Network Management Protocol (SNMP)

“…In contrast, host and port have both the syntax and semantics specified in [RFC3986]. See [RFC3411] for the semantics of securityName, contextEngineID, and contextName.…”

“…The SNMP architecture includes control of access to management information (see Section 4.3 of [RFC3411]). An SNMP URI does not contain sufficient security information to obtain access in all situations, as the SNMP URI syntax is incapable of encoding SNMP securityModels, SNMP securityLevels, and credential or keying information for SNMP securityNames.…”

Configuring Networks and Devices with Simple Network Management Protocol (SNMP)

“…The OwnerString textual convention from RMON-MIB RFC 2819 [32] has been used successfully for this purpose. More recently, RFC 3411 [1] introduced the SnmpAdminString which has been designed as a UTF8 string. This is more suitable for representing names in many languages.…”