Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ietf-dslite@2016-11.14 is not flagged as (at least) a warning #296

Open
bclaise opened this issue Jan 3, 2017 · 0 comments
Open

ietf-dslite@2016-11.14 is not flagged as (at least) a warning #296

bclaise opened this issue Jan 3, 2017 · 0 comments

Comments

@bclaise
Copy link

bclaise commented Jan 3, 2017

Hi,

draft-ietf-softwire-dslite-yang-01.txt:
file "ietf-dslite@2016-11.14"

This should be:
file "ietf-dslite@2016-11-14"

This should be flagged by pyang.

From RFC 7950:

5.2. File Layout

YANG modules and submodules are typically stored in files, one
"module" or "submodule" statement per file. The name of the file
SHOULD be of the form:

 module-or-submodule-name ['@' revision-date] ( '.yang' / '.yin' )

"module-or-submodule-name" is the name of the module or submodule,
and the optional "revision-date" is the latest revision of the module
or submodule, as defined by the "revision" statement (Section 7.1.9).

7.1.9. The "revision" Statement

The "revision" statement specifies the editorial revision history of
the module, including the initial revision. A series of "revision"
statements detail the changes in the module's definition. The
argument is a date string in the format "YYYY-MM-DD", followed by a
block of substatements that holds detailed revision information. A
module SHOULD have at least one "revision" statement. For every
published editorial change, a new one SHOULD be added in front of the
revisions sequence so that all revisions are in reverse chronological
order.

Then the ABNF

revision-date = date-arg-str

...

;; Date

date-arg-str = < a string that matches the rule >
< date-arg >

date-arg = 4DIGIT "-" 2DIGIT "-" 2DIGIT

Regards, B.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants