Re: [Json] Add Extension to JS MIME
Adam Roach <adam@nostrum.com> Tue, 15 August 2017 17:29 UTC
Return-Path: <adam@nostrum.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED0721321CB; Tue, 15 Aug 2017 10:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2yRr6pr7zKy2; Tue, 15 Aug 2017 10:29:07 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 C8B68132143; Tue, 15 Aug 2017 10:29:07 -0700 (PDT)
Received: from Svantevit.roach.at (cpe-70-122-154-80.tx.res.rr.com [70.122.154.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v7FHT5iF041686 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 15 Aug 2017 12:29:06 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-154-80.tx.res.rr.com [70.122.154.80] claimed to be Svantevit.roach.at
From: Adam Roach <adam@nostrum.com>
To: Bradley Meck <bradley.meck@gmail.com>, "Matthew A. Miller" <linuxwolf@outer-planes.net>
Cc: json@ietf.org, art-ads@ietf.org
References: <CANnEKUb_pd_T6h5O4gEYttv4wWCcTNmeNvBw+TCiRtsqVgxkQg@mail.gmail.com> <90efaa17-bb8c-7e40-1827-861ec34f2ad6@outer-planes.net> <CANnEKUaFaFwxsEVA1vUyosPn8e-+jG9ESpAvHdxvw1R+LadN9A@mail.gmail.com> <a1f90fa1-3a93-2842-17f1-c45a35a0630d@nostrum.com>
Message-ID: <5ef82202-d8d8-d8e7-3b81-b8d79d44c551@nostrum.com>
Date: Tue, 15 Aug 2017 12:29:05 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <a1f90fa1-3a93-2842-17f1-c45a35a0630d@nostrum.com>
Content-Type: multipart/alternative; boundary="------------8A49EAFF324564D137B4B551"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/tHIuJp7H7DQtwdcQt3p5jld2QIQ>
Subject: Re: [Json] Add Extension to JS MIME
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Aug 2017 17:29:10 -0000
On 8/14/17 8:28 PM, Adam Roach wrote: > On 8/14/17 1:00 PM, Bradley Meck wrote: >> I have never made/updated an RFC. Is there a tutorial on how to do >> this. I don't know what I-D / [DISPATCH] means, it looks like a >> different WG? Do I send a new email to their mailing list? > > For something as small as this, I'm not sure putting it through > DISPATCH is quite the right path. There's no way we'd start a mini-WG > for a document that simply performs IANA registration; there's no WG > that this fits in; and the only other option is AD sponsorship. Thanks for tagging me on the draft-in-progress[1]. This looks like really good material; however, I'll note that its scope is somewhat broader than the original description led me to believe it would be. At the same time, Ben points out to me that DISPATCH actually does have a provision in its charter that allows it to adopt administrative documents, such as IANA registrations. Based on the slightly larger scope, I'd like input from the ART (Applications and Realtime) community at large on the issues that extend beyond the simple filename extension; and, in particular: 1. The question of whether modules need their own MIME type (e.g., application/javascript+module) or MIME type parameter (e.g., application/javascript;goal=module) 2. Formally changing the IANA status of text/javascript from "OBSOLETE" to "COMMON." So I think the right path forward, now that I understand the likely scope of the final document, would be: 1. Get the document in a shape you're happy with, and publish it as a -00 draft. (I believe Matt will be submitting a PR in the near future to help with some simple structural issues; wait for those.) 2. Send an email to the DISPATCH mailing list (https://www.ietf.org/mailman/listinfo/dispatch) with a pointer to the document, asking for the WG to consider adopting it under its "simple administrative documents" clause. Let me know if you have any questions or concerns. /a ____ [1] https://github.com/bmeck/I-D/tree/master/javascript-mjs
- [Json] Add Extension to JS MIME Bradley Meck
- Re: [Json] Add Extension to JS MIME Matthew A. Miller
- Re: [Json] Add Extension to JS MIME Bradley Meck
- Re: [Json] Add Extension to JS MIME Allen Wirfs-Brock
- Re: [Json] Add Extension to JS MIME Matthew A. Miller
- Re: [Json] Add Extension to JS MIME Adam Roach
- Re: [Json] Add Extension to JS MIME Adam Roach
- Re: [Json] Add Extension to JS MIME Matthew A. Miller