Re: [dispatch] draft-ietf-dispatch-javascript-mjs-02: goal parameter

Bradley Meck <> Wed, 13 June 2018 14:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0CB1B130E31 for <>; Wed, 13 Jun 2018 07:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tXgJcFpXzAW0 for <>; Wed, 13 Jun 2018 07:20:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 61B92130E30 for <>; Wed, 13 Jun 2018 07:20:46 -0700 (PDT)
Received: by with SMTP id d185-v6so3628201ioe.0 for <>; Wed, 13 Jun 2018 07:20:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=JtoYDbHko7T4BnPJBQ8NXwQAjmf7H6tps1Cn1QlnxzA=; b=ia2+mypCEgQcAOYwQU4fTWPIEFbQtUhfvt264KbTvVsfyRtIBkMrcuYIyfmtjNM7TW uTc846q5oZL68TRpZMK+KGF0blp1jAB9ZCTnI8EEw+vMReyaKIF07yt69dnD4XTHYZcV OLdetoZmVr3brVOGF9YQEBD4ce2RI4UVpM9UF86sss2/oToo9sojK62HP1S/OKoivBHo oObz6rh4HQOT6ioAA1DCPplINToItpTqB9m7VClejSinib+lZ0HgQ8B92bvtwKIXhxC/ C+GZ3M6OobHYaIQmTc9IoOWqd/WD/9axy9qMrPBwoMCF3iHWLfIg7ClouBCb9EifPE09 KYIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=JtoYDbHko7T4BnPJBQ8NXwQAjmf7H6tps1Cn1QlnxzA=; b=Z1CMzOkfyTD3codSY3VUy7IuUaxFcNAZmX23YFEwhW9oaH9WCgMXDzeevccfOLckIf S13GEkWhksr8jHk0MZOH1zCXjMrOMPRpYnqK+SgiLruq02Uy/RpvyfiL75PXWwpQDaEB huWSDfgOdAMZHopglOVsSlKpVkj8HHAXT48A8ZlRzBQ+swkKfIpFzz3g1FKKjL5MzVWo FjS4dHVNhrTRGwSLTZuws5MfG0/JKqvoP8AgTpNso7T9kR1vMGCydgQwotYZ6Ja7btE9 cxz2JMfmzKDgf2XV37SozZD/wqdb0MnwIk8EQHeI2rkYFPVkf854XcUA+zg313QHql86 CBmw==
X-Gm-Message-State: APt69E2n7YtOKYp1mRBl4JvgZPFJuWhTcsRLwI21dYxttPNkLGuDl5/W zNQAxamr0Ju4iUegx6iUSPTtBgkyuo6QKCBzaeVbORBW
X-Google-Smtp-Source: ADUXVKIuiC8kb5JgFh05tUgsTnUMrJxRdF24zj7/gUs5yb9e/Bfi5XqsaxU/JPYGGXQQOfi7EI4gUDP2vnfHglRNbYA=
X-Received: by 2002:a6b:b00a:: with SMTP id z10-v6mr4703732ioe.211.1528899645410; Wed, 13 Jun 2018 07:20:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:9e08:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 07:20:24 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Bradley Meck <>
Date: Wed, 13 Jun 2018 09:20:24 -0500
Message-ID: <>
Content-Type: multipart/alternative; boundary="0000000000004313c5056e86b04b"
Archived-At: <>
Subject: Re: [dispatch] draft-ietf-dispatch-javascript-mjs-02: goal parameter
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Jun 2018 14:20:49 -0000

Sorry for the late reply, I am new to some of this process.

I'd refer ,
and the comments leading up to it.

The original intent of this draft was to introduce things related to JS
Modules and the syntactic goal related to them. The addition of the MIMEs
to reflect reality was done according to your comments in the issue
tracker. This draft could be split, but I would not personally submit one
with just the new MIME registrations as that was not the original intent of
this draft.

There is a problem of not wanting to implement things before being
standardized as Adam Roach points out. I don't think that reflecting the
reality of implementations is possible if implementations such as Node
won't ship the parameter without it being standardized. I also don't think
separating to match reality makes much sense for additional features like
new file extensions when it comes to file extensions as WHATWG explicitly
states to not use file extensions during MIME sniffing.

Per the changes related to JS Modules:

It seems that Allen and I think it is useful.

* We are both members of TC39, which is in charge of the JS language
specification and there is an open issue tracking this MIME update.
* That tracking issue does not have any disagreement with the current

I am also a Node.js contributor with heavy involvement in the upcoming
Module work, and am seeking to use MIME as a means to disambiguate the
intended interpretation of source texts.

Adam of IETF remarks that it makes sense to land it preemptively if it
would be useful later.

Per the comment of lack of interest from WHATWG:

* It seems Firefox is interested.
* Node has interest but no say in WHATWG, if it did there would have the
required 2 party interest if I understand things.
* No outstanding disagreement on the feature seems to be found on a quick
search. Seems like just a lack of interest, not a statement that the
parameter should not exist.

The lack of Node as a relevant figure in WHATWG I think shows how this MIME
can be useful outside of browsers and strengthens that lack of interest
from WHATWG does not mean lack of utility for other technologies.

I don't think a change to this update is needed, but am going to reach out
to these parties again and see if they would like to reply here as well.


On Fri, May 18, 2018 at 10:03 AM, Anne van Kesteren <>

> I'm not convinced adding a goal parameter at this point is useful
> since not all JavaScript hosts seem keen on adopting it. In
> particular, a change proposal to the HTML Standard has not gotten
> sufficient implementer interest:
> I'd much prefer it if the registration was first updated to "match
> reality" and additional features are only added if there's actually
> sufficient implementers behind them. (Otherwise you have another
> Cookie2.)
> --
> _______________________________________________
> dispatch mailing list