From nobody Tue Aug 1 09:01:18 2017 Return-Path: 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 9D27812EC1D for ; Tue, 1 Aug 2017 09:01:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=filament-com.20150623.gappssmtp.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 gNnrWwkUd8WQ for ; Tue, 1 Aug 2017 09:01:14 -0700 (PDT) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 DDB1D12EAE8 for ; Tue, 1 Aug 2017 09:01:12 -0700 (PDT) Received: by mail-it0-x22e.google.com with SMTP id 77so10175392itj.1 for ; Tue, 01 Aug 2017 09:01:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Mn1UWxZy2TyLc3YyPa6iRuC4bWfB4dtIne8Uz7WcLNM=; b=tIXUsoMldzLuj1F5jTjlOg+jvdHazl1NXv8E8WoRLFXhcon3QhQ5x7aKIcrXC4RBza O6rGP7nnZl96ltUDxdVRXUzudbBJ1SRYV/BsDNJaW+FVkCvFlGUaDWGhH7JVdxm7rl6M SeN6INpOTWEAUlO8P6w5gBRXZjND/PZQ5uQFumAHOgJDnFEXgrWpkmDnA6ZUsV9AgbYY lf0wvtCFQTcOlY4XfuE650KxiZ7YNJupFjQhSuWNPq9qm1ByuV5nn/ahm7EbLmM3139P bpsjCpju+fUjH4PpdiXWLW2+G/HkjieLIrgpEHzoeoqIHMfZu/HiU0CqWkZDyNA+21OV JXwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Mn1UWxZy2TyLc3YyPa6iRuC4bWfB4dtIne8Uz7WcLNM=; b=p+R+pVEOPhgLMqZiLRMmRVXcINk9XV2EY44rPA51qL0d3TsCcIs+YDWkQ6XgZyIB05 aCHE48KQIGmseaDWtNPpMoAh7Qc0OE0CjNCbzZaFIbVeQykUHhcU5iZe6vOgfL6nGC79 xe0bV4qIyTxmOGfp4zXshIF91IahnDN5LUT6DUJTDDy7oypLMiR29FLMkmnC6JWNId/A rRSSv+nFIEu6hZu2H9uYDzd488kAJ/HqW2tPicqGvXyT3AKGqL3WrO/gMfyl7S3gACd+ /FDDbaYGmHhJkrffyPBhzdSCQJ3zk8H0+CnrKsI908XxpDs+RD4/9oX0DSevi92VcfGw gv6A== X-Gm-Message-State: AIVw111oitPVEGi5uqtZ9ebw3Q/f1vmOYArOscM9waLmOVcLAboianNC e+QNvhWnT54GCXac X-Received: by 10.36.135.202 with SMTP id f193mr2369252ite.48.1501603272021; Tue, 01 Aug 2017 09:01:12 -0700 (PDT) Received: from aither.local ([2601:282:4202:67d3:698a:246b:b568:1b8d]) by smtp.gmail.com with ESMTPSA id f202sm14602951iof.69.2017.08.01.09.01.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Aug 2017 09:01:11 -0700 (PDT) To: Pete Cordell , Anders Rundgren References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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> Cc: Julian Reschke , json@ietf.org From: Peter Saint-Andre - Filament Message-ID: <2892a0eb-0bd2-cd2e-87e7-aa2e29009b4b@filament.com> Date: Tue, 1 Aug 2017 10:01:09 -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: <9cddf2e7-f987-3942-3580-05c3da6a4805@codalogic.com> 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-BeenThere: json@ietf.org 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: Tue, 01 Aug 2017 16:01:16 -0000 On 7/24/17 9:12 AM, Pete Cordell wrote: > On 22/07/2017 08:51, Anders Rundgren wrote: >> I don't have any text to offer but I believe that UFT-8 encoding is the >> only recommendable way for transferring JSON data from one system to >> another which includes lots of other use case than HTTP. For example: >> Writing JSON to databases, usage in WebSocket messages, or simply putting >> JSON in file. >> >> Yes, it seems to me that "Serialized format"/"External representation" is >> really the common denominator rather than networks and/or protocols. > > And: > > On 22/07/2017 10:18, Anders Rundgren wrote: >> I would consider "external form" as an alternative to limiting the >> specification >> to special cases like networks and or protocols. > > And: > > On 22/07/2017 08:53, Julian Reschke wrote: >> Whatever we say, it should make clear that it includes all derived >> media types (*/*+json) as well. > > Thanks Anders and Julian. > > Makes me wonder whether the best approach is to start with what is > currently the second paragraph of 8.1 as a 'softener', and then hit the > reader with UTF-8 being the only real way to go for interoperability of > open systems. We're not writing a novel here. :-) > So maybe 8.1 becomes something like: > > 8.1. Character Encoding > > 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. > > Therefore, JSON text exchanged between systems that don't form a > closed ecosystem MUST be encoded using UTF-8. > > 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. I feel like we're over-complicating things. I had proposed: 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]. Carsten said that looked fine to him. Julian suggested that we mention the application/json media type and types derived from it. Anders suggested that we specify this in terms of serialized formats between systems (even storage in a file) rather than networks or protocols. Taking that feedback into account, I suggest: When an entity represents JSON text in a serialized format (e.g., as the payload of an application protocol using the application/json media type or a type derived therefrom), it MUST encode that text using UTF-8 [RFC3629]. Peter From nobody Tue Aug 1 09:28:48 2017 Return-Path: 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 2D5CD131DF7 for ; Tue, 1 Aug 2017 09:28:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.92 X-Spam-Level: X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 zUsbjED8xW8j for ; Tue, 1 Aug 2017 09:28:45 -0700 (PDT) Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0324B131C28 for ; Tue, 1 Aug 2017 09:28:44 -0700 (PDT) Received: (qmail 18543 invoked from network); 1 Aug 2017 17:20:21 +0100 Received: from host109-157-169-220.range109-157.btcentralplus.com (HELO ?192.168.1.72?) (109.157.169.220) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 1 Aug 2017 17:20:21 +0100 To: Peter Saint-Andre - Filament , Anders Rundgren Cc: Julian Reschke , json@ietf.org References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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> From: Pete Cordell Message-ID: <62d58ceb-282d-329d-3f27-8ed5ef268d13@codalogic.com> Date: Tue, 1 Aug 2017 17:28:40 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <2892a0eb-0bd2-cd2e-87e7-aa2e29009b4b@filament.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Archived-At: 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2017 16:28:47 -0000 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. Pete Cordell Codalogic Ltd C++ tools for C++ programmers, http://codalogic.com Read & write XML in C++, http://www.xml2cpp.com From nobody Wed Aug 9 06:34:58 2017 Return-Path: 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 852B71321BB for ; Wed, 9 Aug 2017 06:34:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 2KT4xp76jVhS for ; Wed, 9 Aug 2017 06:34:55 -0700 (PDT) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 920EF131D2F for ; Wed, 9 Aug 2017 06:34:55 -0700 (PDT) Received: by mail-io0-x22d.google.com with SMTP id g35so24924021ioi.3 for ; Wed, 09 Aug 2017 06:34:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=hxr01OQZYOLcfH7Ug0a/yBZBKgDAo6PD4DYK18q/fkg=; b=R9HQ3AC2+A6ELjrtcgLJWFmEraSfdNJFJ0tCGUTdczQYqSLCG16ZE7PoNKbhXa/uXK DwaKNPFeSH9X1LKC3y5uuW5xayi/wGYS0Wv9GugPmIvFZrVUyOiXaGaFqSDHoTBDXulv hYdkBiI+7VtcKehJwruaHiYi0sz3IjcZ7RuQVSbBRFlH0esztBIvVBmosSfwwkyOhW8M QHI5GK61rCcBDdxHMXbS6MVtYtxSHX+JdzrdFEFVIBKsKs5t9IT/QdhWBRe4+LEnHG+C /UCPGoX/9be6/Xq+38CokzwsD9mkDddfOu7QeH5OGyJn/JD2i/1kSdqScKzyh5UeLAoX khuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hxr01OQZYOLcfH7Ug0a/yBZBKgDAo6PD4DYK18q/fkg=; b=uP/3zscgm8pDjR91lhFX6N7gqEErpaFLFFit9CshGqwGzgsgsYZZ98G0HTbQOmQEN1 cPaNhkiZFXiru3gvNaIPA/dcbTLa+HNoi9JL70nbPbcNsXpR3VC71MZa/tnj6/LIRNrf dA6w8eM0DiUan93UlcHFA2bQpQ5dv9BW43VT4NIe3Qqs+ng5Srg/RbRbod2I3UPMbE3A DlO+xoCLj+9lbl1ZNrkRjhsj8cItZgpebU93qqYXleRrzUf3FyDKNI29ZzvtfVfCaVGB FSqkAoccZzUc6VqR8QZFKYbczfwWOcoIqsSBTOLJtpaXTqAd2DYtknKpGTDWLd4Q9fe+ nG0g== X-Gm-Message-State: AIVw11305TjfKwgs6WFFDpf+kC1x1VGQDUu1tyVoEx2/UhA/AT4HTsRu hzqC9FsriL2L0GOKKRJEacOeLNI0ogHTU/k= X-Received: by 10.107.172.199 with SMTP id v190mr6418664ioe.159.1502285694362; Wed, 09 Aug 2017 06:34:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.143.80 with HTTP; Wed, 9 Aug 2017 06:34:33 -0700 (PDT) From: Bradley Meck Date: Wed, 9 Aug 2017 08:34:33 -0500 Message-ID: To: json@ietf.org Content-Type: multipart/alternative; boundary="001a1148d73429e8a10556522525" Archived-At: Subject: [Json] Add Extension to JS MIME X-BeenThere: json@ietf.org 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: Wed, 09 Aug 2017 13:34:57 -0000 --001a1148d73429e8a10556522525 Content-Type: text/plain; charset="UTF-8" Hiya! I would like to ask about adding a new file extension to the IANA MIME registry for `application/javascript`. It seems the IESG is in charge of that mime per https://www.iana.org/assignments/media-types/ application/javascript . The change request is to add `.mjs` as a known extension as Node.js merges support for the new Module parse goal of JavaScript. Doing so as the PR is merged seemed the best way to get people to update their MIME libraries in a timely manner as well. Let me know what I need to do to get this process started / if there is some better place to ask. Cheers, Bradley --001a1148d73429e8a10556522525 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hiya!

