On Thu, Jun 02, 2016 at 06:53:42AM -0400, Susan Hares wrote: > Juergen: > > Do you think this definition belongs in the ephemeral requirements? If so, > we can add it. But perhaps we should define both ephemeral configuration > and ephemeral operational state. Joel point out at the I2RS interim that > ephemeral operational state is just like all other operational state - it > disappears upon reboot. It is ephemeral configuration which is different > than normal configuration - since it disappears upon reboot where normal > configuration does not. > > Is this diagram close to your existing model where opstate and ephemeral > configuration are parallel? > > +--------------------+ +--------------------------+ > | opstate | | ephemeral config | > +--------------------+ +--------------------------+ >
I see two boxes, I am unsure what you think these boxes drawn this way mean. What is 'this definition' in your first sentence? I really have problems to follow what is going on. /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
