Re: [netmod] draft-ietf-netmod-rfc6087bis-13 - section 4.26.2

Martin Bjorklund <mbj@tail-f.com> Mon, 28 August 2017 11:13 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 F3CB813213F for <netmod@ietfa.amsl.com>; Mon, 28 Aug 2017 04:13:11 -0700 (PDT)
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 mFWA37j6AJpB for <netmod@ietfa.amsl.com>; Mon, 28 Aug 2017 04:13:10 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id C75791329C5 for <netmod@ietf.org>; Mon, 28 Aug 2017 04:13:09 -0700 (PDT)
Received: from localhost (unknown [173.38.220.57]) by mail.tail-f.com (Postfix) with ESMTPSA id EA6181AE043A; Mon, 28 Aug 2017 13:13:07 +0200 (CEST)
Date: Mon, 28 Aug 2017 13:11:40 +0200
Message-Id: <20170828.131140.1417940736768839828.mbj@tail-f.com>
To: bart.bogaert@nokia.com
Cc: netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <AM2PR07MB06272C83075A2F7404910829949E0@AM2PR07MB0627.eurprd07.prod.outlook.com>
References: <AM2PR07MB06272C83075A2F7404910829949E0@AM2PR07MB0627.eurprd07.prod.outlook.com>
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/q0O8M-55uE1Mwom7mGNG_Cc0q5w>
Subject: Re: [netmod] draft-ietf-netmod-rfc6087bis-13 - section 4.26.2
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: Mon, 28 Aug 2017 11:13:12 -0000

Hi,

"Bogaert, Bart (Nokia - BE/Antwerp)" <bart.bogaert@nokia.com> wrote:
> I would like to understand why the YANG 1.1 feature logic is *much more
> expensive* than YANG 1.0.

The document says "much more _expressive_".

> As far as I can see the way YANG features are
> being defined has not changed between YANG 1.0 and YANG 1.1.

if-feature can in YANG 1.1 be a boolean expression of features, e.g.,
"foo or bar and not baz".


> On the other hand, the second paragraph of this section seems to deal with
> "when" versus "if-feature" and the preference to use if-feature instead of
> when, if possible.  But as far as I'm aware there are no changes w.r.t. when
> between YANG 1.0 and YANG 1.1.  This paragraph seems to suggest that "when"
> is worse than if-feature.  I can understand that when is to be evaluated and
> depends on the when-condition while a feature can be considered as a design
> and implementation choice (the feature is supported or not) and does not
> need any run-time 'validation'.  But why is this so different in YANG 1.1
> versus YANG 1.0?

This was true also in 1.0 (i.e., 'if-feature' is simpler than 'when')



/martin




> Where can we find more background on the statement made in this section
> about much more expensive and what exactly is meant by this, certainly when
> we want to see this in the perspective of the run-time characteristics and
> impact on a NC server running in a device.
> 
>  
> 
> Thanks in advance,
> 
> Bart
>