I would like to ask about adding a new file exten= sion to the IANA MIME registry for `application/javascript`. It seems the I= ESG is in charge of that mime per=C2=A0https://www.iana.org/assignments/media-types/application/javascript=C2=A0.=

The change request is to add `.mjs` as a known extension as Node.j= s merges support for the new Module parse goal of JavaScript. Doing so as t= he PR is merged seemed the best way to get people to update their MIME libr= aries in a timely manner as well.

=
Let me know what I need to do to get = this process started / if there is some better place to ask.

Cheers,
Bradley
--001a1148d73429e8a10556522525-- From nobody Mon Aug 14 09:41:03 2017 Return-Path: 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 2E53D1321B9 for ; Mon, 14 Aug 2017 09:41:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.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 f9hAWpkkJUHL for ; Mon, 14 Aug 2017 09:40:59 -0700 (PDT) Received: from mail-yw0-x242.google.com (mail-yw0-x242.google.com [IPv6:2607:f8b0:4002:c05::242]) (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 72C79120713 for ; Mon, 14 Aug 2017 09:40:59 -0700 (PDT) Received: by mail-yw0-x242.google.com with SMTP id n83so6522743ywn.3 for ; Mon, 14 Aug 2017 09:40:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=KYUVOJNFyXAmurdPcnysn2FwDPga/QZwG8IX9+92RMI=; b=KJcZX4ss8q6IfpnS6fKuAZdZiFQAT8ajV5Q4dctDUumpM1mpA0nj8nzaxZ3x9CiLA4 KbVuEK6/YQB6KDkY9jWiq8mi9FG0Gd/HNryxvlJOFxXNrlPhmtW1P/xbnZ0TXaMreN9F rfGc/yfSnD9T2GaerCf9ONoY1jQNmSpJalx0hRlYXsNO8HCQGN08UyiVb0G4a20bfBrk eXP5nBvfuCi+o1MTl7wZHG8yj5MTP3n5Sa1rokmZl+w7g5Ur88OHLU4qIhGYKMNCub14 Sxr7Vwk9ACaeWEkkM9QeAlLBilpGKhKhVsCy1BY+PNDK6dq/eNOY7LiQ6YygDe944nPX OFYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=KYUVOJNFyXAmurdPcnysn2FwDPga/QZwG8IX9+92RMI=; b=EButOSzzHZPFYHdfenxhR2jJjs+HJiGewsWgOlAEQHtqGck2Q0KgHRG4kRJTkr33ve 0EN10MCzjUJC7ugVRzEgqYILKmRkHwxN8tUvaHb4WCombZCP6ZYhyuNHatz6O5DM2w38 BkZk60vTGbgS/HNici3W78PIKUWlrUmh4fXz9NYBn2bidjaG/BrgtHHE1nHkF21aT7Vg rOKU6hy4G9PseDKyThWI6R9vQvV4pv7Z2ykIuNggEAHBLQ6cEL0vxRk+954vuqmIbhCd QV0AZl2FMCwxEjqXP3aBfG7Bt2uxtiLZ5p7k+GDeklr2eGQMlC6Wd3Ir77b9lAufvDdR Earw== X-Gm-Message-State: AHYfb5hO5HYcEOunicj/id0L1RSjnYz5+fuFSe9L18EC0WVzCfG06XDC kU5UC6B9392yAotZMLZlvA== X-Received: by 10.13.212.201 with SMTP id w192mr20196717ywd.100.1502728858114; Mon, 14 Aug 2017 09:40:58 -0700 (PDT) Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id 204sm2850016ywk.50.2017.08.14.09.40.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Aug 2017 09:40:57 -0700 (PDT) To: json@ietf.org References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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> From: "Matthew A. Miller" Message-ID: <20320239-7afb-5d4a-047f-ae0132e2a0ca@outer-planes.net> Date: Mon, 14 Aug 2017 10:40:55 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Thunderbird/55.0 MIME-Version: 1.0 In-Reply-To: <62d58ceb-282d-329d-3f27-8ed5ef268d13@codalogic.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="j03JtnqI2LjIXc9G4v4e9LpA9DWW58e9k" Archived-At: 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Aug 2017 16:41:01 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --j03JtnqI2LjIXc9G4v4e9LpA9DWW58e9k Content-Type: multipart/mixed; boundary="u61oDGqw4Xh47kaC96eVaL05ROeCxkubx"; protected-headers="v1" From: "Matthew A. Miller" To: json@ietf.org Message-ID: <20320239-7afb-5d4a-047f-ae0132e2a0ca@outer-planes.net> Subject: Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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> In-Reply-To: <62d58ceb-282d-329d-3f27-8ed5ef268d13@codalogic.com> --u61oDGqw4Xh47kaC96eVaL05ROeCxkubx Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable 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. :-) >=20 > I had been thinking that too.=C2=A0 I do like the direction of focussin= g the > requirement on open systems communication though (not to be confused > with systems built on open software!).=C2=A0 I think the following is p= retty > simple and side-steps issues about what is a network protocol, payload,= > serialization etc.: >=20 > 8.1.=C2=A0 Character Encoding >=20 > =C2=A0=C2=A0 JSON text exchanged between systems that are not part of a= closed > =C2=A0=C2=A0 ecosystem MUST be encoded using UTF-8. >=20 > =C2=A0=C2=A0 Previous specifications of JSON have not required the use = of UTF-8 > =C2=A0=C2=A0 when transmitting JSON text.=C2=A0 However, the vast major= ity of JSON- > =C2=A0=C2=A0 based software implementations have chosen to use the UTF-= 8 encoding, > =C2=A0=C2=A0 to the extent that it is the only encoding that achieves > =C2=A0=C2=A0 interoperability. >=20 > =C2=A0=C2=A0 Implementations MUST NOT add a byte order mark (U+FEFF) to= the > =C2=A0=C2=A0 beginning of a networked-transmitted JSON text.=C2=A0 In t= he interests of > =C2=A0=C2=A0 interoperability, implementations that parse JSON texts MA= Y ignore > =C2=A0=C2=A0 the presence of a byte order mark rather than treating it = as an > =C2=A0=C2=A0 error. >=20 >=20 Hello JSONbis Working Group, does anyone have comments on Pete Cordell's suggested text? - m&m Matthew A. Miller < http://goo.gl/LM55L > --u61oDGqw4Xh47kaC96eVaL05ROeCxkubx-- --j03JtnqI2LjIXc9G4v4e9LpA9DWW58e9k Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJZkdKYAAoJEOz0ck4QngW7l08IAJ5wQ8GnKm2t9PNRFevrYVdY uvXusaC/oewt+fFwKJOACt8hkAuXji4xlRf456cIz92jNDN9uS4y+ENwQIhWule5 3Gv9u87CMlGGLdxBDgdebTTp3tV1JOR5a7IWFSAtjA3KjlmuVIQ4HSlQC9DfwfvR 0vnnSJC4IJ3gpuq5vmMCtGD5aDAHlpt0bD0H+NsqNz2/SSnReDiBBw8ifPtuc4E+ rwiPbmGUODQecNTJbFw8noVfeo1/pgYMEhUd7v0glZz3Kd+DqkWeGdmwP6B18pk1 SHpjhTqhwwzICXjyD51/54RimKv753j7dJg/y1wuxSo2EToq7PVHm3VNXIe15Lk= =zc5p -----END PGP SIGNATURE----- --j03JtnqI2LjIXc9G4v4e9LpA9DWW58e9k-- From nobody Mon Aug 14 09:50:35 2017 Return-Path: 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 ; 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 ; 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 ; 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" To: "Matthew A. Miller" Cc: json@ietf.org Date: Mon, 14 Aug 2017 09:50:31 -0700 Message-ID: In-Reply-To: <20320239-7afb-5d4a-047f-ae0132e2a0ca@outer-planes.net> References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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: 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From nobody Mon Aug 14 09:56:24 2017 Return-Path: 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 7985D1323A4 for ; Mon, 14 Aug 2017 09:56:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=filament-com.20150623.gappssmtp.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 ZxyqZsxJX9IN for ; Mon, 14 Aug 2017 09:56:22 -0700 (PDT) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 E987D1321B9 for ; Mon, 14 Aug 2017 09:56:21 -0700 (PDT) Received: by mail-it0-x22c.google.com with SMTP id f16so11451149itb.0 for ; Mon, 14 Aug 2017 09:56:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=wX4lyjVcoSwwd9SYD2w9JoeGRiRfgff52GNv8FHKXH0=; b=yx13FHg8w5Wwbg5Bb8LPTHFgr2uKKkHrbQRUA6exoJDfnhbv/UwPkC7NWAc8S08Eip 5jspKrCrtZ5ctZwSBe6vHmLXW0l8QDCxXvoLmeLgIc8G5S0N4LQgPN0DkEjRGHC1FbMU 6lezwPTiBsqpkhbvYRSgmfFEGUdUEG7HgLJBZEvnLq0i+huchGJexDCo9XxfFHceI3DP Z06BFRPZQQM06GlYKaLWPa8+sxE3aU5PhosNPxA0aD7ogcsh0Kf3j7D1XI1NZ0jgBOAS Ap6Z2tst7A2Ml/Pr6N1/XRp1a7l2P6We8zuJ2RqOv8UiOU/56+NDAMuyhdBWbNNjXU7z E2zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=wX4lyjVcoSwwd9SYD2w9JoeGRiRfgff52GNv8FHKXH0=; b=rlb9G94Hroi/NsK/uT9GSsur7/MWNhrwDd+tN2+IYaMyhHxYoijHOpn4vsxqlZ+u0G 0AfYRSqKVzrpzYMKIsiymWOm11d0n8APtVqa6XFwMRWG1sWAT0J3K5Fta+MJlooctJzW HQPEGO2jyWMYTf5ZJXVbGUaAndXDmDn0S4GwsDI99copZQ1RrffOMcKH9RrGnHr44sC8 hVstyJh2TPMZsQQPSNFWcoad5hx1/A0wiwV8HQoDsw0DukC6ftNKiSwedroRV14C11td 7An+wZ93/EjVk7mNJDecYhW34OySswNlXxChexTE0KMSTZDzT6KCEREyHKKmRTOktEsc c8kw== X-Gm-Message-State: AHYfb5hLA0HniJnona3d8dJOugLQ2ildZHS9A+in/vT05k3ugx/NCUIM qdxUApCqMObCzDQm X-Received: by 10.36.113.70 with SMTP id n67mr6949443itc.39.1502729781192; Mon, 14 Aug 2017 09:56:21 -0700 (PDT) Received: from aither.local (71-33-179-50.hlrn.qwest.net. [71.33.179.50]) by smtp.gmail.com with ESMTPSA id k66sm2890534ita.40.2017.08.14.09.56.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Aug 2017 09:56:19 -0700 (PDT) To: Paul Hoffman , "Matthew A. Miller" References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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> Cc: json@ietf.org From: Peter Saint-Andre - Filament Message-ID: <5625f6c1-8f23-a0a9-63d8-059080299247@filament.com> Date: Mon, 14 Aug 2017 10:56:18 -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=utf-8 Content-Transfer-Encoding: 7bit Archived-At: 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Aug 2017 16:56:23 -0000 On 8/14/17 10:50 AM, Paul Hoffman wrote: > 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. What Pete suggested seems good enough. Peter From nobody Mon Aug 14 10:37:01 2017 Return-Path: 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 38E7B1323B9 for ; Mon, 14 Aug 2017 10:37:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.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 zmz897uaqx8z for ; Mon, 14 Aug 2017 10:36:58 -0700 (PDT) Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 7A7D91323B5 for ; Mon, 14 Aug 2017 10:36:58 -0700 (PDT) Received: by mail-yw0-x236.google.com with SMTP id u207so59007836ywc.3 for ; Mon, 14 Aug 2017 10:36:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to; bh=4/y3YFj4Ag/T1kpgQTnH+0A5T4pPdbPDyMx/sy2/hIo=; b=AlPrW3blkIXfYM0IdRtnOLVJKMTnv/g/bHtoPlWSWUCnFWTiD3jCcB3/XZOux+hbkg 1QyAd2AbdVewd1K3V/5s+vAfNjunpOCzmIbt8bmZ/+CTgcp9SQxhFbgVvqpyYQ9N5Wxp KocM9kDjILkfCXIBq1FeUPTGYGphiC8TFshf8TZyg8pNnpkESKJ8QtgWUnZ3r6wxwB0g 5ffsspKgFwrPLCpT8hfHBQ9ChYibg5yFTCinKgDrclrBViJ0petvIig0mL5UGw3J4jH9 mrwejsS5XwU0d6IIQRWLN/qThZu7zanOSH5nZsaZOf8Q+Bjc/t+mKpP4e2g6IcViyfZk b4Sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to; bh=4/y3YFj4Ag/T1kpgQTnH+0A5T4pPdbPDyMx/sy2/hIo=; b=WqcVMZdpRMyRqNfE3I3IsEJF7Sogp+JVvNtU7N7TDoTfGfg5Zo42P46uY72i6dzpf/ e3BwBTlHuGQftsMdSOBlCcHT3Br2GslXffxYt7VJENB/x27uxa6lCguclYZ9noE0L9PU Q7XVVMRm7HBmd9qu7EnTopI0uLPnrB6o8keUOTX9LuY6+tHQkKP8zfVcu9vKAwZQZ5Dp va/Gv7kibyo8kB9n/GXjX9U26/jC5TDGPEbZMp0cYlFcDwcgixgutccE11CtfVYWwz78 GT+DifFUvtwSpMNvSDwt5BuAeFKmmtdaJff6+w5T0W2Hqur8p60VlhtpfqpYqafeFIVn kYlw== X-Gm-Message-State: AHYfb5ihBq1ZMKAO7MGzSXkCzAjU/WkY6CmMbVTmpiOfa1RXvOPcYrZb 8OozrOiKup8mHMH8 X-Received: by 10.129.227.73 with SMTP id w9mr20175451ywl.77.1502732217658; Mon, 14 Aug 2017 10:36:57 -0700 (PDT) Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id u186sm2910958ywd.73.2017.08.14.10.36.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Aug 2017 10:36:56 -0700 (PDT) To: json@ietf.org References: From: "Matthew A. Miller" Cc: art-ads@ietf.org Message-ID: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> Date: Mon, 14 Aug 2017 11:36:55 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Thunderbird/55.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ek5QdpaD20Hjn5DPxbSA69CMegoOliI7F" Archived-At: Subject: Re: [Json] Add Extension to JS MIME X-BeenThere: json@ietf.org 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: Mon, 14 Aug 2017 17:37:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ek5QdpaD20Hjn5DPxbSA69CMegoOliI7F Content-Type: multipart/mixed; boundary="gEWF5Bjgu3aphqXocHmc6hfuKQ295ikRo"; protected-headers="v1" From: "Matthew A. Miller" To: json@ietf.org Cc: art-ads@ietf.org Message-ID: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> Subject: Re: [Json] Add Extension to JS MIME References: In-Reply-To: --gEWF5Bjgu3aphqXocHmc6hfuKQ295ikRo Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 17/08/09 07:34, Bradley Meck wrote: > Hiya! >=20 > I would like to ask about adding a new file extension to the IANA MIME > registry for `application/javascript`. It seems the IESG is in charge o= f > that mime > per=C2=A0https://www.iana.org/assignments/media-types/application/javas= cript > =C2= =A0. >=20 > The change request is to add `.mjs` as a known extension as Node.js > merges support for the new Module parse goal of JavaScript. Doing so as= > the PR is merged seemed the best way to get people to update their MIME= > libraries in a timely manner as well. >=20 > Let me know what I need to do to get this process started / if there is= > some better place to ask. >=20 Hello Bradley, I think the right approach here is create an internet-draft upating RFC 4329, adding .mjs as one of the extensions for "application/javascript". That I-D would likely need to be [DISPATCH]ed, as there is no existing WG I can see that covers this. For the document, at the very least it seems necessary to update the ECMA-262 reference in addition to the updated IANA instructions. I'm not sure much of anything does need to be said about differences between =2Emjs versus .js -- the content is still JavaScript, but hinting at differences in module expectations. The IANA considerations section itself, I don't know what the right wording is in this case. I think almost everything stays the same, other than the file extension(s), and the published specification? - m&m Matthew A. Miller < http://goo.gl/LM55L > PS: Thanks to Adam Roach for confirming my thoughts, and suggesting some places to look at. [DISPATCH] - https://datatracker.ietf.org/wg/dispatch/about/ --gEWF5Bjgu3aphqXocHmc6hfuKQ295ikRo-- --Ek5QdpaD20Hjn5DPxbSA69CMegoOliI7F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEbBAEBCgAGBQJZkd+4AAoJEOz0ck4QngW7LWwH9At6+0wZWWtWqEZ8hVBgA/P/ I6l4YWgNg3ifh0kOrQqppVQUcAHbAgGp109XJMQbZR4fv5opgyNr/Sz2zJwxIIsQ uS+VGx9nCh6d564POARBKpIXXj99FBy+zYYrfgwUPmRGN7w95gAqcFDEtKT1+j0Q EETsf4lMpDI3hxUgplLAu1fJa7PrUZXaQJG982z4GjcDWTH+mak0c5nzb096nxMu qWgiEEHvcdkAxRzHp9dXCb+uGp2X44JFAyJaO/hmD7KpJTgTURa8GV4IkZKWTXoq t5CmK6gAhO9btwr0q6pKLCVIT0HzNGDBsfsBG39NYay4NF5vOSpwfi5bwUskQA== =exsc -----END PGP SIGNATURE----- --Ek5QdpaD20Hjn5DPxbSA69CMegoOliI7F-- From nobody Mon Aug 14 11:00:37 2017 Return-Path: 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 C769E1323C8; Mon, 14 Aug 2017 11:00:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 WKLSOIkTgrLa; Mon, 14 Aug 2017 11:00:30 -0700 (PDT) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 5CC8B1323C4; Mon, 14 Aug 2017 11:00:30 -0700 (PDT) Received: by mail-io0-x22a.google.com with SMTP id o9so41246658iod.1; Mon, 14 Aug 2017 11:00:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LXNdwvG9kaGHvBYgaGp666Cj1SQAUTFjkivWaV4B2fQ=; b=u148BYmrUO+zu1wcuAk0eNzaUFv/sJrAQhx3sd5FiN3SnCUMrp5rMbqdaeSvXZ7TcP QkgogKyB4N8yBi0wrNiSsDCjNPOiG2UZ7wfVeDNPnGlunJ1SCkdpAe9IzU7azFTkpH2J GOA/JWHbFv5RZUwtDCisSMDsrTEh4caoFOnFa82RAAJU9tMq+Fx0W5u/F+FGp08yhI6F 3e0gmAAe6ZCnWnEVyPPMSqwBvYJ27VUrjDyq1xkuiuQ2aLBo8JhR6Srb3P9yiNLSaCJT F9wYaUZFOm6QRxAWdq1lwlCwgfeapGFvAZJgXO4p5lT52eA87KIlvqDFsQrt67JS/5X3 hw6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LXNdwvG9kaGHvBYgaGp666Cj1SQAUTFjkivWaV4B2fQ=; b=q7Dj3TdstOe33O0Cx6KTGhN5eEFYpaerl54Rri16oeP/XHuwxU8+zyMEtEquVVG8yu WEgH0Hh/DTar6W9M0fRI5ZLLWAw2A3JK48JRUWFfnyC/nDa7r0SIUff9FAkOZx5dWbUf YjtUPzJfBxyp1uUHhXEynYW5bv9wyYkWUoN9krnrdElY+sskZIx4oOa8qbNuM1c58cYs dr05JFRpC2jU968LaxdTORkbYvbP1wyA+iYFfPNgomt6YioNYCxLCrDPVTlTtpWXujRX CqQMAyj8xVeMgFhI78giRQA6BJ7vsCB+xpYUaY5oM5MFUK1gSFnTjYqKan9B+eitLgeY XOVA== X-Gm-Message-State: AHYfb5gz7BKKZXsLWjydAbplS3UEqXCASiwvgWB3MPGmSsm65Gu/ZPTR 6XEET89ik/SQuCpuMQDIof2mm8ChrIvwniY= X-Received: by 10.107.19.78 with SMTP id b75mr14714073ioj.4.1502733629522; Mon, 14 Aug 2017 11:00:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.143.80 with HTTP; Mon, 14 Aug 2017 11:00:09 -0700 (PDT) In-Reply-To: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> References: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> From: Bradley Meck Date: Mon, 14 Aug 2017 13:00:09 -0500 Message-ID: To: "Matthew A. Miller" Cc: json@ietf.org, art-ads@ietf.org Content-Type: multipart/alternative; boundary="001a113f26fc2e06eb0556ba7008" Archived-At: Subject: Re: [Json] Add Extension to JS MIME X-BeenThere: json@ietf.org 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: Mon, 14 Aug 2017 18:00:33 -0000 --001a113f26fc2e06eb0556ba7008 Content-Type: text/plain; charset="UTF-8" Thanks, replies inline. > Hello Bradley, > > I think the right approach here is create an internet-draft upating RFC > 4329, adding .mjs as one of the extensions for "application/javascript". > That I-D would likely need to be [DISPATCH]ed, as there is no existing > WG I can see that covers this. > I have never made/updated an RFC. Is there a tutorial on how to do this. I don't know what I-D / [DISPATCH] means, it looks like a different WG? Do I send a new email to their mailing list? > > For the document, at the very least it seems necessary to update the > ECMA-262 reference in addition to the updated IANA instructions. I'm > not sure much of anything does need to be said about differences between > .mjs versus .js -- the content is still JavaScript, but hinting at > differences in module expectations. > TC39 / ECMA262 has said that they are not in the business of the MIME in https://github.com/tc39/ecma262/issues/322 . So there won't be any need to change references to that standard. > > The IANA considerations section itself, I don't know what the right > wording is in this case. I think almost everything stays the same, > other than the file extension(s), and the published specification? > Yes, for the IANA, the only change is to add the file extension. There could be a separate update since WHATWG treats text/javascript as the default as per https://html.spec.whatwg.org/multipage/scripting.html#prepare-a-script / https://github.com/nodejs/node-eps/pull/61#issuecomment-321304962 . However, I think that is a separate change. > > - m&m > > Matthew A. Miller > < http://goo.gl/LM55L > > > PS: Thanks to Adam Roach for confirming my thoughts, and suggesting some > places to look at. > > [DISPATCH] - https://datatracker.ietf.org/wg/dispatch/about/ > > > _______________________________________________ > json mailing list > json@ietf.org > https://www.ietf.org/mailman/listinfo/json > > --001a113f26fc2e06eb0556ba7008 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, replies inline.



