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/eid8784

--------------------------------------
Type: Technical
Reported by: Maria Matejka <[email protected]>

Section: 9.12.4

Original Text
-------------
   If the second member type in the union had been of type "string"
   instead of an enumeration, the current value would have matched, and
   the resulting configuration would have been valid.

Corrected Text
--------------
   If the second member type in the union had been of type "string"
   instead of an enumeration, the current value would have matched, and
   the resulting configuration would have been valid. However, the leaf's
   value must then be reinterpreted if a matching instance is added later.

Notes
-----
>From the example wording, it looks like that the event-to-be-watched is only 
>target instance removal for a successfully resolved leafref. Yet from the 
>specification, one can infer that one indeed needs to watch also for creation 
>of a target instance for unsuccessfully resolved possible leafref, and 
>therefore the example is misleading.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) 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-14)
--------------------------------------
Title               : The YANG 1.1 Data Modeling Language
Publication Date    : August 2016
Author(s)           : M. Bjorklund, Ed.
Category            : PROPOSED STANDARD
Source              : Network Modeling
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to