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

"Paul Hoffman" <paul.hoffman@vpnc.org> Mon, 14 August 2017 16:50 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 B81C51321B9 for <json@ietfa.amsl.com>; Mon, 14 Aug 2017 09:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 pF74kSnz9Dti for <json@ietfa.amsl.com>; Mon, 14 Aug 2017 09:50:33 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CD2B120713 for <json@ietf.org>; Mon, 14 Aug 2017 09:50:33 -0700 (PDT)
Received: from [169.254.132.216] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v7EGnZ0e014280 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 14 Aug 2017 09:49:36 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [169.254.132.216]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Matthew A. Miller" <linuxwolf@outer-planes.net>
Cc: json@ietf.org
Date: Mon, 14 Aug 2017 09:50:31 -0700
Message-ID: <FBF7729E-40DD-4693-A08F-306E88F1FA75@vpnc.org>
In-Reply-To: <20320239-7afb-5d4a-047f-ae0132e2a0ca@outer-planes.net>
References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <DB9BA7EA-D393-4079-B347-620A09280B26@isode.com> <CAC4RtVBYMrRCrUZ1qqD+_rH4M8N23GOgbbh=921fEYqH+gCm5Q@mail.gmail.com> <c06e583a-965e-9eaf-975f-e6876ac056ed@filament.com> <f1a6b553-c787-e248-67bd-74d68d98a845@gmx.de> <262E8314-263A-4443-B912-AFCF1A3277B2@tzi.org> <166957c4-26fc-90b5-a798-59280c91b466@filament.com> <8B60039F-96DD-4F72-8139-D80B6F11566C@tzi.org> <3760a157-5b88-e334-712c-03eecd675794@codalogic.com> <7a88952c-3e46-3f87-b3c2-2864f216c62d@gmail.com> <9cddf2e7-f987-3942-3580-05c3da6a4805@codalogic.com> <2892a0eb-0bd2-cd2e-87e7-aa2e29009b4b@filament.com> <62d58ceb-282d-329d-3f27-8ed5ef268d13@codalogic.com> <20320239-7afb-5d4a-047f-ae0132e2a0ca@outer-planes.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/MlamzxP0LwG5HGc84-egFIdDC9s>
Subject: Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt
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: Mon, 14 Aug 2017 16:50:35 -0000

On 14 Aug 2017, at 9:40, Matthew A. Miller wrote:

> On 17/08/01 10:28, Pete Cordell wrote:
>> On 01/08/2017 17:01, Peter Saint-Andre - Filament wrote:
>>>
>>> We're not writing a novel here. :-)
>>
>> I had been thinking that too.  I do like the direction of focussing the
>> requirement on open systems communication though (not to be confused
>> with systems built on open software!).  I think the following is pretty
>> simple and side-steps issues about what is a network protocol, payload,
>> serialization etc.:
>>
>> 8.1.  Character Encoding
>>
>>    JSON text exchanged between systems that are not part of a closed
>>    ecosystem MUST be encoded using UTF-8.
>>
>>    Previous specifications of JSON have not required the use of UTF-8
>>    when transmitting JSON text.  However, the vast majority of JSON-
>>    based software implementations have chosen to use the UTF-8 encoding,
>>    to the extent that it is the only encoding that achieves
>>    interoperability.
>>
>>    Implementations MUST NOT add a byte order mark (U+FEFF) to the
>>    beginning of a networked-transmitted JSON text.  In the interests of
>>    interoperability, implementations that parse JSON texts MAY ignore
>>    the presence of a byte order mark rather than treating it as an
>>    error.
>>
>>
>
> Hello JSONbis Working Group,
>
> does anyone have comments on Pete Cordell's suggested text?

The current wording works for me, and so does Pete's.

--Paul