Re: [netmod] leaf-list in YANG 1.1

Alex Campbell <Alex.Campbell@Aviatnet.com> Tue, 29 May 2018 02:14 UTC

Return-Path: <Alex.Campbell@Aviatnet.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 F0453127775 for <netmod@ietfa.amsl.com>; Mon, 28 May 2018 19:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 qBCybwA_pLgf for <netmod@ietfa.amsl.com>; Mon, 28 May 2018 19:14:03 -0700 (PDT)
Received: from mail-send.aviatnet.com (mail-send.aviatnet.com [192.147.115.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B578126DD9 for <netmod@ietf.org>; Mon, 28 May 2018 19:14:03 -0700 (PDT)
From: Alex Campbell <Alex.Campbell@Aviatnet.com>
To: "Bogaert, Bart (Nokia - BE/Antwerp)" <bart.bogaert@nokia.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: leaf-list in YANG 1.1
Thread-Index: AdP25fycB9A0DIxRRXyoayBZtavGuAADKpdC
Date: Tue, 29 May 2018 02:14:00 +0000
Message-ID: <1527560040669.32302@Aviatnet.com>
References: <DB6PR07MB442102BCE3D8DD74BE45BB40946D0@DB6PR07MB4421.eurprd07.prod.outlook.com>
In-Reply-To: <DB6PR07MB442102BCE3D8DD74BE45BB40946D0@DB6PR07MB4421.eurprd07.prod.outlook.com>
Accept-Language: en-NZ, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.15.6.10]
Content-Type: multipart/alternative; boundary="_000_152756004066932302Aviatnetcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/3gvYqx9Xqv8JVNPkP9A8G9jw6SA>
Subject: Re: [netmod] leaf-list in YANG 1.1
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: Tue, 29 May 2018 02:14:05 -0000

As far as I'm aware, state values are not writable by the client, so the question is moot.


Regards, Alex


________________________________
From: netmod <netmod-bounces@ietf.org> on behalf of Bogaert, Bart (Nokia - BE/Antwerp) <bart.bogaert@nokia.com>
Sent: Tuesday, 29 May 2018 12:56 p.m.
To: netmod@ietf.org
Subject: [netmod] leaf-list in YANG 1.1

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi,

We have a question about the leaf-list in config-false data.  When comparing YANG 1.0 and YANG 1.1 the restriction on having unique values seems to have been lifted for config-false data:

  *   Section 7.7 RFC 7950: "In configuration data, the values in a leaf-list MUST be unique."
  *   Section 7.7 RFC 6020: "The values in a leaf-list MUST be unique.")

This means one can have multiple entries with the same value in a state leaf-list.  What is expected to happen when you delete an entry by specifying the value of the leaf-list entry and there happen to be multiple entries with the same value? Are all these entries deleted or is one expected to perform as many delete operations as there are entries matching the value specified in the delete operation?

Regards, Bart