Re: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt

"L. David Baron" <dbaron@dbaron.org> Wed, 11 July 2018 01:05 UTC

Return-Path: <dbaron@dbaron.org>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8622130DC7; Tue, 10 Jul 2018 18:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.941
X-Spam-Level:
X-Spam-Status: No, score=-1.941 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dbaron.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IwUeaqLxp8YI; Tue, 10 Jul 2018 18:05:15 -0700 (PDT)
Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net [217.70.183.193]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 947B0127332; Tue, 10 Jul 2018 18:05:13 -0700 (PDT)
X-Originating-IP: 103.21.135.19
Received: from pescadero.dbaron.org (unknown [103.21.135.19]) (Authenticated sender: dbaron-out@dbaron.org) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id AD13C240007; Wed, 11 Jul 2018 01:05:10 +0000 (UTC)
Received: by pescadero.dbaron.org (Postfix, from userid 1000) id D378E120119; Wed, 11 Jul 2018 01:05:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dbaron.org; s=b; t=1531271105; bh=+3ePGb+sNY/PU3JkNz3GBl09ehgXV+lW7hyTVGHtyfg=; l=5519; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pdlxQhLHvk/a4lza0TYCO0uuQIis+5JtXDAoIDaXd+GImP1Y7NI9LJtwrb1iirSMw foq0rClAGkm9IyZwM/Nr2HcmUlLi73O6og+RDCWY1Z2WJc4ALugeT5qhXQsd+QeY1W msI4SM4j4ii/BeC2xFToc583sMkTptvRbtl2bBXLu9BJykcEIbXclXb3sALRezN1Sa cfF1F7dl9KwohG0jIzRlbTCWQ6oV3ljwHCFbW5pkACXj7PEFr9jPs49Hai7VDQb+N/ EEYWUHv7pfD/HYTJlB7ZmSnD9kLSo6wdXVbRaNCxVaTrATyCJzcw6XBoqhhrNfLV8E SIuikMXRPNPQA==
Date: Wed, 11 Jul 2018 11:05:05 +1000
From: "L. David Baron" <dbaron@dbaron.org>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Cc: DISPATCH <dispatch@ietf.org>, draft-ietf-dispatch-javascript-mjs@ietf.org, Barry Leiba <barryleiba@computer.org>
Message-ID: <20180711010505.GA4920@pescadero.dbaron.org>
References: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB"
Content-Disposition: inline
In-Reply-To: <CAHBDyN5kB=yi_eFty2hRO4LpadKrSSY0KY-BAS2447Y84pPoWg@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/lnvyIRAfg7-Di_ynVz0D74PdkSI>
Subject: Re: [dispatch] WGLC: draft-ietf-dispatch-javascript-mjs-02.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 01:05:18 -0000

Hi -

I have a few comments on the document:


There are two things that might be read to imply that processors
(e.g., browsers) should change their behavior as a result of file
extensions.  In particular, in section 4 (Registration):

                                                           In addition,
   a new file extension of .mjs is to be added to the list of file
   extensions with the restriction that it must correspond to the Module
   grammar of [ECMA-262].

and then repeatedly in the subsections of that section:

   Restrictions on usage:  The file extension .mjs must be parsed using
      the Module grammar of [ECMA-262] 

This seems like a reasonable thing to suggest as the intended use of
the .mjs extension, but I think it could be read to imply that
implementations should change their behavior as a result of file
extensions, which would be a rather unusual requirement on the Web.

If that requirement were the intent, it would seem to contradict the
processing rules for script elements in the HTML specification at:
https://html.spec.whatwg.org/multipage/scripting.html#attr-script-type
which specify that the type attribute on the script element
determines whether a script is interpreted as a classic script or as
a module script.


Additionally, I wonder whether it would be useful to have a section
that documents the changes from RFC4329.  The introduction to
section 4 (Registration) seems to document some of them, but I
noticed that it doesn't mention that application/ecmascript and
application/javascript have been changed to Obsolete, and a number
of types not previously listed in RFC4329 (but listed in
https://mimesniff.spec.whatwg.org/#javascript-mime-type) have been
added as Obsolete.  (I didn't check for other differences.)


I'm happy to see the obsolete/common distinction in this draft
reflecting current practice.

-David


On Tuesday 2018-07-10 13:15 -0500, Mary Barnes wrote:
> Hi all,
> 
> 
> We would like to start a 2 week WGLC for this document.    If you think the
> document is ready, please respond to this email.  If you have comments that
> you would like considered and/or any editorial suggestions, please post
> those as well.
> 
> 
> The WGLC ends on July 25, 2018.
> 
> 
> Regards,
> 
> Mary
> 
> DISPATCH WG tri-chair
> 
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>;
> Date: Tue, May 8, 2018 at 5:41 PM
> Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-02.txt
> To: i-d-announce@ietf.org
> Cc: dispatch@ietf.org
> 
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Dispatch WG of the IETF.
> 
>         Title           : ECMAScript Media Types Updates
>         Authors         : Bradley Farias
>                           Matthew A. Miller
>         Filename        : draft-ietf-dispatch-javascript-mjs-02.txt
>         Pages           : 21
>         Date            : 2018-05-08
> 
> Abstract:
>    This document proposes updates to the ECMAScript media types,
>    superseding the existing registrations for "application/javascript"
>    and "text/javascript" by adding an additional extension and removing
>    usage warnings.  This document updates RFC4329, "Scripting Media
>    Types".
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-02
> https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dispatch-javascript-mjs-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> 

-- 
đť„ž   L. David Baron                         http://dbaron.org/   đť„‚
𝄢   Mozilla                          https://www.mozilla.org/   𝄂
             Before I built a wall I'd ask to know
             What I was walling in or walling out,
             And to whom I was like to give offense.
               - Robert Frost, Mending Wall (1914)