<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.5.8 --><!DOCTYPE rfcSYSTEM "rfc2629.dtd"[ <!ENTITYRFC2045 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2045.xml"> <!ENTITY RFC2119 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"> <!ENTITY RFC2397 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2397.xml"> <!ENTITY RFC2978 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2978.xml"> <!ENTITY RFC3552 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3552.xml"> <!ENTITY RFC3629 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3629.xml"> <!ENTITY RFC4288 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4288.xml">nbsp " "> <!ENTITYRFC4329 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4329.xml">zwsp "​"> <!ENTITYRFC6365 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6365.xml">nbhy "‑"> <!ENTITYRFC6648 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6648.xml"> <!ENTITY RFC6838 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6838.xml"> <!ENTITY RFC8174 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"> <!ENTITY RFC3236 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3236.xml"> <!ENTITY RFC3875 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3875.xml"> <!ENTITY RFC3986 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"> <!ENTITY RFC3987 SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3987.xml">wj "⁠"> ]><?rfc toc="yes"?> <?rfc tocindent="yes"?> <?rfc sortrefs="yes"?> <?rfc symrefs="yes"?> <?rfc strict="yes"?> <?rfc compact="yes"?> <?rfc comments="yes"?> <?rfc inline="yes"?><rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-dispatch-javascript-mjs-17" number="9239" submissionType="IETF" category="info"obsoletes="4329">consensus="true" obsoletes="4329" updates="" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3"> <!-- xml2rfc v2v3 conversion 3.12.2 --> <front><title>ECMAScript<title>Updates to ECMAScript MediaTypes Updates</title>Types</title> <seriesInfo name="RFC" value="9239"/> <author initials="M." surname="Miller" fullname="Matthew A. Miller"><organization></organization><organization/> <address> <email>linuxwolf+ietf@outer-planes.net</email> </address> </author> <author initials="M." surname="Borins" fullname="Myles Borins"> <organization>GitHub</organization> <address> <email>mylesborins@github.com</email> </address> </author> <author initials="M." surname="Bynens" fullname="Mathias Bynens"> <organization>Google</organization> <address> <email>mths@google.com</email> </address> </author> <author initials="B." surname="Farias" fullname="Bradley Farias"><organization></organization><organization/> <address> <email>bradley.meck@gmail.com</email> </address> </author> <date year="2022"month="March" day="02"/>month="May"/> <area>ART</area> <workgroup>DISPATCH</workgroup><keyword>Internet-Draft</keyword><keyword>JavaScript</keyword> <keyword>ECMAScript</keyword> <keyword>MIME type</keyword> <keyword>Content-Type</keyword> <keyword>modules</keyword> <keyword>TC39</keyword> <keyword>ESM</keyword> <abstract> <t>This document describes the registration of media types for the ECMAScript and JavaScript programming languages and conformance requirements for implementations of these types. This document obsoletesRFC4329, "ScriptingRFC 4329 ("Scripting MediaTypes",Types)", replacing the previous registrationsfor "text/javascript" and "application/javascript"with information and requirements aligned with common usage and implementation experiences.</t> </abstract> <note title="IESG Note"> <t>This document records the relationship between the work of Ecma International's Technical Committee 39 and the media types used to identify relevant payloads.</t> <t>That relationship was developed outside of the IETF and as a result is unfortunately not aligned with the best practices of BCP 13. Consequently, consensus exists in the IETF to document the relationship and update the relevant IANA registrations for those media types, but this is not an IETF endorsement of the media types chosen for this work.</t> </note> </front> <middle> <sectionanchor="introduction"><name>Introduction</name>anchor="introduction" numbered="true" toc="default"> <name>Introduction</name> <t>This memo describes media types for the JavaScript and ECMAScript programming languages. Refer to the sections "Introduction" and "Overview" in <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> for background information on these languages. This document updates the descriptions and registrations for these media types to reflect existing usage on the Internet, and it provides up-to-date security considerations.</t> <t>This document replaces the mediatypestype registrations in <xreftarget="RFC4329"/>,target="RFC4329" format="default"/> and updates the requirements for implementations using those media types defined in <xreftarget="RFC4329"/>target="RFC4329" format="default"/> based on current existing practices. As a consequence, this document obsoletes <xreftarget="RFC4329"/>.</t>target="RFC4329" format="default"/>.</t> <sectionanchor="terminology"><name>Terminology</name>anchor="terminology" numbered="true" toc="default"> <name>Terminology</name> <t>The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t> </section> </section> <sectionanchor="compatibility"><name>Compatibility</name>anchor="compatibility" numbered="true" toc="default"> <name>Compatibility</name> <t>This document defines equivalent processing requirements for thetypes text/javascript, text/ecmascript, and application/javascript.various script media types. The most widely supported media type in use is text/javascript; all others are considered historical and obsolete aliases of text/javascript.</t> <t>The types defined in this document are applicable to scripts written in <xreftarget="ECMA-262"/>.target="ECMA-262" format="default"/>. New editions of <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> are subjected to strong obligations of backward compatibility, imposed by the standardization process of Ecma International's Technical Committee 39 (TC39). As a result, JavaScript code based on an earlier edition is generally compatible with a JavaScript engine adhering to a later edition. The few exceptions to this are documented in <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> in the section "Additions and Changes That Introduce Incompatibilities with Prior Editions". JavaScript developers commonly use feature detection to ensure that modern JavaScript features are only used when available in the current environment. Later editions of <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> are not directly addressed in this document, although it is expected that implementations will behave as if applicability were extended to them. This document does not address other extensions to <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> or scripts written in other languages.</t> <t>This document may be updated to take other content into account. Updates of this document may introduce new optional parameters; implementations must consider the impact of such an update.</t> <t>This document does not define how fragment identifiers in resource identifiers(<xref target="RFC3986"/>,<xreftarget="RFC3987"/>)target="RFC3986" format="default"/> <xref target="RFC3987" format="default"/> for documents labeled with one of the media types defined in this document are resolved. An update of this document may define processing of fragment identifiers.</t> <t>Note that this use of the "text" media type tree willfully does not align with its original intent per <xreftarget="RFC2045"/>.target="RFC2045" format="default"/>. The reason for this is historical. <xreftarget="RFC4329"/>target="RFC4329" format="default"/> registered both the text/* and application/* types, marking the text/*onestypes obsolete. This was done to encourage people toward application/*, matching the guidance in <xreftarget="RFC4288"/>,target="RFC4288" format="default"/>, the predecessor to <xreftarget="RFC6838"/>.target="RFC6838" format="default"/>. Since then, however, the industry widely adopted text/* anyway. The definitions in this document reflect the current state of implementation across the JavaScript ecosystem, in web browsers and other environments such as Node.js alike, in order to guaranteebackwardsbackward compatibility with existing applications as much as possible. Future registrations should not view this as a repeatable precedent.</t> </section> <sectionanchor="modules"><name>Modules</name>anchor="modules" numbered="true" toc="default"> <name>Modules</name> <t>In order to formalize support for modular programs, <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> (starting with the 6th Edition) defines two top-level goal symbols (or roots to the abstract syntax tree) for the ECMAScript grammar: Module and Script. The Script goal represents the original structure where the code executes in the global scope, while the Module goal represents the module system built into ECMAScript starting with the 6th Edition. See the section "ECMAScript Language: Scripts and Modules"ofin <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> for details.</t> <t>This separation means that (in the absence of additional information) there are two possible interpretations for any given ECMAScript source text.</t> <t>Ecma International's Technical Committee 39 (TC39), the standards body in charge of ECMAScript, has determined that media types are outside of their scope of work <xreftarget="TC39-MIME-ISSUE"/>.</t>target="TC39-MIME-ISSUE" format="default"/>.</t> <t>It is not possible to fully determine if a source text of ECMAScript is meant to be parsed using the Module or Script grammar goals based upon content or media type alone. Therefore, as permitted by the media types in this document, scripting environments use out-of-band information in order to determine what goal should be used. Some scripting environments have chosen to adopt the file extension of .mjs for this purpose.</t> </section> <sectionanchor="encoding"><name>Encoding</name>anchor="encoding" numbered="true" toc="default"> <name>Encoding</name> <t>Refer to <xreftarget="RFC6365"/>target="RFC6365" format="default"/> for a discussion of terminology used in this section. Source text (as defined in<xref target="ECMA-262"/>,the section "SourceText")Text" in <xref target="ECMA-262" format="default"/>) can be binary source text. Binary source text is a textual data object that represents source text encoded using a character encoding scheme. A textual data object is a whole text protocol message or a whole text document, or a part of it, that is treated separately for purposes of external storage and retrieval. An implementation's internal representation of source text is not considered binary source text.</t> <t>Implementations need to determine a character encoding scheme in order to decode binary source text to source text. The media types defined in this document allow an optional charset parameter to explicitly specify the character encoding scheme used to encode the source text.</t> <t>In order to ensure interoperability and align with widespread implementation practices, the charset parameter is optional rather than required, despite the recommendation inBCP 13<xreftarget="RFC6838"/>target="RFC6838" format="default">BCP 13</xref> for text/* types.</t> <t>How implementations determine the character encoding scheme can be subject to processing rules that are out of the scope of this document. For example, transport protocols can require that a specific character encoding scheme is to be assumed if the optional charset parameter is not specified, or they can require that the charset parameter is used in certain cases. Such requirements are not defined by this document.</t> <t>Implementations that support binary source textMUST<bcp14>MUST</bcp14> support binary source text encoded using the UTF-8 <xreftarget="RFC3629"/>target="RFC3629" format="default"/> character encoding scheme. Module goal sourcesMUST<bcp14>MUST</bcp14> be encoded as UTF-8; all other encodings will fail. Source goal sourcesSHOULD<bcp14>SHOULD</bcp14> be encoded as UTF-8; other character encoding schemesMAY<bcp14>MAY</bcp14> besupported,supported but are discouraged. Whether U+FEFF is processed as a Byte Order Mark (BOM) signature or not depends on the hostenvironment,environment and is not defined by this document.</t> <sectionanchor="charset-parameter"><name>Charsetanchor="charset-parameter" numbered="true" toc="default"> <name>Charset Parameter</name> <t>The charset parameter provides a means to specify the character encoding scheme of binary source text. If present, the value of the charset parameterMUST<bcp14>MUST</bcp14> be a registered charset <xreftarget="CHARSETS"/>,target="CHARSETS" format="default"/> and is considered valid if it matches the mime-charset production defined in <xreftarget="RFC2978"/>, section 2.3.</t>target="RFC2978" sectionFormat="of" section="2.3"/>.</t> <t>The charset parameter is only used when processing a Script goal source; Module goal sourcesMUST<bcp14>MUST</bcp14> always be processed as UTF-8.</t> </section> <sectionanchor="character-encoding-scheme-detection"><name>Characteranchor="character-encoding-scheme-detection" numbered="true" toc="default"> <name>Character Encoding Scheme Detection</name> <t>It is possible that implementations cannot interoperably determine a single character encoding scheme simply by complying with all requirements of the applicable specifications. To foster interoperability in such cases, the following algorithm is defined. Implementations apply this algorithm until a single character encoding scheme is determined.</t><t><list style="numbers"><ol spacing="normal" type="1"><li> <t>If the binary source text is not already determined to be using a Module goal and starts with a Unicode encoding form signature, the signature determines the encoding. The following octet sequences, at the very beginning of the binary source text, are considered with their corresponding character encoding schemes:<vspace blankLines='1'/> <figure><artwork><![CDATA[ +------------------+----------+ | Leading sequence | Encoding | |------------------+----------| | EF</t> <table align="left" anchor="tab"> <name></name> <thead> <tr> <th>Leading sequence</th> <th>Encoding</th> </tr> </thead> <tbody> <tr> <td>EF BBBF | UTF-8 | | FF FE | UTF-16LE | | FE FF | UTF-16BE | +------------------+----------+ ]]></artwork></figure> <vspace blankLines='1'/>BF</td> <td>UTF-8</td> </tr> <tr> <td>FF FE</td> <td>UTF-16LE</td> </tr> <tr> <td>FE FF</td> <td>UTF-16BE</td> </tr> </tbody> </table> <t> Implementations of this stepMUST<bcp14>MUST</bcp14> use these octet sequences to determine the character encoding scheme, even if the determined scheme is not supported. If this step determines the character encoding scheme, the octet sequence representing the Unicode encoding form signatureMUST<bcp14>MUST</bcp14> be ignored when decoding the binary source text.</t><t>Else,</li> <li>Else, if a charset parameter is specified and its value is valid and supported by the implementation, the value determines the character encodingscheme.</t> <t>Else,scheme.</li> <li>Else, the character encoding scheme is assumed to beUTF-8.</t> </list></t>UTF-8.</li> </ol> <t>If the character encoding scheme is determined to be UTF-8 through any means other than step 1 as defined above and the binary source text starts with the octet sequence EF BB BF, the octet sequence is ignored when decoding the binary source text.</t> </section> <sectionanchor="character-encoding-scheme-error-handling"><name>Characteranchor="character-encoding-scheme-error-handling" numbered="true" toc="default"> <name>Character Encoding Scheme Error Handling</name> <t>Binary source text that is not properly encoded for the determined character encoding can pose a security risk, as discussed insection 5.<xref target="security-considerations"/>. That said, because of the varied and complex environments scripts are executed in, most of the error handling specifics are left to the processors. The following are broad guidelines that processors follow.</t> <t>If binary source text is determined to have been encoded using a certain character encoding scheme that the implementation is unable to process, implementations can consider the resource unsupported (i.e., do not decode the binary source text using a different character encoding scheme).</t> <t>Binary source text can be determined to have been encoded using a certain character encoding scheme but contain octet sequences that are not valid according to that scheme. Implementations can substitute those invalid sequences with the replacement character U+FFFD (properly encoded for thescheme),scheme) or stop processing altogether.</t> </section> </section> <sectionanchor="security-considerations"><name>Securityanchor="security-considerations" numbered="true" toc="default"> <name>Security Considerations</name> <t>Refer to <xreftarget="RFC3552"/>target="RFC3552" format="default"/> for a discussion of terminology used in this section. Examples in this section and discussions of interactions of host environments with scripts, modules, and extensions to <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> are to be understood as non-exhaustive and of a purely illustrative nature.</t> <t>The programming language defined in <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> is not intended to be computationallyself-sufficient,self-sufficient; rather, it is expected that the computational environment provides facilities to programs to enable specific functionality. Such facilities constitute unknown factors and are thus not defined by this document.</t> <t>Derived programming languages are permitted to include additional functionality that is not described in <xreftarget="ECMA-262"/>;target="ECMA-262" format="default"/>; such functionality constitutes an unknown factor and is thus not defined by this document. In particular, extensions to <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> defined for the JavaScript programming language are not discussed in this document.</t> <t>Uncontrolled execution of scripts can be exceedingly dangerous. Implementations that execute scriptsMUST<bcp14>MUST</bcp14> give consideration to their application's threat models and those of the individual features they implement; in particular, theyMUST<bcp14>MUST</bcp14> ensure that untrusted content is not executed in an unprotected environment.</t> <t>Module scripts in ECMAScript can request the fetching and processing of additionalscripts,scripts; this is calledimporting."importing". Implementations that support modules need to process imported sources in the same way as scripts. See the section "ECMAScript Language: Scripts and Modules" in <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> for details. Further, there may be additional privacy and securityconcernsconcerns, depending on the location(s) the original script and its imported modules are obtained from. For instance, a script obtained from "host-a.example" could request to import a script from "host-b.example", which could expose information about the executing environment (e.g., IP address) to "host-b.example".</t> <t>Specifications for host environment facilities and for derived programming languages should include security considerations. If an implementation supports such facilities, the respective security considerations apply. In particular, if scripts can be referenced from or included in specific document formats, the considerations for the embedding or referencing document format apply.</t> <t>For example, scripts embedded in application/xhtml+xml <xreftarget="RFC3236"/>target="RFC3236" format="default"/> documents could be enabled through the host environment to manipulate the document instance, which could cause the retrieval of remote resources; security considerations regarding retrieval of remote resources of the embedding document would apply in this case.</t> <t>This circumstance can further be used to makeinformation,information that is normally only available to thescript,script also available to a web server by encoding the information in the resource identifier of the resource, which can further enable eavesdropping attacks. Implementation of such facilities is subject to the security considerations of the host environment, as discussed above.</t> <t>The programming language defined in <xreftarget="ECMA-262"/>target="ECMA-262" format="default"/> does include facilities to loop, cause computationally complex operations, or consume large amounts of memory; this includes, but is not limited to, facilities that allow dynamically generated source text to be executed (e.g., the eval() function); uncontrolled execution of such features can cause denial of service, which implementationsMUST<bcp14>MUST</bcp14> protect against.</t> <t>With the addition of SharedArrayBuffer objects in ECMAScript version 8, it could be possible to implement a high-resolutiontimertimer, which could lead to certain types of timing and side-channel attacks (e.g., <xreftarget="SPECTRE"/>).target="SPECTRE" format="default"/>). Implementations can take steps to mitigate this concern, such as disabling or removing support for SharedArrayBuffer objects, or can take additional steps to ensureaccess tothat this shared memory is only accessible between execution contexts that have some form of mutual trust.</t> <t>A host environment can provide facilities to access external input. Scripts that pass such input to the eval() function or similar language features can be vulnerable to code injection attacks. Scripts are expected to protect against such attacks.</t> <t>A host environment can provide facilities to output computed results in a user-visible manner. For example, host environments supporting a graphical user interface can provide facilities that enable scripts to present certain messages to the user. ImplementationsMUST<bcp14>MUST</bcp14> take steps to avoid confusion of the origin of such messages. In general, the security considerations for the host environment apply in such a case as discussed above.</t> <t>Implementations are required to support the UTF-8 character encoding scheme; the security considerations of <xreftarget="RFC3629"/>target="RFC3629" format="default"/> apply. Additional character encoding schemes may be supported; support for such schemes is subject to the security considerations of those schemes.</t> <t>Source text is expected to be in Unicode Normalization Form C. Scripts and implementationsMUST<bcp14>MUST</bcp14> consider security implications of unnormalized source text and data. For a detailed discussion of suchimplicationsimplications, refer to the security considerations in <xreftarget="RFC3629"/>.</t>target="RFC3629" format="default"/>.</t> <t>Scripts can be executed in an environment that is vulnerable to code injection attacks. For example, aCGICommon Gateway Interface (CGI) script <xreftarget="RFC3875"/>target="RFC3875" format="default"/> echoing user input could allow the inclusion of untrusted scripts that could be executed in an otherwise trusted environment. This threat scenario is subject to security considerations that are out of the scope of this document.</t> <t>The "data" resource identifier scheme <xreftarget="RFC2397"/>,target="RFC2397" format="default"/>, in combination with the types defined in this document, could be used to cause execution of untrusted scripts through the inclusion of untrusted resource identifiers in otherwise trusted content. Security considerations of <xreftarget="RFC2397"/>target="RFC2397" format="default"/> apply.</t> <t>Implementations can fail to implement a specific security model or other means to prevent possibly dangerous operations. Such failure could possibly be exploited to gain unauthorized access to a system or sensitive information; such failure constitutes an unknown factor and is thus not defined by this document.</t> </section> <sectionanchor="iana-considerations"><name>IANAanchor="iana-considerations" numbered="true" toc="default"> <name>IANA Considerations</name> <t>The media type registrations herein are divided into two major categories:the(1) the sole media type"text/javascript""text/javascript", which is now in commonusage,usage andall(2) all of the media types that areobsolete.</t>obsolete (i.e., "application/ecmascript", "application/javascript", "application/x-ecmascript", "application/x-javascript", "text/ecmascript", "text/javascript1.0", "text/javascript1.1", "text/javascript1.2", "text/javascript1.3", "text/javascript1.4", "text/javascript1.5", "text/jscript", "text/livescript", and "text/x-ecmascript").</t> <t>For both categories, the "Published specification" entry for the media typesareis updated to reference <xreftarget="ECMA-262"/>.target="ECMA-262" format="default"/>. In addition, a new file extension of .mjsishas been added to the list of file extensions with the restriction that contents should be parsed using the Module goal. Finally, the <xreftarget="HTML"/>target="HTML" format="default"/> specification uses "text/javascript" as the default media type of ECMAScript when preparing script tags; therefore, "text/javascript" intended usageis to behas been moved from OBSOLETE to COMMON.</t> <t>These changesare to behave been reflected in the IANAMedia Types"Media Types" registry in accordance with <xreftarget="RFC6838"/>.target="RFC6838" format="default"/>. All registrations will point to this document as the reference. The outdated note stating that the "text/javascript" media type has been "OBSOLETED in favor of application/javascript"is to behas been removed. The outdated note stating that the "text/ecmascript" media type has been "OBSOLETED in favor of application/ecmascript"is to behas been removed. IANAis requested to addhas added the note "OBSOLETED in favor of text/javascript" to all registrations except"text/javascript".</t>"text/javascript"; that is, this note has been added to the "text/ecmascript", "application/javascript", and "application/ecmascript" registrations.</t> <t>Four of the legacy media types in this document have a subtype starting with the "x-" prefix:</t><t><list style="symbols"> <t>application/x-ecmascript</t> <t>application/x-javascript</t> <t>text/x-ecmascript</t> <t>text/x-javascript</t> </list></t><ul spacing="normal"> <li>application/x-ecmascript</li> <li>application/x-javascript</li> <li>text/x-ecmascript</li> <li>text/x-javascript</li> </ul> <t>Note that these are grandfathered media types registered as perAppendix A of<xreftarget="RFC6838"/>.target="RFC6838" sectionFormat="of" section="A"/>. These registrations predateBCP 178<xreftarget="RFC6648"/>,target="RFC6648" format="default">BCP 178</xref>, which they violate, and are only included in this document forbackwardsbackward compatibility.</t> <sectionanchor="common-javascript-media-types"><name>Commonanchor="common-javascript-media-types" numbered="true" toc="default"> <name>Common JavaScript Media Types</name> <sectionanchor="textjavascript"><name>text/javascript</name> <dl>anchor="textjavascript" numbered="true" toc="default"> <name>text/javascript</name> <dl newline="false" spacing ="normal"> <dt> Type name: </dt> <dd><t>text</t>text </dd> <dt> Subtype name: </dt> <dd><t>javascript</t>javascript </dd> <dt> Required parameters: </dt> <dd><t>N/A</t>N/A </dd> <dt> Optional parameters: </dt> <dd><t>charset, see section 4.1charset. See <xref target="charset-parameter"/> of[this document].</t>RFC 9239. </dd> <dt> Encoding considerations: </dt> <dd><t>Binary</t>Binary </dd> <dt> Security considerations: </dt> <dd><t>See section 5See <xref target="security-considerations"/> of[this document].</t>RFC 9239. </dd> <dt> Interoperability considerations: </dt> <dd><t>ItIt is expected that implementations will behave as if this registration applies to later editions of <xreftarget="ECMA-262"/>,target="ECMA-262" format="default"/>, and its published specification references may be updated accordingly from time to time. Although this expectation is unusual among media type registrations, it matches widespread industry conventions. Seesection 2<xref target="compatibility"/> of[this document].</t>RFC 9239. </dd> <dt> Published specification: </dt> <dd><t><xref target="ECMA-262"/></t><xref target="ECMA-262" format="default"/> </dd> <dt> Applicationswhichthat use this media type: </dt> <dd><t>ScriptScript interpreters as discussed in[this document].</t>RFC 9239. </dd> </dl><t>Additional information:</t> <dl><dl newline="true" spacing="normal"> <dt>Additional information:</dt> <dd> <dl newline="false" spacing="compact"> <dt> Deprecated alias names for this type: </dt> <dd><t>application/javascript,application/javascript, application/x-javascript, text/javascript1.0, text/javascript1.1, text/javascript1.2, text/javascript1.3, text/javascript1.4, text/javascript1.5, text/jscript,text/livescript</t>text/livescript </dd><dt/> <dd> <dl><dt> Magic number(s): </dt> <dd><t>n/a</t>N/A </dd> <dt> File extension(s): </dt> <dd><t>.js, .mjs</t>.js, .mjs </dd> <dt> Macintosh File Type Code(s): </dt> <dd><t>TEXT</t>TEXT </dd> </dl> </dd> </dl> <dl newline="false" spacing="normal"> <dt> Person & email address to contact for further information: </dt> <dd><t>See Author's Address sectionSee the Authors' Addresses sections of[this document]RFC 9239 and <xreftarget="RFC4329"/>.</t>target="RFC4329" format="default"/>. </dd> <dt> Intended usage: </dt> <dd><t>COMMON</t>COMMON </dd> <dt> Restrictions on usage: </dt> <dd><t>TheThe .mjs file extension signals that the file represents a JavaScript module. Execution environments that rely on file extensions to determine how to process inputs parse .mjs files using the Module grammar of <xreftarget="ECMA-262"/>.</t>target="ECMA-262" format="default"/>. </dd> <dt> Author: </dt> <dd><t>See Author's Address sectionSee the Authors' Addresses sections of[this document]RFC 9239 and <xreftarget="RFC4329"/>.</t>target="RFC4329" format="default"/>. </dd> <dt> Change controller: </dt> <dd><t>IESG <iesg@ietf.org></t>IESG <iesg@ietf.org> </dd> </dl> </section> </section> <sectionanchor="historic-javascript-media-types"><name>Historicanchor="historic-javascript-media-types" numbered="true" toc="default"> <name>Historic JavaScript Media Types</name> <t>The following media types and legacy aliases are added or updated for historical purposes. All herein have an intended usage ofOBSOLETE,OBSOLETE and are not expected to be in use with modern implementations.</t> <sectionanchor="textecmascript"><name>text/ecmascript</name>anchor="textecmascript" numbered="true" toc="default"> <name>text/ecmascript</name> <dl> <dt> Type name: </dt> <dd><t>application</t>text </dd> <dt> Subtype name: </dt> <dd><t>ecmascript</t>ecmascript </dd> <dt> Required parameters: </dt> <dd><t>N/A</t>N/A </dd> <dt> Optional parameters: </dt> <dd><t>charset, see section 4.1charset. See <xref target="charset-parameter"/> of[this document].</t>RFC 9239. </dd> <dt> Encoding considerations: </dt> <dd><t>Binary</t>Binary </dd> <dt> Security considerations: </dt> <dd><t>See section 5See <xref target="security-considerations"/> of[this document].</t>RFC 9239. </dd> <dt> Interoperability considerations: </dt> <dd><t>ItIt is expected that implementations will behave as if this registration applies to later editions of <xreftarget="ECMA-262"/>,target="ECMA-262" format="default"/>, and its published specification references may be updated accordingly from time to time. Although this expectation is unusual among media type registrations, it matches widespread industry conventions. Seesection 2<xref target="compatibility"/> of[this document].</t>RFC 9239. </dd> <dt> Published specification: </dt> <dd><t><xref target="ECMA-262"/></t><xref target="ECMA-262" format="default"/> </dd> <dt> Applicationswhichthat use this media type: </dt> <dd><t>ScriptScript interpreters as discussed in[this document].</t>RFC 9239. </dd> </dl><t>Additional information:</t> <dl><dl newline="true" spacing="normal"> <dt>Additional information:</dt> <dd> <dl newline="false" spacing="compact"> <dt> Deprecated alias names for this type: </dt> <dd><t>application/ecmascript,application/ecmascript, application/x-ecmascript,text/x-ecmascript</t>text/x-ecmascript </dd> <dt> Magic number(s): </dt> <dd><t>n/a</t>N/A </dd> <dt> File extension(s): </dt> <dd><t>.es, .mjs</t>.es, .mjs </dd> <dt> Macintosh File Type Code(s): </dt> <dd><t>TEXT</t>TEXT </dd> </dl> </dd> </dl> <dl newline="false" spacing="normal"> <dt> Person & email address to contact for further information: </dt> <dd><t>See Author's Address sectionSee the Authors' Addresses sections of[this document]RFC 9239 and <xreftarget="RFC4329"/>.</t>target="RFC4329" format="default"/>. </dd> <dt> Intended usage: </dt> <dd><t>OBSOLETE</t>OBSOLETE </dd> <dt> Restrictions on usage: </dt> <dd><t>ThisThis media type is obsolete; current implementations should use text/javascript as the only JavaScript/ECMAScript media type. The .mjs file extension signals that the file represents a JavaScript module. Execution environments that rely on file extensions to determine how to process inputs parse .mjs files using the Module grammar of <xreftarget="ECMA-262"/>.</t>target="ECMA-262" format="default"/>. </dd> <dt> Author: </dt> <dd><t>See Author's Address sectionSee the Authors' Addresses sections of[this document]RFC 9239 and <xreftarget="RFC4329"/>.</t>target="RFC4329" format="default"/>. </dd> <dt> Change controller: </dt> <dd><t>IESG <iesg@ietf.org></t>IESG <iesg@ietf.org> </dd> </dl> </section> </section> </section> </middle> <back><references title='Normative References'> &RFC2045; &RFC2119; &RFC2397; &RFC2978; &RFC3552; &RFC3629; &RFC4288; &RFC4329; &RFC6365; &RFC6648; &RFC6838; &RFC8174;<references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2045.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2397.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2978.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3552.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3629.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4288.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4329.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6365.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6648.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6838.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <reference anchor="CHARSETS" target="https://www.iana.org/assignments/character-sets"> <front><title>Assigned character sets</title> <author ><title>Character Sets</title> <author> <organization>IANA</organization> </author><date year="n.d."/></front> </reference> <reference anchor="ECMA-262" target="https://262.ecma-international.org/12.0/"> <front><title>ECMAScript 2021 language specification, ECMA-262<title>ECMA-262 12th Edition, June2021</title> <author >2021. ECMAScript 2021 language specification</title> <author> <organization>Ecma International</organization> </author> <date year="2021" month="June"/> </front> </reference> </references><references title='Informative References'> &RFC3236; &RFC3875; &RFC3986; &RFC3987;<references> <name>Informative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3236.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3875.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3987.xml"/> <reference anchor="HTML" target="https://html.spec.whatwg.org/multipage/scripting.html#prepare-a-script"> <front> <title>HTML Living Standard</title><author ><author> <organization>WHATWG</organization> </author> <dateyear="2017" month="August"/>year="2022" month="May"/> </front> </reference> <reference anchor="SPECTRE" target="https://arxiv.org/abs/1801.01203"> <front> <title>Spectre Attacks: Exploiting Speculative Execution</title> <author initials="P." surname="Kocher" fullname="Paul Kocher"><organization></organization> </author> <author initials="A." surname="Fogh" fullname="Anders Fogh"> <organization></organization><organization/> </author> <author initials="D."surname="Gerkin"surname="Genkin" fullname="DanielGerkin"> <organization></organization>Genkin"> <organization/> </author> <author initials="D." surname="Gruss" fullname="Daniel Gruss"><organization></organization><organization/> </author> <author initials="W." surname="Haas" fullname="Werner Haas"><organization></organization><organization/> </author> <author initials="M." surname="Hamburg" fullname="Mike Hamburg"><organization></organization><organization/> </author> <author initials="M." surname="Lipp" fullname="Moritz Lipp"><organization></organization><organization/> </author> <author initials="S." surname="Mangard" fullname="Stefan Mangard"><organization></organization><organization/> </author> <author initials="T." surname="Prescher" fullname="Thomas Prescher"><organization></organization><organization/> </author> <author initials="M." surname="Schwarz" fullname="Michael Schwarz"><organization></organization><organization/> </author> <author initials="Y." surname="Yarom" fullname="Yuval Yarom"><organization></organization><organization/> </author> <date year="2018" month="January"/> </front> <seriesInfo name="DOI" value="10.48550/arXiv.1801.01203"/> </reference> <reference anchor="TC39-MIME-ISSUE" target="https://web.archive.org/web/20170814193912/https://github.com/tc39/ecma262/issues/322"> <front> <title>Add`application/javascript+module`'application/javascript+module' mime to remove ambiguity</title><author ><author> <organization>TC39</organization> </author> <date year="2017" month="August"/> </front> <refcontent>Wayback Machine archive</refcontent> </reference> </references> </references> <sectionanchor="acknowledgements"><name>Acknowledgements</name> <t>This work builds upon its antecedent document, authored by Bjoern Hoehrmann. The authors would like to thank Adam Roach, Alexey Melnikov, Allen Wirfs-Brock, Anne van Kesteren, Ben Campbell, Benjamin Kaduk, Éric Vyncke, Francesca Palombini, James Snell, Kirsty Paine, Mark Nottingham, Murray Kucherawy, Ned Freed, Robert Sparks, and Suresh Krishnan for their guidance and feedback throughout this process.</t> </section> <section anchor="changes-from-rfc-4329"><name>Changesanchor="changes-from-rfc-4329" numbered="true" toc="default"> <name>Changes from RFC 4329</name><t><list style="symbols"> <t>Added<ul spacing="normal"> <li>Added a section discussing ECMAScript modules and the impact onprocessing.</t> <t>Updatedprocessing.</li> <li>Updated the Security Considerations section to discuss concerns associated with ECMAScript modules andSharedArrayBuffers.</t> <t>UpdatedSharedArrayBuffers.</li> <li>Updated the character encoding scheme detection to remove normative guidance on its use, to better reflect operationalreality.</t> <t>Changedreality.</li> <li>Changed the intended usage of the media typetext/javascript"text/javascript" fromobsoleteOBSOLETE tocommon.</t> <t>ChangedCOMMON.</li> <li>Changed the intended usage for all other script media types toobsolete.</t> <t>Updatedobsolete.</li> <li>Updated various references where the original has beenobsoleted.</t> <t>Updatedobsoleted.</li> <li>Updated references to ECMA-262 to match the version at the time ofpublication.</t> </list></t>publication.</li> </ul> </section> <section anchor="acknowledgements" numbered="false" toc="default"> <name>Acknowledgements</name> <t>This work builds upon its antecedent document, authored by <contact fullname="Björn Höhrmann"/>. The authors would like to thank <contact fullname="Adam Roach"/>, <contact fullname="Alexey Melnikov"/>, <contact fullname="Allen Wirfs-Brock"/>, <contact fullname="Anne van Kesteren"/>, <contact fullname="Ben Campbell"/>, <contact fullname="Benjamin Kaduk"/>, <contact fullname="Éric Vyncke"/>, <contact fullname="Francesca Palombini"/>, <contact fullname="James Snell"/>, <contact fullname="Kirsty Paine"/>, <contact fullname="Mark Nottingham"/>, <contact fullname="Murray Kucherawy"/>, <contact fullname="Ned Freed"/>, <contact fullname="Robert Sparks"/>, and <contact fullname="Suresh Krishnan"/> for their guidance and feedback throughout this process.</t> </section> </back><!-- ##markdown-source: H4sIAA4ZH2IAA+1c624bOZb+r6cgHGA7npbk2E4cx1ksWnbsjqfjJBs729uY HuxQVZTEuC6aYpVldSYPsM+1L7bnQrLIUsnp7h1ggcE0BhO5isXLuX7n8JCj 0WhQ6zpTJ+L87GpynVR6WYsrlWopbtZLZcTHZSprZQZyOq3U3ckgLZNC5tA+ reSsHmlVz0apNktZJ4vRJ3knDfUxyj+Z0f7zQQIfz8tqfSJ0MSsHA72sTkRd NaY+ePLkxZODgayUPBGTDzeDVVndzquyWZ6IV5fX7yc3Z68Ht2oNj9MTcVnU qipUPXqFww7KqSkzBfM6EU8PD14MBqaWRfpfMisLmFpRDpb6RPypLpOhgP/T RaqKeihMWdWVmhn4tc7tj7rSCbxKynwp7Y8cGsMrXWS6UH8eDGRTL8rqZCBG AwH/6QJGvRqLK51lqqJHTJErWdcLtRKT6F1ZzWWhf5G1LosTeqJyqbMTAb03 96sym32LRPyubGCFo2UmC2XGsNLucKdlBT/D4dYZ8Cd4HI0kvtf162YaDpjj B1Nq/91c14tmOobVboyzLlQ8jqwXWprwRWekspxnKhqpXsAQ9HhjiNOxuJAV dBgMcVrJNFPr8MVWsk257ThXye13c3xGQwyKssqh9Z3C1h8uzg6ePH3mfu7v v3A/D188dz9fPD+2Pw+fPTtwP48OXNunB8euAQqZ/Xl0eOT6PTp66hocHR/2 /Dzef/70ZAC/z15PPlyf31zzSrxACbtSkO/J2wn9bbVxZ2KMnhcqFclCViCZ qhJG1WaHG8lqruoTsajrpTnZ21utVmMtCzmGvvYkfUlCvOc/HuHH8C1q+ejg 6GDrRM6TXFptI9rLLJpWYCUOnhzsCxDXeSPnSpilSvRMJ/TR0I8j9g/qhThP NT/+Y1Mo+pDXgablpH3YuzboZKxgUiMdTopWun8wfrIHNgUsi+e95eLB4ZFj 6PFzx6/DF8dH7U+Sg9c3V2+20uLH15ObH78P14/NxRt9p4u5uEaTI6s0WMmk mYNlg7WA5etby6LOszFSarxayHo1p1XkTVbrJdBwj00n9D3Gho+WlVqCeRzJ Eb/AtV2/Pz+7+XDeN+WR/dcp1XvZZOKHMllYQ7TZYgJ2sTLiopwvtrR4BTqo MvG9qm518ZU2YNTNliY/ou2uxGspt7W40rcK3ufTpppvawKWq/4FqL9cbmlx XauZLMBgFXPHl81GN4syB2v2vlLmAdJcaVAdWNV1sljJ6pctrX5q7mQmfpIV GqBATHaugcfgasSkrmVyC1bv/H6ZlbomuYF3TUbiCo/hN0p0pA+yaGS1RjE6 7hUjWd3rO9b1qdnbP36yP36yf/DkEOdwA6I9urq8Oh9dXl9/7BUUkm1sFxuc NBV/kctlZnV4r3Xm3+Zl2mTqLyLXuQKHKiqVlzB7YJeeN7peh7P/mg6s1HQs q2QBy6clwN972PjJ8f7T/ReHL/YP9lzT1knt1cnhiz00A2AO9rQxjTJ7hwcH g8FgNBoJIEONdm4wuFloIwCjNGj/RKpwAVNwk+CYYdZzje1wdaKciZxgTk0w BywItQnsG2g3sOJO2j+XVTmvZJ4jC53VM9QoKdkAFQmO8ddGA3nQ+lKnOl9m 9CcNa3BcGMcoHncs4gl7XOOczhBkyVmFEJftDGEoAAsJPseJg7G402VjolXy FHZqdV8H7NyhWe/083pHrIDqwttUIBW2jtYlM3ZN1BIBEzRqDHoBbBqvWKj7 paq0AuKYMXMr1yl48MHgEfqZCkQrwYaWdzmIVsC3Ph4FTMHxApb18mgMBl/N wPyA4OLnRiVMm51weEuUd3equtNqtQMUEJ8/Ozf25QuNPgVlRoiKqwwIBP9j noZjxoxtGEbTBHh1S54EE7fLMu4uXDxp3SyDuQNFoTUukWnOo3uEPKQugRJ3 GgaCgUd1OcLBceENmNA1CqyBl3bAcVdrWLDsZMM5xPMkAlkx/fKFhw2X+VVV aAwLb9lZaqpmGsUrHgCIb+AhrBZWUeE8PR2WqPsaBUxMgKK0PhgcZQ7w/xYF C7oGCjx6JG5UBYJTZuV8jRRRAoIPgdEHSMrVx+sbUDn6V7x9R78/nP/7x8sP 56/w9/XryZs3/odrcf363cc3r9pf7Zdn766uzt++4o/hqeg8upr8tDO0Evn+ 5vLd28kbksh4MQAOUC6mShA2AhNQA4Wk8fpDNDw9ey/2nwpeMEJhoCX/gfAU /lgtVMGDlUW2tn8CB9cCTISSFXYis0wkcqlrmUFoBEOYRbkqBDhQhdQTZxg/ 1XqqMxCwTTOMDDUCBQIcJj4C+QR+kQBsyAkKjxX62HAN+QG6AfcAZ91vyEgF QbBKcEYrkHZYmWmWSwgBgSytuOHiGhBAvTHaS1p0CbMBjISkdmoD38PyaoAj CXh/opuVKrSMIKVs5ePexixTGxK+yVG7nGlGzOWvjViB5taq6JqlsXgLEadi fE3jRkYL+zPN9BOYDRgOuwOLBzQvp2DCW4+Edg1gTsphsGPjEDW2RKWbrtly WsRrwzLHROxhM2z4xoBGJYuCiATikeP8lTh8IR4j9ti1ugowDPDvMDTqSZmq VtsB0IEMZhoMuF0m8mquAFACf9Z+ykAu8kcy7EoVcyC0kCkwkYxNCe8Be7Wd jUlKZkjE+0RZo0yeQjPXHW+cQQqoq4vQoRCE0q1VP1uANwBm3wDU954O7XRI ZA0NaNrvKw2ibwMlszMOV5GqO5WVS5RD9rawbJTZmZJ1g1ME0eMpwMQhRsdn ANmAF2EvtjWvyvWRkroLaKUzEjm7Jm9jizsNEoMEGIs3IeH6ha0oYbqgzUkN /cs0hfFMj6CD4mZg+Js5II0a+YkogWUUqdX1FCsNmjhVC4mgEzzPzCsJCapY gVJCF6AfKYs5LCHvYqu0hLXj/Oy0WLX5M+PYHi0IGNKjfvxZ6+q71i6XazTJ 7Ap5NhKCG/4MbEiNjcBggygmCWAJtFQ2y8bosNuZ9rJTgJiWS9YvAbEhBCHA EfNyg2A5QnBnr4ihmvJbOIBpkgVqFU9wY/qeTGykBNh5MavknF5qTKRBmI+i CKQAMpZNBRMLnz8m34KxNqIC98fzL192ybq7gQyQcKoyByNLGIqx8TYssGkp cfjsTqVAwIlbTz8J7VoCrwPN+lYF5HhbQi8khtQPKpqdGAHpndB5QIynSDpn DdqiVsQQIVskDSsFVwF2CHimmfugytYdP3n6DI34DeElaUCF2QPCwPC/1s2M IyjEQIw80RTkij0m+puf/7DhEeERkXIIhMAofh61LtEvO/dlNWaFCAL5QdYE RLRCmLlU5ZJcEjmKeATsu4aQznYOMWFK0ZBHcAfHxygMNlBJFXKhrFjhbMoM yXCt8auaAAjIHZi9ij/SRQoSDTGx9eQyBTVA5fKLXq/kmulIvNYeo9YdbMsY OrRx4NZYbjqRi0yq0phuyKGS0qyB+DlmiMHyTMW0KleGQAJCATYqrdk0VuGM eAsmefyJwqdbRV8DuOS4BExJJQv0j84Vm9gXsyx5xBuQ32DXuR0C3LVBVzgW Fw25hhiyA2hrspQkFIMc6+TYDQPSq8kDAIMShRpBwO6KQn8zGFwG06XQJ9O/ KAepSGopSwBw0UZhZhhb08dA54pmT2s5avOCux4h1iuwluVylKHHE/MSVMas 82mZgVmBEaqyrI2L41zQDy2AY/eki7t9gTyFhLI6sWshNl2HGNG1w+GAEGBW iG/YjddcGAsCRSTpCkEvCxACFUUpHGWc55xn5RTbJ+Cwh9BYZ9zYDt43CKdX BIuVmDY6sw4iWMRW4sEarpWKgUjw3Rvrp07sKllKLVd3Nnw4WWhVAxrwjs1g FpI1IlcS3STaxsd2ucAFjLOwI2nhD9k5Hx3vYjOEtUg0YK8T0TZmCeJe0GMx 13fgaMOls49BXYc5/XakOYzAqwGTmaJTpcz6nGbeDgZ2h+KnmoJBh0dCj0To qanRs1q/oCvmNv6Jm1hA0U4WjkLMSwI6qHueBKhK7DjcgIRtwhXH0xOUIQFL YeM+4AzCKxdJeykDUsbCT3JnLKpulhhFWySCits6NNpBIzsKlrKsFMV6S5xb XbeBQEiPTWjn09ixGSRH2tSjcjaayk4GJbSFLS0wSW6NABsuhFUG/f11matt 4xBKTDCrQHiYXAXNeoaq6OEeEnacfzKtw102FYY7ZPbOwe+l0PVg4HNH7KkO j55ZNZEAdE3SGNdZ3eYPGFk7yli1REUN+PpYdjIdrRYOW022X9wg8NiFCLxA GkzBIoEvDPVCiNONhygskn41QEIARxI8/Sf2frIOjVD4EXr81MuUDPaflKWJ wMR5rhB19fZOw64WZWZ7BH9Ql0mZgdgYzlhVcYNWdOgNCDWJvcaAn8IBg8ad 0LQ1RogBkAeWZQSckbMVm+qycslIMC+VVncIoBAjxh7+GyPsplJgkn16uENJ VNwgA9DDA1DxDgwvFAcArUg/QM+OEnAUvMlUDOIjxt/8asicZYDlQYR8CIFz MapuQwmCfPeILTQGcLypxzq/fd4k7BYrptYTxWQJFmbDU6I7hrQuhCPY2qJm xHkGOCI38sk+2Tf004qXAEv2CwRRWVAAJAuXZ0qHmB5b6lrZLCXv+KfeEFG+ 7DAEpmwiLNTkvP1g8Bpo2Q27Wj4/TDGrxzYzg2QJ82HomVnwra9x8Yf3MhFf QQQuSoxjJc4GqAJI0hAoc4pnaEC7ftuz37B9SCCNdTPSGBgqRedEoGi7/FhF sZ0jsRmPrTensJV7zngmqgIgAv9iSg2tJ4LceCPCZRysyJN7CkmzqZI0tEOt PepFGd4H3sfmEdfw8eZidGzj3CMKzx4ymSEM5H4Njwlkdn2DZ6BOgwyk78km Q2ZY9+AdStSbzTX39meTENvmB1OZ/MSSaTOlQ4CjLIfo7DgUxHj7x4Wirj5+ e3F+cYFcsxLMw0lxugYFe0dafwVxp3h8+u5qV2BlAuesQCyYc0vQPeM2MRaY rQ28OSd4tfkalx89wnQbidJ7J0qccN2UML81Ih2eLX+locNMaZ/rvZwJ6zzY JoG7aXzSYHMCjt0yjONds8+fXa2I21PRJvQ70LcmRdQ1B91un0bnauTH8tta G5spWPUSIoyD8eF4G6XQksZ5wsBMyShsYoK83C7eMoMA3RBmDQWF5LJlINPd gS/cfUe6v3L5TQeiWwDdly0ES4PiEriYCGGD6YO+s4cYbbDLNQoaBuHZ2sdd qI+RBbJMDnL2USEMbQRivGyInl2nB0yh5ABZOJadWYlemgiczbHiYZHjii0b Udg6q8WhrUK0XzRFrbNfs1IdBjvAh/0xSjNOpMf2aZfcQr+8jqKkkrE5C0Yo BCjBFLsal57/CIEaBc5uKhgGtJbBRmveUPhRWM7dVxb4tOQqYX1g2e2+H25S sYu5UxXmYyGKL2zer391w+4eD02Xw7ukrEC/IWqi+W43nycDXyDy7Wjjv+DR t77d38QbICb1YacOj7wC/K1t92B/QTtxfiFOT8XphWgfsYvCn0E7MNsX5yL4 j9vtH705j9udY9Oedqdhu6+tlxp2ZddBGdCOJZsJDBJ587vDzxhGP2inh0Jh BsGClUBKW5knjOJ8HFvwdiIdiXtgHAJD0TzbOMLDg4fF3XsDeFBWzs4S/Hc9 9IYaB2NxnhlMI85sULFhuz0IYzcCGsiOSRvrRUg3/Z6oje1jaxo6tF9LF5jd oZvdww6Vso8MLdmCOHdwOfv6lxvmh6W8XlS0r4SpJPbvZRsDEH/3RRB6yylV MhXpNqMXGq8efjtt6xUGzOL/NrY+6AfPq6rEKroizSg10RPyu3iZ0kzka8A5 OBzocqMB5XoojEAdg2p0H65ipNLmllJBNuXBgMJhiGdkjBFXS42IUSUy2DW5 k5WTQfKm6r6THnd5yconU7H3IW/d204ULX1hl+6dLH+VqVntssIWXZSV2fAQ 2HRalRBS4gaFyqwkyzr4yDZnEex3gbHcUbZpqoC5G4kTF75sFWIfBnVCXIyB ClcAYOc27IM58Raf341rilarH+uxGkPIW1oI7UP0nsW5mad6NlO0NbJ17rvj XvGzge3fj0QYfWCmEltteAQXItN+Blu0BFx1anf6OdRzgVfX9+BUIQA3ta4b ygWgyOuC+2kH8Xpvq6LymCwQ/1xcvBKPt+qaJRfFwaYulxGEzupyTnEU5Ryv nbadRfVZ3RQkFqv//hTkOacJTPcV6WfbG/lmwqsy8b66G51Z6lgFHtp9DMNh ywP76m3dUkMVyHVZUjBQlMVI3S/AeFBxLG2noXdbgp8E0kLc2/BeFrxk72lD l766v23JVWcdaSs29c4DTVNT2x0FTH2pbDYyzQyMjKbAjlNJw956Bd4MCjoI qdQGnDOZuJoPVmzaJuOsWBQ7iFlTJNwTyINLfQSfo95bwW2K2wJLseBtXdpN SCLwovlq2PxKVUDLdFtta6WC1D/MUhdJ1qQq3OiJJhp5n6gGLWTAS4554i/b BRmqTYgW5cLgry8J1Lyg/LHGEmvg1gNS6DrpKSvtlae2vCVwgV2KfizQWlXg RFRqvZlLJ1s3Z00kVhsptFQYm2KhEKAWcFm96SrrFX0XBBlxmyyu5LQuEOKV YHv4G+wDk+dUEZQZC3XK1j9riGpAPjGL70uEKGPnHc5LXGlIVXpNs7DpXJom BJ14sEulbZULsyvw6sxcTEyy+oT1RYOBDRzdOnW0DegSiMrY7RxlSw5svWtQ 2REIqDdOiSSeYEkbbaRuobVL/Vlb5lP4rtaNv8dgwmY3XBEY4G6xkmuqjeQx x/+Xjdm+8mO3MSsumoqNEW+t2oqjYNVL0GuZcFY9LPsFh0tpaky6Ea148lnJ wvLY7HZ2vdsya4wf/OIddShBPUXvjIpUlfmYctG6wN1WrL6VrouoldhBVzKS Y5u03oG54f6eZ29ph2q/Dz6b+s9ofx3zJ/Q12GT24UHp+hTT5wQgWRfjzULx WI3ngI4u37uisF0cuzsMSOZ1lNUhbnS9YWifkWDMsYcMrN3VdGZ1W302haey u3nlJNXWl7SDDx0YRA+FRmJLv5w52jSZesNWVYrgYOK4RxymOXMY4LyW32li BrgdmnhUZ25VDr6BhbDyI+CfnV7sNAeDaJPDzZB7saYlqEm6xxNU397nmcVM B4dHaPJ97Vni9pPZ86Y+bOzLQqNM5LLQSzy2wxrtJ9mKeiiKHAAxH+wGJNol PDdTt0DdvNzKm0rhESYuj36gAx8eeWL6ia1oIpwddI4K84yurCPRFbTkyROj Z2xU3CY7L/o20qdh4OGxAgi6pgRxWz7qzli48uzwhaRqKaOqOxxl3WJ99kJR NUAUz7T1eW697pWnejB/i6UURB0mBVi+JB/BB7E24gBfEBkoL4LidmfO2u9e LtnZ9OxahJEypRh+D1KlckJnHWLwmJXlcmjFrAtdXZRNmWaaKEUfOHcQDRgW q15kjqWnhs9B5WW1fskiYoczvPFjHXimAQSSSAyjeVAARrvK6bqQORbgwPhc m936SL9vPQ0CfGt5SXhBuB/vekC4+xIQwlYURbxyMIVCYKIBSIhmFUH50q1k dKNmQi0Wfwg5l6i/wJsfXZjnnCh2dQ1hnkonVSXXpw2GxLbCoYtMQJ4pAjum 6MCblrDMx08DtGCh54sR1a7ysmqdQ9eh+chw3xu+cvExb+yjtOncIR6UQ9zw KQqVOfF2VP382Z4T/fJld0voSzXJmA4jcQL24nkAZc0EA4Whr1wEWQad8rY6 L+kAbFj7t5VUvAGMg4WgzI1r4SOE7YitXNm9oc6sXPpdKG5EBJ2qekX5BC8a hDjvayuTlHEwWCNEyVaU8YbKVAigArsnmzae0l4cqXV0zc7O15foAtRt7GEb Z5CksY6Y3jrD0RFtSgIAC7FK0mt/JM0gNndNVtCmFQkO5Wt08clF6c6OXUdZ s6U/4NERbctC+9VvXDhgpyXlX9C+qNSe1SDpl+gjqtGdZobkKIZVtxJhM19g RYazP2AIlwsq2sO+ONsAE1BbZ0SxkI2UHfFLt/XqlcVWGfk6Uey8RwnIEMRa IO9Kzcc5G59R8WjYWx/XPyMnexBl+KCfcJhng/bePTObyEH3O4+Nbb/Kn7Dj gz1WGduKhK1JtZdf82lhLYMDiZNWex8oH7CRiE8/voyMBC3SNf2NXhaRvf0U 4Xickg0VgE7D+V2Xt7ZSmZ39BVqDs3EUcfU6CJ9X9XPCZh7+w4yaonBF0LGf ozyarKVVBmmjNpV2cnVsLMJeq84p1V5iuH18Zg+SoptXiGLtCMVa7PbrDEys ylKcfX/pYjGewPFzrIRUyaLks6ikwmwvCHkSLmBoB5DCLbtNEpjQfrZ4PJ4/ 7d2sNIJp+1l0IokPLNgEh0nAOFS67IjWNkr+hgorxm47yNadXlhqs9VcYXH4 4jlWWGBeu8wxzU6E9Ynkh6v0hi0pHApnhBPBoD4qtvHLFoL3ntbRfTS2+Rsq LX/YSvBifYzWhzSwVKkLgXzI6JlD2Sn0j7xb5ytz8Fw7JVEZTAXJsgDfthlS nTW0i48k9J+QWNH9C0xQdI24w0K3IpACtwBEujJ8tFeYOqQQOohOXPrSD/V3 SVzSafjJ28lG7j+u7uyc58DsD+oJlWehu0z53ADW2efyE4J+vn9J401JXJiZ Rf1t3g1gYTPOd2Vl2J/vt+dts6zvqFarT+44EcfsdEKpncdw40P8Jjgt57MN nYOu4GwdhER7hGfhtlR047Zy2p4EhPCFNxLj5tHeDt8DRWiczREpgAkKz7eV 2mOVy1hcaIq9eHGfP+M9MaAWUS0Q6rPpu4zB3Qowk4CuQubEpf+2AAsLoNnl 0tNazs1LzgNyvf7mAH6ng+8L8FWdeIeHzei8O71+9+b85hzf4EH0d2/Z5hna gy/cbgB/Z89QOeOlWHDDS8OslBKy4S05yjIQvaMDXxOqpwpFmqobl+BSah8O tAXMphUOPusFppvlpsC0CB7kYu7YPZlNWgTUxYMetCu541b/Cuc7AxRIeYZt 92N4+vEtKOlvmEl7cv13zyTsYnMmxAltXCKVVQB0geZAM9syxAah8LsN5vAR 6U2ykqY3PjuTqTkmnx86JcIhmkQ/TSSIjzcRxe5HOyjuM31/Mhj8Ic7ujVoy bLxq5wWvaKad5vZZ0C4684lCj8IO4UmRzmjXL7oxwIk3PebTMWKypIz6vZh4 z+hEnLUopiOegcRom0rNn9viYbxNDHEDG2DaYrnTJWYch35TjwLhMPcaE9Xd UdJzgNDWlrAxD7a6ArXFFo+6kgBmAPlD9x0NBif0GkCnZZt/HH7wwYUl7Qll avN2bzIYvNs8vkwvbQUTFqa2+yVPx/tIz5//FC3zz3gKzFerRP6SuuK6BJhk P3ahNtfBKM+2jHHZLdfs6efyd51ep6Gi64hIhG1q78FT9kO/GbNspuDYFogB IzfjTaTpHkX31RF4egbNfm3vc8J/0RjbI/k0PV5TUJDSGMygyBzvj9iGSIZh WXJ4hsOd3wUSIpxj0BYy4WALE973r5KIH9JlMJiEZ2JZiTgJr8NrhJj79jCd vzWlMhvFTT1zmfQecKSiz1dY9pcwlfEOENKM4GyZHVqIky1+ZbjVig27Krk/ ftLzbL/n2UHPs8OeZ097nj1zz6JZZICGnZ7j1ZBzwPBFk09V9djs2gUWexJ/ XERoq309/gRigjgN/7zCG6zq0iy4OdmaMwgF2uY35/95A2IALAIp+Re+BdJf 4UDxKyhawrbPbQHE3GFtnxDa/8ZgJoO+dZLXI3ekY/EFQZcRiKJeGSihvfPo kQ4ytC0QGPAZwxioUvVnZlp4QO+DA3nRJSa82TpuL4uLc2r2MB/txWxA3Khq Fq9yCLeyMVo3DGzbaZoeiGvPkHZMEWqEvVju70NjvjFF+Nw/d3x5fv29+Plf wTrOv8ObUvHWuJ//bUD+7LW9IGGrR4srAKOoo0gdUHG39tDtOxQ4gCw5o0lb ve11P+7EIWNXG4CxaS+6SBtW7dBW68K5IKKbr0JLRdDH3tvS8SHjwDcHWKbj mwML0uOiw+/+6aL/6aL/6aJ/lYuObhvbEoMMe+IMcm6/xz2qfxD36Ezfww4y 4jzt9dns0Ut/P0tXWW1OhiQnRi0ul0JhUusS9oIsSjvY+B/fPf//+me86xOj UXTVYpJgYjRT6ZxPztkqFLovA288SQ1fS6FpW6a2V9CEF4bR3Dl3evqpRCf5 ulQLvHe1sKX+3MTY0he8ZceWgRe3YBhkLj6UMlkMB5NM3WMBo8oKfVve4YNM FeJHXc3M6BTIfwuPigKPLhTiB0WhfjEcnEKbM5kvpyrL6K9PEvgmfpBpAx/8 z38jDvmPdZHcquHgosKMl0mkeC8z2gXQw8EfyeBcF/T9D7oy4LDeY1XccEBn ZN+WNeZAFjKHBw3upYsfGrykWK7Ww8FbWPtFpVQ6HHwowaLU4hpk45bLrcHd A0MX4ocKLHEhi4HdctRVexsTFaXB98gTt1/A5XHt8V2+zNGm/MgBgQDYO/b/ gGKD1tOLjdvRAnkMVcwVB9pDNe7qsfD46Bh6++hyvtBmS+07KQgP0pYvSmPK RNOnBJm2DL1RkmC6g24/dhDdqGdvO/YXzLcUtfLa0EknhHI1dubumPL7E3S9 BJdywwyYupY0G4AxTo5vGDiuv3PXTZJ9x4zOV/qlswL+KLnpWkLe7PdZ+5ZI eHSH7xT2eKW9/cgXifr0pesiDfsIvrU3GtG98FRdVnOiyxfQoLnVfNCaoBO7 2vHgfwGjvoBsp2IAAA== --></rfc>