You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"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.
The text was updated successfully, but these errors were encountered:
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" 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.
The text was updated successfully, but these errors were encountered: