Re: [i2rs] Ephemeral State Requirements discussion

"Susan Hares" <shares@ndzh.com> Mon, 06 June 2016 19:07 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 05DBB12D529 for <i2rs@ietfa.amsl.com>; Mon, 6 Jun 2016 12:07:22 -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 r_UkAoFdcGo8 for <i2rs@ietfa.amsl.com>; Mon, 6 Jun 2016 12:07:21 -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 2370E12B02A for <i2rs@ietf.org>; Mon, 6 Jun 2016 12:07:21 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.192.86;
From: Susan Hares <shares@ndzh.com>
To: 'Juergen Schoenwaelder' <j.schoenwaelder@jacobs-university.de>
References: <20160531063840.GA21289@elstar.local> <026df5be-4a60-f340-60aa-d713a0e75c48@joelhalpern.com> <20160531184844.GB22928@elstar.local> <413ef504-49a8-2ba2-7fd4-582a41bd0ad0@joelhalpern.com> <20160531192729.GA23116@elstar.local> <005801d1bb7a$e7b2e440$b718acc0$@ndzh.com> <20160601091953.GD24118@elstar.local> <20160602142733.GU17462@pfrc.org> <20160606174413.GA7492@elstar.local> <01a701d1c01f$918dbf00$b4a93d00$@ndzh.com> <20160606183122.GA7624@elstar.local>
In-Reply-To: <20160606183122.GA7624@elstar.local>
Date: Mon, 06 Jun 2016 15:07:13 -0400
Message-ID: <021201d1c026$a26da540$e748efc0$@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: AQI0uYM8sjGjGwBI4gABc7Ny2GzULQK0BcphAi793oQBuWOzdwI595xIAmQeUIICKRsUlAGlb1GWAf+1h4wCu7lVpQJ3IH1PnmT4RrA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/LruXFtwXoErrVYDPkNm3OzS9KL0>
Cc: 'Jeffrey Haas' <jhaas@pfrc.org>, i2rs@ietf.org, "'Joel M. Halpern'" <jmh@joelhalpern.com>
Subject: Re: [i2rs] Ephemeral State Requirements discussion
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: Mon, 06 Jun 2016 19:07:22 -0000

Juergen: 

Please start by defining validation for NETCONF configuration.  Then, we can
provide the additions for ephemeral configuration state that are not in
ephemeral requirements.  See the rest of the comments below. 

Sue 

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
Sent: Monday, June 06, 2016 2:31 PM
To: Susan Hares
Cc: 'Jeffrey Haas'; i2rs@ietf.org; 'Joel M. Halpern'
Subject: Re: [i2rs] Ephemeral State Requirements discussion

On Mon, Jun 06, 2016 at 02:16:38PM -0400, Susan Hares wrote:
>> Juergen: 
>> 
>> I2RS Ephemeral Configuration - is configuration which needs 
>> validation, but does not survive a reboot.

> Sue, 'validation' is not enough; there needs to be a clearer definition
what 'validation' means.
 
>> I2RS data models which are "ephemeral at top node" and have 
>> operational state.  In these models, the operational state is like all 
>> other operational state.

>The phrase 'ephemeral at top node' just confuses me.

  module: ietf-i2rs-rib
      +--rw routing-instance  (what do NETCONF people call this node?) 


> I suggest we focus on the I2RS ephemeral Configuration.  On this topic 
> you stated below:
>  
> "Again, for configuration datastores, I can obtain the config and 
> validate it pretty much anywhere, on the device or offline at a 
> controller. My understanding is that this would not be true for I2RS'
> ephemeral stat datastores; I would need some amount of additional data 
> to do something close to YANG's configuration datastore validation."
> 
> Why is this not true for ephemeral datastore?  I am missing any reason 
> why you think this is true.

>Configuration datastore validation works because data is self-consistent
without references to any (external) state. 
>Are you saying that the same is true for I2RS' ephemeral datastores?

Please define what NETCONF/RESTCONF/NETMOD means by external state?  
See Ephemeral-REQ-01 to Ephemeral-REQ-04 which specify the external state
references.  
    
/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