Re: [core] CBOR Encoding of Data Modeled with YANG
Michel Veillette <Michel.Veillette@trilliantinc.com> Fri, 11 December 2015 15:22 UTC
Return-Path: <Michel.Veillette@trilliantinc.com>
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 DC6D61B2A73 for <core@ietfa.amsl.com>; Fri, 11 Dec 2015 07:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 4scSso4CGbz7 for <core@ietfa.amsl.com>; Fri, 11 Dec 2015 07:22:33 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0750.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:750]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C277B1B2A05 for <core@ietf.org>; Fri, 11 Dec 2015 07:22:32 -0800 (PST)
Received: from BLUPR06MB1763.namprd06.prod.outlook.com (10.162.224.149) by BLUPR06MB1761.namprd06.prod.outlook.com (10.162.224.147) with Microsoft SMTP Server (TLS) id 15.1.355.16; Fri, 11 Dec 2015 15:22:10 +0000
Received: from BLUPR06MB1763.namprd06.prod.outlook.com ([10.162.224.149]) by BLUPR06MB1763.namprd06.prod.outlook.com ([10.162.224.149]) with mapi id 15.01.0355.012; Fri, 11 Dec 2015 15:22:10 +0000
From: Michel Veillette <Michel.Veillette@trilliantinc.com>
To: Ladislav Lhotka <lhotka@nic.cz>
Thread-Topic: [core] CBOR Encoding of Data Modeled with YANG
Thread-Index: AdEtPHYWp5+Kr9OtQ0Oj//Irn0p12QGuw2eAAAChYQAACegR0AAA6emAAABLczA=
Date: Fri, 11 Dec 2015 15:22:10 +0000
Message-ID: <BLUPR06MB1763FBE41C0F67D60F4C6CBDFEEA0@BLUPR06MB1763.namprd06.prod.outlook.com>
References: <BLUPR06MB176391F16B5E9D6CCC531771FE0E0@BLUPR06MB1763.namprd06.prod.outlook.com> <m2zixhwcl2.fsf@birdie.labs.nic.cz> <566A9D84.8020809@tzi.org> <BLUPR06MB1763219CCE11D928B2168FFBFEEA0@BLUPR06MB1763.namprd06.prod.outlook.com> <E1492607-F3BA-4FA5-9BD4-4F7746171747@nic.cz>
In-Reply-To: <E1492607-F3BA-4FA5-9BD4-4F7746171747@nic.cz>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michel.Veillette@trilliantinc.com;
x-originating-ip: [207.96.192.122]
x-microsoft-exchange-diagnostics: 1; BLUPR06MB1761; 5:TfnaS841KYB9QdbkIbS5Yb+q3mcgiEJhV7vpXAcsqtwAbeMDyBSCvyW5QqrC533C7QgAX94wQwwU5QQMkByKIPV1PrFqtfpZkqIqr3Tie7la39pk2ket/yf8Wji9SlUtOaazETJjBcICHPIcnFz1lw==; 24:ykGkpMvI8SjaswyxOUuOjU/qutB4ggyxMLlLVSw5m6SiCtUK44KSKUHszjoXc/Tw2zQZZzssR3JpLPaFDbsEVqgqsb9NSFS8agEUwzSZSPI=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR06MB1761;
x-microsoft-antispam-prvs: <BLUPR06MB176108D9F5A0F69A96434CB1FEEA0@BLUPR06MB1761.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(256376046250027);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(520078)(8121501046)(5005006)(10201501046)(3002001); SRVR:BLUPR06MB1761; BCL:0; PCL:0; RULEID:; SRVR:BLUPR06MB1761;
x-forefront-prvs: 0787459938
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(13464003)(377454003)(189002)(24454002)(2900100001)(77096005)(92566002)(81156007)(101416001)(76176999)(54356999)(33656002)(2950100001)(93886004)(106356001)(40100003)(66066001)(86362001)(575784001)(50986999)(122556002)(105586002)(99286002)(97736004)(11100500001)(5004730100002)(10400500002)(74316001)(102836003)(87936001)(5002640100001)(3846002)(5001960100002)(586003)(5008740100001)(189998001)(6116002)(110136002)(5003600100002)(19580405001)(1220700001)(1096002)(76576001)(19580395003); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR06MB1761; H:BLUPR06MB1763.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: trilliantinc.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: trilliantinc.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Dec 2015 15:22:10.1667 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB1761
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/FE-NA8qiwHYlRffCtCqYBO_8N-k>
Cc: Core <core@ietf.org>
Subject: Re: [core] CBOR Encoding of Data Modeled with YANG
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: Fri, 11 Dec 2015 15:22:35 -0000
I plan to propose an update to section 3.1.7 based on the text of draft-ietf-netmod-yang-json-06 section 6.8. I can either use the module name or the module ID as namespace identifier. For compactness, I intent to initially propose the module ID. For example, if the module ID registered for iana-if-type is 72, we will have "72:ethernetCsmacd". Is this make sense? Regards, Michel -----Original Message----- From: Ladislav Lhotka [mailto:lhotka@nic.cz] Sent: December-11-15 10:05 AM To: Michel Veillette <Michel.Veillette@trilliantinc.com> Cc: Carsten Bormann <cabo@tzi.org>; Core <core@ietf.org> Subject: Re: [core] CBOR Encoding of Data Modeled with YANG > On 11 Dec 2015, at 15:50, Michel Veillette <Michel.Veillette@trilliantinc.com> wrote: > > Hi Ladislav > > About tagging and tag 4 specifically, the overhead require by them will need to be justified. > We need to identify which specific applications require schemaless processing of unknown data nodes. Fair enough. > > About identitities > This issue have already been mentioned by Juergen and the current > intent is to adopt the same representation as > draft-ietf-netmod-yang-json-06 Juergen questioned the need for a new namespace notation but if I understand correctly the example in sec. 3.1.7, in iana-interface-type.ethernetCsmacd there is no namespace at all: iana-interface-type is an identity, and so is ethernetCsmacd. Lada > > Regards, > Michel > > -----Original Message----- > From: Carsten Bormann [mailto:cabo@tzi.org] > Sent: December-11-15 4:55 AM > To: Ladislav Lhotka <lhotka@nic.cz> > Cc: Michel Veillette <Michel.Veillette@trilliantinc.com>; Core > <core@ietf.org> > Subject: Re: [core] CBOR Encoding of Data Modeled with YANG > > my 2 µJ for now... > >> 1. Would it make sense to use semantic tagging (major type 6) to >> distinguish numbers or strings with special semantics? Possible >> candidates that come to my mind are instance-identifier and >> identityref values. > > In general, the assumption has been that semantic information would come out of the YANG schema. Is there a case where that is not so, and we need to represent it at the representation level? > >> 2. Why is the "decimal64" type encoded as an integer and not as "decimal >> fraction" (major type 6, tag 4)? Whilst the decimal value can be >> obtained by using the leaf's definition, > > Because we can get the exponent value out of the schema, we don't need to transmit it. > >> perhaps it may simetimes be >> useful to be able to correctly interpret the values without using a >> schema. > > Right. We probably have to make up our mind how useful YANG-based information should be in a schemaless environment. If we want to make it useful, that requires quite some different thinking than what we have now. > >> 3. I think it is necessary to include namespaces/module names in the >> encoding of identitities (sec 3.1.7). It is probably not very likely >> in that particular example, but somebody could define another >> "iana-interface-type" identity in another module. Identities were >> designed to be extensible in a decentralised fashion, so the CBOR >> encoding should IMO also represent the namespace. > > We should take note of this problem and put it as one more objective for the identifier discussion (the hashes vs. structured IDs vs. ... one). > > Grüße, Carsten -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C
- [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG weigengyu
- Re: [core] CBOR Encoding of Data Modeled with YANG Kepeng Li
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Alexander Pelov
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Alexander Pelov
- Re: [core] CBOR Encoding of Data Modeled with YANG Carsten Bormann
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Alexander Pelov
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG Alexander Pelov
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG Alexander Pelov
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG Ladislav Lhotka
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Carsten Bormann
- Re: [core] CBOR Encoding of Data Modeled with YANG Ladislav Lhotka
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Ladislav Lhotka
- Re: [core] CBOR Encoding of Data Modeled with YANG Ladislav Lhotka
- Re: [core] CBOR Encoding of Data Modeled with YANG peter van der Stok
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG peter van der Stok
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Juergen Schoenwaelder
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Ladislav Lhotka
- Re: [core] CBOR Encoding of Data Modeled with YANG Carsten Bormann
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Ladislav Lhotka
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Ladislav Lhotka
- Re: [core] CBOR Encoding of Data Modeled with YANG Michel Veillette
- Re: [core] CBOR Encoding of Data Modeled with YANG Andy Bierman
- Re: [core] CBOR Encoding of Data Modeled with YANG peter van der Stok