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

Dave Crocker <dcrocker@bbiw.net> Wed, 22 May 2013 16:11 UTC

Return-Path: <dcrocker@bbiw.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 87DEE21F96C1 for <apps-discuss@ietfa.amsl.com>; Wed, 22 May 2013 09:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 46wWs9Xsk25p for <apps-discuss@ietfa.amsl.com>; Wed, 22 May 2013 09:11:11 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 802E021F96BB for <apps-discuss@ietf.org>; Wed, 22 May 2013 09:11:11 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4MGB7LC018655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 May 2013 09:11:10 -0700
Message-ID: <519CEE17.2050000@bbiw.net>
Date: Wed, 22 May 2013 09:11:03 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: James M Snell <jasnell@gmail.com>
References: <61CB1D18-BABC-4C77-93E6-A9E8CDA8326B@vpnc.org> <CABP7RbcUJJoPJYdCOGSoa8fJfqj+R5RttjDtG5zXDirUV9OMQA@mail.gmail.com>
In-Reply-To: <CABP7RbcUJJoPJYdCOGSoa8fJfqj+R5RttjDtG5zXDirUV9OMQA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Wed, 22 May 2013 09:11:10 -0700 (PDT)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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:11:16 -0000

On 5/22/2013 8:47 AM, James M Snell wrote:
> There have, however, been a number
> of previous attempts at alternative compact binary representations (or
> at least discussions) that did not seem to really go anywhere.


Indeed, Jack Haverty, then of MIT, lobbied hard for an especially 
concise, variable-length encoding form for email, back when RFC 733 was 
being developed, in 1977 for email.

We thought his idea clever but deciding to stay with the existing 
simple-ASCII practice, for messages that looked pretty much as they do 
today.

Jack's scheme certainly wasn't identical to the CBOR proposal, but it 
looks like the design approach is related.

I've always thought the approach a good one... assuming that it makes 
the right choices for what data to represent the most concisely.

For that, there should be some empirical data cited and possibly some 
discussion of significant earlier, related encoding schemes.  I suspect 
BER is the major one to consider.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net