Re: [core] New Version Notification for draft-bierman-core-yid-00.txt
Michel Veillette <Michel.Veillette@trilliantinc.com> Tue, 23 August 2016 15: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 CDCDA12D734 for <core@ietfa.amsl.com>; Tue, 23 Aug 2016 08:35:49 -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 nC7g_f8GbYD0 for <core@ietfa.amsl.com>; Tue, 23 Aug 2016 08:35:46 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0129.outbound.protection.outlook.com [104.47.32.129]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D58D012DA68 for <core@ietf.org>; Tue, 23 Aug 2016 08:24:38 -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=1huRfBjAJQqxUpR3Hclpz35zQKTSXslHl7hMDZaZSic=; b=hnTK9IAkIYclYPXXiob7r0aQwZ31h1NHJzG2Hg0lRBuOjvRcKR1mH1tlpVHF84bg4gU2mxPltvINI4ywqJMxnNgqu7T4APu6LkFJSVko6Yvc2uPacprQkZ4Otvurtz68B02C9rtIwrdeyNOgc30l7Hlcn2S20C21/9FUmRQdh9o=
Received: from BN6PR06MB2308.namprd06.prod.outlook.com (10.173.19.139) by BN6PR06MB2305.namprd06.prod.outlook.com (10.173.19.136) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.587.13; Tue, 23 Aug 2016 15:24:34 +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 15:24:34 +0000
From: Michel Veillette <Michel.Veillette@trilliantinc.com>
To: Andy Bierman <andy@yumaworks.com>, Core <core@ietf.org>
Thread-Topic: [core] New Version Notification for draft-bierman-core-yid-00.txt
Thread-Index: AdH9UnGGdbcJKHL+RaiqPFv3qZC4IQ==
Date: Tue, 23 Aug 2016 15:24:34 +0000
Message-ID: <BN6PR06MB2308181338DAF308CBE0CEDCFEEB0@BN6PR06MB2308.namprd06.prod.outlook.com>
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: 57bc0a6e-15a6-4018-ec06-08d3cb699689
x-microsoft-exchange-diagnostics: 1; BN6PR06MB2305; 6:dYQyyQeH05Dp0iRNFE8IHoThOe/78zXWuDuUyg2FATj7dETI0dd5SZJQhb9UdjQlBPzTmLpLLY6S4aVJWZP/oyM2uUwHDg45iswsu/S06efDhdISj6iSbjK9jHSt36n+eLaC2cKITaeTbuT3tdWitSmpdV+vXsIzQjkAgKo0qFX6mtCP8QAKktSM/g2ZFnn8TS0LFwfnmItQWrxYdT9CKT2O88Eh3eneG4PJLKEp2cLpEz+ZdrU/Fh0qqk91sVkhKX7M4itjx4vwBkP13R53yWVYrPNwWhRLnHiNEDx3pLM=; 5:qFS7fBghjcdTUJMjDiefl85ZAciQzOGLz4Yz4YvME+PbWBSoMPxc13tTWJtSS9wNKkj50MXpoY/Xk0lYsuq4fnCXO7P5ip0xNKLP7eHnMyKaQIDv7tl2jgYce/yV7oERuvRPW0hCtdxsfWSCNrqcWA==; 24:7q4bvqbrQ8PU2XdmjdzqZ0SMbkbPL7AJ47Yk/GpP+RjovT9Pj2nAk6Bywt1y/ZDv9OJe+v82egZECzlbjNpxzBBo2njIKR6rg30noNTl65k=; 7:3fHWtkT351Xf5ekJsBPWNNbvQa/imi9LwMZN4dqjUWzOho21XDukd2/eDwTB+VpMlAI2desWr2uqVjO2v/fcd5qR4nZ6Dj1UcXVa9JONSDE4e4ig0YOilK/SLNHM5AHbwKpdg05GalWIuOMm+PsyhkYnRVZ04xsDqH8ucIjjOaVxcvorophudUMdOp+y8Gm9hceNeIFARZ0WeLTeIbI3plM6NP5xeHoMuVFKzpzAQh8eZwHZmeWHXo5MkTP8TKpS
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN6PR06MB2305;
x-microsoft-antispam-prvs: <BN6PR06MB2305F406DCC60D7118D38D06FEEB0@BN6PR06MB2305.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:BN6PR06MB2305; BCL:0; PCL:0; RULEID:; SRVR:BN6PR06MB2305;
x-forefront-prvs: 004395A01C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(199003)(377424004)(189002)(22974007)(377454003)(69234005)(19300405004)(7846002)(7906003)(7736002)(81166006)(81156014)(8676002)(77096005)(122556002)(74316002)(15975445007)(106356001)(8936002)(19580395003)(66066001)(15650500001)(87936001)(105586002)(68736007)(2900100001)(9686002)(76576001)(230783001)(50986999)(7696003)(10400500002)(2420400007)(16601075003)(6116002)(2906002)(92566002)(19625215002)(19609705001)(107886002)(102836003)(5660300001)(5001770100001)(7110500001)(97736004)(54356999)(33656002)(3846002)(790700001)(14971765001)(16236675004)(586003)(3660700001)(11100500001)(189998001)(101416001)(19617315012)(86362001)(5002640100001)(10710500007)(19580405001)(3280700002)(99286002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR06MB2305; 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_BN6PR06MB2308181338DAF308CBE0CEDCFEEB0BN6PR06MB2308namp_"
MIME-Version: 1.0
X-OriginatorOrg: trilliantinc.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Aug 2016 15:24:34.5706 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR06MB2305
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/sDOUnFUhKYYEVKQ9vtYnv25e2f8>
Subject: Re: [core] New Version Notification for draft-bierman-core-yid-00.txt
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 15:35:50 -0000
Hi Andy draft-bierman-core-yid-00 propose that only manually assigned YIDs are maintained in the registry (mapping list or mapping-url). YIDs associated to a hash are excluded from this registry. This solution doesn't seem to work if the following design objectives listed in section 1.2 need to be respected: 1- Persistent Identifiers: It is important that once an identifier is assigned, that is it never changed in any future revisions in the module. 1- Module updates need be simple, and only require the latest module and registry information. For example, YANG module X is created with: Data node A associated to YID = hash 1 Data node B associated to YID = hash 2 Data node C associated to YID = hash 3 Than, a new revision is created with: Data node D associated to YID = hash 2 Data node E associated to YID = hash 4 Is this example, we have a hash clash between data node B and D. However, the YID assigned to data node B by version 1 is not allowed to change (objective #1). Only data node D can be rehashed. Using only the latest module (objection #2) and no entry in the registry, the proper rehash can't be performed. A simple solution to this problem is to maintain all YIDs in the registry. A new entry is rehashed only if a clash is detected with an entry already present in the registry. In summary, the process is the same independently of the algorithm in used (sequential, murmur3 hash, manual). Each time an YID is assigned, it must be added to the registry. And new entries are not allowed to collide with entries already present in the registry. The standard may describe these different algorithms (murmur3 hash, sequential, manual) but don’t need to mandate one. Regards, Michel From: core [mailto:core-bounces@ietf.org] On Behalf Of Andy Bierman Sent: Tuesday, August 16, 2016 2:39 PM To: Core <core@ietf.org> Subject: [core] Fwd: New Version Notification for draft-bierman-core-yid-00.txt FYI, Peter and I have written a new draft called "Numeric YANG Identifiers" which replaces the "YANG Hash" draft. This draft combines hash-based and manual numbering and defines a simple registry-based process for management of module and object identifiers. The need for a rehash procedure and rehash errors has been removed. YANG Hash is now scoped by the module identifier so there are no inter-module interactions. Hash collisions within a module are not allowed. Manual assignments for colliding nodes are used to avoid the rare occurrence of a hash collision within the same module. Andy ---------- Forwarded message ---------- From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> Date: Tue, Aug 16, 2016 at 11:29 AM Subject: New Version Notification for draft-bierman-core-yid-00.txt To: Peter van der Stok <consultancy@vanderstok.org<mailto:consultancy@vanderstok.org>>, Andy Bierman <andy@yumaworks.com<mailto:andy@yumaworks.com>> A new version of I-D, draft-bierman-core-yid-00.txt has been successfully submitted by Andy Bierman and posted to the IETF repository. Name: draft-bierman-core-yid Revision: 00 Title: Numeric YANG Identifiers Document date: 2016-08-16 Group: Individual Submission Pages: 33 URL: https://www.ietf.org/internet-drafts/draft-bierman-core-yid-00.txt Status: https://datatracker.ietf.org/doc/draft-bierman-core-yid/ Htmlized: https://tools.ietf.org/html/draft-bierman-core-yid-00 Abstract: This document describes an encoding of YANG object identifiers using numeric values instead of string values. It combines several techniques to provide optimized serialization in protocol messages. Note Discussion and suggestions for improvement are requested, and should be sent to core@ietf.org<mailto:core@ietf.org>. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>. The IETF Secretariat
- [core] Fwd: New Version Notification for draft-bi… Andy Bierman
- Re: [core] Fwd: New Version Notification for draf… Michel Veillette
- Re: [core] Fwd: New Version Notification for draf… Andy Bierman
- Re: [core] Fwd: New Version Notification for draf… Michel Veillette
- Re: [core] New Version Notification for draft-bie… Andy Bierman
- Re: [core] New Version Notification for draft-bie… Michel Veillette