Re: [netmod] [Technical Errata Reported] RFC7951 (7020)
> On Jul 11, 2022, at 5:17 AM, Ladislav Lhotka wrote: > > Hi, > > this erratum should be verified. > > Lada (author of the RFC) > Agreed. Kent ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
Re: [netmod] [Technical Errata Reported] RFC7951 (7020)
Hi, this erratum should be verified. Lada (author of the RFC) Dne 11. 07. 22 v 11:13 RFC Errata System napsal(a): The following errata report has been submitted for RFC7951, "JSON Encoding of Data Modeled with YANG". -- You may review the report below and at: https://www.rfc-editor.org/errata/eid7020 -- Type: Technical Reported by: Jernej Tuljak Section: 6.8 Original Text - An "identityref" value is represented as a string -- the name of an identity. If the identity is defined in a module other than the leaf node containing the identityref value, the namespace-qualified form (Section 4) MUST be used. Otherwise, both the simple and namespace- qualified forms are permitted. Corrected Text -- An "identityref" value is represented as a string -- the name of an identity. If the identity is defined in a module other than the leaf or leaf-list node containing the identityref value, the namespace-qualified form (Section 4) MUST be used. Otherwise, both the simple and namespace- qualified forms are permitted. Notes - The original text omitted leaf-list nodes, which may also be of "identityref" type. 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. -- RFC7951 (draft-ietf-netmod-yang-json-10) -- Title : JSON Encoding of Data Modeled with YANG Publication Date: August 2016 Author(s) : L. Lhotka 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 netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] [Technical Errata Reported] RFC7951 (7020)
The following errata report has been submitted for RFC7951, "JSON Encoding of Data Modeled with YANG". -- You may review the report below and at: https://www.rfc-editor.org/errata/eid7020 -- Type: Technical Reported by: Jernej Tuljak Section: 6.8 Original Text - An "identityref" value is represented as a string -- the name of an identity. If the identity is defined in a module other than the leaf node containing the identityref value, the namespace-qualified form (Section 4) MUST be used. Otherwise, both the simple and namespace- qualified forms are permitted. Corrected Text -- An "identityref" value is represented as a string -- the name of an identity. If the identity is defined in a module other than the leaf or leaf-list node containing the identityref value, the namespace-qualified form (Section 4) MUST be used. Otherwise, both the simple and namespace- qualified forms are permitted. Notes - The original text omitted leaf-list nodes, which may also be of "identityref" type. 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. -- RFC7951 (draft-ietf-netmod-yang-json-10) -- Title : JSON Encoding of Data Modeled with YANG Publication Date: August 2016 Author(s) : L. Lhotka Category: PROPOSED STANDARD Source : Network Modeling Area: Operations and Management Stream : IETF Verifying Party : IESG ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
Re: [netmod] JSON encoding of "leaf-list" nodes of type identityref
Hi Jernej, this is a clear omission, can you please file an erratum? Thanks, Lada Dne 11. 07. 22 v 10:57 Jernej Tuljak napsal(a): Hi, RFC7951, Section 6.8, says this [1]: An "identityref" value is represented as a string -- the name of an identity. If the identity is defined in a module other than the leaf node containing the identityref value, the namespace-qualified form (Section 4) MUST be used. Otherwise, both the simple and namespace- qualified forms are permitted. This text fails to mention leaf-list nodes. It should probably say: An "identityref" value is represented as a string -- the name of an identity. If the identity is defined in a module other than the leaf or leaf-list node containing the identityref value, the namespace-qualified form (Section 4) MUST be used. Otherwise, both the simple and namespace-qualified forms are permitted. [1] - https://datatracker.ietf.org/doc/html/rfc7951#section-6.8 Jernej ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] JSON encoding of "leaf-list" nodes of type identityref
Hi, RFC7951, Section 6.8, says this [1]: An "identityref" value is represented as a string -- the name of an identity. If the identity is defined in a module other than the leaf node containing the identityref value, the namespace-qualified form (Section 4) MUST be used. Otherwise, both the simple and namespace- qualified forms are permitted. This text fails to mention leaf-list nodes. It should probably say: An "identityref" value is represented as a string -- the name of an identity. If the identity is defined in a module other than the leaf or leaf-list node containing the identityref value, the namespace-qualified form (Section 4) MUST be used. Otherwise, both the simple and namespace-qualified forms are permitted. [1] - https://datatracker.ietf.org/doc/html/rfc7951#section-6.8 Jernej ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
