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 11:15 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 F2FED12D110 for <i2rs@ietfa.amsl.com>; Thu, 2 Jun 2016 04:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.749
X-Spam-Level: *
X-Spam-Status: No, score=1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793, T_KAM_HTML_FONT_INVALID=0.01] 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 KhoevTLYIymi for <i2rs@ietfa.amsl.com>; Thu, 2 Jun 2016 04:15:55 -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 BCA2412B076 for <i2rs@ietf.org>; Thu, 2 Jun 2016 04:15:54 -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> <016c01d1bcbd$10aa6ba0$31ff42e0$@ndzh.com> <20160602110449.GC26659@elstar.local>
In-Reply-To: <20160602110449.GC26659@elstar.local>
Date: Thu, 02 Jun 2016 07:15:34 -0400
Message-ID: <017101d1bcc0$1b3a18b0$51ae4a10$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0172_01D1BC9E.942E9330"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
thread-index: AQGbYteCLdCrzIxPBPS4NCrBr2pzpwL+zBapARJ2dYkCgJ24lgHgYBRGAiQAaU+f7gZWkA==
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/0VzKVX0xnifZAbCC7pvOSKC5zTg>
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 11:15:57 -0000

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