Re: default-operation

[Andy Bierman <abierman@cisco.com>]

At 03:03 PM 11/1/2004, Sandeep Adwankar wrote:
>What is the result of this rpc?
>
>1. Is this a data model that specifies default merge behavior
>2. Is this a data model that doesn't support optional "operation"

I'm not sure I understand your questions. 
 
We can't tell the defaults and optional parameters from an
XML instance document fragment.  You need to have the schema
for that.  

The intent of the "replace" operation is that only
the specified configuration parameters are affected.

It appears that the MTU on interface "Ethernet0/0" is 
being changed in this example.   I'm not sure it's specified
in the document if that is the case or not.  

This example could also be interpreted as "Remove all parameters 
for interface Ethernet0/0 and just set the MTU to 1500".
If this is correct, then are all parameters unset or do the
parameters with defaults get changed to the default value?

In a strict interpretation, "replace only the subtree(s) that 
are specified in the request" will wipe out almost the whole config 
because <top> is specified in the request.  

I think we need some clarifying text on this issue.
Thanks for bringing it up.

>attribute
>and hence the default-operation replace will happen
>
><rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
>   <edit-config>
>     <target>
>        <running/>
>     </target>
>     <default-operation>replace</default-operation>
>     <config>
>        <top xmlns="http://example.com/schema/1.2/config";>
>           <interface>
>              <name>Ethernet0/0</name>
>              <mtu>1500</mtu>
>           </interface>
>        </top>
>      </config>
>    </edit-config>
></rpc>
>
>
>thanks,
>Sandeep

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/>