: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 specific variable. The agent based on design could respond to this message with a GET-RESPONSE message indicating that a change request was successful or an error message indicating the reason for change request failure. In the example below, the SET request is to change the status of link-1 for card-6 in shelf-2 to "Offline." It can be seen that the SET message body will have information about what needs to be set and where the information needs to be set. SET message with XML: <setenvp setenvp to= 'host' xmlns= 'setinfo:client' xmlns: setenvp= URI <setenvp Header> Fundamentals of EMS, NMS and OSS/BSS <setenvp: setenvp from= 'host' id=`stream-id' xmlns='setinfo:client' xmlns:setenvp=`-URI </setenvp:Header> <setenvp:Body> <iq type= 'set' to='mib