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

Dave Crocker <dhc@dcrocker.net> Tue, 29 September 2020 17:26 UTC

Return-Path: <dhc@dcrocker.net>
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 C00E03A0F32 for <dmarc@ietfa.amsl.com>; Tue, 29 Sep 2020 10:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level:
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 TpWS8G6RnxYA for <dmarc@ietfa.amsl.com>; Tue, 29 Sep 2020 10:26:32 -0700 (PDT)
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 47B953A0F30 for <dmarc@ietf.org>; Tue, 29 Sep 2020 10:26:28 -0700 (PDT)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net [24.130.62.181]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 08THTZhQ003768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 29 Sep 2020 10:29:35 -0700
To: hsantos@isdg.net, dmarc@ietf.org
References: <20200927171611.838B321D9BAD@ary.qy> <5069099.lO0Lvmlme3@zini-1880> <a4e016ba-673a-81f0-829b-b3b7adb6fcac@dcrocker.net> <5F73393D.4010805@isdg.net>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <7afb25f6-c258-e92c-fdfe-10fe26ccecec@dcrocker.net>
Date: Tue, 29 Sep 2020 10:26:21 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <5F73393D.4010805@isdg.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jpQVNYVWn_x60uE08SkB_4fjXc0>
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: Tue, 29 Sep 2020 17:26:35 -0000

On 9/29/2020 6:40 AM, Hector Santos wrote:
> On 9/27/2020 11:44 PM, Dave Crocker wrote:
> DKIM has a single signature binding requirement, the 5322.From
>> DMARC establishes the relationship.
> I don't read it that way.
>
> DKIM binds the signer d= domain and the from.domain with no 
> enforcement on it nor any indication that they are related when they 
> not the same (the missing link). 


Absolutely not.  Please re-read the DKIM specification more carefully.  
It is quite explicit that it is doing not doing this.

To the extent that you remain convinced of what you are claiming, you 
need to point to the documentation that supports that view.


> But if they are the same domain, then they are viewed as self-signed 
> and 100% related.

Not based on the DKIM specification.

To the extent that you remain convinced of what you are claiming, you 
need to point to the documentation that supports that view.


> The DKIM POLICY

DKIM has no construct that qualifies as 'policy'.

To the extent that you remain convinced of what you are claiming, you 
need to point to the documentation that supports that view.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net