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

John Cowan <cowan@ccil.org> Tue, 18 April 2017 11:55 UTC

Return-Path: <cowan@ccil.org>
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 9EA1212EB37 for <json@ietfa.amsl.com>; Tue, 18 Apr 2017 04:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ccil-org.20150623.gappssmtp.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 F9ITXoTKQmnY for <json@ietfa.amsl.com>; Tue, 18 Apr 2017 04:55:51 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00E22129B84 for <json@ietf.org>; Tue, 18 Apr 2017 04:55:50 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id w64so54325367wma.0 for <json@ietf.org>; Tue, 18 Apr 2017 04:55:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GUhKuFj96PRneH1tohRSwss7tCNo+nB5k5bdBR8yGmc=; b=eu/IHeRcIpjno5I77+mTkIdKcRXvnjghuQEGLRuEE9pKta2mi3A7gKHOOTsWJKWD9M Ub9sOoUDpWRmV+Kf1e+DuTNQt0B6WNUBgZo3rmbROepq2tBr3gtl0trq1X5jdeaCNtY7 HTtN9qbtpiTB/Yn8gJntA26iBs9cdNsn9RL832mln2/RlrvbLHlCuxCwKHmYb82k/2gx xA+yT9DxmmYMkM3cTgrjPeUScl9TY8OBDNDY9iFeyXYXL1TlUPOvxbrzmHl1d81v5+6q LtW6Cm5817TGa1MwAMBp51z2gbo0ZR8mnDTE2a8G3nWy+VwiPywlnzBbXMeY4h22ZkMp dk2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GUhKuFj96PRneH1tohRSwss7tCNo+nB5k5bdBR8yGmc=; b=W1ipy0HptpcEcea39YOec7zJu8WgYOWs35SPOn1hM+hWXELoqSJV1Ol4FpGS8jY8Af 0blGFSQfQivgb0hi3xR1F9XSS+of8MnHs+D2XLWC2QnXyvwmUxEmCBinAC63qbzzPDQh zy4M7ePxXbRjAdpqziHPnzz6e+x3R8Kj/lzb86bmozZMWTHBkcwg7uasABgAX+NqCt1a q1LfDOBfNGO51gcZzeNge0IwUmPWe5CpFjVk4xBBniIt7idN13hDKjZDr+ophnQRaEGy bPvAGsqt8GCBAgfT1jkR8Qq+AeKzfeV1XkhSmkr+fT4ni9TEkz1RssRx2Xjw4K9ErlSQ Pncw==
X-Gm-Message-State: AN3rC/4jv/mug3Q1t616PEQ0J+fczP5VGR6TC7QVovpflcDFVSRvReVv ZGKuFW3kalusUsE9Hyi/fp53Qb27jOoMJ8M=
X-Received: by 10.28.236.135 with SMTP id h7mr13042778wmi.74.1492516549145; Tue, 18 Apr 2017 04:55:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.126.4 with HTTP; Tue, 18 Apr 2017 04:55:28 -0700 (PDT)
In-Reply-To: <eabbccb0-8d15-d595-7cd0-37acc0621c57@it.aoyama.ac.jp>
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> <20170417175627.GK23461@localhost> <10B651F1-7FE0-484D-BD2E-FD146BC5FB04@tzi.org> <eabbccb0-8d15-d595-7cd0-37acc0621c57@it.aoyama.ac.jp>
From: John Cowan <cowan@ccil.org>
Date: Tue, 18 Apr 2017 07:55:28 -0400
Message-ID: <CAD2gp_To0kmpmPmXdnp3P=+XwfMNgDUSJ3rHmdVOxZzbbUn2Bg@mail.gmail.com>
To: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>
Cc: Carsten Bormann <cabo@tzi.org>, "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>, "json@ietf.org" <json@ietf.org>
Content-Type: multipart/alternative; boundary=001a1147128abbd05d054d6f96c1
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/G1KV47Aq7zcuFERqTjfonKaqvrE>
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: Tue, 18 Apr 2017 11:55:53 -0000

On Tue, Apr 18, 2017 at 1:22 AM, Martin J. Dürst <duerst@it.aoyama.ac.jp>
wrote:

In my view, the only reason to still have a MAY for UTF-16/32 is that this
> will avoid questions like: "I have a JSON parser in language FOO, it can
> take a string or an input stream as an argument. In FOO, strings are
> UTF-16, but the JSON RFC doesn't seem to allow this. What should I do."


The answer to that is something like this:  "In the IETF, we do interchange
standards.  What you do with JSON internally to your system is your own
business."

-- 
John Cowan          http://vrici.lojban.org/~cowan        cowan@ccil.org
Said Agatha Christie / To E. Philips Oppenheim
"Who is this Hemingway? / Who is this Proust?
Who is this Vladimir / Whatchamacallum,
This neopostrealist / Rabble?" she groused.
        --George Starbuck, Pith and Vinegar