Ladislav Lhotka <[email protected]> writes: > On Tue, 2019-10-22 at 17:02 +0200, Martin Bjorklund wrote: >> Hi, >> >> The problem is that it is not clear that we can use this new >> definition with the rest of the text in the RFC that uses this term. >> For example, section 7.1.5 talks about "the imported module's schema >> tree", and this doesn't really work if the schema tree is not tied to >> a module. > > On the other hand, sec. 9.9 says (and that's how I stumbled upon this): > > The "path" substatement (Section 9.9.2) is used to identify the > referred leaf or leaf-list node in the schema tree. > > With the current definition of schema tree, it would mean that the referred > leaf > or leaf-list node must be in the same module, which is of course a nonsense.
The erratum was rejected, but if we keep the definition of "schema tree", then the above definition of "path" statement is technically incorrect. Lada > > Lada > >> >> Also the proposed definition is recursive since it is defined in >> terms of "schema node", and a "schema node" is already defined as "a >> node in the schema tree". >> >> So it probably makes sense to look at this definition (and the text >> and other definitions) if we do a document update, but as it is >> currently written I think it should be rejected. >> >> >> /martin >> >> >> >> RFC Errata System <[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://www.rfc-editor.org/errata/eid5879 >> > >> > -------------------------------------- >> > Type: Technical >> > Reported by: Ladislav Lhotka <[email protected]> >> > >> > Section: 3 >> > >> > Original Text >> > ------------- >> > o schema tree: The definition hierarchy specified within a module. >> > >> > >> > Corrected Text >> > -------------- >> > o schema tree: The hierarchy of schema nodes defined in the set of all >> modules >> > implemented by a server, as specified in the YANG library data >> > [RFC7895]. >> > >> > >> > >> > Notes >> > ----- >> > The original definition of the term has two problems: >> > >> > 1. Schema tree is not limited to a single module. Some YANG constructs, >> > such >> as augment and leafref type, may refer to a schema node that is defined in >> another module. >> > >> > 2. Apart from schema nodes, YANG modules contain definitions that do not >> contribute to the schema tree: groupings, typedefs, identities etc. >> > >> > Instructions: >> > ------------- >> > This erratum is currently posted as "Reported". If necessary, please >> > use "Reply All" to discuss whether it should be verified or >> > rejected. When a decision is reached, the verifying party >> > can log in to change the status and edit the report, if necessary. >> > >> > -------------------------------------- >> > RFC7950 (draft-ietf-netmod-rfc6020bis-14) >> > -------------------------------------- >> > Title : The YANG 1.1 Data Modeling Language >> > Publication Date : August 2016 >> > Author(s) : M. Bjorklund, Ed. >> > Category : PROPOSED STANDARD >> > Source : Network Modeling >> > Area : Operations and Management >> > Stream : IETF >> > Verifying Party : IESG >> > > -- > Ladislav Lhotka > Head, CZ.NIC Labs > PGP Key ID: 0xB8F92B08A9F76C67 > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
