Explicit and unique naming of configuration target

[Larry Menten <lmenten@lucent.com>]

Rob,
Phil,

The Enns draft does not explicitly name the target element of the operation.
A transaction that is intended to create an ospf instance, an ospf area 
instance
within that ospf instance, an ospf interface instance within that area, 
and an
MD5 key instance within that interface is the same as one that would be 
formulated
just to create the MD5 key instance.  The behavior is determined by the 
current
state of the configuration.

I would propose that the draft be modified to explicitly name the target 
of the
operation.  This could be done with an XPath expression or by replacing the
contents of the <target> element with a tree that provides the tag hierarchy
with unique keys. What are your thoughts?

Thanks,

Larry

--
Larry Menten               Lucent Technologies/Bell Laboratories
Phone: 908 582-4467        600 Mountain Avenue, Murray Hill, NJ  07974 USA 


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