Re: [dispatch] Robert Wilton's No Objection on draft-ietf-dispatch-javascript-mjs-13: (with COMMENT)

Mathias Bynens <mths@google.com> Thu, 06 January 2022 10:51 UTC

Return-Path: <mathiasb@google.com>
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 E00D93A1206 for <dispatch@ietfa.amsl.com>; Thu, 6 Jan 2022 02:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.099
X-Spam-Level:
X-Spam-Status: No, score=-17.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-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, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 AFpuKIIY_aUj for <dispatch@ietfa.amsl.com>; Thu, 6 Jan 2022 02:51:03 -0800 (PST)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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 878D83A1207 for <dispatch@ietf.org>; Thu, 6 Jan 2022 02:51:03 -0800 (PST)
Received: by mail-pj1-x102c.google.com with SMTP id r16-20020a17090a0ad000b001b276aa3aabso8076745pje.0 for <dispatch@ietf.org>; Thu, 06 Jan 2022 02:51:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=K4JjeMPVOf65j8rLPzpF/UlXy2bI4bPfunIffJlapoc=; b=G8/kMPzsiiW6TyG1yslEzPAj0JPEZxAAceSZDMb1Sh3T7gnPtJ4aWL28y0Ul9MOChz CA7wIKzRJDY/ZNdFi1sN713IKszWWfjqELbEkFx7WAR4+cHK/fDoGxD/x5S8jzdPXUNA 4cLjcgNYS3O2DUIiQRGB/TrCki6NjpX5dzQwXP3LiO7z2VVg0DfjD2k2CvYYd1FPtLIz jwtcpJZ4hIjLdoOWSVK/tx0pumFi8Y64H00UlTJXEnbuaEeCflqWueyA4EqQHVzh/r6S j0CLt9jUc/lMY8cJ+NJdHzX43tgzBpbHiATFcfC69h6/M/hWgvkmIjE2+urbloIjF4Dp IvsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=K4JjeMPVOf65j8rLPzpF/UlXy2bI4bPfunIffJlapoc=; b=aH5HlcldFCaOJ42Jxf0wAK35LFZlQqJiualdzpILqvidMZhkivAfM4VK83sBr96kNl rSoJZEP4M3lYyz/gtiHkAXzHo1ZpbJuSs7oDjURdJSlWiR88tDLAxA5oB9pjOuSWvUE3 etAQ1WIpOCIAM1r3peCZGMrUqQnObJgVbHoO7kFz78A0VO7GdcJhXpdsaGjaaYbGIom2 XLADqe2SWQZlpsm30m4m9KByGRTiJmMQju1iyLYWKMJDdh50/9JCCE0X5E8wk5c22UfI XDoQOKZe7o4fElnotFD/UWwJpV7encjtk6K5YfehIoGjgfvUJFH1NZD6r8SC59WS7Ct2 uzXw==
X-Gm-Message-State: AOAM532b7NN8gswaWtGYHdn78z9kGaG5wG1yfelhu7jQydvTGmEwrWz1 554vL3H0BeHHw5IP57f2poT10+dpdzDPm52eql0UUg==
X-Google-Smtp-Source: ABdhPJwOOug8EG241jrmdGX4nduVNxDXITqxDzm4zenzSLAuBPCKIjKXSZM9pmARFEpc+ikDmM6LUqpLuzkOEvtd56I=
X-Received: by 2002:a17:90a:fd0e:: with SMTP id cv14mr3961444pjb.197.1641466261543; Thu, 06 Jan 2022 02:51:01 -0800 (PST)
MIME-Version: 1.0
References: <164139103325.1563.3624861447117160382@ietfa.amsl.com>
In-Reply-To: <164139103325.1563.3624861447117160382@ietfa.amsl.com>
From: Mathias Bynens <mths@google.com>
Date: Thu, 06 Jan 2022 11:50:50 +0100
Message-ID: <CADizRgaOppq7NyvhYrbQwXEDxiq3YdwfypsNfUe8VNJtrtryAw@mail.gmail.com>
To: Robert Wilton <rwilton@cisco.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-dispatch-javascript-mjs@ietf.org, dispatch chairs <dispatch-chairs@ietf.org>, DISPATCH WG <dispatch@ietf.org>, Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary="0000000000006ed5bc05d4e7a5cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/c9aIwWovrXLZUOUnJeWaZxnZPEc>
Subject: Re: [dispatch] Robert Wilton's No Objection on draft-ietf-dispatch-javascript-mjs-13: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Jan 2022 10:51:08 -0000

Hi Rob,

Happy to elaborate on this on behalf of the authors.

This paragraph refers to exactly what happened with RFC4329, which this new
draft aims to supersede.

There was no way RFC4329 could have predicted that .mjs / JavaScript
modules would be a thing in the future. But now that this has happened,
it’s important that an RFC exists that captures this implementation
reality, so that the media types are not just a de facto standard but an
actual IETF standard. That’s what we hope to accomplish with this new draft.

It is possible that this process repeats itself in the future. In addition
to “classic scripts” and “modules”, ECMAScript could introduce an
additional script goal in the future. At that point, we might need an
additional media type registration, which would then ideally be
accomplished by updating our draft and superseding it.

I hope this clarifies things. Thanks for your review!

Mathias Bynens

On Wed, Jan 5, 2022 at 2:57 PM Robert Wilton via Datatracker <
noreply@ietf.org> wrote:

> Robert Wilton has entered the following ballot position for
> draft-ietf-dispatch-javascript-mjs-13: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/blog/handling-iesg-ballot-positions/
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Hi,
>
> Thanks for cleaning up the use of these media types.
>
> I've no significant comments, with only a nit level comment that I found
> the
> following paragraph in the introduction to be slightly strange because I
> read
> it as implying (i) to be compliant with this RFC, implementations must also
> read/consider any future RFCs that update it, and (ii) future 'optional'
> updates may break implementation conformance to this RFC, which makes those
> updates seem less optional.  I would propose just deleting this paragraph,
> but
> happy to leave it to the authors discretion.
>
>    This document may be updated to take other content into account.
>    Updates of this document may introduce new optional parameters;
>    implementations MUST consider the impact of such an update.
>
> Regards,
> Rob
>
>
>
>