IETF Logo Mail Archive

Re: [core] Comments on draft-ietf-core-yang-cbor-00

Carsten Bormann <cabo@tzi.org> Mon, 23 May 2016 11:14 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 479D312D67B for <core@ietfa.amsl.com>; Mon, 23 May 2016 04:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 nom1jthLGBVO for <core@ietfa.amsl.com>; Mon, 23 May 2016 04:14:14 -0700 (PDT)
Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [IPv6:2001:4b98:c:538::198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B00012D678 for <core@ietf.org>; Mon, 23 May 2016 04:14:14 -0700 (PDT)
Received: from mfilter22-d.gandi.net (mfilter22-d.gandi.net [217.70.178.150]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id CEB49FB8C9; Mon, 23 May 2016 13:14:12 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter22-d.gandi.net
Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter22-d.gandi.net (mfilter22-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id YHwNDao1afJX; Mon, 23 May 2016 13:14:11 +0200 (CEST)
X-Originating-IP: 93.199.242.26
Received: from nar-3.local (p5DC7F21A.dip0.t-ipconnect.de [93.199.242.26]) (Authenticated sender: cabo@cabo.im) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id AC76BFB8CC; Mon, 23 May 2016 13:14:10 +0200 (CEST)
Message-ID: <5742E600.1010503@tzi.org>
Date: Mon, 23 May 2016 13:14:08 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Ladislav Lhotka <lhotka@nic.cz>
References: <CABCOCHRRACvVXx2S_hZm2TxbvP48aO4Q4REkh0LFjmHkMkZ1Vg@mail.gmail.com> <m2y473svm0.fsf@nic.cz> <57401CC2.2040002@tzi.org> <m237p99gnw.fsf@birdie.labs.nic.cz>
In-Reply-To: <m237p99gnw.fsf@birdie.labs.nic.cz>
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/PmGK6FWXX-uH7wV_OVcDM0OWFYo>
Cc: Core <core@ietf.org>
Subject: Re: [core] Comments on draft-ietf-core-yang-cbor-00
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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 May 2016 11:14:16 -0000

Ladislav Lhotka wrote:
>> We were thinking about possibly adding CBOR tags to disambiguate this.
> 
> This might be a good idea anyway because resolving a union type may
> involve, e.g., (repeated) regular expression matching.

Right, minimizing the complexity of the matcher is a good objective.

Now, how do we use tags to identify the alternatives in the union?
As far as I understand, these can be moved around when the module is
updated.
How do people handle this in their software?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email