[netmod] [Errata Rejected] RFC6991 (7647)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 12 January 2024 14:45 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 46949C14F60A; Fri, 12 Jan 2024 06:45:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WU7HD2Q2ADpj; Fri, 12 Jan 2024 06:45:08 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B73AC14CE2E; Fri, 12 Jan 2024 06:45:08 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5FBD21B65DC9; Fri, 12 Jan 2024 06:45:08 -0800 (PST)
To: david.martinezgarci@upm.es, j.schoenwaelder@jacobs-university.de
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: <20240112144508.5FBD21B65DC9@rfcpa.amsl.com>
Date: Fri, 12 Jan 2024 06:45:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/e3pAoy3YCeuDIePJuulQcn-qc0Y>
Subject: [netmod] [Errata Rejected] RFC6991 (7647)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 12 Jan 2024 14:45:09 -0000

The following errata report has been rejected for RFC6991,
"Common YANG Data Types".

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

--------------------------------------
Status: Rejected
Type: Technical

Reported by: David Martínez García <david.martinezgarci@upm.es>
Date Reported: 2023-09-18
Rejected by: Robert Wilton (IESG)

Section: 3

Original Text
-------------
[...]

typedef object-identifier-128 {
       type object-identifier {

[...]

(and other typedefs that appear in the latest revisions of the module)

Corrected Text
--------------
[...]

typedef object-identifier-128 {
       type yang:object-identifier {

[...]

(and other typedefs that appear in the latest revisions of the module)

Notes
-----
In Section 3, the textual definition of the "ietf-yang-types" module presents, in my opinion, inconsistencies when defining typedefs that point to other typedefs in the same module: sometimes the value for the "type" key contains the prefix of the module and sometimes not. Please, see the example attached. This can also be applied to other typedefs defined in the latest revisions of the module, such as "date-no-zone" and "time-no-zone". I think this should be addressed to provide clarification and consistency, and thus can be extended to other modules and the YANG standard as well. Thanks for your time.
 --VERIFIER NOTES-- 
As discussed on the NETMOD mailing list.: This YANG isn't wrong, and generally I don't think that YANG modules use (or should use) prefixes for types defined in the same module that they are used.

I agree that there is some inconsistency in RFC 6991 in using the "yang:" prefix, but that has been fixed by the author for the next revision of this YANG module.

--------------------------------------
RFC6991 (draft-ietf-netmod-rfc6021-bis-03)
--------------------------------------
Title               : Common YANG Data Types
Publication Date    : July 2013
Author(s)           : J. Schoenwaelder, Ed.
Category            : PROPOSED STANDARD
Source              : Network Modeling
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG