Re: [netmod] import-by-semver issue

[Andy Bierman <[e-mail]>]

On Sun, Mar 24, 2019 at 9:14 AM Juergen Schoenwaelder <
[e-mail]> wrote:

> On Sun, Mar 24, 2019 at 03:14:18PM +0000, Rob Wilton (rwilton) wrote:
> >
> > 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).
> >
>
> The difference is that NBC changes are not allowed. As long as you
> find a certain symbol, it has fixed and predictable semantics.
>
> Sorry, but changing the way the import statement works is an NBC
> change of YANG and this can't be done with extensions.
>
>
I strongly agree.
The expected behavior for tools needs to be consistent, especially for
the construction of the schema tree, which depends on the import rules.

Implementation complexity should matter in the IETF, but it does not.
Just keep raising the complexity up to 10 and complain that the tools have
bugs,
as if the two are unrelated. (Simply looking for a hardwired string
"semver:version"
will not work since the prefix is not required to be "semver" in the
import-stmt.)




> /js
>


Andy


> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <https://www.jacobs-university.de/>
>