From nobody Tue Apr 27 10:26:13 2021 Return-Path: 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 37E6A3A1812 for ; Tue, 27 Apr 2021 10:26:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=github.com 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 YzZA8z3Lwy5r for ; Tue, 27 Apr 2021 10:26:06 -0700 (PDT) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA1A3A1815 for ; Tue, 27 Apr 2021 10:26:06 -0700 (PDT) Received: by mail-ed1-x533.google.com with SMTP id i3so45217807edt.1 for ; Tue, 27 Apr 2021 10:26:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Btzw9Yc+5c2mn6FeranT96j+omUW8mGBTubLflLm1zY=; b=Egb4qjZVUgKNvzuXp5+jAF9h2W6msptcuhYdKPTEeko61IO1VBFhxdVA5NMMxisLz3 GWbjAEuTWtjXJpLClTdSrgOv0lkn0e4uKN4R/sTH3egGuEvkaJxd+gGGDXtg6COAt0AE kmW+U4KysYHGBUv1T+2tqrDoCAKF8XLoJ2pdEGR6ZWwk+YHbX2tLV5+U6/CwmgbuExKq 5J/GiGfsWOsjkSM00R+h+/rpvxx/3ES2s/4Ktel9D8neMZ7l1j8aNtj6r27ywPgmhMZT 7BXibDzbuOeLL8fOPl6S+jAJmVpcQYjk9U3xr54oqBdlPyPB2a8VV1uuucii48V3ggbA Yu6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Btzw9Yc+5c2mn6FeranT96j+omUW8mGBTubLflLm1zY=; b=Z2mD/G3nkAbxVJVqcY4YA35iQZ6C45oH5JThlmpZdTi8DN52B66TTnpnyQpieInnNc cjsUXsej6aZQKJ0cc0fCdbTgszBriZI8jGw2R9N2OX67zhJeIcB7zCoQGy2jjiiif1tL CEtZwqVDlzazf5mJR5naZzSXDe5GZPS7mcAErQ27UfFTUbJCx6vbblo0vYsk0OIFKm8w yT8mEQJnn46E28a17H1JS7EU5/11pyV3RLG/dyM6tAKKuD6aKfeUwe1zZYXgDjX0WJOp MHxide8ic38a8NZXxSR3NMp/PVLZPtd5TGAsP2O/6KaeJn/pOcMUlo0PLcBMvE1azTRM /BFA== X-Gm-Message-State: AOAM530xhR2xOGCXnOXdfVYmIBFjIS3jlxxgUl2K+Nf8MgFrg5ysMNW+ Y3DzG4j7se5Z6pGEQy/uQkPnFC9x2bF5tmTb3qKR+A== X-Google-Smtp-Source: ABdhPJyBMuP5U0nUo2J7cb5BsVvbebfA1HK+980bw7J+WGwQQRTfNefNyQwKSKx07JgGjz64efUCUTYhxmRBR3HWwBI= X-Received: by 2002:aa7:c7da:: with SMTP id o26mr5807200eds.244.1619544359233; Tue, 27 Apr 2021 10:25:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Myles Borins Date: Tue, 27 Apr 2021 13:25:47 -0400 Message-ID: To: Mathias Bynens Cc: Kirsty P , "Matthew A. Miller" , DISPATCH WG Content-Type: multipart/alternative; boundary="0000000000003b0f4a05c0f78e50" Archived-At: Subject: Re: [dispatch] 3rd WGLC - draft-ietf-dispatch-javascript-mjs - deadline 10th May X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2021 17:26:11 -0000 --0000000000003b0f4a05c0f78e50 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Disclaimer: I am one of the authors of the draft. I would like to also express my support for this draft. It imho reflects ecosystem usage, for example there are currently over 6 million files with the .mjs extension on GitHub . The extension is supported in some mimetype collections and DBs, such as that of the python programming language , but still hasn't been adopted by industry standard tools such as apache . The lack of consistency here makes for poor developer experiences and inconsistent experiences across platforms + tools. This draft being accepted would be an extremely strong signal to let folks know that they can implement support for .mjs. Separate from the new extension that will be supported the updated draft includes a number of additional improvements that reflect the current reality of the web. This includes making "text/javascript" COMMON rather than OBSOLETE and an update to the security considerations. Thank you everyone for your time and considerations regarding this matter. On Tue, Apr 27, 2021 at 10:17 AM Mathias Bynens wrote: > Disclaimer: I am one of the authors of this draft. Nevertheless, I > would like to express my support and speak to the importance of its > standardization. > > The draft supersedes the earlier RFC4329, providing updated > definitions to align with what has quickly become implementation > reality, both in web browsers as well as other popular JavaScript > environments such as Node.js. > > Thanks, > Mathias > > On Tue, Apr 27, 2021 at 3:49 PM Kirsty P wrote: > > ________________________________ > > From: Kirsty P > > Sent: 26 April 2021 16:25 > > To: dispatch@ietf.org > > Subject: 3rd WGLC - draft-ietf-dispatch-javascript-mjs - deadline 10th > May > > > > Hi DISPATCH, > > > > Summary: draft-ietf-dispatch-javascript-mjs is now ready for its 3rd > WGLC (Working Group Last Call). Please send your comments and/or > expressions of support to the DISPATCH list. > > > > Longer: the draft was recently updated to address feedback from a revie= w > and from the 2nd WGLC [1]. The authors posted an update to the list with > more information [2]. We (DISPATCH chairs) feel like all the comments hav= e > been addressed, so it's time for 3rd WGLC. > > > > We need to hear positive noises and support for this draft from the WG > before progressing the -08 draft, so please email to signal your > endorsement, even if you have no comments to make. The draft can be found > on datatracker here: > https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/ > > > > WGLC is open for 2 weeks - so will finish close-of-play on Monday 10th > May. > > > > Kirsty > > (DISPATCH co-chair) > > > > [1] > https://mailarchive.ietf.org/arch/msg/dispatch/MOp48vAf_K4cjoS9XoFgxBUqXg= 0/ > > [2] > https://mailarchive.ietf.org/arch/msg/dispatch/TmuVIJS6Umh37oOhiIHv-5Mzki= s/ > > > > > > > > This information is exempt under the Freedom of Information Act 2000 > (FOIA) and may be exempt under other UK information legislation. Refer an= y > FOIA queries to ncscinfoleg@ncsc.gov.uk. All material is UK Crown > Copyright =C2=A9 > --0000000000003b0f4a05c0f78e50 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Disclaimer: I am one of the authors of the draft.

