Alcatel-Lucent 7450 - Page 345

NETCONF
7450 ESS System Mangement Guide Page 345
</router>
</configure>
</data>
</rpc-reply>
]]>]]>
The chunked framing mechanism is supported (in addition to the EOM mechanism). As per
RFC 6242, Section 4.1 - Framing Protocol, "... If the :base:1.1 capability is advertised by both
peers, the chunked framing mechanism (see Section 4.2) is used for the remainder of the
NETCONF session. Otherwise, the old end-of-message-based mechanism (see Section 4.3) is
used."
Example 1 — Chunked message:
#302
<?xml version="1.0" encoding="UTF-8"?><rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><get-config><source><running/></
source><filter><config><configure><router><interface><interface-name>system</inter-
face-name></interface></router></configure></config></filter></get-config></rpc>
##
Example 2 — Chunked message:
#38
<?xml version="1.0" encoding="UTF-8"?>
#85
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
#62
<source><running/></source>
<filter>
<configure>
##79
<system>
<netconf>
</netconf>
</system>
##55
</configure>
</filter>
</get-config>
</rpc>
##
Handling of default data (for example, ' info' vs 'info detail') is done using the mechanisms
detailed in RFC 6243. The SR OS NETCONF server supports the 'trim' method and advertises
that in the <hello>:
<capability>urn:ietf:params:netconf:capability:with-defaults:1.0?basic-mode=trim</
capability>
Pseudo-transactional capabilities are supported. A user can save a rollback checkpoint (for
example, prior to doing an <edit-config> or a series of <edit-config>) and perform a rollback
revert if needed later.