Re: default-operation

[Andy Bierman <abierman@cisco.com>]

At 09:38 AM 11/3/2004, Sandeep Adwankar wrote:


>Andy Bierman wrote:
>
>> 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.
>
>The question is simple. If same rpc as shown below is
>send to two devices, one that understands "operation" attribute
>and one whose configuration doesn't, What happens then?

One implementation is conformant and the other is not.

Andy


>The device that understands "operation" attribute will do replace.
>What about device that don't have "operation" in schema, will
>it do merge?
>
>      <rpc message-id="101"
>xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
>         <edit-config>
>           <target>
>             <running/>
>           </target>
>           <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
>             <top xmlns="http://example.com/schema/1.2/config";>
>               <interface xc:operation="replace">
>                 <name>Ethernet0/0</name>
>                 <mtu>1500</mtu>
>                 <address>
>                   <name>1.2.3.4</name>
>                   <mask>255.0.0.0</mask>
>                 </address>
>               </interface>
>             <top>
>           </config>
>         </edit-config>
>       </rpc>
>
>thanks,
>Sandeep
>
>
>
>--
>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/> 


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