[babel] YANG errors in datatracker

Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 19 November 2019 06:00 UTC

From: Mahesh Jethanandani <mjethanandani@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_35232C3D-0587-48BF-A0EE-185B54246AC6"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <E419D6CE-8F99-450D-8549-846DB1BEE272@gmail.com>
Date: Tue, 19 Nov 2019 14:00:00 +0800
To: Babel at IETF <babel@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/4Z_ZmyJoOZAr-jLXJGrMBjXXonE>
Subject: [babel] YANG errors in datatracker
Precedence: list

Hi Donald,

To the question of the two errors being reported in data tracker for the Babel YANG model, I just wanted to confirm that those errors are tooling errors. 

ietf-babel@2019-10-18.yang:96: error: keyword "if-feature" not in canonical order (see RFC 6020, Section 12)
ietf-babel@2019-10-18.yang:103: error: keyword "if-feature" not in canonical order (see RFC 6020, Section 12)

The ABNF grammar for YANG in RFC 7950 (updated version of RFC 6020) says the following for the identity statement where these errors are reported.

identity-stmt       = identity-keyword sep identifier-arg-str optsep
                         (";" /
                          "{" stmtsep
                              ;; these stmts can appear in any order
                              *if-feature-stmt
                              *base-stmt
                              [status-stmt]
                              [description-stmt]
                              [reference-stmt]
                          "}") stmtsep


It is clear that the if-feature statement can appear before/after base-stmt per the above grammar, and as such these errors are tooling errors. I believe that it has been fixed in pyang, but that version of pyang has not been published.

Thanks

Mahesh Jethanandani
mjethanandani@gmail.com

[babel] YANG errors in datatracker Mahesh Jethanandani
Re: [babel] YANG errors in datatracker Donald Eastlake