IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Mon, 17 April 2017 17:56 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 6CD5413172A for <json@ietfa.amsl.com>; Mon, 17 Apr 2017 10:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level:
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=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 kWY_ekhhfcXU for <json@ietfa.amsl.com>; Mon, 17 Apr 2017 10:56:56 -0700 (PDT)
Received: from homiemail-a72.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 4F4A5131758 for <json@ietf.org>; Mon, 17 Apr 2017 10:56:32 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTP id 6756DA00CEC2; Mon, 17 Apr 2017 10:56:31 -0700 (PDT)
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-a72.g.dreamhost.com (Postfix) with ESMTPSA id F1EB8A000B32; Mon, 17 Apr 2017 10:56:30 -0700 (PDT)
Date: Mon, 17 Apr 2017 12:56:28 -0500
From: Nico Williams <nico@cryptonector.com>
To: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Cc: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
Message-ID: <20170417175627.GK23461@localhost>
References: <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> <40e3207f-e047-c898-1f0c-4422de1d597a@it.aoyama.ac.jp> <1b3ec14a-927a-8d46-e3d3-9807a9588437@outer-planes.net> <CAHBU6ivsq8+Z=MMkUH+=Q0uwc5NCtaJLYw5cp0Qg8eX2hQQ6sA@mail.gmail.com> <b74cb31b-8e04-17d0-548a-fc164ce07c05@outer-planes.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <b74cb31b-8e04-17d0-548a-fc164ce07c05@outer-planes.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/-eDhujcmix_woW4ZOBblCDDxzTk>
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: Mon, 17 Apr 2017 17:56:57 -0000

On Mon, Apr 17, 2017 at 11:41:29AM -0600, Matthew A. Miller wrote:
> [ /me doffs hat ]
> 
> Thinking about this more, putting an encoding detection algorithm as an
> appendix seems like a reasonable compromise to me.  To start, how about
> removing the detection text from Section 8.1 and have an appendix that
> starts with that text plus the table?

Or we could even just assert that such an algorithm is possible, and
that implementors MAY implement one.

> Assuming the above, what does everyone think of the following for
> Section 8.1?

+1.

Nico
--

v2.23.0 | Report a Bug | By Email