Re: [ietf-dkim] DKIM and EAI

"John Levine" <johnl@taugh.com> Fri, 09 February 2018 23:24 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 E55A012D82F for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Fri, 9 Feb 2018 15:24:26 -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 header.b=NJc2/PlY; dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=taugh.com header.b=C9de798Y
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 WQRNxyR0ZLu0 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Fri, 9 Feb 2018 15:24:25 -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 B164312D82D for <ietf-dkim-archive@ietf.org>; Fri, 9 Feb 2018 15:24:25 -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 w19NNKEU004891; Fri, 9 Feb 2018 15:23:21 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=iecc.com header.i=@iecc.com header.b=NJc2/PlY; 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 w19NNHtr004886 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf-dkim@mipassoc.org>; Fri, 9 Feb 2018 15:23:19 -0800
Received: (qmail 79006 invoked from network); 9 Feb 2018 23:22:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1349c.5a7e2d2b.k1802; bh=MWBZjP93cpKytwX0dKllUZoP51pmMshAewV/j8Y4dJQ=; b=NJc2/PlYCMUHccbFzK8z+9CPfbO0DiaX7qJQ14BNts0aB+r7P6edXdMZC2qETmDhKk5C1KJOxCqxBwUKszFHr/eZLgstKtN5pqzK2kM5M8c966QFJZf9xhhSBoeYv1y7WTdd2Oj/SbcTeovvE1R5v+Gguf6B7arpYb7ubMADa69q07SGtq8oHvEV7LZC+PHbf+44B5iIPyZ1Jjhkh3O1qRN716WVQWRT6hpdAF2U36qcbEp4eE0+gnd81cYOtghH
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1349c.5a7e2d2b.k1802; bh=MWBZjP93cpKytwX0dKllUZoP51pmMshAewV/j8Y4dJQ=; b=C9de798YedJ/clF8Or6fNlNdJDVpmp+2tX/ZYrILgbStXRKo8DuGZ3CDoy4P+3KLDKoMoOgREYz7bTziR2u5NcwkTvKi/wfqDPs8UNvcmp7BTPHwiWMNC4FHS0wu7+mC8HaSEVEFbB36prCH0hSCd9kS0uX/lX3ZZQ/5dOdfr5coVWUMlDfT1JSN0bAJLfwb9h8PVBXBN/5Eom2CNRf/m0HnSaDJKlKnql27CrWcqOCGwVGNZ0utXlgxaOwbTidA
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 09 Feb 2018 23:22:19 -0000
Received: by ary.qy (Postfix, from userid 501) id 6D9F11A7B7E9; Fri, 9 Feb 2018 18:22:18 -0500 (EST)
Date: 9 Feb 2018 18:22:18 -0500
Message-Id: <20180209232219.6D9F11A7B7E9@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: ietf-dkim@mipassoc.org
In-Reply-To: <1707398.kN3rUcK64s@kitterma-e6430>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Cc: ietf-dkim@kitterman.com
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>

In article <1707398.kN3rUcK64s@kitterma-e6430> you write:
>Does this need to update RFC 7208 since there are SPF related MUST 
>requirements?

I would think so, also 6376, 7489, 7601 since it updates DKIM, DMARC, and A-R specs.

R's,
John
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html