 XML-based protocol. Its definition acts as a framework that allows subsequent extension of the design while leaving the foundation of the design intact. XML-based protocols are much more popular today for both enterprise and telecom management. A major reason for this popularity is the features of XML that makes it well suited for data handling in network management. Some of these features are: Structure of management information can be defined in an easy, flexible, and powerful manner. Data transport uses widely deployed protocols. Third-party applications can intercept and parse the data if the structure is shared Interoperability and centralized validation of management data. Ease of integrating management data from disparate sources. The XMLP message is defined in the form of an XML infoset, with element and attribute information in an abstract "document" called the envelope. XMLP message envelope XMLP Namespace XMLP Header XMLP Body XMLP namespaces: This is used for a unique name that avoids name collision, helps grouping of elements, and for use as a version control scheme. Management Protocols XMLP header: Used for adding semantics for authentication, transaction, con- text, and SO on. XMLP body: Data to be handled by the receiver. XML-based protocols have their drawbacks too. Use of XML leads to an increase in traffic load for message transfer. XMLP-based protocols are slow and the time duration for an interaction between the agent and manger using an XML protocol is more compared to most non-XML protocols. Though initially XML- based protocol was intended for a web-based enterprise management and scenarios of network management on the web, now XML protocols have gained more accep- tance. SOAP is the protocol suggested in MTOSI (multi-technology operations system interface) defined by TeleManagement Forum (TMF) and NETCONF is hailed as the next generation network management protocol. 6.7 Overview of SOAP (Simple Object Access Protocol) SOAP is an XML-based lightweight protocol developed by XML protocol w