Re: [dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-sender-01.txt

Dave Crocker <dhc@dcrocker.net> Tue, 28 July 2020 10:35 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 BC2253A0ADE for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 03:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-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 TOJ-VVr7RsXu for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 03:35:44 -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 4AD2C3A0AE4 for <dmarc@ietf.org>; Tue, 28 Jul 2020 03:35:44 -0700 (PDT)
Received: from [192.168.1.67] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 06SAcINe022149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Jul 2020 03:38:19 -0700
To: Joseph Brennan <brennan@columbia.edu>
References: <159585216728.2214.8844545419487435807@ietfa.amsl.com> <bff8ea92-82cd-b389-df78-643e17209450@dcrocker.net> <5c414951-6c24-7af1-7a67-cc31a5390e23@tana.it> <47c7f86c-4cb5-712c-63c5-810b8b630823@dcrocker.net> <CAMSGcLCm8LiJ1v2vCqe4pmRBrypumHahmkwJTRQ+u2a0oQrwNQ@mail.gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Cc: IETF DMARC WG <dmarc@ietf.org>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
Message-ID: <a0b81a26-6fd0-934b-eeb5-2d86b9e591cf@dcrocker.net>
Date: Tue, 28 Jul 2020 03:35:36 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAMSGcLCm8LiJ1v2vCqe4pmRBrypumHahmkwJTRQ+u2a0oQrwNQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A9B70C1A064573D1FB239939"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/HJlfBjVxUm620vwH8Er3JcuEybE>
Subject: Re: [dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-sender-01.txt
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, 28 Jul 2020 10:35:53 -0000

On 7/27/2020 1:12 PM, Joseph Brennan wrote:
> Avoiding it by redefining From: to serve the former purpose of Sender: 
> and creating a new Author: to serve the former purpose of From: seems 
> to me to start us down a long road of new header fields every couple 
> of years.
Oh?  This is cast essentially as a fear. Your basis for believing this 
is what?

As for the re-defining of From:, the premise of the Author: proposal is 
that DMARC has already effected that change.


> Verifying that the message really is from phisher.example is a useful 
> data point. The receiving system can choose to mark it with a warning 
> like "you never had mail before from phisher.example".

Mark  it how and for what use? How does that deal with the user-level 
problems caused by From:-field rewriting?


> Consider a DMARC DNS tag for the bank to ask the receiving system to 
> verify the From, while the end-user system would not use that tag. I 
> think this is the distinction that should be made, for mailing lists 
> to work but sensitive data to be more protected than end-user mail.

I don't understand what you are suggesting or how it would work usefully.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net