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

Carsten Bormann <cabo@tzi.org> Mon, 05 June 2023 09:11 UTC

Return-Path: <cabo@tzi.org>
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 17CD2C151985 for <netmod@ietfa.amsl.com>; Mon, 5 Jun 2023 02:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 YxNbKNemYOyp for <netmod@ietfa.amsl.com>; Mon, 5 Jun 2023 02:11:24 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 7115CC14CF05 for <netmod@ietf.org>; Mon, 5 Jun 2023 02:11:23 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4QZSX861SLzDCg9; Mon, 5 Jun 2023 11:11:20 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <xcnchfz3p3mjgfhy7qlqtujgb7qtzgq44c4axor2vwzr6b3vex@aywzozhx5j2k>
Date: Mon, 05 Jun 2023 11:11:20 +0200
Cc: Robert Varga <nite@hq.sk>, "netmod@ietf.org" <netmod@ietf.org>
X-Mao-Original-Outgoing-Id: 707649080.371501-8dd98935f5dedc7244d3b406c8d42e28
Content-Transfer-Encoding: quoted-printable
Message-Id: <01DB83F4-0B6B-4F63-9E6E-1A4161204F3A@tzi.org>
References: <01000187fd8e0407-84bd7e7b-ede3-43d8-a9b3-5d4d0a915509-000000@email.amazonses.com> <jr5nepvspm3kpoxbv6dpxwi234ggjuthvckeerj2hb3g3qdc6x@4o42ngfbw72f> <12cd6ad9-e384-7cbc-d14d-fdf58cdbb0df@hq.sk> <6fdiqbrvqqsrcddq4c4z7kpwnl7rublqizqoija23penfnuvbk@heqvysdnhuvp> <985d7c5a-4b16-280e-c1d7-ee1e61edcf9e@hq.sk> <vln6ljsf7d3esxz2szeglscueacga746pnflg2exhlgzss6h42@cuar6zkh74wx> <E356E06A-47D7-4009-897E-CF73408F6353@tzi.org> <xcnchfz3p3mjgfhy7qlqtujgb7qtzgq44c4axor2vwzr6b3vex@aywzozhx5j2k>
To: Jürgen Schönwälder <jschoenwaelder@constructor.university>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Y8XuYJ2Zi4c7DcL6PTbMxzOCOyA>
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: Mon, 05 Jun 2023 09:11:29 -0000

On 2023-06-04, at 19:42, Jürgen Schönwälder <jschoenwaelder@constructor.university> wrote:
> 
>> 
>> I’m not sure I understand the current discussion, but wouldn't
>> 
>> curl -s https://www.rfc-editor.org/rfc/rfc9127.xml | xmlstarlet sel -T -t -v "//sourcecode[@name='ietf-bfd-types@2021-10-21.yang']/text()”
>> 
>> be considered an authoritative source for that YANG file in that RFC?
>> 
> 
> There are many ways to extract YANG modules from RFCs and the results
> they produce are not necessarily byte-level identical.

Thanks.  This particular method only works for RFC 8650 onwards, but could be considered canonical for those.  As XML is neutral with respect to the bytes that constitute a line break, if byte level determinism is required, the canonical form of a line break (#xA, i.e. a bare LF) should be assumed.  There also is https://github.com/ietf-tools/xml2rfc/issues/986 (YANG files extracted this way typically start with an empty line).

> So far this was
> not considered necessary. Before people go and try to engineer a
> solution, it may be useful to understand why solving this problem is
> relevant or important.

Right.  I wasn’t about to engineer a solution, but more interested in finding out what people consider the authoritative solution today, and I now have a useful answer.

Grüße, Carsten