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

Martin Björklund <mbj+ietf@4668.se> Mon, 15 March 2021 10:18 UTC

Return-Path: <mbj+ietf@4668.se>
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 5F1613A09F5 for <netconf@ietfa.amsl.com>; Mon, 15 Mar 2021 03:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.121
X-Spam-Level:
X-Spam-Status: No, score=-0.121 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, PDS_NAKED_TO_NUMERO=1.999, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=4668.se header.b=JAneo+F8; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CHfmPxW/
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 DLmHvrpe6ROD for <netconf@ietfa.amsl.com>; Mon, 15 Mar 2021 03:18:32 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9811F3A09EA for <netconf@ietf.org>; Mon, 15 Mar 2021 03:18:32 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id D47E519F0; Mon, 15 Mar 2021 06:18:30 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 15 Mar 2021 06:18:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=4668.se; h=date :message-id:to:cc:subject:from:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=fm1; bh= g/3HBwugNCF6mO4s18WC0nBgDuWluqQzy5xFzIWABBA=; b=JAneo+F8X2Bz2VOP vLHsZVeVezesFWveUqqvb0CHniaFa/hkTKh1DOoT19yB0iwvLJ3D9KJ0e9vlTU93 2gtoxKsdYS6fZLXNr9fK3UlbQ2c7XUvtQAtT9HEYRH8p8OlOyPDHDk/8Bj3bBdKP an2HIoh/kNcrDJNxKkvLnjEbgZSIGtpMJiwScNCXAOmjnfWSgVz7PxoGpMKXwzSu PN0No3EKcVzwFKM0Dll2WaaDnjYaQxk/DYfej6cjb5r6i2sOY4w043bxMnMPLEPB uxi2sEDzTyJ07sIGMQeh4G98edBaeITVs5daEsgYbIzYzeqSqDFMnp6lOPMtgZH4 CgIZbA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=g/3HBwugNCF6mO4s18WC0nBgDuWluqQzy5xFzIWAB BA=; b=CHfmPxW/QBEVRfLVgtXbaY+TPDSigp4F1iDr2mMD/xtUN6QXfE4jJKypO bQiLVhBXJhiF/ZvwtTdYLmJYxVSjgMhZxksT/G5HVXfgRj7OHFvPEV394HhiLLG1 IR+Yt/3HFVEYPS4Yi/VOe5PychW30Aibsf+A+iTV8VhQPyys9wyNc+cw+AYYD3BS IVmbL5CMzzeMuLczFEUazp3mCmyNbNc62gmrzaEEAVpAMk5yVqsiV+0k/Upz6eOj THgfwupyEttg1NezYrWJgRSvWci40yOYIIdKy0rtlJtZ0EsdkhwbaIcKhPKN/GWP ZcME7BgBX6Y6AfMt+7z5isAZeviiQ==
X-ME-Sender: <xms:dDRPYENy-pXyjwL7podnV0EhpvO5sFNhVfbdgfAeUFomqK1HyO3s9Q> <xme:dDRPYK5ZhLaOxUWsgJBdiYNMAcfvQzhDXGxcWjcFo8o7XQvMzkh9kNX7VbubaWxuD do7vzs8G1KEOfPcp7w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddvledgudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffkffvuffhjghfofggtgfgsehtqh ertdertddunecuhfhrohhmpeforghrthhinhcuuehjnphrkhhluhhnugcuoehmsghjodhi vghtfhesgeeiieekrdhsvgeqnecuggftrfgrthhtvghrnheptdeugefhheeikeekfeelff evhfevueelveelfefgueefudegffegudetffffffdunecuffhomhgrihhnpehrfhgtqdgv ughithhorhdrohhrghdpihgvthhfrdhorhhgnecukfhppeduheekrddujeegrdegrddvud ehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhgs jhdoihgvthhfseegieeikedrshgv
X-ME-Proxy: <xmx:dDRPYIJ4edAZo9EUY5bXzWU6CbHUzNfFCrPA0n8spHN_ItEkhJkZAQ> <xmx:dDRPYEcIgHtK2M46ioePfJDXJIyoF90OFkQRAVtjRYvM5-PYfTa7pg> <xmx:dDRPYLdZZt9LLFm2PhbfsmsD-iCCvh6NvgpuwyU27XZK6aMkOzlgbQ> <xmx:djRPYII-U7ENVLnsaeasysSeA2BuOCACrav4R4y_g9b_OaR67DaDFw>
Received: from localhost (unknown [158.174.4.215]) by mail.messagingengine.com (Postfix) with ESMTPA id 9B3F524005E; Mon, 15 Mar 2021 06:18:27 -0400 (EDT)
Date: Mon, 15 Mar 2021 11:18:26 +0100 (CET)
Message-Id: <20210315.111826.1844702859879595481.id@4668.se>
To: janl@tail-f.com
Cc: rwilton=40cisco.com@dmarc.ietf.org, mbj+ietf@4668.se, rfc-editor@rfc-editor.org, netconf@ietf.org, warren@kumari.net
From: Martin =?iso-8859-1?Q?Bj=F6rklund?= <mbj+ietf@4668.se>
In-Reply-To: <608B4604-1970-4BE3-85E5-565985A4EBF6@tail-f.com>
References: <20210315.102411.704461003596497032.id@4668.se> <MN2PR11MB4366C5416AE4DB8CCF3FE7C3B56C9@MN2PR11MB4366.namprd11.prod.outlook.com> <608B4604-1970-4BE3-85E5-565985A4EBF6@tail-f.com>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Y_YVX2E8mvq_mRWgRRj4dzfpFF8>
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:18:34 -0000

Jan Lindblad <janl@tail-f.com> wrote:
> Rob, Martin,
> 
> Wouldn't changing the revision date be a massively
> non-backwards-compatible change?

Note that this is in the revision history list.

> 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.


/martin



> 
> 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
> > 
>