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

Dave Cridland <dave@cridland.net> Wed, 22 May 2013 17:40 UTC

Return-Path: <dave@cridland.net>
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 E979621F95EB for <apps-discuss@ietfa.amsl.com>; Wed, 22 May 2013 10:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 e-dV4FzJ6Ga3 for <apps-discuss@ietfa.amsl.com>; Wed, 22 May 2013 10:40:04 -0700 (PDT)
Received: from mail-oa0-f47.google.com (mail-oa0-f47.google.com [209.85.219.47]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4CE21F9413 for <apps-discuss@ietf.org>; Wed, 22 May 2013 10:40:04 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id m1so3044628oag.20 for <apps-discuss@ietf.org>; Wed, 22 May 2013 10:40:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6dExKjt4a5j9KbgMU85QBICHCIPp1EalVXArFnVobFM=; b=TwsAE7OvocbeT3GrMmnNhaN1FuPzb/grVU8rIySxqlkGyOSruDgqfVIt1Dhv5mT+sX Lqo7le1AdKORaKnrBWHdQrrsYKg/zKhPv8Q9bWMzVyDoqAmYasp72CkglysLFNMX+jID H76PYYLzBdSzaiAArfM310lm7wcPGCHg+HmF4=
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:x-gm-message-state; bh=6dExKjt4a5j9KbgMU85QBICHCIPp1EalVXArFnVobFM=; b=Scfd61sMcTkPRfRsaz4fQTWUOmtkI3L9C0JAJY+jZO9ZWGOpCC+0DlmavvHHY0Tlhn k7Bh11cHOLt6rTGJ9Tlt4Lrd52fWlQP3uGazO3q4J0lVr0qO72JkkPNwTBaY9b8i3+X/ mupn8nnkGVDu6ygTm9ox902usshIR7iWV/xP+oJzN9Lbv52DcUrEdi2vMSJVUqQzZwcX no+CLa2YXqOsPGySN3yzl1ZJDDHx0sW8l6gbI4nDJdXdLYiDSfhxceItIyCmko95Afgl 0l/uGAHCoM6OXoyt1qgaqCG3cslGX+BFz3lUCh83XCh4ZduPEj/8aVxL1zthhlTCKv1V 7QAg==
MIME-Version: 1.0
X-Received: by 10.60.85.74 with SMTP id f10mr5777972oez.32.1369244403778; Wed, 22 May 2013 10:40:03 -0700 (PDT)
Received: by 10.60.62.146 with HTTP; Wed, 22 May 2013 10:40:03 -0700 (PDT)
In-Reply-To: <04905D53-5022-4741-A2B6-9EE4593A4C65@tzi.org>
References: <61CB1D18-BABC-4C77-93E6-A9E8CDA8326B@vpnc.org> <CABP7RbcUJJoPJYdCOGSoa8fJfqj+R5RttjDtG5zXDirUV9OMQA@mail.gmail.com> <3638B63C-0E75-4E99-BF65-28F83DB856A6@vpnc.org> <CAMm+LwjKzHnOKDp0dmHN1Czes-f7tcJ2U1qz7S_HoSpcfKMyyA@mail.gmail.com> <04905D53-5022-4741-A2B6-9EE4593A4C65@tzi.org>
Date: Wed, 22 May 2013 18:40:03 +0100
Message-ID: <CAKHUCzx35qsiz5xiw2dbOjWfRuy05Whxo6-+VpCqmBdvZCj4cA@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="089e0111b71c4ca94304dd520e2c"
X-Gm-Message-State: ALoCoQkB74bqW4fiPP0Wx+ijR16rEBwZjlkWApkTyVG5+1ya/GaSrftnyEUpgX1AJYLX58ce61++
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 17:40:09 -0000

On Wed, May 22, 2013 at 5:29 PM, Carsten Bormann <cabo@tzi.org> wrote:

> > I would like to have available a BER like encoding for JSON.
>
> What is it that you like about BER?
> (And, as you mentioned there are a couple, which BER do you like :-)?
>
>
There's only one BER, but there are also DER, CER, PER, XER, and probably
others I can't instantly recall.


> > But this proposal seems to be something rather different.
>
> We try to learn.
>
> CBOR can sure do everything a "BER for JSON" could do.  And a little more.
>

I think that's the right approach.

My only concerns - not hills to die on, but worth discussion, I think - are
that:

 - I'd be keen to see a clean subset defined which always can be translated
to JSON. My gut feeling is that this would be useful.

 - I'm instantly put on guard by the notion that there are multiple
representations for the number 7. I would in general much prefer to see
only one. I admit this may not be possible, or simple - maps, for instance,
have no intrinsic ordering, enforcing an integer use the most compact
representation is awkward, and so on. But having a canonical representation
might well be missed later.

Dave.