On 10/16/2015 6:05 AM, Ladislav Lhotka wrote:
On 16 Oct 2015, at 12:27, Balazs Lengyel <[email protected]> wrote: IMHO YANG should define the behavoir, and I would want it to be the same on Netconf/Restconf/CLI etc. I agree that " 1) you get an error back" would be the best: because it is the easiest to understand for the operator, with the fewest corner cases. Also we must define if in the same transaction we set b=42 and a=2. which of the 3 options are taken? We should not leave such complex cases undefined, or alternatively state that they are implementation dependant.I might be difficult to say what is a complex case, unless we abandon XPath in "when" statements and use something else - and considerably simpler. Here is another interesting corner case - does it qualify as being complex? leaf-list bar { type uint8; when "count(../*) > 1"; } leaf foo { type uint8; }
Interesting example...
Assuming no instances exist, is this edit allowed? (This was essentially your question.) <bar>1</bar> <foo>2</foo>
I think this should succeed
But what about this? <bar>1</bar> <bar>2</bar>
I think this should succeed too because the when is satisfied in the data store after the edit-config. -Xiang Li _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
