Re: [I2rs-proto-dt] [i2rs] inteirm 10/7/20

"Susan Hares" <shares@ndzh.com> Mon, 12 October 2015 06:55 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs-proto-dt@ietfa.amsl.com
Delivered-To: i2rs-proto-dt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 479CF1A1AB6; Sun, 11 Oct 2015 23:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.055
X-Spam-Level:
X-Spam-Status: No, score=-99.055 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, USER_IN_WHITELIST=-100] autolearn=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 a5EM1_J-v5Fv; Sun, 11 Oct 2015 23:55:27 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0867D1A1AB8; Sun, 11 Oct 2015 23:55:26 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=74.43.47.139;
From: Susan Hares <shares@ndzh.com>
To: 'Juergen Schoenwaelder' <j.schoenwaelder@jacobs-university.de>
References: <05c801d102ce$eb398930$c1ac9b90$@ndzh.com> <20151011161106.GA61856@elstar.local>
In-Reply-To: <20151011161106.GA61856@elstar.local>
Date: Mon, 12 Oct 2015 02:55:12 -0400
Message-ID: <00b901d104ba$f3570690$da0513b0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHHBWI2YK0cgP6O7aghYGNeB+dLGgIYY1VbnmqnxNA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs-proto-dt/jmKazvFoIX9BIY61344LOR3n61M>
Cc: i2rs@ietf.org, i2rs-proto-dt@ietf.org
Subject: Re: [I2rs-proto-dt] [i2rs] inteirm 10/7/20
X-BeenThere: i2rs-proto-dt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: I2RS protocol design team <i2rs-proto-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs-proto-dt>, <mailto:i2rs-proto-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs-proto-dt/>
List-Post: <mailto:i2rs-proto-dt@ietf.org>
List-Help: <mailto:i2rs-proto-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs-proto-dt>, <mailto:i2rs-proto-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2015 06:55:28 -0000

Juergen: 

>Identities? I assume you mean schema nodes, do you?  Adding by defining an
YANG extension such as i2rs:ephemeral true? >How does such an i2rs:ephemeral
true interplay with config true/false? What about contexts for must/when
expressions? Or >is the idea to settle on RESTCONF and to work with YANG
patch?

Yes - I should have said schema nodes. 

Sue 

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
Sent: Sunday, October 11, 2015 12:11 PM
To: Susan Hares
Cc: i2rs@ietf.org; i2rs-proto-dt@ietf.org
Subject: Re: [i2rs] inteirm 10/7/20

On Fri, Oct 09, 2015 at 04:13:03PM -0400, Susan Hares wrote:
> The 10/7/2015 interim discussed the ephemeral portion of the protocol
> 
>  
> 
> 1)      Ephemeral state is not unique to zI2RS 
> 
> 2)      The ephemeral datastore is a datastore holds 
> 
> configuration that is intended to not survive a reboot.
>

Configuration as YANG config true or a subset thereof?

> 3)      The ephemeral datastore is never locked.
> 
> 4)      I2RS is using a 2 panes of glass mechanisms
> 
> Pane 1: normal configuration
> 
> Pane 2:  ephemeral state
> 
>  
> 
>                 The I2RS agent and configuration software on
> 
>               the node  must handle this complexity.

So is there one ephemeral datastore or are there multiple?  Some slides say
one per client, others seem to indicate one for all clients.

> 
> 5)      The key word "ephemeral" can be used to identify 
> 
> Identities which are ephemeral in data models.
> 
> Does anyone have any concerns with adding this to Yang?

Identities? I assume you mean schema nodes, do you?  Adding by defining an
YANG extension such as i2rs:ephemeral true? How does such an i2rs:ephemeral
true interplay with config true/false? What about contexts for must/when
expressions? Or is the idea to settle on RESTCONF and to work with YANG
patch?

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

_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs