Hi, the following text in sec. 3.2 of schema-mount-08 is wrong for traditional datastores, and even more so for NDMA:
In case 1 ["inline"], the mounted schema is determined at run time: every instance of the mount point that exists in the parent tree MUST contain a copy of YANG library data [RFC7895] that defines the mounted schema exactly as for a top-level data model. A client is expected to retrieve this data from the instance tree, possibly after creating the mount point. Instances of the same mount point MAY use different mounted schemas. An instance of the mount point in any *configuration* datastores cannot contain YANG library (being state data), and so the MUST cannot hold. It is not clear to me how to repair this without considerable complications and/or a lot of handwaving. There is actually one good solution but it has impact on YANG library: the server could provide it in a reply to an operation, say "get-yang-library" rather than as state data. Then everything would be fine - this operation would turn into an action for the mount point, and it can be used equally well for config true and false mount points. So my proposal is to move from YANG library as state data to an operation. It could be done along with changing the YANG library structure, so there will be little extra impact on implementations. Lada -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
