RE: A question about <edit-config> operation

["Romascanu, Dan \(Dan\)" <dromasca@avaya.com>]

> -----Original Message-----
> From: owner-netconf@ops.ietf.org 
> > 
> > We usually think it set the MTU to 1500 on an interface named 
> > "Ethernet0/0", but why don't think it set the name to 
> "Ethernet0/0" on 
> > interfaces whose MTU equal to 1500?
> 
> 
> Because the schema that defines the structure and semantics 
> of the data model (not shown here) says the key for instance 
> uniqueness is the <name> element, not the <mtu> element.
> 
> A comment will be added to the prot-13 draft to make this 
> seemingly obvious detail more clear.
> 

I am not sure that there will be a prot-13 draft. draft-...prot-12 was
approved by the IESG and submitted to the RFC Editor. You are probably
referring to the following change which will show up in the RFC version:


Page 39, bottom:

OLD:

   Example:

       Set the MTU to 1500 on an interface named "Ethernet0/0" in the
       running configuration:

NEW:

   Example:

       The <edit-config> examples in this section utilize a simple
       data model, in which multiple instances of the 'interface'
       element may be present, and an instance is distinguished
       by the 'name' element within each 'interface' element.

       Set the MTU to 1500 on an interface named "Ethernet0/0" in the
       running configuration:

Dan


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