st machine otherwise default port is assumed. Multicast is also possible where the transmission is to a group of machines. This happens when an arbitrary group of receivers expresses interest in receiving a particular data stream. The destination in this case for the XMLP-UDP message will be the multicast group. The source address is specified in the UDP packet and needs to be the IPv4 or IPv6 address of the sender. The receiver needs to be programed to reject a packaged XMLP message that has inappropriate values for the source address. The XMLP envelope needs to fit within a single datagram with inherent encryption capability. 18.5.3 XMLP-Based Management Framework Let us start with the management data originating from the network elements. There is usually a single manager for multiple network elements. So there will be multiple agents running on the different network elements, collecting management data and feeding data to a common XMLP manager. The management information obtained from the agents is first passed through a data conversion/XML parser module, where the body of the XMLP envelope is parsed to extract useful information. This infor- mation is stored in a database and it will consist of fault, configuration, account- ing, performance, and security (FCAPS) information. The purpose of the FCAPS management code is to organize the data collected from the agents after parsing to appropriate containers in the database (DB). This FCAPS management module is not mandatory but is usually present in most XMLP management frameworks (see Figure 18.3). Fundamentals of EMS, NMS and OSS/BSS Management application Web-based server that supports UDP Adapter framework Third-party applications XMLP-UDP FCAPS management Code agents Data conversion/ XML parser Figure 18.3 XMLP management framework. The data derived can be sent out via an adapter framework to feed third-party management applications. An example of this would be CORBA IDL, which is supported by most third-party management applications. Before XML became pop