IETF Logo Mail Archive

Re: [ietf-822] More encoding (was Re: Fwd: New Version Notification for draft-crocker-inreply-react-02.txt)

John Levine <johnl@taugh.com> Sun, 18 October 2020 21:37 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9458E3A0D9C for <ietf-822@ietfa.amsl.com>; Sun, 18 Oct 2020 14:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.05
X-Spam-Level:
X-Spam-Status: No, score=0.05 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=Xe4eWqTJ; dkim=pass (2048-bit key) header.d=taugh.com header.b=dvgest+s
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 MYOpVFEQeEER for <ietf-822@ietfa.amsl.com>; Sun, 18 Oct 2020 14:37:37 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1575A3A0D7E for <ietf-822@ietf.org>; Sun, 18 Oct 2020 14:37:36 -0700 (PDT)
Received: (qmail 83608 invoked from network); 18 Oct 2020 21:37:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=14695.5f8cb59f.k2010; bh=thiksafiPh/JEsD8Xqwoj6bF4kEuX/jukcx8ta7z04k=; b=Xe4eWqTJTf4TRDJF1rJ9TAzFT3ZtQ8Y1TalYtMNmzMtcvh3rnc1m6mSeayKmCQ2T71esrtcMyxyqH+YJDfVhft6h/pFB5h60XNrHILbdr8eRXVVLFlp+IpdwCQegX/oSxkZCLT6irnmY3U4wrFXDXC3MWpX+Y8h1Jrh7KG3oEfVj12N6o3XfeqxhzhqZPMt8bJGedsf8Fl0fKzkWFoKBtS0sSKCO6yian07V0uZJMeRHZuaMuFxZyX4Jm5PfXrpkeWS0rVuAbBIFYMpFe1XNnQ208jLX7rT/9RAkK+oJ42MBzGVh2LjvtBWlEePrDbok4N5SXDNmTBH7b65Avlk7+Q==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=14695.5f8cb59f.k2010; bh=thiksafiPh/JEsD8Xqwoj6bF4kEuX/jukcx8ta7z04k=; b=dvgest+sEc2OK8QbIfXinNBnVMfKBQsRCDSkIhqiMGIe7X5FukAI0oM+ssB+GDFV2pQeyefTE/xsDmp5NTPVNTh35XA/ViPk4eSgVmZiZwqZE4YuJWNAw4HK/UlO9H4MjHPui6YsBnLteC65jMHVxMzkwn8BJUYtCWyitkabllYq8LyDX7YYuZyrNTXBX0w8bXR3mJJ+asEkIHOAZt+8EbMh++armzqOnkOEQwFD6br7llgVXaXEHtHiFvpeA6F7uaZ2XyV+/Hj0lMPgKfPDxveMs2HMzYTYAQYCHxAaAR+TBT4DXFmF9FhNPuxA3TF+bRGTqBjnyZpCUabf/eGkvw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 18 Oct 2020 21:37:34 -0000
Received: by ary.qy (Postfix, from userid 501) id 2B2F823A11AC; Sun, 18 Oct 2020 17:37:33 -0400 (EDT)
Date: Sun, 18 Oct 2020 17:37:33 -0400
Message-Id: <20201018213734.2B2F823A11AC@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-822@ietf.org
Cc: ned.freed@mrochek.com
In-Reply-To: <01RQYDVJUD5A005PTU@mauve.mrochek.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/0qR3nwIC6oYd_xlTYtBzX8TLOKo>
Subject: Re: [ietf-822] More encoding (was Re: Fwd: New Version Notification for draft-crocker-inreply-react-02.txt)
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Oct 2020 21:37:39 -0000

In article <01RQYDVJUD5A005PTU@mauve.mrochek.com> you write:
>> On 10/16/2020 4:01 PM, Ned Freed wrote:
>> >>     In messages that are not Internationalized [RFC6532], emoji and any
>> >>     other non-ASCII characters MUST be encoded using [MIME-Enc].

>> However, I just got an offlist suggestion I'd like to get reactions to:
>
>> > ... consider allowing the emoji to be specified (one option) as "U+1F44D", so:
>> >    In-Reply-React: U+1F44D U+1F622

>> Thoughts?
>
>My thought is "no". It's not that encoded-words are great, it's that they enjoy
>universal deployment. Use encoded-words and access to the unencoded form is one
>routine call away, if that. Anything else is more work, and no matter how much
>better is looks to coding geeks, it's still nonsense to users.

I agree. Every MUA that can display Unicode already has code to handle
encoded-words. Use it. Indeed, having tracked down some MIME bugs in
mail processing libraries I can say that in many cases it would take
extra special case coding to make an MUA *not* do encoded-word
decoding on a new header field.

v2.23.0 | Report a Bug | By Email