IETF Logo Mail Archive

Re: [core] progressing ietf-core-yang-cbor and ietf-core-sid

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 05 February 2020 12:45 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB8D3120236 for <core@ietfa.amsl.com>; Wed, 5 Feb 2020 04:45:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 0hQ3FK2fIH3n for <core@ietfa.amsl.com>; Wed, 5 Feb 2020 04:45:42 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 044B512013A for <core@ietf.org>; Wed, 5 Feb 2020 04:45:41 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2a02:8109:b6c0:52b8::5]) by relay.sandelman.ca (Postfix) with ESMTPS id 7D2B21F45A; Wed, 5 Feb 2020 12:45:40 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id B8547118A; Wed, 5 Feb 2020 07:45:37 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ivaylo Petrov <ivaylo@ackl.io>, Core <core@ietf.org>
cc: Andy Bierman <andy@yumaworks.com>, Alexander Pelov <alexander@ackl.io>
In-reply-to: <CAJFkdRzyuJWboogs8QcP4DtZ5+sHOAyGnUraVMYq728H6dNH9g@mail.gmail.com>
References: <29380.1565102380@localhost> <BL0PR06MB50428065032ECC2AB3345F619AD70@BL0PR06MB5042.namprd06.prod.outlook.com> <7505.1565633977@localhost> <BL0PR06MB50424C618A704460E4A8F8D99AA90@BL0PR06MB5042.namprd06.prod.outlook.com> <18990.1577231446@localhost> <CAJFkdRyWOfCb4U09rEJ-ZMR3GUuk-rmQ+f3Fs164Mxs8qkeVuw@mail.gmail.com> <22612.1578626081@localhost> <CAJFkdRztFUxdGcdvtTgB=9c-e_BwDAgLTmVPJ+OB8-dgs1sGog@mail.gmail.com> <15754.1578789013@localhost> <CAJFkdRy_3pC37ZxzhTmzqRgWjwDvEFTuhu5Z8+_ktaJgoeOGfg@mail.gmail.com> <6025.1578939111@localhost> <F67A7C80-0955-4836-9B84-66CB52AB6FD9@tzi.org> <26398.1579112884@localhost> <0805B57C-3DCB-4601-976C-2D51CE812312@tzi.org> <14603.1579125396@localhost> <CFF6555D-85EF-42CB-B773-17116F9CC554@tzi.org> <18568.1579133839@localhost> <CABCOCHRJ6-YUSn=MXGMtJT5tK3m9uR3U1K2xYd2UgW2MYkv6ig@mail.gmail.com> <CAJFkdRy8tDbYnnyr-mCer-Bip6s7pcXyGQPmo+nO8zRavSTm1w@mail.gmail.com> <CABCOCHRXH4AqYh6y9wVtCdA8T01sG7tAXmhzwzAk3QV9OjLonA@mail.gmail.com> <5C3B4919- 5513-4342-888D-998A11366D36@tzi.org> <CABCOCHQy71hMB+NkZZw__Kkov8n-MsqEV3O4pEx5K_DsAnQUDw@mail.gmail.com> <CAJFkdRyRF=huVQE+_+2EBpM3S-K0bpgKeBXnfqJtrz2xgZbi9w@mail.gmail.com> <CABCOCHS5jqjid4uok7JegrTj-rMfJ_eZM1_VA-eHigQ2dqu3gA@mail.gmail.com> <CAJFkdRz2-VgAa1gqF84Sodrh4mLOKD8-s6dXJtdRTxvVhBiUtQ@mail.gmail.com> <CABCOCHTtC-crDSW+5OHLBPEvB0MYGm7i626gfFSQ0AnAsonW0g@mail.gmail.com> <CAJFkdRy-=41hxxWqi3QCBWDcw1vJ5riMGg3L9suY5zj8-0piSQ@mail.gmail.com> <CAJFkdRzyuJWboogs8QcP4DtZ5+sHOAyGnUraVMYq728H6dNH9g@mail.gmail.com>
Comments: In-reply-to Ivaylo Petrov <ivaylo@ackl.io> message dated "Wed, 05 Feb 2020 11:46:59 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 25.1.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 05 Feb 2020 13:45:37 +0100
Message-ID: <28929.1580906737@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/6JIOIiWLgD2Jk7YpCO9bh-8VceA>
Subject: Re: [core] progressing ietf-core-yang-cbor and ietf-core-sid
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2020 12:45:44 -0000

Ivaylo Petrov <ivaylo@ackl.io> wrote:
    > leaf sid-file-version {
    > type sid-file-version-identifier;
    > description
    > "Version number of the \".sid\" file. Useful to distinguish \".sid\"
    > files generated using different YANG module dependencies that might not
    > be reflected in the YANG module revision.";
    > }

...
    > +In case of an update to an existing ".sid" file, an additional step is needed
    > +that increments the ".sid" file version number. If there was no version number
    > +in the previous version of the ".sid" file, 0 is assumed as the version number
    > +of the old version of the ".sid" file and the version number is 1 for the new
    > +".sid" file. Apart from that, changes of SID files can also be automated using
    > +the same method described above, only unassigned YÀNG items are processed at
    > +step #3. Already existing items in the SID file should not be given new SIDs.

I don't think that this adequately makes it clear (hits them on the head...) that the
sid-file-version-identifier is specific to the YANG module revision.

Could you reword to:
description
 "The version number of the \".sid\" file. \".sid\" files and the version
  sequence are specific to a given YANG module revision.
  This number starts at zero when there is a YANG module update.
  This number can distinguish updates to the SID file which are the result of
  new processing, or the result of reported errata. ";

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email