> That's what I meant. > RPC input MUST be honored by the server or it is not implementing <rpc> > correctly. > > Constraints on RPC output and notification output are for documentation > purposes. > A client could try to evaluate them with its own copies of the server's > running and > operational datastore contents, but I think the YANG definition says the > constraint > is enforced on the server. > > Maybe NMDA could clarify this issue.
What would be the update? Would you change the XPath context text in Section 5.1 to not include the additional datastore contexts, or just add a clarification that any such constraints are just conceptual and primarily for description purpose? And, if the latter, shouldn't it be a clarification on RFC 7950? Kent
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
