Re: [Json] msgpack/binarypack (Re: [apps-discuss] JSON mailing list and BoF)

Sadayuki Furuhashi <> Mon, 04 March 2013 08:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 385B921F8868; Mon, 4 Mar 2013 00:01:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id E7ZdUKijPp0Y; Mon, 4 Mar 2013 00:01:20 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 2EE6121F886A; Mon, 4 Mar 2013 00:01:17 -0800 (PST)
Received: by with SMTP id h15so2426716dan.37 for <multiple recipients>; Mon, 04 Mar 2013 00:01:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=esE5O15hpYl+P0Ek4vPjVxrX2iYE4w7pIYUDi9hdF+o=; b=lDgbbYAiR7E6PZDbE5G64dvzAEVspkzFaN7lT/UGkN+1rCkkvFfIAyN2XOQV0lmVaL fZty6zVLcvxM3oLI2FXt0Yt3KzYFgVqj7VP+BEfyK5aP6VK21ddx5McDtmkpKUfihDqc jaJTjs8/zTKM2aIkt70SxR12RgyuACv/JutfWJMprshsZd3k7ns5+SDkY03H1tHPHos5 vKXfOdYTB5En2fWtZq8JCkoA6jjzT/mqXFIeXMfFi1zNRXKIzKhrlHKzGVlZKkcw7Dxj iSXn17cO9Yd2VCKbzzXlPVXgOwaDeHra9m1QVakxVlmXLb+JKI/3wqC3/mwYTODAEobJ nOeg==
X-Received: by with SMTP id nx3mr27161899pbb.13.1362384076928; Mon, 04 Mar 2013 00:01:16 -0800 (PST)
Received: from [] ( []) by with ESMTPS id ol7sm21486662pbb.14.2013. (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Mar 2013 00:01:14 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Sadayuki Furuhashi <>
In-Reply-To: <>
Date: Mon, 4 Mar 2013 00:01:10 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: "" <>, "" <>
X-Mailer: Apple Mail (2.1499)
Cc: Carsten Bormann <>, "Joe Hildebrand \(jhildebr\)" <>
Subject: Re: [Json] msgpack/binarypack (Re: [apps-discuss] JSON mailing list and BoF)
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Mar 2013 08:01:21 -0000

I'm frsyuki (Sadyuki Furuhashi).

As the initial developer of the MessagePack specification, I am feeling unrest
in bringing MessagePack to IETF as an Internet-Draft at this very moment.

I don't against having a standard itself but I really have difficulty on its downside: incompatibility.

Because at least I already have hundreds TBs of data stored in MessagePack format.
And there're already many other users who don't expect incompatible changes. Here is a list of users:
(This list is quite old, though. There're more users now. You'll see the list includes Pinterest, Redis, etc.)

Thus compatibility is an essential problem of msgpack. So I can't help opposing drafts which are
incompatible with MessagePack.

Another problem which makes this decision complicated is that we're discussing on changing
the msgpack spec. We'll likely add string or binary type to msgpack. Prof. Dr. Bormann kindly
joined us to help happening this change. But we have not updated implementations based on
the new spec yet. It's not validated by users. It means that we need to disscuss about the
change of spec, implement it in many languages, validate them on production environments,
and write documents. I don't think we can make them all happen soon, at the same time.

I don't against having a standard itself but we're not prepared to start it now. However, even
writing an individual Internet-Draft under my name is an our possible option. Meaning that
sooner or later, we'll have a document about the new MessagePack spec (which includes
the string/binary types). I can't commit the timing at this time, though. We're focunsing on
the new spec right now.

Let me keep updated about discussion on our issue thread:

Sadayuki Furuhashi

On 2013/02/24, at 5:11, Carsten Bormann <> wrote:

> On Feb 19, 2013, at 17:39, Carsten Bormann <> wrote:
>> On Feb 19, 2013, at 00:47, "Joe Hildebrand (jhildebr)" <> wrote:
>>> As an individual, I'm +1 on that.  I love msgpack, and don't mind the
>>> addition of UTF8 as a separate type.  Was frsyuki involved in the draft,
>>> or at least know that it happened?
>> I tried to involve him.
> Well, I did engage the msgpack community some more.
> You can find a transcript of some 275 messages about separating byte and UTF-8 strings at:
> Summary:
> Some members of the msgpack community are very enraged that this change hasn't happened earlier.
> Of course, some have gone off and done their own incompatible forks.
> Others are very enraged that any change is happening at all, and that new people are intruding on their turf.
> (And some probably feel guilty that it took a ****storm from outside to finally make this change.)
> frsyuki is now working on a proposal that solves the problem:
> The proposal is technically complete (and has already been implemented).
> It already is pretty good at the details, too, but this whole thing is being done in a process that is closer to Japanese consensus processes than to IETF culture.
> My -01 will be fully aligned with whatever the state of frsyuki's proposal will be on Monday's I-D deadline (find today's snapshot at
> (frsyuki's proposal may change some more, but those will in all likelihood be minor details.)
> I think his overall thinking is fine, but it is much more dominated by a requirement for backwards compatibility than an IETF process would be.
> So, the larger question on whether the msgpack community is ready to take part (or just endure) in an IETF-style consensus process (including handing over change control) still looms.
> That doesn't diminish from the requirement for a msgpack-like format, and I think we should use Hallway Time in Orlando to discuss potential ways forward.
> I any case, I definitely don't want to disturb the constructive discussion about chartering a very narrow JSON fixup WG with this work.
> (I do want to find a home for it, soon, though: I want to build other specs on top of it.)
> Grüße, Carsten
> _______________________________________________
> json mailing list