Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt

Peter Saint-Andre - Filament <> Fri, 21 July 2017 01:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7066F1270A3 for <>; Thu, 20 Jul 2017 18:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rePw-pGM2Sna for <>; Thu, 20 Jul 2017 18:42:53 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 72EFF126D73 for <>; Thu, 20 Jul 2017 18:42:53 -0700 (PDT)
Received: by with SMTP id l7so17968835iof.1 for <>; Thu, 20 Jul 2017 18:42:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=FtzVkXynp1xITWB0TLf4Nf/L+EFAPQgBfn0VRaN8Ifk=; b=Ba8vfIJdJgHPdShYlkW3hunNRijcxlRjRPPhmSbgiYb55yPI/ML9qZg5o0diVcLvDb DFEj+nb59EJMss5NtAuSBDnb/SNtI4zedRaILgIoepI1tq+y5ePuUhyQYYEyujxC2iGA SvQrMM+yve0MSWv1DBbVwlGOyV89TFJIMW/uqBIP5fXgW4SEIvkKJ5339sZqLno5GIWn uI+vzTfE9H5zpxLOiKomb9DvtrmdfervuuBtCH0C33quKiegeBf3/tDJOQvesP0g8k8S zHb/HXETGlDl72dOrhomvFR65vSn4BdwiVbvAWcI+fpjFFyVjPM2VpHR467cYM4/De0e hD/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=FtzVkXynp1xITWB0TLf4Nf/L+EFAPQgBfn0VRaN8Ifk=; b=E1eL04cSS6KUub+Lr0sYpz/roRdosGiUC2f8GxMVGkwSwvdo+s/AR66pTclolRxQvR KiRzh2eYzscyvWIvoSA1AHyAhjIRvjzaPFVMlBYycKmLWoeSDFP7RaqFM200kw5d+A9f Qjzm4jMs6uVdMeu/3zlSpxKRvdEmee2RUPBma2I6SqLTcLXn2XsXm8albe2R+sKK2pm9 V/wqVJkAd1IaVAuYUTY3TgYFeE0DPcG3JyYOgU1Fam7i9YjKKC90oNxvJYXXVZKmGI5t vl1dF8UglP2T88WzBwaX9YVz8P1K07OcnGoOcXmNBGuly8UPWneB/HwBoMueQaGdI2mB iKsg==
X-Gm-Message-State: AIVw1136iu1hEnulnW65jm64MkapwruIUOaPBaY0+zCMxSTCBWJNJL0R u2gQ8hCB5fasR8J4mZs=
X-Received: by with SMTP id i38mr5466173iod.22.1500601372697; Thu, 20 Jul 2017 18:42:52 -0700 (PDT)
Received: from aither.local ([2601:282:4202:67d3:20e7:86ef:990:8177]) by with ESMTPSA id f84sm133498ita.33.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jul 2017 18:42:51 -0700 (PDT)
References: <> <> <>
From: Peter Saint-Andre - Filament <>
Message-ID: <>
Date: Thu, 20 Jul 2017 19:42:49 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 21 Jul 2017 01:42:55 -0000

I have three comments about this new sentence:

   When transmitting over a network protocol, or as a payload of a
   network protocol intended to be interpreted as part of a protocol,
   JSON text MUST be encoded in UTF-8 (Section 3 of [UNICODE]).

1. Is the term "network protocol" sufficiently clear? It might be
interpreted as a communications protocol at the network layer (e.g.,
IP), not as an application-layer protocol above the network layer -
which is where most or all usage of JSON occurs.

2. What are we trying to say with "as a payload of a network protocol
intended to be interpreted as part of a protocol"?

3. Why do we reference Section 3 of the Unicode Standard for the
definition of UTF-8, not RFC 3629? (Among other things, there's no
guarantee that Section 3 of will
continue to talk about UTF-8.)

I suggest:

   When an entity transmits JSON text over a network, e.g. as the
   payload of an application protocol, it MUST encode that text using
   UTF-8 [RFC3629].


On 7/20/17 4:50 AM, Barry Leiba wrote:
> I've reviewed this version and I think it's ready to publish.
> Barry
> On Wed, Jul 19, 2017 at 4:03 PM, Alexey Melnikov
> <> wrote:
>> As requested by several people, this is the version that includes RFC Editor notes.
>>> On 19 Jul 2017, at 15:45, wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>> This draft is a work item of the Javascript Object Notation Update WG of the IETF.
>>>        Title           : The JavaScript Object Notation (JSON) Data Interchange Format
>>>        Author          : Tim Bray
>>>    Filename        : draft-ietf-jsonbis-rfc7159bis-04.txt
>>>    Pages           : 15
>>>    Date            : 2017-07-18
>>> Abstract:
>>>   JavaScript Object Notation (JSON) is a lightweight, text-based,
>>>   language-independent data interchange format.  It was derived from
>>>   the ECMAScript Programming Language Standard.  JSON defines a small
>>>   set of formatting rules for the portable representation of structured
>>>   data.
>>>   This document removes inconsistencies with other specifications of
>>>   JSON, repairs specification errors, and offers experience-based
>>>   interoperability guidance.
>>> The IETF datatracker status page for this draft is:
>>> There are also htmlized versions available at:
>>> A diff from the previous version is available at:
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at
>>> Internet-Drafts are also available by anonymous FTP at: