ake it possible for third-party parsers to be used in processing the XML protocol message. GET Message with XML: <getenvp getenvp to= 'host' xmlns=`reqinfo:client' xmlns: getenvp= <getenvp: Header> <getenvp:getenvp from=`host' 'stream-id' kmlns=`reqinfo:client' xmlns: getenvp= </getenvp: Header> <getenvp: Body> <iq type='get to='mib@host id=`query-id'> <query xmlns=`reqinfo:iq:shelf-6.card-2.status'/> </iq> </getenvp : Body> </ getenvp getenvp > GET-NEXT message with XML: <getenvp getenvp to='host' xmlns=`reqinfo:client' xmlns getenvp= - URI , <getenvp: Header> <getenvp:getenvp from=`host' 'stream-id' xmlns=`reqinfo:client' xmlns:getenvp= URI </getenvp: Header> <getenvp:Body> <iq type='get-next to= 'mib@host' id= 'query-id'> <query xmlns=`reqinfo:iq: shelf-6.card-3.status': XML-Based Protocols </iq> </getenvp : Body> </ getenvp getenvp > 2. GET-RESPONSE message: The agent responds to the GET or GET-NEXT message from the manager with a GET-RESPONSE message that contains either the information requested or an error indication generated while pro- cessing the request from manager. The example below shows the response message with status information as "In-Service" for card-2 in shelf-6. In the GET-RESPONSE message, the Body will contain details of the request for which the response is being sent and the response. The query ID is populated in the message response Body along with specific information on the value given as response to the query. This makes it easy to tag the response against the request. GET-RESPONSE message with XML: <getenvp getenvp to= 'host' xmlns= 'reqinfo:client' xmlns: getenvp=` URI > <getenvp Header> <getenvp: getenvp from='host' id= 'stream-id' xmlns=`reqinfo:client' xmlns:getenvp= ---URI </getenvp:Header> <getenvp: Body> <iq type=`get-response' o='mgr@host' id= "query-id'> <query xmlns=`reqinfo:iq shelf-6. card-2. status'> <var>In-Service</var> </query> </iq> </getenvp:I Body> </ getenvp:getenvp > 3. SET Message: This message allows the manager to request a change to be made in the value of a