Re: [netmod] YANG Versioning Weekly Call Minutes - 2021-06-08

On Tue, Jun 8, 2021 at 11:00 AM Sterne, Jason (Nokia - CA/Ottawa) <
jason.sterne@nokia.com> wrote:

> Hi Andy,
>
>
>
> Nothing in RFC7950 says duplicates are allowed. We don't plan to change
> that (or particularly say anything about it) in any of our YANG revision
> work.
>
>
>
> But maybe in YANG NEXT, **if** a Semver-like revision label was adopted
> as the main identifier (and revision date just becomes a non-key
> attribute), i.e. yang library was changed to use revision label instead of
> revision date, then two versions could be allowed on the same date.  But
> that's for a YANG NEXT discussion.
>

If we were having a YANG-Next discussion, I would certainly agree that
YANG 2.0 should officially use module-name + revision-label and not use
revision-date as a module identifier at all.

Although non-intuitive, creating a new version of YANG is actually more
backward-compatible than continually adding ad-hoc bits and pieces to YANG
1.1.
A new language version allows NBC changes to be clearly identified,
and lots of NBC changes (like revision-label) are needed to take YANG to
the next level.
Attempts to fix major problems indirectly (e.g. YANG extensions) will fail
in the long run.

Good thing we are not discussing YANG-next...

>
> Jason
>

Andy

>
>
> *From:* Andy Bierman <andy@yumaworks.com>
> *Sent:* Tuesday, June 8, 2021 1:49 PM
> *To:* Sterne, Jason (Nokia - CA/Ottawa) <jason.sterne@nokia.com>
> *Cc:* netmod@ietf.org
> *Subject:* Re: [netmod] YANG Versioning Weekly Call Minutes - 2021-06-08
>
>
>
>
>
>
>
> On Tue, Jun 8, 2021 at 10:39 AM Sterne, Jason (Nokia - CA/Ottawa) <
> jason.sterne@nokia.com> wrote:
>
> YANG Versioning Weekly Call Minutes - 2021-06-08
>
>
>
> Submodule vs Module in module versioning draft:
>
> - avoid 'artifact', put "submodule or module" everywhere it is applicable
>
> - Reshad: add "or submodules" in most places.
>
>
>
> Non duplicate revision dates:
>
> - revision-label is just another label for that revision date
>
> - we won't say anything in our drafts about non-duplicate revision dates
> in a revision history. This is something for YANG NEXT.
>
>
>
>
>
>
>
> Can you find any text in RFC 7950 that says that a module
>
> with a specific name and revision date can refer to multiple YANG modules?
>
> It seems like the opposite is true -- that if the name and revision date
> are the
>
> same then they refer to the same specific module.
>
>
>
>
>
> Andy
>
>
>
>
>
> YANG SemVer Draft - IETF 110 feedback
>
>
>
> Raise github issue in verdt *and* against pyang to flag when a module or
> submodule is missing a revision label
>
>
>
> Raise github issue to review the IANA guidelines (in our 2 drafts) with
> IANA folks
>
>
>
> We discussed pre-release version precedence
>
> - can't assume precedence of pre-release versions
>
> - wipe out the pre-release revision history when publishing the final
> version (SHOULD) ?  or when publishing each pre-release version? Put this
> guidance in Module Revision Handling (instead of Semver ?)
>
> - Joe to propose wording
>
>
>
> Rgds,
>
> Jason
>
>
>
> ----------------------------------------------
>
> 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
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>
>