On Tue, May 19, 2015 at 11:26 PM, Juergen Schoenwaelder <[email protected]> wrote: > On Tue, May 19, 2015 at 09:20:52PM +0000, Kent Watsen wrote: >> >> >> It's unclear to me why Y45-04 is needed at all. Doesn't a newer revision >> of a module contain all the same typedefs from before, and thus a module >> could import just the more recent revision to get everything it needs? >> Why would a module ever have to import an older revision? >> >> RFC 6020 says "New typedefs, groupings, rpcs, notifications, extensions, >> features, and identities may be added." I take this to imply that they >> cannot be removed or even renamed. Is this not the case? >> > > The definitions can be changed and Y45 is about making sure that we > always know precisely which definition is used - this was called > typedef drift and grouping drift. Please check the extensive > discussions we had about this plus the I-Ds people wrote about this. > I do not think we should restart this discussion once more. >
You seem to be suggesting that Kent is an uninformed observer and Y45-04 is actually really easy to understand. Neither is true. The solution is not intuitive at all. The implications of cherry-picking YANG statements from various revisions of a YANG module are not well understood. The concept of writing a YANG module so it works with all possible combinations of all possible back-revisions of imported modules is not well understood. The question "why can't the module being updated use the latest revision of an import" is quite legitimate. So is the question "Why can't I determine what a server implementation is required to support for a given YANG module?" The issue title "Better YANG conformance" is misleading because YANG conformance specificity is actually much worse with this solution. It's great for vendors who want to interpret for themselves what conformance means. Andy > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
