Re: [Yot] [I-D.ietf-core-yang-cbor] update

Carsten Bormann <cabo@tzi.org> Thu, 08 February 2018 15:51 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: yot@ietfa.amsl.com
Delivered-To: yot@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D18A126E64 for <yot@ietfa.amsl.com>; Thu, 8 Feb 2018 07:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 eEW60XhI2dYy for <yot@ietfa.amsl.com>; Thu, 8 Feb 2018 07:51:12 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 9D80D126BF3 for <yot@ietf.org>; Thu, 8 Feb 2018 07:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w18Fp7vl011875; Thu, 8 Feb 2018 16:51:07 +0100 (CET)
Received: from [IPv6:2001:638:708:18::71] (unknown [IPv6:2001:638:708:18::71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3zcjNC27NCzDXJQ; Thu, 8 Feb 2018 16:51:07 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <BN6PR06MB230801BB8CBE448B3DBA2969FEFE0@BN6PR06MB2308.namprd06.prod.outlook.com>
Date: Thu, 08 Feb 2018 16:51:06 +0100
Cc: "yot@ietf.org" <yot@ietf.org>, Michael Richardson <mcr@sandelman.ca>
X-Mao-Original-Outgoing-Id: 539797865.194033-3a4e70b2ac5c723874ea0a3c6c290cd8
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB2014BB-869A-4B26-846A-1181B7A3401A@tzi.org>
References: <BN6PR06MB230801BB8CBE448B3DBA2969FEFE0@BN6PR06MB2308.namprd06.prod.outlook.com>
To: Michel Veillette <Michel.Veillette@trilliantinc.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/sdt2dUgJDpFRNdBUSX8F1rNqy38>
Subject: Re: [Yot] [I-D.ietf-core-yang-cbor] update
X-BeenThere: yot@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Yang of Things <yot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yot>, <mailto:yot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yot/>
List-Post: <mailto:yot@ietf.org>
List-Help: <mailto:yot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yot>, <mailto:yot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2018 15:51:14 -0000

On Feb 5, 2018, at 23:25, Michel Veillette <Michel.Veillette@trilliantinc.com> wrote:
> 
> Draft [I-D.ietf-core-yang-cbor] have been updated to support YANG data templates defined using the yang-data extension. YANG data templates are used by CoMI to define the CoAP error payload and in [I-D.richardson-anima-ace-constrained-voucher-02] to define a voucher encoded in CBOR.

So how do we handle the media types (content-formats) for this?

Obviously, specifications that make heavy use of yang-data may want to define their own media types.
On the other hand, the top level SID is already useful for finding out what yang module is being used, so defining a generic media type for yang-data in CBOR (like the ones defined as “application/yang-data+xml” and “application/yang-data+json” in RFC 8040) would make sense.

Grüße, Carsten