Re: [ietf-dkim] DKIM and EAI

"John R. Levine" <johnl@iecc.com> Fri, 09 February 2018 22:04 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 D8E721270FC for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Fri, 9 Feb 2018 14:04:15 -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 NJ0f-AsUwnsQ for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Fri, 9 Feb 2018 14:04:14 -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 151681270A3 for <ietf-dkim-archive@ietf.org>; Fri, 9 Feb 2018 14:04:14 -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 w19M32E3031322; Fri, 9 Feb 2018 14:03:03 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=iecc.com header.i=@iecc.com header.b=oev0KPHP; 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 w19M2wIU031318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf-dkim@mipassoc.org>; Fri, 9 Feb 2018 14:03:00 -0800
Received: (qmail 62007 invoked from network); 9 Feb 2018 22:02:01 -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:user-agent; s=f233.5a7e1a59.k1802; bh=m1F5Q2jZR1vvYR+yW8GOwHtdwfSWjtZ+dgg+OazFNXY=; b=oev0KPHPdofNoCT363L8OKls3d0SPqLZBcuxKTLJey7xLVmG4lBtCCrHv8OfThp+g+wMFJIxSV95HA0oIzQHhw9SLl6ct9IlN2Xj1mFK5dUHcq1vq7aU+GbZWSx4kvCUzi+iNYW9PpP+cmeCy7/sFqZwKFCCHiYVQsWC7YPT8P6T4He8+D7cfWb/jD/NZvX6NJkAewjQtxcQwr2fCkY4SnDn6xHAgytBlUFviw3DMqdJ/sC9ZvMcGqBKcFFuYC1j
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; 09 Feb 2018 22:02:00 -0000
Date: 9 Feb 2018 17:02:00 -0500
Message-ID: <alpine.OSX.2.21.1802091700001.56621@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: "DKIM List" <ietf-dkim@mipassoc.org>
In-Reply-To: <alpine.OSX.2.21.1712052213140.62996@ary.qy>
References: <alpine.OSX.2.21.1712052213140.62996@ary.qy>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Subject: Re: [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 once again change the topic for a moment ...

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

I pushed out a new version that says something about SPF macros, 
attempting to say that if you try to expand a UTF-8 local part, it doesn't 
match anything.  I figure this is consistent with what would happen if 
your local part was something like foo..bar which won't match anything 
either.

I would appreciate if people would take a look and see if anything seems 
obviously wrong.  I'm doing some EAI whitepapery things for ICANN and it 
would be nice if, for a change, the advice they offer matches reality.

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