construct. It also defines the :interleave capability, which when supported with the basic :notification capability facilitates the processing of other NETCONF operations while the subscription is active. A capability to support partial locking of the running configuration is defined in RFC 5717. This allows multiple sessions to edit non-overlapping sub-trees within the running configuration. Without this capability, the only lock available is for the entire configuration. A capability to monitor the NETCONF protocol is defined in RFC 6022. This document contains a data model including information about NETCONF datastores, sessions, locks, and statistics that facilitates the management of a NETCONF server. It also defines methods for NETCONF clients to discover data models supported by a NETCONF server and defines the <get-schema> operation to retrieve them. Messages The NETCONF messages layer provides a simple, transport-independent framing mechanism for encoding RPC invocations (<rpc> messages), RPC results (<rpc-reply> messages), and event notifications (<notification> messages). Every NETCONF message is a well-formed XML document. An RPC result is linked to an RPC invocation by a message-id attribute. NETCONF messages can be pipelined, i.e., a client can invoke multiple RPCs without having to wait for RPC result messages first. RPC messages are defined in RFC 6241 and notification messages are defined in RFC 5277. Transport NETCONF Protocol over Secure Shell (SSH): rfc:6242 NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication: rfc:7589 See also YANG Network management Configuration management Network monitoring XML Schema References Internet protocols Internet Standards Network management System administration Application layer protocols