IETF Logo Mail Archive

Re: [ietf-822] What about doing more? (was: Re: Fwd: New Version Notification for draft-crocker-inreply-react-01.txt)

John Levine <johnl@taugh.com> Tue, 13 October 2020 17:20 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 E3CF23A0AE0 for <ietf-822@ietfa.amsl.com>; Tue, 13 Oct 2020 10:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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=ziJ5clJr; dkim=pass (2048-bit key) header.d=taugh.com header.b=TKl70JaK
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 Uf3v49vqvwsD for <ietf-822@ietfa.amsl.com>; Tue, 13 Oct 2020 10:20:47 -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 D75A63A0AD9 for <ietf-822@ietf.org>; Tue, 13 Oct 2020 10:20:46 -0700 (PDT)
Received: (qmail 93080 invoked from network); 13 Oct 2020 17:20:44 -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=16b96.5f85e1ec.k2010; bh=HLrKejl6nqdDZff8GDT0M01ylxMocTbPwC8ICOjZwn8=; b=ziJ5clJrTAQJGLJQcH0XpKsaLE2iY9O0UAVsm+JvCCt4xuyYb2tZVD1WNTKas+VSq/6wkxBPHHTmtVXnjsu3tsqVEiNC9fxmri15TX6Q4ut+/dJlQVdMK4W0IuE37fso3BWG8zEkhhTByh93njlExdijzCRC3prI116l0JIjgLJLVLi2wO/3fdE7b3YoWsaL53gtRwAOk9s6rVsdWQSu5xpj3KiONWEv90Hg3EaEj5sBsRHW4EHyeJcW62I0WjyVQx74tygYX7vMLKSG+/WKSa4Yr6uBY79n7gxYRcCaPL0Cs4k0MvhFPVrvs7nSx1MybE3qv3OSk397W6BzdHge1w==
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=16b96.5f85e1ec.k2010; bh=HLrKejl6nqdDZff8GDT0M01ylxMocTbPwC8ICOjZwn8=; b=TKl70JaKMwJddRWqoPNGJ8CeY0XXmpnnJ7sNXJjHK49oc8SdPl0hvAgUExRqVJzXh4YaowKgo5lIIoUUbmkgFJ/nL9aqsgmTIXS1iM33v20NeT9H6IRT1fPR2KHaGFXaHoTbUnhmx3AI69uC/2vytq/xgy1luigkArwQO6amMt9ep92vxLcvxQePG4O7Ilxcbm7pWUuStP2l4FyHOom2d4hvh/V04S5ruvZ3Wfp71BqsbZDvA8YCf3Ca68mdQcMaj/Azs7RN6f+qHf46Axffgvtqjfp1LGFeQWpwjEw/2kC5sKrFTP1rmN1vZVRMqwJtrtS1+ZcnuyKKrES7edZnTQ==
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; 13 Oct 2020 17:20:43 -0000
Received: by ary.qy (Postfix, from userid 501) id 3165F2359F70; Tue, 13 Oct 2020 13:20:42 -0400 (EDT)
Date: Tue, 13 Oct 2020 13:20:42 -0400
Message-Id: <20201013172043.3165F2359F70@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-822@ietf.org
Cc: dcrocker@bbiw.net
In-Reply-To: <3795a81a-d13d-8e4a-2ba7-20bc987f1a1d@dcrocker.net>
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/15BnV2l4OcNV_Tixdfh4SBVgUCs>
Subject: Re: [ietf-822] What about doing more? (was: Re: Fwd: New Version Notification for draft-crocker-inreply-react-01.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: Tue, 13 Oct 2020 17:20:50 -0000

In article <3795a81a-d13d-8e4a-2ba7-20bc987f1a1d@dcrocker.net> you write:
>This thread seems to be about a concern that an implementor will not 
>know how to properly deal with Unicode.  No doubt that's a valid issue, 
>but this specification isn't the place to fix this.  Unicode is a 
>discrete (and complex) topic.

Quite right. Ever since MIME was invented 30 years ago it's been
possible to send mail that includes text with code points that aren't
valid in their putative encoding. I am having trouble understanding
why anyone thinks we this is a problem we should try to solve now for
this tiny application.

>If there is a statement to include, it should be a very general, 
>non-normative pointer to background information about Unicode or Unicode 
>technical issues.

Naah.  Let's leave the worms in the can for once.

R's,
John

v2.23.0 | Report a Bug | By Email