Re: [Json] Add Extension to JS MIME

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