Hello Bradley,

I think the right approach here is create an internet-draft upating RFC
4329, adding .mjs as one of the extensions for "application/javascript= ".
=C2=A0That I-D would likely need to be [DISPATCH]ed, as there is no existin= g
WG=C2=A0 I can see that covers this.

I = have never made/updated an RFC. Is there a tutorial on how to do this. I do= n't know what I-D / [DISPATCH] means, it looks like a different WG? Do = I send a new email to their mailing list?
=C2=A0

For the document, at the very least it seems necessary to update the
ECMA-262 reference in addition to the updated IANA instructions.=C2=A0 I= 9;m
not sure much of anything does need to be said about differences between .mjs versus .js -- the content is still JavaScript, but hinting at
differences in module expectations.

TC3= 9 / ECMA262 has said that they are not in the business of the MIME in=C2=A0= https://github.com/t= c39/ecma262/issues/322 . So there won't be any need to change refer= ences to that standard.
=C2=A0

The IANA considerations section itself, I don't know what the right
wording is in this case.=C2=A0 I think almost everything stays the same, other than the file extension(s), and the published specification?

Yes, for the IANA, the only change is to add th= e file extension.
=C2=A0
There could be a separate upda= te since WHATWG treats text/javascript as the default as per https:= //html.spec.whatwg.org/multipage/scripting.html#prepare-a-script / h= ttps://github.com/nodejs/node-eps/pull/61#issuecomment-321304962 . Howe= ver, I think that is a separate change.



