Re: [core] CBOR Encoding of Data Modeled with YANG
Andy Bierman <andy@yumaworks.com> Sat, 12 December 2015 00:29 UTC
Return-Path: <andy@yumaworks.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 948251A8A74 for <core@ietfa.amsl.com>; Fri, 11 Dec 2015 16:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 Gx7OkztZw42v for <core@ietfa.amsl.com>; Fri, 11 Dec 2015 16:29:45 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7867F1A8A71 for <core@ietf.org>; Fri, 11 Dec 2015 16:29:44 -0800 (PST)
Received: by lbpu9 with SMTP id u9so72768122lbp.2 for <core@ietf.org>; Fri, 11 Dec 2015 16:29:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oxiOuYXycUbY8qrxY6bCn7Rr+J0jUgd9CxbqfzEbbAM=; b=QclZoBnc+CvuRYsP/IjyLC4yPkDuL26cwvJk1B2hQwSX0hwT7c4/wOi4H2teQfiU9/ XuwBx34Bd63msiC2ykeJB5QnohYnRJ7umJj6Hz6TmuXhU/YvP3uprVEjRWJXnkDKp9ld n8CjYpAIg5MDhEslY4qrGgYtBe7ZS1wK9GwR6p6ha+1Pn51cooWFDkpQyUBusu0zfbUU XVSm+UXYiTULbPi8iE2WLf86KpnRVl/MAE/4ks9SLWADDuiRfMceDHgGxXYq6QW994mL gexMtSI2AhFAa0Tz3FsyjNMCnlI9bDScmpeEy/9hcBQnUQKP98NMDwWQtJuKib0mNZvA WNUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=oxiOuYXycUbY8qrxY6bCn7Rr+J0jUgd9CxbqfzEbbAM=; b=krWTcAxeJPA7iTyB1OFRQr2LzGMyBGrVv85+lshdvBaKlWS/34Iib1HTWsPDV0pfoP 0Mi3UQbTqCfGtD5bq6PsTkwn5Ym+6ff+2jOtWHlUa3ORcaN80kax+myp2mHkEInyrttK QLKFhFZh1cqftrYetaVhfX4/m+XJclzClyw/1aIs4z72o3dLqim1IRK/JBQg715ArQBt jQej3Q/0S4Kt5Mkdy+YvQqAK3aqfvYsYHyBwshEGQFscZgH5MWPwTHbhwpyxJrya1d3C IVmkP6vfnbztMA5jW0gpnxUjxcBvycLfRlvuNx7Iw8/Lyp0cHqbrBlcYUsCzVczDkhMU yy1w==
X-Gm-Message-State: ALoCoQnIhjVGNInkn5jV0rg19bFN0WI4DuxhBBUoOdRB+gePxIDmR46hCp/Dq9MVd9h6TeOFDCqPZMuoVVMAXDHuc1cJ9/+8jw==
MIME-Version: 1.0
X-Received: by 10.112.16.101 with SMTP id f5mr2106300lbd.30.1449880182537; Fri, 11 Dec 2015 16:29:42 -0800 (PST)
Received: by 10.112.144.36 with HTTP; Fri, 11 Dec 2015 16:29:42 -0800 (PST)
In-Reply-To: <5666CE50.90008@tzi.org>
References: <20151207091044.GA59864@elstar.local> <BLUPR06MB1763ABFE8DE1E0E18F5F06A5FE090@BLUPR06MB1763.namprd06.prod.outlook.com> <20151207194229.GA61491@elstar.local> <BLUPR06MB1763B7F9EBF812C06DB04252FE090@BLUPR06MB1763.namprd06.prod.outlook.com> <20151207203826.GA61647@elstar.local> <BLUPR06MB1763E9AB0D1E4A0478D47C05FE090@BLUPR06MB1763.namprd06.prod.outlook.com> <20151208093350.GA62650@elstar.local> <5666AE1A.2040908@ackl.io> <20151208105530.GA62785@elstar.local> <64B950CF-863D-4440-AF7A-F8DF79C80409@telecom-bretagne.eu> <20151208115310.GA62928@elstar.local> <5666CE50.90008@tzi.org>
Date: Fri, 11 Dec 2015 16:29:42 -0800
Message-ID: <CABCOCHS751-JWhUn9Fvs6wOM-w66V-ztEvtx3bTfHxw1Rt7R_A@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="001a11c3fdfe3f59070526a889a0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/pgjFLooCi3oOdaCTtDBXi9rVZKU>
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: Sat, 12 Dec 2015 00:29:46 -0000
On Tue, Dec 8, 2015 at 4:34 AM, Carsten Bormann <cabo@tzi.org> wrote: > Juergen Schoenwaelder wrote: > > I want independently developed systems to interoperate. In general, I > > can't assume modules have data node IDs (since a YANG module like lets > > say ietf-interfaces simply does not define them). > > One discussion we haven't had is whether we can combine COMI-style > identifier hashing as the general solution with optional use of manually > managed identifiers. This would give us the coverage of "any item from > any YANG module" that we would like to have, but still provide the > opportunity for more optimization in specific modules that can benefit > from tighter representation (including the external/internal identifier > split), which we might be able to subject to a tighter development regime. > > IMO this is the only realistic path to cover the wide range of use-cases. Some outside organization (not IANA) can number modules and objects based on the expected frequency of use, alphabetical sort, or whatever. There has been some discussion offline, and some text in the CoMI draft. 2 approaches have been discussed: 1) different entry points (/mg or /cool, maybe both in the same server) pros: simple and low impact cons: not flexible enough if managed and hashed objects depend on each other (e.g., standard module is registered/managed and vendor extension is hashed) 2) use a bit in the object ID to tell the ID types apart pros: allows seamless integration of both types of modules cons: adds 1 bit to every ID; neither type wants bit 31 always set; not really needed if the server only has 1 kind of module > Grüße, Carsten > Andy > > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core >
- [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