RFC 6991, "Common YANG Data Types", July 2013

Errata ID: 7647
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: David Martínez García
Date Reported: 2023-09-18
Rejected by: Robert Wilton
Date Rejected: 2024-01-12

Section 3 says:

[...]

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

[...]

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

It should say:

[...]

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.

Report New Errata