le Response <rpc-reply message-id="218" xmlns="http://ietf.org/ netconf/1./base"> <ok/> </rpc-reply> IV. <delete-config> This operation is used to delete a configuration datastore. <!-- Example Request <rpc message-id= "220" xmlns="http://ietf.org/ netconf/1.0/base"> Application Layer <delete-config> <target> <!-- The current or <running> configuration cannot be deleted --> <startup/> </target> </delete-config> </rpc> <!-- Example Response <rpc-reply - message-id = "220" xmlns="http://ietf.org/ netconf/1.0/base"> <ok/> </rpc-reply> V. <get-state> This operation is used to retrieve the state information of network element. <!-- Example Request <rpc message-id="222" xmlns="http://ietf.org/ xmlconf/1.0/base"> <get-state> <state > <interface> <name>ExternalRouter 6</name> </interface> </state > <format >xml</forrat> </get-state> </rpc> <!-- Example Response <rpc-reply - message-id="222" xmlns="http://ietf.org/ xmlconf/1.0/base"> <state> <interface> <name>ExternalRouter 6</name> <status>Active</status> <connections> 5 </connections> </interface> </state> </rpc-reply> Fundamentals of EMS, NMS and OSS/BSS VI. <kill-session> This operation is used to terminate a specific session. <!-- Example Request <rpc message-id="224" emlns="http://ietf.org/ xmlconf/1./base"> <kill-session> <session-id> 2 </session-id> </kill-session> </rpc> <!- Example Response --> <rpc-reply - message-id ="224" xmlns="http://ietf.org/ netconf/1./base"> <ok/> </rpc-reply> VII. <lock> This operation is used to lock the configuration source. The lock will not be granted if a lock is already held by another session on the source or the previous modification has not been committed. <!-- Example Request <rpc message-id="226" xmlns="http://ietf.org/ xmlconf/1./base"> <lock> <target> <running/> </target> </ lock> </rpc> <!-- Example Response <rpc-reply - message-id ="226" xmlns="http://ietf.org/ netconf/1./base"> <ok/> </rpc-reply> VIII. <commit> This operation is used to publish a completed configuration on the network element. Application Layer <!-- Exam