[netconf] system configuration sync mechanism

["maqiufang (A)" <[e-mail]>]

Dear all,
One of the open issues of draft https://datatracker.ietf.org/doc/html/draft-ma-netconf-with-system-02 is about how to synchronize the system configuration into <running>.
I think we could have 2 options.
Option 1: Any update in <system> will be synced up into <running> automatically
  PRO:

       o  effective for the client: there is no need for the client to retrieve the referenced system configuration from <operational> and then copy it into <running> manually.
  CON:
            o   implementation complexity

Option 2: To define a RPC operation to propagate <running> with <system>
  PRO:
       o  client-driven: it totally depends on the client when and how to populate <running>.
  CON:
       o  The client needs to :

o   spend energy to detect the <system> update and operate the RPC every time the client references the system configuration or the system configuration is in the when/must statement.

o   subscribe the <system> update and copy it into <running> whenever an update is detected.

I incline to the view that this issue involves some kind of trade-off, which is hard to distinguish the preference.
Maybe both options can be reserved and differentiated by different modes, so that the server implementer may choose from.
Any thoughts?


Best Regards,
Qiufang Ma