Generate Well-Formed XML Documents
Each set of NETCONF and Junos XML tag elements emitted by the
NETCONF server and a client application within a <hello>, <rpc>, or <rpc-reply> tag element must constitute a well-formed XML document by obeying
the structural rules defined in the document type definition (DTD)
for the kind of information being sent. The client application must
emit tag elements in the required order and only in the allowed contexts.
The NETCONF server and client applications must also comply
with RFC 4742, Using the NETCONF Configuration Protocol
over Secure SHell (SSH), available at http://www.ietf.org/rfc/rfc4742.txt. In particular, the server and applications must send the character
sequence ]]>]]> after each XML document.
Because this sequence is not legal within an XML document, it unambiguously
signals the end of a document. In practice, the client application
sends the sequence after the closing </hello> tag and each closing </rpc> tag, and
the NETCONF server sends it after the closing </hello> tag and each closing </rpc-reply> tag.
In the following example (and in all examples in this document of tag elements emitted by a client application), bold font is used to highlight the part of the tag sequence that is discussed in the text.
<!-- generated by a client application -->
<hello | rpc>
<!-- contents of top-level tag element -->
</hello | /rpc>
]]>]]>
<!-- generated by the NETCONF server -->
<hello | rpc-reply attributes>
<!-- contents of top-level tag element -->
</hello | /rpc-reply>
]]>]]>