upported have undergone a huge change. With convergence in networks space, a flat and simple model like SNMP does not scale up to meeting the next generation net- work management requirements. A typical example of convergence at a network element level is an L3-L7 switch in a converged network. This switch performs multiple other functionalities in addition to switching including, but not limited Fundamentals of EMS, NMS and OSS/BSS to, authentication, encryption, and application routing. As a result, the informa- tion base to be managed is much more complex. Attempts to serve this complex information base using SNMP has resulted in a force-fitting of this information into the limited 2-dimensional SNMP MIB model. This is clearly indicated in the proliferation of "helper tables" in any modern network element MIB. Another characteristic difference between legacy and next-generation packet networks is the number of network elements involved. Next generation networks have wit- nessed a mushrooming of both numbers and types of network elements to support a variety of services. This effective collection and analysis of events from all these elements is another area where a trap-based notification model of SNMP is show- ing signs of strain. The discussion SO far was on why SNMP is not suitable for NGNM and the need for a new protocol. XML as a language very much suited for network man- agement because it helps to define the structure of management information in an easy and flexible manner. XML is able to reliably transfer management data over widely deployed protocols like HTTP and TCP. Using the defined structure, XML ensures interoperability among management applications from different vendors and facilitates better integration of management data from disparate sources by flexibly linking between a managed object and management application. XML- based protocols bring in the advantages of XML for information exchange and also address the challenges in current network management making it the preferred protocol for we