> This is where NMDA and non-NMDA conflict. True. I suspect that the IETF-solution will require NMDA, just like with the “system-config” config draft.
> The template is also expanded in <running>. Disagree, <running> is always only what client’s set. Kent // contributor > 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]
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
