ability to retrieve both op-state types together

[kwatsen]

On the interim call, Rob made in interesting point about config+operational, using BGP as an example.

Do we need to amend point 4 to allow for a method to retrieve these in a single operation?

OLD:

   4.  Separation of configuration and operational state data; ability
       to retrieve them independently
       A.  Be able to retrieve only the derived state aspects of
           operational state
       B.  Be able to retrieve only the non-derived state aspects of
           operational state

NEW:

   4.  Separation of configuration and operational state data; ability
       to retrieve them both together and independently
       A.  Be able to retrieve only the derived state aspects of
           operational state
       B.  Be able to retrieve only the non-derived state aspects of
           operational state
       C.  Be able to retrieve both the derived and non-derived state
           aspects of operational state together

[rgwilton]

Yes, I think that this is a requirement, and hence support this proposed change.

For asynchronous servers, I expect that it is more useful to return applied config + derived state together in a single request than it is to return intended cfg + derived state since the client is likely to already know what the intended config is.

I'm not sure whether section 4 of openconfig-netmod-opstate-01 makes this requirement completely clear, but I think that it is because it assumes that the applied-cfg is part of the operational state and hence naturally returned as part of a get request. Section 5.1.also implies that the would be returned together.

Rob

[kwatsen]

This proposal was accepted on today's interim call

[kwatsen]

Change applied to draft - moving to REVIEW state

[kwatsen]

4-C was accepted in -00 draft (moving to DONE)