IETF Logo Mail Archive

Re: [ietf-dkim] DKIM and EAI

Scott Kitterman <ietf-dkim@kitterman.com> Fri, 09 February 2018 22:59 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 23168129515 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Fri, 9 Feb 2018 14:59:20 -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 (1024-bit key) reason="fail (message has been altered)" header.d=kitterman.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 hfX5O0lFwxBr for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Fri, 9 Feb 2018 14:59:17 -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 15543128959 for <ietf-dkim-archive@ietf.org>; Fri, 9 Feb 2018 14:59:17 -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 w19MwNGJ002266; Fri, 9 Feb 2018 14:58:24 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=kitterman.com header.i=@kitterman.com header.b=03MjGTlp; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w19MwJTw002261 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf-dkim@mipassoc.org>; Fri, 9 Feb 2018 14:58:21 -0800
Received: from kitterma-e6430.localnet (mobile-166-170-33-206.mycingular.net [166.170.33.206]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 6234BC4015B for <ietf-dkim@mipassoc.org>; Fri, 9 Feb 2018 16:57:21 -0600 (CST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1518217041; bh=4ucVlK7A0mCbvPdAjAJolqMAWHkFF+9W0N5vweN3uU0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=03MjGTlp6KM8hXQoGcCIzBWGAbG70AtCnM+l727vovzq3+jLH0gsmGImGn0OVie1P rK6+09o0PIlLp7Sj7+YAfLHEFCy8FERJGc58pjnJgpZyazWXJ/CIsHX+AGdP/Zgrqr pFhY6kknLWK3+Cq7aMzHzzMI5PBggd3vLoMOIkGU=
From: Scott Kitterman <ietf-dkim@kitterman.com>
To: ietf-dkim@mipassoc.org
Date: Fri, 09 Feb 2018 17:57:16 -0500
Message-ID: <1707398.kN3rUcK64s@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-139-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <alpine.OSX.2.21.1802091700001.56621@ary.qy>
References: <alpine.OSX.2.21.1712052213140.62996@ary.qy> <alpine.OSX.2.21.1802091700001.56621@ary.qy>
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-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

On Friday, February 09, 2018 05:02:00 PM John R. Levine wrote:
> > 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.

Thanks.  I think that's a reasonable resolution of the SPF macro issue that I 
raised.  Not ideal, in theory, but plenty good enough for the corner case it 
is.

Does this need to update RFC 7208 since there are SPF related MUST 
requirements?

Scott K
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

v2.23.0 | Report a Bug | By Email