Re: more fun with the operation attribute

[Andy Bierman <ietf@andybierman.com>]

Phil Shafer wrote:
> Andy Bierman writes:
> > So what should the proper standard response to this PDU be, if any?
>
> IMHO, create, merge, and replace should all succeed if the target
> doesn't exist.

Yes, but that is clear if the create, merge, of replace operation
is by itself and the target does not exist.

In this case, they are all part of one request.
The data modeling languages describe what a valid
datastore (PDU result) on the agent should look like.
In this case, it just says the key to the <user> 'table'
is the <name> child element.

A sequential CLI model would allow this PDU, (w/o
the cut-and-paste end-tag errors that is) and the
final result would be "last one wins". In this case,
that means the 'replace' node would be the one that
actually sets the user entry for 'fred'.

Are there use cases where a different result makes operational sense?
If not, can we try to standardize this behavior to
mean "last one wins" (when multiple valid operations for the same
data element are attempted).

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