On Thu, Sep 27, 2018 at 09:11:41AM +0000, Rohit R Ranade wrote: > > [Rohit R Ranade] So how to decide the origin annotation for top-level > non-presence container. Consider the case of "nacm" root node of > ietf-netconf-acm module which is a container. > Consider that "enable-nacm" came via "intended" origin, and "read-default" > came via "default" origin. > +--rw nacm > +--rw enable-nacm? boolean > +--rw read-default? action-type > +--rw write-default? action-type > +--rw exec-default? action-type > [Rohit R Ranade] So how to decide the origin for the container, when its > child may have mixed origin ?
Up to the implementation. An implementation may set origin=default on nacm and then origin=intended on enable-nacm. This would mean origin=default for read-default, write-default, exec-default. It is a matter of how much effort an implementation wants to spend to reduce the total number of origin annotations that are needed. There might also be rather dumb implementations that set origin on every node. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
