-------------------------------------------------- 冯冲 Feng Chong Mobile: +86-13776612983<tel:+86-13776612983> Email: [email protected]<mailto:[email protected]> 发件人：Fengchong (frank) <[email protected]> 收件人：netmod <[email protected]> 抄 送：Yangang <[email protected]> 时 间：2019-09-06 15:19:28 主题[netmod] Please clarify implementation about ‘when’ Hi all, In RFC7950 secton 8, several description about when： In section 8.2<https://tools.ietf.org/html/rfc7950#section-8.2>. Configuration Data Modifications o If a request modifies a configuration data node such that any node's "when" expression becomes false, then the node in the data tree with the "when" expression is deleted by the server. In 8.3.1<https://tools.ietf.org/html/rfc7950#section-8.3.1>. Payload Parsing o If data for a node tagged with "when" is present and the "when" condition evaluates to "false", the server MUST reply with an "unknown-element" <error-tag> in the <rpc-error>. In 8.3.2<https://tools.ietf.org/html/rfc7950#section-8.3.2>. NETCONF <edit-config> Processing Modification requests for nodes tagged with "when", and the "when" condition evaluates to "false". In this case, the server MUST reply with an "unknown-element" <error-tag> in the <rpc-error>. YANG module： module foo { namespace “http://foo.com”; prefix “foo”; Leaf a {…} Leaf b { When “a = 10”; } } Scene 1: The first edit-config request: <edit-config> <target> <candidate/> </target> <config> <a xmlns= “http://foo.com”>3</a> </config> </edit-config> This request will set a = 3. The second request: <edit-config> <target> <candidate/> </target> <config> <a xmlns= “http://foo.com”>10</a> <b xmlns= “http://foo.com”>5</b> </config> </edit-config> According 8.3.1, in rpc payload parsing phase, the a’s value in candidate datastore is 3,so leaf b’s when condition is evaluated to false, server will report ‘unknown-element’ error. Is it expected by user? Scene 2: The first edit-config request: <edit-config> <target> <candidate/> </target> <config> <a xmlns= “http://foo.com”>10</a> </config> </edit-config> This request will set a = 10. The second request: <edit-config> <target> <candidate/> </target> <config> <a xmlns= “http://foo.com”>3</a> <b xmlns= “http://foo.com”>5</b> </config> </edit-config> According 8.3.1, in rpc payload parsing phase, the a’s value in candidate datastore is 10, so leaf b’s when condition is evaluated to true, server will accept this request in payload parsing phase. In edit-config request processing phase, if leaf a’s modification is processed firstly, the a’s value will be changed to 3, so the b’s when condition will be false, when server process b’s modification, b will be treated as unknown-element, the edit-config request will fail. If leaf b’s modification is processed firstly, server will accept this modification ,because b’s when condition is true, and when server process a’s modification , this modification will be accepted, and b’s when condition will be evaluated to false, leaf b will be deleted automatically, the edit-config request will be OK. How server should process this situation?
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
