On Tue, Jul 11, 2017 at 09:48:30PM +0000, Kent Watsen wrote: > > Could all the presenters please have a slide on their module's NMDA > compatibility status? Things to consider: > > - is the operational state of configured values important? > - is there is a need to support system generated entries? > - note: if yes to either, the module SHOULD be NMDA-compatible. > is it? - is there a "-state" tree in the Appendix? >
I find this confusing. I think modules should be default be NMDA-compatible. I also think -state trees should be avoided as much as possible. So the questions should be something like this: - Is the module NMDA-compatible? If not, why not? - Does the appendix include a -state tree? If so, why is it necessary and how to transition away from it? /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
