Re: [core] YANG list to CBOR mapping

Carsten Bormann <cabo@tzi.org> Mon, 23 November 2015 16:50 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6211A9060 for <core@ietfa.amsl.com>; Mon, 23 Nov 2015 08:50:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 8IH9vnuMwQbg for <core@ietfa.amsl.com>; Mon, 23 Nov 2015 08:50:45 -0800 (PST)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [IPv6:2001:4b98:c:538::197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 985721A905F for <core@ietf.org>; Mon, 23 Nov 2015 08:50:45 -0800 (PST)
Received: from mfilter20-d.gandi.net (mfilter20-d.gandi.net [217.70.178.148]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id EF89C41C946; Mon, 23 Nov 2015 17:50:43 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter20-d.gandi.net
Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter20-d.gandi.net (mfilter20-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 3uNCoqeIw1K7; Mon, 23 Nov 2015 17:50:42 +0100 (CET)
X-Originating-IP: 93.199.254.229
Received: from nar.local (p5DC7FEE5.dip0.t-ipconnect.de [93.199.254.229]) (Authenticated sender: cabo@cabo.im) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 736EB41C945; Mon, 23 Nov 2015 17:50:40 +0100 (CET)
Message-ID: <565343DE.3050202@tzi.org>
Date: Mon, 23 Nov 2015 17:50:38 +0100
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Michel Veillette <Michel.Veillette@trilliantinc.com>
References: <170106a36217a736a4b55991c4a5cf6a@xs4all.nl> <BLUPR06MB1763CC28443C787020D60CF7FE1A0@BLUPR06MB1763.namprd06.prod.outlook.com> <b02eb0119020ae52bbddfaed84dc1b01@xs4all.nl> <BLUPR06MB17633FB706D866D2C3E917B0FE070@BLUPR06MB1763.namprd06.prod.outlook.com>
In-Reply-To: <BLUPR06MB17633FB706D866D2C3E917B0FE070@BLUPR06MB1763.namprd06.prod.outlook.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/j3F05VlkZFnK8bhBhf0NcZsPNfo>
Cc: "ana@ackl.io" <ana@ackl.io>, Core <core@ietf.org>
Subject: Re: [core] YANG list to CBOR mapping
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2015 16:50:49 -0000

Michel Veillette wrote:
> Hi Peter
> 
> Have you defined an MergePatch() function similar to RFC 7396 section 2 for your proposed extension?

AFAIK, the function defined by RFC 7396 should "just work".

> Do we intent to support two PATCH approaches, RFC 7396 style and draft-ietf-netconf-yang-patch style?

Good question.  yang-patch seems a bit more complicated than is needed
for many constrained applications.  It also is not idempotent.

> IF so, why list need to be supported by the RFC 7396 style since this approach provide a partial coverage (list without keys and user ordered list is not fully supported) ? Should we address list only in the draft-ietf-netconf-yang-patch style?

I would expect many constrained applications to make use of maps, which
typically are represented in YANG as lists with keys*).  So I would
prefer to be able to address these with a simple, merge-patch style
update mechanism.

Grüße, Carsten

*) leaf-lists are a special case where updating isn't quite addressed
yet by CoMI as far as I know.