Subject: [Netconf] Action invoked on operational state vs configuration datastore

From: Qin Wu <[email-masked]>
Date: Tue, 17 Jul 2018 11:43:34 +0000

Hi, folks:
We have posted inline action capability draft (https://tools.ietf.org/html/draft-zheng-netconf-inline-action-capability-01) before this meeting and collected a few feedback on the list.
Unfortunately this draft is not on the NETCONF agenda this time due to time limitation reason. One of our proposal is to invoke action on both operational state datastore and configuration datastore.
Use Case for action invoked on operation datastore is:

In this case, we can see action operation output become edit-data operation input.

The second case is action is invoked on configuration datastore, this case seems a little tricky, since as described in RFC8342, Actions are always invoked in the context of the operational state datastore.
But talking with authors of RFC8342, it looks RFC8342 doesn't prevent evaluate action on other type of datastore, e.g., running, what is needed is to update RFC7950 to allow evaluation action on other datastore.
So I believe this case will be useful as well, e.g.,
You may first Enable ifstatistics on 1000 interfaces from the running configuration And then setting the MTU to 1500 on an interface named "Ethernet0/0" and 1000 on an interface named "Ethernet0/1" in the running configuration.
In this case, we can use action to realize ifstatistics enabling. Action operaton will not interfere with edit-config operation on MTU setting.
Comments and feedback on this?

-Qin