The following errata report has been held for document update 
for RFC7950, "The YANG 1.1 Data Modeling Language". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6031

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Radek Krejci <rkre...@cesnet.cz>
Date Reported: 2020-03-27
Held by: Robert Wilton (IESG)

Section: 9.9.3

Original Text
-------------
The "require-instance" statement, which is a substatement to the 
"type" statement, MAY be present if the type is "instance-identifier"
or "leafref".  It takes as an argument the string "true" or "false".
If this statement is not present, it defaults to "true".

Corrected Text
--------------
The "require-instance" statement, which is a substatement to the
"type" statement, MAY be present if the type is "instance-identifier",
"leafref" or a type derived from them.  It takes as an argument the
string "true" or "false".  If this statement is not present, it
defaults to "true".

Notes
-----
The document does not specify whether the “require-instance” keyword is allowed 
in typedef refinements derived from the “leafref” or “instance-identifier” base 
types, but it is anticipated that a future revision of YANG would allow this.   
It is suggested that modules using YANG language versions 1 [RFC 6020] and 1.1 
[RFC 7950] avoid using this construct, YANG module validation tools flag a 
warning if this construct is used, but implementations allow this if possible.

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

_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to