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

Jan Lindblad <janl@tail-f.com> Mon, 15 March 2021 10:32 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 0B8933A0ADA for <netconf@ietfa.amsl.com>; Mon, 15 Mar 2021 03:32:32 -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, RCVD_IN_DNSWL_BLOCKED=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 Igh5waUTQC5L for <netconf@ietfa.amsl.com>; Mon, 15 Mar 2021 03:32:30 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3C13A0AD7 for <netconf@ietf.org>; Mon, 15 Mar 2021 03:32:30 -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 0B8E21AE035B; Mon, 15 Mar 2021 11:32:29 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Jan Lindblad <janl@tail-f.com>
In-Reply-To: <20210315.111826.1844702859879595481.id@4668.se>
Date: Mon, 15 Mar 2021 11:32:28 +0100
Cc: rwilton=40cisco.com@dmarc.ietf.org, rfc-editor@rfc-editor.org, netconf@ietf.org, warren@kumari.net
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2DEF87C-F637-4FC6-9D03-47FA73197806@tail-f.com>
References: <20210315.102411.704461003596497032.id@4668.se> <MN2PR11MB4366C5416AE4DB8CCF3FE7C3B56C9@MN2PR11MB4366.namprd11.prod.outlook.com> <608B4604-1970-4BE3-85E5-565985A4EBF6@tail-f.com> <20210315.111826.1844702859879595481.id@4668.se>
To: =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/wiGNQbaqvzfsVWxeqPCoipdwN5k>
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 10:32:32 -0000

Martin,

>> Rob, Martin,
>> 
>> Wouldn't changing the revision date be a massively
>> non-backwards-compatible change?
> 
> Note that this is in the revision history list.

I understand. Do you consider changing the revision history a backwards compatible change that clients, servers and tools should reasonably be able to cope with?

>> Anyone might be importing this module by revision, and tools could be hardcoded towards the revision date, given that this is a pretty fundamental module.
>> 
>> What is the (technical) benefit of changing the date?
> 
> The idea is that if we ever do a new version of this module, we fix
> the revision history list in that new version.

Yes, the description of the idea was clear. I see some potential trouble doing this, and so far I haven't been able to think of any use case that would benefit from a change. Is there any?

Correct information is always nice, but changing module identification data also leads to confusion. I don't think we should change it unless someone can point to some benefits that outweigh the cost.

Best Regards,
/jan


>>> Hi Martin,
>>> 
>>> I agree, hold for doc update seems appropriate.
>>> 
>>> Any other comments?
>>> 
>>> Regards,
>>> Rob
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Martin Björklund <mbj+ietf@4668.se>
>>>> Sent: 15 March 2021 09:24
>>>> To: rfc-editor@rfc-editor.org
>>>> Cc: andy@yumaworks.com; mbj+ietf@4668.se; j.schoenwaelder@jacobs-
>>>> university.de; kent+ietf@watsen.net; Rob Wilton (rwilton)
>>>> <rwilton@cisco.com>om>; warren@kumari.net; mjethanandani@gmail.com;
>>>> netconf@ietf.org
>>>> Subject: Re: [netconf] [Technical Errata Reported] RFC8525 (6484)
>>>> 
>>>> Hi,
>>>> 
>>>> Wow, this is obviously a bug.
>>>> 
>>>> I am not sure it can be fixed with an errata however.  Perhaps "hold
>>>> for document update"?
>>>> 
>>>> 
>>>> /martin
>>>> 
>>>> 
>>>> RFC Errata System <rfc-editor@rfc-editor.org> wrote:
>>>>> The following errata report has been submitted for RFC8525,
>>>>> "YANG Library".
>>>>> 
>>>>> --------------------------------------
>>>>> You may review the report below and at:
>>>>> https://www.rfc-editor.org/errata/eid6484
>>>>> 
>>>>> --------------------------------------
>>>>> Type: Technical
>>>>> Reported by: Jernej Tuljak <jernej.tuljak@mg-soft.si>
>>>>> 
>>>>> Section: 4
>>>>> 
>>>>> Original Text
>>>>> -------------
>>>>>    revision 2016-04-09 {
>>>>>      description
>>>>>        "Initial revision.";
>>>>>      reference
>>>>>        "RFC 7895: YANG Module Library";
>>>>>    }
>>>>> 
>>>>> Corrected Text
>>>>> --------------
>>>>>    revision 2016-06-21 {
>>>>>      description
>>>>>        "Initial revision.";
>>>>>      reference
>>>>>        "RFC 7895: YANG Module Library";
>>>>>    }
>>>>> 
>>>>> Notes
>>>>> -----
>>>>> Initial revision of ietf-yang-library YANG module was 2016-06-21, not
>>>> 2016-04-09.
>>>>> 
>>>>> Instructions:
>>>>> -------------
>>>>> This erratum is currently posted as "Reported". If necessary, please
>>>>> use "Reply All" to discuss whether it should be verified or
>>>>> rejected. When a decision is reached, the verifying party
>>>>> can log in to change the status and edit the report, if necessary.
>>>>> 
>>>>> --------------------------------------
>>>>> RFC8525 (draft-ietf-netconf-rfc7895bis-07)
>>>>> --------------------------------------
>>>>> Title               : YANG Library
>>>>> Publication Date    : March 2019
>>>>> Author(s)           : A. Bierman, M. Bjorklund, J. Schoenwaelder, K.
>>>> Watsen, R. Wilton
>>>>> Category            : PROPOSED STANDARD
>>>>> Source              : Network Configuration
>>>>> Area                : Operations and Management
>>>>> Stream              : IETF
>>>>> Verifying Party     : IESG
>>>>> 
>>>>> _______________________________________________
>>>>> netconf mailing list
>>>>> netconf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/netconf
>>> 
>>> _______________________________________________
>>> netconf mailing list
>>> netconf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netconf
>>> 
>>