=
I would like to also express my support for this draft. It imho = reflects ecosystem usage, for example there are currently over 6 mi= llion files with the .mjs extension on GitHub.

The extension is supported in some mimetype collections and DBs, such as t= hat of the python programming language, but still hasn't been = adopted by industry standard tools such as apache. The lack of consistency her= e makes for poor developer experiences and inconsistent experiences across = platforms=C2=A0+ tools. This draft being accepted would be an extremely str= ong signal to let folks know that they can implement support for .mjs.

Separate from the new extension that will be supported= the updated draft includes a number of additional improvements that reflec= t the current reality of the web. This includes making "text/javascrip= t" COMMON rather than OBSOLETE and an update to the security considera= tions.

Thank you everyone for your time and consid= erations regarding this=C2=A0matter.

On Tue, Apr 27, 2021 at 10:17 AM = Mathias Bynens <mths@google.com&g= t; wrote:
Discla= imer: I am one of the authors of this draft. Nevertheless, I
would like to express my support and speak to the importance of its
standardization.

The draft supersedes the earlier RFC4329, providing updated
definitions to align with what has quickly become implementation
reality, both in web browsers as well as other popular JavaScript
environments such as Node.js.

Thanks,
Mathias

On Tue, Apr 27, 2021 at 3:49 PM Kirsty P <Kirsty.p@ncsc.gov.uk> wrote:
> ________________________________
> From: Kirsty P
> Sent: 26 April 2021 16:25
> To: dispatch@ie= tf.org <dispa= tch@ietf.org>
> Subject: 3rd WGLC - draft-ietf-dispatch-javascript-mjs - deadline 10th= May
>
> Hi DISPATCH,
>
> Summary: draft-ietf-dispatch-javascript-mjs is now ready for its 3rd W= GLC (Working Group Last Call). Please send your comments and/or expressions= of support to the DISPATCH list.
>
> Longer: the draft was recently updated to address feedback from a revi= ew and from the 2nd WGLC [1]. The authors posted an update to the list with= more information [2]. We (DISPATCH chairs) feel like all the comments have= been addressed, so it's time for 3rd WGLC.
>
> We need to hear positive noises and support for this draft from the WG= before progressing the -08 draft, so please email to signal your endorseme= nt, even if you have no comments to make. The draft can be found on datatra= cker here: https://datatracker.i= etf.org/doc/draft-ietf-dispatch-javascript-mjs/
>
> WGLC is open for 2 weeks - so will finish close-of-play on Monday 10th= May.
>
> Kirsty
> (DISPATCH co-chair)
>
> [1] https://mailarch= ive.ietf.org/arch/msg/dispatch/MOp48vAf_K4cjoS9XoFgxBUqXg0/
> [2] https://mailarch= ive.ietf.org/arch/msg/dispatch/TmuVIJS6Umh37oOhiIHv-5Mzkis/
>
>
>
> This information is exempt under the Freedom of Information Act 2000 (= FOIA) and may be exempt under other UK information legislation. Refer any F= OIA queries to ncscinfoleg@ncsc.gov.uk. All material is UK Crown Copyright =C2=A9
--0000000000003b0f4a05c0f78e50--