Thanks, Kent and Lada, I will update the errata with this disposition unless there is any objection.
Cheers. > On Jun 23, 2026, at 8:57 AM, Ladislav Lhotka > <[email protected]> wrote: > > > >> 23. 6. 2026 v 0:29, Kent Watsen <[email protected] >> <mailto:[email protected]>>: >> >> I agree with the Errata, but wonder if the sentence could be cleaner, for >> instance: >> >> • CORRECTED: All referential integrity constraints defined by the value >> of a leaf with the "instance-identifier" type or via the "path" statement of >> the "leafref" type MUST... >> >> • NEW CORRECTED: All referential integrity constraints defined by the >> value of a leaf with the "instance-identifier" or "leafref" types MUST... >> > > Yes, maybe it's better to keep it simple even though, strictly speaking, for > leafref the constraint is defined by both the value *and* "path" statement. > > Lada > >> >> Kent >> >> >>> On Jun 22, 2026, at 3:18 PM, [email protected] wrote: >>> >>> The following errata report has been submitted for RFC7950, >>> "The YANG 1.1 Data Modeling Language" >>> >>> -------------------------------------- >>> You may review the report below and at: >>> https://errata.rfc-editor.org/eid9005/ >>> >>> -------------------------------------- >>> Type: Technical >>> Reported by: Ladislav Lhotka <[email protected]> >>> >>> Section 8.1 says: >>> >>> Original Text >>> ------------- >>> o All referential integrity constraints defined via the "path" statement >>> MUST be satisfied. >>> >>> Corrected Text >>> -------------- >>> o All referential integrity constraints defined by the value of a leaf with >>> the "instance-identifier" type or via the "path" statement of the "leafref" >>> type MUST be satisfied if the "require-instance" property for that type is >>> true. >>> >>> Notes >>> ----- >>> The original bullet item has two problems: >>> >>> 1. Its formulation was adopted from RFC 6020 without taking into account >>> that the "require-instance" statement was added to the "leafref" type in >>> YANG 1.1. >>> >>> 2. The "instance-identifier" type defines another referential integrity >>> constraint that should be treated the same as the "leafref" constraint. >>> >>> Instructions: >>> ------------- >>> This erratum is currently posted as "Reported". Please >>> use "Reply All" to discuss whether it should be verified or >>> rejected. When a decision is reached, the verifying party >>> will log in to change the status and edit the report, if necessary. >>> >>> -------------------------------------- >>> RFC7950 (draft-ietf-netmod-rfc6020bis) >>> -------------------------------------- >>> Title : The YANG 1.1 Data Modeling Language >>> Publication Date : August 2016 >>> Author(s) : M. Bjorklund, Ed. >>> Category : Proposed Standard >>> Source : netmod (ops) >>> Stream : IETF >>> Verifying Party : IESG >>> >>> _______________________________________________ >>> netmod mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >> >> _______________________________________________ >> netmod mailing list -- [email protected] <mailto:[email protected]> >> To unsubscribe send an email to [email protected] >> <mailto:[email protected]> > > -- > Ladislav Lhotka > PGP Key ID: 0xB8F92B08A9F76C67 > > > > _______________________________________________ > netmod mailing list -- [email protected] <mailto:[email protected]> > To unsubscribe send an email to [email protected] > <mailto:[email protected]> Mahesh Jethanandani [email protected]
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
