"Alexander Clemm (alex)" <[email protected]> wrote: > - As Martin mentioned, clearly by allowing to mount you are > decoupling schema information and instance population. Regarding > the issue of validation, this can be addressed by several ways.
I think that the mount point effectively works as a 'chroot' for all mounted data models in the mount point. This means that if ietf-interfaces and ietf-routing are mounted under /devices/device/data, all XPath expressions and leafref paths and instance-identifiers in these models are evaluated in a chrooted environment where their '/' is set to /device/device[name='...']/data. This is how we implement validation for such modules in our NCS (manager product). In an implementation that actually does not store the data locally, but fetches it from a remote device (like the original mount proposal), it is fine to push also validation to the remote node. [maybe mount is not a good name for this generalized thing; this term might make you believe that the data has to be provided by some other server.] /martin _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
