> -----Original Message-----
...
> > 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.
>
It may be clear that "intended" may not be the right choice, but what is? I
think it does not hurt to be explicit about it. This way, people don't have to
guess if it should be learned, or maybe system, or possibly even unknown. In
its current definition, "learned" only talks about "protocol interactions with
other systems ... such as routing protocols, DHCP, etc." If it is "learned"
then update its definition to something like
learned: represents configuration that has been learned via
protocol interactions with other systems, including protocols such
as link-layer negotiations, routing protocols, DHCP, etc, or as a side
effect of RPCs.
--- Alex
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
