Hi, Currently, the schema mount draft says that the "mount-point" extension only can be defined in an "anydata" node. However, this doesn't really work, since RFC 7950 says:
An anydata node is treated as an opaque chunk of data. This data can be modified in its entirety only. But the idea with schema mount is to build a composite model that can be manipulated just like a normal model, or a model that is augmented. If we mount models in an "anydata" node, clients would have to replace the enitire mounted subtree in order to change e.g. a single leaf. For this reason, I propose that we go back to the previous model where "mount-point" would be allowed in "container" and "list". Note that a client that doesn't know anything about these mounts would see some nodes in some unknown namespace; just like in the case that there is an augment that the client doesn't know about. /martin _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
