Re: [netconf] [Technical Errata Reported] RFC8525 (6484)

Jan Lindblad <janl@tail-f.com> Mon, 15 March 2021 16:53 UTC

Return-Path: <janl@tail-f.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D80A03A16B3 for <netconf@ietfa.amsl.com>; Mon, 15 Mar 2021 09:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79OSVKJ7Dk8k for <netconf@ietfa.amsl.com>; Mon, 15 Mar 2021 09:53:55 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id E06263A16B2 for <netconf@ietf.org>; Mon, 15 Mar 2021 09:53:54 -0700 (PDT)
Received: from [192.168.1.117] (213-67-237-150-no99.tbcn.telia.com [213.67.237.150]) by mail.tail-f.com (Postfix) with ESMTPSA id 6DEE91AE035B; Mon, 15 Mar 2021 17:53:53 +0100 (CET)
From: Jan Lindblad <janl@tail-f.com>
Message-Id: <B15F561D-206D-4BFA-8CE7-776BFCF3D732@tail-f.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A7F628A1-8A1F-4E2C-A9E2-2B4339739BE8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 15 Mar 2021 17:53:52 +0100
In-Reply-To: <MN2PR11MB43662E23EEE66A69BE7076FDB56C9@MN2PR11MB4366.namprd11.prod.outlook.com>
Cc: Andy Bierman <andy@yumaworks.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>, "warren@kumari.net" <warren@kumari.net>, "netconf@ietf.org" <netconf@ietf.org>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
References: <608B4604-1970-4BE3-85E5-565985A4EBF6@tail-f.com> <20210315.111826.1844702859879595481.id@4668.se> <E2DEF87C-F637-4FC6-9D03-47FA73197806@tail-f.com> <20210315.114630.905811507297421433.id@4668.se> <MN2PR11MB4366AA4D6AF92B353C0E14B5B56C9@MN2PR11MB4366.namprd11.prod.outlook.com> <20210315120259.2r7ae3vzfmv2uln5@anna.jacobs.jacobs-university.de> <CABCOCHSV+fN-wreswUnYuo8O++iFH_am_a8NOQQCZG8AfwpOEw@mail.gmail.com> <MN2PR11MB43662E23EEE66A69BE7076FDB56C9@MN2PR11MB4366.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/RKD6sGp8LnJVqRtl7pN9kxK2sKQ>
Subject: Re: [netconf] [Technical Errata Reported] RFC8525 (6484)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2021 16:53:57 -0000

Andy wrote:

> I strongly object to the introduction of YET ANOTHER module revision for the YANG library,
> just to fix something that has no impact on any real tools. 

I don't strongly object to making changes in YANG Library, but I think any changes on this fundamental level need to have substantial technical merit to warrant the cost.

> Only the first revision-stmt actually matters, and that is correct in this case.

If the import-by-revision-or-derived YANG extension proposed by the versioning dt is approved and published as RFC, the revision history will start to play a role in the interpretation of module contents. That may actually be an argument for correcting or reconciling the misrepresented date in the module at next the YANG Library change.

> On 15 Mar 2021, at 17:34, Rob Wilton (rwilton) <rwilton@cisco.com> wrote:
> 
> I still think that “Hold for Document Update” is the right outcome for this errata.  I.e., this is a valid problem and should be fixed if a new version of the module is published.
>  
> But I’m opposed to using an errata to change a YANG module published in an RFC.  That would mean that there are now two revisions of the YANG module with the same date but different content.

Now, that is a kind of change I would strongly object to.

/jan


>  
> From: Andy Bierman <andy@yumaworks.com> 
> Sent: 15 March 2021 16:17
> To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>de>; Rob Wilton (rwilton) <rwilton@cisco.com>om>; Martin Björklund <mbj+ietf@4668.se>se>; janl@tail-f.com; warren@kumari.net; netconf@ietf.org
> Subject: Re: [netconf] [Technical Errata Reported] RFC8525 (6484)
>  
>  
>  
> On Mon, Mar 15, 2021 at 5:03 AM Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de <mailto:j.schoenwaelder@jacobs-university.de>> wrote:
> On Mon, Mar 15, 2021 at 11:57:37AM +0000, Rob Wilton (rwilton) wrote:
> > 
> > I'm wondering whether we should consider doing an RFC8525-bis document with the specific aim of addressing this?
> >
> 
> This sounds like an overkill solution, an errata seems the way to
> handle a little bug fix like this. I very doubt this affects many
> implementations...
> 
>  
>  
> I strongly object to the introduction of YET ANOTHER module revision for the YANG library,
> just to fix something that has no impact on any real tools.  Only the first revision-stmt actually
> matters, and that is correct in this case.
>  
> This bug should be handled with a simple Errata correcting the revision history.
> The data string is clearly wrong and changing it has no impact at all on
> modules that import ietf-yang-library.
>  
>  
> /js
>  
> Andy
>  
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://www.jacobs-university.de/ <https://www.jacobs-university.de/>>
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org <mailto:netconf@ietf.org>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>