Re: [core] CBOR Encoding of Data Modeled with YANG

"Kepeng Li" <kepeng.lkp@alibaba-inc.com> Mon, 07 December 2015 10:49 UTC

Return-Path: <kepeng.lkp@alibaba-inc.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 DDE2C1A1B82 for <core@ietfa.amsl.com>; Mon, 7 Dec 2015 02:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.089
X-Spam-Level:
X-Spam-Status: No, score=0.089 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 AssuCCgqN-8n for <core@ietfa.amsl.com>; Mon, 7 Dec 2015 02:49:08 -0800 (PST)
Received: from out4133-146.mail.aliyun.com (out4133-146.mail.aliyun.com [42.120.133.146]) by ietfa.amsl.com (Postfix) with ESMTP id E7DA41A1B76 for <core@ietf.org>; Mon, 7 Dec 2015 02:49:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1449485345; h=Date:Subject:From:To:Message-ID:Mime-version:Content-type; bh=tLygWSNlPlpcRPwpXHugjeHtoG8SW+lJlhSfK4pVzUE=; b=T3Fh8KkNoTBjqpcN1MpjDpeieQMHiLtvOvTJw8s2KOeqviBc9gA9rVJqpCGp74xWYDqq9pS9UcyT1Hk2BiSeUygflCiO2MOIBpicnemJ6/+u978i3j7lOH73N9A8IRA1y5yasgRKpabaVL4HwQw75Nxr+3M5zIk4YxMIq23Mu7Y=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R751e4; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03304; MF=kepeng.lkp@alibaba-inc.com; NM=1; PH=DS; RN=4; SR=0; TI=SMTPD_----4JmBZ0-;
Received: from 30.10.35.214(mailfrom:kepeng.lkp@alibaba-inc.com ip:42.120.74.157) by smtp.aliyun-inc.com(127.0.0.1); Mon, 07 Dec 2015 18:49:00 +0800
User-Agent: Microsoft-MacOutlook/14.4.8.150116
Date: Mon, 07 Dec 2015 18:48:56 +0800
From: Kepeng Li <kepeng.lkp@alibaba-inc.com>
To: weigengyu <weigengyu@bupt.edu.cn>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Michel Veillette <Michel.Veillette@trilliantinc.com>
Message-ID: <D28B849B.2510A%kepeng.lkp@alibaba-inc.com>
Thread-Topic: [core] CBOR Encoding of Data Modeled with YANG
References: <BLUPR06MB176391F16B5E9D6CCC531771FE0E0@BLUPR06MB1763.namprd06.prod.outlook.com> <20151207091044.GA59864@elstar.local> <FB3CCF216AE74BE29256F4ED3B21713B@WeiGengyuPC>
In-Reply-To: <FB3CCF216AE74BE29256F4ED3B21713B@WeiGengyuPC>
Mime-version: 1.0
Content-type: text/plain; charset="GB2312"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/5QUwFThUfARfMbq0kFQIP2NS3Ok>
Cc: 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: Mon, 07 Dec 2015 10:49:10 -0000

This is a good requirement for us to revise the "Node ID“ draft and keep
it alive.

Kind Regards
Kepeng

在 7/12/15 5:48 pm, "weigengyu" <weigengyu@bupt.edu.cn> 写入:

>Hi Juergen,
>
>There had been a draft about "Node ID“, CoAP Option Extension: NodeId,
>draft-li-core-coap-node-id-option-02.
>It was expired June 19, 2015.
>
>Regards,
>
>Gengyu WEI
>Network Technology Center
>School of Computer
>Beijing University of Posts and Telecommunications
>-----原始邮件----- 
>From: Juergen Schoenwaelder
>Sent: Monday, December 07, 2015 5:10 PM
>To: Michel Veillette
>Cc: Core
>Subject: Re: [core] CBOR Encoding of Data Modeled with YANG
>
>A few notes:
>
>- The document talks about a 'node ID' in several places but never
>  defines this concept nor does it explain how these node IDs are
>  created.
>
>- Your ID should normatively depend on YANG 1.1 and cover all the YANG
>  1.1 constructs, that is, include anydata.
>
>- I am not sure I understand the anyxml encoding.
>
>- I guess I am having an issue with yet another ad-hoc namespace
>  notation invention in 3.1.7. YANG type: identityref. Why not use the
>  <module>:<identifier> notation used by the JSON encoding?
>
>- The document confuses YANG types and YANG data node definition
>  statements. I suggest to follow the structure of
>  draft-ietf-netmod-yang-json-06.txt.
>
>/js
>
>On Wed, Dec 02, 2015 at 08:08:49PM +0000, Michel Veillette wrote:
>> For those interested to the development of the "CBOR Encoding of Data
>> Modeled with YANG" draft.
>>
>> The current document is available at:
>> https://core-wg.github.io/yang-cbor/
>>
>> Proposed changes to the Reference, Introduction and Security
>> Considerations sections are available at:
>> https://github.com/core-wg/yang-cbor/pull/2/files
>>
>> Michel Veillette
>> System Architecture Director
>> Trilliant Inc.
>> Tel: 450-375-0556 ext. 237
>>
>> _______________________________________________
>> core mailing list
>> core@ietf.org
>> https://www.ietf.org/mailman/listinfo/core
>
>-- 
>Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
>Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>
>_______________________________________________
>core mailing list
>core@ietf.org
>https://www.ietf.org/mailman/listinfo/core
>