Re: Second Example in section 7.2 of netconf-proto

[Martin Bjorklund <mbj@tail-f.com>]

Andy Bierman <ietf@andybierman.com> wrote:
> > If this is the case, how is 'replace' different from 'merge'??
> 
> 
> Depends on the data model.
> What if the data model allowed duplicate entries?
> What if some subtrees allow duplicates or have
> some additive properties (defined in the object semantics)?
> Then merge and replace act very differently.

So if the datamodel does not allow duplicates, then 'replace' and
'merge' behave the same?

> We have copy-config for course-grained clobbering
> of config data.  Edit-config is for fine-grained operations,

But copy-config replaces the *entire* configuration, which also means
that you have to have write-access to *all* config data in order to
use copy-config at all.

> so yes, you would have to explicitly delete subtrees by
> including the root of the subtree in the request.

This seems quite complicated...  Maybe an operation
"really-REALLY-replace" would be useful :)


/martin

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