d console. The configuration data depends on the type of device being managed and varies based on the device implementation. The transport layer can be any basic transport protocol that satisfies some requisites of NETCONF. In this implementation, the XML-based messaging patterns of the RPC model and the NETCONF operations are discussed. 32.3 RPC Elements in NETCONF I. <rpc> element The <rpc> element has the following characteristics: It has a message-id attribute to identify the RPC request from the sender. The receiver can use the same identifier in response, to indicate what request has triggered the specific response. This element is used in both management and operation channels. The method to be invoked is specified inside the <rpc> tags <rpc message - id = 212> method> <! - - This can be any method </ method> </rpc> Fundamentals of EMS, NMS and OSS/BSS II. <rpc-reply> element The <rpc-reply> element has the following characteristics: This message is sent in response to a <rpc> operation. The value of the message-id attribute is the same as the value of the <rpc> for which the response is sent. The response data is specified inside the <rpc-reply> tags. <rpc-reply message-id = 212> < content> <! -The response content comes within the rpc-reply tags --> </ content> </rpc-reply> III. <rpc-error> element The <rpc-error> element has the following characteristics: This message is sent in <rpc-reply> messages. It is used to capture errors that occur during the processing of an <rpc> request. The error message has the following attributes: - <tag> This tag is used to identify the error condition using a string. - <error-code> This tag is used to identify the error condition using an integer. - <severity> This tag is used to identify the error severity. - <statement> This tag gives the cause of the error. - <message> This is a string description of the error condition. Additional attributes like <action> can be used to describe the action to be taken when the specific error is encountered and <edit-path> to describ