Re: [netmod] draft-ietf-netmod-rfc6991-bis: Comment on node-instance-identifier

Per Hedeland <per@hedeland.org> Mon, 04 November 2019 12:19 UTC

Return-Path: <per@hedeland.org>
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 A9BCD120058; Mon, 4 Nov 2019 04:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 dkmjKHvlozBx; Mon, 4 Nov 2019 04:19:55 -0800 (PST)
Received: from mailout.easydns.com (mailout.easydns.com [64.68.202.10]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA71120019; Mon, 4 Nov 2019 04:19:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailout.easydns.com (Postfix) with ESMTP id 66C68C1429; Mon, 4 Nov 2019 12:19:54 +0000 (UTC)
Received: from mailout.easydns.com ([127.0.0.1]) by localhost (emo12-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tKo9-JO8gmv6; Mon, 4 Nov 2019 12:19:54 +0000 (UTC)
Received: from hedeland.org (81-228-157-209-no289.tbcn.telia.com [81.228.157.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easydns.com (Postfix) with ESMTPSA id F1218C13E3; Mon, 4 Nov 2019 12:19:49 +0000 (UTC)
Received: from pluto.hedeland.org (pluto.hedeland.org [10.1.1.5]) by tellus.hedeland.org (8.15.2/8.15.2) with ESMTPS id xA4CJlu6030740 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 4 Nov 2019 13:19:47 +0100 (CET) (envelope-from per@hedeland.org)
To: =?UTF-8?B?U2Now7Zud8OkbGRlciwgSsO8cmdlbg==?= <J.Schoenwaelder@jacobs-university.de>, Robert Wilton <rwilton@cisco.com>
Cc: "netmod@ietf.org" <netmod@ietf.org>, "draft-ietf-netmod-rfc6991-bis@ietf.org" <draft-ietf-netmod-rfc6991-bis@ietf.org>
References: <9878ec54-4b3b-e83c-a60c-973478de11f4@cisco.com> <20191104103242.prnszis5olcfzcyl@anna.jacobs.jacobs-university.de>
From: Per Hedeland <per@hedeland.org>
Message-ID: <14e342e5-cd63-898b-4b77-0537b4d3c3b4@hedeland.org>
Date: Mon, 4 Nov 2019 13:19:47 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <20191104103242.prnszis5olcfzcyl@anna.jacobs.jacobs-university.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ZyaYCcY3O7sdaVRkYGflamMY8IU>
Subject: Re: [netmod] draft-ietf-netmod-rfc6991-bis: Comment on node-instance-identifier
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: Mon, 04 Nov 2019 12:19:57 -0000

On 2019-11-04 11:32, Schönwälder, Jürgen wrote:
> Hi,
> 
> this may be resolved by adding
> 
>       The special value '/' refers to the entire accessible tree.
> 
> to the description statement. Does this work for you?

Hm, it seems to me that this would conflict with this part of the
description:

        A node-instance-identifier value is an
        unrestricted YANG instance-identifier expression.

        All the same rules as an instance-identifier apply,
        except that predicates for keys are optional.  If a key
        predicate is missing, then the node-instance-identifier
        represents all possible server instances for that key.

- since '/' is not a valid value for a YANG instance-identifier.
I.e. if '/' should be included in the typedef (seems reasonable to
me), the text for it probably needs to be "incorporated" in the text
above.

--Per

> /js
> 
> On Mon, Sep 30, 2019 at 03:17:25PM +0100, Robert Wilton wrote:
>> Hi Juergen,
>>
>> Should the "node-instance-identify" type specify how the path "/" is
>> treated?
>>
>> I noted that in rfc8341, the behavior for "/" is described in the leaf
>> "path" description rather than in the type definition, but I was thinking
>> that it might be better if this behaviour was specified as part of the
>> typedef.
>>
>> Snippet from RFC8341:
>>
>>               case data-node {
>>                 leaf path {
>>                   type node-instance-identifier;
>>                   mandatory true;
>>                   description
>>                     "Data node instance-identifier associated with the
>>                      data node, action, or notification controlled by
>>                      this rule.
>>
>>                      Configuration data or state data
>>                      instance-identifiers start with a top-level
>>                      data node.  A complete instance-identifier is
>>                      required for this type of path value.
>>
>>                      The special value '/' refers to all possible
>>                      datastore contents.";
>>                 }
>>               }
>>
>> Thanks,
>> Rob
>>
>