ON THIS PAGE
End-of-document Character Sequence
Usage
<hello>
<!-- child tag elements included by client application or NETCONF server -->
</hello>
]]>]]>
<rpc [attributes]>
<!-- tag elements in a request from a client application -->
</rpc>
]]>]]>
<rpc-reply xmlns="URN" xmlns:junos="URL">
<!-- tag elements in the response from the NETCONF server -->
</rpc-reply>
]]>]]>
Description
Signal the end of each XML document sent by the NETCONF server and client
applications. A client application sends the sequence after its closing
</hello> tag and each closing
</rpc> tag. The NETCONF server sends the sequence after
its closing </hello> tag and each closing
</rpc-reply> tag.
Use of this signal is required by RFC 4742, Using the NETCONF Configuration Protocol over Secure SHell (SSH), available at http://www.ietf.org/rfc/rfc4742.txt .
Starting in Junos OS Release 24.4R1 and Junos OS Evolved Release 24.4R1, you can
configure the NETCONF session to comply with RFC 6242, Using the NETCONF
Protocol over Secure Shell (SSH). If you enable RFC 6242 compliance
and both peers advertise the :base:1.1 capability, the NETCONF
session uses chunked framing for all messages after the initial
<hello> message. Otherwise, the NETCONF session uses
the end-of-document character sequence (]]>]]>) as the message
separator.