- m&m

Matthew A. Miller
< h= ttp://goo.gl/LM55L >

PS: Thanks to Adam Roach for confirming my thoughts, and suggesting some places to look at.

[DISPATCH] - https://datatracker.ietf.org/wg/dis= patch/about/


_______________________________________________
json mailing list
json@ietf.org
https://www.ietf.org/mailman/listinfo/json


--001a113f26fc2e06eb0556ba7008-- From nobody Mon Aug 14 11:31:17 2017 Return-Path: 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 4A50B1323C4 for ; Mon, 14 Aug 2017 11:31:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable 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 wthG7FReABIr for ; Mon, 14 Aug 2017 11:31:13 -0700 (PDT) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 9D7921323B5 for ; Mon, 14 Aug 2017 11:31:13 -0700 (PDT) X-MHO-User: bf2feb20-811e-11e7-950d-03a3531dacf2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 50.39.217.219 X-Mail-Handler: DuoCircle Outbound SMTP Received: from [192.168.254.4] (unknown [50.39.217.219]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id bf2feb20-811e-11e7-950d-03a3531dacf2; Mon, 14 Aug 2017 18:31:12 +0000 (UTC) From: Allen Wirfs-Brock Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_8830C186-3C3B-443E-BC36-8ED72B0418ED" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Mon, 14 Aug 2017 11:31:09 -0700 In-Reply-To: Cc: "Matthew A. Miller" , art-ads@ietf.org, json@ietf.org To: Bradley Meck References: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Json] Add Extension to JS MIME X-BeenThere: json@ietf.org 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: Mon, 14 Aug 2017 18:31:16 -0000 --Apple-Mail=_8830C186-3C3B-443E-BC36-8ED72B0418ED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Aug 14, 2017, at 11:00 AM, Bradley Meck = wrote: >=20 > TC39 / ECMA262 has said that they are not in the business of the MIME = in https://github.com/tc39/ecma262/issues/322 = . So there won't be any = need to change references to that standard. Actually the references (and some of the referencing text) probably = should be updated given that 4329 says: "The types defined in this document are applicable to scripts written in = [JS15] and [ECMA], respectively, as well as to scripts written in a = compatible language or profile such as [EcmaCompact]. This document does not address scripts written in other languages. In = particular, future versions of JavaScript, future editions of [ECMA], = and extensions to [ECMA], such as [E4X], are not directly addressed. = This document may be updated to take other content into account. =E2=80=9C and the reference [ECMA]] is specifically to ECMA-262, Edition 3. Also = [EcmaCompact] and [E4X] have been withdrawn as Ecma standards [JS15] = is very obsolete and a vendor specific document. Given that ECMA-262 is not revised on a year scheduled, the [ECMA] = reference should probably change to an undated reference. Allen= --Apple-Mail=_8830C186-3C3B-443E-BC36-8ED72B0418ED Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Aug 14, 2017, at 11:00 AM, Bradley Meck <bradley.meck@gmail.com> wrote:

