[ietf-dkim] DKIM and EAI

"John R. Levine" <johnl@iecc.com> Wed, 06 December 2017 03:32 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2972128D6F for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 5 Dec 2017 19:32:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=iecc.com
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 ERtgQF-FY3PE for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 5 Dec 2017 19:32:40 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 7B7B0128D64 for <ietf-dkim-archive@ietf.org>; Tue, 5 Dec 2017 19:32:40 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [127.0.0.1]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id vB63RTt3019785; Tue, 5 Dec 2017 19:27:30 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=iecc.com header.i=@iecc.com header.b=w1EGK8D4; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id vB63RObA019762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf-dkim@mipassoc.org>; Tue, 5 Dec 2017 19:27:26 -0800
Received: (qmail 24342 invoked from network); 6 Dec 2017 03:27:06 -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=5f14.5a27638a.k1712; bh=3xaET4iyL14EEvb6cTUivDuPwSaRsVUCPLQDRMSn+qM=; b=w1EGK8D4tB02ldjijhP3yw5Cx37CQlmlEUIFYB8OB0GEnstwcK/ohRmE4P902J5ooT28dfnLaquk7elzJAQOuVB3Uuu3UHSTs7Mjqi1DcmgON6KFQ1z3MEs4VyPMP1RY+FhO+itXdIpmUooC/e/H+9uZSvryCjAgVWyEcqWrSeoqcD715ZO6x0iqxNrR2Z7/zgkqX/WapJNKS9f9eH0qIK57IsldQ3T2P2TtkDUgoZI05g0iQloB0F1XAwr3OsJG
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; 06 Dec 2017 03:27:06 -0000
Date: 5 Dec 2017 22:27:05 -0500
Message-ID: <alpine.OSX.2.21.1712052213140.62996@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: "DKIM List" <ietf-dkim@mipassoc.org>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Subject: [ietf-dkim] DKIM and EAI
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim/>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: "ietf-dkim" <ietf-dkim-bounces@mipassoc.org>

If I may change the topic for a moment ...

I'm working on some stuff for ICANN to help people get EAI mail working. 
One of the underspecified bits of EAI is how authentication works with 
SPF, DKIM, DMARC and now, I suppose ARC.  There's a bunch of places where 
one needs to make arbitrary decisions about what's in ASCII (a-labels) or 
what's in UTF-8 (u-labels.)  I did a draft about it last year:

 	https://datatracker.ietf.org/doc/draft-levine-appsarea-eaiauth/

It would be nice if this could be finished and published, so I have 
something better than an expired draft to point at when people ask me how 
to do DKIM and SPF with their EAI mail.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html