> ... > - templates are NOT themselves ever validated > - only the post-expanded/flattened result is validated (e.g., in > <intended>) > .... > > This is where NMDA and non-NMDA conflict. The template is also expanded in <running>.
The client does an edit-config on <running> to create /interfaces/interface. The server combines the client edit with template fields in <running>. Otherwise XPath (must, when, path) that references the template fields will fail. A template field is like a configured YANG default -- the value in use if no value is provided. The performance gain is from the "power edit" and refactoring. The implementation can pre-validate, share storage, etc. The internal storage of <running> can be optimized, but a representation of <running> returned to clients should contain expanded templates. K. > Andy
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
