On Sun, Oct 07, 2018 at 09:49:57AM -0700, Andy Bierman wrote: > > Can somebody explain the rationale for the highlighted text from 5.3.4?
Note the difference between "applies to" and "carries". A non-presence container has no relevance for configuration and hence an origin value does not *apply* to a non-presence container. Still, a non-presence container can *carry* an origin attribute. > There are many top-level configuration NP-containers defined already. > It is clearly more efficient to have 1 origin attribute in the top-level > container than in each of the child nodes. There is no requirement to produce efficient encodings. This is up to implementations, the cost of calculating a minimal encodings may be high for systems that like to stream information. That said, even toplevel origin attributes are not sufficient to guarantee an efficient encoding. If most child nodes have an origin different than what is stated in the toplevel container, you gain little. The requirement really is that an origin must be defined for all configuration data nodes (except np-containers). The way how this is done is up to implementations. If implementations want to set default origins at the toplevel, so be it. /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
