Re: [core] 🔔 Working Group Adoption call for draft-somaraju-core-sid

Michel Veillette <Michel.Veillette@trilliantinc.com> Tue, 23 August 2016 20:35 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 E62B112DAF3 for <core@ietfa.amsl.com>; Tue, 23 Aug 2016 13:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 TQ29xU_hw9M8 for <core@ietfa.amsl.com>; Tue, 23 Aug 2016 13:35:27 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0106.outbound.protection.outlook.com [104.47.32.106]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C621312DAF7 for <core@ietf.org>; Tue, 23 Aug 2016 13:35:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-trilliantinc-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=L66UVHVUGRDc9mS+jbqnBduHZcvbldgHzhmkOw8Q4q8=; b=lhtCCWwaeaVZuXxeLhR1GmKn/fferZsNjr9c/McX3HdrdVno/znS1kJGuIx8FnjSyS0SsSga3JFEYgp/NPWDAmcuWQWjWx+kItShdisnYEk2jbu+IkngF0us/m6Kuq8npj2vSRH7z+/9ewejL5ESMiber2dlZFm4v2uTqEWrdTs=
Received: from BN6PR06MB2308.namprd06.prod.outlook.com (10.173.19.139) by BN6PR06MB2306.namprd06.prod.outlook.com (10.173.19.137) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.557.21; Tue, 23 Aug 2016 20:35:23 +0000
Received: from BN6PR06MB2308.namprd06.prod.outlook.com ([10.173.19.139]) by BN6PR06MB2308.namprd06.prod.outlook.com ([10.173.19.139]) with mapi id 15.01.0557.027; Tue, 23 Aug 2016 20:35:23 +0000
From: Michel Veillette <Michel.Veillette@trilliantinc.com>
To: Jaime Jiménez <jaime.jimenez@ericsson.com>, "core@ietf.org WG" <core@ietf.org>
Thread-Topic: [core] 🔔 Working Group Adoption call for draft-somaraju-core-sid
Thread-Index: AQHR/RmUGWUF12YwLkiGi0nYbykEOqBW/Yig
Date: Tue, 23 Aug 2016 20:35:23 +0000
Message-ID: <BN6PR06MB23089B3621DD9CC77AD944A5FEEB0@BN6PR06MB2308.namprd06.prod.outlook.com>
References: <8D2B6B77-9FA4-4171-959C-D9080F6AF507@ericsson.com> <B46CF3BB-BF16-4E15-967D-07B1BCD1E4D3@ackl.io>
In-Reply-To: <B46CF3BB-BF16-4E15-967D-07B1BCD1E4D3@ackl.io>
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-ms-office365-filtering-correlation-id: 64767748-6ab7-4d8a-b36c-08d3cb950215
x-microsoft-exchange-diagnostics: 1; BN6PR06MB2306; 6:z4fG6ulfeqoYLxqx6NCoDMkN+/ZXXMC160Vag5dTrLuuMYmuJw3+lZ6CGjdflEGKm5JmbBImXmJOx02CfpuVAWwcdTF8oVcL/GtF0TMIsrtB5H5Yf6noaUC4L3E46DqJ3+fIDoH1MQPRsbOst2de8vabHkB3JhvXQ9bW1zw6XaliZVQfv4THbaQKfq7/fOFmJppTj7GVARiCZlKll4cH9Z8ELfrAWsH+iKTA9jkCsPbu/aVKQ2xqwYDufFbX2B9lahPvyhMZYCbSvdFRiAbyidp/K5D/jG1IFQuqkBtcDJ4=; 5:yfWDJhJrwAq9NuLvyXuHcfXjxXLPn54uc/GpThOKlVmvR7msV5sd+oAGc37gXF0IQPxj8GW7k4EdOw2PhUFqhCOY8g2XBqgw6H4U04ASE3+heWCLXc+TNz5j6KqtnAOJ/w7fmn+IQKSWmYTnoHtzXg==; 24:sWduj4d5m3LlHsznFoFjcYdHJApZW1QBvhtp/0+xYx+V9XkHArBplP5fKZiEt+zr6nSuIpKALk8Bo9fp/e0olQPm26nFSLpx42z6kumiSzs=; 7:VB/KRthg0fATbjgkeq9fXCsbDc/ME9+8w8chzgxbItLxr6w1LY54/KMoqKf6D9MlkF/TcVWr6iAqPvUCE3alkO8Oc02g4vrElIT8y0ohDDFwX4cHF0Kv1Uqq9FwJqx9Au27Yuip+VVe8rp4a4UAN/QKUjNTJHGzt4s/ErZkUieygL7SWLcG9o6Hdrx4LzDQovUBP/RHXSOviONoB5aDJ1ygwTGAO+BvPyVlnW5VDdu9MzifvfMbCQdar141qGNEi
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN6PR06MB2306;
x-microsoft-antispam-prvs: <BN6PR06MB23064AAD2267B3BA0F20F006FEEB0@BN6PR06MB2306.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(120809045254105)(100405760836317)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:BN6PR06MB2306; BCL:0; PCL:0; RULEID:; SRVR:BN6PR06MB2306;
x-forefront-prvs: 004395A01C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(377454003)(199003)(189002)(76576001)(33656002)(19617315012)(7906003)(97736004)(74316002)(107886002)(92566002)(19625215002)(2950100001)(189998001)(5001770100001)(2900100001)(50986999)(122556002)(101416001)(3280700002)(229383001)(105586002)(230783001)(87936001)(19300405004)(19580405001)(8936002)(99286002)(9686002)(106116001)(68736007)(10400500002)(19580395003)(102836003)(3660700001)(81166006)(15975445007)(790700001)(7846002)(86362001)(106356001)(66066001)(7736002)(81156014)(5002640100001)(586003)(7696003)(16236675004)(77096005)(19609705001)(2906002)(54356999)(76176999)(3846002)(6116002)(5660300001)(11100500001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR06MB2306; H:BN6PR06MB2308.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:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN6PR06MB23089B3621DD9CC77AD944A5FEEB0BN6PR06MB2308namp_"
MIME-Version: 1.0
X-OriginatorOrg: trilliantinc.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Aug 2016 20:35:23.2852 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR06MB2306
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/73Evr7ubb0UaN9WufBImQtWHYD0>
Subject: Re: [core] 🔔 Working Group Adoption call for draft-somaraju-core-sid
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: Tue, 23 Aug 2016 20:35:30 -0000

+1

I also want to confirm my support for the adoption of (https://datatracker.ietf.org/doc/draft-somaraju-core-sid/) .

This draft is a fundamental building block for bringing YANG data models to CORE.
This draft is a prerequisite for the following works:

- CBOR encoding of YANG data model (https://datatracker.ietf.org/doc/draft-ietf-core-yang-cbor/)
- CoAP operation/function set (https://datatracker.ietf.org/doc/draft-veillette-core-cool/)
- YANG data model discovery (https://datatracker.ietf.org/doc/draft-veillette-core-cool-library/)

The alternate assignment algorithm of IDs based on murmur3 and improved description texts
proposed by Andy in (https://datatracker.ietf.org/doc/draft-bierman-core-yid/) don't fundamentally change
the registration process defined by the SID draft. These proposed improvements can be addressed during the review process.

Regards,
Michel Veillette

From: Alexander Pelov [mailto:a@ackl.io]
Sent: Tuesday, August 23, 2016 4:37 AM
To: Jaime Jiménez <jaime.jimenez@ericsson.com>
Cc: core@ietf.org WG <core@ietf.org>; draft-somaraju-core-sid@ietf.org
Subject: Re: [core] 🔔 Working Group Adoption call for draft-somaraju-core-sid

Dear all,

I want to confirm my support for the adoption of the document draft-somaraju-core-sid (a.k.a. the SID draft).

I do so for the following main reasons:
- We need a way to represent YANG identifiers for the draft-ietf-core-yang-cbor. The SID draft provides just this. We must adopt the document if we want to move forward with the work on this WG item.
- The SID draft is the result of more than a year and a half of discussions with people from CoRE, NETMOD, IANA and other SDOs.
- It is a straightforward and simple document, which provides the minimal structure on top of which IDs can be allocated.
- It provides for a way of having multiple independent registries, keeping all interoperable, and relieving IANA from the need to do overcomplicated, per-device allocations.
- Running code. There is a tool and a registry which are already used for prototyping.


The SID draft is aimed at:
- Interoperability (having devices with modules from different registries on a single network).

- Future-proof. The authors understand that today there are less than 2000 YANG modules. Yet, the ranges which will be allocated are FOREVER. This means, that in 2046, we’ll still be allocating IDs from the ranges we provide today. Independently of the size of identifiers, delta-encoding provides for ultra-efficient data transfer. However, once we move over the 32-bit identifiers, we’ll be taking a 8-byte penalty hit per request. The SID draft provides for a very straightforward and simple way of allocating blocks of IDs as necessary for a module.

- Constrained-device and constrained-network oriented (if needed) - after months of discussions we have confirmed that the most efficient way of representing the data items is with delta-encoding. When retrieving more than one item, the IDs take one byte on the wire in most cases. The allocation of IDs can be manual, automatic, or other - this is not enforced. What the draft enables is the users to make use of this ultra-efficient identifier representation - if they need it.
  - If not needed - an alternative mapping scheme can be used, e.g. trading interoperability and ultra-efficiency for compatibility with existing implementations.


In conclusion, we need the SID draft to be able to move forward with our WG item - the YANG-CBOR draft.

Best,
Alexander

Disclaimer: I am one of the authors of the draft. I believe we could make adjustments after the adoption OR decide to have specific drafts for specific use-cases, but we should not spend too much time getting back-and-fourth in changing the WG draft.


Le 15 août 2016 à 17:06, Jaime Jiménez <jaime.jimenez@ericsson.com<mailto:jaime.jimenez@ericsson.com>> a écrit :

Dear CoRE-WG,

As we discussed at last IETF96, working group adoption has been requested for draft-somaraju-core-sid. At the IETF meeting the room consensus was for adoption (3 people), since not too many people had read the draft we have to take it to the list. Please reply with your comments, including although not limited to whether or not you support adoption. Non-authors are especially encouraged to comment.

Since there are several concurrent WGA calls, we will end the call on August 26, 2016.

Thanks,
Jaime and Carsten

_______________________________________________
core mailing list
core@ietf.org<mailto:core@ietf.org>
https://www.ietf.org/mailman/listinfo/core