he last category is new, and at the publication date of RFC 3410 (Ref. 13) it includes seven documents: RFC 3410, which is the referenced document of this section. STD 62, RFC 3411, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks" describes the overall architecture for security and administration. NETWORK MANAGEMENT STD 62, RFC 3412, "Message Processing and Dispatching for the Simple Net- work Management Protocol (SNMP)" describes the possibility of multiple message processing models and the dispatcher portion that can be part of the SNMP proto- col engine. STD 62, RFC 3413, "Simple Network Management Protocol Application," describes the five initial types of applications that can be associated with an SNMPv.3 engines and their elements of procedure. STD 62, RFC 3414, "User-Based Security Model (USM) for Version 3 of SNMP," describes the threats against which protection is provided, as well as the mechanisms, protocols, and supporting data used to provide SNMP message-level security with the user-based security model. STD 62, RFC 3415, "View-Based Access Control Model (VCAM) for the SNMP," describes how view-based access control can be applied with command responder and notification originator applications. RFC 2576, "SNMPv.3 Coexistence and Transition," describes coexistence between the SNMPv.3 Management Framework, SNMPv.2 Management Framework, and the original SNMPv.1 Management Framework and is in the process of being updated. 21.7.6 Common Management Information Protocol (CMIP) SNMP was developed rapidly with an objective to serve as a network management com- munications standard until CMIP was issued. SNMP met such success that it now has a life of its own. CMIP remains with slow implementation. It hasn't remotely reached the popularity of SNMP. CMIP is an ISO development and it is designed to operate in the OSI environment. It is considerably more complex than its SNMP counterpart. Figure 21.12 illustrates the OSI Management architecture that uses CMIP to acc