Re: [Tools-discuss] EAI, threat or menace, was Dates added: 6 and 7 Dec

John R Levine <johnl@taugh.com> Thu, 14 October 2021 15:59 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7333A0B4F for <tools-discuss@ietfa.amsl.com>; Thu, 14 Oct 2021 08:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, SPF_PASS=-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=p3bFSoIa; dkim=pass (2048-bit key) header.d=taugh.com header.b=eCh02F96
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 lX56kimf66Dr for <tools-discuss@ietfa.amsl.com>; Thu, 14 Oct 2021 08:59:32 -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 5E52C3A0B4D for <tools-discuss@ietf.org>; Thu, 14 Oct 2021 08:59:31 -0700 (PDT)
Received: (qmail 6671 invoked from network); 14 Oct 2021 15:59:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=1a0c.616853e2.k2110; bh=hkqwg+GiOtzCuP5yA9PMWyKURgt7fUvhW1q7pmQLnuo=; b=p3bFSoIaRX+IXdLUKMueNtO2GZEcv/6ofXds2XdujQmn/pGBJJN4U6Ty5DYjz2foJbJYqdLXQmabUShJllT1qZkMMMriHUI9uw5sta/p5w1Ndxk060UTAbm1JSVY7/N1D1XqcAOiFw5zmlLV7ty7AvkDw8q+QaHxjsttxbBzJzp+n3HcraDStMmtokE/AOm/F4+vySw3NvCBOl9uC+/VQkmmqSxa+YNXY1wp1+3eM/ZLmTLSjMN00G6enIoWN2rLwsKefAJspBBdrA+5S47mEz7meqI9iWsgPj3Hp+HGAXur6Nu/rDQFiL8ub7ooN8HGtufpHy0gOFqMmfrMIlyKDw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=1a0c.616853e2.k2110; bh=hkqwg+GiOtzCuP5yA9PMWyKURgt7fUvhW1q7pmQLnuo=; b=eCh02F96MIZM+vX9Qcvx+sMsY+0nMhLoysHPo48d6slftf/FFEbUkxcKPB1DnM80rdcIJTcZlcujBFbL+P1U5ux8rGu18Rq6kzcTTHI6bCduefVlX/cjdjoQCR8ZX4dD8ZbLtV2aMD3G1P4l8EgSsLM6NvtRNpk/dy1TuhVlRAm8yqmWtiCmWVVrqCBBc8VD9ErcZGOHlyDk2S3mjYKI+bj0oaxqOEt+ag+7Qp/gUtsZ9N7fMYXtHjFuP924NBCHoHH8fYTglEUmytVAvLQ3uGz92VpeNnvwDlLl03vuZaSNwJrEUqJC9XZPcthriHNtGmJWd+GvNOZuGy1NFD5dHQ==
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; 14 Oct 2021 15:59:30 -0000
Received: by ary.qy (Postfix, from userid 501) id BDC542A57C4B; Thu, 14 Oct 2021 11:59:29 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 66FFB2A57C2C; Thu, 14 Oct 2021 11:59:29 -0400 (EDT)
Date: Thu, 14 Oct 2021 11:59:29 -0400
Message-ID: <79dd3b8-dba1-9e8f-5945-1836c07b15@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Robert Sparks <rjsparks@nostrum.com>, tools-discuss@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <7b838a0c-c914-b432-0eee-8e6952c6cd58@nostrum.com>
References: <20211014031201.B56272A51027@ary.qy> <7b838a0c-c914-b432-0eee-8e6952c6cd58@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/XUasyUh25IyvL5twmN5Bk5FCW4M>
Subject: Re: [Tools-discuss] EAI, threat or menace, was Dates added: 6 and 7 Dec
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2021 15:59:38 -0000

On Thu, 14 Oct 2021, Robert Sparks wrote:
>> By IDN support, do you mean EAI mail with UTF-8 on both sides of an e-mail 
>> address, ...

> Indeed, and yes, we mean the former - it's a project that's had action on and 
> off for several years. Its time to look again to see if we can finish taking 
> the step.

FYI, ICANN is also planning to add EAI support to their Mailman lists, 
although I am reasonably sure they have no clue how hard it is.  It is 
also on the roadmap for Mailman 3 although I doubt they will do anything 
soon unless someone gives it to them.

I can say more about this in December but my strong advice, having been 
doing EAI work for the UASG for several years, is first to enable EAI on 
the IETF's regular mail system.  In theory this is just turning on a 
postfix flag,  In practice, things break and we will learn interesting 
things from what breaks and what is involved in fixing it.

While the smoke clears we can figure out whether it is plausble to EAI-ize 
our mailing lists.  The first 90% of the work is enabling EAI features on 
inbound and outbound mail and the archive which I would expect to be 
fairly straightforward.  The other 90% is that if you want your EAI 
support to be useful, there has to be some way for EAI and ASCII users to 
be on the same list, to arrange to deliver messages from EAI users to 
ASCII mail systems that do not handle EAI mail, and make it at least 
somewhat possible to reply, preferably without making things worse for 
people at systems like Gmail which have ASCII addreses but can send and 
receive EAI mail.  The EAI working group tried to solve the gateway 
problem for a decade and failed, so it seems unlikely that we will do much 
better.  (Needless to say, any solution starting "You can just ..." has 
been tried and failed already.)

R's,
John