Re: [Json] Add Extension to JS MIME

"Matthew A. Miller" <> Mon, 14 August 2017 17:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 38E7B1323B9 for <>; Mon, 14 Aug 2017 10:37:00 -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 zmz897uaqx8z for <>; Mon, 14 Aug 2017 10:36:58 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7A7D91323B5 for <>; Mon, 14 Aug 2017 10:36:58 -0700 (PDT)
Received: by 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;; 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;; 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 with SMTP id w9mr20175451ywl.77.1502732217658; Mon, 14 Aug 2017 10:36:57 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id u186sm2910958ywd.73.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Aug 2017 10:36:56 -0700 (PDT)
References: <>
From: "Matthew A. Miller" <>
Message-ID: <>
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-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

On 17/08/09 07:34, Bradley Meck wrote:
> 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
> <> .
> 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.

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
.mjs 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
< >

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