Re: [Json] [apps-discuss] JSON mailing list and BoF

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 19 February 2013 15:25 UTC

Return-Path: <jhildebr@cisco.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 4699721F8DBB for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 07:25:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1d0U-9nONy2d for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 07:25:13 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 68B8C21F8C12 for <json@ietf.org>; Tue, 19 Feb 2013 07:25:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=550; q=dns/txt; s=iport; t=1361287513; x=1362497113; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Qa5fMRNnm/Lv0Cxq2PSSatMK0oZ6lWaIqXN19t9CtbQ=; b=iqCKnkLy/pZnr7QqK9gHimCo6OPSlmPr2jp4UlM+uxPinRc1hzv8J/FB vNBf79wCVVCEDnDoKsJ5Z0lXbzPKrwuIirfHxAHlD4QQe/daKORsY+Spb 8bwhyfmbJza981zcbhN8oa6cUBSUC/PdjwCIs9oBU9udJKuY6Qc9yaP3R 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAMqXI1GtJV2c/2dsb2JhbABFhgK6PYEKFnOCIQEEbgsSAQgOFFYlAgQBDQUIiAqwMJAejlsCMQeCX2EDiDCeU4MHgic
X-IronPort-AV: E=Sophos;i="4.84,696,1355097600"; d="scan'208";a="178746368"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 19 Feb 2013 15:25:09 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r1JFP9t1009782 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 15:25:09 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 09:25:08 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Tim Bray <tbray@textuality.com>, Bjoern Hoehrmann <derhoermi@gmx.net>
Thread-Topic: [Json] [apps-discuss] JSON mailing list and BoF
Thread-Index: AQHODhKwsPxTte9Ry0KhDmvQvHsA3piAt/6AgABvgQCAABYvAA==
Date: Tue, 19 Feb 2013 15:25:08 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70F895E88@xmb-rcd-x10.cisco.com>
In-Reply-To: <CAHBU6iumbfna-ez7=WjqEubViN3A81DxWhmZoeXGp5BTVV_+9A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.129.24.68]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <418F8E0A3D2F7449A3489FEBF10813B1@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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: Tue, 19 Feb 2013 15:25:15 -0000

On 2/19/13 12:05 AM, "Tim Bray" <tbray@textuality.com> wrote:

>Easily solved: ³In all instances when JSON is transmitted over a network,
>it MUST be encoded in UTF-8; a charset argument on the Content-type MAY
>be provided, but its value MUST be utf-8.²

Could we change section 3 to explain that if you want to liberal in what
you accept you can parse according to the older rules (including dealing
with a BOM), but that you MUST always generate UTF-8 with no BOM if you're
going to be 4627bis compliant?

-- 
Joe Hildebrand