Re: [EAI] New version of E-mail Authentication for Internationalized Mail draft

"John R Levine" <johnl@taugh.com> Wed, 24 January 2018 14:42 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447E1124D68 for <ima@ietfa.amsl.com>; Wed, 24 Jan 2018 06:42:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=4bj/rKAT; dkim=pass (1536-bit key) header.d=taugh.com header.b=zBZic0kV
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 YT4z8dQohFVh for <ima@ietfa.amsl.com>; Wed, 24 Jan 2018 06:42:43 -0800 (PST)
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 2BFE7124BAC for <ima@ietf.org>; Wed, 24 Jan 2018 06:42:43 -0800 (PST)
Received: (qmail 74800 invoked from network); 24 Jan 2018 14:42:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1242e.5a689b61.k1801; bh=/5R3JUCbtEWx+2q19JxJMPaSW3zwF9W76o1+2/hUYiw=; b=4bj/rKAToJwpfs2cXZmVLQ1QSzex2PAsDzEkjkcEKuktR9jqXy6qJjtfE865Y2XAeIVdHpnhoV2+mb5UWh0PxTzd1n6PZIajA88Zy8ZKeVMLHvce3MO0dN1y9rNtMmlLoABZdc8CwgwFjsSqBLz96MjNcw1ka7tswhNlpw5aDZ3b6YBWcE3YekMvp0AjN3JMhVpjyOSl5o9PUYqdfqa/cI/yIxXJZgfE51Rps6FcpVf0g/EE6T5/djke5vgO1jLZ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1242e.5a689b61.k1801; bh=/5R3JUCbtEWx+2q19JxJMPaSW3zwF9W76o1+2/hUYiw=; b=zBZic0kVJ25ImSbtYGaVlMFryUGmMPNvbL2hocP/0IncUHbs3RDZS8L4L1QNExVxIcKuAjEUWc0GLUB/3ZK0hQ9Qcf100MXU9oiWpFE15bbez5lWVTOabqlbDTpiBVI29vaIeOb7yfjdYYpsxKLgzkZd8i9dpcY+P9S/o24boe0Ct0gEspMahxFLhlSJIZCfMr6EFg3+lmN8iHxvSH/XGK1qNQq4XfEsCpdA8J4z17xCilq6hbHrYTn2i9o3TqSA
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 24 Jan 2018 14:42:41 -0000
Date: 24 Jan 2018 09:42:42 -0500
Message-ID: <alpine.OSX.2.21.1801240939330.23908@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Frank Ellermann" <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Cc: "IETF EAI" <ima@ietf.org>
In-Reply-To: <CAHhFyboKJiDipz1XaCmGCiHpQBOa8cHZUfgXUBADdOTK6OPTpQ@mail.gmail.com>
References: <alpine.OSX.2.21.1801232001100.22978@ary.qy> <CAHhFyboKJiDipz1XaCmGCiHpQBOa8cHZUfgXUBADdOTK6OPTpQ@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ima/yY6TeDIlAU2TSi_PiEeq_8UD0AI>
Subject: Re: [EAI] New version of E-mail Authentication for Internationalized Mail draft
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ima/>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 14:42:45 -0000

> but apparently I thought that local part macros might not work as
> expected (bad enough

Scott mentioned that on another list.  My first suggestion is to say that 
macros that use local parts don't work with EAI addresses, the second is 
to say that you use the UTF-8 local parts as is and if that creates some 
hard to type DNS names, so be it.  (The DNS is 8 bit clean other than 
ASCII case folding so there's no DNS problems.)

It has always been my impression that SPF local parts are fragile even 
with ASCII names, e.g., what DNS name does this entirely valid ASCII local 
part turn into?

    a.b\.c\\d)e

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly