Re: [dmarc-ietf] Fwd: Agenda requests for Madrid IETF

Alessandro Vesely <vesely@tana.it> Sun, 26 July 2020 09:45 UTC

Return-Path: <vesely@tana.it>
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 CDB073A0D25 for <dmarc@ietfa.amsl.com>; Sun, 26 Jul 2020 02:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.122
X-Spam-Level:
X-Spam-Status: No, score=-2.122 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 R2HNSL_gLr-M for <dmarc@ietfa.amsl.com>; Sun, 26 Jul 2020 02:45:52 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 CC7CF3A0D24 for <dmarc@ietf.org>; Sun, 26 Jul 2020 02:45:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1595756748; bh=Krz+cLCKWcFQLTUipxrHzTeJMzbwT10cpwQ28sqDSeE=; l=2387; h=To:References:From:Cc:Date:In-Reply-To; b=CxBqUGqBYvTxmW1cM6p8nkDAsc13sDAV4D/vivehqrGw4xyV5idKDpOi2pCGylqKY S5+EgpjC0Ak86dL1LHjW3zn94urm6l1F81XgQuF/TB8RPO7QdDeFJQwm47GhtJZiV9 QUiKZ+ptA4DOTCk22OQg+zdZt+3Xh743S+qo+5CIukQRoanZdshhSodRXDFQa
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC053.000000005F1D50CC.00003061; Sun, 26 Jul 2020 11:45:48 +0200
To: Dotzero <dotzero@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <CAOZAAfNL1Fp-Htm5BNeOypo+rQ6ydHxSa=PdkCSEc4B_XqN-sg@mail.gmail.com> <CAJ4XoYdoK_iLi+g7=083danmS3otwikToQDLrrXjH91XE0oZ9g@mail.gmail.com> <CAJ4XoYc_DoVRBHTs1uiY-apR1JbeAy-GdmBi=1EGoLCeeRHM=g@mail.gmail.com> <CAL0qLwb6=-9TJj1PoVxi+fxpvhUeTd6yzW-ZfB4nGb_pfO_MAw@mail.gmail.com> <CAJ4XoYf4+6RCYf28+QfEavtYpp1RD2MSGohM5c+PqZa6tkAQ7A@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Cc: dmarc@ietf.org
Message-ID: <ce9a7316-98d1-e6cc-b626-291591cfef64@tana.it>
Date: Sun, 26 Jul 2020 11:45:48 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAJ4XoYf4+6RCYf28+QfEavtYpp1RD2MSGohM5c+PqZa6tkAQ7A@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PDVCxYwh9COSPtGUNwYyQbYIWN8>
Subject: Re: [dmarc-ietf] Fwd: Agenda requests for Madrid IETF
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: Sun, 26 Jul 2020 09:45:57 -0000

On Sun 26/Jul/2020 04:00:40 +0200 Dotzero wrote:
> On Sat, Jul 25, 2020 at 9:48 AM Murray S. Kucherawy wrote:
>> On Fri, Jul 24, 2020 at 12:05 PM Dotzero wrote:
>>
>>> I would like to see an agenda item as to whether work around "Display
>>> Name" changes are in scope or out of scope for this effort and this working
>>> group. It would seem to me that any such efforts are more appropriate for
>>> the emailcore working group.
>>>
>>
>> A quick read of the current charters suggests to me that it's in scope for
>> neither.  That seems to be especially true for emailcore.
>>
>> Do you have such a change to propose?
>>
>>
> I was hoping for a ruling that such an effort be ruled out of scope for the 
> DMARC effort/working group and further discussions be limited by the Chairs.
> As "Not Douglas E. Foster" (John Levine)  noted, it is a free form field.

Although out of scope, I'd still propose that display name abuse be explicitly 
mentioned in one of the specs as an out-of-scope problem that has to be solved 
at a different level.


> DMARC has been intended from the start to mitigate direct domain
> abuse by 3rd parties. I'm hoping that the working group will make better
> progress by focusing on issues specific to DMARC and not try boiling the
> ocean by trying to "fix" all forms of abuse through this effort. Display
> Name abuse is a broader problem that DMARC simply is not in a position to
> address. This is especially true as most current implementations are at the
> MTA and MUA providers are not visible among the participants in this
> working group. My opinion is that trying to address this problem space in
> this working group is somewhat like trying to push on a rope.


Let me add that, for the sake of Murray's dkim-transform, unlike subject tag 
and footer additions which only need a couple of bits to be undone, display 
name removal would require the full original header field, as in a (partial) z= 
tag.

BTW, dkim-transform, along with From: rewriting, using To:, using Author:, and 
giving up any modifications make for an effective solution of the MLM problem. 
  None of them belongs specifically to DMARC, albeit the spec could mention them.

Dkim-transform, in particular, looks like an update to RFC 6376.  Yet, it might 
be practical for this WG to adopt it.  Shall we discuss that F2F?


Best
Ale
--