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

Carsten Bormann <cabo@tzi.org> Wed, 22 May 2013 19:18 UTC

Return-Path: <cabo@tzi.org>
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 A3EED11E8142 for <apps-discuss@ietfa.amsl.com>; Wed, 22 May 2013 12:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.205
X-Spam-Level:
X-Spam-Status: No, score=-106.205 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 J4xtU8dhyLlR for <apps-discuss@ietfa.amsl.com>; Wed, 22 May 2013 12:18:34 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 7937521F96F9 for <apps-discuss@ietf.org>; Wed, 22 May 2013 12:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r4MJIQd6013186; Wed, 22 May 2013 21:18:26 +0200 (CEST)
Received: from [192.168.217.105] (p54891D40.dip0.t-ipconnect.de [84.137.29.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 157323973; Wed, 22 May 2013 21:18:26 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CABP7Rbftgm2asyu6LgGHoZVQKy3aCY5vHu6_qHQrXbdd+P65wA@mail.gmail.com>
Date: Wed, 22 May 2013 21:18:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F042DA71-C726-4236-9EE7-5F3D1B6D56E1@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> <alpine.LSU.2.00.1305221841270.3056@hermes-2.csi.cam.ac.uk> <8F16DE1E-3D5F-4C38-937E-14EAF66D3D94@vpnc.org> <519D0893.8010602@bbiw.net> <CB2CE68C-278A-4468-8C05-27622B7FA9A2@tzi.org> <CABP7Rbftgm2asyu6LgGHoZVQKy3aCY5vHu6_qHQrXbdd+P65wA@mail.gmail.com>
To: James M Snell <jasnell@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF Apps Discuss <apps-discuss@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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 19:18:40 -0000

On May 22, 2013, at 20:43, James M Snell <jasnell@gmail.com> wrote:

> Best bet: define the syntax, provide a couple of great open source
> implementations, let people know about them.. then time will tell
> whether it'll be worthwhile to standardize. There shouldn't be any
> rush on getting an RFC done.

Of course, the degree of success of a technical specification is dominated by external effects, such as the highly random process in which it is picked up by implementers.

What I am trying to do here is just provide a very good specification.

Good marketing, open-source reference implementations, TED speaking engagements, articles in Network World, pickup by CPU vendors that put in useful instructions for generating/parsing it, cloud services, funding for related research etc. (in other words, mindshare) comes after that.  

However, this is a specification that could (and should) be used by other specifications that the IETF and other organizations will be creating.  So saying "you can have the RFC after the first TED talk" is not helping those other specifications along.

(This is not an argument against running code, just against "let the market decide on whatever and then standardize".)

Grüße, Carsten