IETF Logo Mail Archive

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 14:40 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 677EA12D0ED for <i2rs@ietfa.amsl.com>; Thu, 2 Jun 2016 07:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 h0qLTyTWCcIi for <i2rs@ietfa.amsl.com>; Thu, 2 Jun 2016 07:40:49 -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 B640112D0F1 for <i2rs@ietf.org>; Thu, 2 Jun 2016 07:40:48 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=107.92.120.142;
Date: Thu, 02 Jun 2016 10:40:38 -0400
Message-ID: <vgrpp9a37rgoga07jm7yt7rg.1464878438864@email.android.com>
Importance: normal
From: Susan Hares <shares@ndzh.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_5825557027023280"
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/pcMO89XJj1bd9qJ30jFVdKXl6mo>
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 14:40:51 -0000

Juergen
The definition I was using was operational state (read only )  that is defined under a node defined ephemeral.  Joel challenged that definition saying with split operational state from config - operational state does not need to be under an ephemeral node.
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/2/2016  7:50 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 
I might be able to answer the picture question once I know what is
really meant by 'ephemeral operational state'.

/js

On Thu, Jun 02, 2016 at 07:15:34AM -0400, Susan Hares wrote:
> Juergen: 
> 
>  
> 
> On first sentence, ... restated 
> 
> Do you believe the "ephemeral operational state" belongs in the ephemeral
> requirements? If so, we can add it.  Perhaps we should also add a definition
> for ephemeral configuration. 
> 
>  
> 
> On picture -- here is your picture: 
> 
>  
> 
>    +-------------+                  +-----------+
> 
>    | <candidate> |                  | <startup> |
> 
>    |  (ct, rw)   |<---+        +--->| (ct, rw)  |
> 
>    +-------------+    |        |    +-----------+
> 
>           |           |        |           |
> 
>           |         +------------+         |
> 
>           +-------->| <running>  |<--------+
> 
>                     | (ct, rw)   |
> 
>                     +------------+
> 
>                           |         // e.g., removal of 'inactive' nodes
> 
>                           v
> 
>                     +------------+
> 
>                     | <intended> |  // subject to validation
> 
>                     | (ct, ro)   |
> 
>                     +------------+
> 
>                           |         // e.g., missing resources or delays
> 
>                           v
> 
>                     +------------+
> 
>                     | <applied>  |
> 
>                     | (ct, ro)   |
> 
>                     +------------+
> 
>                           |         // e.g., autodiscovery of values
> 
>                           v
> 
>           +--------------------------------+
> 
>           | <operational-state>            |<-- control plane and
> 
>           | (ct + cf, ro)                  |    ephemeral datastores
> 
>           +--------------------------------+
> 
>  
> 
> Is this part of the picture 
> 
>  
> 
>           +--------------------------------+
> 
>           | <operational-state>            |<-- control plane and
> 
>           | (ct + cf, ro)                  |    ephemeral datastores
> 
>           +--------------------------------+
> 
>  
> 
> Really 
> 
>   +--------------------+    +--------------------------+
> +-----------------------+
> 
>  |    opstate         |    | ephemeral config  |   | applied  config    |
> 
>  | (cf, ro)               |    |   (ct, ro, ephemeral|  | (ct, ro)
> |
> 
>  +--------------------+    +---------------------------+
> +-------------------------+
> 
>  
> 
> Or just 
> 
>   +--------------------+    +--------------------------+    
> 
>   |    opstate         |    | ephemeral config  |    
> 
>   | (cf, ro)               |    |   (ct, ro, ephemeral 
> 
>   +--------------------+    +---------------------------+   
> 
>  
> 
>  
> 
> Sue 
> 
>  
> 
> -----Original Message-----
> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
> Sent: Thursday, June 02, 2016 7:05 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
> 
>  
> 
> 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/>
> http://www.jacobs-university.de/>
> 
>  
> 
> _______________________________________________
> 
> i2rs mailing list
> 
>  <mailto:i2rs@ietf.org> i2rs@ietf.org
> 
>  <https://www.ietf.org/mailman/listinfo/i2rs>
> https://www.ietf.org/mailman/listinfo/i2rs
> 

-- 
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
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs

v2.23.0 | Report a Bug | By Email