Re: [netmod] schema mount and YANG library

Martin Bjorklund <mbj@tail-f.com> Thu, 18 January 2018 07:56 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 B911112EB13 for <netmod@ietfa.amsl.com>; Wed, 17 Jan 2018 23:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Gw45OTMlYJol for <netmod@ietfa.amsl.com>; Wed, 17 Jan 2018 23:56:51 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3009D12EABE for <netmod@ietf.org>; Wed, 17 Jan 2018 23:56:51 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id EC1CD1AE0118; Thu, 18 Jan 2018 08:56:48 +0100 (CET)
Date: Thu, 18 Jan 2018 08:56:48 +0100
Message-Id: <20180118.085648.2091191419931632376.mbj@tail-f.com>
To: lberger@labn.net
Cc: rwilton@cisco.com, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <5d8b65cf-e75e-e11e-a41a-722697ec3af8@labn.net>
References: <16104ca0948.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <20180117.171817.479473055872371790.mbj@tail-f.com> <5d8b65cf-e75e-e11e-a41a-722697ec3af8@labn.net>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/87JZ9QDzUwTq9uqz1_gv1U9FYSU>
Subject: Re: [netmod] schema mount and YANG library
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: Thu, 18 Jan 2018 07:56:55 -0000

Lou Berger <lberger@labn.net> wrote:
> 
> 
> On 1/17/2018 11:18 AM, Martin Bjorklund wrote:
> ...
> >>> My main concern is actually the YL version.  I strongly think SM need
> >>> to use YL-bis rather that the old YL, so that it can support NMDA.
> >>>
> >> Right now to SM is independent of Yang Library version and can run
> >> with either.
> > No this is not correct.  SM uses a grouping from the old YANG
> > library (for the "use-schema" case),
> I thought YLbis was an updat e to UL (i.e., no name change) as such SM
> can include either.

The old "modules-state" structure is deprecated, and a new structure
that allows multiple datastores is defined.  Note that YLbis can be
used by both NMDA-capabale and non-NMDA-capabale servers.

> >   and talks about mounting
> > "modules-state" ("inline" case).
> In informative descriptions only.  Certainly these can be changed to
> allow for YL-bis if need be.
> 
> >> I certainly would expect use of Yang Library bis and nmda
> >> to have advantages.
> >>
> >>> The implementation effort for supporting the new YL in clients and
> >>> servers is minimal, esp. when compared to the efforts involved in
> >>> supporting SM.
> >>>
> >>> Adding an indirection is (for me) less important, but it has the
> >>> benefit of solving the two issues (a) and (b) above, and I haven't
> >>> seen any technical problem with it.
> >>>
> >> (A) has implementation implications and those participating in the
> >> discussion at the time expressed as not being worth the cost.
> >> I don't believe b was seen as a significant issue either.
> >>
> >>> Do you have any technical concerns with using an annotation as an
> >>> indirection?
> >>>
> >> The technicsl issue I have with the approaches the same one that was
> >> raised when debated previously, ie the implementation overhead of
> >> requiring inline schemas to be available at the top level.
> > Ok.  I'm ok with keeping the inline case as it is.  However, I think
> > we need to use the new YL-bis, so that we can support the NMDA.
> Given that NMDA support is not yet fully defined, we're still in the
> transition period where support for both NMDA and non-NMDA
> implementations need to be considered.  Rob presented some options
> earlier in the thread that I think captures this.

Again, note that YLbis supports both NMDA and non-NMDA servers.

Also note that YLbis is just a different read-only monitoring
structure.  Given an implementation that supports the old YL, it is
trivial to add support for YLbis (especially compared to the more than
non-trivial amount of work required to support schema mount...).


/martin