[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: comments on draft-ietf-netconf-prot-02.txt
On Tue, Mar 09, 2004 at 10:43:11AM -0800, Rob Enns wrote:
> > d) The edit-config(target, options, config) with the merge / replace
> > / delete attribute operations looks a bit strange (like others have
> > noted before). This really smells like a compound operation which
> > combines merge/replace/delete operations into a single rpc call. I
> > recently looked closer at NFSv4 protocol (RFC 3530) which has such
> > a compound operation and NETCONF might be actually simpler by
> > adopting a model which makes compound operations first class
> > citizens.
>
> This was discussed a little in Seoul, the current restriction on
> edit-config is that all values of the operation attribute in a single
> edit-config operation must have the same value. Is removing that
> restriction what you have in mind?
With this restriction, you really have separate merge / replace and
delete operations. So why not call them by name, e.g. merge-config,
replace-config and delete-config? Why do you still want to specify
these semantics as attributes???
/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/>