Re: [netmod] import-by-semver issue

"Rob Wilton (rwilton)" <rwilton@cisco.com> Sun, 24 March 2019 15:14 UTC

From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: Andy Bierman <andy@yumaworks.com>, NetMod WG <netmod@ietf.org>
Thread-Topic: [netmod] import-by-semver issue
Thread-Index: AQHU4arYjIn8/1YI30euxcwhgGMsT6YahbWggABuJwD//9uzgIAAXWcA//+zwcA=
Date: Sun, 24 Mar 2019 15:14:18 +0000
Message-ID: <de771cdd329046cfa42a92d8d8ecf525@XCH-RCD-007.cisco.com>
References: <CABCOCHRQXwRM1_xNzwoWxdT6e_zSNSFpvooDDmP3g11gxd3NuA@mail.gmail.com> <892d5ab4649549698808a6150067f840@XCH-RCD-007.cisco.com> <CABCOCHT3qfo4s7JV6WktWuz2C_UA6NFjqdVcjxVjxCDTUHWDzg@mail.gmail.com> <4c0a8dca338f4ca384dea933f046511e@XCH-RCD-007.cisco.com> <20190324143116.evgabiqpmz5gwgem@anna.jacobs.jacobs-university.de>
In-Reply-To: <20190324143116.evgabiqpmz5gwgem@anna.jacobs.jacobs-university.de>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/67tuXe97iAhtpC5SqSpVhdjZZCg>
Subject: Re: [netmod] import-by-semver issue
Precedence: list

Hi Juergen,

> -----Original Message-----
> From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
> Sent: 24 March 2019 15:31
> To: Rob Wilton (rwilton) <rwilton@cisco.com>
> Cc: Andy Bierman <andy@yumaworks.com>; NetMod WG <netmod@ietf.org>
> Subject: Re: [netmod] import-by-semver issue
> 
> On Sun, Mar 24, 2019 at 02:07:15PM +0000, Rob Wilton (rwilton) wrote:
> > Hi Andy,
> >
> > There are many ways to write and design compilers.
> >
> > Compilers that don’t understand import-by-semver just ignore the extension,
> no deviation is required.  They just import whichever arbitrary revision that they
> would have imported anyway, as specified by YANG 1.1.  The import-by-semver
> statement just reduces the set of valid modules revisions that can be used for
> import.
> >
> 
> If two compilers (one supporting semver, the other not) resolve imports
> differently, then the design is in my view somewhat broken, in particular if you
> allow NBC changes.

But that is true of YANG compilers today.  If there are multiple revisions of a module that could be chosen, then each compiler is at liberty to decide which revision to choose (last paragraph of section 5.1.1 in RFC 7950).

So, I would argue that "import-by-version" doesn't make YANG compilers any less consistent that they are already today, since that inconsistency already exists.

I presume that the real solution here is to explicitly define the full set of implemented, import-only-modules to the compiler so that it always compiles a consistent schema.  Perhaps other compilers have different ways to solve this problem.

Note, I also think that YANG library has a similar inconsistency.  I.e. there is no guarantee that two different compilers will construct exactly the same datastore schema from the YANG library output.  I think that this is a design bug, but also one that we attempt to address in draft-verdt-netmod-yang-semver-00.

Thanks,
Rob

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

[netmod] import-by-semver issue Andy Bierman
Re: [netmod] import-by-semver issue Rob Wilton (rwilton)
Re: [netmod] import-by-semver issue Andy Bierman
Re: [netmod] import-by-semver issue Rob Wilton (rwilton)
Re: [netmod] import-by-semver issue Juergen Schoenwaelder
Re: [netmod] import-by-semver issue Rob Wilton (rwilton)
Re: [netmod] import-by-semver issue Martin Bjorklund
Re: [netmod] import-by-semver issue Rob Wilton (rwilton)
Re: [netmod] import-by-semver issue Juergen Schoenwaelder
Re: [netmod] import-by-semver issue Andy Bierman
Re: [netmod] import-by-semver issue Martin Bjorklund