On Tue, Sep 12, 2017 at 12:09:57PM +0100, Robert Wilton wrote: > > > > There are several possible pitfalls here since (i) <operational> can > > change anytime, (ii) it might not be easy/possible to obtain a > > consistent snapshot of <operational>, and (iii) dynamic datastores can > > provide values that "overwrite" <intended> and hence comparing values > > may not really be sufficient. As long as the text is understood as > > additional explanation and not used to write naive code to determine > > how much of <intended> has been applied, it is fine. Otherwise, it > > may be a source of future problems. > One tweak could be to change "applied" to "in use": > > The contents of <intended> are related to the 'config true' > subset of <operational>, such that a client can determine to what > extent the intended configuration is currently in use by checking > whether the contents of <intended> also appear in <operational>. > > Is this better? >
I think this is better but the change does not address (i)-(iii) in case someone uses this text to go and write naive code. But perhaps nobody is ever going to do that. ;-) /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
