On Wed, Mar 18, 2026 at 10:18 AM Andy Bierman <[email protected]> wrote:
> Hi, > > There is an issue with this leaf that we have encountered in > implementation. > The YANG library is a bootstrap data structure. The client must use the > correct schema to retrieve this data from the server first, and then build > a > schema tree for the session after the library contents are known. > > But now the client has to use the contents to know what schema to use to > read this data. > Some clients (not ours ;-) do not handle any augmentations to > /modules-state at all. > > NETCONF has no support for this issue, but RESTCONF added a leaf to query. > https://datatracker.ietf.org/doc/html/rfc8040#section-3.3.3 > > This leaf assumes knowing the ietf-yang-library revision date is > sufficient. > It no longer is because of this new leaf. > > Sorry I did not bring this issue up in the YD review. There is a reason why the RFC 8525 version contains all of the old version as well. An old client can use /modules-state, and a new client can use /yang-library instead. Any client can check /modules-state without knowing anything about the server. Our client only works because it converts unknown nodes to anydata. mgr_val_parse: 'module' has no child node 'augmented-by'. Using anydata Clearing INVALID namespace for anyxml node 'augmented-by' It is also possible to prune the bad data instead. A client that does not do either one will probably throw an "unknown-namespace" error. > Andy > > Andy
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
