Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field

Scott Kitterman <sklist@kitterman.com> Mon, 28 September 2020 12:38 UTC

Return-Path: <sklist@kitterman.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86FF73A10EC for <dmarc@ietfa.amsl.com>; Mon, 28 Sep 2020 05:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=ADOaHyNM; dkim=pass (2048-bit key) header.d=kitterman.com header.b=oxX9fhYt
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 zsEw1rpUZ4vM for <dmarc@ietfa.amsl.com>; Mon, 28 Sep 2020 05:38:02 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41EEC3A10EB for <dmarc@ietf.org>; Mon, 28 Sep 2020 05:38:01 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id 20291F80284 for <dmarc@ietf.org>; Mon, 28 Sep 2020 08:38:01 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1601296681; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=VHjYPnKeawGYxWLGUsoywHgi/d32J3ey6/v5tVlHRqU=; b=ADOaHyNMb4mYQJPcZHJ180zWrTa+BriIe3FiflyEiTJgXqwue49DHwVmViwSB+Kk+zKGc sDvGLKHoIG/ogCdAQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1601296681; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=VHjYPnKeawGYxWLGUsoywHgi/d32J3ey6/v5tVlHRqU=; b=oxX9fhYt0MCQShQ/US31zHe7wvUrIYnws85SVcyGMFOYZeSBvBVl86Cdqjqd+9rZFPyLS V54JGMPgFQrIAt33yQ1bSeQ0moWMxd7OUkswkAaqDUPfTysHrg4gUZEbmg/XdJZjZ53vJJR END8U6DWzCaAx5fXaEu6McRw27oHngNbJcF59RctvuOzDX7sq5fwxboa+cIEuHtxO8jWJJo o3L14wrbLcYl7Fwv4yV+WtQ4lOEIkRQdgvgIQTe/KaUXH4kwTkZOjmR9kUSAolje2o59oWi TKU0WERijrIvWmLieQ06m7zJKUkkJpmJzVTbhp0RJ4lLIoaNY7b8DUBtacNA==
Received: from zini-1880.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id E9557F801D5 for <dmarc@ietf.org>; Mon, 28 Sep 2020 08:38:00 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Mon, 28 Sep 2020 08:38:00 -0400
Message-ID: <1876967.kAKdQI6qeJ@zini-1880>
In-Reply-To: <a4e016ba-673a-81f0-829b-b3b7adb6fcac@dcrocker.net>
References: <20200927171611.838B321D9BAD@ary.qy> <5069099.lO0Lvmlme3@zini-1880> <a4e016ba-673a-81f0-829b-b3b7adb6fcac@dcrocker.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/I1isL_Azf8hn0mmaH1UKSc6iYN8>
Subject: Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2020 12:38:03 -0000

On Sunday, September 27, 2020 11:44:11 PM EDT Dave Crocker wrote:
> On 9/27/2020 11:22 AM, Scott Kitterman wrote:
> > This seems to me to be an odd view because no RFC is needed to use From
> > and
> > it's relationship to either DKIM signing domain or SPF validated Mail
> > From.
> 
> The DKIM d= value establishes no relationship with any other identifer,
> such as the From: field.  At all.  None.
> 
> DMARC establishes the relationship. DMARC does other things, but for the
> above suggested alternative, this is the functional difference that
> requires DMARC.
> 
> To reiterate: Among currently published specifications, without DMARC
> there is no relationship between DKIM's d= value and the rfc5322.From
> domain name.

I just realized I neglected to respond to this part of your mail.

Right, but my mail server, my rules.  I don't need the IETF's permission to 
make such an association if I find it's a useful token for my analysis.  The 
only thing that requires any kind of formal connection is the connection to 
policy.

If you argue yourself out of the connection to policy, you've argued yourself 
out of DMARC entirely.  In order to generate the data for my classifier, it's 
entirely unnecessary to even look up the DMARC record (it might be useful as 
additional data for a more nuanced analysis, but it not needed to determine 
the relationship between rfc5322.From and DKIM d= or rfc5321.MailFrom).

Scott K