If a document uses a term like 'ephemeral operational state' then I
think it should be defined somewhere (and ideally there would be an
indication where the definition can be found).

/js

On Wed, Jun 01, 2016 at 09:07:43AM -0400, Susan Hares wrote:
> Juergen: 
> 
> The I2RS architecture document has passed to RFC editor.  Your time to
> request the definitions in that document has long past.  If you are asking
> for a definition of ephemeral state in the I2RS ephemeral requirements
> document, this is a valid comment.  Is this what you are asking for? 
> 
> Sue  
> 
> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:[email protected]] 
> Sent: Wednesday, June 01, 2016 8:31 AM
> To: Susan Hares
> Cc: 'Jeffrey Haas'; [email protected]; 'Benoit Claise'; 'Alia Atlas'
> Subject: Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am
> -? Topic: Ephemeral State Requirements
> 
> OK. So if ephemeral state is the same as ephemeral data, can we simply get
> rid of one of the terms?
> 
> Still looking for a definition of 'ephemeral operational state' (since I
> consider operational state by nature to be ephemeral). And without it, I
> can't really resolve the 'defined as' relationships.
> 
> /js
> 
> On Wed, Jun 01, 2016 at 08:24:34AM -0400, Susan Hares wrote:
> > :== is a symbol that translates to defines as.
> > 
> > Left side :== (defines as) right side info Cat:== animal small furry 
> > Sue
> > 
> > 
> > Sent via the Samsung Galaxy Note5, an AT&T 4G LTE smartphone--------
> Original message --------From: Juergen Schoenwaelder
> <[email protected]> Date: 6/1/2016  4:25 AM  (GMT-05:00)
> To: Susan Hares <[email protected]> Cc: 'Jeffrey Haas' <[email protected]>,
> [email protected], 'Benoit Claise' <[email protected]>, 'Alia Atlas'
> <[email protected]> Subject: Re: [i2rs] I2RS Interim Meeting - June 1, 2016
> - 10:00am - 11:00am -
> >   Topic: Ephemeral State Requirements On Tue, May 31, 2016 at 
> > 03:29:55PM -0400, Susan Hares wrote:
> > > Juergen: 
> > > 
> > > 
> > > >I understand YANG validation rules and I understand YANG's notion 
> > > >of
> > > configuration datastores. I do not >think this matches your 
> > > ephemeral configuration validation.
> > > 
> > > This does not provide a technical discussion of: 
> > > a) what you understand the ephemeral configuration validation rules 
> > > to be,
> > > b) why you do not the model matches the configuration validation rules. 
> > > 
> > > 1 Data Model is a great idea for NETCONF/NETMOD.  However, it should 
> > > encompass
> > > 
> > > Ephemeral data:== ephemeral state ::== Ephemeral configuration + 
> > > Ephemeral operational state
> > >
> > 
> > Unless you define what the terms mean and what ::== means I have no 
> > clue what you are trying to convey here.
> > 
> > /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/>
> 
> -- 
> 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/>
> 

-- 
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

Reply via email to