Hi all,
I have a question regarding the semantics of the “candidate” validation
mode.
Section 5 states that in this mode “the candidate does not apply the
constraint checks”. However, it is not clear which constraints are
included in this statement, and what validation steps remain.
RFC 7950 Section 8 distinguishes between:
* properties that MUST hold in all data trees (e.g., type constraints,
key presence, choice/case rules, if-feature and when conditions), and
* additional constraints that define a valid data tree (e.g., must,
unique, referential integrity, mandatory, min/max-elements).
Given this, it is unclear:
* Whether “candidate” mode skips only the latter category (e.g.,
must/unique), or also skips properties that are required to hold in
all data trees (e.g., type constraints and structural rules).
* Whether a successful “candidate” validation result implies that the
data satisfies the minimal requirements of a YANG data tree, or
whether it may still violate those properties.
Depending on the interpretation, “candidate” mode could either represent
partial validation of a YANG data tree, or allow data that would not
qualify as a YANG data tree at all.
It would be helpful if the draft could clarify:
* which constraints are included in “constraint checks” that are not
applied in this mode, and
* what guarantees a successful validation result is intended to provide.
Best regards,
Jeroen van Bemmel
_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]
