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

"John R Levine" <johnl@taugh.com> Wed, 24 January 2018 01:01 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 B154812D88E for <ima@ietfa.amsl.com>; Tue, 23 Jan 2018 17:01:26 -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=6a8grSGN; dkim=pass (1536-bit key) header.d=taugh.com header.b=YOK8hWnP
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 ew5-PdoL5E_F for <ima@ietfa.amsl.com>; Tue, 23 Jan 2018 17:01:25 -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 ECD1D127698 for <ima@ietf.org>; Tue, 23 Jan 2018 17:01:24 -0800 (PST)
Received: (qmail 44120 invoked from network); 24 Jan 2018 01:01:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=ac55.5a67dae4.k1801; bh=vi3OW0MLPTgiaD0oEulRnzTnVLWnYVGk7Yhc6I4C+cM=; b=6a8grSGNf1oeQCrFE8HVnHiyE0236pBjZ6lHgN9ZRgJqkKyLPbK2sS3msF2UObICD0vTSQRujxrj2rd06N1V0Xj3eKSHA2Ygmvfdpj2JALCXDIQJ8BzoDALKJvjTy/nGsl/4pZJzuoU2JmGfGXqI87zv5D28hXnkCju/T7eRWBK1eRSBjkvYU0WdlkCmIdmSZ0OGxh9pZnQ7NpmdnOBfUxdjWdgzxo2cFxSCMvOsc9V8kfnKzIlx9y4O/sChrIdc
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=ac55.5a67dae4.k1801; bh=vi3OW0MLPTgiaD0oEulRnzTnVLWnYVGk7Yhc6I4C+cM=; b=YOK8hWnPvlvcxYN0NLLnYrYtqm/iPLUI0+5nRf8SwpweEsxe2HszqksCnl88gA7OxIJJmn077qZ8slecAMRVhiy4MopLHbp/xUyAjxbpQA/7jdomIedEmqBkK7Lou9/906RDezBEWDo1cgTn1aqVLf6Y1TTQL6OpSP0I3SpKFH9MTOgZxFPeWND97pEpfHpOdWAjXgZUm+OwEbBTVUe0k/vqwG6sHsXHA6Vt9uExKRzIF4fzrEykWIfW3lrRdH82
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 01:01:23 -0000
Date: 23 Jan 2018 20:01:23 -0500
Message-ID: <alpine.OSX.2.21.1801232001100.22978@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: ima@ietf.org
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/qNMLp0aUUYGjONcNxYN21o6jcWE>
Subject: [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 01:01:27 -0000

Read all about it: 
https://datatracker.ietf.org/doc/draft-levine-appsarea-eaiauth/

This is an updated version of a draft I wrote two years ago, that tries to nail 
down the small changes to SPF, DKIM, and DMARC in EAI messages.  This version 
adds a section for the Authentication-Results header.

What it mostly says is that wherever you can have a domain name in a mail 
message header it can be a U-label, and wherever there's a mailbox, the local 
part can be UTF-8, while stuff in the DNS doesn't change and domains there are 
A-labels, same as always.  It's intended to be utterly unsurprising, but 
there's enough ambiguity and well-intended bad advice in existing RFCs that I 
think this is worth doing.

I'm working on an intro to implenting EAI document underwritten by ICANN so it 
would be nice if this were far enough along that I could point to it in the 
relevant sections rather than just Making Stuff Up.

R's,
John