On Wed, Nov 13, 2024 at 4:05 PM Kent Watsen <[email protected]> wrote:
> Hi Shiya, > > Where does it say <running> contains only data provided by the client in > <edit-config> operations? > (Nowhere) > > > To put a finer point on this, it is a long-standing desire that changes to > <running> happen only with the client’s knowledge. That said, <running> > could contain config that was *generated* due to a client-instruction. For > instance, the “resolve-system” flag that was recently removed from the > “system-config” draft or, in Yuma’s case, an instruction that causes a > template-expansion to occur at time of the <edit-config>. > > RFC 4741 was way before YANG existed. Even in RFC 6241, the WG was careful about leaving the datastore details to the implementation. The metadata in the edit-config operation are processing instructions. They do not get added to the datastore. The template or loop instructions are no different. I do not agree with your strict interpretation of client-initiated. A client may set a CLI parameter or otherwise direct the server to use some feature or behavior. In this template case all the data is client-provided, but even when system data is provided, it is due to the configuration settings from the operator. > Kent // contributor > > 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]
