Re: [Json] Add Extension to JS MIME

Bradley Meck <> Mon, 14 August 2017 18:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C769E1323C8; Mon, 14 Aug 2017 11:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WKLSOIkTgrLa; Mon, 14 Aug 2017 11:00:30 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5CC8B1323C4; Mon, 14 Aug 2017 11:00:30 -0700 (PDT)
Received: by with SMTP id o9so41246658iod.1; Mon, 14 Aug 2017 11:00:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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;; 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 with SMTP id b75mr14714073ioj.4.1502733629522; Mon, 14 Aug 2017 11:00:29 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 14 Aug 2017 11:00:09 -0700 (PDT)
In-Reply-To: <>
References: <> <>
From: Bradley Meck <>
Date: Mon, 14 Aug 2017 13:00:09 -0500
Message-ID: <>
To: "Matthew A. Miller" <>
Content-Type: multipart/alternative; boundary="001a113f26fc2e06eb0556ba7008"
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:00:33 -0000

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

> - m&m
> Matthew A. Miller
> < >
> PS: Thanks to Adam Roach for confirming my thoughts, and suggesting some
> places to look at.
> _______________________________________________
> json mailing list