Re: [Json] Add Extension to JS MIME

"Matthew A. Miller" <> Tue, 15 August 2017 20:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6D06413232C for <>; Tue, 15 Aug 2017 13:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qVRzBXtwmbzT for <>; Tue, 15 Aug 2017 13:00:45 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4002:c05::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4B50D1321EB for <>; Tue, 15 Aug 2017 13:00:44 -0700 (PDT)
Received: by 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;; 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;; 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 with SMTP id s62mr23566212ywe.226.1502827243395; Tue, 15 Aug 2017 13:00:43 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id a11sm3884085ywe.36.2017. (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 <>
References: <> <> <> <> <>
Message-ID: <>
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: <>
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-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
>     ( 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" < >
* [MERGED] #4 "fixing up formatting" < >

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