Re: [netmod] YANG library structure

Martin Bjorklund <mbj@tail-f.com> Fri, 08 December 2017 14:08 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F537124D68 for <netmod@ietfa.amsl.com>; Fri, 8 Dec 2017 06:08:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 r55F94xx61bR for <netmod@ietfa.amsl.com>; Fri, 8 Dec 2017 06:08:35 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id C33B1124D37 for <netmod@ietf.org>; Fri, 8 Dec 2017 06:08:34 -0800 (PST)
Received: from localhost (h-85-209.A165.priv.bahnhof.se [94.254.85.209]) by mail.tail-f.com (Postfix) with ESMTPSA id 7C1F41AE0398; Fri, 8 Dec 2017 15:08:31 +0100 (CET)
Date: Fri, 08 Dec 2017 15:08:31 +0100 (CET)
Message-Id: <20171208.150831.2068512524982133442.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: lberger@labn.net, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20171208121434.2vfbrc5pdbwnx3ig@elstar.local>
References: <20171208111504.iwpcck3hkbboryeo@elstar.local> <acd4d422-c260-3f70-c09f-18946a642c02@labn.net> <20171208121434.2vfbrc5pdbwnx3ig@elstar.local>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/lnaYrBvhqLmO8xmbJlZlFvtMOSo>
Subject: Re: [netmod] YANG library structure
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Dec 2017 14:08:36 -0000

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> On Fri, Dec 08, 2017 at 07:08:32AM -0500, Lou Berger wrote:
> > On 12/08/2017 06:15 AM, Juergen Schoenwaelder wrote:
> > >  
> > >> In talking to some others on this topic, they suggested using a library per
> > >> datastore. I haven't look into this enough to know if that is a good or bad
> > >> idea, but it seems functionally equivalent to your first option but realized
> > >> in a different way. Just something to add to the mix.
> > > If people want to put additional options on the table, they should
> > > work out the details and write down a tree diagram and send the result
> > > to the list.
> > 
> > I guess we have a different philosophical approach here.  I'd prefer to
> > hear about fresh ideas, even if half baked or asked as a "stupid
> > question". Sometimes, if not dismissed out of hand, these lead to
> > something that is a better result than others that have been immersed in
> > the issue have thought of.
> >
> 
> The devil is usally in the details and 'using a library per datastore'
> is for my taste a bit too little to understand what is actually being
> proposed. I am not dismissing proposals, but I like to be able to
> understand what is being proposed. And for that I need a proposal that
> is a bit more than 'using a library per datastore'.

I agree.  In this case, I can't understand how it would work at all.
The library is config false, so a client can never get it via
get-config from <running>.  Maybe the proposal is a new operation
<get-yang-library> with the datastore as a parameter?  Or maybe the
idea is to somehow return meta data together with <get-config>?  I can
guess, and dismiss the proposal based on my guesses ;-)  Or someone
can write up a concrete proposal.


/martin