attachment
<div dir="ltr"><div>FYI - Update to Java script media types <br></div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <span dir="auto"><<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>></span><br>Date: Fri, May 6, 2022 at 3:29 PM<br>Subject: [dispatch] RFC 9239 on Updates to ECMAScript Media Types<br>To: <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>>, <<a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a>><br>Cc: <<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>>, <<a href="mailto:drafts-update-ref@iana.org">drafts-update-ref@iana.org</a>>, <<a href="mailto:dispatch@ietf.org">dispatch@ietf.org</a>><br></div><br><br>A new Request for Comments is now available in online RFC libraries.<br>
<br>
<br>
RFC 9239<br>
<br>
Title: Updates to ECMAScript Media Types <br>
Author: M. Miller,<br>
M. Borins,<br>
M. Bynens,<br>
B. Farias<br>
Status: Informational<br>
Stream: IETF<br>
Date: May 2022<br>
Mailbox: <a href="mailto:linuxwolf%2Bietf@outer-planes.net" target="_blank">linuxwolf+ietf@outer-planes.net</a>,<br>
<a href="mailto:mylesborins@github.com" target="_blank">mylesborins@github.com</a>,<br>
<a href="mailto:mths@google.com" target="_blank">mths@google.com</a>,<br>
<a href="mailto:bradley.meck@gmail.com" target="_blank">bradley.meck@gmail.com</a><br>
Pages: 13<br>
Obsoletes: RFC 4329<br>
<br>
I-D Tag: draft-ietf-dispatch-javascript-mjs-17.txt<br>
<br>
URL: <a href="https://www.rfc-editor.org/info/rfc9239" rel="noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc9239</a><br>
<br>
DOI: 10.17487/RFC9239<br>
<br>
This document describes the registration of media types for the<br>
ECMAScript and JavaScript programming languages and conformance<br>
requirements for implementations of these types. This document<br>
obsoletes RFC 4329 ("Scripting Media Types)", replacing the previous<br>
registrations with information and requirements aligned with common<br>
usage and implementation experiences.<br>
<br>
This document is a product of the Dispatch Working Group of the IETF.<br>
<br>
<br>
INFORMATIONAL: This memo provides information for the Internet community.<br>
It does not specify an Internet standard of any kind. Distribution of<br>
this memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer" target="_blank">https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="https://www.rfc-editor.org/search" rel="noreferrer" target="_blank">https://www.rfc-editor.org/search</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/retrieve/bulk" rel="noreferrer" target="_blank">https://www.rfc-editor.org/retrieve/bulk</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org" target="_blank">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
<br>
<br>
_______________________________________________<br>
dispatch mailing list<br>
<a href="mailto:dispatch@ietf.org" target="_blank">dispatch@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/dispatch" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/dispatch</a><br>
</div></div></div>