IETF Logo Mail Archive

Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"

Nico Williams <nico@cryptonector.com> Thu, 23 March 2017 23:00 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 89C5B1292D3 for <json@ietfa.amsl.com>; Thu, 23 Mar 2017 16:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level:
X-Spam-Status: No, score=-4.796 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, RCVD_IN_MSPIKE_H2=-2.796] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
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 o09fkjTzRLeV for <json@ietfa.amsl.com>; Thu, 23 Mar 2017 16:00:26 -0700 (PDT)
Received: from homiemail-a67.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F953127B31 for <json@ietf.org>; Thu, 23 Mar 2017 16:00:26 -0700 (PDT)
Received: from homiemail-a67.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTP id EE465D000083C; Thu, 23 Mar 2017 16:00:25 -0700 (PDT)
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=n5lUa2CpMuhHKX Dx381pkFxtspk=; b=Wg2AVI66xSqOBll3bWhLzZ5AASLjeG/5gFex5PWThacJua cPxkMmhZg+YHf9mj+wSuIaymUnlcpqjJmWEt0DBw/Tt6t/VFgtvYHx3iWSUpHmCi GtGpIXTLnh4YR9/7LN26AnNTJp7zmKLMwuPc5ux1Sy8W8I+ZQCJXNF7l6/s+k=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTPSA id A49BDD000083A; Thu, 23 Mar 2017 16:00:25 -0700 (PDT)
Date: Thu, 23 Mar 2017 18:00:22 -0500
From: Nico Williams <nico@cryptonector.com>
To: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Cc: "json@ietf.org" <json@ietf.org>
Message-ID: <20170323230020.GC7490@localhost>
References: <dad91b19-e774-e239-36d2-9d086cca8e0d@gmx.de> <ac432615-ee84-3cdf-6b37-480626bd18c1@gmx.de> <804f9930-26a5-a565-0607-452b386cfeb5@outer-planes.net> <D89BCFAA-B81F-4EEB-8B3A-180BAAB9D16C@att.com> <e69d7c21-85cb-45f4-c0c2-34c624e63049@outer-planes.net> <14252631-AD76-4537-89BF-6368F4A8CDF4@att.com> <7e6af21f-16ea-a3bc-9c01-595ae8acebba@gmx.de> <05100401-88D4-4158-A3FF-3EF144D85449@att.com> <CAD2gp_T0bfpnsCA_t4BAMtEhr7p8JkZggjnY4F+m9-M2hWLfmw@mail.gmail.com> <1e94516c-9c82-8b0e-0d2d-7dbaa83b21bd@outer-planes.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1e94516c-9c82-8b0e-0d2d-7dbaa83b21bd@outer-planes.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/aZfpRccIiWO1xuU1oO3LnGr0_V0>
Subject: Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 23 Mar 2017 23:00:27 -0000

On Thu, Mar 23, 2017 at 04:37:36PM -0500, Matthew A. Miller wrote:
> Our sponsoring AD and I have been discussing this option.  Alexey is
> willing to go through another IETF last call if we can get consensus.
> 
> To start, to what degree is UTF-8 encouraged?
> 
> 0) don't encourage UTF-8 more than already is
> 1) SHOULD encode as UTF-8 for all usages
> 2) SHOULD encode as UTF-8 where the media type is 'application/json'
> 3) MUST encode as UTF-8 where the media type is 'application/json'
> 4) other -- please specify

(1) and (3)

I don't mind (4): MUST encode in UTF-8 for all uses, though I don't
think we need to go that far.

Nico
--

v2.2.1 | Report a Bug | By Email