Re: [i2rs] Ephemeral State Requirements discussion

["Joel M. Halpern" <[e-mail]>]

If I understood you correctly Juergen, you are suggesting using your 
document:
https://tools.ietf.org/html/draft-schoenw-netmod-revised-datastores-00
as a basis for addressing the I2RS requirements.

I am having trouble understanding how the approach in your document 
would work for ephemeral configured information.
1) The document says that such information is treated like other control 
protocols.
1a) How would one use NetConf or RestConf to write this?
1b) How would the controllable relationship with conventional 
configuration be realized
1c) How would the descriptions of this information be provided? 
(Arguably, this last is not a requirements question, but it would help 
in understanding your proposal.
2) Similarly, since operations have been segregated by datastore, how 
would an I2RS client read the configured information to tell what was 
being applied?
3) How would the I2RS requirement for priority of operation be applied?
4) How would the requirement for reversion to configured values upon 
removal of an I2RS modification be done?

It is very hard as a reader to tell if your approach is acceptable, 
better than, or worse than, the one we have on the table.

As far as I can tell, in terms of a consistent architecture for data 
stores, both approaches consist of creating extra data stores when needed.

Yours,
Joel