[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Second Example in section 7.2 of netconf-proto

Sharon Chisholm wrote:

hi

In section 7.2, the second example indicates it will add an interface,
but uses the operator of replace. The definition of replace does not
actually say that if the entry does not exist, it is created. Should it,
or should the operator of create be used instead in this example?

I also wonder with these examples if there is an implicit assumption
that the key is name and this somehow defines whether something exists
or not?



How about some text that says:

"The manager must understand the data model being used.
In these examples, the manager knows a priori that the 'name' element
is used for instance identification to distinguish multiple instances
of the 'interface' element.



      Add an interface named "Ethernet0/0" to the running configuration,
      replacing any previous interface with that name:

     <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>192.0.2.4</name>
                 <prefix-length>24</prefix-length>
               </address>
             </interface>
           </top>
         </config>
       </edit-config>
     </rpc>

     <rpc-reply message-id="101"
          xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
       <ok/>
     </rpc-reply>


Sharon Chisholm
Nortel Ottawa, Ontario 
Canada



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