RFC 7950, "The YANG 1.1 Data Modeling Language", August 2016

Note: This RFC has been updated by RFC 8342, RFC 8526

Errata ID: 6031
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Radek Krejci
Date Reported: 2020-03-27
Held for Document Update by: Robert Wilton
Date Held: 2020-05-04

Section 9.9.3 says:

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

It should say:

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.

Report New Errata