idnits 2.17.1 draft-ietf-dispatch-javascript-mjs-00.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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The abstract seems to contain references ([2], [3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. (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 (October 7, 2017) is 2392 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 918 -- Looks like a reference, but probably isn't: '2' on line 920 -- Looks like a reference, but probably isn't: '3' on line 922 == Unused Reference: 'RFC3023' is defined on line 897, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Obsolete normative reference: RFC 4329 (Obsoleted by RFC 9239) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DISPATCH B. Farias 3 Internet-Draft 4 Updates: 4329 (if approved) M. Miller 5 Intended status: Informational Mozilla 6 Expires: April 10, 2018 October 7, 2017 8 ECMAScript Media Types Updates 9 draft-ietf-dispatch-javascript-mjs-00 11 Abstract 13 This document proposes updates to the ECMAScript media types, 14 superseding the existing registrations for "application/javascript" 15 and "text/javascript" by adding an additional extension and removing 16 usage warnings. This document updates RFC4329, "Scripting Media 17 Types". 19 Note to Readers 21 The issues list for this draft can be found at 22 https://github.com/bmeck/I-D/labels/javascript-mjs [1]. 24 The most recent (often, unpublished) draft is at 25 https://github.com/bmeck/I-D/tree/master/javascript-mjs [2]. 27 Recent changes are listed at https://github.com/bmeck/I- 28 D/commits/master/javascript-mjs [3]. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at https://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on April 10, 2018. 47 Copyright Notice 49 Copyright (c) 2017 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (https://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 3. Notational Conventions . . . . . . . . . . . . . . . . . . . 3 67 4. Registration . . . . . . . . . . . . . . . . . . . . . . . . 3 68 4.1. appliaction/ecmascript . . . . . . . . . . . . . . . . . 3 69 4.2. application/javascript . . . . . . . . . . . . . . . . . 4 70 4.3. application/x-ecmascript . . . . . . . . . . . . . . . . 5 71 4.4. application/x-javascript . . . . . . . . . . . . . . . . 6 72 4.5. text/ecmascript . . . . . . . . . . . . . . . . . . . . . 7 73 4.6. text/javascript . . . . . . . . . . . . . . . . . . . . . 8 74 4.7. text/javascript1.0 . . . . . . . . . . . . . . . . . . . 9 75 4.8. text/javascript1.1 . . . . . . . . . . . . . . . . . . . 10 76 4.9. text/javascript1.2 . . . . . . . . . . . . . . . . . . . 11 77 4.10. text/javascript1.3 . . . . . . . . . . . . . . . . . . . 12 78 4.11. text/javascript1.4 . . . . . . . . . . . . . . . . . . . 13 79 4.12. text/javascript1.5 . . . . . . . . . . . . . . . . . . . 14 80 4.13. text/jscript . . . . . . . . . . . . . . . . . . . . . . 15 81 4.14. text/livescript . . . . . . . . . . . . . . . . . . . . . 16 82 4.15. text/x-ecmascript . . . . . . . . . . . . . . . . . . . . 17 83 4.16. text/x-javascript . . . . . . . . . . . . . . . . . . . . 18 84 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 85 5.1. Normative References . . . . . . . . . . . . . . . . . . 19 86 5.2. Informative References . . . . . . . . . . . . . . . . . 20 87 5.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 20 88 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 20 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 91 1. Introduction 93 This document updates the existing media types for the ECMAScript 94 programming language. It supersedes the media types registrations in 95 [RFC4329] for "application/javascript" and "text/javascript". 97 2. Background 99 In order to formalize support for modular programs [ECMA-262] now 100 defines two top-level goal symbols for the ECMAScript grammar. This 101 means that (in the absence of additional information) there are two 102 possible interpretations for any given ECMAScript Source Text. The 103 TC39 standards body for ECMAScript has determined that media types 104 are outside of their scope of work [TC39-MIME-ISSUE]. 106 It is not possible to fully determine if a Source Text of ECMAScript 107 is meant to be parsed in the Module or Script grammar goals based 108 upon content alone. Therefore, scripting environments must use out 109 of band information in order to determine what goal a Source Text 110 should be treated as. To this end some scripting environments have 111 chosen to adopt a new file extension of .mjs for determining the goal 112 of a given Source Text. 114 3. Notational Conventions 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in [RFC2119]. 120 4. Registration 122 The ECMAScript media types are to be updated to point to a non-vendor 123 specific standard undated specification of ECMAScript. In addition, 124 a new file extension of .mjs is to be added to the list of file 125 extensions with the restriction that it must correspond to the Module 126 grammar of [ECMA-262]. Finally, the [HTML] specification is using 127 text/javascript as the default media type of ECMAScript when 128 preparing script tags; therefore, text/javascript has been moved 129 intended usage from OBSOLETE to COMMON. 131 4.1. appliaction/ecmascript 133 Type name: application 135 Subtype name: ecmascript 137 Required parameters: none 138 Optional parameters: charset, see section 4.1 of [RFC4329]. 140 goal, declares the goal symbol within [ECMA-262] to be used while 141 parsing. 143 Encoding considerations: Encoding is host dependent with differences 144 in byte order marks, the charset parameter, and text 145 preprocessing. 147 Security considerations: See section 5 of [RFC4329]. 149 Interoperability considerations: See notes in various sections of 150 [RFC4329]. This media type does not specify the grammar of 151 [ECMA-262] used when missing the goal parameter. 153 Published specification: [[RFCXXXX]] 155 Applications which use this media type: Script interpreters as 156 discussed in [RFC4329]. 158 Additional information: 160 Magic number(s): n/a 162 File extension(s): .js, .mjs 164 Macintosh File Type Code(s): TEXT 166 Person & email address to contact for further information: See 167 Author's Address section. 169 Intended usage: OBSOLETE 171 Restrictions on usage: The file extension .mjs must be parsed using 172 the Module grammar of [ECMA-262] 174 Author: See Author's Address section. 176 Change controller: IESG 178 4.2. application/javascript 180 Type name: application 182 Subtype name: javascript 184 Required parameters: none 185 Optional parameters: charset, see section 4.1 of [RFC4329]. 187 goal, declares the goal symbol within [ECMA-262] to be used while 188 parsing. 190 Encoding considerations: Encoding is host dependent with differences 191 in byte order marks, the charset parameter, and text 192 preprocessing. 194 Security considerations: See section 5 of [RFC4329]. 196 Interoperability considerations: See notes in various sections of 197 [RFC4329]. This media type does not specify the grammar of 198 [ECMA-262] used when missing the goal parameter. 200 Published specification: [[RFCXXXX]] 202 Applications which use this media type: Script interpreters as 203 discussed in [RFC4329]. 205 Additional information: 207 Magic number(s): n/a 209 File extension(s): .js, .mjs 211 Macintosh File Type Code(s): TEXT 213 Person & email address to contact for further information: See 214 Author's Address section. 216 Intended usage: OBSOLETE 218 Restrictions on usage: The file extension .mjs must be parsed using 219 the Module grammar of [ECMA-262] 221 Author: See Author's Address section. 223 Change controller: IESG . 225 4.3. application/x-ecmascript 227 Type name: application 229 Subtype name: x-ecmascript 231 Required parameters: none 232 Optional parameters: charset, see section 4.1 of [RFC4329]. 234 goal, declares the goal symbol within [ECMA-262] to be used while 235 parsing. 237 Encoding considerations: Encoding is host dependent with differences 238 in byte order marks, the charset parameter, and text 239 preprocessing. 241 Security considerations: See section 5 of [RFC4329]. 243 Interoperability considerations: See notes in various sections of 244 [RFC4329]. This media type does not specify the grammar of 245 [ECMA-262] used when missing the goal parameter. 247 Published specification: [[RFCXXXX]] 249 Applications which use this media type: Script interpreters as 250 discussed in [RFC4329]. 252 Additional information: 254 Magic number(s): n/a 256 File extension(s): .js, .mjs 258 Macintosh File Type Code(s): TEXT 260 Person & email address to contact for further information: See 261 Author's Address section. 263 Intended usage: OBSOLETE 265 Restrictions on usage: The file extension .mjs must be parsed using 266 the Module grammar of [ECMA-262] 268 Author: See Author's Address section. 270 Change controller: IESG 272 4.4. application/x-javascript 274 Type name: application 276 Subtype name: x-javascript 278 Required parameters: none 279 Optional parameters: charset, see section 4.1 of [RFC4329]. 281 goal, declares the goal symbol within [ECMA-262] to be used while 282 parsing. 284 Encoding considerations: Encoding is host dependent with differences 285 in byte order marks, the charset parameter, and text 286 preprocessing. 288 Security considerations: See section 5 of [RFC4329]. 290 Interoperability considerations: See notes in various sections of 291 [RFC4329]. This media type does not specify the grammar of 292 [ECMA-262] used when missing the goal parameter. 294 Published specification: [[RFCXXXX]] 296 Applications which use this media type: Script interpreters as 297 discussed in [RFC4329]. 299 Additional information: 301 Magic number(s): n/a 303 File extension(s): .js, .mjs 305 Macintosh File Type Code(s): TEXT 307 Person & email address to contact for further information: See 308 Author's Address section. 310 Intended usage: OBSOLETE 312 Restrictions on usage: The file extension .mjs must be parsed using 313 the Module grammar of [ECMA-262] 315 Author: See Author's Address section. 317 Change controller: IESG 319 4.5. text/ecmascript 321 Type name: text 323 Subtype name: ecmascript 325 Required parameters: none 326 Optional parameters: charset, see section 4.1 of [RFC4329]. 328 goal, declares the goal symbol within [ECMA-262] to be used while 329 parsing. 331 Encoding considerations: Encoding is host dependent with differences 332 in byte order marks, the charset parameter, and text 333 preprocessing. 335 Security considerations: See section 5 of [RFC4329]. 337 Interoperability considerations: See notes in various sections of 338 [RFC4329]. This media type does not specify the grammar of 339 [ECMA-262] used when missing the goal parameter. 341 Published specification: [[RFCXXXX]] 343 Applications which use this media type: Script interpreters as 344 discussed in [RFC4329]. 346 Additional information: 348 Magic number(s): n/a 350 File extension(s): .js, .mjs 352 Macintosh File Type Code(s): TEXT 354 Person & email address to contact for further information: See 355 Author's Address section. 357 Intended usage: OBSOLETE 359 Restrictions on usage: The file extension .mjs must be parsed using 360 the Module grammar of [ECMA-262] 362 Author: See Author's Address section. 364 Change controller: IESG 366 4.6. text/javascript 368 Type name: text 370 Subtype name: javascript 372 Required parameters: none 373 Optional parameters: charset, see section 4.1 of [RFC4329]. 375 goal, declares the goal symbol within [ECMA-262] to be used while 376 parsing. 378 Encoding considerations: Encoding is host dependent with differences 379 in byte order marks, the charset parameter, and text 380 preprocessing. 382 Security considerations: See section 5 of [RFC4329]. 384 Interoperability considerations: See notes in various sections of 385 [RFC4329]. This media type does not specify the grammar of 386 [ECMA-262] used when missing the goal parameter. 388 Published specification: [[RFCXXXX]] 390 Applications which use this media type: Script interpreters as 391 discussed in [RFC4329]. 393 Additional information: 395 Magic number(s): n/a 397 File extension(s): .js, .mjs 399 Macintosh File Type Code(s): TEXT 401 Person & email address to contact for further information: See 402 Author's Address section. 404 Intended usage: COMMON 406 Restrictions on usage: The file extension .mjs must be parsed using 407 the Module grammar of [ECMA-262] 409 Author: See Author's Address section. 411 Change controller: IESG 413 4.7. text/javascript1.0 415 Type name: text 417 Subtype name: javascript1.0 419 Required parameters: none 420 Optional parameters: charset, see section 4.1 of [RFC4329]. 422 goal, declares the goal symbol within [ECMA-262] to be used while 423 parsing. 425 Encoding considerations: Encoding is host dependent with differences 426 in byte order marks, the charset parameter, and text 427 preprocessing. 429 Security considerations: See section 5 of [RFC4329]. 431 Interoperability considerations: See notes in various sections of 432 [RFC4329]. This media type does not specify the grammar of 433 [ECMA-262] used when missing the goal parameter. 435 Published specification: [[RFCXXXX]] 437 Applications which use this media type: Script interpreters as 438 discussed in [RFC4329]. 440 Additional information: 442 Magic number(s): n/a 444 File extension(s): .js, .mjs 446 Macintosh File Type Code(s): TEXT 448 Person & email address to contact for further information: See 449 Author's Address section. 451 Intended usage: OBSOLETE 453 Restrictions on usage: The file extension .mjs must be parsed using 454 the Module grammar of [ECMA-262] 456 Author: See Author's Address section. 458 Change controller: IESG 460 4.8. text/javascript1.1 462 Type name: text 464 Subtype name: javascript1.1 466 Required parameters: none 467 Optional parameters: charset, see section 4.1 of [RFC4329]. 469 goal, declares the goal symbol within [ECMA-262] to be used while 470 parsing. 472 Encoding considerations: Encoding is host dependent with differences 473 in byte order marks, the charset parameter, and text 474 preprocessing. 476 Security considerations: See section 5 of [RFC4329]. 478 Interoperability considerations: See notes in various sections of 479 [RFC4329]. This media type does not specify the grammar of 480 [ECMA-262] used when missing the goal parameter. 482 Published specification: [[RFCXXXX]] 484 Applications which use this media type: Script interpreters as 485 discussed in [RFC4329]. 487 Additional information: 489 Magic number(s): n/a 491 File extension(s): .js, .mjs 493 Macintosh File Type Code(s): TEXT 495 Person & email address to contact for further information: See 496 Author's Address section. 498 Intended usage: OBSOLETE 500 Restrictions on usage: The file extension .mjs must be parsed using 501 the Module grammar of [ECMA-262] 503 Author: See Author's Address section. 505 Change controller: IESG 507 4.9. text/javascript1.2 509 Type name: text 511 Subtype name: javascript1.2 513 Required parameters: none 514 Optional parameters: charset, see section 4.1 of [RFC4329]. 516 goal, declares the goal symbol within [ECMA-262] to be used while 517 parsing. 519 Encoding considerations: Encoding is host dependent with differences 520 in byte order marks, the charset parameter, and text 521 preprocessing. 523 Security considerations: See section 5 of [RFC4329]. 525 Interoperability considerations: See notes in various sections of 526 [RFC4329]. This media type does not specify the grammar of 527 [ECMA-262] used when missing the goal parameter. 529 Published specification: [[RFCXXXX]] 531 Applications which use this media type: Script interpreters as 532 discussed in [RFC4329]. 534 Additional information: 536 Magic number(s): n/a 538 File extension(s): .js, .mjs 540 Macintosh File Type Code(s): TEXT 542 Person & email address to contact for further information: See 543 Author's Address section. 545 Intended usage: OBSOLETE 547 Restrictions on usage: The file extension .mjs must be parsed using 548 the Module grammar of [ECMA-262] 550 Author: See Author's Address section. 552 Change controller: IESG 554 4.10. text/javascript1.3 556 Type name: text 558 Subtype name: javascript1.3 560 Required parameters: none 561 Optional parameters: charset, see section 4.1 of [RFC4329]. 563 goal, declares the goal symbol within [ECMA-262] to be used while 564 parsing. 566 Encoding considerations: Encoding is host dependent with differences 567 in byte order marks, the charset parameter, and text 568 preprocessing. 570 Security considerations: See section 5 of [RFC4329]. 572 Interoperability considerations: See notes in various sections of 573 [RFC4329]. This media type does not specify the grammar of 574 [ECMA-262] used when missing the goal parameter. 576 Published specification: [[RFCXXXX]] 578 Applications which use this media type: Script interpreters as 579 discussed in [RFC4329]. 581 Additional information: 583 Magic number(s): n/a 585 File extension(s): .js, .mjs 587 Macintosh File Type Code(s): TEXT 589 Person & email address to contact for further information: See 590 Author's Address section. 592 Intended usage: OBSOLETE 594 Restrictions on usage: The file extension .mjs must be parsed using 595 the Module grammar of [ECMA-262] 597 Author: See Author's Address section. 599 Change controller: IESG 601 4.11. text/javascript1.4 603 Type name: text 605 Subtype name: javascript1.4 607 Required parameters: none 608 Optional parameters: charset, see section 4.1 of [RFC4329]. 610 goal, declares the goal symbol within [ECMA-262] to be used while 611 parsing. 613 Encoding considerations: Encoding is host dependent with differences 614 in byte order marks, the charset parameter, and text 615 preprocessing. 617 Security considerations: See section 5 of [RFC4329]. 619 Interoperability considerations: See notes in various sections of 620 [RFC4329]. This media type does not specify the grammar of 621 [ECMA-262] used when missing the goal parameter. 623 Published specification: [[RFCXXXX]] 625 Applications which use this media type: Script interpreters as 626 discussed in [RFC4329]. 628 Additional information: 630 Magic number(s): n/a 632 File extension(s): .js, .mjs 634 Macintosh File Type Code(s): TEXT 636 Person & email address to contact for further information: See 637 Author's Address section. 639 Intended usage: OBSOLETE 641 Restrictions on usage: The file extension .mjs must be parsed using 642 the Module grammar of [ECMA-262] 644 Author: See Author's Address section. 646 Change controller: IESG 648 4.12. text/javascript1.5 650 Type name: text 652 Subtype name: javascript1.5 654 Required parameters: none 655 Optional parameters: charset, see section 4.1 of [RFC4329]. 657 goal, declares the goal symbol within [ECMA-262] to be used while 658 parsing. 660 Encoding considerations: Encoding is host dependent with differences 661 in byte order marks, the charset parameter, and text 662 preprocessing. 664 Security considerations: See section 5 of [RFC4329]. 666 Interoperability considerations: See notes in various sections of 667 [RFC4329]. This media type does not specify the grammar of 668 [ECMA-262] used when missing the goal parameter. 670 Published specification: [[RFCXXXX]] 672 Applications which use this media type: Script interpreters as 673 discussed in [RFC4329]. 675 Additional information: 677 Magic number(s): n/a 679 File extension(s): .js, .mjs 681 Macintosh File Type Code(s): TEXT 683 Person & email address to contact for further information: See 684 Author's Address section. 686 Intended usage: OBSOLETE 688 Restrictions on usage: The file extension .mjs must be parsed using 689 the Module grammar of [ECMA-262] 691 Author: See Author's Address section. 693 Change controller: IESG 695 4.13. text/jscript 697 Type name: text 699 Subtype name: jscript 701 Required parameters: none 702 Optional parameters: charset, see section 4.1 of [RFC4329]. 704 goal, declares the goal symbol within [ECMA-262] to be used while 705 parsing. 707 Encoding considerations: Encoding is host dependent with differences 708 in byte order marks, the charset parameter, and text 709 preprocessing. 711 Security considerations: See section 5 of [RFC4329]. 713 Interoperability considerations: See notes in various sections of 714 [RFC4329]. This media type does not specify the grammar of 715 [ECMA-262] used when missing the goal parameter. 717 Published specification: [[RFCXXXX]] 719 Applications which use this media type: Script interpreters as 720 discussed in [RFC4329]. 722 Additional information: 724 Magic number(s): n/a 726 File extension(s): .js, .mjs 728 Macintosh File Type Code(s): TEXT 730 Person & email address to contact for further information: See 731 Author's Address section. 733 Intended usage: OBSOLETE 735 Restrictions on usage: The file extension .mjs must be parsed using 736 the Module grammar of [ECMA-262] 738 Author: See Author's Address section. 740 Change controller: IESG 742 4.14. text/livescript 744 Type name: text 746 Subtype name: livescript 748 Required parameters: none 749 Optional parameters: charset, see section 4.1 of [RFC4329]. 751 goal, declares the goal symbol within [ECMA-262] to be used while 752 parsing. 754 Encoding considerations: Encoding is host dependent with differences 755 in byte order marks, the charset parameter, and text 756 preprocessing. 758 Security considerations: See section 5 of [RFC4329]. 760 Interoperability considerations: See notes in various sections of 761 [RFC4329]. This media type does not specify the grammar of 762 [ECMA-262] used when missing the goal parameter. 764 Published specification: [[RFCXXXX]] 766 Applications which use this media type: Script interpreters as 767 discussed in [RFC4329]. 769 Additional information: 771 Magic number(s): n/a 773 File extension(s): .js, .mjs 775 Macintosh File Type Code(s): TEXT 777 Person & email address to contact for further information: See 778 Author's Address section. 780 Intended usage: OBSOLETE 782 Restrictions on usage: The file extension .mjs must be parsed using 783 the Module grammar of [ECMA-262] 785 Author: See Author's Address section. 787 Change controller: IESG 789 4.15. text/x-ecmascript 791 Type name: text 793 Subtype name: x-ecmascript 795 Required parameters: none 796 Optional parameters: charset, see section 4.1 of [RFC4329]. 798 goal, declares the goal symbol within [ECMA-262] to be used while 799 parsing. 801 Encoding considerations: Encoding is host dependent with differences 802 in byte order marks, the charset parameter, and text 803 preprocessing. 805 Security considerations: See section 5 of [RFC4329]. 807 Interoperability considerations: See notes in various sections of 808 [RFC4329]. This media type does not specify the grammar of 809 [ECMA-262] used when missing the goal parameter. 811 Published specification: [[RFCXXXX]] 813 Applications which use this media type: Script interpreters as 814 discussed in [RFC4329]. 816 Additional information: 818 Magic number(s): n/a 820 File extension(s): .js, .mjs 822 Macintosh File Type Code(s): TEXT 824 Person & email address to contact for further information: See 825 Author's Address section. 827 Intended usage: OBSOLETE 829 Restrictions on usage: The file extension .mjs must be parsed using 830 the Module grammar of [ECMA-262] 832 Author: See Author's Address section. 834 Change controller: IESG 836 4.16. text/x-javascript 838 Type name: text 840 Subtype name: x-javascript 842 Required parameters: none 843 Optional parameters: charset, see section 4.1 of [RFC4329]. 845 goal, declares the goal symbol within [ECMA-262] to be used while 846 parsing. 848 Encoding considerations: Encoding is host dependent with differences 849 in byte order marks, the charset parameter, and text 850 preprocessing. 852 Security considerations: See section 5 of [RFC4329]. 854 Interoperability considerations: See notes in various sections of 855 [RFC4329]. This media type does not specify the grammar of 856 [ECMA-262] used when missing the goal parameter. 858 Published specification: [[RFCXXXX]] 860 Applications which use this media type: Script interpreters as 861 discussed in [RFC4329]. 863 Additional information: 865 Magic number(s): n/a 867 File extension(s): .js, .mjs 869 Macintosh File Type Code(s): TEXT 871 Person & email address to contact for further information: See 872 Author's Address section. 874 Intended usage: OBSOLETE 876 Restrictions on usage: The file extension .mjs must be parsed using 877 the Module grammar of [ECMA-262] 879 Author: See Author's Address section. 881 Change controller: IESG 883 5. References 885 5.1. Normative References 887 [ECMA-262] 888 Ecma International, "Standard ECMA-262: ECMAScript 889 Language Specification", August 2017, . 892 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 893 Requirement Levels", BCP 14, RFC 2119, 894 DOI 10.17487/RFC2119, March 1997, 895 . 897 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 898 Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, 899 . 901 [RFC4329] Hoehrmann, B., "Scripting Media Types", RFC 4329, 902 DOI 10.17487/RFC4329, April 2006, 903 . 905 5.2. Informative References 907 [HTML] WHATWG, "HTML Living Standard", August 2017, 908 . 911 [TC39-MIME-ISSUE] 912 TC39, "Add `application/javascript+module` mime to remove 913 ambiguity5", August 2017, . 916 5.3. URIs 918 [1] https://github.com/bmeck/I-D/labels/javascript-mjs 920 [2] https://github.com/bmeck/I-D/tree/master/javascript-mjs 922 [3] https://github.com/bmeck/I-D/commits/master/javascript-mjs 924 Appendix A. Acknowledgements 926 Thanks to Suresh Krishnan, Alexey Melnikov, Mark Nottingham, James 927 Snell, Matthew A. Miller, Adam Roach, and Allen Wirfs-Brock for 928 guiding me through this process. 930 Authors' Addresses 932 Bradley Farias 934 Email: bradley.meck@gmail.com 935 Matthew A. Miller 936 Mozilla 938 Email: linuxwolf+ietf@outer-planes.net