On 2015-10-14 23:06, Andy Bierman wrote:
Our server applies all the edits first, when checks all the when-stmts
that might have changed value. Nodes that have already existed in the
datastore may get pruned, not just the new nodes.
Hello Andy,
We definitely need a new section/paragraph in RFC6020 about the scenario when
the when statement is changed in a transaction and something under the when
statement is also changed in the same transaction!
---------------------------------------------------------------
So if you have the model
leaf a {type boolean;}
leaf b {
when a
type int8;
}
We have 3 cases:
1) if "a" is false and then you get an edit config with: set b=5 ; set
a=true: result OK
2) if "a" is false and then you get an edit config with: set b=5: result
unknown-element
3) if "a" is true and then you get an edit config with: set b=5 ; set
a=false: result OK, b gets pruned (contradicts 8.2.1)
Are these the results dictated by YANG and supported by your implementation?
regards Balazs
--
Balazs Lengyel Ericsson Hungary Ltd.
Senior Specialist
ECN: 831 7320
Mobile: +36-70-330-7909 email: [email protected]
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
