Vojtech Vilimek <[email protected]> writes:
> Hi Lada and all,
>
> On 5/25/26 2:04 PM, Ladislav Lhotka wrote:
>>>> It is valid, multiple revisions of the same import-only module may coexist
>>>> in a module set. That's why the "import-only-module" list has name &
>>>> revision as its key.
>
>>>>
>>> Is is possible to decode this information from a YANG Library?
>>>
>>> By the information is meant what implemented module depends on what
>>> import-only module.
>
>> These dependencies are specified in the importing modules. In your example,
>> module A should import D with revision 2 and B with revision 1.
>
> Okay, there is a slight misunderstanding. I did not include the
> following part in my question. I am sorry for that.
>
> It is common practice, even encouraged by the IETF (at least based on my
> understanding), to use revisionless imports. If module A imports D in
> revisionless fashion but is implemented as if the D was revision 1, and
> if module B imports D in revisionless fashion but is implemented as if D
> was revision 2, in such situation, is it possible to decode this from
> the YANG Library?
If both A and B are used in the same datastore, then I don't think it is
possible to resolve this situation via YANG library, even if separate module
sets are used for the pairs (A, D@2) and (B, D@1) because the description of
the "module-set" list in RFC 8525 says that a module set does have to be
referentially complete wrt import statements.
It might actually be useful to be able to resolve the imported revisions in
YANG library given that an import statement without "revision-date" leaves the
revision undefined (RFC 7950, sec. 7.1.5).
Lada
>
> I am trying to understand in deployability of YANG in environment where
> not all parties update their implementation to the latest and greatest
> revisions.
>
>>
>> A complete example using two revisions of the ietf-inet-types module is here:
>>
>> https://yangson.labs.nic.cz/examples.html#example-3
>>
>
> I omitted the YANG modules from the question to keep it short. I hope we
> have now a clear common image of how they should look.
>
>> Lada
>
>
> Have a nice day!
>
> Best regards,
> Vojtech Vilimek
>
--
Ladislav Lhotka <[email protected]>
PGP Key ID: 0xB8F92B08A9F76C67
_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]
