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

Nico Williams <nico@cryptonector.com> Thu, 23 May 2013 20:57 UTC

Return-Path: <nico@cryptonector.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 C285821F86BB for <apps-discuss@ietfa.amsl.com>; Thu, 23 May 2013 13:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 VOJ-ksOKEVL7 for <apps-discuss@ietfa.amsl.com>; Thu, 23 May 2013 13:57:19 -0700 (PDT)
Received: from homiemail-a85.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by ietfa.amsl.com (Postfix) with ESMTP id 47BA921F86D3 for <apps-discuss@ietf.org>; Thu, 23 May 2013 13:15:12 -0700 (PDT)
Received: from homiemail-a85.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTP id 102A5BC042 for <apps-discuss@ietf.org>; Thu, 23 May 2013 13:15:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=YEfsA5kbVo8FeJfz6nKJUyPy56s=; b=AGd5j/MjR/6 2U97TlaLjtzVvbATFLpyOzCwSNmmPm4b3FKfdZc6G8OKnev2GNWECEt415TWp3i5 /fvCZEJmNGrzAWkZo7DYmmkg+kpVV587Dd6bFVyMeyx3XeTUk7vS0HFdkWFAd/P4 C+O8mIJGfrekinm4tXt+xf0zj0PsGUMU=
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a85.g.dreamhost.com (Postfix) with ESMTPSA id A2BBCBC040 for <apps-discuss@ietf.org>; Thu, 23 May 2013 13:15:11 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id a12so2414089wgh.35 for <apps-discuss@ietf.org>; Thu, 23 May 2013 13:15:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Zuj06p86ev+tHmV5D3KGFrVwHPOr+6RbQkoXvn+Sb8g=; b=JdUjAilnDMdhpvQY6wP/9Zy1Yt0k0jiXOzXuwBIxOVPjTzfpYVKCSqzoK36Xg7fJWs JlGSyJq1EcHWfd0RqQ5wsW1u2z24L8MtkY36Qb9nrlGKxApcz9vLIVThv7YupbThUPRL bxvxbHW1vPzXvXft7JbODrcyD16af7TiQe7jTFf2GI2JmXpEd8uCxB4g7j+dHu1xuuDd fdaRPxWo7Bcq19g45rIPB/Ib6YanAPJ7nVo4dc6hKiuBvK+xxoIlQN1+k6uihLiyiOKf iopMwWMRw39S6a0dR4qorlF533kGvNfSHpLZtkj6ke9liSJsDccnb5Hpxwe5sMN/3nrW 1SrQ==
MIME-Version: 1.0
X-Received: by 10.181.13.229 with SMTP id fb5mr28175361wid.16.1369340013405; Thu, 23 May 2013 13:13:33 -0700 (PDT)
Received: by 10.216.111.132 with HTTP; Thu, 23 May 2013 13:13:33 -0700 (PDT)
In-Reply-To: <6C80DF35-E465-4107-B2B5-34D8D1C2F2CF@vpnc.org>
References: <61CB1D18-BABC-4C77-93E6-A9E8CDA8326B@vpnc.org> <CAK3OfOhVRqUp+xn8mBj8_x8pgubc7bhWebzsFLvoj+ieWmr5gg@mail.gmail.com> <142483A4-2E80-43F1-B3BE-B5B01650BB8F@tzi.org> <CAK3OfOim44hRaRoFh8vKfK5SPVAnvTGiBV4cizvw30K=ZQPJHQ@mail.gmail.com> <84317001-DB56-4DBE-9D1E-A4E605BC07A0@tzi.org> <CAK3OfOj9dH-E1infhUECwgKYQF7ASw1Z21M5oG24PHMLWxuVYw@mail.gmail.com> <3367FDBE-8268-4F3A-85CF-94D64BF60FCC@vpnc.org> <CABP7RbdBFBKsXhJ=Y0CowWQBK_WDBmPkAT_+dUj1xic-=J=Jug@mail.gmail.com> <6C80DF35-E465-4107-B2B5-34D8D1C2F2CF@vpnc.org>
Date: Thu, 23 May 2013 15:13:33 -0500
Message-ID: <CAK3OfOh4QiqO2OPz7j00BCnKRGgvGOJ3RmwjLP5gJHzrwMfu4Q@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "apps-discuss@ietf.org 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: Thu, 23 May 2013 20:57:33 -0000

On Thu, May 23, 2013 at 2:24 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> On May 23, 2013, at 11:35 AM, James M Snell <jasnell@gmail.com> wrote:
>
>> That's well and good, from everything I've seen so far in this thread,
>> the collective majority opinion can be summarized as "Ugh... Groan..
>> Another one? Really?"
>
> Just a note that this is one of the only ones that people are groaning about that has an Internet Draft and might go through the IETF consensus process. Carsten and I (maybe naively) thought that doing this in this environment, instead of say posting ephemeral specs on a web page and not having it be clear where the community fit it, was a good thing.

There's a huge world outside the IETF.  The folks working on Simple
and BSON, to take two examples, may not care about bringing their work
to us, but then, they may also be annoyed by our blindsiding them with
a standards-track binary JSON (I know, CBOR's a superset) encoding
that's not interoperable with theirs.

In particular, if there's wide deployment of one of them, why
shouldn't we pick one of them?

Should we not invite the wider JSON community to this discussion?

Nico
--