IETF Logo Mail Archive

Re: [Json] Wording on encoding; removing the table

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 22 November 2013 22:56 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 090B41AE345 for <json@ietfa.amsl.com>; Fri, 22 Nov 2013 14:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tuDvy5B5pmDL for <json@ietfa.amsl.com>; Fri, 22 Nov 2013 14:56:42 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id ED15B1AE1F8 for <json@ietf.org>; Fri, 22 Nov 2013 14:56:41 -0800 (PST)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id rAMMuVex047998 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 22 Nov 2013 15:56:32 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20131122224717.GE3655@localhost>
Date: Fri, 22 Nov 2013 14:56:31 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9285A77-4CCD-46CD-AE29-EDFE3BD47501@vpnc.org>
References: <v8av89128j49csd5bb5ba2rqrgschs4c79@hive.bjoern.hoehrmann.de> <BE35B0E6-6C71-47EB-BA29-08A32935D20E@vpnc.org> <20131122224717.GE3655@localhost>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1822)
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] Wording on encoding; removing the table
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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, 22 Nov 2013 22:56:43 -0000

On Nov 22, 2013, at 2:47 PM, Nico Williams <nico@cryptonector.com> wrote:

> On Fri, Nov 22, 2013 at 02:36:41PM -0800, Paul Hoffman wrote:
>> Please note that the chairs tried to find some consensus in the BOM
>> discussion and found none. Given that, and given that the current
>> table is now wrong, our proposal is to remove it, not try to doctor
>> it.
> 
> That's fair.
> 
>> Proposed replacement:
>> 
>>   The default encoding for JSON transmitted over the Internet is UTF-8.
>>   Transmitting JSON using other encodings may not be interoperable
>>   unless the receiving system definitively knows the encoding.
>> 
>> Does anyone have a technical objection to the proposed replacement? If
>> so, please state the error and (hopefully) a correction.
> 
> Might it be worthwhile to note that the previous RFC had implied (but
> not stated) that UTF-16 and UTF-32 had been intended to be supported?

Sorry, yes, we will need to add some words to that effect to Appendix A as well.

> Also, what does this mean for the MIME media type encoding
> considerations text?

Nothing. The text above says that UTF-8 is the default, not the only possible encoding.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email