[netmod] [Errata Held for Document Update] RFC7950 (6031)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 04 May 2020 10:02 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18DC23A0771; Mon, 4 May 2020 03:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.999, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gEKsuMW2XGVR; Mon, 4 May 2020 03:02:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 907563A076F; Mon, 4 May 2020 03:02:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E2E24F406F5; Mon, 4 May 2020 03:02:42 -0700 (PDT)
To: rkrejci@cesnet.cz, mbj@tail-f.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rwilton@cisco.com, iesg@ietf.org, netmod@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20200504100242.E2E24F406F5@rfc-editor.org>
Date: Mon, 4 May 2020 03:02:42 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/anxV18dmwIwIpoM7TJjAMnC71fE>
Subject: [netmod] [Errata Held for Document Update] RFC7950 (6031)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2020 10:02:47 -0000

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