Navigation
Overview of a NETCONF XML Management Protocol Session
Communication between the NETCONF server and a client application is session based. The two parties explicitly establish a connection before exchanging data and close the connection when they are finished. Each request from the client application and each response from the NETCONF server constitutes a well-formed XML document, because the tag streams obey the structural rules defined in the NETCONF and Junos XML DTDs for the kind of information they encode. Client applications must produce a well-formed XML document for each request by emitting tag elements in the required order and only in the legal contexts.
The following list outlines the basic structure of a NETCONF session.
- The client application establishes a connection to the NETCONF server and opens the NETCONF session.
- The NETCONF server and client application exchange initialization information, which is used to determine if they are using compatible versions of the Junos OS and the NETCONF XML management protocol.
- The client application sends one or more requests to the NETCONF server and parses its responses.
- The client application closes the NETCONF session and the connection to the NETCONF server.
