This I-D updates RFC7950, since it changes the XPath context that YANG uses, yet there is no mention of 'Updates'
Well, a purist will say that people can create and use models using RFC7950 with no need to have any understanding of this I-D so technically no 'Updates' is needed. But a practical engineer will say that the expectation is that many, if not most, future models will rely on this I-D and its updates to RFC7950 so to say that you do not need to know about it is just misleading. I am in the latter camp. I thought of alternatives. It is true that new models will have a Normative Reference to this I-D but I suspect that that will not be enough to alert users. RFC6087bis could mention it but that is aimed at producers rather than consumers who are the ones affected. So. pragmatically, I think that this I-D needs an 'Updates'. Tom Petch ----- Original Message ----- From: "Lou Berger" <lber...@labn.net> To: "netmod WG" <netmod@ietf.org> Cc: <netmod-cha...@ietf.org>; <draft-ietf-netmod-revised-datasto...@ietf.org> Sent: Friday, September 01, 2017 10:02 PM Subject: [netmod] WG Last Call: draft-ietf-netmod-revised-datastores-04 > 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 > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
