Hi!
I exported new modules to NETCONF, but some do not show up in the capabilities list, but they can be downloaded by get_schema.
Is this behavior correct? The capabilities do not report all exported yangs?
BRj
Hi!
I exported new modules to NETCONF, but some do not show up in the capabilities list, but they can be downloaded by get_schema.
Is this behavior correct? The capabilities do not report all exported yangs?
BRj
I did some more research and found that I have problems wit yangs that are defined with “yang-version 1.1”. Looking at https://tools.ietf.org/html/rfc7950#section-5.6.4 I can’t figure out what needs to be done.
Please help!
You don’t need to do anything, ConfD does it all for you!
Basically the original idea of reporting all the YANG modules in the NETCONF <hello> is abandoned - it was hugely ineffecient for a device with hundreds of modules to report them all in every NETCONF session, especially since they typically remain the same for extended periods of time. The solution described in https://tools.ietf.org/html/rfc7895 (and referenced in https://tools.ietf.org/html/rfc7950), i.e. the ietf-yang-library module, is the way to go now - clients can request the info if and when they need to, in addition there are ways for clients to figure out when the info has changed.
For backward compatibility, YANG 1 modules are still reported in the <hello>, while YANG 1.1 modules are only reported via ietf-yang-library. Of course YANG 1 modules are also reported via ietf-yang-library, i.e. that is now the only place a client needs to check.