idnits 2.17.1 draft-ietf-dispatch-javascript-mjs-03.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 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 (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 (February 22, 2019) is 1887 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 967 -- Looks like a reference, but probably isn't: '2' on line 969 -- Looks like a reference, but probably isn't: '3' on line 971 ** Obsolete normative reference: RFC 4329 (Obsoleted by RFC 9239) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 5 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: August 26, 2019 Mozilla 7 B. Farias 8 February 22, 2019 10 ECMAScript Media Types Updates 11 draft-ietf-dispatch-javascript-mjs-03 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 Note to Readers 23 The issues list for this draft can be found at 24 https://github.com/bmeck/I-D/labels/javascript-mjs [1]. 26 The most recent (often, unpublished) draft is at 27 https://github.com/bmeck/I-D/tree/master/javascript-mjs [2]. 29 Recent changes are listed at https://github.com/bmeck/I- 30 D/commits/master/javascript-mjs [3]. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at https://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on August 26, 2019. 49 Copyright Notice 51 Copyright (c) 2019 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (https://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 69 3.1. Common Javascript Media Types . . . . . . . . . . . . . . 3 70 3.1.1. text/javascript . . . . . . . . . . . . . . . . . . . 3 71 3.2. Historic Javascript Media Types . . . . . . . . . . . . . 4 72 3.2.1. application/ecmascript . . . . . . . . . . . . . . . 5 73 3.2.2. application/javascript . . . . . . . . . . . . . . . 6 74 3.2.3. application/x-ecmascript . . . . . . . . . . . . . . 7 75 3.2.4. application/x-javascript . . . . . . . . . . . . . . 8 76 3.2.5. text/ecmascript . . . . . . . . . . . . . . . . . . . 9 77 3.2.6. text/javascript1.0 . . . . . . . . . . . . . . . . . 10 78 3.2.7. text/javascript1.1 . . . . . . . . . . . . . . . . . 11 79 3.2.8. text/javascript1.2 . . . . . . . . . . . . . . . . . 12 80 3.2.9. text/javascript1.3 . . . . . . . . . . . . . . . . . 13 81 3.2.10. text/javascript1.4 . . . . . . . . . . . . . . . . . 14 82 3.2.11. text/javascript1.5 . . . . . . . . . . . . . . . . . 15 83 3.2.12. text/jscript . . . . . . . . . . . . . . . . . . . . 16 84 3.2.13. text/livescript . . . . . . . . . . . . . . . . . . . 17 85 3.2.14. text/x-ecmascript . . . . . . . . . . . . . . . . . . 18 86 3.2.15. text/x-javascript . . . . . . . . . . . . . . . . . . 19 87 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 88 4.1. Normative References . . . . . . . . . . . . . . . . . . 20 89 4.2. Informative References . . . . . . . . . . . . . . . . . 20 90 4.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 21 91 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 21 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 94 1. Introduction 96 This document updates the existing media types for the ECMAScript 97 programming language. It supersedes the media types registrations in 98 [RFC4329] for "application/javascript" and "text/javascript". 100 2. Background 102 In order to formalize support for modular programs [ECMA-262] now 103 defines two top-level goal symbols for the ECMAScript grammar. This 104 means that (in the absence of additional information) there are two 105 possible interpretations for any given ECMAScript Source Text. The 106 TC39 standards body for ECMAScript has determined that media types 107 are outside of their scope of work [TC39-MIME-ISSUE]. 109 It is not possible to fully determine if a Source Text of ECMAScript 110 is meant to be parsed in the Module or Script grammar goals based 111 upon content alone. Therefore, scripting environments must use out 112 of band information in order to determine what goal a Source Text 113 should be treated as. To this end some scripting environments have 114 chosen to adopt a new file extension of .mjs for determining the goal 115 of a given Source Text. 117 3. IANA Considerations 119 The media type registrations herein are divided into two major 120 categories: the sole media type "text/javascript" which is now in 121 common usage, and all of the media types that are obsolete. 123 For both categories, The ECMAScript media types are to be updated to 124 point to a non-vendor specific standard undated specification of 125 ECMAScript. In addition, a new file extension of .mjs is to be added 126 to the list of file extensions with the restriction that it must 127 correspond to the Module grammar of [ECMA-262]. Finally, the [HTML] 128 specification is using "text/javascript" as the default media type of 129 ECMAScript when preparing script tags; therefore, "text/javascript" 130 has been moved intended usage from OBSOLETE to COMMON. 132 3.1. Common Javascript Media Types 134 3.1.1. text/javascript 136 Type name: text 138 Subtype name: javascript 140 Required parameters: none 141 Optional parameters: charset, see section 4.1 of [RFC4329]. 143 goal, declares the goal symbol in the Syntactic Grammars of 144 [ECMA-262] to be used while parsing. This parameter is case 145 insensitive. 147 Encoding considerations: Encoding is host dependent with differences 148 in byte order marks, the charset parameter, and text 149 preprocessing. 151 Security considerations: See section 5 of [RFC4329]. 153 Interoperability considerations: See notes in various sections of 154 [RFC4329]. This media type does not specify the grammar of 155 [ECMA-262] used when missing the goal parameter. 157 Published specification: [[RFCXXXX]] 159 Applications which use this media type: Script interpreters as 160 discussed in [RFC4329]. 162 Additional information: 164 Magic number(s): n/a 166 File extension(s): .js, .mjs 168 Macintosh File Type Code(s): TEXT 170 Person & email address to contact for further information: See 171 Author's Address section. 173 Intended usage: COMMON 175 Restrictions on usage: The file extension .mjs must be parsed using 176 the Module grammar of [ECMA-262] 178 Author: See Author's Address section. 180 Change controller: IESG 182 3.2. Historic Javascript Media Types 184 The following media types are added or updated for historical 185 purposes. All herein have an intended usage of OBSOLETE, and are not 186 expected to be in use with modern implementations. 188 3.2.1. application/ecmascript 190 Type name: application 192 Subtype name: ecmascript 194 Required parameters: none 196 Optional parameters: charset, see section 4.1 of [RFC4329]. 198 goal, declares the goal symbol in the Syntactic Grammars of 199 [ECMA-262] to be used while parsing. This parameter is case 200 insensitive. 202 Encoding considerations: Encoding is host dependent with differences 203 in byte order marks, the charset parameter, and text 204 preprocessing. 206 Security considerations: See section 5 of [RFC4329]. 208 Interoperability considerations: See notes in various sections of 209 [RFC4329]. This media type does not specify the grammar of 210 [ECMA-262] used when missing the goal parameter. 212 Published specification: [[RFCXXXX]] 214 Applications which use this media type: Script interpreters as 215 discussed in [RFC4329]. 217 Additional information: 219 Magic number(s): n/a 221 File extension(s): .es, .mjs 223 Macintosh File Type Code(s): TEXT 225 Person & email address to contact for further information: See 226 Author's Address section. 228 Intended usage: OBSOLETE 230 Restrictions on usage: This media type is obsolete; current 231 implementations should use text/javascript as the only javascript/ 232 ECMAscript media type. The file extension .mjs must be parsed 233 using the Module grammar of [ECMA-262] 235 Author: See Author's Address section. 237 Change controller: IESG 239 3.2.2. application/javascript 241 Type name: application 243 Subtype name: javascript 245 Required parameters: none 247 Optional parameters: charset, see section 4.1 of [RFC4329]. 249 goal, declares the goal symbol in the Syntactic Grammars of 250 [ECMA-262] to be used while parsing. This parameter is case 251 insensitive. 253 Encoding considerations: Encoding is host dependent with differences 254 in byte order marks, the charset parameter, and text 255 preprocessing. 257 Security considerations: See section 5 of [RFC4329]. 259 Interoperability considerations: See notes in various sections of 260 [RFC4329]. This media type does not specify the grammar of 261 [ECMA-262] used when missing the goal parameter. 263 Published specification: [[RFCXXXX]] 265 Applications which use this media type: Script interpreters as 266 discussed in [RFC4329]. 268 Additional information: 270 Magic number(s): n/a 272 File extension(s): .js, .mjs 274 Macintosh File Type Code(s): TEXT 276 Person & email address to contact for further information: See 277 Author's Address section. 279 Intended usage: OBSOLETE 281 Restrictions on usage: This media type is obsolete; current 282 implementations should use text/javascript as the only javascript/ 283 ECMAscript media type. The file extension .mjs must be parsed 284 using the Module grammar of [ECMA-262] 286 Author: See Author's Address section. 288 Change controller: IESG . 290 3.2.3. application/x-ecmascript 292 Type name: application 294 Subtype name: x-ecmascript 296 Required parameters: none 298 Optional parameters: charset, see section 4.1 of [RFC4329]. 300 goal, declares the goal symbol in the Syntactic Grammars of 301 [ECMA-262] to be used while parsing. This parameter is case 302 insensitive. 304 Encoding considerations: Encoding is host dependent with differences 305 in byte order marks, the charset parameter, and text 306 preprocessing. 308 Security considerations: See section 5 of [RFC4329]. 310 Interoperability considerations: See notes in various sections of 311 [RFC4329]. This media type does not specify the grammar of 312 [ECMA-262] used when missing the goal parameter. 314 Published specification: [[RFCXXXX]] 316 Applications which use this media type: Script interpreters as 317 discussed in [RFC4329]. 319 Additional information: 321 Magic number(s): n/a 323 File extension(s): .es, .mjs 325 Macintosh File Type Code(s): TEXT 327 Person & email address to contact for further information: See 328 Author's Address section. 330 Intended usage: OBSOLETE 332 Restrictions on usage: This media type is obsolete; current 333 implementations should use text/javascript as the only javascript/ 334 ECMAscript media type. The file extension .mjs must be parsed 335 using the Module grammar of [ECMA-262] 337 Author: See Author's Address section. 339 Change controller: IESG 341 3.2.4. application/x-javascript 343 Type name: application 345 Subtype name: x-javascript 347 Required parameters: none 349 Optional parameters: charset, see section 4.1 of [RFC4329]. 351 goal, declares the goal symbol in the Syntactic Grammars of 352 [ECMA-262] to be used while parsing. This parameter is case 353 insensitive. 355 Encoding considerations: Encoding is host dependent with differences 356 in byte order marks, the charset parameter, and text 357 preprocessing. 359 Security considerations: See section 5 of [RFC4329]. 361 Interoperability considerations: See notes in various sections of 362 [RFC4329]. This media type does not specify the grammar of 363 [ECMA-262] used when missing the goal parameter. 365 Published specification: [[RFCXXXX]] 367 Applications which use this media type: Script interpreters as 368 discussed in [RFC4329]. 370 Additional information: 372 Magic number(s): n/a 374 File extension(s): .js, .mjs 376 Macintosh File Type Code(s): TEXT 378 Person & email address to contact for further information: See 379 Author's Address section. 381 Intended usage: OBSOLETE 382 Restrictions on usage: This media type is obsolete; current 383 implementations should use text/javascript as the only javascript/ 384 ECMAscript media type. The file extension .mjs must be parsed 385 using the Module grammar of [ECMA-262] 387 Author: See Author's Address section. 389 Change controller: IESG 391 3.2.5. text/ecmascript 393 Type name: text 395 Subtype name: ecmascript 397 Required parameters: none 399 Optional parameters: charset, see section 4.1 of [RFC4329]. 401 goal, declares the goal symbol in the Syntactic Grammars of 402 [ECMA-262] to be used while parsing. This parameter is case 403 insensitive. 405 Encoding considerations: Encoding is host dependent with differences 406 in byte order marks, the charset parameter, and text 407 preprocessing. 409 Security considerations: See section 5 of [RFC4329]. 411 Interoperability considerations: See notes in various sections of 412 [RFC4329]. This media type does not specify the grammar of 413 [ECMA-262] used when missing the goal parameter. 415 Published specification: [[RFCXXXX]] 417 Applications which use this media type: Script interpreters as 418 discussed in [RFC4329]. 420 Additional information: 422 Magic number(s): n/a 424 File extension(s): .es, .mjs 426 Macintosh File Type Code(s): TEXT 428 Person & email address to contact for further information: See 429 Author's Address section. 431 Intended usage: OBSOLETE 433 Restrictions on usage: This media type is obsolete; current 434 implementations should use text/javascript as the only javascript/ 435 ECMAscript media type. The file extension .mjs must be parsed 436 using the Module grammar of [ECMA-262] 438 Author: See Author's Address section. 440 Change controller: IESG 442 3.2.6. text/javascript1.0 444 Type name: text 446 Subtype name: javascript1.0 448 Required parameters: none 450 Optional parameters: charset, see section 4.1 of [RFC4329]. 452 goal, declares the goal symbol in the Syntactic Grammars of 453 [ECMA-262] to be used while parsing. This parameter is case 454 insensitive. 456 Encoding considerations: Encoding is host dependent with differences 457 in byte order marks, the charset parameter, and text 458 preprocessing. 460 Security considerations: See section 5 of [RFC4329]. 462 Interoperability considerations: See notes in various sections of 463 [RFC4329]. This media type does not specify the grammar of 464 [ECMA-262] used when missing the goal parameter. 466 Published specification: [[RFCXXXX]] 468 Applications which use this media type: Script interpreters as 469 discussed in [RFC4329]. 471 Additional information: 473 Magic number(s): n/a 475 File extension(s): .js, .mjs 477 Macintosh File Type Code(s): TEXT 479 Person & email address to contact for further information: See 480 Author's Address section. 482 Intended usage: OBSOLETE 484 Restrictions on usage: This media type is obsolete; current 485 implementations should use text/javascript as the only javascript/ 486 ECMAscript media type. The file extension .mjs must be parsed 487 using the Module grammar of [ECMA-262] 489 Author: See Author's Address section. 491 Change controller: IESG 493 3.2.7. text/javascript1.1 495 Type name: text 497 Subtype name: javascript1.1 499 Required parameters: none 501 Optional parameters: charset, see section 4.1 of [RFC4329]. 503 goal, declares the goal symbol in the Syntactic Grammars of 504 [ECMA-262] to be used while parsing. This parameter is case 505 insensitive. 507 Encoding considerations: Encoding is host dependent with differences 508 in byte order marks, the charset parameter, and text 509 preprocessing. 511 Security considerations: See section 5 of [RFC4329]. 513 Interoperability considerations: See notes in various sections of 514 [RFC4329]. This media type does not specify the grammar of 515 [ECMA-262] used when missing the goal parameter. 517 Published specification: [[RFCXXXX]] 519 Applications which use this media type: Script interpreters as 520 discussed in [RFC4329]. 522 Additional information: 524 Magic number(s): n/a 526 File extension(s): .js, .mjs 527 Macintosh File Type Code(s): TEXT 529 Person & email address to contact for further information: See 530 Author's Address section. 532 Intended usage: OBSOLETE 534 Restrictions on usage: This media type is obsolete; current 535 implementations should use text/javascript as the only javascript/ 536 ECMAscript media type. The file extension .mjs must be parsed 537 using the Module grammar of [ECMA-262] 539 Author: See Author's Address section. 541 Change controller: IESG 543 3.2.8. text/javascript1.2 545 Type name: text 547 Subtype name: javascript1.2 549 Required parameters: none 551 Optional parameters: charset, see section 4.1 of [RFC4329]. 553 goal, declares the goal symbol in the Syntactic Grammars of 554 [ECMA-262] to be used while parsing. This parameter is case 555 insensitive. 557 Encoding considerations: Encoding is host dependent with differences 558 in byte order marks, the charset parameter, and text 559 preprocessing. 561 Security considerations: See section 5 of [RFC4329]. 563 Interoperability considerations: See notes in various sections of 564 [RFC4329]. This media type does not specify the grammar of 565 [ECMA-262] used when missing the goal parameter. 567 Published specification: [[RFCXXXX]] 569 Applications which use this media type: Script interpreters as 570 discussed in [RFC4329]. 572 Additional information: 574 Magic number(s): n/a 575 File extension(s): .js, .mjs 577 Macintosh File Type Code(s): TEXT 579 Person & email address to contact for further information: See 580 Author's Address section. 582 Intended usage: OBSOLETE 584 Restrictions on usage: This media type is obsolete; current 585 implementations should use text/javascript as the only javascript/ 586 ECMAscript media type. The file extension .mjs must be parsed 587 using the Module grammar of [ECMA-262] 589 Author: See Author's Address section. 591 Change controller: IESG 593 3.2.9. text/javascript1.3 595 Type name: text 597 Subtype name: javascript1.3 599 Required parameters: none 601 Optional parameters: charset, see section 4.1 of [RFC4329]. 603 goal, declares the goal symbol in the Syntactic Grammars of 604 [ECMA-262] to be used while parsing. This parameter is case 605 insensitive. 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]. This media type does not specify the grammar of 615 [ECMA-262] used when missing the goal parameter. 617 Published specification: [[RFCXXXX]] 619 Applications which use this media type: Script interpreters as 620 discussed in [RFC4329]. 622 Additional information: 624 Magic number(s): n/a 626 File extension(s): .js, .mjs 628 Macintosh File Type Code(s): TEXT 630 Person & email address to contact for further information: See 631 Author's Address section. 633 Intended usage: OBSOLETE 635 Restrictions on usage: This media type is obsolete; current 636 implementations should use text/javascript as the only javascript/ 637 ECMAscript media type. The file extension .mjs must be parsed 638 using the Module grammar of [ECMA-262] 640 Author: See Author's Address section. 642 Change controller: IESG 644 3.2.10. text/javascript1.4 646 Type name: text 648 Subtype name: javascript1.4 650 Required parameters: none 652 Optional parameters: charset, see section 4.1 of [RFC4329]. 654 goal, declares the goal symbol in the Syntactic Grammars of 655 [ECMA-262] to be used while parsing. This parameter is case 656 insensitive. 658 Encoding considerations: Encoding is host dependent with differences 659 in byte order marks, the charset parameter, and text 660 preprocessing. 662 Security considerations: See section 5 of [RFC4329]. 664 Interoperability considerations: See notes in various sections of 665 [RFC4329]. This media type does not specify the grammar of 666 [ECMA-262] used when missing the goal parameter. 668 Published specification: [[RFCXXXX]] 670 Applications which use this media type: Script interpreters as 671 discussed in [RFC4329]. 673 Additional information: 675 Magic number(s): n/a 677 File extension(s): .js, .mjs 679 Macintosh File Type Code(s): TEXT 681 Person & email address to contact for further information: See 682 Author's Address section. 684 Intended usage: OBSOLETE 686 Restrictions on usage: This media type is obsolete; current 687 implementations should use text/javascript as the only javascript/ 688 ECMAscript media type. The file extension .mjs must be parsed 689 using the Module grammar of [ECMA-262] 691 Author: See Author's Address section. 693 Change controller: IESG 695 3.2.11. text/javascript1.5 697 Type name: text 699 Subtype name: javascript1.5 701 Required parameters: none 703 Optional parameters: charset, see section 4.1 of [RFC4329]. 705 goal, declares the goal symbol in the Syntactic Grammars of 706 [ECMA-262] to be used while parsing. This parameter is case 707 insensitive. 709 Encoding considerations: Encoding is host dependent with differences 710 in byte order marks, the charset parameter, and text 711 preprocessing. 713 Security considerations: See section 5 of [RFC4329]. 715 Interoperability considerations: See notes in various sections of 716 [RFC4329]. This media type does not specify the grammar of 717 [ECMA-262] used when missing the goal parameter. 719 Published specification: [[RFCXXXX]] 720 Applications which use this media type: Script interpreters as 721 discussed in [RFC4329]. 723 Additional information: 725 Magic number(s): n/a 727 File extension(s): .js, .mjs 729 Macintosh File Type Code(s): TEXT 731 Person & email address to contact for further information: See 732 Author's Address section. 734 Intended usage: OBSOLETE 736 Restrictions on usage: This media type is obsolete; current 737 implementations should use text/javascript as the only javascript/ 738 ECMAscript media type. The file extension .mjs must be parsed 739 using the Module grammar of [ECMA-262] 741 Author: See Author's Address section. 743 Change controller: IESG 745 3.2.12. text/jscript 747 Type name: text 749 Subtype name: jscript 751 Required parameters: none 753 Optional parameters: charset, see section 4.1 of [RFC4329]. 755 goal, declares the goal symbol in the Syntactic Grammars of 756 [ECMA-262] to be used while parsing. This parameter is case 757 insensitive. 759 Encoding considerations: Encoding is host dependent with differences 760 in byte order marks, the charset parameter, and text 761 preprocessing. 763 Security considerations: See section 5 of [RFC4329]. 765 Interoperability considerations: See notes in various sections of 766 [RFC4329]. This media type does not specify the grammar of 767 [ECMA-262] used when missing the goal parameter. 769 Published specification: [[RFCXXXX]] 771 Applications which use this media type: Script interpreters as 772 discussed in [RFC4329]. 774 Additional information: 776 Magic number(s): n/a 778 File extension(s): .js, .mjs 780 Macintosh File Type Code(s): TEXT 782 Person & email address to contact for further information: See 783 Author's Address section. 785 Intended usage: OBSOLETE 787 Restrictions on usage: The file extension .mjs must be parsed using 788 the Module grammar of [ECMA-262] 790 Author: See Author's Address section. 792 Change controller: IESG 794 3.2.13. text/livescript 796 Type name: text 798 Subtype name: livescript 800 Required parameters: none 802 Optional parameters: charset, see section 4.1 of [RFC4329]. 804 goal, declares the goal symbol in the Syntactic Grammars of 805 [ECMA-262] to be used while parsing. This parameter is case 806 insensitive. 808 Encoding considerations: Encoding is host dependent with differences 809 in byte order marks, the charset parameter, and text 810 preprocessing. 812 Security considerations: See section 5 of [RFC4329]. 814 Interoperability considerations: See notes in various sections of 815 [RFC4329]. This media type does not specify the grammar of 816 [ECMA-262] used when missing the goal parameter. 818 Published specification: [[RFCXXXX]] 820 Applications which use this media type: Script interpreters as 821 discussed in [RFC4329]. 823 Additional information: 825 Magic number(s): n/a 827 File extension(s): .js, .mjs 829 Macintosh File Type Code(s): TEXT 831 Person & email address to contact for further information: See 832 Author's Address section. 834 Intended usage: OBSOLETE 836 Restrictions on usage: The file extension .mjs must be parsed using 837 the Module grammar of [ECMA-262] 839 Author: See Author's Address section. 841 Change controller: IESG 843 3.2.14. text/x-ecmascript 845 Type name: text 847 Subtype name: x-ecmascript 849 Required parameters: none 851 Optional parameters: charset, see section 4.1 of [RFC4329]. 853 goal, declares the goal symbol in the Syntactic Grammars of 854 [ECMA-262] to be used while parsing. This parameter is case 855 insensitive. 857 Encoding considerations: Encoding is host dependent with differences 858 in byte order marks, the charset parameter, and text 859 preprocessing. 861 Security considerations: See section 5 of [RFC4329]. 863 Interoperability considerations: See notes in various sections of 864 [RFC4329]. This media type does not specify the grammar of 865 [ECMA-262] used when missing the goal parameter. 867 Published specification: [[RFCXXXX]] 869 Applications which use this media type: Script interpreters as 870 discussed in [RFC4329]. 872 Additional information: 874 Magic number(s): n/a 876 File extension(s): .es, .mjs 878 Macintosh File Type Code(s): TEXT 880 Person & email address to contact for further information: See 881 Author's Address section. 883 Intended usage: OBSOLETE 885 Restrictions on usage: The file extension .mjs must be parsed using 886 the Module grammar of [ECMA-262] 888 Author: See Author's Address section. 890 Change controller: IESG 892 3.2.15. text/x-javascript 894 Type name: text 896 Subtype name: x-javascript 898 Required parameters: none 900 Optional parameters: charset, see section 4.1 of [RFC4329]. 902 goal, declares the goal symbol in the Syntactic Grammars of 903 [ECMA-262] to be used while parsing. This parameter is case 904 insensitive. 906 Encoding considerations: Encoding is host dependent with differences 907 in byte order marks, the charset parameter, and text 908 preprocessing. 910 Security considerations: See section 5 of [RFC4329]. 912 Interoperability considerations: See notes in various sections of 913 [RFC4329]. This media type does not specify the grammar of 914 [ECMA-262] used when missing the goal parameter. 916 Published specification: [[RFCXXXX]] 918 Applications which use this media type: Script interpreters as 919 discussed in [RFC4329]. 921 Additional information: 923 Magic number(s): n/a 925 File extension(s): .js, .mjs 927 Macintosh File Type Code(s): TEXT 929 Person & email address to contact for further information: See 930 Author's Address section. 932 Intended usage: OBSOLETE 934 Restrictions on usage: The file extension .mjs must be parsed using 935 the Module grammar of [ECMA-262] 937 Author: See Author's Address section. 939 Change controller: IESG 941 4. References 943 4.1. Normative References 945 [ECMA-262] 946 Ecma International, "Standard ECMA-262: ECMAScript 947 Language Specification", August 2017, . 950 [RFC4329] Hoehrmann, B., "Scripting Media Types", RFC 4329, 951 DOI 10.17487/RFC4329, April 2006, 952 . 954 4.2. Informative References 956 [HTML] WHATWG, "HTML Living Standard", August 2017, 957 . 960 [TC39-MIME-ISSUE] 961 TC39, "Add `application/javascript+module` mime to remove 962 ambiguity5", August 2017, . 965 4.3. URIs 967 [1] https://github.com/bmeck/I-D/labels/javascript-mjs 969 [2] https://github.com/bmeck/I-D/tree/master/javascript-mjs 971 [3] https://github.com/bmeck/I-D/commits/master/javascript-mjs 973 Appendix A. Acknowledgements 975 Thanks to Suresh Krishnan, Alexey Melnikov, Mark Nottingham, James 976 Snell, Adam Roach, and Allen Wirfs-Brock for guiding me through this 977 process. 979 Authors' Addresses 981 Myles Borins 982 Google 984 Email: mylesborins@google.com 986 Mathias Bynens 987 Google 989 Email: mths@google.com 991 Matthew A. Miller 992 Mozilla 994 Email: linuxwolf+ietf@outer-planes.net 996 Bradley Farias 998 Email: bradley.meck@gmail.com