same value operation attributes restriction

[Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>]

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

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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