Re: [netmod] Adding a pre-existing leaf into a new 'choice' - NBC change?

Ladislav Lhotka <lhotka@nic.cz> Fri, 23 November 2018 09:55 UTC

Return-Path: <lhotka@nic.cz>
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 42596130E0F for <netmod@ietfa.amsl.com>; Fri, 23 Nov 2018 01:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 YuSFchPTQcYf for <netmod@ietfa.amsl.com>; Fri, 23 Nov 2018 01:55:11 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87929130DFC for <netmod@ietf.org>; Fri, 23 Nov 2018 01:55:11 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:718:1a02:1::380]) by mail.nic.cz (Postfix) with ESMTPSA id D3FA4642D7 for <netmod@ietf.org>; Fri, 23 Nov 2018 10:55:09 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1542966909; bh=sWAPdPIa51z86uJ6gI2AH8eHwCeCTSy7DZyJumAcajg=; h=From:To:Date; b=V0ddKfEjenaGXGuZulHS/Dl+eUY6E+hC51NAAyCY4pkiG1v39yci4flrLGW2HfQ0/ PczSHWK5axv9FjOxo3x+hqu1uP9+KpYvgJ7n3+Y/f05qCa28468qn5q26zp9WVLl4A Wj8S6ByYQ1SOjNsIaH/EBQgIKwzDkN9ZMDS1jUVU=
Message-ID: <70587074aed82edac5e4ab1cbf2479e14edca626.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: netmod@ietf.org
Date: Fri, 23 Nov 2018 10:55:09 +0100
In-Reply-To: <20181123093813.gpxrtanbxgadpwih@anna.jacobs.jacobs-university.de>
References: <87wop5kzgb.fsf@nic.cz> <20181122.143948.1543843065251732639.mbj@tail-f.com> <CABCOCHS18StYKGC4f7cPWFraKNHRsC9cWfrmfZ0j773awdicvQ@mail.gmail.com> <20181122.150027.823800945772964674.mbj@tail-f.com> <20181122163046.bkzck2bmbrf3fzm7@anna.jacobs.jacobs-university.de> <87tvk85et8.fsf@nic.cz> <20181123093813.gpxrtanbxgadpwih@anna.jacobs.jacobs-university.de>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.2
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/PlhnpLRmSnT5_AAaD76UTy1Ytfo>
Subject: Re: [netmod] Adding a pre-existing leaf into a new 'choice' - NBC change?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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, 23 Nov 2018 09:55:14 -0000

On Fri, 2018-11-23 at 10:38 +0100, Juergen Schoenwaelder wrote:
> On Fri, Nov 23, 2018 at 10:22:11AM +0100, Ladislav Lhotka wrote:
> > Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> writes:
> > 
> > > On Thu, Nov 22, 2018 at 03:00:27PM +0100, Martin Bjorklund wrote:
> > > > Andy Bierman <andy@yumaworks.com> wrote:
> > > > > 9.9 <https://tools.ietf.org/html/rfc7950#section-9.9>;.  The leafref
> > > > > Built-In Type
> > > > > 
> > > > >    The leafref built-in type is restricted to the value space of some
> > > > >    leaf or leaf-list node in the schema tree and optionally further
> > > > >    restricted by corresponding instance nodes in the data tree.  The
> > > > >    "path" substatement (Section 9.9.2
> > > > > <https://tools.ietf.org/html/rfc7950#section-9.9.2>;) is used to
> > > > > identify the referred
> > > > >    leaf or leaf-list node in the schema tree.  The value space of the
> > > > >    referring node is the value space of the referred node.
> > > > 
> > > > Yes, it should be "data tree" in both occurrences.
> > > 
> > > Time for an errata?
> > 
> > Here is the old discussion thread:
> > 
> > https://www.ietf.org/mail-archive/web/netmod/current/msg15979.html
> > 
> > Everything relevant had been extensively discussed in it, and I am
> > sceptical that we can come up with anything significantly better - it
> > will only be more (or different) hand-waving. The problem is inherent in
> > the leafref design introduced in YANG 1.1. It won't go away no matter
> > how much we paper over it.
> > 
> 
> So you think the use of 'schema tree' in the text quoted above (is
> used to identify the referred leaf or leaf-list node in the schema
> tree) is correct??

It is certainly more correct than "data tree". The assumption is that the "path"
statement (that by definition selects some instance nodes in the data tree) also
implicitly points to a leaf or leaf-list node iin the schema tree.

> 
> I do not want to discuss whether you like the design of leafrefs or
> not here - at this time we should focus on whether the text is correct
> or not given the design we have. So again, you think that 'schema
> tree' is correct in the statement?

There are two problems with it:

1. There may be no such schema node, because it can be possibly invalidated by a
"when" expression.

2. The term "value space" is not defined.

Lada

> 
> /js
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67