Re: [netmod] Joint WGLC on "semver" and "module-versioning" drafts

Andy Bierman <andy@yumaworks.com> Thu, 25 May 2023 00:29 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 652B1C151990 for <netmod@ietfa.amsl.com>; Wed, 24 May 2023 17:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Zl9oGevUVCl for <netmod@ietfa.amsl.com>; Wed, 24 May 2023 17:29:41 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEE29C15198F for <netmod@ietf.org>; Wed, 24 May 2023 17:29:41 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-64a9335a8e7so321590b3a.0 for <netmod@ietf.org>; Wed, 24 May 2023 17:29:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1684974581; x=1687566581; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zE0yzXN+MbxEnwmC0iZwQhEt2THyBqvjP6sqgB5VTnk=; b=ewU06gGp6xjm/6pj1cAWhwhNs3VKTc9oO+udtJfxzzoQQCrP/9756FX5sPz7yZK/MV fL1SAzbPp3grLmvWkDGjXDk2S4G6uAj+DeUsKIuNRT9vaMY26a6wOJ3KsxCEhp3QBN3I 4CGlLSbxQwyrTiWLWQ7xYOlJPXfpgyfvD27RWatiRG70XBe8kNCmxSqt/nerzliYvT0K XhSAUVrkFsi4M0lj1vFurLZMnBlyb71WwfKBkBbPijpNElO1CH/tCa0ceVyZeowzyGtp fM6rM3cZJdKT5NyX/LJSEfVXdyinjduFaRmioPHNmcbmBLp9+tdhrO5sDF3BtL2eugeU bNPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684974581; x=1687566581; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zE0yzXN+MbxEnwmC0iZwQhEt2THyBqvjP6sqgB5VTnk=; b=Kjj/iDO4H0tMPq2QOta1bmbFjcyQs9tugQ3g6gDKvKrrKIjt2ctrP5n5q3rPJyq45Z xxCnJrNEZ4kCbynTpczk0KBTyvagJerelRyBf+R/qenA99+6SX0osq8G2IXfK1uh0RAW +u7ABtyJRgvOtVkuGg4lo5N9ww3z4X7ZO8qLb4K+0pF6CJdajySpfeyiPwpXGahe29Cg IckPOPhZi+Zlqr7D9uW29l/oqrRmA7BwKvt3hT0l9ptl/dvtIWc/BuYSr/EAkdm+SyEC s0Az/g4PAnSDWsnvtkTBeEaFGArp1hde30HHe+RP4cLtI1Wri2HhUh5WvJon0er92nJu eFsA==
X-Gm-Message-State: AC+VfDxUQEK0P8VZhQypbAvz9Dzik1GnhPnRvKA4dtxML06h4aWBpo9C OsMsJTEvLdJ5hUNAMfjF2Fgm57BU0Z1NQkjo/qlhWA==
X-Google-Smtp-Source: ACHHUZ5ef0WmeBTG2EbMyfpaH9c5mnUJyT61ogrVm64RZ+opdSMW1f4uQSjnF5jHsut42tsf0iXex2pE/BBl3WrRWQ0=
X-Received: by 2002:a05:6a20:12d1:b0:10e:3131:222b with SMTP id v17-20020a056a2012d100b0010e3131222bmr1098310pzg.26.1684974580729; Wed, 24 May 2023 17:29:40 -0700 (PDT)
MIME-Version: 1.0
References: <01000187fd8e0407-84bd7e7b-ede3-43d8-a9b3-5d4d0a915509-000000@email.amazonses.com> <af6b37a6-a439-adfc-0738-e2fc8e48b07e@hq.sk>
In-Reply-To: <af6b37a6-a439-adfc-0738-e2fc8e48b07e@hq.sk>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 24 May 2023 17:29:28 -0700
Message-ID: <CABCOCHQ2eGHA-NkGNScEJ9mEbCRT0TYUGzbpsche064qagdsmw@mail.gmail.com>
To: Robert Varga <nite@hq.sk>
Cc: Kent Watsen <kent+ietf@watsen.net>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000057216505fc79b7f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pbs-f8VHMYfPinPrrrmUoXKL764>
Subject: Re: [netmod] Joint WGLC on "semver" and "module-versioning" drafts
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 May 2023 00:29:45 -0000

On Tue, May 16, 2023 at 11:10 AM Robert Varga <nite@hq.sk> wrote:

> On 09/05/2023 00.49, Kent Watsen wrote:
> > Dear NETMOD WG,
> >
> > This message begins a joint two-week WGLC for
> draft-ietf-netmod-yang-semver-11 and
> draft-ietf-netmod-yang-module-versioning-09
> >   ending on Monday, May 22nd.  Neither draft has IPR declared.  Here are
> the direct links to the HTML version for these drafts:
> >
> >     -
> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-semver-11
> >     -
> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-module-versioning-09
> >
> > Positive comments, e.g., "I've reviewed this document and believe it is
> ready for publication", are welcome!  This is useful and important, even
> from authors.  Objections, concerns, and suggestions are also welcomed at
> this time.
>
> Hello, I have reviewed the module-versioning draft and overall it looks
> fine (well, aside from the incoming pain :), but we'll cope with that in
> due time).
>
> One concern I have is with
>
> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-module-versioning-09#name-file-names,
>
> which changes file naming.
>
> Previously the canonical file name included revision -- and now that
> information is lost. While I understand the desire for descriptive
> names, which are a boon for humans, the until the entire ecosystem
> adopts labels, this change is either-or -- and hence tools have to pick
> which metadata is more important: label or revision.
>
> Would it be possible to define a format which contains *both* the label
> and revision, so as not to pick favorites?
>
>

This is an example of an important detail that could be solved differently
if a new YANG language version was used.  In YANG 1.1 the revision-date is
optional.
In YANG 1.2, both the revision-date and label could be mandatory.

It is common practice to release YANG changes in multiple release trains
on the same day.  So the {date, label} is the unique identifier for the
YANG file,
not some combination of optional parts.  IMO the file name you suggest
should
be the mandatory-to-implement canonical file name format for YANG 1.2.

I understand it could be a bad idea to start over with the yang-next list
and "work on YANG 1.2".
IMO there are only a small number of must-haves on that list, and most
issues
could be deferred. YANG 1.2 could be derived from these 2 drafts + a small
number of yang-next issues.

In the current form, I do not agree that the YANG module revision update
rules
should be updated without changing the yang-version value.


Thanks,
> Robert
>


Andy


> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>