[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: same value operation attributes restriction
On Tue, Mar 23, 2004 at 02:24:06PM -0800, Andy Bierman wrote:
> At 07:36 AM 3/23/2004, Juergen Schoenwaelder wrote:
> 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.
But then why do you want to define operation attributes at all
in the netconf protocol? Why do you want to establish a CLR
which says the operation must be specified as an attribute and
it must be either replace, merge or delete?
I would just feel much better if the boundary between the netconf
protocol and the data manipulated by the protocol is well defined.
/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/>