YANG Versioning Weekly Call Minutes - 2020-11-03 We mainly discussed how Packages should work with schema mount. Some rough notes from the discussion below.
For next week we'll come up with a prioritized list of Versioning topics that need broader WG input. Rough Notes re schema mount & packages: - if a server only advertises a single package XX, which describes a mp as mounting YY, then the client is guaranteed of finding YY at the mp (assuming no deviations, module replacements, etc in XX). TBD: or can the server mount something else there without advertising a different package that describes that mount ? Can it mount ZZ that is a super-set of YY ? Is this different from modules because mounts are a run-time concept ? - might need an additional flag (exact schema vs minimum-set/super-set) - if 3 packages are listed, then at least 1 of the 3 must be mounted (and no other packages besides those 3 could be at that mp) ? Is that what we want? - if 0 packages are listed, then you have no idea (undefined) - the mount-point info in a parent package replaces the mp info in child packages (recursively). This is also how conflicts are resolved. - replacing what is available at a mp may or may not be NBC. You have to look at all the versions of all modules at the mp before & after. -> TBD: what if packages foo & bar have the identical modules & versions. Are they the same or different ? Call it NBC.
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
