> On 09 May 2016, at 10:59, Robert Varga <[email protected]> wrote: > > On 05/05/2016 04:44 PM, Balazs Lengyel wrote: >> 5) IMHO allowing such dynamic introduction of new YANG modules into a >> network element, with flexible mountpoints, flexible set of modules at >> each mountpoint, a flexible set of deviations and features for each >> mounted module makes discovery actual available schema tree difficult. I >> think we are providing to much flexibility, over-complicating the issue. >> Some more static mounting solution that can be read from YANG modules >> instead of run-time data would be easier. > > Unfortunately, there is at least one use case, where the organization of > 'the world' is a run-time rather than modeling-time property, hence the > discovery process needs to be driven by data available in run-time.
Either way, schema mount isn't really about modeling-time but rather about session-time. I would prefer that the server publish the complete schema upfront, as a part of the "contract" with the client. > > That use case is important for things like OpenDaylight, but may not be > important when talking directly to "simple" network elements, e.g. those > which can be statically modeled. One option is to have separate mechanisms for the simple and complex cases. Lada > > Bye, > Robert > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
