Re: [apps-discuss] Concise Binary Object Representation (CBOR)

James M Snell <jasnell@gmail.com> Wed, 22 May 2013 16:28 UTC

Return-Path: <jasnell@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A88A921F9717 for <apps-discuss@ietfa.amsl.com>; Wed, 22 May 2013 09:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.953
X-Spam-Level:
X-Spam-Status: No, score=-5.953 tagged_above=-999 required=5 tests=[AWL=-2.354, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjK3zfyyGlE7 for <apps-discuss@ietfa.amsl.com>; Wed, 22 May 2013 09:28:23 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id B02D221F9714 for <apps-discuss@ietf.org>; Wed, 22 May 2013 09:28:17 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id i4so2885481oah.7 for <apps-discuss@ietf.org>; Wed, 22 May 2013 09:28:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=R5neXiI04rHhpBMhlHkm3PeTTO6rMqJuYsI5wf4kXlM=; b=XatGCMDmMJx31uu8TCY0BjV+h3TyJfSkHO/ZRS8CZaMCK1qio2w+9wmbUZmaLGak3o yXJKLPSMhh1UD33CDphoyJKWnMrxg9N8DRWoGXNHcxsQ8ftPzAdJMB3823/BJQly4rWu bzy/7hU64A1MqIg1GRhSMgrvL3F22/3E6GFUtVFq/zCJPm9/2GJceMMVBTwsEUhfXPl7 mOu62nCpsQ1mp641/QB+/zWcv59bDCAVA4aAT51HTIVJ/9bMgGA5/FB1v/xOuLvftD1T UKfEs46k0IiCR+kR1fPKYKEALTfKtl9uL15642UDIfLX3WCbC1T0HdKKjn4R3Wc//rYI U3iw==
X-Received: by 10.60.92.41 with SMTP id cj9mr5368737oeb.31.1369240097264; Wed, 22 May 2013 09:28:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.3.137 with HTTP; Wed, 22 May 2013 09:27:57 -0700 (PDT)
In-Reply-To: <3638B63C-0E75-4E99-BF65-28F83DB856A6@vpnc.org>
References: <61CB1D18-BABC-4C77-93E6-A9E8CDA8326B@vpnc.org> <CABP7RbcUJJoPJYdCOGSoa8fJfqj+R5RttjDtG5zXDirUV9OMQA@mail.gmail.com> <3638B63C-0E75-4E99-BF65-28F83DB856A6@vpnc.org>
From: James M Snell <jasnell@gmail.com>
Date: Wed, 22 May 2013 09:27:57 -0700
Message-ID: <CABP7RbefzR0GLzx=_E9O0pZFbi--SN-49KdhT=ydMKdxPK66PQ@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Concise Binary Object Representation (CBOR)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 16:28:28 -0000

On Wed, May 22, 2013 at 9:00 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
[snip]
>> What is
>> the current implementation status of this? Are there implementations
>> available or any existing plans to use this new format in a specific
>> app or spec?
>
> Both Carsten and I did versions (in Ruby and Python) to make sure the spec made sense and the examples worked. At least one other member of this list has apparently done a version in JavaScript.
>

Good to know, thank you.

>> I'm largely just curious about the context and motivation
>> behind this...
>
> There are many contexts. It might be useful in CORE and other constrained-environment work. It might be useful for the next protocols that need a compact binary representation and the WG doesn't want to fight over the specific features. If the design goals fit your needs (and we actually met them...), then it's useful to have it be widely available.
>

The main point of my question was to find out if this was specifically
attached to some other piece of work or if it's a standalone "it's
here if you need it and want it" type of effort. There is certainly
nothing wrong with either approach, it's just better to have that
context. I can see how this would be useful in the general sense, just
not sure I can imagine any cases where it's something I would
absolutely use.

- James