Re: [Json] Add Extension to JS MIME

"Matthew A. Miller" <> Mon, 14 August 2017 18:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D4F761323B5 for <>; Mon, 14 Aug 2017 11:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.601
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FbZf3nre0u-k for <>; Mon, 14 Aug 2017 11:43:41 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4002:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C4C301323C4 for <>; Mon, 14 Aug 2017 11:43:41 -0700 (PDT)
Received: by 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;; 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;; 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 with SMTP id c126mr21718676ywd.13.1502736220678; Mon, 14 Aug 2017 11:43:40 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id f127sm2942402ywc.0.2017. 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 <>
References: <> <> <>
From: "Matthew A. Miller" <>
Message-ID: <>
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-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

On 17/08/14 12:00, Bradley Meck wrote:
> 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?

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 < > or < >.  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: < >

More can be found here: < >

Regarding the terms I used:
* I-D ===> Internet Draft
* DISPATCH ==> : A
working group for determining where ART work ought to be done
* ART ==> Applications in Real-Time : A grouping within the IETF

>     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 . So there won't be any
> need to change references to that standard.

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 (-:

>     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
> /
> .
> However, I think that is a separate change.

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