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

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

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3DAC33A0928 for <>; Wed, 29 Apr 2020 23:40:39 -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 Cy7fL_KfkA_l for <>; Wed, 29 Apr 2020 23:40:35 -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 1D3263A0924 for <>; Wed, 29 Apr 2020 23:40:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=dk12062016; t=1588228835; bh=HH4pzFk916cGUSYwLmtD7DZCHNJqETufHWI3 5zbc2xs=; 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=DNt+MN4ZnBHfhqjax4TdSOl+cr952MlUS dr9AlZeuWbd6PibKkyTgS/S48Tr4+EwmlMb7SoNTlTRS0FpJDLv8a4n33gv6UgAeuy+ oEYe3/JRK3oYrvST4COQmF9CEnLfOfrEEe3bq24n92WagWgmv4jKDSNbZ3GJgWbt1DT qFKz/eyv1KbMc6fe9gHBkDIt00iXJCqWj7dX3glT25if9RcdU/xO/L7hf83AvQM4Rz8 0qOVkwmBGuq0QnoGt+hk+TQPimw12S23LRfdy+VGQy5KQFs8OIf3a89ZVxbdo0sP+m+ bzLlu7y1GiR/flPvQRLu8k9dVOCRrwdkcoZGu/5iw==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016;; b=apMBZdj3h7W+u2cAW7Bp27/obFLil0cNBLI3YWGr1Q3hrOF6wlojtLVykh9fQ2ekxi6EXbGauWZS4DJMPkOm11QK5NCVHTLxspzkpUKayRomcjPUA0SA/Gx6Bjqp28J3CLKV36ICZmd+zW1/ppVPzSSbk2/+VCkzj28fUUjwb5hXXY+j1Ky4hIJYYNQAGiH54L4G+AQtHumQ1ONOi6iAnTgjgHA6U+ENSrVZBQyEDDXc1cccpuwk9TVJUqhuY+sHELtP6IbcbGUDnj+hLS0qtAJh9aae5RUIosUyV928T9ABB2+FYHwWIhYUmxLezu8Zh4eajri38VsGflEzY9a1KA==; 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 1jU2s5-000Aux-HO for; Thu, 30 Apr 2020 02:40:33 -0400
References: <20200430014516.01551188B50A@ary.qy> <> <7AD06F46449F354499AC2E24@PSB>
From: Asmus Freytag <>
Message-ID: <>
Date: Wed, 29 Apr 2020 23:40:33 -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: <7AD06F46449F354499AC2E24@PSB>
Content-Type: multipart/alternative; boundary="------------687543C8A86BF76822A8670A"
Content-Language: en-US
X-ELNK-Trace: 464f085de979d7246f36dc87813833b26976a2cdabd2db7a5943ee04b8fa0e096686fa1d6e8847f3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
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 06:40:39 -0000

On 4/29/2020 9:17 PM, John C Klensin wrote:
> John and Asmus,
> It seem to me that we are straying into doing the design (or
> redesign) work that is the responsibility of the WG.  Explaining
> the problem to the WG and suggesting fixes would be entirely
> reasonable.   Trying to convince each other, IMO, a lot less so.
>     john
Good point - let's treat this discussion not as leading up to a
solution but to help us understand what requirements we'd

like to suggest to the WG.


> --On Wednesday, April 29, 2020 19:37 -0700 Asmus Freytag
> <> wrote:
>> On 4/29/2020 6:45 PM, John Levine wrote:
>>> It looks like step 1 is saying that if the text starts with a
>>> BOM, you ignore the declared charset and sniff the BOM
>>> instead, which sounds to me like an ancient workaround that
>>> is perhaps no longer needed.
>> If data are preceded by ("start with")  a BOM, you do want to
>> strip it; you never want to keep it (and the chance that a
>> legitimate text starts with a BOM that has an actual function
>> in the text is perfectly negligible).
>> If you have data that carries a UTF-16 bom it cannot be UTF-8,
>> no matter what the charset declaration says (FF can't be a
>> byte in UTF-8).
>> Therefore, you always want to look for all three.
>> If  it's UTF-8 you confirm you have the good character set
>> and remove it.
>> If it's one of the UTF-16 ones, you switch the charset to
>> UTF-16 (or proper endianness) and remove it. (Or reject the
>> input?)
>>> Given that they are deprecating all of the existing
>>> javascript media types and reviving text/javascript which
>>> 4329 declared obsolete, this might be a good time to say if
>>> you're going to use our lovely new (old) media type, declare
>>> the correct character set so consumers can believe it and
>>> stop doing byte sniffing kludges.
>> There are two issues here. One centers around the fact that
>> BOMs are "invisible". You can work hard at avoiding them, but
>> they may be added by some "helpful" tool.
>> The other is that they serve as a useful consistency check
>> when present.
>> You may write the spec to reject data with initial BOM, but
>> then you'd still need to check for them. You definitely don't
>> want to admit data without checking. Since you already need to
>> check for them, you are better off giving clear instructions
>> of how to make use of the fact that you've detected one.
>> A./