 various protocols. While internet-based man- agement like a web-based enterprise management would require a management protocol that works with HTTP, a telecom network would rather use SNMP with a well-defined MIB for its management. Evolution: The initial management requirements were limited to man- aging individual elements based on proprietary protocols. With stan- dard protocols it was later possible to manage networks. Then a single management solution was expected to manage a set of networks in a domain. Now management solutions are expected to manage networks across multiple domains. An organization in the communication indus- try wants its management solution to handle enterprise management, telecom network management, service management, and management of its storage devices. Most management solutions (Adventnet, IBM Netcool, etc.) support a variety of management protocols and can handle networks associated with different domains. Having support for multiple management solutions is just a stepping stone in devel- oping a converged management solution. Having a common information model and set of standard interface definitions for interaction between management com- ponents are some of the other factors that affect the development of a converged management solution. Additional Reading 1. William Stallings. The Practical Guide to Network Management Standards. Reading, MA: Addison-Wesley, 1993. Natalia Olifer and Victor Olifer. Computer Networks: Principles, Technologies and Protocols for Network Design. New York: John Wiley & Sons, 2006. Chapter 7 Standardizing Bodies Consider a crossroad in a busy street without traffic signals. The chaotic situation caused by this scenario is an example of the need for proper rules and regulations that everyone needs to follow in order to use the road. With multiple vendors coming with different network elements, element management systems, network manage- ment systems, and OSS solutions interoperability is a big issue and without defined standards communication is not 