----- Original Message ----- From: "Jeffrey Haas" <[email protected]> To: "t.petch" <[email protected]> Cc: <[email protected]> Sent: Thursday, May 01, 2014 1:34 AM > On Fri, Mar 28, 2014 at 10:48:13AM +0000, t.petch wrote: > > This tri-partite split has been the norm for Ops Area for many years > > now. > > It may or may not be appropriate for I2RS but I do think that I2RS > > should > > at least take cognizance of this in deciding what terms to use > > I think this is one of the clearest description of one of our problems - and > thus requirements - that I've seen thus far. :-)
Yeah, problems are my speciality - I then look to Andy, Juergen, Lada and Martin for solutions:-) But, Jeff, you then say, in a parallel post "The issues then comes back to the ones noted in draft-bjorklund-netmod-operational-00: How do we distinguish operational, config or ephemeral config states? " whereas I see operational state, config and read-only statistics, with state (unqualified) referring to the first and last collectively! 'ephemeral' does not appear in Martin's I-D, nor would I expect it to - I don't see it as a concept in YANG/NETCONF. There is a separate issue of persistent and ephemeral in YANG, or, arguably, in NETCONF, which is also not documented AFAICS. This is probably of less interest to I2RS at this time. If there is one running datastore, then, presumably, it is persistent (across reboots) - the documents appear not to say. If there is running and startup, presumably startup is persistent and running is not. But if you have running and acme-special datastores, then which is persistent? This is one of several issues, like operational state, that have surfaced from time to time and, for me, have not got nailed down as well as I would like, and so - surface from time to time. Tom Petch > -- Jeff _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
