YANG Versioning Weekly Call Minutes - 2021-03-23
Try to focus on a smaller number of issues in parallel and drive them to 100%
completion (text in draft).
Agenda bashing:
- recap of feedback received for issues presented in IETF110
Actions:
- review draft text for state BC/NBC rules
Whitespace:
Add to 3.1 (Reshad):
As per RFC 7950, all published revisions of a module are given a new unique
revision date. This applies even for module revisions containing only changes
to any whitespace, formatting, comments or line endings (e.g. DOS vs UNIX).
In 3.3 add the word "file" here:
A specific revision-label identifies a specific revision (variant) of
the module. If two YANG modules contain the same module name and the
same revision-label (and hence also the same revision-date) in their
latest revision statement, then the *file* contents of the two modules,
including the revision history, MUST be identical.
---------------------------------------
Module with history that has a mix of revision-labels and nothing.
- i.e. not every version must have a revision-label (there MUST be only be a
single scheme, 3.3.1)
- current text in Module Versioning draft 3.3 is good enough (it says "MAY"
have a revision-label)
---------------------------------------
Update the first parapgraph of 3.3.1 as follows:
The OPTIONAL "rev:revision-label-scheme" extension statement is used to
indicate which revision-label scheme a module or submodule uses. There MUST
NOT be more than one revision label scheme in a module or submodule.
The mandatory argument to this extension statement:
-----------------------------------
YANG module: clarify that only a single revision label scheme statement can
exist in a module or submodule. There may be 0 or 1 revision label scheme
statements.
The statement MUST only be a substatement to the YANG module or submodule
statement.
Y1: Zero or one rev:revision-label-scheme statements per module or
submodule is allowed.
Y2: There MUST be zero or one rev:revision-label-scheme statements
per module or submodule
Y3: There MUST be at most one rev:revision-label-scheme statements in
a module or submodule.
Y4: Zero or one rev:revision-label-scheme statements are allowed per
module or submodule.
Decision: Y3
A next step: see if there are Github issues that can just be closed now.
----------------------------------------------
Weekly webex call details:
Meeting number (access code): 171 069 0374
Meeting password: semver?
Occurs every Tuesday effective Tuesday, September 1, 2020 until Tuesday, August
24, 2021 from 9:00 AM to 10:00 AM, (UTC-04:00) Eastern Time (US & Canada)
9:00 am | (UTC-04:00) Eastern Time (US & Canada) | 1 hr
https://ietf.webex.com/ietf/j.php?MTID=ma7627a2ae7b770537cff5f5b89293c70
Tap to join from a mobile device (attendees only)
+1-650-479-3208,,1710690374## Call-in toll number (US/Canada)
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