TC39 / ECMA262 has said that = they are not in the business of the MIME in https://github.com/tc39/ecma262/issues/322 . So there won't be any = need to change references to that = standard.

Actually the references (and some of the referencing text) = probably should be updated given that 4329 says:

"The types defined in = this document are applicable to scripts written in [JS15] and [ECMA], = respectively, as well as to scripts written in   a compatible = language or profile such as [EcmaCompact].

This document does not address scripts = written in other languages. In particular, future versions of = JavaScript, future editions of [ECMA], and extensions to [ECMA], such as = [E4X], are not directly addressed.  This document may be updated to = take other content into account.
=E2=80=9C

and the reference = [ECMA]] is specifically to ECMA-262, Edition 3.  Also [EcmaCompact] = and [E4X] have been withdrawn as Ecma standards   [JS15] is very = obsolete and a vendor specific document.

Given that ECMA-262 is not revised on a = year scheduled, the [ECMA] reference should probably change to an = undated reference.

Allen
= --Apple-Mail=_8830C186-3C3B-443E-BC36-8ED72B0418ED-- From nobody Mon Aug 14 11:43:44 2017 Return-Path: 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 D4F761323B5 for ; Mon, 14 Aug 2017 11:43:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.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 FbZf3nre0u-k for ; Mon, 14 Aug 2017 11:43:41 -0700 (PDT) Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 C4C301323C4 for ; Mon, 14 Aug 2017 11:43:41 -0700 (PDT) Received: by mail-yw0-x22b.google.com with SMTP id l82so59872891ywc.2 for ; Mon, 14 Aug 2017 11:43:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=mv+4tlN2Jjy8Y0RHE+YgbGIcMlqjI6abihZNb4SnsYg=; b=dCcIEU2tH3L3LyN4Sayo7TF/tmiAnYYfNUpa8fCE7LKswhDkHt1OO7HU0TD7RAmetL hX4NCWOlhXWeuxjHeaLZdOUZIvRQHULZGVjYTUNth2Y1hHC1BP+XjwePmZRJ0e9+iKzR OdCvfEWGwV8AWkHd8Dy2ySg3hoxLAmnL7Q7mmxnGV8hB3ejITmfpEmjmY+HBSPy3IaK6 lpphjn7uV659aU2mNk0RyII28tx4lVyq0vhsnBXe+JlSP3n1JVRd8bap91lSe7prAqup OnjCPUVOLtFPJ30p4C5Raq9vWnNMSKxbi+gtSXwUAEvMHGOUGzvywklZenF44u9QOtn+ h31g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=mv+4tlN2Jjy8Y0RHE+YgbGIcMlqjI6abihZNb4SnsYg=; b=di7UEn2QtMgX+jIgkluXbIiM66WOMoVqGAs3og1jHTP1r66gJ/ueBZLnexUeVoEppf UGmjNrDlhnaVfy0x5eLZ+fEhxQNoU25pEDiDZ2VlIt/ydQaIyLUazwJkEUo+fLwwM98G GF8E8gLD8yGs0AgKbQXJe9w1B9ZXMkg4Cn81kKxFLQfV4E/bSLXLF5ytzptTXyzov8eN XFOcGD6TLbjWXY3fAsi4PMtdUy6BFjqunP05/6uQ1LMcprV7+06Y8Aj+RhI2pZMCwAa3 IuPt6PUCM7fWxon8SR8zUKloybZD3k+B+l413WmIBExIGsUjrQdToc0O5YYQ0Ro33Dys 8Ipw== X-Gm-Message-State: AHYfb5hxiQaP9WO2ct12fJODV48M40VTZqXVDL+rHgtB2Cz/rcFmGYvt 3hCSucAvw8DWUbEbvb74ng== X-Received: by 10.13.193.132 with SMTP id c126mr21718676ywd.13.1502736220678; Mon, 14 Aug 2017 11:43:40 -0700 (PDT) Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id f127sm2942402ywc.0.2017.08.14.11.43.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Aug 2017 11:43:40 -0700 (PDT) Sender: Matthew Miller To: json@ietf.org References: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> From: "Matthew A. Miller" Message-ID: <0dbcfa02-d9ce-caf9-bc76-9eccffffa688@outer-planes.net> Date: Mon, 14 Aug 2017 12:43:37 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Thunderbird/55.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NLhOQ2DSmRgOMbti7xOeqJUk6PtB7nwJf" Archived-At: Subject: Re: [Json] Add Extension to JS MIME X-BeenThere: json@ietf.org 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: Mon, 14 Aug 2017 18:43:44 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NLhOQ2DSmRgOMbti7xOeqJUk6PtB7nwJf Content-Type: multipart/mixed; boundary="QvpqU3oCT9lqvNaW8QOAuXd0KfcqC9w19"; protected-headers="v1" From: "Matthew A. Miller" To: json@ietf.org Message-ID: <0dbcfa02-d9ce-caf9-bc76-9eccffffa688@outer-planes.net> Subject: Re: [Json] Add Extension to JS MIME References: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> In-Reply-To: --QvpqU3oCT9lqvNaW8QOAuXd0KfcqC9w19 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 17/08/14 12:00, Bradley Meck wrote: > Thanks, replies inline. >=20 >=20 >=20 > Hello Bradley, >=20 > I think the right approach here is create an internet-draft upating= RFC > 4329, adding .mjs as one of the extensions for "application/javascr= ipt". > =C2=A0That I-D would likely need to be [DISPATCH]ed, as there is no= existing > WG=C2=A0 I can see that covers this. >=20 >=20 > I have never made/updated an RFC. Is there a tutorial on how to do this= =2E > I don't know what I-D / [DISPATCH] means, it looks like a different WG?= > Do I send a new email to their mailing list? > =C2=A0 >=20 This will be a lot to unpack, and I'm absolutely sure will require follow up. You can ping me off-list and I will attempt to do so. I would start with Markdown, either < https://github.com/cabo/kramdown-rfc2629/ > or < https://github.com/miekg/mmark >. karmdown-rfc2629 has some decent examples, and mmark has a doc describing its syntax. There is an RFC that covers writing Internet-Drafts (from whence RFCs come), which applies disirregardless of the source format: < https://tools.ietf.org/html/rfc7322 > More can be found here: < https://www.ietf.org/id-info/guidelines.html > Regarding the terms I used: * I-D =3D=3D=3D> Internet Draft * DISPATCH =3D=3D> https://datatracker.ietf.org/wg/dispatch/about/ : A working group for determining where ART work ought to be done * ART =3D=3D> Applications in Real-Time : A grouping within the IETF (https://www.ietf.org/iesg/area.html) >=20 > For the document, at the very least it seems necessary to update th= e > ECMA-262 reference in addition to the updated IANA instructions.=C2= =A0 I'm > not sure much of anything does need to be said about differences be= tween > .mjs versus .js -- the content is still JavaScript, but hinting at > differences in module expectations. >=20 >=20 > TC39 / ECMA262 has said that they are not in the business of the MIME > in=C2=A0https://github.com/tc39/ecma262/issues/322 . So there won't be = any > need to change references to that standard. > =C2=A0 >=20 I understand that TC39 does not see this as their responsibility, and that's fine; this work is not asking anything of TC39 itself. I do strongly recommend pointing to an edition of ECMA-262 that describes EcmaScript/Javacript modules (e.g., Sixth -- or 2015 -- Edition). Or better yet, whatever Allen says (-: >=20 > The IANA considerations section itself, I don't know what the right= > wording is in this case.=C2=A0 I think almost everything stays the = same, > other than the file extension(s), and the published specification? >=20 >=20 > Yes, for the IANA, the only change is to add the file extension. > =C2=A0 > There could be a separate update since WHATWG treats text/javascript as= > the default as per > https://html.spec.whatwg.org/multipage/scripting.html#prepare-a-script = / > https://github.com/nodejs/node-eps/pull/61#issuecomment-321304962 . > However, I think that is a separate change. >=20 In my opinion, if we're already opening this can o' worms for one, we ought to consider all that are relevant. - m&m Matthew A. Miller --QvpqU3oCT9lqvNaW8QOAuXd0KfcqC9w19-- --NLhOQ2DSmRgOMbti7xOeqJUk6PtB7nwJf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJZke9ZAAoJEOz0ck4QngW7aTYH/13CeXS7+28sPMR2LKVpEYKg VMu+kloDl36rLd9cmg/c7qeG17pj1Z7pzSM3YynD8YBPOx9rgv/R1HOHpJKiBhWj CPs5aGO6mLeBLImYC6B13LLFy48rlEb+6HQhXlNn3SqxFEJvAezUr3aEBMCapQP9 ANrT7KO5wjc28S46uZaniOtdXhkijzg/eCtwi8/Q1y/qiAd+qxLHmsok1mXmQDjg bbmt1R4ZyGkTJr0pwMYDer+746MbrtXjp4RAD7mVDFIE7uPKDtOMExttqLRhNOyS VdiCoO+EwzRdc87qTM4itvpwvOZL0GZ8bflO22ghYkuyezjWYwVHF4AHjZ91jJo= =Vz/o -----END PGP SIGNATURE----- --NLhOQ2DSmRgOMbti7xOeqJUk6PtB7nwJf-- From nobody Mon Aug 14 18:28:43 2017 Return-Path: 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 F0ECC132476; Mon, 14 Aug 2017 18:28:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] 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 BDwtF31qKpCU; Mon, 14 Aug 2017 18:28:40 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 223C21321B6; Mon, 14 Aug 2017 18:28:40 -0700 (PDT) Received: from Svantevit.roach.at (cpe-70-122-154-80.tx.res.rr.com [70.122.154.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v7F1SaOV076086 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 14 Aug 2017 20:28:38 -0500 (CDT) (envelope-from adam@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-154-80.tx.res.rr.com [70.122.154.80] claimed to be Svantevit.roach.at To: Bradley Meck , "Matthew A. Miller" Cc: json@ietf.org, art-ads@ietf.org References: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> From: Adam Roach Message-ID: Date: Mon, 14 Aug 2017 20:28:36 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Json] Add Extension to JS MIME X-BeenThere: json@ietf.org 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: Tue, 15 Aug 2017 01:28:42 -0000 On 8/14/17 1:00 PM, Bradley Meck wrote: > I have never made/updated an RFC. Is there a tutorial on how to do > this. I don't know what I-D / [DISPATCH] means, it looks like a > different WG? Do I send a new email to their mailing list? For something as small as this, I'm not sure putting it through DISPATCH is quite the right path. There's no way we'd start a mini-WG for a document that simply performs IANA registration; there's no WG that this fits in; and the only other option is AD sponsorship. I'm happy to sponsor this document. In terms of what a document would look like, I think this is a pretty good example of the level of complexity we're looking at: https://tools.ietf.org/html/rfc5955 The first step is writing an internet-draft, and the easiest way to produce an internet-draft nowadays is using Carsten's kramdown tools: https://github.com/cabo/kramdown-rfc2629 Let me know if you need any other pointers in getting started. I've touched base with Matt Miller, and he should be available to provide assistance with format and content as well. /a From nobody Tue Aug 15 10:29:11 2017 Return-Path: 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 ED0721321CB; Tue, 15 Aug 2017 10:29:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.878 X-Spam-Level: X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] 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 2yRr6pr7zKy2; Tue, 15 Aug 2017 10:29:07 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 C8B68132143; Tue, 15 Aug 2017 10:29:07 -0700 (PDT) Received: from Svantevit.roach.at (cpe-70-122-154-80.tx.res.rr.com [70.122.154.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v7FHT5iF041686 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 15 Aug 2017 12:29:06 -0500 (CDT) (envelope-from adam@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-154-80.tx.res.rr.com [70.122.154.80] claimed to be Svantevit.roach.at From: Adam Roach To: Bradley Meck , "Matthew A. Miller" Cc: json@ietf.org, art-ads@ietf.org References: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> Message-ID: <5ef82202-d8d8-d8e7-3b81-b8d79d44c551@nostrum.com> Date: Tue, 15 Aug 2017 12:29:05 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------8A49EAFF324564D137B4B551" Content-Language: en-US Archived-At: Subject: Re: [Json] Add Extension to JS MIME X-BeenThere: json@ietf.org 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: Tue, 15 Aug 2017 17:29:10 -0000 This is a multi-part message in MIME format. --------------8A49EAFF324564D137B4B551 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 8/14/17 8:28 PM, Adam Roach wrote: > On 8/14/17 1:00 PM, Bradley Meck wrote: >> I have never made/updated an RFC. Is there a tutorial on how to do >> this. I don't know what I-D / [DISPATCH] means, it looks like a >> different WG? Do I send a new email to their mailing list? > > For something as small as this, I'm not sure putting it through > DISPATCH is quite the right path. There's no way we'd start a mini-WG > for a document that simply performs IANA registration; there's no WG > that this fits in; and the only other option is AD sponsorship. Thanks for tagging me on the draft-in-progress[1]. This looks like really good material; however, I'll note that its scope is somewhat broader than the original description led me to believe it would be. At the same time, Ben points out to me that DISPATCH actually does have a provision in its charter that allows it to adopt administrative documents, such as IANA registrations. Based on the slightly larger scope, I'd like input from the ART (Applications and Realtime) community at large on the issues that extend beyond the simple filename extension; and, in particular: 1. The question of whether modules need their own MIME type (e.g., application/javascript+module) or MIME type parameter (e.g., application/javascript;goal=module) 2. Formally changing the IANA status of text/javascript from "OBSOLETE" to "COMMON." So I think the right path forward, now that I understand the likely scope of the final document, would be: 1. Get the document in a shape you're happy with, and publish it as a -00 draft. (I believe Matt will be submitting a PR in the near future to help with some simple structural issues; wait for those.) 2. Send an email to the DISPATCH mailing list (https://www.ietf.org/mailman/listinfo/dispatch) with a pointer to the document, asking for the WG to consider adopting it under its "simple administrative documents" clause. Let me know if you have any questions or concerns. /a ____ [1] https://github.com/bmeck/I-D/tree/master/javascript-mjs --------------8A49EAFF324564D137B4B551 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
On 8/14/17 8:28 PM, Adam Roach wrote:
On 8/14/17 1:00 PM, Bradley Meck wrote:
I have never made/updated an RFC. Is there a tutorial on how to do this. I don't know what I-D / [DISPATCH] means, it looks like a different WG? Do I send a new email to their mailing list?

For something as small as this, I'm not sure putting it through DISPATCH is quite the right path. There's no way we'd start a mini-WG for a document that simply performs IANA registration; there's no WG that this fits in; and the only other option is AD sponsorship.

Thanks for tagging me on the draft-in-progress[1]. This looks like really good material; however, I'll note that its scope is somewhat broader than the original description led me to believe it would be. At the same time, Ben points out to me that DISPATCH actually does have a provision in its charter that allows it to adopt administrative documents, such as IANA registrations.

Based on the slightly larger scope, I'd like input from the ART (Applications and Realtime) community at large on the issues that extend beyond the simple filename extension; and, in particular:
  1. The question of whether modules need their own MIME type (e.g., application/javascript+module) or MIME type parameter (e.g., application/javascript;goal=module)

  2. Formally changing the IANA status of text/javascript from "OBSOLETE" to "COMMON."


So I think the right path forward, now that I understand the likely scope of the final document, would be:

  1. Get the document in a shape you're happy with, and publish it as a -00 draft. (I believe Matt will be submitting a PR in the near future to help with some simple structural issues; wait for those.)

  2. Send an email to the DISPATCH mailing list (https://www.ietf.org/mailman/listinfo/dispatch) with a pointer to the document, asking for the WG to consider adopting it under its "simple administrative documents" clause.


Let me know if you have any questions or concerns.

/a
____
[1] https://github.com/bmeck/I-D/tree/master/javascript-mjs
--------------8A49EAFF324564D137B4B551-- From nobody Tue Aug 15 13:00:50 2017 Return-Path: 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 6D06413232C for ; Tue, 15 Aug 2017 13:00:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: 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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.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 qVRzBXtwmbzT for ; Tue, 15 Aug 2017 13:00:45 -0700 (PDT) Received: from mail-yw0-x244.google.com (mail-yw0-x244.google.com [IPv6:2607:f8b0:4002:c05::244]) (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 4B50D1321EB for ; Tue, 15 Aug 2017 13:00:44 -0700 (PDT) Received: by mail-yw0-x244.google.com with SMTP id p68so1096019ywg.5 for ; Tue, 15 Aug 2017 13:00:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=t1s4wE14MqagP8ozb83cty5RlU6EjazTM0CH/J6YLzQ=; b=f/icuuiu3hnQs17oEmJ7zgUsYd+FWo0iV0Vp6bKYan4R+KvzQ59VTL78+rcYX23pF8 T5di9tv3thyVa7c0T6nz0LjhZOPhbAMbaqyr47DaStEq644ULCdBrcfk/cs61LSoBsIe nh2K9aZlNjZM1cwd04aDP/EQXg0pfp0tZSBtItmnoCPz7ehHYVvRMh4WK38a9IbuaLQo rvsfW3GW1QLxtEHoWXikw05o9GcClgGaXMNfYSLRaeXSBLXSeSmhdENi5+H/zQbxeMIH VVJIPvcRy7/km9b0pcZfGw3Gt8spQPeJ5CbEh2F5YEEpCMNWOCA8t3sOyABq/KiXaIyi K0PQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:subject:to:cc:references:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=t1s4wE14MqagP8ozb83cty5RlU6EjazTM0CH/J6YLzQ=; b=r60+ADEhkj+VVO5w9jHkcZBEZnTnbg+x/iKOiKOsybf8Oz/iAPeYmnifphnhiz9b/t xJ16bzqZR/kmRIN0QRRwjYQDUgVNBvrLLUN+1jGeTZX8DJ4eW1t/Ec9eR2Lv2n0JvcC3 2aexbIbmUzUu3XCRRXMoA6c3SbKDnljT/UOYchUOhrJx7aQawDi+dFoHH/iCOcUK3Dob OBkRGT7SU3VQXO/6cPSBUZm8KE643UsMYmM2HYJG2hkxofhepjgPXGKs4D30hZjDsK++ iM4nWvUZJaQHNBKEjpUiyOJZkPuGPmdTk2TK7sAjjobiplIJN/LF0CfBCQckbiXnDHzQ PZlQ== X-Gm-Message-State: AHYfb5jfAokRm8v08/Ivx7HM2CogYqpPNmyrHn/bTQ6x68HRY/5sOr7z YEGgBDqNDvT8tX4u X-Received: by 10.13.233.65 with SMTP id s62mr23566212ywe.226.1502827243395; Tue, 15 Aug 2017 13:00:43 -0700 (PDT) Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id a11sm3884085ywe.36.2017.08.15.13.00.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Aug 2017 13:00:42 -0700 (PDT) Sender: Matthew Miller From: "Matthew A. Miller" To: Adam Roach , Bradley Meck Cc: json@ietf.org, art-ads@ietf.org References: <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> <5ef82202-d8d8-d8e7-3b81-b8d79d44c551@nostrum.com> Message-ID: <8ffd0373-112c-9a2e-5e82-8542c1819065@outer-planes.net> Date: Tue, 15 Aug 2017 14:00:41 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Thunderbird/56.0 MIME-Version: 1.0 In-Reply-To: <5ef82202-d8d8-d8e7-3b81-b8d79d44c551@nostrum.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Json] Add Extension to JS MIME X-BeenThere: json@ietf.org 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: Tue, 15 Aug 2017 20:00:48 -0000 On 17/08/15 11:29, Adam Roach wrote: > On 8/14/17 8:28 PM, Adam Roach wrote: >> On 8/14/17 1:00 PM, Bradley Meck wrote: >>> I have never made/updated an RFC. Is there a tutorial on how to do >>> this. I don't know what I-D / [DISPATCH] means, it looks like a >>> different WG? Do I send a new email to their mailing list? >> >> For something as small as this, I'm not sure putting it through >> DISPATCH is quite the right path. There's no way we'd start a mini-WG >> for a document that simply performs IANA registration; there's no WG >> that this fits in; and the only other option is AD sponsorship. > > Thanks for tagging me on the draft-in-progress[1]. This looks like > really good material; however, I'll note that its scope is somewhat > broader than the original description led me to believe it would be. At > the same time, Ben points out to me that DISPATCH actually does have a > provision in its charter that allows it to adopt administrative > documents, such as IANA registrations. > > Based on the slightly larger scope, I'd like input from the ART > (Applications and Realtime) community at large on the issues that extend > beyond the simple filename extension; and, in particular: > > 1. The question of whether modules need their own MIME type (e.g., > application/javascript+module) or MIME type parameter (e.g., > application/javascript;goal=module) > > 2. Formally changing the IANA status of text/javascript from "OBSOLETE" > to "COMMON." > > > So I think the right path forward, now that I understand the likely > scope of the final document, would be: > > 1. Get the document in a shape you're happy with, and publish it as a > -00 draft. (I believe Matt will be submitting a PR in the near > future to help with some simple structural issues; wait for those.) > > 2. Send an email to the DISPATCH mailing list > (https://www.ietf.org/mailman/listinfo/dispatch) with a pointer to > the document, asking for the WG to consider adopting it under its > "simple administrative documents" clause. > > > Let me know if you have any questions or concerns. > I broke them into 2 PRs, both now merged: * [MERGED] #3 "fixup xrefs and expand abstract and intro" < https://github.com/bmeck/I-D/pull/3 > * [MERGED] #4 "fixing up formatting" < https://github.com/bmeck/I-D/pull/4 > I think -00 is good to go. There are some questions/concerns in the issues, but I don't believe any of them must be addressed before this initial publishing. - m&m Matthew A. Miller From nobody Tue Aug 15 20:02:07 2017 Return-Path: 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 56BA513248A for ; Tue, 15 Aug 2017 20:02:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.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 eyKjKW7kNEWN for ; Tue, 15 Aug 2017 20:02:03 -0700 (PDT) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (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 63ED3132483 for ; Tue, 15 Aug 2017 20:02:03 -0700 (PDT) Received: by mail-it0-x244.google.com with SMTP id s132so1748661ita.1 for ; Tue, 15 Aug 2017 20:02:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:from:subject:cc:references:to:message-id:date:user-agent :mime-version:in-reply-to; bh=6Vy8xuxT4DidwEhaxYlxGzR5k2aZuLfQ1T9qbx9zj+o=; b=izXZDoHbJDV5sNn1XgKjuj+Ls2JVYhj79Yvkmd8LCZpgfJ4mMgus2vP2kVVvQeW7PS EqZfDrzF3A7pJqEmSYX8Bi4+dwIgKLYGTeDJ29YVgeZzhCe1XDz1DEdnUxjlglgCYIJi TUThBR4yY3HMg9ho4AtXDIpu5jdta/JcUiJc2AUyPrgiYpps97ZviqhwaT4Pz+G6It/T WY+sb5kWBf/MkayQx/8IitA5bwj3EAnn0m1IBTuaWC7snLAHOX36s+uelWdYhwzT/Mev gAQo52kgcPl0kp9+HLiQW0ZMRwmSBw5pA1YGhfhf79kYRhoqW/H8EZxYZubvTtOUD/AZ NyNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:subject:cc:references:to:message-id :date:user-agent:mime-version:in-reply-to; bh=6Vy8xuxT4DidwEhaxYlxGzR5k2aZuLfQ1T9qbx9zj+o=; b=JMnNB+wd1Q1Et1y75Si1aV1/5am645/dLoSOSkq0iYbppNvndX+WdZfGBt+HHFxrMC CmWzrFj4t9p3BnKz3bT2fbUje2i/rPw4vZEa6rZATIEI90DCLTuMcZt/I2xGSEzr3t/4 TIWY4mjmd1bCrivFG6FukTAXRj/fjYh+3XTXvWGW0HqKFubgDwsWBBjK7jNL7nhemFc0 4UXlamyRz6pKwibuge7oiDd99e61t1LUqnpXHHgGJTcXyjF7p8mKef1e4yQWYeqrEUgA YTXLCuOQa5VB9VKhuxOfpbylWNBsIn1/c1s/hw7eU7WRbdh9czbOjA26MZrZrBEHXa1k eP2Q== X-Gm-Message-State: AHYfb5gSfqm6DklUN80NjFKBIor4ogM6nrGOFzXgVtbUJgqftN54GpDr 1zzUFk8erfaZVuLY X-Received: by 10.36.71.135 with SMTP id t129mr573042itb.141.1502852522728; Tue, 15 Aug 2017 20:02:02 -0700 (PDT) Received: from [192.168.29.239] (c-73-217-32-196.hsd1.co.comcast.net. [73.217.32.196]) by smtp.gmail.com with ESMTPSA id a45sm79300itj.14.2017.08.15.20.02.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Aug 2017 20:02:01 -0700 (PDT) Sender: Matthew Miller From: "Matthew A. Miller" Cc: Peter Saint-Andre - Filament , Paul Hoffman References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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> <5625f6c1-8f23-a0a9-63d8-059080299247@filament.com> To: json@ietf.org Message-ID: <48bc8b78-8e55-b5a1-a897-be06730e6e86@outer-planes.net> Date: Tue, 15 Aug 2017 21:01:58 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <5625f6c1-8f23-a0a9-63d8-059080299247@filament.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GeWAvoDXEHWNMGDeV72M3NKn6BNeNqGd7" Archived-At: 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Aug 2017 03:02:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GeWAvoDXEHWNMGDeV72M3NKn6BNeNqGd7 Content-Type: multipart/mixed; boundary="2Ov5tHQpP12vFpMnIRsBA1a3RdRsf0i6F"; protected-headers="v1" From: "Matthew A. Miller" To: json@ietf.org Cc: Peter Saint-Andre - Filament , Paul Hoffman Message-ID: <48bc8b78-8e55-b5a1-a897-be06730e6e86@outer-planes.net> Subject: Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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> <5625f6c1-8f23-a0a9-63d8-059080299247@filament.com> In-Reply-To: <5625f6c1-8f23-a0a9-63d8-059080299247@filament.com> --2Ov5tHQpP12vFpMnIRsBA1a3RdRsf0i6F Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Thanks you all. We can take Pete Cordell's suggestions, with the reference corrected from [UNICODE] to [RFC3629]: """ 8.1. Character Encoding JSON text exchanged between systems that are not part of a closed ecosystem MUST be encoded using UTF-8 [RFC3629]. 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. """ Unless there are strong objections, this is the text we'll submit to the editor. - m&m Matthew A. Miller On 17/08/14 10:56, Peter Saint-Andre - Filament wrote: > On 8/14/17 10:50 AM, Paul Hoffman wrote: >> 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 pre= tty >>>> simple and side-steps issues about what is a network protocol, paylo= ad, >>>> 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 encod= ing, >>>> 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 ignor= e >>>> 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. >=20 > What Pete suggested seems good enough. >=20 > Peter >=20 --2Ov5tHQpP12vFpMnIRsBA1a3RdRsf0i6F-- --GeWAvoDXEHWNMGDeV72M3NKn6BNeNqGd7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJZk7WnAAoJEOz0ck4QngW7JlkH/39memAE9Sp5CPHE0w9Gi6du m1hEE06Ki+zYK5uB2MszubF3efH1Z5bnuq7FF2q3Dwu95TbNupi9oFm9Nc4JWUSw uMGbob0TUPScGeHsbKdmavJjbdUkVzqqwXfdUQE5/YsbwT4DDGpg0xGFM7yxwpti 2szkyFXJHfVNbYU2iwGhUnfqLdoSamEytWSmfXr+/dwsVG2BF0b90rwFx/L6nROq Ipvm2RJHEcQHkuwqX+ErAKGNRZZdFSwBU9CpnkaZNObC27QtXDmj5z/sE2pfHvZe A/KwhUL55ebq/VMJMnKAu/qt28o1vDxwv85SNmMqK7fmowfU3+f85Mf0nH7GPS4= =vKyP -----END PGP SIGNATURE----- --GeWAvoDXEHWNMGDeV72M3NKn6BNeNqGd7-- From nobody Wed Aug 16 20:58:57 2017 Return-Path: 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 245821323B3 for ; Wed, 16 Aug 2017 20:58:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: 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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.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 vYt_vOjkONQs for ; Wed, 16 Aug 2017 20:58:54 -0700 (PDT) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 E05391241F5 for ; Wed, 16 Aug 2017 20:58:53 -0700 (PDT) Received: by mail-it0-x233.google.com with SMTP id 77so26228379itj.1 for ; Wed, 16 Aug 2017 20:58:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:to:cc:from:subject:message-id:date:user-agent:mime-version; bh=bV043U5c8/3jQ86sAGjHkmKL7SjYaoYpYt5PfqN6BsA=; b=OPP+oEZh1EPjVuMVNLenQxMXpPUE6gJr/64QrY/uVUQUPVr+1w8ya15122RyZR2GEC wjknSZSJaRPNME/abABwDHsywWOf+b/pTjNruOu9+elI6tfcJNHSsQLJLX7ytPRSJQR9 Qu2pA7j5KikOo+dFi4jPKRcI0AsixbxqJtx0Q5+0avLdAaudACz2d09orB2hhB8b87Jl MBKQT4Nv5uKEQmBJnMmsh+Wt/YCV4txY18PflbcrImhBkZlljEzu0VV3WcLvdGN5XySL r/Yb9Rbri05TsOHUR8EoqSqAs2PXkNXPCIm7a/8FpFU1BLxGspuuqtUX/MujnGipDsWC YMzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:to:cc:from:subject:message-id:date :user-agent:mime-version; bh=bV043U5c8/3jQ86sAGjHkmKL7SjYaoYpYt5PfqN6BsA=; b=t40wOoqo9xnVGTlwDuQTfwCbJ+0MQGhkJLGyAwBgWysZsMlRJPeX2BXJR0fa7xXJmt TOvGQfH6Kg98sialZot169YwWkbFSYWYu9wxRiKgyss/ODEs47GF/BELfhfjFCfeysBs seGiKL8yvKAcqcSKT0h1FLc5cmuDjhziGrXZW+vkCuJCRDu9M8mZpBxEmaospS6bjxjP VNWgMf0C0tLyB4v3ckiQqJaMB+9wkPJy8q09rQ9k7G1+XEnt134aKEMkibYX+2DS3okI eBEA6y1ZJrzV2HZJWyNtD0iyi4H5O67FCbCGnjOPVCsBFrODCXWpr6Y5kDrxap8ZBqjZ immQ== X-Gm-Message-State: AHYfb5iyw5MdkK8KSu6AXxUWHpRssWcuLk4zimB+haEs4VEZb6KFXpnp upGrYehx24p1jXM2 X-Received: by 10.36.178.76 with SMTP id h12mr610369iti.108.1502942333291; Wed, 16 Aug 2017 20:58:53 -0700 (PDT) Received: from [192.168.29.239] (c-73-217-32-196.hsd1.co.comcast.net. [73.217.32.196]) by smtp.gmail.com with ESMTPSA id b83sm1092760iod.35.2017.08.16.20.58.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Aug 2017 20:58:52 -0700 (PDT) Sender: Matthew Miller To: "json@ietf.org" Cc: Bradley Meck From: "Matthew A. Miller" Message-ID: <03333ba4-d073-7fad-ed34-b4ec5d2b1970@outer-planes.net> Date: Wed, 16 Aug 2017 21:58:51 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pwRNR5WCVJRl7CVGMrkTPQNqGBs2thWuM" Archived-At: Subject: [Json] ECMAScript Media Types Updates Work X-BeenThere: json@ietf.org 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: Thu, 17 Aug 2017 03:58:56 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --pwRNR5WCVJRl7CVGMrkTPQNqGBs2thWuM Content-Type: multipart/mixed; boundary="d0i5PAWn4xrfkbgqDAJxRjFwhS1CBxgqI"; protected-headers="v1" From: "Matthew A. Miller" To: "json@ietf.org" Cc: Bradley Meck Message-ID: <03333ba4-d073-7fad-ed34-b4ec5d2b1970@outer-planes.net> Subject: ECMAScript Media Types Updates Work --d0i5PAWn4xrfkbgqDAJxRjFwhS1CBxgqI Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hello JSON, We've started on a document to update the ECMAScript/JavaScript media types < https://datatracker.ietf.org/doc/draft-bfarias-javascript-mjs >. Issues can be filed on the GitHub repo at < https://github.com/bmeck/I-D/issues >. I ask we continue discussion here for now. Thanks, --=20 - m&m Matthew A. Miller --d0i5PAWn4xrfkbgqDAJxRjFwhS1CBxgqI-- --pwRNR5WCVJRl7CVGMrkTPQNqGBs2thWuM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJZlRR7AAoJEOz0ck4QngW7ijoIAJ8mfVzkDLcXQP/i9pfucvtS Tsem2jylc/Aw2SihIVWGKFG6rQA6jET4smdVa3UTDxC0BjH+3eSHbZr2wwKPko3k 7Fu8fbu09ot4WkQknl+KCtxxONKCdW4Pl8FCVl/py0VE37DY8m+Sq+PW9zKjgt+E ILSS6OTwfOadPji9nHvRZxEdsocyye4R7OkhqlobhxKX8/z/WY+Mdk2BgFY3tEKi wRm7YGFd7Rz5vkXFkifA4T8l40yFy4ae5+KtIShWbYYr0EFOHUXb+/VEWJhg++zT am6zXIXIUYmGlPRiTve0EjWkmJAQdbYSzX0rZyQKpIsIIbBJb3fiBDwBZnkf3g0= =F6/l -----END PGP SIGNATURE----- --pwRNR5WCVJRl7CVGMrkTPQNqGBs2thWuM-- From nobody Wed Aug 23 04:09:34 2017 Return-Path: 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 5F8C4132355 for ; Wed, 23 Aug 2017 04:09:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.918 X-Spam-Level: X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 e3AKeN7YG_tF for ; Wed, 23 Aug 2017 04:09:30 -0700 (PDT) Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4597C1320CF for ; Wed, 23 Aug 2017 04:09:29 -0700 (PDT) Received: (qmail 17373 invoked from network); 23 Aug 2017 12:00:55 +0100 Received: from host159-180-98-181.range159-180.btcentralplus.com (HELO ?192.168.1.72?) (159.180.98.181) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 23 Aug 2017 12:00:55 +0100 To: "Matthew A. Miller" , json@ietf.org Cc: Peter Saint-Andre - Filament References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <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> <5625f6c1-8f23-a0a9-63d8-059080299247@filament.com> <48bc8b78-8e55-b5a1-a897-be06730e6e86@outer-planes.net> From: Pete Cordell Message-ID: <7d1355f6-80b3-c5ff-2e2a-9c09943db0b7@codalogic.com> Date: Wed, 23 Aug 2017 12:09:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <48bc8b78-8e55-b5a1-a897-be06730e6e86@outer-planes.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Archived-At: 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2017 11:09:33 -0000 Thanks Matt and all for your patience on this issue and going the extra mile (or 2 or 3). Hopefully it'll save some confusion for readers in the future. Cheers, Pete. On 16/08/2017 04:01, Matthew A. Miller wrote: > Thanks you all. We can take Pete Cordell's suggestions, with the > reference corrected from [UNICODE] to [RFC3629]: > > > """ > 8.1. Character Encoding > > JSON text exchanged between systems that are not part of a closed > ecosystem MUST be encoded using UTF-8 [RFC3629]. > > 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. > """ > > Unless there are strong objections, this is the text we'll submit to the > editor. > > > - m&m > > Matthew A. Miller > > On 17/08/14 10:56, Peter Saint-Andre - Filament wrote: >> On 8/14/17 10:50 AM, Paul Hoffman wrote: >>> 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. >> >> What Pete suggested seems good enough. >> >> Peter >> > > > > > _______________________________________________ > json mailing list > json@ietf.org > https://www.ietf.org/mailman/listinfo/json >