[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Exchanging Initialization Tag Elements
After the client application establishes a connection
to a NETCONF server, the two exchange <hello> tag elements,
as shown in the following example. For legibility, the example places
the client application’s <hello> tag element below
the NETCONF server’s. The two parties can actually emit their <hello> tag elements at the same time. For information about
the ]]>]]> character sequence used in this and the
following examples, seeGenerating Well-Formed XML Documents. For a detailed
discussion of the<hello> tag element, see Exchanging <hello>
Tag Elements.
|
NETCONF Server
|
Client Application
|
|
<hello>
<capabilities>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:candidate:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:url:1.0?candidate:1.0</capability>
<capability>http://xml.juniper.net/netconf/junos/1.0</capability>
<capability>http://xml.juniper.net/netconf/junos/sdx/1.0</capability>
</capabilities>
<session-id>3911</session-id>
</hello>
]]>]]>
|
|
|
<hello>
<capabilities>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:candidate:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:url:1.0?candidate:1.0</capability>
<capability>http://xml.juniper.net/netconf/junos/1.0</capability>
<capability>http://xml.juniper.net/netconf/junos/sdx/1.0</capability>
</capabilities>
</hello>
]]>]]>
|
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
