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

Dave Crocker <dhc@dcrocker.net> Sat, 26 September 2020 19:59 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 AF8E73A0A0C for <dmarc@ietfa.amsl.com>; Sat, 26 Sep 2020 12:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.113
X-Spam-Level:
X-Spam-Status: No, score=-2.113 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, 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 1sKFWNYPHWsa for <dmarc@ietfa.amsl.com>; Sat, 26 Sep 2020 12:59:56 -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 9A2E03A0A06 for <dmarc@ietf.org>; Sat, 26 Sep 2020 12:59:56 -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 08QK32JS007070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 26 Sep 2020 13:03:02 -0700
To: Scott Kitterman <sklist@kitterman.com>, dmarc@ietf.org
References: <20200815225306.967CC1E9E41D@ary.local> <6484002.GchzCIbhPQ@zini-1880> <aa8eb7e5-e16f-e99d-2164-5654ed0024dd@dcrocker.net> <6537157.XWSk9BjR4o@zini-1880>
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
Message-ID: <f0bf22da-7b79-35d5-09b9-b80f21aafccc@dcrocker.net>
Date: Sat, 26 Sep 2020 12:59:50 -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: <6537157.XWSk9BjR4o@zini-1880>
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/VnooQpHJuFe8tGj628MMUcOmHEI>
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: Sat, 26 Sep 2020 19:59:58 -0000

On 9/26/2020 8:41 AM, Scott Kitterman wrote:
> On Friday, September 25, 2020 11:03:51 PM EDT Dave Crocker wrote:
>> Perhaps you have not noticed but the demonstrated field use of DMARC, to
>> date, tends to be contrary to the design, to the extent anyone thinks
>> that the design carries a mandate that receivers follow the directives
>> of the domain owners.
>>
>> So the text in the draft merely reflects real-world operational style.
> I think it's not nearly as clear as you seem to think.  If the standard is
> users will not 100% do the right thing, then I agree that won't happen, but I
> don't think it's a reasonable standard.  I think the standard ought to be that
> there is an overall tendency towards reduced risk.

And there is no (or perhaps only minuscule) evidence that such a 
tendency is demonstrated.

Even the 'study' you cited uses the word 'slight'.

The larger question is:  where is the body of research and/or experience 
that demonstrates the positive effect you are relying on?  As far as I 
know "trust indicators" have somewhere between a poor and a terrible 
history.  So to the extent you believe they are helpful, please produce 
the body of work demonstrating it.

My real point is that we /know/ there is a critical and demonstrably 
useful -- actually, essential -- function performed by anti-abuse 
filtering engines at receivers, independent of the end-user.  Good ones 
reduce incoming abuse down from roughly 95% of the stream to a tiny 
percent.

DMARC processing is included in some such engines' repertoire.

The proposal adds to that, but based on the Sender: field, rather than 
the From: field.


> My claim is that this proposal is substantially at odds with the protocol as
> documented (#1).

I disagree.

Again, please clarify exactly how it is at odds and please explain in 
detail what real-world processing of DMARC it impedes.


> I think we agree that this proposal is at odds with DMARC as documented.

We do not agree.

Again, rather than making a broad claim, please provide actual detail to 
substantiate your claim.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net