IETF Logo Mail Archive

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

Barry Leiba <barryleiba@computer.org> Tue, 18 July 2017 11:04 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 2E5C11252BA; Tue, 18 Jul 2017 04:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 z5YuLtfqDTMR; Tue, 18 Jul 2017 04:04:33 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (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 6D973129459; Tue, 18 Jul 2017 04:04:33 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id 32so12632669qtv.1; Tue, 18 Jul 2017 04:04:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9lK/fkfLUH+Iwx9t6xjmrRrnIOTGAQLYFEamncUknlA=; b=MosNaGM7L9E0mPRzhfmbdwUX7hxu4C20sGGTTkNEa0hz7X70Jcjb6WNbkXBw9YcpDw H0jTbTOUm5OisV5vcrzkT7nzXAFGwqlhwXVXyjl5PizxsOggtB52ei20e1t2DlIz+tfQ 28/jq6i3wG0Qby80y7qhbN1oXB03jUj528AVoPhbaoK+Z10i9vv86cilK1nrBN0uUjWy O/fYZ0ZqUvs3oQImGcyO/flHaWJP02dD9yV9gkM/L/XhFA4q7KNg2uSJbZ+3wBb+ylSq GQt5B4dNpWllKp2FOvSKI49on0nSZuiYjsFnf+2xyZMlvm7P5Dym8YsmhqfY56FCZVdG wzoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9lK/fkfLUH+Iwx9t6xjmrRrnIOTGAQLYFEamncUknlA=; b=hprkYmErTgdcEGlZWZzm3Y1a+8nUBtoLYOOoeQUYHiJ6nXUKg5FiRF1okxmO9700wk bEIDeeWq1gkyW3TgWL8D/tY+s6K/cBEKkK+nzih2mTC6H3k3neGX7tsK64h7yXyDxsSh 2o1O8YhhbVfOBLQ1gcHjR9QTweihP/cu0FuLXktBEGP0jBnXujVhUoWGe2cz+Jj0wbvm 4yXgNNB7cXWq9dsxZsBONgVEJscowf4EHtkl+nF0CvIpQpstSNjP/FiyjEh3S7FaDxWF r3XD9WRIxH7kudWs+gdDM/4n1AfSm/aM4F06dwcg5KPepoS6Fq+dbWLhqVZk2x+L4bbR RzuQ==
X-Gm-Message-State: AIVw111dG2se8xrXKoLpksM3jRzYmpYpcybSDzbmvZjS16JcDMvpeqUE t0rataLVYkmM91E2fucmp+lEK79ACw==
X-Received: by 10.237.44.225 with SMTP id g88mr1165391qtd.150.1500375872539; Tue, 18 Jul 2017 04:04:32 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.200.37.40 with HTTP; Tue, 18 Jul 2017 04:04:32 -0700 (PDT)
In-Reply-To: <6a42a587-f09c-14bc-847b-7882c8f3e9f7@gmx.de>
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>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 18 Jul 2017 13:04:32 +0200
X-Google-Sender-Auth: GsoTXo3Hr3jvtx6EYYFqN4mN-yI
Message-ID: <CAC4RtVC0fBbw-YiifN5p-gPLxHYRB0jkSumankTTcY+KbyTasw@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "ietf@ietf.org" <ietf@ietf.org>, "json@ietf.org" <json@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/pbbrQuDrpCCWUx3IbfDoLcmiwso>
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:04:35 -0000

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

v2.23.0 | Report a Bug | By Email