Re: Second Example in section 7.2 of netconf-proto

[Andy Bierman <ietf@andybierman.com>]

Phil Shafer wrote:
> Andy Bierman writes:
>   
> > Merge and replace do not care about existing data.
> > Create on data that already exists is an error.
> > Delete on data that does not exist is an error.
> > Replace foo with nothing is not an error.
> > Merge foo with nothing is not an error.
> > Replace nothing with foo is not an error.
> > Merge nothing with foo is not an error.
> >     
>
> This all jibes with my memory.  The purpose of replace was
> to replace any and all matching data with the new incoming
> config.  So failing if nothing exists wouldn't help anyone.
> If you wanted that, you would use "create".
>   

This really matters when you consider simple ordered lists like ACLs.
Without 'replace' you could not exchange all the old entries in the list
for some new entries -- in one operation. 

> Thanks,
>  Phil
>
>   

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