Re: [core] ? WG adoption of draft-veillette-core-yang-cbor-mapping-00

Michel Veillette <Michel.Veillette@trilliantinc.com> Thu, 21 April 2016 21:00 UTC

Return-Path: <Michel.Veillette@trilliantinc.com>
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 DB62A12E59E for <core@ietfa.amsl.com>; Thu, 21 Apr 2016 14:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trilliant.onmicrosoft.com
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 Wus6GWAYMwmU for <core@ietfa.amsl.com>; Thu, 21 Apr 2016 14:00:35 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0115.outbound.protection.outlook.com [65.55.169.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC7BB12E502 for <core@ietf.org>; Thu, 21 Apr 2016 14:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-trilliantinc-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=YP4L+Uk+VTHV3o46OCFyq3D1V5V1RmYb5RVBImUDmKc=; b=GDi+k9ADWbOMNEFh7UwSjyMR7wDuel20qdk400ZV4YavivMV8Ue2jv7djOX9Ixk9nLDKAzLJOHTyWm3ligCnEUOvUZJpc1PCGZFcNxq4PgXVzVVpmG54EcPXT9+1S9BzVVupRDDwZUOQH1Dosvon332IibQUCjVphgjm4Efybow=
Received: from BLUPR06MB1763.namprd06.prod.outlook.com (10.162.224.149) by BLUPR06MB1763.namprd06.prod.outlook.com (10.162.224.149) with Microsoft SMTP Server (TLS) id 15.1.466.19; Thu, 21 Apr 2016 21:00:29 +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.0466.023; Thu, 21 Apr 2016 21:00:29 +0000
From: Michel Veillette <Michel.Veillette@trilliantinc.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [core] ? WG adoption of draft-veillette-core-yang-cbor-mapping-00
Thread-Index: AQHRm/X9d/034ye6rkCrz4BefXTDrJ+U0HzQgAAVWwCAAAIn4A==
Date: Thu, 21 Apr 2016 21:00:29 +0000
Message-ID: <BLUPR06MB17635E7755D44E34BB1FACA5FE6E0@BLUPR06MB1763.namprd06.prod.outlook.com>
References: <570A4583.2030100@tzi.org> <5718A09E.7040607@gmx.net> <BLUPR06MB1763F3B6BDE5240402576758FE6E0@BLUPR06MB1763.namprd06.prod.outlook.com> <20160421174806.GA8710@elstar.local> <BLUPR06MB1763C3A1543AAB909C95D20EFE6E0@BLUPR06MB1763.namprd06.prod.outlook.com> <20160421204630.GA8993@elstar.local>
In-Reply-To: <20160421204630.GA8993@elstar.local>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: jacobs-university.de; dkim=none (message not signed) header.d=none;jacobs-university.de; dmarc=none action=none header.from=trilliantinc.com;
x-originating-ip: [207.96.192.122]
x-ms-office365-filtering-correlation-id: 69a18df5-fed0-4f64-792d-08d36a27f879
x-microsoft-exchange-diagnostics: 1; BLUPR06MB1763; 5:nTK2/0IXkzA/FA0tuz/faxMJzoDtQiEONc9KLFzAr4szyXusBEagb0FrOv/eXhxaaIzH26SPLduHKW/567IwcU/DHbqoQqZVoU2gY9lX51Q0RN4TFe5UqGAsV5FFteDMVPgsVwWI9UFdp+NDzV2vOUi+OG/26q1LwQoZFLGnVBY7BXGfqugNNMBU3FgzQvcQ; 24:fRWt0T8Vj+tXGKxLZahN9MWjGjWRZlpjEBYQ7mrWNs1ULvy3qyNzwg3mznTP+/Umcx+OWcxwZhkNl8NNE3JwbIZlQcDisM6bxigmONDUSR0=; 7:mQTGueVuBvBOmM70PS4vuQlQRNdrrzCdean8fagmcZogG3hP2gohBEfgtJuC/QBDe1sDq7hBEA5F6IuVt1TP6Eem2GuzHk0un9FF2qm6DmU4757G+e8IH4Qr2jns0+NauVPrnRVXBYzHxWnGFX99XUGFd9qvAeO6jPWUUdFcql+ln00DsqNscwyD1yTfTLL2zjOKXG7kY8XlZLCFiG3xzNEIltmLq77siCBLHVJ1Kbs=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR06MB1763;
x-microsoft-antispam-prvs: <BLUPR06MB176347B036EF7F628241ED5AFE6E0@BLUPR06MB1763.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:BLUPR06MB1763; BCL:0; PCL:0; RULEID:; SRVR:BLUPR06MB1763;
x-forefront-prvs: 091949432C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(24454002)(13464003)(110136002)(15975445007)(1720100001)(122556002)(5002640100001)(2900100001)(586003)(1220700001)(2950100001)(77096005)(66066001)(189998001)(6116002)(102836003)(5003600100002)(92566002)(5008740100001)(93886004)(10400500002)(74316001)(106116001)(87936001)(3660700001)(81166005)(99286002)(3280700002)(5004730100002)(19580405001)(19580395003)(86362001)(9686002)(33656002)(76576001)(76176999)(54356999)(4326007)(50986999)(11100500001)(230783001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR06MB1763; H:BLUPR06MB1763.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: trilliantinc.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Apr 2016 21:00:29.2579 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB1763
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/bxSRwjFb3wW7vi77BcJ-XQAvn2c>
Cc: "core@ietf.org WG" <core@ietf.org>
Subject: Re: [core] ? WG adoption of draft-veillette-core-yang-cbor-mapping-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: Thu, 21 Apr 2016 21:00:37 -0000

Hi Juergen

The extract I have provided is from a publically available document, see:
https://www.iab.org/wp-content/IAB-uploads/2016/03/ipso-paper.pdf

My remark about the LWM2M modeling language was just to highlight that such language don't necessary imply code generation.

Regards,
Michel

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
Sent: April-21-16 4:47 PM
To: Michel Veillette <Michel.Veillette@trilliantinc.com>
Cc: Hannes Tschofenig <hannes.tschofenig@gmx.net>; core@ietf.org WG <core@ietf.org>
Subject: Re: [core] ? WG adoption of draft-veillette-core-yang-cbor-mapping-00

On Thu, Apr 21, 2016 at 07:47:53PM +0000, Michel Veillette wrote:
> Hi Juergen
> 
> I'm not sure I can share a LWM2M definition files since peoples need fill a form to get access to them, see the following link.
> 
> http://technical.openmobilealliance.org/Technical/technical-informatio
> n/release-program/current-releases/oma-lightweightm2m-v1-0

Then I can't help.
 
> I didn't go through a formal mapping between these two modeling languages but following is what this mapping might look like:
> 
> LWM2M                | YANG
> ---------------------+---------------
> <Object>             | module
> <Name>               | module name
> <Description1>       | description
> <MultipleInstances>  | list if true, container if false
> <Mandatory>          | mandatory
> <Item>               | leaf if <MultipleInstances> is true, leaf-list if false
>  <Name>              | leaf name
>  <Operations>        | config
>  <MultipleInstances> | See <Item>
>  <Mandatory>         | mandatory
>  <Type>              | type
>  <RangeEnumeration>  | range or enum
>  <Units>             | units
>  <Description>       | description
>

The devil is usually in the details but since there is no public specification I do not know. It sounds somewhat surprising that an '<Object>' would equate a YANG module but then I simply do not know.
Only someone who has access to the specifications and who can get clearance to write about a mapping according to IETF rules can work on this.

/js

PS: You shall [...] not [...] use all or any part of a Document as part
    of a specification or standard not emanating from the Licensor
    without the prior written consent of the Licensor [...]

-- 
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/>