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

Alexey Melnikov <aamelnikov@fastmail.fm> Tue, 18 July 2017 09:34 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 36384131A67 for <json@ietfa.amsl.com>; Tue, 18 Jul 2017 02:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=Hu4n2IFl; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JHwiTC6H
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 zqRPR49arGhe for <json@ietfa.amsl.com>; Tue, 18 Jul 2017 02:34:08 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF05C131945 for <json@ietf.org>; Tue, 18 Jul 2017 02:34:07 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5A1F220BD2; Tue, 18 Jul 2017 05:34:07 -0400 (EDT)
Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Tue, 18 Jul 2017 05:34:07 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=FZgIC/SxHidJBJB7pKfY29mFNKu5V gVlg3K6M390MqE=; b=Hu4n2IFlxPnpfs95hsamzyH5XGeQHLJu7+WAcMzqGRVeG w5IOdmKyWg3Xy8aUy27iKa6ro12L6BXws4tRLNIOEX3Uhi/jbrWq7g5b3+6YtfHb JkpyAiIRxvuUghQ0zUlCPUkOOpJWNcg+GNffbCu6V0zI4PD/fov8hevk9l0yXvzg ToXNm8wcF4gnfoRMrpPLn2FhvdP0GjzwxkSJ55t+yPWYIc5I0dFAvgLqNFTBisxy qXEBHBoQ7MXKMqFoQLDnfR8ImGgL7FWF5Y/FMMmQxL5RFFf4JQGx89FQhs3fDCI6 E12hWh1fw2PA+GthkKRiV5ZxqOFkibfzD+3E1VkVg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=FZgIC/ SxHidJBJB7pKfY29mFNKu5VgVlg3K6M390MqE=; b=JHwiTC6HDMksGa7oht/wgU yJrc3NHUfm+0QzyMazFfjcV+ZoU6WNzo9IQR6wNUIGeDcdi1B2zKiBxvkOjbQp2o ayTxEBsyxn6kfkLvM6Owt+aibojQv7RUPK6VBP9LqR3o9+r49BQCwdI0aIbN5OEW ey/Egtul9k268qPvJHbZWLmY5VGCPquyOUDYmJZKb1d8gpw2MILSQ4EmIIJwHwQQ hxCkRoGjAChrkZZoZ34nnafOjY9b9afU8LdZmS31JL933F40eJqYfdTI1s6HKgoh jYuzMo81hv3T7T3AEKaT5LwXHmxQfdG42+2ObZqxDS831BBGQ3KOWUWkjYWiJ/NQ ==
X-ME-Sender: <xms:D9ZtWTGsvV5Lj-uf0ZZFshb0ufBFzoCoyI7iNEOswtlAYJeN_7TA5A>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 3AD7848001; Tue, 18 Jul 2017 05:34:07 -0400 (EDT)
Message-Id: <1500370447.565092.1044410712.5AAE5B7E@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Julian Reschke <julian.reschke@gmx.de>, "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Cc: json@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-b8c51eee
Date: Tue, 18 Jul 2017 10:34:07 +0100
In-Reply-To: <47640061-e387-ef14-4ed6-c1c203c3c2fb@gmx.de>
References: <e69d7c21-85cb-45f4-c0c2-34c624e63049@outer-planes.net> <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> <6eb23f90-6623-7888-bc1c-6640a9dababc@codalogic.com> <61bfad2b-850d-a11f-e80b-d5ed9ccb4dc9@codalogic.com> <08a88696-65ef-da05-0d77-1a07d04ebfc8@outer-planes.net> <bb9fead6-23e7-8c1d-bc80-b60c81c4b89a@codalogic.com> <6f047d01-ad72-59ab-9d34-20a8177ab3af@outer-planes.net> <be4d9f12-a4be-3723-e52a-56a60722a75f@gmx.de> <a3805f67-620b-67f0-9c06-c865b71029e7@codalogic.com> <bb1ef6a8-506c-344b-b903-980ed50ad2d3@gmx.de> <44b4523a-5e4b-ccad-af96-931d8b9ad1c2@codalogic.com> <ac1d1b68-67e7-c19f-a556-280df73f465b@outer-planes.net> <db3e4d88-d3bc-2ab5-fd8d-0a9ed90865e9@codalogic.com> <CAHBU6itmYDyBfz0qqr0LAUTuvdR1oBSUnz7VSie=pZRva=Ynzw@mail.gmail.com> <787b7e15-ea97-b458-c886-d21c4dd02803@outer-planes.net> <47640061-e387-ef14-4ed6-c1c203c3c2fb@gmx.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/P6S68qmBlwCr523ncniSY_ugepI>
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 Jul 2017 09:34:09 -0000

Hi Julian,

On Tue, Jul 18, 2017, at 09:47 AM, Julian Reschke wrote:
> On 2017-07-18 10:27, Matthew A. Miller wrote:
> > Hello all,
> > 
> > I see consensus for the updated text below.  A note to the RFC editor is
> > added to ensure publication does not move forward until section 8.1 is
> > updated, and the change noted in the appendix.
> > ...
> 
> 1) I'm OK with the change.
> 
> 2) I'm *not* OK with the way it's being executed:
> 
> - there should have been a new Internet Draft to review
> 
> - we are making an important normative change (that can make existing 
> usages of JSON non-compliant) without getting IETF consensus for that
> change
> 
> - we're putting the RFC Production Center in charge to maintain our text 
> (because the note to the RFC Editor does not say what to put into 
> Appendix A)

I added a note for Appendix A. If people want to wordsmith it, it is not
too late for that.