Re: [i2rs] Kathleen Moriarty's No Objection on draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT)

"Susan Hares" <shares@ndzh.com> Wed, 25 January 2017 17:57 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 15A72129AA2; Wed, 25 Jan 2017 09:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] 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 yRJYJaXN3AAQ; Wed, 25 Jan 2017 09:57:19 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [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 AE6B7129A9B; Wed, 25 Jan 2017 09:57:18 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.13.195;
From: Susan Hares <shares@ndzh.com>
To: 'Juergen Schoenwaelder' <j.schoenwaelder@jacobs-university.de>, 'Giles Heron' <giles.heron@gmail.com>
References: <CAG4d1rf+HNHfN0qNRpZKC2NZnj9gjKUdiHU9H-56J6-pefs3dA@mail.gmail.com> <20170125145217.GF41033@elstar.jacobs.jacobs-university.de> <CAG4d1rehjq327TTBk1n4gyRBL4yT97vnXN4sdjwYJp7aaT926g@mail.gmail.com> <20170125151802.GA41293@elstar.jacobs.jacobs-university.de> <733F61EE-456C-4F71-B7B4-D1965BDCC36C@gmail.com> <20170125153326.GH41033@elstar.jacobs.jacobs-university.de>
In-Reply-To: <20170125153326.GH41033@elstar.jacobs.jacobs-university.de>
Date: Wed, 25 Jan 2017 12:52:47 -0500
Message-ID: <01b101d27733$d7826490$86872db0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDMDDOlqUr6NUq+FONL11ADZxeNCgGvnhE+AZ//NCkDIpJlDQJvvn+6AfFrv3ei/7PQ8A==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/mZvTgHhLXCLCfDSngiQJO24JygM>
Cc: draft-ietf-i2rs-yang-l3-topology@ietf.org, i2rs@ietf.org, 'Lou Berger' <lberger@labn.net>, iesg@ietf.org, 'Alia Atlas' <akatlas@gmail.com>
Subject: Re: [i2rs] Kathleen Moriarty's No Objection on draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT)
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: Wed, 25 Jan 2017 17:57:20 -0000

Juergen: 
 
"And with the revised datastore model it will also be straight forward to have an implementation that just exposes topological data via the operational state datastore.  And the revised datastore model also paves the path to support datastores that can also inject ephemeral data."

Where do you believe the revised data store model suggest ephemeral data can be injected - (?written)? 

Sue 

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
Sent: Wednesday, January 25, 2017 10:33 AM
To: Giles Heron
Cc: draft-ietf-i2rs-yang-l3-topology@ietf.org; i2rs@ietf.org; Lou Berger; iesg@ietf.org; Alia Atlas
Subject: Re: [i2rs] Kathleen Moriarty's No Objection on draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT)

On Wed, Jan 25, 2017 at 03:19:58PM +0000, Giles Heron wrote:
> 
> > On 25 Jan 2017, at 15:18, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> > 
> > On Wed, Jan 25, 2017 at 10:07:45AM -0500, Alia Atlas wrote:
> >> 
> >> So - if one has models - such as a writable topology - where there 
> >> can be dependencies on dynamic data, then those models can't be in 
> >> the configuration data-store as currently defined.
> >> 
> > 
> > Yes
> 
> but isn’t this confusing models and implementation?

I just confirmed that the old datastore model does not support writable ephemeral datastores. No more no less. And there is work in NETMOD (and NETCONF) to revise the datastore model and to make data model reuse in different datastores even simpler.
 
> if you have a case where you have a dependency on dynamic data then you can’t put that instantiation of the model in the configuration data-store.
> 
> but if your implementation never depends on dynamic data then it ought to be fine.

Yes. This should be fine.

And with the revised datastore model it will also be straight forward to have an implementation that just exposes topological data via the operational state datastore.  And the revised datastore model also paves the path to support datastores that can also inject ephemeral data.

/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