IETF Logo Mail Archive

Re: [Json] Allow any JSON value at the top level

Nico Williams <nico@cryptonector.com> Fri, 07 June 2013 20:19 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1235521F99C2 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 13:19:56 -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 ivgxQ13pluap for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 13:19:51 -0700 (PDT)
Received: from homiemail-a54.g.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2E42521F99C1 for <json@ietf.org>; Fri, 7 Jun 2013 13:19:51 -0700 (PDT)
Received: from homiemail-a54.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTP id 67FFD40122422 for <json@ietf.org>; Fri, 7 Jun 2013 13:19:50 -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; s=cryptonector.com; bh=W96foJVjAbPU9RifG40O 8NS2GzM=; b=bYkpvXTvBsiR8MTxmP15X66WxqFuk4r5SJWtjpxGpWyD3y/iuVnL 0MrecYK/zHb3UrIYsPw/9A0vIc4jE8ptCbJNzYd4S/R5P1CkEoZpAp0Ux6FsEOuW qETYnygmrCvAcpend2M7pzwpLaJe/zXQIgbV9hpjkRQrg1Tyl6Dszs4=
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTPSA id 0F3FA4012241B for <json@ietf.org>; Fri, 7 Jun 2013 13:19:49 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id cb5so1564853wib.15 for <json@ietf.org>; Fri, 07 Jun 2013 13:19:48 -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; bh=aCQeRp4LQYtA/iGBKOsw2erL7sKXZYHA0TdQWgDsqx0=; b=P4qyMy629pDUIDRzMR9CB6DvDJ4IzGNrMXb5moVqQmN0UCiesOYo7qK3SI5jTDkh98 XYOh9ea7TZ8ZxP/ZhUCbBZqpEqS1wQTsckVDLk7bqlRTpBerM9BHQrkifKl3L5l9nUD9 FfIbwfOW3SMFcX8pyJS9UeW9P9fMvschPfmoHaN+xis1BqI2T5seXi5afWIpcD02kuFu jlFyh52564uFnHA1bhruOCs6Feh96a9Rp/t946ES7Kg3FuJGh6B1VDgyhCE6CdS9w651 T1WN/RpKEC75ijGXcAay9Q4ljSrlAm6FK0XLwj0lz93ePxrdJPL+sKI9DHUfzQXbozgB gUHg==
MIME-Version: 1.0
X-Received: by 10.194.79.74 with SMTP id h10mr119900wjx.84.1370636388405; Fri, 07 Jun 2013 13:19:48 -0700 (PDT)
Received: by 10.216.63.136 with HTTP; Fri, 7 Jun 2013 13:19:48 -0700 (PDT)
In-Reply-To: <CAK3OfOhPBkjSyYUxGvccXVQ1Wjxh1YK7_rtXYB7xHpw4L703sg@mail.gmail.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com> <3B4E7F65-B9B9-4C95-B077-D178B8DD8216@vpnc.org> <51B20529.2040906@drees.name> <CAK3OfOhPBkjSyYUxGvccXVQ1Wjxh1YK7_rtXYB7xHpw4L703sg@mail.gmail.com>
Date: Fri, 07 Jun 2013 15:19:48 -0500
Message-ID: <CAK3OfOhwXhhZH33htcdW_NdddLP9dreNFgGZdySzBBbDN1DDzQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: stefan@drees.name
Content-Type: text/plain; charset="UTF-8"
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Allow any JSON value at the top level
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 20:19:56 -0000

On Fri, Jun 7, 2013 at 11:52 AM, Nico Williams <nico@cryptonector.com> wrote:
> If the top-level may be any value then we still have the first
> character being ASCII and the section 3 encoding detection algorithm
> still works:
>
>            00 00 00 xx  UTF-32BE
>            00 xx  UTF-16BE
>            xx 00  UTF-32LE
>            xx 00  UTF-16LE
>            xx xx  UTF-8

Ah, no, what a braino.  /me is embarrassed.

v2.23.0 | Report a Bug | By Email