Hi Adrian,
Some of this has been discussed on YANG doctors list some time ago. Bad
luck, before it was archived.
Good news, I explained the conclusions on the NETMOD mailing list. See
Hi Tom,
Long time!
> > What I see from 7950 is that a "YANG module" is a compilable blob of
> > YANG that may include other modules or specific constructs from another
> > module. That is clear enough.
> >
> > What is less clear is what a "data model" is or is not. I think that
> > if, for
> For now I'll complete the AD writeup, and put it in AD watching,
> revised ID needed state. Once y'all have figured out an answer I'll
> hit the Go button.
Fair enough, Warren.
I have an update ready with changes for everyone else's comment, so we are
"close".
I know that Benoit is busy
Hi Benoit,
>> In RFC 8199, we made a distinction between model and YANG modules.
>> This is why we defined the terms "Network Service YANG modules" and
>> "Network Element YANG modules" and not models. You should follow this
>> convention. After all, from the abstract, this document focuses on