Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am -? Topic: Ephemeral State Requirements

"Susan Hares" <shares@ndzh.com> Thu, 02 June 2016 10:54 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64ECC12D132 for <i2rs@ietfa.amsl.com>; Thu, 2 Jun 2016 03:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.738
X-Spam-Level: *
X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, RDNS_NONE=0.793] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gJuxwQTSFKOg for <i2rs@ietfa.amsl.com>; Thu, 2 Jun 2016 03:54:09 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D02F212D126 for <i2rs@ietf.org>; Thu, 2 Jun 2016 03:54:08 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.63;
From: Susan Hares <shares@ndzh.com>
To: 'Juergen Schoenwaelder' <j.schoenwaelder@jacobs-university.de>
References: <6qtqondee9e8m6od11bh1ilt.1464783874424@email.android.com> <20160601123117.GB24741@elstar.local> <014801d1bc06$98eed670$cacc8350$@ndzh.com> <20160602103621.GA26659@elstar.local>
In-Reply-To: <20160602103621.GA26659@elstar.local>
Date: Thu, 02 Jun 2016 06:53:42 -0400
Message-ID: <016c01d1bcbd$10aa6ba0$31ff42e0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
thread-index: AQGbYteCLdCrzIxPBPS4NCrBr2pzpwL+zBapARJ2dYkCgJ24lqAOITYg
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/--UD8vEgMfKVJgsZpIkXJG3AcKQ>
Cc: 'Jeffrey Haas' <jhaas@pfrc.org>, i2rs@ietf.org, 'Benoit Claise' <bclaise@cisco.com>, 'Alia Atlas' <akatlas@gmail.com>
Subject: Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am -? Topic: Ephemeral State Requirements
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 10:54:10 -0000

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

Sue 


 

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
Sent: Thursday, June 02, 2016 6:36 AM
To: Susan Hares
Cc: 'Jeffrey Haas'; i2rs@ietf.org; 'Benoit Claise'; 'Alia Atlas'
Subject: Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am
-? Topic: Ephemeral State Requirements

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:j.schoenwaelder@jacobs-university.de]
> Sent: Wednesday, June 01, 2016 8:31 AM
> To: Susan Hares
> Cc: 'Jeffrey Haas'; i2rs@ietf.org; '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 
> <j.schoenwaelder@jacobs-university.de> Date: 6/1/2016  4:25 AM  
> (GMT-05:00)
> To: Susan Hares <shares@ndzh.com> Cc: 'Jeffrey Haas' <jhaas@pfrc.org>, 
> i2rs@ietf.org, 'Benoit Claise' <bclaise@cisco.com>, 'Alia Atlas'
> <akatlas@gmail.com> 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/>