Re: [netmod] Meeting Notes from open YANG versioning Design Team meeting

"Rob Wilton (rwilton)" <rwilton@cisco.com> Mon, 01 April 2019 10:08 UTC

From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Meeting Notes from open YANG versioning Design Team meeting
Thread-Index: AdTkoRj6svo9SZKZQ5Ggg56oL5hxCAB4MM0AAAFrlwAABcXAgAAPTsjg
Date: Mon, 01 Apr 2019 10:08:46 +0000
Message-ID: <bbcfe0a60ff742c1814229118903585f@XCH-RCD-007.cisco.com>
References: <c22dd347c9ac42d68f74177c36bdea27@XCH-RCD-007.cisco.com> <7D105CD4-9C4A-4643-9B8E-0F54B54F5B26@gmail.com> <20190329183132.7t75vbtbtxostah2@anna.jacobs.jacobs-university.de> <DD076E9A-F950-4A50-9CD6-89A4AF6A71A5@gmail.com>
In-Reply-To: <DD076E9A-F950-4A50-9CD6-89A4AF6A71A5@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_bbcfe0a60ff742c1814229118903585fXCHRCD007ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/DQemddH9mQxytBEALTRsCpsARlY>
Subject: Re: [netmod] Meeting Notes from open YANG versioning Design Team meeting
Precedence: list

I agree that the requirements for SDO models are slightly different from vendors models.  Really, I think that the SDO requirements are a subset of the vendor model requirements.

I think that a single solution should be possible here.

Thanks,
Rob


From: Mahesh Jethanandani <mjethanandani@gmail.com>
Sent: 29 March 2019 21:17
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: Rob Wilton (rwilton) <rwilton@cisco.com>; netmod@ietf.org
Subject: Re: [netmod] Meeting Notes from open YANG versioning Design Team meeting




On Mar 29, 2019, at 11:31 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>> wrote:

On Fri, Mar 29, 2019 at 10:50:52AM -0700, Mahesh Jethanandani wrote:


The combination of these bullet items, and maybe other bullet items does not make clear if there was any consensus in allowing (or maybe even preventing) vendors from using a versioning system to keep track of NBC changes on other (non-latest) branches of the model. I think I heard from multiple vendors (outside of this meeting) that making NBC changes was needed on the non-latest branches, whatever IETF or other SDOs decide. Has that sentiment changed?

If it is the case, the split between the requirements of SDO and the vendors is inevitable.

If there is a solution that can handle multiple branches, then the
same solution should work for SDOs that choose to use only a single
branch. I do not see why a split is inevitable.

If a single solution works for both SDO and the vendor, that is great. And I think that was the point of the third bullet in the list I send.

But that does mean the requirements of SDO and the vendor community cannot be different. There is a strong requirement that SDOs make NBC changes only on the most recent version of the YANG models. In the vendor community, NBC changes are going to be made on non-latest branches also.



/js

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

Mahesh Jethanandani
mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>

[netmod] Meeting Notes from open YANG versioning … Rob Wilton (rwilton)
Re: [netmod] Meeting Notes from open YANG version… Mahesh Jethanandani
Re: [netmod] Meeting Notes from open YANG version… Juergen Schoenwaelder
Re: [netmod] Meeting Notes from open YANG version… Mahesh Jethanandani
Re: [netmod] Meeting Notes from open YANG version… Rob Wilton (rwilton)