idnits 2.17.1 draft-ietf-dispatch-javascript-mjs-02.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 (May 08, 2018) is 2177 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 934 -- Looks like a reference, but probably isn't: '2' on line 936 -- Looks like a reference, but probably isn't: '3' on line 938 == Unused Reference: 'RFC3023' is defined on line 913, 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: November 9, 2018 May 08, 2018 8 ECMAScript Media Types Updates 9 draft-ietf-dispatch-javascript-mjs-02 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 November 9, 2018. 47 Copyright Notice 49 Copyright (c) 2018 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. application/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. application/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 in the Syntactic Grammars of 141 [ECMA-262] to be used while parsing. This parameter is case 142 insensitive. 144 Encoding considerations: Encoding is host dependent with differences 145 in byte order marks, the charset parameter, and text 146 preprocessing. 148 Security considerations: See section 5 of [RFC4329]. 150 Interoperability considerations: See notes in various sections of 151 [RFC4329]. This media type does not specify the grammar of 152 [ECMA-262] used when missing the goal parameter. 154 Published specification: [[RFCXXXX]] 156 Applications which use this media type: Script interpreters as 157 discussed in [RFC4329]. 159 Additional information: 161 Magic number(s): n/a 163 File extension(s): .es, .mjs 165 Macintosh File Type Code(s): TEXT 167 Person & email address to contact for further information: See 168 Author's Address section. 170 Intended usage: OBSOLETE 172 Restrictions on usage: The file extension .mjs must be parsed using 173 the Module grammar of [ECMA-262] 175 Author: See Author's Address section. 177 Change controller: IESG 179 4.2. application/javascript 181 Type name: application 183 Subtype name: javascript 185 Required parameters: none 186 Optional parameters: charset, see section 4.1 of [RFC4329]. 188 goal, declares the goal symbol in the Syntactic Grammars of 189 [ECMA-262] to be used while parsing. This parameter is case 190 insensitive. 192 Encoding considerations: Encoding is host dependent with differences 193 in byte order marks, the charset parameter, and text 194 preprocessing. 196 Security considerations: See section 5 of [RFC4329]. 198 Interoperability considerations: See notes in various sections of 199 [RFC4329]. This media type does not specify the grammar of 200 [ECMA-262] used when missing the goal parameter. 202 Published specification: [[RFCXXXX]] 204 Applications which use this media type: Script interpreters as 205 discussed in [RFC4329]. 207 Additional information: 209 Magic number(s): n/a 211 File extension(s): .js, .mjs 213 Macintosh File Type Code(s): TEXT 215 Person & email address to contact for further information: See 216 Author's Address section. 218 Intended usage: OBSOLETE 220 Restrictions on usage: The file extension .mjs must be parsed using 221 the Module grammar of [ECMA-262] 223 Author: See Author's Address section. 225 Change controller: IESG . 227 4.3. application/x-ecmascript 229 Type name: application 231 Subtype name: x-ecmascript 233 Required parameters: none 234 Optional parameters: charset, see section 4.1 of [RFC4329]. 236 goal, declares the goal symbol in the Syntactic Grammars of 237 [ECMA-262] to be used while parsing. This parameter is case 238 insensitive. 240 Encoding considerations: Encoding is host dependent with differences 241 in byte order marks, the charset parameter, and text 242 preprocessing. 244 Security considerations: See section 5 of [RFC4329]. 246 Interoperability considerations: See notes in various sections of 247 [RFC4329]. This media type does not specify the grammar of 248 [ECMA-262] used when missing the goal parameter. 250 Published specification: [[RFCXXXX]] 252 Applications which use this media type: Script interpreters as 253 discussed in [RFC4329]. 255 Additional information: 257 Magic number(s): n/a 259 File extension(s): .es, .mjs 261 Macintosh File Type Code(s): TEXT 263 Person & email address to contact for further information: See 264 Author's Address section. 266 Intended usage: OBSOLETE 268 Restrictions on usage: The file extension .mjs must be parsed using 269 the Module grammar of [ECMA-262] 271 Author: See Author's Address section. 273 Change controller: IESG 275 4.4. application/x-javascript 277 Type name: application 279 Subtype name: x-javascript 281 Required parameters: none 282 Optional parameters: charset, see section 4.1 of [RFC4329]. 284 goal, declares the goal symbol in the Syntactic Grammars of 285 [ECMA-262] to be used while parsing. This parameter is case 286 insensitive. 288 Encoding considerations: Encoding is host dependent with differences 289 in byte order marks, the charset parameter, and text 290 preprocessing. 292 Security considerations: See section 5 of [RFC4329]. 294 Interoperability considerations: See notes in various sections of 295 [RFC4329]. This media type does not specify the grammar of 296 [ECMA-262] used when missing the goal parameter. 298 Published specification: [[RFCXXXX]] 300 Applications which use this media type: Script interpreters as 301 discussed in [RFC4329]. 303 Additional information: 305 Magic number(s): n/a 307 File extension(s): .js, .mjs 309 Macintosh File Type Code(s): TEXT 311 Person & email address to contact for further information: See 312 Author's Address section. 314 Intended usage: OBSOLETE 316 Restrictions on usage: The file extension .mjs must be parsed using 317 the Module grammar of [ECMA-262] 319 Author: See Author's Address section. 321 Change controller: IESG 323 4.5. text/ecmascript 325 Type name: text 327 Subtype name: ecmascript 329 Required parameters: none 330 Optional parameters: charset, see section 4.1 of [RFC4329]. 332 goal, declares the goal symbol in the Syntactic Grammars of 333 [ECMA-262] to be used while parsing. This parameter is case 334 insensitive. 336 Encoding considerations: Encoding is host dependent with differences 337 in byte order marks, the charset parameter, and text 338 preprocessing. 340 Security considerations: See section 5 of [RFC4329]. 342 Interoperability considerations: See notes in various sections of 343 [RFC4329]. This media type does not specify the grammar of 344 [ECMA-262] used when missing the goal parameter. 346 Published specification: [[RFCXXXX]] 348 Applications which use this media type: Script interpreters as 349 discussed in [RFC4329]. 351 Additional information: 353 Magic number(s): n/a 355 File extension(s): .es, .mjs 357 Macintosh File Type Code(s): TEXT 359 Person & email address to contact for further information: See 360 Author's Address section. 362 Intended usage: OBSOLETE 364 Restrictions on usage: The file extension .mjs must be parsed using 365 the Module grammar of [ECMA-262] 367 Author: See Author's Address section. 369 Change controller: IESG 371 4.6. text/javascript 373 Type name: text 375 Subtype name: javascript 377 Required parameters: none 378 Optional parameters: charset, see section 4.1 of [RFC4329]. 380 goal, declares the goal symbol in the Syntactic Grammars of 381 [ECMA-262] to be used while parsing. This parameter is case 382 insensitive. 384 Encoding considerations: Encoding is host dependent with differences 385 in byte order marks, the charset parameter, and text 386 preprocessing. 388 Security considerations: See section 5 of [RFC4329]. 390 Interoperability considerations: See notes in various sections of 391 [RFC4329]. This media type does not specify the grammar of 392 [ECMA-262] used when missing the goal parameter. 394 Published specification: [[RFCXXXX]] 396 Applications which use this media type: Script interpreters as 397 discussed in [RFC4329]. 399 Additional information: 401 Magic number(s): n/a 403 File extension(s): .js, .mjs 405 Macintosh File Type Code(s): TEXT 407 Person & email address to contact for further information: See 408 Author's Address section. 410 Intended usage: COMMON 412 Restrictions on usage: The file extension .mjs must be parsed using 413 the Module grammar of [ECMA-262] 415 Author: See Author's Address section. 417 Change controller: IESG 419 4.7. text/javascript1.0 421 Type name: text 423 Subtype name: javascript1.0 425 Required parameters: none 426 Optional parameters: charset, see section 4.1 of [RFC4329]. 428 goal, declares the goal symbol in the Syntactic Grammars of 429 [ECMA-262] to be used while parsing. This parameter is case 430 insensitive. 432 Encoding considerations: Encoding is host dependent with differences 433 in byte order marks, the charset parameter, and text 434 preprocessing. 436 Security considerations: See section 5 of [RFC4329]. 438 Interoperability considerations: See notes in various sections of 439 [RFC4329]. This media type does not specify the grammar of 440 [ECMA-262] used when missing the goal parameter. 442 Published specification: [[RFCXXXX]] 444 Applications which use this media type: Script interpreters as 445 discussed in [RFC4329]. 447 Additional information: 449 Magic number(s): n/a 451 File extension(s): .js, .mjs 453 Macintosh File Type Code(s): TEXT 455 Person & email address to contact for further information: See 456 Author's Address section. 458 Intended usage: OBSOLETE 460 Restrictions on usage: The file extension .mjs must be parsed using 461 the Module grammar of [ECMA-262] 463 Author: See Author's Address section. 465 Change controller: IESG 467 4.8. text/javascript1.1 469 Type name: text 471 Subtype name: javascript1.1 473 Required parameters: none 474 Optional parameters: charset, see section 4.1 of [RFC4329]. 476 goal, declares the goal symbol in the Syntactic Grammars of 477 [ECMA-262] to be used while parsing. This parameter is case 478 insensitive. 480 Encoding considerations: Encoding is host dependent with differences 481 in byte order marks, the charset parameter, and text 482 preprocessing. 484 Security considerations: See section 5 of [RFC4329]. 486 Interoperability considerations: See notes in various sections of 487 [RFC4329]. This media type does not specify the grammar of 488 [ECMA-262] used when missing the goal parameter. 490 Published specification: [[RFCXXXX]] 492 Applications which use this media type: Script interpreters as 493 discussed in [RFC4329]. 495 Additional information: 497 Magic number(s): n/a 499 File extension(s): .js, .mjs 501 Macintosh File Type Code(s): TEXT 503 Person & email address to contact for further information: See 504 Author's Address section. 506 Intended usage: OBSOLETE 508 Restrictions on usage: The file extension .mjs must be parsed using 509 the Module grammar of [ECMA-262] 511 Author: See Author's Address section. 513 Change controller: IESG 515 4.9. text/javascript1.2 517 Type name: text 519 Subtype name: javascript1.2 521 Required parameters: none 522 Optional parameters: charset, see section 4.1 of [RFC4329]. 524 goal, declares the goal symbol in the Syntactic Grammars of 525 [ECMA-262] to be used while parsing. This parameter is case 526 insensitive. 528 Encoding considerations: Encoding is host dependent with differences 529 in byte order marks, the charset parameter, and text 530 preprocessing. 532 Security considerations: See section 5 of [RFC4329]. 534 Interoperability considerations: See notes in various sections of 535 [RFC4329]. This media type does not specify the grammar of 536 [ECMA-262] used when missing the goal parameter. 538 Published specification: [[RFCXXXX]] 540 Applications which use this media type: Script interpreters as 541 discussed in [RFC4329]. 543 Additional information: 545 Magic number(s): n/a 547 File extension(s): .js, .mjs 549 Macintosh File Type Code(s): TEXT 551 Person & email address to contact for further information: See 552 Author's Address section. 554 Intended usage: OBSOLETE 556 Restrictions on usage: The file extension .mjs must be parsed using 557 the Module grammar of [ECMA-262] 559 Author: See Author's Address section. 561 Change controller: IESG 563 4.10. text/javascript1.3 565 Type name: text 567 Subtype name: javascript1.3 569 Required parameters: none 570 Optional parameters: charset, see section 4.1 of [RFC4329]. 572 goal, declares the goal symbol in the Syntactic Grammars of 573 [ECMA-262] to be used while parsing. This parameter is case 574 insensitive. 576 Encoding considerations: Encoding is host dependent with differences 577 in byte order marks, the charset parameter, and text 578 preprocessing. 580 Security considerations: See section 5 of [RFC4329]. 582 Interoperability considerations: See notes in various sections of 583 [RFC4329]. This media type does not specify the grammar of 584 [ECMA-262] used when missing the goal parameter. 586 Published specification: [[RFCXXXX]] 588 Applications which use this media type: Script interpreters as 589 discussed in [RFC4329]. 591 Additional information: 593 Magic number(s): n/a 595 File extension(s): .js, .mjs 597 Macintosh File Type Code(s): TEXT 599 Person & email address to contact for further information: See 600 Author's Address section. 602 Intended usage: OBSOLETE 604 Restrictions on usage: The file extension .mjs must be parsed using 605 the Module grammar of [ECMA-262] 607 Author: See Author's Address section. 609 Change controller: IESG 611 4.11. text/javascript1.4 613 Type name: text 615 Subtype name: javascript1.4 617 Required parameters: none 618 Optional parameters: charset, see section 4.1 of [RFC4329]. 620 goal, declares the goal symbol in the Syntactic Grammars of 621 [ECMA-262] to be used while parsing. This parameter is case 622 insensitive. 624 Encoding considerations: Encoding is host dependent with differences 625 in byte order marks, the charset parameter, and text 626 preprocessing. 628 Security considerations: See section 5 of [RFC4329]. 630 Interoperability considerations: See notes in various sections of 631 [RFC4329]. This media type does not specify the grammar of 632 [ECMA-262] used when missing the goal parameter. 634 Published specification: [[RFCXXXX]] 636 Applications which use this media type: Script interpreters as 637 discussed in [RFC4329]. 639 Additional information: 641 Magic number(s): n/a 643 File extension(s): .js, .mjs 645 Macintosh File Type Code(s): TEXT 647 Person & email address to contact for further information: See 648 Author's Address section. 650 Intended usage: OBSOLETE 652 Restrictions on usage: The file extension .mjs must be parsed using 653 the Module grammar of [ECMA-262] 655 Author: See Author's Address section. 657 Change controller: IESG 659 4.12. text/javascript1.5 661 Type name: text 663 Subtype name: javascript1.5 665 Required parameters: none 666 Optional parameters: charset, see section 4.1 of [RFC4329]. 668 goal, declares the goal symbol in the Syntactic Grammars of 669 [ECMA-262] to be used while parsing. This parameter is case 670 insensitive. 672 Encoding considerations: Encoding is host dependent with differences 673 in byte order marks, the charset parameter, and text 674 preprocessing. 676 Security considerations: See section 5 of [RFC4329]. 678 Interoperability considerations: See notes in various sections of 679 [RFC4329]. This media type does not specify the grammar of 680 [ECMA-262] used when missing the goal parameter. 682 Published specification: [[RFCXXXX]] 684 Applications which use this media type: Script interpreters as 685 discussed in [RFC4329]. 687 Additional information: 689 Magic number(s): n/a 691 File extension(s): .js, .mjs 693 Macintosh File Type Code(s): TEXT 695 Person & email address to contact for further information: See 696 Author's Address section. 698 Intended usage: OBSOLETE 700 Restrictions on usage: The file extension .mjs must be parsed using 701 the Module grammar of [ECMA-262] 703 Author: See Author's Address section. 705 Change controller: IESG 707 4.13. text/jscript 709 Type name: text 711 Subtype name: jscript 713 Required parameters: none 714 Optional parameters: charset, see section 4.1 of [RFC4329]. 716 goal, declares the goal symbol in the Syntactic Grammars of 717 [ECMA-262] to be used while parsing. This parameter is case 718 insensitive. 720 Encoding considerations: Encoding is host dependent with differences 721 in byte order marks, the charset parameter, and text 722 preprocessing. 724 Security considerations: See section 5 of [RFC4329]. 726 Interoperability considerations: See notes in various sections of 727 [RFC4329]. This media type does not specify the grammar of 728 [ECMA-262] used when missing the goal parameter. 730 Published specification: [[RFCXXXX]] 732 Applications which use this media type: Script interpreters as 733 discussed in [RFC4329]. 735 Additional information: 737 Magic number(s): n/a 739 File extension(s): .js, .mjs 741 Macintosh File Type Code(s): TEXT 743 Person & email address to contact for further information: See 744 Author's Address section. 746 Intended usage: OBSOLETE 748 Restrictions on usage: The file extension .mjs must be parsed using 749 the Module grammar of [ECMA-262] 751 Author: See Author's Address section. 753 Change controller: IESG 755 4.14. text/livescript 757 Type name: text 759 Subtype name: livescript 761 Required parameters: none 762 Optional parameters: charset, see section 4.1 of [RFC4329]. 764 goal, declares the goal symbol in the Syntactic Grammars of 765 [ECMA-262] to be used while parsing. This parameter is case 766 insensitive. 768 Encoding considerations: Encoding is host dependent with differences 769 in byte order marks, the charset parameter, and text 770 preprocessing. 772 Security considerations: See section 5 of [RFC4329]. 774 Interoperability considerations: See notes in various sections of 775 [RFC4329]. This media type does not specify the grammar of 776 [ECMA-262] used when missing the goal parameter. 778 Published specification: [[RFCXXXX]] 780 Applications which use this media type: Script interpreters as 781 discussed in [RFC4329]. 783 Additional information: 785 Magic number(s): n/a 787 File extension(s): .js, .mjs 789 Macintosh File Type Code(s): TEXT 791 Person & email address to contact for further information: See 792 Author's Address section. 794 Intended usage: OBSOLETE 796 Restrictions on usage: The file extension .mjs must be parsed using 797 the Module grammar of [ECMA-262] 799 Author: See Author's Address section. 801 Change controller: IESG 803 4.15. text/x-ecmascript 805 Type name: text 807 Subtype name: x-ecmascript 809 Required parameters: none 810 Optional parameters: charset, see section 4.1 of [RFC4329]. 812 goal, declares the goal symbol in the Syntactic Grammars of 813 [ECMA-262] to be used while parsing. This parameter is case 814 insensitive. 816 Encoding considerations: Encoding is host dependent with differences 817 in byte order marks, the charset parameter, and text 818 preprocessing. 820 Security considerations: See section 5 of [RFC4329]. 822 Interoperability considerations: See notes in various sections of 823 [RFC4329]. This media type does not specify the grammar of 824 [ECMA-262] used when missing the goal parameter. 826 Published specification: [[RFCXXXX]] 828 Applications which use this media type: Script interpreters as 829 discussed in [RFC4329]. 831 Additional information: 833 Magic number(s): n/a 835 File extension(s): .es, .mjs 837 Macintosh File Type Code(s): TEXT 839 Person & email address to contact for further information: See 840 Author's Address section. 842 Intended usage: OBSOLETE 844 Restrictions on usage: The file extension .mjs must be parsed using 845 the Module grammar of [ECMA-262] 847 Author: See Author's Address section. 849 Change controller: IESG 851 4.16. text/x-javascript 853 Type name: text 855 Subtype name: x-javascript 857 Required parameters: none 858 Optional parameters: charset, see section 4.1 of [RFC4329]. 860 goal, declares the goal symbol in the Syntactic Grammars of 861 [ECMA-262] to be used while parsing. This parameter is case 862 insensitive. 864 Encoding considerations: Encoding is host dependent with differences 865 in byte order marks, the charset parameter, and text 866 preprocessing. 868 Security considerations: See section 5 of [RFC4329]. 870 Interoperability considerations: See notes in various sections of 871 [RFC4329]. This media type does not specify the grammar of 872 [ECMA-262] used when missing the goal parameter. 874 Published specification: [[RFCXXXX]] 876 Applications which use this media type: Script interpreters as 877 discussed in [RFC4329]. 879 Additional information: 881 Magic number(s): n/a 883 File extension(s): .js, .mjs 885 Macintosh File Type Code(s): TEXT 887 Person & email address to contact for further information: See 888 Author's Address section. 890 Intended usage: OBSOLETE 892 Restrictions on usage: The file extension .mjs must be parsed using 893 the Module grammar of [ECMA-262] 895 Author: See Author's Address section. 897 Change controller: IESG 899 5. References 901 5.1. Normative References 903 [ECMA-262] 904 Ecma International, "Standard ECMA-262: ECMAScript 905 Language Specification", August 2017, . 908 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 909 Requirement Levels", BCP 14, RFC 2119, 910 DOI 10.17487/RFC2119, March 1997, 911 . 913 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 914 Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, 915 . 917 [RFC4329] Hoehrmann, B., "Scripting Media Types", RFC 4329, 918 DOI 10.17487/RFC4329, April 2006, 919 . 921 5.2. Informative References 923 [HTML] WHATWG, "HTML Living Standard", August 2017, 924 . 927 [TC39-MIME-ISSUE] 928 TC39, "Add `application/javascript+module` mime to remove 929 ambiguity5", August 2017, . 932 5.3. URIs 934 [1] https://github.com/bmeck/I-D/labels/javascript-mjs 936 [2] https://github.com/bmeck/I-D/tree/master/javascript-mjs 938 [3] https://github.com/bmeck/I-D/commits/master/javascript-mjs 940 Appendix A. Acknowledgements 942 Thanks to Suresh Krishnan, Alexey Melnikov, Mark Nottingham, James 943 Snell, Matthew A. Miller, Adam Roach, and Allen Wirfs-Brock for 944 guiding me through this process. 946 Authors' Addresses 948 Bradley Farias 950 Email: bradley.meck@gmail.com 951 Matthew A. Miller 952 Mozilla 954 Email: linuxwolf+ietf@outer-planes.net