Looking at a YANG module in future, how can I tell whether or not it is written to work with revised datastores?
If the module is written assuming revised datastores and the environment does not support this in some regard, then we have a management malfunction, which could be disastrous. I think that there should be some mechanistic way, something that can be automated, for a system to check whether or not a module is assuming revised datastores or not. This is a bit like the change from YANG 1.0 to YANG 1.1; there needs to be a way of telling what environment the module is written for, and so we have the yang-version 1.1; statement. Revised datastores needs something similar in the module. Tom Petch ----- Original Message ----- From: "Lou Berger" <[email protected]> Sent: Friday, September 01, 2017 10:02 PM > All, > > This starts a two week working group last call on > draft-ietf-netmod-revised-datastores-04. > > The working group last call ends on September 17. > Please send your comments to the netmod mailing list. > > Positive comments, e.g., "I've reviewed this document and > believe it is ready for publication", are welcome! > This is useful and important, even from authors. > > Thank you, > Netmod Chairs > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
