IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Fri, 22 November 2013 22:47 UTC

Return-Path: <nico@cryptonector.com>
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 89E6F1AE393 for <json@ietfa.amsl.com>; Fri, 22 Nov 2013 14:47:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 m-8gRQ_CuVPl for <json@ietfa.amsl.com>; Fri, 22 Nov 2013 14:47:32 -0800 (PST)
Received: from homiemail-a111.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id 6204A1AE2D8 for <json@ietf.org>; Fri, 22 Nov 2013 14:47:32 -0800 (PST)
Received: from homiemail-a111.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a111.g.dreamhost.com (Postfix) with ESMTP id 570B22005D90A; Fri, 22 Nov 2013 14:47:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=lRFmuDvxVTH+2J uzyciOo5s8iaA=; b=thLazRXDK0BgG0YVY5RpBAZB15NgSlwnVf9bt/lzh8UlHt LjJntwmsPgywGvyEDZqokBEdF77xppn3767et2stFpCpxSi15sHh6nAJUBnJ+28q /9r3vIMJXfyHvaMv3Swxsh3zTfFeGxbCn+cuKCFObncQu77AF7n52o7hWYZp0=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a111.g.dreamhost.com (Postfix) with ESMTPA id 223952005D909; Fri, 22 Nov 2013 14:47:25 -0800 (PST)
Date: Fri, 22 Nov 2013 16:47:18 -0600
From: Nico Williams <nico@cryptonector.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20131122224717.GE3655@localhost>
References: <v8av89128j49csd5bb5ba2rqrgschs4c79@hive.bjoern.hoehrmann.de> <BE35B0E6-6C71-47EB-BA29-08A32935D20E@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BE35B0E6-6C71-47EB-BA29-08A32935D20E@vpnc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
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:47:34 -0000

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?

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

Nico
--

v2.23.0 | Report a Bug | By Email