Juergen: I agree you if you overwrite data, the original config data and the I2RS values must be kept some-place. However, this is an implementation matter in my mind. Why do you tag it to a different data store.
Also, is the augmentation of any variable considered a separate data store? Sue -----Original Message----- From: i2rs [mailto:[email protected]] On Behalf Of Juergen Schoenwaelder Sent: Monday, June 06, 2016 3:03 PM To: Fedyk, Don Cc: 'Jeffrey Haas'; [email protected]; 'Joel M. Halpern'; Susan Hares Subject: Re: [i2rs] Ephemeral State Requirements discussion On Mon, Jun 06, 2016 at 06:51:46PM +0000, Fedyk, Don wrote: > Does this imply for a minor tweak of some operational datastore > (temporary link metric change or something similar) , I2RS ephemeral > has to have its own complete datastore? Yes. Because this is where the information that something got overwritten is stored. And in this case, the datastore would essentially consist of a single key/value pair. The phrase 'complete datastore' may indicate something complex while it can actually be lightweight. In any case, somewhere information must be kept that something was overwritten - we call this something a datastore. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
