Re: [netmod] Fwd: New Version Notification for draft-lengyel-netmod-yang-instance-data-01.txt

Joe Clarke <jclarke@cisco.com> Tue, 26 June 2018 19:42 UTC

Return-Path: <jclarke@cisco.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 D857B130E1F for <netmod@ietfa.amsl.com>; Tue, 26 Jun 2018 12:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 QIsTdyyunX9M for <netmod@ietfa.amsl.com>; Tue, 26 Jun 2018 12:42:21 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F57C128CF3 for <netmod@ietf.org>; Tue, 26 Jun 2018 12:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3649; q=dns/txt; s=iport; t=1530042141; x=1531251741; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=3uiuX3nL7Xpxke0iFRpBGn0usDkCk3dnR7Ke32MyDHg=; b=C2zOYjujCfKRyNwL63GcWdywEn7iu8rP5ry4cGyGkZSUS47Hf/HkGpwU zBYG/2fogKJOHadfZXbXhyQsO6LR6TiTF5uo5vTy5jfjSzVrILDHN7DiY lG7jSlmPT3+oVsrhiQTIl3pKJrYhKzlPhrbvz5xWsTuHHRDCLXrfKZjfO o=;
X-IronPort-AV: E=Sophos;i="5.51,275,1526342400"; d="scan'208";a="135015195"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jun 2018 19:42:21 +0000
Received: from [10.118.87.86] (rtp-jclarke-nitro5.cisco.com [10.118.87.86]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w5QJgKgS013724; Tue, 26 Jun 2018 19:42:20 GMT
To: Balazs Lengyel <balazs.lengyel@ericsson.com>, Robert Wilton <rwilton@cisco.com>, "netmod@ietf.org" <netmod@ietf.org>
References: <152889763632.15168.12247537431295038165.idtracker@ietfa.amsl.com> <75383a97-d08b-b202-70a6-eab064963af8@ericsson.com> <b58d21a9-d27e-c8b3-e8e3-483dd6942c9e@cisco.com> <f946ca96-1cb2-e032-9adc-7df00702e216@ericsson.com> <20180626121156.fq5ioq2gh5sy3v7n@anna.jacobs.jacobs-university.de> <e50fdff6-caa2-aada-011e-534b14ffdcf1@cisco.com> <20180626135232.cdlrbbideyackdfe@anna.jacobs.jacobs-university.de> <e5877095-d5ee-d1e3-a144-a2e2a20062dc@cisco.com> <341ece85-4e00-dca4-580a-de234306c941@ericsson.com> <f470fd68-320e-8201-7045-68c8885ec3e2@cisco.com> <3cf59f95-8d26-44c5-2f30-947befa29f72@ericsson.com>
From: Joe Clarke <jclarke@cisco.com>
Openpgp: preference=signencrypt
Autocrypt: addr=jclarke@cisco.com; prefer-encrypt=mutual; keydata= xsDiBDo1cJ0RBADSZSmbmzdRr1CoRWWKmAyu0eaQimaLV1TsZEML/ksLyg6faXrKIA/MWc7M w4FmKkDjaZdFzobzabnKp2QwVadLqi1gYY2WsApKC0rSoqsPx5E847AmwNWXgjXiXORXmnZL mf5PZ2ECOEJC27sji5Nrh9GSw7OPp6c+EE20gMNVrwCgu3iK5vyGQfy0/wX/jcIvP0nHznUD /RvijiKomyaf6F5pibmouFNeuCDHc8lwx2giA/MCZl/nSkI2/UX27sULGNgvKNkVPu/AukXu zW3fIthsJgjQZUoi/BTe9kUP+RL3+RALXXuLv7b3xGRHJ8A1Rpy9H43fkjHZ945YNPrUvJlG LP5PNGBD1xC21X3EGAyywVynDskcA/4qgbJFkVzmPjFJUjq+RW1zw3UIb3bbkskl/wk5qd+M w2EhiSPTbEhJQAQUvqSGFWEGp2ANic7iYLdPXV/O6I1/guRRaY0eK77YkkCjz1snaKYnGSeI GHGwmHb6D+ZHzTqZqr6IssgEIUHjXfgOUTARQbL15nJTVRzDGUiT/65R3c0eSm9lIENsYXJr ZSA8amNsYXJrZUBjaXNjby5jb20+wl8EExECABcFAjyDqGQFCwcKAwQDFQMCAxYCAQIXgAAS CRDN7TXCWm4C3wdlR1BHAAEB5KkAn0kBda/9+uF6RfnDSFS7RExUU9DqAJ4knRckYiSASteC K03QVtEiXblL287ATQQ6NXCeEAQAhIURlK17jmIMdMIuScFU6xK+jkKgVVFrjlRH5vLV2spp jH/uQ57MMGuOcs7PckXCnPjBV8Tm32Tuw+fCyrbc2gt0ouiT/5WWj0EMeAfWew1zBXX2okGf LqS6gucVDS6tcEFN6PmJEmX+tWDcmiqx/xXiSfMVYiLMdlK+YDkMDDsAAwUD/3BWOyfdnBGH Kv28zx+5wq/2vhYnUYCAdVD2ZWCJizQTMbkcxEIKAwtAj6yqKq9ah82nt4VHl5ZejVe47jvR 2nXwJ5VQ9eITuTjTLDw+3qr9lN077VZ32hyb5ULJcW756j9Z3YB2FTANw6KHgChaSVVx9kYJ FlAggraU7mi39/wvwk4EGBECAAYFAjo1cJ4AEgkQze01wlpuAt8HZUdQRwABAQbdAJ9R8SzU Mluu9r93BMv6fAW9j6qTZgCfYcEAqOMJv+3Z+YxLiDtWcCY4Sfo=
Organization: Cisco
Message-ID: <c01247af-165a-3f33-01d0-eca38a2b6c78@cisco.com>
Date: Tue, 26 Jun 2018 15:42:20 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <3cf59f95-8d26-44c5-2f30-947befa29f72@ericsson.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/1MfsqFzYLPDe8ERK1u1kC9tssSE>
Subject: Re: [netmod] Fwd: New Version Notification for draft-lengyel-netmod-yang-instance-data-01.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 26 Jun 2018 19:42:25 -0000

On 6/26/18 11:38, Balazs Lengyel wrote:
> Any opinions on Rob's suggestion about a free-text versioning string?
> I am neutral on this.

Like I mentioned, I would use this for YANG Catalog input, and I would
want MD around yang-library instance data.  That MD would include the
vendor, platform, and version of software.

I'm not asking for all of these to be standardized, though.  I would
just want a way to extend the MD as needed.

Joe

> 
> regards Balazs
> 
> On 6/26/2018 5:31 PM, Robert Wilton wrote:
>> On 26/06/2018 16:20, Balazs Lengyel wrote:
>>> On 6/26/2018 4:07 PM, Robert Wilton wrote:
>>>>>>>>        7) It might want to include a semantic version number for an
>>>>>>>>        instance-data-set, depending on whether the YANG
>>>>>>>> versioning discussions
>>>>>>>>        ends up.
>>>>>>>>
>>>>>>>>      BALAZS: Yes I would like to. However I am not exactly clear
>>>>>>>> on what does
>>>>>>>>      backwards compatibility mean for instance data.
>>>>>>>>      Data MAY NOT be removed or changed only added.  ???
>>>>>>>>      Who would use the semver numbers ???
>>>>>>> What does the version number mean? Every change of instance data
>>>>>>> in an
>>>>>>> instacne-data-set leads to a new version number? What is a bug
>>>>>>> fix in
>>>>>>> this sense? What is a non-backwards compatible change of instance
>>>>>>> data?
>>>>>>> I am left a bit puzzled.
>>>>>> Probably I don't mean semantic version.  But often files have
>>>>>> versioning, or
>>>>>> revision, information associated with them.  This can be muxed
>>>>>> into the file
>>>>>> name/path, but it also seems like potentially useful metadata, and
>>>>>> being
>>>>>> able to handle this generically in a consistent way might be
>>>>>> beneficial.
>>>>>>
>>>>>> As an example, perhaps the capability information related to S/W
>>>>>> release
>>>>>> 1.2.4, etc.
>>>>> We need to separate a version number of the instance data from the a
>>>>> version number (or version context) that may be needed in order to
>>>>> understand what a YANG (module, path) tuple means if we move to a
>>>>> different YANG versioning scheme. The later I agree would be needed,
>>>>> the former I am less sure of - at least if we talk semantic version
>>>>> numbers.
>>>> Yes, I agree with the need for the latter, that may entail listing
>>>> the versions of the modules in the meta-data.
>>>>
>>>> But what I was actually referring to was the former, and thinking
>>>> more of it is just being a string field in the meta-data with a well
>>>> defined name, that is optional to populate.  Actually, I see the
>>>> current definition already has a revision with a date and
>>>> description string.  This is roughly along the lines of what I was
>>>> thinking of for versioning (although I'm not sure why this should be
>>>> a list rather than just a pair of leaves).
>>>>
>>>> Thanks,
>>>> Rob
>>> BALAZS:  IMHO if we want to use versioning (semver) to version the
>>> instance-data-set itself we first need to understand what backwards
>>> compatibility means for an instance data set.
>> So, I'm suggesting versioning, but not semver.  Just a string version
>> field.  E.g. for XR I would just put in the XR release number "R4.5.1"
>> or similar.
> 
> Balazs Lengyel                       Ericsson Hungary Ltd.
> Senior Specialist
> Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.com 
> 
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>