Re: [netmod] ietf-yang-library edit

[Andy Bierman <[e-mail]>]

Hi,

The entire reason for import-by-revision is to make sure that
the importing module can safely use definitions that have been added after
the first revision of the imported module.


Andy



On Tue, Nov 14, 2017 at 9:04 PM, Robert Wilton <[e-mail]> wrote:

>
>
> On 15/11/2017 12:48, Balazs Lengyel wrote:
>
> Hello,
>
> I though our strategy was to always use the latest revision available. At
> least till now that works for me.
>
> Yes, I'm not convinced that the import by revision is really that helpful
> since it states that it must pull in exactly that version, but really the
> dependency is "at least version X, assuming newer revisions are backwards
> compatible".
>
> E.g. if/when ietf-yang-types is updated again, it would be cleaner/simpler
> if the server could just use the latest version rather than having to
> potentially import multiple revisions.
>
> Thanks,
> Rob
>
>
> regards Balazs
>
> On 2017-11-15 10:33, Andy Bierman wrote:
>
> Hi,
>
> The ietf-yang-library module relies on "yang-identifier", which was added
> to the 2nd
> version of the ietf-yang-types. It does not compile unless that version is
> used.
>
>
> OLD:
>
>     import ietf-yang-types {
>         prefix yang;
>     }
>
>
> NEW:
>
>     import ietf-yang-types {
>         prefix yang;
>         revision-date "2013-07-15";
>         reference "RFC 6991: Common YANG Data Types";
>     }
>
>
> There are other modules such as ietf-ip that rely on RFC 6991 additions
> and the import-stmt (in every case) should be changed to specify the
> required revision-date.
>
>
> Andy
>
>
>
>
> _______________________________________________
> netmod mailing [e-mail]://www.ietf.org/mailman/listinfo/netmod
>
>
> --
> Balazs Lengyel                       Ericsson Hungary Ltd.
> Senior Specialist
> Mobile: [phone]              email: [e-mail]
>
>
>
> _______________________________________________
> netmod mailing [e-mail]://www.ietf.org/mailman/listinfo/netmod
>
>
>