>....
The actual edit-operation in effect at any node depends on the operation attribute(s) and the default-operation parameter. The default is 'merge'. So a merge on type 'any' can silently turn into a 'replace' instead?In the same way as merge "silently turns into a replace" on an integer: <ifMtu nc:operation="merge">1500</ifMtu> vs. <ifMtu nc:operation="replace">1500</ifMtu>
Except 'any' can have child nodes, so the difference is noticeable.
<foo>
<a/>
</foo>
merged with
<foo>
<b/>
</foo>
results in
<foo>
<a/>
<b/>
</foo>
or
<foo>
<b/>
<a/>
</foo>
but not
<foo>
<b/>
</foo>
/martin
Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/netconf/>