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

Asmus Freytag <> Thu, 30 April 2020 20:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0F2EA3A12D0 for <>; Thu, 30 Apr 2020 13:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key); domainkeys=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MXfV246gV12g for <>; Thu, 30 Apr 2020 13:40:50 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 411B73A12CE for <>; Thu, 30 Apr 2020 13:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=dk12062016; t=1588279250; bh=BwIC72wzt47T02j1/Xqxe+c26yOyCMiqr6s8 SrJp0Io=; h=Received:Subject:To:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=lBYz0wtVKvrxtG1oh0m9buPrJ9i3idNkG GNJ1ZOjmLHocvYV6KLXkFv2kNxumwc6O8ebfM7tsYLkw2r9QIPryHycUV7xd7tZFXmt 4MSrwkLIEBwjHUNsY0MBbWjWHDxSBGVVctCSe907s+ree7CF79bkmkojdbvsKe56NTI oKbGN3y8cTd0nP3Q4Qmi6JmvE1YfKrhzc74Eq2oe/dwAmAEDC5St/woJRd33UlC04fi MGynx/vfT4AiZrkweiOxBcbRnmTKhiosVRMEAWJM5tarc3f2PhXT3SCOCzfl6Q+XfeQ wtPenZS37/LecS3MvDp4sfSKIU+FBFkMd/TUEkDMw==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016;; b=Xrdy1tKVqtAxNVnnApIKBD5EQA9i7eF/tLKBU96Q21E58dawhy9dTH2VbqC9rnk1NwiJjrBamfsOh89mse9721t5xUH+o1NHFOx1kPjHRjZarxaMaga4WJemqKGCg/thKNlyalErJa+trzoQyUYAwufZXKRr7JqBiApUqoqyf0oidWEtvMfoV10rwk/i8yemFA5bU0TeNJY6JvMRcGvQauM8S1avcgG434sdMSOz+gM3H/UkSodhl3/vhty8yqU9v9jhmg6PTNUzDC8vNew5yZVzvFnYFflgxkIUyxNuzororpDycvjJ7iou0S9rHcyBng84j3GX3JMMF8H6VvVEKQ==; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [] (helo=[]) by with esmtpa (Exim 4) (envelope-from <>) id 1jUFzC-00017U-Fy for; Thu, 30 Apr 2020 16:40:46 -0400
References: <20200430014516.01551188B50A@ary.qy> <> <7AD06F46449F354499AC2E24@PSB> <> <alpine.OSX.2.22.407.2004301241440.26342@ary.qy>
From: Asmus Freytag <>
Message-ID: <>
Date: Thu, 30 Apr 2020 13:40:48 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.22.407.2004301241440.26342@ary.qy>
Content-Type: multipart/alternative; boundary="------------0DA865038A9515ED48E8FFE9"
Content-Language: en-US
X-ELNK-Trace: 464f085de979d7246f36dc87813833b26976a2cdabd2db7a292d8ac68119a1b82c4532c24b597639350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Archived-At: <>
Subject: Re: [I18ndir] Review volunteer needed (Fwd: [dispatch] WGLC of draft-ietf-dispatch-javascript-mjs-07)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 30 Apr 2020 20:40:56 -0000

Just saw this, and think these items should be raised, but I also like 
some of the other John's feedback on document structure. While it's not 
an i18n issue per se, it really impeded the review. I also think the 
other John and some more direct suggestions on how to write the language 
(and there's the point about NFC and what it implies about Unicode - 
although legacy data almost always is in NFC once converted, per design 
of NFC).


On 4/30/2020 10:22 AM, 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.
> 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.

Good point. In that case, if BOM can happily survive then that removes 
the implicit requirement for BOM sniffing altogether, making a stronger 
case for disallowing it to override anything.

If specific legacy support is required, it should be called out as such.


> Regards,
> John Levine,, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.