nt protocol for a packet-based network may not be best suited for a circuit switched telecom network. Hence various standardizing bodies worked on developing management protocols for various management applications and networks. These efforts and resources have resulted in a vast choice of standard- ized protocols, with vendors offering a wide range of tools and platforms based on these protocols. These tools and platforms greatly facilitate the development and integration of the management systems and network elements. Application and network are not the only items that determine the choice of a management protocol. It can also be a trade off between complexity and simplicity. Some protocols are aimed at simplicity, which would ensure easy agent implemen- tation and short turn around time in software development. These protocols like SNMP (simple network management protocol) are better structured and easy to understand. The simplicity in interaction often results in extra functionality to be inserted in mapping of the information model. There are protocols like CMIP (common management information protocol) that are more functionality rich and have an object-oriented structure making it a complex protocol. The wide range of operations in the protocol results in com- plex but powerful agents. There can also be scenarios where different management protocols should be combined within the same network element yielding the best solution for a specific interaction paradigm. This chapter gives an overview of some popular standardized management protocols. Based on the information in this chapter, the reader can make an informed decision on what protocol to use for implementing the requirements elicited in a project. 6.2 Overview of SNMP (Simple Network Management Protocol) The SNMP was developed by IETF in 1988 as a solution to manage elements on the Internet and other attached networks. SNMP was derived from its predecessor SGMP (simple gateway management protocol) and was intended to be replaced by object-oriented CMI