Hi, I am still concerned that the datastore conformance requirements are under-specified and too server-centric.
The YANG definitions defined for NETCONF and RESTCONF operations do not ac tually require the "real" datastore identities to be used by a server. The server implementor has the freedom to replace all of the standard datastores with proprietary definitions. While this provides unlimited flexibility for the server, it also provides unlimited complexity for the client. I think the existing :candidate, :writable-running, and :startup capabilities cover the standard conventional datastores. IMO the MUST be a new capability for the :operational datastore and the exact identityref and semantics for this datastore MUST be supported if the :operational:1.0 capability is advertised. Both NETCONF and RESTCONF can list capabilities so both protocols can advertise this capability URI. Andy
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
