Re: same value operation attributes restriction

[Andy Bierman <abierman@cisco.com>]

At 07:36 AM 3/23/2004, Juergen Schoenwaelder wrote:
>I heard people saying that the current restriction 
>
>    In the interest of simplicity, all operation attributes
>    appearing within the <config> subtree MUST have the same value.
>
>should be dropped. This raises some questions how operation 
>attributes interact. Can I have a subtree marked "delete" and within 
>the subtree an subtree marked "merge" or "replace"? What about the
>other combinations that are possible? Can I use the operation attribute
>everywhere in the XML tree (note that we have not yet agreed on the
>data model aspects)? What happens if I "delete" something which can 
>not be deleted (because it is somehow hard-wired into the box)? I 
>guess I get an error response but the current ID is rather vague how
>the operation attribute value within an edit-config RPC operation 
>and the subtree holding the active operation attribute is actually 
>identified. There are probably more questions of this type that 
>need to be answered in order to remove the restriction...
>
>If, for the interest of simplicity, we keep this restriction, then 
>you might as well...

This whole issue is a bad reminder to me of all the stupid
things that were done in SNMP "to protect people from
themselves".   IMO, we don't know enough about the interactions
between NETCONF and NETCONF data models to start creating
CLRs without understanding their consequences.

We can have a CLR that says only 1 operation attribute can
appear in a given element sub-tree.  Or we can say that
if multiple operation attributes appear, unpredictable
results will occur.  Or we don't have to say anything --
we can let the data model designers make choices appropriate
for that data model.


>/js

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