On Wed, Nov 01, 2017 at 11:42:43AM +0000, Robert Wilton wrote: > > > One other comment, it would be good to also indicate that when an RPC > > leads to modification of data nodes, what the “origin” of those > > modifications is. > > > That is an interesting question. > > To describe this as a concrete example, if you have a single config true > YANG list for dynamic/configuration subscriptions then a subscription can be > created either via configuration or as an RPC operation. > > I would probably classify this as "learned", and I think that we could > extend the definition of the "learned" origin to cover this case.
I do not think any changes are needed, section 5.3.4 is pretty clear that the origin 'intended' applies to configuration provided by <intended>. If you at the options, there is pretty much only 'learned' applicable. /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
