Re: [Json] draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 18 July 2017 07:40 UTC

Return-Path: <alexey.melnikov@isode.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 86E56131691; Tue, 18 Jul 2017 00:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 PQr4OiwA_QlC; Tue, 18 Jul 2017 00:40:55 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id CC35512ECF0; Tue, 18 Jul 2017 00:40:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1500363654; d=isode.com; s=june2016; i=@isode.com; bh=vwrPx0PSglqewztan7UOZ4G0HnNkzkZ1saXMJ0PrIOQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=kNLC8/Mvb7U9VlVssxfWPKG5kNplLjSmPwP14RL3IljiqrxRl5qQ6k1OaZJSaS/jBAJmXb 7G26lpaepAD0eDUvLyRXIayJTql5Bz4vVNpaUhnl5w6QJoKLjol1NV6Ydc5qdgigcdfEb1 Ksy69NAEyhmWZvGICoVW5pso+e6Q4is=;
Received: from [172.16.18.185] (94.112.246.234.static.b2b.upcbusiness.cz [94.112.246.234]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <WW27hQBf=oKf@statler.isode.com>; Tue, 18 Jul 2017 08:40:53 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (14F89)
In-Reply-To: <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de>
Date: Tue, 18 Jul 2017 10:05:26 +0200
Cc: "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
Message-Id: <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com>
References: <596CE6E3.3070808@isode.com> <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Vi35Br732ijqkVr2rcEjhg3jLhI>
Subject: Re: [Json] draft-ietf-jsonbis-rfc7159bis-03: recommendation to use UTF-8
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 07:40:56 -0000

Hi Julian,

> On 18 Jul 2017, at 08:52, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
>> On 2017-07-17 18:33, Alexey Melnikov wrote:
>> Hi,
>> The JSONBIS WG decided to update recommendation on Unicode encoding to
>> be UTF-8. (For details see the RFC Editor's notes in the approval
>> message that will be sent out shortly.) This took a bit of time to
>> debate in the WG, so the document approval took a bit longer than
>> originally expected.
>> Best Regards,
>> Alexey, as the responsible AD
> 
> The last WG mail related to this topic is over 2 months old, and I don't see any declaration of consensus.
> 
> It would be good if the chair would send a summary about what's going on to the WG mailing list before anything gets finalized.
> 
> (I note that <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/> has been saying "Revised ID Needed" for 48 days, and I was under the assumption that there'd be indeed a revised ID).

I just posted a message on this: this is approved with updated RFC Editor notes. See the approval message once it is sent.

Best Regards,
Alexey