On Mon, Jun 06, 2016 at 02:16:38PM -0400, Susan Hares wrote: > Juergen: > > I2RS Ephemeral Configuration - is configuration which needs validation, but > does not survive a reboot.
Sue, 'validation' is not enough; there needs to be a clearer definition what 'validation' means. > I2RS data models which are "ephemeral at top node" and have operational > state. In these models, the operational state is like all other operational > state. The phrase 'ephemeral at top node' just confuses me. > I suggest we focus on the I2RS ephemeral Configuration. On this topic you > stated below: > > "Again, for configuration datastores, I can obtain the config and validate > it pretty much anywhere, on the device or offline at a controller. My > understanding is that this would not be true for I2RS' > ephemeral stat datastores; I would need some amount of additional data to do > something close to YANG's configuration datastore validation." > > Why is this not true for ephemeral datastore? I am missing any reason why > you think this is true. Configuration datastore validation works because data is self-consistent without references to any (external) state. Are you saying that the same is true for I2RS' ephemeral datastores? /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
