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

Andy Bierman <andy@yumaworks.com> Wed, 31 May 2023 15:23 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 83316C151533 for <netmod@ietfa.amsl.com>; Wed, 31 May 2023 08:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_BLOCKED=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 91XiRhrg4GsB for <netmod@ietfa.amsl.com>; Wed, 31 May 2023 08:22:58 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 3731EC15199B for <netmod@ietf.org>; Wed, 31 May 2023 08:22:58 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2af24ee004dso62778981fa.0 for <netmod@ietf.org>; Wed, 31 May 2023 08:22:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1685546576; x=1688138576; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=4K2qo7tlphyeoBKSKZQGKB8M1HVSiqXNGYPglFxendI=; b=gsqHNFVXfdSAEI7ToF0uuGS5H3FuCGdDOhXWnTITvTc9a+urPSnKdQ8tR2CjitVvCa b3EW4Z6rshDj/ffitjrLNujd6TQKp825z18XoiaIK3PQqru96/cTihGBdRMvUeVfFYs0 V97JRY8gU6CHjEdsNTGZ8OSP/XtxoHpycHgGLjUa48arklJ79pHeBdYI3fnhZVJ+KMIw JACRzjS1NiNaj4qKAI05K5ejjJUGgbv0YaZF+667dAscu/pqGRkQ12r0d0KDpkVYMki1 GhC5Hh8fatc1WLktwcDmNSIwUFh9FSiDpU1PIFaSTc5sgCp1tRG7gAsYOzWvhys9VW0U piqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685546576; x=1688138576; h=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=4K2qo7tlphyeoBKSKZQGKB8M1HVSiqXNGYPglFxendI=; b=W9zrnNGinELusksGCznlz60ecOu+4XkcCdMCel+j5oCjyOuphFAECO2rRfmPDKwaNI 0YcNyJn2ZdCeLSwEVYz3BBc+gFTrTtbCNjmRViEhAuXcXgtXqiV9Q0/5gGNlQtjSH7tt dMRvrNiRONeS+XFpGl4kRxcjHQXg8/F+B+u+Y7YGF2uTQY46U5eDrZvx6DQDY9iu1nxZ XOWHKofjjWP2fSXMQcBpAZw7EQ8gsDGU6YV7PHC09BttIXD2efLlwmWmPj6vaNky0TC3 R6vhLcTanupWMyhbh26OuvKwdJmnd6BLrwRLMVlrLJiSdXZo2S7UqWL+9voSEaUyf75P QNOQ==
X-Gm-Message-State: AC+VfDxhyFdPd86AaPFAftfQDf8xkhggO1En+9hhbVt1JOdkuGQD78RQ qXBdLuLEkKW5dphIMDIQM8h55q0WIUrVsoGDpTY+PQ==
X-Google-Smtp-Source: ACHHUZ7XSr0jWhM6ypwpEOP0/jRQdK/JMctGoy1ayPU0S4Gen4n7RteHCRlC/8L/cF1ah5gvBRmTFnEY5E/kOeOm18o=
X-Received: by 2002:a2e:9d53:0:b0:2ab:19a0:667b with SMTP id y19-20020a2e9d53000000b002ab19a0667bmr2599390ljj.0.1685546576264; Wed, 31 May 2023 08:22:56 -0700 (PDT)
MIME-Version: 1.0
References: <01000187fd8e0407-84bd7e7b-ede3-43d8-a9b3-5d4d0a915509-000000@email.amazonses.com> <jr5nepvspm3kpoxbv6dpxwi234ggjuthvckeerj2hb3g3qdc6x@4o42ngfbw72f> <12cd6ad9-e384-7cbc-d14d-fdf58cdbb0df@hq.sk> <6fdiqbrvqqsrcddq4c4z7kpwnl7rublqizqoija23penfnuvbk@heqvysdnhuvp> <CABCOCHSFmMQDZZa-u8Ycm75aGarV+hfEakmnE_OUp0ODftzELg@mail.gmail.com>
In-Reply-To: <CABCOCHSFmMQDZZa-u8Ycm75aGarV+hfEakmnE_OUp0ODftzELg@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 31 May 2023 08:22:44 -0700
Message-ID: <CABCOCHS3QLSdzXNfRsd_0irwpJ6T9STsOgR3fuKmHjaqh=2uaw@mail.gmail.com>
To: Jürgen Schönwälder <jschoenwaelder@constructor.university>, Robert Varga <nite@hq.sk>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ee55a905fcfee446"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/lwoGDX5uq9RBe-I8L-gKH0IvFms>
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: Wed, 31 May 2023 15:23:02 -0000

On Wed, May 31, 2023 at 3:12 AM Andy Bierman <andy@yumaworks.com> wrote:

>
>
> On Wed, May 31, 2023 at 12:50 AM Jürgen Schönwälder
> <jschoenwaelder@constructor.university> wrote:
>
>> On Wed, May 31, 2023 at 02:13:11AM +0200, Robert Varga wrote:
>> > On 30/05/2023 20.28, Jürgen Schönwälder wrote:
>> > >    It is unclear what "identical" means here. If two people extract a
>> > >    module from an RFC, they may not end up with identical byte
>> > >    sequences. So does white space matter when we talk about MUST be
>> > >    identical? What about comments? The problem is that the IETF still
>> > >    publishes YANG modules in RFCs instead of files.
>> >
>> > As for RFC vs. files, the mechanics of extracting of files from RFCs
>> seems
>> > to be well established, plus it is an IETF-owned cron job which updates
>> > https://github.com/YangModels/yang/tree/main/standard/ietf/RFC -- so I
>> would
>> > (and I actually do) assume that is the normative source of byte-exact
>> files.
>>
>> I have YANG modules that were extracted years ago using some version
>> of smistrip of the past. Do you believe my files extracted back then
>> are byte-by-byte equivalent to what some cron job produces on some
>> github repo somewhere today? Do you guarantee that the software behind
>> the cron job will never ever be updated causing it to produce
>> something where white space may differ?
>>
>>
> The rfcstrip tool has been adding extra '\n' characters to YANG modules
> for years.
> In fact, there is not even one YANG module on a repo somewhere that is a
> byte-exact copy of the RFC version.
>
>
I checked some recent YANG modules, and the extra newline problem has been
fixed.
I am finding a different issue where trailing whitespace in the author's
YANG file on github
is removed from the YangModels repo version.  E.g.
ietf-netconf-server@2023-04-17

This should be a normal non-issue, but the new proposal requires a new
revision date
every time a meaningless space is added or removed from the file. Not sure
what problem
that is trying to solve.


/js
>>
>>
> Andy
>
>
>
>> --
>> Jürgen Schönwälder              Constructor University Bremen gGmbH
>> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
>> Fax:   +49 421 200 3103         <https://constructor.university/>
>>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>>
>