idnits 2.17.1 draft-ietf-dispatch-javascript-mjs-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4329, updated by this document, for RFC5378 checks: 2001-09-24) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 19, 2019) is 1773 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 4329 (Obsoleted by RFC 9239) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DISPATCH M. Borins 3 Internet-Draft M. Bynens 4 Updates: 4329 (if approved) Google 5 Intended status: Informational M. Miller 6 Expires: December 21, 2019 Mozilla 7 B. Farias 8 June 19, 2019 10 ECMAScript Media Types Updates 11 draft-ietf-dispatch-javascript-mjs-04 13 Abstract 15 This document proposes updates to the ECMAScript media types, 16 superseding the existing registrations for "application/javascript" 17 and "text/javascript" by adding an additional extension and removing 18 usage warnings. This document updates RFC4329, "Scripting Media 19 Types". 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on December 21, 2019. 38 Copyright Notice 40 Copyright (c) 2019 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 58 3.1. Common Javascript Media Types . . . . . . . . . . . . . . 3 59 3.1.1. text/javascript . . . . . . . . . . . . . . . . . . . 3 60 3.2. Historic Javascript Media Types . . . . . . . . . . . . . 4 61 3.2.1. application/ecmascript . . . . . . . . . . . . . . . 4 62 3.2.2. application/javascript . . . . . . . . . . . . . . . 5 63 3.2.3. application/x-ecmascript . . . . . . . . . . . . . . 6 64 3.2.4. application/x-javascript . . . . . . . . . . . . . . 7 65 3.2.5. text/ecmascript . . . . . . . . . . . . . . . . . . . 8 66 3.2.6. text/javascript1.0 . . . . . . . . . . . . . . . . . 9 67 3.2.7. text/javascript1.1 . . . . . . . . . . . . . . . . . 10 68 3.2.8. text/javascript1.2 . . . . . . . . . . . . . . . . . 11 69 3.2.9. text/javascript1.3 . . . . . . . . . . . . . . . . . 12 70 3.2.10. text/javascript1.4 . . . . . . . . . . . . . . . . . 13 71 3.2.11. text/javascript1.5 . . . . . . . . . . . . . . . . . 14 72 3.2.12. text/jscript . . . . . . . . . . . . . . . . . . . . 15 73 3.2.13. text/livescript . . . . . . . . . . . . . . . . . . . 16 74 3.2.14. text/x-ecmascript . . . . . . . . . . . . . . . . . . 17 75 3.2.15. text/x-javascript . . . . . . . . . . . . . . . . . . 18 76 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 77 4.1. Normative References . . . . . . . . . . . . . . . . . . 19 78 4.2. Informative References . . . . . . . . . . . . . . . . . 19 79 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 19 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 82 1. Introduction 84 This document updates the existing media types for the ECMAScript 85 programming language. It supersedes the media types registrations in 86 [RFC4329] for "application/javascript" and "text/javascript". 88 2. Background 90 In order to formalize support for modular programs [ECMA-262] now 91 defines two top-level goal symbols for the ECMAScript grammar. This 92 means that (in the absence of additional information) there are two 93 possible interpretations for any given ECMAScript Source Text. The 94 TC39 standards body for ECMAScript has determined that media types 95 are outside of their scope of work [TC39-MIME-ISSUE]. 97 It is not possible to fully determine if a Source Text of ECMAScript 98 is meant to be parsed in the Module or Script grammar goals based 99 upon content alone. Therefore, scripting environments must use out 100 of band information in order to determine what goal a Source Text 101 should be treated as. To this end some scripting environments have 102 chosen to adopt a new file extension of .mjs for determining the goal 103 of a given Source Text. 105 3. IANA Considerations 107 The media type registrations herein are divided into two major 108 categories: the sole media type "text/javascript" which is now in 109 common usage, and all of the media types that are obsolete. 111 For both categories, The ECMAScript media types are to be updated to 112 point to a non-vendor specific standard undated specification of 113 ECMAScript. In addition, a new file extension of .mjs is to be added 114 to the list of file extensions with the restriction that it must 115 correspond to the Module grammar of [ECMA-262]. Finally, the [HTML] 116 specification is using "text/javascript" as the default media type of 117 ECMAScript when preparing script tags; therefore, "text/javascript" 118 has been moved intended usage from OBSOLETE to COMMON. 120 3.1. Common Javascript Media Types 122 3.1.1. text/javascript 124 Type name: text 126 Subtype name: javascript 128 Required parameters: none 130 Optional parameters: charset, see section 4.1 of [RFC4329]. 132 Encoding considerations: Encoding is host dependent with differences 133 in byte order marks, the charset parameter, and text 134 preprocessing. 136 Security considerations: See section 5 of [RFC4329]. 138 Interoperability considerations: See notes in various sections of 139 [RFC4329]. 141 Published specification: [[RFCXXXX]] 143 Applications which use this media type: Script interpreters as 144 discussed in [RFC4329]. 146 Additional information: 148 Magic number(s): n/a 150 File extension(s): .js, .mjs 152 Macintosh File Type Code(s): TEXT 154 Person & email address to contact for further information: See 155 Author's Address section. 157 Intended usage: COMMON 159 Restrictions on usage: The .mjs file extension signals that the file 160 represents a JavaScript module. Execution environments that rely 161 on file extensions to determine how to process inputs parse .mjs 162 files using the Module grammar of [ECMA-262]. 164 Author: See Author's Address section. 166 Change controller: IESG 168 3.2. Historic Javascript Media Types 170 The following media types are added or updated for historical 171 purposes. All herein have an intended usage of OBSOLETE, and are not 172 expected to be in use with modern implementations. 174 3.2.1. application/ecmascript 176 Type name: application 178 Subtype name: ecmascript 180 Required parameters: none 182 Optional parameters: charset, see section 4.1 of [RFC4329]. 184 Encoding considerations: Encoding is host dependent with differences 185 in byte order marks, the charset parameter, and text 186 preprocessing. 188 Security considerations: See section 5 of [RFC4329]. 190 Interoperability considerations: See notes in various sections of 191 [RFC4329]. 193 Published specification: [[RFCXXXX]] 194 Applications which use this media type: Script interpreters as 195 discussed in [RFC4329]. 197 Additional information: 199 Magic number(s): n/a 201 File extension(s): .es, .mjs 203 Macintosh File Type Code(s): TEXT 205 Person & email address to contact for further information: See 206 Author's Address section. 208 Intended usage: OBSOLETE 210 Restrictions on usage: This media type is obsolete; current 211 implementations should use text/javascript as the only JavaScript/ 212 ECMAScript media type. The .mjs file extension signals that the 213 file represents a JavaScript module. Execution environments that 214 rely on file extensions to determine how to process inputs parse 215 .mjs files using the Module grammar of [ECMA-262]. 217 Author: See Author's Address section. 219 Change controller: IESG 221 3.2.2. application/javascript 223 Type name: application 225 Subtype name: javascript 227 Required parameters: none 229 Optional parameters: charset, see section 4.1 of [RFC4329]. 231 Encoding considerations: Encoding is host dependent with differences 232 in byte order marks, the charset parameter, and text 233 preprocessing. 235 Security considerations: See section 5 of [RFC4329]. 237 Interoperability considerations: See notes in various sections of 238 [RFC4329]. 240 Published specification: [[RFCXXXX]] 241 Applications which use this media type: Script interpreters as 242 discussed in [RFC4329]. 244 Additional information: 246 Magic number(s): n/a 248 File extension(s): .js, .mjs 250 Macintosh File Type Code(s): TEXT 252 Person & email address to contact for further information: See 253 Author's Address section. 255 Intended usage: OBSOLETE 257 Restrictions on usage: This media type is obsolete; current 258 implementations should use text/javascript as the only JavaScript/ 259 ECMAScript media type. The .mjs file extension signals that the 260 file represents a JavaScript module. Execution environments that 261 rely on file extensions to determine how to process inputs parse 262 .mjs files using the Module grammar of [ECMA-262]. 264 Author: See Author's Address section. 266 Change controller: IESG . 268 3.2.3. application/x-ecmascript 270 Type name: application 272 Subtype name: x-ecmascript 274 Required parameters: none 276 Optional parameters: charset, see section 4.1 of [RFC4329]. 278 Encoding considerations: Encoding is host dependent with differences 279 in byte order marks, the charset parameter, and text 280 preprocessing. 282 Security considerations: See section 5 of [RFC4329]. 284 Interoperability considerations: See notes in various sections of 285 [RFC4329]. 287 Published specification: [[RFCXXXX]] 288 Applications which use this media type: Script interpreters as 289 discussed in [RFC4329]. 291 Additional information: 293 Magic number(s): n/a 295 File extension(s): .es, .mjs 297 Macintosh File Type Code(s): TEXT 299 Person & email address to contact for further information: See 300 Author's Address section. 302 Intended usage: OBSOLETE 304 Restrictions on usage: This media type is obsolete; current 305 implementations should use text/javascript as the only JavaScript/ 306 ECMAScript media type. The .mjs file extension signals that the 307 file represents a JavaScript module. Execution environments that 308 rely on file extensions to determine how to process inputs parse 309 .mjs files using the Module grammar of [ECMA-262]. 311 Author: See Author's Address section. 313 Change controller: IESG 315 3.2.4. application/x-javascript 317 Type name: application 319 Subtype name: x-javascript 321 Required parameters: none 323 Optional parameters: charset, see section 4.1 of [RFC4329]. 325 Encoding considerations: Encoding is host dependent with differences 326 in byte order marks, the charset parameter, and text 327 preprocessing. 329 Security considerations: See section 5 of [RFC4329]. 331 Interoperability considerations: See notes in various sections of 332 [RFC4329]. 334 Published specification: [[RFCXXXX]] 335 Applications which use this media type: Script interpreters as 336 discussed in [RFC4329]. 338 Additional information: 340 Magic number(s): n/a 342 File extension(s): .js, .mjs 344 Macintosh File Type Code(s): TEXT 346 Person & email address to contact for further information: See 347 Author's Address section. 349 Intended usage: OBSOLETE 351 Restrictions on usage: This media type is obsolete; current 352 implementations should use text/javascript as the only JavaScript/ 353 ECMAScript media type. The .mjs file extension signals that the 354 file represents a JavaScript module. Execution environments that 355 rely on file extensions to determine how to process inputs parse 356 .mjs files using the Module grammar of [ECMA-262]. 358 Author: See Author's Address section. 360 Change controller: IESG 362 3.2.5. text/ecmascript 364 Type name: text 366 Subtype name: ecmascript 368 Required parameters: none 370 Optional parameters: charset, see section 4.1 of [RFC4329]. 372 Encoding considerations: Encoding is host dependent with differences 373 in byte order marks, the charset parameter, and text 374 preprocessing. 376 Security considerations: See section 5 of [RFC4329]. 378 Interoperability considerations: See notes in various sections of 379 [RFC4329]. 381 Published specification: [[RFCXXXX]] 382 Applications which use this media type: Script interpreters as 383 discussed in [RFC4329]. 385 Additional information: 387 Magic number(s): n/a 389 File extension(s): .es, .mjs 391 Macintosh File Type Code(s): TEXT 393 Person & email address to contact for further information: See 394 Author's Address section. 396 Intended usage: OBSOLETE 398 Restrictions on usage: This media type is obsolete; current 399 implementations should use text/javascript as the only JavaScript/ 400 ECMAScript media type. The .mjs file extension signals that the 401 file represents a JavaScript module. Execution environments that 402 rely on file extensions to determine how to process inputs parse 403 .mjs files using the Module grammar of [ECMA-262]. 405 Author: See Author's Address section. 407 Change controller: IESG 409 3.2.6. text/javascript1.0 411 Type name: text 413 Subtype name: javascript1.0 415 Required parameters: none 417 Optional parameters: charset, see section 4.1 of [RFC4329]. 419 Encoding considerations: Encoding is host dependent with differences 420 in byte order marks, the charset parameter, and text 421 preprocessing. 423 Security considerations: See section 5 of [RFC4329]. 425 Interoperability considerations: See notes in various sections of 426 [RFC4329]. 428 Published specification: [[RFCXXXX]] 429 Applications which use this media type: Script interpreters as 430 discussed in [RFC4329]. 432 Additional information: 434 Magic number(s): n/a 436 File extension(s): .js, .mjs 438 Macintosh File Type Code(s): TEXT 440 Person & email address to contact for further information: See 441 Author's Address section. 443 Intended usage: OBSOLETE 445 Restrictions on usage: This media type is obsolete; current 446 implementations should use text/javascript as the only JavaScript/ 447 ECMAScript media type. The .mjs file extension signals that the 448 file represents a JavaScript module. Execution environments that 449 rely on file extensions to determine how to process inputs parse 450 .mjs files using the Module grammar of [ECMA-262]. 452 Author: See Author's Address section. 454 Change controller: IESG 456 3.2.7. text/javascript1.1 458 Type name: text 460 Subtype name: javascript1.1 462 Required parameters: none 464 Optional parameters: charset, see section 4.1 of [RFC4329]. 466 Encoding considerations: Encoding is host dependent with differences 467 in byte order marks, the charset parameter, and text 468 preprocessing. 470 Security considerations: See section 5 of [RFC4329]. 472 Interoperability considerations: See notes in various sections of 473 [RFC4329]. 475 Published specification: [[RFCXXXX]] 476 Applications which use this media type: Script interpreters as 477 discussed in [RFC4329]. 479 Additional information: 481 Magic number(s): n/a 483 File extension(s): .js, .mjs 485 Macintosh File Type Code(s): TEXT 487 Person & email address to contact for further information: See 488 Author's Address section. 490 Intended usage: OBSOLETE 492 Restrictions on usage: This media type is obsolete; current 493 implementations should use text/javascript as the only JavaScript/ 494 ECMAScript media type. The .mjs file extension signals that the 495 file represents a JavaScript module. Execution environments that 496 rely on file extensions to determine how to process inputs parse 497 .mjs files using the Module grammar of [ECMA-262]. 499 Author: See Author's Address section. 501 Change controller: IESG 503 3.2.8. text/javascript1.2 505 Type name: text 507 Subtype name: javascript1.2 509 Required parameters: none 511 Optional parameters: charset, see section 4.1 of [RFC4329]. 513 Encoding considerations: Encoding is host dependent with differences 514 in byte order marks, the charset parameter, and text 515 preprocessing. 517 Security considerations: See section 5 of [RFC4329]. 519 Interoperability considerations: See notes in various sections of 520 [RFC4329]. 522 Published specification: [[RFCXXXX]] 523 Applications which use this media type: Script interpreters as 524 discussed in [RFC4329]. 526 Additional information: 528 Magic number(s): n/a 530 File extension(s): .js, .mjs 532 Macintosh File Type Code(s): TEXT 534 Person & email address to contact for further information: See 535 Author's Address section. 537 Intended usage: OBSOLETE 539 Restrictions on usage: This media type is obsolete; current 540 implementations should use text/javascript as the only JavaScript/ 541 ECMAScript media type. The .mjs file extension signals that the 542 file represents a JavaScript module. Execution environments that 543 rely on file extensions to determine how to process inputs parse 544 .mjs files using the Module grammar of [ECMA-262]. 546 Author: See Author's Address section. 548 Change controller: IESG 550 3.2.9. text/javascript1.3 552 Type name: text 554 Subtype name: javascript1.3 556 Required parameters: none 558 Optional parameters: charset, see section 4.1 of [RFC4329]. 560 Encoding considerations: Encoding is host dependent with differences 561 in byte order marks, the charset parameter, and text 562 preprocessing. 564 Security considerations: See section 5 of [RFC4329]. 566 Interoperability considerations: See notes in various sections of 567 [RFC4329]. 569 Published specification: [[RFCXXXX]] 570 Applications which use this media type: Script interpreters as 571 discussed in [RFC4329]. 573 Additional information: 575 Magic number(s): n/a 577 File extension(s): .js, .mjs 579 Macintosh File Type Code(s): TEXT 581 Person & email address to contact for further information: See 582 Author's Address section. 584 Intended usage: OBSOLETE 586 Restrictions on usage: This media type is obsolete; current 587 implementations should use text/javascript as the only JavaScript/ 588 ECMAScript media type. The .mjs file extension signals that the 589 file represents a JavaScript module. Execution environments that 590 rely on file extensions to determine how to process inputs parse 591 .mjs files using the Module grammar of [ECMA-262]. 593 Author: See Author's Address section. 595 Change controller: IESG 597 3.2.10. text/javascript1.4 599 Type name: text 601 Subtype name: javascript1.4 603 Required parameters: none 605 Optional parameters: charset, see section 4.1 of [RFC4329]. 607 Encoding considerations: Encoding is host dependent with differences 608 in byte order marks, the charset parameter, and text 609 preprocessing. 611 Security considerations: See section 5 of [RFC4329]. 613 Interoperability considerations: See notes in various sections of 614 [RFC4329]. 616 Published specification: [[RFCXXXX]] 617 Applications which use this media type: Script interpreters as 618 discussed in [RFC4329]. 620 Additional information: 622 Magic number(s): n/a 624 File extension(s): .js, .mjs 626 Macintosh File Type Code(s): TEXT 628 Person & email address to contact for further information: See 629 Author's Address section. 631 Intended usage: OBSOLETE 633 Restrictions on usage: This media type is obsolete; current 634 implementations should use text/javascript as the only JavaScript/ 635 ECMAScript media type. The .mjs file extension signals that the 636 file represents a JavaScript module. Execution environments that 637 rely on file extensions to determine how to process inputs parse 638 .mjs files using the Module grammar of [ECMA-262]. 640 Author: See Author's Address section. 642 Change controller: IESG 644 3.2.11. text/javascript1.5 646 Type name: text 648 Subtype name: javascript1.5 650 Required parameters: none 652 Optional parameters: charset, see section 4.1 of [RFC4329]. 654 Encoding considerations: Encoding is host dependent with differences 655 in byte order marks, the charset parameter, and text 656 preprocessing. 658 Security considerations: See section 5 of [RFC4329]. 660 Interoperability considerations: See notes in various sections of 661 [RFC4329]. 663 Published specification: [[RFCXXXX]] 664 Applications which use this media type: Script interpreters as 665 discussed in [RFC4329]. 667 Additional information: 669 Magic number(s): n/a 671 File extension(s): .js, .mjs 673 Macintosh File Type Code(s): TEXT 675 Person & email address to contact for further information: See 676 Author's Address section. 678 Intended usage: OBSOLETE 680 Restrictions on usage: This media type is obsolete; current 681 implementations should use text/javascript as the only JavaScript/ 682 ECMAScript media type. The .mjs file extension signals that the 683 file represents a JavaScript module. Execution environments that 684 rely on file extensions to determine how to process inputs parse 685 .mjs files using the Module grammar of [ECMA-262]. 687 Author: See Author's Address section. 689 Change controller: IESG 691 3.2.12. text/jscript 693 Type name: text 695 Subtype name: jscript 697 Required parameters: none 699 Optional parameters: charset, see section 4.1 of [RFC4329]. 701 Encoding considerations: Encoding is host dependent with differences 702 in byte order marks, the charset parameter, and text 703 preprocessing. 705 Security considerations: See section 5 of [RFC4329]. 707 Interoperability considerations: See notes in various sections of 708 [RFC4329]. 710 Published specification: [[RFCXXXX]] 711 Applications which use this media type: Script interpreters as 712 discussed in [RFC4329]. 714 Additional information: 716 Magic number(s): n/a 718 File extension(s): .js, .mjs 720 Macintosh File Type Code(s): TEXT 722 Person & email address to contact for further information: See 723 Author's Address section. 725 Intended usage: OBSOLETE 727 Restrictions on usage: The .mjs file extension signals that the file 728 represents a JavaScript module. Execution environments that rely 729 on file extensions to determine how to process inputs parse .mjs 730 files using the Module grammar of [ECMA-262]. 732 Author: See Author's Address section. 734 Change controller: IESG 736 3.2.13. text/livescript 738 Type name: text 740 Subtype name: livescript 742 Required parameters: none 744 Optional parameters: charset, see section 4.1 of [RFC4329]. 746 Encoding considerations: Encoding is host dependent with differences 747 in byte order marks, the charset parameter, and text 748 preprocessing. 750 Security considerations: See section 5 of [RFC4329]. 752 Interoperability considerations: See notes in various sections of 753 [RFC4329]. 755 Published specification: [[RFCXXXX]] 757 Applications which use this media type: Script interpreters as 758 discussed in [RFC4329]. 760 Additional information: 762 Magic number(s): n/a 764 File extension(s): .js, .mjs 766 Macintosh File Type Code(s): TEXT 768 Person & email address to contact for further information: See 769 Author's Address section. 771 Intended usage: OBSOLETE 773 Restrictions on usage: The .mjs file extension signals that the file 774 represents a JavaScript module. Execution environments that rely 775 on file extensions to determine how to process inputs parse .mjs 776 files using the Module grammar of [ECMA-262]. 778 Author: See Author's Address section. 780 Change controller: IESG 782 3.2.14. text/x-ecmascript 784 Type name: text 786 Subtype name: x-ecmascript 788 Required parameters: none 790 Optional parameters: charset, see section 4.1 of [RFC4329]. 792 Encoding considerations: Encoding is host dependent with differences 793 in byte order marks, the charset parameter, and text 794 preprocessing. 796 Security considerations: See section 5 of [RFC4329]. 798 Interoperability considerations: See notes in various sections of 799 [RFC4329]. 801 Published specification: [[RFCXXXX]] 803 Applications which use this media type: Script interpreters as 804 discussed in [RFC4329]. 806 Additional information: 808 Magic number(s): n/a 810 File extension(s): .es, .mjs 812 Macintosh File Type Code(s): TEXT 814 Person & email address to contact for further information: See 815 Author's Address section. 817 Intended usage: OBSOLETE 819 Restrictions on usage: The .mjs file extension signals that the file 820 represents a JavaScript module. Execution environments that rely 821 on file extensions to determine how to process inputs parse .mjs 822 files using the Module grammar of [ECMA-262]. 824 Author: See Author's Address section. 826 Change controller: IESG 828 3.2.15. text/x-javascript 830 Type name: text 832 Subtype name: x-javascript 834 Required parameters: none 836 Optional parameters: charset, see section 4.1 of [RFC4329]. 838 Encoding considerations: Encoding is host dependent with differences 839 in byte order marks, the charset parameter, and text 840 preprocessing. 842 Security considerations: See section 5 of [RFC4329]. 844 Interoperability considerations: See notes in various sections of 845 [RFC4329]. 847 Published specification: [[RFCXXXX]] 849 Applications which use this media type: Script interpreters as 850 discussed in [RFC4329]. 852 Additional information: 854 Magic number(s): n/a 855 File extension(s): .js, .mjs 857 Macintosh File Type Code(s): TEXT 859 Person & email address to contact for further information: See 860 Author's Address section. 862 Intended usage: OBSOLETE 864 Restrictions on usage: The .mjs file extension signals that the file 865 represents a JavaScript module. Execution environments that rely 866 on file extensions to determine how to process inputs parse .mjs 867 files using the Module grammar of [ECMA-262]. 869 Author: See Author's Address section. 871 Change controller: IESG 873 4. References 875 4.1. Normative References 877 [ECMA-262] 878 Ecma International, "Standard ECMA-262: ECMAScript 879 Language Specification", August 2017, . 882 [RFC4329] Hoehrmann, B., "Scripting Media Types", RFC 4329, 883 DOI 10.17487/RFC4329, April 2006, 884 . 886 4.2. Informative References 888 [HTML] WHATWG, "HTML Living Standard", August 2017, 889 . 892 [TC39-MIME-ISSUE] 893 TC39, "Add `application/javascript+module` mime to remove 894 ambiguity", August 2017, . 897 Appendix A. Acknowledgements 899 The authors would like to thank Suresh Krishnan, Alexey Melnikov, 900 Mark Nottingham, James Snell, Adam Roach, and Allen Wirfs-Brock for 901 their guidance throughout this process. 903 Authors' Addresses 905 Myles Borins 906 Google 908 Email: mylesborins@google.com 910 Mathias Bynens 911 Google 913 Email: mths@google.com 915 Matthew A. Miller 916 Mozilla 918 Email: linuxwolf+ietf@outer-planes.net 920 Bradley Farias 922 Email: bradley.meck@gmail.com