IETF Logo Mail Archive

Re: [EAI] [dmarc-ietf] I18ndir last call review of draft-ietf-dmarc-eaiauth-03

"John R Levine" <johnl@taugh.com> Wed, 20 March 2019 03:14 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 3E3EE1311CF for <ima@ietfa.amsl.com>; Tue, 19 Mar 2019 20:14:18 -0700 (PDT)
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=TURCkUdh; dkim=pass (1536-bit key) header.d=taugh.com header.b=GP0N8d5+
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 2rXtGF4D07fQ for <ima@ietfa.amsl.com>; Tue, 19 Mar 2019 20:14:16 -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 F3E0F130F16 for <ima@ietf.org>; Tue, 19 Mar 2019 20:14:15 -0700 (PDT)
Received: (qmail 19393 invoked from network); 20 Mar 2019 03:14:14 -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=4bbf.5c91b006.k1903; bh=9cYsXoLTGGSEwhZ8Ff5SijRLr2FwEpmNJBryXUqIGyY=; b=TURCkUdh5hkfBaVNFzGHwHdM2RQFUP9RCvqFINz9RpJEBtSt9YavGctEkt3I+eD+2XaC0wr2A3lRk6Y7v8Bs1lzVus0hUbhWNItaQ9oYrUr4VHZ7sev7ek3nnzLe9IY3ndDe7zyfIylqyDKGQ2ALrJCiHJz64GEeNMz7jvwZzCfuuxCwOW8qnm2P6S5wDwYcMO3hRCvQYaoVvS1txRFKyu9z00S1NERFT9emqNkDZVzaY3uzWQmEotEXqcStXGJ0
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=4bbf.5c91b006.k1903; bh=9cYsXoLTGGSEwhZ8Ff5SijRLr2FwEpmNJBryXUqIGyY=; b=GP0N8d5+WLWiK3wev1tjzF0h/qW60gd8AxpaQIRSAir1HDNhUzWcCobHJ7f+You1uWhPRGGPMmZu8DxSWm9MZ4NMuO/x/eXs4nFfYy+M807o3DtyImNhJi9zb9fCD90SjrNoQ2AgfH90sPizjefjHs3OzaWe/NZEa+3AtbucfmrLZf/RYQQOSi57SL2zQus8K87Rj+ILIbfOojwC65lSTg62InGfDBc6xqm9FJplYxe+8Zbvb86VXuU/SiJ373f/
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 20 Mar 2019 03:14:14 -0000
Date: Tue, 19 Mar 2019 23:14:13 -0400
Message-ID: <alpine.OSX.2.21.1903192311190.78847@ary.qy>
From: John R Levine <johnl@taugh.com>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "ima@ietf.org" <ima@ietf.org>
In-Reply-To: <1924d25f-1c81-6b96-be24-1597ece038cd@it.aoyama.ac.jp>
References: <20190319205728.A59CC20103B8D6@ary.qy> <1924d25f-1c81-6b96-be24-1597ece038cd@it.aoyama.ac.jp>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-139395014-1553051654=:78847"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ima/A5wWKvzTwxHZjuvb-TkEFqs-5n8>
Subject: Re: [EAI] [dmarc-ietf] I18ndir last call review of draft-ietf-dmarc-eaiauth-03
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Mar 2019 03:14:26 -0000

On Tue, 20 Mar 2019, Martin J. Dürst wrote:
>> What do we call mail that's not EAI mail?
>
> Maybe just that, 'non-EAI mail'? Or something like "mail that needs the
> SMTPUTF8 extension for transmission"? Or "mail with non-ASCII addresses"?

Non-EAI seems simple enough.

>> It's not ASCII mail, since non-EAI messages can contain any character 
>> sets you want in the message body.

> And in comments in headers, if properly encoded.

With 8BITMIME, which is supported by pretty much every MTA in the world, 
UTF-8 message bodies don't need to be encoded.  They can include literal 
UTF-8 or any other character set that interprets ASCII CR/LF as CR/LF.

I have an updated version of the draft, will post it once the window 
reopens.

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

v2.23.0 | Report a Bug | By Email