----- Original Message ----- From: "Phil Shafer" <p...@juniper.net> Sent: Thursday, March 23, 2017 8:24 PM
> William Ivory writes: > >Yes, I'd noticed that. Does this make the behaviour 'undefined' in YANG 1.0? > > No, this was a clarification. The text in 6020 was reasonably clear: > > The "when" statement makes its parent data definition statement > conditional. The node defined by the parent data definition > statement is only valid when the condition specified by the "when" > statement is satisfied. > > And no default should be provided for any invalid node. If the node > can't exist, the default can't either. William Having tracked the discussions that led to RFC7950, the sense I got was that if you can avoid using 'when' then avoid using it. If you cannot avoid using 'when' avoid using it. Not something that is ever likely to appear in an I-D but the 'when' statement does have complex interactions that may not be intuitive and although RFC7950 does spell them out, yet they may not be apparent; which this thread also spells out to me:-) I would not say this of any other YANG statement. Tom Petch > Thanks, > Phil > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
