Re: [I18ndir] Review volunteer needed (Fwd: [dispatch] WGLC of draft-ietf-dispatch-javascript-mjs-07)

Pete Resnick <resnick@episteme.net> Thu, 30 April 2020 17:30 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C0573A03F6 for <i18ndir@ietfa.amsl.com>; Thu, 30 Apr 2020 10:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 3bzrvabS6nxO for <i18ndir@ietfa.amsl.com>; Thu, 30 Apr 2020 10:30:32 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80F253A0D88 for <i18ndir@ietf.org>; Thu, 30 Apr 2020 10:30:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 2BB9EAAF7518; Thu, 30 Apr 2020 12:30:28 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6eDhjpdjm-em; Thu, 30 Apr 2020 12:30:26 -0500 (CDT)
Received: from [172.16.1.15] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 6D608AAF74FE; Thu, 30 Apr 2020 12:30:26 -0500 (CDT)
From: "Pete Resnick" <resnick@episteme.net>
To: "John R Levine" <johnl@taugh.com>
Cc: i18ndir@ietf.org
Date: Thu, 30 Apr 2020 12:30:26 -0500
X-Mailer: MailMate (1.13.1r5683)
Message-ID: <8CE808C7-DF4F-45A9-9C17-2D82A8B78A9E@episteme.net>
In-Reply-To: <alpine.OSX.2.22.407.2004301241440.26342@ary.qy>
References: <20200430014516.01551188B50A@ary.qy> <33a39102-0385-e235-1cdc-57cf6dad4f4b@ix.netcom.com> <7AD06F46449F354499AC2E24@PSB> <ACB0D0AB-2271-409D-A9A1-DFFD5A1AEE93@episteme.net> <alpine.OSX.2.22.407.2004301241440.26342@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/dcZ1-1Q1_7wFgHQKF6afM7WRWl4>
Subject: Re: [I18ndir] Review volunteer needed (Fwd: [dispatch] WGLC of draft-ietf-dispatch-javascript-mjs-07)
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2020 17:30:40 -0000

On 30 Apr 2020, at 12:22, John R Levine wrote:

>> the WG to take some action? If I don't hear from anyone, I'll start 
>> accosting people privately.
>
> Nooo, not the Private Accosting.

Obviously you have never experienced my full-out private accosting. :-)

> Summary:
>
> The i18n directorate has some concerns about character set handling in
> draft-ietf-dispatch-javascript-mjs-07.
>
> We understand it to say that if a javascript MIME element does not 
> have a name that ends with .mjs, a consumer ignores the declared 
> charset and looks at the first few bytes of the content for a byte 
> order mark (BOM.) If it finds one, it uses the charset implied by the 
> BOM, which can be UTF-16BE, UTF-16LE, or UTF-8.  If there's no BOM, it 
> uses the declared charset unless there isn't one, in which case it 
> defaults to UTF-8.
>
> We are unaware of any other MIME type that uses this sort of trick to 
> work around mislabelled content, and are concerned that it leads to 
> failures in general MIME code that doesn't handle this special case.  
> We also don't know how important the workaround is in practice, e.g., 
> how many MIME producers still mislabel UTF-16 as UTF-8 or vice versa.
>
> For better interoperation it could say something like producers MUST 
> put the correct charset on any media (same as any other media type) 
> and that consumers SHOULD use the declared charset but MAY do the BOM 
> trick for backward compatibility in certain cases.
>
> It also says the BOM must be removed from the decoded text.  That's 
> confusing since ECMAscript treats a BOM as a space which would be 
> harmless at the start of a block of code.

Thanks for taking up the pen John. If folks think something needs to be 
elaborated or added, or if you have some wordsmithing, do speak up.

I'll check with Barry whether he wants this on the official review form. 
If so, I'll assign the review to you in the datatracker. Otherwise, you 
can just email the dispatch list and sign it "John, stuckee for the 
directorate" or some such.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best