I have yang data model that mixes configurational and operational parameters, which should be possible according to RFC 8342. However, if I define callpoint to the root of my model and try to subscribe to the same root the subscription fails with the error “badly formatted or nonexistent path”.
How to deal with it? Does confd limits subscription to paths not covered by callpoints?
How to deal with such a model then? I want to store config data in CDB but I don’t want to replicate the whole list just for keeping operational data. Apparently IETF yang data models start obsoleting separate lists for config/operational data as well.