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

Pete Resnick <presnick@qti.qualcomm.com> Tue, 18 July 2017 11:18 UTC

Return-Path: <presnick@qti.qualcomm.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 9175813178B; Tue, 18 Jul 2017 04:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.002
X-Spam-Level:
X-Spam-Status: No, score=-7.002 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_HI=-5, 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=qti.qualcomm.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 nxHRwuVRZvZ4; Tue, 18 Jul 2017 04:18:20 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EC8F131488; Tue, 18 Jul 2017 04:18:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1500376700; x=1531912700; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=f1aCV/FMkh3T51ytMuRUHO/4NIvcHJJL4QwQ/ggEx1A=; b=qDxOReyYyKQ/g3X/9XbD6sL2tawDkvEhW1diz2fB3wCr6LvDMteYnqXE DG69WtukpjZhGeQoVnKMARuII0Cd2EL/Q8w2AlLnBPW+tpDvu0qaDTqJ4 ZZmw/ZUGqwrP0uFWeI3RA3C+R9iWe39hpXurxR2kzn39FfRM7WQm9fid6 o=;
X-IronPort-AV: E=Sophos;i="5.40,377,1496127600"; d="scan'208";a="111796188"
Received: from unknown (HELO ironmsg02-R.qualcomm.com) ([10.53.140.106]) by sabertooth02.qualcomm.com with ESMTP; 18 Jul 2017 04:18:19 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8594"; a="1000376862"
X-MGA-submission: =?us-ascii?q?MDHdP7SZDsoDm676c6k/mkii9nF9Q3H+lG8Ce4?= =?us-ascii?q?v+KQ/XEtFHxg7glU+p2FvXE9pxFDK2gNPcm/VMASCf0/gj+k6wG9OJU4?= =?us-ascii?q?VmluZubRyJ0Ua4pXVXkG12CxJt9s71vzlBWrMe45WxcQQ4d+WT5VWbm8?= =?us-ascii?q?xr?=
Received: from nasanexm01b.na.qualcomm.com ([10.85.0.82]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 18 Jul 2017 04:18:19 -0700
Received: from [10.64.103.81] (10.80.80.8) by NASANEXM01B.na.qualcomm.com (10.85.0.82) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 18 Jul 2017 04:18:18 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Barry Leiba <barryleiba@computer.org>
CC: Julian Reschke <julian.reschke@gmx.de>, Alexey Melnikov <alexey.melnikov@isode.com>, "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
Date: Tue, 18 Jul 2017 13:18:15 +0200
Message-ID: <28D32024-5E4C-44C7-A54A-049BA97289CE@qti.qualcomm.com>
In-Reply-To: <CAC4RtVC0fBbw-YiifN5p-gPLxHYRB0jkSumankTTcY+KbyTasw@mail.gmail.com>
References: <596CE6E3.3070808@isode.com> <92698d15-6557-8bb1-aad0-a0965e779e71@gmx.de> <668A56FD-4B89-472C-9E4C-BE5C0E6921F9@isode.com> <6a42a587-f09c-14bc-847b-7882c8f3e9f7@gmx.de> <CAC4RtVC0fBbw-YiifN5p-gPLxHYRB0jkSumankTTcY+KbyTasw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01E.na.qualcomm.com (10.85.0.31) To NASANEXM01B.na.qualcomm.com (10.85.0.82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/OMzXzxAfHFfReEnUwWupUdyW05c>
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 11:18:22 -0000

Alexey,

I believe Julian and Barry's notes constitute an appeal of the Protocol 
Action, and I think they're probably right. Please rescind it, publish 
the new draft, and give people a bit to review. No need for another 
formal LC, but doing this in a note to the RFC Editor isn't kosher.

pr

On 18 Jul 2017, at 13:04, Barry Leiba wrote:

> I have to agree with Julian here: this is not a change that's
> appropriate to do in an RFC Editor note.  The change is probably fine,
> but draft revisions are cheap and it's easy enough to post a revised
> I-D to make sure we can all see the final version in context.
>
> Thanks,
> Barry
>
>
> On Tue, Jul 18, 2017 at 10:19 AM, Julian Reschke 
> <julian.reschke@gmx.de> wrote:
>> On 2017-07-18 10:05, Alexey Melnikov wrote:
>>>
>>> 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.
>>> ...
>>
>>
>> This is not how it's supposed to work. Please have a new I-D posted 
>> and get
>> people to review the changes in context. This is a *very* important 
>> piece of
>> standards work - we need to make sure it meets quality standards.
>>
>> From a quick glance at
>> <https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/writeup/>, 
>> I
>> already note that the appendix "Changes from RFC 7159" is now 
>> incomplete.
>>
>> Best regards, Julian
>>
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json