IETF Logo Mail Archive

Re: [Json] Complete section 3 proposal

Carsten Bormann <cabo@tzi.org> Wed, 19 June 2013 07:36 UTC

Return-Path: <cabo@tzi.org>
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 462B021F8EB3 for <json@ietfa.amsl.com>; Wed, 19 Jun 2013 00:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.201
X-Spam-Level:
X-Spam-Status: No, score=-106.201 tagged_above=-999 required=5 tests=[AWL=0.048, 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 Arl9cRrMDBuo for <json@ietfa.amsl.com>; Wed, 19 Jun 2013 00:36:21 -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 64D3921F9EE5 for <json@ietf.org>; Wed, 19 Jun 2013 00:36:19 -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 r5J7a6Ho018104; Wed, 19 Jun 2013 09:36:06 +0200 (CEST)
Received: from [192.168.217.105] (p54893A31.dip0.t-ipconnect.de [84.137.58.49]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 32143368D; Wed, 19 Jun 2013 09:36:06 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <C9A3CF00-3B30-4DE4-95C4-9F3E6CA2DA86@vpnc.org>
Date: Wed, 19 Jun 2013 09:36:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <210C6860-3EAA-423B-93FD-926D71151C07@tzi.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC58C0B@xmb-rcd-x10.cisco.com> <C9A3CF00-3B30-4DE4-95C4-9F3E6CA2DA86@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1508)
Cc: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Complete section 3 proposal
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: Wed, 19 Jun 2013 07:36:27 -0000

On Jun 19, 2013, at 00:16, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> Because the first code point of a JSON text will always be a character in the range U+0022 to U+007B,

The following six characters can occur at the start of a JSON text:

           %x20                ; Space
           %x09                ; Horizontal tab
           %x0A                ; Line feed or New line
           %x0D                ; Carriage return

           %x5B                ; [ left square bracket
           %x7B                ; { left curly bracket

Four of those six characters are not in that range.
They are all in the ASCII subset of Unicode.

(Of course, that set might increase if we redefine what a JSON text is, but it is likely to stay ASCII.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email