
From nobody Sat Jan  2 04:08:15 2021
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 9F2DC3A1127 for <dmarc@ietfa.amsl.com>; Sat,  2 Jan 2021 04:08:13 -0800 (PST)
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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 JlEmwo6_hBeh for <dmarc@ietfa.amsl.com>; Sat,  2 Jan 2021 04:08:10 -0800 (PST)
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 832A53A1126 for <dmarc@ietf.org>; Sat,  2 Jan 2021 04:08:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609589287; bh=Kbc5N0cUuh6KEx562SMziKOCg1pNW8vx0H/Tr76HuXg=; l=1316; h=To:References:From:Date:In-Reply-To; b=AMeQlH04fQVY+eHTe5inuxd61ihNSgVhreMCJR9TTUp6aHBLRucaxkh3VNU5QtAd7 SONyL/8rAGK+JgcRgo1v6r+isp7OH2kULbxCR41vWVrVHakr8xR/xSLH6ByR8nc0zf ZNYduuwM5RUaqWrIClxFTx9p2nDWYr+zquJPbTly0xF9rRXGp29ZSxwE4+qVJ
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC026.000000005FF06227.00007FCD; Sat, 02 Jan 2021 13:08:07 +0100
To: dmarc@ietf.org
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com> <3999b617-b0e7-7341-93df-4a2ccea134e4@tana.it> <64cb14ed-322b-eecb-bed2-13349e19b833@taugh.com> <f0fa378a-f963-c96b-f9a1-a1bea16910fd@mtcc.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <8f438ed3-88cb-58dd-6a12-630e4000ecf9@tana.it>
Date: Sat, 2 Jan 2021 13:08:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f0fa378a-f963-c96b-f9a1-a1bea16910fd@mtcc.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/clkYPE1xT1CoJdvZNOQMqOqqyyY>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 02 Jan 2021 12:08:14 -0000

On Thu 31/Dec/2020 19:36:15 +0100 Michael Thomas wrote:
> On 12/31/20 10:22 AM, John R Levine wrote:
>>>> To what?  The Yahoo address is the only address the scout troop has?
>>>
>>> Copy that to Reply-To: and write a mangled From: that looks troopy but 
>>> passes DMARC.  Just like MLMs do.
>>
>> Lists at MLMs have names that the subscribers will recognize, but the scout 
>> troop only has the Yahoo address.
>>
>> There are certainly kludges that one can apply to circumvent DMARC 
>> rejections, but this is a clear failure, an existing legitimate mail use that 
>> DMARC breaks.
>>
>>
> The entire problem with catering to the long tail is that it is holding hostage 
> better email security. We should stop doing that. There is no right to stasis 
> forevermore. If the scouts email breaks, they can get somebody to fix it. They 
> will thank us in the long run when scammers can't phish using them as a prop.


I agree.  Setting p=none makes DMARC non-actionable.  I, for one, keep p=none 
because of mailing lists.

MLMs seem to be much better than ESPs, since their From: rewriting solves DMARC 
problems effectively, creating only an acceptable noise.

I added two new tickets:
https://trac.ietf.org/trac/dmarc/ticket/92
https://trac.ietf.org/trac/dmarc/ticket/93


Best
Ale
-- 
















From nobody Sat Jan  2 10:47:26 2021
Return-Path: <johnl@iecc.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 D081E3A0CE0 for <dmarc@ietfa.amsl.com>; Sat,  2 Jan 2021 10:47:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level: 
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=kr63DT+D; dkim=pass (2048-bit key) header.d=taugh.com header.b=lGw4Zf0C
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 0moXhEMizoRw for <dmarc@ietfa.amsl.com>; Sat,  2 Jan 2021 10:47:23 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 121FB3A0CDF for <dmarc@ietf.org>; Sat,  2 Jan 2021 10:47:22 -0800 (PST)
Received: (qmail 30916 invoked from network); 2 Jan 2021 18:47:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=78c1.5ff0bfb8.k2101; bh=QAJbsUlBUiVnsbjbrHNIQQoYgBnSespZC3ZjzqziWx0=; b=kr63DT+DYfvxr0AJAWqN/ZUF6bZHERYkJzeATq6zcfryT1xwCaaiWhMrsWRMJNberUsK/s20kO8FNNtX8PODjqcHq2/1viIauc8uqna9WKaDXgL5yA/iB6h4ia0lHKgwlCXDcUdcxq1KgHasN2dSK8Vb3GWj+Z+UKSysfg70F7RMeZVza6ftWFbpYnpr3EGzpSvd3sSHVkJ1D0YZ/DfO7wnCKmz86/QGz2uULLZ1vjNzLYtz3Z1RMppTUs1PSQAinugN1Z73B7A7fo83rkUmjeAkEH9awT1GGFnV0dJrPBH+lzctFVXTAJouUQpkweVAXXUwP4DqSfxZhY6ChrUdrQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=78c1.5ff0bfb8.k2101; bh=QAJbsUlBUiVnsbjbrHNIQQoYgBnSespZC3ZjzqziWx0=; b=lGw4Zf0C2kqfkDq36xqjWHTG7tcrpaBeYmTqvl7S6Po+OARRullwxASlA6Zzf7h+01sd9QPnZcZx26ESVPuDrDbVRGLHYjexfFJk67H6HO2fuLtnFXO89Ab0521jspEOJah6rBqXuiqhk9RkzjpNXD83vA/uqMWZakHsTK/Fc0faSXy1JVUc7Tr+7MCMmgxU7t6u8acwnYOG3t9oSGurYS0k6tDYClSAN0Xqh8WfI9rKLzlArlfc8+l72tthutx+cImqHnfYPg00R1nmJWhC8elX1Ee91pPYHuEeQVDm3FwYrxh58f9uV5Z5rV/UhR/UtRKqzkTr5rBUT/k78Q7F8A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 02 Jan 2021 18:47:20 -0000
Received: by ary.qy (Postfix, from userid 501) id 7CACA4A147E9; Sat,  2 Jan 2021 13:47:18 -0500 (EST)
Date: 2 Jan 2021 13:47:18 -0500
Message-Id: <20210102184719.7CACA4A147E9@ary.qy>
From: "John Levine" <johnl@taugh.com>
Reply-To: uucp@examp1e.com
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <8f438ed3-88cb-58dd-6a12-630e4000ecf9@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PxKwVmy5Ac709ZTRMi-RkOY1vAk>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 02 Jan 2021 18:47:25 -0000

In article <8f438ed3-88cb-58dd-6a12-630e4000ecf9@tana.it>,
Alessandro Vesely  <vesely@tana.it> wrote:
>> The entire problem with catering to the long tail is that it is holding hostage 
>> better email security. We should stop doing that. There is no right to stasis 
>> forevermore. If the scouts email breaks, they can get somebody to fix it. They 
>> will thank us in the long run when scammers can't phish using them as a prop.

I agree too. I'm pretty sure there are more small organizations using
provider e-mail addresses than little private mail servers sending
less than 1000 messages a day, so let's declare both of those out of
scope. Or maybe not.

>I agree.  Setting p=none makes DMARC non-actionable.  I, for one, keep p=none 
>because of mailing lists.

I keep it because none of my domains are particular phish targets and
I would prefer to get my mail delivered, even the part of it that
DMARC can't describe.

R's,
John

PS: This really is off in the weeds, isn't it?


From nobody Sat Jan  2 10:53:57 2021
Return-Path: <dougfoster.emailstandards@gmail.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 949E93A0CE9 for <dmarc@ietfa.amsl.com>; Sat,  2 Jan 2021 10:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 waoB3coeKvoJ for <dmarc@ietfa.amsl.com>; Sat,  2 Jan 2021 10:53:53 -0800 (PST)
Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 771DB3A0CE7 for <dmarc@ietf.org>; Sat,  2 Jan 2021 10:53:53 -0800 (PST)
Received: by mail-vk1-xa2d.google.com with SMTP id d23so5283525vkf.3 for <dmarc@ietf.org>; Sat, 02 Jan 2021 10:53:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=LxUvMMxUsJP5TIPNJc7vMX7iE2M/MkilfTdQ4B5ywfA=; b=TfmIrOoy3dHPUdd7yN5yermqU2oRPBzaH6nIsTpWb9BMc5TjrRUPI2xZt+TTHASaZt XU334MyL9wD3Oae2tg/3N2Giw9OkNd5jja95WWkVJy59JoVlIG79prmoE/TwHD3+gJD3 qGE6aTxdW3kXSU6vWkLtsFhIvNpf8o4n+/6qrhjEpHTv8NZDJmsiWMx82KKYtX2D8zqt CuL1hh7kyzs/lojqpdWLR+9t+clzt0k0weWjtYaNbfRH91tjbOxGpfJNrhK1PI5AucRn ShTwXEVBiPsXqGH5nvJdT0XZyfO2In/3gtU4jzKJJ8ppH8GT7HmzdsFS4TnzsV/roVGM TDzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=LxUvMMxUsJP5TIPNJc7vMX7iE2M/MkilfTdQ4B5ywfA=; b=l7XEenP8Mzt486SBJ+wk8dtWC6dg6L1eDnWPWu2ewL1gBoCx2iylJ7VcuZc/k0HBR6 DU++vUFnH0ZIWHHEmCtHWm1nnEkD8/MrK09OQPcb6nj+3YMZj1eDmVjB7fKVwB5vBhjl X8cF2/BCxDF/7IqUnr+492DhclSbKHZrMBuX0ySDqFzaBc5sSEQ5wa+UfMQxz5GZy5Cl oyatfxYxU+jAc1zVFjNqRu/2mWpwLT7E4r9PTJ/C2YNWu6npO9Qh32ZoIe06mj2qUcjD 4lWUYedYb6a1ylsmzljyfvMd8sDf2KOUx588KqPcm/koNOqOQGvrsyz2aa+7xb5izhZK U7qA==
X-Gm-Message-State: AOAM532pqRrodcAFVx0G9rN7kqBJrrkNyemKqyNvC3CmacIw6VuBWcAm US6yoXFI2QAWPio3e9tzWVLORlR8muGS+DYpqWkZT8Va6dE=
X-Google-Smtp-Source: ABdhPJzKGJD53s4l5DwI4tgAYAGyvzYgjgeDTo+et7kBpfJ6hpbFsUksTX0YtKzxIkeWW5hl/xuD0/Q8FyWljRoPuhY=
X-Received: by 2002:ac5:cde4:: with SMTP id v4mr19903863vkn.21.1609613632403;  Sat, 02 Jan 2021 10:53:52 -0800 (PST)
MIME-Version: 1.0
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com>
In-Reply-To: <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 2 Jan 2021 13:53:41 -0500
Message-ID: <CAH48ZfzDkz4iS2k-+8_-zW-y4m+c1dhRMvPQZmpbLLG2KY0eGA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c8fb0905b7ef6028"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DZlcsKLRbATBS5HEaV7xhfSrXTk>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 02 Jan 2021 18:53:56 -0000

--000000000000c8fb0905b7ef6028
Content-Type: text/plain; charset="UTF-8"

Regarding this section:

   Experience with DMARC has revealed some issues of interoperability
   with email in general that require due consideration before
   deployment, particularly with configurations that can cause mail to
   be rejected.  These are discussed in Section 9.

I suggest replacing it with a scope statement, such as this:

DMARC checks are applicable when a message is received directly from
the domain owner, or received indirectly from a mediator without
in-transit modification.  As discussed in Section 9, these two
criteria do not cover all legitimate email flows.   When a message is
received indirectly with modification, DMARC cannot produce a usable
result, and the message should be evaluated using alternate criteria.
 When messages may have been forwarded with modifications, the
algorithm for distinguishing between authorized and unauthorized
messages becomes difficult to define.



On Thu, Dec 31, 2020 at 12:51 PM John R Levine <johnl@taugh.com> wrote:

> >> The main effect is that the mail they'd been sending from their ESP
> >> with their Yahoo address on the From: line used to work, and now falls
> >> on the floor or worse.
> >
> > Why can't the ESPs do From: rewriting?
>
> To what?  The Yahoo address is the only address the scout troop has?
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000c8fb0905b7ef6028
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Regarding this section:<div><br></div><div><pre style=3D"c=
olor:rgb(0,0,0);white-space:pre-wrap">   Experience with DMARC has revealed=
 some issues of interoperability
   with email in general that require due consideration before
   deployment, particularly with configurations that can cause mail to
   be rejected.  These are discussed in Section 9.</pre><pre style=3D"color=
:rgb(0,0,0);white-space:pre-wrap">I suggest replacing it with a scope state=
ment, such as this:</pre><pre style=3D"color:rgb(0,0,0);white-space:pre-wra=
p">DMARC checks are applicable when a message is received directly from the=
 domain owner, or received indirectly from a mediator without in-transit mo=
dification.  As discussed in Section 9, these two criteria do not cover all=
 legitimate email flows.   When a message is received indirectly with modif=
ication, DMARC cannot produce a usable result, and the message should be ev=
aluated using alternate criteria.   When messages may have been forwarded w=
ith modifications, the algorithm for distinguishing between authorized and =
unauthorized messages becomes difficult to define.</pre><pre style=3D"color=
:rgb(0,0,0);white-space:pre-wrap"><br></pre></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 31, 2020 at 1=
2:51 PM John R Levine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.co=
m</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>&gt;&gt; The main effect is that the mail they&#39;d been sending from the=
ir ESP<br>
&gt;&gt; with their Yahoo address on the From: line used to work, and now f=
alls<br>
&gt;&gt; on the floor or worse.<br>
&gt;<br>
&gt; Why can&#39;t the ESPs do From: rewriting?<br>
<br>
To what?=C2=A0 The Yahoo address is the only address the scout troop has?<b=
r>
<br>
Regards,<br>
John Levine, <a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@tau=
gh.com</a>, Taughannock Networks, Trumansburg NY<br>
Please consider the environment before reading this e-mail. <a href=3D"http=
s://jl.ly" rel=3D"noreferrer" target=3D"_blank">https://jl.ly</a><br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000c8fb0905b7ef6028--


From nobody Sat Jan  2 14:06:22 2021
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 93CA93A0E82 for <dmarc@ietfa.amsl.com>; Sat,  2 Jan 2021 14:06:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcrocker.net
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 dcWyJnriwXqv for <dmarc@ietfa.amsl.com>; Sat,  2 Jan 2021 14:06:19 -0800 (PST)
Received: from bumble.maple.relay.mailchannels.net (bumble.maple.relay.mailchannels.net [23.83.214.25]) (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 AE5B63A0E81 for <dmarc@ietf.org>; Sat,  2 Jan 2021 14:06:18 -0800 (PST)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 7DBC636091C for <dmarc@ietf.org>; Sat,  2 Jan 2021 22:06:17 +0000 (UTC)
Received: from nl-srv-smtpout2.hostinger.io (100-96-9-178.trex.outbound.svc.cluster.local [100.96.9.178]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 674AB360213 for <dmarc@ietf.org>; Sat,  2 Jan 2021 22:06:16 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout2.hostinger.io ([UNAVAILABLE]. [145.14.159.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.11); Sat, 02 Jan 2021 22:06:17 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Battle-Minister: 2a4312c25cbe1f86_1609625177038_1397405837
X-MC-Loop-Signature: 1609625177038:3842476714
X-MC-Ingress-Time: 1609625177038
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net [24.130.62.181]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout2.hostinger.io (smtp.hostinger.com) with ESMTPSA id 7DD3D333EFAF for <dmarc@ietf.org>; Sat,  2 Jan 2021 22:06:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1609625174; bh=Bzup/uBV/IPSGiwPs5y8tzilAa6A0xqjuAwz1ngu1+o=; h=Reply-To:Subject:To:References:From:Date:In-Reply-To; b=AjhS+XKGjnn0piD9gsJq07pkSYrcLRb5H9aScqZxnkEcMT4tJEkUXElZuqswtSYdI O86WTmQg9Qsq19DFVszJ9KTs4xe7vreBLCLTJ2galkUyQ3dVHxkSaoo3CzfILnrxiG XcubbaJMjvacz3dITYehTAIXD7H4MHpVCoER21LojESfbKh6Hu63ZIeU5IJH7PDziq ZPM2oaHoakbH3AL6VDZAq08gf9QkPxxqKduXUDnyhIjym9WL5jVTHb613rOycMSvvb u3uqwZv+AiwIstJKUhWxkhGnTl53MsLTTIf524KVx3P6Pm+j1BMeiKervLw2QYaiJ3 hNdw4PuFxrM7w==
Reply-To: dcrocker@bbiw.net
To: dmarc@ietf.org
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com> <3999b617-b0e7-7341-93df-4a2ccea134e4@tana.it> <64cb14ed-322b-eecb-bed2-13349e19b833@taugh.com> <f0fa378a-f963-c96b-f9a1-a1bea16910fd@mtcc.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <9c126f51-39da-b581-5a97-420e781f97d8@dcrocker.net>
Date: Sat, 2 Jan 2021 14:06:12 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f0fa378a-f963-c96b-f9a1-a1bea16910fd@mtcc.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/lcMPvXde6aZsqgBI4oSOK9xoe1c>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 02 Jan 2021 22:06:21 -0000

> The entire problem with catering to the long tail is that it is holding 
> hostage better email security. We should stop doing that.


The entire problem with statements like these is that they provide a 
cavalier dismissal of established practice, while lacking thoughtful 
cost/benefit detail, as well as failing to consider more general 
application of the 'logic'.

Email (and most other online) security has a sufficiently poor record so 
that claims about what is essential to do -- absent compellingly 
validated, reliable, and precise data -- has nothing at all with what is 
essential to do and everything to do with avoiding serious discussion.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Jan  3 02:49:46 2021
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 900AE3A0D1C for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 02:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.482
X-Spam-Level: 
X-Spam-Status: No, score=-0.482 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 txPWT-Rww2ev for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 02:49:41 -0800 (PST)
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 78D1C3A0D16 for <dmarc@ietf.org>; Sun,  3 Jan 2021 02:49:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609670977; bh=TIX/vjkAYKtY99ede1cWxzKZYh/cMXx6yHztVQn/Dh8=; l=1413; h=To:References:From:Date:In-Reply-To; b=DRjyW6jjzkFGM9udZFL8OMDv8K0nPhusUET5qI06rsSG2h6SNkSpFw0cJLG6S8M3o 6+1g0BgIOzewZMMvXvPEuXjVHddJIxlTCeThb2Sl4yJXpwdgQ17gbvN7FffUggq98L 5xibBLGSgV1jimqwRTZZCQ8eYlhgn05ZwbuvF4WNf1CqrGF7NXUJlsG0Ixm4X
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0CC.000000005FF1A141.00002E5E; Sun, 03 Jan 2021 11:49:37 +0100
To: dmarc@ietf.org
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com> <CAH48ZfzDkz4iS2k-+8_-zW-y4m+c1dhRMvPQZmpbLLG2KY0eGA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <64c4ebd3-4e06-e12e-d072-7ae2562cf4e1@tana.it>
Date: Sun, 3 Jan 2021 11:49:36 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfzDkz4iS2k-+8_-zW-y4m+c1dhRMvPQZmpbLLG2KY0eGA@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/vyc2tkNvxjFODQ5W2sXyh4XLe5c>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 03 Jan 2021 10:49:45 -0000

On Sat 02/Jan/2021 19:53:41 +0100 Douglas Foster wrote:
> Regarding this section:
> 
>     Experience with DMARC has revealed some issues of interoperability
>     with email in general that require due consideration before
>     deployment, particularly with configurations that can cause mail to
>     be rejected.  These are discussed in Section 9.
> 
> I suggest replacing it with a scope statement, such as this:
> 
> DMARC checks are applicable when a message is received directly from
> the domain owner, or received indirectly from a mediator without
> in-transit modification.  As discussed in Section 9, these two
> criteria do not cover all legitimate email flows.   When a message is
> received indirectly with modification, DMARC cannot produce a usable
> result, and the message should be evaluated using alternate criteria.
>   When messages may have been forwarded with modifications, the
> algorithm for distinguishing between authorized and unauthorized
> messages becomes difficult to define.


I disagree.  Limiting the applicability of DMARC is not going to boost its 
actionable usage.  The above wording boils down to suggesting a sequence of 
operations as follows:

1:  check SPF.  If not pass then the message is indirect.

2:  check DKIM.  If not pass then the message is with modification.  Hence 
DMARC results are not usable.


That would nullify the whole protocol.


Best
Ale
-- 





















From nobody Sun Jan  3 03:00:19 2021
Return-Path: <johnl@taugh.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 E546F3A0D2B for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 03:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[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 rZ3eXSrchaNA for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 03:00:10 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 A054B3A0D2C for <dmarc@ietf.org>; Sun,  3 Jan 2021 03:00:10 -0800 (PST)
Received: (qmail 74284 invoked by uid 100); 3 Jan 2021 11:00:09 -0000
Date: 3 Jan 2021 10:59:45 -0000
Message-ID: <20210103105945.74264.qmail@submit.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Ee5V8KRoHWN8WUPeXTvxDdheQ1U>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jan 3 06:00:08 2021
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, 03 Jan 2021 11:00:13 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 28 (23.5%) | 275151 (23.9%) | Michael Thomas <mike@mtcc.com>
 24 (20.2%) | 134423 (11.7%) | Alessandro Vesely <vesely@tana.it>
 20 (16.8%) | 105135 ( 9.1%) | John Levine <johnl@taugh.com>
 15 (12.6%) | 231170 (20.1%) | Todd Herr <todd.herr@valimail.com>
  5 ( 4.2%) |  69353 ( 6.0%) | Seth Blank <seth@valimail.com>
  4 ( 3.4%) |  56360 ( 4.9%) | Dotzero <dotzero@gmail.com>
  4 ( 3.4%) |  42341 ( 3.7%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  4 ( 3.4%) |  25597 ( 2.2%) |  <ned+dmarc@mrochek.com>
  3 ( 2.5%) |  54861 ( 4.8%) | Laura Atkins <laura@wordtothewise.com>
  3 ( 2.5%) |  28200 ( 2.5%) | Hector Santos <hsantos@isdg.net>
  2 ( 1.7%) |  71849 ( 6.2%) | Brotman, Alex <alex_brotman@comcast.com>
  2 ( 1.7%) |  21005 ( 1.8%) | Tim Wicinski <tjw.ietf@gmail.com>
  2 ( 1.7%) |  18623 ( 1.6%) | Murray S. Kucherawy <superuser@gmail.com>
  1 ( 0.8%) |   6488 ( 0.6%) | Kurt Andersen (b) <kboth@drkurt.com>
  1 ( 0.8%) |   5669 ( 0.5%) | Dave Crocker <dhc@dcrocker.net>
  1 ( 0.8%) |   4582 ( 0.4%) | Jim Fenton <fenton@bluepopcorn.net>


From nobody Sun Jan  3 03:36:51 2021
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 AE4EA3A0D7D for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 03:36:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.482
X-Spam-Level: 
X-Spam-Status: No, score=-0.482 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 sGD1fYGI3Gkf for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 03:36:48 -0800 (PST)
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 DA8743A0D7B for <dmarc@ietf.org>; Sun,  3 Jan 2021 03:36:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609673803; bh=Ed2y0qvJ8jjt9/qyEXtGILAzQWr6mDl6cMM3vt3s85k=; l=2073; h=To:References:From:Date:In-Reply-To; b=DKL4A+MlKN2qQpaz5bq35CRcD0L/e2LMunQOd3AZbdenDshdVby7xfSHKdOgD37D0 SHuxBwg5qEmMp8VDIobdmTUPtS8OyNpaFnYlLA4q/tv6qME6Uy/nYAEeHLaoYZewKO wcKOYcq96TrXeUv1KJ7NipUov3semWsqEVfx7n82olfcUz1EKjC+ilWqyk0zn
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC07E.000000005FF1AC4B.000033B8; Sun, 03 Jan 2021 12:36:43 +0100
To: dmarc@ietf.org, John Levine <johnl@taugh.com>
References: <20210102184719.7CACA4A147E9@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <8ef62775-9109-9fdf-6c1f-6c7cd7e92957@tana.it>
Date: Sun, 3 Jan 2021 12:36:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210102184719.7CACA4A147E9@ary.qy>
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/v7RorsPLnXL_4ir3DfiBHMJa1rI>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 03 Jan 2021 11:36:50 -0000

On Sat 02/Jan/2021 19:47:18 +0100 John Levine wrote:
> In article <8f438ed3-88cb-58dd-6a12-630e4000ecf9@tana.it>,
> Alessandro Vesely  <vesely@tana.it> wrote:
>>> The entire problem with catering to the long tail is that it is holding hostage 
>>> better email security. We should stop doing that. There is no right to stasis 
>>> forevermore. If the scouts email breaks, they can get somebody to fix it. They 
>>> will thank us in the long run when scammers can't phish using them as a prop.
> 
> I agree too. I'm pretty sure there are more small organizations using
> provider e-mail addresses than little private mail servers sending
> less than 1000 messages a day, so let's declare both of those out of
> scope. Or maybe not.
> [...]
> 
> PS: This really is off in the weeds, isn't it?


I don't think so.  There is a very practical outcome.  We should expand Section 
9.5, "Interoperability Issues" and say something actually workable.  And its 
referring to Section 5.2 of RFC 6377, "DKIM Author Domain Signing Practices", 
has done its time and can be dropped.

I recall that MLMs were involved in a discussion about DMARC mitigation 
here[*], before From: rewriting started to take root.  Perhaps, things happened 
that way because, after all, IETF's own mailing lists were affected. 
Conversely, we never addressed the Girls Scout troops problem.

Now, MLMs work well even though From: rewriting isn't standardized yet, while 
ESPs apparently didn't get that hint.  Therefore we should describe From: 
rewriting (and possibly some other workarounds of those) in Section 9.5 of 
dmarcbis, so that everybody knows.  BTW, that's our chance to say /how/ to 
rewrite From:.

We should also encourage large free-mailbox providers to publish selectors with 
trusted ESPs' public keys.  Unlike MLM transformations, ESP messages cannot be 
authenticated by other means.


Best
Ale
-- 

[*] dmarc-ietf] IETF Mailing Lists and DMARC
Cullen Jennings, Wed, 02 November 2016 16:00 UTC
https://mailarchive.ietf.org/arch/msg/dmarc/2uVZ0BVpGoXSviXZxhU-G0sDSNc/





















From nobody Sun Jan  3 08:09:28 2021
Return-Path: <johnl@taugh.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 863CF3A0FF8 for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 08:09:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=THeoxzqC; dkim=pass (2048-bit key) header.d=taugh.com header.b=MeEbZI4D
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 zlHJ_GOTI1qW for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 08:09:24 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 8A7CD3A0FF7 for <dmarc@ietf.org>; Sun,  3 Jan 2021 08:09:24 -0800 (PST)
Received: (qmail 56169 invoked from network); 3 Jan 2021 16:09:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=db58.5ff1ec33.k2101; i=johnl-iecc.com@submit.iecc.com; bh=ix7Lj82uouOEjR9lTvXniPEJNsH+/0lhhikuolvyN9M=; b=THeoxzqCK3MlCSzcCLuCWuS74UuQDEy2fdFaV8emecd7qganp5aYaOvi+O4SbKj7CmpSPM7eYyinpkuBqePz4QwAj77S5YH/Bb+LanvAOy+VVVWJjk4zkMvZWNsGk845aBaV0Wf3CoOG29ERqOTFQReygJbzCvXtyDejbQd7tD0uEjjPMBTnbQ7gsIpt5ScZ+7YWQwhaOJmYA9m+UPNI8GtBOJtLDnvKxbcMbZe48JXvP/24Gvu8zLv017kk4y+4oPIW95bedqkSf/HOLnSGxeKCuQOgiv6qs2hqxLdiMQp1rOFvv2lDEoxZMsZVw8biauvwPNJXGZJJhplPD9M7Lg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=db58.5ff1ec33.k2101; olt=johnl-iecc.com@submit.iecc.com; bh=ix7Lj82uouOEjR9lTvXniPEJNsH+/0lhhikuolvyN9M=; b=MeEbZI4DX7WdPU7sBqzSrihO/nOsjKClHMbLNqDp7zQU5rOG78SL6XegkipncH6a8akUlHTeq8Tu69rOBUL7chEkwbhRVBHpTNS2P1RYdlCVak5smSYpqBW/d3GSUWHW/135kNJLycvPTiGc9cDoJ0RMW1kkOWMsdsqSVDXbNhuQFJciD2WCM7PWTEjUsGyvkgZhclpEBpH0i9MbPYlQXE83CmVVw4esmXDC5BfeCUvw8bsa8Pl2dN+Wbdw6zbT54Ubw/XlvIPMgoSJOg41RnFs5rXDAMdpr/sO3ifybAHAcQGBpX7O9GeS/LtxDgzHfR9+Adeirb7fwvhoM6ozbUg==
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 03 Jan 2021 16:09:22 -0000
Date: 3 Jan 2021 11:09:22 -0500
Message-ID: <f2c5b41a-c564-44c4-a215-8357cb0e576@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <8ef62775-9109-9fdf-6c1f-6c7cd7e92957@tana.it>
References: <20210102184719.7CACA4A147E9@ary.qy> <8ef62775-9109-9fdf-6c1f-6c7cd7e92957@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/UxvszDgI346qZZig5AuvLO-3zJw>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 03 Jan 2021 16:09:27 -0000

On Sun, 3 Jan 2021, Alessandro Vesely wrote:
> I don't think so.  There is a very practical outcome.  We should expand 
> Section 9.5, "Interoperability Issues" and say something actually workable.

With some trepidation I ask, like what?

If it's anything like telling mailing lists how to rewrite From lines, 
the answer is no.  That's way out of scope.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

PS: 10.5


From nobody Sun Jan  3 11:57:15 2021
Return-Path: <dougfoster.emailstandards@gmail.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 0B6F73A113C for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 11:57:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 7Cafq0Nx6yPQ for <dmarc@ietfa.amsl.com>; Sun,  3 Jan 2021 11:57:10 -0800 (PST)
Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C15D53A113B for <dmarc@ietf.org>; Sun,  3 Jan 2021 11:57:10 -0800 (PST)
Received: by mail-vk1-xa2d.google.com with SMTP id m145so5729155vke.7 for <dmarc@ietf.org>; Sun, 03 Jan 2021 11:57:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=MiaGd1kYgKCXzGzxEUeP2fSujSXP19rjm0iOzk/fs2Y=; b=r/uLcDWno/7VwRRT3+1cjJq2oA+kZdkhwf3hH61vq1d/j3UwyQLdBGWZRJ5d+SFMFQ s/p6Zr+DpONMH3vlaNrXf2+P2n+erGspD4miEKJ8LKjqPqRC9g41J67JIJQhKJYgzQE4 LRPorJCWqQpmLJeQr4W0uLf6OcYKcZlmD/qdpXfN/nMIUoMYBzFuI0kJEwircMddMlLT AbDuVxyRL/+zxXkYpM4Gzvmj+PJuRQRZRxEafI1rM6D2H0jNDWpls6qTED/qkaOtXxhQ 2Rk2X1q783axwobcF1y3WbrbGPVUc2ODHJ+1h3bLciMuW/jlK+PClOcmMz8Lkdi7lwi7 4ZNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=MiaGd1kYgKCXzGzxEUeP2fSujSXP19rjm0iOzk/fs2Y=; b=V9adgaFPJE/EcgQe8m+mB2055YAFD37KMSgE941Hssk0v31/myCzS0Y9TMo974M0Iz zu0VyuYLt2zHR/W3il3QF9fQ1JfRqegLgUPAHruGip76GgOYLTLIX+7uC+PD8HGlTdiz YsPSfja31byWryvGeuNu2ZPXrv1+PTSsAV6fgWbJfFjGYnLvA4v2sWarx1pjmiDjz06j FLTBT8Yix1jMS2CbdaMNMGXz3eBhWhacSiZSkLhkWocWV9MUnfi85E/2BuJ6K/ATWFqE Vkn0s1LbKVQKYekLCO7SH5iSoaEZpMTXZUx73zpZZyJBmG48ss/1aqZ3tnPUWq5rzbI7 HUGw==
X-Gm-Message-State: AOAM533eaNAXXQQL9a9WrQzl9GP+MoshVmYZRWz5VHZOvVEcR+zsF+vx dj8mVkSM7f970ghZOXz7ZETDzNBTVcAlVEqHSTHdxI1oFbs=
X-Google-Smtp-Source: ABdhPJw3KlntQy4K8IYPUnPQMdQKW7ffxdJMeJlbasvyC/3pllvfvJfLti/nYvMoBKbo0frLL3kiaGF91xFzHFmie3E=
X-Received: by 2002:a1f:20d1:: with SMTP id g200mr42637771vkg.25.1609703829534;  Sun, 03 Jan 2021 11:57:09 -0800 (PST)
MIME-Version: 1.0
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com> <CAH48ZfzDkz4iS2k-+8_-zW-y4m+c1dhRMvPQZmpbLLG2KY0eGA@mail.gmail.com> <64c4ebd3-4e06-e12e-d072-7ae2562cf4e1@tana.it> <CAH48ZfzVkO_oxY1SjeWTqH9oUxHJaAsU2XKBZx-CQ9U0Ba8N0w@mail.gmail.com>
In-Reply-To: <CAH48ZfzVkO_oxY1SjeWTqH9oUxHJaAsU2XKBZx-CQ9U0Ba8N0w@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sun, 3 Jan 2021 14:56:59 -0500
Message-ID: <CAH48Zfwkxbi7pmmY15DKSRyCgc82jEUJ8hHRtvAQ9J3yJHy6_A@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f3fb0005b80460bd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-B-jhg1Fe-qOexZmQOwb9LYrZuo>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 03 Jan 2021 19:57:13 -0000

--000000000000f3fb0005b80460bd
Content-Type: text/plain; charset="UTF-8"

You can disagree about whether this wording is appropriate, but there
should be no disagreement about the scope problem.   We do not have a
protocol which can handle all situations, and much of our discussion is
caused by those who apply DMARC to situations where it does not work.

Lets define "legitimate mail" as used in my proposed text to mean "delivery
is desired by the intended recipient and the message contains nothing that
threatens the interest of the user, the interest of the user's network, or
the policies of the user's organization."   Perhaps this is too
restrictive, because it  excludes advertising which is harmless in its
intent but unwanted by the recipient.

What is clear is that by this definition, mailing list messages are
legitimate, and yet are incompatible with DMARC.  Similarly, messages which
are tagged with informational content by a spam filter and then forwarded
at the request of the primary recipient are also legitimate.  In both
cases, specific messages may be unwanted or hostile, but the class of
messages is wanted.

My exception language is still incomplete, because we have another class of
senders who ignore DMARC but are too important to block.    My list in that
category includes a U.S. government agency and two vendors of cloud-based
products for secure web relay.

We need to set appropriate expectations for product developers, email
gateway operators, and domain owners.    Otherwise we end up with wrong
assumptions which lead to products which mindlessly apply a disposition
without providing adequate exception mechanisms.

Address rewriting is NOT the optimal answer to the problem, because it
hides the forwarding operation without addressing the complications that
forwarding creates for correctly evaluating email reputation.

Email evaluation products need to handle all possible scenarios.  This
includes
- forwarded and not forwarded
- with and without SMTP rewrite
- with and without modification.
- with and without From rewrite
- with and without ARC sets
- whether the email header chain is accurately documented or fraudulently
fabricated.

The only way to handle all of these scenarios is for the email filter to
examine the entire chain of Received headers and other headers.   There is
no simple algorithm for performing this analysis.   There is an opportunity
for IETF to provide ways for legitimate MTAs to facilitate this process,
and ARC is a step in the right direction, but only a first step.

We may be able to promote DMARC adoption by overselling its capabilities,
but I do not see that as a good thing.

DF


On Sun, Jan 3, 2021 at 7:48 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> But we do not have a comprehensive protocol, so we need to set appropriate
> expectations.
>
> I will define "legitimate mail" as used in my proposed text to mean
> "delivery is desired by the intended recipient and the message contains
> nothing that threatens the interest of the user, the interest of the user's
> network, or the policies of the user's organization."
>
> Either mailing list messages, as a class are legitimate, or not -- and we
> have concluded that they are.   (Indvidual messages could be in either
> category.)    Messages that are tagged by a spam filter and then forwarded
> to the recipients alternate mailbox are also legitimate.  We need to set
> appropriate expectations for product developers, email gateway operators,
> and domain owners. My exception language is actually still incomplete,
> because we have the category of senders who ignore DMARC but are too
> important to block.    My list in that category includes a U.S. government
> agency and two vendors of cloud-based email filtering software.
>
> DMARC FAIL can at best provide a data point for a filtering algorithm, as
> was stated in my interchange with Todd.   Claiming more than that will only
> result in misuse of DMARC concepts.
>
> There are real security issues to consider with forwarded mail.   Address
> rewriting hides some of them without solving the problems.   We need an
> in-depth assessment of how to evaluate forwarded mail.   Is this group the
> one to do it or is it assigned somewhere else?
>
> Doug Foster
>
> On Sun, Jan 3, 2021 at 5:50 AM Alessandro Vesely <vesely@tana.it> wrote:
>
>> On Sat 02/Jan/2021 19:53:41 +0100 Douglas Foster wrote:
>> > Regarding this section:
>> >
>> >     Experience with DMARC has revealed some issues of interoperability
>> >     with email in general that require due consideration before
>> >     deployment, particularly with configurations that can cause mail to
>> >     be rejected.  These are discussed in Section 9.
>> >
>> > I suggest replacing it with a scope statement, such as this:
>> >
>> > DMARC checks are applicable when a message is received directly from
>> > the domain owner, or received indirectly from a mediator without
>> > in-transit modification.  As discussed in Section 9, these two
>> > criteria do not cover all legitimate email flows.   When a message is
>> > received indirectly with modification, DMARC cannot produce a usable
>> > result, and the message should be evaluated using alternate criteria.
>> >   When messages may have been forwarded with modifications, the
>> > algorithm for distinguishing between authorized and unauthorized
>> > messages becomes difficult to define.
>>
>>
>> I disagree.  Limiting the applicability of DMARC is not going to boost
>> its
>> actionable usage.  The above wording boils down to suggesting a sequence
>> of
>> operations as follows:
>>
>> 1:  check SPF.  If not pass then the message is indirect.
>>
>> 2:  check DKIM.  If not pass then the message is with modification.
>> Hence
>> DMARC results are not usable.
>>
>>
>> That would nullify the whole protocol.
>>
>>
>> Best
>> Ale
>> --
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>

--000000000000f3fb0005b80460bd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">You can disagree about whether this wording is appropriate=
, but there should be no disagreement about the scope problem.=C2=A0 =C2=A0=
We do not have a protocol which can handle=C2=A0all situations,=C2=A0and mu=
ch of=C2=A0our discussion is caused by those who apply DMARC to situations =
where it=C2=A0does not work.<div><div><br></div><div>Lets define &quot;legi=
timate mail&quot; as used in my proposed text to mean &quot;delivery is des=
ired by the intended recipient and the message contains nothing that threat=
ens the interest of the user, the interest of the user&#39;s network, or th=
e policies of the user&#39;s organization.&quot;=C2=A0 =C2=A0Perhaps this i=
s too restrictive, because it=C2=A0 excludes=C2=A0advertising=C2=A0which is=
 harmless in its intent but unwanted by the recipient.</div><div><br></div>=
<div>What is clear is that by this definition, mailing list messages are le=
gitimate, and yet are incompatible with DMARC.=C2=A0 Similarly, messages wh=
ich are tagged with informational content by a spam filter=C2=A0and then fo=
rwarded at the request of the primary recipient are also legitimate.=C2=A0 =
In both cases, specific messages may be unwanted or hostile, but the class =
of messages is wanted.</div><div><br></div><div><div>My exception language =
is still incomplete, because we have another class of senders who ignore DM=
ARC but are too important to block.=C2=A0 =C2=A0 My list in that category i=
ncludes a U.S.=C2=A0government agency and two vendors of cloud-based produc=
ts for secure web relay.=C2=A0</div><div></div></div><div><br></div><div>We=
 need to set appropriate expectations for product=C2=A0developers, email ga=
teway operators, and domain owners.=C2=A0 =C2=A0 Otherwise we end up with w=
rong assumptions which lead to products which mindlessly apply a dispositio=
n without providing adequate exception mechanisms.</div><div><br></div><div=
>Address rewriting is NOT the optimal answer to the problem, because it hid=
es the forwarding operation without addressing the complications that forwa=
rding creates for correctly evaluating email reputation.</div><div><br></di=
v><div>Email evaluation=C2=A0products need to handle all possible scenarios=
.=C2=A0 This includes=C2=A0</div><div>- forwarded and not forwarded</div><d=
iv>- with and without=C2=A0SMTP rewrite</div><div>- with and without modifi=
cation.=C2=A0</div><div>- with and without From rewrite</div><div>- with an=
d without ARC sets</div><div>- whether the email header chain is accurately=
 documented or fraudulently fabricated.</div><div><br></div><div>The only w=
ay to handle all of these scenarios is for the email filter to examine the =
entire chain of Received headers and other headers.=C2=A0 =C2=A0There is no=
 simple algorithm for performing this analysis.=C2=A0 =C2=A0There is an opp=
ortunity for IETF to provide ways for legitimate MTAs to facilitate this pr=
ocess, and ARC is a step in the right direction,=C2=A0but only a first step=
.</div><div><br></div><div>We may be able to promote DMARC adoption by over=
selling=C2=A0its capabilities, but I do not see that as a good thing.</div>=
<div><br></div><div>DF</div><div><br></div></div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jan 3, 2021 at 7:4=
8 AM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.c=
om">dougfoster.emailstandards@gmail.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">But we do not have =
a comprehensive protocol, so we need to set appropriate expectations.<div><=
br></div><div>I will define &quot;legitimate mail&quot; as used in my propo=
sed text to mean &quot;delivery is desired by the intended recipient and th=
e message contains nothing that threatens the interest of the user, the int=
erest of the user&#39;s network, or the policies of the user&#39;s organiza=
tion.&quot;</div><div><br></div><div>Either mailing list messages, as a cla=
ss are legitimate, or not -- and we have concluded that they are.=C2=A0 =C2=
=A0(Indvidual=C2=A0messages could be in either category.)=C2=A0 =C2=A0 Mess=
ages that are tagged by a spam filter=C2=A0and then forwarded to the recipi=
ents alternate mailbox are also legitimate.=C2=A0 We need to set appropriat=
e expectations for product=C2=A0developers, email gateway operators, and do=
main owners. My exception language is actually still incomplete, because we=
 have the category of senders who ignore DMARC but are too important to blo=
ck.=C2=A0 =C2=A0 My list in that category includes a U.S.=C2=A0government a=
gency and two vendors of cloud-based email filtering software.=C2=A0</div><=
div><br></div><div>DMARC FAIL can at best provide a data point for a filter=
ing algorithm, as was stated in my interchange with Todd.=C2=A0 =C2=A0Claim=
ing more than that will only result in misuse of DMARC concepts.</div><div>=
<br></div><div>There are real security issues to consider with forwarded ma=
il.=C2=A0 =C2=A0Address rewriting hides some of them without solving the=C2=
=A0problems.=C2=A0 =C2=A0We need an in-depth assessment of how to evaluate =
forwarded mail.=C2=A0 =C2=A0Is this group the one to do it or is it assigne=
d somewhere else?</div><div><br></div><div>Doug Foster</div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jan 3, =
2021 at 5:50 AM Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it" tar=
get=3D"_blank">vesely@tana.it</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">On Sat 02/Jan/2021 19:53:41 +0100 Douglas Fost=
er wrote:<br>
&gt; Regarding this section:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Experience with DMARC has revealed some issues of i=
nteroperability<br>
&gt;=C2=A0 =C2=A0 =C2=A0with email in general that require due consideratio=
n before<br>
&gt;=C2=A0 =C2=A0 =C2=A0deployment, particularly with configurations that c=
an cause mail to<br>
&gt;=C2=A0 =C2=A0 =C2=A0be rejected.=C2=A0 These are discussed in Section 9=
.<br>
&gt; <br>
&gt; I suggest replacing it with a scope statement, such as this:<br>
&gt; <br>
&gt; DMARC checks are applicable when a message is received directly from<b=
r>
&gt; the domain owner, or received indirectly from a mediator without<br>
&gt; in-transit modification.=C2=A0 As discussed in Section 9, these two<br=
>
&gt; criteria do not cover all legitimate email flows.=C2=A0 =C2=A0When a m=
essage is<br>
&gt; received indirectly with modification, DMARC cannot produce a usable<b=
r>
&gt; result, and the message should be evaluated using alternate criteria.<=
br>
&gt;=C2=A0 =C2=A0When messages may have been forwarded with modifications, =
the<br>
&gt; algorithm for distinguishing between authorized and unauthorized<br>
&gt; messages becomes difficult to define.<br>
<br>
<br>
I disagree.=C2=A0 Limiting the applicability of DMARC is not going to boost=
 its <br>
actionable usage.=C2=A0 The above wording boils down to suggesting a sequen=
ce of <br>
operations as follows:<br>
<br>
1:=C2=A0 check SPF.=C2=A0 If not pass then the message is indirect.<br>
<br>
2:=C2=A0 check DKIM.=C2=A0 If not pass then the message is with modificatio=
n.=C2=A0 Hence <br>
DMARC results are not usable.<br>
<br>
<br>
That would nullify the whole protocol.<br>
<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>
</blockquote></div>

--000000000000f3fb0005b80460bd--


From nobody Mon Jan  4 03:50:21 2021
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 470163A0C5D for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 03:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.482
X-Spam-Level: 
X-Spam-Status: No, score=-0.482 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 U3aVwZu9Tnqi for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 03:50:18 -0800 (PST)
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 75C263A0C59 for <dmarc@ietf.org>; Mon,  4 Jan 2021 03:50:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609761013; bh=xczu1VpXtW1LC0rWpVOIuS5/ACuXr4RhbEFIpl83eVs=; l=4678; h=To:References:From:Date:In-Reply-To; b=BTEjQ4Fn3drip+tJIWMtJLamMHWg+D6WqpRt26fBpJr65/6pN2jbAKZRdR0i+kna7 qAh8/4l9q/cdF0qZA3oM0AdskNqbpyE0NP7acLX+JaNlUTroin0yGWo5cCmfOxOYi1 4BwmdqtLzXdVrg9GZE5ttzSPnclmv8t5JlR1lNL5oIP41crllFkUwwyDg3uIT
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0CF.000000005FF300F5.00006F82; Mon, 04 Jan 2021 12:50:13 +0100
To: dmarc@ietf.org
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com> <CAH48ZfzDkz4iS2k-+8_-zW-y4m+c1dhRMvPQZmpbLLG2KY0eGA@mail.gmail.com> <64c4ebd3-4e06-e12e-d072-7ae2562cf4e1@tana.it> <CAH48ZfzVkO_oxY1SjeWTqH9oUxHJaAsU2XKBZx-CQ9U0Ba8N0w@mail.gmail.com> <CAH48Zfwkxbi7pmmY15DKSRyCgc82jEUJ8hHRtvAQ9J3yJHy6_A@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <c3aef9ac-c7f9-e129-b71f-33f611237f9a@tana.it>
Date: Mon, 4 Jan 2021 12:50:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48Zfwkxbi7pmmY15DKSRyCgc82jEUJ8hHRtvAQ9J3yJHy6_A@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/Q7oQJqTS8TQOHVZQQWxP1C2iaME>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 04 Jan 2021 11:50:20 -0000

On Sun 03/Jan/2021 20:56:59 +0100 Douglas Foster wrote:
> You can disagree about whether this wording is appropriate, but there
> should be no disagreement about the scope problem.   We do not have a
> protocol which can handle all situations, and much of our discussion is
> caused by those who apply DMARC to situations where it does not work.


Let me object to the consistency of this point of view.  Unlike PGP, DMARC is 
not designed as an end-to-end protocol.  The only way that a user could decide 
on a per-message basis whether or not her message should be subject to which 
policy would be to have a variety of domains configured with each policy and 
then set her From: header field appropriately.  Clearly not a viable mode of 
operation.

A general purpose domain can have email users and some transactional mail as 
well.  DMARC has to be configured to suite all of them.  There are special 
domains, which are highly abused.  They had to direct their users to use 
subdomains for non-transactional mail.  The need to do so can be considered a 
DMARC defect, IMHO.


> Lets define "legitimate mail" as used in my proposed text to mean "delivery
> is desired by the intended recipient and the message contains nothing that
> threatens the interest of the user, the interest of the user's network, or
> the policies of the user's organization."   Perhaps this is too
> restrictive, because it  excludes advertising which is harmless in its
> intent but unwanted by the recipient.


Having advertisements come /From: advertiser/ is a goal.


> What is clear is that by this definition, mailing list messages are
> legitimate, and yet are incompatible with DMARC.


No, MLM messages with rewritten From: are fully compatible.


> Similarly, messages which are tagged with informational content by a spam
> filter and then forwarded at the request of the primary recipient are also
> legitimate.

Not sure.  Spam shouldn't be forwarded.


> In both cases, specific messages may be unwanted or hostile, but the class
> of messages is wanted. >
> My exception language is still incomplete, because we have another class of
> senders who ignore DMARC but are too important to block.    My list in that
> category includes a U.S. government agency and two vendors of cloud-based
> products for secure web relay.
> 
> We need to set appropriate expectations for product developers, email
> gateway operators, and domain owners.    Otherwise we end up with wrong
> assumptions which lead to products which mindlessly apply a disposition
> without providing adequate exception mechanisms.


It is much simpler if the sender is DMARC-aware and sends messages that pass 
DMARC.  There is a plethora of legacy devices and servers that send plain old 
mail.  They are a problem and need to be identified and somehow gatewayed or 
delivered skipping DMARC processing.


> Address rewriting is NOT the optimal answer to the problem, because it
> hides the forwarding operation without addressing the complications that
> forwarding creates for correctly evaluating email reputation.


Hiding depends on how you rewrite and forward.  Receivers can examine ARC 
chains and/or undo MLM transformations so as to deliver a fully meaningful 
message header.


> Email evaluation products need to handle all possible scenarios.  This
> includes
> - forwarded and not forwarded
> - with and without SMTP rewrite
> - with and without modification.
> - with and without From rewrite
> - with and without ARC sets
> - whether the email header chain is accurately documented or fraudulently fabricated.


Girl Scout troops will inevitably fall in the not forwarded category.  ESP 
messages, instead, should come /From: ESP/.


> The only way to handle all of these scenarios is for the email filter to
> examine the entire chain of Received headers and other headers.   There is
> no simple algorithm for performing this analysis.   There is an opportunity
> for IETF to provide ways for legitimate MTAs to facilitate this process,
> and ARC is a step in the right direction, but only a first step.


I wish it ends up in something deterministic that can be used by small and 
large providers alike.


> We may be able to promote DMARC adoption by overselling its capabilities,
> but I do not see that as a good thing.


Some people push for domains to migrate toward a strict policy.  They assume 
that p=none is a transitory status.  I wouldn't call that "overselling", as, in 
fact, having p=none currently provides the best deliverability.  Yet, p=none 
makes DMARC non-actionable, which I think is a limitation.


Best
Ale
-- 


























From nobody Mon Jan  4 04:15:49 2021
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 57A5F3A0C97 for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 04:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.482
X-Spam-Level: 
X-Spam-Status: No, score=-0.482 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 bFps6FbAArrd for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 04:15:46 -0800 (PST)
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 308BD3A0C8B for <dmarc@ietf.org>; Mon,  4 Jan 2021 04:15:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609762544; bh=zlD/h7S363e3Xi2biKpgTK7nZpiXtn/0Flkj+KwMXtk=; l=1655; h=To:References:From:Date:In-Reply-To; b=CNllb3EKznL3IIERdlvR1Jr0X0qwIgjANUhF/tCLR885dFf/ZLEKh6t9UOelHMM9J Ucq322macoTBfJXTs+o2hDG0fXa01wL38+I4ZrcE6/vk70+jex4I8iVavOcVn63tc3 JIC+AB9gLPv8kUb3fmBD7MIn3mbudAQRq2zrFx34qg5nWfzfXeFTmRMgoBuz5
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0D8.000000005FF306F0.0000721E; Mon, 04 Jan 2021 13:15:44 +0100
To: John R Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210102184719.7CACA4A147E9@ary.qy> <8ef62775-9109-9fdf-6c1f-6c7cd7e92957@tana.it> <f2c5b41a-c564-44c4-a215-8357cb0e576@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <58b9ebf7-ee45-87a6-b1e8-c7fe7d2158f3@tana.it>
Date: Mon, 4 Jan 2021 13:15:43 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f2c5b41a-c564-44c4-a215-8357cb0e576@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xyTdgERLCmTTeMKWdEP481k9nyg>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 04 Jan 2021 12:15:47 -0000

On Sun 03/Jan/2021 17:09:22 +0100 John R Levine wrote:
> On Sun, 3 Jan 2021, Alessandro Vesely wrote:
>> I don't think so.  There is a very practical outcome.  We should expand 
>> Section 9.5, "Interoperability Issues" and say something actually workable.
> 
> With some trepidation I ask, like what?


I'd add the whole "Sending side workarounds", mostly as-is, but edited as needed.


> If it's anything like telling mailing lists how to rewrite From lines, the 
> answer is no.  That's way out of scope.


Why?  I read:

     The working group will specify mechanisms for reducing or eliminating
     the DMARC's effects on indirect mail flows, including deployed
     behaviors of many different intermediaries, such as mailing list
     managers, automated mailbox forwarding services, and MTAs that
     perform enhanced message handling that results in message
     modification. Among the choices for addressing these issues are:

(which can hardly be considered fully completed with just ARC), and:

     The working group will document operational practices in terms of
     configuration, installation, monitoring, diagnosis and reporting. It
     will catalog currently prevailing guidelines as well as developing
     advice on practices that are not yet well-established but which are
     believed to be appropriate.

Isn't From: rewriting an operational practice?  It is not so important to tell 
MLMs how to do, since they already seem to do a good job, as it is to tell 
ESPs, which, as you say, don't.


> PS: 10.5


Eh?

10.5.  DMARC Report Format Registry?
Mac OS X 10.5 Leopard?
Magnitude 10.5?

What did you mean?


Best
Ale
-- 









From nobody Mon Jan  4 04:22:37 2021
Return-Path: <laura@wordtothewise.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 663AD3A0C97 for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 04:22:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
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 7TPWvBKfeGtM for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 04:22:34 -0800 (PST)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id 7BBC03A0C9D for <dmarc@ietf.org>; Mon,  4 Jan 2021 04:22:25 -0800 (PST)
Received: from [192.168.0.227] (unknown [37.228.231.27]) by mail.wordtothewise.com (Postfix) with ESMTPSA id 3A85F9F149 for <dmarc@ietf.org>; Mon,  4 Jan 2021 04:22:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1609762943; bh=A6VQz5oSm2zwMr4FD2JDLW6SZx+N2cm3oafGZADECSU=; h=From:Subject:Date:References:To:In-Reply-To:From; b=lkjK58l8B7aaxZUbaaNq8EFLQUrphyJyXebiuui3VT4XbvKVuyG9xl0Uo0fOl5yk7 0wk7qL1aX9fxKxesBPoinyJe0OIIAOpiyMcQmjUdb0rK/qNwEkddl84ckE74ww5GSp uI7oC+aHmJ+0JV2129dlC+HjhZX0f2gSfrWlqQKU=
From: Laura Atkins <laura@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8291518E-6B28-4292-8DB4-81C9A515E899"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 4 Jan 2021 12:22:20 +0000
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com> <CAH48ZfzDkz4iS2k-+8_-zW-y4m+c1dhRMvPQZmpbLLG2KY0eGA@mail.gmail.com> <64c4ebd3-4e06-e12e-d072-7ae2562cf4e1@tana.it> <CAH48ZfzVkO_oxY1SjeWTqH9oUxHJaAsU2XKBZx-CQ9U0Ba8N0w@mail.gmail.com> <CAH48Zfwkxbi7pmmY15DKSRyCgc82jEUJ8hHRtvAQ9J3yJHy6_A@mail.gmail.com> <c3aef9ac-c7f9-e129-b71f-33f611237f9a@tana.it>
To: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <c3aef9ac-c7f9-e129-b71f-33f611237f9a@tana.it>
Message-Id: <123E18E2-71AB-4946-B886-A12A735AA1AC@wordtothewise.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qCe1HIabpnqrdf8HuwBPwi8njbA>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 04 Jan 2021 12:22:36 -0000

--Apple-Mail=_8291518E-6B28-4292-8DB4-81C9A515E899
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 4 Jan 2021, at 11:50, Alessandro Vesely <vesely@tana.it> wrote:
>=20
>=20
>=20
>> Lets define "legitimate mail" as used in my proposed text to mean =
"delivery
>> is desired by the intended recipient and the message contains nothing =
that
>> threatens the interest of the user, the interest of the user's =
network, or
>> the policies of the user's organization."   Perhaps this is too
>> restrictive, because it  excludes advertising which is harmless in =
its
>> intent but unwanted by the recipient.
>=20
>=20
> Having advertisements come /From: advertiser/ is a goal.

Yes.=20

[snip]

>> Email evaluation products need to handle all possible scenarios.  =
This
>> includes
>> - forwarded and not forwarded
>> - with and without SMTP rewrite
>> - with and without modification.
>> - with and without =46rom rewrite
>> - with and without ARC sets
>> - whether the email header chain is accurately documented or =
fraudulently fabricated.
>=20
> Girl Scout troops will inevitably fall in the not forwarded category.  =
ESP messages, instead, should come /From: ESP/.

This incompatible with the above goal of having advertisements come from =
the advertiser.=20

I find it highly problematic that we=E2=80=99re teaching recipients that =
they get official mail from companies that come from an address that is =
not connected to the company at all. It further devalues the 5322.from =
and means that recipients cannot trust the domains that the see there. =
This is even more true when the domain is one they=E2=80=99ve never =
heard of and passes all of the checks and comes in with a =E2=80=98verifie=
d by DMARC.=E2=80=99=20

There is absolutely nothing stopping a phisher from taking advantage of =
this. In fact, phishers currently do send DMARC verified email where the =
domain in the 5322.from is unrelated to the links in the message or to =
the domain being phished.=20

This seems to me to be a step along the path of making DMARC irrelevant =
by teaching recipients that mail with a 5322.from address they don=E2=80=99=
t recognize is legitimate email.=20
=20
laura=20

--=20
Having an Email Crisis?  We can help! 800 823-9674=20

Laura Atkins
Word to the Wise
laura@wordtothewise.com
(650) 437-0741	=09

Email Delivery Blog: https://wordtothewise.com/blog=09








--Apple-Mail=_8291518E-6B28-4292-8DB4-81C9A515E899
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 4 Jan 2021, at 11:50, Alessandro Vesely &lt;<a =
href=3D"mailto:vesely@tana.it" class=3D"">vesely@tana.it</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D""><br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">Lets define "legitimate mail" as used in my proposed text to =
mean "delivery<br class=3D"">is desired by the intended recipient and =
the message contains nothing that<br class=3D"">threatens the interest =
of the user, the interest of the user's network, or<br class=3D"">the =
policies of the user's organization." &nbsp;&nbsp;Perhaps this is too<br =
class=3D"">restrictive, because it &nbsp;excludes advertising which is =
harmless in its<br class=3D"">intent but unwanted by the recipient.<br =
class=3D""></blockquote><br class=3D""><br class=3D"">Having =
advertisements come /From: advertiser/ is a goal.<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Yes.&nbsp;</div><div><br =
class=3D""></div><div>[snip]</div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D""><div class=3D""><blockquote type=3D"cite" =
class=3D"">Email evaluation products need to handle all possible =
scenarios. &nbsp;This<br class=3D"">includes<br class=3D"">- forwarded =
and not forwarded<br class=3D"">- with and without SMTP rewrite<br =
class=3D"">- with and without modification.<br class=3D"">- with and =
without =46rom rewrite<br class=3D"">- with and without ARC sets<br =
class=3D"">- whether the email header chain is accurately documented or =
fraudulently fabricated.<br class=3D""></blockquote><br class=3D"">Girl =
Scout troops will inevitably fall in the not forwarded category. =
&nbsp;ESP messages, instead, should come /From: ESP/.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>This =
incompatible with the above goal of having advertisements come from the =
advertiser.&nbsp;</div><div><br class=3D""></div><div>I find it highly =
problematic that we=E2=80=99re teaching recipients that they get =
official mail from companies that come from an address that is not =
connected to the company at all. It further devalues the 5322.from and =
means that recipients cannot trust the domains that the see there. This =
is even more true when the domain is one they=E2=80=99ve never heard of =
and passes all of the checks and comes in with a =E2=80=98verified by =
DMARC.=E2=80=99&nbsp;</div><div><br class=3D""></div><div>There is =
absolutely nothing stopping a phisher from taking advantage of this. In =
fact, phishers currently do send DMARC verified email where the domain =
in the 5322.from is unrelated to the links in the message or to the =
domain being phished.&nbsp;</div><div><br class=3D""></div><div>This =
seems to me to be a step along the path of making DMARC irrelevant by =
teaching recipients that mail with a 5322.from address they don=E2=80=99t =
recognize is legitimate =
email.&nbsp;</div><div>&nbsp;</div><div>laura&nbsp;</div></div><br =
class=3D""><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px; font-family: Helvetica; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal;"><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
class=3D"">--&nbsp;</div><div class=3D"">Having an Email Crisis? =
&nbsp;We can help! 800 823-9674&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Laura Atkins</div><div class=3D"">Word =
to the Wise</div><div class=3D""><a =
href=3D"mailto:laura@wordtothewise.com" =
class=3D"">laura@wordtothewise.com</a></div><div class=3D"">(650) =
437-0741<span class=3D"Apple-tab-span" style=3D"white-space: pre;">		=
</span></div><div class=3D""><br =
class=3D""></div></span></span></span></span></span></div><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;">Email Delivery Blog: <a =
href=3D"https://wordtothewise.com/blog" =
class=3D"">https://wordtothewise.com/blog</a><span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span></span></span></span></span></span></div></span></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_8291518E-6B28-4292-8DB4-81C9A515E899--


From nobody Mon Jan  4 07:54:02 2021
Return-Path: <Alex_Brotman@comcast.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 DA6CD3A0E6B for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 07:53:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.com
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 1hzwheej1PYg for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 07:53:52 -0800 (PST)
Received: from mx0a-00143702.pphosted.com (mx0a-00143702.pphosted.com [148.163.145.77]) (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 971533A0E68 for <dmarc@ietf.org>; Mon,  4 Jan 2021 07:53:34 -0800 (PST)
Received: from pps.filterd (m0184894.ppops.net [127.0.0.1]) by mx0a-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 104FqX0I014985; Mon, 4 Jan 2021 10:53:34 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=20190412; bh=ozpC4LuJ7Y024JOHqnVEO7Exfqk0q6z8etbX/JS1HPI=; b=z8bWeOOVq+pqMecxAXLSRIYXoD3NcDlSPh/LGDgYhIzOuReEhoGU0Wqv+i5McgLBNT9h hURcxQSpX0lXKkBVJTMEX9VTD72NXjrqx8PagDDsglme+laQ8Rwn07mxpyTrOKxn59eY JJRLOYxbuSPeUwgXxzoxJP99Ajx3OUdZbT+awcviYzgQDmIosWNH87FRb6nqsXxngYZm /sw8BtPQIgOlX0AfRaGj+ynbQYDr1XM3da4N285/iIi2dcLn9fSTGKXlys5+DNNlwGu8 9TWjB6SmRA3TvjV7KZcjQdeY0f9VXbXqYQW/MUBDveqCrVreB9m5D0YBLxgRxqrbqvxy wA== 
Received: from pacdcex52.cable.comcast.com (dlppfpt-wc-1p.slb.comcast.com [96.99.226.136]) by mx0a-00143702.pphosted.com with ESMTP id 35tk149xgb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 04 Jan 2021 10:53:33 -0500
Received: from PACDCEX49.cable.comcast.com (24.40.2.148) by PACDCEX52.cable.comcast.com (24.40.2.151) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 4 Jan 2021 10:53:31 -0500
Received: from PACDCEXEDGE01.cable.comcast.com (76.96.78.71) by PACDCEX49.cable.comcast.com (24.40.2.148) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 4 Jan 2021 10:53:31 -0500
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.176) by webmail.comcast.com (76.96.78.71) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 4 Jan 2021 10:53:21 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4430.namprd11.prod.outlook.com (2603:10b6:208:192::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3721.19; Mon, 4 Jan 2021 15:53:20 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42%7]) with mapi id 15.20.3721.024; Mon, 4 Jan 2021 15:53:20 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: Alessandro Vesely <vesely@tana.it>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Clarification about data integrity within Aggregate Reports (Ticket #40)
Thread-Index: Adbe970H9Y1q6TEdQzWwRVOyDn0z2AAkbDIAAMnKOVA=
Date: Mon, 4 Jan 2021 15:53:20 +0000
Message-ID: <MN2PR11MB4351CB31FD6C315422559BDCF7D20@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB435151665586B5A40D101103F7D70@MN2PR11MB4351.namprd11.prod.outlook.com> <59d0e09e-9296-c16e-94b1-8f344faf88d2@tana.it>
In-Reply-To: <59d0e09e-9296-c16e-94b1-8f344faf88d2@tana.it>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: tana.it; dkim=none (message not signed) header.d=none;tana.it; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:15c0:e939:8606:8e39]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e33e13c5-f496-4089-1579-08d8b0c8dc00
x-ms-traffictypediagnostic: MN2PR11MB4430:
x-microsoft-antispam-prvs: <MN2PR11MB4430392B4E65AC49EF92611FF7D20@MN2PR11MB4430.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Hdxca8869kcHqZIEQ6Xo+4jKLZfTdpl2CAle7d/o5gMPx/JRpbxkdkXqGpT6/SHo3pI2aKvFPcvRWo+XxX7GStvchDFwEMgrFg4Zq/QZFlNLKwBOmC7i2dSCtYEBWW6Hc6TrwX+S27CFCiL5cL97w7l+EJpiBGOxIWkpsnVs6BzIW1p1Dmfg7XK79Ng5vguBTVE2+sgEJ+MZRPkBN4Xxcf7cekH5M4CR5dqoW/6cbckP/TrjkY9j4unzHqZzi4Dkgz1e4ELNLwqTex/PlefBAIrnN9bQrCctpjrB1XOiALZCzNxPATcRQG3EZw6qvOxg3MYv0X5TJ82uYgfiKQc5hEEAyl/IMkNvMx7ztuEkmo+hcjh6yw4yi8x5Bx/okWjk8Afeji6moUyz5CmGYWzHw9nBCc4kKzf4JchEeD+mWAPlQ3Oh9BLnSCP63FuuTaY2fd8BNOWSzd/bnU8PrtmPyQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(396003)(39860400002)(366004)(376002)(136003)(53546011)(6506007)(19627235002)(110136005)(316002)(8676002)(7696005)(83380400001)(86362001)(2906002)(71200400001)(52536014)(76116006)(186003)(9686003)(55016002)(66946007)(5660300002)(66446008)(64756008)(66556008)(66476007)(8936002)(33656002)(966005)(478600001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?zD6uGFb+l9rhWeBLpGx7pOo1hDHPzi11aJ0H4yL4JWZHOaf+6EqOytUh754F?= =?us-ascii?Q?XM//iaHRmU4w23mpoTfvRTG/AktX0S8T8d3Wgl8+D/oq39QcJLKFOng0mMR4?= =?us-ascii?Q?g/E50wIiHoJ2K0fsfWTwe0T7LtHVbOX6cK8Ry+TD5POFA+8sfNmDEk/wYsGI?= =?us-ascii?Q?+EWsYI/SWTV7GzmJEkWafWd6VMM4+cyk1BSSngOn9IgPG1AXZyDxsHYAr8H1?= =?us-ascii?Q?Wh+bR7hmgXN26Bc7IXi27wN+8j9EUwzJf3LpFGyAQd1vqk2MksJ2mpRgxZ7v?= =?us-ascii?Q?MjuKfiyMgSyhi5TQCSahS9vbVNKZCU5Tf76I5egM35ADkL/BCWqzc9HTZcIy?= =?us-ascii?Q?RMhP1kR6/rBf3rYmY1qICRbnC3IExz+2Q1jTA1Q3GfwL0CZrdsYT3tFoSIT6?= =?us-ascii?Q?7Dt6HdTewjbNbidDi9GmhuY/F52bCnZ92XmJP9o9+af9N2+fG6+Ht2zNyjY2?= =?us-ascii?Q?C/WY8feXLCNdn99RAICvAv1izdrHyAqrtlrh9FdDqm4LMhDtvV0YT4yNUsRv?= =?us-ascii?Q?7fp9ZE8UieDpuWIZKELqCkAojDeXdQa3HZSUyPBtgoyqwGapRGmH1w1z1jqW?= =?us-ascii?Q?7RUPRiGxwkCYHN12tZE/7UWz2ZxnDtupkhStY7q7pZiOB55lJ4SX/dFagMN3?= =?us-ascii?Q?UhgwkirvKAps+SnMxQIkAjECfsquXTDV2q1KwWZwBkokFzFDJaDmTR2sh0Z7?= =?us-ascii?Q?MG2vspzl0E1rHiwpt3qffaXL0SYjPo9FndG6zIsAHK7iImGLTfj7JR/7W7Mi?= =?us-ascii?Q?V70Ik8AtGEJb7LNARioEJOqfY4aLP57AV4bSrLb3F43WMTn9vy7zQvJwnFQG?= =?us-ascii?Q?CrBH9GHEKFqufV6GxWrdVR+S42jOaMhuqsNJv8DfJbR8Onvgjynz8UHKUCL4?= =?us-ascii?Q?5seQcKOy7ZFXZc0GCya3hlTFBgl6f2bTKYWb6UnrBxqng9WswmGvqKx5Vxts?= =?us-ascii?Q?nvncfD8h3qdGAd6PxuGjb2bGbR75KiZt+cnytVUJyufIAwEhqtSV2SdJn3/f?= =?us-ascii?Q?Eof9CFKG411tLOVmDd1ZnB2pHyCq+W52CCzapLFcO2B/8JU=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZPZdV7byO84M6eZklPRBVBQb/IwOt/N1FYA3guqiBwsbJV7mhd9DSAp2H057LdQzrxxb2lJQocT4jr2iy/xAVolv6DtZlRfL2W9+dhhUS3jVaylr0ZiwdmvMpeRUymCJU4LMI9hoh9gBjj8BUzi4sLQ8eabb/bIwTLgdQMD+q4nsFxZrz8ibyYgoHN1kWfY7TqvRk0yUXJMIr7tMe9A3o0vcpYry1wdPtrSnEAbtD6KwGqqFPy/LXAJvZPkm3VLgqSw7K2GMAeFGX6zafSpA1owf9OD/w5KpHRQ4SyKI1866+mD3QWSSJZ/bQWNDXtZz7QYIkHZkCIXN35Opn7wrtQ==
arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=z+OFrBzzDYVHlhXZEkQ1wOEc+mXRaGswKu6J5G0+ytg=; b=MJhlmqZUzbrRDrBN29esjLJT1FnbG5aifKUKTV3Fg0vwlCri1y8J2cIBk//F7+tKe4t9mUtpnR50/y9kQxXuTJoFFW5PT/Q5UMzopURSkpZpPCb9fQrZDQQG26kjVILP2fUXTXI8/rPKlcTLWtdmnG6xuZeuOaJPw9ABjf44rXMJNn58Us+5MlIxHe7A/GW7g1pbt66o4Tgb/wpKEKOHffoyqIU1gqaLvi0SO1VwVOi2dmePdNJQ9T/G7KNaH9wjVJgP3iGNr/59HBB8sm79iS+s8ckQ3++C/q709527fHL0mDxZO9VCVWy99QvvGb0Nv4kHZNJKdk1FrCXSdUkEZQ==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=comcast.com; dmarc=pass action=none header.from=comcast.com; dkim=pass header.d=comcast.com; arc=none
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: MN2PR11MB4351.namprd11.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: e33e13c5-f496-4089-1579-08d8b0c8dc00
x-ms-exchange-crosstenant-originalarrivaltime: 04 Jan 2021 15:53:20.2047 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 906aefe9-76a7-4f65-b82d-5ec20775d5aa
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: QVgIElSVw5krbFASy/7rrt8VlEMv+0lzhCT4U00bjWrH/FNTnmnfaptjyW3poQ3BOKgztwTpZ4iDP0Vv/hiO+CyEcFka5n6BE4n/FnVcL64=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4430
x-originatororg: comcast.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWS
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-04_10:2021-01-04, 2021-01-04 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/u8F8miduS9-_0bIEwmwn29l3_uM>
Subject: Re: [dmarc-ietf] Clarification about data integrity within Aggregate Reports (Ticket #40)
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, 04 Jan 2021 15:53:58 -0000

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

> -----Original Message-----
> From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Alessandro Vesely
> Sent: Thursday, December 31, 2020 10:27 AM
> To: dmarc@ietf.org
> Subject: Re: [dmarc-ietf] Clarification about data integrity within Aggre=
gate
> Reports (Ticket #40)
>
> On Wed 30/Dec/2020 23:18:35 +0100 Brotman, Alex wrote:
> > Hello folks,
> >
> > There's an open ticket
> (https://urldefense.com/v3/__https://trac.ietf.org/trac/dmarc/ticket/40__=
;!
> !CQl3mcHX2A!VCWZO-
> 6THaYEt8r1yDE9TgQzeJyuFmGpwSepa3SWwao3ViUQfPaxJ5FrbnTPKuzHLj6b
> $ ) noting that we should clarify what constitutes valid data in a report=
. For
> example, the report cannot state that DMARC-DKIM was a "pass" when
> DKIM itself was a failure.  See the original thread here:
> >
> > https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/dmar
> > c/Ii_dLXFzBNnRP361F922ty789I8/__;!!CQl3mcHX2A!VCWZO-
> 6THaYEt8r1yDE9TgQz
> > eJyuFmGpwSepa3SWwao3ViUQfPaxJ5FrbnTPKvlFgYhq$
> >
> > It seems like the gist is that within the report it should never happen=
 that
> DKIM or SPF are noted to have passed in the context of DMARC if they have
> not passed on their own.  It should also be properly noted by the reporte=
r if
> they override with local policy.  Not by overriding the SPF/DKIM failures=
 (and
> showing them as incorrectly passing), but instead by noting that local po=
licy
> overrides properly (regardless of whether that override is higher or lowe=
r).
> >
> > Does that seem properly summarized?
>
>
> If the aggregate report content, Section 2.2, was well explained, the abo=
ve
> text would be redundant.  The point is that Section 2.2 looks like a high=
 level
> list of features.  It is completely useless for implementing a report pro=
ducer,
> let alone a consumer.  We have to rewrite that section, possibly trying t=
o re-
> use the same wording and the same order of appearance of concepts, so as
> to minimize readers' confusion, but strictly matching the content of Appe=
ndix
> A (was Appendix C).
>

I don't think I disagree here, but I want to be clear on what you're reques=
ting.  You'd like to see a more verbose description of the goal of the aggr=
egate report, as well as the contents?

"... Each report MUST contain data for only one 5322 domain.  The values re=
ported MUST be as evaluated from the original message, not from the local p=
olicy overrides ..." and so on?


> The consistency checks above can be useful for building verification tool=
s.
>
> Let me take this occasion to recall that there are XML syntax check tools=
 that
> can be used to automatically verify the syntax based on the schema.  We
> should write a more compliant XML in order to use them.

I've written an RNC (Relax NG Compact) previously.  As we get closer to fin=
alizing any format changes, we can create that, and then use jing/pyjing to=
 validate XML reports.  You'd want to use this to enforce report contents a=
s specified above?  Not that I'm opposed, though, it can't enforce that the=
 sender is using the proper values for DKIM pass/fail, only that the value =
is one of "pass"/"fail" (at least for RNC).  I don't believe there's a way =
to create interrelated dependencies where we could say that "DMARC can't po=
ssibly pass if both SPF and DKIM fail, and the report should be bogus if th=
at's the case".

>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dmarc
> __;!!CQl3mcHX2A!VCWZO-
> 6THaYEt8r1yDE9TgQzeJyuFmGpwSepa3SWwao3ViUQfPaxJ5FrbnTPKvtKzeGr
> $


From nobody Mon Jan  4 09:46:28 2021
Return-Path: <johnl@iecc.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 F36A93A0EBE for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 09:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.048
X-Spam-Level: 
X-Spam-Status: No, score=0.048 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=NQRvrFUw; dkim=pass (2048-bit key) header.d=taugh.com header.b=oyYPbRie
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 mmP5qFL6Q271 for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 09:46:25 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 2628E3A0EBC for <dmarc@ietf.org>; Mon,  4 Jan 2021 09:46:24 -0800 (PST)
Received: (qmail 63079 invoked from network); 4 Jan 2021 17:46:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=f665.5ff35470.k2101; bh=d+HVFRiZ+W6v4RLUkSwNkE2+BRpWQyL3wkyghh+Nu/E=; b=NQRvrFUwDkZn0vOkks7v/TNUmzhF8TrWUvgqH9P6pyypObxUEOUugEJ810K1ZFok6Gg1QKYJoUD3o+YeR+uN/NzU61qmvsguRHoCZtGpYa+o5twKp07v1Q0n0ozfhCPcEEjtq/XW/k4mdMTmyz8lhOq40QCEIxpJzREEjnyIwF449XMuuPWevyNgKamC+aB9XWzpx+quvarr6XwZx0GapDxY3HTecSlrrNGJN4qkktaY9N6HIORJMHafINaZ7cgzXgco508o2GFOgR0De4Fy6LImk1iNAGQW/cxI+HaSFPXvTIFxfPtBLac5G6f5rwaiXpqkXbyk1TRQ5qo6O/pQOA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=f665.5ff35470.k2101; bh=d+HVFRiZ+W6v4RLUkSwNkE2+BRpWQyL3wkyghh+Nu/E=; b=oyYPbRieS3zusGRqJ66gb/gFt7ld4Y7bIhTEmTSzFj3hyYanLD6ajsyANFHb9oSSkDa8yseYKYFQ+QJrTEM9k8Eb2Hjw0/jZfcUPqU7MJJrG6eFBKxrd724C1SLnI4HXVNsq7Sx5vfgrxM1zaPVo7LXMGvjn7UDvuDYjJbMlV5UVFaIrJPZzgbdsPCwmqFQ+fVw3tbBFBNgkDd6e1otuSE6WRJFfbwL4ocbXq+X1UA40LbCqowqkkXjCMIfBho77+KlaQCyJwttUV8Qe85sF8PRHHi92vnwMtV97QVUBP+3B9aT77pB1dv0inxJubvYWBF9/C53U67fMJBnw6Q8p7w==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 04 Jan 2021 17:46:23 -0000
Received: by ary.qy (Postfix, from userid 501) id 2545154CFF9F; Mon,  4 Jan 2021 12:46:22 -0500 (EST)
Date: 4 Jan 2021 12:46:22 -0500
Message-Id: <20210104174623.2545154CFF9F@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: laura@wordtothewise.com
In-Reply-To: <123E18E2-71AB-4946-B886-A12A735AA1AC@wordtothewise.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DpcTy6Bg8LLOd3TxaYlsDa9v01Y>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 04 Jan 2021 17:46:27 -0000

In article <123E18E2-71AB-4946-B886-A12A735AA1AC@wordtothewise.com> you write:
>There is absolutely nothing stopping a phisher from taking advantage of this. In fact, phishers currently do send DMARC verified email where the
>domain in the 5322.from is unrelated to the links in the message or to the domain being phished. 
>
>This seems to me to be a step along the path of making DMARC irrelevant by teaching recipients that mail with a 5322.from address they don’t
>recognize is legitimate email. 

We went through this same argument with DKIM 15 years ago, explaining
over and over to people who imagined that DKIM was a magic whitelist
bullet that a DKIM signature by itself tells you nothing. It's only
useful if you know something, good or bad, about the domain.

Similarly, DMARC alignment tells you nothing unless you also have a
reputation for the domain. I have trouble imagining why anyone would
think it's a good idea to get alignment by using third party domains
that recipients don't know.

R's,
John


From nobody Mon Jan  4 09:49:57 2021
Return-Path: <dcrocker@gmail.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 DBA0B3A0EC9 for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 09:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.459
X-Spam-Level: 
X-Spam-Status: No, score=-0.459 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 znoW_sxa7ON5 for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 09:49:54 -0800 (PST)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5B193A0EC8 for <dmarc@ietf.org>; Mon,  4 Jan 2021 09:49:54 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id v3so14906013plz.13 for <dmarc@ietf.org>; Mon, 04 Jan 2021 09:49:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=ZU72kzNc8oleZ99xdX/IWdskPuolZTck/4LiI8bNhIc=; b=irT7kP/T3BjaEx1uvxFafZzZvuV6NpuHHHprjLOfojzELHx/NCiOAkyuUjhZgrWyi9 hZrNMZ1JQdd3n52boTb+K4iBFG/eAO4CjM+euB5OJE8dwslMQTjJwUOsmtEVzkHRlfAs UIxoU/sjtwL/A4OH0v3mq3aiuPB9gSLGdXOYS0pieorm04Zse4xwqm8do91/lmElRS4y GBqmPT/9FbwXxXC9fJqJxqsSMgct9n/YkPie6MEUtf7WpovYvyPaprN8sOQDXPylROtF rcAlDKYL5vFZdLHXjZd1SVdx/Dr1dZ75Aq+Wz0ensG9avBO7qW8zmtALS0/kutDFuLo+ kgcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ZU72kzNc8oleZ99xdX/IWdskPuolZTck/4LiI8bNhIc=; b=pM0ueTTnVaXpXZ6lz0sANkr8MX5vggKvnVBNdXiShNH+XBsjG7UYHcrxqTG91wiIcr Dh5OTqpyhLmrudosgwYgDlD5Gy7U2uPK7OM0yp/X+QkL/rrB2Nyoo1+lKvwdwfBp3g7q Pksb8Oxb5bhGHHm4vNXDB/gczRTnKhyPzS0hSeUqzImAM4XBaoOP9nSwYjDoyJIlhwpe 6mw3qDxYIhu2cVFishQht0WTkLzhG1mFc0naAlq/8nckleextNyeftBLz0w2wOZV/bdp HGNzIV+6M0W/w8DUV51iJN5golSVknUQshAzQoVw6TI1Vw02+RwM6lvdqZHB8otWow9D Ho5g==
X-Gm-Message-State: AOAM531OcatJLaZdkMU4eKAc0ZOMQ1nQk2nkNLAiymmfvcadwAc+qodK eSFXV3LgWfiVWWusSIUV1VtKfdFbsWE=
X-Google-Smtp-Source: ABdhPJxeY9hrRWrCRfYLi5pbP8TZZmaovzi9NOnFjmCju7AQlxEfUpNdhryZucIn99QIX9ISY8cM/A==
X-Received: by 2002:a17:90a:f3c5:: with SMTP id ha5mr12400pjb.61.1609782594094;  Mon, 04 Jan 2021 09:49:54 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id fs12sm12085pjb.49.2021.01.04.09.49.53 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Jan 2021 09:49:53 -0800 (PST)
To: dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <21e3e22a-907a-8b86-2fea-e616d6b01a8c@gmail.com>
Date: Mon, 4 Jan 2021 09:49:51 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210104174623.2545154CFF9F@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/GK0_0RG6IhKs1KFsItsuONihH08>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 04 Jan 2021 17:49:56 -0000

> Similarly, DMARC alignment tells you nothing unless you also have a
> reputation for the domain.


Authentication creates a noise-free basis for developing an 
indentifier's reputation.

Any activity involving an authenticated identifier is, in fact, the 
responsibility of the agency responsible for that identifier.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Mon Jan  4 09:58:59 2021
Return-Path: <mike@fresheez.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 048613A0ED1 for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 09:58:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.113
X-Spam-Level: 
X-Spam-Status: No, score=-0.113 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 e0KcNcc7hpkr for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 09:58:56 -0800 (PST)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DECAE3A0EDF for <dmarc@ietf.org>; Mon,  4 Jan 2021 09:58:56 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id b5so57337pjl.0 for <dmarc@ietf.org>; Mon, 04 Jan 2021 09:58:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=MzokzmIFgM0A3kRYNd+v4rjMKnXk4yLSGztbvNxof9o=; b=LmBwaiSiknM7necNEIFmiAKKGV01Jf7brZwGC6MaZhwV+48XZ99JABqJvV9tMh9TU5 tLLxAC8hWCAcsp4dco6VlA9RYAi/ggInh35HRwMMW4yy0NWs19UKYuawzGRll3X72PcL jIkAH+PcErnthJQnk2fXZL0TyA4bx2JBcTZurWnPBYD9T4fEgegqD0H0nfiPwlx6eNVZ bkskdRmDTsZVybD6zTRMjx9DeJqjzTkG0zhNJrkr4L86+FjCzq9Qe8rzVlXhJc7BbrST Yt41l+OzGZmqpSaAqBMRYyz/AuHM2zrdszEK76y3U5v26kVDQSntNSdM7gZUUIJzIrfL 4TZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=MzokzmIFgM0A3kRYNd+v4rjMKnXk4yLSGztbvNxof9o=; b=Mym9sTpTG73HSj/e96PnU9zcL9M/GdsS0T60rlc5Jqe1hCKOLtI5syblLbtI5dlCJD rk4/L+Gb2ePsZuraEXYuFQqJh2PVXUakDiuDIjmcqmepJXert0Ru5+kgqc+gPMQ0bL0R M81zWX8Se7LPTl4gl8aSyvE6eOv3EqS+Fi9eMnXhPgEmrWYvErWdId/T40x8M/m2CY4J nl0amWwd3+ODAT9eN2KlncuHWt7mxQDXyZPkuFybuKbjbQ8dUeW3PTFXEuhO9ELaSRSS AEKDaP5R4bANmJjFJbOotvuYZWoF5aiKYN0TvPpTgs16egogh4ms6GmfNnGb0ExbZJP9 7ZNQ==
X-Gm-Message-State: AOAM530xC0WMfrrgoWDxEtVZwJg13u/xuoupuAqPzKIGRaNnijilpYah Y7HgiprtTQhLHPYewgZb7beyZoUk+E/gjQ==
X-Google-Smtp-Source: ABdhPJxYlo8jylIDE9iKl1QarTa8i1anOh1/RqlVi30n78qDSkF+f2Tab42cMsUoMniwd/vkRDX4UA==
X-Received: by 2002:a17:90a:9d88:: with SMTP id k8mr32470pjp.141.1609783135835;  Mon, 04 Jan 2021 09:58:55 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id p4sm31153pjl.30.2021.01.04.09.58.54 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Jan 2021 09:58:55 -0800 (PST)
To: dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <f7d2d6da-d74e-7def-6a65-a18f3cb3171d@mtcc.com>
Date: Mon, 4 Jan 2021 09:58:53 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210104174623.2545154CFF9F@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/auakK8PF8PJ3Uxa4Sqvc_9ynd_I>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 04 Jan 2021 17:58:58 -0000

On 1/4/21 9:46 AM, John Levine wrote:
>
> Similarly, DMARC alignment tells you nothing unless you also have a
> reputation for the domain. I have trouble imagining why anyone would
> think it's a good idea to get alignment by using third party domains
> that recipients don't know.
>
You don't need to know anything about the originating domain if they 
have a p=reject policy to do as they suggest. For many domains and 
especially commercial domains that is probably exactly the right thing 
to do.

Mike


From nobody Mon Jan  4 11:24:50 2021
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 C00EF3A0FEA for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 11:24:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.482
X-Spam-Level: 
X-Spam-Status: No, score=-0.482 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 XeE9RnTsa2sm for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 11:24:47 -0800 (PST)
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 3AD783A0FE7 for <dmarc@ietf.org>; Mon,  4 Jan 2021 11:24:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609788285; bh=2iNXubpzKqzG69JUAlo/UFNfSsvtJEuyiqxwhFGL+z0=; l=3123; h=To:References:From:Date:In-Reply-To; b=DS4hX8OIKoRtB0YdDnMplNqfwKJsqzeunwzzh/yNS6ryN+gmFeJgGMODjGmLdcMhS mIMWy5zeIXWwRhSzlN2PGUK43MFQr1h+PCDiqr3vNAIJUwicksOqU2ulcF6Ass5+Tm DyvCr5xFJG+0uqWa9sNW5cc6ZBdFj/JPfIclU3p4e6xrlgQJndFxMgEArPBIH
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC026.000000005FF36B7D.00001D48; Mon, 04 Jan 2021 20:24:45 +0100
To: dmarc@ietf.org
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com> <CAH48ZfzDkz4iS2k-+8_-zW-y4m+c1dhRMvPQZmpbLLG2KY0eGA@mail.gmail.com> <64c4ebd3-4e06-e12e-d072-7ae2562cf4e1@tana.it> <CAH48ZfzVkO_oxY1SjeWTqH9oUxHJaAsU2XKBZx-CQ9U0Ba8N0w@mail.gmail.com> <CAH48Zfwkxbi7pmmY15DKSRyCgc82jEUJ8hHRtvAQ9J3yJHy6_A@mail.gmail.com> <c3aef9ac-c7f9-e129-b71f-33f611237f9a@tana.it> <123E18E2-71AB-4946-B886-A12A735AA1AC@wordtothewise.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <c3b74c98-8a69-c3d6-a609-f5515ac419ae@tana.it>
Date: Mon, 4 Jan 2021 20:24:43 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <123E18E2-71AB-4946-B886-A12A735AA1AC@wordtothewise.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/NQIknTTIOf5bd9D7Issu7EHfdo8>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 04 Jan 2021 19:24:49 -0000

On Mon 04/Jan/2021 13:22:20 +0100 Laura Atkins wrote:
>> On 4 Jan 2021, at 11:50, Alessandro Vesely <vesely@tana.it> wrote:
>> 
>>> Lets define "legitimate mail" as used in my proposed text to mean "delivery
>>> is desired by the intended recipient and the message contains nothing that
>>> threatens the interest of the user, the interest of the user's network, or
>>> the policies of the user's organization."   Perhaps this is too
>>> restrictive, because it  excludes advertising which is harmless in its
>>> intent but unwanted by the recipient.
>> 
>> Having advertisements come /From: advertiser/ is a goal.
> 
> Yes.
> 
> [snip]
> 
>>> Email evaluation products need to handle all possible scenarios.  This
>>> includes
>>> - forwarded and not forwarded
>>> - with and without SMTP rewrite
>>> - with and without modification.
>>> - with and without From rewrite
>>> - with and without ARC sets
>>> - whether the email header chain is accurately documented or fraudulently fabricated.
>> 
>> Girl Scout troops will inevitably fall in the not forwarded category.  ESP messages, instead, should come /From: ESP/.
> 
> This incompatible with the above goal of having advertisements come from the advertiser.


That depends on how you define "advertiser".  If you entrust your communication to an external agent, the advertiser becomes that.  Maybe, an agent they could differentiate by using subdomains, similar to the "onmicrosoft.com" suffix.


> I find it highly problematic that we’re teaching recipients that they get official mail from companies that come from an address that is not connected to the company at all. It further devalues the 5322.from and means that recipients cannot trust the domains that the see there. This is even more true when the domain is one they’ve never heard of and passes all of the checks and comes in with a ‘verified by DMARC.’


Agreed.

A recipient should somehow trust the ESP, or else discard their messages.

Then, there are several ways that an ESP (or a MLM) can try and convey some kind of transparency of intents.  One can use subdomains and display names.  IMHO, we should add some guidelines about this in the spec.

Of course, publishing the ESP's selectors would complete the entrust better.  The scalability looks similar to that of subscribed feedback loops.

(Managing communication internally is even better.)


> There is absolutely nothing stopping a phisher from taking advantage of this. In fact, phishers currently do send DMARC verified email where the domain in the 5322.from is unrelated to the links in the message or to the domain being phished.


We cannot prevent phishers from doing so anyway.  Yet, if we insist on using DMARC nevertheless, authentication will create "a noise-free basis for developing an indentifier's reputation", in Dave's words.


> This seems to me to be a step along the path of making DMARC irrelevant by teaching recipients that mail with a 5322.from address they don’t recognize is legitimate email.


It is as legitimate as the identifier's reputation.


Best
Ale
-- 

















From nobody Mon Jan  4 12:18:06 2021
Return-Path: <dougfoster.emailstandards@gmail.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 3FDEA3A102E for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 12:18:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Sd6luMIH-1gb for <dmarc@ietfa.amsl.com>; Mon,  4 Jan 2021 12:18:01 -0800 (PST)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A84593A102C for <dmarc@ietf.org>; Mon,  4 Jan 2021 12:18:01 -0800 (PST)
Received: by mail-ua1-x931.google.com with SMTP id s23so9506400uaq.10 for <dmarc@ietf.org>; Mon, 04 Jan 2021 12:18:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iZuYl7AdU9sZiJ5IKcKcEDPkbuq4IOcxiFXrz4GiNCw=; b=n6/RCjFoPAnhccHSgKbNBLpyznw3uDZeG/SANrp+ajaRHiUsHsskKV/RHW7gLxKAYn wh/FioydNbRjIOyYXVlD82hakW/At2tA2kCoLSB4np3++OZxBq9UCJaAV2yTq4+uUtJp 8Vh7kTToVVneaQEyiunr462G4fiIxgs8zPneXVJmdcf/EEBj5VcwwJljeOm2yTDePcTc K6ofVZErfXHVjRtXK2rVGZi4a+6XYhcnKS9qfmDZmvGF6uCuuDT9do3acPHFQJD7vcqQ 54h+yTyAuCDrkayLA3089gicAr4YY+Ol40NddLEYuQkdvsz82rajgTnmjo/yfCPcspeS Jgsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iZuYl7AdU9sZiJ5IKcKcEDPkbuq4IOcxiFXrz4GiNCw=; b=Bpe6L94cI3B/F1trfVcV0vxNiXGHKawTehkzahyZdJl4BXb/xTirXkwyN7K6lhtsNB AHSvQEpEgB7zR2ipFYrbI4h1DbjkpbSpqKE9l5h4ZoEctGWjFh5wbGYFEQfi5RvAwlQi 9FaPf3xqrIEm1B0KhqrLHpWjFfSRljEkpfNvxnRKUoOT94id3RaCyE+WgJY7IwKTIQq+ qKBlZZlpNWqKLUk6ZU/olOoeeKhT5GfXe0rdqnYRQctdslgzhoPnHIsXh1UGCawEptvD HBpZRR3WBSNeHxF537tgEUDHg3sqZueb2ZFW7udopXAcRyzxk6QbIrv1R2fJMaXQTTRD mHHw==
X-Gm-Message-State: AOAM530RKKWgPmSr9iXQLTBQzmOVyb4+iqAb8ADy6osX22iAx5AVodEc o/T2TsbRjDx1pxhj9rA/V+u8uEaea04A8IH72SIYsCXM
X-Google-Smtp-Source: ABdhPJxV2JbpEEESYhXthWwl9/cQ9LMzdd00RR0LK0R4v4r7RiIla7Wu1zSvRVSAqSE9jwBs/zP/f2Yg90z/XjqZ9tc=
X-Received: by 2002:a9f:2e01:: with SMTP id t1mr46609959uaj.95.1609791480759;  Mon, 04 Jan 2021 12:18:00 -0800 (PST)
MIME-Version: 1.0
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com> <CAH48ZfzDkz4iS2k-+8_-zW-y4m+c1dhRMvPQZmpbLLG2KY0eGA@mail.gmail.com> <64c4ebd3-4e06-e12e-d072-7ae2562cf4e1@tana.it> <CAH48ZfzVkO_oxY1SjeWTqH9oUxHJaAsU2XKBZx-CQ9U0Ba8N0w@mail.gmail.com> <CAH48Zfwkxbi7pmmY15DKSRyCgc82jEUJ8hHRtvAQ9J3yJHy6_A@mail.gmail.com> <c3aef9ac-c7f9-e129-b71f-33f611237f9a@tana.it> <123E18E2-71AB-4946-B886-A12A735AA1AC@wordtothewise.com> <c3b74c98-8a69-c3d6-a609-f5515ac419ae@tana.it>
In-Reply-To: <c3b74c98-8a69-c3d6-a609-f5515ac419ae@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 4 Jan 2021 15:17:46 -0500
Message-ID: <CAH48ZfwXzEfpftiB1=Ctk4snzkuXVtxpOQPh28k0DgzVERSgXQ@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005f8a7b05b818c955"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/IN31RwHHivkbhCeYyyscNOCe7lQ>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 04 Jan 2021 20:18:04 -0000

--0000000000005f8a7b05b818c955
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I have not seen an identity problem with ESPs, bevause messages are
received directly.  They consistently use their own domain for MailFrom to
ensure SPF pass, and the client domain for From.    Domains that use DMARC
enforcement have signatures.

Additionally, the From domain correctly presents the client identity, so I
do not fear spoofing, even from ESPs that happily provide their services to
criminal domains.  Those that serve criminals have all of their
unclassified clients sent to administrative quarantine.  A small portion
that is found to be wanted traffic will be released and exempted from
quarantine on future messages.

If the same messages were received indirectly, it would be a problem
because the SMTP rewrite hides the ESP identity, so the quarantine would
not happen.  Hence, I must start scanning the entire Received chain and
related headers.

Since everyone deals with the same ESPs, I think everyone needs to do full
scans also.

DF


On Mon, Jan 4, 2021, 2:24 PM Alessandro Vesely <vesely@tana.it> wrote:

> On Mon 04/Jan/2021 13:22:20 +0100 Laura Atkins wrote:
> >> On 4 Jan 2021, at 11:50, Alessandro Vesely <vesely@tana.it> wrote:
> >>
> >>> Lets define "legitimate mail" as used in my proposed text to mean
> "delivery
> >>> is desired by the intended recipient and the message contains nothing
> that
> >>> threatens the interest of the user, the interest of the user's
> network, or
> >>> the policies of the user's organization."   Perhaps this is too
> >>> restrictive, because it  excludes advertising which is harmless in it=
s
> >>> intent but unwanted by the recipient.
> >>
> >> Having advertisements come /From: advertiser/ is a goal.
> >
> > Yes.
> >
> > [snip]
> >
> >>> Email evaluation products need to handle all possible scenarios.  Thi=
s
> >>> includes
> >>> - forwarded and not forwarded
> >>> - with and without SMTP rewrite
> >>> - with and without modification.
> >>> - with and without From rewrite
> >>> - with and without ARC sets
> >>> - whether the email header chain is accurately documented or
> fraudulently fabricated.
> >>
> >> Girl Scout troops will inevitably fall in the not forwarded category.
> ESP messages, instead, should come /From: ESP/.
> >
> > This incompatible with the above goal of having advertisements come fro=
m
> the advertiser.
>
>
> That depends on how you define "advertiser".  If you entrust your
> communication to an external agent, the advertiser becomes that.  Maybe, =
an
> agent they could differentiate by using subdomains, similar to the "
> onmicrosoft.com" suffix.
>
>
> > I find it highly problematic that we=E2=80=99re teaching recipients tha=
t they
> get official mail from companies that come from an address that is not
> connected to the company at all. It further devalues the 5322.from and
> means that recipients cannot trust the domains that the see there. This i=
s
> even more true when the domain is one they=E2=80=99ve never heard of and =
passes all
> of the checks and comes in with a =E2=80=98verified by DMARC.=E2=80=99
>
>
> Agreed.
>
> A recipient should somehow trust the ESP, or else discard their messages.
>
> Then, there are several ways that an ESP (or a MLM) can try and convey
> some kind of transparency of intents.  One can use subdomains and display
> names.  IMHO, we should add some guidelines about this in the spec.
>
> Of course, publishing the ESP's selectors would complete the entrust
> better.  The scalability looks similar to that of subscribed feedback loo=
ps.
>
> (Managing communication internally is even better.)
>
>
> > There is absolutely nothing stopping a phisher from taking advantage of
> this. In fact, phishers currently do send DMARC verified email where the
> domain in the 5322.from is unrelated to the links in the message or to th=
e
> domain being phished.
>
>
> We cannot prevent phishers from doing so anyway.  Yet, if we insist on
> using DMARC nevertheless, authentication will create "a noise-free basis
> for developing an indentifier's reputation", in Dave's words.
>
>
> > This seems to me to be a step along the path of making DMARC irrelevant
> by teaching recipients that mail with a 5322.from address they don=E2=80=
=99t
> recognize is legitimate email.
>
>
> It is as legitimate as the identifier's reputation.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--0000000000005f8a7b05b818c955
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I have not seen an identity problem with ESPs, bevause me=
ssages are received directly.=C2=A0 They consistently use their own domain =
for MailFrom to ensure SPF pass, and the client domain for From.=C2=A0 =C2=
=A0 Domains that use DMARC enforcement have signatures.<div dir=3D"auto"><b=
r></div><div dir=3D"auto">Additionally, the From domain correctly presents =
the client identity, so I do not fear spoofing, even from ESPs that happily=
 provide their services to criminal domains.=C2=A0 Those that serve crimina=
ls have all of their unclassified clients sent to administrative quarantine=
.=C2=A0 A small portion that is found to be wanted traffic will be released=
 and exempted from quarantine on future messages.</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">If the same messages were received indirectly, it=
 would be a problem because the SMTP rewrite hides the ESP identity, so the=
 quarantine would not happen.=C2=A0 Hence, I must start scanning the entire=
 Received chain and related headers.</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">Since everyone deals with the same ESPs, I think everyone need=
s to do full scans also.</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>DF</div><div dir=3D"auto"><br></div></div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 4, 2021, 2:24 PM Alessandr=
o Vesely &lt;<a href=3D"mailto:vesely@tana.it" rel=3D"noreferrer noreferrer=
" target=3D"_blank">vesely@tana.it</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">On Mon 04/Jan/2021 13:22:20 +0100 Laura Atkins wrote:<br>
&gt;&gt; On 4 Jan 2021, at 11:50, Alessandro Vesely &lt;<a href=3D"mailto:v=
esely@tana.it" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">v=
esely@tana.it</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt;&gt; Lets define &quot;legitimate mail&quot; as used in my proposed=
 text to mean &quot;delivery<br>
&gt;&gt;&gt; is desired by the intended recipient and the message contains =
nothing that<br>
&gt;&gt;&gt; threatens the interest of the user, the interest of the user&#=
39;s network, or<br>
&gt;&gt;&gt; the policies of the user&#39;s organization.&quot;=C2=A0 =C2=
=A0Perhaps this is too<br>
&gt;&gt;&gt; restrictive, because it=C2=A0 excludes advertising which is ha=
rmless in its<br>
&gt;&gt;&gt; intent but unwanted by the recipient.<br>
&gt;&gt; <br>
&gt;&gt; Having advertisements come /From: advertiser/ is a goal.<br>
&gt; <br>
&gt; Yes.<br>
&gt; <br>
&gt; [snip]<br>
&gt; <br>
&gt;&gt;&gt; Email evaluation products need to handle all possible scenario=
s.=C2=A0 This<br>
&gt;&gt;&gt; includes<br>
&gt;&gt;&gt; - forwarded and not forwarded<br>
&gt;&gt;&gt; - with and without SMTP rewrite<br>
&gt;&gt;&gt; - with and without modification.<br>
&gt;&gt;&gt; - with and without From rewrite<br>
&gt;&gt;&gt; - with and without ARC sets<br>
&gt;&gt;&gt; - whether the email header chain is accurately documented or f=
raudulently fabricated.<br>
&gt;&gt; <br>
&gt;&gt; Girl Scout troops will inevitably fall in the not forwarded catego=
ry.=C2=A0 ESP messages, instead, should come /From: ESP/.<br>
&gt; <br>
&gt; This incompatible with the above goal of having advertisements come fr=
om the advertiser.<br>
<br>
<br>
That depends on how you define &quot;advertiser&quot;.=C2=A0 If you entrust=
 your communication to an external agent, the advertiser becomes that.=C2=
=A0 Maybe, an agent they could differentiate by using subdomains, similar t=
o the &quot;<a href=3D"http://onmicrosoft.com" rel=3D"noreferrer noreferrer=
 noreferrer noreferrer" target=3D"_blank">onmicrosoft.com</a>&quot; suffix.=
<br>
<br>
<br>
&gt; I find it highly problematic that we=E2=80=99re teaching recipients th=
at they get official mail from companies that come from an address that is =
not connected to the company at all. It further devalues the 5322.from and =
means that recipients cannot trust the domains that the see there. This is =
even more true when the domain is one they=E2=80=99ve never heard of and pa=
sses all of the checks and comes in with a =E2=80=98verified by DMARC.=E2=
=80=99<br>
<br>
<br>
Agreed.<br>
<br>
A recipient should somehow trust the ESP, or else discard their messages.<b=
r>
<br>
Then, there are several ways that an ESP (or a MLM) can try and convey some=
 kind of transparency of intents.=C2=A0 One can use subdomains and display =
names.=C2=A0 IMHO, we should add some guidelines about this in the spec.<br=
>
<br>
Of course, publishing the ESP&#39;s selectors would complete the entrust be=
tter.=C2=A0 The scalability looks similar to that of subscribed feedback lo=
ops.<br>
<br>
(Managing communication internally is even better.)<br>
<br>
<br>
&gt; There is absolutely nothing stopping a phisher from taking advantage o=
f this. In fact, phishers currently do send DMARC verified email where the =
domain in the 5322.from is unrelated to the links in the message or to the =
domain being phished.<br>
<br>
<br>
We cannot prevent phishers from doing so anyway.=C2=A0 Yet, if we insist on=
 using DMARC nevertheless, authentication will create &quot;a noise-free ba=
sis for developing an indentifier&#39;s reputation&quot;, in Dave&#39;s wor=
ds.<br>
<br>
<br>
&gt; This seems to me to be a step along the path of making DMARC irrelevan=
t by teaching recipients that mail with a 5322.from address they don=E2=80=
=99t recognize is legitimate email.<br>
<br>
<br>
It is as legitimate as the identifier&#39;s reputation.<br>
<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer noreferrer noreferrer" =
target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mai=
lman/listinfo/dmarc</a><br>
</blockquote></div>

--0000000000005f8a7b05b818c955--


From nobody Tue Jan  5 03:20:47 2021
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 298173A040B for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 03:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 PfjinwcxsU4f for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 03:20:42 -0800 (PST)
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 A34173A03F8 for <dmarc@ietf.org>; Tue,  5 Jan 2021 03:20:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609845639; bh=hK5EEX7hDdTwWN54BzdfVj99mHhrvyjc0Y875rur82s=; l=4955; h=To:References:From:Date:In-Reply-To; b=BS1p2cc73xa4+SPtqyu/r0f+bmqydywTwsbcQXpPFbWvek9jFx1grOxj/Uh4JyARm jQsdJ0nGECpyOBGjjARVZmPx/U1vok1f40yPvCRyD4+TwNYkgA1nEmDNKL86OvBbQx sWwjeiXJd8E9uZJI1HGLrRbgP7sv+JtAFm3izxQJUuePJLu8z4DZ3auZ0NsLh
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.000000005FF44B87.0000277F; Tue, 05 Jan 2021 12:20:38 +0100
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>, "dmarc@ietf.org" <dmarc@ietf.org>
References: <MN2PR11MB435151665586B5A40D101103F7D70@MN2PR11MB4351.namprd11.prod.outlook.com> <59d0e09e-9296-c16e-94b1-8f344faf88d2@tana.it> <MN2PR11MB4351CB31FD6C315422559BDCF7D20@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <9c362df2-8338-75f6-d8c2-256124842cda@tana.it>
Date: Tue, 5 Jan 2021 12:20:37 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4351CB31FD6C315422559BDCF7D20@MN2PR11MB4351.namprd11.prod.outlook.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/-omxO8A8CuDeDBpqFuV4DKgZdgU>
Subject: Re: [dmarc-ietf] Clarification about data integrity within Aggregate Reports (Ticket #40)
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, 05 Jan 2021 11:20:46 -0000

On Mon 04/Jan/2021 16:53:20 +0100 Brotman, Alex wrote:
> -----Original Message----- From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Alessandro Vesely
>> On Wed 30/Dec/2020 23:18:35 +0100 Brotman, Alex wrote:
>>>
>>> There's an open ticket (https://trac.ietf.org/trac/dmarc/ticket/40) noting
>>> that we should clarify what constitutes valid data in a report. For 
>>> example, the report cannot state that DMARC-DKIM was a "pass" when DKIM
>>> itself was a failure. >>>
>>> It seems like the gist is that within the report it should never happen that
>>> DKIM or SPF are noted to have passed in the context of DMARC if they have
>>> not passed on their own.  [...]
>>>
>>> Does that seem properly summarized?
>>
>> If the aggregate report content, Section 2.2, was well explained, the above
>> text would be redundant.  The point is that Section 2.2 looks like a high level
>> list of features.  It is completely useless for implementing a report producer,
>> let alone a consumer.  We have to rewrite that section, possibly trying to re-
>> use the same wording and the same order of appearance of concepts, so as
>> to minimize readers' confusion, but strictly matching the content of Appendix
>> A (was Appendix C).
> 
> I don't think I disagree here, but I want to be clear on what you're requesting.  You'd like to see a more verbose description of the goal of the aggregate report, as well as the contents?
> 
> "... Each report MUST contain data for only one 5322 domain.  The values reported MUST be as evaluated from the original message, not from the local policy overrides ..." and so on?


Yes, more or less.

Section 2.2 is good until "The format for these reports is defined in Appendix 
C."  (Ok, that should be Appendix A)  Following that, it should describe what 
the content actually must be.  I'd start, for example, like so:

     Aggregate reports (feedback) consist of two parts, a header and a set of
     records.  The header holds the report metadata (report_metadata) as well as
     the policy discovered for the given domain, subject of the report
     (policy_published).  Each report MUST contain data for only one domain.
     That policy MUST correspond to the DMARC record that the subject domain
     published during the reporting period.  If the subject domain modified its
     DMARC record during the period, a report generator MAY create multiple
     reports for the same domain, each for the periods during which the record
     didn't vary.  Otherwise, a generator SHOULD report the last policy it
     found.

     The set of records (record)...

I think we can skip elements whose content is obvious, but say something about 
various cases.  I can write more text after we find the right tone.  Is the 
above too lengthy?


>> The consistency checks above can be useful for building verification tools.
>>
>> Let me take this occasion to recall that there are XML syntax check tools that
>> can be used to automatically verify the syntax based on the schema.  We
>> should write a more compliant XML in order to use them.
> 
> I've written an RNC (Relax NG Compact) previously.  As we get closer to finalizing any format changes, we can create that, and then use jing/pyjing to validate XML reports.


jing is a nice utility.  I had used svalidate and xmlstarlet, which provide 
similar validation.


>  You'd want to use this to enforce report contents as specified above?


Absolutely.  Let me note that, to pass tests using the utilities mentioned 
above, reports should start something like so:

     <?xml version="1.0" encoding="UTF-8"?>
     <dmarc:feedback xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
         xmlns:dmarc="http://dmarc.org/dmarc-xml/0.1"
         xs:schemaLocation="http://dmarc.org/dmarc-xml/0.1 rua.xsd">
         <report_metadata>
         ...

(replace schemaLocation as appropriate)

The above form is currently not used.  Note that the "version" element becomes 
irrelevant when a schema is given.

It is easy, as a developer upgrades her report producer, to add the correct 
boilerplate.  To wit, it's more difficult to add selectors or to switch from 
.zip to .gz.


>  Not that I'm opposed, though, it can't enforce that the sender is using the proper values for DKIM pass/fail, only that the value is one of "pass"/"fail" (at least for RNC).  I don't believe there's a way to create interrelated dependencies where we could say that "DMARC can't possibly pass if both SPF and DKIM fail, and the report should be bogus if that's the case".


Right.  On the other hand, it makes little sense to check consistency if the 
syntax is bad.

We could create a web-based DMARC checking tool.  You get there and request a 
check, authenticating yourself and providing a few email addresses for the 
test.  The tool will then send you various messages from various IPs/ domains 
and then check the aggregate reports you produce.  That would include the 
consistency checks of ticket #40.


Best
Ale
-- 

























From nobody Tue Jan  5 04:25:44 2021
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 A78BD3A0A26 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 04:25:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 f8C6KyH51D2X for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 04:25:41 -0800 (PST)
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 52F5C3A0A1D for <dmarc@ietf.org>; Tue,  5 Jan 2021 04:25:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609849539; bh=l/QYdbLiP5BIjOtVHeXc53472D8gIS65xtrEwZwHsNM=; l=1211; h=To:References:From:Date:In-Reply-To; b=ABnObEATGl69oLNY/HFkvzRkUsPRsix9xOLmelFVLnOBgBiEZQzJFnjyTeRRKi/sO WrQalaMR5osZN4DSAHnYshuHmaE2P9H4IEwNrhuDrx9j4j0fROzGcb+eESZQRsOi9E fBVUFfLzYEb74ozXbPD8hjnfNzkFiGpw0egSaexP2C6aBCXQRRRO6LIHtFHjc
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC026.000000005FF45AC3.00002DAB; Tue, 05 Jan 2021 13:25:39 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org, todd.herr@valimail.com
References: <20201231192500.1B3483F0176B@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <be0601ec-7e50-f280-4cf4-66c3b4ac7fa5@tana.it>
Date: Tue, 5 Jan 2021 13:25:37 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20201231192500.1B3483F0176B@ary.qy>
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/EebqhnwmC0b7w14B210YpfPLiP8>
Subject: Re: [dmarc-ietf] Ticket #80 - DMARCbis Should Have Clear and Concise Definition of DMARC
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, 05 Jan 2021 12:25:43 -0000

On Thu 31/Dec/2020 20:24:59 +0100 John Levine wrote:
> In article <CAHej_8kkuQR3_LiV_O5Z-EPvVeZrdTPvCiK7rOmWKxQKsp=6pA@mail.gmail.com> you write:
>>
>>Dave Crocker submitted some suggestions on-list, and I noodled a bit with
>>the text myself, and submit the following for your collective consideration:
> 
> I have a few minor editorial tweaks to suggest but they can wait.  I think
> we should use this text.


+1, I see it's not yet on github.  Please go ahead, possibly posting a .txt as 
well, so we can run IETF's diff tool.


Among the minor tweaks I have:

1.  In the Abstract, the term email (or mail) appears late.  I'd suggest either 
"an email author's domain name" or "validation of the domain's email use".

2.  Shall we really stick to "RFC5322.From domain"?  Rfc5322bis will presumably 
get published at about the same time as this I-D, so that terminology is doomed 
to sound as antique as message/rcf822.  Possible alternatives:

2.1. Author's domain.
2.2. domain part of the From: header field address.
2.3. Main identifier (DMARC's main identifier, when used outside the I-D).

3.  In the 1st paragraph, "reports about use of the domain name", /email/ use.


Best
Ale
-- 

























From nobody Tue Jan  5 05:36:34 2021
Return-Path: <todd.herr@valimail.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 AFF983A0EB5 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 05:36:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 EUmpHf5Dfm4E for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 05:36:32 -0800 (PST)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF2443A0EB3 for <dmarc@ietf.org>; Tue,  5 Jan 2021 05:36:31 -0800 (PST)
Received: by mail-qk1-x733.google.com with SMTP id 19so26365797qkm.8 for <dmarc@ietf.org>; Tue, 05 Jan 2021 05:36:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=yWPwbzbfGAtUi4zIb/crRXHAeKnb8+pytKTcK/Og4vc=; b=O3Nh7bNfW0LsqJYTCT+fZNjzoKm11y9Bz9ugmmjHu0TBMU8CJftb54WCHy5bJhLI6C So53rgczF/qFeqL4FYgsnxvlh1shTnZBsYDsb5xN2Kazc1WDzL7h+Cm3nwFJMG3VZ9lR FqvQzE//vEO/LmXvkPk2TNPXjxC5Zt+yAEZH9LOaXIyrKiTPN2kPUR4jhCUn+0vEhIV7 4hyI+RWSuZWivU3DrbXjvNQIk0KghlDGya6UtYE0sece8pzTj77V+2QNZ6BAa17wxSgT LtsDB17Ha0+iUgmUpT3L1IJAiqfh4Cz9jIN82/yNiUkdLgMvE4FaLlgt4WJ2hcSnZufd gjjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=yWPwbzbfGAtUi4zIb/crRXHAeKnb8+pytKTcK/Og4vc=; b=mlhQ+ThaOQMK2OXZ5YkfzbXeNR0D/444yL215HQGIDl5jq+J9f7VuhMpvcRgcXCDE2 zp7/NTkvoKlYaEVkLkruoCxxkbr0Oqt8/AkPIzQSsTl2/0RXl22SCEJny6W1QIWEgRCa dAFiIayfEwDVn0l38yUVLoY0zSGjquwR6h1GcALbcRrtRP07xg+Eq6dixPxy3XlCwDGb 3f6fyiBl6EwQl90W0IIkqABQVGNxCJbor1A4bEaXDrTTNp5+aMfF6++KSTxbwQ1Tqq/0 skHRaFaW7NNR8UuIs1tZo/pVrnfhszgQrP7Qs5zQ8lMWekpi9aIkIwNfYvtBOGiL4nFh qJrA==
X-Gm-Message-State: AOAM533jeINBqRzhLO7BuxNwKpRD8g2dasTdgPuZFhb/dt0AGC3FoMrM DYQMzFLPx/UxbpP+5cMTQJJx1JTTfmIiHpaI92COjDLdq5TQ+w==
X-Google-Smtp-Source: ABdhPJzZLsYsnYHT6yOYMT4YdnmxlNHboYyFu1IpGbpuX+lr/fkB2M/JqKaiUlE87fT4B8m0MeHnBjrEkfDqq2mxy2c=
X-Received: by 2002:a37:a656:: with SMTP id p83mr76836450qke.208.1609853790751;  Tue, 05 Jan 2021 05:36:30 -0800 (PST)
MIME-Version: 1.0
References: <20201231192500.1B3483F0176B@ary.qy> <be0601ec-7e50-f280-4cf4-66c3b4ac7fa5@tana.it>
In-Reply-To: <be0601ec-7e50-f280-4cf4-66c3b4ac7fa5@tana.it>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 5 Jan 2021 08:36:15 -0500
Message-ID: <CAHej_8mNzuAys9V0BHCk9o=6rzK9vEpZ6Db3OE4zA+E=vXhrjw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000569f2105b8274bd1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ua9s09-I9sIHH-ZGgwRFLnogvrc>
Subject: Re: [dmarc-ietf] Ticket #80 - DMARCbis Should Have Clear and Concise Definition of DMARC
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, 05 Jan 2021 13:36:34 -0000

--000000000000569f2105b8274bd1
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 5, 2021 at 7:25 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Thu 31/Dec/2020 20:24:59 +0100 John Levine wrote:
> > In article <CAHej_8kkuQR3_LiV_O5Z-EPvVeZrdTPvCiK7rOmWKxQKsp=
> 6pA@mail.gmail.com> you write:
> >>
> >>Dave Crocker submitted some suggestions on-list, and I noodled a bit with
> >>the text myself, and submit the following for your collective
> consideration:
> >
> > I have a few minor editorial tweaks to suggest but they can wait.  I
> think
> > we should use this text.
>
>
> +1, I see it's not yet on github.  Please go ahead, possibly posting a
> .txt as
> well, so we can run IETF's diff tool.
>
>
>
Updated version, including .txt but without your suggested minor tweaks, is
posted here - https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis

Note that lack of inclusion of your minor tweaks obviously does not mean
that they've been rejected; I just wanted to complete the process of
checking in a new branch, doing a pull request, and merging the new branch
with main.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000569f2105b8274bd1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 5, 2021 at 7:25 AM Alessandro=
 Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote:=
<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">On Thu 31/Dec/2020 20:24:59 +0100 John Levine wrote:<br>
&gt; In article &lt;CAHej_8kkuQR3_LiV_O5Z-EPvVeZrdTPvCiK7rOmWKxQKsp=3D<a hr=
ef=3D"mailto:6pA@mail.gmail.com" target=3D"_blank">6pA@mail.gmail.com</a>&g=
t; you write:<br>
&gt;&gt;<br>
&gt;&gt;Dave Crocker submitted some suggestions on-list, and I noodled a bi=
t with<br>
&gt;&gt;the text myself, and submit the following for your collective consi=
deration:<br>
&gt; <br>
&gt; I have a few minor editorial tweaks to suggest but they can wait.=C2=
=A0 I think<br>
&gt; we should use this text.<br>
<br>
<br>
+1, I see it&#39;s not yet on github.=C2=A0 Please go ahead, possibly posti=
ng a .txt as <br>
well, so we can run IETF&#39;s diff tool.<br>
<br>
<br></blockquote><div><br></div><div>Updated version, including .txt but wi=
thout your suggested minor tweaks, is posted here -=C2=A0<a href=3D"https:/=
/github.com/ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis">https://github.com/iet=
f-wg-dmarc/draft-ietf-dmarc-dmarcbis</a></div><div><br></div><div>Note that=
 lack of inclusion of your minor tweaks obviously does not mean that they&#=
39;ve been rejected; I just wanted to complete the process of checking in a=
 new branch, doing a pull request, and merging the new branch with main.</d=
iv><div><br></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><=
span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom=
:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</=
b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-s=
ize:small;font-family:Arial"> | Sr. Technical Program Manager</span></div><=
span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;=
font-family:Arial"><div style=3D"text-align:left"><span style=3D"vertical-a=
lign:baseline"><b>e:</b></span><span style=3D"vertical-align:baseline"> <a =
href=3D"mailto:todd.herr@valimail.com" target=3D"_blank">todd.herr@valimail=
.com</a></span></div></span><span><div><span><b>p:</b></span><span> 703.220=
.4153 </span><span></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34=
,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-c=
olor:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><s=
pan style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-c=
olor:transparent;vertical-align:baseline;white-space:pre-wrap"><img src=3D"=
https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0=
Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2=
x5EcZV3rjz19-Dx9rESL" style=3D"border: none; height: 40px; width: 177px;"><=
/span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D=
"background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-b=
ottom:0pt"><font color=3D"#666666" face=3D"Arial"><span style=3D"font-size:=
10.6667px;white-space:pre-wrap">This email and all data transmitted with it=
 contains confidential and/or proprietary information intended solely for t=
he use of individual(s) authorized to receive it. If you are not an intende=
d and authorized recipient you are hereby notified of any use, disclosure, =
copying or distribution of the information included in this transmission is=
 prohibited and may be unlawful. Please immediately notify the sender by re=
plying to this email and then delete it from your system.</span></font></p>=
</span></div></div>

--000000000000569f2105b8274bd1--


From nobody Tue Jan  5 10:01:11 2021
Return-Path: <fenton@bluepopcorn.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 583813A1092 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 10:01:10 -0800 (PST)
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_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 O_u7eZt6NR6K for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 10:01:08 -0800 (PST)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 D62FF3A1068 for <dmarc@ietf.org>; Tue,  5 Jan 2021 10:01:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=+XGTWqNA26JdDU9wW689oJQP0vYaQvxku9wNXsGZdas=; b=dmJQGoLNDvYtBupJOlw4cg+Qtg rR+d6z/MIu96kYoeXh7owo53v+dFi/Riyzhts21IKgS9k6Cr1Xx6090g6SNr5EVvSN4O4TzKBLQ1X Oq8HItgi2iW8TjYK4PaFdApgcjw02IEQ5R2LvBRTjXgPcU8zKEIvgBDjc1SzdcLjfb0Y=;
Received: from [2601:647:4400:1261:108d:ac48:81ff:6e96] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1kwqdn-0005Qg-P2; Tue, 05 Jan 2021 10:01:07 -0800
From: "Jim Fenton" <fenton@bluepopcorn.net>
To: "John Levine" <johnl@taugh.com>
Cc: dmarc@ietf.org
Date: Tue, 05 Jan 2021 10:01:07 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net>
In-Reply-To: <20210104174623.2545154CFF9F@ary.qy>
References: <20210104174623.2545154CFF9F@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/KGrOdH77zdcJGZBruoypjNxEsyE>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 18:01:10 -0000

On 4 Jan 2021, at 9:46, John Levine wrote:

> Similarly, DMARC alignment tells you nothing unless you also have a
> reputation for the domain. I have trouble imagining why anyone would
> think it's a good idea to get alignment by using third party domains
> that recipients don't know.

Because recipients often can’t see (or don’t pay attention to) the 
domain name and the reputation system you postulate doesn’t exist. 
OTOH, getting alignment avoids a restrictive policy that might be 
associated with the original domain.

-Jim


From nobody Tue Jan  5 10:18:02 2021
Return-Path: <johnl@taugh.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 EFF883A10C7 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 10:18:00 -0800 (PST)
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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=MQu9dVwK; dkim=pass (2048-bit key) header.d=taugh.com header.b=xkEpb1PV
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 RCAAsHEUsdGX for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 10:17:59 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 1F6B03A10D6 for <dmarc@ietf.org>; Tue,  5 Jan 2021 10:17:58 -0800 (PST)
Received: (qmail 81655 invoked from network); 5 Jan 2021 18:17:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=13ef5.5ff4ad54.k2101; i=johnl-iecc.com@submit.iecc.com; bh=K0/TGAXCFQ3eGp59Xn08ZKJUjRGny9xWksWK2zFaZzY=; b=MQu9dVwKrQ7k1jVPZkJzoVPXjUy+WaGhtx5LKvGKhIexNFQtqs4raYdVbDHNDNmuLMV+psPAFfh1VLKpWKd1kUUzggQl4TtIyOXfB2k6JSXZyjee80FBAOyL0pCa3AAX3jppzmiKq4Ct2Jx4RMEXYf/IlJVmQjQ3kaZOc1tYB1pd1+Mou0IqO99Vuh+MI60KlJE/lQbOF16ZvaDp5G8KTqybkNQuWcg1sGJD4GzkGxkKwCNzVKaQDWfMsBRC1JHMgKn6V/6i9BhDdGFrQu1LVDS6sDU/JRMgBW2nV4YzXjFdRcUgair9mm1XR61R3zugsOX64K5Dfdz7KQNH2cGcdQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=13ef5.5ff4ad54.k2101; olt=johnl-iecc.com@submit.iecc.com; bh=K0/TGAXCFQ3eGp59Xn08ZKJUjRGny9xWksWK2zFaZzY=; b=xkEpb1PVoC/jjx/PR+su769jmmpmrGTYLVf8xgTgi9XcRhLH04SJRAn2MedN18fK2w8eSN1vDNWn8Ak1J4FeuvJBU4X5xSpyINzKobaRcgZcfa8hM7wJxU15RBYcK9VhBu1lfIdYl+V8H1PB2G6+MxA6isHczqiwxZ4MJ+ZUqzOD1TQFlQa6A+5PLGpOiy5TO2NZJLMakuHU27++aAju4y4O7arMvPGjwH87uYDf49LaDzR+t1i/MLAjqLy+9Kan4ZmttdvzIBBmtr/lH7ATxdN+dzcwyaZ93Hop3IwUAT/09nuP3x56pGdNeloU1cZisvJSCUmUPMaI5m3QIUpXMw==
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 05 Jan 2021 18:17:55 -0000
Date: 5 Jan 2021 13:17:55 -0500
Message-ID: <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com>
From: "Paypal security confirm your password now" <johnl@taugh.com>
To: "Jim Fenton" <fenton@bluepopcorn.net>
Cc: dmarc@ietf.org
In-Reply-To: <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-2132600213-1609870675=:69993"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/UV5QxCJUEoFkWYhX9aWter_vI1k>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 18:18:01 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-2132600213-1609870675=:69993
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

>> reputation for the domain. I have trouble imagining why anyone would
>> think it's a good idea to get alignment by using third party domains
>> that recipients don't know.
>
> Because recipients often can’t see (or don’t pay attention to) the domain 
> name and the reputation system you postulate doesn’t exist. OTOH, getting 
> alignment avoids a restrictive policy that might be associated with the 
> original domain.

I think you're saying that I can always evade DMARC problems by putting an 
address I control on the From line and nobody will notice.  That would 
mean that DMARC is useless.

If that's not what you're saying, could you clarify?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
--0-2132600213-1609870675=:69993--


From nobody Tue Jan  5 10:28:45 2021
Return-Path: <kurta@drkurt.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 201E93A10EB for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 10:28:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.com
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 gqwtnSFsxwgU for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 10:28:42 -0800 (PST)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69C683A10E5 for <dmarc@ietf.org>; Tue,  5 Jan 2021 10:28:42 -0800 (PST)
Received: by mail-io1-xd35.google.com with SMTP id w18so298583iot.0 for <dmarc@ietf.org>; Tue, 05 Jan 2021 10:28:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bm5s8AuMNZQR7dVGotGPpYk9f7G4bnB0IQlyvac2B8Q=; b=WLobeElaKeNFNHpaYLHLEvI2uWQOxPeSD11jqLk8K/3gOpK++dxrtErZk+HxjOJsA9 Pyu/GJZ0vMzn1hZkKfSZypcOK3L4hm2DeDprWqxuHGtFJP0h0N6/fuBRBvvZ3lKs3aIj GCYXzW1m5ne2dV8vpKGz+Xv6V9LkvuPRt+bAY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bm5s8AuMNZQR7dVGotGPpYk9f7G4bnB0IQlyvac2B8Q=; b=laFerzyG8Vmmf5iVSvSD/BTzeIKE5mV80Igzgk6Uupyiuy4z9rE/g1vG9xzd2EVtk8 p7zuCoUnPZtqUWVZGSXdLX1112MN6g8+3Lscp0mlAntJQTSg2VcyK0zvtw93fLk/B03O olCfINZ1YVmKf57oKsnMpctMnBbLal6pDjk8GXfFx7hiENYadA/HEUUaXQTuX36K3zNh 89EZK/j2qpaRmpkWzLh/uys0Gn3NLdnIG1oWr0MsoBMEqbdH7oBbLqAKmpvEJ9ZBzlL2 4lMoJfYlIn8WGloyh2X57FbBDQWy6ZJjGaokoLJ+DFRlFw5WyW3uIgDvatiTIQeAvnSR PtRw==
X-Gm-Message-State: AOAM532vTeF0l6Iy7MjT1eew++mbhk1USMx+VA4yvRW+Ky4Q2peOw827 OLLx40Mj5po5/OF1eBFHvNRuBX18LcNQETX9a+J7NJFAJnXIBg==
X-Google-Smtp-Source: ABdhPJxsBcIjX5M2HhOc28Eau1yPi+mhldCExCM31m/DbEWCh5ZYSAhVTWeM9SCZh6SwrvOCIGlSlv1R3rDOlHL5iKg=
X-Received: by 2002:a02:a1ca:: with SMTP id o10mr794877jah.19.1609871321529; Tue, 05 Jan 2021 10:28:41 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com>
In-Reply-To: <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Tue, 5 Jan 2021 10:28:13 -0800
Message-ID: <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com>
To: Paypal security confirm your password now <johnl@taugh.com>
Cc: Jim Fenton <fenton@bluepopcorn.net>, "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004115f405b82b60ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VIKfu2UADJGmhp2Mr35K-3v_s50>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 18:28:44 -0000

--0000000000004115f405b82b60ec
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 5, 2021 at 10:18 AM Paypal security confirm your password now <
johnl@taugh.com> wrote:

> >> reputation for the domain. I have trouble imagining why anyone would
> >> think it's a good idea to get alignment by using third party domains
> >> that recipients don't know.
> >
> > Because recipients often can=E2=80=99t see (or don=E2=80=99t pay attent=
ion to) the
> domain
> > name and the reputation system you postulate doesn=E2=80=99t exist. OTO=
H,
> getting
> > alignment avoids a restrictive policy that might be associated with the
> > original domain.
>
> I think you're saying that I can always evade DMARC problems by putting a=
n
> address I control on the From line and nobody will notice.  That would
> mean that DMARC is useless.
>
> If that's not what you're saying, could you clarify?
>

That is indeed the assertion - as long as you consider 97+% to be "always"
and interpret "nobody" in terms of real human actors (excluding the
automatons on this list) and discount the influence of receiver-level
reputation/filtering mechanisms. Personally, I think those levels of
rounding errors should not be ignored either for good or evil. The
formation of this working group and our initial deliverables provides some
level of concurrence with my personal perspective.

--Kurt

--0000000000004115f405b82b60ec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 5, 2021 at 10:18 AM Paypal se=
curity confirm your password now &lt;<a href=3D"mailto:johnl@taugh.com">joh=
nl@taugh.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">&gt;&gt; reputation for the domain. =
I have trouble imagining why anyone would<br>
&gt;&gt; think it&#39;s a good idea to get alignment by using third party d=
omains<br>
&gt;&gt; that recipients don&#39;t know.<br>
&gt;<br>
&gt; Because recipients often can=E2=80=99t see (or don=E2=80=99t pay atten=
tion to) the domain <br>
&gt; name and the reputation system you postulate doesn=E2=80=99t exist. OT=
OH, getting <br>
&gt; alignment avoids a restrictive policy that might be associated with th=
e <br>
&gt; original domain.<br>
<br>
I think you&#39;re saying that I can always evade DMARC problems by putting=
 an <br>
address I control on the From line and nobody will notice.=C2=A0 That would=
 <br>
mean that DMARC is useless.<br>
<br>
If that&#39;s not what you&#39;re saying, could you clarify?<br></blockquot=
e><div><br></div><div>That is indeed the assertion - as long as you conside=
r 97+% to be &quot;always&quot; and interpret=C2=A0&quot;nobody&quot; in te=
rms of real human actors (excluding the automatons on this list) and discou=
nt the influence of receiver-level reputation/filtering mechanisms. Persona=
lly, I think those levels of rounding errors should not be ignored either f=
or good or evil. The formation of this working group and our initial delive=
rables provides some level of concurrence with my personal perspective.</di=
v><div><br></div><div>--Kurt</div></div></div>

--0000000000004115f405b82b60ec--


From nobody Tue Jan  5 10:50:42 2021
Return-Path: <fenton@bluepopcorn.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 5FEBC3A1147 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 10:50:41 -0800 (PST)
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_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 S2wfYDDAaVc8 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 10:50:39 -0800 (PST)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 C8C8C3A1158 for <dmarc@ietf.org>; Tue,  5 Jan 2021 10:50:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=sCovOmI0GhNzj/Rx+j211HU5TbwmGqCAibxlq7iXK1c=; b=XA2BgcpnvGp6xQ6JBqCZuBL3zg 7O/b5/SyrSZ+A8HgYyAqEd9U0Xx3qY7toJeq3dlW+doBamuUY+u+1qxckh6upK59cAKIL4Ah8Ja2U XPfML99pCe7sRWRVn66EaLz1yNhQoFMBSS1xJKUE9x9js1enJUbJryjotYebMbCY8TMI=;
Received: from [2601:647:4400:1261:108d:ac48:81ff:6e96] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1kwrPj-0005d8-0B; Tue, 05 Jan 2021 10:50:39 -0800
From: "Jim Fenton" <fenton@bluepopcorn.net>
To: "Paypal security confirm your password now" <johnl@taugh.com>
Cc: dmarc@ietf.org
Date: Tue, 05 Jan 2021 10:50:38 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <A2966FEB-45C6-46E1-8D7C-E811C785666A@bluepopcorn.net>
In-Reply-To: <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/eaAndLrLxxuV0jIkRJBruG2XRdk>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 18:50:41 -0000

On 5 Jan 2021, at 10:17, Paypal security confirm your password now 
wrote:

>>> reputation for the domain. I have trouble imagining why anyone would
>>> think it's a good idea to get alignment by using third party domains
>>> that recipients don't know.
>>
>> Because recipients often can’t see (or don’t pay attention to) 
>> the domain name and the reputation system you postulate doesn’t 
>> exist. OTOH, getting alignment avoids a restrictive policy that might 
>> be associated with the original domain.
>
> I think you're saying that I can always evade DMARC problems by 
> putting an address I control on the From line and nobody will notice.  
> That would mean that DMARC is useless.
>
> If that's not what you're saying, could you clarify?

I used the word “often” and indeed some people will notice as I did. 
But I recall we beat this issue to death a few months ago, although 
I’m not sure what WG consensus on that was, if any.

It looks like we’ve strayed pretty far from the subject line (failure 
reports) though.

-Jim


From nobody Tue Jan  5 11:22:35 2021
Return-Path: <dcrocker@gmail.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 0F2D13A102B for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 11:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 bSNklJMO8p_X for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 11:22:27 -0800 (PST)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0AC23A103C for <dmarc@ietf.org>; Tue,  5 Jan 2021 11:22:27 -0800 (PST)
Received: by mail-pj1-x102c.google.com with SMTP id hk16so214734pjb.4 for <dmarc@ietf.org>; Tue, 05 Jan 2021 11:22:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=/fld0DIQ/nQ8OjRy9obeZgmeu6ByunZQOieyCz5troU=; b=fqCiwVtuC/U8vFH+/vy5qWhCNALKp2WZ4WpSljX+wp5USw8z7MmHoL5ASwdhRjcGvc Bbc7ZjCsb2s6LTEzOcWP0MH3Et5XHIe3tATL9IreNYhnhLOxvmAA4qyI9+Zur96NRSfw 8/bWD9lBY4wGRM8PyYafQckQGNbwf2OKLXgfhNlDyBnUEPkz40NmN6qxf+zcaUypFY2K rUHogoT5nV7Rh9ebKfPv//gm3c85F/NTnrUdstBhY+iAtNTqsobC/qYBTUb9VzjHy1lg /iKhyvPrRgvIejZevjUGUkXBfot32JJsvdLQq33YWnUjciCUBW+tY9XeOt04QuLFs7Zg d/YA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=/fld0DIQ/nQ8OjRy9obeZgmeu6ByunZQOieyCz5troU=; b=rfzVO+fQH+dwVn5CVFYLlOHlgYaO2tRtdFSXhtLQxVlo2Gl0DDO6BZyk6Jm0WtfoCI yW0uukX3pIPdHCV3AY6/BKaTx2wEmHMzHAsKukfafGPRmrm7FklwYaxx2ySc68YTrfjF sxUKqT6Eb9jNg3DKVNOO+oaIe3DZu4ohX9BVHuypL38fdBkXJsUDVEccyJyen26R9SPi Z4dW0aaEfEgg/7/VZapnIDxadVLjgbJZZBUHv3XV9yrZ+HGRLkBDxMDdXcB3bklOV6y8 DRYDgrvTddZq8lfJVb95l4HY3RF/ICX0Jt1GDXziBqUB8t95xa8chK4RQTyiRwwHOsUk mI9w==
X-Gm-Message-State: AOAM531YWbbdZurr4Ph+dJG9oci1YGG9f6yfTOAlUDMF5bocnM57NfzV P5ZeB/DI1rUj/KL3S8+8fkvrbY/IJWQ=
X-Google-Smtp-Source: ABdhPJx2UhJdJzPwTttguG8r5ElTjFHyDZVT41mOy6E5iK3K8k1hwbd137iIePp6SecTnQVB5oyrEQ==
X-Received: by 2002:a17:902:34f:b029:dc:3032:e47d with SMTP id 73-20020a170902034fb02900dc3032e47dmr1022688pld.15.1609874546808;  Tue, 05 Jan 2021 11:22:26 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id g17sm507491pgg.78.2021.01.05.11.22.25 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 11:22:26 -0800 (PST)
To: "dmarc@ietf.org" <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com>
Date: Tue, 5 Jan 2021 11:22:25 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------6BB891855698B185017A5908"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/y9PjFGh7S0jr_kWd_So87NhEe3I>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 19:22:29 -0000

This is a multi-part message in MIME format.
--------------6BB891855698B185017A5908
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 1/5/2021 10:28 AM, Kurt Andersen (b) wrote:
>
>     > Because recipients often can’t see (or don’t pay attention to)
>     the domain
>     > name and the reputation system you postulate doesn’t exist.
>     OTOH, getting
>     > alignment avoids a restrictive policy that might be associated
>     with the
>     > original domain.
>
>     I think you're saying that I can always evade DMARC problems by
>     putting an
>     address I control on the From line and nobody will notice.  That
>     would
>     mean that DMARC is useless.
>
>     If that's not what you're saying, could you clarify?
>
>
> That is indeed the assertion - as long as you consider 97+% to be 
> "always" and interpret "nobody" in terms of real human actors 
> (excluding the automatons on this list) and discount the influence of 
> receiver-level reputation/filtering mechanisms. Personally, I think 
> those levels of rounding errors should not be ignored either for good 
> or evil. The formation of this working group and our initial 
> deliverables provides some level of concurrence with my personal 
> perspective.


From: header field rewriting demonstrates that DMARC is, indeed, trivial 
to defeat (or rather, to route around.)  Also, receiver filtering 
engines are all that matter.  Real-time actions by recipients are 
demonstrably irrelevant to DMARC (and all other anti-abuse) utility.

DMARC has utility because a great deal of spam includes unauthorized use 
of domain names that happen to support DMARC.

Some anti-abuse methods have inherent utility.  They are useful even if 
abusers seek to defeat the methods.  Other methods have utility by 
virtue of correlations with current behavior.  They are useful now, but 
merely require some effort by abusers to defeat (or route around.)

DMARC has the appearance of the former but is actually the latter.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


--------------6BB891855698B185017A5908
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/5/2021 10:28 AM, Kurt Andersen (b)
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com">
      <blockquote class="gmail_quote" style="margin:0px 0px 0px
        0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">&gt;
        Because recipients often can’t see (or don’t pay attention to)
        the domain <br>
        &gt; name and the reputation system you postulate doesn’t exist.
        OTOH, getting <br>
        &gt; alignment avoids a restrictive policy that might be
        associated with the <br>
        &gt; original domain.<br>
        <br>
        I think you're saying that I can always evade DMARC problems by
        putting an <br>
        address I control on the From line and nobody will notice.  That
        would <br>
        mean that DMARC is useless.<br>
        <br>
        If that's not what you're saying, could you clarify?<br>
      </blockquote>
      <div><br>
      </div>
      <div>That is indeed the assertion - as long as you consider 97+%
        to be "always" and interpret "nobody" in terms of real human
        actors (excluding the automatons on this list) and discount the
        influence of receiver-level reputation/filtering mechanisms.
        Personally, I think those levels of rounding errors should not
        be ignored either for good or evil. The formation of this
        working group and our initial deliverables provides some level
        of concurrence with my personal perspective.</div>
    </blockquote>
    <p><br>
    </p>
    <p>From: header field rewriting demonstrates that DMARC is, indeed,
      trivial to defeat (or rather, to route around.)  Also, receiver
      filtering engines are all that matter.  Real-time actions by
      recipients are demonstrably irrelevant to DMARC (and all other
      anti-abuse) utility.<br>
    </p>
    <p>DMARC has utility because a great deal of spam includes
      unauthorized use of domain names that happen to support DMARC. <br>
    </p>
    <p>Some anti-abuse methods have inherent utility.  They are useful
      even if abusers seek to defeat the methods.  Other methods have
      utility by virtue of correlations with current behavior.  They are
      useful now, but merely require some effort by abusers to defeat
      (or route around.)</p>
    <p>DMARC has the appearance of the former but is actually the
      latter.</p>
    <p>d/<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Dave Crocker
<a class="moz-txt-link-abbreviated" href="mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------6BB891855698B185017A5908--


From nobody Tue Jan  5 11:34:53 2021
Return-Path: <mike@fresheez.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 BA8903A11E8 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 11:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 SpmrHQokivjx for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 11:34:44 -0800 (PST)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FDE73A11F7 for <dmarc@ietf.org>; Tue,  5 Jan 2021 11:34:43 -0800 (PST)
Received: by mail-pl1-x634.google.com with SMTP id j1so278618pld.3 for <dmarc@ietf.org>; Tue, 05 Jan 2021 11:34:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=g/LN+TDnZWIWrkIqnHLD5UwxFzgS+lRir+XqOHJVOnY=; b=lubPX8xDUzN810lGNOkBMPW7oRKkEgtmJJZCeq9ze0ybIF3BM+aW8gMnYBDMbbnzN7 Mn+2MVfLCc2IhlCtZOe/fmPH3M8cG7rSUtxWS170Dr0sm29ozIZT0Mydh0vEnASMOB09 lBrdGjC19S9A1uVHNw10NohGkKqWVQxPLWJvM9RY035PBUzOy/9BHM2MiPItMIksQV9k eoqHXYL7Udcynh7Kjd0rvSMZ7FICD7qAP4AcrZScoa5z0v52d93Es3gJZskWlWBWrULs Pn88q5eQ7fZOHXUYFYIcyXRzTIM2Qh8PIUYShxgBDRJCEKm6YCMO2908Wv9BLBpoY5Zm B4mQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=g/LN+TDnZWIWrkIqnHLD5UwxFzgS+lRir+XqOHJVOnY=; b=oTixgw4UlmwCokgeDGklmO6PtJgxqfnmope2Z0m4S3HSskpxPp0b975QG3XNtdF5ET WGh8ocJTCMia+BS+A6F7j7qCzG6iSDIc6k2xaBo987sBkrNz04PdFQx7vKXDa5fWGWB7 NuoLwHb6aHgzUjAfGli/yUocuof7vfK6SrZXV/s9ehPt08zu3VTR6UdXS5AgVnB8TMWq E9agcgDdTa+M268AqHyl3MXjTFv8TxuQL/Gc/udxh4buFQvDnLya8LJ8DZr1hAq4vNhq Ki/SIUmJ1ns/PoFDr/aL+AI8yVub9TX7TeL0XesAp9qWKQbD88oREvaxOsdLSzH4tAqg LhvQ==
X-Gm-Message-State: AOAM531HyIRpPgpdPfI4ad5VCeGrEmNH25ZDEM4bcfo60GSwd0ZGoNIC fnVMfCnLImW3pF30vIbbpm2UI2hHCOnjDQ==
X-Google-Smtp-Source: ABdhPJwMadNrU/92awcxuH3sWR/sJ6Vokse7XRvkY5IMtAu0n/0FiJe7VSeKirM1Y2kdO4N112kMXw==
X-Received: by 2002:a17:90a:414d:: with SMTP id m13mr693951pjg.229.1609875283022;  Tue, 05 Jan 2021 11:34:43 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id gk4sm10168pjb.57.2021.01.05.11.34.42 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 11:34:42 -0800 (PST)
To: dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com>
Date: Tue, 5 Jan 2021 11:34:41 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com>
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/GdkJANVhUTO5d2yBb1BDlsYxaQA>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 19:34:52 -0000

On 1/5/21 11:22 AM, Dave Crocker wrote:
>
> From: header field rewriting demonstrates that DMARC is, indeed, 
> trivial to defeat (or rather, to route around.)  Also, receiver 
> filtering engines are all that matter.  Real-time actions by 
> recipients are demonstrably irrelevant to DMARC (and all other 
> anti-abuse) utility.
>
That's not the conclusion of the paper that Doug Foster linked to the 
other day. It showed that visual indicators statistically helped. The 
biggest problem was the low deployment rate of DMARC from what I can 
tell from the paper. Everybody here should read that paper IMO.

When I first came back and saw the From rewriting I was very confused by 
what it was until I figured out what was going on. If it were directly 
sent to me I would definitely be suspicious. But Thunderbird shows the 
entire email address when you view it, unlike some of the crappy MUA's 
out there. What we should be agitating for is better MUA's in general 
that care about security. Not IETF, obviously, but the email community 
at large.

Mike


From nobody Tue Jan  5 12:05:06 2021
Return-Path: <dcrocker@gmail.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 D8D6B3A11A1 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 12:05:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.358
X-Spam-Level: 
X-Spam-Status: No, score=-2.358 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JaPQ__nGZD2P for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 12:05:02 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2424F3A119B for <dmarc@ietf.org>; Tue,  5 Jan 2021 12:05:02 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id c12so358589pfo.10 for <dmarc@ietf.org>; Tue, 05 Jan 2021 12:05:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=MVBEIsgBNGE/NGeh5yturFY8nKYvBHKjrNIQx0GmgBE=; b=loj9NbZWX0LKF1TLoxmG1hg51312WguOK6H22l1O0NqZQpngwOzVDt8Rc5bEzAHxav m0x6HTYnWMtxikJwZ6rUfBNKS8nio6On/zZ/K+oQaQhUhqdutbUmPweZ+u7+iJjcjgLi m4//TRijrt0/ESs+mxkMha61VWdq6ux3gaZyVHsayz0uqIs3C7ybq6U163IYwmnTTKEt vtL6dAruk0StTIlBhfLkMllrlvPX5pJkt6TBNKyxi2M1VBoFlYJzfuxNk401xeEEb8QD S1xk4iR+AhZrNWERygSzWtLp+KFKjvNKsU1WKb+5qmu2jkS/7386j17Ur/WLE3Grvg5h KlGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=MVBEIsgBNGE/NGeh5yturFY8nKYvBHKjrNIQx0GmgBE=; b=RsEccFR48N8cRSjqLsUpLbjjGWeOn+WInHzoW7ANRkr1soKT3LmDkcCEepatOVIZxo tL7H2pivXb7EAYBUQx0dYwnqkConapS94/Atjuk+6f80gTqfFe/iO8Ehd4tp/0h3w8FK 5TqPl5N+JHT0u//s4R3dhhD8P0NgkYXK7Ih870o/sXnvvIVkUbWkYuiNbH5qB7Ep4P0u WFSPxVCj8tLWKyrxQ4KhTpFkRiM1gdHIW09sKHXqUSqZHnL5lhkkiJMEc8yT2gw86N8b pSvNTLmsLVhCJKiL3qmwhNqhvEmaPZPlav5iwemNC/wappMrM1ubNsp05lsBu0MOVsXx TtDA==
X-Gm-Message-State: AOAM533uV4uVs494Ue7nqu9zVsDUAB5IY6YhA9jMJSxTuvBFsDTHXfdg v9XuUVXsSDMAVzJhdTqcMo0zN+k567I=
X-Google-Smtp-Source: ABdhPJxfmR/psqlbER40dYP1dIDMv65Q1luLAG4C0poggDcwh5q5xC27ZhapZ3HuQlzCIPFTO3QyPw==
X-Received: by 2002:a62:7907:0:b029:19d:cf5d:20ae with SMTP id u7-20020a6279070000b029019dcf5d20aemr699197pfc.2.1609877100958;  Tue, 05 Jan 2021 12:05:00 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id s1sm4092686pjk.1.2021.01.05.12.04.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 12:05:00 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <050e8614-c088-a165-a733-35c5eee52eed@gmail.com>
Date: Tue, 5 Jan 2021 12:04:59 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com>
Content-Type: multipart/alternative; boundary="------------0EA026969B59934DDDB54980"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/TsWfZP22axoPT8nnVTs5lKd69Lw>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 20:05:05 -0000

This is a multi-part message in MIME format.
--------------0EA026969B59934DDDB54980
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 1/5/2021 11:34 AM, Michael Thomas wrote:
> On 1/5/21 11:22 AM, Dave Crocker wrote:
>> From: header field rewriting demonstrates that DMARC is, indeed, 
>> trivial to defeat (or rather, to route around.)  Also, receiver 
>> filtering engines are all that matter.  Real-time actions by 
>> recipients are demonstrably irrelevant to DMARC (and all other 
>> anti-abuse) utility.
>>
> That's not the conclusion of the paper that Doug Foster linked to the 
> other day.


1. I've looked back over his postings to this mailing list and am not 
finding the link you refer to.  Please post it (again).

2. A single study is unlikely to be definitive about much of anything.

3. Especially when it counters years of experience, including the Web EV 
experiment:

https://en.wikipedia.org/wiki/Extended_Validation_Certificate

>
>       Effectiveness against phishing attacks with IE7 security UI
>
> In 2006, researchers at Stanford University 
> <https://en.wikipedia.org/wiki/Stanford_University> and Microsoft 
> Research <https://en.wikipedia.org/wiki/Microsoft_Research> conducted 
> a usability study^[21] 
> <https://en.wikipedia.org/wiki/Extended_Validation_Certificate#cite_note-21> 
> of the EV display in Internet Explorer 7 
> <https://en.wikipedia.org/wiki/Internet_Explorer_7>. Their paper 
> concluded that "participants who received no training in browser 
> security features did not notice the extended validation indicator and 
> did not outperform the control group", whereas "participants who were 
> asked to read the Internet Explorer help file were more likely to 
> classify both real and fake sites as legitimate". 


> When I first came back and saw the From rewriting I was very confused 
> by what it was until I figured out what was going on. 

You think you are representative of end users?  Try again.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


--------------0EA026969B59934DDDB54980
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/5/2021 11:34 AM, Michael Thomas
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com">On 1/5/21
      11:22 AM, Dave Crocker wrote:
      <br>
      <blockquote type="cite" style="color: #0000a0;">
        From: header field rewriting demonstrates that DMARC is, indeed,
        trivial to defeat (or rather, to route around.)  Also, receiver
        filtering engines are all that matter.  Real-time actions by
        recipients are demonstrably irrelevant to DMARC (and all other
        anti-abuse) utility.
        <br>
        <br>
      </blockquote>
      That's not the conclusion of the paper that Doug Foster linked to
      the other day.</blockquote>
    <p><br>
    </p>
    <p>1. I've looked back over his postings to this mailing list and am
      not finding the link you refer to.  Please post it (again).</p>
    <p>2. A single study is unlikely to be definitive about much of
      anything.</p>
    <p>3. Especially when it counters years of experience, including the
      Web EV experiment:<br>
    </p>
    <p>    
      <a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Extended_Validation_Certificate">https://en.wikipedia.org/wiki/Extended_Validation_Certificate</a></p>
    <blockquote type="cite">
      <h3><span class="mw-headline"
          id="Effectiveness_against_phishing_attacks_with_IE7_security_UI">Effectiveness
          against phishing attacks with IE7 security UI</span></h3>
      In 2006, researchers at <a
        href="https://en.wikipedia.org/wiki/Stanford_University"
        title="Stanford University">Stanford University</a> and <a
        href="https://en.wikipedia.org/wiki/Microsoft_Research"
        title="Microsoft Research">Microsoft Research</a> conducted a
      usability study<sup id="cite_ref-21" class="reference"><a
href="https://en.wikipedia.org/wiki/Extended_Validation_Certificate#cite_note-21">[21]</a></sup>
      of the EV display in <a
        href="https://en.wikipedia.org/wiki/Internet_Explorer_7"
        title="Internet Explorer 7">Internet Explorer 7</a>. Their paper
      concluded that "participants who received no training in browser
      security features did not notice the extended validation indicator
      and did not outperform the control group", whereas "participants
      who were asked to read the Internet Explorer help file were more
      likely to classify both real and fake sites as legitimate".
    </blockquote>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com">When I
      first came back and saw the From rewriting I was very confused by
      what it was until I figured out what was going on. </blockquote>
    <p>You think you are representative of end users?  Try again.</p>
    <p><br>
    </p>
    <p>d/<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Dave Crocker
<a class="moz-txt-link-abbreviated" href="mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------0EA026969B59934DDDB54980--


From nobody Tue Jan  5 12:12:00 2021
Return-Path: <mike@fresheez.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 27A133A11B1 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 12:11:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 Sbrr4rV--oVa for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 12:11:57 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA6A13A11B0 for <dmarc@ietf.org>; Tue,  5 Jan 2021 12:11:57 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id l23so310652pjg.1 for <dmarc@ietf.org>; Tue, 05 Jan 2021 12:11:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=GOHPWyZkUia3teNcb4Oeq1EEb6JqaPUWVvn9Q3ZTa1c=; b=kduuk53V7QC0RT26kTHdugnkVC1XYUHd4xcoSzPel1n39Fu5oXBzfKLAbyz7GKP7Yi GC8aCCvUiVmSDatkDS8pzVo+sB/TZ9DiRREb4H6UZUZClsQPxQeGi8JgtLOxdSSRhMoe /geNTyXPABnF0xvPIAVvV456cC4l+aWDnPYGUPXRMZEZ7LbucTp+93vE4V3PM1OPBeTz axAh258bcnKtL2M4q8wqmCxEeYRX1w0Mw8H0ugWmFPJyuh2lG+LWlTDDYF/i+lbCOTHL EvhBQYdrPCIOMQ35Zc++kwv2D1VSlQxRCZu9UdIyb4CA2nyStRycsbijugqkdj+B5uCg WYtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GOHPWyZkUia3teNcb4Oeq1EEb6JqaPUWVvn9Q3ZTa1c=; b=As6u9HtR8IrxIyGCqWO4G2fswad7H5GY8t1kIBxwcsBLoKmkjMVwNTaYhGP/CJn2x4 tyfgUg05TQUGYWFsLIyGMOeefRYZsP4bMIpwFVJFrFIaiWbTznOZYYAbxvjwDutXKpYK nD+At17bgtivS6cLXbqOJ5ueMC9jEayIn8ah2b20RrGOYwU2EOr/lRKxapdOfwFD5xce 1CJJZYi0wfpqoAuDNkvgM+jgCqnPe9KqN0AAuWnVz9Mon9xHs9yiDDSVGsCLs/f27GRb frMG0+iq6B/0WfGJr5SvVjxqYGFDySjnICtF2WS0GZ8V/TXcWTU0iOfqzl+m9Qa7Z+DC pp4g==
X-Gm-Message-State: AOAM531jiNwFXDHLcRYg+w8lxe50HxKjBVTqsnEFLZL0jTQ5vSfpfZWq 2R5G2Na+Fl/ZbQ2lZ6RyxEzit0AMM06Y3g==
X-Google-Smtp-Source: ABdhPJzCGrZScXT8r2+5vKkLKhjnYTl+vg1RECPQ6lTpQ2ZxcK+ZXRzm6sMdky6W2IaQI6p5agu0Sg==
X-Received: by 2002:a17:902:a983:b029:dc:2564:91f2 with SMTP id bh3-20020a170902a983b02900dc256491f2mr1195083plb.46.1609877515466;  Tue, 05 Jan 2021 12:11:55 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id i13sm43038pgd.32.2021.01.05.12.11.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 12:11:54 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com>
Date: Tue, 5 Jan 2021 12:11:53 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <050e8614-c088-a165-a733-35c5eee52eed@gmail.com>
Content-Type: multipart/alternative; boundary="------------B2A10F661D2B1C6569BB110A"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/NNs4q7p1zXuKtukGT7a2Sm5TWLg>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 20:11:59 -0000

This is a multi-part message in MIME format.
--------------B2A10F661D2B1C6569BB110A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/5/21 12:04 PM, Dave Crocker wrote:
> On 1/5/2021 11:34 AM, Michael Thomas wrote:
>> On 1/5/21 11:22 AM, Dave Crocker wrote:
>>> From: header field rewriting demonstrates that DMARC is, indeed, 
>>> trivial to defeat (or rather, to route around.)  Also, receiver 
>>> filtering engines are all that matter.  Real-time actions by 
>>> recipients are demonstrably irrelevant to DMARC (and all other 
>>> anti-abuse) utility.
>>>
>> That's not the conclusion of the paper that Doug Foster linked to the 
>> other day.
>
>
> 1. I've looked back over his postings to this mailing list and am not 
> finding the link you refer to.  Please post it (again).
>
> 2. A single study is unlikely to be definitive about much of anything.
>
https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf

Actual data, actual experiments. Finally. And it's a lot better than all 
of the conjecture here which is the currency of the realm.


> When I first came back and saw the From rewriting I was very confused 
> by what it was until I figured out what was going on.
>
> You think you are representative of end users?  Try again.
>
>
I use my inner Luddite to use all of the time. It's one of my skills. 
But an MUA designed with security in mind with its UI would go a long 
way too. From re-writing is exactly the wrong thing to do from a 
security standpoint though.

Mike


--------------B2A10F661D2B1C6569BB110A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/5/21 12:04 PM, Dave Crocker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:050e8614-c088-a165-a733-35c5eee52eed@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div class="moz-cite-prefix">On 1/5/2021 11:34 AM, Michael Thomas
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com">On
        1/5/21 11:22 AM, Dave Crocker wrote: <br>
        <blockquote type="cite" style="color: #0000a0;"> From: header
          field rewriting demonstrates that DMARC is, indeed, trivial to
          defeat (or rather, to route around.)  Also, receiver filtering
          engines are all that matter.  Real-time actions by recipients
          are demonstrably irrelevant to DMARC (and all other
          anti-abuse) utility. <br>
          <br>
        </blockquote>
        That's not the conclusion of the paper that Doug Foster linked
        to the other day.</blockquote>
      <p><br>
      </p>
      <p>1. I've looked back over his postings to this mailing list and
        am not finding the link you refer to.  Please post it (again).</p>
      <p>2. A single study is unlikely to be definitive about much of
        anything.</p>
    </blockquote>
    <p><a class="moz-txt-link-freetext" href="https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf">https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf</a></p>
    <p>Actual data, actual experiments. Finally. And it's a lot better
      than all of the conjecture here which is the currency of the
      realm.<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:050e8614-c088-a165-a733-35c5eee52eed@gmail.com">When I
      first came back and saw the From rewriting I was very confused by
      what it was until I figured out what was going on.
      <p>You think you are representative of end users?  Try again.</p>
      <br>
    </blockquote>
    <p>I use my inner Luddite to use all of the time. It's one of my
      skills. But an MUA designed with security in mind with its UI
      would go a long way too. From re-writing is exactly the wrong
      thing to do from a security standpoint though.<br>
    </p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------B2A10F661D2B1C6569BB110A--


From nobody Tue Jan  5 12:48:58 2021
Return-Path: <dcrocker@gmail.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 8D4833A11F0 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 12:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 n5rp1adEdc6q for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 12:48:55 -0800 (PST)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BB393A11EA for <dmarc@ietf.org>; Tue,  5 Jan 2021 12:48:55 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id lb18so347926pjb.5 for <dmarc@ietf.org>; Tue, 05 Jan 2021 12:48:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=btW3z7ME5UeuF2gE1nsPbfIf9JaYWdy4iBn11cUwlXw=; b=C0V3jhgLO+Kv0y1WvQ1OBMvYezSvWSVgU1RjhvEBrQkJ9q4zpNRR75G4HjJoa80usl kuW+X821VRjxtydjKwwpB1omVQc1K/bvEHO1A78Z9KhETRzyCfOJVWtwS38GsNf5eP3d bNzH2Ql5ynIf1aIUkqMYa561qYrLdihfSN2oXKT3VAj31tgBM4Rv2EZK7YpR29db6FHj sGAAAZGMC0uxCVHTEIRaH5Uz05d8ajVJplfqt1EDDUXraPzqH1TgBQ1vKDIdBipb0es7 dxwtep47r69JkDu84pIwk/vi3EVRGJe59zwLw1/sGD8VE2a5oIQGOXKwMYc0wcC6Th7p OT8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=btW3z7ME5UeuF2gE1nsPbfIf9JaYWdy4iBn11cUwlXw=; b=mnMbBHFYcE9ZaQHdqBcmcOw2WiaYve1JNz5rCA1D+QrFzdQqTiroRLzyZ8O5BRf1nu x9OjE3S5HHi2OENzkQ7vl/VQVHroDXzYMOZ+v7gwvniGdbxnaInLAnxwvZ/GxdeNEHQb lBnVYGJtCBHliUufh2yvAlvI0IGTAoR8NtmAe3fnKN75Rg+Pxq7TfAa/NR43lU+cJe4+ UKyxNV3wcwoyR/5KOdzoCDtY9VDcZkB30tiIvpTrjuY+Zor3c7i722zRV2aExWawkvcl K+Cpv9lKKY2Ab2iis3Vn3/R57tFqs3LglAAiWtGMAiLDWQyKffsKeXe6SJYJ4GGXOil/ O5GQ==
X-Gm-Message-State: AOAM531ECLl6gXL4FB714+hMGPPbR0R8fDliI8vzSXCQxxUX9R2yhmSK bYu5LriHYVNteSlNFWJdFb69zhUcwzU=
X-Google-Smtp-Source: ABdhPJz/zvpCrpDrPos3VXoLuSy76vXMxKZBLsu70AofTST9DIVVzR1d3g0OTS0Ir2rxpwZcKsEBjA==
X-Received: by 2002:a17:90a:fb8a:: with SMTP id cp10mr963928pjb.136.1609879734570;  Tue, 05 Jan 2021 12:48:54 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id d20sm4143051pjz.3.2021.01.05.12.48.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 12:48:53 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com>
Date: Tue, 5 Jan 2021 12:48:52 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com>
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/BhSauaEiNEwZgAqxgqgXRrJdLXs>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 20:48:57 -0000

On 1/5/2021 12:11 PM, Michael Thomas wrote:
> On 1/5/21 12:04 PM, Dave Crocker wrote:
>>
>> 1. I've looked back over his postings to this mailing list and am not 
>> finding the link you refer to.  Please post it (again).
>>
>> 2. A single study is unlikely to be definitive about much of anything.
>>
> https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf
>
thanks.

How carefully did you read the details?  While I suppose the study is a 
bit interesting, it's a very long way from serving as definitive 'proof' 
of much of anything.


> Actual data, actual experiments. Finally. And it's a lot better than 
> all of the conjecture here which is the currency of the realm.
>
You might want to review the actual semantics of the statistical methods 
used for actual experiments.  They don't mean what you seem to think 
they mean. In particular note that the focus of such semantics is on 
negatives, rather than positives.  It's the reason that conclusions 
about affirmative statements require a constellation of studies.


> I use my inner Luddite to use all of the time. It's one of my skills. 
> But an MUA designed with security in mind with its UI would go a long 
> way too. From re-writing is exactly the wrong thing to do from a 
> security standpoint though.

That's been a regular refrain, for decades. Odd that we do not yet see 
actual efficacy, after all that... conjecture.

By now, there should be that constellation of compelling evidence for 
the efficacy of visual indicators with average recipients.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Tue Jan  5 12:55:29 2021
Return-Path: <mike@fresheez.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 950D83A1207 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 12:55:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 Zbk6kssDqN5P for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 12:55:25 -0800 (PST)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D8EC3A1204 for <dmarc@ietf.org>; Tue,  5 Jan 2021 12:55:25 -0800 (PST)
Received: by mail-pj1-x102f.google.com with SMTP id lb18so357924pjb.5 for <dmarc@ietf.org>; Tue, 05 Jan 2021 12:55:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=17YtKmvV/BsV7kHNbSUUV3oC6QMzptn0n41ViG5hG6g=; b=EQ5s3qhHupYZuBtMIoGMUefQRWohJONzfsdE7DMMBAyhyH9a+vQ0Nx9dRpD1AUyTzq 8x7txpqc2ysT7LbgmXhJHHdOOQxP7Ft6U4ZS95qYN5vY4Nad85uysZ141HVdMapsGnX8 AiluuC1tePszOYOSg/BPQYQWRrr2WXlcBJBHyExksnBc7XjEwTpfZWGc2t4+TroAEaGG t+kA5Os3qt3p1En17Ms/nGXnXkz5tgvRA0bT8v7uoAphuXQIbufCeScvt+GpkYH7A4MH Q1XJVlXMnkPAGu4cxKJjWZjRsmG56Ibo5KkQTEl9Rebyt/v3efrbGMt9/IiwgkBdq2kR tibA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=17YtKmvV/BsV7kHNbSUUV3oC6QMzptn0n41ViG5hG6g=; b=H3pcfp3m7r76P9bkAGS6FZ8ihsKvIZ0oX+wNi60B/EqvMmHIFoDlqXvJ8nhhZKKUkX RsxtXrmOGD/oitXV6ojl1BFO2MdiOU9abACgpWp8oiMSoD7IE96vZhvLRJ2bsyXoqY5r iRYEvBmhQajZrnIP7LWXvU4hha7MmtW8Mqmwm9lAXES1QwMwagJkYTOB7Bo+hIDXvUcy BPsIYrYRLM+PH9I0VwE3rEPSCkTfcrIMAiaIEBRGjugoRYn55COfcNMgDOYiXRxCfF61 Bd+sWpV/fx1S03v8tHNOiFpP7ElGAmc21WJ690AdaAlFIP09W9HospKfaP/Pcb6wTXRA E0cw==
X-Gm-Message-State: AOAM53310nG5cuSckw8k4bUnUpI1Nf4MA6Keo53lbjbLL9xoVGCCD/8l z93Qxw+JnciuGmXOT9gARi9GOrhY86Pgsw==
X-Google-Smtp-Source: ABdhPJySQ6w1PLskH7nRq/y8xLwNLk194VZXhIdd9vysb8iLRnQ5Mw6lF7Ine3G3/UbC9lQuTz4WVQ==
X-Received: by 2002:a17:903:22ca:b029:dc:9882:1f79 with SMTP id y10-20020a17090322cab02900dc98821f79mr1046528plg.33.1609880124487;  Tue, 05 Jan 2021 12:55:24 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id c24sm84159pgi.71.2021.01.05.12.55.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 12:55:23 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com>
Date: Tue, 5 Jan 2021 12:55:22 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com>
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/chady0dHUjj17oEoFUVg5PXZ3hc>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 20:55:28 -0000

On 1/5/21 12:48 PM, Dave Crocker wrote:
> On 1/5/2021 12:11 PM, Michael Thomas wrote:
>> On 1/5/21 12:04 PM, Dave Crocker wrote:
>>>
>>> 1. I've looked back over his postings to this mailing list and am 
>>> not finding the link you refer to.  Please post it (again).
>>>
>>> 2. A single study is unlikely to be definitive about much of anything.
>>>
>> https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf 
>>
>>
> thanks.
>
> How carefully did you read the details?  While I suppose the study is 
> a bit interesting, it's a very long way from serving as definitive 
> 'proof' of much of anything.
>
Who said it was proof? It's data. Very useful data, IMO. Did you read it 
carefully? It took me about a day to digest it. It also says with actual 
data that your assertion that users can't be trusted for anything is not 
correct. Categorical statements without data are always dubious.

Mike


From nobody Tue Jan  5 13:18:12 2021
Return-Path: <dcrocker@gmail.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 248533A011B for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 13:18:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 QEDE6MJ0TYPJ for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 13:18:10 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EABC03A0115 for <dmarc@ietf.org>; Tue,  5 Jan 2021 13:18:09 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id y8so419123plp.8 for <dmarc@ietf.org>; Tue, 05 Jan 2021 13:18:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=7KiQ79DC1JCVHad/vlcPIe3f11YgKitTNaJQXA/VWz4=; b=hkTyxbs5lo0fgVyrBAhu8FV55OfVtbXcmVvgD9BH9PktjxX8sX1o88mauE/bU/mwiv j4IXFO8X/Xc8mkeAK6evwZDE4TrSzVMSbiIzHIRexnLVSrbRdIyH8GqTDVWRxaBe7Niq pBU3SLUYlb6UmGYN806vf0Dqdy2+JFDp4oCRVBZEYkmKntvMNfG81/85/QvOMTAPu3LS jMnqZ13L6VTctprQv4vQ1QWCl0IWhwlT4GKJsP5MhQDUZCZWCf5TJeHZ+rTD86FhKQYs nbuXUTZu3T9JJoIL2KLHYR8CBQxdzmd7WYk2YlTOPx4BhzTJQR6qyD+0/gLlYTV9dpJ5 N1sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=7KiQ79DC1JCVHad/vlcPIe3f11YgKitTNaJQXA/VWz4=; b=D+zbyKq93vK/4H0QVXpA3pGtD1XsI3sXkyU0zFHIhI2UW1DgPXHuK9nZJ3LmDkZouk vpvKorzr6fSd3nX/dGgCxI2C+UFOioSbeyVE/EAEjrbOO4EAiudTBofpP10bd4k4D8ZK V3exLBmJEohwGQbRAfh2nMz/ZamtXAX3w8dxd6Ju16ma2Jc7zXCVQy/q1RfMJSkWyhLj cJ2a3SSGm7SqYBnCtDgjMaV847vwziPoIkLyA2jnyQ//ba+9blPnlkjc5UWR4q3zYUql a8qmMuOIDW9QxKcD/L88WsawWFtgsfjUemOXqqW6Hjsizwi0m4YnPdfmukLpjzvD3v0V NYcA==
X-Gm-Message-State: AOAM530EpvjJhVwTIEHytTLk7k98gjlVSqc3z2H5B7oCpjrIjZntOb1Q adKjqlYO6qFipBsmwwHVBN4Ty7HJKdQ=
X-Google-Smtp-Source: ABdhPJwITC3FdEUod92iOlv6l6xVZW+kO9BK4CCa77sqErKmItt4kZ6yvWAPKE5TkldIE/eh0MBS3Q==
X-Received: by 2002:a17:90a:d90e:: with SMTP id c14mr1013405pjv.85.1609881489233;  Tue, 05 Jan 2021 13:18:09 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id c62sm272903pfa.116.2021.01.05.13.18.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 13:18:08 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com>
Date: Tue, 5 Jan 2021 13:18:07 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com>
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/HYK4e7-YqED3jL3CqcRFFGrGrHU>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 21:18:11 -0000

On 1/5/2021 12:55 PM, Michael Thomas wrote:
> It also says with actual data that your assertion that users can't be 
> trusted for anything is not correct.

I didn't say that.  And it didn't say that.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Tue Jan  5 13:20:48 2021
Return-Path: <mike@fresheez.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 2D9653A02BB for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 13:20:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 DAGVPfhkVsWt for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 13:20:43 -0800 (PST)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B2513A0163 for <dmarc@ietf.org>; Tue,  5 Jan 2021 13:20:43 -0800 (PST)
Received: by mail-pj1-x102a.google.com with SMTP id b5so430150pjl.0 for <dmarc@ietf.org>; Tue, 05 Jan 2021 13:20:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=HVg0HUpbQV6WK3wRzvDR2emXn1a5MGp0DKZt2B/jyaM=; b=gzCjYQ7kkIZAS9f/+nPqSP8NId7DTz3IXfFt4Xjs11R4RNEjfVOUlcwTbg6+sTskZK HDi3Q7+oMXiS6iLV/L3qolP4GgNuLGJe6tqHv5MRugE/75fBYqP0ICbCRv85zRl0f6TE Y4wKjfjlgbAqoKt+G5Q4ag79Q17YuZo6jFtCVv6KO9jKoO2DAe4Q+cWwaK1axqA64JhW ONn7/f3TAeegXoMZmOgzA0geiW6SeCRujAnsTvWegLDekFt6GaQxO0kysq8jw6oyRel4 iLcIR9aC1Fu1CptBT2Gy7a/+c5P7drX/gcyErj6xB1JLnCEIFa1qADVTtf2QqhyhIxZg Isww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=HVg0HUpbQV6WK3wRzvDR2emXn1a5MGp0DKZt2B/jyaM=; b=VrWnSd8CzhB4aO8C67BwUNOkGuk7Z4EvhgSMVqJOnqjLZtP6ujO+n5Nu2hQEkveqyp JOTsCEcHYHFm91URVFkSmIY0Z6lFebLhSTUeeoYQwSJqNacdkbMba3v2oyU8s079wGdr 3u3NW7UKFHVpfBS5teWh8JR6L69U1J+RgOyd5UDmOhanIns2iN1Qp8wLX3phOVTvY/1x 7ZzJYySG9Xhg5S/UkyAmoqaQvcwrBMrLkFoXxo8m4BiEdgWpgxAB8s9KJjsrhMCUZf1W biHAv+Fbrv0qcazxLO/e1kkMirZpPOd28V44vYyxapPKJcENzZPokmXEJ3vxWjWEd0kt 8MAg==
X-Gm-Message-State: AOAM533fYv0/iGlCxglF81yalvV0dtgIG2MGiNyyu5FGX9pKgSqOv8OJ Uwex+dzDBfFZ6+Fj5IVsizD8Tol/vJd6Dw==
X-Google-Smtp-Source: ABdhPJyDieyPB6bDMW3zgvg1bgipjxgfLN0JS1Ql6uvfSOkmrg41eA4l+DvafOsWC1k9Uj8W4XC/Zw==
X-Received: by 2002:a17:90a:4bc3:: with SMTP id u3mr1088439pjl.56.1609881642335;  Tue, 05 Jan 2021 13:20:42 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id x27sm274441pfr.122.2021.01.05.13.20.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 13:20:41 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com>
Date: Tue, 5 Jan 2021 13:20:39 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com>
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/rocXGAUGLUVUpCTZog2vj2nNMXM>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 21:20:47 -0000

On 1/5/21 1:18 PM, Dave Crocker wrote:
> On 1/5/2021 12:55 PM, Michael Thomas wrote:
>> It also says with actual data that your assertion that users can't be 
>> trusted for anything is not correct.
>
> I didn't say that.  And it didn't say that.
>
>
"Also, receiver filtering engines are all that matter." The word all 
includes human beings. That's the nature of "all".

And you are wildly off topic.

Mike


From nobody Tue Jan  5 13:49:05 2021
Return-Path: <dcrocker@gmail.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 E5EA93A0888 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 13:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 03ilE94iWEmh for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 13:49:03 -0800 (PST)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDB7A3A086D for <dmarc@ietf.org>; Tue,  5 Jan 2021 13:49:03 -0800 (PST)
Received: by mail-pl1-x634.google.com with SMTP id q4so463559plr.7 for <dmarc@ietf.org>; Tue, 05 Jan 2021 13:49:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=E6BVVQop1igH6OzfAUgXi9uiZwcsRCRFerphiNtw4lU=; b=GXMaI9J6qF31Lo9HjrpTm383JxGLAyY4cYocvU8X3Ko0nb8PPUh4HcWzpRvbBc/VKS tN/Up2Ke/rhTyi6+RJVQ6ZfjQ20uTbj2sYfm3u1w+SIbpKT64LKy6niGm71e224OpkS4 ETrCNQLkt3kBG4caM77tDXJ/2ajL+rCR4amgDDr+7AH61fLVQSjwTxaZOCTHyJpbNH5b kDN1zybZfL6tKAdGAqjQFs/pgqxfkVvOHb+hcsRL6FN5QrjmE4s7B7k3wr73yyFek6ck lJ+bMioRKyU6jiWGmBnLj1EhEzjHXRRI83Cg+JR4rv94kLKXUZL57dVXBQRG2Nb2gj2E A1WQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=E6BVVQop1igH6OzfAUgXi9uiZwcsRCRFerphiNtw4lU=; b=ro4wDpTHGFfV2UFxD5aMXBQ5HBO/90rW9m0MJXzpxZsY8im2YNySqs0AgLhc+moK3C 6nvo/ICnHryV1QR62xFsOXpA2Y+U+p7a+LP/Xmn2kPo0Jk6sHfx6874vEuOVDC4K3i6H BZ9zO3e5z7aRF3OPd0Kp93smKGycyTYFdMYoQSjogMFv6QnI7zrZrzJpbDlyLUB/TUvH PMy8RZHHZAeVhg+eo976f+ASav8eP+7UhcR2VPNxpGP4hEULxv73uMDRrsJZ4JGsRY3a POAFIzdClVL0pG9+qPv9Rssstjn5nI3FBuRowdiRXSMmcQieCiqhrbERuTGPFmA5QP08 GBnQ==
X-Gm-Message-State: AOAM531rtBs+5nYWkSgkPrgQWYGQ7Uv7oGGu8oGrE2va9bV4wNf/xhOG kARTR9cNTh/ricPk50WWqhQYwH2V0rY=
X-Google-Smtp-Source: ABdhPJx/acjT9R03xGA/ZDfYyi5W5l2k1XDdP9TBXufRZPR5jWGOs9Kt/fHWrU8I3yXILwtZPj8h8A==
X-Received: by 2002:a17:902:9a02:b029:dc:3481:3ff1 with SMTP id v2-20020a1709029a02b02900dc34813ff1mr1125037plp.28.1609883343127;  Tue, 05 Jan 2021 13:49:03 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id q12sm147054pgj.24.2021.01.05.13.49.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 13:49:02 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com>
Date: Tue, 5 Jan 2021 13:49:01 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com>
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/wmnn3kG8LkCCCVgRC0fv0Cvedeo>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 21:49:05 -0000

On 1/5/2021 1:20 PM, Michael Thomas wrote:
> On 1/5/21 1:18 PM, Dave Crocker wrote:
>> On 1/5/2021 12:55 PM, Michael Thomas wrote:
>>> It also says with actual data that your assertion that users can't 
>>> be trusted for anything is not correct.
>> I didn't say that.  And it didn't say that.
> "Also, receiver filtering engines are all that matter." The word all 
> includes human beings. That's the nature of "all".

1. In terms of average use for typical email, it is.

2. The quoted statement has no semantic relationship to what you claimed 
I asserted (above).


> And you are wildly off topic.

'we' might be. but note that I'm merely responding to your own content.


d/


-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Tue Jan  5 13:58:14 2021
Return-Path: <mike@fresheez.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 4812D3A0925 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 13:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 rCC_66OQFkyc for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 13:58:11 -0800 (PST)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 175083A0907 for <dmarc@ietf.org>; Tue,  5 Jan 2021 13:58:11 -0800 (PST)
Received: by mail-pj1-x1032.google.com with SMTP id iq13so462774pjb.3 for <dmarc@ietf.org>; Tue, 05 Jan 2021 13:58:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=4xSvgM6/0yOuW3vJA5BWxRcyKEFdSpsPcBSwbahlhKU=; b=UTc6eAXSgOMFhhXUXxz+gbkju+dTwuKK7XPKVLlOo4Jt+3ve31zNIsiIQ5grNVCoZh 96RFBNazx4GGbu6PGPZWAiqOzMryYHWWbNy6uczg44i8bly1h60s/gdIyxb6fvtBe+r0 KE4T8YvQyzs5wDg1FDFSwQParePIkZv+091VWtLZ047RU6RG+UGg3Yt/cs7VG0pBl+2q I8rjaLLE/P2vqoA8RQ4H9BNNAvN/lKyMTGNqDMf7dBcrybUwYQE6mGd+/2oS7R4bv3LA tU5OQpWX0SvPSefcKY7JnnNg+EaDXKi3hfICRPvaNcDyauuHMWicEAqq/K1mCbBQQ93q G2Uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=4xSvgM6/0yOuW3vJA5BWxRcyKEFdSpsPcBSwbahlhKU=; b=CBLi0/uXffOnA3qH6D1jRC6IS/zB5oyHX9MYRS0FABz+mV/Gp7NFrNYaRmJFuaiimD i5PF5WhF/CLWLho8ILtIx2ZbuChOA4EFOEW4dOiJabs83d4j46RfWgHCCPTcxAmTJu4D ckxSvK7pIo4GXmwUYk7lfippRX4X3MIvDd697+HWDSf+Su5bh0Tl+P3o2CA4HtfVBK1+ 5njau6BiejhOwK54DuI2v+5pdDFhuuT7DGpz0XEiwUaS0CvSXAGWdeMADk32lJFMJzTA G2M7R16knFHvXEMKyKsFBDUa4V6Y4GRabIVq0mmhiJIc4jRupAN8c/dxCHsIBmtryRgA M/7g==
X-Gm-Message-State: AOAM532cUBH/6eOhyUn37cG3o98FxuqzmEknSe8qQb4xeIhlHEauLd/l ajw/+A0JlElIaNW95qDrLtB0PoWoX1R8aQ==
X-Google-Smtp-Source: ABdhPJyAyti+48lK1pUkPjoMKQ7n8eYRzbc5/NjG2gD8cSKPuQ0Z7w2P/b1WGokGUZ5Z5ZTCK8Fgfg==
X-Received: by 2002:a17:90a:f00f:: with SMTP id bt15mr1140885pjb.209.1609883890164;  Tue, 05 Jan 2021 13:58:10 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id x23sm170077pgk.14.2021.01.05.13.58.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 13:58:09 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com>
Date: Tue, 5 Jan 2021 13:58:08 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com>
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/13Rk7kIZe6dD7gu5KDcKPoQBLWs>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 21:58:12 -0000

On 1/5/21 1:49 PM, Dave Crocker wrote:
> On 1/5/2021 1:20 PM, Michael Thomas wrote:
>> On 1/5/21 1:18 PM, Dave Crocker wrote:
>>> On 1/5/2021 12:55 PM, Michael Thomas wrote:
>>>> It also says with actual data that your assertion that users can't 
>>>> be trusted for anything is not correct.
>>> I didn't say that.  And it didn't say that.
>> "Also, receiver filtering engines are all that matter." The word all 
>> includes human beings. That's the nature of "all".
>
> 1. In terms of average use for typical email, it is.
>
What study asserts that for email? You wouldn't take my word for it if I 
said that. But of course I wouldn't make a categorical statement without 
empirical evidence.

You really should read the paper. It's quite clever what they did, and 
provides a lot of interesting information to consider. It was very 
interesting to see what was happening in the wild instead of the 
conjecture that informs most of what goes on. They apparently have a 
follow on study they're working on.

Mike


From nobody Tue Jan  5 14:07:08 2021
Return-Path: <dcrocker@gmail.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 A95763A09B5 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 14:07:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 S2KsE_7aII-5 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 14:07:05 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 777443A0983 for <dmarc@ietf.org>; Tue,  5 Jan 2021 14:07:05 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id a188so525320pfa.11 for <dmarc@ietf.org>; Tue, 05 Jan 2021 14:07:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=qQtjjPf7o4pzeQGmw+mkJZ915EhUX+n5KSnT61Q5DIQ=; b=C+MvWiJdrynvfuqSfcpPiIwTlNeNkvfOH5mXViZlx6CUVrSxs8KQTa6oUZWMfNOoGi OR6ithSkUXpyxUXRCZ+uMFeaZwGscs1INDmGSy9uq0GFvPsb3BW6oqrJQcAP2rT4SCjA 5fh/ne6kumI3VsK04U+HxOOsjmS4y6tl0HW05G0KicdWijAe4GmTFjXQwy4uX3fBEaHY XPikx0B3K1JsHb46ojoM8kJLERZVBOkNf/9uAIEmvp/11F1X+/zdtYL2+/tVnRBzUtBi WWikFJefhufjv4jPkYPLV/T9CO0gSVDQBjfMzT7Nujdn9Bg6Dg+49PAaIzkmXR4xJaBR D9Sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=qQtjjPf7o4pzeQGmw+mkJZ915EhUX+n5KSnT61Q5DIQ=; b=t0RCbjmYXQOkpcSmWZtAs+hwNe6Gh4fgSa3IRWl0tJx6w8tSSC5tBHZZdxfknF9eOs BD2QS39lUp2F5tWuxmthVfoyataA4I0e2DCoXzaUrURFJrjfF6oG5+a49VBYsawPmtS/ Q7v6F+wJxEEcj58OyoYeaijisu45pLXNTHkYFecFBokk5FcvKEgX/Q1To8xAlmAyh3aU xTPudEZttZOfYsodJsMgbPmps5voH6Gs9Vg/nhy4yd9YzU1ywqyMfr+jZgBVQMqzB7MF eZ2gpmeFxn/1vNM5LiN2UcGiKW731WjuS1BmvZfyfCg1ULVqMHdjgvT6v7xiR8s0Qg5G 4SEg==
X-Gm-Message-State: AOAM5302laqStS0ZEWGfms9peH8pdMuWu6GIC4LILzNCYFjLLyeYuvVP VxfSVr0jps6Q4KnpE5IDZ6ib3mEIeV8=
X-Google-Smtp-Source: ABdhPJwjRaHfyeOKJnsyxc3g/oFsUHodxg6T49Vm0Wz7KJYfPIj3A+F5spAvEsYuZ7eJNHMRyYQ44A==
X-Received: by 2002:a65:434c:: with SMTP id k12mr1192723pgq.373.1609884423592;  Tue, 05 Jan 2021 14:07:03 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id y9sm183798pjt.37.2021.01.05.14.07.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 14:07:03 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com>
Date: Tue, 5 Jan 2021 14:07:01 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com>
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/r7unHaCXKKFeotbjU1pL-Jx4f_o>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 22:07:07 -0000

On 1/5/2021 1:58 PM, Michael Thomas wrote:
> On 1/5/21 1:49 PM, Dave Crocker wrote:
>> On 1/5/2021 1:20 PM, Michael Thomas wrote:
>>> On 1/5/21 1:18 PM, Dave Crocker wrote:
>>>> On 1/5/2021 12:55 PM, Michael Thomas wrote:
>>>>> It also says with actual data that your assertion that users can't 
>>>>> be trusted for anything is not correct.
>>>> I didn't say that.  And it didn't say that.
>>> "Also, receiver filtering engines are all that matter." The word all 
>>> includes human beings. That's the nature of "all".
>> 1. In terms of average use for typical email, it is.
> What study asserts that for email? You wouldn't take my word for it if 
> I said that. But of course I wouldn't make a categorical statement 
> without empirical evidence.

You seem to be seeing a requirement to prove the negative, while the 
actual requirement is to prove the positive.  A claim that there is 
meaningful efficacy, for average recipients, by having visual trust 
indicators, requires affirmative demonstration that there is.  There is 
no requirement to prove there isn't.  My point is that we have decades 
of belief that it's useful but no demonstration that it actually is.  
And we have history such as the EV effort, showing that it isn't.

Your focus on email, as somehow distinctive, would need some basis for 
ignoring the web experience.  Feel free to provide it.


> You really should read the paper.

Your implication that I haven't is both odd and troublesome.


d/

-- 

Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Tue Jan  5 14:19:46 2021
Return-Path: <mike@fresheez.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 C92563A09E0 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 14:19:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 5xdmPwvsv0aW for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 14:19:43 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 505133A08F9 for <dmarc@ietf.org>; Tue,  5 Jan 2021 14:19:43 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id d2so558806pfq.5 for <dmarc@ietf.org>; Tue, 05 Jan 2021 14:19:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=fYJMTHa9I9e6Mty2OEZaAkvmZXrpuzAtzX4Gk3MN/hQ=; b=KaG96XhkG+oA8iNMkdzBmmwhda3ewPmudqPlhNkjgbtrnq3M/i0TQrm+uEeFeIfZrG p74pvzYAVbJXwB29Uvel1KmIUBDoyG/SFVsWUKNxuOlilCmfX7nFUiTIaLrClEJm5YnN EaOQI8OJpp8BwTA/PTdRhjgZl8dnh/unXelMTFmkCRdGnphDJVmVUG4u+fzJy3//X1+Z ZW5zwZLsVdwdkKSGfqkbXlL5xsNC7IneSafwWj65EmVm83GXNyR8zRuDBP5SVok53V2v Ls8pR0yuZUrnpEAwL1JTHS7mJy+uuUk4vd90FidkpeocVatQIv5oYa/0ECtciNQBbkzY OK5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=fYJMTHa9I9e6Mty2OEZaAkvmZXrpuzAtzX4Gk3MN/hQ=; b=rLGfZpx/Kd2LgelJ5vLbH9mw/RWwQPAgtXDtCh2B3n7ZM9Zf0l8KfRaOZlfBEMAoka CnzIDfzIgo1yI9WTcJOBMSJ0JuncF1kLL0QK0SH6n1e2CVs7rf/ChkmNKYQoMihpExBN hucSWnJh3lsA5wUHrdxPS15eooSxiFZ6Pnkn/VEwGsSKzNrM8ND/I1qM1Efgv/vvqxS0 eNzS3IMBLsQcGy/d49uBt4j2DegNrqQHJeepDsj8FiVAv1eUZQWxEyeAvNcdTyvGZweu qapjQ4ViTak5oA5Y39VdVoJhTG6I1VjGW9LyFbNk3dQwAWwAzOYvjzPxjYeYUe91CQHL LDxQ==
X-Gm-Message-State: AOAM531bvavURs2wufIv8oT+NjwW+zxAekKbxtpzm9E80fqJXASHoX5E M4RNvgHjNRV1odCkx6Ib4XXLEEJY2eLEsw==
X-Google-Smtp-Source: ABdhPJwnqLO9p6HdV+Udz3s7Oe9GDFKvqkwVdGqh9CAldrt9+nqIFT/ps1eGFDh6qDhYyM2dxKd+ag==
X-Received: by 2002:a62:6d06:0:b029:1a8:4d3f:947a with SMTP id i6-20020a626d060000b02901a84d3f947amr1058451pfc.6.1609885182263;  Tue, 05 Jan 2021 14:19:42 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id d133sm347633pfd.6.2021.01.05.14.19.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 14:19:41 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com> <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com>
Date: Tue, 5 Jan 2021 14:19:40 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com>
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/0POiyISYS9MaS38zhgPiHPMIDUA>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 22:19:45 -0000

On 1/5/21 2:07 PM, Dave Crocker wrote:
> On 1/5/2021 1:58 PM, Michael Thomas wrote:
>> On 1/5/21 1:49 PM, Dave Crocker wrote:
>>> On 1/5/2021 1:20 PM, Michael Thomas wrote:
>>>> On 1/5/21 1:18 PM, Dave Crocker wrote:
>>>>> On 1/5/2021 12:55 PM, Michael Thomas wrote:
>>>>>> It also says with actual data that your assertion that users 
>>>>>> can't be trusted for anything is not correct.
>>>>> I didn't say that.  And it didn't say that.
>>>> "Also, receiver filtering engines are all that matter." The word 
>>>> all includes human beings. That's the nature of "all".
>>> 1. In terms of average use for typical email, it is.
>> What study asserts that for email? You wouldn't take my word for it 
>> if I said that. But of course I wouldn't make a categorical statement 
>> without empirical evidence.
>
> You seem to be seeing a requirement to prove the negative, while the 
> actual requirement is to prove the positive.  A claim that there is 
> meaningful efficacy, for average recipients, by having visual trust 
> indicators, requires affirmative demonstration that there is.  There 
> is no requirement to prove there isn't.  My point is that we have 
> decades of belief that it's useful but no demonstration that it 
> actually is.  And we have history such as the EV effort, showing that 
> it isn't.
>
> Your focus on email, as somehow distinctive, would need some basis for 
> ignoring the web experience.  Feel free to provide it.

Your example of web is fraught because web stuff has had visual 
indicators for decades now, and trying to compare EV certs isn't 
especially a good example because the situations are not the same. At 
least this study is directly relevant and it doesn't support your 
categorical statement. This is actually a Good Thing.

I did provide it with that paper. You seem to be dismissing it out of 
hand in favor of something that isn't even email based. We are here 
because of email, so I think that's pretty relevant.

>
>> You really should read the paper.
>
> Your implication that I haven't is both odd and troublesome.
>
In 15 minutes? It's like 30 pages long and very technical. And you're 
asking me whether I read it closely? If you have read it before, just 
say that. If you haven't you can skip to the part that doesn't support 
your categorical statement.

Mike


From nobody Tue Jan  5 14:43:38 2021
Return-Path: <dcrocker@gmail.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 259E43A093D for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 14:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FiivB0hHm72N for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 14:43:35 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D1373A044E for <dmarc@ietf.org>; Tue,  5 Jan 2021 14:43:35 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id lj6so536149pjb.0 for <dmarc@ietf.org>; Tue, 05 Jan 2021 14:43:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=fxJooz9oQnQ/5sSg06fD4xHn1RxlWyNlMzvSBR7Mj8Q=; b=rPBBGubdyYqe9oZFLH5qJeNOt3UmUlgZHQyH+mZ9Ra5wbbhuLYUmcm8b2vpTplXPBI W/sPyLFnAfYPoo400Tk7PSbKbGz01xvwe5YOYzjp9BR+b3xSC7A9Sb2pUiXqqVkkLueG Xhe5065aByRBS9PvsGqkYws68U1bEUz87seig/q3rCLyUeWBEwHcC8c9d4vfuBgDxq3f 1xUoGNsZZRNruPP3TlV0+fUbrh1yLVS48jVbfXdCQB8UcXVLT8UHOm1ce6PvuviVVTHz VM++sU0HVF8moO75Edgc7Si4KSPsvobVWgiDay0sJSYBJLvNpLQ7KMA64+1aq9m08W0j WF9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=fxJooz9oQnQ/5sSg06fD4xHn1RxlWyNlMzvSBR7Mj8Q=; b=lkfDD6lgy0MrR+Aw1DQMDG8VPlMH/SP9wwcK0nwnPXQ+mvUU47yLUY+jZMGdjH/DTH ttdUvBGVNzdyQhx+GIwmijUpzwMck9mX6sV/7m7OxhmTBKecxbpUNHnahC8gXuv83wFS h+qKVaFyUcHD1PRf/tKKx9j0XmiNMoc6gag2ekhMZJ4IlSNmWw53cVE822ryduyVO3sT PyaxYgNxGeMeHoLEkGaAeJnOtPdF+zmRcL8Q8dqOj0VoTu8Z5fgJPtIORpnReoLDG88B htBYUzNVvAOAR83e1C7kqZ+oY4cNoNpEpjOvs6aWtgPc4O8qp29XJ5SxxwhjqMxQFLRY v11g==
X-Gm-Message-State: AOAM531v/8JcOVjFh2EOALuHeKaelBOclzbGo5/2aFDlE5BuKUQb5WyU i1yuWTcuTRPm1dEgMw9w48QeL1NjQ7s=
X-Google-Smtp-Source: ABdhPJzxpbSP2MmrMn48E/lJ5I+Gfy8J34C9BWze9i8GDD1Tjtr3HI9b2OeHdc3oqJKFRSWSIMnmoA==
X-Received: by 2002:a17:902:8307:b029:dc:8ac6:c4f8 with SMTP id bd7-20020a1709028307b02900dc8ac6c4f8mr1328599plb.79.1609886614401;  Tue, 05 Jan 2021 14:43:34 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id z23sm376309pfj.143.2021.01.05.14.43.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 14:43:33 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com> <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com> <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com>
Date: Tue, 5 Jan 2021 14:43:32 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com>
Content-Type: multipart/alternative; boundary="------------7E531BC3E45EB6AD95BF5E49"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/l2qDt8Bamy3d1OaRkzm4tHPySzo>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 22:43:37 -0000

This is a multi-part message in MIME format.
--------------7E531BC3E45EB6AD95BF5E49
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


>> Your focus on email, as somehow distinctive, would need some basis 
>> for ignoring the web experience.  Feel free to provide it.
> Your example of web is fraught because web stuff has had visual 
> indicators for decades now, and trying to compare EV certs isn't 
> especially a good example because the situations are not the same. At 
> least this study is directly relevant and it doesn't support your 
> categorical statement. This is actually a Good Thing.

Oh?  A trust indicator to a user, flagging a domain name, isn't pretty 
much the same?  Please explain.


> At least this study is directly relevant and it doesn't support your 
> categorical statement. This is actually a Good Thing.

It is largely unrelated to my observation about efficacy of trust 
indicators for average users..


> I did provide it with that paper. You seem to be dismissing it out of 
> hand in favor of something that isn't even email based. We are here 
> because of email, so I think that's pretty relevant.

Except that I didn't 'dismiss' it, out of hand or otherwise.


>>> You really should read the paper.
>> Your implication that I haven't is both odd and troublesome.
> In 15 minutes? It's like 30 pages long and very technical. And you're 
> asking me whether I read it closely? If you have read it before, just 
> say that. If you haven't you can skip to the part that doesn't support 
> your categorical statement.

sigh.


d/


-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


--------------7E531BC3E45EB6AD95BF5E49
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <br>
    <blockquote type="cite"
      cite="mid:215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com">
      <blockquote type="cite" style="color: #0000a0;">Your focus on
        email, as somehow distinctive, would need some basis for
        ignoring the web experience.  Feel free to provide it.
        <br>
      </blockquote>
      Your example of web is fraught because web stuff has had visual
      indicators for decades now, and trying to compare EV certs isn't
      especially a good example because the situations are not the same.
      At least this study is directly relevant and it doesn't support
      your categorical statement. This is actually a Good Thing. <br>
    </blockquote>
    <p>Oh?  A trust indicator to a user, flagging a domain name, isn't
      pretty much the same?  Please explain.</p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com"> At least
      this study is directly relevant and it doesn't support your
      categorical statement. This is actually a Good Thing.
      <br>
    </blockquote>
    <p>It is largely unrelated to my observation about efficacy of trust
      indicators for average users..</p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com">
      I did provide it with that paper. You seem to be dismissing it out
      of hand in favor of something that isn't even email based. We are
      here because of email, so I think that's pretty relevant.
      <br>
    </blockquote>
    <p>Except that I didn't 'dismiss' it, out of hand or otherwise.  <br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com">
      <blockquote type="cite">
        <blockquote type="cite">You really should read the paper.
          <br>
        </blockquote>
        Your implication that I haven't is both odd and troublesome.
        <br>
      </blockquote>
      In 15 minutes? It's like 30 pages long and very technical. And
      you're asking me whether I read it closely? If you have read it
      before, just say that. If you haven't you can skip to the part
      that doesn't support your categorical statement.
      <br>
    </blockquote>
    <p>sigh.</p>
    <p><br>
    </p>
    <p>d/<br>
    </p>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Dave Crocker
<a class="moz-txt-link-abbreviated" href="mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------7E531BC3E45EB6AD95BF5E49--


From nobody Tue Jan  5 14:57:27 2021
Return-Path: <mike@fresheez.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 4B0663A0E72 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 14:57:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 nQookNSAqfjE for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 14:57:18 -0800 (PST)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 864AB3A0C6C for <dmarc@ietf.org>; Tue,  5 Jan 2021 14:57:17 -0800 (PST)
Received: by mail-pj1-x102e.google.com with SMTP id lj6so555355pjb.0 for <dmarc@ietf.org>; Tue, 05 Jan 2021 14:57:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=k9/t2To/A+0BWhB2jVGdXXa79T4tYAjlg8e2LgLuxbY=; b=a91tSvinlmDpoXvQpmigmss+dW76PthmIZsW81N2Wql8CCAsbQRLtkYWwC6dyCO3jC nFM88AiJVXhwnbdMvZ6Um6699QF3zL+QZ6pU5KwLQqa8i5Q1ux12lSkv+awCV8nikO6p GCS63Uc3cGDgsRKy0xY+uAY+V3p42XydiyD7csdVhFQYdstr8QNSmLqGN0LXNS80grlb dCDrTnSQFsVtreqiVlNalrMsYqpBmIvgBk81jm54YYpPIcqEYkwBJ7z7170de/VnYPEF KZByNxdeT7h2w4VNMNNVeccZa7pqHBMiuzZDInYposG/8rS9M4EOl45HdB3BrJgfIkY7 1TfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=k9/t2To/A+0BWhB2jVGdXXa79T4tYAjlg8e2LgLuxbY=; b=LiPxoTz2VnfEwxtwar3O/TCRWR8rK5xa7szIulk7c9jiTmxU3YwDswriNB2ACIxm9o S0s5u29t5Th5JFSxfDENcmqivg8jLNYdq4K5ZIIWj/ig7t7OZzKO2XQ3C9WcnXUAJ6fX U5lNUrQAb2o+0GyPC8fMKx2UU0e//g11dfn28p0gqcFDZFaD5W5HdrSDtMP/Ud9+NP7L 6+Kb9Qp3jOg8THOtajLEawHOYnKXAVp4oYSF5Uyp/F9hGrPXFBGhDVMPIk29hiXrRIKA fEoDqJpjTdRiO4dzJCnly5+jzxuvPJhLovH/dvBOPZC2zxmTyhXdDTcCrJA4Rku5PHym UrwA==
X-Gm-Message-State: AOAM533KipkrYwM4+bI0sh+Eu4qw6apCNO61bZuQ0bXHVjjNm8XsY0ED KTJ0vEzKSd8EfJmoRrXSbxFc7q0PvnlGd2L7
X-Google-Smtp-Source: ABdhPJxcD6iYpDr4JOITBlK4uxkd2pqiJmhaU8z2GEH+EzouNfKfMhH/1OGHZTVvSQvK6hKpoZHL9A==
X-Received: by 2002:a17:90b:1918:: with SMTP id mp24mr1305862pjb.45.1609887436531;  Tue, 05 Jan 2021 14:57:16 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id a141sm359142pfa.189.2021.01.05.14.57.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 14:57:15 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com> <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com> <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com> <fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <b3d77e5a-8024-218f-cd3c-6286f9ecd7dc@mtcc.com>
Date: Tue, 5 Jan 2021 14:57:14 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com>
Content-Type: multipart/alternative; boundary="------------6701ED76567500E448918EFC"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/EBbYOdvETITtr-umYxoT-CwrLuA>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 22:57:25 -0000

This is a multi-part message in MIME format.
--------------6701ED76567500E448918EFC
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/5/21 2:43 PM, Dave Crocker wrote:
>
>>> Your focus on email, as somehow distinctive, would need some basis 
>>> for ignoring the web experience.  Feel free to provide it.
>> Your example of web is fraught because web stuff has had visual 
>> indicators for decades now, and trying to compare EV certs isn't 
>> especially a good example because the situations are not the same. At 
>> least this study is directly relevant and it doesn't support your 
>> categorical statement. This is actually a Good Thing.
>
> Oh?  A trust indicator to a user, flagging a domain name, isn't pretty 
> much the same?  Please explain.
>
Pretty much != same. The study was directly about email. If you read it, 
the authors were also skeptical about the efficacy. It sounds like you 
have an issue with the study, not me. Maybe you should take it up with 
them and we can be done. In the mean time, I'll take hard data over your 
speculation.

Mike


--------------6701ED76567500E448918EFC
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/5/21 2:43 PM, Dave Crocker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <br>
      <blockquote type="cite"
        cite="mid:215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com">
        <blockquote type="cite" style="color: #0000a0;">Your focus on
          email, as somehow distinctive, would need some basis for
          ignoring the web experience.  Feel free to provide it. <br>
        </blockquote>
        Your example of web is fraught because web stuff has had visual
        indicators for decades now, and trying to compare EV certs isn't
        especially a good example because the situations are not the
        same. At least this study is directly relevant and it doesn't
        support your categorical statement. This is actually a Good
        Thing. <br>
      </blockquote>
      <p>Oh?  A trust indicator to a user, flagging a domain name, isn't
        pretty much the same?  Please explain.</p>
    </blockquote>
    <p>Pretty much != same. The study was directly about email. If you
      read it, the authors were also skeptical about the efficacy. It
      sounds like you have an issue with the study, not me. Maybe you
      should take it up with them and we can be done. In the mean time,
      I'll take hard data over your speculation.<br>
    </p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------6701ED76567500E448918EFC--


From nobody Tue Jan  5 15:44:17 2021
Return-Path: <dcrocker@gmail.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 1A32A3A0E96 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 15:44:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 eQsPcOik0pvC for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 15:44:14 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC6EE3A0E94 for <dmarc@ietf.org>; Tue,  5 Jan 2021 15:44:14 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id b5so630625pjl.0 for <dmarc@ietf.org>; Tue, 05 Jan 2021 15:44:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=gLYfMhW9Y9dSo3sZpyjOCCFRBuv2pMyk7yVPPn23mII=; b=k93YKKp6+wSmlDa26LC5ShkKoPwFymVzyQjdTQknqxSjTOZzyFFLBpg/On/aIgVEQ1 GJwqlKrfbPXM7rzrqhxOj7s7SzoZa8yiEEljPZbLBgwam96wfGqUhptT2jduP6nK2eFo s5h88Y6KPBzXLCsD/wd93DrWQ3ki+qTDt3i9kwNOstZIRDxHScx0el88Zr6nviqYy2x4 U+ZhsiMwUr8mXhl68RUlEmgQbEuh0ftULRl9Wk79tvSlSRrNFI6Dw3ItTI36k/U0cnkb anixIGI/iAv3M30papckUismULAW+KPWCmJ10EnSSX+iDkizcxXXIBlMEdfasA3PDJIJ Sokw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=gLYfMhW9Y9dSo3sZpyjOCCFRBuv2pMyk7yVPPn23mII=; b=o7r5pclIMn5+UBdifmpg/AH35LePMv/dtaw7g+/0rGDR0bHksUP4ry9YL8u+ucubg8 2JngEGhznvtccMuFQQbhZfRN6WDLWC/fwzFgRDtsgTjpVsZXtYw62PZFQvaqMO0wvmOB 4ymYyWz9oibQkyvoAtgYFdy2Lq/ZlqpVzjlXOit10U7H6TLQl1ToFgCu6WDL7QdPPwBj QT5/DCbYI3Sr3vwHoKthrZpaEKlixhm9hp3V82DIv2lwl7RWpfLaqHkuhAgpvIpAepCY AQXdYj1CcB8G63GLt6kZ4byWNVR6XC3LMMwWJ10rSHjEFrSJ0d/8XpiI+ISp1+Px5Nx8 q0Eg==
X-Gm-Message-State: AOAM533disjFf+8AAHqsY6W8JPbGBsZ4Zv3jIVj2375tN1koJOXu+nB3 K9TA3/DlIje3USqhwTriteIPCa4bXAw=
X-Google-Smtp-Source: ABdhPJxeCKAkaKLzoEO+mtcg3M+U+gB0Y1oGD75Wv/WtjI8xxOwTViLpnTIr85x3FI/PBWCQW2uTxA==
X-Received: by 2002:a17:90a:d18c:: with SMTP id fu12mr1433399pjb.153.1609890254058;  Tue, 05 Jan 2021 15:44:14 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id s21sm278989pga.12.2021.01.05.15.44.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 15:44:13 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com> <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com> <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com> <fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com> <b3d77e5a-8024-218f-cd3c-6286f9ecd7dc@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <a7e6944a-363c-9d40-9cd9-1fe640ea6cfb@gmail.com>
Date: Tue, 5 Jan 2021 15:44:12 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <b3d77e5a-8024-218f-cd3c-6286f9ecd7dc@mtcc.com>
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/kMEBqp0fxLsTjSQQMrdbxPZl6P0>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 23:44:16 -0000

On 1/5/2021 2:57 PM, Michael Thomas wrote:
>>
>> Oh?  A trust indicator to a user, flagging a domain name, isn't 
>> pretty much the same?  Please explain.
>>
> Pretty much != same.
>
A trust indicator, to a user, flagging a domain name. Essentially the 
same user-oriented mechanism. Web vs. email.  Why and how does that make 
a difference?

The extensive experience with the web EV experiment has been that it 
does NOT make a difference.  Since you seem to dismiss this web 
experience, please explain why it is not relevant to the current topic.


> The study was directly about email. If you read it, the authors were 
> also skeptical about the efficacy.
>
Exactly.  Thank you for noting that.  But, then, it raises the question 
of why you cited it as demonstrating meaningful efficacy for signalling 
DMARC results to end users?


d/

-- 

Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Tue Jan  5 15:50:49 2021
Return-Path: <mike@fresheez.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 A8DBB3A0EA7 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 15:50:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 L6OTDp4ps0OY for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 15:50:47 -0800 (PST)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5310E3A0EA4 for <dmarc@ietf.org>; Tue,  5 Jan 2021 15:50:47 -0800 (PST)
Received: by mail-pf1-x429.google.com with SMTP id m6so664713pfm.6 for <dmarc@ietf.org>; Tue, 05 Jan 2021 15:50:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=yY5HSSyXfj+o2HxnhAHxJ5llP6LyKp9ph+qPZ6Lsby4=; b=Nb9Tk3VGzxwnIFzLkALwwDzDulCxsN+RyhFAOfHYEP7x7kdHGUOH66A7xgEC1SG6gh ku3zk5aQHX7BUoxILeilMifmMBNMC7voWjv8NctET+c3rFeWexXdRdzIvQavqSeGthId DDdMyjCHEWJnqyMHFFrxQj4sIEnql93Slegvu5gOEfxaaFgORhV9P6z5QfhKakAfU9Uu YCXAKYVch/+yo3Zm24XKeDx8iRpBGlq5srY7Ev0K4mAaat7u/CrNAXF9agQ6JN8OyWaS YNeBiD9SCifn1u29t3WRU/cWdximpcg+26b/rLom2KRWsiztoZhPxrJ7JN0cQFJLwhaT 8DFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=yY5HSSyXfj+o2HxnhAHxJ5llP6LyKp9ph+qPZ6Lsby4=; b=imScQtvPXPv12R8u3/3WVOpwp65YQuLami2LJmfPAz9ZRaSSw2V7j3LiIeIVh81Om0 EhIzvUNrLGG8yJrUodLR/SNGZ7ZzuhrA/0Y4i2C5AEDpS4faYrLvf0pKkM6Oigqjma2y 3qqwgwTVOHN89Aw/MkMA7q5KUG2mUIALbqX+12T0JbfHtur779yYsNiQ4/piaZestC3v ALCv0DaFBlyXnFVcA8rrgDXmxTez8QnBKFRj7ONPOP8nrJD0yPZkllj6KirLEExncQEd CrTSNkuNEppSY4bORc3jP/H5loj4WT9wAAnDpROOU3Frk+As8BmK8F5kgx88iwGYFRiz EvDw==
X-Gm-Message-State: AOAM530YDmY7uA67BRM/s5rxVfCNaEWx/A0bB6RYszXS994P7E84x3Dr acIdrPlyVHp6l8LZmpompTHeWnOvE+cpEI+D
X-Google-Smtp-Source: ABdhPJx4YbpF0EBJYGNk9kUo+YrRdbWbwPixAxYrErbUbsfsR9YxCQIN4CqI9ngYkDLvO3QXDrU30Q==
X-Received: by 2002:a65:6409:: with SMTP id a9mr1511460pgv.171.1609890646150;  Tue, 05 Jan 2021 15:50:46 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id k18sm310035pjz.26.2021.01.05.15.50.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 15:50:45 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com> <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com> <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com> <fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com> <b3d77e5a-8024-218f-cd3c-6286f9ecd7dc@mtcc.com> <a7e6944a-363c-9d40-9cd9-1fe640ea6cfb@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <e509cd25-19f9-ae75-ba62-30173af6857b@mtcc.com>
Date: Tue, 5 Jan 2021 15:50:44 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <a7e6944a-363c-9d40-9cd9-1fe640ea6cfb@gmail.com>
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/43R-UIuFbqTUuNZPispiFxiuoP4>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 23:50:49 -0000

On 1/5/21 3:44 PM, Dave Crocker wrote:
> On 1/5/2021 2:57 PM, Michael Thomas wrote:
>>>
>>> Oh?  A trust indicator to a user, flagging a domain name, isn't 
>>> pretty much the same?  Please explain.
>>>
>> Pretty much != same.
>>
> A trust indicator, to a user, flagging a domain name. Essentially the 
> same user-oriented mechanism. Web vs. email.  Why and how does that 
> make a difference?
>
> The extensive experience with the web EV experiment has been that it 
> does NOT make a difference.  Since you seem to dismiss this web 
> experience, please explain why it is not relevant to the current topic.

I'm dismissing nothing. That is a strawman. I already said why its 
problematic to compare the two which apparently you did dismissing and 
why it's preferable to have an apples-apples comparison.

>> The study was directly about email. If you read it, the authors were 
>> also skeptical about the efficacy.
>>
> Exactly.  Thank you for noting that.  But, then, it raises the 
> question of why you cited it as demonstrating meaningful efficacy for 
> signalling DMARC results to end users?
>
Quit cutting out needed context to make your points. The study directly 
contradicts your categorical statement. Your issue is with the study's 
authors not me. Quit shooting the messenger.

Mike, this is just silly. and typical. I'm done.


From nobody Tue Jan  5 15:55:45 2021
Return-Path: <dcrocker@gmail.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 4DEB13A0EBD for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 15:55:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ZJ6WWzZyPQaP for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 15:55:43 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23F493A0EBC for <dmarc@ietf.org>; Tue,  5 Jan 2021 15:55:43 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id p18so938272pgm.11 for <dmarc@ietf.org>; Tue, 05 Jan 2021 15:55:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=BPLV+7tRmTrrS8jbmGbvA3nFlUJInGlJIcWRMSH1hfc=; b=OxoJFJi+pswWSLqhQQokX/6Lef7D2g+62I/q28QyfAte/NziAnzpC/5kpPXT+JtlcH KUasxzLQbJkdrA/aSed1KQQUo6H+CKCx8m2DhI3XDmx+ol0HfeB4YaYErblpviKULtj/ lkm7nR4U3iBX5a4QnO4Yo4bhLXw/FoD8GrGrz1Putxcxj2sczdfUHYQIsfWfN2c4s37h /NgzYh0gQ8FZ3zHmFOtjhcUT6PwPBtWH1KDEMW9cD76fAPansMttwIJ17+4kJdBwf836 uNPICnW2aslUUlUY4QauwYS0TuCv1FcKWSYK2zqjC2VUCqwtMdPH0Pt61IsRVzxuJhvn t2Xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=BPLV+7tRmTrrS8jbmGbvA3nFlUJInGlJIcWRMSH1hfc=; b=kjZW+O1wBN4sYYmf4mxIYabj2LbYBlrBuplyJwTjuq14e89HnkuQDBVUYfQ00S5X0X HdUG1U41hH16v8j93UvRzqFMLFw9yJJ/BPRo7peCMXgSM8bBrtQt9Ze6oel6Bem7noTg Q4i9jZlMp6YCnhgO9eEavI+a7zE1rQElDAdhKcLi0P17AlvHsp85ALnuLAipEvx7cCQV 3AlyQvPeWB/HggbQcYid0fFYWcDK3uJY/hlxp/fgDRT//5PooLhjKkcUv4QGZYl04F9l wjQg6tDFBeW7pT7TmhnD66v+O/DW9jndps3nG/kCOQW0nmDCJ2cJ2TUvoMipPvJge3G0 bywg==
X-Gm-Message-State: AOAM532rZecsjIlagQNy87YEaz+g2WKp5fblMX2lL8DimDdLfhR3m10g 5lIk3un8c9UKFq+7/9gjoS/xJZBqDnE=
X-Google-Smtp-Source: ABdhPJyaRJKlqfNOt/vm3T7nGEJtEqqf6aOgqG+6RIIdS/Jhj0eEM34GLZvH+wnqXwX8/1nlzClC9w==
X-Received: by 2002:a62:4d03:0:b029:1ac:6159:4572 with SMTP id a3-20020a624d030000b02901ac61594572mr1306429pfb.10.1609890942495;  Tue, 05 Jan 2021 15:55:42 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id w131sm442880pfc.46.2021.01.05.15.55.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 15:55:41 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com> <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com> <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com> <fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com> <b3d77e5a-8024-218f-cd3c-6286f9ecd7dc@mtcc.com> <a7e6944a-363c-9d40-9cd9-1fe640ea6cfb@gmail.com> <e509cd25-19f9-ae75-ba62-30173af6857b@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <aee386fe-54ee-a01c-bd0c-80eb940ca185@gmail.com>
Date: Tue, 5 Jan 2021 15:55:41 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <e509cd25-19f9-ae75-ba62-30173af6857b@mtcc.com>
Content-Type: multipart/alternative; boundary="------------B78275608167084E2596DBDB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/33n4uzVCFPJHp5QMDejTCLK5-20>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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, 05 Jan 2021 23:55:44 -0000

This is a multi-part message in MIME format.
--------------B78275608167084E2596DBDB
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 1/5/2021 3:50 PM, Michael Thomas wrote:
>>
> Quit cutting out needed context to make your points. The study 
> directly contradicts your categorical statement.

Except that it doesn't.

  Feel free to provide an serious explanation of why you think 
otherwise, but please put some effort into accurately representing what 
I said or what the study shows.  Attention to detail will help.  
Conclusions are less important than showing your work.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


--------------B78275608167084E2596DBDB
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/5/2021 3:50 PM, Michael Thomas
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:e509cd25-19f9-ae75-ba62-30173af6857b@mtcc.com">
      <blockquote type="cite" style="color: #0000a0;"><br>
      </blockquote>
      Quit cutting out needed context to make your points. The study
      directly contradicts your categorical statement.</blockquote>
    <p>Except that it doesn't.</p>
    <p> Feel free to provide an serious explanation of why you think
      otherwise, but please put some effort into accurately representing
      what I said or what the study shows.  Attention to detail will
      help.  Conclusions are less important than showing your work.<br>
    </p>
    <p>d/<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Dave Crocker
<a class="moz-txt-link-abbreviated" href="mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------B78275608167084E2596DBDB--


From nobody Tue Jan  5 17:11:30 2021
Return-Path: <dougfoster.emailstandards@gmail.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 1EA5B3A1078 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 17:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 m9BWnSKAOynv for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 17:11:26 -0800 (PST)
Received: from mail-ua1-x936.google.com (mail-ua1-x936.google.com [IPv6:2607:f8b0:4864:20::936]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A9BE3A1075 for <dmarc@ietf.org>; Tue,  5 Jan 2021 17:11:26 -0800 (PST)
Received: by mail-ua1-x936.google.com with SMTP id t15so567228ual.6 for <dmarc@ietf.org>; Tue, 05 Jan 2021 17:11:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9PsUPPFFsEdtmhQWfYy1ttufJ5xWJd7hx2q7roNCDaE=; b=kR0CGauSgVNIzlVOOH5Nmd7IzFhLc1gigva7rmE2c844334lMdC4kHnd1i/zCYbL4h 0tFBVRFr9+8wn9Bl51w5eYO1DW+LUROFkKuTxhYj47yCTp8AELHsD8sVrfIFNddWrKog ZyBQE/+3JQbDhcqhgs+AGRuFn/z3NYwcwMwlkn9F0d4sGtuu17m0IC4v0i7pAb5W3dog FrKrFgEdsyABrEzNjaLRKZegOPSSfMWwKoPoVh+0qIkI4YDo8VIn7Bs4yAmyd2H9JYBg q9U3p/JBuRUWs7N9Twa0MnVoFLiI71AhEid4jdT5VjpOMWmd4K4UYIlBKUXe/66iPebM tDkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9PsUPPFFsEdtmhQWfYy1ttufJ5xWJd7hx2q7roNCDaE=; b=ttbqUL+0C9lbip3zi95fQp+21x6ljX4W2qmEROWhWGIhenN23BQfD7Nz2AxenDyO23 1nxIgZimzvX13UQFnIk+J/OwlQR/KpxaFEaek7axML8rGuowL/oCVGlNVpXaqPClfCdB jQdDVuU3eHq7Yi3x6HWeC+LHYO6nd2jcws4UzYTjgmTnuuAW+8bOnALDlnJhqyRPgd/Z ghRqAMuPZ4WpxDnnqel4OzgLjVrhj/tFuZR74fmvnUm2Rriol34T2gRUOraGFgr4ucfZ aKk/6IyvJztzRyZy5Zl1Ppq5exJBc2YT5pg/PvGLvPkckLVe942GiOKd3Pf9km7o7Re/ PMBA==
X-Gm-Message-State: AOAM533BoYDcbc2MO38EATtkDd2doMWqg5NL1QGA3Wl7viO0S2FVQ0pz E7khoUYrNhqRFOzjiXtfvC0L6N4kRCcOrEFLEGQ=
X-Google-Smtp-Source: ABdhPJzpXpo3iYOMnWLajBmXvlQUheT5b4ggsXGnEtOiGb5UlqfuD+NlHBD5pnySk5L+TCyM7eVIIZvkOw9dsbRFNIA=
X-Received: by 2002:ab0:770d:: with SMTP id z13mr714275uaq.110.1609895485719;  Tue, 05 Jan 2021 17:11:25 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com>
In-Reply-To: <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 5 Jan 2021 20:11:14 -0500
Message-ID: <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: Michael Thomas <mike@mtcc.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008d478005b83100d0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-5I_PWq9a8Z66n6AI34h2Imknyc>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 01:11:28 -0000

--0000000000008d478005b83100d0
Content-Type: text/plain; charset="UTF-8"

Sorry that my name was dragged into this.   The study in question was one
provided by Laura Atkins several months ago.   I forwarded it to Michael to
bring him up to speed.   To date, it is the only study submitted to this
group.  I was not trying to introduce new information or re-ignite this
fight.  The chairs and our charter call for us to proceed with DMARC as a
tool to control misuse of the From address, which is also what I want.

To that end, we want to make sender, intermediary, and forwarder interests
converge as much as possible.    Our strategy is for intermediaries to
provide sufficient information for an evaluator to fairly judge whether a
particular message is in his interests or contrary to them.   By my
analysis, we are not there yet.

The particular information that I seek to achieve this result is the
following:
(a) know whether forwarding action(s) have occurred during transit
(b) reconstruct the message identity state prior to the forward(s), so I
can evaluate the message based on both the intermediate and final message
states.

I cannot reconstruct prior state using most ARC sets, because ARC only
provides an identifier if that identifier was evaluated.  Even then, some
of the identifiers are provided in comments or not at all.   Evaluating the
message based on its prior state requires a complete set of identifiers.

DF

--0000000000008d478005b83100d0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sorry that my name was dragged into this.=C2=A0 =C2=A0The =
study in question was one=C2=A0 provided by Laura Atkins several months ago=
.=C2=A0 =C2=A0I forwarded it to Michael to bring him up to speed.=C2=A0 =C2=
=A0To date, it is the only study submitted to this group.=C2=A0 I was not t=
rying to introduce new information or re-ignite this fight.=C2=A0 The chair=
s and our charter call for us to proceed with DMARC as a tool to control mi=
suse of the From address, which is also what I want.<div><br></div><div>To =
that end, we want to make sender, intermediary, and forwarder interests con=
verge as much as possible.=C2=A0 =C2=A0 Our strategy is for intermediaries =
to provide sufficient information=C2=A0for an evaluator to fairly judge whe=
ther a particular message is in his interests or contrary to them.=C2=A0 =
=C2=A0By my analysis, we are not there yet.</div><div><br></div><div>The pa=
rticular=C2=A0information that I seek to achieve=C2=A0this result is the fo=
llowing:</div><div>(a) know whether forwarding action(s) have occurred duri=
ng transit</div><div>(b) reconstruct=C2=A0the message identity state prior =
to the forward(s), so I can evaluate the message=C2=A0based on both the int=
ermediate and final message states.<br><div><br></div><div>I cannot reconst=
ruct prior state using most ARC sets, because ARC only provides an identifi=
er if that identifier was evaluated.=C2=A0 Even then, some of the identifie=
rs are provided in comments or not at all.=C2=A0 =C2=A0Evaluating the messa=
ge based on its prior state requires a complete set of identifiers.</div><d=
iv><br></div><div>DF</div></div></div>

--0000000000008d478005b83100d0--


From nobody Tue Jan  5 17:19:40 2021
Return-Path: <mike@fresheez.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 9C5C23A108E for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 17:19:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 Iw6mXGS8Ytxv for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 17:19:37 -0800 (PST)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88C213A1076 for <dmarc@ietf.org>; Tue,  5 Jan 2021 17:19:37 -0800 (PST)
Received: by mail-pf1-x432.google.com with SMTP id m6so775169pfm.6 for <dmarc@ietf.org>; Tue, 05 Jan 2021 17:19:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=pZt6KDJdhgkLviLH/YElBuV2IQXLulZA2G71oaxoh28=; b=OP2enINpLFV2f7E3QqXV3ujo4auMaU/dD2GXqxWvkJDDQRL6oZBKKtCgXcFzcTMMje kkkMz+UI0ZbLQQVXBGDUSiHlC9yXc8kFb2sQbzQ2ZrYATlDENTSZgrNx64mCM7pJTvAS yfTfRvLZfxv4SJi4i+o+rtCtcKGqaSGxKLnABL8emtdoCDOtxkF6+PQ3zCFT8qI2ei8q onLf60uXPLwl8DJqgm8+yqGPpCJGNDNUhvCjID9IrPILJ1febTCetBYRxJ14St3aQCca 0dvb6Dnnm0Oc2ihFun2E/wn04vUYKpX8iL8rfKna1xDwAC31JoUaWTxA+uliz6JCtU8v pghw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=pZt6KDJdhgkLviLH/YElBuV2IQXLulZA2G71oaxoh28=; b=QXAH9Q08Av4WUrB+hHLDwuZ6FLAp1q6X0NhjYlz36uSs9Ni4OIFX3NhWKGffaVOZ9C MLWztLtXS/7m707D40c6q3E3RxScdgAc97aUd8WQf+esbvHrngCoG0pUtO0QnqxZNWFD i0zC9k3LXjqegCleVuLb/ZSnPFlKTfVnbzrMemKzB3hfQy8tvE8Y1TAwVsrA4lCcpL22 EJke1sTdoOeuIEttDt/E+Z5pquzdVRLPPLXNUOyYOJ7TKnGwzd7P3cifZ55TKRqQlugX ja/mEDT34KkA1byzc2bHuxl+lY0StGeTc2eX7j1tgXtZFseQ1q8uD0CGYt3Tfrtb5bdj AlHQ==
X-Gm-Message-State: AOAM530HHbumo44UtoSBLbT165PLM2WtF7OiOxQ6VPJf3O8BA0uXYKVr m3IXH4B58ROjl866QN5CkTbedLn4zg6NhQfD
X-Google-Smtp-Source: ABdhPJy60+MoHM+kzQ2vY4dfSJqYIBAMvVIOBbWEGWmGi79CNE/3NZvNAI5qEI4f0S/UjqXqK9xFZg==
X-Received: by 2002:aa7:8f35:0:b029:19b:1258:ec5d with SMTP id y21-20020aa78f350000b029019b1258ec5dmr1547845pfr.9.1609895976594;  Tue, 05 Jan 2021 17:19:36 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id o129sm519536pfg.66.2021.01.05.17.19.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 17:19:36 -0800 (PST)
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com>
Date: Tue, 5 Jan 2021 17:19:34 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com>
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/XdL2BOr3x6Sop0JAevpuYgFskhs>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 01:19:39 -0000

On 1/5/21 5:11 PM, Douglas Foster wrote:
> Sorry that my name was dragged into this.   The study in question was 
> one  provided by Laura Atkins several months ago.   I forwarded it to 
> Michael to bring him up to speed.   To date, it is the only study 
> submitted to this group. I was not trying to introduce new information 
> or re-ignite this fight.  The chairs and our charter call for us to 
> proceed with DMARC as a tool to control misuse of the From address, 
> which is also what I want.


No it was an unalloyed good that you brought that up. We can use a much 
more data-driven approach rather than opinion and conjecture. It would 
be good for it to be required reading for everybody on this working 
group, and not snarled at as a heresy. DKIM itself was a leap of faith. 
16 years later it is gratifying that we have data.

Mike


From nobody Tue Jan  5 17:23:23 2021
Return-Path: <dcrocker@gmail.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 AACE63A109D; Tue,  5 Jan 2021 17:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 7auKZ1bI-Aae; Tue,  5 Jan 2021 17:23:19 -0800 (PST)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 781413A109B; Tue,  5 Jan 2021 17:22:41 -0800 (PST)
Received: by mail-pl1-x632.google.com with SMTP id x12so709077plr.10; Tue, 05 Jan 2021 17:22:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=wTvwBiR+DYkM8SCIbYudLRI5f2kOSeiymnNEvazZ8CU=; b=S04WL+AbVvY33DW820YUoId7UypqgRPoyFFA1l4JaOc+WsyTUjsGoT86379d8Y0vNK 3MPkx1UZZqbk62AENgjNxE/8iLi+vN1C9/PlLGgprPXGm8VhQu8n0vJYiL5xwOCDBzz/ FiMIIol4okkDOFLlgCeymzsP/5qkrKopSnz4LAgsumtwhRFm1vtP+dT2D09pTHq+rzMy 8XNM9WES/8qWrAQByxdbD8YTOyIiHlf9NKf3PzUBK8e5goH5KYNock5v0cUjwVZWWYA1 khk2ZCPmM0NPV8keQP8xV29HlyY7J2bRESIYPH7fl9IgZiWSSkYv4uQ0Y11gcUzhYX9v qL9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=wTvwBiR+DYkM8SCIbYudLRI5f2kOSeiymnNEvazZ8CU=; b=lrMnG7OyC2ctnYWhTNmeOPAcKYnpgKH7NHcT5KztIWjGC78V57S1IH2uRYlGif8BPR SyMZbPz6lEr8JDX33QKUo4crm07cWUMVZhKzjREG4NFk6TQWzN2D+cWZBMM/hf5v9mYS bLi9Ojrd3pojG5+5eRSylQlI5G5KQX/OS67eo5O+7HRkIURTpXcAYJj2K2JdxKbdlxcn eTKEIbmVrWqPl2zrguqnFNnlGMbtYgAkRRmPhflgA/QVp9z7HbAriB5+phy0WXsMtXtc 8UooEvraKGBo7w9vgAIOEuVQynOLf+zX0hiJuTzRRVMcHj9Act/N7x+eLsY3j54eftoo VQkA==
X-Gm-Message-State: AOAM531iz1YWMEUyQhjQLb4lPda3qCa/tYwgOdMivgcxsMqUGBc11KuT vXnmC3iOQMJBUXY9DBR5ramICmTuGTc=
X-Google-Smtp-Source: ABdhPJw4SKyMrwQQynOPjikLJqfIj+otV8CiNyXilz2ph4HZa/nw4KmVbeYMQQ1tNnA30qPaxRdZ5A==
X-Received: by 2002:a17:90a:68c3:: with SMTP id q3mr1788403pjj.135.1609896160867;  Tue, 05 Jan 2021 17:22:40 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id u11sm408826pjy.17.2021.01.05.17.22.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 17:22:40 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, dmarc-chairs@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <230aac25-200b-1645-bbe9-902e7d5bc17e@gmail.com>
Date: Tue, 5 Jan 2021 17:22:39 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com>
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/LEk62H1ZpyAsJblexna-VCpnGn8>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 01:23:22 -0000

On 1/5/2021 5:19 PM, Michael Thomas wrote:
> and not snarled at as a heresy. 

Michael,

That was yet another ad hominem from you.  As well as being grossly 
inaccurate.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Tue Jan  5 17:23:51 2021
Return-Path: <mike@fresheez.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 9C0913A1092 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 17:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 UNvkZW38jpA0 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 17:23:48 -0800 (PST)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 897D43A0FB3 for <dmarc@ietf.org>; Tue,  5 Jan 2021 17:23:48 -0800 (PST)
Received: by mail-pg1-x530.google.com with SMTP id v19so1065344pgj.12 for <dmarc@ietf.org>; Tue, 05 Jan 2021 17:23:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=U1eREQQtLTko7HgvFUj9rHXwqE11WbjQ/JumnhotHnk=; b=Lg1OQLBNddrCA+ENeOSJm59r/PFJmDcmaf1psju8Tdu9n9ldJ6Q9G3FXS7rxLeswYN HjM8rEREZ9L7CV/20TsXi38U5NCKor7BYPWz6iwzcbRX7hb9BqYgpI73nxzQGr6U1Aw7 SG/AlPjC88gPyMKtoSFsBoivLigAqqD949l8AQt2+ZZBJa31tW1J/0co+GrzNVzEd5Gr A8Vpsrvvz9B/VVRQdap9+K2IsDOuEgDN14/VUUITAc/HWDhP042SJVMXrgypQxUMVS5z QxcjmH4wd2kfeMQyXO5YTy8esLKcSU5Kmxg/2pwe+TUM6EQYUpOOlilij1lPDZ6yz5K3 M/Rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=U1eREQQtLTko7HgvFUj9rHXwqE11WbjQ/JumnhotHnk=; b=h1k8rPhxyA/lFmJM+5zVDnCJbAwkIcBmYVx0GQEy9I0oNzaThVdA1pCcOMyMbjiBm9 kouKD8nOP2GAxI4G+17JKAWm2NjXKQ3AAbcLHSRqaFor8Nj104YDq49K8ejgqc6xmaU4 JN5dtLczHMwX7NAVgaf5N9ShHHgmIZhGwLGVhQv8LzdxNaUDiNvwTSAdTFOMnMEkiVUS ubmqTw6fIMKCXwvOGalHm/r/sAVgGpJD2sDFHRAU6OzhAq2MN+CV1mcce8GXWHQjBFKA sTWhtst+R3v9YQ/uJupIYdSvu0vXOxp3LUh6LYYbDUgu2xEBmIS7kUSaCoZcz7c6Xv76 PVgQ==
X-Gm-Message-State: AOAM531XjwqQn6114k2OzB2cFGoFgbU8rYk/RzxVj4PWc9dpy5EuDh4I r92vV1zV1BUD/8WrhW3qM0qZVw==
X-Google-Smtp-Source: ABdhPJwv1YIgrp8GTd8nvTIqYid7ajgdZpoHYonS+dR7Q71l+n21v+DFjv0ORTRtUi+eTA8viuetQA==
X-Received: by 2002:a63:c207:: with SMTP id b7mr1871366pgd.184.1609896228002;  Tue, 05 Jan 2021 17:23:48 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id u25sm513581pfn.101.2021.01.05.17.23.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 17:23:47 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, dmarc-chairs@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <230aac25-200b-1645-bbe9-902e7d5bc17e@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <98acd06f-bfe6-4b5b-f4e2-6d175e28babe@mtcc.com>
Date: Tue, 5 Jan 2021 17:23:45 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <230aac25-200b-1645-bbe9-902e7d5bc17e@gmail.com>
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/nQ5qOGukXFTU_3JN9F1ktmqbh8c>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 01:23:50 -0000

On 1/5/21 5:22 PM, Dave Crocker wrote:
> On 1/5/2021 5:19 PM, Michael Thomas wrote:
>> and not snarled at as a heresy. 
>
> Michael,
>
> That was yet another ad hominem from you.  As well as being grossly 
> inaccurate.
>
Your issue is with the authors of the study. Leave me out of this.

Mike


From nobody Tue Jan  5 22:02:36 2021
Return-Path: <dotzero@gmail.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 385913A10E3 for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 22:02:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 sG7kE5B4zeSB for <dmarc@ietfa.amsl.com>; Tue,  5 Jan 2021 22:02:30 -0800 (PST)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEF083A10E2 for <dmarc@ietf.org>; Tue,  5 Jan 2021 22:02:29 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id h4so1678935qkk.4 for <dmarc@ietf.org>; Tue, 05 Jan 2021 22:02:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QlYiyNTePcJV4Ph4sDsFxQ200P6Zs0on15sihHNUhnc=; b=XBqRMndNdII2uSFjt7NARX3a1+lJ/KZHSwrpte0K4hViWR5nQSENymGWH2srKVFqsW HrrlrpWyPvDLneblGMyUDTMYpy41cYNkshLX4gzjRFlJ6j6omYfvhiHhY6kk/5LJHhRj 4DjXOiu7n7wM/Y3FOLM1dfbmUPNLK1eNE/Z/o9s1R5eCnlniZ9jjxEJTxbHtT2dCv70y 7O6uXwHDvoVs0GKix+8WlBRAhvezxdVt1rIc6YV7WeP3MbLMueYTx/+gSBmdBG/62yhD 6f7RsV4T1tJ1eip5/6cU3ghwsGJK5ZnGFDcah0J7SiCAQQOoVcZMx12yp4LRmRzDwDBT Q7AQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QlYiyNTePcJV4Ph4sDsFxQ200P6Zs0on15sihHNUhnc=; b=E36/nTLzHUXfVVLpG93qamC7or0alWdgC6ogI/wtguJmVXQb0Vlcn54TwxkJB0uHAL O5TjcViozsFj3KtgNXD8RS3vBcXNSAbDQ+QmeQIUVMDcr+Ye+R7EkUSBCf/r6cgAHhMg azr4rwJqzkOvY6DqhsYglc6k+zlgfRU/7uEmMQVgWHWf5KYiwGHp8Ia0rDwRqmeoDBMK cGDcg1NPH0PMTCGjaZAbdWsmU2n4UDLNYRC8Ge822WEsHB3WSS+OaB7LhwNOU2/I0gp1 XE+mwfd4KDcjIvpsynOWN2iWWuMDT3SXIqoArXbZiUZX9AeRd2SLyR+H+/cbumpC1W0R nAew==
X-Gm-Message-State: AOAM532Uh7gJqNNb57aQLe/vysg8lNmWqfuz87cnbfwkyjNVIJnSjNi5 Pp77ZZfEdVnklRl/g7Y94AqrmTdk49PUG2imNKQ=
X-Google-Smtp-Source: ABdhPJztmC5HLiYzwTllUUULekJ4/cCSiQkSoYQG49X6t0dOvBf/heMCI2uMzEgzZkHEC+rIe1xRsq9xEHlnovXCmgI=
X-Received: by 2002:a37:478e:: with SMTP id u136mr3020103qka.64.1609912948797;  Tue, 05 Jan 2021 22:02:28 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com>
In-Reply-To: <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com>
From: Dotzero <dotzero@gmail.com>
Date: Wed, 6 Jan 2021 01:02:17 -0500
Message-ID: <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006eb51205b8351173"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/iH9fPTavqVnXmNhDohpTw8_mkuM>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 06:02:33 -0000

--0000000000006eb51205b8351173
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 5, 2021 at 8:19 PM Michael Thomas <mike@mtcc.com> wrote:


> No it was an unalloyed good that you brought that up. We can use a much
> more data-driven approach rather than opinion and conjecture. It would
> be good for it to be required reading for everybody on this working
> group, and not snarled at as a heresy. DKIM itself was a leap of faith.
> 16 years later it is gratifying that we have data.
>
> Mike
>

DKIM was NOT a leap of faith. At the time there was plenty of data from DK
(Domain Keys) and IIM to inform those involved. Please stop making
assertions of "fact" which are simply not true.

Michael Hammer

--0000000000006eb51205b8351173
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 5, 2021 at 8:19 PM Michae=
l Thomas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<=
br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
No it was an unalloyed good that you brought that up. We can use a much <br=
>
more data-driven approach rather than opinion and conjecture. It would <br>
be good for it to be required reading for everybody on this working <br>
group, and not snarled at as a heresy. DKIM itself was a leap of faith. <br=
>
16 years later it is gratifying that we have data.<br>
<br>
Mike<br></blockquote><div><br></div><div>DKIM was NOT a leap of faith. At t=
he time there was plenty of data from DK (Domain Keys) and IIM to inform th=
ose involved. Please stop making assertions of &quot;fact&quot; which are s=
imply not true. <br></div><div><br></div><div>Michael Hammer<br></div></div=
></div>

--0000000000006eb51205b8351173--


From nobody Wed Jan  6 02:10:43 2021
Return-Path: <laura@wordtothewise.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 CA3793A128B for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 02:10:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
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 ohc8MveEx-Xu for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 02:10:39 -0800 (PST)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id 728713A1286 for <dmarc@ietf.org>; Wed,  6 Jan 2021 02:10:39 -0800 (PST)
Received: from [192.168.0.227] (unknown [37.228.231.27]) by mail.wordtothewise.com (Postfix) with ESMTPSA id E5A3E9F149 for <dmarc@ietf.org>; Wed,  6 Jan 2021 02:10:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1609927838; bh=vZFG5fIC0e250DJ1CEusghRcqhCEd1GeblTF8nHUUwM=; h=From:Subject:Date:References:To:In-Reply-To:From; b=DBkdEjqJwVPhspY+fEF3rWuRTD5agxtJvDW36Ans2r2794QKVLGV/aB2Ik8WiCmR+ X3uQYjEQgztIiri6BrTi7z/ien6b2obcQUXJfJ1oJr+LKfqoyC1ucqUanA7yl3VGeD Pgs7mMmeyfnnUqp5a3Kzf1M40CUxKn9ko79n60W4=
From: Laura Atkins <laura@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E21B0534-F68F-413C-BB50-2D278E1FBD91"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 6 Jan 2021 10:10:35 +0000
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <050e8614-c088-a165-a733-35c5eee52eed@gmail.com>
Message-Id: <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mGSm0A5c-eih2PARiL7h6bGxVHw>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 10:10:42 -0000

--Apple-Mail=_E21B0534-F68F-413C-BB50-2D278E1FBD91
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Changed the subject line because this has nothing to do with failure =
reports.=20

> On 5 Jan 2021, at 20:04, Dave Crocker <dcrocker@gmail.com> wrote:
>=20
> On 1/5/2021 11:34 AM, Michael Thomas wrote:
>> On 1/5/21 11:22 AM, Dave Crocker wrote:=20
>>> From: header field rewriting demonstrates that DMARC is, indeed, =
trivial to defeat (or rather, to route around.)  Also, receiver =
filtering engines are all that matter.  Real-time actions by recipients =
are demonstrably irrelevant to DMARC (and all other anti-abuse) utility.=20=

>>>=20
>> That's not the conclusion of the paper that Doug Foster linked to the =
other day.
> 1. I've looked back over his postings to this mailing list and am not =
finding the link you refer to.  Please post it (again).
>=20
Someone mentioned it was the article I shared a few months ago. If so =
it=E2=80=99s this one: =
https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.p=
df =
<https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.=
pdf>

Note: a single study does not make any conclusion accurate.=20
> 2. A single study is unlikely to be definitive about much of anything.
>=20
Absolutely true.=20

Anyone relying on a single piece of evidence to prove their point is =
wrong. I am absolutely sure there is a bigger body of research out there =
and more data. In fact, I was at a conference in SF many years ago =
reporting a study done between a mailbox provider and a large sender of =
email. Their study showed quite definitively that visual indicators in =
email do not affect user behavior in any statistically meaningful way.=20=


> 3. Especially when it counters years of experience, including the Web =
EV experiment
>=20
>      https://en.wikipedia.org/wiki/Extended_Validation_Certificate =
<https://en.wikipedia.org/wiki/Extended_Validation_Certificate>Effectivene=
ss against phishing attacks with IE7 security UI
>>=20
>> In 2006, researchers at Stanford University =
<https://en.wikipedia.org/wiki/Stanford_University> and Microsoft =
Research <https://en.wikipedia.org/wiki/Microsoft_Research> conducted a =
usability study[21] =
<https://en.wikipedia.org/wiki/Extended_Validation_Certificate#cite_note-2=
1> of the EV display in Internet Explorer 7 =
<https://en.wikipedia.org/wiki/Internet_Explorer_7>. Their paper =
concluded that "participants who received no training in browser =
security features did not notice the extended validation indicator and =
did not outperform the control group", whereas "participants who were =
asked to read the Internet Explorer help file were more likely to =
classify both real and fake sites as legitimate".

And that=E2=80=99s with the Extended Validation Certificate which =
required extensive checks by the certification authority. In email =
anyone can =E2=80=98certify=E2=80=99 their mail with DMARC. Bad actors =
can trivially get a DMARC pass if they control the mail. If we start =
saying =E2=80=98bypass DMARC by rewriting the From: address=E2=80=99 to =
legitimate mailers then every bad actor on the planet is going to do the =
same thing.=20

Header rewriting is a poor solution to the problem of indirect mail =
flows.=20

>> When I first came back and saw the =46rom rewriting I was very =
confused by what it was until I figured out what was going on.
> You think you are representative of end users?  Try again.
>=20
I think he=E2=80=99s representative of one kind of enduser. He=E2=80=99s =
getting a trust indicator in email (DMARC fails) and doesn=E2=80=99t =
understand what that indicator means or implies. When I shared the =
relevant piece of the DMARC spec causing the DMARC failure he told me =
that was =E2=80=98all gobbledygook=E2=80=99 and that alignment wasn=E2=80=99=
t even part of DMARC.=20

I think this is exactly one of the types of responses we can expect from =
end users.=20

laura=20

--=20
Having an Email Crisis?  We can help! 800 823-9674=20

Laura Atkins
Word to the Wise
laura@wordtothewise.com
(650) 437-0741	=09

Email Delivery Blog: https://wordtothewise.com/blog=09








--Apple-Mail=_E21B0534-F68F-413C-BB50-2D278E1FBD91
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Changed the subject line because this has nothing to do with =
failure reports.&nbsp;<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 5 Jan 2021, at 20:04, Dave =
Crocker &lt;<a href=3D"mailto:dcrocker@gmail.com" =
class=3D"">dcrocker@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">
 =20
    <meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DUTF-8" class=3D"">
 =20
  <div class=3D"">
    <div class=3D"moz-cite-prefix">On 1/5/2021 11:34 AM, Michael Thomas
      wrote:<br class=3D"">
    </div>
    <blockquote type=3D"cite" =
cite=3D"mid:f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com" class=3D"">On =
1/5/21
      11:22 AM, Dave Crocker wrote:
      <br class=3D"">
      <blockquote type=3D"cite" style=3D"color: #0000a0;" class=3D"">
        From: header field rewriting demonstrates that DMARC is, indeed,
        trivial to defeat (or rather, to route around.)&nbsp; Also, =
receiver
        filtering engines are all that matter.&nbsp; Real-time actions =
by
        recipients are demonstrably irrelevant to DMARC (and all other
        anti-abuse) utility.
        <br class=3D"">
        <br class=3D"">
      </blockquote>
      That's not the conclusion of the paper that Doug Foster linked to
      the other day.</blockquote><p class=3D"">1. I've looked back over =
his postings to this mailing list and am
      not finding the link you refer to.&nbsp; Please post it =
(again).</p></div></div></blockquote>Someone mentioned it was the =
article I shared a few months ago. If so it=E2=80=99s this =
one:&nbsp;<font face=3D"ArialMT" class=3D""><a =
href=3D"https://www.usenix.org/system/files/conference/usenixsecurity18/se=
c18-hu.pdf" =
class=3D"">https://www.usenix.org/system/files/conference/usenixsecurity18=
/sec18-hu.pdf</a></font></div><div><br class=3D""></div><div>Note: a =
single study does not make any conclusion =
accurate.&nbsp;</div><div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><p class=3D"">2. A single study is unlikely =
to be definitive about much of
      anything.</p></div></div></blockquote>Absolutely =
true.&nbsp;</div><div><br class=3D""></div><div>Anyone relying on a =
single piece of evidence to prove their point is wrong.&nbsp;I am =
absolutely sure there is a bigger body of research out there and more =
data. In fact, I was at a conference in SF many years ago reporting a =
study done between a mailbox provider and a large sender of email. Their =
study showed quite definitively that visual indicators in email do not =
affect user behavior in any statistically meaningful =
way.&nbsp;</div><div><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><p class=3D"">3. Especially =
when it counters years of experience, including the
      Web EV experiment<br class=3D"">
    </p><p class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;
      <a class=3D"moz-txt-link-freetext" =
href=3D"https://en.wikipedia.org/wiki/Extended_Validation_Certificate">htt=
ps://en.wikipedia.org/wiki/Extended_Validation_Certificate</a></p>
    <blockquote type=3D"cite" class=3D"">
      <h3 class=3D""><span class=3D"mw-headline" =
id=3D"Effectiveness_against_phishing_attacks_with_IE7_security_UI">Effecti=
veness
          against phishing attacks with IE7 security UI</span></h3>
      In 2006, researchers at <a =
href=3D"https://en.wikipedia.org/wiki/Stanford_University" =
title=3D"Stanford University" class=3D"">Stanford University</a> and <a =
href=3D"https://en.wikipedia.org/wiki/Microsoft_Research" =
title=3D"Microsoft Research" class=3D"">Microsoft Research</a> conducted =
a
      usability study<sup id=3D"cite_ref-21" class=3D"reference"><a =
href=3D"https://en.wikipedia.org/wiki/Extended_Validation_Certificate#cite=
_note-21" class=3D"">[21]</a></sup>
      of the EV display in <a =
href=3D"https://en.wikipedia.org/wiki/Internet_Explorer_7" =
title=3D"Internet Explorer 7" class=3D"">Internet Explorer 7</a>. Their =
paper
      concluded that "participants who received no training in browser
      security features did not notice the extended validation indicator
      and did not outperform the control group", whereas "participants
      who were asked to read the Internet Explorer help file were more
      likely to classify both real and fake sites as =
legitimate".</blockquote></div></div></blockquote><div><br =
class=3D""></div><div>And that=E2=80=99s with the Extended Validation =
Certificate which required extensive checks by the certification =
authority. In email anyone can =E2=80=98certify=E2=80=99 their mail with =
DMARC. Bad actors can trivially get a DMARC pass if they control the =
mail. If we start saying =E2=80=98bypass DMARC by rewriting the From: =
address=E2=80=99 to legitimate mailers then every bad actor on the =
planet is going to do the same thing.&nbsp;</div><div><br =
class=3D""></div><div>Header rewriting is a poor solution to the problem =
of indirect mail flows.&nbsp;</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">
    <blockquote type=3D"cite" =
cite=3D"mid:f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com" class=3D"">When=
 I
      first came back and saw the =46rom rewriting I was very confused =
by
      what it was until I figured out what was going on. </blockquote><p =
class=3D"">You think you are representative of end users?&nbsp; Try =
again.</p></div></div></blockquote>I think he=E2=80=99s representative =
of one kind of enduser. He=E2=80=99s getting a trust indicator in email =
(DMARC fails) and doesn=E2=80=99t understand what that indicator means =
or implies. When I shared the relevant piece of the DMARC spec causing =
the DMARC failure he told me that was =E2=80=98all gobbledygook=E2=80=99 =
and that alignment wasn=E2=80=99t even part of DMARC.&nbsp;<br =
class=3D""></div><div><br class=3D""></div><div>I think this is exactly =
one of the types of responses we can expect from end =
users.&nbsp;</div><div><br class=3D""></div><div>laura&nbsp;</div><div><br=
 class=3D""></div><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px; font-family: Helvetica; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal;"><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
class=3D"">--&nbsp;</div><div class=3D"">Having an Email Crisis? =
&nbsp;We can help! 800 823-9674&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Laura Atkins</div><div class=3D"">Word =
to the Wise</div><div class=3D""><a =
href=3D"mailto:laura@wordtothewise.com" =
class=3D"">laura@wordtothewise.com</a></div><div class=3D"">(650) =
437-0741<span class=3D"Apple-tab-span" style=3D"white-space: pre;">		=
</span></div><div class=3D""><br =
class=3D""></div></span></span></span></span></span></div><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;">Email Delivery Blog: <a =
href=3D"https://wordtothewise.com/blog" =
class=3D"">https://wordtothewise.com/blog</a><span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span></span></span></span></span></span></div></span></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_E21B0534-F68F-413C-BB50-2D278E1FBD91--


From nobody Wed Jan  6 04:30:00 2021
Return-Path: <dougfoster.emailstandards@gmail.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 59AE73A046A for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 04:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 hBIJZhJ9zYXB for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 04:29:56 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A23113A045E for <dmarc@ietf.org>; Wed,  6 Jan 2021 04:29:56 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id z16so1674043vsp.5 for <dmarc@ietf.org>; Wed, 06 Jan 2021 04:29:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gHaSMAwWOVaZyywPIdDy2wX4iv5qGOPS9UlwUqG4oMs=; b=SfyQ+YHqLIzgil58sfAB0/K2mOdI9KNZQBRDd1HaIoxsD7TQSQO2UnAcrp6eW8M6Ua BTbg2fOHY+iJXkVBATSrSclXPyVGhhJzXNHemqMHgTiFHdySErPTWbfKyxjnfjwjL4dW KqqMVbuf9Ld2N2YFXO1pCnaVhA0boTtWs2OiGIycFFpRsFNqPf62FLo3gE3sxc0/yvVG IzZCljk1SIzLo2MZBAkFs0X+jZ5VZEfWEFBJGrmCSJV7PYVGYtd7jBSk5j+6anaIrcZI YbA8CD25+wwSTcxOVPEada2ZDGO0gDlYiivZMYWNZ/Bu7hhZux7CS2xunODtYY0ja3Dh 8aEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gHaSMAwWOVaZyywPIdDy2wX4iv5qGOPS9UlwUqG4oMs=; b=U/WzvrucIVnMonmhdu2i58Q3BRzV72ZDU+yUJtt9Du+KTvx4v9wgmcBmx4qu3JwtuE L3Dx32tS1c3A+Q2zus+ck47nGQDnJyrqb5Q5RZ0X2G+90UdP6oICDFI+z42vK47Rj6Uk LaBtxW3MgSPx/sTBkPWCUrrFSEmIvC0WPUNPJVjx0teCMqGwNYcTkUUO2CBEWKMYsW/Z jT6/gGokx+lZ5aHJA1R+WczLeDtCMfUhi4tMqVIq6QFr7/KwWDtTjNcUbYhOb2WXvR+o efePD2bhruJkifTbYxvMPULgGQb++ZzaFBi908EPIj0qiiJafYhUqRbr10Dm/RrUsw1I 4q0g==
X-Gm-Message-State: AOAM530fjal7Bv8IRb+HHoHyGG+rHqGsj1PDduK0FSKRPWJyelKlaTY1 NRKX1oBcbNnBxLDYW5RbJyCoEtfjmXcbdfaFteE=
X-Google-Smtp-Source: ABdhPJyO0gzCF37VgYzSqKvajXpZK7ZghpwAO6xwy0YF95e2FNqhG9kqDkYMkI6d7pBMpTIheUaq+L2Cw6rtqwtiPBQ=
X-Received: by 2002:a67:c983:: with SMTP id y3mr2678616vsk.59.1609936195444; Wed, 06 Jan 2021 04:29:55 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com>
In-Reply-To: <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 6 Jan 2021 07:29:44 -0500
Message-ID: <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com>
To: Laura Atkins <laura@wordtothewise.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000a62bc05b83a7b2b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/iuFZTkkqEMANdbM8i-ze2OM3njQ>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 12:29:58 -0000

--0000000000000a62bc05b83a7b2b
Content-Type: text/plain; charset="UTF-8"

I am no fan of header rewrite, but...

If you are going to talk about "Trust Indicators", we need to define terms,
which has not been done.   Here are my definitions:
- The From header is an Identity Assertion.
- DMARC is an Identity Verification technique.
- A text message saying, "This message verified by DMARC", is a Trust
Indicator.
My definitions are consistent with the way that that one study used a trust
indicator.   Using these definitions, From rewrite has nothing to do with
Trust Indicator research.  If anyone wants to assert different definitions,
please get them on the table.

The fact that users complain about From rewrite is proof that they look at
the information.    This is because it is an Identity Assertion, not a
Trust Indicator.

I accept that actual Trust Indicators have a small effect, but rounding
down  to zero seems like an overstatement.   When fighting malware, I will
take all the help that I can get, even small help.

Lots of organizations use trust indicators and lots of organizations use
DMARC for validating the From address.  Message annotation has gone up
exactly because many MUAs are making the From address visible only on
request.   Common tag lines are now of the form:  "This message is from an
external source, so be careful."   I don't see that it is our job to tell
domain owners that they are wrong,

Domain administrators are within their rights to block any incoming message
for any reason.   Users routinely work with their domain administrators to
ensure that the messages that they want get accepted and messages that they
do not want get blocked.    If users and domain administrators cannot solve
their differences, the user can communicate using a different domain.  If
DMARC produces false positives that cannot be resolved by this process, we
would do well to ask why.

I see no relevance between the EV experience and DMARC.   EV is an identity
verification technique, but it lacked a policy mechanism.   As a website
user, I have no way of knowing whether a particular website MUST have an EV
certificate or not.   If such a policy mechanism existed, it would have
been automated and the site would be blocked.   DMARC has a policy
mechanism, and it has been automated, so messages are blocked.

Forwarding hides information that the email filter needs to make a correct
decision.   Header rewrite hides the problem, but does not solve it.   When
we get the automation right, predicting user behavior will not be necessary.

Doug Foster


>
>

--0000000000000a62bc05b83a7b2b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">I am no fan of header rewrite, but...<div=
><div><br></div><div>If you are going to talk about &quot;Trust Indicators&=
quot;, we need to define terms, which has not been done.=C2=A0 =C2=A0Here a=
re my definitions:</div><div>- The From header is an Identity Assertion.</d=
iv><div>- DMARC is an Identity Verification technique.</div><div>- A text m=
essage saying, &quot;This message verified by DMARC&quot;, is a Trust Indic=
ator.</div><div>My definitions are consistent with the way that that one st=
udy used a trust indicator.=C2=A0 =C2=A0Using these definitions, From rewri=
te has nothing to do with Trust Indicator research.=C2=A0 If anyone wants t=
o assert different=C2=A0definitions, please get them on the table.</div><di=
v><br></div><div><div>The fact that users complain about From rewrite is pr=
oof that they look at the information.=C2=A0 =C2=A0 This is because it is a=
n Identity Assertion, not a Trust Indicator.<br></div><div></div></div><div=
><br></div><div>I accept that actual Trust Indicators have a small effect,=
=C2=A0but rounding down=C2=A0 to zero seems like an overstatement.=C2=A0 =
=C2=A0When fighting malware, I will take all the help that I can get, even =
small help.</div><div><div><br></div><div>Lots of organizations use trust i=
ndicators and lots of organizations use DMARC for validating the From addre=
ss.=C2=A0 Message annotation has gone up exactly because many MUAs are maki=
ng the From address visible only on request.=C2=A0 =C2=A0Common tag lines=
=C2=A0are now of the form:=C2=A0 &quot;This message is from an external sou=
rce, so be careful.&quot;=C2=A0 =C2=A0I don&#39;t see that it is our job to=
 tell domain owners that they are wrong,</div><div><br></div><div>Domain ad=
ministrators are within their rights to block any incoming message for any =
reason.=C2=A0 =C2=A0Users routinely work with their domain administrators t=
o ensure that the messages that they want get accepted and messages that th=
ey do not want get blocked.=C2=A0 =C2=A0 If users and domain administrators=
 cannot solve their differences, the user can communicate using a different=
 domain.=C2=A0 If DMARC produces false positives that cannot be resolved by=
 this process, we would do well to ask why.</div><div></div></div><div><br>=
</div><div>I see no relevance between the EV experience and DMARC.=C2=A0 =
=C2=A0EV is an identity verification technique, but it lacked a policy mech=
anism.=C2=A0 =C2=A0As a website user, I have no way of knowing whether a pa=
rticular website MUST have an EV certificate or not.=C2=A0 =C2=A0If such a =
policy mechanism existed, it would have been automated and the site would b=
e blocked.=C2=A0 =C2=A0DMARC has a policy mechanism, and it has been automa=
ted, so messages are blocked.</div><div><br></div></div><div>Forwarding hid=
es information that the email filter needs to make a correct decision.=C2=
=A0 =C2=A0Header rewrite hides the problem, but does not solve it.=C2=A0 =
=C2=A0When we get the automation right, predicting user behavior will not b=
e necessary.</div><div><br></div><div>Doug Foster</div></div><br><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>
</blockquote></div></div>

--0000000000000a62bc05b83a7b2b--


From nobody Wed Jan  6 04:52:42 2021
Return-Path: <laura@wordtothewise.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 0B25B3A0813 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 04:52:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
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 bJ7pcN44Z5rc for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 04:52:37 -0800 (PST)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id DC5E93A0809 for <dmarc@ietf.org>; Wed,  6 Jan 2021 04:52:37 -0800 (PST)
Received: from [192.168.0.227] (unknown [37.228.231.27]) by mail.wordtothewise.com (Postfix) with ESMTPSA id 6818E9F149 for <dmarc@ietf.org>; Wed,  6 Jan 2021 04:52:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1609937557; bh=pMupoUh4HPYFa0p9yMvFoHtJBdorhwmU0q/LhCNaqiw=; h=From:Subject:Date:References:To:In-Reply-To:From; b=f1j7xTLzKtkMITVCFO5d41Y4+uvknY53Njvc1bB4ppl5RCFDuDPsmhcAuhhOXvtbM vVCqZHn7MCoiW5EE8Yi2PvEbcwsWL4LwqYRItDtEC3tJgB+uz8mXEBRz+OpX8FWF6S 1Ltsrvnmu3/30ohRrxD03a0L5npIrt7d1LmmiVYI=
From: Laura Atkins <laura@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A1B901DB-9765-4648-8D65-7DC05D705008"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 6 Jan 2021 12:52:33 +0000
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com> <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com>
Message-Id: <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/11pUrppM-XHee8HSkBbLxwrET1g>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 12:52:40 -0000

--Apple-Mail=_A1B901DB-9765-4648-8D65-7DC05D705008
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 6 Jan 2021, at 12:29, Douglas Foster =
<dougfoster.emailstandards@gmail.com> wrote:
>=20
> I am no fan of header rewrite, but...
>=20
> If you are going to talk about "Trust Indicators", we need to define =
terms, which has not been done.   Here are my definitions:
> - The =46rom header is an Identity Assertion.
> - DMARC is an Identity Verification technique.
> - A text message saying, "This message verified by DMARC", is a Trust =
Indicator.
> My definitions are consistent with the way that that one study used a =
trust indicator.   Using these definitions, =46rom rewrite has nothing =
to do with Trust Indicator research.  If anyone wants to assert =
different definitions, please get them on the table.
>=20
> The fact that users complain about =46rom rewrite is proof that they =
look at the information.    This is because it is an Identity Assertion, =
not a Trust Indicator.

The header rewriting being proposed - that is header rewriting by the =
ESP so that the messages that go through their system are rewritten to =
point to the ESP and not the author of the message - means that the =
identity assertion is disconnected from the context of a message.

Want to know what mail goes through ESPs? Bank mail, social media mail, =
marketing mail. Billions of emails a day go through ESPs that you have =
and have not heard of.=20

The proposal at issue is that these ESPs be allowed to rewrite the =46rom =
 address any message they handle to point to an email address they =
control. This disconnects the identity in the 5322.from address from the =
actual sender of the message.=20

Most users may know who constantcontact are or mailchimp because they =
advertise widely. Some might have heard of GoDaddy but do you know what =
the company name of the GoDaddy ESP is? I don=E2=80=99t off the top of =
my head.=20

> I accept that actual Trust Indicators have a small effect, but =
rounding down  to zero seems like an overstatement.   When fighting =
malware, I will take all the help that I can get, even small help.

And now we have a malware company that rewrites headers to point to a =
domain they own and it passes DMARC and is given a Trust Indicator. =
Recipients are used to seeing domains they don=E2=80=99t know or =
understand send trusted mail from their bank, or their girl scout troop, =
or their social media company. They have no reason to distrust the =
unfamiliar identity assertion in the from address.=20

> Lots of organizations use trust indicators and lots of organizations =
use DMARC for validating the =46rom address.  Message annotation has =
gone up exactly because many MUAs are making the =46rom address visible =
only on request.   Common tag lines are now of the form:  "This message =
is from an external source, so be careful."   I don't see that it is our =
job to tell domain owners that they are wrong,

This has nothing to do with header rewriting at all, which is the topic =
at hand.=20

> Domain administrators are within their rights to block any incoming =
message for any reason.   Users routinely work with their domain =
administrators to ensure that the messages that they want get accepted =
and messages that they do not want get blocked.    If users and domain =
administrators cannot solve their differences, the user can communicate =
using a different domain.  If DMARC produces false positives that cannot =
be resolved by this process, we would do well to ask why.

Header rewriting doesn=E2=80=99t solve false positives, it increases the =
chances of them. Header rewriting for commercial messages by ESPs means =
that folks attempting to masquerade as a legitimate company have a RFC =
recommended way to evade DMARC and pretend to be the company they=E2=80=99=
re attacking.=20

This isn=E2=80=99t random speculation, this is what is going to happen. =
We've spent the last 20 years watching spammers and phishers do =
everything they can to get mail out. If the DMARC RFC says =E2=80=98ESPs =
should rewrite headers to avoid DMARC policies on mail going through the =
ESP=E2=80=99 then we=E2=80=99ve just made DMARC utterly worthless. =
We=E2=80=99ve also set up every company that is currently using DMARC =
p=3Dreject to be attacked in ways they cannot tract.=20

> I see no relevance between the EV experience and DMARC.   EV is an =
identity verification technique, but it lacked a policy mechanism.   As =
a website user, I have no way of knowing whether a particular website =
MUST have an EV certificate or not.   If such a policy mechanism =
existed, it would have been automated and the site would be blocked.   =
DMARC has a policy mechanism, and it has been automated, so messages are =
blocked.

The whole point here is that header rewriting evades the policy =
mechanism of DMARC so that messages aren=E2=80=99t blocked.

> Forwarding hides information that the email filter needs to make a =
correct decision.   Header rewrite hides the problem, but does not solve =
it.   When we get the automation right, predicting user behavior will =
not be necessary.

You=E2=80=99re going to need to provide evidence this is the case.

laura

--=20
Having an Email Crisis?  We can help! 800 823-9674=20

Laura Atkins
Word to the Wise
laura@wordtothewise.com
(650) 437-0741	=09

Email Delivery Blog: https://wordtothewise.com/blog=09








--Apple-Mail=_A1B901DB-9765-4648-8D65-7DC05D705008
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 6 Jan 2021, at 12:29, Douglas Foster &lt;<a =
href=3D"mailto:dougfoster.emailstandards@gmail.com" =
class=3D"">dougfoster.emailstandards@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div dir=3D"ltr" class=3D"">I am no fan of header rewrite, =
but...<div class=3D""><div class=3D""><br class=3D""></div><div =
class=3D"">If you are going to talk about "Trust Indicators", we need to =
define terms, which has not been done.&nbsp; &nbsp;Here are my =
definitions:</div><div class=3D"">- The =46rom header is an Identity =
Assertion.</div><div class=3D"">- DMARC is an Identity Verification =
technique.</div><div class=3D"">- A text message saying, "This message =
verified by DMARC", is a Trust Indicator.</div><div class=3D"">My =
definitions are consistent with the way that that one study used a trust =
indicator.&nbsp; &nbsp;Using these definitions, =46rom rewrite has =
nothing to do with Trust Indicator research.&nbsp; If anyone wants to =
assert different&nbsp;definitions, please get them on the =
table.</div><div class=3D""><br class=3D""></div><div class=3D""><div =
class=3D"">The fact that users complain about =46rom rewrite is proof =
that they look at the information.&nbsp; &nbsp; This is because it is an =
Identity Assertion, not a Trust Indicator.<br =
class=3D""></div></div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>The header rewriting being proposed - that is =
header rewriting by the ESP so that the messages that go through their =
system are rewritten to point to the ESP and not the author of the =
message - means that the identity assertion is disconnected from the =
context of a message.</div><div><br class=3D""></div><div>Want to know =
what mail goes through ESPs? Bank mail, social media mail, marketing =
mail. Billions of emails a day go through ESPs that you have and have =
not heard of.&nbsp;</div><div><br class=3D""></div><div>The proposal at =
issue is that these ESPs be allowed to rewrite the =46rom &nbsp;address =
any message they handle to point to an email address they control. This =
disconnects the identity in the 5322.from address from the actual sender =
of the message.&nbsp;</div><div><br class=3D""></div><div>Most users may =
know who constantcontact are or mailchimp because they advertise widely. =
Some might have heard of GoDaddy but do you know what the company name =
of the GoDaddy ESP is? I don=E2=80=99t off the top of my =
head.&nbsp;</div><div><br class=3D""></div><blockquote type=3D"cite" =
class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D""><div class=3D"">I accept that actual Trust Indicators have a =
small effect,&nbsp;but rounding down&nbsp; to zero seems like an =
overstatement.&nbsp; &nbsp;When fighting malware, I will take all the =
help that I can get, even small =
help.</div></div></div></div></blockquote><div><br =
class=3D""></div><div>And now we have a malware company that rewrites =
headers to point to a domain they own and it passes DMARC and is given a =
Trust Indicator. Recipients are used to seeing domains they don=E2=80=99t =
know or understand send trusted mail from their bank, or their girl =
scout troop, or their social media company. They have no reason to =
distrust the unfamiliar identity assertion in the from =
address.&nbsp;</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D""><div class=3D""><div class=3D"">Lots of organizations use =
trust indicators and lots of organizations use DMARC for validating the =
=46rom address.&nbsp; Message annotation has gone up exactly because =
many MUAs are making the =46rom address visible only on request.&nbsp; =
&nbsp;Common tag lines&nbsp;are now of the form:&nbsp; "This message is =
from an external source, so be careful."&nbsp; &nbsp;I don't see that it =
is our job to tell domain owners that they are =
wrong,</div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>This has nothing to do with header rewriting at =
all, which is the topic at hand.&nbsp;</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div dir=3D"ltr" class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D""><div class=3D""><div class=3D"">Domain =
administrators are within their rights to block any incoming message for =
any reason.&nbsp; &nbsp;Users routinely work with their domain =
administrators to ensure that the messages that they want get accepted =
and messages that they do not want get blocked.&nbsp; &nbsp; If users =
and domain administrators cannot solve their differences, the user can =
communicate using a different domain.&nbsp; If DMARC produces false =
positives that cannot be resolved by this process, we would do well to =
ask why.</div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>Header rewriting doesn=E2=80=99t solve false =
positives, it increases the chances of them. Header rewriting for =
commercial messages by ESPs means that folks attempting to masquerade as =
a legitimate company have a RFC recommended way to evade DMARC and =
pretend to be the company they=E2=80=99re attacking.&nbsp;</div><div><br =
class=3D""></div><div>This isn=E2=80=99t random speculation, this is =
what is going to happen. We've spent the last 20 years watching spammers =
and phishers do everything they can to get mail out. If the DMARC RFC =
says =E2=80=98ESPs should rewrite headers to avoid DMARC policies on =
mail going through the ESP=E2=80=99 then we=E2=80=99ve just made DMARC =
utterly worthless. We=E2=80=99ve also set up every company that is =
currently using DMARC p=3Dreject to be attacked in ways they cannot =
tract.&nbsp;</div><br class=3D""><blockquote type=3D"cite" class=3D""><div=
 dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><div =
class=3D""><div class=3D""></div></div><div class=3D"">I see no =
relevance between the EV experience and DMARC.&nbsp; &nbsp;EV is an =
identity verification technique, but it lacked a policy mechanism.&nbsp; =
&nbsp;As a website user, I have no way of knowing whether a particular =
website MUST have an EV certificate or not.&nbsp; &nbsp;If such a policy =
mechanism existed, it would have been automated and the site would be =
blocked.&nbsp; &nbsp;DMARC has a policy mechanism, and it has been =
automated, so messages are =
blocked.</div></div></div></div></blockquote><div><br =
class=3D""></div><div>The whole point here is that header rewriting =
evades the policy mechanism of DMARC so that messages aren=E2=80=99t =
blocked.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
dir=3D"ltr" class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"">Forwarding hides information that the email filter needs to =
make a correct decision.&nbsp; &nbsp;Header rewrite hides the problem, =
but does not solve it.&nbsp; &nbsp;When we get the automation right, =
predicting user behavior will not be =
necessary.</div></div></div></blockquote><div><br =
class=3D""></div><div>You=E2=80=99re going to need to provide evidence =
this is the case.</div><div><br class=3D""></div><div>laura</div></div><br=
 class=3D""><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px; font-family: Helvetica; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal;"><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
class=3D"">--&nbsp;</div><div class=3D"">Having an Email Crisis? =
&nbsp;We can help! 800 823-9674&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Laura Atkins</div><div class=3D"">Word =
to the Wise</div><div class=3D""><a =
href=3D"mailto:laura@wordtothewise.com" =
class=3D"">laura@wordtothewise.com</a></div><div class=3D"">(650) =
437-0741<span class=3D"Apple-tab-span" style=3D"white-space: pre;">		=
</span></div><div class=3D""><br =
class=3D""></div></span></span></span></span></span></div><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;">Email Delivery Blog: <a =
href=3D"https://wordtothewise.com/blog" =
class=3D"">https://wordtothewise.com/blog</a><span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span></span></span></span></span></span></div></span></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_A1B901DB-9765-4648-8D65-7DC05D705008--


From nobody Wed Jan  6 06:12:07 2021
Return-Path: <dcrocker@gmail.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 AB6103A0BBC for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 06:12:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 sQafx2d3wIgB for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 06:12:05 -0800 (PST)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 982BA3A0BB1 for <dmarc@ietf.org>; Wed,  6 Jan 2021 06:12:05 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id c22so2267649pgg.13 for <dmarc@ietf.org>; Wed, 06 Jan 2021 06:12:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=1ZyBPzOGJdUtbpPKzf29HnpLCDaiquP+6ht0WQqjRAw=; b=MpMy+0md7xDwGoGy0wk5TYqYg0q/eEmfcOHSbxogdCiMrDCKe9HX+JotqrhgBNUAas hTfmnqkJ+Xybm7GwXVYkosGlpYC89HbJHdcVQGfiXJRV/RjhBlNk5Y51Ivn9oi7SKzLh EIT0FsUvyFcVZiVaagwHnyASBhir6PCBzJeQhmM9Uchq9hQJku6G4Fl+YLuF1SeToBPe aUA0GXaQ54OPF8D/H33ZvPIGFin4hp0ZG7J2sRRkJP9hbBlZk9crX3GNvxIUG4Wf7js/ MRSW2/DSgcgdYBPaKQ6TK+Db2iBf/GZM9/tSk7/rS6Rvy75nfOO/ZFS/+Dtt8Z4M5KGY S+PA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=1ZyBPzOGJdUtbpPKzf29HnpLCDaiquP+6ht0WQqjRAw=; b=lgBU1QOf4+WHXA6SLgZPj1C9TvHJYZOBYsuQfwd10gAaKUdGqAEY5T+6oO/ewif9O1 oLIiLdnYwWX3F6mDUE3dTQqsE3OWxpUGltKTMf5k7CMCGl/pZ2j2Wb6zabtDHzMz5Xca spSfkfeCtm4KzwBMtCj2QdOZUxRG8u/MdKAcH/ethuhKZnqbzt1XnBuTLsBmXuZ/h8Ba LWFJ/XfP6zYf1FEWqmLd6u2Ws9aQQe0wEN68uN34JDfdy9ofIfACIpgkndnC1dKFVIBO t+avvYamrpxzBl5qhsikz3CwOniNpqNf/kESyeXh0rtafV4lsJTJwey0j9Y8hJeHFuiT tlAg==
X-Gm-Message-State: AOAM533brQJ30eDlD2WcLqME2XcZnoNhwURVX7k+a9gzSj1YaUXc8X2/ 46jguW5NCjcQcXJa6ii1gB8+htTkVG0=
X-Google-Smtp-Source: ABdhPJxrHyuKVnWMBH0bfmsmhxAtZGEfQdqFkSwi+B3KcC8EdhC9vM2Ipzo0JBWV/yluxmF9x7LdtQ==
X-Received: by 2002:a05:6a00:1506:b029:18b:5a31:ed87 with SMTP id q6-20020a056a001506b029018b5a31ed87mr4280717pfu.55.1609942324702;  Wed, 06 Jan 2021 06:12:04 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id a1sm2692618pfo.56.2021.01.06.06.12.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 06:12:04 -0800 (PST)
To: Laura Atkins <laura@wordtothewise.com>, IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <659a9162-1b10-6597-a94e-3902193f9b28@gmail.com>
Date: Wed, 6 Jan 2021 06:12:02 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com>
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/wn9QdkWQxIib-vvBJHkYC7qGgDc>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 14:12:07 -0000

On 1/6/2021 2:10 AM, Laura Atkins wrote:
>>> When I first came back and saw the From rewriting I was very 
>>> confused by what it was until I figured out what was going on. 
>>
>> You think you are representative of end users? Try again.
>>
> I think he’s representative of one kind of enduser. 

Each of us is, of course.  But that was not the point in my 
comment/question.

The issue is whether he/you/me are sufficiently representative of an 
'average' user, where average is drawn from a population of millions (or 
these days, possibly billions.)  Because we aren't.

If there were benefit in talking about a highly specialized (and 
extremely tiny) market segment of geek users, then fine.  But we weren't.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Wed Jan  6 06:41:13 2021
Return-Path: <mike@fresheez.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 8BC2A3A0D13 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 06:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 Lq-qwohz8bfR for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 06:41:10 -0800 (PST)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38B013A0D06 for <dmarc@ietf.org>; Wed,  6 Jan 2021 06:41:10 -0800 (PST)
Received: by mail-pl1-x630.google.com with SMTP id 4so1641539plk.5 for <dmarc@ietf.org>; Wed, 06 Jan 2021 06:41:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=0pjvbKkFWKQQonlxkyjYgVp6g35YBzo2j4HXrO966Pk=; b=JWJyy3vtEKJGzTUnstlVF+JqSWBWFa2qT0o0VksEopFMsRJAPzuxQfZvR0mC6AdcZr 7gOnKmYSEm00VYOaAjDnjK219y2fSxvJq3U34GSqiI6uzdL6b0q2tqnyo3kmtJc6/ANJ /INjEtDhbB4k1cetWAnOhP6JRntdzXudswL/mdBZ7K2sUfwLR81y5OB+swzzAM+yPnLp yoaUuujEXduffSwn/tqnIqdFblaqgro27y8bUi0I68ngrThPmWWicV3d8cEC/AfFPfM3 k8PzL4EbEpudiK8OuRtRfxdP1SLffu3g16Cr8yF+4aN6Fy86y+GL1CJflxPreyAoJsRK H/LA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=0pjvbKkFWKQQonlxkyjYgVp6g35YBzo2j4HXrO966Pk=; b=dzFqBGA1+ku8LwTPfQSjczGJ3fiQ/CIuzq/xNUU4Je4tWlbg6bEWUVDKg8avXScTYV TOZl9h8dHFihL4yg05v1gUZkt4X0SWwTlQETEBlgKeH84ZKGTNWvzGYmOUQV2Rvc72WN ONf2wR3IDE/Rrl+AWLB1mnvWeO5eqz9FwfevZuSp5CpU0flf+FJisR1H4/sKgbT+HihO vl1qpWot08qy7yIsYA8OKToZESr5MbDboF3m7JriE5XQYNMQLmlmDqrc/ePsojYe2gbm VzDQ3Iu43i10atX1nW4ks+LJbReYLQOGvojeRgRhJqm/4Kh7oyrSNeqUK0TgrjG5oAw2 N6zg==
X-Gm-Message-State: AOAM533lxLPbyYoUSQdnY/p3gas4aJj/ehR1wU8JZnDGSVfnIzkNIl05 wXQZxNjDXebkp/dD8Tn3RQFLOpdy23GlL273
X-Google-Smtp-Source: ABdhPJx4eHrqpdVcrglv8RVk+XHsd0/nDbbMDdIg3GCoq7ctCUXRmjtUrAFesgdSjES/FCG2gMHb8A==
X-Received: by 2002:a17:90a:7844:: with SMTP id y4mr4664027pjl.68.1609944069279;  Wed, 06 Jan 2021 06:41:09 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id o9sm2535922pjw.9.2021.01.06.06.41.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 06:41:08 -0800 (PST)
To: Dotzero <dotzero@gmail.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <67638446-094e-b598-adc5-dd540c69d487@mtcc.com>
Date: Wed, 6 Jan 2021 06:41:06 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------CDAE27AA21848A7D9ECFD7ED"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Jj08VvA_OucpVUCb7OCVt9XovuE>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 14:41:12 -0000

This is a multi-part message in MIME format.
--------------CDAE27AA21848A7D9ECFD7ED
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/5/21 10:02 PM, Dotzero wrote:
>
>
> On Tue, Jan 5, 2021 at 8:19 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>     No it was an unalloyed good that you brought that up. We can use a
>     much
>     more data-driven approach rather than opinion and conjecture. It
>     would
>     be good for it to be required reading for everybody on this working
>     group, and not snarled at as a heresy. DKIM itself was a leap of
>     faith.
>     16 years later it is gratifying that we have data.
>
>     Mike
>
>
> DKIM was NOT a leap of faith. At the time there was plenty of data 
> from DK (Domain Keys) and IIM to inform those involved. Please stop 
> making assertions of "fact" which are simply not true.
>
Um, dude, I was one of the authors of IIM. You're literally claiming to 
know more than me about what was in my head.

Mike


--------------CDAE27AA21848A7D9ECFD7ED
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/5/21 10:02 PM, Dotzero wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Tue, Jan 5, 2021 at 8:19
            PM Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
              moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
          </div>
          <div> </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            No it was an unalloyed good that you brought that up. We can
            use a much <br>
            more data-driven approach rather than opinion and
            conjecture. It would <br>
            be good for it to be required reading for everybody on this
            working <br>
            group, and not snarled at as a heresy. DKIM itself was a
            leap of faith. <br>
            16 years later it is gratifying that we have data.<br>
            <br>
            Mike<br>
          </blockquote>
          <div><br>
          </div>
          <div>DKIM was NOT a leap of faith. At the time there was
            plenty of data from DK (Domain Keys) and IIM to inform those
            involved. Please stop making assertions of "fact" which are
            simply not true. <br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>Um, dude, I was one of the authors of IIM. You're literally
      claiming to know more than me about what was in my head.<br>
    </p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------CDAE27AA21848A7D9ECFD7ED--


From nobody Wed Jan  6 06:56:35 2021
Return-Path: <mike@fresheez.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 2F85D3A0D47 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 06:56:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 o7de8ai7sjMz for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 06:56:33 -0800 (PST)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 041E73A0825 for <dmarc@ietf.org>; Wed,  6 Jan 2021 06:56:32 -0800 (PST)
Received: by mail-pj1-x102c.google.com with SMTP id j13so1706323pjz.3 for <dmarc@ietf.org>; Wed, 06 Jan 2021 06:56:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=oWuA1lUmvKJAViYnpswNyj+iQ0WT8Dx/dPuAnUsJE0g=; b=Y+Q7IcGgvjNjEljb38vfp4Lt4An1bH9HlbxmOn6Xiz6zUK+5F4niZdWZnzf9EWXDML 9To3H1Cd28GPNhF0+UgyacaxKJ2Tvh7bayVZwnDGCuSVxDXegI6Va8e1PKFdm9FEOQt8 qtoOY0+DTCJJwBwsxsWWgeITs0e9PHJaARY7uElQQqQfWMwJh1gyOzla8d0puCRxelM8 hTksxaw638qYyvH5xduBrFjm8Gma5ZMdJT6zmDuWzB9jF7WheoL9ztTHLbXIaxaYwYNb iDUfb0ddd7l9tEsazGaatgwbqeLTy3witYxbjVhcKGbl+HQjzpZu4AXRPD6CjSLAn07U LNQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=oWuA1lUmvKJAViYnpswNyj+iQ0WT8Dx/dPuAnUsJE0g=; b=iFEtM6Qt1CedVXbrWm5Uf6xQK9rgOIqDGj4Ct4PU5o4wxopKnK9yWdzikISH8zhx3B hp4RLb1R9XrrYcqarrOnXvy4tup0cYz8nAGKlWjEte232Hgzw6iZ0wx13c51Mxa0jJcQ EDt9fTVZkuDzOlQpKV76KhiAufAlU+G1uwvm8EopN3ZEaJY/XGdvXkB8Fz1gWINJl2e7 FfAi18YfNBE6YOwGDYP5kXDSTOgXGkyu8FGFuEVj7m6fDtGEUPCdjsRqDEDLpwMd7NJG W9aYTyLYN1ZyCUryKEV4IqS1ZIVST6GciB1g5qjPWjV9QE3YhoB3ZQw1ogfhlJkOzCR8 nbqg==
X-Gm-Message-State: AOAM5314BNGyIy73MvoERJBNe1U1AyUztpyVC36Vw0dJf/sAsWLCFnPd KzmekdM+5kxmxoqIjW4XSD4ZI0o44l5Zlbnk
X-Google-Smtp-Source: ABdhPJx7/P9mZykroze/Q7fBCLcpWNZ+qn7V6lVDcIIERedefpdfvJ2/lyg9EjaBRwMkwqp1lKfxYg==
X-Received: by 2002:a17:902:9b8a:b029:dc:3baf:201e with SMTP id y10-20020a1709029b8ab02900dc3baf201emr4628537plp.15.1609944990881;  Wed, 06 Jan 2021 06:56:30 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id t5sm2531469pjr.22.2021.01.06.06.56.29 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 06:56:30 -0800 (PST)
To: dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <039e5632-c08d-65d4-5c09-3906cee97264@mtcc.com>
Date: Wed, 6 Jan 2021 06:56:29 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com>
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/-jlemmmPF-gzeMuGDRItImgxero>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 14:56:34 -0000

On 1/6/21 2:10 AM, Laura Atkins wrote:
>
> 2. A single study is unlikely to be definitive about much of anything.
>
> Absolutely true.
>
> Anyone relying on a single piece of evidence to prove their point is 
> wrong. I am absolutely sure there is a bigger body of research out 
> there and more data. In fact, I was at a conference in SF many years 
> ago reporting a study done between a mailbox provider and a large 
> sender of email. Their study showed quite definitively that visual 
> indicators in email do not affect user behavior in any statistically 
> meaningful way.

Dave made a categorical statement that the only thing that can have an 
effect on phishing is filters. I provided that study as a counterpoint 
which does not support his categorical assertion. He then tried to 
assert that something completely irrelevant to email is pertinent to 
prove his point: another one off study which is irrelevant to email. At 
the very least categorical statements in the face of little data are 
ridiculous, and should be ignored.


> I think he’s representative of one kind of enduser. He’s getting a 
> trust indicator in email (DMARC fails) and doesn’t understand what 
> that indicator means or implies. When I shared the relevant piece of 
> the DMARC spec causing the DMARC failure he told me that was ‘all 
> gobbledygook’ and that alignment wasn’t even part of DMARC.
>
I beg your pardon. I designed and implemented SSP. If you don't know 
what this is, you are unqualified to tell me what I do or don't 
understand. Take your ad hominems elsewhere.

Mike, newbies



From nobody Wed Jan  6 06:59:54 2021
Return-Path: <dotzero@gmail.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 D142E3A0DFC for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 06:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Or9qwrj3sFeJ for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 06:59:51 -0800 (PST)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C1CE3A0DD9 for <dmarc@ietf.org>; Wed,  6 Jan 2021 06:59:51 -0800 (PST)
Received: by mail-qv1-xf29.google.com with SMTP id p12so1279866qvj.13 for <dmarc@ietf.org>; Wed, 06 Jan 2021 06:59:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kOhQzjbpQPrV7ZUyPvbawLo2a2QJKDQxkIzHrU1KBSI=; b=bm8+s5WS0kZlHEoxibO2XSQTpjuaK4dv9OPaCklBJOQL8FLHC6PKv9D9FXUuut1V5H Y21imEeWuI2YRmhU39ObvosQnaPOkK2rpHueNSM5T3C25wc15FZ69afy7ExXngkbl6o/ 230NyFS5LHsl1jmeZwIcfbvP3DJo94FzmwSZ60aRCSqAikgsKjicPdRl+MgHgzFn93cn tOmFuBNMAwq8fO5BMzvRcFQetnJxrvkirHr7z8QTYVhwoe1oSYd7zuYZklPGzXxfYWDf Yw3HZzE8eiLHPkTr6+v1p27ucGgkU1jfZ8WItsH6qUcLGECAaF84XxSdtERRRWFrg4FE KhAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kOhQzjbpQPrV7ZUyPvbawLo2a2QJKDQxkIzHrU1KBSI=; b=B4qSfM1LCA5+U6lo+0xru8cY+Ru1fAV9d47G4FRvkMQ64hvRjF0Llynss08d7swK3C 2NaYJ4/PReT2uVLFFiprObJam1ARRUOoJiHm3GX7CMdTM2p+D/O39IPGgTBjsGOOpNw0 ibMDuSRb1AtxSTa4/GqXxTtFCWS5ldfMrDimMPsKEXMSwbTU/TyDbbddvjBGbtJPWevN UzkDbQ1cmn25+KYGaxAYFoTl4xJSqXwBSg1u69iPfG9W0LC5zC84o0rhVb7QbnrV1M5U 6U7Cno+EUKFzgm8VZzFDbs2g7jD6LscmBHKJTztcDRiWPAhL7HPQRN8UPeTyxevvesKL QsCw==
X-Gm-Message-State: AOAM530DHkBJrbQ/IHfGzR3ByzFUHLF2DYd6c58WWl+7LTV2iY6MLWaJ i7Xx9d5A7J+kwIkCcUozCTQpWeNfIseLA9rEyT4=
X-Google-Smtp-Source: ABdhPJxKuFup1vDj8ABZknF/XciibJ2xwj9dMNZD5jmgQ7X2k2y9FtEJ18bNfJRj2XiarMi8JNKkS4MMP+TqAc0uGPg=
X-Received: by 2002:a0c:f283:: with SMTP id k3mr4171353qvl.48.1609945190382; Wed, 06 Jan 2021 06:59:50 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com>
In-Reply-To: <67638446-094e-b598-adc5-dd540c69d487@mtcc.com>
From: Dotzero <dotzero@gmail.com>
Date: Wed, 6 Jan 2021 09:59:39 -0500
Message-ID: <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002e439505b83c93e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/6y23CpCM0MonhEehyCQBPnTcqIw>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 14:59:53 -0000

--0000000000002e439505b83c93e7
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 6, 2021 at 9:41 AM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/5/21 10:02 PM, Dotzero wrote:
>
>
>
> On Tue, Jan 5, 2021 at 8:19 PM Michael Thomas <mike@mtcc.com> wrote:
>
>
>> No it was an unalloyed good that you brought that up. We can use a much
>> more data-driven approach rather than opinion and conjecture. It would
>> be good for it to be required reading for everybody on this working
>> group, and not snarled at as a heresy. DKIM itself was a leap of faith.
>> 16 years later it is gratifying that we have data.
>>
>> Mike
>>
>
> DKIM was NOT a leap of faith. At the time there was plenty of data from DK
> (Domain Keys) and IIM to inform those involved. Please stop making
> assertions of "fact" which are simply not true.
>
> Um, dude, I was one of the authors of IIM. You're literally claiming to
> know more than me about what was in my head.
>
> Mike
>

So all the data was in your head? I wasn't using IIM but was publishing DK
and getting feedback from Yahoo! and a few other receivers through private
channels. There were other senders in a similar situation as myself. And
yes, people were discussing things privately (Web of Trust groups). Your
claim that there was no data available at the time is quite simply false.

Michael Hammer

--0000000000002e439505b83c93e7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 6, 2021 at 9:41 AM Michae=
l Thomas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/5/21 10:02 PM, Dotzero wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr"><br>
        </div>
        <br>
        <div class=3D"gmail_quote">
          <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 5, 2021 at 8:19
            PM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=
=3D"_blank">mike@mtcc.com</a>&gt; wrote:<br>
          </div>
          <div>=C2=A0</div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            No it was an unalloyed good that you brought that up. We can
            use a much <br>
            more data-driven approach rather than opinion and
            conjecture. It would <br>
            be good for it to be required reading for everybody on this
            working <br>
            group, and not snarled at as a heresy. DKIM itself was a
            leap of faith. <br>
            16 years later it is gratifying that we have data.<br>
            <br>
            Mike<br>
          </blockquote>
          <div><br>
          </div>
          <div>DKIM was NOT a leap of faith. At the time there was
            plenty of data from DK (Domain Keys) and IIM to inform those
            involved. Please stop making assertions of &quot;fact&quot; whi=
ch are
            simply not true. <br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>Um, dude, I was one of the authors of IIM. You&#39;re literally
      claiming to know more than me about what was in my head.<br>
    </p>
    <p>Mike<br></p></div></blockquote><div><br></div><div>So all the data w=
as in your head? I wasn&#39;t using IIM but was publishing DK and getting f=
eedback from Yahoo! and a few other receivers through private channels. The=
re were other senders in a similar situation as myself. And yes, people wer=
e discussing things privately (Web of Trust groups). Your claim that there =
was no data available at the time is quite simply false. <br></div><div><br=
></div><div>Michael Hammer<br></div></div></div>

--0000000000002e439505b83c93e7--


From nobody Wed Jan  6 07:07:45 2021
Return-Path: <mike@fresheez.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 3ACA93A0E31 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 7W1bZaj1AKPj for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:07:41 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAD923A0E1D for <dmarc@ietf.org>; Wed,  6 Jan 2021 07:07:41 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id 30so2407069pgr.6 for <dmarc@ietf.org>; Wed, 06 Jan 2021 07:07:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=7dKXODBem6Ii/6verLPzuxc04ur+FX/pdbl5N0Ylbio=; b=foO6AYdgtm1+s+pZBlkWxaKx60wgTXJTq741Ph8gfdzlPW7eaVIQsmngJL7an2+N3K 2DKEaKgahf/L5w/lAMSUWSTvyhd4UtgyH5UKGTxJJZPrdy3KgtrbKniAfRlAvDMme7ue 45tR1joPMtbFVIZQzpAeWuYAFgt/cWUpHyqTcCAL4Clt+ySj5BQAt7fzHQpu2bL+Li/y ft+WRGI58S2giZqoExRHQ3aSkrvcubeOC47PSp4jJftm7v7Ce/hawLeAz8MUjvQ65qcD sE+qDjEA3gcLWtAazWhluk4YiHWEtJMGPLoRgdEXOFtxD4fMNCSbrQcxmM+whui/j3qQ qytQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=7dKXODBem6Ii/6verLPzuxc04ur+FX/pdbl5N0Ylbio=; b=kyj96sKpog9jTVNeyIAdXFGkuxWXcLOXV71V+S7YLhjfhd0Rulnc4r7xzbmURjLa9a MV7PFzm/a9O4KzVU/cKwstHM1mKhRZVe5WRev1x/XCCK/Ucm5yuX0o6Zldu++ARum7PC uWrb9SSuCPKCnsCzF4GLZS3nKRgy2S9hc2+aTPQUM1UPlh2NvCOdTong7eQZt5L+9mjw /dU1Oc1tAdgQ6NZrLoYXLrRK+vp8g58rGDFGvPbSSI0ajGplSkEZQ1Y47sLRPft6RP9c SwkSawvk0Ctr4Lk6yoIMDO4+5ZyM4tv6JehTnvankn/VeOM5PGfG0HqO//gwQ5Gsyd6B E0UQ==
X-Gm-Message-State: AOAM5310iTwWtUjVkZ7FmUVsIk4has3vHgoyCTNNIOwIK6UhRzM4bsRc p+qq5hk5UnMHWdJR4ejhfvAU++4WXXXnh8Rn
X-Google-Smtp-Source: ABdhPJwC9S69ogfFPL795dY1LvRQlbLK5Aov6sjFYuvqB7GcxmOp4rCxdfDbg8YnGXpW6NWlZyRXjg==
X-Received: by 2002:a63:308:: with SMTP id 8mr4943692pgd.15.1609945660860; Wed, 06 Jan 2021 07:07:40 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id 9sm2902307pfn.188.2021.01.06.07.07.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 07:07:40 -0800 (PST)
To: Dotzero <dotzero@gmail.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com> <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com>
Date: Wed, 6 Jan 2021 07:07:38 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------F2C6870C185FF9AC7CB9F672"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YhZHWCdSZCRc9n01UE5aj5GoTWk>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 15:07:43 -0000

This is a multi-part message in MIME format.
--------------F2C6870C185FF9AC7CB9F672
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/6/21 6:59 AM, Dotzero wrote:
>
>
> On Wed, Jan 6, 2021 at 9:41 AM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     On 1/5/21 10:02 PM, Dotzero wrote:
>>
>>
>>     On Tue, Jan 5, 2021 at 8:19 PM Michael Thomas <mike@mtcc.com
>>     <mailto:mike@mtcc.com>> wrote:
>>
>>         No it was an unalloyed good that you brought that up. We can
>>         use a much
>>         more data-driven approach rather than opinion and conjecture.
>>         It would
>>         be good for it to be required reading for everybody on this
>>         working
>>         group, and not snarled at as a heresy. DKIM itself was a leap
>>         of faith.
>>         16 years later it is gratifying that we have data.
>>
>>         Mike
>>
>>
>>     DKIM was NOT a leap of faith. At the time there was plenty of
>>     data from DK (Domain Keys) and IIM to inform those involved.
>>     Please stop making assertions of "fact" which are simply not true.
>>
>     Um, dude, I was one of the authors of IIM. You're literally
>     claiming to know more than me about what was in my head.
>
>     Mike
>
>
> So all the data was in your head? I wasn't using IIM but was 
> publishing DK and getting feedback from Yahoo! and a few other 
> receivers through private channels. There were other senders in a 
> similar situation as myself. And yes, people were discussing things 
> privately (Web of Trust groups). Your claim that there was no data 
> available at the time is quite simply false.
>
You are literally telling me what I knew at the time. It was a lot of 
the reason that we got push back to form the DKIM working group. It 
wasn't until I read that paper that I got some concrete feel for how it 
affected things, and that was 16 years later. The biggest change for the 
better was senders closing open relays. It's still not clear that DKIM 
had any affect on that.

Mike


--------------F2C6870C185FF9AC7CB9F672
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/6/21 6:59 AM, Dotzero wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Wed, Jan 6, 2021 at 9:41
            AM Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
              moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p><br>
              </p>
              <div>On 1/5/21 10:02 PM, Dotzero wrote:<br>
              </div>
              <blockquote type="cite">
                <div dir="ltr">
                  <div dir="ltr"><br>
                  </div>
                  <br>
                  <div class="gmail_quote">
                    <div dir="ltr" class="gmail_attr">On Tue, Jan 5,
                      2021 at 8:19 PM Michael Thomas &lt;<a
                        href="mailto:mike@mtcc.com" target="_blank"
                        moz-do-not-send="true">mike@mtcc.com</a>&gt;
                      wrote:<br>
                    </div>
                    <div> </div>
                    <blockquote class="gmail_quote" style="margin:0px
                      0px 0px 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex"> No it was an
                      unalloyed good that you brought that up. We can
                      use a much <br>
                      more data-driven approach rather than opinion and
                      conjecture. It would <br>
                      be good for it to be required reading for
                      everybody on this working <br>
                      group, and not snarled at as a heresy. DKIM itself
                      was a leap of faith. <br>
                      16 years later it is gratifying that we have data.<br>
                      <br>
                      Mike<br>
                    </blockquote>
                    <div><br>
                    </div>
                    <div>DKIM was NOT a leap of faith. At the time there
                      was plenty of data from DK (Domain Keys) and IIM
                      to inform those involved. Please stop making
                      assertions of "fact" which are simply not true. <br>
                    </div>
                    <br>
                  </div>
                </div>
              </blockquote>
              <p>Um, dude, I was one of the authors of IIM. You're
                literally claiming to know more than me about what was
                in my head.<br>
              </p>
              <p>Mike<br>
              </p>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>So all the data was in your head? I wasn't using IIM but
            was publishing DK and getting feedback from Yahoo! and a few
            other receivers through private channels. There were other
            senders in a similar situation as myself. And yes, people
            were discussing things privately (Web of Trust groups). Your
            claim that there was no data available at the time is quite
            simply false. <br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>You are literally telling me what I knew at the time. It was a
      lot of the reason that we got push back to form the DKIM working
      group. It wasn't until I read that paper that I got some concrete
      feel for how it affected things, and that was 16 years later. The
      biggest change for the better was senders closing open relays.
      It's still not clear that DKIM had any affect on that.</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------F2C6870C185FF9AC7CB9F672--


From nobody Wed Jan  6 07:14:27 2021
Return-Path: <mike@fresheez.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 E79E83A119A for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:14:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 fVdLNt-_EKxR for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:14:18 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8FFE3A1026 for <dmarc@ietf.org>; Wed,  6 Jan 2021 07:14:06 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id s21so1849940pfu.13 for <dmarc@ietf.org>; Wed, 06 Jan 2021 07:14:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=lwB1Jai+jLxXDPWpMl/AYZ8sf6P0lOGVJ350taqSCcQ=; b=QU3nT4G5dQs8l5J0Ldnf88GfhcZsAiEUJKqxAIZv3QBPzuJaN8JQ9FpnqxOHwgQUe3 xigzQqjDW70exudpIEOviG8IglgqnEoHm+IFERkVRv5lv5AezqrGlGJQxNIHRtrxrG9C AXMLFVmddp2BotjZKmiidy9SicQPOnXg2WnQrVIuIbUR/8R3ZftSIxWUr0mOsnYlN70H gbh0t0zQmyAnziOJqbPi91Yu8lIYYfK4MRx0ycQQqLIE6/9QoSs7RnvwTOVeqTbZze5c hTJIgLg25dh0icbtUrpoe/IIFxd9TrfjQVTR5S22/zaHVc07yeFA+ab66kBpbWsIEUAU Ve0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=lwB1Jai+jLxXDPWpMl/AYZ8sf6P0lOGVJ350taqSCcQ=; b=cSybyBZKFQJsQHGLsNtvdBvyeXaDYDTrCE8MWcVGrIdmpytmM3Ks3FNmdcGoOlSE11 QYRBMJJC/IFeV41sN5ou7YgetMj/y8p0R28hNwUemwjhnn0V+EVqdy+N2rvJ/lWZQK/t 6NoBoCeXUFzbsDdI33pqQk5TUuGT96tGv6KzSMBafhB1slTZZ7eK6FaUUMEWSTGU3sGQ +p1T3/es47/foiYT50SyHfEbjI3azfoPq45AFVh+Jyn9pXpiHwX6tFZYX4ZvtlwUU24i WoSUPCKBHVFpNrnwuCMT16u2uGda96OdU5wBPoSpxbKnyFr6SaFSqdThjQGxaoeARzxb xoPg==
X-Gm-Message-State: AOAM530bAgOk1299MB+mkFMX1rBvstwiPDU9kbQcLGPOpxpVJ54WUXVQ DDIlImJEAg7MR+lnRLbC9WVBPAQzevH2bGFa
X-Google-Smtp-Source: ABdhPJy728mnZtHAJdBHkllqwTBMIfYweCn3imfu0ryDBj/l6Te+QOLJnRRiFBf4M+AMXkWGbX8dIQ==
X-Received: by 2002:a63:7746:: with SMTP id s67mr4970922pgc.91.1609946045890;  Wed, 06 Jan 2021 07:14:05 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id a136sm3181409pfd.149.2021.01.06.07.14.04 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 07:14:05 -0800 (PST)
To: dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com> <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com> <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <b4c0e4fd-30a3-bacb-742f-ae611109af84@mtcc.com>
Date: Wed, 6 Jan 2021 07:14:04 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
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/j-YHeIGWW1qerb1G4qTUGZ-iHmY>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 15:14:26 -0000

On 1/6/21 4:52 AM, Laura Atkins wrote:
>
> Most users may know who constantcontact are or mailchimp because they 
> advertise widely. Some might have heard of GoDaddy but do you know 
> what the company name of the GoDaddy ESP is? I don’t off the top of my 
> head.

An extremely dubious assertion. Source? I barely know who they are and 
could not name them unless I saw their names first.

Mike


From nobody Wed Jan  6 07:18:59 2021
Return-Path: <dotzero@gmail.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 8C16A3A0EC8 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Bq9JVQDbXRle for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:18:57 -0800 (PST)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CC603A0F0E for <dmarc@ietf.org>; Wed,  6 Jan 2021 07:18:05 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id w79so2693109qkb.5 for <dmarc@ietf.org>; Wed, 06 Jan 2021 07:18:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ipi5BJjPtziySF7KpFIW9XwI1d4iSdgHiCkiDObCjGc=; b=cOXas9TwTxV+nw0RFxNkt6LNBU1xdPgFN7sHMpn4gsiAGbNLNJwiHWAgaWnnXXnLH3 vRdGO0kY9RbFPT0AaShKx0IhOhGMOTcxdyq1z7q1vtdkSTHHaXsGCdMyQapzHYZgXw1h eaMcfWw2sgHYlDlUlhNYYooPFYBKUs+mw+uerIQ3MuMps93WWjZ0zBcaFHKlEX7sVDhG UxlkShWsPeMDwzTSmUGydEQtw5bSx1QMW48aclz3e8MDUqmMSpiWEePrC3/TFVpXsYT1 IyQ1ps7fow6aqmqPr3ap5Qa/4b9u+izm3Czhrgc0mWC6DesKYEBs1rbTFrKCwnIsMbE9 4umQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ipi5BJjPtziySF7KpFIW9XwI1d4iSdgHiCkiDObCjGc=; b=QKYFsQsHnMyr0FTS5c3PL3sxPrAozom3UkMjT6AGmKNHfU6oN3qTl/xYDRWn7UaIre A+ZCZYlbbOkGNv80n6MHoaMDp7wHw3uvcd3AQQpGXOKmRoPO8vCE8gDw1/jkwnrboOom YfxJvcFyW0LMRzJ1Ev3pbRRFJZqX+jamcXuP/o8L1VNRIjtO+sJoyvx3V/vA1UoY87zI MCz0Et2+5SK0o7D8haYqkPG6WtrlhrPXSBqsCc/sntk2XO9JYnWyW2Fmu/lZxEIbjAyM a1r1AzKbP7xeiEAavzPo8CtSMYUEnrzlqZZUbYwlkkc63y7n2eoHxfU8GT1EFKQFEhRl AvWA==
X-Gm-Message-State: AOAM531kDeo6f8VspxIYYMJDeWR3lFdHJpuPLcL5SjpyPQcrWITLE/fi 1tjpQBaSDaDdDN6gqWhAck3HiJNuzW0YvPOego4=
X-Google-Smtp-Source: ABdhPJz/1phJ2Rff2tKPtTKhJ2TnwMKrvyWgdfIKMGfemMiLwFCyRzBbwyOyWj0ISGsipvESvqLFLajKcP7n0MVF5tE=
X-Received: by 2002:a05:620a:f92:: with SMTP id b18mr4768553qkn.146.1609946284542;  Wed, 06 Jan 2021 07:18:04 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com> <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com> <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com>
In-Reply-To: <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com>
From: Dotzero <dotzero@gmail.com>
Date: Wed, 6 Jan 2021 10:17:54 -0500
Message-ID: <CAJ4XoYfjdFJ8sRu8WybkgN_qkK5w4iQ-6WuJ-y6cEuZ3OGMUKw@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000065d04705b83cd4dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QqQf7vv1r9wDmdpAm-j_m8UKyNU>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 15:18:59 -0000

--00000000000065d04705b83cd4dd
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 6, 2021 at 10:07 AM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/6/21 6:59 AM, Dotzero wrote:
>
>
>
> On Wed, Jan 6, 2021 at 9:41 AM Michael Thomas <mike@mtcc.com> wrote:
>
>>
>> On 1/5/21 10:02 PM, Dotzero wrote:
>>
>>
>>
>> On Tue, Jan 5, 2021 at 8:19 PM Michael Thomas <mike@mtcc.com> wrote:
>>
>>
>>> No it was an unalloyed good that you brought that up. We can use a much
>>> more data-driven approach rather than opinion and conjecture. It would
>>> be good for it to be required reading for everybody on this working
>>> group, and not snarled at as a heresy. DKIM itself was a leap of faith.
>>> 16 years later it is gratifying that we have data.
>>>
>>> Mike
>>>
>>
>> DKIM was NOT a leap of faith. At the time there was plenty of data from
>> DK (Domain Keys) and IIM to inform those involved. Please stop making
>> assertions of "fact" which are simply not true.
>>
>> Um, dude, I was one of the authors of IIM. You're literally claiming to
>> know more than me about what was in my head.
>>
>> Mike
>>
>
> So all the data was in your head? I wasn't using IIM but was publishing DK
> and getting feedback from Yahoo! and a few other receivers through private
> channels. There were other senders in a similar situation as myself. And
> yes, people were discussing things privately (Web of Trust groups). Your
> claim that there was no data available at the time is quite simply false.
>
> You are literally telling me what I knew at the time. It was a lot of the
> reason that we got push back to form the DKIM working group. It wasn't
> until I read that paper that I got some concrete feel for how it affected
> things, and that was 16 years later. The biggest change for the better was
> senders closing open relays. It's still not clear that DKIM had any affect
> on that.
>
> Mike
>

No, you are literally telling everyone else how things were. In fact, there
was a lot of data. You are the one who claimed that everything was in your
head and the rest of us have no clue. - "DKIM itself was a leap of faith"
and that we were doing things based on opinion and conjecture. It did not
take 16 years for there to be data. There was data before DK and IIM were
merged to form DKIM.

Michael Hammer

--00000000000065d04705b83cd4dd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 6, 2021 at 10:07 AM Micha=
el Thomas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/6/21 6:59 AM, Dotzero wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr"><br>
        </div>
        <br>
        <div class=3D"gmail_quote">
          <div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 6, 2021 at 9:41
            AM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=
=3D"_blank">mike@mtcc.com</a>&gt; wrote:<br>
          </div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <p><br>
              </p>
              <div>On 1/5/21 10:02 PM, Dotzero wrote:<br>
              </div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div dir=3D"ltr"><br>
                  </div>
                  <br>
                  <div class=3D"gmail_quote">
                    <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 5,
                      2021 at 8:19 PM Michael Thomas &lt;<a href=3D"mailto:=
mike@mtcc.com" target=3D"_blank">mike@mtcc.com</a>&gt;
                      wrote:<br>
                    </div>
                    <div>=C2=A0</div>
                    <blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> No i=
t was an
                      unalloyed good that you brought that up. We can
                      use a much <br>
                      more data-driven approach rather than opinion and
                      conjecture. It would <br>
                      be good for it to be required reading for
                      everybody on this working <br>
                      group, and not snarled at as a heresy. DKIM itself
                      was a leap of faith. <br>
                      16 years later it is gratifying that we have data.<br=
>
                      <br>
                      Mike<br>
                    </blockquote>
                    <div><br>
                    </div>
                    <div>DKIM was NOT a leap of faith. At the time there
                      was plenty of data from DK (Domain Keys) and IIM
                      to inform those involved. Please stop making
                      assertions of &quot;fact&quot; which are simply not t=
rue. <br>
                    </div>
                    <br>
                  </div>
                </div>
              </blockquote>
              <p>Um, dude, I was one of the authors of IIM. You&#39;re
                literally claiming to know more than me about what was
                in my head.<br>
              </p>
              <p>Mike<br>
              </p>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>So all the data was in your head? I wasn&#39;t using IIM but
            was publishing DK and getting feedback from Yahoo! and a few
            other receivers through private channels. There were other
            senders in a similar situation as myself. And yes, people
            were discussing things privately (Web of Trust groups). Your
            claim that there was no data available at the time is quite
            simply false. <br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>You are literally telling me what I knew at the time. It was a
      lot of the reason that we got push back to form the DKIM working
      group. It wasn&#39;t until I read that paper that I got some concrete
      feel for how it affected things, and that was 16 years later. The
      biggest change for the better was senders closing open relays.
      It&#39;s still not clear that DKIM had any affect on that.</p>
    <p>Mike<br></p></div></blockquote><div><br></div><div>No, you are liter=
ally telling everyone else how things were. In fact, there was a lot of dat=
a. You are the one who claimed that everything was in your head and the res=
t of us have no clue. -=20
&quot;DKIM itself
                      was a leap of faith&quot; and that we were doing thin=
gs based on opinion and conjecture. It did not take 16 years for there to b=
e data. There was data before DK and IIM were merged to form DKIM.<br></div=
><div><br></div><div>Michael Hammer<br></div></div></div>

--00000000000065d04705b83cd4dd--


From nobody Wed Jan  6 07:20:13 2021
Return-Path: <laura@wordtothewise.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 5D5083A0E8D for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:20:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
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 xqhegZchprN2 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:20:11 -0800 (PST)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id EA5C23A0E8A for <dmarc@ietf.org>; Wed,  6 Jan 2021 07:20:10 -0800 (PST)
Received: from [192.168.0.227] (unknown [37.228.231.27]) by mail.wordtothewise.com (Postfix) with ESMTPSA id E72F69F149 for <dmarc@ietf.org>; Wed,  6 Jan 2021 07:20:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1609946410; bh=SrfF/2vBxPYrZqkLOz2glqEioc4DhToE02ANY4ailSU=; h=From:Subject:Date:References:To:In-Reply-To:From; b=gftGLlHZzey8Xx4LmTrBg5qRTns2XZhEjh/Uq27zvVzS8kd+fMnT7thFWNmMtYup3 /BrFKVsya/5X9EUiMrxK4c/TBopwj17WTnbN3vFT8XkQvbUgf9G3U9XmPPsz7w/R48 1rB2TjjoEEnb505YwuCqlxkAu12xvSvshoNwX5So=
From: Laura Atkins <laura@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F01B7247-634E-4FE0-93BC-8667B4E515EC"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 6 Jan 2021 15:20:08 +0000
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com> <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com> <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com> <b4c0e4fd-30a3-bacb-742f-ae611109af84@mtcc.com>
To: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <b4c0e4fd-30a3-bacb-742f-ae611109af84@mtcc.com>
Message-Id: <B705BC02-824F-4F83-B0D9-EF9349410A56@wordtothewise.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jKcL3Yoq7PyxkY9RtbLQRS1raXw>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 15:20:12 -0000

--Apple-Mail=_F01B7247-634E-4FE0-93BC-8667B4E515EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 6 Jan 2021, at 15:14, Michael Thomas <mike@mtcc.com> wrote:
>=20
>=20
> On 1/6/21 4:52 AM, Laura Atkins wrote:
>>=20
>> Most users may know who constantcontact are or mailchimp because they =
advertise widely. Some might have heard of GoDaddy but do you know what =
the company name of the GoDaddy ESP is? I don=E2=80=99t off the top of =
my head.
>=20
> An extremely dubious assertion. Source? I barely know who they are and =
could not name them unless I saw their names first.


That was actually my point. One you decided to clipp out of the email =
you=E2=80=99re replying to. Having these companies rewrite the 5322.from =
address to domains they control does not increase security. It is an end =
run around the small amount of protection DMARC offers and is a bad =
idea.=20

laura=20

--=20
Having an Email Crisis?  We can help! 800 823-9674=20

Laura Atkins
Word to the Wise
laura@wordtothewise.com
(650) 437-0741	=09

Email Delivery Blog: https://wordtothewise.com/blog=09








--Apple-Mail=_F01B7247-634E-4FE0-93BC-8667B4E515EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 6 Jan 2021, at 15:14, Michael Thomas &lt;<a =
href=3D"mailto:mike@mtcc.com" class=3D"">mike@mtcc.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D""><br class=3D"">On 1/6/21 4:52 AM, Laura Atkins wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Most =
users may know who constantcontact are or mailchimp because they =
advertise widely. Some might have heard of GoDaddy but do you know what =
the company name of the GoDaddy ESP is? I don=E2=80=99t off the top of =
my head.<br class=3D""></blockquote><br class=3D"">An extremely dubious =
assertion. Source? I barely know who they are and could not name them =
unless I saw their names first.<br =
class=3D""></div></div></blockquote></div><div><br =
class=3D""></div><div>That was actually my point. One you decided to =
clipp out of the email you=E2=80=99re replying to. Having these =
companies rewrite the 5322.from address to domains they control does not =
increase security. It is an end run around the small amount of =
protection DMARC offers and is a bad idea.&nbsp;</div><div><br =
class=3D""></div><div>laura&nbsp;</div><br class=3D""><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px; font-family: Helvetica; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal;"><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
class=3D"">--&nbsp;</div><div class=3D"">Having an Email Crisis? =
&nbsp;We can help! 800 823-9674&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Laura Atkins</div><div class=3D"">Word =
to the Wise</div><div class=3D""><a =
href=3D"mailto:laura@wordtothewise.com" =
class=3D"">laura@wordtothewise.com</a></div><div class=3D"">(650) =
437-0741<span class=3D"Apple-tab-span" style=3D"white-space: pre;">		=
</span></div><div class=3D""><br =
class=3D""></div></span></span></span></span></span></div><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;">Email Delivery Blog: <a =
href=3D"https://wordtothewise.com/blog" =
class=3D"">https://wordtothewise.com/blog</a><span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span></span></span></span></span></span></div></span></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_F01B7247-634E-4FE0-93BC-8667B4E515EC--


From nobody Wed Jan  6 07:23:23 2021
Return-Path: <mike@fresheez.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 F14533A0E8C for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 jcS76e8yHXJG for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:23:20 -0800 (PST)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 999DB3A0E8A for <dmarc@ietf.org>; Wed,  6 Jan 2021 07:23:20 -0800 (PST)
Received: by mail-pg1-x52f.google.com with SMTP id i5so2458878pgo.1 for <dmarc@ietf.org>; Wed, 06 Jan 2021 07:23:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=CVb7SfPU262txKJC+bW8wHA9Au8AzoFrg3aMoD/9l8Q=; b=gr9Z/HWidv4JXt+rFhdbJ5kYKFRQW/KRUx6ZYLxKbW0qjVhok8qv8Gv8CASj05YnzX umvklyGBb2CgwLXFCsbQb5sXt/E5C32s08+BFdY7UBGsChX7v8pDHHbOPcUlO88ZEVBn k2TPWCAqzFRaHGZus/dsnG4wG78DuS4r6MkPmK5ewq2vnf3TGzUZm2mRqkmzc/+yAtkQ om6QytmIUsAmM2XdTYH+qCr3b928WBlI2k/0RQYIVxRx3ao9YJpKFnPmgckYOHC8HVNb xD3sXfT+eBmiJJKWpX24k0vK6antbZiCO+3t1Xi8krEt4XqIbZuVNlZVuxlOf4hO7AHJ LYFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=CVb7SfPU262txKJC+bW8wHA9Au8AzoFrg3aMoD/9l8Q=; b=Cb3QnHtDRNEvxApm5bsglYur8+kt6CEKUmiJH8JRTKko7sCl5u7pfZqOK5g65XqfeS gBOwbMnAwwQTo6Knya18IqsDMhFMMGaAltfdGJM6/1Z6ag+4Gp2w9erVU8Am8aEAD2as N6ipqodv+rrlpc+bCiAdTQi5XWNGtH7li68OaHiW+Ukc+LVIb0UiUeDXXdJGqggz9jCG 8Apd0zlJUELm+yXkZOgUhRtIHKhFHP7OG3L5C8TtDlh5h5mJJDT+G47LaVX5HO2RgNoy ekZlF4OI90HaprjhU55x2Vp8Sm9W3qW+DX0ZPW0t77efwuaJskLK6LpMrV2ZKMt7Jmx+ kMww==
X-Gm-Message-State: AOAM532+5c8f1xOpfGVrZVKy52pYHUymcqWIomKFjcq5m5ZsLDNJQMOE qLlesfmumoPOwdHHvicWfiCbGR0374S6jJ9S
X-Google-Smtp-Source: ABdhPJwlIoVaGLplg3ZH762LT1h/3pHN9V9IqqgfjMP60KSHTWlKw5C2PU3ts4YXm2xNuycwja8cmg==
X-Received: by 2002:a62:4e4e:0:b029:19e:aaab:8be with SMTP id c75-20020a624e4e0000b029019eaaab08bemr4588156pfb.59.1609946599599;  Wed, 06 Jan 2021 07:23:19 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id r79sm2957850pfc.166.2021.01.06.07.23.18 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 07:23:18 -0800 (PST)
To: dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com> <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com> <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com> <b4c0e4fd-30a3-bacb-742f-ae611109af84@mtcc.com> <B705BC02-824F-4F83-B0D9-EF9349410A56@wordtothewise.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <51e3cd47-3cee-6ea8-b078-821897421821@mtcc.com>
Date: Wed, 6 Jan 2021 07:23:17 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <B705BC02-824F-4F83-B0D9-EF9349410A56@wordtothewise.com>
Content-Type: multipart/alternative; boundary="------------25093D5C34B6CD0FBE4759AA"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/EwhIjgPp5r_Tt3SQsvxjQYiwkKw>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 15:23:22 -0000

This is a multi-part message in MIME format.
--------------25093D5C34B6CD0FBE4759AA
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/6/21 7:20 AM, Laura Atkins wrote:
>
>
>> On 6 Jan 2021, at 15:14, Michael Thomas <mike@mtcc.com 
>> <mailto:mike@mtcc.com>> wrote:
>>
>>
>> On 1/6/21 4:52 AM, Laura Atkins wrote:
>>>
>>> Most users may know who constantcontact are or mailchimp because 
>>> they advertise widely. Some might have heard of GoDaddy but do you 
>>> know what the company name of the GoDaddy ESP is? I don’t off the 
>>> top of my head.
>>
>> An extremely dubious assertion. Source? I barely know who they are 
>> and could not name them unless I saw their names first.
>
> That was actually my point. One you decided to clipp out of the email 
> you’re replying to. Having these companies rewrite the 5322.from 
> address to domains they control does not increase security. It is an 
> end run around the small amount of protection DMARC offers and is a 
> bad idea.
>
I agree about From rewriting. But your assertion here is extremely 
dubious. But mailing lists should just die, IMO.

https://rip-van-webble.blogspot.com/2020/12/are-mailing-lists-toast.html

Mike


--------------25093D5C34B6CD0FBE4759AA
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/6/21 7:20 AM, Laura Atkins wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:B705BC02-824F-4F83-B0D9-EF9349410A56@wordtothewise.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <br class="">
      <div><br class="">
        <blockquote type="cite" class="">
          <div class="">On 6 Jan 2021, at 15:14, Michael Thomas &lt;<a
              href="mailto:mike@mtcc.com" class=""
              moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:</div>
          <br class="Apple-interchange-newline">
          <div class="">
            <div class=""><br class="">
              On 1/6/21 4:52 AM, Laura Atkins wrote:<br class="">
              <blockquote type="cite" class=""><br class="">
                Most users may know who constantcontact are or mailchimp
                because they advertise widely. Some might have heard of
                GoDaddy but do you know what the company name of the
                GoDaddy ESP is? I don’t off the top of my head.<br
                  class="">
              </blockquote>
              <br class="">
              An extremely dubious assertion. Source? I barely know who
              they are and could not name them unless I saw their names
              first.<br class="">
            </div>
          </div>
        </blockquote>
      </div>
      <div><br class="">
      </div>
      <div>That was actually my point. One you decided to clipp out of
        the email you’re replying to. Having these companies rewrite the
        5322.from address to domains they control does not increase
        security. It is an end run around the small amount of protection
        DMARC offers and is a bad idea. </div>
      <br>
    </blockquote>
    <p>I agree about From rewriting. But your assertion here is
      extremely dubious. But mailing lists should just die, IMO.</p>
    <p><a class="moz-txt-link-freetext" href="https://rip-van-webble.blogspot.com/2020/12/are-mailing-lists-toast.html">https://rip-van-webble.blogspot.com/2020/12/are-mailing-lists-toast.html</a><br>
    </p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------25093D5C34B6CD0FBE4759AA--


From nobody Wed Jan  6 07:26:30 2021
Return-Path: <mike@fresheez.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 633A03A0EA4 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:26:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 dZuDTWpo9jn9 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:26:27 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FB7F3A0E9E for <dmarc@ietf.org>; Wed,  6 Jan 2021 07:26:27 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id b5so1764267pjl.0 for <dmarc@ietf.org>; Wed, 06 Jan 2021 07:26:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=DOP/8ksz7W4Xp80xeyfrwFuEr442wcAj71lyXzQqUWE=; b=abcm7cLT59M///UOM4MW3K2WWKsKSl1jVBvTaTk88OLt6M9S95dJLJsZf879L3sJNs 6oVjBV6xwn7uyeURz4eQZ/pxWkYD/q2WYJmysZ/uPOvb4cJyDS8h8WxzGKtV+Gfmwg+A Pe2lUb3lx2xb3MUbMjuN7mbEUfFb7/6mwthWTDrnsgEB3oKBduOv9dOWff4NpJTKl7H/ 7DHM2gyjd78bRdgrdyIPRmGNQQIFP1A2ek08PNZic/Y4pGUYCgSzP1C4J4W9jciT9R1g 2GP5hj7Np2L3h0EgbVggDbdti3WvPYpN7nf1TJneqcj+TJ4NO1RzoVE3rIqMJfOPgoMD X+MQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=DOP/8ksz7W4Xp80xeyfrwFuEr442wcAj71lyXzQqUWE=; b=QlaXPDA4/dPU3Gkkrn9fJaHSiMGOS+L7pmDTsYvzsY3yLxH9atrv27gSOPQXEla9m9 B1pz+wrcS+5h/Xmb+T7Xd5XgRFcxmNYGDk9N2FlWvrNznrDGY0TQfvSBaX7xmdQbUR1x TYo/IetCgJbY8NrV3bgBBCmJTozXWo7q2DIm0Pn3ynzHJf/S/NQFRlPfPbECLZPsWyd5 5AWo+KQ6mTq36JEXtoOYN7hN/QFYSyaOfCl+mTIrBMsYiFD1xHCjUa+SccWYtg9YosYI my7JWRjfKxB93qSICnaSiZiFbac0xb3rGmkXNyMQXBDNa2XNfhXJdZ+YNj+S3bNt8NcJ 4FgA==
X-Gm-Message-State: AOAM531vVmukOEBcZiTAGjlZ1KcY25aGAVjEiDs/bM+qkA2jWWbmpq7B wQTSM77UVMcRC/qf0ovGZFzVsSb4mn0NLg54
X-Google-Smtp-Source: ABdhPJxW7MW63ozfdsZEiIdu07ETO2TnOmR57xhDjuvjfMmmBvnJUyYtAYgpzYrmgIdiJDTBdR05sQ==
X-Received: by 2002:a17:902:7793:b029:da:d44d:1968 with SMTP id o19-20020a1709027793b02900dad44d1968mr4905179pll.47.1609946786043;  Wed, 06 Jan 2021 07:26:26 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id ev23sm2636156pjb.24.2021.01.06.07.26.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 07:26:25 -0800 (PST)
To: Dotzero <dotzero@gmail.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com> <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com> <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com> <CAJ4XoYfjdFJ8sRu8WybkgN_qkK5w4iQ-6WuJ-y6cEuZ3OGMUKw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <da2077f6-8a97-2ea8-bb2f-2a10cb8582e9@mtcc.com>
Date: Wed, 6 Jan 2021 07:26:23 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAJ4XoYfjdFJ8sRu8WybkgN_qkK5w4iQ-6WuJ-y6cEuZ3OGMUKw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A30A3CBDDF55138EFE3C4B45"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4GJLIUkD_0BnloRRzM6z-Zp7boo>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 15:26:28 -0000

This is a multi-part message in MIME format.
--------------A30A3CBDDF55138EFE3C4B45
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/6/21 7:17 AM, Dotzero wrote:You are literally telling me what I 
knew at the time. It was a lot of the reason that we got push back to 
form the DKIM working group. It wasn't until I read that paper that I 
got some concrete feel for how it affected things, and that was 16 years 
later. The biggest change for the better was senders closing open 
relays. It's still not clear that DKIM had any affect on that.
>
>     Mike
>
>
> No, you are literally telling everyone else how things were. In fact, 
> there was a lot of data. You are the one who claimed that everything 
> was in your head and the rest of us have no clue. - "DKIM itself was a 
> leap of faith" and that we were doing things based on opinion and 
> conjecture. It did not take 16 years for there to be data. There was 
> data before DK and IIM were merged to form DKIM.
>
What data? Data that showed what? That's completely news to me. You 
weren't even part of the informal group who caused DKIM to be created, iirc.

Mike


--------------A30A3CBDDF55138EFE3C4B45
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/6/21 7:17 AM, Dotzero wrote:You
      are literally telling me what I knew at the time. It was a lot of
      the reason that we got push back to form the DKIM working group.
      It wasn't until I read that paper that I got some concrete feel
      for how it affected things, and that was 16 years later. The
      biggest change for the better was senders closing open relays.
      It's still not clear that DKIM had any affect on that.</div>
    <blockquote type="cite"
cite="mid:CAJ4XoYfjdFJ8sRu8WybkgN_qkK5w4iQ-6WuJ-y6cEuZ3OGMUKw@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p>Mike<br>
              </p>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>No, you are literally telling everyone else how things
            were. In fact, there was a lot of data. You are the one who
            claimed that everything was in your head and the rest of us
            have no clue. - "DKIM itself was a leap of faith" and that
            we were doing things based on opinion and conjecture. It did
            not take 16 years for there to be data. There was data
            before DK and IIM were merged to form DKIM.<br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>What data? Data that showed what? That's completely news to me.
      You weren't even part of the informal group who caused DKIM to be
      created, iirc.</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------A30A3CBDDF55138EFE3C4B45--


From nobody Wed Jan  6 07:59:24 2021
Return-Path: <superuser@gmail.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 1CB883A1158 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 rkho4D-t92od for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 07:59:14 -0800 (PST)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 205CD3A1322 for <dmarc@ietf.org>; Wed,  6 Jan 2021 07:58:29 -0800 (PST)
Received: by mail-vs1-xe31.google.com with SMTP id j140so2004437vsd.4 for <dmarc@ietf.org>; Wed, 06 Jan 2021 07:58:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bNZuEsCi1TIwVye/w7gU9mzb+ml0HXZt5Dg3Y8y49gs=; b=Bs24NBSOFw/6LPsz1Sv6Q7eYR8EP9bBG2E/4c9k8T4uz7N52tVX1Asn2pBfu3KXBlg 9HhB0cqtrci9uAE64p653vR58SccIn86izeK+juRsZccBZj7XIlNjc6TUL+y1IuD13zP RAbGlK/fiOSb0FMkm3Gh1sqFphSd9Nutzr52j3vJMagOcnBvYFSHYiZ0PJvuHAEIKiBh wAXwxnxBDvF8W9HpKvanloSnBsunZH0ImU+jlbmlz8ENMpdo7RMMaYIb7Y8j8u/op+mJ QGFCWKXJTZplt1U44UQx/8l3xKbO1ovWnyeMPa43lFZgsHlq3EvBr0S8AisbaW0l/+Ey b1zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bNZuEsCi1TIwVye/w7gU9mzb+ml0HXZt5Dg3Y8y49gs=; b=AT3XqyFGGbauTfey/vCLQ9RnAN0RsT9+5o4qpBxfaCaQHBEHqobUD7doi6PflrrUCH 5Hj3WujrDe//FSWsZp64eUv6PuQDR89lN7GJgN2Zi4i19dixwE4xBw3GbH3fBAedmLxG cifArCiqvmEUlEOCbU1qs1ZJvduESCpBX0iL7v9HcJhtoNvws9OQqimDG4Ujvz7aZUzR jowIZrywi8w1s9qHHuWYiO3Bm2afCWuY0194V4WR/rMbq5Rj6gwG50wpnXMVWznsO6i9 LeyqPkCPZmHZwpewjX16Sx89GNJVLfnGuMdZFkSg7kTrzMH0OtcN5gbQ/BCDZNaah1sr lz9Q==
X-Gm-Message-State: AOAM5319epUgUgsgeaPbgv1XgTnYGgiLhIaXNaqs665OHVvYNYzOFH6n hIDlpepAlR3fO1dgtkXhonnkna8F+lGOLy+6OBc=
X-Google-Smtp-Source: ABdhPJwFCNjpCRYcBNIEsM0rkJbLQm3h5yPpfuWb7u+BRXo+XtseHFKj7y41P5CqA16k7160SgkO8ZPtWLhAF+xsraQ=
X-Received: by 2002:a67:2bc2:: with SMTP id r185mr3611969vsr.15.1609948708009;  Wed, 06 Jan 2021 07:58:28 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com> <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com> <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com> <CAJ4XoYfjdFJ8sRu8WybkgN_qkK5w4iQ-6WuJ-y6cEuZ3OGMUKw@mail.gmail.com> <da2077f6-8a97-2ea8-bb2f-2a10cb8582e9@mtcc.com>
In-Reply-To: <da2077f6-8a97-2ea8-bb2f-2a10cb8582e9@mtcc.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 6 Jan 2021 07:58:16 -0800
Message-ID: <CAL0qLwYM3Ct19xdA+Lh-+7JfS-+QqBgJzQRywvWs-ruh0Dqbdw@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: Dotzero <dotzero@gmail.com>, Dave Crocker <dcrocker@gmail.com>,  Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d8f97705b83d641d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/AKKFMdoQaLHgoB-e5CO60uCKVo8>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 15:59:22 -0000

--000000000000d8f97705b83d641d
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 6, 2021 at 7:26 AM Michael Thomas <mike@mtcc.com> wrote:

> No, you are literally telling everyone else how things were. In fact,
> there was a lot of data. You are the one who claimed that everything was in
> your head and the rest of us have no clue. - "DKIM itself was a leap of
> faith" and that we were doing things based on opinion and conjecture. It
> did not take 16 years for there to be data. There was data before DK and
> IIM were merged to form DKIM.
>
> What data? Data that showed what? That's completely news to me. You
> weren't even part of the informal group who caused DKIM to be created, iirc.
>
Everyone,

A working group charter is in some sense a contract between the IESG and
the working group regarding what work it will do, how it will do it, and
what its deliverables are.

I hope it's clear that the discussion taking place here does nothing in
service of that contract.

Please get yourselves back on track without undue delay.

-MSK, your increasingly irritable Area Director

--000000000000d8f97705b83d641d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jan 6, 2021 at 7:26 AM Michael Th=
omas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:</div=
><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div><blockquote type=3D"cite">
      <div dir=3D"ltr"><div class=3D"gmail_quote"><div>No, you are literall=
y telling everyone else how things
            were. In fact, there was a lot of data. You are the one who
            claimed that everything was in your head and the rest of us
            have no clue. - &quot;DKIM itself was a leap of faith&quot; and=
 that
            we were doing things based on opinion and conjecture. It did
            not take 16 years for there to be data. There was data
            before DK and IIM were merged to form DKIM.<br></div>
         =20
         =20
        </div>
      </div>
    </blockquote>
    <p>What data? Data that showed what? That&#39;s completely news to me.
      You weren&#39;t even part of the informal group who caused DKIM to be
      created, iirc.</p></div></blockquote><div>Everyone,<br></div><div> <b=
r></div>A working group charter is in some sense a contract between the IES=
G and the working group regarding what work it will do, how it will do it, =
and what its deliverables are.</div><div class=3D"gmail_quote"><br></div><d=
iv class=3D"gmail_quote">I hope it&#39;s clear that the discussion taking p=
lace here does nothing in service of that contract.</div><div class=3D"gmai=
l_quote"><br></div><div class=3D"gmail_quote">Please get yourselves back on=
 track without undue delay.<br></div><div class=3D"gmail_quote"><br></div><=
div class=3D"gmail_quote">-MSK, your increasingly irritable Area Director<b=
r></div></div>

--000000000000d8f97705b83d641d--


From nobody Wed Jan  6 10:02:51 2021
Return-Path: <dcrocker@gmail.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 1C1AA3A10DA for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 10:02:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 oKv6bBBfRP-D for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 10:02:48 -0800 (PST)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D37433A10D8 for <dmarc@ietf.org>; Wed,  6 Jan 2021 10:02:47 -0800 (PST)
Received: by mail-pl1-x62f.google.com with SMTP id s15so1918154plr.9 for <dmarc@ietf.org>; Wed, 06 Jan 2021 10:02:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=zDGIy6RoXvuHi0RvPEbKWVOrfHYk3Np5s+iX5oXhE5s=; b=pDdp7Fla2WnF3b5721md6LFAwtL2Nr6/lqytWJee2Y4Pu5vHPAVBRuwDt//dH4H0lw JwYr8pi7DuOBf2CUaI0GFbRi7M4QttvqhmtHbemyEQYlaxIqKR86b6ffM2e8EFQCfWWa UvybsY7h9Kw9EIsMkJGC9Q4ca41dv9lqKdGLUhy2WWGS8wUv+2sgVvoVisb2SYvuABAX xw/CpaMGmPafOyLqCPUwAQXVIbNcbjqyrdPyfCPjkzsv4si1RU1Tn7H+sVQChN/NFweW I7m/yiOFxz8GOeU20Lbla6mLaxujFBIHWPgjPgJe4kNCeAHjaystcCVOls1bVIL/vc76 1hEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=zDGIy6RoXvuHi0RvPEbKWVOrfHYk3Np5s+iX5oXhE5s=; b=uhq7YM/rumQcp8SZokRSBjn6eHJAKd+Kax6nIIXkZZjmHgZ8GkqrGiTWKuIImF2kU9 mCCL4vD4It/toCFC7ene3ZP7pC4rHuo4inIstzOVNpS/+fIIAjTCcM/xnZ288ARr6diy bI4iAyZS6eq0oJ4ca1rvQSqZvtzs25bTRwVk4kq2UMtUbcznnFCtSkhkszlXUmAGxblY EwOJnhEJ7F0BqJO5IOqTY8Iww/XGvBvSl5VdfNps0OJdk6QEvw9Fpy3HW0XD11nA734+ tmWn7YJVt6jzrZKJVVhNZUK4kQja4FgE6LpgcxrL3XYKehQVzMqTA2zaZxFNx7YZQRKR wPJw==
X-Gm-Message-State: AOAM531AL5a33R/ywXQ1WOCDM1N/16P+O7JsL5y9m8LXrJ2BwmQJzm1W xKU+zKnVlM0kVDj11bFQfbe1HZOLY3I=
X-Google-Smtp-Source: ABdhPJyT7gHf7fk46Qvl8yZMujkDXNCruk61tnDmWc/grOSkMsFUJPoCMHA3B/+/DKB15DJC4I0NPA==
X-Received: by 2002:a17:90a:474c:: with SMTP id y12mr5584844pjg.175.1609956167226;  Wed, 06 Jan 2021 10:02:47 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id u189sm3036445pfb.51.2021.01.06.10.02.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 10:02:46 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, Dotzero <dotzero@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <93013855-3187-2a19-8c00-a2c589dc08ac@gmail.com>
Date: Wed, 6 Jan 2021 10:02:45 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <67638446-094e-b598-adc5-dd540c69d487@mtcc.com>
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/pMMOlYlyKnTTgkbiCaeLMXkBUCM>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 18:02:49 -0000

On 1/6/2021 6:41 AM, Michael Thomas wrote:
> Um, dude, I was one of the authors of IIM. You're literally claiming 
> to know more than me about what was in my head.

Um, dude, she was claiming there was operational experience, upon which 
DKIM was based.  I don't recall IIM having operational experience, but 
DomainKeys had gone through two rounds of field deployment.  So, 
arguably, she was being kind about IIM.

The issue isn't what was in your head but what was in the field 
experience of the industry.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Wed Jan  6 10:04:37 2021
Return-Path: <dcrocker@gmail.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 D9D9D3A10D8 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 10:04:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Y2yGHTXs-9Z4 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 10:04:34 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BD583A10DA for <dmarc@ietf.org>; Wed,  6 Jan 2021 10:04:34 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id 15so2748531pgx.7 for <dmarc@ietf.org>; Wed, 06 Jan 2021 10:04:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=XSHeiK+7KGZAw5p0emB6JG+bSr/rwbApdtJ2qiP6DlA=; b=rAgiaIlBPxTJezZx6oVZNyV3d4ghkp9I503M505K+Anf8PFoZDmWT55ofpMIp8tRoA C55OwCP/+vYLQAz21Lh8R+RcKdNUOKCk1xYPdM5mM6w96H9105vX1nZCkV4MrFytPWea HOBXlZV4QUxCugEi1C5MGvnhe1iHQMqKpdVNGrO/zteMMx8+u0tG2NJBpKWiS8fdbn85 0j9tXkwMOEhrHkI8UJM3rW2sCgHomGZleyuFJNnpvKg9/N1cG2slzNapdGImXH6Ea8qx vMSXWfke5CLNlENonQfL+0SiOYkgPmvejNhizQR5yA6fHzQMdhH/DypUSlMgdw30ytRv Bx4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=XSHeiK+7KGZAw5p0emB6JG+bSr/rwbApdtJ2qiP6DlA=; b=WPDNPefN8IXYLEq3W9/hXOiIW23OZ1ZMILpPPZ19lRQ5B8uJT4/yAGUKJCshiGRV7u E5b97A+fXlaCH5u0njWog5sP0HgC7gcM9Uj5yqX2yxyDa2x7ozkVXzAaeHhBl0ejQMs1 RCktg45JJA4O9o5YbfLgvzMo9uYTsjZuimuON7t+QPq5A0ssDFflS5ROIkzfwlocXqoZ KPnrkSHrEE8O1/sadqSjpgV7SofDEqcBDHxc7EixO0QwyVeYexFDf8dMVOK483nZYB4w 5HUVwhANl8tZPbkF6HYMJv0b3Afrb3CUdBNLVx4c3ZDwbSNokpfzgg7cT7ZntbfrFLgK J9WQ==
X-Gm-Message-State: AOAM5331xxdJFANdhUm5UiGF2GUIzFWxF6zyCGnnAZPqQ4xrm0Yx5Zuw YYDu8tmsHbMXR69D/v3EdKnH9MJTGbI=
X-Google-Smtp-Source: ABdhPJzvsMs+5E0f5XTQct9aAsHl8KAIOj9IVe8Tzj5WH9eiL+bwDtIxBFzXbanRyJUei0MIgNExCg==
X-Received: by 2002:a62:f204:0:b029:1ad:ea07:86df with SMTP id m4-20020a62f2040000b02901adea0786dfmr4981395pfh.34.1609956273484;  Wed, 06 Jan 2021 10:04:33 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id a31sm3567792pgb.93.2021.01.06.10.04.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 10:04:33 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, Dotzero <dotzero@gmail.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com> <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com> <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <daafad85-4a20-cefa-0728-d66437fa2e8a@gmail.com>
Date: Wed, 6 Jan 2021 10:04:31 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com>
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/OlTQhoXLwQTj7CMZAaYW8mVLTic>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 18:04:36 -0000

On 1/6/2021 7:07 AM, Michael Thomas wrote:
>
> You are literally telling me what I knew at the time.
>

They are literally doing nothing of the kind.  Since you think 
otherwise, please provide sufficient analysis of what they actually 
wrote to explain your rather divergent interpretation of it.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Wed Jan  6 10:06:44 2021
Return-Path: <mike@fresheez.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 088F53A10E4 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 10:06:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 aV1tfXcG-ti2 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 10:06:41 -0800 (PST)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B7F63A10D8 for <dmarc@ietf.org>; Wed,  6 Jan 2021 10:06:32 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id g3so1948254plp.2 for <dmarc@ietf.org>; Wed, 06 Jan 2021 10:06:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=HLwbfE/J1MtuT9deE5yGdKDUdgTqLSV690Ig5AL4erk=; b=j3KKouMhJVGyBcUB7/D/CBEe0OCZf90Gubk7jMCGjOVuolMIodgAESTg6C0FCmbcs+ 3AV+smIZmV7X6+JCOqIdZuCeGbk1/lIDcp03ZAZVQn43EVGL0jMQ04nL9oJCNUYt0Stl FsezxRE40UBTDo10nwaE9xd8OrZq1iB8vJGzkmDRoIOtIeWOWjfPeebc3z4vvKZvQ/6O BbHT6ipozgLR85WIwtW6pEXZw1QTLEUvk54FdP002QO7ULkflzzx7HwHnNECPiilX2YC XkVarUZt301DjTPdNxNIpVLPEtVAqSPNNYD86/2pU2WhXLRItQ+qqyzQ1UB2r5AHNHtV Y4Kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=HLwbfE/J1MtuT9deE5yGdKDUdgTqLSV690Ig5AL4erk=; b=dln/kFXlvEWjmkpxnkq+tOKlHW2t/FeAfnS3ectdwILhrlINtq8HtzSpiyzFDaE5KR dBNbyl7mfMLuw6F8z8AWLEpdto4Ug5Og67oOQaOg+SlYFzbF82GTYpUwnoUlFPoxZIhR 8zajaK0hbQWnw5dVOUl1rERvH4o9C0sLPzs5CbpWGjxLpkImOmsrPb0Fur2qtOgctUW2 QefUf3chUccM9v6DMa3yp7fZxUrf42W4Elg6f7xuOJkr3tjw6FliSh++adJc0PJsgtgf X3aK1rRGEFTYEeCAMXQaJY+DUUWMB2Jtr4vt47PiJ/9PQNeqYjzKRXstPagR5n/dj+0/ x6NA==
X-Gm-Message-State: AOAM530TuaevyqHCJbOAHqxc5K3pzObo4TfQXAJGq6HwbWQuCo+6qDxc bIfx6yRDYrxPPfVi/I+m8fm/SF/RqhenZwwk
X-Google-Smtp-Source: ABdhPJw+rOCkdSw0Ly/VEO4lWk7Qo32Op98bKp0owLFHC4FQf/ebaVPYdKvRcLZdioMepw6sssBO1g==
X-Received: by 2002:a17:90a:1748:: with SMTP id 8mr5364849pjm.47.1609956391692;  Wed, 06 Jan 2021 10:06:31 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id m3sm3117067pfa.134.2021.01.06.10.06.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 10:06:30 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, Dotzero <dotzero@gmail.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com> <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com> <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com> <daafad85-4a20-cefa-0728-d66437fa2e8a@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <ec57d490-4895-7acb-0db3-2c67325301af@mtcc.com>
Date: Wed, 6 Jan 2021 10:06:29 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <daafad85-4a20-cefa-0728-d66437fa2e8a@gmail.com>
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/eZxDZaSxFEp3T8QYS_e1c_TnskE>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 18:06:43 -0000

The AD said to stop an hour ago. So stop.

On 1/6/21 10:04 AM, Dave Crocker wrote:
> On 1/6/2021 7:07 AM, Michael Thomas wrote:
>>
>> You are literally telling me what I knew at the time.
>>
>
> They are literally doing nothing of the kind.  Since you think 
> otherwise, please provide sufficient analysis of what they actually 
> wrote to explain your rather divergent interpretation of it.
>
> d/
>


From nobody Wed Jan  6 10:08:23 2021
Return-Path: <dcrocker@gmail.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 24A8E3A116F for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 10:08:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 PRijL0oIYZQQ for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 10:08:14 -0800 (PST)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FD0D3A119A for <dmarc@ietf.org>; Wed,  6 Jan 2021 10:08:13 -0800 (PST)
Received: by mail-pf1-x42a.google.com with SMTP id x126so2157157pfc.7 for <dmarc@ietf.org>; Wed, 06 Jan 2021 10:08:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=j1LUZcGnOwUTZrI+hGla2d1cwedpJnLi0E3AXpmBIQI=; b=cdFW6nHjJJhJAGWTYzrwXIEMzj5Lc160DTbC7m1L14OB3J2EYcB3hFbSXnhuXLryj7 PCLDmQ4wZmlpJo/kX3W/7dKh63xUNqnWXsLitMQ8CcF8n5cdcpcRZ19SyJK+R2A9Vn/u f25281mpnofKSWhAlZSt+4GR1HMcT1tV9hi4OwJEtjRE1fA5VF5Fh4FFBr8UMC4BRexS uMpawYTxk8xKUt96DG9XvSu7VZxqKJ1tjnuebukj378fDZIHWXmTAXuBDMf5qyRrAh0F hOb1kF4W8HD3tWhGdvt93QdfleJUmQ+tNGmqyyqvoQw/fs6Rt5+Dq3Nl3BOO+jB5362G s/CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=j1LUZcGnOwUTZrI+hGla2d1cwedpJnLi0E3AXpmBIQI=; b=P+B53ykvB4yMia9cLyT6yXOMVeBoWY7oDeduhuAqG1aOR3REwghp1TlDkOgUfboNGA 0GwUsx+IAD891Jw9XzriRN3m/xx6HueJLAon5T0TgQa1hW96ZhjC7XquwPrCV6ABhDHh By3KLLhV4Y+Gi3hYazUHRshXi8CqJSPChs563/HbedEpBE4PhYlqhShnIupZsJ9aMs9/ ZsISO5VbD9ThwJPSysOosj4IEo+gtZ/FashXNW22lzQrbjb1KEwQLDJbYPc3R2bItIe7 gbycoO9ys76ki47mZa00hX50CPwtXrardGMc+/x2FA4Bid03azrP9o0IVLCfuIKH0Buc smnA==
X-Gm-Message-State: AOAM5314gg4cjz3pL0lr1ihT4SOumbm7sJCEhrHkbl0ipXHoeqvGyIz3 Mtg5kZRfTxmMMkt/vY9+r6m47i/0tBg=
X-Google-Smtp-Source: ABdhPJzL0+rRsG56UL1ZqbjnDLil1yQl4MS/GsL//4eWPpG9SI2oCdVgwIWBd/vPR9xiKi0SU6caXQ==
X-Received: by 2002:a63:e108:: with SMTP id z8mr5697587pgh.363.1609956492975;  Wed, 06 Jan 2021 10:08:12 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id s1sm3056995pfb.103.2021.01.06.10.08.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 10:08:12 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <CAH48Zfxef+5H7nh7ahHvaP+B=+i1OB7XfFB+ptkcWeDRt0o8Mw@mail.gmail.com> <9926b42c-f767-6355-a940-6862f2e4ffb8@mtcc.com> <CAJ4XoYe+Wbs16WGLXf-33dzwg1bu6K73rS2RN=jNR4xcJ-FZHA@mail.gmail.com> <67638446-094e-b598-adc5-dd540c69d487@mtcc.com> <CAJ4XoYcOHiC-sHxd_h+cqjioSpiupjFpR82p21kZ_7nPNZErcA@mail.gmail.com> <d6a9c579-c440-98c9-8044-89e0dcd4d467@mtcc.com> <daafad85-4a20-cefa-0728-d66437fa2e8a@gmail.com> <ec57d490-4895-7acb-0db3-2c67325301af@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <bb4dfa80-8b75-183e-ee86-6943e14bf4fe@gmail.com>
Date: Wed, 6 Jan 2021 10:08:11 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <ec57d490-4895-7acb-0db3-2c67325301af@mtcc.com>
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/nFTndeEjjLD5u7OioeyWc8v6piY>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Wed, 06 Jan 2021 18:08:21 -0000

On 1/6/2021 10:06 AM, Michael Thomas wrote:
> The AD said to stop an hour ago. So stop. 

And yet, you didn't.

I only just, finally, read his directive.  what's your excuse?

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Wed Jan  6 11:11:43 2021
Return-Path: <johnl@iecc.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 5B52F3A124C for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 11:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=QYTvtaAV; dkim=pass (2048-bit key) header.d=taugh.com header.b=vrpXxuAh
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 ETGqnqyx1z9g for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 11:11:29 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 55CE93A1216 for <dmarc@ietf.org>; Wed,  6 Jan 2021 11:11:28 -0800 (PST)
Received: (qmail 25952 invoked from network); 6 Jan 2021 19:11:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=655e.5ff60b60.k2101; bh=oCP+l+LLPxZoOPP1H7eGSKs5zDdns/ue/F6Fkv2R8U8=; b=QYTvtaAVcGZk1+AHJbjgU54MOoNMJ7RD6//IvELGqp4oU6Pggv82/K6sF089WNAKM/gJw8U+yXKvg8I8Eqxq2iOKNAeWT+N9ZgNPpS8qcQtuYUpUd072lRek/M95mNp70wW65tZh9BAoj0LnDi7biqRcMGPQkmTF8bZU8ltS1NVCh737vdhrVro8t2SW8tj3h8uDTQOPeb9HpK42sfCm90T79gVKPY5ftdXxl9/LTafdaqZJSUQIYEEUHNU8q44gBWLCpY4n2hYBGaBK6dXRL+ILB8Qb7tU2ao4rI9xboT+/IjTI2aUw2QkfUT0F9i9kx8qCBVF+9M+dUSovqGgqEw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=655e.5ff60b60.k2101; bh=oCP+l+LLPxZoOPP1H7eGSKs5zDdns/ue/F6Fkv2R8U8=; b=vrpXxuAhl9A0/CB+TxnXWx/vDC8I0TORBpBKzoU8yXkMqwoVBtE6RTH8nPUBmi8cZ5uVi/BfQWyVIb38BOyoRR6rnVJw88WJhclXZ0ApW0RbrvW0btv0gE9CC1HLSJzk/jTkU4ftHawlSCB6jzCdSyUPqbyoUbI/Js4dwKccsBUJvl3P+Xp09xuVDfoF4VdyOVg30MnVqgKpvktl8l3ARrj6AAixhwBloFM+vf4clcFkDoCIztsNn3jklMGbvvX00qWSdMQtHL2Sg5h9BGoLq5Z8UzC0J6vGDQWOQtt9oqMoT+NKWXldko+Fe/WwN/9MyFrk3IZZDp1Zw0FCfNnG/w==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 06 Jan 2021 19:11:27 -0000
Received: by ary.qy (Postfix, from userid 501) id 290BC5D043E4; Wed,  6 Jan 2021 14:11:26 -0500 (EST)
Date: 6 Jan 2021 14:11:26 -0500
Message-Id: <20210106191127.290BC5D043E4@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: laura@wordtothewise.com
In-Reply-To: <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/TQ-bR-A3UMqOS6QIKiHnEuN5HSM>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 19:11:38 -0000

In article <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com> you write:
>The header rewriting being proposed - that is header rewriting by the ESP so that the messages that
>go through their system are rewritten to point to the ESP and not the author of the message - means
>that the identity assertion is disconnected from the context of a message.
>
>Want to know what mail goes through ESPs? Bank mail, social media mail, marketing mail. Billions of
>emails a day go through ESPs that you have and have not heard of. 

It's even worse than that. Some ESPs are not very good at managing
their customers. Sendgrid, one of the larger ESPs, sends me a stream
of bank phishes, fake vaccine offers and (for symmetry I suppose)
antivax kookery mixed in with the legit bulk mail and some receipts
for real transactions. They do not have a good reputation and a great
deal of the mail they send goes straight to the junk folder where it
belongs.

Header rewriting is not any sort of solution to the problems that DMARC creates.

R's,
John


From nobody Wed Jan  6 14:57:28 2021
Return-Path: <dougfoster.emailstandards@gmail.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 039FF3A1353 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 14:57:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gvX8nMrH8Wqq for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 14:57:24 -0800 (PST)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 604403A1352 for <dmarc@ietf.org>; Wed,  6 Jan 2021 14:57:24 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id h6so2664434vsr.6 for <dmarc@ietf.org>; Wed, 06 Jan 2021 14:57:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=faMNO2Ox/TNXuHbsVkAbApj03jD2+/jshJyFkAElAEg=; b=BGYLONga0inDYULOrDyQgzUDA8QDR0CJu1A6rSrRAD9BGse5Jay0uZJIDS5Wo1zYsI h34tQWH3c5yXgNkYimyjDOVyLc65fu9lHJDl45siN8ZIj70QoubUe4b1e+XefDNXYS+o tcGTinqIVo0OpW3rBvlPgAW4X+R9hlFvZg/HlFiANw/gViP7OxHMf0CTmyXXv9j3pOdD 87ZpHPi1X3RDQW8z7T+dcZmkrgdVNkB9Uwhu504SbiVQZJ4hhuahQi5JSmQNqMPAsr+k l/bAy7Eez6G42QtkUqqdSXosktPQh2lgieBotaMEaJ5o/5ttTXE16wo1r2d3gwVSlvTP XNBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=faMNO2Ox/TNXuHbsVkAbApj03jD2+/jshJyFkAElAEg=; b=c7rqf1892XSqWDTqadPnYnLNp9STYRRfo4LOjEPcZUplbjDSSKjV9KkIGJjOCNQh1a NkyzmtThokfp0W6B5/AjdltDIbi+mUde3xm1+aPmzAMWZlSJggRMmR661Ioez4mPMpsr Cuh31gcKFvqxxKzbNOgnQA1YqB1gevDkQS4JYVFTwLUmgBvd9NIM1SVGS+PjgeG8M5a+ Hj98UYTQ3R4kTaAsPpAVUCfuGVmvyAkv8weUEc54ZmL49EHr3/WgsK4Ukmm2in1PawLs ofHy0NtVZKOhZbQdCVIIH7CcWPmPFsw1OhHR9MRM9xUoap765wN3NEiMAe65tbDDp0Qp gYog==
X-Gm-Message-State: AOAM531gozbVWki0TC+q/Vb+ZB2dYdhTAj1uwZBDm74XQ9JQpQ7Ib0Dx 1UhL0XMcEKbjkobbHf8s271Qge5TxjJZAMAHLWxlB78E
X-Google-Smtp-Source: ABdhPJxd3fGFZKXSMm/XtvEsVYLt+aP/biDLAPsnPC0pRWbz3mkx+DdZfG+W7gGeQgFJcoXX8k1odqoLu3MprZ5I/HI=
X-Received: by 2002:a67:d083:: with SMTP id s3mr4912490vsi.25.1609973843346; Wed, 06 Jan 2021 14:57:23 -0800 (PST)
MIME-Version: 1.0
References: <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com> <20210106191127.290BC5D043E4@ary.qy>
In-Reply-To: <20210106191127.290BC5D043E4@ary.qy>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 6 Jan 2021 17:57:13 -0500
Message-ID: <CAH48ZfwUXbNuQsi1Z3S3YyegdANuqfRM-byO7tScB3prG6sU8g@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000007c85a05b8433f83"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/fBQ0u-nPW9ivHWD7Xva6sd-KpjI>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 22:57:26 -0000

--00000000000007c85a05b8433f83
Content-Type: text/plain; charset="UTF-8"

I don't know how ESPs and From Rewrite ended up in the same sentence.  ESPs
do not need From rewrite because they can do DKIM signing.    The
incentives are all against them using or allowing From rewrite.

Taking business from criminal clients does not include allowing one client
to impersonate another client or a non-client.   Such behavior would hurt
the revenue of the ESP.


On Wed, Jan 6, 2021 at 2:12 PM John Levine <johnl@taugh.com> wrote:

> In article <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com> you
> write:
> >The header rewriting being proposed - that is header rewriting by the ESP
> so that the messages that
> >go through their system are rewritten to point to the ESP and not the
> author of the message - means
> >that the identity assertion is disconnected from the context of a message.
> >
> >Want to know what mail goes through ESPs? Bank mail, social media mail,
> marketing mail. Billions of
> >emails a day go through ESPs that you have and have not heard of.
>
> It's even worse than that. Some ESPs are not very good at managing
> their customers. Sendgrid, one of the larger ESPs, sends me a stream
> of bank phishes, fake vaccine offers and (for symmetry I suppose)
> antivax kookery mixed in with the legit bulk mail and some receipts
> for real transactions. They do not have a good reputation and a great
> deal of the mail they send goes straight to the junk folder where it
> belongs.
>
> Header rewriting is not any sort of solution to the problems that DMARC
> creates.
>
> R's,
> John
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--00000000000007c85a05b8433f83
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t know how ESPs and From Rewrite ended up in the=
 same sentence.=C2=A0 ESPs do not need From rewrite because they can do DKI=
M signing.=C2=A0 =C2=A0 The incentives are all against them using or allowi=
ng From rewrite.<div><br></div><div>Taking business from criminal clients d=
oes not include allowing=C2=A0one client to impersonate another client or a=
 non-client.=C2=A0 =C2=A0Such behavior would hurt the revenue of the ESP.</=
div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Wed, Jan 6, 2021 at 2:12 PM John Levine &lt;<a href=
=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">In article &lt;<a href=3D"mailto=
:D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com" target=3D"_blank">=
D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com</a>&gt; you write:<b=
r>
&gt;The header rewriting being proposed - that is header rewriting by the E=
SP so that the messages that<br>
&gt;go through their system are rewritten to point to the ESP and not the a=
uthor of the message - means<br>
&gt;that the identity assertion is disconnected from the context of a messa=
ge.<br>
&gt;<br>
&gt;Want to know what mail goes through ESPs? Bank mail, social media mail,=
 marketing mail. Billions of<br>
&gt;emails a day go through ESPs that you have and have not heard of. <br>
<br>
It&#39;s even worse than that. Some ESPs are not very good at managing<br>
their customers. Sendgrid, one of the larger ESPs, sends me a stream<br>
of bank phishes, fake vaccine offers and (for symmetry I suppose)<br>
antivax kookery mixed in with the legit bulk mail and some receipts<br>
for real transactions. They do not have a good reputation and a great<br>
deal of the mail they send goes straight to the junk folder where it<br>
belongs.<br>
<br>
Header rewriting is not any sort of solution to the problems that DMARC cre=
ates.<br>
<br>
R&#39;s,<br>
John<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--00000000000007c85a05b8433f83--


From nobody Wed Jan  6 14:58:58 2021
Return-Path: <dougfoster.emailstandards@gmail.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 8B8533A1358 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 14:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Z1W2yLEXLASy for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 14:58:55 -0800 (PST)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79F823A1353 for <dmarc@ietf.org>; Wed,  6 Jan 2021 14:58:55 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id e15so2689660vsa.0 for <dmarc@ietf.org>; Wed, 06 Jan 2021 14:58:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HfAtG4GjWlRX6Y/K+WIJUjLiUIx3LhiqAFaK9ly5qEg=; b=HVK7wyoKMS8gUxj+5xWZPRS8cLhqoQ/efB8TJoUDaL/UsLx0EWPwbU3TeM3X7OwSS2 ugp/Ekcr4drRssfjTCSbd0VPSVMLPwvUn4C+hwvy5/Ky/ajlaKjZHuJyuek2N7jnyOq/ L2o/v/sKtcgRaSChHZj1+2nsS1nAYDs+PDy7zjHqoJBu9Dhz1zPnZNpOjEemCdt6ljzW 8JXZFsewTBAsMIY7BUVuliKcdbdFdCGrf3/4Bpgc4cQbRAeOqN5Rtz2RIskf9hPT6Eu4 QXuvarlz+pY76E83vRS/ZpV1Rc9lywPu7WPNj1NoTPK6pnY3cElsZsfeQp6ycpBQDP+t 9jIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HfAtG4GjWlRX6Y/K+WIJUjLiUIx3LhiqAFaK9ly5qEg=; b=T146c0AbfKqnXkTPPhB9rvoNKKqTd/rhzu+PDCv2J3zl1kQZ36Tp8WzrEQdt3ZHaMy 9OG+MKyS9Q6xdm/SbZYzXziyajgB0sfbiA9tV66s2rnvLzdeylGQ0s67gzmxQ8WO34Ng HbFkuZJ9qGkbeQLaLF+K9PQT61d3ZlHxlNVySF2QilO9ScT9kP1v8tQ5xz4T1xtkWn9s BlEvFwTU1txyvdC95f5LFIM5VF7fu+Xm8hvsmroaAOVEPcpbnT3YM0nSriG65wSQ3Vea OrWT1zhNP8fQ0vjyzf9zCT7L1dCescRMQEJfkw3o95E8y/zaK7BPfAzOZDUrTSmqW+A7 7SMQ==
X-Gm-Message-State: AOAM533zsRmDeygUit0hQd2eUIf0Jg0FJtXcIF7RPXCjoAI4dMKb0opQ u65OdyaO4HELFg4vGObWTdtplVK7tqkcyMDfpfopwIyqw48=
X-Google-Smtp-Source: ABdhPJyJ+9x6pYKxm9JMXQq1mbBaSRYEVNqjgvCBwBgSH28WZI58qmJcef8RuWWRZVyRgg80eOWeN34/Q9ZbDeKKb4A=
X-Received: by 2002:a67:507:: with SMTP id 7mr5210771vsf.42.1609973934541; Wed, 06 Jan 2021 14:58:54 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com> <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com> <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
In-Reply-To: <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 6 Jan 2021 17:58:44 -0500
Message-ID: <CAH48ZfwgPyHwE2F-fcGshvJUW2ao5AVHgBruQQqg8sc0hzdaUQ@mail.gmail.com>
To: Laura Atkins <laura@wordtothewise.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007752d005b84344f1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/iL-L0-dVm-5uUZ4PRlpYo9TLWyY>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 22:58:57 -0000

--0000000000007752d005b84344f1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On this topic:

Forwarding hides information that the email filter needs to make a correct
decision.   Header rewrite hides the problem, but does not solve it.   When
we get the automation right, predicting user behavior will not be necessary=
.


You=E2=80=99re going to need to provide evidence this is the case.

>
>

--0000000000007752d005b84344f1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On this=C2=A0topic:<br><blockquote type=
=3D"cite"><div dir=3D"ltr"><div dir=3D"ltr"><div>Forwarding hides informati=
on that the email filter needs to make a correct decision.=C2=A0 =C2=A0Head=
er rewrite hides the problem, but does not solve it.=C2=A0 =C2=A0When we ge=
t the automation right, predicting user behavior will not be necessary.</di=
v></div></div></blockquote><div><br></div><div>You=E2=80=99re going to need=
 to provide evidence this is the case.</div></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
</blockquote></div></div>

--0000000000007752d005b84344f1--


From nobody Wed Jan  6 15:33:09 2021
Return-Path: <dougfoster.emailstandards@gmail.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 215633A0DBD for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 15:33:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 20--GduBr1hJ for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 15:33:06 -0800 (PST)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE8313A0D75 for <dmarc@ietf.org>; Wed,  6 Jan 2021 15:33:06 -0800 (PST)
Received: by mail-vs1-xe36.google.com with SMTP id s85so2711273vsc.3 for <dmarc@ietf.org>; Wed, 06 Jan 2021 15:33:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HMYJTPWRq76FJ/ufdhunqdjmCndDa7daObRlLn+whO0=; b=oa7+iZxQaJASW8kNlcEqQTYHnKurmMih1I/dWBGYVANxsU7l6+wg8pPUSMj5Zy9fG+ dqmanw9xUReNsN9yuvzdK5pXKoSZojZQRQ1Q7yT4ZospX0DNDp2MrnLWqf6iE3mFG5bA ZwSqQ1xSI7hM+t7VlML1uNXNcDgqu2ERH4qnI7mCG7BQ7AcrNqCz0TbiygdjM+MOwt5H WYoifgpz4B1WKBb7IzRNdxTMkLXn1XRrb5l0z81zLnoWFqs38G7gRPKraXwIXWq+DWII NElh5FD9ZFtzpOw07gt/O/z63davhtMlpcDFZO7gH7gOmm9fC9JjQZQ5+l023NpwSo5H KsKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HMYJTPWRq76FJ/ufdhunqdjmCndDa7daObRlLn+whO0=; b=YOqRAn43wH5vD1YWSi5fymbR4DHQQoV+JdJ90YeQJBMLV3Yy9xVvGjIDJSo53mKBkj ge4hbmgIjw/O5kIwd4H0m5/x7e3K5LbHfz4l+YTfddYQnUZS/ahfkUShOOxv9Mn2/CvK aDf+lsTm4FZipMFjQFp4tyY/O9AHyBTHs1zPNG8MjBfMVlzl7YoFF5QFLMgpZUdb38Gh D1fee/2qE72yUtWzAfp/0/Zj55Y+j2G/+56+YGpv3+LsdjiFPG3O/cCl/AmbRrMO8uNY jnZlTVrLZ1B7l+3jYjVvruRzv+ZwUpg6C8wcPv/crqxLtNVClXoXMEFeMiXaBM6YNT+b jg6g==
X-Gm-Message-State: AOAM532KhxPcp0tgG+qsuejEq6vUJeftZ/ZogYrN5QWmpOxdOxK16f+N NGUvlP4QsTzsRYP/w/66yC2FLmVV+TLWcqol8F0hlqwJnqg=
X-Google-Smtp-Source: ABdhPJwUXQlrh1FtbQut95r+IDMBxpMqxKL/zpdXiWh7E/ZbAkeS1tgjc3T6UdrvXwXvnnLMXQQX/pOLEsdEQuzratk=
X-Received: by 2002:a67:d083:: with SMTP id s3mr4979894vsi.25.1609975985743; Wed, 06 Jan 2021 15:33:05 -0800 (PST)
MIME-Version: 1.0
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com> <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com> <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
In-Reply-To: <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 6 Jan 2021 18:32:55 -0500
Message-ID: <CAH48Zfyf=NV0dJJZzG7bPKSro1hd1q=4eGQLBkDG1oo4XU3dXw@mail.gmail.com>
To: Laura Atkins <laura@wordtothewise.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ba2a8205b843be8b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/bjdoctfHA3AKuPEqvDRhjhRQnYQ>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Wed, 06 Jan 2021 23:33:08 -0000

--000000000000ba2a8205b843be8b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

A previous attempt at this reply was sent prematurely.  Sorry about that.

I said:
Forwarding hides information that the email filter needs to make a correct
decision.   Header rewrite hides the problem, but does not solve it.   When
we get the automation right, predicting user behavior will not be necessary=
.

Laura replied:
You=E2=80=99re going to need to provide evidence this is the case.

Happy to explain, but I have been saying as much for some time.

My source filtering uses five parameters:   Source IP, Reverse DNS of the
Source, Helo name, SMTP address, and From Address.

Assuming that a forwarder adds no threat content, the need to evaluate the
actual source remains.    But this is difficult to do:

-- Forwarding hides the three elements of server identity behind the
forwarding server.
-- SMTP rewrite hides the source domain identity, such as the ESP which
sent the message.
-- From rewrite hides the asserted author identity.

We have hidden everything.   If the forwarder could be trusted to block all
spam, this might not be a concern.   But everybody assesses spam
differently and everybody misses some of it.   As a group, forwarding
services have an incentive to minimize false positives, so the likelihood
of spam getting through is high.   Mailing lists have different incentives,
and should be able to block spam reliably.   Whether they do so or not is
outside my experience.




>
>

--000000000000ba2a8205b843be8b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>A previous attempt at this reply was sent prematurely=
.=C2=A0 Sorry about that.</div><div dir=3D"ltr"><br></div><div>I said:</div=
><div dir=3D"ltr">Forwarding hides information that the email filter needs =
to make a correct decision. =C2=A0 Header rewrite hides the problem, but do=
es not solve it. =C2=A0 When we get the automation right, predicting user b=
ehavior will not be necessary.<br><br>Laura replied:<br>You=E2=80=99re goin=
g to need to provide evidence this is the case.<br></div><div><br></div><di=
v>Happy to explain, but I have been saying as much for some time.</div><div=
><br></div><div>My source filtering uses five parameters:=C2=A0 =C2=A0Sourc=
e IP, Reverse DNS of the Source, Helo name, SMTP address, and From Address.=
</div><div><br></div><div>Assuming that a forwarder adds no threat content,=
 the need to evaluate the actual source=C2=A0remains.=C2=A0 =C2=A0 But this=
 is difficult to do:</div><div><br></div><div>-- Forwarding hides the three=
 elements of server=C2=A0identity behind the forwarding server.</div><div>-=
- SMTP rewrite hides the source domain identity, such as the ESP which sent=
 the message.</div><div>-- From rewrite hides the asserted author identity.=
</div><div><br></div><div>We have hidden=C2=A0everything.=C2=A0 =C2=A0If th=
e forwarder could be trusted to block all spam, this might not be a concern=
.=C2=A0 =C2=A0But everybody assesses spam differently and everybody misses =
some of it.=C2=A0 =C2=A0As a group, forwarding services have an incentive t=
o minimize false positives, so the likelihood of spam getting through is hi=
gh.=C2=A0 =C2=A0Mailing lists have different incentives, and should be able=
 to block spam reliably.=C2=A0 =C2=A0Whether they do so or not is outside m=
y experience.</div><div><br></div><div><br></div><div><br></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>
</blockquote></div></div>

--000000000000ba2a8205b843be8b--


From nobody Wed Jan  6 16:21:33 2021
Return-Path: <seth@valimail.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 886CF3A1402 for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 16:21:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 ts4ekOubi2HN for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 16:21:30 -0800 (PST)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAB393A1400 for <dmarc@ietf.org>; Wed,  6 Jan 2021 16:21:30 -0800 (PST)
Received: by mail-vs1-xe35.google.com with SMTP id s2so2763757vsk.2 for <dmarc@ietf.org>; Wed, 06 Jan 2021 16:21:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:from:date:message-id:subject:to:cc; bh=5QKkpaohbvf+ZXxZL9OGfm1KxBYH+8/Ar95Yfd7Aa+I=; b=UcAVQ6R93s5hh9y2TKSj12z5Y/fVLgcq+DjY0aFgR4o7QufRuF3e87qSXOZmAC8XU9 koYjakJtx7daRNZMdrX6O6gKrSY1SZUmKNc9uQgT1QFn+Cf00K4T7Xyqkuai4Ynsh7et 1ORatvWAjuNc3ask7tl1rOloWZgTFIblBOmR38RoA3SzQPssxCHEA+iR0GmjwHpZ2+QA 0upf1f2gFYGi1o3M0ifb1oj1mdoduVisGaqwGSRlypPrubjjEttGFiSz17pMMunZxnOg 3i9/RCpLzqIG334s4KBEccTHrC8hEsVibm30tA1hpQrJ1+XAt07iTuIUy8TEf5Ai/1ie lIvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=5QKkpaohbvf+ZXxZL9OGfm1KxBYH+8/Ar95Yfd7Aa+I=; b=RqSDyqUDLRO+Ft7VkZGjFuUcO3pAnrdqAYr0BYZuricA764VIonM3OZyyVQhwbyl61 VAsj1c//elGPgeif9JcxAGXIx4oSNsR2i68hugiyajIU+bHM+HZccaoA0vf2mXteGqub PD+jYLqnBmSePoObzrv3FB5phxyIER/DEXTUCR/HbAf1UFxVns4oWoiiWYO7PP9MrZb0 YLI4kpzLjZ0YABXW4uPEGtngC3kjVsjhldRMfWCf2LFqvoYNeu86nQVYgkubozAPsBlW CCr9MXCtEgvUUFb1O3GgSPvYCjMUhyt68gdiaZDiJ09w0FKbTuwKaflasj0jjVoVlJF1 Zt4A==
X-Gm-Message-State: AOAM530UeoVHs7ignUksmlWxxE/+MPgEAi9noOrBVlqY1X4U/N/7BcMV SPY7jX/PTsb5vQw9KgZE2tezVskk2QS82TWYvZXWQYvEGFvlMw==
X-Google-Smtp-Source: ABdhPJwAnFgR807UqMNXyzZTJ3RqBT3Uk4DpRwkyfX+BYVlVHCY+y3XKIhUMItKFPeteC2xRxm1TRix8+gDJdw/RF6E=
X-Received: by 2002:a67:e409:: with SMTP id d9mr5125401vsf.52.1609978889459; Wed, 06 Jan 2021 16:21:29 -0800 (PST)
MIME-Version: 1.0
From: Seth Blank <seth@valimail.com>
Date: Wed, 6 Jan 2021 16:21:18 -0800
Message-ID: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Cc: ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000cd6e0a05b8446b07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ub6xFEU15w0HAW82ZEnHr_mS180>
Subject: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 00:21:33 -0000

--000000000000cd6e0a05b8446b07
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Working Group colleagues,

Discussion on this list is increasingly out of scope and process,
unproductive, and antagonistic. This behavior undermines the chartered work
of this group and will not be tolerated. We expect and require more civil
discourse from our participants, and remind everyone that disciplining
others is the purview of the chairs.

The current phase of work of our charter (
https://datatracker.ietf.org/doc/charter-ietf-dmarc/) is to deliver a
standards track DMARC document based upon operational feedback. We are not
relitigating SPF, DKIM, DMARC, or ARC, adding new functionality, or
rehashing other IETF documents or processes.

When we kicked off DMARC bis, Alexey outlined a clear process:
https://mailarchive.ietf.org/arch/msg/dmarc/rBWzfzDa_tOhaVdxFzUBYVi46QI/

Only tickets opened by the Chairs or a document editor to the list are in
scope for working group discussion. Everything else should result in the
creation of a ticket to be discussed later, or off-list discussion. The
Chairs re-affirm that all tickets will be brought to the list.

To be clear: Before you hit =E2=80=9Csend=E2=80=9D on an email to this list=
, make sure it
is on topic for an open ticket and is not likely to escalate tensions.
Otherwise, delete the message or start a private conversation that is not
on the list.

>From here on out, due to the counter-productive nature of current list
discourse, off topic or antagonistic discussions will be given a single
public warning, per BCP 94 (https://tools.ietf.org/html/bcp94), which
implies that further violations will result in a 30 day suspension for the
participant. The ADs have been consulted, and everyone should consider
themselves warned.

Finally, several members of this working group seem to be very effective at
antagonizing each other. If a thread is spiralling, and a BCP 94 warning is
given and not heeded, all active participants in the thread after the
warning has been issued will be suspended, even if it=E2=80=99s to tell oth=
ers to
respect the warning.

Now, let=E2=80=99s get back to our chartered work at hand and open tickets.

Seth, Tim, and Alexey, as Chairs

--=20

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000cd6e0a05b8446b07
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Working Group colleagues,<br><br>Discussion on this list i=
s increasingly out of scope and process, unproductive, and antagonistic. Th=
is behavior undermines the chartered work of this group and will not be tol=
erated. We expect and require more civil discourse from our participants, a=
nd remind everyone that disciplining others is the purview of the chairs.<b=
r><br>The current phase of work of our charter (<a href=3D"https://datatrac=
ker.ietf.org/doc/charter-ietf-dmarc/">https://datatracker.ietf.org/doc/char=
ter-ietf-dmarc/</a>) is to deliver a standards track DMARC document based u=
pon operational feedback. We are not relitigating SPF, DKIM, DMARC, or ARC,=
 adding new functionality, or rehashing other IETF documents or processes.<=
br><br>When we kicked off DMARC bis, Alexey outlined a clear process: <a hr=
ef=3D"https://mailarchive.ietf.org/arch/msg/dmarc/rBWzfzDa_tOhaVdxFzUBYVi46=
QI/">https://mailarchive.ietf.org/arch/msg/dmarc/rBWzfzDa_tOhaVdxFzUBYVi46Q=
I/</a><br><br>Only tickets opened by the Chairs or a document editor to the=
 list are in scope for working group discussion. Everything else should res=
ult in the creation of a ticket to be discussed later, or off-list discussi=
on. The Chairs re-affirm that all tickets will be brought to the list.<br><=
br>To be clear: Before you hit =E2=80=9Csend=E2=80=9D on an email to this l=
ist, make sure it is on topic for an open ticket and is not likely to escal=
ate tensions. Otherwise, delete the message or start a private conversation=
 that is not on the list.<br><br>From here on out, due to the counter-produ=
ctive nature of current list discourse, off topic or antagonistic discussio=
ns will be given a single public warning, per BCP 94 (<a href=3D"https://to=
ols.ietf.org/html/bcp94">https://tools.ietf.org/html/bcp94</a>), which impl=
ies that further violations will result in a 30 day suspension for the part=
icipant. The ADs have been consulted, and everyone should consider themselv=
es warned.<br><br>Finally, several members of this working group seem to be=
 very effective at antagonizing each other. If a thread is spiralling, and =
a BCP 94 warning is given and not heeded, all active participants in the th=
read after the warning has been issued will be suspended, even if it=E2=80=
=99s to tell others to respect the warning.<br><br>Now, let=E2=80=99s get b=
ack to our chartered work at hand and open tickets.<br><br>Seth, Tim, and A=
lexey, as Chairs<br><div><br></div>-- <br><div dir=3D"ltr" class=3D"gmail_s=
ignature" data-smartmail=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"=
line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-=
align:left"><span style=3D"vertical-align:baseline;white-space:pre-wrap;fon=
t-size:small;font-family:Arial"><b>Seth Blank</b></span><span style=3D"vert=
ical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"=
> | VP, Standards and New Technologies</span></div><span style=3D"vertical-=
align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div=
 style=3D"text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b=
></span><span style=3D"vertical-align:baseline"> <a href=3D"mailto:seth@val=
imail.com" target=3D"_blank">seth@valimail.com</a></span></div></span><span=
><div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div><=
/span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helveti=
ca,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height=
:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-=
family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:b=
aseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com=
/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx=
4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"bo=
rder:none;height:40px;width:177px"></span></p><p dir=3D"ltr" style=3D"color=
:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;backg=
round-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:=
0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line=
-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=
=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This em=
ail and all data transmitted with it contains confidential and/or proprieta=
ry information intended solely for the use of individual(s) authorized to r=
eceive it. If you are not an intended and authorized recipient you are here=
by notified of any use, disclosure, copying or distribution of the informat=
ion included in this transmission is prohibited and may be unlawful. Please=
 immediately notify the sender by replying to this email and then delete it=
 from your system.</span></font></p></span></div></div>

--000000000000cd6e0a05b8446b07--


From nobody Wed Jan  6 16:31:03 2021
Return-Path: <tjw.ietf@gmail.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 E85423A1400; Wed,  6 Jan 2021 16:31:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 uG_wIdl2O7Ao; Wed,  6 Jan 2021 16:30:59 -0800 (PST)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FDF53A0EBC; Wed,  6 Jan 2021 16:30:59 -0800 (PST)
Received: by mail-ot1-x329.google.com with SMTP id q25so4766030otn.10; Wed, 06 Jan 2021 16:30:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i+MdCkuudr6UsbEYLQN0YBDU8shaZb13n6w7ypRhkSk=; b=ZQ3Ly3ppKHMEXNuwAae6TpUHZFKdEzOPkuIv13Fna+Q+2y1AQUFDZIFVZLS3QxRyDG VGuDQ4p56JNojfGkPr1UWaBW5sgKhoTmzihTD2WXckhd9eqxkoHJuStGhLBLPEW/MGnP 90taofZVATAKbjLk7n3JYoxw4KAsRRHG3l0+OPFrUWftERhCC5Zcp3hZ5SGnJvsYeyuT NAJnKw/VlXb2JsEscueCwpvmNPE5GsWTku+++M5FhejeijWxzTVt3rsb8zrwsMByUicS pcaZpdzRBbJ1OrVJ+35kgCy53n+NMC1E7btUBFXlSBOcqge9N6gu2Wl8e1Z3kkLWsXUF TEZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=i+MdCkuudr6UsbEYLQN0YBDU8shaZb13n6w7ypRhkSk=; b=ZT7q/mYZpo1dY0XP6V4jQNgu2flgUTXWK5ErTHcjdtYDeuv1db1ouEgNfFTOgKqTbY rZJB9QdQogjv1iDnjDxwZP4PhOLj45dmiSJwKaIUfrUaiXJLU4Vbe8l/A1aaOojdfZw/ zFvYf4PG6apiIXuB8zKsqhigWbAETLSNQjS7lY96TKDKJ3fDU5l/J27bje826tpNTj68 HcernS8Vj337GWYzr10fLaRH40Ic5eZLz9qCORQvdJBwM7JoBt4/0ysBJLrcwV7UUny7 QxupQ21/II9ovuf8krk7QKwHjtMxgXdUf/GKP5EOEhzk4x9Wdyl2RhQbeaTwYhTOrO5x KGPw==
X-Gm-Message-State: AOAM5318SmQD6MJUyHQLXSXkfZQ4YNpkoD1iYTnEIFiz1oZwdHoZnc6L z+LahhfLVpwkyrbUsJ4TqsNSDZL6FOx160kzYLQ=
X-Google-Smtp-Source: ABdhPJyG25Re1AR85ZoXwQA/0FxetU46ctkneFT3Qxnn8Ne1W5h9/sMvhrfzXQL1g1NDjBnCfLyjnwg2goHf+S32hAw=
X-Received: by 2002:a05:6830:104f:: with SMTP id b15mr5058802otp.155.1609979458352;  Wed, 06 Jan 2021 16:30:58 -0800 (PST)
MIME-Version: 1.0
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com>
In-Reply-To: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Wed, 6 Jan 2021 19:30:47 -0500
Message-ID: <CADyWQ+E1pVLcciOm-aBGu4aqErASp-eOUmPKrZWHvz+sgmKgzg@mail.gmail.com>
To: Seth Blank <seth@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b5fa0205b8448dd7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_OIKqqZti810YJnJHgFumswQgB0>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 00:31:01 -0000

--000000000000b5fa0205b8448dd7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

All

If you feel a need to be heard, that is also what the chairs are here for.

thanks
tim


On Wed, Jan 6, 2021 at 7:21 PM Seth Blank <seth@valimail.com> wrote:

> Working Group colleagues,
>
> Discussion on this list is increasingly out of scope and process,
> unproductive, and antagonistic. This behavior undermines the chartered wo=
rk
> of this group and will not be tolerated. We expect and require more civil
> discourse from our participants, and remind everyone that disciplining
> others is the purview of the chairs.
>
> The current phase of work of our charter (
> https://datatracker.ietf.org/doc/charter-ietf-dmarc/) is to deliver a
> standards track DMARC document based upon operational feedback. We are no=
t
> relitigating SPF, DKIM, DMARC, or ARC, adding new functionality, or
> rehashing other IETF documents or processes.
>
> When we kicked off DMARC bis, Alexey outlined a clear process:
> https://mailarchive.ietf.org/arch/msg/dmarc/rBWzfzDa_tOhaVdxFzUBYVi46QI/
>
> Only tickets opened by the Chairs or a document editor to the list are in
> scope for working group discussion. Everything else should result in the
> creation of a ticket to be discussed later, or off-list discussion. The
> Chairs re-affirm that all tickets will be brought to the list.
>
> To be clear: Before you hit =E2=80=9Csend=E2=80=9D on an email to this li=
st, make sure it
> is on topic for an open ticket and is not likely to escalate tensions.
> Otherwise, delete the message or start a private conversation that is not
> on the list.
>
> From here on out, due to the counter-productive nature of current list
> discourse, off topic or antagonistic discussions will be given a single
> public warning, per BCP 94 (https://tools.ietf.org/html/bcp94), which
> implies that further violations will result in a 30 day suspension for th=
e
> participant. The ADs have been consulted, and everyone should consider
> themselves warned.
>
> Finally, several members of this working group seem to be very effective
> at antagonizing each other. If a thread is spiralling, and a BCP 94 warni=
ng
> is given and not heeded, all active participants in the thread after the
> warning has been issued will be suspended, even if it=E2=80=99s to tell o=
thers to
> respect the warning.
>
> Now, let=E2=80=99s get back to our chartered work at hand and open ticket=
s.
>
> Seth, Tim, and Alexey, as Chairs
>
> --
>
> *Seth Blank* | VP, Standards and New Technologies
> *e:* seth@valimail.com
> *p:* 415.273.8818
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibit=
ed
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
>

--000000000000b5fa0205b8448dd7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e">All</div><div class=3D"gmail_default" style=3D"font-family:monospace"><b=
r></div><div class=3D"gmail_default" style=3D"font-family:monospace">If you=
 feel a need to be heard, that is also what the chairs are here for.=C2=A0<=
/div><div class=3D"gmail_default" style=3D"font-family:monospace"><br></div=
><div class=3D"gmail_default" style=3D"font-family:monospace">thanks</div><=
div class=3D"gmail_default" style=3D"font-family:monospace">tim</div><div c=
lass=3D"gmail_default" style=3D"font-family:monospace"><br></div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Ja=
n 6, 2021 at 7:21 PM Seth Blank &lt;<a href=3D"mailto:seth@valimail.com">se=
th@valimail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr">Working Group colleagues,<br><br>Discussion=
 on this list is increasingly out of scope and process, unproductive, and a=
ntagonistic. This behavior undermines the chartered work of this group and =
will not be tolerated. We expect and require more civil discourse from our =
participants, and remind everyone that disciplining others is the purview o=
f the chairs.<br><br>The current phase of work of our charter (<a href=3D"h=
ttps://datatracker.ietf.org/doc/charter-ietf-dmarc/" target=3D"_blank">http=
s://datatracker.ietf.org/doc/charter-ietf-dmarc/</a>) is to deliver a stand=
ards track DMARC document based upon operational feedback. We are not relit=
igating SPF, DKIM, DMARC, or ARC, adding new functionality, or rehashing ot=
her IETF documents or processes.<br><br>When we kicked off DMARC bis, Alexe=
y outlined a clear process: <a href=3D"https://mailarchive.ietf.org/arch/ms=
g/dmarc/rBWzfzDa_tOhaVdxFzUBYVi46QI/" target=3D"_blank">https://mailarchive=
.ietf.org/arch/msg/dmarc/rBWzfzDa_tOhaVdxFzUBYVi46QI/</a><br><br>Only ticke=
ts opened by the Chairs or a document editor to the list are in scope for w=
orking group discussion. Everything else should result in the creation of a=
 ticket to be discussed later, or off-list discussion. The Chairs re-affirm=
 that all tickets will be brought to the list.<br><br>To be clear: Before y=
ou hit =E2=80=9Csend=E2=80=9D on an email to this list, make sure it is on =
topic for an open ticket and is not likely to escalate tensions. Otherwise,=
 delete the message or start a private conversation that is not on the list=
.<br><br>From here on out, due to the counter-productive nature of current =
list discourse, off topic or antagonistic discussions will be given a singl=
e public warning, per BCP 94 (<a href=3D"https://tools.ietf.org/html/bcp94"=
 target=3D"_blank">https://tools.ietf.org/html/bcp94</a>), which implies th=
at further violations will result in a 30 day suspension for the participan=
t. The ADs have been consulted, and everyone should consider themselves war=
ned.<br><br>Finally, several members of this working group seem to be very =
effective at antagonizing each other. If a thread is spiralling, and a BCP =
94 warning is given and not heeded, all active participants in the thread a=
fter the warning has been issued will be suspended, even if it=E2=80=99s to=
 tell others to respect the warning.<br><br>Now, let=E2=80=99s get back to =
our chartered work at hand and open tickets.<br><br>Seth, Tim, and Alexey, =
as Chairs<br><div><br></div>-- <br><div dir=3D"ltr"><span><p dir=3D"ltr" st=
yle=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=
=3D"text-align:left"><span style=3D"vertical-align:baseline;white-space:pre=
-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span styl=
e=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-fami=
ly:Arial"> | VP, Standards and New Technologies</span></div><span style=3D"=
vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Ar=
ial"><div style=3D"text-align:left"><span style=3D"vertical-align:baseline"=
><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=3D"mailto=
:seth@valimail.com" target=3D"_blank">seth@valimail.com</a></span></div></s=
pan><span><div><span><b>p:</b></span><span> 415.273.8818 </span><span></spa=
n></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Aria=
l,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);li=
ne-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:1=
1pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertica=
l-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleuserco=
ntent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0L=
hbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" st=
yle=3D"border: none; height: 40px; width: 177px;"></span></p><p dir=3D"ltr"=
 style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-s=
ize:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(25=
5,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=
=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-space:=
pre-wrap">This email and all data transmitted with it contains confidential=
 and/or proprietary information intended solely for the use of individual(s=
) authorized to receive it. If you are not an intended and authorized recip=
ient you are hereby notified of any use, disclosure, copying or distributio=
n of the information included in this transmission is prohibited and may be=
 unlawful. Please immediately notify the sender by replying to this email a=
nd then delete it from your system.</span></font></p></span></div></div>
</blockquote></div>

--000000000000b5fa0205b8448dd7--


From nobody Wed Jan  6 18:14:09 2021
Return-Path: <dcrocker@gmail.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 3469A3A1124; Wed,  6 Jan 2021 18:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cD9fcaRncp3R; Wed,  6 Jan 2021 18:14:06 -0800 (PST)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01E753A02BB; Wed,  6 Jan 2021 18:14:05 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id v3so2606949plz.13; Wed, 06 Jan 2021 18:14:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=092goDxnGbJLGDxdhwJwXI2GYQ6UjkK7BWSXNA9v0dU=; b=nUpZF2HOUUJLNBAE6gBRUB4JrGGm8J18hdEsctB6IH2uLaSte+wK3fuTF6QYKX4bC8 c1aoD0ec4ekUR7/JN0T2Rn6d08S5I3fBQdn0van6cqwOTtfMxouLVZJc+qBW5YG99Spp WK+bUfjjcREmJSigWFBAWfqlz4XBiFMs8auca5Hf0UJfld+PFB3jON8/TSsEF94ze9dF vWRiEcEwuQ+4cCyoytZPs4HNgUMMIEHiN2STb8/t1UcO+fRn3KDtpEBcD0nY6zndMT2T m5dGA4tzXndcGHElegCT4MfQUtjzbW9pxzq2s/3TlyujEDJmCthNI4Mgr0rw8qlD7dhQ ixjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=092goDxnGbJLGDxdhwJwXI2GYQ6UjkK7BWSXNA9v0dU=; b=dgt+fDSLHsdgBhllu4KAawZ0dSsyb1Z4iFRlvtg+HVHrq/po3wU2/rPPwuNL3LqWdG WVBs9AzEwmpWoYAV5CFUmxpicZihKGTx/I/Zobsz6/Fuxds506HSWz8DtuWeQrQVnFpJ uhhJwT7f62x5WbsSgkuWEc1Cr9UYw8HTEvzDWMJOLmzgCZAuSDsDSEzVFse+c08QFCHd QZpOJW6nSPnxMKta1naU/roJdEw1slX9v4RylB+rVie4ckTd8YNp3UEjnj9DpKU5+cff 0BEF+ezjIRbRLwNWa63naVqyQh8H3wbvv7nm2QAC/cM5kvY1ky9RPeMASa0dKPv5irsc R7GA==
X-Gm-Message-State: AOAM530vxpYD9KfuYO+cCP4npppGvzCxdwbBiOo69+1EVU9Emi+SvPp2 KuZmwdkSbouOO3Qd68xv1sFl8Noksgw=
X-Google-Smtp-Source: ABdhPJwuqGCDZ1qLCmeLlUnFLhWPQ6i7i6AqbE3cjfrWfLX5S+p6GvZzMaWFpg5dzpowuNMKSoT7Xw==
X-Received: by 2002:a17:90a:cc06:: with SMTP id b6mr7080776pju.94.1609985645244;  Wed, 06 Jan 2021 18:14:05 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id x5sm3170866pjr.38.2021.01.06.18.14.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 18:14:04 -0800 (PST)
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
Cc: ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com>
Date: Wed, 6 Jan 2021 18:14:03 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/5ovZ8h_gilS3szRWeMG95ZY3e6Q>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 02:14:07 -0000

On 1/6/2021 4:21 PM, Seth Blank wrote:
> and is not likely to escalate tensions. 


Seth,

Sorry, but please provide guidelines for how anyone is supposed to 
evaluate their draft posting, in that regard?

And please do it with respect to the current list rather than in 
abstract and generic terms.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Wed Jan  6 18:37:56 2021
Return-Path: <mike@fresheez.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 B985E3A110D for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 18:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 ukOIf5xSUVwU for <dmarc@ietfa.amsl.com>; Wed,  6 Jan 2021 18:37:46 -0800 (PST)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72B6E3A146C for <dmarc@ietf.org>; Wed,  6 Jan 2021 18:37:46 -0800 (PST)
Received: by mail-pg1-x531.google.com with SMTP id 15so3757872pgx.7 for <dmarc@ietf.org>; Wed, 06 Jan 2021 18:37:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=4ktJQwb5UiZzFUTxH50A5sdHw12T0AUiw2oCSxNgFzc=; b=b08RdbMyTpwOacxJDfRymqrXXMQblMYj49A/DRBwd82QZl3+GFDfarSMB9GBurreYv mZJYTvAFklc0VuCdT21Qh1J+YgutEsxTGmYoC2WGCdYj5ZwqqYp8JY7jDUQ86lvqCO2d R5sXvpguxMn9u6YhVtGVCMCevHl5m3sREKZTpO04mBCHvAK3T3noq/QD4eesIYf83HFw ObEaPAp15PBw3F01XCPFQnvQ18A26m5R1V8wULQHaFYi99NCRY24jxkSYQxTXM4NWA3c BrtwLODGflz6nxXe6a7Yyn9BitLnwaQWT+50m1eeGzJ7hzVb/ueXZ3u8Apag/N/NoeUA VtjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=4ktJQwb5UiZzFUTxH50A5sdHw12T0AUiw2oCSxNgFzc=; b=l3hqjbA2Oyy5ou+7l5hlKIxFjNKDDL9VrVhk52HssI4dV+Zs7SBT355RHJR6u3DbfV CaeFoZSyX2aRCnqqg49+MTVMrnhrtz3W75U2ZzcboIoGO5ualqd+MPpsNc7hiuGQUBRR EEdIDD/pPV9RIaf9yBNJVnapeoVxu9omdwVlHaBxGmaBBsYOli8rjjW6s6dJn2Km5OP/ AbRWoa3emXxrnsJRpH+Dqir1wy8Ve3xB9acBRFs5154SDBgVzX1wimbci+6lOO2lqEMR Ja8T9w5PWYUfDwz7oL8bkQ7ll2Obr5VCURs20BYHunvjdYmOJDTQ1DW9qDmMtiUia9NJ R+xw==
X-Gm-Message-State: AOAM531OVxMcDcJwxHj+xhbh1VqUflf1Hed3KAjntlgBWcF+QteCsiRW ZAGrRlpfacyPJPYbdcwdbrgeEUXUl6jVGnli
X-Google-Smtp-Source: ABdhPJwP6TsS1bRqxQof91H/XjKjNY/dlyelwMtSoxg4HLzxAnlEEqZw77nm1yFKjXhX15lU3vYrrw==
X-Received: by 2002:a65:6116:: with SMTP id z22mr7696767pgu.264.1609987065584;  Wed, 06 Jan 2021 18:37:45 -0800 (PST)
Received: from mike-mac.lan (107-182-39-88.volcanocom.com. [107.182.39.88]) by smtp.gmail.com with ESMTPSA id a22sm3830270pfg.49.2021.01.06.18.37.44 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 18:37:44 -0800 (PST)
To: dmarc@ietf.org
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <c84b0c20-a3e5-35c7-93b6-397ad5295637@mtcc.com>
Date: Wed, 6 Jan 2021 18:37:43 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mMnoXQ3jnMtCcvHYnFbgBV-e4w4>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 02:37:51 -0000

On 1/6/21 4:21 PM, Seth Blank wrote:
> Working Group colleagues,
>
> Discussion on this list is increasingly out of scope and process, 
> unproductive, and antagonistic. This behavior undermines the chartered 
> work of this group and will not be tolerated. We expect and require 
> more civil discourse from our participants, and remind everyone that 
> disciplining others is the purview of the chairs.

I completely recommend everybody read and understand this paper. It 
doesn't address every answer to every question, but it does allow us to 
be much more data driven rather than uninformed conjecture. It's fine to 
dispute its conclusions, but it is not fine to dispute it to just 
dismiss it out of hand based on feelings or bias. It really gave me some 
grounding from the gut feelings which doesn't confirm much of anything. 
DKIM and DMARC need to more data and much less conjecture.

https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf

Mike



From nobody Wed Jan  6 20:47:15 2021
Return-Path: <tjw.ietf@gmail.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 ABF2F3A0CC1; Wed,  6 Jan 2021 20:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level: 
X-Spam-Status: No, score=-1.097 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 b_wLDg7bfQqu; Wed,  6 Jan 2021 20:47:12 -0800 (PST)
Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C5683A0EB3; Wed,  6 Jan 2021 20:47:11 -0800 (PST)
Received: by mail-oi1-x232.google.com with SMTP id q25so6062944oij.10; Wed, 06 Jan 2021 20:47:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UykRh1Vq0JXsEZ8BC3UbxexnQC0kNRj8dqJUcxAmAdc=; b=Zk3hES1pXATxYitq1b//1kFpWwoPo3agyFuuudTFne8pIXihe6uY3YGmOwG5yVUo/R 1sT5qfGb3r9w5UKTbD3aNVw+VMpk+5OiD/4xqZC0uf+2z7F0dEAzQd+VBPnMAs17b05Y szfzxNXvC+kWDqXWvf0R5ITNZP2uIlkoC+omItRvPmXkPbKvM6v+s6EbKypR1Md+a2l1 sQ0Ru0qLppa9qTaSkKWap70/+eis7EkZQJcpg6a9zkqywHA2TIq44am9SV9sHeXgsjJA kjeuLDPHToQgqzHSnj/iLgy0NFbpOpKAv64SRek2nFQqWs/QhZky3MpNbjuZwpfOSVif SPPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UykRh1Vq0JXsEZ8BC3UbxexnQC0kNRj8dqJUcxAmAdc=; b=nUuTCZvvZuoDq0suFmsccZVXDbnzh7oECm7SMIjER3qdxxxFJ2P6x6kCxB++6v3lhb rN2kV1YQFURJ2zNS1wwwfP/h0bldYcZ4EpXtMGPT8i1ue+lGhWQjEqcIzIaQsoqHzkO4 SYvtRT911psxVXiyVjC+L6n+vJuHWrty91Oxa0A80eDTBgVKy2H+8i1L6DlbufGPo9U7 OPKo7hS4YOO/6hTiizuMQYrsqCvw23eOTXhFTxyEhDD5QRK9oOFs0H+4tFDjcQBXiBPn j0tVC06mN/Y1qgqPLtSboeUqs21KWUOzQYQvPALL6N3zxXATcWOjfHEWKgUPl2i4tBUs uZ1w==
X-Gm-Message-State: AOAM533b7/mrPTLx2VXilE8Oh0MYrcXNmkM3KfIhJx+704ZUp5fxGN6z IiTpMWbCqGAujE0RHjhzNk0Ui7/TuJnO3nWG9YA=
X-Google-Smtp-Source: ABdhPJzPbwNofRkRB/OcjFSoLcqcW0Gi/dWLIctfU5XnVCEukXWY28FukziRvzKEYRToZVz6dUB/FxX45xCtqrnNcks=
X-Received: by 2002:aca:210c:: with SMTP id 12mr293981oiz.45.1609994831282; Wed, 06 Jan 2021 20:47:11 -0800 (PST)
MIME-Version: 1.0
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com> <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com>
In-Reply-To: <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Wed, 6 Jan 2021 23:47:00 -0500
Message-ID: <CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: Seth Blank <seth=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>,  ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000002442205b848229a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/j9RUrhAMi-8v0xJ4dUzeiWUgCXw>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 04:47:14 -0000

--00000000000002442205b848229a
Content-Type: text/plain; charset="UTF-8"

Dave

You should have a pretty good idea based on these arguments over the past
few months to have a sense of how responses will be received. Take a step
back and take a second read.

This goes for all. Folks have very specific views of how they think mail
should work in regards to DMARC/DKIM/SPF/ARC/etc and instead of discounting
the discussion because the two views aren't identical, try to be a bit
open minded.

Tim



On Wed, Jan 6, 2021 at 9:14 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 1/6/2021 4:21 PM, Seth Blank wrote:
> > and is not likely to escalate tensions.
>
>
> Seth,
>
> Sorry, but please provide guidelines for how anyone is supposed to
> evaluate their draft posting, in that regard?
>
> And please do it with respect to the current list rather than in
> abstract and generic terms.
>
>
> d/
>
> --
> Dave Crocker
> dcrocker@gmail.com
> 408.329.0791
>
> Volunteer, Silicon Valley Chapter
> American Red Cross
> dave.crocker2@redcross.org
>
>

--00000000000002442205b848229a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e">Dave</div><div class=3D"gmail_default" style=3D"font-family:monospace"><=
br></div><div class=3D"gmail_default" style=3D"font-family:monospace">You s=
hould have a pretty good idea based on these arguments over the past few mo=
nths=C2=A0to have a sense of how responses will be received. Take a step ba=
ck and take a second read.=C2=A0</div><div class=3D"gmail_default" style=3D=
"font-family:monospace"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:monospace">This goes for all. Folks have very specific views of ho=
w they think mail should work in regards to DMARC/DKIM/SPF/ARC/etc and inst=
ead of discounting the discussion because the two views aren&#39;t identica=
l, try to be a bit open=C2=A0minded. =C2=A0</div><div class=3D"gmail_defaul=
t" style=3D"font-family:monospace"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:monospace">Tim</div><div class=3D"gmail_default" style=
=3D"font-family:monospace"><br></div><div class=3D"gmail_default" style=3D"=
font-family:monospace"><br></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 6, 2021 at 9:14 PM Dave Crocke=
r &lt;<a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank">dcrocker@gmai=
l.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">On 1/6/2021 4:21 PM, Seth Blank wrote:<br>
&gt; and is not likely to escalate tensions. <br>
<br>
<br>
Seth,<br>
<br>
Sorry, but please provide guidelines for how anyone is supposed to <br>
evaluate their draft posting, in that regard?<br>
<br>
And please do it with respect to the current list rather than in <br>
abstract and generic terms.<br>
<br>
<br>
d/<br>
<br>
-- <br>
Dave Crocker<br>
<a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank">dcrocker@gmail.com<=
/a><br>
408.329.0791<br>
<br>
Volunteer, Silicon Valley Chapter<br>
American Red Cross<br>
<a href=3D"mailto:dave.crocker2@redcross.org" target=3D"_blank">dave.crocke=
r2@redcross.org</a><br>
<br>
</blockquote></div>

--00000000000002442205b848229a--


From nobody Wed Jan  6 20:52:06 2021
Return-Path: <dcrocker@gmail.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 EDCFD3A0EB3; Wed,  6 Jan 2021 20:52:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 w4Sek4PiLEzX; Wed,  6 Jan 2021 20:52:04 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9DA83A0E80; Wed,  6 Jan 2021 20:52:03 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id m6so3128511pfm.6; Wed, 06 Jan 2021 20:52:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=59UTueCuNkvD7kVj0OEGNs36lo5ncH7SvuCSG+PY100=; b=ic8mzXkcfZGWBo81ZqikMDZGCvAdGGAWFIYjmjwtSY6tn64aut0xYHZBwmdhcNjnGX 0ghRykYUYrzhzfA5SgDFJX1Vo7ffa2ubkOIitjjXFz/vV8Fp6oA16pD2PvG+b/M9XeAD e7wcjDXYig8YrvlDelaepGFe2F44tgvgEAJ9D2qXitYqmkxEHsDgEdq2qiynPc9/hCK0 +kWDh+I3+eHqseBP5bGXTfP//zw/wXuDFQac0BSA3S9Mwkyk5+NDx0vkgEngpgv8rzvX m1/7Pt8t5ivA199OzufvDdKwXQZaqQ0zkbjjlLc2MwAZ3zZb6/R68K/GUlTZRklt6kfN j43w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=59UTueCuNkvD7kVj0OEGNs36lo5ncH7SvuCSG+PY100=; b=uXOgYR+UL3GbmhJWfKiwdnIGnXLAGkYSVjAxCbUY+uyRivbDM6ab9qSb4OJa8a32mW s88yLJLVwvQVmh/gcOY2IH4KTTK5JEY6BqAqxum61S3ZRKQCGSDI0ddye6eTZObttbC9 mX4Qez0Nm0+zlKzRHGzOo7PFZTMxrGEJDrT2h9689U9t2AnYIu5EyYnDehpOIK5dHdxZ 1DMlv/A+P3BK/gJAG+f8k8lBTESg/mSzsTcngCG/vwn07Nz+Pk7Rpe1XJnDGgCMeeXa7 GrxfQzQjqdIf0aXfh6qzasIZ7yGszgr2EYXftEqWlJJNy6cBlDuY430WLoemXxHJsz6u DNSA==
X-Gm-Message-State: AOAM532yENN6o/3Grvd+R3uuDVdnmIeIyjHWAsLyga3Qyfuu/dNvSMq2 uiYekoUCVeiSQy8HxAk/8vuOmWbFEWw=
X-Google-Smtp-Source: ABdhPJwq515wZLrdKntogKWBORTSXnx/xGr1GUXJxhm5I6I5V3fm3wo4HWGVdfVFCacccyXR3x151A==
X-Received: by 2002:a63:5642:: with SMTP id g2mr26296pgm.434.1609995123120; Wed, 06 Jan 2021 20:52:03 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id gm18sm544715pjb.55.2021.01.06.20.52.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Jan 2021 20:52:02 -0800 (PST)
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: Seth Blank <seth=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>, ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com> <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com> <CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <d8dd3487-48b7-bd35-90fb-60c1d62eb39f@gmail.com>
Date: Wed, 6 Jan 2021 20:52:00 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8D922E9B2A46ECBECB57897F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_AhzKnv63NUn-7ZxaG6VmWQWTDs>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 04:52:05 -0000

This is a multi-part message in MIME format.
--------------8D922E9B2A46ECBECB57897F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 1/6/2021 8:47 PM, Tim Wicinski wrote:
> You should have a pretty good idea based on these arguments over the 
> past few months to have a sense of how responses will be received. 
> Take a step back and take a second read.
>
> This goes for all. Folks have very specific views of how they think 
> mail should work


Tim,

This has nothing to do with differences in opinion.  It has to do with 
his persistent inability to conduct civil discourse in the face of 
disagreement.

Disagreement is fine.  Abuse is not.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


--------------8D922E9B2A46ECBECB57897F
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/6/2021 8:47 PM, Tim Wicinski
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com">
      <div class="gmail_default" style="font-family:monospace">You
        should have a pretty good idea based on these arguments over the
        past few months to have a sense of how responses will be
        received. Take a step back and take a second read. </div>
      <div class="gmail_default" style="font-family:monospace"><br>
      </div>
      <div class="gmail_default" style="font-family:monospace">This goes
        for all. Folks have very specific views of how they think mail
        should work <br>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>Tim,</p>
    <p>This has nothing to do with differences in opinion.  It has to do
      with his persistent inability to conduct civil discourse in the
      face of disagreement.</p>
    <p>Disagreement is fine.  Abuse is not.<br>
    </p>
    <p>d/<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Dave Crocker
<a class="moz-txt-link-abbreviated" href="mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------8D922E9B2A46ECBECB57897F--


From nobody Wed Jan  6 21:05:49 2021
Return-Path: <tjw.ietf@gmail.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 DDECF3A0127; Wed,  6 Jan 2021 21:05:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level: 
X-Spam-Status: No, score=-1.097 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CfrQuge-I_v1; Wed,  6 Jan 2021 21:05:42 -0800 (PST)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8280A3A0163; Wed,  6 Jan 2021 21:05:42 -0800 (PST)
Received: by mail-ot1-x333.google.com with SMTP id i6so5259108otr.2; Wed, 06 Jan 2021 21:05:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZjBtm2fHPerFAa45k5igLyGxy8JN6b/M3ACRAZRjI9k=; b=BOvOtYwad7IckpT9NmAEPJJPUINcKPiVA7NpnM/Y+KLVdyUUP7uLjqY3bYo1o+sN60 kOKbMky+R1DAL9WcIPqrYRS9kdybCm2qTaCZPk/0bS4FJQGUTvt6TS6z6ohJKLEui2h7 w0SlArl/Yfigw/10PWhSxZXi7sWUOvaICDjUfmQjPOsw1W1cdlstuxnAnqXIPs7yujah t9Q8lgvF9QtJmtnT7v6imT1+Cs6xFMa9VQW+E5rYGszsvoT1D6At3g+pNilxis7dqqGI 00zY/bGxFK5B/rtfLhPKUFj7THVHrU0LLfHnJmLDBYgfRRwY2G8oDkaUbZdLsU0NSXLO tnQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZjBtm2fHPerFAa45k5igLyGxy8JN6b/M3ACRAZRjI9k=; b=XHZ0nbA1lZ3FJ9MliHYrcAezMbfN34YNQumqrXW/qhyZhwLPVR5x5K7oy7OpXLZRYz D8TlIR6T1sCpDa39nQ/alXj+MHYBziV/bEiNINF8pGCw3KdFJAxGPMnKUJ54W7fqrney MSzaCyvtIbC/pWMo8aEmXlGhwJyIz0DGrY6xP6BUJL9AhFt8ilKFDij5F7ltI20P1h11 pyoqYrAej1izhKeDb6D6zlOtVyXmp4CEj5G9zfwPVuZEegJncLUcnA0PyrAhJDgK66qj MqSU4354QLIWToxVgzU34CK3+lZwKMKoXyOL/Q3Q1aKmVF7n6aQqFBA5Oor5Fyqjn1h1 UiAw==
X-Gm-Message-State: AOAM5335qhrwKvx0jPtKbdfbYLJcxGlU3u4LNqcJinUzKpdlyfsyNt1F fDd9+4cqSyVZArBsedHmEBl3EJIkwhbv1WT7tz4=
X-Google-Smtp-Source: ABdhPJz526VpD7JjjojK3CgHGJJkHS/y87x9CqoHactY6VyA3JEewYbUvVIY9VunWZQZ5nG5cd712j37sny2YGtHbFM=
X-Received: by 2002:a9d:3ef6:: with SMTP id b109mr5620341otc.288.1609995940815;  Wed, 06 Jan 2021 21:05:40 -0800 (PST)
MIME-Version: 1.0
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com> <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com> <CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com> <d8dd3487-48b7-bd35-90fb-60c1d62eb39f@gmail.com>
In-Reply-To: <d8dd3487-48b7-bd35-90fb-60c1d62eb39f@gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Thu, 7 Jan 2021 00:05:30 -0500
Message-ID: <CADyWQ+GCPX8jCQJmnGNgCX1mtNScyOj30TmR5C5J9bopWpiHxw@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: Seth Blank <seth=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>,  ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000246e3005b8486464"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/88obQj_Vmr1uuQrPfGbAnVZyyJ8>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 05:05:47 -0000

--000000000000246e3005b8486464
Content-Type: text/plain; charset="UTF-8"

Dave

I agree.  But it seems one person's civil discourse is another person's
abuse.

Perhaps we can start from the position that nobody is attempting to insult
or abuse one another.
I don't believe anyone here consciously wants to be abusive to anyone else.
I have been accused of being an optimist.

tim


On Wed, Jan 6, 2021 at 11:52 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 1/6/2021 8:47 PM, Tim Wicinski wrote:
>
> You should have a pretty good idea based on these arguments over the past
> few months to have a sense of how responses will be received. Take a step
> back and take a second read.
>
> This goes for all. Folks have very specific views of how they think mail
> should work
>
>
> Tim,
>
> This has nothing to do with differences in opinion.  It has to do with his
> persistent inability to conduct civil discourse in the face of disagreement.
>
> Disagreement is fine.  Abuse is not.
>
> d/
>
> --
> Dave Crockerdcrocker@gmail.com
> 408.329.0791
>
> Volunteer, Silicon Valley Chapter
> American Red Crossdave.crocker2@redcross.org
>
>

--000000000000246e3005b8486464
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e">Dave</div><div class=3D"gmail_default" style=3D"font-family:monospace"><=
br></div><div class=3D"gmail_default" style=3D"font-family:monospace">I agr=
ee.=C2=A0 But it seems one person&#39;s civil discourse=C2=A0is another per=
son&#39;s abuse.=C2=A0</div><div class=3D"gmail_default" style=3D"font-fami=
ly:monospace"><br></div><div class=3D"gmail_default" style=3D"font-family:m=
onospace">Perhaps we can start from the position that nobody is attempting =
to insult or abuse one another.=C2=A0</div><div class=3D"gmail_default" sty=
le=3D"font-family:monospace">I don&#39;t believe anyone here consciously wa=
nts to be abusive to anyone else.=C2=A0</div><div class=3D"gmail_default" s=
tyle=3D"font-family:monospace">I have been accused of being an optimist.=C2=
=A0</div><div class=3D"gmail_default" style=3D"font-family:monospace"><br><=
/div><div class=3D"gmail_default" style=3D"font-family:monospace">tim</div>=
<div class=3D"gmail_default" style=3D"font-family:monospace"><br></div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On W=
ed, Jan 6, 2021 at 11:52 PM Dave Crocker &lt;<a href=3D"mailto:dcrocker@gma=
il.com">dcrocker@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>On 1/6/2021 8:47 PM, Tim Wicinski
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div class=3D"gmail_default" style=3D"font-family:monospace">You
        should have a pretty good idea based on these arguments over the
        past few months=C2=A0to have a sense of how responses will be
        received. Take a step back and take a second read.=C2=A0</div>
      <div class=3D"gmail_default" style=3D"font-family:monospace"><br>
      </div>
      <div class=3D"gmail_default" style=3D"font-family:monospace">This goe=
s
        for all. Folks have very specific views of how they think mail
        should work <br>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>Tim,</p>
    <p>This has nothing to do with differences in opinion.=C2=A0 It has to =
do
      with his persistent inability to conduct civil discourse in the
      face of disagreement.</p>
    <p>Disagreement is fine.=C2=A0 Abuse is not.<br>
    </p>
    <p>d/<br>
    </p>
    <pre cols=3D"72">--=20
Dave Crocker
<a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank">dcrocker@gmail.com<=
/a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a href=3D"mailto:dave.crocker2@redcross.org" target=3D"_blank">dave.crocke=
r2@redcross.org</a></pre>
  </div>

</blockquote></div>

--000000000000246e3005b8486464--


From nobody Thu Jan  7 02:14:32 2021
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 0A94C3A0E80 for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 02:14:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 YtnbZIhklHjS for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 02:14:29 -0800 (PST)
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 8DA2F3A0E82 for <dmarc@ietf.org>; Thu,  7 Jan 2021 02:14:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1610014465; bh=1u6io9kHevL9cxahP41S5Wi4/8Vx25K7DhsmlqLnCno=; l=1218; h=To:References:From:Date:In-Reply-To; b=AuW+JnTNPtNqWpCan59Hq4hbZT2Lwa2W6OFR4pDLP/i+pzV3hWmnll9dl7A+HMcPG Nt54MA4I5JUih2wumuksdn+tT4YA9ukL21/SAx/Mf/EZlDIP5t+6qSmMWBZYVTXdGn US7qeUtoixLITX5uLljF5CDqiStdox+PIkKw2Enb8551G72Gc4wEN+ZpKvqUe
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC056.000000005FF6DF01.000016B6; Thu, 07 Jan 2021 11:14:25 +0100
To: Dave Crocker <dcrocker@gmail.com>, Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com> <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com> <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com> <fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com> <b3d77e5a-8024-218f-cd3c-6286f9ecd7dc@mtcc.com> <a7e6944a-363c-9d40-9cd9-1fe640ea6cfb@gmail.com> <e509cd25-19f9-ae75-ba62-30173af6857b@mtcc.com> <aee386fe-54ee-a01c-bd0c-80eb940ca185@gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <72e6d5f9-1dc2-1d32-25ce-e5b208895bd8@tana.it>
Date: Thu, 7 Jan 2021 11:14:24 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <aee386fe-54ee-a01c-bd0c-80eb940ca185@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZhKw9kOIPOYRnoBt399QBAzaL4g>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Thu, 07 Jan 2021 10:14:31 -0000

On Wed 06/Jan/2021 00:55:41 +0100 Dave Crocker wrote:
> On 1/5/2021 3:50 PM, Michael Thomas wrote:
>>>
>> Quit cutting out needed context to make your points. The study directly 
>> contradicts your categorical statement.
> 
> Except that it doesn't.
> 
> Feel free to provide an serious explanation of why you think otherwise, but 
> please put some effort into accurately representing what I said or what the 
> study shows.  Attention to detail will help.  Conclusions are less important 
> than showing your work.


The report says:
     This returns the email-opening rate of 53.4% and 48.9%. Among these users,
     the corresponding click-through rates are 48.9% (without security
     indicator) and 37.2% (with security indicator) respectively. The
     results indicate that security indicators have a positive impact to reduce
     risky user actions.
https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf


You said:
     My point is that we have decades of belief that it's useful but no
     demonstration that it actually is.  And we have history such as the EV
     effort, showing that it isn't.
https://mailarchive.ietf.org/arch/msg/dmarc/r7unHaCXKKFeotbjU1pL-Jx4f_o


Best
Ale
-- 









From nobody Thu Jan  7 04:10:21 2021
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 668F23A100D for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 04:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level: 
X-Spam-Status: No, score=-2.381 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.262, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 8ok2uDFoJOi9 for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 04:10:17 -0800 (PST)
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 9BE633A100C for <dmarc@ietf.org>; Thu,  7 Jan 2021 04:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1610021413; bh=oh0bF7yc+qyPnFnyHtG0tF86QjOAtmW7vQe4zVyhl8o=; l=6812; h=To:References:From:Date:In-Reply-To; b=CXtLUIe5rNxlC1WQlhfUv2kNEHGB574btIUjBaJjjQ3AKun0NOuIb+ybqp9BRJZPj o6gMsmKCI8PTF198uWcQshSiDZFCu/yuieWObP+49K52emUVhfcuKO9b8+6ex0TeWL vgcPy6hxX4rCI54kUjtT8tC6jGOT537Gp3aCOsvGtvNHsbFFWmf8DS1jKGCBP
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC026.000000005FF6FA25.0000236D; Thu, 07 Jan 2021 13:10:13 +0100
To: dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <ECBF25D9-F05C-4DE9-AD97-6D4D01B01B57@wordtothewise.com> <CAH48ZfyTUNg2_PnHFHEtZFemfvBgWBMpGLphGTL=3mRvD9o==w@mail.gmail.com> <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <5effe248-6364-20f3-5ead-c5bb6a2a3afb@tana.it>
Date: Thu, 7 Jan 2021 13:10:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <D3A51087-6E1A-465F-89CD-63172E8075D4@wordtothewise.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/TOWVBzt10FAhfPqwsNdV7MAD1zE>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Thu, 07 Jan 2021 12:10:19 -0000

On Wed 06/Jan/2021 13:52:33 +0100 Laura Atkins wrote:
>> On 6 Jan 2021, at 12:29, Douglas Foster <dougfoster.emailstandards@gmail.com> wrote:
>> 
>> I am no fan of header rewrite, but...
>> 
>> If you are going to talk about "Trust Indicators", we need to define terms, which has not been done.   Here are my definitions:
>> - The From header is an Identity Assertion.
>> - DMARC is an Identity Verification technique.
>> - A text message saying, "This message verified by DMARC", is a Trust Indicator.
>> My definitions are consistent with the way that that one study used a trust indicator.   Using these definitions, From rewrite has nothing to do with Trust Indicator research.  If anyone wants to assert different definitions, please get them on the table.
>> 
>> The fact that users complain about From rewrite is proof that they look at the information.    This is because it is an Identity Assertion, not a Trust Indicator.
> 
> The header rewriting being proposed - that is header rewriting by the ESP so that the messages that go through their system are rewritten to point to the ESP and not the author of the message - means that the identity assertion is disconnected from the context of a message.
> 
> Want to know what mail goes through ESPs? Bank mail, social media mail, marketing mail. Billions of emails a day go through ESPs that you have and have not heard of.
> 
> The proposal at issue is that these ESPs be allowed to rewrite the From  address any message they handle to point to an email address they control. This disconnects the identity in the 5322.from address from the actual sender of the message.
> 
> Most users may know who constantcontact are or mailchimp because they advertise widely. Some might have heard of GoDaddy but do you know what the company name of the GoDaddy ESP is? I don’t off the top of my head.


The options we have depend on both identities, the ESP customer, be it a bank 
or a girl scout trooper, and the ESP itself.  If the customer avails itself of 
a free-mailbox provider, the options depend, in turn, on what ancillary 
services does the latter provide.

Ancillary services may include publishing external selectors on behalf of the 
ESP, and authorizing an ESP to use submission on behalf of its customer.  They 
both result in better authentication than From: rewriting.  To cope with girl 
scout troop at a free-mailbox provider, an ESP could also get itself an account 
at that provider and gain DMARC authentication that way.

For cases where the above options don't apply, From: rewriting is an 
established workaround.  We ourselves are using it on this list.  Its 
effectiveness depends on the reputation of the ESP domain.  It might be better 
known than the customer domain, in which case the customer itself may prefer it 
for increased deliverability.


>> I accept that actual Trust Indicators have a small effect, but rounding down  to zero seems like an overstatement.   When fighting malware, I will take all the help that I can get, even small help.
> 
> And now we have a malware company that rewrites headers to point to a domain they own and it passes DMARC and is given a Trust Indicator. Recipients are used to seeing domains they don’t know or understand send trusted mail from their bank, or their girl scout troop, or their social media company. They have no reason to distrust the unfamiliar identity assertion in the from address.


Phishing happens irrespective of our recommending From: rewriting or not.

If we do specify it, we could say something like:

DON'T:
From: "Someone <user@good.example>" <me@devil.example>

DO:
From: "Someone via devil" <me@devil.example>
Reply-To: Someone <user@good.example>


It seems Mailman is careful enough when it rewrites entries like:
From: "user@example.com" <user@example.com>

The latter is an example of bad display names.  It can be accepted, as it's 
sadly so common, as long as the addresses match.  Mismatched addresses like in 
the first example should be interpreted as a sign of phishing, and hence 
trigger filtering or distrust indicators as needed.

Can we say that?

Would such kind of normative help to improve filters and trust indicators?


>> Domain administrators are within their rights to block any incoming message for any reason.   Users routinely work with their domain administrators to ensure that the messages that they want get accepted and messages that they do not want get blocked.    If users and domain administrators cannot solve their differences, the user can communicate using a different domain.  If DMARC produces false positives that cannot be resolved by this process, we would do well to ask why.
> 
> Header rewriting doesn’t solve false positives, it increases the chances of them. Header rewriting for commercial messages by ESPs means that folks attempting to masquerade as a legitimate company have a RFC recommended way to evade DMARC and pretend to be the company they’re attacking.


People cannot pretend /to be/ another company, they can only pretend to /be on 
behalf of/ it.  Shouldn't we train users to look at the name after the strudel?

Web browsers came to the conclusion of highlighting the organizational domain 
part of URLs.  (It is one of PSL's uses.)  Do we have data on the effects of 
doing so?


> This isn’t random speculation, this is what is going to happen. We've spent the last 20 years watching spammers and phishers do everything they can to get mail out. If the DMARC RFC says ‘ESPs should rewrite headers to avoid DMARC policies on mail going through the ESP’ then we’ve just made DMARC utterly worthless. We’ve also set up every company that is currently using DMARC p=reject to be attacked in ways they cannot tract.


Keeping in mind that that attack path is here to stay anyway, we can choose to 
either content ourselves with mentioning it in the Security Considerations, or 
also suggest to use it as a legitimate workaround.

CON:
DMARC may seem to be utterly worthless, since it can be circumvented so easily.

PRO:
The workaround increases deliverability of mail flows from domains with strict 
policies.


IMHO, there is value in certifying DMARC's main identifier.  Increasing the 
deliverability of strict policies will invite more domains to get beyond 
p=none, especially if, eventually, mail from domains with p=none or without 
DMARC record at all is going to be treated with some suspicion.

Mailing lists are going to stick on From: rewriting for the foreseeable future, 
and not standardizing that workaround while we're using it is somewhat 
schizophrenic of our stance.  Undoubtedly, mailing lists are doomed to 
disappear, in the long run.  Meanwhile, they have full citizenship in the email 
panorama.


Best
Ale
-- 




















From nobody Thu Jan  7 05:21:29 2021
Return-Path: <johnl@iecc.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 772DD3A10BC for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 05:21:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=BaYHVw9U; dkim=pass (2048-bit key) header.d=taugh.com header.b=rkEaC73M
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 wBsWBH98kGw2 for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 05:21:19 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 BE3F43A10CF for <dmarc@ietf.org>; Thu,  7 Jan 2021 05:21:18 -0800 (PST)
Received: (qmail 23804 invoked from network); 7 Jan 2021 13:21:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=5cf9.5ff70acd.k2101; bh=mLQd1gf095EueVDLW1yMSqpPwFpBBJk19CXY3B5JiiA=; b=BaYHVw9ULwuG08fcIqsNAdPpWZNoyjivmG/HILnOcgW5r6p4dLl8zoum/EAn7c5ihoHKqgvsGQeiM0j2vPJPj5K/MqxK+UDM+Zr8kFsUFMrvxxh9qTL61IkYR9p8yzcpaH9S4TOSEZU8TI3x0jFChYl8hSuWY4shVAYnXpRInTOnpf9A+cxS3CCAlvocvxPkx+MKL4rSmydx6sCvHqvp12bqJwOfRFuYw7PUrpXhqSh53c2LE87CVhNzzAnv9q+GLDTrBgSmOr6EJ6aNCLCpqCnpimMtmF2lDpOSYlZbNp62SaX+NjiI97ng3/t57mfadNDJvEqpXrJtZJQQ7TTuuA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=5cf9.5ff70acd.k2101; bh=mLQd1gf095EueVDLW1yMSqpPwFpBBJk19CXY3B5JiiA=; b=rkEaC73MSCNHhV5a842qbp4yjV7+Q9Vn+WLTayy1jqenNtT3hEhW/hpgK/Uv9Kr8B+IZ1wqSGLbTadu2uoXvmlWVFvo5Bc2fHfKE/uX3McdStSWLnyq3WrkPD+ajvB85MTrRq7YG72rCMWxy3gk4SmQsYGgzJkxRJQBHoL2FQjk7AdzahYx+dSKbIc0BNNwS6UkYT2BBLDyO1U1Y7uKtSuDsTuqQBUxm07VGjE5xklziEW7alrGQcfKMU/j0d10/n07t/YZR3iHyxiBGbIjWv96nr858nQ9h43rlyFjIa90t9tzsqKTaaRy0TueTzG60oq/I0weFb0aMVoUATzlJ+g==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 07 Jan 2021 13:21:16 -0000
Received: by ary.qy (Postfix, from userid 501) id DA29B5F75A08; Thu,  7 Jan 2021 08:21:15 -0500 (EST)
Date: 7 Jan 2021 08:21:15 -0500
Message-Id: <20210107132115.DA29B5F75A08@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <5effe248-6364-20f3-5ead-c5bb6a2a3afb@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QyziSgxQaXzqgrQPF76qLbq1ajk>
Subject: Re: [dmarc-ietf] Header Rewriting
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: Thu, 07 Jan 2021 13:21:28 -0000

In article <5effe248-6364-20f3-5ead-c5bb6a2a3afb@tana.it> you write:
>Can we say that?
>
>Would such kind of normative help to improve filters and trust indicators?

No. As Dave has repeatedly reminded us, when we guess about user
interface features, we invariably guess wrong.

Please can we stop this unproductive thread?

R's,
John


From nobody Thu Jan  7 06:38:27 2021
Return-Path: <barryleiba@gmail.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 BE74D3A11AF; Thu,  7 Jan 2021 06:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 aOfmnRiZO6RE; Thu,  7 Jan 2021 06:38:23 -0800 (PST)
Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44B9B3A11A2; Thu,  7 Jan 2021 06:38:23 -0800 (PST)
Received: by mail-lf1-f41.google.com with SMTP id h22so15124146lfu.2; Thu, 07 Jan 2021 06:38:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bVnd1tsydqjiOhGhYlmH8Nepuh12KZ0tQKvFVPCyH2A=; b=MaP4nP94XAMHiFjmAjBrXK/c+4KnwtKiVOvVjps4WVyLDl/o+5vqVYQVqHN4TLaMcu YFei1v4X6ZVMwIKNJYEMth+dj/UzDWi03txtkqWRPKnHsV5pfjn2A2g/Jv0vVHNMxrQ+ KQGKljVuN1VKK+E1CwCCDda4InoJwAvGiaNf21fWq7bLEM1Th5uE30lorHV7qnI4zjJo NKkAxfn4hgcmHNRYCAiQf3eyhYYEAhxhnNlTc75wU/tPfB2CFuKjVVoxmjcBMvs9LHtO 74BHYJcULZffIq0sboWstjxEQt7Y3xjyxUXPzf24m9u7mJ21dTUtKi8JlsmTN9tPJhfy 7uVQ==
X-Gm-Message-State: AOAM531ZvMk5iLNmaACOKYJBVyCph7lDpvnMgI8JNJHl6VtW2PJSeGio /sxaUMPXJjbNHdZa0UNT8lqCBEt++NPw20LSfWk=
X-Google-Smtp-Source: ABdhPJxfIrXQrkYCm1FCj+UkVohG8GfwPIrs8fD6xiKEe6ad6CTDBak3M23moeNkwyXPqJ8TV1GxQ9YAaIiNikeX1jw=
X-Received: by 2002:a05:651c:316:: with SMTP id a22mr4060272ljp.473.1610030301262;  Thu, 07 Jan 2021 06:38:21 -0800 (PST)
MIME-Version: 1.0
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com> <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com> <CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com> <d8dd3487-48b7-bd35-90fb-60c1d62eb39f@gmail.com>
In-Reply-To: <d8dd3487-48b7-bd35-90fb-60c1d62eb39f@gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 7 Jan 2021 09:38:10 -0500
Message-ID: <CALaySJJza3qv72XJda2jHV4RfrfgGkyJmzrtjPkprVsvzQ63jQ@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, Seth Blank <seth=40valimail.com@dmarc.ietf.org>,  IETF DMARC WG <dmarc@ietf.org>, ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WNtrNKYeIRJ0_o-Ye9AAD5Xp5-8>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 14:38:25 -0000

Supporting what Tim said, and expanding a bit (and, yes, it's general,
not specific): If we all do our best to stick to the technical issues
and to keep our tone neutral, then it's easier for the chairs to
respond appropriately to cases of inability to conduct civil
discourse, and to target that response appropriately.  Best efforts to
understand each other, to respond to the points, and to avoid
implications that anyone's concerns are trivial will make it possible
for the chairs to manage the discussion and to take appropriate action
when they have to.  If you think something's been hashed out enough
and that further discussion along the same line isn't useful, don't
say that publicly: let the chairs know what you think, and let them
handle it from there.

Barry

On Wed, Jan 6, 2021 at 11:52 PM Dave Crocker <dcrocker@gmail.com> wrote:
>
> On 1/6/2021 8:47 PM, Tim Wicinski wrote:
>
> You should have a pretty good idea based on these arguments over the past few months to have a sense of how responses will be received. Take a step back and take a second read.
>
> This goes for all. Folks have very specific views of how they think mail should work
>
>
> Tim,
>
> This has nothing to do with differences in opinion.  It has to do with his persistent inability to conduct civil discourse in the face of disagreement.
>
> Disagreement is fine.  Abuse is not.
>
> d/
>
> --
> Dave Crocker
> dcrocker@gmail.com
> 408.329.0791
>
> Volunteer, Silicon Valley Chapter
> American Red Cross
> dave.crocker2@redcross.org


From nobody Thu Jan  7 06:47:41 2021
Return-Path: <mike@fresheez.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 EBCA53A11D0 for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 06:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 yAtqc3O0Aexm for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 06:47:39 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FCBC3A11C4 for <dmarc@ietf.org>; Thu,  7 Jan 2021 06:47:39 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id i5so5104117pgo.1 for <dmarc@ietf.org>; Thu, 07 Jan 2021 06:47:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=rWYr24e3hALX9+zK0qLMFCrwhyf8Yl217XaDQrcTxck=; b=U+nMR/oCxJ1YFxdhT+bBjjuvt0+36yrdRawiDwW3KZ12A4ywYS13AzAJlRuyVmAOgb BnpLkXJCU972Cl6EKMS6T7RA4YoaABv+EaldRmG7bd5O2vPxtlWVuTR0fUOpT39XR7OD h4nhWgSpQIdtY9IEoReJwTdK8B91zaRD9y/6f51TMqC3REhmr7Y7KKCENGwDb4UwuEHU XL7B+MpVXdVD+tGBa0fdb/Kqc3LKM78UTxWEi5crWu0Kh4+uwwUGGcectD3FXKx+GQcJ djN2Ho9xEGm6CH1m0t4AgVtdxo44NYSOVF2sbJT34nU4yaoG09XNB0YlyISwNAMjbSLr EsWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=rWYr24e3hALX9+zK0qLMFCrwhyf8Yl217XaDQrcTxck=; b=IqPiaHHdQxU6WShd7dBXTe395u7u8X8LdzWn+daetgosNBq93o5eS4czRZWy4qErAe EE/PdABA/ieGp+5PfNavmUknf78UjS+t6VOhDSJ16Ee2ZJBcIHEJp3+OwQKMEUzNlzft VMu3IEwAHnK2KnFZHP58MQPM83Muzod6eyawhl3hwMNKOaInymEm1xRGSImrGrQ+nPLW bxAAT8iB00ICRQt23UbxK/D72yldH8tFPd0ecnhCldd+Xbqa1sXXw+sXr1w5hOOVstt1 v5n64r/pqJ27WsTiNr7MIEwhuRcCYOCXU1p/89oZPbj/D32iDaJ3h3qgO66qaWLPkfuC KR9w==
X-Gm-Message-State: AOAM533Tt769DmNJzUexsxnkiKylcBxcYh9LB6uNptrdjTgdMJKkVIeK On4neYQmGvL3bW+Pi9+OhKKbNmyhfU4CKbQ0
X-Google-Smtp-Source: ABdhPJzA/E0ONj3XI2fE3sAjugRvG0I2Ipc+IvATmKY7a+yjlUDzPW76jkq5B5AoL/nJ1YDSqWOWtw==
X-Received: by 2002:a65:434c:: with SMTP id k12mr2130843pgq.373.1610030858231;  Thu, 07 Jan 2021 06:47:38 -0800 (PST)
Received: from mike-mac.lan (107-182-33-192.volcanocom.com. [107.182.33.192]) by smtp.gmail.com with ESMTPSA id j17sm5872248pfh.183.2021.01.07.06.47.37 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Jan 2021 06:47:37 -0800 (PST)
To: dmarc@ietf.org
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com> <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com> <CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com> <d8dd3487-48b7-bd35-90fb-60c1d62eb39f@gmail.com> <CALaySJJza3qv72XJda2jHV4RfrfgGkyJmzrtjPkprVsvzQ63jQ@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <578ae4e8-2cd0-37ad-b095-c86a2cccc43d@mtcc.com>
Date: Thu, 7 Jan 2021 06:47:36 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJza3qv72XJda2jHV4RfrfgGkyJmzrtjPkprVsvzQ63jQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/w_C4punSOMxdTXsPIlEYCizyzI0>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 14:47:41 -0000

PS: what brought this all up was me pointing to a report which 
contradicted his claim, and he nastily snarled about whether I had read 
it. he constantly gets away with that kind of shit and never suffers any 
consequences. never. yes, i've been told he's been tut-tut'd in private, 
but it never changes his behavior. get rid of him if you want to make 
progress. he's poison, and i'm not the only one who feels that way.

Mike

On 1/7/21 6:38 AM, Barry Leiba wrote:
> Supporting what Tim said, and expanding a bit (and, yes, it's general,
> not specific): If we all do our best to stick to the technical issues
> and to keep our tone neutral, then it's easier for the chairs to
> respond appropriately to cases of inability to conduct civil
> discourse, and to target that response appropriately.  Best efforts to
> understand each other, to respond to the points, and to avoid
> implications that anyone's concerns are trivial will make it possible
> for the chairs to manage the discussion and to take appropriate action
> when they have to.  If you think something's been hashed out enough
> and that further discussion along the same line isn't useful, don't
> say that publicly: let the chairs know what you think, and let them
> handle it from there.
>
> Barry
>
> On Wed, Jan 6, 2021 at 11:52 PM Dave Crocker <dcrocker@gmail.com> wrote:
>> On 1/6/2021 8:47 PM, Tim Wicinski wrote:
>>
>> You should have a pretty good idea based on these arguments over the past few months to have a sense of how responses will be received. Take a step back and take a second read.
>>
>> This goes for all. Folks have very specific views of how they think mail should work
>>
>>
>> Tim,
>>
>> This has nothing to do with differences in opinion.  It has to do with his persistent inability to conduct civil discourse in the face of disagreement.
>>
>> Disagreement is fine.  Abuse is not.
>>
>> d/
>>
>> --
>> Dave Crocker
>> dcrocker@gmail.com
>> 408.329.0791
>>
>> Volunteer, Silicon Valley Chapter
>> American Red Cross
>> dave.crocker2@redcross.org
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Thu Jan  7 06:57:50 2021
Return-Path: <dcrocker@gmail.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 B8F8C3A103C for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 06:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WKHob6gbY20K for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 06:57:48 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5D603A0C2E for <dmarc@ietf.org>; Thu,  7 Jan 2021 06:57:48 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id v19so5073443pgj.12 for <dmarc@ietf.org>; Thu, 07 Jan 2021 06:57:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=ywip/AtTOLLQhno+Wuqxujx2aIU9IB8iKUSGVa2dU9s=; b=Kf8ZJjdI+E14EJ6xx7UJ6e16nHimTXClS50x/86UewJkiXXT42BzP/qTvZtNQQxsQs shftzXIPvJGoyPrpv26kUArKA8Mrk2TTH/yu3Pga0vYCajQyMRRW3QWAO0qtK0i1n3sF Z1+KtskS0yiXF2Oh2QJqSGCG6TQGML3v57mB2rX+U3WY2d9Jknf7brM36pWCA+NUM/Bb tiBCywKtkN7kvvAmKMnrZykcc0vozcNALC4eqvFUJTeR2KDC54PfozHqPhhF4mUCNOe4 XWP3SbgnMZadQnrhnnMQ44JFlzZq5NXp8M8yY1GwEWN+Mf/t/UtD8aRLLTGuT7mvmE7O 1EbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ywip/AtTOLLQhno+Wuqxujx2aIU9IB8iKUSGVa2dU9s=; b=SK8r3/8/y/vl0Z7sb3VnXFSDIWxMqg2wdIQabCx6igp/Lxagr4CilPUgu5NZIk8CQs +5Z1cUssNAz2gU7LKoQcUYaJL1N3xL4g2eCmx+KNUQNPToL62yuO9C1iGbwwSrdqo8s2 aeooec+ScldJHYJFaI7SnbNMykvkNQqJ741K4BQ2/1hXMTK73lVULQYPF75Tf2sU/qUX UuEhrjtGsDWJIaItu5Kge/XozlpU+bj71BIKA41eSbce5QvqvyjzwozDn3AqhgfDcZkF 6P1hkGaYZp6jgqDxyMB5tLICyyDzOHWmKc3tjzFrmcquCNhOD1Aih4oWPggWjidbUVSX 83CQ==
X-Gm-Message-State: AOAM532cwh1oWnVrKcB95zMHdJbxi9LcC7iFiSmgtJu5FtFVfxbPQcby PA08P95IFMV2l7Nanc9IcVOqvpD87xg=
X-Google-Smtp-Source: ABdhPJxW925Sn5oWtaouKH45xen8wWaXaEWWM0EgDIwPuJpsD7KIecTC7IO3ubmiPGeMIcMp7dxj0g==
X-Received: by 2002:a63:f80f:: with SMTP id n15mr2180975pgh.415.1610031468109;  Thu, 07 Jan 2021 06:57:48 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id d2sm2401650pjd.29.2021.01.07.06.57.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Jan 2021 06:57:47 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com> <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com> <CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com> <d8dd3487-48b7-bd35-90fb-60c1d62eb39f@gmail.com> <CALaySJJza3qv72XJda2jHV4RfrfgGkyJmzrtjPkprVsvzQ63jQ@mail.gmail.com> <578ae4e8-2cd0-37ad-b095-c86a2cccc43d@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <a5498d82-f020-0e76-f945-b9706dc1cc6d@gmail.com>
Date: Thu, 7 Jan 2021 06:57:46 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <578ae4e8-2cd0-37ad-b095-c86a2cccc43d@mtcc.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/7MsYYiqqsHVqABs7IK4Gj3T1gAc>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 14:57:50 -0000

On 1/7/2021 6:47 AM, Michael Thomas wrote:
> PS: what brought this all up was me pointing to a report which 
> contradicted his claim,

It didn't.


> and he nastily snarled about whether I had read it. 

There is a pleasant way to snarl?

In any event, please document specifics, that qualify as 'snarling', 
since I've no idea what you are referring to.


> he constantly gets away with that kind of shit and never suffers any 
> consequences. never. yes, i've been told he's been tut-tut'd in private, 

I haven't been.

Might be interesting to see the exact text that claims otherwise.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


From nobody Thu Jan  7 06:58:57 2021
Return-Path: <mike@fresheez.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 995F03A103C for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 06:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 yHGxGTt_GoB4 for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 06:58:53 -0800 (PST)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA41E3A0C2E for <dmarc@ietf.org>; Thu,  7 Jan 2021 06:58:53 -0800 (PST)
Received: by mail-pl1-x62f.google.com with SMTP id b8so3692448plx.0 for <dmarc@ietf.org>; Thu, 07 Jan 2021 06:58:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=s77jozp+fLSUwZUvEtCh4jLD430uJiYXLvdN2iIgLf4=; b=A3bLiGUrHyDW90zCyB3jb/BiGyzaxfI7PN6l0cvTCns/WdeSX12RnsPo5wfauilPEJ WZAMa6adAj8kQAC9NyALZi3RSO2shu2fUeruX6ijqytNh0JQnFCoCTCDV+7aWm35Azki YjY+Gsd51QTCgmntePvfBD3GV5GIi3e6PJjFxfYcpRTLQd3kDTP6tCyLQDwo5/5gKEgV 5nAmQTW+Pj35vWpEE7ti1Mg9+Z5sHblANu37THmGkiByeKp4slG2sHyp3iqV1S0mczQc 7ZJAtkC91QaYbTm2joYqxT1htdRrrX2I28aWNxL6x4mjnV5dNZPZqFfR9mI14dvtH0ua +KoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=s77jozp+fLSUwZUvEtCh4jLD430uJiYXLvdN2iIgLf4=; b=UEVCZzMWmPwL8mO0RL/CdNUIaSwN7RBIfuxllZvTC16naLSz1J4sMwq4bZzzyuzE+M IetW13nEBadwVBSU7RgtTMnDU7FsX2i2zpeJINebGBf7+uo3qqasn1+UyoJOVGzmskGU gypwkZDSmaEQ3eJaG4lmoaR4FjOtr3UMbgfTgTZijikrPzDMlpD7AfNgoSGvmsuVuybg rhItRVvdrfsEbXTixlXlQeWRxAAihs0PH9COsocX7PUTKBHhq/iRZDIJV3BggWSMnxLZ yuVCr6s5WqMX+IS6kyIf+qkxXvBA6I1vzDpRfNPd16lOn2hGiqDh0HkWqLtkb+xDhn4h ZzkA==
X-Gm-Message-State: AOAM533eZhTqDgNhs8qjsSQaOShoTH4MUYOs+QtXDHh3dvW+Y00+qtde WS+tTQJuJmMeNMCfN+pCjDpbji4+TEpP7pc9
X-Google-Smtp-Source: ABdhPJzf2SZ5E5kfcX6sstlGU5pGWR+GVYbO1353D8qpNlilXia9vuBpiVXV3wN30WKFdNZ3jLAfiw==
X-Received: by 2002:a17:90a:a45:: with SMTP id o63mr9757368pjo.146.1610031532909;  Thu, 07 Jan 2021 06:58:52 -0800 (PST)
Received: from mike-mac.lan (107-182-33-192.volcanocom.com. [107.182.33.192]) by smtp.gmail.com with ESMTPSA id iq3sm5361676pjb.57.2021.01.07.06.58.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Jan 2021 06:58:52 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <CAOZAAfPW6Oki-4Ebgk9yS1H-r19PBTqE8nDMTFjUKY38JKgrfQ@mail.gmail.com> <acf32e64-f1fa-25df-b677-2e279ffeb2cc@gmail.com> <CADyWQ+HQk2+o+YweayH5t3GHua79zUBB1=1VFr6XXLgPt6kO0g@mail.gmail.com> <d8dd3487-48b7-bd35-90fb-60c1d62eb39f@gmail.com> <CALaySJJza3qv72XJda2jHV4RfrfgGkyJmzrtjPkprVsvzQ63jQ@mail.gmail.com> <578ae4e8-2cd0-37ad-b095-c86a2cccc43d@mtcc.com> <a5498d82-f020-0e76-f945-b9706dc1cc6d@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <700069bd-a69b-97a9-00c3-e08fd3edefb8@mtcc.com>
Date: Thu, 7 Jan 2021 06:58:51 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <a5498d82-f020-0e76-f945-b9706dc1cc6d@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Q_81WwXuvehFD9GFC5970ku4YLA>
Subject: Re: [dmarc-ietf] Decorum on the DMARC WG list and BCP 94
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: Thu, 07 Jan 2021 14:58:56 -0000

oh, shit. that was not intended to be public. apologies to all. please 
disregard.

Mike

On 1/7/21 6:57 AM, Dave Crocker wrote:
> On 1/7/2021 6:47 AM, Michael Thomas wrote:
>> PS: what brought this all up was me pointing to a report which 
>> contradicted his claim,
>
> It didn't.
>
>
>> and he nastily snarled about whether I had read it. 
>
> There is a pleasant way to snarl?
>
> In any event, please document specifics, that qualify as 'snarling', 
> since I've no idea what you are referring to.
>
>
>> he constantly gets away with that kind of shit and never suffers any 
>> consequences. never. yes, i've been told he's been tut-tut'd in private, 
>
> I haven't been.
>
> Might be interesting to see the exact text that claims otherwise.
>
>
> d/
>


From nobody Thu Jan  7 07:25:11 2021
Return-Path: <dcrocker@gmail.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 8F5F33A1211 for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 07:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 i6-tKwiVxrz3 for <dmarc@ietfa.amsl.com>; Thu,  7 Jan 2021 07:25:07 -0800 (PST)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B512B3A0E54 for <dmarc@ietf.org>; Thu,  7 Jan 2021 07:25:07 -0800 (PST)
Received: by mail-pl1-x62b.google.com with SMTP id j1so3718210pld.3 for <dmarc@ietf.org>; Thu, 07 Jan 2021 07:25:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=zulgFfbZ6gv6nCvNtJgXjwbjwgvgIJRuISZU+j4jUXg=; b=PnlThfIU3F1zshAceVZaukNf+4puFS6zId3uJ7V4hcxT8g08L5GpMoEacNGN6WdnK2 vN1Ok3bM3Npi1j+TuRgjFoDjVvNkNS9TzjwHeU0PcKcQpn5rKlnRmin4xOSJ5wpLFsPa MH9Y+/fO9RyLJiVHfoPypIuF6Xa3O1xorhp2h0e/XQIR6zkqw6gfNccixWZJSM+9Ryph RFMlaWQpQzlcUDiNQgZLm+YWJP3P04UjYzoV4+MWu3GYKOLVe5mPfzym0xvJFutL763m 7XW/nuZ/T4TJUoCVlm446zLiLA2QzCFI3p5k7iixTk8WXk92c2e/GKtr4FxldJt+zzpz C1gQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=zulgFfbZ6gv6nCvNtJgXjwbjwgvgIJRuISZU+j4jUXg=; b=hhxyZ7mNTlGTZQbFBtCieISB8Vnj4sIHBwaxTD7pHEk0jyiGaLI3D9RdKAtFusbAzL PTHSovBdSIov1xU8HoDmz/bUWNkvjLAjcdWNudENjVCLnhZiWabE3Zp0xGz3XGSeeas/ ju4E/oG7Kmfyiv3vDsKAneR8o8ewuf+epUVGL+zOqRmBLyiyQ5S+TtSZDf8ekNFYgJQU kdUXpHvCSZPMErPQX82IbJa9hv6ybRRnaBcHEfRdmE7XlhpRcpbNGtiBKDmpgDI2jKLr cPN2Nl+gcAxHKScPm/a9wFyjJlfRLLJec24mb10QUNIEenyxXw7CoGgJQafmR1id/1PR vPGA==
X-Gm-Message-State: AOAM5303UNjYqjRkeWUMtJXtVp+BJeEvJR230QitHpF58DfStEvmUGjK NUaQiKu6ZlZ7GjGNqz7TnkDYb9cwHao=
X-Google-Smtp-Source: ABdhPJz+BshdiMNM/7aiCatBYx7ue1Wmi/W/GDg6jvQdYTG6Rvj1zrSaMIM5dureeB+/yvfM00Rfmg==
X-Received: by 2002:a17:90a:8b8a:: with SMTP id z10mr9812311pjn.67.1610033107044;  Thu, 07 Jan 2021 07:25:07 -0800 (PST)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id x15sm5998792pfi.184.2021.01.07.07.25.05 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Jan 2021 07:25:06 -0800 (PST)
To: dmarc@ietf.org
References: <20210104174623.2545154CFF9F@ary.qy> <CABuGu1o2t7WaEOh+nsx3_MRUGgGHqKHzQ9302FM9-HL0GxvJvA@mail.gmail.com> <f15c8f53-8075-99a1-83c7-f687200e6a94@gmail.com> <f640ee95-ba0a-6aa7-1a14-2af1db151e27@mtcc.com> <050e8614-c088-a165-a733-35c5eee52eed@gmail.com> <cd3a41e8-cc4f-05eb-5c86-47b0047e8d08@mtcc.com> <d9e23994-8666-5c3f-3e42-9a12a2ed6daf@gmail.com> <974f9dcd-33ec-9d11-7857-3a473f994a2c@mtcc.com> <72d6bc7d-6862-8184-9f16-e1cc14120239@gmail.com> <f9244f50-8748-a395-a412-ca82bfe6bbea@mtcc.com> <4f2250f2-cc1c-5c3e-3d64-fa0e8b4ad086@gmail.com> <fcd84963-48dd-1fd0-a754-769f8cd7b58c@mtcc.com> <cba89cdb-40c6-48ff-45a0-287117a90385@gmail.com> <215493fa-a033-e5b0-ce8d-4a409ae93684@mtcc.com> <fa04ac5d-3a9f-5546-c77b-e6ddb5c1b1d4@gmail.com> <b3d77e5a-8024-218f-cd3c-6286f9ecd7dc@mtcc.com> <a7e6944a-363c-9d40-9cd9-1fe640ea6cfb@gmail.com> <e509cd25-19f9-ae75-ba62-30173af6857b@mtcc.com> <aee386fe-54ee-a01c-bd0c-80eb940ca185@gmail.com> <72e6d5f9-1dc2-1d32-25ce-e5b208895bd8@tana.it>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <d45f26f1-92c6-762e-2334-fc2c2b9a89ec@gmail.com>
Date: Thu, 7 Jan 2021 07:25:05 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <72e6d5f9-1dc2-1d32-25ce-e5b208895bd8@tana.it>
Content-Type: multipart/alternative; boundary="------------7788D26D055D82F6B8B44026"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/NqMJal9ffEqaffwbpLGGtsmUGEY>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Thu, 07 Jan 2021 15:25:10 -0000

This is a multi-part message in MIME format.
--------------7788D26D055D82F6B8B44026
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 1/7/2021 2:14 AM, Alessandro Vesely wrote:
> On Wed 06/Jan/2021 00:55:41 +0100 Dave Crocker wrote:
>> On 1/5/2021 3:50 PM, Michael Thomas wrote:
>>>>
>>> Quit cutting out needed context to make your points. The study 
>>> directly contradicts your categorical statement.
>>
>> Except that it doesn't.
>>
>> Feel free to provide an serious explanation of why you think 
>> otherwise, but please put some effort into accurately representing 
>> what I said or what the study shows.  Attention to detail will help.  
>> Conclusions are less important than showing your work.
>
>
> The report says:
>     This returns the email-opening rate of 53.4% and 48.9%. Among 
> these users,
>     the corresponding click-through rates are 48.9% (without security
>     indicator) and 37.2% (with security indicator) respectively. The
>     results indicate that security indicators have a positive impact 
> to reduce
>     risky user actions.
> https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf 
>
>
>
> You said:
>     My point is that we have decades of belief that it's useful but no
>     demonstration that it actually is.  And we have history such as 
> the EV
>     effort, showing that it isn't.
> https://mailarchive.ietf.org/arch/msg/dmarc/r7unHaCXKKFeotbjU1pL-Jx4f_o


We've got roughly 25 years of anti-abuse effort.  This includes some 
that have attempted to use end-user trust indicators.  All have proved 
useless.  The entire anti-abuse industry relies on filtering engines, 
not end-user behavior. (End user 'education' is minor and generic.  
There is little or no evidence it has much effect.)

A single, small-sample study under somewhat-controlled conditions does 
not provide 'proof' of efficacy.  At very best, it suggest a line for 
further inquiry.

At the very least, note the Study Limitations section.  Then note that 
studies like these have very, very low correlation factors. A result of 
0.4 is about as good as it ever gets, and that's quite rare.  But it 
means that, at best, the study accounts of only 16% of the behavior, 
leaving 84% due to other factors.  This is not much of a foundation for 
the time and opportunity cost of a standards effort.

 From the cited paper:

> Visual Security Indicators. Security Indicators are
> commonly used in web or mobile browsers to warn users
> of unencrypted web sessions [25, 39, 61, 49], phishing
> web pages [21, 24, 69, 70], and malware sites [7]. Existing work shows 
> that users often ignore the security indicators due to a lack of 
> understanding of the attack [69] or
> the frequent exposure to false alarms [43]

It's significant that their text misses a variety of cognitive 
limitations that are also likely to account for the lack of efficacy.

d/


-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


--------------7788D26D055D82F6B8B44026
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/7/2021 2:14 AM, Alessandro Vesely
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:72e6d5f9-1dc2-1d32-25ce-e5b208895bd8@tana.it">On Wed
      06/Jan/2021 00:55:41 +0100 Dave Crocker wrote:
      <br>
      <blockquote type="cite">On 1/5/2021 3:50 PM, Michael Thomas wrote:
        <br>
        <blockquote type="cite">
          <blockquote type="cite">
            <br>
          </blockquote>
          Quit cutting out needed context to make your points. The study
          directly contradicts your categorical statement.
          <br>
        </blockquote>
        <br>
        Except that it doesn't.
        <br>
        <br>
        Feel free to provide an serious explanation of why you think
        otherwise, but please put some effort into accurately
        representing what I said or what the study shows.  Attention to
        detail will help.  Conclusions are less important than showing
        your work.
        <br>
      </blockquote>
      <br>
      <br>
      The report says:
      <br>
          This returns the email-opening rate of 53.4% and 48.9%. Among
      these users,
      <br>
          the corresponding click-through rates are 48.9% (without
      security
      <br>
          indicator) and 37.2% (with security indicator) respectively.
      The
      <br>
          results indicate that security indicators have a positive
      impact to reduce
      <br>
          risky user actions.
      <br>
<a class="moz-txt-link-freetext" href="https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf">https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-hu.pdf</a>
      <br>
      <br>
      <br>
      You said:
      <br>
          My point is that we have decades of belief that it's useful
      but no
      <br>
          demonstration that it actually is.  And we have history such
      as the EV
      <br>
          effort, showing that it isn't.
      <br>
<a class="moz-txt-link-freetext" href="https://mailarchive.ietf.org/arch/msg/dmarc/r7unHaCXKKFeotbjU1pL-Jx4f_o">https://mailarchive.ietf.org/arch/msg/dmarc/r7unHaCXKKFeotbjU1pL-Jx4f_o</a>
      <br>
    </blockquote>
    <p><br>
    </p>
    <p>We've got roughly 25 years of anti-abuse effort.  This includes
      some that have attempted to use end-user trust indicators.  All
      have proved useless.  The entire anti-abuse industry relies on
      filtering engines, not end-user behavior. (End user 'education' is
      minor and generic.  There is little or no evidence it has much
      effect.)</p>
    <p>A single, small-sample study under somewhat-controlled conditions
      does not provide 'proof' of efficacy.  At very best, it suggest a
      line for further inquiry.  <br>
    </p>
    <p>At the very least, note the Study Limitations section.  Then note
      that studies like these have very, very low correlation factors. 
      A result of 0.4 is about as good as it ever gets, and that's quite
      rare.  But it means that, at best, the study accounts of only 16%
      of the behavior, leaving 84% due to other factors.  This is not
      much of a foundation for the time and opportunity cost of a
      standards effort.<br>
    </p>
    <p>From the cited paper:</p>
    <p>
      <blockquote type="cite"><span class="fontstyle0">Visual Security
          Indicators. </span><span class="fontstyle2">Security
          Indicators are<br>
          commonly used in web or mobile browsers to warn users<br>
          of unencrypted web sessions [25, 39, 61, 49], phishing<br>
          web pages [21, 24, 69, 70], and malware sites [7]. Existing
          work shows that users often ignore the security indicators due
          to a lack of understanding of the attack [69] or<br>
          the frequent exposure to false alarms [43]</span> <br style="
          font-style: normal; font-variant: normal; font-weight: normal;
          letter-spacing: normal; line-height: normal; orphans: 2;
          text-align: -webkit-auto; text-indent: 0px; text-transform:
          none; white-space: normal; widows: 2; word-spacing: 0px;
          -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
          0px; ">
      </blockquote>
      <br>
    </p>
    <p>It's significant that their text misses a variety of cognitive
      limitations that are also likely to account for the lack of
      efficacy.<br>
    </p>
    <p>d/</p>
    <br>
    <pre class="moz-signature" cols="72">-- 
Dave Crocker
<a class="moz-txt-link-abbreviated" href="mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------7788D26D055D82F6B8B44026--


From nobody Sun Jan 10 03:00:11 2021
Return-Path: <johnl@taugh.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 E704A3A0962 for <dmarc@ietfa.amsl.com>; Sun, 10 Jan 2021 03:00:08 -0800 (PST)
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, 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 wS9c__R-XZzX for <dmarc@ietfa.amsl.com>; Sun, 10 Jan 2021 03:00:07 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 246CB3A095F for <dmarc@ietf.org>; Sun, 10 Jan 2021 03:00:06 -0800 (PST)
Received: (qmail 16021 invoked by uid 100); 10 Jan 2021 11:00:06 -0000
Date: 10 Jan 2021 10:59:42 -0000
Message-ID: <20210110105942.16009.qmail@submit.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ijE-KMI0kZN9MWuZNx9M6IhMDgE>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jan 10 06:00:05 2021
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, 10 Jan 2021 11:00:09 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 21 (26.2%) | 150638 (22.7%) | Michael Thomas <mike@mtcc.com>
 19 (23.8%) | 139728 (21.0%) | Dave Crocker <dcrocker@gmail.com>
  9 (11.2%) |  61551 ( 9.3%) | Alessandro Vesely <vesely@tana.it>
  7 ( 8.8%) |  77397 (11.7%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  6 ( 7.5%) |  28311 ( 4.3%) | John Levine <johnl@taugh.com>
  4 ( 5.0%) |  81092 (12.2%) | Laura Atkins <laura@wordtothewise.com>
  3 ( 3.8%) |  30034 ( 4.5%) | Tim Wicinski <tjw.ietf@gmail.com>
  3 ( 3.8%) |  28733 ( 4.3%) | Dotzero <dotzero@gmail.com>
  2 ( 2.5%) |   8824 ( 1.3%) | Jim Fenton <fenton@bluepopcorn.net>
  1 ( 1.2%) |  14153 ( 2.1%) | Brotman, Alex <alex_brotman@comcast.com>
  1 ( 1.2%) |  12136 ( 1.8%) | Seth Blank <seth@valimail.com>
  1 ( 1.2%) |  10208 ( 1.5%) | Todd Herr <todd.herr@valimail.com>
  1 ( 1.2%) |   8464 ( 1.3%) | Murray S. Kucherawy <superuser@gmail.com>
  1 ( 1.2%) |   7698 ( 1.2%) | Kurt Andersen (b) <kboth@drkurt.com>
  1 ( 1.2%) |   5358 ( 0.8%) | Barry Leiba <barryleiba@computer.org>


From nobody Wed Jan 13 20:30:13 2021
Return-Path: <superuser@gmail.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 4438B3A10A4 for <dmarc@ietfa.amsl.com>; Wed, 13 Jan 2021 20:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 h96TJF-39fsB for <dmarc@ietfa.amsl.com>; Wed, 13 Jan 2021 20:30:10 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8317B3A109F for <dmarc@ietf.org>; Wed, 13 Jan 2021 20:30:10 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id w187so1434852vsw.5 for <dmarc@ietf.org>; Wed, 13 Jan 2021 20:30:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=5nUpXBzoZ15+5DhqX4q5h7/dAfbaLJjMGriNu1CqGqo=; b=l9C8V9xhU7CWa0pateC4IvVqIA08OeO47171haOzGpBW4sfN2qaO4+3EjeG5Zyqk+u fKWgSmaiQwS3B6MONKOlLilUdW/aUG0oAq9PD5NXQ+t7nn8alVsCOm6Sv4m4L/UX0A/5 jwZ30a0kxQFp60XNAUK+isvuYGkfSm36uQEfH4BOTTRAfWWMrgIdswNAch3UfQspvh7Z Xx5RWpBlG96BmatLBXkgOXOCOsdPt9/SG0dq7R//Adgm36f32ZaA2kBzrHRigAD3TKbM smEND9FAagGlt4BaXCGVgpSiihfEjEhsFyzbh8vLeHI0CQNkherlaQWaNny4MhvbSfv2 knyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5nUpXBzoZ15+5DhqX4q5h7/dAfbaLJjMGriNu1CqGqo=; b=S/1O9h9CYlkfaNOtHCK4TKlRLaAeksl7fz0HIGdOqlCUo3X7uaMDm8pXR3jacRxC// 1WD30oYXBJnWguJC6i3jD8LohgYLYhDakdFqqeYaMUMRrHJTfbhsVQH0RGK/WUpaonsU c+C+d14OEMxyxVVWy0GdshQkLHDQ0a4G9K/JffQ+vuZMzvfkz7rW4RKpkYQtx6MCg+9O 5fxoszvH5xWxRAguQiNBUzkPikhZpGMHTUrfLOoroO1WXdwnlPy86zdtZhUmPdq9KoDb ceSDIsd2kMARNhAcwfvNiN2XJnYadq0yDFFY0bZdwgsMhn7b1RLFB19lC9+I2J2jUsE/ t2mA==
X-Gm-Message-State: AOAM533Xpi6pJEr6XhzJZDGFcwsFhskoUaktSb6oIMMWeTVOkrDb0fBQ +sptzsONsBdVDJNimQ0ZF9J+qtEdrHkCAuBpqK1m0hM4b9A=
X-Google-Smtp-Source: ABdhPJxWisU4tngOxFQp5097NynA3EsFtOVfceEWUGITyCK4NI8MCuBW59PLkoB87lu5kiTRAMkbQVOcg0wBJj+R4zE=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr4792372vsy.54.1610598609058;  Wed, 13 Jan 2021 20:30:09 -0800 (PST)
MIME-Version: 1.0
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 13 Jan 2021 20:29:51 -0800
Message-ID: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f8015605b8d4b5aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/iFJWghWV1eSNkaWfmeguO9aRzjw>
Subject: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 04:30:12 -0000

--000000000000f8015605b8d4b5aa
Content-Type: text/plain; charset="UTF-8"

How are implementers dealing with forensic report loops?

Say I send a message from X to Y, whose DKIM signature fails.  Y sends me
back a forensic report, whose DKIM signature also fails.  X sends a
forensic report to Y, whose report fails, etc.  We need a way to break the
loop.

As I recall, email routing loops are broken by simply counting the Received
fields, but a given forensic report is a new message each time, so a
mechanism like that won't work.

Off the top of my head, a few options:

1) a new header field indicating "This is a forensic report, don't generate
a forensic report about it."

2) some kind of token that's always in the Subject field of a DMARC
forensic report.

3) always generate forensic reports as the null sender, and specify that
forensic reports should never be generated in response to the null sender

4) something else?

-MSK

--000000000000f8015605b8d4b5aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>How are implementers dealing with forensic repor=
t loops?<br><br></div>Say I send a message from X to Y, whose DKIM signatur=
e fails.=C2=A0 Y sends me back a forensic report, whose DKIM signature also=
 fails.=C2=A0 X sends a forensic report to Y, whose report fails, etc.=C2=
=A0 We need a way to break the loop.<br><br></div><div>As I recall, email r=
outing loops are broken by simply counting the Received fields, but a given=
 forensic report is a new message each time, so a mechanism like that won&#=
39;t work.</div><div><br></div><div>Off the top of my head, a few options:<=
br><br></div><div>1) a new header field indicating &quot;This is a forensic=
 report, don&#39;t generate a forensic report about it.&quot;<br><br></div>=
<div>2) some kind of token that&#39;s always in the Subject field of a DMAR=
C forensic report.</div><div><br></div><div>3) always generate forensic rep=
orts as the null sender, and specify that forensic reports should never be =
generated in response to the null sender</div><div><br></div><div>4) someth=
ing else?<br><br></div><div>-MSK<br></div></div>

--000000000000f8015605b8d4b5aa--


From nobody Thu Jan 14 01:22:35 2021
Return-Path: <smj@crash.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 346A23A1387 for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 01:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 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.262, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=crash.com
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 OjTY3kdtHIZg for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 01:22:32 -0800 (PST)
Received: from segv.crash.com (segv.crash.com [IPv6:2001:470:1:1e9::4415]) (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 A947C3A134B for <dmarc@ietf.org>; Thu, 14 Jan 2021 01:22:27 -0800 (PST)
Received: from shiny.crash.com (192-184-141-33.static.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.7) with ESMTPSA id 10E9MCkC034127 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dmarc@ietf.org>; Thu, 14 Jan 2021 09:22:25 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 10E9MCkC034127
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1610616146; bh=xs2KvYePZAPyPB1nHRnAy32QKwFORYkc7mC/aunpJsc=; h=Subject:To:References:From:Date:In-Reply-To; b=CQZRd05/Ag5oYdGL3vFpdkyg10fgrWC5ist0hmgavnk1cXnVhBmMm6Oc8MOFe6Y5z gdn+oPY1OrKJmjdJqvUA6bTTohmbyRgmnI9XvblNx+MwCmL13ErWl0nFGYYXiUq5Eg ad5MKMCakRUvTfwKcnv3P/Oh5yVMNmuVrYsm+5gz4x/4qqeeqrNu2gQhrRoXoDn2qV UuCdsaTvS9i6nyiDKuLgylfXA44Cl7u7T8oKZepUyOF7UsoRNiYvHv4yaa9xoNzm+V ZXMA/Ucqclg9WBR1QNrJg3AQwHvMXLK9Ov3VTyY/F+88xqBN5Zaywc0XcNi0ztDvN2 pA+uc173ehAXA==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.static.sonic.net [192.184.141.33] claimed to be shiny.crash.com
To: dmarc@ietf.org
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com>
Date: Thu, 14 Jan 2021 01:22:10 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Thu, 14 Jan 2021 09:22:25 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/HX2oj5DisKEmgMYxxDu77xKqx5I>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 09:22:34 -0000

On 1/13/21 20:29, Murray S. Kucherawy wrote:
>
> How are implementers dealing with forensic report loops?

The question of whether such a thing is actually ever seen in the wild
should be asked, if only to document that it was asked and answered. See
prior "this is a vanishingly small number who cares" discussions.

Channeling Dave, is it fair to just say the objective is: To ensure that
forensic reports do not ever cause the recipient of a forensic report to
generate another forensic report in response? Is that overly broad? Are
there other goals or conditions?


> Say I send a message from X to Y, whose DKIM signature fails.  Y sends
> me back a forensic report, whose DKIM signature also fails.  X sends a
> forensic report to Y, whose report fails, etc.  We need a way to break
> the loop.

Is there a functional or operational difference between aggregate and
forensic reports I'm not thinking of that would cause the solution for
one case to be unsuitable for the other? Or can we hope for a mechanism
that applies to all DMARC reports?


> Off the top of my head, a few options:
>
> 1) a new header field indicating "This is a forensic report, don't
> generate a forensic report about it."

Is there a reason somebody might use this new header in an abusive way?
Or include it in a forged forensic report to avoid exposure? Cue a 0.1%
of 0.1% sidebar...

Jumping ahead of those questions, would the new header have to be DKIM
signed by the report generator, and the entity /doing final delivery of
that report/ required to validate the DKIM signature(s) from the report
generator, and only generate a forensic report in response if this new
header is not present? Or if the signature didn't cover the new header?
Or if the signature couldn't be validated?

"Doing final delivery of that report" -- is that sufficient? Or, "any
entity processing the report and potentially generating a report in
response?"


> 2) some kind of token that's always in the Subject field of a DMARC
> forensic report.
DMARC forensic report Subject: lines aren't uniform, but the last time I
looked there was an awful lot of similarity. If that were tightened up a
little more, would an explicit token really be necessary?


> 3) always generate forensic reports as the null sender, and specify
> that forensic reports should never be generated in response to the
> null sender

I suppose that would meet the goal, but what would be lost along the
way? What keeps coming to mind is the advice I've seen to have your
bounce messages authenticate with DMARC - if a sender does that or is in
the process of implementing it, they might want whatever forensic
reports they could potentially get...

cf.
https://www.validity.com/how-to-authenticate-your-bounce-messages-with-dmarc/


--S.



From nobody Thu Jan 14 02:36:45 2021
Return-Path: <juri@sapienti-sat.org>
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 D98553A1337 for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 02:36:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 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.262, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sapienti-sat.org
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 5IZ_qoC06dnA for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 02:36:41 -0800 (PST)
Received: from batleth.sapienti-sat.org (batleth.sapienti-sat.org [IPv6:2a01:4f8:221:43c5::2]) (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 54D383A12DC for <dmarc@ietf.org>; Thu, 14 Jan 2021 02:36:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sapienti-sat.org; h=content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:to:subject:subject; s= dkim20170413; t=1610620597; bh=aZ07TU+i2AVwDeNQ3nFAp48eIcb3Qv9wZ 5tcoaMctlM=; b=BpbucjpIE1oNrLFdh/r/oIZ8V2XgW7QDQOsGOut1gA7ZaIWEL 2UNa/jPUFfFpe0473hwJtjWostyo3kCv7sjw9gmabkz/oNuxPtFvjplFxPEvyQed EPfoveYfKkR1UVagJMjhEA48+vvNpsqBtiHCuw+KTGC8ncnLaQkRCmsDWALMA9Cb rWxFvuDlg6nuWxy+DkOGYc/dimJVO7TZqhTq8Mcadm5P3I0qooXrLFyo9oqy62Ok 8WKKFK0xHDbSFT2fj/qh63Js0wmjtNkb2vns0NAAwfcCb78b2bsn9G+geKhjCppW TRxlrqD90Ra7Na0ZG/4Wf/p9BV61m6H42TkvA==
X-Virus-Scanned: Debian amavisd-new at sapienti-sat.org
Received: from [IPv6:2001:470:6d:e38::11] (mpese.home.sapienti-sat.org [IPv6:2001:470:6d:e38::11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: juri@sapienti-sat.org) by batleth.sapienti-sat.org (Postfix) with ESMTPSA id EE44033E0460 for <dmarc@ietf.org>; Thu, 14 Jan 2021 11:36:36 +0100 (CET)
To: dmarc@ietf.org
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com>
From: Juri Haberland <juri@sapienti-sat.org>
Autocrypt: addr=juri@sapienti-sat.org; prefer-encrypt=mutual; keydata= mQGiBEpkkU0RBACvs80AZxmG2dlbE8uFuRtWaGbvdlTKzwn4s37Sc98yNzDr57btydCdasf8 OvctyUrngCuC/JmBDw9MpNVVRJ2lLOSi7r5JgjXSbpeW95UKUnQk2m/+nRkNPrKY0FXhP4VE 04lmV3vb0cKpi3Iuceuc4U/PkwlbfzvMCqMJp/zGGwCgqnxsnNu+MOEPB1zum0pT1ZmZptEE AJkzjTYdnt4zarO0K8Yk9BMy39puGMuW6HD4MiN1DfkqH9RYe7qh6L8DasmSed/TlVNpsH+y fdhwD/9f+8Ifc1vpFjgcm9mEmJqyjpQTKG9oQE1KpcnHXKwG/Gr/lXrQbgiiungc+d18tafN yAKQfmkKIDqFVmKPjlOJHWYN7qlKA/0R3/6RyerO84hsLt6jFWeOm/9KEh6WfnoooDQhAq7M sFjCNUoF32x/hpabB9MqF6vcl/Ka8Dmdj95Ae10K9MD5L7TNaWkL7FepFptcCkHonLQQM4E2 vDAJtyyKUaQiOPw80oEOMISXzQD78Vbg6Q9nmsmkpuSAUVTqUksTTwtnNrQmSnVyaSBIYWJl cmxhbmQgPGp1cmlAc2FwaWVudGktc2F0Lm9yZz6IYAQTEQIAIAUCSmSRTQIbAwYLCQgHAwIE FQIIAwQWAgMBAh4BAheAAAoJED9MVq+NNYZCRlAAn38ddF0pjwOZR0VyoIe4UpfpZV5fAKCO o87TVyYoBYwru4hunuVMOpXgG7kCDQRKZJFTEAgAoBRVOPPgl3foNLJn+C8QnuExrwKdeguE 5l2lSw3Fummo9CQCN72gYrqMNksFeIcoWAWclm/8bA551KWum8g2TjTA7NuVdIvzahr8MFGi oBNktr1GLAJ2SNpzyUA3fICIJqXdUdlvnjk4olQE6ACylbxDT+2x5HVzvhxw1fvz4c4JRvnP J1q2/LMu6sgBta6cgVTzYzBvxf1JyjbHsFKZSJZ+3JO3AO5y40XbU+EZVT60ChbU8GCJEVer 2RFlYfYSdniSxgQPuYVxZsfXgQlv0xQ3QTTDLU9jpJJX4EfwfWaio01X3l8QqIBtVpu07ZXI klOJk1QXC3HDIhAt/uGdVwAEDQgAmK0fEhrg/HY2Zs2VXIkWViS8I68sAw/GRGAsif0pkHTx dQ2oEZYMK1bNW7VFBphby554hUAmvwcCCUso0INqiw0sXs6ZARL3nT6QPc3uU0jMFpg1cWHf yElUopAR0S0kxVfShE3fNKOnizTPcRboCLOVZzuM1BxVO55Dkc9fPX1zik9hzJjbG4bzEqNG cg7+EY0YqeEVFccyRXsjvFRTl4ckvCMhsyqGwE8AnwFOYJXqfbLjEDSBngblniWTEjZ47t5p rN6sri7+sWIUaybzdINKGZMijndTVccMtRvbbx62+0dRoxUV2GIrNcCOvQ7e5Q4/vL8okoK9 MZMUWQnUeYhJBBgRAgAJBQJKZJFTAhsMAAoJED9MVq+NNYZCX74An2lQsova+seE0su7vK2y GGyRrnQdAJ9nvrSrslx2qcHkRycgYoFozVkRsw==
Message-ID: <6547b3f4-190b-2c20-a864-cf51168ddab2@sapienti-sat.org>
Date: Thu, 14 Jan 2021 11:36:36 +0100
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: <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/f-FqQP-fNy1ce3kzMeFG4uUlLvA>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 10:36:43 -0000

On 14.01.21 10:22, Steven M Jones wrote:
> On 1/13/21 20:29, Murray S. Kucherawy wrote:
>>
>> How are implementers dealing with forensic report loops?
> 
> The question of whether such a thing is actually ever seen in the wild
> should be asked, if only to document that it was asked and answered. See
> prior "this is a vanishingly small number who cares" discussions.

I had this happening twice with different (small) report receivers, so I
stopped sending failure reports alltogether.

Regards,
  Juri


From nobody Thu Jan 14 03:12:31 2021
Return-Path: <dilyan.palauzov@aegee.org>
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 BD5CC3A098C for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 03:12:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
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 t2Ly-DOBE80C for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 03:12:27 -0800 (PST)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (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 946B73A08B0 for <dmarc@ietf.org>; Thu, 14 Jan 2021 03:12:26 -0800 (PST)
Authentication-Results: mail.aegee.org/10EBCMYL3939648; auth=pass (LOGIN) smtp.auth=didopalauzov@aegee.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1610622742; i=dkim+MSA-tls@aegee.org; bh=t50xDqO4qgWk3BSdclsrC9Wb8zkijilAr8MMdSGz1UM=; h=Subject:From:To:Date:In-Reply-To:References; b=lQBVYGknYkLdiQT9EVLh59vK/i5pKb6c0US0FnyxVTka3+HDbtF1vGG1QiqlE//zC RBJJTjK0mmzwKDi1XM77i7FU52yjqpzJCMHQGO7j1KoDt3aurj0VKQ8N21UDRcTBPd XhIjfqgsJ0UBf35i/9fXU5y76W3aeAfttERMIbUmrfO8LvQ/j0x/Uf39O5+gR/fcXF i/eSBHRUroP1nknDcYQOXRHK9zNbicIz5YFF+z0FFb2h73ecteaftDKknc0ZfPk6le ySssJUMJ4Ic7vs7YaOE4j9bZ9098I0U+v2Ovs4LPiwACzlhoul7OA4w7n2FItTTPkW /DJC/ITaegjzo96XMwKT65e6QGpA0S4flpP1oghoE0uTKPBhfVVYPxtPYeNe74ik+K 1a5I5L98zmz8XjC2D1jNeDiXpLNPe3O2i4Y90ypQLdwXIucr2yDDG/XRbmNRdj93sJ /0oVpGjT+kN4VfJRQARGG1Is/Q+LYL2hXsipzqwFkgMBP3+0Q/HNZ6bio9sUjI0MT4 WmzwOs1MztSskXb4mjQCZTBbB3JgwdHEL/nH5L2VDD8cjvhVNIvv59Z0Ji9nh8FsaQ GKdyZb7viMaQP02GoeUU3fToKzEN28x6jJCamC7YClKo97yABZpHVzkbEuSZLHxZmn sXtBLR5gdDV/nyVcbnDr1Qpc=
Authentication-Results: mail.aegee.org/10EBCMYL3939648; dkim=none
Received: from [192.168.0.125] (87.118.146.153.topnet.bg [87.118.146.153] (may be forged)) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id 10EBCMYL3939648 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <dmarc@ietf.org>; Thu, 14 Jan 2021 11:12:22 GMT
Message-ID: <621d4aa5a72baf46b45a005f8e45eab6f7421e50.camel@aegee.org>
From: =?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?= <dilyan.palauzov@aegee.org>
To: dmarc@ietf.org
Date: Thu, 14 Jan 2021 13:12:21 +0200
In-Reply-To: <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.39.2 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/JH0bvoypRtUc0UqUlKIEjvAzFmo>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 11:12:30 -0000

Hello,

Am Donnerstag, dem 14.01.2021 um 01:22 -0800 schrieb Steven M Jones:
> On 1/13/21 20:29, Murray S. Kucherawy wrote:
> > 
> > How are implementers dealing with forensic report loops?
> 
> The question of whether such a thing is actually ever seen in the
> wild
> should be asked, if only to document that it was asked and answered.
> See
> prior "this is a vanishingly small number who cares" discussions.

Imagine a case, where two sites sending forensic reports on failures
exchange messages and the one site is misconfigured: on each received
forensic report it sends a bounce, which bounce does not DMARC-align. 
This the same problem as with a misconfigured site sending Aggregate
reports, but does happen once a second, not once a day.  By sending
reports with return-path:<> you prevent the misconfigured recipient of
the report to generate a bounce, which bounce must DMARC-align, but
does not DMARC-align.


I want to remind on real-world cases addressed on this mailing list
• On 25 May 2019 with Subject “Is there any recommendation to send
DMARC message-specific failure reports FROM:<>”?
• On 31 May 2019 with Subject “Endless Email Loops with Aggregate
Reports”
• On 4 JUne 2019 with Subject “Endless Loops with DKIM reports” which
addresses reporting per “RFC 6651  Extensions to DKIM for Failure
Reporting” - this is not much different than forensic reports

that lead to https://trac.ietf.org/trac/dmarc/ticket/30 “Endless Email
Loops with Aggregate Reports”.

I have not read the thread “Ticket #28 - Failure report mail loops”.

A possible approach is not to send failure reports for messages
received on the address for accepting aggregate/forensic reports. 
These messages shall just be excluded from all calculations.

Does anybody compare the number of messages sent from her host1 to the
host2 of somebody else, with the number of reported messages in the
aggregate report?  If the numbers do not match, does somebody apply
negative spam weights for host2?

Greetings
  Дилян


From nobody Thu Jan 14 07:24:49 2021
Return-Path: <superuser@gmail.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 DDCFA3A14C0 for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 07:24:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9E7qLx-AWxqz for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 07:24:46 -0800 (PST)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CE2A3A14BF for <dmarc@ietf.org>; Thu, 14 Jan 2021 07:24:46 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id e15so3291954vsa.0 for <dmarc@ietf.org>; Thu, 14 Jan 2021 07:24:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=M6rFbiZ/J8GKkK9g0o2E92dp3g6FwlacOQ2x8vOI3Fw=; b=WWmPZWgKU0502FunFjxAdLhymz22z8T4qUZgn3jQtxipV8YIERGzdq+Ez12GHwR6qH jw9cpFjbMstxjRtFgYEfhIAPE1a4Zrzh53rU3YmHIow70PcZfzJytuBwNkGIugTn75eE EPxQneREyumEYE24+O368t0RzqSSRMFOIFawyWIwd2fQoGXjmTx2opyUVB9UV7zudM+M 9p3/2zHMhlz8zITHzMxR6mNvG00oV8tDcEb3nIq5r/idJUsMToyFq8nVia/HYAzRxvj1 fbKVfV1IMxoyYE0Up5qDO+PMAXbzMLjrMH0g1ufCzcHoEieaXORa2hZiYmm8mhRYUg+N livQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M6rFbiZ/J8GKkK9g0o2E92dp3g6FwlacOQ2x8vOI3Fw=; b=ZzQRLymndkjwT4ssZdtnyJKD37f18xGE71yaIldjS5EGSN0mfZSk1RhzlrEeZTfstU NQHfaHfs71DA6HQsGUU2Px3D96AE4/oVPv5I+yKRXMKCjupZh52K/f1N9Df3oKsFlj6M Hz8Tyquaem7J1E3WB3Yux0RgUaoestkbFsAs2ySogcVxwdq0FwyFntgXoCznjojWIGWu dVJhQb5pPWYdc/BgC1TfNHp2tbcR09jwdDv+cQ5lo9iCHtt2nOomHOeel+HQS8J7hK+a t1dAiD+eZunOe3v/oPPV6atJV2EahDt3Mgs5ljOdj+bGeNuxk10vSJySJkIMitYiKxQH 8nIg==
X-Gm-Message-State: AOAM533rENRwNLSZHS1fMo2nNIZ+inbERSkdX4K5LYJ0v5QEwXIvVuxF EIMr3U5fhFF+8ms3/TFFmip8n3NRlv2IncOQklU=
X-Google-Smtp-Source: ABdhPJzLoTtgmZR3ho0qPkjZY1AD01E2gHLi+MK/9Ew/92qH4Biq0VCbyBdxPTA1WCYVfQoDnPnBoMmcGNjILGbmZyo=
X-Received: by 2002:a67:fb46:: with SMTP id e6mr7266746vsr.40.1610637884726; Thu, 14 Jan 2021 07:24:44 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com>
In-Reply-To: <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 14 Jan 2021 07:24:33 -0800
Message-ID: <CAL0qLwZVWRFnaK1iqMC800GCt651xwu=dEqhz=r9Z_CG2y3AKA@mail.gmail.com>
To: Steven M Jones <smj@crash.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fb23e805b8dddaeb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Nx6WM2m__r19cLS3jb9DwLmE41U>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 15:24:48 -0000

--000000000000fb23e805b8dddaeb
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 14, 2021 at 1:22 AM Steven M Jones <smj@crash.com> wrote:

> On 1/13/21 20:29, Murray S. Kucherawy wrote:
> >
> > How are implementers dealing with forensic report loops?
>
> The question of whether such a thing is actually ever seen in the wild
> should be asked, if only to document that it was asked and answered. See
> prior "this is a vanishingly small number who cares" discussions.
>

I'm asking the question in response to an actual use case.  Granted it's an
isolated case so far, but it comes from a not-insignificant organization
that probably handles a substantial email load, so at least for their side
this is already happening, or could happen, at scale.

Channeling Dave, is it fair to just say the objective is: To ensure that
> forensic reports do not ever cause the recipient of a forensic report to
> generate another forensic report in response? Is that overly broad? Are
> there other goals or conditions?
>

I believe that's exactly what I was asking for.

> Say I send a message from X to Y, whose DKIM signature fails.  Y sends
> > me back a forensic report, whose DKIM signature also fails.  X sends a
> > forensic report to Y, whose report fails, etc.  We need a way to break
> > the loop.
>
> Is there a functional or operational difference between aggregate and
> forensic reports I'm not thinking of that would cause the solution for
> one case to be unsuitable for the other? Or can we hope for a mechanism
> that applies to all DMARC reports?
>

I don't see a reason why we need a different method for each report type.
The case in hand is forensic reports, but that's just part of the specific
incident to which I'm responding.


> > Off the top of my head, a few options:
> >
> > 1) a new header field indicating "This is a forensic report, don't
> > generate a forensic report about it."
>
> Is there a reason somebody might use this new header in an abusive way?
> Or include it in a forged forensic report to avoid exposure? Cue a 0.1%
> of 0.1% sidebar...
>

I can't imagine one, but I'm running on little sleep at the moment.

Jumping ahead of those questions, would the new header have to be DKIM
> signed by the report generator, and the entity /doing final delivery of
> that report/ required to validate the DKIM signature(s) from the report
> generator, and only generate a forensic report in response if this new
> header is not present? Or if the signature didn't cover the new header?
> Or if the signature couldn't be validated?
>

Sure, those are all things to consider.

"Doing final delivery of that report" -- is that sufficient? Or, "any
> entity processing the report and potentially generating a report in
> response?"
>

I think you could put the check in either place.  Also fodder for
discussion of a solution.

> 2) some kind of token that's always in the Subject field of a DMARC
> > forensic report.
>
> DMARC forensic report Subject: lines aren't uniform, but the last time I
> looked there was an awful lot of similarity. If that were tightened up a
> little more, would an explicit token really be necessary?
>

I don't particularly care for the idea of standardizing a Subject header
field value, or part of one, as a way of doing loop detection anyway, but I
thought I'd throw it in there just to round out the list.

> 3) always generate forensic reports as the null sender, and specify
> > that forensic reports should never be generated in response to the
> > null sender
>
> I suppose that would meet the goal, but what would be lost along the
> way? What keeps coming to mind is the advice I've seen to have your
> bounce messages authenticate with DMARC - if a sender does that or is in
> the process of implementing it, they might want whatever forensic
> reports they could potentially get...
>

I'm also not a fan of the idea of treating different bounce messages in
different ways.  That seems like avoidable complexity.  Do we want to ever
send back a forensic report for something from the null sender,
irrespective of what's in it?

-MSK

--000000000000fb23e805b8dddaeb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 14, 2021 at 1:22 AM Steven M =
Jones &lt;<a href=3D"mailto:smj@crash.com">smj@crash.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">On 1/13/21 20:29, Murray S. Kucherawy wrote:<br>
&gt;<br>
&gt; How are implementers dealing with forensic report loops?<br>
<br>
The question of whether such a thing is actually ever seen in the wild<br>
should be asked, if only to document that it was asked and answered. See<br=
>
prior &quot;this is a vanishingly small number who cares&quot; discussions.=
<br></blockquote><div><br></div><div>I&#39;m asking the question in respons=
e to an actual use case.=C2=A0 Granted it&#39;s an isolated case so far, bu=
t it comes from a not-insignificant organization that probably handles a su=
bstantial email load, so at least for their side this is already happening,=
 or could happen, at scale.</div><div> <br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">
Channeling Dave, is it fair to just say the objective is: To ensure that<br=
>
forensic reports do not ever cause the recipient of a forensic report to<br=
>
generate another forensic report in response? Is that overly broad? Are<br>
there other goals or conditions?<br></blockquote><div><br></div><div>I beli=
eve that&#39;s exactly what I was asking for.</div><div> <br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">
&gt; Say I send a message from X to Y, whose DKIM signature fails.=C2=A0 Y =
sends<br>
&gt; me back a forensic report, whose DKIM signature also fails.=C2=A0 X se=
nds a<br>
&gt; forensic report to Y, whose report fails, etc.=C2=A0 We need a way to =
break<br>
&gt; the loop.<br>
<br>
Is there a functional or operational difference between aggregate and<br>
forensic reports I&#39;m not thinking of that would cause the solution for<=
br>
one case to be unsuitable for the other? Or can we hope for a mechanism<br>
that applies to all DMARC reports?<br></blockquote><div><br></div><div>I do=
n&#39;t see a reason why we need a different method for each report type.=
=C2=A0 The case in hand is forensic reports, but that&#39;s just part of th=
e specific incident to which I&#39;m responding.<br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
&gt; Off the top of my head, a few options:<br>
&gt;<br>
&gt; 1) a new header field indicating &quot;This is a forensic report, don&=
#39;t<br>
&gt; generate a forensic report about it.&quot;<br>
<br>
Is there a reason somebody might use this new header in an abusive way?<br>
Or include it in a forged forensic report to avoid exposure? Cue a 0.1%<br>
of 0.1% sidebar...<br></blockquote><div><br></div><div>I can&#39;t imagine =
one, but I&#39;m running on little sleep at the moment.</div><div> <br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">
Jumping ahead of those questions, would the new header have to be DKIM<br>
signed by the report generator, and the entity /doing final delivery of<br>
that report/ required to validate the DKIM signature(s) from the report<br>
generator, and only generate a forensic report in response if this new<br>
header is not present? Or if the signature didn&#39;t cover the new header?=
<br>
Or if the signature couldn&#39;t be validated?<br></blockquote><div><br></d=
iv><div>Sure, those are all things to consider.</div><div> <br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">
&quot;Doing final delivery of that report&quot; -- is that sufficient? Or, =
&quot;any<br>
entity processing the report and potentially generating a report in<br>
response?&quot;<br></blockquote><div><br></div><div>I think you could put t=
he check in either place.=C2=A0 Also fodder for discussion of a solution.</=
div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
&gt; 2) some kind of token that&#39;s always in the Subject field of a DMAR=
C<br>
&gt; forensic report.<br><br>
DMARC forensic report Subject: lines aren&#39;t uniform, but the last time =
I<br>
looked there was an awful lot of similarity. If that were tightened up a<br=
>
little more, would an explicit token really be necessary?<br></blockquote><=
div><br></div><div>I don&#39;t particularly care for the idea of standardiz=
ing a Subject header field value, or part of one, as a way of doing loop de=
tection anyway, but I thought I&#39;d throw it in there just to round out t=
he list.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
&gt; 3) always generate forensic reports as the null sender, and specify<br=
>
&gt; that forensic reports should never be generated in response to the<br>
&gt; null sender<br>
<br>
I suppose that would meet the goal, but what would be lost along the<br>
way? What keeps coming to mind is the advice I&#39;ve seen to have your<br>
bounce messages authenticate with DMARC - if a sender does that or is in<br=
>
the process of implementing it, they might want whatever forensic<br>
reports they could potentially get...<br></blockquote><div><br></div><div>I=
&#39;m also not a fan of the idea of treating different bounce messages in =
different ways.=C2=A0 That seems like avoidable complexity.=C2=A0 Do we wan=
t to ever send back a forensic report for something from the null sender, i=
rrespective of what&#39;s in it?<br></div><div><br></div><div>-MSK</div><br=
></div></div>

--000000000000fb23e805b8dddaeb--


From nobody Thu Jan 14 07:28:33 2021
Return-Path: <superuser@gmail.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 5788E3A10DA for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 07:28:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 YkQU4gGTcEGC for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 07:28:30 -0800 (PST)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E29A23A10D3 for <dmarc@ietf.org>; Thu, 14 Jan 2021 07:28:29 -0800 (PST)
Received: by mail-vs1-xe36.google.com with SMTP id j140so3292698vsd.4 for <dmarc@ietf.org>; Thu, 14 Jan 2021 07:28:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DRT/iVsyKWMn3yTRnxoKN6KwcdN0/CeVzlnK6hSuDwg=; b=tQYVyE7p9Gt54qRQwro23IBqyFzbJ2AJNCI+d90oYDcaiMbCFaEofJiPZwTfFzwiMT lz0v9Km0PMEXXECSPNLiku8+Wzf4y5r+6PXlTt2QE01JDxXL7C7FOuUIcA1liEYhC8eD xNNDc26xbQ2Wf+k1gxSOBSHCBktfFYqncgnP7QFhP225kTNwiv1OYQXGhi8q8BaqDfi/ L4K9Zo6LI+FS63JTibuBDzYJtULowZryYihkuXu+w6PdrWAKe50uOoBDuwopEbi/LGyb Gm/xh91nYQZRp4jy2frkyVumv+oinJnkrl/DcyFBhkD1GpM5yzXf9TzojMwvvk5zdXWk wTbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DRT/iVsyKWMn3yTRnxoKN6KwcdN0/CeVzlnK6hSuDwg=; b=GjU4WSxTqjbPGNiyQmVGw7VdpesOvcK40en12HRoUkWg85tDrpjQiIIGH1IciUJMxz oLn3Tlse2sLkPlPxr68d+oAzpQniJiOd+EsiwvdonW+YyEgmPJnrcxH486/RsKzvSc+t 03fzuDw9UvMReXkj6tBao+pp0UPt4wXACourkNH3WVlIKJwVT/H6hDptksG7eEsCafL+ qPrux8/D7KzJVV3qYz0JRohy8CxOVdpMZB+jf7EJzM8svQsjfTYypOw6CvwWpYWkKMam 1LqYGRxnvrp3CRsJ8j2i4tNlpI7ZVrngdqqp0e2KnIZwzF9K/8OLpgfWKswisKuaDQZU te/Q==
X-Gm-Message-State: AOAM533dTrc3WNj/E3QegR1FX7gRSQDH0XYBz5Xl13F39/6XcB2yQYGV lyYWZfCYwl7Hnu2V4cqHuSNG5ZYCpZZK4qido18=
X-Google-Smtp-Source: ABdhPJwkqOol0NIRueGz774QgrxjT84mvEs9cee+BTydUrAhtpmM13mb8ecmISm36B1YhQBltROzLyxkWGsqnUAKkiU=
X-Received: by 2002:a67:fb46:: with SMTP id e6mr7284946vsr.40.1610638108975; Thu, 14 Jan 2021 07:28:28 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com> <621d4aa5a72baf46b45a005f8e45eab6f7421e50.camel@aegee.org>
In-Reply-To: <621d4aa5a72baf46b45a005f8e45eab6f7421e50.camel@aegee.org>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 14 Jan 2021 07:28:17 -0800
Message-ID: <CAL0qLwa2Xy-aM_p1ebmHfOvPfo8SKeivMjp4qQSh_AyXHWr=-w@mail.gmail.com>
To: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= <dilyan.palauzov@aegee.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000058e7dc05b8dde851"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ElvtFxH2m2w92g1_pJ5FF4fVsVY>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 15:28:31 -0000

--00000000000058e7dc05b8dde851
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 14, 2021 at 3:12 AM =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=
=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2 <dilyan.palauzov@aegee.org>
wrote:

> I have not read the thread =E2=80=9CTicket #28 - Failure report mail loop=
s=E2=80=9D.
>

Thanks, and apologies to the group; I should've checked for an open ticket
on this topic first.

This one recommends rate limiting rather than simpler "don't" type
guidance.  I think we can table this until that ticket is open.

A possible approach is not to send failure reports for messages
> received on the address for accepting aggregate/forensic reports.
> These messages shall just be excluded from all calculations.
>

That seems plausible, though less bulletproof than simply using the address
already reserved by the email standard for administrative messages.

-MSK

--00000000000058e7dc05b8dde851
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 14, 2021 at 3:12 AM =D0=94=D0=
=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2 &lt;=
<a href=3D"mailto:dilyan.palauzov@aegee.org">dilyan.palauzov@aegee.org</a>&=
gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">I have not read the thread =E2=80=9CTicket #28 - Fail=
ure report mail loops=E2=80=9D.<br></blockquote><div><br></div><div>Thanks,=
 and apologies to the group; I should&#39;ve checked for an open ticket on =
this topic first.</div><div><br></div><div>This one recommends rate limitin=
g rather than simpler &quot;don&#39;t&quot; type guidance.=C2=A0 I think we=
 can table this until that ticket is open.</div><div><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">
A possible approach is not to send failure reports for messages<br>
received on the address for accepting aggregate/forensic reports. <br>
These messages shall just be excluded from all calculations.<br></blockquot=
e><div><br></div><div>That seems plausible, though less bulletproof than si=
mply using the address already reserved by the email standard for administr=
ative messages.</div><div><br></div><div>-MSK<br></div></div></div>

--00000000000058e7dc05b8dde851--


From nobody Thu Jan 14 08:04:16 2021
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 09FEB3A15AF for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 08:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 fodlnzyD2pC3 for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 08:04:12 -0800 (PST)
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 7BF343A15AB for <dmarc@ietf.org>; Thu, 14 Jan 2021 08:04:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1610640248; bh=+GxwAsjbTvs07drMkhPHLXvXDz1E1Rr6/0DFzhjv7ac=; l=1258; h=To:Cc:References:From:Date:In-Reply-To; b=Cr4vroGfHMrPzm3B/R/z+xwy24vg94k40S/BbklnbSP++HSeezZaSg9UU/1A1V9vm kwKqPSfSFlNxP+B9FhK0AwzQjOjYOTrTO8pm2Hymp5WiOd/qFFe89gVARCu5B+PSo9 wYAxRo08RXnhZdkzYMv0TqqN/ZLJo5t7T4tQ9KlAWJdU5dNaLcnrtVD/mhuUm
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Original-Cc: IETF DMARC WG <dmarc@ietf.org>
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.0000000060006B78.00006D1C; Thu, 14 Jan 2021 17:04:08 +0100
To: "Murray S. Kucherawy" <superuser@gmail.com>, Steven M Jones <smj@crash.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com> <CAL0qLwZVWRFnaK1iqMC800GCt651xwu=dEqhz=r9Z_CG2y3AKA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <06305d81-acd3-5c88-75ed-3daca7bfa814@tana.it>
Date: Thu, 14 Jan 2021 17:04:07 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwZVWRFnaK1iqMC800GCt651xwu=dEqhz=r9Z_CG2y3AKA@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/LcevO_DYD2l24U2h6rnJW_GmfhQ>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 16:04:14 -0000

On Thu 14/Jan/2021 16:24:33 +0100 Murray S. Kucherawy wrote:
> On Thu, Jan 14, 2021 at 1:22 AM Steven M Jones <smj@crash.com> wrote:
>> On 1/13/21 20:29, Murray S. Kucherawy wrote:
> 
>>> 3) always generate forensic reports as the null sender, and specify that
>>> forensic reports should never be generated in response to the null
>>> sender >>
>> I suppose that would meet the goal, but what would be lost along the way?
>> What keeps coming to mind is the advice I've seen to have your bounce
>> messages authenticate with DMARC - if a sender does that or is in the
>> process of implementing it, they might want whatever forensic reports they
>> could potentially get...

Another way is to set the From: domain to a subdomain having a DMARC record 
with neither rua= nor ruf=.  I use noloop.tana.it for aggregate reports.


> I'm also not a fan of the idea of treating different bounce messages in 
> different ways.  That seems like avoidable complexity.  Do we want to ever 
> send back a forensic report for something from the null sender, irrespective
> of what's in it?


It might be interesting to know if regular NDNs are authenticated all right. 
As they have the null sender, rule (3) prevents that feedback.


Best
Ale
-- 





















From nobody Thu Jan 14 09:35:46 2021
Return-Path: <johnl@iecc.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 85CA83A1332 for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 09:35:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=gOcJUDTN; dkim=pass (2048-bit key) header.d=taugh.com header.b=ZRbuZxQV
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 eUu_Br2GI0tx for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 09:35:43 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 E76D13A1230 for <dmarc@ietf.org>; Thu, 14 Jan 2021 09:35:42 -0800 (PST)
Received: (qmail 20472 invoked from network); 14 Jan 2021 17:35:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=4ff2.600080ed.k2101; bh=0lMGAtzWX2rE68DB5JMt4/OrJb+3sRVYl4qdV16l0Kw=; b=gOcJUDTNt4k6z7Ta7PpUhvfyP/naxvDAzY/4vg4osHhPbWF7rSzC96JafJJyZ/7WQ9lLLKZDzdygV8OXwbSqpgKvwCrZyBv7lV4e1tZPdS5VNOaO85cVMBAwBj44kSVAzImTWN8wEbbq5WhxnwbzVDer3OC+Jv+VpwIgtcmwQ50Olit2IDMD4k5k3FZ7HETa2MPU+9xt8nLR3gckonntrhwJKSZx79ne57qqttFE41zkdOht9xnaentbZnUgtkSxbG7E3kckkKCzpIaUWhiA/MA9QGvFhWA/Z3VPqfJCe6Skabs0wabjy2vWOr/3v26eLH/8g5td0ucPz8O8gRTglQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=4ff2.600080ed.k2101; bh=0lMGAtzWX2rE68DB5JMt4/OrJb+3sRVYl4qdV16l0Kw=; b=ZRbuZxQVK761z26gwyjImaUqff5qX+rrP/o4+ndqqgHr5WjowuUdqWSs9E2DnMuNrOSEHbA623jYw3ZOFqLXFnniIZsyHaqjX9HoPzWjWvwM1ahCazqc6tdNwEB+sM4lI5/0CFPJ+Uc/ng0Gab98JT4ESoFWDNNkij2WTSoXRbdGflP0C9MZyDgcf9Ueuwn5uqHhvOPU+B8yG3KZDD+789++CJjOBEXq+YUJN3hWmPcTISbVDBKexzErmd0D4VdO8Pw0b4zc8B/ByCIxfAQHTx9RP6XjXOdGRrtBB464vFOw561KK2GpqThF840CdG67OxmLPP+vIV8UwosmPSrFWg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 14 Jan 2021 17:35:41 -0000
Received: by ary.qy (Postfix, from userid 501) id B2B4A6A6C816; Thu, 14 Jan 2021 12:35:40 -0500 (EST)
Date: 14 Jan 2021 12:35:40 -0500
Message-Id: <20210114173540.B2B4A6A6C816@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: superuser@gmail.com
In-Reply-To: <CAL0qLwZVWRFnaK1iqMC800GCt651xwu=dEqhz=r9Z_CG2y3AKA@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9P44n-MbaZkJajCjk9WnBNflT0Y>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 17:35:45 -0000

In article <CAL0qLwZVWRFnaK1iqMC800GCt651xwu=dEqhz=r9Z_CG2y3AKA@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>On Thu, Jan 14, 2021 at 1:22 AM Steven M Jones <smj@crash.com> wrote:
>
>> On 1/13/21 20:29, Murray S. Kucherawy wrote:
>> >
>> > How are implementers dealing with forensic report loops?
>>
>> The question of whether such a thing is actually ever seen in the wild
>> should be asked, if only to document that it was asked and answered. See
>> prior "this is a vanishingly small number who cares" discussions.
>
>I'm asking the question in response to an actual use case.  Granted it's an
>isolated case so far, but it comes from a not-insignificant organization
>that probably handles a substantial email load, so at least for their side
>this is already happening, or could happen, at scale.

Why isn't the solution to fix the sender's configuration so the reports
are aligned?  They're just mail messages.

R's,
John


From nobody Thu Jan 14 09:51:06 2021
Return-Path: <kurta@drkurt.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 2D4483A119E for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 09:51:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.com
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 WoF1WdJQQxYk for <dmarc@ietfa.amsl.com>; Thu, 14 Jan 2021 09:51:03 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6467E3A149D for <dmarc@ietf.org>; Thu, 14 Jan 2021 09:51:00 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id u17so12935566iow.1 for <dmarc@ietf.org>; Thu, 14 Jan 2021 09:51:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WMturFuGkGjPf0w7X6T/bNI+6ciA7hJ1p+Lmte/ey60=; b=SuLN7b5+XqYGqO0oLQKk2s3q8fdIxRxXWDCVuVwqtQuarnWSTZW5KPSa2CAqnVpkTF mzUZopdw38nLn92oSRbrUv09OXwhr+autFh54A4RuRNjaR7vQMKTaOe/9qeGPr6l8LOq DUrzCi4uEIL+GuPB2vSG4PQvaQOVX4OBRPSl4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WMturFuGkGjPf0w7X6T/bNI+6ciA7hJ1p+Lmte/ey60=; b=EVrEcqCqORuV1tOQzuhykc5I99YW0gfPD3FOGBOehBHQlV91QUbTfhP4vY+lzprKi/ UtvcU0kCRqCkR+VggTkSD9gdv9N+onHAZlaIreySav+qq5dOm3IuSucItj5SWNqc1/n6 r+8NCJS78ikfYkdMK5u+rGY4oOctfL6sRpynOP9AVjiyrS1L5BOZ+DFUbR14VVVde3/l E5AyOpqqtlDwubv93KFXMEWq4Af/HMT41DbsCgO8NxnfUtsOCUrt+XJFvOYjnfVxsxDO klM/6hI1Xkp19kMC/hoHMv7dR5ijtF4ugfKybXLSljG7EiYc1fWSW4zuadUefhtwx3Jc y0OA==
X-Gm-Message-State: AOAM5331q2zGeKjjcpC+LkdW3LGc1OO0UdjpXnQzLDU4kPqA/NUGYrnH 63rtedT72l2LeIeWj/usgOeZdL56YPqCBbxGLvHOIg==
X-Google-Smtp-Source: ABdhPJx2SB+pCeayJ26IBEBVzXj/IaaVrUDNSzMWazYr9U1a6gUliOultR8fZ3gDkRE9MumYuC6yF/bjhUX8HPmDEA0=
X-Received: by 2002:a92:9f15:: with SMTP id u21mr8069497ili.120.1610646659474;  Thu, 14 Jan 2021 09:50:59 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com> <621d4aa5a72baf46b45a005f8e45eab6f7421e50.camel@aegee.org> <CAL0qLwa2Xy-aM_p1ebmHfOvPfo8SKeivMjp4qQSh_AyXHWr=-w@mail.gmail.com>
In-Reply-To: <CAL0qLwa2Xy-aM_p1ebmHfOvPfo8SKeivMjp4qQSh_AyXHWr=-w@mail.gmail.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Thu, 14 Jan 2021 09:50:47 -0800
Message-ID: <CABuGu1oK+4xHjs-o0i617MGxuGaQVmrR-3_Tfrec=_1BWz5NRg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= <dilyan.palauzov@aegee.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ff3a7705b8dfe5b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/94OF0gfiODzZFJ-G9zJ6aH3Sx3c>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Thu, 14 Jan 2021 17:51:05 -0000

--000000000000ff3a7705b8dfe5b8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 14, 2021 at 7:28 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Thu, Jan 14, 2021 at 3:12 AM =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=
=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2 <dilyan.palauzov@aegee.org>
> wrote:
>
>> I have not read the thread =E2=80=9CTicket #28 - Failure report mail loo=
ps=E2=80=9D.
>>
>
> Thanks, and apologies to the group; I should've checked for an open ticke=
t
> on this topic first.
>
> This one recommends rate limiting rather than simpler "don't" type
> guidance.  I think we can table this until that ticket is open.
>
> A possible approach is not to send failure reports for messages
>> received on the address for accepting aggregate/forensic reports.
>> These messages shall just be excluded from all calculations.
>>
>
> That seems plausible, though less bulletproof than simply using the
> address already reserved by the email standard for administrative message=
s.
>

I thought that we discussed that ticket and decided that the incidence of
problems was low enough to warrant a "WONT FIX" determination.

https://mailarchive.ietf.org/arch/browse/dmarc/?gbt=3D1&index=3DW3uGPEpT3Yi=
5lqKntZXyL8jkNjk

--Kurt

--000000000000ff3a7705b8dfe5b8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 14, 2021 at 7:28 AM Murray S.=
 Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com">superuser@gmail.com</=
a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 14, =
2021 at 3:12 AM =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=D0=BB=D0=B0=D1=
=83=D0=B7=D0=BE=D0=B2 &lt;<a href=3D"mailto:dilyan.palauzov@aegee.org" targ=
et=3D"_blank">dilyan.palauzov@aegee.org</a>&gt; wrote:<br></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I have n=
ot read the thread =E2=80=9CTicket #28 - Failure report mail loops=E2=80=9D=
.<br></blockquote><div><br></div><div>Thanks, and apologies to the group; I=
 should&#39;ve checked for an open ticket on this topic first.</div><div><b=
r></div><div>This one recommends rate limiting rather than simpler &quot;do=
n&#39;t&quot; type guidance.=C2=A0 I think we can table this until that tic=
ket is open.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
A possible approach is not to send failure reports for messages<br>
received on the address for accepting aggregate/forensic reports. <br>
These messages shall just be excluded from all calculations.<br></blockquot=
e><div><br></div><div>That seems plausible, though less bulletproof than si=
mply using the address already reserved by the email standard for administr=
ative messages.</div></div></div></blockquote><div><br></div><div>I thought=
 that we discussed that ticket and decided that the incidence of problems w=
as low enough to warrant a &quot;WONT FIX&quot; determination.</div><div><b=
r></div><div><a href=3D"https://mailarchive.ietf.org/arch/browse/dmarc/?gbt=
=3D1&amp;index=3DW3uGPEpT3Yi5lqKntZXyL8jkNjk">https://mailarchive.ietf.org/=
arch/browse/dmarc/?gbt=3D1&amp;index=3DW3uGPEpT3Yi5lqKntZXyL8jkNjk</a><br><=
/div><div><br></div><div>--Kurt</div><div>=C2=A0</div></div></div>

--000000000000ff3a7705b8dfe5b8--


From nobody Fri Jan 15 08:25:12 2021
Return-Path: <superuser@gmail.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 1186A3A0C9D for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 08:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gnanar1p5_eB for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 08:25:09 -0800 (PST)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CD6E3A0CA0 for <dmarc@ietf.org>; Fri, 15 Jan 2021 08:25:09 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id h18so5307957vsg.8 for <dmarc@ietf.org>; Fri, 15 Jan 2021 08:25:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bHrHCqQLPimxzFACYqokvHTVcHqyq5+/iUXLHMhZShM=; b=ZMGj9lbvqC0q85lqZtIfSm+McAfvlQAGMqOMpTGmj68yEQM+/BGHpmODU2NMnKzEbH 94QJGUzyvoq7PPllaoVR82mqR3MBMGPhqOKdI1WBpc0PomW/8qUmXvo2jB4cUkEN2dqy JZPCHzm1y9irGfFvq/exxJBctI8vWK7hAvC5oSBcvB1OwRlykgz6gMPSLWoPPK/r4KlQ hbBNo8il8vsDj0SGb0fp68/LDynl/G+O85WVZXEV5HPWDKuW/NWWPv3gyNA1mwEyPcG3 hGNvTsvQQUDl8BntgJZYA/tBYmvcQb5+hxl2KDOOylFWQopHNl9MXY3CQVArQUUQSM+E IKxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bHrHCqQLPimxzFACYqokvHTVcHqyq5+/iUXLHMhZShM=; b=rArCn+SSyjvpk6c99KPkMeDy5LAcyALbUvd1qACgB+5IoMR1R5X0ozimV28InP+y// F6X50U/jE3luRGkRZQPcbFvB8vD2jE2jfxugUpE5OXBulm0PBm5uWuZLupFP58gUzb8i mFwqCkrY/9+F5tSmemr4TkoJfwjjs/K5Ws1ebcOxPU9tmv6NeX8ILIMNvWaKDQlnPXU6 vxt56TceldizzPILWybIPIO12co+OuZiGBrAXPe+uEbJpFArswJl8D9/SxOGUFrtrEqR CN57vzjmtJZ6RaEm9HWbZ8BgBv5wPMj0Xr/pWUDFMb2ypUfUvAgjVSPDSer8P+Q0D0VR Uhow==
X-Gm-Message-State: AOAM5316g2gUDrWPHfkV+LlXC7SmAkeqXHO/XD36S58r88yRz6aispLk YpX34DjrpMNA8hPlXkqKHfBkHqrvrOJLbETESmY=
X-Google-Smtp-Source: ABdhPJwMFSPpyxfJhM6gDS7C5lj9786p9WEU0c3NVqP43yqmrJlBX4pU8+xO1BBMEuX/l8o8fWNN/9pVyPq1HcnjM9I=
X-Received: by 2002:a05:6102:808:: with SMTP id g8mr5946291vsb.0.1610727908630;  Fri, 15 Jan 2021 08:25:08 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com> <621d4aa5a72baf46b45a005f8e45eab6f7421e50.camel@aegee.org> <CAL0qLwa2Xy-aM_p1ebmHfOvPfo8SKeivMjp4qQSh_AyXHWr=-w@mail.gmail.com> <CABuGu1oK+4xHjs-o0i617MGxuGaQVmrR-3_Tfrec=_1BWz5NRg@mail.gmail.com>
In-Reply-To: <CABuGu1oK+4xHjs-o0i617MGxuGaQVmrR-3_Tfrec=_1BWz5NRg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 15 Jan 2021 08:24:57 -0800
Message-ID: <CAL0qLwbeR_HGY9kFc9WxqnfCOqatmPKtdaT2x-LSsrAuxNMRgg@mail.gmail.com>
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Cc: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= <dilyan.palauzov@aegee.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d2e37705b8f2d071"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Bilp87WnnITEqFBY7fgqdWIMhec>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Fri, 15 Jan 2021 16:25:11 -0000

--000000000000d2e37705b8f2d071
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 14, 2021 at 9:51 AM Kurt Andersen (b) <kboth@drkurt.com> wrote:

> I thought that we discussed that ticket and decided that the incidence of
> problems was low enough to warrant a "WONT FIX" determination.
>
>
> https://mailarchive.ietf.org/arch/browse/dmarc/?gbt=1&index=W3uGPEpT3Yi5lqKntZXyL8jkNjk
>

We did, and if it had only ever come up exactly once, I might think nothing
of it.  But here it is again.  Now I'm inclined to think where there's
smoke there's fire, and this might require more consideration.

-MSK, participating

--000000000000d2e37705b8f2d071
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 14, 2021 at 9:51 AM Kurt Ande=
rsen (b) &lt;<a href=3D"mailto:kboth@drkurt.com">kboth@drkurt.com</a>&gt; w=
rote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr">I thought that we discussed that ticket a=
nd decided that the incidence of problems was low enough to warrant a &quot=
;WONT FIX&quot; determination.<div class=3D"gmail_quote"><div><br></div><di=
v><a href=3D"https://mailarchive.ietf.org/arch/browse/dmarc/?gbt=3D1&amp;in=
dex=3DW3uGPEpT3Yi5lqKntZXyL8jkNjk" target=3D"_blank">https://mailarchive.ie=
tf.org/arch/browse/dmarc/?gbt=3D1&amp;index=3DW3uGPEpT3Yi5lqKntZXyL8jkNjk</=
a><br></div></div></div></blockquote><div><br></div><div>We did, and if it =
had only ever come up exactly once, I might think nothing of it.=C2=A0 But =
here it is again.=C2=A0 Now I&#39;m inclined to think where there&#39;s smo=
ke there&#39;s fire, and this might require more consideration.</div><div><=
br></div><div>-MSK, participating<br></div></div></div>

--000000000000d2e37705b8f2d071--


From nobody Fri Jan 15 13:31:52 2021
Return-Path: <dougfoster.emailstandards@gmail.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 3C6673A11E4 for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 13:31:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LzO9RPbFE98a for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 13:31:44 -0800 (PST)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F9A33A11DD for <dmarc@ietf.org>; Fri, 15 Jan 2021 13:31:44 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id x26so5831410vsq.1 for <dmarc@ietf.org>; Fri, 15 Jan 2021 13:31:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OzQr/1rT5xEhaDNgx65iawc3yHmvTzeCzPsbYRW3Nds=; b=CPqM/AnxrX+TzeaIzPzAsJE2Y+wN07TIxrqnx0v61N9XJQ3gGrbOcLk2F0miyt4557 HqwpknW8fT+hnBryg2AJ5Fp1OSsZf4+ASpIp2pxhpA4bP9n4aRgfEhikFpFGSlOa0e24 7kQs8n30upXDIppGSH1g9g3Cf0bRw8r68rL8T+l23QgE7NVXteQp5TtSRSbtUTAV6MGw vFD/hFyOPRp9ONPdt0Xaj0dprXXjjERsqHeVJysKsNCoZxu4FGkxtrLDnlTE7S1T08U/ PptujO3NGGJGfVeq/FOAX9SnMO6yCnOw+7BSzwHnQpXCLRsZ5XWC3heCqM30JT6cD79w 6Hqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OzQr/1rT5xEhaDNgx65iawc3yHmvTzeCzPsbYRW3Nds=; b=Dy2bE9/l3hrhzz69aPbO5sMhfcg1e0YzWpvoOtV8CcVTcsmD4r7/Tfcg6cFYaTA3qv rsQ9Cn1NpR9w4bwonxjz8ZygWCz3MTbgRRamzlpIwIMpzq9HC+y6FhZP7fmNm3NzPBqX wOtMLojigg2bUs4rh73+ckDO+cDC5XbBHwgy9GA7Hh/sr+sfNE1YDADuj0qRYS3qcPjf 5soXvrYJPeXqk3iIUfBL3RDHhEkAJrRtTjFW+Evabc94FFpwFjI+PQWOI3jFUdr1KArq aDu8E4oklGL9Rt2rivLjxhzj0baCPjjRqof7bXVAO5oVD9DyTSwxIayWUd9Yp/4g9jD3 txWg==
X-Gm-Message-State: AOAM530XX1XUt4IRMXJDmVcaKNcfcZ8xr673610h2lnDln6x6AyBtLws kq19z2ncb3FN7EkzDvyoxtbJzMgnALdH6DlvJF8=
X-Google-Smtp-Source: ABdhPJyvmcuhOR99AD+XaApJcNnnjaTEsSIEA1HoiXGG+5EfgNI1stb1EsV2uwKB/kepiVZpOHRvwZoPneEp0wxCtuM=
X-Received: by 2002:a05:6102:3029:: with SMTP id v9mr9858842vsa.25.1610746303377;  Fri, 15 Jan 2021 13:31:43 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com> <621d4aa5a72baf46b45a005f8e45eab6f7421e50.camel@aegee.org> <CAL0qLwa2Xy-aM_p1ebmHfOvPfo8SKeivMjp4qQSh_AyXHWr=-w@mail.gmail.com> <CABuGu1oK+4xHjs-o0i617MGxuGaQVmrR-3_Tfrec=_1BWz5NRg@mail.gmail.com> <CAL0qLwbeR_HGY9kFc9WxqnfCOqatmPKtdaT2x-LSsrAuxNMRgg@mail.gmail.com>
In-Reply-To: <CAL0qLwbeR_HGY9kFc9WxqnfCOqatmPKtdaT2x-LSsrAuxNMRgg@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Fri, 15 Jan 2021 16:31:30 -0500
Message-ID: <CAH48Zfz4yGzGZcXJBjdeyO7dPK405EtmRebkgvMTS34Jgek2zg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "Kurt Andersen (b)" <kboth@drkurt.com>, IETF DMARC WG <dmarc@ietf.org>,  =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= <dilyan.palauzov@aegee.org>
Content-Type: multipart/alternative; boundary="0000000000003c750105b8f71982"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/b5JkRTCiOFjzhBAkYagLTmEx8UM>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Fri, 15 Jan 2021 21:31:47 -0000

--0000000000003c750105b8f71982
Content-Type: text/plain; charset="UTF-8"

I would think this should prevent problems if at least one complies:

Reports should be sent from a no-reply account so that any auto-reply will
be rejected as invalid recipient.   DMARC reporting SHOULD NOT occur for
such messages, even if the DATA section is accepted before rejecting or
discarding the message.

Report reception accounts should be dedicated to this purpose.
 Unacceptable incoming messages to this account SHOULD be excluded from
DMARC reporting, regardless of reason.  Accepted messages MAY also be
excluded from DMARC reporting.

Doug Foster

On Fri, Jan 15, 2021, 11:25 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Thu, Jan 14, 2021 at 9:51 AM Kurt Andersen (b) <kboth@drkurt.com>
> wrote:
>
>> I thought that we discussed that ticket and decided that the incidence of
>> problems was low enough to warrant a "WONT FIX" determination.
>>
>>
>> https://mailarchive.ietf.org/arch/browse/dmarc/?gbt=1&index=W3uGPEpT3Yi5lqKntZXyL8jkNjk
>>
>
> We did, and if it had only ever come up exactly once, I might think
> nothing of it.  But here it is again.  Now I'm inclined to think where
> there's smoke there's fire, and this might require more consideration.
>
> -MSK, participating
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--0000000000003c750105b8f71982
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I would think this should prevent problems if at least on=
e complies:<div dir=3D"auto"><br></div><div dir=3D"auto">Reports should be =
sent from a no-reply account so that any auto-reply will be rejected as inv=
alid recipient.=C2=A0 =C2=A0DMARC reporting SHOULD NOT occur for such messa=
ges, even if the DATA section is accepted before rejecting or discarding th=
e message.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Report recept=
ion accounts should be dedicated to this purpose.=C2=A0 =C2=A0Unacceptable =
incoming messages to this account SHOULD be excluded from DMARC reporting, =
regardless of reason.=C2=A0 Accepted messages MAY also be excluded from DMA=
RC reporting.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Doug Foste=
r</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Fri, Jan 15, 2021, 11:25 AM Murray S. Kucherawy &lt;<a href=3D"ma=
ilto:superuser@gmail.com">superuser@gmail.com</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 14,=
 2021 at 9:51 AM Kurt Andersen (b) &lt;<a href=3D"mailto:kboth@drkurt.com" =
target=3D"_blank" rel=3D"noreferrer">kboth@drkurt.com</a>&gt; wrote:<br></d=
iv><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr">I thought that we discussed that ticket and decided t=
hat the incidence of problems was low enough to warrant a &quot;WONT FIX&qu=
ot; determination.<div class=3D"gmail_quote"><div><br></div><div><a href=3D=
"https://mailarchive.ietf.org/arch/browse/dmarc/?gbt=3D1&amp;index=3DW3uGPE=
pT3Yi5lqKntZXyL8jkNjk" target=3D"_blank" rel=3D"noreferrer">https://mailarc=
hive.ietf.org/arch/browse/dmarc/?gbt=3D1&amp;index=3DW3uGPEpT3Yi5lqKntZXyL8=
jkNjk</a><br></div></div></div></blockquote><div><br></div><div>We did, and=
 if it had only ever come up exactly once, I might think nothing of it.=C2=
=A0 But here it is again.=C2=A0 Now I&#39;m inclined to think where there&#=
39;s smoke there&#39;s fire, and this might require more consideration.</di=
v><div><br></div><div>-MSK, participating<br></div></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank" rel=3D"noreferrer">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div>

--0000000000003c750105b8f71982--


From nobody Fri Jan 15 13:40:27 2021
Return-Path: <dilyan.palauzov@aegee.org>
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 03B903A11F7 for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 13:40:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
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 Ii2gAwR40rau for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 13:40:22 -0800 (PST)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (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 621EE3A11F6 for <dmarc@ietf.org>; Fri, 15 Jan 2021 13:40:21 -0800 (PST)
Authentication-Results: mail.aegee.org/10FLeDEW289960; auth=pass (LOGIN) smtp.auth=didopalauzov@aegee.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1610746816; i=dkim+MSA-tls@aegee.org; bh=y63BcwR5gn/bJlqa0HZDRMYudXa1kmkIAUMjaYbTpLU=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=ZATi3aB57bgAJBM3qgSnSBk+2O9uMGJyoJ267DmuqlHW5L/Li1BLqPfJAyKKxdcmt Ixyx4dk3Ptd9ROjCrzlCMKhIZx0vFCCaabtYsYaZytHgtuXyqs6moTULEwC2nOJsS5 lF54d4cTWpYmV3DPPup5VIxSEhGMHJZamyIiGX89f8A434kV8EdEEg72CwAEZ8dF+i JNmel0MR33X8OKaDp0JXx/o/km1QsMsGwlxJzqhOHsANFGJbpiM/vZ89MtDtkRn3za KnTwhvGApZ7ho3lefooBVQIF5C8Uk0y7e1XzJTRAlFnRvn7nF2zw38ELih54slq8tD xaKseFAv/IfGk/qZHsCCOrHgt5UW4BFIVNmbbM3RVpT/7SMPgLlT/ieeXZb+4saBsg mylNjTDSYcv1q9f3fp9dGjYvW0P40nPDVO6lk/6Zvz7eMd0HcB9FIz+U4ORfxiJgCp m6Z+C4CPmakPWE+cD4/Ja18i2Cn4aK6DOr6ix1U+3uuaBLFJAEfxuivnxm5woiLkoD rw/plVIIPrpJKAfkCs4rW2SruXu4yWP2KHpEZMgN3yDGZSDxjh3jY5IWWdrw+vTVsH EWLDrxWop+5TVcNK2Rew7KzC8OLf7nX5WO5FEzqRJ7HiOeMW+h7k8KW05J+Qgj4D26 slXl6GBvd/J2lOZHtFuVOUx8=
Authentication-Results: mail.aegee.org/10FLeDEW289960; dkim=none
Received: from [192.168.0.125] (87.118.146.153.topnet.bg [87.118.146.153] (may be forged)) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id 10FLeDEW289960 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 15 Jan 2021 21:40:14 GMT
Message-ID: <e5d26bccdadc2abb2390f2a491ef5894d5641048.camel@aegee.org>
From: =?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?= <dilyan.palauzov@aegee.org>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Fri, 15 Jan 2021 23:40:13 +0200
In-Reply-To: <CAH48Zfz4yGzGZcXJBjdeyO7dPK405EtmRebkgvMTS34Jgek2zg@mail.gmail.com>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com> <621d4aa5a72baf46b45a005f8e45eab6f7421e50.camel@aegee.org> <CAL0qLwa2Xy-aM_p1ebmHfOvPfo8SKeivMjp4qQSh_AyXHWr=-w@mail.gmail.com> <CABuGu1oK+4xHjs-o0i617MGxuGaQVmrR-3_Tfrec=_1BWz5NRg@mail.gmail.com> <CAL0qLwbeR_HGY9kFc9WxqnfCOqatmPKtdaT2x-LSsrAuxNMRgg@mail.gmail.com> <CAH48Zfz4yGzGZcXJBjdeyO7dPK405EtmRebkgvMTS34Jgek2zg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-0Do961LE++DPOjml0lY9"
User-Agent: Evolution 3.39.2 
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mdo7sFEttPO230wCFJKvF8roLSg>
Subject: Re: [dmarc-ietf] Forensic report loops
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: Fri, 15 Jan 2021 21:40:25 -0000

--=-0Do961LE++DPOjml0lY9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

Hello,

Am Freitag, dem 15.01.2021 um 16:31 -0500 schrieb Douglas Foster:
> I would think this should prevent problems if at least one complies:
> 
> Reports should be sent from a no-reply account so that any auto-reply
> will be rejected as invalid recipient.   DMARC reporting SHOULD NOT
> occur for such messages, even if the DATA section is accepted before
> rejecting or discarding the message.
> 
> Report reception accounts should be dedicated to this purpose. 
>  Unacceptable incoming messages to this account SHOULD be excluded
> from DMARC reporting, regardless of reason.  Accepted messages MAY
> also be excluded from DMARC reporting.
> 

this text suggests WHAT to do, but not WHY to do it.  In my opinion any
suggested workflow shall be accomplished by problem description, so
that the implementers can understand the  rationale of the proposed
solution (and thus higher the chances, that the endless loops are
prevented).  I put the problem description in my previous mail on this
mailing list.

Greetings
  Дилян

 

> Doug Foster
> 
> On Fri, Jan 15, 2021, 11:25 AM Murray S. Kucherawy
> <superuser@gmail.com> wrote:
> > On Thu, Jan 14, 2021 at 9:51 AM Kurt Andersen (b)
> > <kboth@drkurt.com> wrote:
> > > I thought that we discussed that ticket and decided that the
> > > incidence of problems was low enough to warrant a "WONT FIX"
> > > determination.
> > > 
> > >
> >
> https://mailarchive.ietf.org/arch/browse/dmarc/?gbt=1&index=W3uGPEpT3Yi5lqKntZXyL8jkNjk
> > > 
> > 
> > 
> > We did, and if it had only ever come up exactly once, I might think
> > nothing of it.  But here it is again.  Now I'm inclined to think
> > where there's smoke there's fire, and this might require more
> > consideration.
> > 
> > -MSK, participating
> > _______________________________________________
> > dmarc mailing list
> > dmarc@ietf.org
> > https://www.ietf.org/mailman/listinfo/dmarc
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


--=-0Do961LE++DPOjml0lY9
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div>Hello,</div><div><br></div><div>Am Freitag, d=
em 15.01.2021 um 16:31 -0500 schrieb Douglas Foster:</div><blockquote type=
=3D"cite" style=3D"margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding=
-left:1ex"><div dir=3D"auto">I would think this should prevent problems if =
at least one complies:<div dir=3D"auto"><br></div><div dir=3D"auto">Reports=
 should be sent from a no-reply account so that any auto-reply will be reje=
cted as invalid recipient.&nbsp; &nbsp;DMARC reporting SHOULD NOT occur for=
 such messages, even if the DATA section is accepted before rejecting or di=
scarding the message.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Re=
port reception accounts should be dedicated to this purpose.&nbsp; &nbsp;Un=
acceptable incoming messages to this account SHOULD be excluded from DMARC =
reporting, regardless of reason.&nbsp; Accepted messages MAY also be exclud=
ed from DMARC reporting.</div><div dir=3D"auto"><br></div></div></blockquot=
e><div><br></div><div>this text suggests WHAT to do, but not WHY to do it. =
&nbsp;In my opinion any suggested workflow shall be accomplished by problem=
 description, so that the implementers can understand the &nbsp;rationale o=
f the proposed solution (and thus higher the chances, that the endless loop=
s are prevented). &nbsp;I put the problem description in my previous mail o=
n this mailing list.</div><div><br></div><div>Greetings</div><div>&nbsp; =
=D0=94=D0=B8=D0=BB=D1=8F=D0=BD</div><div><br></div><div>&nbsp;</div><div><b=
r></div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; border-left:2=
px #729fcf solid;padding-left:1ex"><div dir=3D"auto"><div dir=3D"auto">Doug=
 Foster</div></div><div><br></div><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Fri, Jan 15, 2021, 11:25 AM Murray S. Kucherawy =
&lt;<a href=3D"mailto:superuser@gmail.com">superuser@gmail.com</a>&gt; wrot=
e:<br></div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; border-le=
ft:2px #729fcf solid;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On=
 Thu, Jan 14, 2021 at 9:51 AM Kurt Andersen (b) &lt;<a href=3D"mailto:kboth=
@drkurt.com" target=3D"_blank" rel=3D"noreferrer">kboth@drkurt.com</a>&gt; =
wrote:<br></div><div class=3D"gmail_quote"><blockquote type=3D"cite" style=
=3D"margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div=
 dir=3D"ltr">I thought that we discussed that ticket and decided that the i=
ncidence of problems was low enough to warrant a "WONT FIX" determination.<=
div class=3D"gmail_quote"><div><br></div><div><a href=3D"https://mailarchiv=
e.ietf.org/arch/browse/dmarc/?gbt=3D1&amp;index=3DW3uGPEpT3Yi5lqKntZXyL8jkN=
jk" target=3D"_blank" rel=3D"noreferrer">https://mailarchive.ietf.org/arch/=
browse/dmarc/?gbt=3D1&amp;index=3DW3uGPEpT3Yi5lqKntZXyL8jkNjk</a><br></div>=
</div></div><br></blockquote><div><br></div><div>We did, and if it had only=
 ever come up exactly once, I might think nothing of it.&nbsp; But here it =
is again.&nbsp; Now I'm inclined to think where there's smoke there's fire,=
 and this might require more consideration.</div><div><br></div><div>-MSK, =
participating<br></div></div></div><div>___________________________________=
____________<br>dmarc mailing list<br></div><div><a href=3D"mailto:dmarc@ie=
tf.org" target=3D"_blank" rel=3D"noreferrer">dmarc@ietf.org</a><br></div><d=
iv><a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferre=
r noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc=
</a><br></div></blockquote></div><div>_____________________________________=
__________<br></div><div>dmarc mailing list<br></div><div><a href=3D"mailto=
:dmarc@ietf.org">dmarc@ietf.org</a><br></div><div><a href=3D"https://www.ie=
tf.org/mailman/listinfo/dmarc">https://www.ietf.org/mailman/listinfo/dmarc<=
/a><br></div></blockquote><div><br></div><div><span></span></div></body></h=
tml>

--=-0Do961LE++DPOjml0lY9--


From nobody Fri Jan 15 19:40:32 2021
Return-Path: <johnl@iecc.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 510F53A149C for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 19:40:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level: 
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=YV//M+0m; dkim=pass (2048-bit key) header.d=taugh.com header.b=sp3bHg0y
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 SGDLChINtLip for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 19:40:29 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 A457C3A14A1 for <dmarc@ietf.org>; Fri, 15 Jan 2021 19:40:28 -0800 (PST)
Received: (qmail 45086 invoked from network); 16 Jan 2021 03:40:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b003.6002602b.k2101; bh=xe2DDE1nXZylYqCjWM+HY7tIas1Zrw5k3A26daDU67k=; b=YV//M+0m5F//gkjuJWAI+qbiVTAsc0LXUyU+Ehkds6LkoIPKystwnK7vhEPzh3VrAqxG/qcjK4ZTL2Q6F9U3x69doS2EoOuDctHqiEJLjWC+MbuHsXBeWjAgb7nGG+6i9Q5nqZlNGr11yM1NjrU+F1PtM0Nzd80nehjwsKFPqmcElheuqnmiwTdzYSdUBgftaQxcso4pjsUbdAbjTKixRXZnSCnnwMbuCnMiH855Rdo4A7yol3NVxTth7k+QoXARQu/E+RGbdsPRP3anK1qUE1QvVhsOyaPoIts6elMZnhi7chiSCQlUHcNF7t3hw54HgX33+iQvMLxfKUxHjqDc3g==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b003.6002602b.k2101; bh=xe2DDE1nXZylYqCjWM+HY7tIas1Zrw5k3A26daDU67k=; b=sp3bHg0yhSQP3Gmv8oNe4woDM0QuJnTwhMNb0rAW9SL5OVZIn3NnlhUQ3rwPBcAv76xI+LvIMFQ/eVEJRQmhcxP0Q5fa2NZJ560nfcoY9i0GcUzcXSvdZ5RphoWCBt5J9yS5aN5aYbByIRCNhuD2OtJjhBl7T32HfBx+jD69yuJbqS1cs4Rkd48K405Wlh9q5dlDpNMXdpX/uNwQif4lxRoqAUkQBYwjFeLOP0V+ihTVs//unS27nXx/ep5ZLWRLsbJm0u2hlCIGaBxmrhkyRVpdU/xATp0CvPrFWXom94TaB5nxHJh8IgBgDieYOqly+zXZvAbZHGZwrh1IFX+X4Q==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 16 Jan 2021 03:40:26 -0000
Received: by ary.qy (Postfix, from userid 501) id 5C93F6AC0428; Fri, 15 Jan 2021 22:40:26 -0500 (EST)
Date: 15 Jan 2021 22:40:26 -0500
Message-Id: <20210116034026.5C93F6AC0428@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: superuser@gmail.com
In-Reply-To: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PneYeYgl6KacWCS1rrxG00Qy-Qc>
Subject: Re: [dmarc-ietf] Forensic report loops are not a problem
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, 16 Jan 2021 03:40:31 -0000

In article <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>How are implementers dealing with forensic report loops?
>
>Say I send a message from X to Y, whose DKIM signature fails.  Y sends me
>back a forensic report, whose DKIM signature also fails.  X sends a
>forensic report to Y, whose report fails, etc.  We need a way to break the
>loop.

If the reports are unaligned and their domain is requesting failure
reports, sending reports about the failure is exactly the right thing
to do.

I still don't understand why anyone thinks there is a problem to be
fixed. If you don't want reports, don't ask for them. If you think the
mail you send shouldn't be provoking DMARC failure reports, adjust
whatever is sending the mail the mail is aligned, or get rid of the
ruf= that asks for the reports. What am I missing here?


From nobody Sat Jan 16 05:22:12 2021
Return-Path: <dougfoster.emailstandards@gmail.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 4CC193A0C7C for <dmarc@ietfa.amsl.com>; Sat, 16 Jan 2021 05:22:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JkWnS2-CWTI0 for <dmarc@ietfa.amsl.com>; Sat, 16 Jan 2021 05:22:09 -0800 (PST)
Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CEE73A0C70 for <dmarc@ietf.org>; Sat, 16 Jan 2021 05:22:09 -0800 (PST)
Received: by mail-ua1-x932.google.com with SMTP id u27so425928uaa.13 for <dmarc@ietf.org>; Sat, 16 Jan 2021 05:22:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wih4KIYmLqGtP8fYSRnq1KrRYefkUnmLSsF2Xzhu4HQ=; b=hW8oVzz8Go7kLRfrXYlEvy+ArV+xd/zBSKGZJMOgfMRaM/N0SKHlWB9pkohVrZNL2/ fHFwEoyZzttwZVkz11VNInejriK+sdxwpRVaQVlUAiOT/vzV65ENS3tOF/KvM0joubHn gikOhp9eq94ZjRhHaH9QjOuaWXMSvtwgFMuUyg9Jrp0CZpQieTnXqqZi3y4Wltrmuevp 1YL8owKGFgOdRu+0hpUKzjGR/Pv6Q70RLBIkRPoprtnEKkXaTnVirgNRqq3FnxnS8XJI qnhVDIiS7s/Psqtq1WVE15nPrAFpFAB9OIs10t3QErnzhJFHlc2xO6wgYmD0nBRmAFep ooxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wih4KIYmLqGtP8fYSRnq1KrRYefkUnmLSsF2Xzhu4HQ=; b=af8pXwZpidkGXm9kWSrP/uYHH/KEjLIftvcUDni/88JydIbz8w93jv1JgsQb0N5N8k kUbOwdBI+tOsbMShip5fI7WenC7lMueEzqfrRbfshRJnSA9L/8kyH0AJ0G92YrcdwqBc ATtAau8wpmjXiLBAWJObjA10nOln6HvjlVXwpEGS9t4r6oDUOWWrfPDjpVjDKrkF2LY7 DmIKILvc3KahZPeMjXcMzpfeFLXltXXnUwagkrWAMOku+Lflc/nG0SrYM1Cps6hXLtF+ NGqbz4DMyNjizCes76oeDBRjofrtNtLSeubpMHEUerPcemkgqtxQ6Anf6AXeyuc3WkWF G0dA==
X-Gm-Message-State: AOAM532YgIyo0WdFE3xaehtOpj39dWa2Jt/Ltbl5rnCMs75fceefEEWP IZ9WbsYPCGyoBBNhhOB22oGr5gX0cIQM1R0xgCI=
X-Google-Smtp-Source: ABdhPJzz8ERZYmVO3LwznU+t8jVjA3z6sRGIEgG1qyXsapD3jwu+6QtLFQGQKGIeoEFO97feR/7zy48vxfg00/GP3cY=
X-Received: by 2002:ab0:770d:: with SMTP id z13mr13679891uaq.110.1610803328476;  Sat, 16 Jan 2021 05:22:08 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy>
In-Reply-To: <20210116034026.5C93F6AC0428@ary.qy>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 16 Jan 2021 08:21:57 -0500
Message-ID: <CAH48Zfybt8Ci2zjLPagcJcMJW7F38omnq=oBfCj316qzWn4N+g@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000326b1b05b90460d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/e4f7Aey_rFQlrpuK_18AdM3uZno>
Subject: Re: [dmarc-ietf] Forensic report loops are not a problem
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, 16 Jan 2021 13:22:11 -0000

--000000000000326b1b05b90460d2
Content-Type: text/plain; charset="UTF-8"

1) Because loop prevention is easily defined.
2) Because loop prevention is easier and simpler and less stressful to
implement than loop correction.
3) Because changing DNS to fix a loop is too slow.
4) Because a loop could be triggered by a malicious spammer, and the
feedback becomes backscatter.
5) Because DMARC reports are courtesy messages for the benefit of the
sender.   The sender has no significant interest in whether the message is
accepted or not.
6) Because loops cause congestion that affect other traffic
7) Because we have reports from the wild which indicate that loops have
actually occurred

Is that enough?

On Fri, Jan 15, 2021 at 10:40 PM John Levine <johnl@taugh.com> wrote:

> In article <CAL0qLwaZx97cztehz_o=
> cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> you write:
> >-=-=-=-=-=-
> >
> >How are implementers dealing with forensic report loops?
> >
> >Say I send a message from X to Y, whose DKIM signature fails.  Y sends me
> >back a forensic report, whose DKIM signature also fails.  X sends a
> >forensic report to Y, whose report fails, etc.  We need a way to break the
> >loop.
>
> If the reports are unaligned and their domain is requesting failure
> reports, sending reports about the failure is exactly the right thing
> to do.
>
> I still don't understand why anyone thinks there is a problem to be
> fixed. If you don't want reports, don't ask for them. If you think the
> mail you send shouldn't be provoking DMARC failure reports, adjust
> whatever is sending the mail the mail is aligned, or get rid of the
> ruf= that asks for the reports. What am I missing here?
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000326b1b05b90460d2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>1) Because loop prevention=C2=A0is easily defined.</d=
iv><div>2) Because loop prevention is easier and simpler and less stressful=
 to implement than loop correction.</div><div>3) Because changing DNS to fi=
x a loop is too slow.</div><div>4) Because a loop could be triggered by a m=
alicious spammer, and the feedback becomes backscatter.</div><div>5) Becaus=
e DMARC reports are courtesy messages for the benefit of the sender.=C2=A0 =
=C2=A0The sender has no significant interest in whether the message is acce=
pted or not.</div><div>6) Because loops cause congestion that affect other =
traffic</div><div>7) Because we have reports from the wild which indicate t=
hat loops have actually=C2=A0occurred</div><div><br></div><div>Is that enou=
gh?</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">On Fri, Jan 15, 2021 at 10:40 PM John Levine &lt;<a href=3D"mailto=
:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">In article &lt;CAL0qLwaZx97cztehz_o=3D<a h=
ref=3D"mailto:cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com" target=3D"_bla=
nk">cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com</a>&gt; you write:<br>
&gt;-=3D-=3D-=3D-=3D-=3D-<br>
&gt;<br>
&gt;How are implementers dealing with forensic report loops?<br>
&gt;<br>
&gt;Say I send a message from X to Y, whose DKIM signature fails.=C2=A0 Y s=
ends me<br>
&gt;back a forensic report, whose DKIM signature also fails.=C2=A0 X sends =
a<br>
&gt;forensic report to Y, whose report fails, etc.=C2=A0 We need a way to b=
reak the<br>
&gt;loop.<br>
<br>
If the reports are unaligned and their domain is requesting failure<br>
reports, sending reports about the failure is exactly the right thing<br>
to do.<br>
<br>
I still don&#39;t understand why anyone thinks there is a problem to be<br>
fixed. If you don&#39;t want reports, don&#39;t ask for them. If you think =
the<br>
mail you send shouldn&#39;t be provoking DMARC failure reports, adjust<br>
whatever is sending the mail the mail is aligned, or get rid of the<br>
ruf=3D that asks for the reports. What am I missing here?<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000326b1b05b90460d2--


From nobody Sat Jan 16 13:31:12 2021
Return-Path: <superuser@gmail.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 A46C73A19DE for <dmarc@ietfa.amsl.com>; Sat, 16 Jan 2021 13:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xVTZvhc1Mdyk for <dmarc@ietfa.amsl.com>; Sat, 16 Jan 2021 13:31:09 -0800 (PST)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48BBB3A19DD for <dmarc@ietf.org>; Sat, 16 Jan 2021 13:31:09 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id x4so7073285vsp.7 for <dmarc@ietf.org>; Sat, 16 Jan 2021 13:31:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wSXxu4PQUbsXFbPFQoXCAcn4OA+Xbyf0N3Gs59GAO2A=; b=WQBZKRNJYepFfdDlKrg2g+AC4i2dsGmSMHYSnFrxo9n+h4UX3o5HNnejF0GaMOjepm kYmkyKn4ekN7YA1aN7MUHH2HX9tAMWGu665MjBZtWRRkeZrYC+uJKtNzQqXDLM2k3k5z mjU/fYZPm9K+WeFr4J7AHCHsa6vP3YpvhRjxykHSAI/qLN1V2d0OkOWXPWYpEkFAAFaC dhGYP58KrSEmCfhEtSpEMZDj16r/AKeQS3uU/P1qqU27IqPHW5ffqp6L5yWEw21St0l6 pLeUYUW9xIGE6E5z66Cke7RGAf8/9YG50JGAjqhInCjZohu38HY7HQmcEJnzRhA7GAzO PdwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wSXxu4PQUbsXFbPFQoXCAcn4OA+Xbyf0N3Gs59GAO2A=; b=IIv2j8afaNYHFo797g7n426Eqm1838tcYJb9SId6kMMdlaueGor/FOWqHRhhPt0Cn6 sRyWyiipnRstuiRDbZH6kEj+U58tD2BLR6dlQ9hNZ3bwS6GYUbRlXjKB+qH6NrS/bK0I 2RwyU/i3aSys51KOE/UM56D7sis88+8TfpZVQjCHd0RWwhVtQUyfDVXc6dZFALo080qR 7oE1y3qOZB/78Sj2BB49JhFiCoqfXgR8H9SL1/9Tloj3iI3MaDizxEAvIYAjhgltIni8 d1yLuM3oT5PBFzNS91PjTzNbvO9i6UEYOKbv5A4LQ4Q5OFi9VMCDw6Fe5EOzAKQusmN3 x78g==
X-Gm-Message-State: AOAM533R7BVJsBzyh1XDjo+MzVRI4JXfoScyWpl/DCLfvDiFZQdtjxGt 8jsAAiG+d+XXyQ4z/Og7OCarVvxhb69nTBYShcFKnbkTnxE=
X-Google-Smtp-Source: ABdhPJzpaGskp8497Pzs+UrnRZ9Xv9u15YBwc868OPFeZ7kClbN7jmKdtJSuN/6nUef1oIrb9BNtB+linKgvFkCEPrY=
X-Received: by 2002:a05:6102:808:: with SMTP id g8mr9452059vsb.0.1610832668272;  Sat, 16 Jan 2021 13:31:08 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy>
In-Reply-To: <20210116034026.5C93F6AC0428@ary.qy>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sat, 16 Jan 2021 13:30:56 -0800
Message-ID: <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fc348c05b90b3416"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/FbU0iW_x11d4ZlddkmYxQdgDR1c>
Subject: Re: [dmarc-ietf] Forensic report loops are not a problem
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, 16 Jan 2021 21:31:11 -0000

--000000000000fc348c05b90b3416
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 15, 2021 at 7:40 PM John Levine <johnl@taugh.com> wrote:

> I still don't understand why anyone thinks there is a problem to be
> fixed. If you don't want reports, don't ask for them. If you think the
> mail you send shouldn't be provoking DMARC failure reports, adjust
> whatever is sending the mail the mail is aligned, or get rid of the
> ruf= that asks for the reports. What am I missing here?
>

You might be right, so I'll go back and ask this use case what the
specifics are.

What I'm concerned about is that since this has come up before N times
(for, admittedly, some currently small value of N), we've seen enough
disparate cases of it that we may be missing something bigger, and if so,
doing something defensive in the specification would be prudent.  There's
smoke here, and there may be fire.

Will report back.

-MSK

--000000000000fc348c05b90b3416
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 15, 2021 at 7:40 PM John Levi=
ne &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:<br=
></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">I still don&#39;t understand why anyone thinks there is a proble=
m to be<br>
fixed. If you don&#39;t want reports, don&#39;t ask for them. If you think =
the<br>
mail you send shouldn&#39;t be provoking DMARC failure reports, adjust<br>
whatever is sending the mail the mail is aligned, or get rid of the<br>
ruf=3D that asks for the reports. What am I missing here?<br></blockquote><=
div><br></div>You might be right, so I&#39;ll go back and ask this use case=
 what the specifics are.</div><div class=3D"gmail_quote"><br></div><div cla=
ss=3D"gmail_quote">What I&#39;m concerned about is that since this has come=
 up before N times (for, admittedly, some currently small value of N), we&#=
39;ve seen enough disparate cases of it that we may be missing something bi=
gger, and if so, doing something defensive in the specification would be pr=
udent.=C2=A0 There&#39;s smoke here, and there may be fire.</div><div class=
=3D"gmail_quote"><br></div><div class=3D"gmail_quote">Will report back.</di=
v><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">-MSK<br><=
/div></div>

--000000000000fc348c05b90b3416--


From nobody Sat Jan 16 14:20:30 2021
Return-Path: <johnl@taugh.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 7ED143A19F4 for <dmarc@ietfa.amsl.com>; Sat, 16 Jan 2021 14:20:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=cAGi1Ejb; dkim=pass (2048-bit key) header.d=taugh.com header.b=jXGcgGb3
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 fIYtH_VCTMkF for <dmarc@ietfa.amsl.com>; Sat, 16 Jan 2021 14:20:25 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 66C413A19F3 for <dmarc@ietf.org>; Sat, 16 Jan 2021 14:20:24 -0800 (PST)
Received: (qmail 70202 invoked from network); 16 Jan 2021 22:20:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=11238.600366a4.k2101; bh=Zgcbv9j8/xHDavVrCaz6xQFwicBvB5KYFbcYLXbRfOE=; b=cAGi1EjbETPwGkwl0anO17E3cu0P/Cs7vzGRZZTCjO47h8ttOItgL4vs0PluaoToIfNPS0vdfixPcUCHB9p+ZsS8ki8WIgtb0Quwzv5QPhsRzVLic3/spjnT6CeXJXw/J8HARyYiXMT7uz2m/VVYK9A6mc1t9Kq0s16YkWgM5ce+4cf9bf2KTNFRSGhV70Cm8F9r5BikoWLAS3501LGJIXxopKu9JfkuEn2w4PXIaKMy0+KWOI7sNN0eAQLvAaHVAiTzi5f73+eArmji8u9BMk50lk7SKK49NVRJM+eZvxzkGLOMrEDUAra+GrntZzn3qmKsIcENKnZf1l3ZKdRlAA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=11238.600366a4.k2101; bh=Zgcbv9j8/xHDavVrCaz6xQFwicBvB5KYFbcYLXbRfOE=; b=jXGcgGb3J07hfiDF20w1YIukGzPgQZfdAhUuHNxQRsF2YxjvIUn3cuGnqGSJmN2ctVCqqwtKW4NxtH0wvEXzooeGeHjsfL+N3aIQUixYSlb30SD6kWSYL0eJtwkFqjnX9/bnxno4Xt/8iMSfYOJmyhdQvmaAqKchRewHwFk9aiN09vM2T55ocR3n54d2AhOyWkP3xWIZZJnSD5H02QayK2Sg7r2r+Z3ffYbGTGlfMW8CVtY+zZVseD6DZhjXNvZ67KFvNY9Mn29Tsm+JphXFNZUbiY3AYKenPXeooZI8fhlolHufG+iVilPK5+s83i5HZnIwLmJORYkKiNuTfWiNXg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 16 Jan 2021 22:20:19 -0000
Received: by ary.qy (Postfix, from userid 501) id 7B1F46AEDD4B; Sat, 16 Jan 2021 17:20:19 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 7020C6AEDD4A; Sat, 16 Jan 2021 17:20:19 -0500 (EST)
Date: 16 Jan 2021 17:20:19 -0500
Message-ID: <3d6db975-4d52-94f0-5ca0-213234d53773@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "IETF DMARC WG" <dmarc@ietf.org>
In-Reply-To: <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy> <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/lrd9Z2jdoVT-lJODDWM8z6jXQ3w>
Subject: Re: [dmarc-ietf] Forensic report loops are not a problem
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, 16 Jan 2021 22:20:28 -0000

> What I'm concerned about is that since this has come up before N times
> (for, admittedly, some currently small value of N), we've seen enough
> disparate cases of it that we may be missing something bigger, and if so,
> doing something defensive in the specification would be prudent.  There's
> smoke here, and there may be fire.

OK, thanks.

My guess is that if we can track it down it is likely to be "my software 
is buggy so I want everyone else to work around it."

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Sun Jan 17 03:00:11 2021
Return-Path: <johnl@taugh.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 94F7E3A0F44 for <dmarc@ietfa.amsl.com>; Sun, 17 Jan 2021 03:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 0dDUyYYxzzyb for <dmarc@ietfa.amsl.com>; Sun, 17 Jan 2021 03:00:08 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 0D1283A0F3A for <dmarc@ietf.org>; Sun, 17 Jan 2021 03:00:07 -0800 (PST)
Received: (qmail 94134 invoked by uid 100); 17 Jan 2021 11:00:06 -0000
Date: 17 Jan 2021 10:59:42 -0000
Message-ID: <20210117105942.94113.qmail@submit.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Zr2HjLWQWFN4zHnSFDU6_3XCDWE>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jan 17 06:00:06 2021
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, 17 Jan 2021 11:00:10 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
  5 (29.4%) |  41559 (34.3%) | Murray S. Kucherawy <superuser@gmail.com>
  4 (23.5%) |  18600 (15.3%) | John Levine <johnl@taugh.com>
  2 (11.8%) |  18171 (15.0%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  2 (11.8%) |  17050 (14.1%) | Дилян Палаузов <dilyan.palauzov@aegee.org>
  1 ( 5.9%) |   8102 ( 6.7%) | Kurt Andersen (b) <kboth@drkurt.com>
  1 ( 5.9%) |   6703 ( 5.5%) | Steven M Jones <smj@crash.com>
  1 ( 5.9%) |   6024 ( 5.0%) | Juri Haberland <juri@sapienti-sat.org>
  1 ( 5.9%) |   4980 ( 4.1%) | Alessandro Vesely <vesely@tana.it>


From nobody Sun Jan 17 09:19:25 2021
Return-Path: <juri@sapienti-sat.org>
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 83F443A12A6 for <dmarc@ietfa.amsl.com>; Sun, 17 Jan 2021 09:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 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.262, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sapienti-sat.org
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 dAPMkghKUv-U for <dmarc@ietfa.amsl.com>; Sun, 17 Jan 2021 09:19:22 -0800 (PST)
Received: from batleth.sapienti-sat.org (batleth.sapienti-sat.org [IPv6:2a01:4f8:221:43c5::2]) (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 016A03A12A3 for <dmarc@ietf.org>; Sun, 17 Jan 2021 09:19:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sapienti-sat.org; h=content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:to:subject:subject; s= dkim20170413; t=1610903958; bh=r8VhK0MEX4Ca85Gz1/4UI2XMVA4BOM/cA XqX8pfw4xM=; b=ehULrDQHLEYTwwIieWYEbzcb8zt+U3a8u0v9awTMfCIt5QRMP FDXX5XuvGKAuEiPp+vNOKvKyvl6UocgpBRBqX9HpmQC3Ew0pSBQq9qaug2b59KWg /Ya/ACsTNOS27ORaWcJksFu9VN1eDC/LpowsCcEw7We1zZcHq9gZquKrQS7Y9A4h uKUO5cvFm1Ea59XhVqm1PnKz/8Lx6kiZBjtMsOhbECTpKRF8B2Q/esmfmH02PPbE /EmQJUdoHrX1Y9Re/tEY/yUfsOTOd4lttgYG1g8zIMX4Cscnc4P7ahPtvVDJKh+h 0EpkJOmOxqp6C3k6kzSkkq1mI8nZKXtHUrNbw==
X-Virus-Scanned: Debian amavisd-new at sapienti-sat.org
Received: from [IPv6:2001:470:6d:e38::21] (stargazer.home.sapienti-sat.org [IPv6:2001:470:6d:e38::21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: juri@sapienti-sat.org) by batleth.sapienti-sat.org (Postfix) with ESMTPSA id 5782633E13BA for <dmarc@ietf.org>; Sun, 17 Jan 2021 18:19:18 +0100 (CET)
To: dmarc@ietf.org
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy> <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com> <3d6db975-4d52-94f0-5ca0-213234d53773@taugh.com>
From: Juri Haberland <juri@sapienti-sat.org>
Autocrypt: addr=juri@sapienti-sat.org; prefer-encrypt=mutual; keydata= mQGiBEpkkU0RBACvs80AZxmG2dlbE8uFuRtWaGbvdlTKzwn4s37Sc98yNzDr57btydCdasf8 OvctyUrngCuC/JmBDw9MpNVVRJ2lLOSi7r5JgjXSbpeW95UKUnQk2m/+nRkNPrKY0FXhP4VE 04lmV3vb0cKpi3Iuceuc4U/PkwlbfzvMCqMJp/zGGwCgqnxsnNu+MOEPB1zum0pT1ZmZptEE AJkzjTYdnt4zarO0K8Yk9BMy39puGMuW6HD4MiN1DfkqH9RYe7qh6L8DasmSed/TlVNpsH+y fdhwD/9f+8Ifc1vpFjgcm9mEmJqyjpQTKG9oQE1KpcnHXKwG/Gr/lXrQbgiiungc+d18tafN yAKQfmkKIDqFVmKPjlOJHWYN7qlKA/0R3/6RyerO84hsLt6jFWeOm/9KEh6WfnoooDQhAq7M sFjCNUoF32x/hpabB9MqF6vcl/Ka8Dmdj95Ae10K9MD5L7TNaWkL7FepFptcCkHonLQQM4E2 vDAJtyyKUaQiOPw80oEOMISXzQD78Vbg6Q9nmsmkpuSAUVTqUksTTwtnNrQmSnVyaSBIYWJl cmxhbmQgPGp1cmlAc2FwaWVudGktc2F0Lm9yZz6IYAQTEQIAIAUCSmSRTQIbAwYLCQgHAwIE FQIIAwQWAgMBAh4BAheAAAoJED9MVq+NNYZCRlAAn38ddF0pjwOZR0VyoIe4UpfpZV5fAKCO o87TVyYoBYwru4hunuVMOpXgG7kCDQRKZJFTEAgAoBRVOPPgl3foNLJn+C8QnuExrwKdeguE 5l2lSw3Fummo9CQCN72gYrqMNksFeIcoWAWclm/8bA551KWum8g2TjTA7NuVdIvzahr8MFGi oBNktr1GLAJ2SNpzyUA3fICIJqXdUdlvnjk4olQE6ACylbxDT+2x5HVzvhxw1fvz4c4JRvnP J1q2/LMu6sgBta6cgVTzYzBvxf1JyjbHsFKZSJZ+3JO3AO5y40XbU+EZVT60ChbU8GCJEVer 2RFlYfYSdniSxgQPuYVxZsfXgQlv0xQ3QTTDLU9jpJJX4EfwfWaio01X3l8QqIBtVpu07ZXI klOJk1QXC3HDIhAt/uGdVwAEDQgAmK0fEhrg/HY2Zs2VXIkWViS8I68sAw/GRGAsif0pkHTx dQ2oEZYMK1bNW7VFBphby554hUAmvwcCCUso0INqiw0sXs6ZARL3nT6QPc3uU0jMFpg1cWHf yElUopAR0S0kxVfShE3fNKOnizTPcRboCLOVZzuM1BxVO55Dkc9fPX1zik9hzJjbG4bzEqNG cg7+EY0YqeEVFccyRXsjvFRTl4ckvCMhsyqGwE8AnwFOYJXqfbLjEDSBngblniWTEjZ47t5p rN6sri7+sWIUaybzdINKGZMijndTVccMtRvbbx62+0dRoxUV2GIrNcCOvQ7e5Q4/vL8okoK9 MZMUWQnUeYhJBBgRAgAJBQJKZJFTAhsMAAoJED9MVq+NNYZCX74An2lQsova+seE0su7vK2y GGyRrnQdAJ9nvrSrslx2qcHkRycgYoFozVkRsw==
Message-ID: <fe31989b-07a0-56fe-af6d-737182d3077e@sapienti-sat.org>
Date: Sun, 17 Jan 2021 18:19:17 +0100
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: <3d6db975-4d52-94f0-5ca0-213234d53773@taugh.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jvHui5jZaM3MVIQ74gf-JucdFlw>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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, 17 Jan 2021 17:19:24 -0000

On 16/01/2021 23:20, John R Levine wrote:
>> What I'm concerned about is that since this has come up before N times
>> (for, admittedly, some currently small value of N), we've seen enough
>> disparate cases of it that we may be missing something bigger, and if so,
>> doing something defensive in the specification would be prudent.  There's
>> smoke here, and there may be fire.
> 
> OK, thanks.
> 
> My guess is that if we can track it down it is likely to be "my software 
> is buggy so I want everyone else to work around it."

The cases that I had to deal with were misconfigurations on the other
side. I had to put these senders on some kind of ignore list to not send
out failure reports for their failing messages. That stopped the loop.

Regards,
  Juri


From nobody Sun Jan 17 13:27:01 2021
Return-Path: <johnl@iecc.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 7BCEA3A084A for <dmarc@ietfa.amsl.com>; Sun, 17 Jan 2021 13:26:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=LjhdMpdL; dkim=pass (2048-bit key) header.d=taugh.com header.b=yX6bUHBc
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 2ZzMq3RHhdU4 for <dmarc@ietfa.amsl.com>; Sun, 17 Jan 2021 13:26:58 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 ED44D3A083E for <dmarc@ietf.org>; Sun, 17 Jan 2021 13:26:57 -0800 (PST)
Received: (qmail 81201 invoked from network); 17 Jan 2021 21:26:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=13d2e.6004ab9e.k2101; bh=VaN0a6QiMIA1qf3wkd+L7Dl+hNniyyYwOE/MRjd63Qc=; b=LjhdMpdLS8sxChsjEJnxaB4sgr3hY6xIm9cRbBM50a4rjUsoycbD2FvYMk9zSRW+Yc1k3i8/JczSlBgqcSK7KDa/Glv0QmkSV4BogylRTx5d85nQ9uspFeReyJaNrggbMRSWKOOjKr11NaTxKfQgTYTMFDxfga3uiJmIXYa6pvQEfQGHqOqqcXh6giX8dqeUy14j/rIy45MIWY5FWjgDEOjg2Bg7ixbdJewXaK4NBDCQen5PrcfMTiUgB4cammHh6VzvP/NFzq//0cE7O9pCgmgCSX6OpUewpxOhueRMv6fXG7g2XVRPaoVJl3MlCA2ihXIdwWYnxJXfuTB7bFGYXQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=13d2e.6004ab9e.k2101; bh=VaN0a6QiMIA1qf3wkd+L7Dl+hNniyyYwOE/MRjd63Qc=; b=yX6bUHBcBXM3t+m0UT0iHf5NwhfSHtxH65xtmwt7nFLth34RFAYbwbkL21sr1AHVkayx6gUWd+/f35qkNVPKtNbPmTooyrI7WlzDeWxkGaZuefGVwZx1ixJLuANkxeY538xI8QHXh4a6M1+nQtzOZFE50zjYW9qED/3Su4ZPgge/v+BOJT8/ViNneLu1eN4Ub4AiDdTdTGpeVkUD8cngkDOc0G+eAzllsfua0JwtydanwBwcaeLux/kyfPMT9rmxy3Wpl4e8rmV2M1Z9+Qsvttq9vgqine56vkA747rnBLHXVswju/7eT+1KNPFWfMjYt2c4Zn1ZqEPnY52itBw+/w==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 17 Jan 2021 21:26:54 -0000
Received: by ary.qy (Postfix, from userid 501) id E605B6B22FF9; Sun, 17 Jan 2021 16:26:53 -0500 (EST)
Date: 17 Jan 2021 16:26:53 -0500
Message-Id: <20210117212653.E605B6B22FF9@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: juri@sapienti-sat.org
In-Reply-To: <fe31989b-07a0-56fe-af6d-737182d3077e@sapienti-sat.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/EJDY90x9-7Ru3-UXMlxGxpQTYQw>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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, 17 Jan 2021 21:27:00 -0000

In article <fe31989b-07a0-56fe-af6d-737182d3077e@sapienti-sat.org> you write:
>> My guess is that if we can track it down it is likely to be "my software 
>> is buggy so I want everyone else to work around it."
>
>The cases that I had to deal with were misconfigurations on the other
>side. I had to put these senders on some kind of ignore list to not send
>out failure reports for their failing messages. That stopped the loop.

I believe you, but did the fail loop cause a significant load on your
system, or were they just ugly?

As I've said before, if they're sending unaligned mail and have an
ruf= to ask for reports, I'd think it fair to assume they'd want the
reports.

R's,
John


From nobody Mon Jan 18 04:09:22 2021
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 F2EB13A12BB for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 04:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 MfSBY4uJDAjn for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 04:09:19 -0800 (PST)
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 972563A12B6 for <dmarc@ietf.org>; Mon, 18 Jan 2021 04:09:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1610971756; bh=MJGDWEeBzEM9a7Rj0Le41gxF17BCa3Qa8MLn0FgpEX4=; l=1249; h=To:References:From:Date:In-Reply-To; b=DKXRSAf+aMMu1xu5CcLEc2LPBUQm6eAwZDg9k0DDIIf3Z18k0tT5TIO11Y67+J00K beBiMfDdBaVFm/giMMtKnqQWcSptVc0aH/lF7iTSmBJTml09/QbZJQIxBcgfq2/9iI 1mKTp1ovq/EbUClZNGYnpprgAaV1HdaWYQvPcsL4S2gFwAmeGbJKWl07+Ec5a
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC07E.0000000060057A6B.000054BB; Mon, 18 Jan 2021 13:09:15 +0100
To: John Levine <johnl@taugh.com>, dmarc-ietf <dmarc@ietf.org>
References: <20210117213536.165266B2315E@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <8b8b3304-80f5-7287-aee8-e86ff72dcd31@tana.it>
Date: Mon, 18 Jan 2021 13:09:15 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210117213536.165266B2315E@ary.qy>
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/DrdyndYBfrGnZLop3vh-eSQg-is>
Subject: [dmarc-ietf] A policy weaker than quarantine, yet better than none
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, 18 Jan 2021 12:09:21 -0000

On Sun 17/Jan/2021 22:35:36 +0100 John Levine wrote:
> If I wanted, I could send a dozen replies to this list faking the addresses
> of previous senders saying that your suggestion is brilliant, or not.

And we tolerate this security hole because...?


On Tue 15/Dec/2020 10:50:10 +0100 I wrote:
> I wish there was an intermediate policy, call it p=mlm-validate, that 
> directs [an intermediate forwarder such as a mailing list] to reject if not
> authenticated, while final recipients can accept it as if p=none.

At least, we could specify in the General Record Format that unrecognized 
policies should be treated as p=none.  Currently, this is subject to the 
existence of a rua= tag.  In Policy Discovery, we have:


    6.  If a retrieved policy record does not contain a valid "p" tag, or
        contains an "sp" tag that is not valid, then:

        1.  if a "rua" tag is present and contains at least one
            syntactically valid reporting URI, the Mail Receiver SHOULD
            act as if a record containing a valid "v" tag and "p=none"
            was retrieved, and continue processing;

        2.  otherwise, the Mail Receiver applies no DMARC processing to
            this message.

(Such optimization should be inferred by the implementation, no?)


Best
Ale
-- 
















From nobody Mon Jan 18 09:54:21 2021
Return-Path: <johnl@taugh.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 3E9833A0B83 for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 09:54:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=P/FaUOnt; dkim=pass (2048-bit key) header.d=taugh.com header.b=h5FbXaMv
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 o3GNO3xOhAJB for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 09:54:17 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 30FDC3A0B60 for <dmarc@ietf.org>; Mon, 18 Jan 2021 09:54:16 -0800 (PST)
Received: (qmail 93350 invoked from network); 18 Jan 2021 17:54:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=16ca1.6005cb47.k2101; bh=YIIIH/eAon+61fImgWl1WBuiJLXt/Xwr4g2vYalczvA=; b=P/FaUOntAowD2bjazuEv+jni3bQdQYn6bmYmlbMNQx2CA+MZKyUWzu87QTGlQRxBr5cDLSQTKpvrTfKgwUC2AZzI5mhO4TbKBWQgT8Uic9MTjvsvyDjtmRXbzNY6F12jjm7elvj8mDOSAphq1TLHDj/dhS8l+7M2Z/S1m057YRIPjio2E8tFngkTBA8GWnc/TBNSKKw98iESiRTuTrOKDeWIOcIBmUAVQgl41LkVeqnI3vgHNKpk978GdJNWh7M7++EdOyqXts2rvbbtewtjhhuWLdVpOcWIWq+Jr7NMHeNQf15mDXE0+I4dctM7h7VzgvHyLwdcfX2fX6AwqP8rjw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=16ca1.6005cb47.k2101; bh=YIIIH/eAon+61fImgWl1WBuiJLXt/Xwr4g2vYalczvA=; b=h5FbXaMv39QrVNx51wgfa1h1iQqvnLhK2sVLDQMJreKqjOioS0AJk4NHiKEq+ND3htNVBT56R7Ms4tJUfvcdmc2PuEQNucRCu4IphWy/z4aFmiZV+qB0gowuOiIhE30mXDMCOtAVN2xVml3vB0n3tzbbfMb23aRyOkDwBH0cIOmmILwIWZO6ROMPjD2YxQeUi4s6MfeOXJmdxkeyFUlk+0xEomruko/+NOBOWy/kgjtaOUOxhRZsW7OjhPOvRF20yLxt0HBO4xI49FeHdWMMYpcbV0T7ek0vV8qmj21ZPz/zzYRl8hW3ItrjwMJ4eTleV5K0jzg3iyGOC9/XhXZ4DQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 18 Jan 2021 17:54:15 -0000
Received: by ary.qy (Postfix, from userid 501) id 34C866B4E3C5; Mon, 18 Jan 2021 12:54:15 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 2B84B6B4E3C4; Mon, 18 Jan 2021 12:54:15 -0500 (EST)
Date: 18 Jan 2021 12:54:15 -0500
Message-ID: <7e5b91cc-8ca8-6f7f-4c3e-83e13a85c61d@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, "dmarc-ietf" <dmarc@ietf.org>
In-Reply-To: <8b8b3304-80f5-7287-aee8-e86ff72dcd31@tana.it>
References: <20210117213536.165266B2315E@ary.qy> <8b8b3304-80f5-7287-aee8-e86ff72dcd31@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/JWhuQk9tQkAXwtl0asV3nLxz20I>
Subject: Re: [dmarc-ietf] A policy weaker than quarantine, yet better than none
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, 18 Jan 2021 17:54:19 -0000

On Mon, 18 Jan 2021, Alessandro Vesely wrote:
> On Sun 17/Jan/2021 22:35:36 +0100 John Levine wrote:
>> If I wanted, I could send a dozen replies to this list faking the addresses
>> of previous senders saying that your suggestion is brilliant, or not.
>
> And we tolerate this security hole because...?

Because it is not a problem worth solving in practice.  Mailing lists have 
all sorts of ways to validate submissions beyond looking at the From 
header, ranging from sender challenges to S/MIME signatures.  No list I 
know of turns them on.

> At least, we could specify in the General Record Format that unrecognized 
> policies should be treated as p=none.

Absolutely not.  Any DMARC record with an invalid p= is just broken.  We 
write standards that say how to interoperate, not how to guess what other 
people had in mind when they implemented it wrong.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Mon Jan 18 10:48:32 2021
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 A6EDB3A0C55 for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 10:48:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 PmAXwwtJ41Je for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 10:48:29 -0800 (PST)
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 D7CD53A0C56 for <dmarc@ietf.org>; Mon, 18 Jan 2021 10:48:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1610995706; bh=jXo4qvntUJIf+3Xk5chPqasizHOBb+32qACpFDfzBgs=; l=775; h=To:References:From:Date:In-Reply-To; b=C61d8eyfTkqla4HUOvU+iMTscCRs32qV0wl4m13Tg9bpm4FBr5XzVxT1WiCtN2IxR yiADClEmBWAA6E8wzD7SQ7/gV3bPgKzeUmP5ZdwigBQaR9R6fNI51LeapnEAGe5BNo YgXpXnRrZ5leYBffzcv69jMi2xUh2h/xcekuXtQMCw7g01QjSKlVGYGEPkDIO
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC056.000000006005D7FA.000001ED; Mon, 18 Jan 2021 19:48:26 +0100
To: John R Levine <johnl@taugh.com>, dmarc-ietf <dmarc@ietf.org>
References: <20210117213536.165266B2315E@ary.qy> <8b8b3304-80f5-7287-aee8-e86ff72dcd31@tana.it> <7e5b91cc-8ca8-6f7f-4c3e-83e13a85c61d@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <fad5eb1c-8cea-e061-fb57-a7e5538d281a@tana.it>
Date: Mon, 18 Jan 2021 19:48:25 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <7e5b91cc-8ca8-6f7f-4c3e-83e13a85c61d@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/P70mQusMdvx0ICdquTZN2Z6Bj34>
Subject: Re: [dmarc-ietf] A policy weaker than quarantine, yet better than none
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, 18 Jan 2021 18:48:31 -0000

On Mon 18/Jan/2021 18:54:15 +0100 John R Levine wrote:
> On Mon, 18 Jan 2021, Alessandro Vesely wrote:
> 
>> At least, we could specify in the General Record Format that unrecognized 
>> policies should be treated as p=none.
> 
> Absolutely not.  Any DMARC record with an invalid p= is just broken.  We write 
> standards that say how to interoperate, not how to guess what other people had 
> in mind when they implemented it wrong.


Right, but IF one day we introduce a new policy, we'll have to be compatible 
with installed base.  Please don't reply that we'll NEVER introduce new policies...

BTW, the current spec does not mean that an invalid p= implies the DMARC record 
is broken.  If it did, it wouldn't say to check rua= in that case.


Best
Ale
-- 
















From nobody Mon Jan 18 10:56:27 2021
Return-Path: <johnl@taugh.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 BF0443A0C62 for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 10:56:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=evkpWIzG; dkim=pass (2048-bit key) header.d=taugh.com header.b=0U2AKjdy
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 oN0krYM6QmyZ for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 10:56:24 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 045453A0C61 for <dmarc@ietf.org>; Mon, 18 Jan 2021 10:56:23 -0800 (PST)
Received: (qmail 12770 invoked from network); 18 Jan 2021 18:56:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=31e0.6005d9d6.k2101; bh=dM/3xkKUaNK0U9fwoMnggH4LwJJL5V4M4PeF9vEq2sY=; b=evkpWIzGh+BDhGxg/OqnxVnTkLSI0GVfM6ZVkwH/1oq8/q2Kj7q1DtJMAOQ4X9Wk27P9FooIp7jx1SYAgw5nYprci/nNDjtWSBtFIvMuGkmc/bh7fZ7lN02vWv0YES8dX2q9NZu7CnasUrx00mkSh/ienposojdDNTSiJJaFbU7rRIXv71Vwd2nMEHT4BJADpRfXbNuzSDKcjoQRzKjfWxKus+pTW+Th3x3t9pn9oohz0hRhp8Or75CEnoIQDLCsniKOIkTUHhYOyxlSbWeskUUwU4yJNMVIgs4yFyok4fipvJaurrkcSsUKhuKePrEMnFl3Jg+PNZ6cwQWTY459Yg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=31e0.6005d9d6.k2101; bh=dM/3xkKUaNK0U9fwoMnggH4LwJJL5V4M4PeF9vEq2sY=; b=0U2AKjdyFyr5AHpePFV/khnCd6TLOatEmhJQEyT/OqPwVcNuHhK0FOiSrZmQ4p2Gmaqz38HdSKIeTP7TnXynVZgF+Z+SSsLgvNk2PkRKt8qXTR528IOiGfjQfNzAxqPi6pzpcSY+eFSEOseAdfgIgvVo4cQ0+D8K9tEMf+jPii9gva+cpEeKJTYIK9ChHqr1Vccxe1Xc+w7fxEWYus/WY4E2/x+XsteiI4VGml0Vz7Em15gQBTMmqyOfNS307R7ozl1tM/W7GLnHZ8+Gu0pqTi41i2DS05FZXYwi78E5WSS6yFA3juUFN9/FePIgv3aSjTXlw/FZ8rugkkwr3t1/6A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 18 Jan 2021 18:56:22 -0000
Received: by ary.qy (Postfix, from userid 501) id 234BC6B50127; Mon, 18 Jan 2021 13:56:22 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 1E2A96B50126; Mon, 18 Jan 2021 13:56:22 -0500 (EST)
Date: 18 Jan 2021 13:56:21 -0500
Message-ID: <128070e1-25e2-ed76-e4cb-a54ef746b02@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, "dmarc-ietf" <dmarc@ietf.org>
In-Reply-To: <fad5eb1c-8cea-e061-fb57-a7e5538d281a@tana.it>
References: <20210117213536.165266B2315E@ary.qy> <8b8b3304-80f5-7287-aee8-e86ff72dcd31@tana.it> <7e5b91cc-8ca8-6f7f-4c3e-83e13a85c61d@taugh.com> <fad5eb1c-8cea-e061-fb57-a7e5538d281a@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wbNb4UG8xWA4f0f3nami_yD9Hlc>
Subject: Re: [dmarc-ietf] A policy weaker than quarantine, yet better than none
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, 18 Jan 2021 18:56:26 -0000

> On Mon 18/Jan/2021 18:54:15 +0100 John R Levine wrote:
> Right, but IF one day we introduce a new policy, we'll have to be compatible 
> with installed base.  Please don't reply that we'll NEVER introduce new 
> policies...

It seems unlikely enough that I don't see any reason to worry about it 
until it happens.

> BTW, the current spec does not mean that an invalid p= implies the DMARC 
> record is broken.  If it did, it wouldn't say to check rua= in that case.

I know.  It would have been better if it didn't say that, but it's too 
late to change it now.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Mon Jan 18 11:14:42 2021
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 ABA103A0100 for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 11:14:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 Xld5waiYsf9A for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 11:14:39 -0800 (PST)
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 7B9DD3A00F7 for <dmarc@ietf.org>; Mon, 18 Jan 2021 11:14:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1610997277; bh=qundZLjsMMCaqPHdhrNeM5CQ9YU22uO9S+G/NyNoRzI=; l=645; h=To:References:From:Date:In-Reply-To; b=B3A7LJ2eUVcD552iPNxNr2zdJn27FV6jz06X5ZpWETH1z6LcQ+cNhJC8ls+fkrP9F rXPPsCRvML7oR9/3V8VipP8LqHiWvNdrVjfq58lk8GqpXUzakyCOuaeG/gn0wSFLvv aoE7yy8fZqVPovFDUhpBNJuU7o8yR301zPZBpgBEZRarOKEBmwaX7sglVCs1N
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [192.168.1.132] ([93.37.83.242]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC0C6.000000006005DE1D.000004E0; Mon, 18 Jan 2021 20:14:37 +0100
To: John R Levine <johnl@taugh.com>, dmarc-ietf <dmarc@ietf.org>
References: <20210117213536.165266B2315E@ary.qy> <8b8b3304-80f5-7287-aee8-e86ff72dcd31@tana.it> <7e5b91cc-8ca8-6f7f-4c3e-83e13a85c61d@taugh.com> <fad5eb1c-8cea-e061-fb57-a7e5538d281a@tana.it> <128070e1-25e2-ed76-e4cb-a54ef746b02@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <7a13ec60-8d17-0d80-2f55-a5a262689897@tana.it>
Date: Mon, 18 Jan 2021 20:14:32 +0100
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: <128070e1-25e2-ed76-e4cb-a54ef746b02@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4Q60R-Gv5qAsi3KMVuoGQIghOk8>
Subject: Re: [dmarc-ietf] A policy weaker than quarantine, yet better than none
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, 18 Jan 2021 19:14:41 -0000

On Mon 18/Jan/2021 19:56:21 +0100 John Levine wrote:

> 
>> BTW, the current spec does not mean that an invalid p= implies the 
>> DMARC record is broken.  If it did, it wouldn't say to check rua= in 
>> that case.
> 
> I know.  It would have been better if it didn't say that, but it's too 
> late to change it now.


I don't understand why you say it's too late.  This is not emailcore, 
and we don't risk getting back to proposed standard if we change too much.

We're just writing a proposed standard.  When choosing between a 
better spec and sticking to the existing one what criteria are we 
complying with?


Best
Ale
-- 













From nobody Mon Jan 18 11:17:50 2021
Return-Path: <dotzero@gmail.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 DFD223A0332 for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 11:17:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VKbysinqxeQ6 for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 11:17:46 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B3EF3A0317 for <dmarc@ietf.org>; Mon, 18 Jan 2021 11:17:46 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id e17so2921255qto.3 for <dmarc@ietf.org>; Mon, 18 Jan 2021 11:17:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/QvTkP1ryUslwrbq4ZSNS+dcLDhX+ujU8d/jYorVoHo=; b=eCVEoyoqfdVsiyOKQp9P93V/UT1CFpwC/euR5STx3WYXtdTOYrBs3uhoUUoAFtew1P yHzlNqla6JkU1sTUFd+bM3nul6+bc/WZP5g10xt3gW2eBwSBAQzBDZUnnnZrl/+mo+98 ZKhxQGTcPRoC8ddKW0IQy9F43NhGzHEsBZgNvT/OaD2ee10Bqobr72x7onJvweW5iDKV 7I0VStdArb4Ms8jXp73bxIrYBj3hahmj40bxktiVnMzeUN2+Frl0rGNUdvIXDOG3+ezY Uz/DNPoit8IA2bM5+kUIgQ3jfv0Fiv2H3inwFmZxOspv2fYKEs55o046uLRcOcqHgC/V Dwdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/QvTkP1ryUslwrbq4ZSNS+dcLDhX+ujU8d/jYorVoHo=; b=MULiskKn+9/DqcY9dJi8WsJJVnkGk9i7UY7tRWpVpSLDMSPSbz6dVH01Nrck/FsgAR 7Yy6UHohIMJr8wVlbeDdSXeArmN5Xj2sPwhpbRbXjAQJrXocbsfPhCPs1cYfNqIj6P1s CuuhlpRU5t0SxU0ReE0QkydRvD8jjJCYzOdEAPzgs0kMVCKTwpiKlckxuA9m7Gm0dKPu w55wjjy5zCNy3nITNf3RtGmhZ6/+uhQhXnmL/ExJ9k95CFbc/nkc/faix7wyU3KfsNK4 VsQpH6NXgASCGiGPpRkyJ/hfCvit6FdUfRBiJx//RpOvPO5gFK5lRiYy36Nof0h5Geu4 EfhQ==
X-Gm-Message-State: AOAM530sxvQaNzEWoFgMc26LB1wIZW7xdaZ/1Jv5o1UP1qbpy3PhEFUd AWbF/RFEvMTeZhgu7mV4YzoNQqEUr0YwGlcoK7c=
X-Google-Smtp-Source: ABdhPJw4nyaa46zCeWBK66kSuNYiQWkw1qY/PRo+dZtB/ueBrY9MlABLrRpOAz/kHqB0r10+DpQAWbc3/qU8Hdia1dM=
X-Received: by 2002:ac8:67ca:: with SMTP id r10mr1034233qtp.267.1610997462388;  Mon, 18 Jan 2021 11:17:42 -0800 (PST)
MIME-Version: 1.0
References: <20210117213536.165266B2315E@ary.qy> <8b8b3304-80f5-7287-aee8-e86ff72dcd31@tana.it> <7e5b91cc-8ca8-6f7f-4c3e-83e13a85c61d@taugh.com> <fad5eb1c-8cea-e061-fb57-a7e5538d281a@tana.it> <128070e1-25e2-ed76-e4cb-a54ef746b02@taugh.com> <7a13ec60-8d17-0d80-2f55-a5a262689897@tana.it>
In-Reply-To: <7a13ec60-8d17-0d80-2f55-a5a262689897@tana.it>
From: Dotzero <dotzero@gmail.com>
Date: Mon, 18 Jan 2021 14:17:31 -0500
Message-ID: <CAJ4XoYfvRQ2KguDBsfWGqHH3-hKYBi9vCf=n6Afu8muJLjuOyw@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: John R Levine <johnl@taugh.com>, dmarc-ietf <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007ad44605b93193b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/BxEKutTgC5NVMvyLAPb7Q_4Zv2Y>
Subject: Re: [dmarc-ietf] A policy weaker than quarantine, yet better than none
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, 18 Jan 2021 19:17:48 -0000

--0000000000007ad44605b93193b0
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 18, 2021 at 2:14 PM Alessandro Vesely <vesely@tana.it> wrote:

>
> On Mon 18/Jan/2021 19:56:21 +0100 John Levine wrote:
>
> >
> >> BTW, the current spec does not mean that an invalid p= implies the
> >> DMARC record is broken.  If it did, it wouldn't say to check rua= in
> >> that case.
> >
> > I know.  It would have been better if it didn't say that, but it's too
> > late to change it now.
>
>
> I don't understand why you say it's too late.  This is not emailcore,
> and we don't risk getting back to proposed standard if we change too much.
>
> We're just writing a proposed standard.  When choosing between a
> better spec and sticking to the existing one what criteria are we
> complying with?
>

You are assuming facts not in evidence, namely that your proposal results
in a better standard.

Michael Hammer

--0000000000007ad44605b93193b0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 18, 2021 at 2:14 PM Aless=
andro Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On Mon 18/Jan/2021 19:56:21 +0100 John Levine wrote:<br>
<br>
&gt; <br>
&gt;&gt; BTW, the current spec does not mean that an invalid p=3D implies t=
he <br>
&gt;&gt; DMARC record is broken.=C2=A0 If it did, it wouldn&#39;t say to ch=
eck rua=3D in <br>
&gt;&gt; that case.<br>
&gt; <br>
&gt; I know.=C2=A0 It would have been better if it didn&#39;t say that, but=
 it&#39;s too <br>
&gt; late to change it now.<br>
<br>
<br>
I don&#39;t understand why you say it&#39;s too late.=C2=A0 This is not ema=
ilcore, <br>
and we don&#39;t risk getting back to proposed standard if we change too mu=
ch.<br>
<br>
We&#39;re just writing a proposed standard.=C2=A0 When choosing between a <=
br>
better spec and sticking to the existing one what criteria are we <br>
complying with?<br></blockquote><div><br></div><div>You are assuming facts =
not in evidence, namely that your proposal results in a better standard. </=
div><div><br></div><div>Michael Hammer<br></div></div></div>

--0000000000007ad44605b93193b0--


From nobody Mon Jan 18 12:20:40 2021
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 03D7E3A03C9 for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 12:20:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 3MZRF50CvO_L for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 12:20:37 -0800 (PST)
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 B1B853A0332 for <dmarc@ietf.org>; Mon, 18 Jan 2021 12:20:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611001234; bh=ETksIB8foOUD3AF9dEUXiF4CqQ+i1edOXNCjcxv5p9s=; l=1030; h=To:References:From:Date:In-Reply-To; b=DSk/+unijn25qWxBHtnVJtCVNB1g1gU6L6eDZhEWE35vXfAbznPdwZakBWBwYw2eH EfZn4oeNCvgPtCfR3DnDLgwsikVCrb6EKKEDUoG5Ic2dkhMl9Zv91sNkdGdn+HQ14W e2b92Dbtdft83bZwBjqCwCjqC5d0mcODZ2hbKFO6sISTEd0H0ZzEA1MGRCm3K
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [192.168.1.132] ([93.37.83.242]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC0C3.000000006005ED92.00000C69; Mon, 18 Jan 2021 21:20:34 +0100
To: Dotzero <dotzero@gmail.com>, dmarc-ietf <dmarc@ietf.org>, John R Levine <johnl@taugh.com>
References: <20210117213536.165266B2315E@ary.qy> <8b8b3304-80f5-7287-aee8-e86ff72dcd31@tana.it> <7e5b91cc-8ca8-6f7f-4c3e-83e13a85c61d@taugh.com> <fad5eb1c-8cea-e061-fb57-a7e5538d281a@tana.it> <128070e1-25e2-ed76-e4cb-a54ef746b02@taugh.com> <7a13ec60-8d17-0d80-2f55-a5a262689897@tana.it> <CAJ4XoYfvRQ2KguDBsfWGqHH3-hKYBi9vCf=n6Afu8muJLjuOyw@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <4a88860d-4b41-b271-d93e-dfa7c3628f41@tana.it>
Date: Mon, 18 Jan 2021 21:20:34 +0100
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: <CAJ4XoYfvRQ2KguDBsfWGqHH3-hKYBi9vCf=n6Afu8muJLjuOyw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/NCGX64iTfVMnRMQDpK4G-n01MYM>
Subject: [dmarc-ietf] Criteria for changes, was A policy weaker than quarantine, yet better than none
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, 18 Jan 2021 20:20:39 -0000

On Mon 18/Jan/2021 20:17:31 +0100 Dotzero wrote:

> On Mon, Jan 18, 2021 at 2:14 PM Alessandro Vesely <vesely@tana.it> wrote:
>> On Mon 18/Jan/2021 19:56:21 +0100 John Levine wrote:
>>
>>>
>>>> BTW, the current spec does not mean that an invalid p= implies the
>>>> DMARC record is broken.  If it did, it wouldn't say to check rua= in
>>>> that case.
>>>
>>> I know.  It would have been better if it didn't say that, but it's too
>>> late to change it now.
>>
>> I don't understand why you say it's too late.  This is not emailcore,
>> and we don't risk getting back to proposed standard if we change too much.
>>
>> We're just writing a proposed standard.  When choosing between a
>> better spec and sticking to the existing one what criteria are we
>> complying with?
>>
> 
> You are assuming facts not in evidence, namely that your proposal results
> in a better standard.


Not my proposal.  John said "it would have been better if...

In general, why are we trying to minimize changes?

Best
Ale
-- 













From nobody Mon Jan 18 22:43:20 2021
Return-Path: <superuser@gmail.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 E7EF03A1224 for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 22:43:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3e2ZWPSTOdDl for <dmarc@ietfa.amsl.com>; Mon, 18 Jan 2021 22:43:16 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A5B43A1221 for <dmarc@ietf.org>; Mon, 18 Jan 2021 22:43:16 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id 186so8068706vsz.13 for <dmarc@ietf.org>; Mon, 18 Jan 2021 22:43:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mVNIhQlmD5spJMMzE6+T8aVKVxA++qW73OY3AtFlrvQ=; b=Eqj47BpWbhdXaXEOTlSIFdwAivLkiMIBQS5EM7ukCK5k6f2ufUJkpRJGFHIkDiG/y0 JB0/rARWE77ImjOc460hCs8+sXp+DQsg80/FJMrBIBb4Sk9oRTdDFCF7gw3d0Ucn/nBF grirjGslo4UqXdYkp9myShHdJJEUen2L/BH+lvOj//IL9HANUGccVwc8cDdk+VbwkWVc q3w6gEYFcZgTKAY/0On2INHWzUWZeQnlJD2O7q05St5/nxF6ODLMUUmo+kjSa1z8YPp1 o9vpf4ItHkR5Axf2Cv7Bk3T/91JJ8K/hVLP8HAivfy4PMF+SEbATH9ghuB/FnZb4eZ0/ 7r4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mVNIhQlmD5spJMMzE6+T8aVKVxA++qW73OY3AtFlrvQ=; b=NuDlc7KjULceC9wgIztMRE1bh60vSX2f4cYX574+Yv/XXPUQ8qXkf0Ub1LUfEENi+Q gUVDBGGBJeMysTd07uzdqOOBLmj8YjlNPUgmOQJAv/InlK/czJU0cyyMMTYNs6Q7/qH3 h1twtvdRPWAVEpm+Fhn2d7lYXplNz/JtXcAtmzG2ffbI7GbSL3hfIXyXVnFeAFaDua8q zqOVFkBRmdrpDc+muIX9bjOSHrZ1nYP+6h74HozqzF+pmi5865+15IekaWPrGXH1Jge4 X5DRIe5GwjtVl5bfZVMum3o69luZm4SAMI9Wg7ybHGtclPQZNoidbU9e2KBeFkin+BFP ypVg==
X-Gm-Message-State: AOAM531REeo7QFtiMjZikCNTt8W6NsKVgK3ONnRy3C1uXdct/ZVQ2MUy aaLDcEwRrVsKj2DfmjUIga/NcYPPNaZIUBSFi9xoI5rbibTP0Q==
X-Google-Smtp-Source: ABdhPJyCfL8tfAswplgfl+dXb0kJM2SY/mmvuDMqtf7Zge4BAKTjLd0Vmnf2wB0xg7U3Uym8i42njMA8tVXnHNKUHr8=
X-Received: by 2002:a67:2bc2:: with SMTP id r185mr1672284vsr.15.1611038594798;  Mon, 18 Jan 2021 22:43:14 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87ima4wu3s.fsf@hobgoblin.ariadne.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 18 Jan 2021 22:43:01 -0800
Message-ID: <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Cc: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="0000000000002997c905b93b27cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/M-0go6seaV_DDLXXPGySzqHLzdA>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 19 Jan 2021 06:43:19 -0000

--0000000000002997c905b93b27cf
Content-Type: text/plain; charset="UTF-8"

In the interests of getting this document on its way, I'd like to suggest
the following edits in response to Dale's most recent message.  If the
working group concurs, we can finally get this out to Last Call.

My goal as an AD here is just to get the GenART feedback addressed, but the
text is being submitted as a WG contribution for discussion and consensus
consideration, not as a demand.   Please process accordingly; I believe the
agreement is to do another WGLC on the document before it goes on its way,
so the sooner consensus is reached on all of this, the sooner it goes.

First, a suggestion of my own that I think I saw elsewhere, but it's not in
Dale's reply: In several places there's a reference to "DMARC [RFC7489]".
That's appropriate the first time the reference is made, but I think after
that you can just say "DMARC" when referring to the protocol generally, or
to "RFC 7489" when you need to make a specific section or text reference.
They don't need to appear together everywhere.

I think Dave's original feedback has been addressed -- good stuff -- so
here are my suggestions around what's left:

On Mon, Nov 16, 2020 at 7:16 PM Dale R. Worley <worley@ariadne.com> wrote:

> My apologies for not tending to this promptly.
>
> In regard to the description of the experiments, the result criteria are
> rather subjective, but I don't see that as a problem.  It does seem to
> me that the title "PSD DMARC Privacy Concern Mitigation Experiment" is
> too narrow, as only the 3rd experiment seems to be about privacy
> issues.  A title as generic as "PSD DMARC Experiments" would be fine.
>

That's OK with me, or "DMARC PSD Experiments" or "DMARC PSD Experiment" if
we want to treat it all as one common thing.


> Although I note that even the -09 does not define "PSD", only "longest
> PSD", even though "PSD" is used in section 2.5.  I suspect that PSD is
> equal to "PSO Controlled Domain Name", though, or rather to some related
> set of them.  That needs to be cleaned up in some way.
>

PSD appears to be well defined in Section 2.2.

In section 3.5 and later there is the phrase "[this document] longest
> PSD".  I'm not sure, but I think this is supposed to be "longest PSD
> ([this document] section NN.NN)".
>

Agreed.

I believe that my strongest critique was that section 1 is difficult to
> understand if one does not already understand DMARC, and it does not
> seem that the section has been revised.  Re-reading it, I notice that it
> says "DMARC leverages public suffix lists to determine which domains are
> organizational domains."  Ignoring that I dislike this use of
> "leverage", a critical point is that it takes the existence of public
> suffix lists a priori -- indeed, this use of "leverage" generally means
> that the leveraged thing already exists and one is now extracting
> additional benefit from that.  Whereas I've never heard of public suffix
> lists and would naively expect that they are difficult to create and
> maintain.  It might be better to say "DMARC uses public suffix lists to
> determine which domains are organizational domains.  Public suffix lists
> are obtained/maintained/distributed by ..."
>

Replace all of Section 1 with this (ignore funny line wrapping):

   DMARC [RFC7489 <https://tools.ietf.org/html/rfc7489>] provides a
mechanism for publishing organizational
   policy information to email receivers.  DMARC allows policy to be
   specified for both individual domains and for organizational domains
   and their sub-domains within a single organization.

   To determine the organizational domain for a message under evaluation,
   and thus where to look for a policy statement, DMARC makes use of a
Public Suffix List.
   The process for doing this can be found in Section 3.2 of the DMARC
specification.

   DMARC as specified presumes that domain names present in a PSL are not
   organizational domains and thus not subject to DMARC processing; domains
   are either organizational domains, sub-domains of organizational
   domains, or listed on a PSL.  For domains listed in a
   PSL, i.e., TLDs and domains that exist between TLDs and
   organization level domains, policy can only be published for the
   exact domain.  No method is available for these domains to express
   policy or receive feedback reporting for sub-domains.  This missing
   method allows for the abuse of non-existent organizational-level
   domains and prevents identification of domain abuse in email.

   This document specifies experimental updates to the DMARC and PSL
algorithm cited
   above, in an attempt to mitigate this abuse.


Looking at the second paragraph of section 1, I notice that despite all
> the special terms for classifying domain names in section 2, the example
> in this section does not describe which of the domain names that it
> mentions fall into which of these classes.  E.g. "tax.gov.example" is
> said to be registered, but it looks like it is also the organizational
> domain, and "gov.example" is its longest PSD.  It would also help to
> mention that "tax.gov.example" is "registered at" "gov.example" to
> introduce the details of the usage "registered at".
>
>     Suppose there exists a domain "tax.gov.example" (registered at
>     "gov.example") ...
>

Introduce a new Section 1.1: "Example" with this:

   As an example, imagine a country code TLD (ccTLD) which has public
   subdomains for government and commercial use (".gov.example" and
   ".com.example").  A PSL whose maintainer is aware of this country's
domain structure
   would include entries for both of these in the PSL, indicating that they are
   PSDs below which registrations can occur.  Suppose further that
there exists a domain
   "tax.gov.example", registered within ".gov.example", that is
   responsible for taxation in this imagined
   country.

   However, by exploiting the typically unauthenticated nature
   of email, there are regular malicious campaigns to impersonate this
   organization that use similar-looking ("cousin") domains such as
   "t4x.gov.example".  Such domains are not registered.

   Within the
   ".gov.example" public suffix, use of DMARC has been mandated, so
   "gov.example" publishes the following DMARC DNS record:

   [remainder of -09's page 3, the example, unchanged]
Introduce a new Section 1.2: "Discussion" comprising the remainder of
-09's Section 1.  In the first paragraph, between "simple" and
"extension", add "experimental".

A suggestion for 2.4:

NEW:

The longest PSD is the Organizational Domain with one label removed.
It names the immediate parent node of the Organizational Domain in the
DNS namespace tree.

-MSK

--0000000000002997c905b93b27cf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">In the interests of getting this document=
 on its way, I&#39;d like to suggest the following edits in response to Dal=
e&#39;s most recent message.=C2=A0 If the working group concurs, we can fin=
ally get this out to Last Call.</div><div dir=3D"ltr"><br></div><div>My goa=
l as an AD here is just to get the GenART feedback addressed, but the text =
is being submitted as a WG contribution for discussion and consensus consid=
eration, not as a demand.=C2=A0=C2=A0 Please process accordingly; I believe=
 the agreement is to do another WGLC on the document before it goes on its =
way, so the sooner consensus is reached on all of this, the sooner it goes.=
<br></div><div><br></div><div>First, a suggestion of my own that I think I =
saw elsewhere, but it&#39;s not in Dale&#39;s reply: In several places ther=
e&#39;s a reference to &quot;DMARC [RFC7489]&quot;.=C2=A0 That&#39;s approp=
riate the first time the reference is made, but I think after that you can =
just say &quot;DMARC&quot; when referring to the protocol generally, or to =
&quot;RFC 7489&quot; when you need to make a specific section or text refer=
ence.=C2=A0 They don&#39;t need to appear together everywhere.</div><div><b=
r></div><div>I think Dave&#39;s original feedback has been addressed -- goo=
d stuff -- so here are my suggestions around what&#39;s left:<br></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, No=
v 16, 2020 at 7:16 PM Dale R. Worley &lt;<a href=3D"mailto:worley@ariadne.c=
om" target=3D"_blank">worley@ariadne.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">My apologies for not tending to thi=
s promptly.<br>
<br>
In regard to the description of the experiments, the result criteria are<br=
>
rather subjective, but I don&#39;t see that as a problem.=C2=A0 It does see=
m to<br>
me that the title &quot;PSD DMARC Privacy Concern Mitigation Experiment&quo=
t; is<br>
too narrow, as only the 3rd experiment seems to be about privacy<br>
issues.=C2=A0 A title as generic as &quot;PSD DMARC Experiments&quot; would=
 be fine.<br></blockquote><div><br></div><div>That&#39;s OK with me, or &qu=
ot;DMARC PSD Experiments&quot; or &quot;DMARC PSD Experiment&quot; if we wa=
nt to treat it all as one common thing.<br></div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
Although I note that even the -09 does not define &quot;PSD&quot;, only &qu=
ot;longest<br>
PSD&quot;, even though &quot;PSD&quot; is used in section 2.5.=C2=A0 I susp=
ect that PSD is<br>
equal to &quot;PSO Controlled Domain Name&quot;, though, or rather to some =
related<br>
set of them.=C2=A0 That needs to be cleaned up in some way.<br></blockquote=
><div><br></div><div>PSD appears to be well defined in Section 2.2.</div><d=
iv> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
In section 3.5 and later there is the phrase &quot;[this document] longest<=
br>
PSD&quot;.=C2=A0 I&#39;m not sure, but I think this is supposed to be &quot=
;longest PSD<br>
([this document] section NN.NN)&quot;.<br></blockquote><div><br></div><div>=
Agreed.</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
I believe that my strongest critique was that section 1 is difficult to<br>
understand if one does not already understand DMARC, and it does not<br>
seem that the section has been revised.=C2=A0 Re-reading it, I notice that =
it<br>
says &quot;DMARC leverages public suffix lists to determine which domains a=
re<br>
organizational domains.&quot;=C2=A0 Ignoring that I dislike this use of<br>
&quot;leverage&quot;, a critical point is that it takes the existence of pu=
blic<br>
suffix lists a priori -- indeed, this use of &quot;leverage&quot; generally=
 means<br>
that the leveraged thing already exists and one is now extracting<br>
additional benefit from that.=C2=A0 Whereas I&#39;ve never heard of public =
suffix<br>
lists and would naively expect that they are difficult to create and<br>
maintain.=C2=A0 It might be better to say &quot;DMARC uses public suffix li=
sts to<br>
determine which domains are organizational domains.=C2=A0 Public suffix lis=
ts<br>
are obtained/maintained/distributed by ...&quot;<br></blockquote><div><br><=
/div><div>Replace all of Section 1 with this (ignore funny line wrapping):<=
br></div><div>
<pre>   DMARC [<a href=3D"https://tools.ietf.org/html/rfc7489" title=3D"&qu=
ot;Domain-based Message Authentication, Reporting, and Conformance (DMARC)&=
quot;" target=3D"_blank">RFC7489</a>] provides a mechanism for publishing o=
rganizational
   policy information to email receivers.  DMARC allows policy to be
   specified for both individual domains and for organizational domains
   and their sub-domains within a single organization.<br><br>   To determi=
ne the organizational domain for a message under evaluation,<br>   and thus=
 where to look for a policy statement, DMARC makes use of a Public Suffix L=
ist.<br>   The process for doing this can be found in Section 3.2 of the DM=
ARC specification.<br></pre><pre>   DMARC as specified presumes that domain=
 names present in a PSL are not
   organizational domains and thus not subject to DMARC processing; domains
   are either organizational domains, sub-domains of organizational
   domains, or listed on a PSL.  For domains listed in a
   PSL, i.e., TLDs and domains that exist between TLDs and
   organization level domains, policy can only be published for the
   exact domain.  No method is available for these domains to express
   policy or receive feedback reporting for sub-domains.  This missing
   method allows for the abuse of non-existent organizational-level
   domains and prevents identification of domain abuse in email.<br><br></p=
re><pre>   This document specifies experimental updates to the DMARC and PS=
L algorithm cited<br>   above, in an attempt to mitigate this abuse.<br></p=
re>

</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Looking at the second paragraph of section 1, I notice that despite all<br>
the special terms for classifying domain names in section 2, the example<br=
>
in this section does not describe which of the domain names that it<br>
mentions fall into which of these classes.=C2=A0 E.g. &quot;tax.gov.example=
&quot; is<br>
said to be registered, but it looks like it is also the organizational<br>
domain, and &quot;gov.example&quot; is its longest PSD.=C2=A0 It would also=
 help to<br>
mention that &quot;tax.gov.example&quot; is &quot;registered at&quot; &quot=
;gov.example&quot; to<br>
introduce the details of the usage &quot;registered at&quot;.<br>
<br>
=C2=A0 =C2=A0 Suppose there exists a domain &quot;tax.gov.example&quot; (re=
gistered at<br>
=C2=A0 =C2=A0 &quot;gov.example&quot;) ...<br></blockquote><div><br></div><=
div>Introduce a new Section 1.1: &quot;Example&quot; with this:<br>
<pre>   As an example, imagine a country code TLD (ccTLD) which has public
   subdomains for government and commercial use (&quot;.gov.example&quot; a=
nd
   &quot;.com.example&quot;).  A PSL whose maintainer is aware of this coun=
try&#39;s domain structure<br>   would include entries for both of these in=
 the PSL, indicating that they are<br>   PSDs below which registrations can=
 occur.  Suppose further that there exists a domain
   &quot;tax.gov.example&quot;, registered within &quot;.gov.example&quot;,=
 that is<br>   responsible for taxation in this imagined
   country.<br><br>   However, by exploiting the typically unauthenticated =
nature
   of email, there are regular malicious campaigns to impersonate this
   organization that use similar-looking (&quot;cousin&quot;) domains such =
as
   &quot;t4x.gov.example&quot;.  Such domains are not registered.<br></pre>=
<pre>   Within the
   &quot;.gov.example&quot; public suffix, use of DMARC has been mandated, =
so
   &quot;gov.example&quot; publishes the following DMARC DNS record:<br></p=
re><pre>   [remainder of -09&#39;s page 3, the example, unchanged]<br>
<span style=3D"font-family:arial,sans-serif">Introduce a new Section 1.2: &=
quot;Discussion&quot; comprising the remainder of -09&#39;s Section 1.  In =
the first paragraph, between &quot;simple&quot; and &quot;extension&quot;, =
add &quot;experimental&quot;.<br></span></pre><pre><span style=3D"font-fami=
ly:arial,sans-serif">A suggestion for 2.4:<br><br>NEW:<br><br><span style=
=3D"font-family:monospace"><span class=3D"gmail-insert">The longest PSD is =
the Organizational Domain with one label removed.</span>  It names the imme=
diate parent node of the Organizational Domain in the DNS namespace tree.</=
span>
</span></pre><pre><span style=3D"font-family:arial,sans-serif">-MSK</span>
</pre>

</div></div></div>

--0000000000002997c905b93b27cf--


From nobody Tue Jan 19 02:30:48 2021
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 80D123A1426 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 02:30:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level: 
X-Spam-Status: No, score=-2.381 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.262, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 2jqXW3KsxVN4 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 02:30:43 -0800 (PST)
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 08EFD3A1422 for <dmarc@ietf.org>; Tue, 19 Jan 2021 02:30:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611052239; bh=NbkOBK5f1+VxkpWkosYKwRHcYLdB3l/NbWLiuETzmWI=; l=7489; h=To:References:From:Date:In-Reply-To; b=DMqLxAfGxqrei9jRAbli7LnULSAjOCcfijuEtOMAD5DIvRM95/VQFHTfD0JSOgSkZ rNg3yF2UiJEMTmG2e1of6CsQJj59FW6lNaognwPc92X2N+nQHB93QG5Ugqrf3e7JGO 1Mjk2ZEhC4ZYIvtthkawuFFFKkoXVnBQa3v0k0dfxUWNKsaLMIcM6xYyKrhEs
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0CB.000000006006B4CF.00001745; Tue, 19 Jan 2021 11:30:39 +0100
To: dmarc@ietf.org
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it>
Date: Tue, 19 Jan 2021 11:30:38 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@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/sTY7Ci3aACBzbur1djT7HhE-Gmg>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 19 Jan 2021 10:30:47 -0000

On Tue 19/Jan/2021 07:43:01 +0100 Murray S. Kucherawy wrote:
> [...]
> On Mon, Nov 16, 2020 at 7:16 PM Dale R. Worley <worley@ariadne.com> wrote:
> 
>> My apologies for not tending to this promptly.
>>
>> In regard to the description of the experiments, the result criteria are
>> rather subjective, but I don't see that as a problem.  It does seem to
>> me that the title "PSD DMARC Privacy Concern Mitigation Experiment" is
>> too narrow, as only the 3rd experiment seems to be about privacy
>> issues.  A title as generic as "PSD DMARC Experiments" would be fine.
>>
> 
> That's OK with me, or "DMARC PSD Experiments" or "DMARC PSD Experiment" if
> we want to treat it all as one common thing.


+1


>> Although I note that even the -09 does not define "PSD", only "longest
>> PSD", even though "PSD" is used in section 2.5.  I suspect that PSD is
>> equal to "PSO Controlled Domain Name", though, or rather to some related
>> set of them.  That needs to be cleaned up in some way.
>>
> 
> PSD appears to be well defined in Section 2.2.


+1


> In section 3.5 and later there is the phrase "[this document] longest
>> PSD".  I'm not sure, but I think this is supposed to be "longest PSD
>> ([this document] section NN.NN)".
>>
> 
> Agreed.


I guess "[this document]" refers to the RFC number to be.  I think it's useless 
and can be safely removed, all of the five occurrences of it.

It is clearer and more useful to specify the referred document when it is /not/ 
this document.  For example:

     Changes in Section 6.5 of RFC 7489 "Domain Owner Actions"

The above is going to be rendered with the correct anchor in the htmlized 
version of the document.  It can be expressed in xml as:

     <xref target="RFC7489" sectionFormat="of" section="6.5"/>

so as to generate correct links whenever possible.


>> I believe that my strongest critique was that section 1 is difficult to
>> understand if one does not already understand DMARC, and it does not
>> seem that the section has been revised.  Re-reading it, I notice that it
>> says "DMARC leverages public suffix lists to determine which domains are
>> organizational domains."  [...]


In fact, those are the two terms appearing in the title.  BTW, I'd change the 
title to:

     Domain-based Message Authentication, Reporting, and Conformance (DMARC)
     Extension For Public Suffix Domains (PSDs)

Anyway, I agree it is correct to introduce /both/ terms.


> Replace all of Section 1 with this (ignore funny line wrapping):
> 
>     DMARC [RFC7489 <https://tools.ietf.org/html/rfc7489>] provides a
>     mechanism for publishing organizational
>     policy information to email receivers.  DMARC allows policy to be
>     specified for both individual domains and for organizational domains
>     and their sub-domains within a single organization.


+1 to break the paragraph here.


>     To determine the organizational domain for a message under evaluation,
>     and thus where to look for a policy statement, DMARC makes use of a
>     Public Suffix List.
>     The process for doing this can be found in Section 3.2 of the DMARC
>     specification.


Couldn't we skip that kind of functional intro and say something general, such 
as anticipating Section 2.2:

     Public Suffix Domains (PSDs) are domain names publicly accessible for
     domain registration.  As explained in Section 2.2, they include all top
     level domains and some more.  The way delegations occur on the global
     Internet makes it difficult to establish whether a domain is a PSD.  A
     community maintained Public Suffix List (PSL) exists for that purpose.

Thinking twice, perhaps we don't need to introduce the PSL until Section 3.4. 
In that case, strike the last two sentences of the above paragraph.


>     DMARC as specified presumes that domain names present in a PSL are not
>     organizational domains and thus not subject to DMARC processing; domains
>     are either organizational domains, sub-domains of organizational
>     domains, or listed on a PSL.  For domains listed in a
>     PSL, i.e., TLDs and domains that exist between TLDs and
>     organization level domains, policy can only be published for the
>     exact domain.


That's still overly specific for an introduction.  It only serves to present 
the concept that there are domains that are not actually organizational domains 
but are characterized by a sort of organizational flavor.  The "these domains" 
of the following sentence.  We don't need seven lines of text for that.


>     No method is available for these domains to express
>     policy or receive feedback reporting for sub-domains.  This missing
>     method allows for the abuse of non-existent organizational-level
>     domains and prevents identification of domain abuse in email.
> 
>     This document specifies experimental updates to the DMARC and PSL
>     algorithm cited above, in an attempt to mitigate this abuse.


If the PSL is not yet introduced:

     This document specifies experimental updates to DMARC and its policy
     discovery, in an attempt to mitigate this abuse.


>> Looking at the second paragraph of section 1, I notice that despite all
>> the special terms for classifying domain names in section 2, the example
>> in this section does not describe which of the domain names that it
>> mentions fall into which of these classes.  E.g. "tax.gov.example" is
>> said to be registered, but it looks like it is also the organizational
>> domain, and "gov.example" is its longest PSD.  It would also help to
>> mention that "tax.gov.example" is "registered at" "gov.example" to
>> introduce the details of the usage "registered at".
>>
>>     Suppose there exists a domain "tax.gov.example" (registered at
>>     "gov.example") ...
>>
> 
> Introduce a new Section 1.1: "Example" with this:


I don't fully agree.  The example only lasts until the end of page 3.  From 
page 4 on, the text describes the core of the experiment, so it shouldn't be 
under an "Example" heading.  If we skip the PSL, the example remains quite 
compact even after adding those "registered at".


>     As an example, imagine a country code TLD (ccTLD) which has public
>     subdomains for government and commercial use (".gov.example" and
>     ".com.example").  A PSL whose maintainer is aware of this country's
>     domain structure
>     would include entries for both of these in the PSL, indicating that they are
>     PSDs below which registrations can occur.  Suppose further that
>     there exists a domain
>     "tax.gov.example", registered within ".gov.example", that is
>     responsible for taxation in this imagined
>     country.
> 
>     However, by exploiting the typically unauthenticated nature
>     of email, there are regular malicious campaigns to impersonate this
>     organization that use similar-looking ("cousin") domains such as
>     "t4x.gov.example".  Such domains are not registered.
> 
>     Within the
>     ".gov.example" public suffix, use of DMARC has been mandated, so
>     "gov.example" publishes the following DMARC DNS record:
> 
>     [remainder of -09's page 3, the example, unchanged]
> Introduce a new Section 1.2: "Discussion" comprising the remainder of
> -09's Section 1.  In the first paragraph, between "simple" and
> "extension", add "experimental".
> 
> A suggestion for 2.4:
> 
> NEW:
> 
> The longest PSD is the Organizational Domain with one label removed.
> It names the immediate parent node of the Organizational Domain in the
> DNS namespace tree.


s/one/the leftmost/


Best
Ale
-- 




















From nobody Tue Jan 19 04:34:30 2021
Return-Path: <dougfoster.emailstandards@gmail.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 F1FA13A14AD for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 04:34:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 hbKq__01CgTg for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 04:34:26 -0800 (PST)
Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1927C3A14AB for <dmarc@ietf.org>; Tue, 19 Jan 2021 04:34:25 -0800 (PST)
Received: by mail-vk1-xa29.google.com with SMTP id e27so4743098vkn.2 for <dmarc@ietf.org>; Tue, 19 Jan 2021 04:34:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=saSJYo3vbwUsoFH4vpC9OtgK4bLyO85PVNM7XgFpo/g=; b=Jm6BA5HSlncQ6yWBNtLWuNM8rrd3FI93Xt2ttZxdeCnk/dtjReDtDLrEfdIyK0sHRx ojkmx2OWSzWFNOCWnrVQD3Wre6keb/IJe9m3UqxpholcWJ6kiSvxvLrUXqIdQ39iU2YH nL1ZE3GtPGQEDqCozgWs98crgQFrVLGUUc6bHaWM3nfr8RsbSJin25a3e/dH3b/XSkXr kEETekH3dNS9z3KGdPiIJbKNyFvtMMpOu0l/+CpUhS+++UUbbV/rd7kVlzRPT6oWENoD Q9feZeqwU14xwfGa6wGrjkyF8RqUCbvms2KmPi2eDvNJ5c5fVgLWsi1kFsolOhaFXjnC eVGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=saSJYo3vbwUsoFH4vpC9OtgK4bLyO85PVNM7XgFpo/g=; b=cYcnvuSimXEq+961k2C7pwE+W+5UHlkx+8liYeUq0ebetnX7jviGE9BnR2PvVaJPyB Xu5aPBYS+mONSTtygc/VQQF2zjvi0NyiXiPEIcff4HDvZNXQpScWG+yv1TBOfDw40Mhz JHwPKYmlQS24++SDHfsagePaafxTBs9vAFe6ffh2TAJ1eOKRIcDRK1TyTVDdlAX958L+ gHeAAes4dSYfDwP/wpmvBktf6ONRnDCqx0VQqb7/klU59AVBUHuOIWIdkQ4WwAzYLyjk MCzvzHG580LGpvZzkKr4sjRupF0y7GRvCJcbGnX18mgMs2C/iMOHiHEvc+WhwmZ3Y0Bs Ib9w==
X-Gm-Message-State: AOAM530LezJgOWQ9RzQji0AgVySHYu46f/QosVSrxiX/SlFZTgRp1l+Q qTWaGtE+s9IT5vmIpCvqTJBT2IYOljzAPlSZ/MU=
X-Google-Smtp-Source: ABdhPJxdVcZ7Nj38vO4M757IEc7K0pkKtxvJnShiwj8tljQaiyBDsQG3RH/d7zf2FMnNC1Q+GyUpbEuK3tI8CPlESUo=
X-Received: by 2002:a1f:4582:: with SMTP id s124mr2488830vka.7.1611059664984;  Tue, 19 Jan 2021 04:34:24 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com>
In-Reply-To: <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 19 Jan 2021 07:34:14 -0500
Message-ID: <CAH48ZfwOdZcJz02a76wktQDpV_dpPHKw+qJjE2ZCDvOqF3Ptdw@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="0000000000000b1c8c05b9400f73"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/bC_SsFtgRAvKNmLPWmySQO_BGEw>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 19 Jan 2021 12:34:29 -0000

--0000000000000b1c8c05b9400f73
Content-Type: text/plain; charset="UTF-8"

I raised objections to the definition of "non-existent", which never
received an adequate response before the discussion went silent.

DMARC checks the From  header address, which may exist only as an
identifier used for mass mailings.   These mailings are often sent by an
ESP using an unrelated SMTP address.    As such, the From address need not
be associated with any A, AAAA, or MX record.    I assert that the only
viable definition of non-existent is "not registered", as evidenced by
absence of an NS record.

I don't believe the proposed definition of "non-existent" is reliably true
even in the special case of interest for this document, impersonation fraud
occurring at the top of an organizational structure.   Example.PSD may
legitimately use mail.Example.PSD for email and www.example.psd for web.
 If the proposed condition MUST always be true, I have not seen that fact
demonstrated.   Since the document raises a general concern about
fraudulent use of non-existent domains, the definition used should be one
that can be generalized.,

Doug Foster

On Tue, Jan 19, 2021 at 1:43 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> In the interests of getting this document on its way, I'd like to suggest
> the following edits in response to Dale's most recent message.  If the
> working group concurs, we can finally get this out to Last Call.
>
> My goal as an AD here is just to get the GenART feedback addressed, but
> the text is being submitted as a WG contribution for discussion and
> consensus consideration, not as a demand.   Please process accordingly; I
> believe the agreement is to do another WGLC on the document before it goes
> on its way, so the sooner consensus is reached on all of this, the sooner
> it goes.
>
> First, a suggestion of my own that I think I saw elsewhere, but it's not
> in Dale's reply: In several places there's a reference to "DMARC
> [RFC7489]".  That's appropriate the first time the reference is made, but I
> think after that you can just say "DMARC" when referring to the protocol
> generally, or to "RFC 7489" when you need to make a specific section or
> text reference.  They don't need to appear together everywhere.
>
> I think Dave's original feedback has been addressed -- good stuff -- so
> here are my suggestions around what's left:
>
> On Mon, Nov 16, 2020 at 7:16 PM Dale R. Worley <worley@ariadne.com> wrote:
>
>> My apologies for not tending to this promptly.
>>
>> In regard to the description of the experiments, the result criteria are
>> rather subjective, but I don't see that as a problem.  It does seem to
>> me that the title "PSD DMARC Privacy Concern Mitigation Experiment" is
>> too narrow, as only the 3rd experiment seems to be about privacy
>> issues.  A title as generic as "PSD DMARC Experiments" would be fine.
>>
>
> That's OK with me, or "DMARC PSD Experiments" or "DMARC PSD Experiment" if
> we want to treat it all as one common thing.
>
>
>> Although I note that even the -09 does not define "PSD", only "longest
>> PSD", even though "PSD" is used in section 2.5.  I suspect that PSD is
>> equal to "PSO Controlled Domain Name", though, or rather to some related
>> set of them.  That needs to be cleaned up in some way.
>>
>
> PSD appears to be well defined in Section 2.2.
>
> In section 3.5 and later there is the phrase "[this document] longest
>> PSD".  I'm not sure, but I think this is supposed to be "longest PSD
>> ([this document] section NN.NN)".
>>
>
> Agreed.
>
> I believe that my strongest critique was that section 1 is difficult to
>> understand if one does not already understand DMARC, and it does not
>> seem that the section has been revised.  Re-reading it, I notice that it
>> says "DMARC leverages public suffix lists to determine which domains are
>> organizational domains."  Ignoring that I dislike this use of
>> "leverage", a critical point is that it takes the existence of public
>> suffix lists a priori -- indeed, this use of "leverage" generally means
>> that the leveraged thing already exists and one is now extracting
>> additional benefit from that.  Whereas I've never heard of public suffix
>> lists and would naively expect that they are difficult to create and
>> maintain.  It might be better to say "DMARC uses public suffix lists to
>> determine which domains are organizational domains.  Public suffix lists
>> are obtained/maintained/distributed by ..."
>>
>
> Replace all of Section 1 with this (ignore funny line wrapping):
>
>    DMARC [RFC7489 <https://tools.ietf.org/html/rfc7489>] provides a mechanism for publishing organizational
>    policy information to email receivers.  DMARC allows policy to be
>    specified for both individual domains and for organizational domains
>    and their sub-domains within a single organization.
>
>    To determine the organizational domain for a message under evaluation,
>    and thus where to look for a policy statement, DMARC makes use of a Public Suffix List.
>    The process for doing this can be found in Section 3.2 of the DMARC specification.
>
>    DMARC as specified presumes that domain names present in a PSL are not
>    organizational domains and thus not subject to DMARC processing; domains
>    are either organizational domains, sub-domains of organizational
>    domains, or listed on a PSL.  For domains listed in a
>    PSL, i.e., TLDs and domains that exist between TLDs and
>    organization level domains, policy can only be published for the
>    exact domain.  No method is available for these domains to express
>    policy or receive feedback reporting for sub-domains.  This missing
>    method allows for the abuse of non-existent organizational-level
>    domains and prevents identification of domain abuse in email.
>
>    This document specifies experimental updates to the DMARC and PSL algorithm cited
>    above, in an attempt to mitigate this abuse.
>
>
> Looking at the second paragraph of section 1, I notice that despite all
>> the special terms for classifying domain names in section 2, the example
>> in this section does not describe which of the domain names that it
>> mentions fall into which of these classes.  E.g. "tax.gov.example" is
>> said to be registered, but it looks like it is also the organizational
>> domain, and "gov.example" is its longest PSD.  It would also help to
>> mention that "tax.gov.example" is "registered at" "gov.example" to
>> introduce the details of the usage "registered at".
>>
>>     Suppose there exists a domain "tax.gov.example" (registered at
>>     "gov.example") ...
>>
>
> Introduce a new Section 1.1: "Example" with this:
>
>    As an example, imagine a country code TLD (ccTLD) which has public
>    subdomains for government and commercial use (".gov.example" and
>    ".com.example").  A PSL whose maintainer is aware of this country's domain structure
>    would include entries for both of these in the PSL, indicating that they are
>    PSDs below which registrations can occur.  Suppose further that there exists a domain
>    "tax.gov.example", registered within ".gov.example", that is
>    responsible for taxation in this imagined
>    country.
>
>    However, by exploiting the typically unauthenticated nature
>    of email, there are regular malicious campaigns to impersonate this
>    organization that use similar-looking ("cousin") domains such as
>    "t4x.gov.example".  Such domains are not registered.
>
>    Within the
>    ".gov.example" public suffix, use of DMARC has been mandated, so
>    "gov.example" publishes the following DMARC DNS record:
>
>    [remainder of -09's page 3, the example, unchanged]
> Introduce a new Section 1.2: "Discussion" comprising the remainder of -09's Section 1.  In the first paragraph, between "simple" and "extension", add "experimental".
>
> A suggestion for 2.4:
>
> NEW:
>
> The longest PSD is the Organizational Domain with one label removed.  It names the immediate parent node of the Organizational Domain in the DNS namespace tree.
>
> -MSK
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--0000000000000b1c8c05b9400f73
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I raised objections to the definition of &quot;non-existen=
t&quot;, which never received an adequate response before the discussion we=
nt silent.=C2=A0 =C2=A0=C2=A0<div><br></div><div>DMARC checks the From=C2=
=A0 header address, which may exist only as an identifier used for mass mai=
lings.=C2=A0 =C2=A0These mailings are often sent by an ESP using an unrelat=
ed=C2=A0SMTP address.=C2=A0 =C2=A0 As such, the From address need not be as=
sociated with any A, AAAA, or MX record.=C2=A0 =C2=A0 I assert that the onl=
y viable definition of non-existent is &quot;not registered&quot;, as evide=
nced by absence of an NS record.<div><br></div><div>I don&#39;t believe the=
 proposed definition of &quot;non-existent&quot; is reliably true even in t=
he special case of interest for this document, impersonation fraud occurrin=
g at the top of an organizational structure.=C2=A0 =C2=A0Example.PSD may le=
gitimately use mail.Example.PSD for email and www.example.psd for web.=C2=
=A0 =C2=A0If the proposed condition MUST always be true, I have not seen th=
at fact demonstrated.=C2=A0 =C2=A0Since the document raises a general conce=
rn about fraudulent use of non-existent domains, the definition used should=
 be one that can be generalized.,</div><div><br></div><div>Doug Foster</div=
></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Tue, Jan 19, 2021 at 1:43 AM Murray S. Kucherawy &lt;<a href=3D"m=
ailto:superuser@gmail.com">superuser@gmail.com</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"=
ltr">In the interests of getting this document on its way, I&#39;d like to =
suggest the following edits in response to Dale&#39;s most recent message.=
=C2=A0 If the working group concurs, we can finally get this out to Last Ca=
ll.</div><div dir=3D"ltr"><br></div><div>My goal as an AD here is just to g=
et the GenART feedback addressed, but the text is being submitted as a WG c=
ontribution for discussion and consensus consideration, not as a demand.=C2=
=A0=C2=A0 Please process accordingly; I believe the agreement is to do anot=
her WGLC on the document before it goes on its way, so the sooner consensus=
 is reached on all of this, the sooner it goes.<br></div><div><br></div><di=
v>First, a suggestion of my own that I think I saw elsewhere, but it&#39;s =
not in Dale&#39;s reply: In several places there&#39;s a reference to &quot=
;DMARC [RFC7489]&quot;.=C2=A0 That&#39;s appropriate the first time the ref=
erence is made, but I think after that you can just say &quot;DMARC&quot; w=
hen referring to the protocol generally, or to &quot;RFC 7489&quot; when yo=
u need to make a specific section or text reference.=C2=A0 They don&#39;t n=
eed to appear together everywhere.</div><div><br></div><div>I think Dave&#3=
9;s original feedback has been addressed -- good stuff -- so here are my su=
ggestions around what&#39;s left:<br></div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 16, 2020 at 7:16 PM Dale R=
. Worley &lt;<a href=3D"mailto:worley@ariadne.com" target=3D"_blank">worley=
@ariadne.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">My apologies for not tending to this promptly.<br>
<br>
In regard to the description of the experiments, the result criteria are<br=
>
rather subjective, but I don&#39;t see that as a problem.=C2=A0 It does see=
m to<br>
me that the title &quot;PSD DMARC Privacy Concern Mitigation Experiment&quo=
t; is<br>
too narrow, as only the 3rd experiment seems to be about privacy<br>
issues.=C2=A0 A title as generic as &quot;PSD DMARC Experiments&quot; would=
 be fine.<br></blockquote><div><br></div><div>That&#39;s OK with me, or &qu=
ot;DMARC PSD Experiments&quot; or &quot;DMARC PSD Experiment&quot; if we wa=
nt to treat it all as one common thing.<br></div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
Although I note that even the -09 does not define &quot;PSD&quot;, only &qu=
ot;longest<br>
PSD&quot;, even though &quot;PSD&quot; is used in section 2.5.=C2=A0 I susp=
ect that PSD is<br>
equal to &quot;PSO Controlled Domain Name&quot;, though, or rather to some =
related<br>
set of them.=C2=A0 That needs to be cleaned up in some way.<br></blockquote=
><div><br></div><div>PSD appears to be well defined in Section 2.2.</div><d=
iv> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
In section 3.5 and later there is the phrase &quot;[this document] longest<=
br>
PSD&quot;.=C2=A0 I&#39;m not sure, but I think this is supposed to be &quot=
;longest PSD<br>
([this document] section NN.NN)&quot;.<br></blockquote><div><br></div><div>=
Agreed.</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
I believe that my strongest critique was that section 1 is difficult to<br>
understand if one does not already understand DMARC, and it does not<br>
seem that the section has been revised.=C2=A0 Re-reading it, I notice that =
it<br>
says &quot;DMARC leverages public suffix lists to determine which domains a=
re<br>
organizational domains.&quot;=C2=A0 Ignoring that I dislike this use of<br>
&quot;leverage&quot;, a critical point is that it takes the existence of pu=
blic<br>
suffix lists a priori -- indeed, this use of &quot;leverage&quot; generally=
 means<br>
that the leveraged thing already exists and one is now extracting<br>
additional benefit from that.=C2=A0 Whereas I&#39;ve never heard of public =
suffix<br>
lists and would naively expect that they are difficult to create and<br>
maintain.=C2=A0 It might be better to say &quot;DMARC uses public suffix li=
sts to<br>
determine which domains are organizational domains.=C2=A0 Public suffix lis=
ts<br>
are obtained/maintained/distributed by ...&quot;<br></blockquote><div><br><=
/div><div>Replace all of Section 1 with this (ignore funny line wrapping):<=
br></div><div>
<pre>   DMARC [<a href=3D"https://tools.ietf.org/html/rfc7489" title=3D"&qu=
ot;Domain-based Message Authentication, Reporting, and Conformance (DMARC)&=
quot;" target=3D"_blank">RFC7489</a>] provides a mechanism for publishing o=
rganizational
   policy information to email receivers.  DMARC allows policy to be
   specified for both individual domains and for organizational domains
   and their sub-domains within a single organization.<br><br>   To determi=
ne the organizational domain for a message under evaluation,<br>   and thus=
 where to look for a policy statement, DMARC makes use of a Public Suffix L=
ist.<br>   The process for doing this can be found in Section 3.2 of the DM=
ARC specification.<br></pre><pre>   DMARC as specified presumes that domain=
 names present in a PSL are not
   organizational domains and thus not subject to DMARC processing; domains
   are either organizational domains, sub-domains of organizational
   domains, or listed on a PSL.  For domains listed in a
   PSL, i.e., TLDs and domains that exist between TLDs and
   organization level domains, policy can only be published for the
   exact domain.  No method is available for these domains to express
   policy or receive feedback reporting for sub-domains.  This missing
   method allows for the abuse of non-existent organizational-level
   domains and prevents identification of domain abuse in email.<br><br></p=
re><pre>   This document specifies experimental updates to the DMARC and PS=
L algorithm cited<br>   above, in an attempt to mitigate this abuse.<br></p=
re>

</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Looking at the second paragraph of section 1, I notice that despite all<br>
the special terms for classifying domain names in section 2, the example<br=
>
in this section does not describe which of the domain names that it<br>
mentions fall into which of these classes.=C2=A0 E.g. &quot;tax.gov.example=
&quot; is<br>
said to be registered, but it looks like it is also the organizational<br>
domain, and &quot;gov.example&quot; is its longest PSD.=C2=A0 It would also=
 help to<br>
mention that &quot;tax.gov.example&quot; is &quot;registered at&quot; &quot=
;gov.example&quot; to<br>
introduce the details of the usage &quot;registered at&quot;.<br>
<br>
=C2=A0 =C2=A0 Suppose there exists a domain &quot;tax.gov.example&quot; (re=
gistered at<br>
=C2=A0 =C2=A0 &quot;gov.example&quot;) ...<br></blockquote><div><br></div><=
div>Introduce a new Section 1.1: &quot;Example&quot; with this:<br>
<pre>   As an example, imagine a country code TLD (ccTLD) which has public
   subdomains for government and commercial use (&quot;.gov.example&quot; a=
nd
   &quot;.com.example&quot;).  A PSL whose maintainer is aware of this coun=
try&#39;s domain structure<br>   would include entries for both of these in=
 the PSL, indicating that they are<br>   PSDs below which registrations can=
 occur.  Suppose further that there exists a domain
   &quot;tax.gov.example&quot;, registered within &quot;.gov.example&quot;,=
 that is<br>   responsible for taxation in this imagined
   country.<br><br>   However, by exploiting the typically unauthenticated =
nature
   of email, there are regular malicious campaigns to impersonate this
   organization that use similar-looking (&quot;cousin&quot;) domains such =
as
   &quot;t4x.gov.example&quot;.  Such domains are not registered.<br></pre>=
<pre>   Within the
   &quot;.gov.example&quot; public suffix, use of DMARC has been mandated, =
so
   &quot;gov.example&quot; publishes the following DMARC DNS record:<br></p=
re><pre>   [remainder of -09&#39;s page 3, the example, unchanged]<br>
<span style=3D"font-family:arial,sans-serif">Introduce a new Section 1.2: &=
quot;Discussion&quot; comprising the remainder of -09&#39;s Section 1.  In =
the first paragraph, between &quot;simple&quot; and &quot;extension&quot;, =
add &quot;experimental&quot;.<br></span></pre><pre><span style=3D"font-fami=
ly:arial,sans-serif">A suggestion for 2.4:<br><br>NEW:<br><br><span style=
=3D"font-family:monospace"><span>The longest PSD is the Organizational Doma=
in with one label removed.</span>  It names the immediate parent node of th=
e Organizational Domain in the DNS namespace tree.</span>
</span></pre><pre><span style=3D"font-family:arial,sans-serif">-MSK</span>
</pre>

</div></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--0000000000000b1c8c05b9400f73--


From nobody Tue Jan 19 06:03:01 2021
Return-Path: <todd.herr@valimail.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 6FB0F3A150C for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 06:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 kHp4CPQhBqkV for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 06:02:56 -0800 (PST)
Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9832A3A150A for <dmarc@ietf.org>; Tue, 19 Jan 2021 06:02:56 -0800 (PST)
Received: by mail-qv1-xf30.google.com with SMTP id h13so9156228qvo.1 for <dmarc@ietf.org>; Tue, 19 Jan 2021 06:02:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=d/FxCOi56OO/ryxKDzvslpsbpM1CGsMG3RPwxcKw9D8=; b=RnJx6LjS1+FT80HavIhymHaJvl8Ir7y+gU27oDysI4ROoETIRgNCEHGcPnVahB6J1L yOVdRlyNs3kGiztWByVQfF3rpSSC+aQmGmQJUp3kQMFA0ShAKjnRGi7Iv58oV93yvZOo zgmMv+oB66noorW4KnoUtDco0qgSiZULtC+WsL4qbj9hZHzdi0cn1d71BGkFy1SzYJw8 MT7ZtJrHho00nd0xK0rQj5mliYl2CjtiepVKo6Bu44PTxHAcitIYhKEKsl4DqJPj9kEv cJiyUiDtPzauKrW4hMJ2sID6Ak5vA4dd58IO/79eORWuNCwm8EQjvdX4GoFor2y5fs1H j0VA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=d/FxCOi56OO/ryxKDzvslpsbpM1CGsMG3RPwxcKw9D8=; b=Mk4lh5rSaC1Haya+AAZg/TcNpZyxt3xUq1WzhgvUrSPZyAG9jJA8Ac4YpAwnpu3Z0O PGCdEYOd7/e5zMwwfy2QvpauQ0h8r2onHTYy4eXcK0X+iAauSzMsATDqLi5c51q6slLZ OXxtZqygCndcl8eEm2xDPwAyzbE8m0JVaFzhiDPAxTB9jzf3DfqsevGk8ylARdc70aCn V4tXYODmjnAoGjOt1MX5YAphda6SJWVWcU+2fiM+xTReKzhCmwLcVJIG3ZeXvrUibLNu SFd2r8kyPVGQlRk2Kkf6uVBbznvgtbRPdDQtJDhlCXKbIF7OYWf1ZfHS7CfAyqqTnBbv 9WUw==
X-Gm-Message-State: AOAM530PBIsKDNbG3HAAU/PlpXV3NQwwpZ/qgm9xzW+q2+BDz69XGjoK sY9Im+KHiSnbhjn5kR9hxn3FnSX8D2t/RkoYVyp9TnxEswMDqA==
X-Google-Smtp-Source: ABdhPJz3cghtO+TUI0QoJgFqMEGi1i0GCZUXOqBrIqBTGfApZkfdTgMJijQIb96oXJxk83fTn7jpKJXEGBHSE0DLqi4=
X-Received: by 2002:a05:6214:c27:: with SMTP id a7mr367320qvd.54.1611064975305;  Tue, 19 Jan 2021 06:02:55 -0800 (PST)
MIME-Version: 1.0
References: <eb3d06f-c89f-2511-3528-d421473e4d42@taugh.com> <a67a4e98-2be0-e2e2-2595-c12d9b87c4df@taugh.com> <7d3be6c4-aa17-3c34-d8f0-4df51e46ccc1@tana.it> <f12991fe-fded-6c0-528c-3b879b4a670@taugh.com> <8b6605de-ca01-904c-de78-deae254e0891@tana.it>
In-Reply-To: <8b6605de-ca01-904c-de78-deae254e0891@tana.it>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 19 Jan 2021 09:02:39 -0500
Message-ID: <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000904d8f05b9414bb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/gH745Jr2hriRD0xiuWd7f85fVNw>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 19 Jan 2021 14:02:59 -0000

--000000000000904d8f05b9414bb5
Content-Type: text/plain; charset="UTF-8"

Picking up the thread on a ticket that was brought before the group
pre-holidays and has lain fallow since the end of 2020...

In reviewing the discussion, I don't believe a consensus has emerged on how
to implement this feature, or even whether to do it.

John proposed a new tag, ruap, for specifying HTTPS URIs (along with mailto:
and supposedly others that may be implemented in the future), while Ale
proposed different ways to express it in the existing rua tag.

Concerns were voiced about interoperability impacts for Ale's suggestions,
and Ale committed to running an experiment to see if there were changes to
his inbound report flows when he implemented one variant for expressing the
URI in the rua tag (     v=DMARC1; p=none; rua=mailto:local@example.com,
mailto:report@service.example, OR-https://service.example/report/;), but
there have been no subsequent posts by him to the list to report on results.

Other concerns were raised about privacy and security issues that might be
inherent in and unique to adding this kind of functionality, issues that
may not have been fully discussed or understood by the community over the
years. There was also a question about whether or not this is something
that people are asking for.

Hatless, it seems to me that the safest implementation of this feature,
presuming the security and privacy concerns can be addressed to the
satisfaction of those who raised them, would be to add a new tag, as John
has proposed, so as to minimize interoperability issues. I say "minimize",
rather than "avoid", simply because while RFC 7489 says "Unknown tags MUST
be ignored.", I don't believe we can say with 100% certainty that all
implementations of DMARC policy record parsing in the known world (both by
report generators and third parties who advise domains on how to publish
DMARC records), implementations that work now, won't "break" if a new tag
is introduced. Of course, that'd be their problem, not ours, because they
weren't following the existing rules.

As editor, I seek guidance from the working group on how to proceed here.

On Thu, Dec 31, 2020 at 11:35 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Thu 31/Dec/2020 16:37:38 +0100 John R Levine wrote:
> > On Thu, 31 Dec 2020, Alessandro Vesely wrote:
> >
> >> On Wed 30/Dec/2020 22:23:20 +0100 John R Levine wrote:
> >>> [ add ruap= to allow https in preference to mailto ]
> >>
> >> I still like better sticking to a unique tag (rua=) and applying
> OR-slashes.
> >> With a comma, it is backward compatible:
> >>
> >> v=DMARC1; p=none; rua=mailto:local@example.com, mailto:
> report@service.example, /https://service.example/report/;
> >
> > No, it's invalid according to the syntax in RFC 7489.
>
>
> I see.  We have:
>
>      dmarc-auri      = "rua" *WSP "=" *WSP
>                         dmarc-uri *(*WSP "," *WSP dmarc-uri)
>
>      URI             = scheme ":" hier-part [ "?" query ] [ "#" fragment ]
>
>      scheme      = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )
>
> So /https cannot be a scheme.  How about:
>
>      v=DMARC1; p=none; rua=mailto:local@example.com, mailto:
> report@service.example, OR-https://service.example/report/;
>
>
> > We have no idea what existing implementations do with DMARC records with
> syntax errors.
> >
> > Here's an experiment -- put that slash syntax in the rua= in your DMARC
> record
> > and see who does or doesn't continue sending reports.
>
>
> Done, with the second alternative.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000904d8f05b9414bb5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Picking up the thread on a ticket that was brought before =
the group pre-holidays and has lain fallow since the end of 2020...<div><br=
></div><div>In reviewing the discussion, I don&#39;t believe a consensus ha=
s emerged on how to implement this feature, or even whether to do it.</div>=
<div><br></div><div>John proposed a new tag, ruap, for specifying HTTPS URI=
s (along with mailto: and supposedly others that may be implemented in the =
future), while Ale proposed different ways to express it in the existing ru=
a tag.</div><div><br></div><div>Concerns were voiced about interoperability=
 impacts for Ale&#39;s suggestions, and Ale committed to running an experim=
ent=C2=A0to see if there were changes to his inbound report flows when he i=
mplemented one variant for expressing the URI in the rua tag (=C2=A0 =C2=A0=
 =C2=A0v=3DDMARC1; p=3Dnone; rua=3Dmailto:<a href=3D"mailto:local@example.c=
om" target=3D"_blank">local@example.com</a>, mailto:<a href=3D"mailto:repor=
t@service.example" target=3D"_blank">report@service.example</a>, OR-<a href=
=3D"https://service.example/report/" rel=3D"noreferrer" target=3D"_blank">h=
ttps://service.example/report/</a>;), but there have been no subsequent pos=
ts by him to the list to report on results.</div><div><br></div><div>Other =
concerns were raised about privacy and security issues that might be inhere=
nt in and unique to adding this kind of functionality, issues that may not =
have been fully discussed or understood by the community over the years. Th=
ere was also a question about whether or not this is something that people =
are asking for.</div><div><br></div><div>Hatless, it seems to me that the s=
afest implementation of this feature, presuming the=C2=A0security and priva=
cy concerns can be addressed to the satisfaction of those who raised them, =
 would be to add a new tag, as John has proposed, so as to minimize interop=
erability issues. I say &quot;minimize&quot;, rather than &quot;avoid&quot;=
, simply because while RFC 7489 says &quot;Unknown tags MUST be ignored.&qu=
ot;, I don&#39;t believe we can say with 100% certainty that all implementa=
tions of DMARC policy record parsing in the known world (both by report gen=
erators and third parties who advise domains on how to publish DMARC record=
s), implementations that work now, won&#39;t &quot;break&quot; if a new tag=
 is introduced. Of course, that&#39;d be their problem, not ours, because t=
hey weren&#39;t following the existing rules.</div><div><br></div><div>As e=
ditor, I seek guidance from the working group on how to proceed here.=C2=A0=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Thu, Dec 31, 2020 at 11:35 AM Alessandro Vesely &lt;<a href=3D"mai=
lto:vesely@tana.it">vesely@tana.it</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">On Thu 31/Dec/2020 16:37:38 +0100 John R =
Levine wrote:<br>
&gt; On Thu, 31 Dec 2020, Alessandro Vesely wrote:<br>
&gt; <br>
&gt;&gt; On Wed 30/Dec/2020 22:23:20 +0100 John R Levine wrote:<br>
&gt;&gt;&gt; [ add ruap=3D to allow https in preference to mailto ]<br>
&gt;&gt;<br>
&gt;&gt; I still like better sticking to a unique tag (rua=3D) and applying=
 OR-slashes. <br>
&gt;&gt; With a comma, it is backward compatible:<br>
&gt;&gt;<br>
&gt;&gt; v=3DDMARC1; p=3Dnone; rua=3Dmailto:<a href=3D"mailto:local@example=
.com" target=3D"_blank">local@example.com</a>, mailto:<a href=3D"mailto:rep=
ort@service.example" target=3D"_blank">report@service.example</a>, /<a href=
=3D"https://service.example/report/" rel=3D"noreferrer" target=3D"_blank">h=
ttps://service.example/report/</a>;<br>
&gt; <br>
&gt; No, it&#39;s invalid according to the syntax in RFC 7489.<br>
<br>
<br>
I see.=C2=A0 We have:<br>
<br>
=C2=A0 =C2=A0 =C2=A0dmarc-auri=C2=A0 =C2=A0 =C2=A0 =3D &quot;rua&quot; *WSP=
 &quot;=3D&quot; *WSP<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 dmarc-uri *(*WSP &quot;,&quot; *WSP dmarc-uri)<br>
<br>
=C2=A0 =C2=A0 =C2=A0URI=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D =
scheme &quot;:&quot; hier-part [ &quot;?&quot; query ] [ &quot;#&quot; frag=
ment ]<br>
<br>
=C2=A0 =C2=A0 =C2=A0scheme=C2=A0 =C2=A0 =C2=A0 =3D ALPHA *( ALPHA / DIGIT /=
 &quot;+&quot; / &quot;-&quot; / &quot;.&quot; )<br>
<br>
So /https cannot be a scheme.=C2=A0 How about:<br>
<br>
=C2=A0 =C2=A0 =C2=A0v=3DDMARC1; p=3Dnone; rua=3Dmailto:<a href=3D"mailto:lo=
cal@example.com" target=3D"_blank">local@example.com</a>, mailto:<a href=3D=
"mailto:report@service.example" target=3D"_blank">report@service.example</a=
>, OR-<a href=3D"https://service.example/report/" rel=3D"noreferrer" target=
=3D"_blank">https://service.example/report/</a>;<br>
<br>
<br>
&gt; We have no idea what existing implementations do with DMARC records wi=
th syntax errors.<br>
&gt; <br>
&gt; Here&#39;s an experiment -- put that slash syntax in the rua=3D in you=
r DMARC record <br>
&gt; and see who does or doesn&#39;t continue sending reports.<br>
<br>
<br>
Done, with the second alternative.<br>
<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Sr. Technical P=
rogram Manager</span></div><span style=3D"vertical-align:baseline;white-spa=
ce:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-align:lef=
t"><span style=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"v=
ertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" target=
=3D"_blank">todd.herr@valimail.com</a></span></div></span><span><div><span>=
<b>p:</b></span><span> 703.220.4153 </span><span></span></div></span><p dir=
=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-seri=
f;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin=
-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial=
;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;whit=
e-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfm=
T2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7=
n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; =
height: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(3=
4,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-=
color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><=
br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Ar=
ial"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email an=
d all data transmitted with it contains confidential and/or proprietary inf=
ormation intended solely for the use of individual(s) authorized to receive=
 it. If you are not an intended and authorized recipient you are hereby not=
ified of any use, disclosure, copying or distribution of the information in=
cluded in this transmission is prohibited and may be unlawful. Please immed=
iately notify the sender by replying to this email and then delete it from =
your system.</span></font></p></span></div>

--000000000000904d8f05b9414bb5--


From nobody Tue Jan 19 06:19:28 2021
Return-Path: <superuser@gmail.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 14E773A1525 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 06:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kh9h1b2TCBIQ for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 06:19:25 -0800 (PST)
Received: from mail-vk1-xa2b.google.com (mail-vk1-xa2b.google.com [IPv6:2607:f8b0:4864:20::a2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FFFF3A1522 for <dmarc@ietf.org>; Tue, 19 Jan 2021 06:19:25 -0800 (PST)
Received: by mail-vk1-xa2b.google.com with SMTP id d6so4805959vkb.13 for <dmarc@ietf.org>; Tue, 19 Jan 2021 06:19:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dqLekn2viQkG/DDFyozDnHafmJYMs/hycGW8Wg7JtbM=; b=eYYuXDGey+6Mu78vsB3iDTZL1/0sM/xVIDoSqq0vTopAz2b+QsL1Oj+ZP5eiL0BQdn 1nMLmKPP6on4/ACRdhu3D7UnuwlGN9G2OkExJmums9Zo0ypx+c2Z1YjJaTMYYGEetmlE v7PT3hCvgkSrjiQ9RQdfbUDAzVMarPIEBK2zpSu94y0uPckKM0CFnVIpB5TnOeVBQdWl tiL32FV51nYlnJa9I6h8y4IuonZwd9zPkmgnH7cxZ+zicw7Ca+Q5pdF2E+hBQIsi883E tw6t2lutuOpZ3QqxMj5pIF4tANpMLOyx2kGCfOyg4ksTciVHK/GNDJVLhFkSr342ZZCP xwVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dqLekn2viQkG/DDFyozDnHafmJYMs/hycGW8Wg7JtbM=; b=Z1I1Tmzg3QRYG30FS5A8lXN3Fgg88SM0fQwMyStY47Wr+AkpA8M+AJGpKw5pa/N5iw 9Zc/dSNbAc9oH/OU1gzoBvTLlZouDALtjknFwfsXID/o00OvUcsp4bwdeS9owXSGemCN fdVnqtkIwIDYjwVnNymGEbTEYpCxZtSzIsPvJeHOE+Qr1lcwePaYhO7Wdu2/dxJgkSKC yYENn42CdHeEZ/Q+zXOoZ0erL+XRvrsoe21jhGDaMzKymCpEqzQF1i9AHCYuFkeRDFDj Gl044woDyk3k8N9VnOJgOnvpKWH+2cVyFvbhMz1GG/gZtkFx4W5736thSxpCL6LzNo8Y eiUg==
X-Gm-Message-State: AOAM530oKw1jYOocAOYd83F5MThV8ka7i6mGtgHoWs/IZ1aq52tq2ks3 zuNuUqhMt5bVfcAgNTa5ZrAQWmPeBBDdYfhBakpSo/cPu/c=
X-Google-Smtp-Source: ABdhPJyEE2i4h3pDdwGzR2HN6+MiR3MT+eVMP5ZtzEDoWi9/ZjNNFSWLRzctwVLcNXkymuUTmYcFe0MYBMdAN9pMIjE=
X-Received: by 2002:a1f:3889:: with SMTP id f131mr2642477vka.22.1611065963981;  Tue, 19 Jan 2021 06:19:23 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it>
In-Reply-To: <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 19 Jan 2021 06:19:11 -0800
Message-ID: <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007e32b805b941860c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/F7Go6Oyj815Id9YQR9L2yI5CiCw>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 19 Jan 2021 14:19:27 -0000

--0000000000007e32b805b941860c
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 19, 2021 at 2:31 AM Alessandro Vesely <vesely@tana.it> wrote:

> I guess "[this document]" refers to the RFC number to be.  I think it's
> useless
> and can be safely removed, all of the five occurrences of it.
>

That's fine too.

>> I believe that my strongest critique was that section 1 is difficult to
> >> understand if one does not already understand DMARC, and it does not
> >> seem that the section has been revised.  Re-reading it, I notice that it
> >> says "DMARC leverages public suffix lists to determine which domains are
> >> organizational domains."  [...]
>
> In fact, those are the two terms appearing in the title.  BTW, I'd change
> the
> title to:
>
>      Domain-based Message Authentication, Reporting, and Conformance
> (DMARC)
>      Extension For Public Suffix Domains (PSDs)
>
> Anyway, I agree it is correct to introduce /both/ terms.
>

I think that's needlessly verbose.  A compromise:

"Experimental DMARC Extension for Public Suffix Domains"

>     To determine the organizational domain for a message under evaluation,
> >     and thus where to look for a policy statement, DMARC makes use of a
> >     Public Suffix List.
> >     The process for doing this can be found in Section 3.2 of the DMARC
> >     specification.
>
> Couldn't we skip that kind of functional intro and say something general,
> such
> as anticipating Section 2.2:
>
>      Public Suffix Domains (PSDs) are domain names publicly accessible for
>      domain registration.  As explained in Section 2.2, they include all
> top
>      level domains and some more.  The way delegations occur on the global
>      Internet makes it difficult to establish whether a domain is a PSD.  A
>      community maintained Public Suffix List (PSL) exists for that purpose.
>
> Thinking twice, perhaps we don't need to introduce the PSL until Section
> 3.4.
> In that case, strike the last two sentences of the above paragraph.
>

It's not obvious to me that this is better, but sure, let's discuss it.

>     DMARC as specified presumes that domain names present in a PSL are not
> >     organizational domains and thus not subject to DMARC processing;
> domains
> >     are either organizational domains, sub-domains of organizational
> >     domains, or listed on a PSL.  For domains listed in a
> >     PSL, i.e., TLDs and domains that exist between TLDs and
> >     organization level domains, policy can only be published for the
> >     exact domain.
>
> That's still overly specific for an introduction.  It only serves to
> present
> the concept that there are domains that are not actually organizational
> domains
> but are characterized by a sort of organizational flavor.  The "these
> domains"
> of the following sentence.  We don't need seven lines of text for that.
>

This is text in -09, not something I'm adding.  Apparently this context was
valuable before.

>> Looking at the second paragraph of section 1, I notice that despite all
> >> the special terms for classifying domain names in section 2, the example
> >> in this section does not describe which of the domain names that it
> >> mentions fall into which of these classes.  E.g. "tax.gov.example" is
> >> said to be registered, but it looks like it is also the organizational
> >> domain, and "gov.example" is its longest PSD.  It would also help to
> >> mention that "tax.gov.example" is "registered at" "gov.example" to
> >> introduce the details of the usage "registered at".
> >>
> >>     Suppose there exists a domain "tax.gov.example" (registered at
> >>     "gov.example") ...
> >>
> >
> > Introduce a new Section 1.1: "Example" with this:
>
> I don't fully agree.  The example only lasts until the end of page 3.
> From
> page 4 on, the text describes the core of the experiment, so it shouldn't
> be
> under an "Example" heading.  If we skip the PSL, the example remains quite
> compact even after adding those "registered at".
>

I don't think you read my suggestion correctly.  I proposed a new Section
1.2 to contain the text you're talking about.  You cited it below but
appear to have missed it.

> A suggestion for 2.4:
> >
> > NEW:
> >
> > The longest PSD is the Organizational Domain with one label removed.
> > It names the immediate parent node of the Organizational Domain in the
> > DNS namespace tree.
>
> s/one/the leftmost/
>

Sure.

-MSK

--0000000000007e32b805b941860c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 19, 2021 at 2:31 AM Alessandr=
o Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote=
:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">I guess &quot;[this document]&quot; refers to the RFC number t=
o be.=C2=A0 I think it&#39;s useless <br>
and can be safely removed, all of the five occurrences of it.<br></blockquo=
te><div><br></div><div>That&#39;s fine too.</div><div> <br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">
&gt;&gt; I believe that my strongest critique was that section 1 is difficu=
lt to<br>
&gt;&gt; understand if one does not already understand DMARC, and it does n=
ot<br>
&gt;&gt; seem that the section has been revised.=C2=A0 Re-reading it, I not=
ice that it<br>
&gt;&gt; says &quot;DMARC leverages public suffix lists to determine which =
domains are<br>
&gt;&gt; organizational domains.&quot;=C2=A0 [...]<br>
<br>
In fact, those are the two terms appearing in the title.=C2=A0 BTW, I&#39;d=
 change the <br>
title to:<br>
<br>
=C2=A0 =C2=A0 =C2=A0Domain-based Message Authentication, Reporting, and Con=
formance (DMARC)<br>
=C2=A0 =C2=A0 =C2=A0Extension For Public Suffix Domains (PSDs)<br>
<br>
Anyway, I agree it is correct to introduce /both/ terms.<br></blockquote><d=
iv><br></div><div>I think that&#39;s needlessly verbose.=C2=A0 A compromise=
:<br><br></div><div>&quot;Experimental DMARC Extension for Public Suffix Do=
mains&quot;</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex">&gt;=C2=A0 =C2=A0 =C2=A0To determine the organizational domain for a=
 message under evaluation,<br>
&gt;=C2=A0 =C2=A0 =C2=A0and thus where to look for a policy statement, DMAR=
C makes use of a<br>
&gt;=C2=A0 =C2=A0 =C2=A0Public Suffix List.<br>
&gt;=C2=A0 =C2=A0 =C2=A0The process for doing this can be found in Section =
3.2 of the DMARC<br>
&gt;=C2=A0 =C2=A0 =C2=A0specification.<br>
<br>
Couldn&#39;t we skip that kind of functional intro and say something genera=
l, such <br>
as anticipating Section 2.2:<br>
<br>
=C2=A0 =C2=A0 =C2=A0Public Suffix Domains (PSDs) are domain names publicly =
accessible for<br>
=C2=A0 =C2=A0 =C2=A0domain registration.=C2=A0 As explained in Section 2.2,=
 they include all top<br>
=C2=A0 =C2=A0 =C2=A0level domains and some more.=C2=A0 The way delegations =
occur on the global<br>
=C2=A0 =C2=A0 =C2=A0Internet makes it difficult to establish whether a doma=
in is a PSD.=C2=A0 A<br>
=C2=A0 =C2=A0 =C2=A0community maintained Public Suffix List (PSL) exists fo=
r that purpose.<br>
<br>
Thinking twice, perhaps we don&#39;t need to introduce the PSL until Sectio=
n 3.4. <br>
In that case, strike the last two sentences of the above paragraph.<br></bl=
ockquote><div><br></div><div>It&#39;s not obvious to me that this is better=
, but sure, let&#39;s discuss it.</div><div> <br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">
&gt;=C2=A0 =C2=A0 =C2=A0DMARC as specified presumes that domain names prese=
nt in a PSL are not<br>
&gt;=C2=A0 =C2=A0 =C2=A0organizational domains and thus not subject to DMAR=
C processing; domains<br>
&gt;=C2=A0 =C2=A0 =C2=A0are either organizational domains, sub-domains of o=
rganizational<br>
&gt;=C2=A0 =C2=A0 =C2=A0domains, or listed on a PSL.=C2=A0 For domains list=
ed in a<br>
&gt;=C2=A0 =C2=A0 =C2=A0PSL, i.e., TLDs and domains that exist between TLDs=
 and<br>
&gt;=C2=A0 =C2=A0 =C2=A0organization level domains, policy can only be publ=
ished for the<br>
&gt;=C2=A0 =C2=A0 =C2=A0exact domain.<br>
<br>
That&#39;s still overly specific for an introduction.=C2=A0 It only serves =
to present <br>
the concept that there are domains that are not actually organizational dom=
ains <br>
but are characterized by a sort of organizational flavor.=C2=A0 The &quot;t=
hese domains&quot; <br>
of the following sentence.=C2=A0 We don&#39;t need seven lines of text for =
that.<br></blockquote><div><br></div>This is text in -09, not something I&#=
39;m adding.=C2=A0 Apparently this context was valuable before.<br></div><d=
iv class=3D"gmail_quote"><br></div><div class=3D"gmail_quote"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">&gt;&gt; Looking at the second paragra=
ph of section 1, I notice that despite all<br>
&gt;&gt; the special terms for classifying domain names in section 2, the e=
xample<br>
&gt;&gt; in this section does not describe which of the domain names that i=
t<br>
&gt;&gt; mentions fall into which of these classes.=C2=A0 E.g. &quot;tax.go=
v.example&quot; is<br>
&gt;&gt; said to be registered, but it looks like it is also the organizati=
onal<br>
&gt;&gt; domain, and &quot;gov.example&quot; is its longest PSD.=C2=A0 It w=
ould also help to<br>
&gt;&gt; mention that &quot;tax.gov.example&quot; is &quot;registered at&qu=
ot; &quot;gov.example&quot; to<br>
&gt;&gt; introduce the details of the usage &quot;registered at&quot;.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0Suppose there exists a domain &quot;tax.gov.exa=
mple&quot; (registered at<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0&quot;gov.example&quot;) ...<br>
&gt;&gt;<br>
&gt; <br>
&gt; Introduce a new Section 1.1: &quot;Example&quot; with this:<br>
<br>
I don&#39;t fully agree.=C2=A0 The example only lasts until the end of page=
 3.=C2=A0 From <br>
page 4 on, the text describes the core of the experiment, so it shouldn&#39=
;t be <br>
under an &quot;Example&quot; heading.=C2=A0 If we skip the PSL, the example=
 remains quite <br>
compact even after adding those &quot;registered at&quot;.<br></blockquote>=
<div><br></div><div>I don&#39;t think you read my suggestion correctly.=C2=
=A0 I proposed a new Section 1.2 to contain the text you&#39;re talking abo=
ut.=C2=A0 You cited it below but appear to have missed it.<br></div><div> <=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">&gt; A suggestio=
n for 2.4:<br>
&gt; <br>
&gt; NEW:<br>
&gt; <br>
&gt; The longest PSD is the Organizational Domain with one label removed.<b=
r>
&gt; It names the immediate parent node of the Organizational Domain in the=
<br>
&gt; DNS namespace tree.<br>
<br>
s/one/the leftmost/<br></blockquote><div><br></div><div>Sure.</div><div><br=
></div><div>-MSK<br></div></div></div>

--0000000000007e32b805b941860c--


From nobody Tue Jan 19 06:24:00 2021
Return-Path: <superuser@gmail.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 8ACD73A1369 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 06:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 c6QGKa8oWrrp for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 06:23:57 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E87FF3A1368 for <dmarc@ietf.org>; Tue, 19 Jan 2021 06:23:56 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id w187so10145420vsw.5 for <dmarc@ietf.org>; Tue, 19 Jan 2021 06:23:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=go2s4LxCou9DlB6AqDaK+1RHTUeFtCAqQ5BKz3C2rm0=; b=foRx5M/VGgOnzf1OtL/sPGsKuw4tmklIAtbRl0eHRSthHHNa6nNiuT1M/vhE9OtBTz 5c8rwr2ET+zk+1geL5NAukxrRU8XguxGYRY7A9pp5H/WAdjY832SBannmwXAqdbA1S72 OWD55KxyCkJVdp/0d7PVFwQnPSN3btFFYc0rh85y+7hh2wCTyyIesTWy7aGtEBOad2rk ynh1mCw+ZYPgOKbIUiFwp7n4EQg2qIiRzIw90Vvob3ZOOaMoVv9qUabtJWfXGhgl2ECC 6s4r33QRikrrSM1BL4ELc3lIbIYcz2UAMVTNUpt4GPVhAUHzAzkgI/UZQblD1DSrkKmC KoHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=go2s4LxCou9DlB6AqDaK+1RHTUeFtCAqQ5BKz3C2rm0=; b=cughVsyHrqvBWHSpS+wfbp4g8kAfsjvp9Xq4S3zzyCWci705p4RlnkIUnNSp5TQXNB TyeD+GSXtHTMK3IcN3V6XDKMeAJ1oDaDtSUt1YbvYOSYliS7B+ulMMsNHz78tV7NVouC n5Cs3DAECARk6GgroVksgYsPpcGz6Xcn8lbgCDD0buhLU5PBZv0siMmIILnmEc3eeTWs 5HgzKOQ6okYe4eftsOV5l2At5WDWuntHu3f1LobKiwaKUmU+tco9Jvf0pSXnHvWcTEez qb8EBkMDuJgue1qvnRBk3/0nMlxX7pmeeyY1IhLY7dIG5d7NqRaTB9THKHkLkAUTKCc8 hdeg==
X-Gm-Message-State: AOAM530IJWTROcZkca/Qvp6IN57mMDKYefzRSJgKohHXAqo9AEJ48tFs jPzeR9vzvmRkGRZ9tWo4MJf8H8Zt2WQyzaNbQmk=
X-Google-Smtp-Source: ABdhPJxi4U4wWI3bBgo4pp7nu/usPQv78UyZrLTKRq0bt4VHQgANWrBfGohbeQjMFOR7uledodguW7Uy4Fw1lCL3YL0=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr2692140vsy.54.1611066235795;  Tue, 19 Jan 2021 06:23:55 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <CAH48ZfwOdZcJz02a76wktQDpV_dpPHKw+qJjE2ZCDvOqF3Ptdw@mail.gmail.com>
In-Reply-To: <CAH48ZfwOdZcJz02a76wktQDpV_dpPHKw+qJjE2ZCDvOqF3Ptdw@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 19 Jan 2021 06:23:42 -0800
Message-ID: <CAL0qLwZf+tEGZj0T6UmaNBSMC-nqSpfb5DAFh8+GDuP6F5pRkQ@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="000000000000b1bdaf05b94196fb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xvi7McA00l177dgvVyj0yF_yfmU>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 19 Jan 2021 14:23:59 -0000

--000000000000b1bdaf05b94196fb
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 19, 2021 at 4:34 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> I raised objections to the definition of "non-existent", which never
> received an adequate response before the discussion went silent.
>
> DMARC checks the From  header address, which may exist only as an
> identifier used for mass mailings.   These mailings are often sent by an
> ESP using an unrelated SMTP address.    As such, the From address need not
> be associated with any A, AAAA, or MX record.    I assert that the only
> viable definition of non-existent is "not registered", as evidenced by
> absence of an NS record.
>

This is a discussion of DMARC, not of PSD, right?  DMARC defines this test
in an Appendix, and then makes it non-mandatory.  PSD says to apply that
test for domains that request it.

Hooking this test up to registration requires introducing RDAP or something
similar.  Is that what we're talking about here?

I don't believe the proposed definition of "non-existent" is reliably true
> even in the special case of interest for this document, impersonation fraud
> occurring at the top of an organizational structure.  Example.PSD may
> legitimately use mail.Example.PSD for email and www.example.psd for web.
>  If the proposed condition MUST always be true, I have not seen that fact
> demonstrated.   Since the document raises a general concern about
> fraudulent use of non-existent domains, the definition used should be one
> that can be generalized.,
>

This sounds like something that should be solved in DMARC, not PSD, but
naturally consensus wins here, so have at it.

-MSK

--000000000000b1bdaf05b94196fb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 19, 2021 at 4:34 AM Douglas F=
oster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfoster=
.emailstandards@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">I rais=
ed objections to the definition of &quot;non-existent&quot;, which never re=
ceived an adequate response before the discussion went silent.=C2=A0 =C2=A0=
=C2=A0<div><br></div><div>DMARC checks the From=C2=A0 header address, which=
 may exist only as an identifier used for mass mailings.=C2=A0 =C2=A0These =
mailings are often sent by an ESP using an unrelated=C2=A0SMTP address.=C2=
=A0 =C2=A0 As such, the From address need not be associated with any A, AAA=
A, or MX record.=C2=A0 =C2=A0 I assert that the only viable definition of n=
on-existent is &quot;not registered&quot;, as evidenced by absence of an NS=
 record.</div></div></blockquote><div><br></div><div>This is a discussion o=
f DMARC, not of PSD, right?=C2=A0 DMARC defines this test in an Appendix, a=
nd then makes it non-mandatory.=C2=A0 PSD says to apply that test for domai=
ns that request it.</div><div><br></div><div>Hooking this test up to regist=
ration requires introducing RDAP or something similar.=C2=A0 Is that what w=
e&#39;re talking about here?<br></div><div> <br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr"><div><div>I don&#39;t believe=
 the proposed definition of &quot;non-existent&quot; is reliably true even =
in the special case of interest for this document, impersonation fraud occu=
rring at the top of an organizational structure.=C2=A0 Example.PSD may legi=
timately use mail.Example.PSD for email and www.example.psd for web.=C2=A0 =
=C2=A0If the proposed condition MUST always be true, I have not seen that f=
act demonstrated.=C2=A0 =C2=A0Since the document raises a general concern a=
bout fraudulent use of non-existent domains, the definition used should be =
one that can be generalized.,</div></div></div></blockquote><div><br></div>=
<div>This sounds like something that should be solved in DMARC, not PSD, bu=
t naturally consensus wins here, so have at it.</div><div><br></div><div>-M=
SK<br></div></div></div>

--000000000000b1bdaf05b94196fb--


From nobody Tue Jan 19 07:27:52 2021
Return-Path: <hsantos@isdg.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 837803A1631 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 07:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 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.262, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=gcY+ghZH; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=JzGPZ5Bu
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 QpQKpciAVpFe for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 07:27:46 -0800 (PST)
Received: from mail.winserver.com (news.winserver.com [76.245.57.69]) (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 04F923A1638 for <dmarc@ietf.org>; Tue, 19 Jan 2021 07:27:40 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; l=8045; t=1611070057; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=KVzpyTnrR+ziQ1IZ7tyTt+cxSJUz xI46oP3Umr1A8wg=; b=gcY+ghZHqjmbHXiNZVu9WB/wEqxxtJxLke7inqyGrzip kEoi1/XAtNUykoFPoXiyevdZqS8iNhbJPfb63t6vSkLGQLRD7SkwhuAkzUxQGPLi IFm1ELW7gj1NJRwQZxRk02Dw/NLhcwo/QuilQsSibPiAacvwlB0DfPIBLctM7ss=
Received: by mail.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Tue, 19 Jan 2021 10:27:37 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  dmarc=pass policy=reject author.d=isdg.net signer.d=beta.winserver.com (atps signer); 
Received: from beta.winserver.com ([76.245.57.74]) by mail.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 215133448.1.2164; Tue, 19 Jan 2021 10:27:36 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=8045; t=1611069649; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=KVzpyTn rR+ziQ1IZ7tyTt+cxSJUzxI46oP3Umr1A8wg=; b=JzGPZ5BuqEyuvGcYS0azdvj JiABeVKLt165MdZI6XPCxeJ9lVKgrWKQDhuPEz3noAD9h7mfdKCNq5RlJQm2ld93 8bC6Z2EbVVuK6/Mc5rNXXgLUfE2IzSzzR1GGx6Ic96u9SPug+ZGeeiNqlf2pThvO 82dixpx2ngfs0sl+psCM=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Tue, 19 Jan 2021 10:20:49 -0500
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 81986502.1.60628; Tue, 19 Jan 2021 10:20:48 -0500
Message-ID: <6006FA69.5000702@isdg.net>
Date: Tue, 19 Jan 2021 10:27:37 -0500
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>,  IETF DMARC WG <dmarc@ietf.org>
References: <eb3d06f-c89f-2511-3528-d421473e4d42@taugh.com> <a67a4e98-2be0-e2e2-2595-c12d9b87c4df@taugh.com> <7d3be6c4-aa17-3c34-d8f0-4df51e46ccc1@tana.it> <f12991fe-fded-6c0-528c-3b879b4a670@taugh.com> <8b6605de-ca01-904c-de78-deae254e0891@tana.it> <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com>
In-Reply-To: <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/W5rQ7xg-ik7WUVSvIoAj4l0kr_I>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 19 Jan 2021 15:27:51 -0000

On 1/19/2021 9:02 AM, Todd Herr wrote:>
> Other concerns were raised about privacy and security issues that
> might be inherent in and unique to adding this kind of functionality,
> issues that may not have been fully discussed or understood by the
> community over the years. There was also a question about whether or
> not this is something that people are asking for.

Reporting concepts were in the each DKIM Policy proposal (SSP, DSAP, 
ADSP) -- a "-r" tag option to send reports. The main concerns were 
unsolicited report abuse.   The DSAP proposal (my own) recognize it 
could be optional so it provided:

    https://tools.ietf.org/html/draft-santos-dkim-dsap-00	

    4.5.  DSAP Tag: r=<abuse-address>

    This tag is optional.  If not defined, the default is no abuse-
    address is available.

    <abuse-address> is either the user-part or a FQDN email address to
    optional send abuse reports.

    Examples:
       r=abuse
       r=abuse@example.com

    If only the user-part is defined, then the full address is
    established by using the originating address domain.

    DKIM verifiers have the option to honor or not honor this reporting
    address.  DKIM signers MUST be aware this reporting address may not
    be utilized by verifiers.

    Verifiers should be aware this reporting address can be a source of
    an report attack vector (Section 7.4).  One possible implementation
    considerations would to limit the report to one report only and to
    track the reception and/or response of the reporting.


but the Section 7.4 discussion was TBD.


>
> Hatless, it seems to me that the safest implementation of this
> feature, presuming the security and privacy concerns can be addressed
> to the satisfaction of those who raised them, would be to add a new
> tag, as John has proposed, so as to minimize interoperability issues.
> I say "minimize", rather than "avoid", simply because while RFC 7489
> says "Unknown tags MUST be ignored.", I don't believe we can say with
> 100% certainty that all implementations of DMARC policy record parsing
> in the known world (both by report generators and third parties who
> advise domains on how to publish DMARC records), implementations that
> work now, won't "break" if a new tag is introduced. Of course, that'd
> be their problem, not ours, because they weren't following the
> existing rules.

We can not continue to design Internet protocols without upward design 
considerations. This is part of the forward and backward compatibility 
design concepts.  Any problem would be a known tag with new 
functionality than originally expected. Sure, we can't say it will not 
happen, but its going to be a very low percentage, if any.  They have 
to fix it.

> As editor, I seek guidance from the working group on how to proceed here.

I am for a URI protocol method as part of the current tag rather than 
a new a separate tag.

However, in principle, I don't see any issue with adding new tags, in 
fact, I am still here on the basis extended protocols will emerged 
once the base protocol is completed.  ATPS will be available to 
piggyback off the DMARC record as it did off ADSP.  The ATPS protocol 
adds "atps=y" tag to the DMARC record.  We have never received reports 
of issues related to extended tags.

There is a also a small scale version called ASL (Authorized Signer 
List) tag which defines a few domains authorized as resigners; for 
example:

asl=example1.com, example2.com, ietf.org, gmail.com

If you believe that adding a new tag is going to be a problem for 
DMARC, then we might as well come up with a new DKIM Policy model and 
a new resource record lookup name.

Imo, you guys are really missing the boat here.  Extended tags is a 
major part of a DKIM POLICY model future simply because we have not 
yet imagine all the needs to make it work well and integrate with 
other concepts.  In DSAP, for example, we had tags such as:

+============================================================+
| Description            |  DSAP Record Tag                  |
|============================================================|
| Version tag            |  v=<dsap-version>/<dkim-version>  |
|------------------------------------------------------------|
| Original party signing |  op=<signing-policy>              |
| practice               |                                   |
|------------------------------------------------------------|
| 3rd party signing      |  3p=<signing-policy>              |
| practice               |                                   |
|------------------------------------------------------------|
| Authorized List of     |  dl=<dom-list>                    |
| 3rd party domains      |                                   |
|------------------------------------------------------------|
| Signature Hashing      |  a=<hash-algorithm>               |
| Method                 |                                   |
|------------------------------------------------------------|
| Reporting address      |  r=<abuse-address>                |
|------------------------------------------------------------|
| Note or comment        |  n=<note>                         |
|------------------------------------------------------------|
| Testing flag           |  t=<testing-flag>                 |
|------------------------------------------------------------|
| Unauthorized signature |  fa=<failure-handling>            |
| failure handling       |                                   |
|------------------------------------------------------------|
| Invalid Signature      |  fs=<failure-handling>            |
| failure handling       |                                   |
|------------------------------------------------------------|
| Signature Expiration   |  fx=<failure-handling>            |
| failure handling       |                                   |
+------------------------------------------------------------+

The optional note tag (n=) allows a domain to store a human readable 
note or comment regarding the DSAP DNS record.  Its purpose is 
considered to be diagnostic in nature.

The fa=, fs= and fx= tags were based on discussion to offer specific 
handling instructions based on specific possible errors:

4.8.  DSAP Tags: fa=<failure-handling>; fs=<failure-handling>;
       fx=<failure-handling>;

    The fa=, fs, and fx= tags define the domain preferred rejection
    action policy a verifier is recommended to perform when an
    unauthorized signature, failed signature or expired signature is
    detected, respectively.

    The fa= tag defines the handling for failed signature authorization.
    The fs= tag defines the handling for failed signature verfication,
    and the fx= tag defines the handling when a signature expired or key
    is revoked.

    Failed signature include failures related to the DKIM-Signature
    hashing, syntax and encryption verification process.

    <failure-handling> values:

    FAIL                The verifer MUST reject the transaction when
                        failure is detected.  (Default)

    SOFTFAIL            The verifer SHOULD reject the transaction when
                        failure is detected.

    IGNORE              The verifer SHOULD NOT reject the transaction
                        when failure is detected.  This value may be
                        defined by the domain to signify the domain is
                        testing DKIM and failure may occur unexpectedly.
                        Verifiers SHOULD consider tracking this handler
                        value for abuse.

    The fa= and fs= tags are optional with default values of SOFTFAIL.

    Examples:

    fa=fail;fs=fail; fx=fail;  Domain has a MUST reject immediate policy
                        for unauthorized, failed or expired signatures.

    fa=fail;            Domain has a MUST reject immediate policy for
                        unauthorized signatures and a SHOULD reject
                        immediate policy for failed and expired
                        signatures.

    undefined values;   DOMAIN has a SHOULD reject immediate policy for
                        all failures.

    fs=fail;  fx=fail;  Domain has a SHOULD reject immediate policy for
                        unauthorized signatures and a MUST reject
                        immediate policy for failed and expired
                        signatures.


My point is simple, extended tags MUST be part of the protocol's 
extendability. If there is evidence with 100% sureness there going to 
be a significant compatibility problem with legacy software that can 
not be corrected, then the only option is a new DMARC version 2 
resource record.

I don't think we (I know I can't) can continue with DMARCbis without 
Extended Tag support and be hesitant to invent them because there is a 
compatibility problem.


-- 
Hector Santos,
https://secure.santronics.com
https://twitter.com/hectorsantos



From nobody Tue Jan 19 11:18:35 2021
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 865173A16E8 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:18:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 o0GjuwN6Plhk for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:18:33 -0800 (PST)
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 D79263A16E3 for <dmarc@ietf.org>; Tue, 19 Jan 2021 11:18:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611083908; bh=cQwZLF/PhhTGFz5Dz2Iolt64B0Mvr4WLYnZuKBSyKPM=; l=569; h=To:References:From:Date:In-Reply-To; b=CptSdF3M9TbPXV4m+OuJWDSTiKF60quaIpcEGej8c2jSGTLzsezqxNbrVQyNCLVJS qS6jTTq5XjrpYFMSka/CUQSb4xgV4NqnaTaEycmFPS4IwYEL1x2t9uSkPln+tqWn9Z JXtcgrsYA9VBjnYQtZ3256zaBoUC79/T6/AUwFtKhM+T4mpPYVPXmdzA+0BMv
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC056.0000000060073084.00005DAF; Tue, 19 Jan 2021 20:18:28 +0100
To: Todd Herr <todd.herr@valimail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <eb3d06f-c89f-2511-3528-d421473e4d42@taugh.com> <a67a4e98-2be0-e2e2-2595-c12d9b87c4df@taugh.com> <7d3be6c4-aa17-3c34-d8f0-4df51e46ccc1@tana.it> <f12991fe-fded-6c0-528c-3b879b4a670@taugh.com> <8b6605de-ca01-904c-de78-deae254e0891@tana.it> <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <d7b0a494-e9f8-4765-2b47-65d299305b41@tana.it>
Date: Tue, 19 Jan 2021 20:18:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@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/RcGF_4msY6m-bf2rJ09xKh3ax2I>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 19 Jan 2021 19:18:35 -0000

On Tue 19/Jan/2021 15:02:39 +0100 Todd Herr wrote:
> Concerns were voiced about interoperability impacts for Ale's suggestions,
> and Ale committed to running an experiment to see if there were changes to
> his inbound report flows when he implemented one variant for expressing the
> URI in the rua tag (v=DMARC1; p=none; rua=mailto:local@example.com, 
> mailto:report@service.example, OR-https://service.example/report/;), but
> there have been no subsequent posts by him to the list to report on
> results.


It seems to work perfectly.


Best
Ale
-- 





















From nobody Tue Jan 19 11:22:24 2021
Return-Path: <todd.herr@valimail.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 095883A16F4 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 cFjhJWuiwwIh for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:22:20 -0800 (PST)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FBAF3A16F1 for <dmarc@ietf.org>; Tue, 19 Jan 2021 11:22:20 -0800 (PST)
Received: by mail-qv1-xf2b.google.com with SMTP id a1so9692607qvd.13 for <dmarc@ietf.org>; Tue, 19 Jan 2021 11:22:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=RbHjtd694Q0NMR50bm+GNLE4emNDyDFx/3m5xYBb8XU=; b=LxzH0HvUHoleg2MpkOy1ORRfza9v9ynEhm/IbWUsIK1gRViUss7x271aXaO1fj8Tn4 WHDMGtpVAb2WFqZK8T3fbqc2qYcKjozTpwHX3B9DtFTPNvKdmDq+P5qg1EvYv+UiWOZv rEKZB5oAqBuS5HW5muDXmFTfT2qmbBeblZJMR47tFY2/YBnsXADaZriGG/4LKCmK7cT2 LPv2uKdkrsRI4HBptLdEustP5amnTC30Umh96D2Bz4NuYrnyr+KuIHRH9IjMMDvTlV3/ YN/4Hrpn7i5lSF18GjhKzS7uOIVAVCnhjtuUZeLKzDhaU9EEOHnr2LgspINgFRy7mVtT pR4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=RbHjtd694Q0NMR50bm+GNLE4emNDyDFx/3m5xYBb8XU=; b=DaTuJtsN0DmW5iHlIQUR2PTdH1+h/pHdEMUtLaTPPcIo3+Ytnw6DC+j5/bBPL6J9Na Gm2Nj2MOTupnKElA8zxY6rrU1UozxGZj0eEnSEsM7iWSj/9Ky/Qqht7ooRA8Y1ojnf2s SVDoN65k9WiGktPtuPSgfuc/x/K0vJVG9pf476g0QvZZAMC1hDgAm5kFpFNCWq95W+ov 9u/V/Rs1A90Ymdvab/kIUac4cn67mxRfaFS/+qS9NC7RKHtOkls0iRdciDAe3F8D4j6R 8UEglQZ0478+eGZzMomNppa6yWYwg97K5xOByCsc4j62lZWWGw/iJpWeB++IcHrROcQL WyQg==
X-Gm-Message-State: AOAM532UGIF3vJfFeCnqHgQY8uCjCDHPa38cWSh6kjLjWypDpTdY18yE 8lO0CSeCySLXcZvwne9kLRas0It0N0U5BSUi18ztdErxSfrQHg==
X-Google-Smtp-Source: ABdhPJz9ZASYLFbIivEhg+jVSoHuinw8TROCgYiiDuaSyhoYO0NDMYG/cR6jOQBS9E90VOCgrX01uYh2S+EX4bPE3bc=
X-Received: by 2002:a05:6214:c27:: with SMTP id a7mr1830440qvd.54.1611084139175;  Tue, 19 Jan 2021 11:22:19 -0800 (PST)
MIME-Version: 1.0
References: <eb3d06f-c89f-2511-3528-d421473e4d42@taugh.com> <a67a4e98-2be0-e2e2-2595-c12d9b87c4df@taugh.com> <7d3be6c4-aa17-3c34-d8f0-4df51e46ccc1@tana.it> <f12991fe-fded-6c0-528c-3b879b4a670@taugh.com> <8b6605de-ca01-904c-de78-deae254e0891@tana.it> <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com> <6006FA69.5000702@isdg.net>
In-Reply-To: <6006FA69.5000702@isdg.net>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 19 Jan 2021 14:22:03 -0500
Message-ID: <CAHej_8=BJPezpi2KZ7GX-N__4Fqfc_b8vFNhu7_Typakv4iMig@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d1c25005b945c1e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/bq5FexuoLCSr3InOdlOGjjZN_ys>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 19 Jan 2021 19:22:23 -0000

--000000000000d1c25005b945c1e3
Content-Type: text/plain; charset="UTF-8"

It seems that I was not successful in conveying my meaning in a few
statements, so allow me to try again...


On Tue, Jan 19, 2021 at 10:28 AM Hector Santos <hsantos=
40isdg.net@dmarc.ietf.org> wrote:

> On 1/19/2021 9:02 AM, Todd Herr wrote:>
> > Other concerns were raised about privacy and security issues that
> > might be inherent in and unique to adding this kind of functionality,
> > issues that may not have been fully discussed or understood by the
> > community over the years. There was also a question about whether or
> > not this is something that people are asking for.
>
> Reporting concepts were in the each DKIM Policy proposal (SSP, DSAP,
> ADSP) -- a "-r" tag option to send reports. The main concerns were
> unsolicited report abuse.   The DSAP proposal (my own) recognize it
> could be optional so it provided:
>

My mention of "other concerns ... about privacy and security" is in
reference to a post in this thread that Mike Hammer made in early December,
where he wrote:

"I don't recall a strong security and privacy concerns discussion around
HTTP(S) reporting. Presumably the report contents are protected in transit
but to what extent is access by arbitrary parties an issue. Notwithstanding
that things like GDPR are political issues, they are worth noting as a real
life operational consideration."



> > Hatless, it seems to me that the safest implementation of this
> > feature, presuming the security and privacy concerns can be addressed
> > to the satisfaction of those who raised them, would be to add a new
> > tag, as John has proposed, so as to minimize interoperability issues.
> > I say "minimize", rather than "avoid", simply because while RFC 7489
> > says "Unknown tags MUST be ignored.", I don't believe we can say with
> > 100% certainty that all implementations of DMARC policy record parsing
> > in the known world (both by report generators and third parties who
> > advise domains on how to publish DMARC records), implementations that
> > work now, won't "break" if a new tag is introduced. Of course, that'd
> > be their problem, not ours, because they weren't following the
> > existing rules.
>
> We can not continue to design Internet protocols without upward design
> considerations. This is part of the forward and backward compatibility
> design concepts.  Any problem would be a known tag with new
> functionality than originally expected. Sure, we can't say it will not
> happen, but its going to be a very low percentage, if any.  They have
> to fix it.
>
> > As editor, I seek guidance from the working group on how to proceed here.
>
> I am for a URI protocol method as part of the current tag rather than
> a new a separate tag.
>
> However, in principle, I don't see any issue with adding new tags,


I'm sorry, but I'm not clear on what position you're advocating here. You
assert that "any problem would be a known tag with new functionality than
originally expected" (which would seem to argue for using a new tag such as
ruap) but then you state that you're for a URI protocol method as part of
the current tag (which would seem to argue against using ruap, but instead
figuring out a way to add https: to rua), but then you state you don't see
any issue with adding new tags.

Can you help me understand your position better, please?

[snip]


> My point is simple, extended tags MUST be part of the protocol's
> extendability. If there is evidence with 100% sureness there going to
> be a significant compatibility problem with legacy software that can
> not be corrected, then the only option is a new DMARC version 2
> resource record.
>
> I don't think we (I know I can't) can continue with DMARCbis without
> Extended Tag support and be hesitant to invent them because there is a
> compatibility problem.
>
>
I wasn't arguing against adding a new tag, merely being cautious, perhaps
overly so, in refusing to assert with 100% certainty that doing so won't
cause any problems.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000d1c25005b945c1e3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>It seems that I was not successful in conveying my me=
aning in a few statements, so allow me to try again...</div><div><br></div>=
<div><br></div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Tue, Jan 19, 2021 at 10:28 AM Hector Santos &lt;hsantos=3D<a href=
=3D"mailto:40isdg.net@dmarc.ietf.org">40isdg.net@dmarc.ietf.org</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 1/19/2021=
 9:02 AM, Todd Herr wrote:&gt;<br>
&gt; Other concerns were raised about privacy and security issues that<br>
&gt; might be inherent in and unique to adding this kind of functionality,<=
br>
&gt; issues that may not have been fully discussed or understood by the<br>
&gt; community over the years. There was also a question about whether or<b=
r>
&gt; not this is something that people are asking for.<br>
<br>
Reporting concepts were in the each DKIM Policy proposal (SSP, DSAP, <br>
ADSP) -- a &quot;-r&quot; tag option to send reports. The main concerns wer=
e <br>
unsolicited report abuse.=C2=A0 =C2=A0The DSAP proposal (my own) recognize =
it <br>
could be optional so it provided:<br></blockquote><div><br></div><div>My me=
ntion of &quot;other concerns ... about privacy and security&quot; is in re=
ference to a post in this thread that Mike Hammer made in early December, w=
here he wrote:</div><div><br></div></div><blockquote style=3D"margin:0 0 0 =
40px;border:none;padding:0px"><div class=3D"gmail_quote"><div>&quot;I don&#=
39;t recall a strong security and privacy concerns discussion around HTTP(S=
) reporting. Presumably the report contents are protected in transit but to=
 what extent is access by arbitrary parties an issue. Notwithstanding that =
things like GDPR are political issues, they are worth noting as a real life=
 operational consideration.&quot;</div><div><br></div></div></blockquote><d=
iv class=3D"gmail_quote"><div><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><br>
&gt; Hatless, it seems to me that the safest implementation of this<br>
&gt; feature, presuming the security and privacy concerns can be addressed<=
br>
&gt; to the satisfaction of those who raised them, would be to add a new<br=
>
&gt; tag, as John has proposed, so as to minimize interoperability issues.<=
br>
&gt; I say &quot;minimize&quot;, rather than &quot;avoid&quot;, simply beca=
use while RFC 7489<br>
&gt; says &quot;Unknown tags MUST be ignored.&quot;, I don&#39;t believe we=
 can say with<br>
&gt; 100% certainty that all implementations of DMARC policy record parsing=
<br>
&gt; in the known world (both by report generators and third parties who<br=
>
&gt; advise domains on how to publish DMARC records), implementations that<=
br>
&gt; work now, won&#39;t &quot;break&quot; if a new tag is introduced. Of c=
ourse, that&#39;d<br>
&gt; be their problem, not ours, because they weren&#39;t following the<br>
&gt; existing rules.<br>
<br>
We can not continue to design Internet protocols without upward design <br>
considerations. This is part of the forward and backward compatibility <br>
design concepts.=C2=A0 Any problem would be a known tag with new <br>
functionality than originally expected. Sure, we can&#39;t say it will not =
<br>
happen, but its going to be a very low percentage, if any.=C2=A0 They have =
<br>
to fix it.<br>
<br>
&gt; As editor, I seek guidance from the working group on how to proceed he=
re.<br>
<br>
I am for a URI protocol method as part of the current tag rather than <br>
a new a separate tag.<br>
<br>
However, in principle, I don&#39;t see any issue with adding new tags,</blo=
ckquote><div><br></div><div>I&#39;m sorry, but I&#39;m not clear on what po=
sition you&#39;re advocating here. You assert that &quot;any problem would =
be a known tag with new functionality than originally expected&quot; (which=
 would seem to argue for using a new tag such as ruap) but then you state t=
hat you&#39;re for a URI protocol method as part of the current tag (which =
would seem to argue against using ruap, but instead figuring out a way to a=
dd https: to rua), but then you state you don&#39;t see any issue with addi=
ng new tags.</div><div><br></div><div>Can you help me understand your posit=
ion better, please?</div><div><br></div><div>[snip]</div><div>=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">
My point is simple, extended tags MUST be part of the protocol&#39;s <br>
extendability. If there is evidence with 100% sureness there going to <br>
be a significant compatibility problem with legacy software that can <br>
not be corrected, then the only option is a new DMARC version 2 <br>
resource record.<br>
<br>
I don&#39;t think we (I know I can&#39;t) can continue with DMARCbis withou=
t <br>
Extended Tag support and be hesitant to invent them because there is a <br>
compatibility problem.<br>
<br></blockquote><div><br></div><div>I wasn&#39;t arguing against adding a =
new tag, merely being cautious, perhaps overly so, in refusing to assert wi=
th 100% certainty that doing so won&#39;t cause any problems.</div><div>=C2=
=A0</div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p d=
ir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p=
><div style=3D"text-align:left"><span style=3D"vertical-align:baseline;whit=
e-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span>=
<span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small=
;font-family:Arial"> | Sr. Technical Program Manager</span></div><span styl=
e=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-fami=
ly:Arial"><div style=3D"text-align:left"><span style=3D"vertical-align:base=
line"><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=3D"m=
ailto:todd.herr@valimail.com" target=3D"_blank">todd.herr@valimail.com</a><=
/span></div></span><span><div><span><b>p:</b></span><span> 703.220.4153 </s=
pan><span></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);f=
ont-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(=
255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;vertical-align:baseline;white-space:pre-wrap"><img src=3D"https://l=
h5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYn=
Zu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rj=
z19-Dx9rESL" style=3D"border: none; height: 40px; width: 177px;"></span></p=
><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sa=
ns-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38=
;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"backgrou=
nd-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt=
"><font color=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px=
;white-space:pre-wrap">This email and all data transmitted with it contains=
 confidential and/or proprietary information intended solely for the use of=
 individual(s) authorized to receive it. If you are not an intended and aut=
horized recipient you are hereby notified of any use, disclosure, copying o=
r distribution of the information included in this transmission is prohibit=
ed and may be unlawful. Please immediately notify the sender by replying to=
 this email and then delete it from your system.</span></font></p></span></=
div></div>

--000000000000d1c25005b945c1e3--


From nobody Tue Jan 19 11:25:51 2021
Return-Path: <todd.herr@valimail.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 E57F63A1737 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:25:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 4Yz__tcE2S9A for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:25:44 -0800 (PST)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519E93A1716 for <dmarc@ietf.org>; Tue, 19 Jan 2021 11:25:44 -0800 (PST)
Received: by mail-qk1-x736.google.com with SMTP id c7so23035779qke.1 for <dmarc@ietf.org>; Tue, 19 Jan 2021 11:25:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=cYnxNkITsSGugfrWfY53EofX511jcFAOlTQD4MuFwh4=; b=NeK/I5qc+b8IZq75rTQ9YxGqD6t5LrtDV42tB2JfgeKdsf1KLfsPEEe0e3DVoCd5q0 yicUHazy9whCuXTOyZwTOpHZ/0oaqTTkuMfwsHVktInxghz8Td2MQe8EaE10gAbKyjsW RBxnd7ds+Om/qFEU6Nwz9M6d1xkfr2uALH/oWkU0YjJk2kqSC4sWbh/nDajUMfW40GKU yZc20e8Jbw4rYxKPHsL5F6og+ZTLSsCsLhMHCDv22zaVGtSBoeHoa5DjpLwnaxXCUuXs ZMa51qxCCkpgTSY3UPAYSwWK6Ndq8jfoNMant2B4MzSVBwnrS1MweQyOPeh1QAJAVCst fWfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=cYnxNkITsSGugfrWfY53EofX511jcFAOlTQD4MuFwh4=; b=MuyGSGxeS08fBDWJdtAg9TH38e3jHcaMwDbgF3JbEYW3MqTK35WcxEidDIB7AWsEh8 39ol4E6lR6oAjICFh/YShMAOSWPgtCYiZTfCP/n/2n8uhIhmbjmAQaGSL7AAt3A5trZm oe0AO/To9GlIIhaBOq0GXfEC1P3Et/wMGqBDmmoU1/BS6hCV79MR0soTQ088HCIlp9eG uPOPwUW/RVb+FnENhbmBfOLdfLOKkFy6ZqhnHGCuJaYzbJdnNb8uo5fy0jcGLUEQENUb lP7uX9Pmdhrdg+T9DYeGRx6JgEvB7rA+h/K1IW8Hb2C6Mr8aP45ZTW/HHy16B5bR4Amf u8sA==
X-Gm-Message-State: AOAM533avsSVUqEHTVxx/vuDKwPGrQvV+VSfP+o1LNR8JFX4m6bUIiDH oFk9KoMANO/Kv26YgtobM9IiySkB6KCj04XEzNW/QLiH/s8=
X-Google-Smtp-Source: ABdhPJwYqi+DCAr2w3k6RuBCdXab7FbBb5YnQvtvIIN4NUV4rAjtcIvnyNEtZx5dGTIJvL5sEjvSyKTbDZPvoFkWnAE=
X-Received: by 2002:a05:620a:1fb:: with SMTP id x27mr2793008qkn.456.1611084343047;  Tue, 19 Jan 2021 11:25:43 -0800 (PST)
MIME-Version: 1.0
References: <eb3d06f-c89f-2511-3528-d421473e4d42@taugh.com> <a67a4e98-2be0-e2e2-2595-c12d9b87c4df@taugh.com> <7d3be6c4-aa17-3c34-d8f0-4df51e46ccc1@tana.it> <f12991fe-fded-6c0-528c-3b879b4a670@taugh.com> <8b6605de-ca01-904c-de78-deae254e0891@tana.it> <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com> <d7b0a494-e9f8-4765-2b47-65d299305b41@tana.it>
In-Reply-To: <d7b0a494-e9f8-4765-2b47-65d299305b41@tana.it>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 19 Jan 2021 14:25:27 -0500
Message-ID: <CAHej_8=K_x5xOw47XBtPYBWzCbfpPSAs=i9WoweZnaa1OFc1uQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f88bc505b945cda8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/B4YnaJulcZSiW_B62cioukx7Xwo>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 19 Jan 2021 19:25:50 -0000

--000000000000f88bc505b945cda8
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 19, 2021 at 2:18 PM Alessandro Vesely <vesely@tana.it> wrote:

> On Tue 19/Jan/2021 15:02:39 +0100 Todd Herr wrote:
> > Concerns were voiced about interoperability impacts for Ale's
> suggestions,
> > and Ale committed to running an experiment to see if there were changes
> to
> > his inbound report flows when he implemented one variant for expressing
> the
> > URI in the rua tag (v=DMARC1; p=none; rua=mailto:local@example.com,
> > mailto:report@service.example, OR-https://service.example/report/;), but
> > there have been no subsequent posts by him to the list to report on
> > results.
>
>
> It seems to work perfectly.
>
>
Can you provide more details, please?

Are you receiving reports by HTTPS, or have you not seen any reduction in
reports, or both, or other?

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000f88bc505b945cda8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 19, 2021 at 2:18 PM Alessandr=
o Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote=
:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">On Tue 19/Jan/2021 15:02:39 +0100 Todd Herr wrote:<br>
&gt; Concerns were voiced about interoperability impacts for Ale&#39;s sugg=
estions,<br>
&gt; and Ale committed to running an experiment to see if there were change=
s to<br>
&gt; his inbound report flows when he implemented one variant for expressin=
g the<br>
&gt; URI in the rua tag (v=3DDMARC1; p=3Dnone; rua=3Dmailto:<a href=3D"mail=
to:local@example.com" target=3D"_blank">local@example.com</a>, <br>
&gt; mailto:<a href=3D"mailto:report@service.example" target=3D"_blank">rep=
ort@service.example</a>, OR-<a href=3D"https://service.example/report/;" re=
l=3D"noreferrer" target=3D"_blank">https://service.example/report/;</a>), b=
ut<br>
&gt; there have been no subsequent posts by him to the list to report on<br=
>
&gt; results.<br>
<br>
<br>
It seems to work perfectly.<br>
<br></blockquote><div><br></div><div>Can you provide more details, please?<=
/div><div><br></div><div>Are you receiving reports by HTTPS, or have you no=
t seen any reduction in reports, or both, or other?</div><div>=C2=A0</div><=
/div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p dir=3D"ltr"=
 style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div styl=
e=3D"text-align:left"><span style=3D"vertical-align:baseline;white-space:pr=
e-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span styl=
e=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-fami=
ly:Arial"> | Sr. Technical Program Manager</span></div><span style=3D"verti=
cal-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial">=
<div style=3D"text-align:left"><span style=3D"vertical-align:baseline"><b>e=
:</b></span><span style=3D"vertical-align:baseline"> <a href=3D"mailto:todd=
.herr@valimail.com" target=3D"_blank">todd.herr@valimail.com</a></span></di=
v></span><span><div><span><b>p:</b></span><span> 703.220.4153 </span><span>=
</span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family=
:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,25=
5);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-s=
ize:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;ve=
rtical-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleu=
sercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDF=
Oqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rES=
L" style=3D"border: none; height: 40px; width: 177px;"></span></p><p dir=3D=
"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;f=
ont-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-to=
p:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:r=
gb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font co=
lor=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-spa=
ce:pre-wrap">This email and all data transmitted with it contains confident=
ial and/or proprietary information intended solely for the use of individua=
l(s) authorized to receive it. If you are not an intended and authorized re=
cipient you are hereby notified of any use, disclosure, copying or distribu=
tion of the information included in this transmission is prohibited and may=
 be unlawful. Please immediately notify the sender by replying to this emai=
l and then delete it from your system.</span></font></p></span></div></div>

--000000000000f88bc505b945cda8--


From nobody Tue Jan 19 13:26:31 2021
Return-Path: <todd.herr@valimail.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 101D53A178E for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 13:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 9LUrtLMaDhJ3 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 13:26:27 -0800 (PST)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D648B3A179C for <dmarc@ietf.org>; Tue, 19 Jan 2021 13:26:26 -0800 (PST)
Received: by mail-qt1-x82c.google.com with SMTP id e17so5737636qto.3 for <dmarc@ietf.org>; Tue, 19 Jan 2021 13:26:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ZA4NTDO0yW2R+WHyxhYORlXirBEKZ9rUzO34a+dKacE=; b=QtfjhNkYbpWQb3aGfyLRqFVtNLu4T+6Ssw6bnh6pjeh4H8p3NptbEz6dqILLY4GVMv w1FF+E4S3wOObyJ4YKkYGIz6lhoJCvhYrBNd0sQW2CrnqJPIUqx52/INvCln4HJxbAU1 nvbh5QT+Ds3gWkRIsvRy1PtiIerr7NZuY4PGpWeRdp/xvt8AACoeGEPfBQtylBCMnUSS Pn8uJTNZx12NifzUED4vpTbawR6LNYj0rE8MDnldOVjG5xSbLdOPxRnJaHdqlDU3FisG zR5ZNnZKUAki9k2vfgR24sZ5H/gTRnY1r5KSegHcbqiWQfc5gQQGx9fC47bafHm3s8iy K5yg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ZA4NTDO0yW2R+WHyxhYORlXirBEKZ9rUzO34a+dKacE=; b=PVEA7dWOvCQhcUmgMmKTfE2GrpSvTQdni7IGLB4QU2SAhIM5l8WZbu3//Z5kkOcDTK byYt18bMSPnTxhbQKq2iMRxyR5ZqKzTYK2Gsy19210AENbsgKvbeuxGhdIjZyCtFvxmq tON/7lo4XAqp/pZZuAXneoVH8c0/pvY2kDKcBBKblYdwvxhUI7UaMTq3F7WEIIC8bkWD qBdymPRDpoJCO58nOHJAp8SVcHMpVAR7eYGR39s+bQ//WGjHtERu1Pdjj4IQFoRP+PHY 4wY0Rm+xJSOBATtWOw/0xu4WvDGGUGB5EkBWS5VX0vm1TwnDIgHXMrbnI+putgYWkbPl z5vQ==
X-Gm-Message-State: AOAM5316VgZNCOn7/bzQyVVNIKrWK6+DUEK11ifSdNjMGDnS+bn1uysf /5q2lVFxTquOzEf9IRWYivO7bAIb2jNEvenfyHiSznwmGhMvPA==
X-Google-Smtp-Source: ABdhPJx2Kq8rRk1D/MDlNDeghkIcWQDGf8Qgiby1xD5SlQk6oEBxs6cS8fWDsahuQDVGEDDhW87rNdIBX6uNkw+grhM=
X-Received: by 2002:a05:622a:20c:: with SMTP id b12mr6212310qtx.208.1611091585612;  Tue, 19 Jan 2021 13:26:25 -0800 (PST)
MIME-Version: 1.0
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <45b3df7-5c6-9744-2ca8-1542e1b33e7b@taugh.com> <478c7b56-f2b4-c7c1-7722-27fdce4bb8e9@tana.it>
In-Reply-To: <478c7b56-f2b4-c7c1-7722-27fdce4bb8e9@tana.it>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 19 Jan 2021 16:26:09 -0500
Message-ID: <CAHej_8=UTfpVBZJnP6anWshO+6ytU7jb4nybru2gmkFDHZwH5w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a9569605b9477d3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/IrYZtxiF2FPiMnyJn_Q1MCl1wZ0>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 19 Jan 2021 21:26:29 -0000

--000000000000a9569605b9477d3e
Content-Type: text/plain; charset="UTF-8"

Picking up the thread on another ticket that was brought before the group
pre-holidays and has lain fallow since the end of 2020...

John Levine asserted that there wasn't a lot of strong opinion on the
matter, and therefore we'd be leaving the spec as is, with the MAIL FROM
SPF check the only one that matters for DMARC.

Ale replied, but I don't interpret his reply as challenging John's
assertion.

Can this ticket be closed?

On Thu, Dec 31, 2020 at 9:47 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Wed 30/Dec/2020 22:06:01 +0100 John R Levine wrote:
> >> We would like to close this ticket by Dec 15, two weeks from now, so
> short
> >> trenchant comments are welcome.
> >>
> >> Ticket #1 is about SPF alignment.  We need to replace references to
> 4408 with
> >> 7408, ando clarify what if anything we do with SPF HELO checks if
> >> the MAIL FROM is null.  One possibility is to say only MAIL FROM SPF
> counts,
> >> if you want to align your bounces, sign them.  The other is to
> explicitly say
> >> that HELO alignment is OK on bounces.
> >
> > I didn't hear a lot of strong opinions, but I think they leaned in the
> > direction of only checking the MAIL FROM, since the name of the MTA
> often is
> > unrelated to the From: domain.
> >
> > This means that if you want your bounces to be DMARC aligned, they'd
> need DKIM
> > signatures.
>
>
> Bounces with HELO mta.example.com should have From:
> postmaster@mta.example.com,
> where example.com may be a virtual domain or the "real" domain name,
> depending
> on the configuration.
>
> --

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000a9569605b9477d3e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Picking up the thread on another ticket that was brought b=
efore the group pre-holidays and has lain fallow since the end of 2020...<d=
iv><br></div>John Levine asserted that there wasn&#39;t a lot of strong opi=
nion on the matter, and therefore we&#39;d be leaving the spec as is, with =
the MAIL FROM SPF check the only one that matters for DMARC.<div><br></div>=
<div>Ale replied, but I don&#39;t interpret his reply as challenging John&#=
39;s assertion.</div><div><br></div><div>Can this ticket be closed?</div><d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Thu, Dec 31, 2020 at 9:47 AM Alessandro Vesely &lt;<a href=3D"mailto:vesely=
@tana.it" target=3D"_blank">vesely@tana.it</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">On Wed 30/Dec/2020 22:06:01 +0100=
 John R Levine wrote:<br>
&gt;&gt; We would like to close this ticket by Dec 15, two weeks from now, =
so short <br>
&gt;&gt; trenchant comments are welcome.<br>
&gt;&gt;<br>
&gt;&gt; Ticket #1 is about SPF alignment.=C2=A0 We need to replace referen=
ces to 4408 with <br>
&gt;&gt; 7408, ando clarify what if anything we do with SPF HELO checks if<=
br>
&gt;&gt; the MAIL FROM is null.=C2=A0 One possibility is to say only MAIL F=
ROM SPF counts, <br>
&gt;&gt; if you want to align your bounces, sign them.=C2=A0 The other is t=
o explicitly say <br>
&gt;&gt; that HELO alignment is OK on bounces.<br>
&gt; <br>
&gt; I didn&#39;t hear a lot of strong opinions, but I think they leaned in=
 the <br>
&gt; direction of only checking the MAIL FROM, since the name of the MTA of=
ten is <br>
&gt; unrelated to the From: domain.<br>
&gt; <br>
&gt; This means that if you want your bounces to be DMARC aligned, they&#39=
;d need DKIM <br>
&gt; signatures.<br>
<br>
<br>
Bounces with HELO <a href=3D"http://mta.example.com" rel=3D"noreferrer" tar=
get=3D"_blank">mta.example.com</a> should have From: <a href=3D"mailto:post=
master@mta.example.com" target=3D"_blank">postmaster@mta.example.com</a>, <=
br>
where <a href=3D"http://example.com" rel=3D"noreferrer" target=3D"_blank">e=
xample.com</a> may be a virtual domain or the &quot;real&quot; domain name,=
 depending <br>
on the configuration.<br>
<br></blockquote></div>-- <br><div dir=3D"ltr"><span><p dir=3D"ltr" style=
=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"t=
ext-align:left"><span style=3D"vertical-align:baseline;white-space:pre-wrap=
;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span style=3D"v=
ertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Ari=
al"> | Sr. Technical Program Manager</span></div><span style=3D"vertical-al=
ign:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div s=
tyle=3D"text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b><=
/span><span style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@=
valimail.com" target=3D"_blank">todd.herr@valimail.com</a></span></div></sp=
an><span><div><span><b>p:</b></span><span> 703.220.4153 </span><span></span=
></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial=
,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical=
-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercon=
tent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0Lh=
bnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" sty=
le=3D"border:none;height:40px;width:177px"></span></p><p dir=3D"ltr" style=
=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:sm=
all;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,=
255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666=
666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre-wrap=
">This email and all data transmitted with it contains confidential and/or =
proprietary information intended solely for the use of individual(s) author=
ized to receive it. If you are not an intended and authorized recipient you=
 are hereby notified of any use, disclosure, copying or distribution of the=
 information included in this transmission is prohibited and may be unlawfu=
l. Please immediately notify the sender by replying to this email and then =
delete it from your system.</span></font></p></span></div></div></div>

--000000000000a9569605b9477d3e--


From nobody Tue Jan 19 13:36:27 2021
Return-Path: <todd.herr@valimail.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 7E3163A0A27 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 13:36:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 rwb3lVPjeGom for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 13:36:24 -0800 (PST)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A2233A1791 for <dmarc@ietf.org>; Tue, 19 Jan 2021 13:35:56 -0800 (PST)
Received: by mail-qk1-x72e.google.com with SMTP id n142so23487267qkn.2 for <dmarc@ietf.org>; Tue, 19 Jan 2021 13:35:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=/wiXPC0Cqah9fsACyD0R5SYmOdx3IjNbsEiQHFPXZAU=; b=Tv/RQD8IkYZOM59OIx1Ed4bMk+FR/RBO3HDarGeQk97BUYW8wWYJfpaMlEy/j3JZ79 3rotqSSMOYZdUfS+H0do7LhYbo0hB2970mQzPXN0MLwIiBwDVZuRB+KPu5AkFz0wY6Ug VD39hPWXEg1yw1zsdhnvBO8hq21NWZcE0mXcyOK1xahY3/sR+apZ3iPUZfi7B8KL9KL7 E9s3PbOyzMc5UPbyNgc9My1HViJskMtgjQFZwc4uZjE4Zo/pxcf+Xcpyycb0VD+AhO5W //7pC0PSOTta5UrfXE2Lc6Fr0VLfg4MkcBpINyO1lwEoru1KZY72r/ojZ+t/2FuwYpjX /3gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=/wiXPC0Cqah9fsACyD0R5SYmOdx3IjNbsEiQHFPXZAU=; b=ksu0rXNpKJtPGo6il26jXr2QJxH/F8wI1+WWOeVBfKtcBOiZJKxmfjRZrtGMIEO8+q /vavXrknz79w8i2RvlT17uFUlEA5SwT908XN0ddpz6Qk3FyPddE0n1InLrkH7d2C0Kyp sZeSwgMnFruWim0aKrMTn9FOyalJk9PbIh7QOYsPCwcA/g8B8c/DhNQRuMQ3vupgIyme KdoRQvnWfnGlB3KLgTRFuTziDeS2dIQO05jM2KbNwqGMT/JRQjd8s3K3zQvt5LDLLrIZ 1tNPc2mY4Wp8ByRKPaU5jh9rQd2JOSfjoIZiD2vXQ7Qg0fW+cIAvTUxYq3guXxYJ9zBE XOnQ==
X-Gm-Message-State: AOAM533Fh0SAARmf75ry5w42miiYWw3JJXSeVZcnNdpvm/xSCEuCCHN9 iRVbAr31NUjgbv94e3BZmr/fMwXRRjCMFZLkjE+lVuf4aqo=
X-Google-Smtp-Source: ABdhPJwPxVrGCBXevf8zaNfc6/CokgdmqtlbZLply85P2FrVlLD7l1C5LLR/3h5inLyMv8WAAU2D0OxHVkK32aRSByA=
X-Received: by 2002:a05:620a:1fb:: with SMTP id x27mr3313981qkn.456.1611092155359;  Tue, 19 Jan 2021 13:35:55 -0800 (PST)
MIME-Version: 1.0
References: <20201231192500.1B3483F0176B@ary.qy> <be0601ec-7e50-f280-4cf4-66c3b4ac7fa5@tana.it> <CAHej_8mNzuAys9V0BHCk9o=6rzK9vEpZ6Db3OE4zA+E=vXhrjw@mail.gmail.com>
In-Reply-To: <CAHej_8mNzuAys9V0BHCk9o=6rzK9vEpZ6Db3OE4zA+E=vXhrjw@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 19 Jan 2021 16:35:39 -0500
Message-ID: <CAHej_8nDVD8yYKVS24TPd3GaCs_0Yptg+hYQ_usTQ5xoOnJ-=g@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ef6cc05b9479fe7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vIBmQbrSp9TB9YctPEvuJr5nk4I>
Subject: Re: [dmarc-ietf] Ticket #80 - DMARCbis Should Have Clear and Concise Definition of DMARC
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, 19 Jan 2021 21:36:27 -0000

--0000000000009ef6cc05b9479fe7
Content-Type: text/plain; charset="UTF-8"

I am going to close this ticket.

I have opened ticket 96, Tweaks to Abstract and Introduction
<https://trac.ietf.org/trac/dmarc/ticket/96>, for Ale's suggestions and for
any tweaks that John might still suggest.


On Tue, Jan 5, 2021 at 8:36 AM Todd Herr <todd.herr@valimail.com> wrote:

> On Tue, Jan 5, 2021 at 7:25 AM Alessandro Vesely <vesely@tana.it> wrote:
>
>> On Thu 31/Dec/2020 20:24:59 +0100 John Levine wrote:
>> > In article <CAHej_8kkuQR3_LiV_O5Z-EPvVeZrdTPvCiK7rOmWKxQKsp=
>> 6pA@mail.gmail.com> you write:
>> >>
>> >>Dave Crocker submitted some suggestions on-list, and I noodled a bit
>> with
>> >>the text myself, and submit the following for your collective
>> consideration:
>> >
>> > I have a few minor editorial tweaks to suggest but they can wait.  I
>> think
>> > we should use this text.
>>
>>
>> +1, I see it's not yet on github.  Please go ahead, possibly posting a
>> .txt as
>> well, so we can run IETF's diff tool.
>>
>>
>>
> Updated version, including .txt but without your suggested minor tweaks,
> is posted here -
> https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis
>
> Note that lack of inclusion of your minor tweaks obviously does not mean
> that they've been rejected; I just wanted to complete the process of
> checking in a new branch, doing a pull request, and merging the new branch
> with main.
>
> --
>
> *Todd Herr* | Sr. Technical Program Manager
> *e:* todd.herr@valimail.com
> *p:* 703.220.4153
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
>


-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000009ef6cc05b9479fe7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am going to close this ticket.<div><br></div><div>I have=
 opened ticket 96, <a href=3D"https://trac.ietf.org/trac/dmarc/ticket/96">T=
weaks to Abstract and Introduction</a>, for Ale&#39;s suggestions and for a=
ny tweaks that John might still suggest.</div><div><br></div></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 5,=
 2021 at 8:36 AM Todd Herr &lt;<a href=3D"mailto:todd.herr@valimail.com">to=
dd.herr@valimail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 5, 2021 a=
t 7:25 AM Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it" target=3D=
"_blank">vesely@tana.it</a>&gt; wrote:<br></div><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">On Thu 31/Dec/2020 20:24:=
59 +0100 John Levine wrote:<br>
&gt; In article &lt;CAHej_8kkuQR3_LiV_O5Z-EPvVeZrdTPvCiK7rOmWKxQKsp=3D<a hr=
ef=3D"mailto:6pA@mail.gmail.com" target=3D"_blank">6pA@mail.gmail.com</a>&g=
t; you write:<br>
&gt;&gt;<br>
&gt;&gt;Dave Crocker submitted some suggestions on-list, and I noodled a bi=
t with<br>
&gt;&gt;the text myself, and submit the following for your collective consi=
deration:<br>
&gt; <br>
&gt; I have a few minor editorial tweaks to suggest but they can wait.=C2=
=A0 I think<br>
&gt; we should use this text.<br>
<br>
<br>
+1, I see it&#39;s not yet on github.=C2=A0 Please go ahead, possibly posti=
ng a .txt as <br>
well, so we can run IETF&#39;s diff tool.<br>
<br>
<br></blockquote><div><br></div><div>Updated version, including .txt but wi=
thout your suggested minor tweaks, is posted here -=C2=A0<a href=3D"https:/=
/github.com/ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis" target=3D"_blank">http=
s://github.com/ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis</a></div><div><br></=
div><div>Note that lack of inclusion of your minor tweaks obviously does no=
t mean that they&#39;ve been rejected; I just wanted to complete the proces=
s of checking in a new branch, doing a pull request, and merging the new br=
anch with main.</div><div><br></div></div>-- <br><div dir=3D"ltr"><span><p =
dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></=
p><div style=3D"text-align:left"><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span=
><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:smal=
l;font-family:Arial"> | Sr. Technical Program Manager</span></div><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-fam=
ily:Arial"><div style=3D"text-align:left"><span style=3D"vertical-align:bas=
eline"><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=3D"=
mailto:todd.herr@valimail.com" target=3D"_blank">todd.herr@valimail.com</a>=
</span></div></span><span><div><span><b>p:</b></span><span> 703.220.4153 </=
span><span></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);=
font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb=
(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span styl=
e=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tra=
nsparent;vertical-align:baseline;white-space:pre-wrap"><img src=3D"https://=
lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TY=
nZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3r=
jz19-Dx9rESL" style=3D"border: none; height: 40px; width: 177px;"></span></=
p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,s=
ans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"backgro=
und-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0p=
t"><font color=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667p=
x;white-space:pre-wrap">This email and all data transmitted with it contain=
s confidential and/or proprietary information intended solely for the use o=
f individual(s) authorized to receive it. If you are not an intended and au=
thorized recipient you are hereby notified of any use, disclosure, copying =
or distribution of the information included in this transmission is prohibi=
ted and may be unlawful. Please immediately notify the sender by replying t=
o this email and then delete it from your system.</span></font></p></span><=
/div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Sr. Technical P=
rogram Manager</span></div><span style=3D"vertical-align:baseline;white-spa=
ce:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-align:lef=
t"><span style=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"v=
ertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" target=
=3D"_blank">todd.herr@valimail.com</a></span></div></span><span><div><span>=
<b>p:</b></span><span> 703.220.4153 </span><span></span></div></span><p dir=
=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-seri=
f;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin=
-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial=
;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;whit=
e-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfm=
T2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7=
n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; =
height: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(3=
4,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-=
color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><=
br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Ar=
ial"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email an=
d all data transmitted with it contains confidential and/or proprietary inf=
ormation intended solely for the use of individual(s) authorized to receive=
 it. If you are not an intended and authorized recipient you are hereby not=
ified of any use, disclosure, copying or distribution of the information in=
cluded in this transmission is prohibited and may be unlawful. Please immed=
iately notify the sender by replying to this email and then delete it from =
your system.</span></font></p></span></div>

--0000000000009ef6cc05b9479fe7--


From nobody Tue Jan 19 14:11:19 2021
Return-Path: <dougfoster.emailstandards@gmail.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 A63D03A1824 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 14:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 AKuB-g5aLbHs for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 14:11:16 -0800 (PST)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F0A63A0C74 for <dmarc@ietf.org>; Tue, 19 Jan 2021 14:11:15 -0800 (PST)
Received: by mail-vs1-xe29.google.com with SMTP id o186so4192468vso.1 for <dmarc@ietf.org>; Tue, 19 Jan 2021 14:11:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=aZj2oyv8qyfy60d0rKZS3eTd3SnoD7QJ93oW+yohMAM=; b=RxB9foDbDiJq5vKBC0Wpbt1JjtK+Rhw0RKbZUt7ycJiMQGObNoiF0Q7fYIODL08aru +kA0AKFRgjRypEDb4fi9M97xZOtc4lt+sj9h72QtoJfb4HCFXlI40vxttgZxzwws0rgJ V8XWl9WP30nM/OZfysQS1jjAyyuAsibPndaxzcPe7baFngY7amX2m0/c2xX6yCsBsssp OVNE6BbknZaz9ZLxzWRtE0pbRI5kdIddNjtWCWQaODb0Kjth/JL7qYbNOPymMpSd+KiA BCqQBi6sSw19UdX1ox/vAq8S54b6jsy3MbLAL8Jep3Jq/ZBKYJedPHe2qdxCSYQLFnqM WzJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=aZj2oyv8qyfy60d0rKZS3eTd3SnoD7QJ93oW+yohMAM=; b=uTuzLnfP2nAMBzGMEEroCR8Tz2aWcV7l8V5SpxMpMe8CJPxczubJ+acuWWbu3n8Ifh krKUzutH6jtbJkyaTWaGz8lnSf+ToAiehqlN2iIJdK+ETjdxDeIMZDpWieNBXEoqFYfJ hKNQk6LF1+rc+XSzaOcJrChILaQRr0yCtrUBzx6lzi2T1zzFwHkZAaXx47uDOVcw31pT yo29oaguejg+57xaluNgx6CyLYPch9owejRFTsBs/psNaOvpn8PEp1IatCL9cFx4vrDJ KyrLSYcU6ft33qKGXc+uzMeTQw+g6uFsxyFMAyPT3w87g6e3pFlxy/47KWA0EjCmzk2u HYxQ==
X-Gm-Message-State: AOAM532FhCQWPsKvUa3kCZK4H5wMI2/RXRWKYygDCWTCBTP5yG1l3dcR vnpPyvvVMaTuRnRfbQJ2asVuTPF1xntQrxE/r4c3gkqER0Y=
X-Google-Smtp-Source: ABdhPJz2lZ/bePxjzpcfgVejw4Ba4YAChFfhuliZ2PW5MFSHHTVFsc8JptGFT/8TQVIq3dEsrITXMMY6kGgrGNJbQbE=
X-Received: by 2002:a67:c29e:: with SMTP id k30mr782440vsj.45.1611094274751; Tue, 19 Jan 2021 14:11:14 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <CAH48ZfwOdZcJz02a76wktQDpV_dpPHKw+qJjE2ZCDvOqF3Ptdw@mail.gmail.com> <CAL0qLwZf+tEGZj0T6UmaNBSMC-nqSpfb5DAFh8+GDuP6F5pRkQ@mail.gmail.com>
In-Reply-To: <CAL0qLwZf+tEGZj0T6UmaNBSMC-nqSpfb5DAFh8+GDuP6F5pRkQ@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 19 Jan 2021 17:11:04 -0500
Message-ID: <CAH48ZfxJBwROXjtTr0YCOtBN0h_Q=jU559fAnUUNRpFjvEinRA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f240c505b9481d0b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/XsRk1FPFJV61CfHZRhWTsBqlHbw>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 19 Jan 2021 22:11:18 -0000

--000000000000f240c505b9481d0b
Content-Type: text/plain; charset="UTF-8"

No Murray, I was speaking to the PSD document.

PSD's entire purpose is to detect abuse of non-existent organizational
domains, so the definition of non-existent is crucial to its success.    I
believe the current language will produce false positives, albeit probably
a small number.    The current language is also more resource-intensive
than mine, although that is not my concern.

I believe this is also a general problem that full DMARC should address.
 If a domain exists but does not have a policy, we interpret this to mean
that the domain owner has not chosen to publish a policy, which is his
right.    If a domain does not exist, then there is no domain owner to
publish a policy and no reason to believe that the use of the domain is
legitimate.   In fact, use of an unregistered domain is a violation of IETF
policy and the entire name registration infrastructure.    Consequently, I
believe that SPF and DMARC SHOULD differentiate between "policy not
specified" and NXDOMAIN.   But to put this topic into play for DMARC, I
need to create a ticket, right?

I also want PSD to use a correct definition of non-existent because it will
establish a precedent for any generalization done as part of the full DMARC
effort.

Doug Foster

On Tue, Jan 19, 2021 at 9:23 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Tue, Jan 19, 2021 at 4:34 AM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> I raised objections to the definition of "non-existent", which never
>> received an adequate response before the discussion went silent.
>>
>> DMARC checks the From  header address, which may exist only as an
>> identifier used for mass mailings.   These mailings are often sent by an
>> ESP using an unrelated SMTP address.    As such, the From address need not
>> be associated with any A, AAAA, or MX record.    I assert that the only
>> viable definition of non-existent is "not registered", as evidenced by
>> absence of an NS record.
>>
>
> This is a discussion of DMARC, not of PSD, right?  DMARC defines this test
> in an Appendix, and then makes it non-mandatory.  PSD says to apply that
> test for domains that request it.
>
> Hooking this test up to registration requires introducing RDAP or
> something similar.  Is that what we're talking about here?
>
> I don't believe the proposed definition of "non-existent" is reliably true
>> even in the special case of interest for this document, impersonation fraud
>> occurring at the top of an organizational structure.  Example.PSD may
>> legitimately use mail.Example.PSD for email and www.example.psd for web.
>>  If the proposed condition MUST always be true, I have not seen that fact
>> demonstrated.   Since the document raises a general concern about
>> fraudulent use of non-existent domains, the definition used should be one
>> that can be generalized.,
>>
>
> This sounds like something that should be solved in DMARC, not PSD, but
> naturally consensus wins here, so have at it.
>
> -MSK
>

--000000000000f240c505b9481d0b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">No Murray, I was speaking to the PSD document.=C2=A0 =C2=
=A0<div><br></div><div>PSD&#39;s entire purpose is to detect abuse of non-e=
xistent organizational domains, so the definition of non-existent is crucia=
l to its success.=C2=A0 =C2=A0 I believe the current language will produce =
false positives, albeit probably a small number.=C2=A0 =C2=A0 The current l=
anguage is also more resource-intensive than mine, although that is not my =
concern.=C2=A0 =C2=A0</div><div><br></div><div>I believe this is also a gen=
eral problem that full DMARC should address.=C2=A0 =C2=A0If a domain exists=
 but does not have a policy, we interpret this to mean that the domain owne=
r has not chosen to publish a policy, which is his right.=C2=A0 =C2=A0 If a=
 domain does not exist, then there is no domain owner to publish a policy a=
nd no reason to believe that the use of the domain is legitimate.=C2=A0 =C2=
=A0In fact, use of an unregistered domain is a violation of IETF policy and=
 the entire name registration infrastructure.=C2=A0 =C2=A0 Consequently, I =
believe that SPF and DMARC SHOULD differentiate between &quot;policy not sp=
ecified&quot; and NXDOMAIN.=C2=A0 =C2=A0But to put this topic into play for=
 DMARC, I need to create a ticket, right?</div><div><br></div><div>I also w=
ant PSD to use a correct definition of non-existent because it will establi=
sh a precedent for any generalization done as part of the full DMARC effort=
.</div><div><br></div><div>Doug Foster</div></div><br><div class=3D"gmail_q=
uote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 19, 2021 at 9:23 AM=
 Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com">superuser@g=
mail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 19, 2021 at 4:34 AM D=
ouglas Foster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com" ta=
rget=3D"_blank">dougfoster.emailstandards@gmail.com</a>&gt; wrote:<br></div=
><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div dir=3D"ltr">I raised objections to the definition of &quot;non-exis=
tent&quot;, which never received an adequate response before the discussion=
 went silent.=C2=A0 =C2=A0=C2=A0<div><br></div><div>DMARC checks the From=
=C2=A0 header address, which may exist only as an identifier used for mass =
mailings.=C2=A0 =C2=A0These mailings are often sent by an ESP using an unre=
lated=C2=A0SMTP address.=C2=A0 =C2=A0 As such, the From address need not be=
 associated with any A, AAAA, or MX record.=C2=A0 =C2=A0 I assert that the =
only viable definition of non-existent is &quot;not registered&quot;, as ev=
idenced by absence of an NS record.</div></div></blockquote><div><br></div>=
<div>This is a discussion of DMARC, not of PSD, right?=C2=A0 DMARC defines =
this test in an Appendix, and then makes it non-mandatory.=C2=A0 PSD says t=
o apply that test for domains that request it.</div><div><br></div><div>Hoo=
king this test up to registration requires introducing RDAP or something si=
milar.=C2=A0 Is that what we&#39;re talking about here?<br></div><div> <br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><d=
iv><div>I don&#39;t believe the proposed definition of &quot;non-existent&q=
uot; is reliably true even in the special case of interest for this documen=
t, impersonation fraud occurring at the top of an organizational structure.=
=C2=A0 Example.PSD may legitimately use mail.Example.PSD for email and www.=
example.psd for web.=C2=A0 =C2=A0If the proposed condition MUST always be t=
rue, I have not seen that fact demonstrated.=C2=A0 =C2=A0Since the document=
 raises a general concern about fraudulent use of non-existent domains, the=
 definition used should be one that can be generalized.,</div></div></div><=
/blockquote><div><br></div><div>This sounds like something that should be s=
olved in DMARC, not PSD, but naturally consensus wins here, so have at it.<=
/div><div><br></div><div>-MSK<br></div></div></div>
</blockquote></div>

--000000000000f240c505b9481d0b--


From nobody Tue Jan 19 15:23:56 2021
Return-Path: <superuser@gmail.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 7ADBC3A1877 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 15:23:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 akxjCI-fzYtK for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 15:23:53 -0800 (PST)
Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40AFA3A171A for <dmarc@ietf.org>; Tue, 19 Jan 2021 15:23:53 -0800 (PST)
Received: by mail-vs1-xe2d.google.com with SMTP id o125so10794356vsc.6 for <dmarc@ietf.org>; Tue, 19 Jan 2021 15:23:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eFI6/5988+8xUlznKKyLSLckBuFQVBmEznAdHfsjTEs=; b=TNgz1jyEgxcTMj7NjtrWsmwqRkIarYIYBKi49Vz593SVQb38SNNTkWLfKq5jqtwjEh Gk8Vd4DeLCK6TpVKfkIU85LvOY8JkFWCMUwHCIELEoFASVlEKS0TljvebNGcdiSak9VT 0y6KaTl5oeGWCwE1QGA3L4GPVO75fRkeD07PWCxj2zJTr1baKOtx7WYNlEnE9iu5sZi1 YSQVL06JXmt29WnIYb+jY7udJbRNCoWG64Lm/oqZgMz682UQC8tJE7vWJlhgRC3BU1lm F/eh2WBxE5Ka4OtdkQ1NUbdiUOCkBhBZbSMUK4hj+c19y2Y/uGxF4+vM0A7UjOh6p5ql uZwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eFI6/5988+8xUlznKKyLSLckBuFQVBmEznAdHfsjTEs=; b=bCTrxTInZYPYWgzvsWumRPdBiknhYpHmp4oXjphiNsQLS/la69dipN1gYQeyPiYzaw GM4GTkpWLTmbsBQtfZWnG/Tlyld4b/+/hA3oCf4FxgD5Kl3+P2zPRqrNrFxhzJ5E0tzl G8X2nBXoNnnOSTG8901ydFkJKmAUotTLwVQ/Kk3TMA9ZkS6l/vQHPRKsXHbvKqqoSpWs DnczegpGY06v5loZYWYMXNlg6KVFcO+hWuQtPIXk1x54VrwUSKDog9iqGV+byGt78DKE 3ohP6/lAEfpt494v3pOaYNTsh4xYD4Tc2vd8IiUsNMhzmXj1rZsq8n5LNlZCYOkrc/x9 iuPw==
X-Gm-Message-State: AOAM532o1SPgENTdWMsxlyAj9OInTF4stipn40aFaBO+RGconjBkg+jC CtIoErx75uFBHJQfrzQYLSy2joZoMr7fFeZw5OU=
X-Google-Smtp-Source: ABdhPJyMYg4dVLYUy85ZRVv7GoJOkmxwVfmhoNS/7azt7MUUn1i2Q1Jr/FSns7K40LuNHIvX0Hr6W8z/ocMhhk+jUwQ=
X-Received: by 2002:a67:2bc2:: with SMTP id r185mr4556510vsr.15.1611098632217;  Tue, 19 Jan 2021 15:23:52 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <CAH48ZfwOdZcJz02a76wktQDpV_dpPHKw+qJjE2ZCDvOqF3Ptdw@mail.gmail.com> <CAL0qLwZf+tEGZj0T6UmaNBSMC-nqSpfb5DAFh8+GDuP6F5pRkQ@mail.gmail.com> <CAH48ZfxJBwROXjtTr0YCOtBN0h_Q=jU559fAnUUNRpFjvEinRA@mail.gmail.com>
In-Reply-To: <CAH48ZfxJBwROXjtTr0YCOtBN0h_Q=jU559fAnUUNRpFjvEinRA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 19 Jan 2021 15:23:40 -0800
Message-ID: <CAL0qLwYhjRx0nomXe_3KcKXTAmONce4bw6K6YLnNRLZJCzoYBQ@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000abe97c05b94921aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/8-b9PgxobllZ6ZYLyiFMOXNJikM>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 19 Jan 2021 23:23:55 -0000

--000000000000abe97c05b94921aa
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 19, 2021 at 2:11 PM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> No Murray, I was speaking to the PSD document.
>
> PSD's entire purpose is to detect abuse of non-existent organizational
> domains, so the definition of non-existent is crucial to its success.    I
> believe the current language will produce false positives, albeit probably
> a small number.    The current language is also more resource-intensive
> than mine, although that is not my concern.
>

What I mean is: If we say PSD experiment participants evaluate the notion
of "non-existent" differently than vanilla DMARC implementations, we have
to account for that when interpreting the results of the experiment.  But
the experiment as crafted is just to determine if the PSD algorithm as
proposed is a useful improvement.  It seems to me that changing the nature
of that test at the same time is scope creep that muddies the waters.

-MSK

--000000000000abe97c05b94921aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 19, 2021 at 2:11 PM Douglas F=
oster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfoster=
.emailstandards@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">No Mur=
ray, I was speaking to the PSD document.=C2=A0 =C2=A0<div><br></div><div>PS=
D&#39;s entire purpose is to detect abuse of non-existent organizational do=
mains, so the definition of non-existent is crucial to its success.=C2=A0 =
=C2=A0 I believe the current language will produce false positives, albeit =
probably a small number.=C2=A0 =C2=A0 The current language is also more res=
ource-intensive than mine, although that is not my concern.=C2=A0 =C2=A0</d=
iv></div></blockquote><div><br></div><div>What I mean is: If we say PSD exp=
eriment participants evaluate the notion of &quot;non-existent&quot; differ=
ently than vanilla DMARC implementations, we have to account for that when =
interpreting the results of the experiment.=C2=A0 But the experiment as cra=
fted is just to determine if the PSD algorithm as proposed is a useful impr=
ovement.=C2=A0 It seems to me that changing the nature of that test at the =
same time is scope creep that muddies the waters.</div><div><br> </div><div=
>-MSK<br></div></div></div>

--000000000000abe97c05b94921aa--


From nobody Tue Jan 19 17:54:38 2021
Return-Path: <johnl@iecc.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 1984A3A0BEB for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 17:54:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=X53ZXUXm; dkim=pass (2048-bit key) header.d=taugh.com header.b=U3v6Y3gD
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 vDmIquGEJFG8 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 17:54:34 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 788703A0BE9 for <dmarc@ietf.org>; Tue, 19 Jan 2021 17:54:34 -0800 (PST)
Received: (qmail 12073 invoked from network); 20 Jan 2021 01:54:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2f23.60078d55.k2101; bh=S7sszjuR8tkRKdzRwkxb/UYyqQHW7wuX6UsTodo8GPc=; b=X53ZXUXmfKd2oupNkrYW7u74PTl2wmGmjAiXndSbDfeq9F5+rksB9lnIv1PJp1PeKicKqh/wrT/KSZRtPfHkxXHzvcUy9E1yK9q1pY5i5wFZMiO/QtIqzXo2XfVhS107UjkIBKFeesRcdL4WtVbAntlwuSofm4gMa12LrpyONjOQPFM8sPyKEBGpysZWY9ClWF0nrsxWt9/CfyJaU+9zD7Zijx7ElHESfi7LoJ+btSrdE/fekU42xroRTqscsQBxe4LtxWTtEykXAlYk0t4UsRfZI0Se7IVKnR3/IdnFv/8xqeb1NgEWS/B6laarGc6Z7xTNlagrmfMdSEKUNGogWg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2f23.60078d55.k2101; bh=S7sszjuR8tkRKdzRwkxb/UYyqQHW7wuX6UsTodo8GPc=; b=U3v6Y3gDP2/FTnD33SrkBqvvrvpOfHlK9BMpLzCrsIjT1k+K3nw3CTSHzwBa+swfR1fBqJVgM1m6NqpyuEjyqF6bHpYr/GUgG0pi67dASdhXVbd93Az/4bvjeSO6Hj/449qLfKfhvo2doFHKjstCmcvVvgWxG3JSHXTS7m8VWqXDA7hSR5tAMiB95I2JrC/6OSFRfvg6C1nchMlBPf7NbIh15Ttd8nW7T+JQvNZKo7/9lHX6/Cm3UI227OR5cr+PEZ9ZxjvxW4Ad1UzBu8JJ85hxAsIi8OV+S0OUQobF5HCX+30YeGyvnoek6oAJNILGdbp18E8rhpo0ZQCeJta4Fg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 20 Jan 2021 01:54:29 -0000
Received: by ary.qy (Postfix, from userid 501) id C8A026B7BB7D; Tue, 19 Jan 2021 20:54:28 -0500 (EST)
Date: 19 Jan 2021 20:54:28 -0500
Message-Id: <20210120015428.C8A026B7BB7D@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: todd.herr@valimail.com
In-Reply-To: <CAHej_8=BJPezpi2KZ7GX-N__4Fqfc_b8vFNhu7_Typakv4iMig@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WcWxe-pHl201boJOkicuT46FARc>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 01:54:36 -0000

In article <CAHej_8=BJPezpi2KZ7GX-N__4Fqfc_b8vFNhu7_Typakv4iMig@mail.gmail.com> you write:
>My mention of "other concerns ... about privacy and security" is in
>reference to a post in this thread that Mike Hammer made in early December,
>where he wrote:
>
>"I don't recall a strong security and privacy concerns discussion around
>HTTP(S) reporting. Presumably the report contents are protected in transit
>but to what extent is access by arbitrary parties an issue. Notwithstanding
>that things like GDPR are political issues, they are worth noting as a real
>life operational consideration."

I saw this but I still don't understand it. The chances of an HTTP
POST getting snooped on are far less than any kind of e-mail.

R's,
John


From nobody Tue Jan 19 18:31:57 2021
Return-Path: <johnl@iecc.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 24EA23A0C57 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 18:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=rBexRRhV; dkim=pass (2048-bit key) header.d=taugh.com header.b=i3Kh89A4
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 29vQfuE7-4Zs for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 18:31:53 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 9208F3A0C56 for <dmarc@ietf.org>; Tue, 19 Jan 2021 18:31:53 -0800 (PST)
Received: (qmail 21388 invoked from network); 20 Jan 2021 02:31:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=5389.60079618.k2101; bh=STMNj5fehtsWH7sZHNawJ8ztu0xjavnpOAZLI6LE95g=; b=rBexRRhV7hmiJV58b/Rca0kuDbRN16rftAhvKw+MwzmqeO/KA7zokjz+hbER33TIB8mln+4doUyMDIMsc6IGV0w7ac4jF/5hWsPhohQJL/P68LtPywiUWrGXEx0AqNbB1NFLFpiuQlHJoZF6cAcpcbemB8TC+rGLd7iIgj+YXh5Ns6a/TV0iiOSTIb4eJaSBqzX89UbjltLgi7lT7yAVyz7oaZoxHDbCb+GlTswyHDBiGw/5xEAMb9sr6bHXtvzr6QGlmrV6VPgHkodAAIsnwyekwJx8CVJWUG33r4yOZPrlcG0c6auoIRx8eZJWe9l3oUSAIR50c4s4ayrRQzQbbA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=5389.60079618.k2101; bh=STMNj5fehtsWH7sZHNawJ8ztu0xjavnpOAZLI6LE95g=; b=i3Kh89A4XaMF7NliHKuXIkxGfCKhs7d2GpXQ13a/Igfqh/oaW+1/Efgq04j6by0Hz+89TPfQVzwzENnOUzjBGHeA4KWZuLS9JBT3DMfiVrZEs//ss44/AwKzUvu0fP6832TcYcK27BAnHt3cxOD4jgqMzW7R4Cy3QPT09ytSgMgHJQmq0zj7zJK2FAPADygG8Tqcebh1Fyh28sX3rnf9I6wP3q7gk55SrP0wROBl8bzoPLT2Cn/nxlsqZvhh4Na9+fXP6aleskvSKoGO/wG6mLXCmk5SBdatdVhblx0sSAyTY3sp1OZg5Yyd5EdB0HAd2REnU29U/JLORkKhE1WZzg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 20 Jan 2021 02:31:51 -0000
Received: by ary.qy (Postfix, from userid 501) id 3C86A6B7C86C; Tue, 19 Jan 2021 21:31:51 -0500 (EST)
Date: 19 Jan 2021 21:31:51 -0500
Message-Id: <20210120023151.3C86A6B7C86C@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: todd.herr@valimail.com
In-Reply-To: <CAHej_8=K_x5xOw47XBtPYBWzCbfpPSAs=i9WoweZnaa1OFc1uQ@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PQM0H-IzKlns6EqDHlKAGp02GeA>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 02:31:55 -0000

In article <CAHej_8=K_x5xOw47XBtPYBWzCbfpPSAs=i9WoweZnaa1OFc1uQ@mail.gmail.com> you write:
>Can you provide more details, please?
>
>Are you receiving reports by HTTPS, or have you not seen any reduction in
>reports, or both, or other?

I didn't try Ale's OR- thing but I did add an https URL to my rua= tag and set up
a web server to catch any POST or PUT traffic.

Other than a few Russian probes shortly after I published it, it's
gotten no traffic at all.

I suppose the good news is that nobody implemented the underspecifed
report URL in one of the earlier DMARC drafts.

R's,
John


From nobody Wed Jan 20 05:08:44 2021
Return-Path: <hsantos@isdg.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 367633A11FF for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 05:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 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.262, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=eS0uCxp3; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=UQPHAoSZ
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 KKe1wkojAP3E for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 05:08:39 -0800 (PST)
Received: from mail.winserver.com (winserver.com [76.245.57.69]) (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 0A8A83A11FE for <dmarc@ietf.org>; Wed, 20 Jan 2021 05:08:38 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2062; t=1611148114; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=5Hi0HPddWdAbOMBHhb2kCABjSodu gusJh6pVtJtwbpQ=; b=eS0uCxp3xfQ58ulNnQ7kv1DM2NIumG0dJSch87ZC2yzb DQy31v6/IWbLyJbX5+0z3GYuGXwARi6CW/WPlDvicQl/+gNXN1k8rUTFzb+khFAe KxGkOD72ILWiIIHqLyUAf+mKdnOH1Tse5JNGA0bUBTFgrq/+f2XUv8bLIQe3wi8=
Received: by mail.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Wed, 20 Jan 2021 08:08:34 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  dmarc=pass policy=reject author.d=isdg.net signer.d=beta.winserver.com (atps signer); 
Received: from beta.winserver.com ([76.245.57.74]) by mail.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 293189516.1.3592; Wed, 20 Jan 2021 08:08:33 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2062; t=1611147700; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=5Hi0HPd dWdAbOMBHhb2kCABjSodugusJh6pVtJtwbpQ=; b=UQPHAoSZFziaKtrhrt0H9W4 dPg54yH4HwWuIj/IUUd10QENfsHRUG3HjQQk5LxGdbJUbZz60b/ZZ+AE+jgYkmUf AlYqhkgOb72mO0NVm1jdzI6B+Pb5o0HNhTMjUVP1Qn4Jeg1buxQtTTiDGC4BoA+w kpMi1p4iJ7keyp2z2lZw=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Wed, 20 Jan 2021 08:01:40 -0500
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 160037799.1.59648; Wed, 20 Jan 2021 08:01:39 -0500
Message-ID: <60082B4E.4070506@isdg.net>
Date: Wed, 20 Jan 2021 08:08:30 -0500
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: dmarc@ietf.org
References: <eb3d06f-c89f-2511-3528-d421473e4d42@taugh.com> <a67a4e98-2be0-e2e2-2595-c12d9b87c4df@taugh.com> <7d3be6c4-aa17-3c34-d8f0-4df51e46ccc1@tana.it> <f12991fe-fded-6c0-528c-3b879b4a670@taugh.com> <8b6605de-ca01-904c-de78-deae254e0891@tana.it> <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com> <6006FA69.5000702@isdg.net> <CAHej_8=BJPezpi2KZ7GX-N__4Fqfc_b8vFNhu7_Typakv4iMig@mail.gmail.com>
In-Reply-To: <CAHej_8=BJPezpi2KZ7GX-N__4Fqfc_b8vFNhu7_Typakv4iMig@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/m3-yctw0sTvRwCJIM7YS0emwlh8>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 13:08:43 -0000

On 1/19/2021 2:22 PM, Todd Herr wrote:
>
> I'm sorry, but I'm not clear on what position you're advocating here.
> You assert that "any problem would be a known tag with new
> functionality than originally expected" (which would seem to argue for
> using a new tag such as ruap) but then you state that you're for a URI
> protocol method as part of the current tag (which would seem to argue
> against using ruap, but instead figuring out a way to add https: to
> rua), but then you state you don't see any issue with adding new tags.
>
> Can you help me understand your position better, please?

Yes, I saw. Allow me to clarify. Diffs in tags vs diffs in tag values.

Overall, I think we should not be "afraid" to invent use new tags. 
This is the main consideration I was pointing out.  Implementation 
MUST not fail with unknown tags.

However, with a known tag, in this case the reporting mechanism, I can 
see now the only delivery protocol defined was "mailto:"

I don't think we can add a "https:" here without probably causing some 
issue with some existing implementations, i.e. report generated by the 
assumed email address will fail (no delivery).  But we don't know for 
sure.  An implementation may not fail if its checking for the 
"mailto:" prefix. Reports would be skipped if HTTPS is not supported 
by the verifier.

I think we should add/defined the "https:" for the exist reporting tag 
ABNFs. The only one who will understand it are implementations with 
HTTPS delivery support only. Others will simply not be able to send a 
report to a domain that desires HTTPS delivery.

I think the worst that will happen is a non-https implementation will 
have one of the following:

1 - check for the prefix "mailto:" and extract the address at 6 position
2 - not check, assume plus 6 has the a valid address.

In each case, it will fail (no https delivery supported), #2 may be an 
a wasted delivery attempt to an invalid email address.

-- 
Hector Santos,
https://secure.santronics.com
https://twitter.com/hectorsantos



From nobody Wed Jan 20 06:39:19 2021
Return-Path: <dougfoster.emailstandards@gmail.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 A25B83A122D for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 06:39:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 iGGLybKAxzSx for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 06:39:16 -0800 (PST)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 298EB3A141A for <dmarc@ietf.org>; Wed, 20 Jan 2021 06:39:16 -0800 (PST)
Received: by mail-vs1-xe2b.google.com with SMTP id o186so5355786vso.1 for <dmarc@ietf.org>; Wed, 20 Jan 2021 06:39:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Rp6/NzYQDKO2vFvgch911G/CnQOE/r3iztbYmWrsWEE=; b=aFw1mHCWSleXc1FpnyDW+EOHSm2/jZaKB2JnIf36JxFnaBhrOysScH3eAiPlHEbjAW 6zSPGUerKHL7ZWrG8wF/BuwctfrWi3HqrJaeRfwJAD1YcLE16HJsaJs+aJOmD9gIzyZV 3I4vRaPlys20+/la1IdEBagt8S3wFKbsAhMJta8i3sqWBB/3wtalbyl4z6vQAhocliEi un1CnaERiyE11iLfA+X2DXOnbj+fmmlOXCTQfSHWZenhn/f6xPBXChODskf7KXa38L25 r+qOYVSXRBJkYA3gqrEqo6/nPHwZcnaRtTJMOq0CQ0e4tkRJG3n4Kj4PkFvJA20cUNrK GSzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Rp6/NzYQDKO2vFvgch911G/CnQOE/r3iztbYmWrsWEE=; b=GBPh+7Z77VydMhJUQ3/ef4hOBL6BK04+wPML+0/otJpPSvBC7k8txrt0Ga5SSTu0dS 1Fk1cYD1urbW/76KcWDtr0SmoNSwA2/oWgR/71gDbkVjmw8xHPLHNc+ofhQWIvcepX38 RApeuijj2nXhNKvc3/obhCiefSVtPMgfsEz5Y1pUa/7C3HNE4BRLlANNs+YkxAKBVaWl NxDG39nTrrQHn+7a0cDbwbfH4HmQYuEpLTUBGjCFlfd11Tq7K9K/ATrLJQYNMjN6dzdE 2ZN4Jw7y69fsxbbHVys+SIj36KBpsqA559erf3i9M8F5Bht24BVkgbD3d7Mavcgb7ZEP kB9w==
X-Gm-Message-State: AOAM5334UHWsmkG1wU6iVDE1UKtBKNRjix4I+eck25f5LnII94OZE8pF Tn2fgZgchV9FLU17kHW3YFr8r/QIV0sOvt/KeoU=
X-Google-Smtp-Source: ABdhPJwl8D5KBeM5TpsmHHtRTBbUwRlOPIXtHAVhSCieZ9xxRKNOkBtGLvwCGuWB575Fs/sZZevZh9UCT5hMVYot4wI=
X-Received: by 2002:a67:c29e:: with SMTP id k30mr3042243vsj.45.1611153555023;  Wed, 20 Jan 2021 06:39:15 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <CAH48ZfwOdZcJz02a76wktQDpV_dpPHKw+qJjE2ZCDvOqF3Ptdw@mail.gmail.com> <CAL0qLwZf+tEGZj0T6UmaNBSMC-nqSpfb5DAFh8+GDuP6F5pRkQ@mail.gmail.com> <CAH48ZfxJBwROXjtTr0YCOtBN0h_Q=jU559fAnUUNRpFjvEinRA@mail.gmail.com> <CAL0qLwYhjRx0nomXe_3KcKXTAmONce4bw6K6YLnNRLZJCzoYBQ@mail.gmail.com>
In-Reply-To: <CAL0qLwYhjRx0nomXe_3KcKXTAmONce4bw6K6YLnNRLZJCzoYBQ@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 20 Jan 2021 09:39:04 -0500
Message-ID: <CAH48ZfxYvCWROPROWZ5m844qxTRMNoMLtkMnAEtQnz4Yk00TkA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000536b2e05b955eb9e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/cTbqSZQJEcaFYZI53B40AW_HDLE>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Wed, 20 Jan 2021 14:39:18 -0000

--000000000000536b2e05b955eb9e
Content-Type: text/plain; charset="UTF-8"

I am happy to postpone the topic in the interest of moving the experiment
forward.
Ticket 97 has been created to discuss it later.


On Tue, Jan 19, 2021 at 6:23 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Tue, Jan 19, 2021 at 2:11 PM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> No Murray, I was speaking to the PSD document.
>>
>> PSD's entire purpose is to detect abuse of non-existent organizational
>> domains, so the definition of non-existent is crucial to its success.    I
>> believe the current language will produce false positives, albeit probably
>> a small number.    The current language is also more resource-intensive
>> than mine, although that is not my concern.
>>
>
> What I mean is: If we say PSD experiment participants evaluate the notion
> of "non-existent" differently than vanilla DMARC implementations, we have
> to account for that when interpreting the results of the experiment.  But
> the experiment as crafted is just to determine if the PSD algorithm as
> proposed is a useful improvement.  It seems to me that changing the nature
> of that test at the same time is scope creep that muddies the waters.
>
> -MSK
>

--000000000000536b2e05b955eb9e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am happy to postpone the topic in the interest of moving=
 the experiment forward.<div>Ticket 97 has been created to discuss it later=
.<br><div><br></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Tue, Jan 19, 2021 at 6:23 PM Murray S. Kuchera=
wy &lt;<a href=3D"mailto:superuser@gmail.com">superuser@gmail.com</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div dir=3D"ltr">On Tue, Jan 19, 2021 at 2:11 PM Douglas Foster &l=
t;<a href=3D"mailto:dougfoster.emailstandards@gmail.com" target=3D"_blank">=
dougfoster.emailstandards@gmail.com</a>&gt; wrote:<br></div><div class=3D"g=
mail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"l=
tr">No Murray, I was speaking to the PSD document.=C2=A0 =C2=A0<div><br></d=
iv><div>PSD&#39;s entire purpose is to detect abuse of non-existent organiz=
ational domains, so the definition of non-existent is crucial to its succes=
s.=C2=A0 =C2=A0 I believe the current language will produce false positives=
, albeit probably a small number.=C2=A0 =C2=A0 The current language is also=
 more resource-intensive than mine, although that is not my concern.=C2=A0 =
=C2=A0</div></div></blockquote><div><br></div><div>What I mean is: If we sa=
y PSD experiment participants evaluate the notion of &quot;non-existent&quo=
t; differently than vanilla DMARC implementations, we have to account for t=
hat when interpreting the results of the experiment.=C2=A0 But the experime=
nt as crafted is just to determine if the PSD algorithm as proposed is a us=
eful improvement.=C2=A0 It seems to me that changing the nature of that tes=
t at the same time is scope creep that muddies the waters.</div><div><br> <=
/div><div>-MSK<br></div></div></div>
</blockquote></div>

--000000000000536b2e05b955eb9e--


From nobody Wed Jan 20 10:58:31 2021
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 D7A403A11FB for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 10:58:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 Z_8AGPw7vLPt for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 10:58:27 -0800 (PST)
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 0F9903A11F9 for <dmarc@ietf.org>; Wed, 20 Jan 2021 10:58:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611169103; bh=F3N1CtVrqHWSRwcjJxpGC4OSJtLDZeROO1h4h6BGXF8=; l=3826; h=To:References:From:Date:In-Reply-To; b=AcipXkMcPSKvcq2SsUGETCkzbCFUYyCZDkdU/6g0qxOVQxiPPn9oj0avS54BlD6Sr 71JRtm5dMnO5CZfQWBdb8R0Ziv0/t9lnk/XnxwI2OJIzGkbAxOqPaRbE6MfdEEwMkB avKdDopapgUQnzOVh92HOXSED23o9g6Dt1LAiQBTZXWawI2imtwoNsmge/gRq
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0D1.0000000060087D4F.00005C45; Wed, 20 Jan 2021 19:58:23 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org, todd.herr@valimail.com
References: <20210120023151.3C86A6B7C86C@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <ccc2489b-742d-acca-58db-55519764b02f@tana.it>
Date: Wed, 20 Jan 2021 19:58:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210120023151.3C86A6B7C86C@ary.qy>
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/sBl9yn7YcGmjlyuj-nCuu-WnMsU>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 18:58:29 -0000

On Wed 20/Jan/2021 03:31:51 +0100 John Levine wrote:
> In article <CAHej_8=K_x5xOw47XBtPYBWzCbfpPSAs=i9WoweZnaa1OFc1uQ@mail.gmail.com> you write:
>> Can you provide more details, please?
>>
>> Are you receiving reports by HTTPS, or have you not seen any reduction in
>> reports, or both, or other?


No, I didn't put a real server's URL.  Just this:
"v=DMARC1; p=none; rua=mailto:dmarcaggr@tana.it, OR-https://service.example/report/; ruf=mailto:dmarcfail@tana.it;"


> I didn't try Ale's OR- thing but I did add an https URL to my rua= tag and set up
> a web server to catch any POST or PUT traffic.


John's record looks more workable, but it's still fluffy:

"v=DMARC1; p=none; rf=afrf; rua=mailto:dmarc-a@abuse.net,https://dmreport.abuse.net/dmreport/; ruf=mailto:dmarc-f@abuse.net"


> I suppose the good news is that nobody implemented the underspecified
> report URL in one of the earlier DMARC drafts.


It is not underspecified.  It specifies the /mailto:/ scheme.  With forward-looking shrewdness, it further specifies:

7.2.1.2.  Other Methods

    The specification as written allows for the addition of other
    registered URI schemes to be supported in later versions.

However, one cannot make guesses about what a receiver would do with, say, rua=fax:+13165550321.  For mailto: they know to send a gzip attachment.  Nothing is specified for https:, even if the scheme is known.  OR-https: is an unknown pseudo-scheme which, as far as parsing is concerned, can be discarded just like https: and fax:.

Likewise, the spec provides for a registry of tags and says that unknown tags must be ignored.  Therefore it is possible to safely add a new tag.  Let's see two cases:

"v=DMARC1; p=none; ruap=mailto:dmarcaggr@example.com, https://service.example/report/; rua=mailto:dmarcaggr@example.com, mailto:report@service.example;"
"v=DMARC1; p=none; ruap=https://example.com/dmarcaggr, https://service.example/report/; rua=mailto:dmarcaggr@example.com, mailto:report@service.example;"

Using my OR- syntax, they would be, respectively:

"v=DMARC1; p=none; rua=mailto:dmarcaggr@example.com, mailto:report@service.example, OR-https://service.example/report/;"
"v=DMARC1; p=none; rua=mailto:dmarcaggr@example.com, OR-https://example.com/dmarcaggr, mailto:report@service.example, OR-https://service.example/report/;"


One last case.  The user has an oldish mailto:-only record, the service introduces https: for those who can support.  The service can override the rua= thanks to step 8 of Section 7.1, Verifying External Destinations:

    8.  If a "rua" or "ruf" tag is thus discovered, replace the
        corresponding value extracted from the domain's DMARC policy
        record with the one found in this record.  This permits the
        Report Receiver to override the report destination.  However, to
        prevent loops or indirect abuse, the overriding URI MUST use the
        same destination host from the first step.

So we have:

at _dmarc.example.com:
"v=DMARC1; p=none; rua=mailto:dmarcaggr@example.com, mailto:report@service.example;"

at example.com._report._dmarc.service.example the verification record can specify a preferred reporting address:

"v=DMARC1; ruap=https://service.example/report/; rua=mailto:report@service.example;"

(Question: is it necessary to also specify rua= if it is unchanged?)

or it can use OR- syntax:

"v=DMARC1; rua=mailto:report@service.example, OR-https://service.example/report/;"


IMHO, both methods are valid and equally well interoperable.  We should choose the one that can be more easily and clearly specified.

For OR-, it is an advantage to be able to keep step 8 above unchanged.  OTOH, the concept of pseudo-scheme requires a new paragraph to be explained.  Perhaps we should provide tentative text, rather than examples?


Best
Ale
-- 
























From nobody Wed Jan 20 11:19:29 2021
Return-Path: <johnl@taugh.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 ABFA43A12F8 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 11:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=i393R3M8; dkim=pass (2048-bit key) header.d=taugh.com header.b=PRoo5qX+
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 CBHqx7t-IBaB for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 11:19:26 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D06FF3A12F7 for <dmarc@ietf.org>; Wed, 20 Jan 2021 11:19:25 -0800 (PST)
Received: (qmail 82676 invoked from network); 20 Jan 2021 19:19:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=142f0.6008823b.k2101; bh=1TS/SAoeLvfFD6ux2/0qLjW7lhKdMbNn9QUy0A+WUfs=; b=i393R3M8Y9VW4UtaNW20QIeGHC7VqaDc82vHdMaULaMeokBvuzETgj5C3kLEoS0IkkBQizvk7v2eO0ZIxG/fpoe98HIHMzJRdg4foYb8Y05VMJFNVpLZb5SVzfnGTTSMHQGyGSla4lW3HDRWJKYhLlqak90S22MaItXwmY9WI4f1sJ06ppK7Lyj7wNeytOvcjsz2UUrntm7grGnvuCTWWUqsM2Keeg8J8Fvwe+08urwZzUaujU8Tuw8aFeD5E69ybAlC2r+EF7Kpy53UWAfRmNJ8lWDT1/EsgoiKqzTYMlqLXongG/os+wJogy56M9Rkja91Kg7OxNAgbjmRM6kCgg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=142f0.6008823b.k2101; bh=1TS/SAoeLvfFD6ux2/0qLjW7lhKdMbNn9QUy0A+WUfs=; b=PRoo5qX+karWdvnWaMlOrzsEoagLV9Ffeke6Pbam0DEb/gdOnA7BkQMK7mXpTblEO4xBa3DAArxmMCv7Wtc7xpykNf2MEKt9iHpSoaBGeOzxqojKPFKfjIuFTECqN+bxYPPwCKM3voHNNC6ZLaot/UcaR/7zLHlYuBveNxe/HSDVeMPBKL2dRqaaoJrHr9ATEEXHxUH3pX9H/ktIuyuvpaSePKREFBcpPZa8+YilCP2RDxrT+V/qcw90yw1/JXzSZwEq3LRRVk9j9jGSFMtW49B1uSw1FtoEWyTXzYPCpEZD062WPZHqk54TuCr8X/gT103Q6eqbxSCXu3evwA/1Yg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 20 Jan 2021 19:19:23 -0000
Received: by ary.qy (Postfix, from userid 501) id 2A8AC6BBF47D; Wed, 20 Jan 2021 14:19:23 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 25FBB6BBF47C; Wed, 20 Jan 2021 14:19:23 -0500 (EST)
Date: 20 Jan 2021 14:19:23 -0500
Message-ID: <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <ccc2489b-742d-acca-58db-55519764b02f@tana.it>
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/k1Gfm0RXCNraBG08LuRcJKbvXq8>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 19:19:28 -0000

On Wed, 20 Jan 2021, Alessandro Vesely wrote:
> John's record looks more workable, but it's still fluffy:
>
> "v=DMARC1; p=none; rf=afrf; 
> rua=mailto:dmarc-a@abuse.net,https://dmreport.abuse.net/dmreport/; 
> ruf=mailto:dmarc-f@abuse.net"

Whaddaya mean fluffy?  Try a PUT or POST to that URI and it'll work.

>> I suppose the good news is that nobody implemented the underspecified
>> report URL in one of the earlier DMARC drafts.
>
> It is not underspecified.  It specifies the /mailto:/ scheme.  ...

Early drafts had an http PUT with some error that would have prevented it 
from working.  It was removed before 7489 was published.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Wed Jan 20 11:28:30 2021
Return-Path: <mike@fresheez.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 7F8EE3A1333 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 11:28:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 uNMaZwI2GZ4G for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 11:28:28 -0800 (PST)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A9C23A1332 for <dmarc@ietf.org>; Wed, 20 Jan 2021 11:28:27 -0800 (PST)
Received: by mail-pj1-x102e.google.com with SMTP id g15so2839452pjd.2 for <dmarc@ietf.org>; Wed, 20 Jan 2021 11:28:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=qz2vSwDSn0LqqE8gSzw66WjZ9+GYEHFyjf/XYgi2Xho=; b=jpmEbbXt+ZDr4rIXUa+4czLREjYY+YW8hqdii/wfwhe1zPi0nqN9eBImuWpdvVqx1d UvogDJxigANpIOKRSaqNLlORvoV8P4pQ5tZVFxbHeLZMRSX7zFhKTUIpTF2wXAYC48YN 0cG3nsgXJc6J1qu7KM1tWjOTtMHjDo49A5eK/Lkoh1Mi7oT9IcXKfDcsNEYdrSg1g/GV ezFwlbi+NeLLIOSSuDscDgbdUHgdKsEtniYOsTVwdHCDBU9bToAaLmpaGY1cXOjbNmgH K4fOjZ2GkSZIJ20hAcl/NqA8vPcSthwpm1gM3vzFCSOHgbliXV8EybxCqSi4xsOUn+eg swIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=qz2vSwDSn0LqqE8gSzw66WjZ9+GYEHFyjf/XYgi2Xho=; b=XPHeI9KI7U2l1DBdcT2wJjaigMtYcvhHJx5iO0WfImgNqbymwy1gONqMRKl7Onegut VFwU5/zGLMyzWQ0nTy+7ZeiwRPdq1Y3tQKW79BhLzhZM0lBwZSjJRwgCK/vavNVcGtoK EAMd1MLFjvQ9EGr3n/97ChkvqqGG8ysRGPFfE7fpkVal360bX8rlwpyKOmSaW8+G4hDQ RLFxte+GWZ40nPRu8PX/ATMb1dO3tqZGpgvUhGfrbx4SY4sNziVWMojex8ZDZ7EArIRg 4ooWuOhpGQ/9BLU/y5L4TRetZb7SQB14R5v9lvfrvGsylmlNQcIBqP0lZWtxRzO0FKjH TL8w==
X-Gm-Message-State: AOAM532tRaljawtuN1sa9ngmS6GBnWTxph5gX1WudrlGHIFKRXTvxG30 pBTIlK5EqBgGe6RcI2pJukzlyMvy/It9+Q==
X-Google-Smtp-Source: ABdhPJx5Jh6HYQG/tf/wqwJ6D0dbhtkk4dQ9rf4RypRPH/43yqupGfDMuHsyEaRGpgKPPBoLLUx5jA==
X-Received: by 2002:a17:903:18a:b029:de:5aaa:e246 with SMTP id z10-20020a170903018ab02900de5aaae246mr11137387plg.70.1611170907004;  Wed, 20 Jan 2021 11:28:27 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id b188sm2954786pfg.68.2021.01.20.11.28.25 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 11:28:26 -0800 (PST)
To: dmarc@ietf.org
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it> <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <78ab729e-7ec5-b154-8e29-b02197933f59@mtcc.com>
Date: Wed, 20 Jan 2021 11:28:24 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com>
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/I_QuBgWDN_YeCw0q2DR-1Pjp_OM>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 19:28:30 -0000

A little off topic, but is there any normative text in DMARC about the 
authenticity of the reporting? It seems like there ought to be normative 
text that the report should have a valid DKIM signature from the domain 
reporting. I'm not sure how you'd go about doing that with HTTPS though 
since client certs are essentially nil, and the normal way to do 
authentication is by creating an account.

Mike

On 1/20/21 11:19 AM, John R Levine wrote:
> On Wed, 20 Jan 2021, Alessandro Vesely wrote:
>> John's record looks more workable, but it's still fluffy:
>>
>> "v=DMARC1; p=none; rf=afrf; 
>> rua=mailto:dmarc-a@abuse.net,https://dmreport.abuse.net/dmreport/; 
>> ruf=mailto:dmarc-f@abuse.net"
>
> Whaddaya mean fluffy?  Try a PUT or POST to that URI and it'll work.
>
>>> I suppose the good news is that nobody implemented the underspecified
>>> report URL in one of the earlier DMARC drafts.
>>
>> It is not underspecified.  It specifies the /mailto:/ scheme. ...
>
> Early drafts had an http PUT with some error that would have prevented 
> it from working.  It was removed before 7489 was published.
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Wed Jan 20 13:21:27 2021
Return-Path: <mike@fresheez.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 3D1713A14FE for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 13:21:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level: 
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 6dtgi12ZplyH for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 13:21:24 -0800 (PST)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2602D3A14C2 for <dmarc@ietf.org>; Wed, 20 Jan 2021 13:21:24 -0800 (PST)
Received: by mail-pj1-x102b.google.com with SMTP id m5so3027989pjv.5 for <dmarc@ietf.org>; Wed, 20 Jan 2021 13:21:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=G4OEIiD4NlCWS7DVUZ50D/k1UnOemAhLvTDoYJhpq3k=; b=W8RCaE8L0vksBfFxiGFjRRV78w0qYkIcOzMlKFzSVm6K4NHit5E8DKfVNLqGJOagL4 zN4d8zEHlZMz5+VfbaHw3vaMpv3YNMtl1XCzhvgqRm0Bzes1gPFNy5rAGRtmInj1kWef Kaaic8wwBA4lfeFx8WNp4fln2ZOI6+pzApQwXzetA2FCvn/wyh6f4B+6JE1Jd5yLYiqB VNtvGO7OE7HA51ksT65to42+PWwTjq4CzgdnW0WKYBv3BhjtgPkgWeGpQGXgM6ajciJU 36EMa1AO9mCp2T61zo+LzykMBoQj4ko/SOtzsY4b1Yd7PGCIx5E3T+wirFg3cdIByYMn JwkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=G4OEIiD4NlCWS7DVUZ50D/k1UnOemAhLvTDoYJhpq3k=; b=b6va332jQnO4BPPZlEHhrYO9FGUoEE1Nx9JfOfzNpk6UKtojbuekx9NprHzoaQLlF8 f0cN0cS9OPgzRp1h+qWE34m7BJyIYLLK+XprFBz01YL9qQfT+4eEkNF/5V5FIikEeUbw pmwE2cRaldhnSXyVbCxlQOXeokJjlrvz228EnudTqqx1BKTUqBWW9QYcfj7efnKM+3SF AhH7FH6yMdTdqI8YvR2ew061OF34fuRk0q87SeM0tNm/29q0Y74PnNlVxpPiephV0koJ sV9sdeCqJswTb6n11F8/+/ojW5/qDphZR3xeGSARSe4rPu+zLY6XK/Gn9URs5Xh42Y6P 9L8Q==
X-Gm-Message-State: AOAM531+KqlnwKzsdYbNnRd3iSvQhCXcqQWQTrTZfqA6or21BM3idH6s eRQoTWWI2qcITN/iTTDoKnpkkPEEc4tZKA==
X-Google-Smtp-Source: ABdhPJz3yBWHahIM7du0eDlnTlwkoapj0i4Xit2T8nr4Pvbs6hSXgxZIFFVtRRHHD6R9FJ+gQUcIHg==
X-Received: by 2002:a17:90a:7f8f:: with SMTP id m15mr160692pjl.214.1611177683101;  Wed, 20 Jan 2021 13:21:23 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id d4sm3244339pfo.127.2021.01.20.13.21.22 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 13:21:22 -0800 (PST)
To: "dmarc@ietf.org" <dmarc@ietf.org>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com>
Date: Wed, 20 Jan 2021 13:21:21 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/raKUOp-kYwGEbZDUlgJ8-kDjv2E>
Subject: [dmarc-ietf] Authentication of reports
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: Wed, 20 Jan 2021 21:21:25 -0000

I just scanned through DMARC and I couldn't find any security 
requirements/mechanisms for the failure reports. I would think at the 
very least the receiver consuming the reports ought make certain that 
the report at the very least have either a valid DKIM signature or a SPF 
pass. Unauthenticated data is always the source of mischief, and I'm 
sure that there have to be attacks that are possible with 
unauthenticated reports. At the very least this should be a security 
consideration, and most likely should have some normative language to 
back it up.

Since I'm sort of new, it's been unclear to me whether whether having a 
new https transport mechanism is in scope or not -- it seems to come up 
pretty often -- but I'm not sure how people would propose to 
authenticate the report sending client. That seems to me to be a basic 
security requirement for any new delivery method. The problem here is 
there isn't a client certificate to determine where the report is coming 
from or any other identifying mechanism. An alternative might be to DKIM 
sign the report itself, but the long and short is that it would need to 
be addressed.

Mike


From nobody Wed Jan 20 13:37:46 2021
Return-Path: <johnl@iecc.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 63E763A1514 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 13:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=FY6sX3A3; dkim=pass (2048-bit key) header.d=taugh.com header.b=W8i0RqLS
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 0LeWbrCp_KiK for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 13:37:44 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 E46253A1512 for <dmarc@ietf.org>; Wed, 20 Jan 2021 13:37:43 -0800 (PST)
Received: (qmail 18799 invoked from network); 20 Jan 2021 21:37:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=496c.6008a2a6.k2101; bh=HgyMvcFLtQzavXkRwn+I09MPew09JT5+R8wDOK+wrrw=; b=FY6sX3A303UfB/XUewVasxeRB0uirl3K5h1xPEmnKf/6l5WrFWUtEx3l8NrXHpA6n09DWoSS/w/xm9fk0SN7NCsXtNuMm/LxQ2x1RPaMgymCFl92k3Bplh5Xxzz9WC7+XXIP09vRqEMEtlhY5PAMMEce3J1NwI1K4neB8wkeaK20/DMGYBxT5Tnta1vKhnyThmhNG0YahO8fvv9kn4fZRNL8C75XoEkc/k8zkSsCHNKFVtl4KsLaWyLujp3XADUj/Qj1jyPhF7XAcG/O0751QH9bR2xy7vjS6bxa+6X8NARi+SjpZUTj6w7J2I2xUiLziCS/vscvn0NwKzcbMcQMIg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=496c.6008a2a6.k2101; bh=HgyMvcFLtQzavXkRwn+I09MPew09JT5+R8wDOK+wrrw=; b=W8i0RqLScFOFTL3C6VvIHkV8H0FMbyhjj414R5bddjBYO37MDiryZgJhQh8qMC3/d+nHrKWdoK0q9z8MbctXErGsh1mHGCzYkzxU7+I1qOlEVeVABgensA1QkkyUvv6HbGr/UQSSsOx3T5PJYmIcv0S4jwg6XuXqScP5I+aDH4QceFtQvZ3GoroD4GOFWmYCXvlKJZKAaMBLMG2ecMyJE3Z0ivfAeo42pBaevFuv1FHbHDMAFh7ydkHYnftA8BYT7v4R9qyczXv1rjVNJSY4Kr/nAl3vx6JnDjprM2ojUCtv5SSEEZe+Z6r/iInyoV4hrQxf5iYDsoQEtLSNPveZrw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 20 Jan 2021 21:37:42 -0000
Received: by ary.qy (Postfix, from userid 501) id 991976BC1F90; Wed, 20 Jan 2021 16:37:42 -0500 (EST)
Date: 20 Jan 2021 16:37:42 -0500
Message-Id: <20210120213742.991976BC1F90@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: mike@mtcc.com
In-Reply-To: <78ab729e-7ec5-b154-8e29-b02197933f59@mtcc.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YCu6G9VpxlTlvL9CYbtHIzj-kKk>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 21:37:45 -0000

In article <78ab729e-7ec5-b154-8e29-b02197933f59@mtcc.com> you write:
>A little off topic, but is there any normative text in DMARC about the 
>authenticity of the reporting?

See section 7.2.

 It seems like there ought to be normative 
>text that the report should have a valid DKIM signature from the domain 
>reporting. 

I've been getting DMARC reports for nearly a decade and do not ever
remember getting one that looked fake. What would be the point? I
don't see this as a problem that needs solving.

It's a good idea for your reports to be aligned but only to prevent
useless reports and the failure loops that some people were
complaining about.

R's,
John


From nobody Wed Jan 20 13:51:33 2021
Return-Path: <mike@fresheez.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 E10F93A152B for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 13:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 kx8bAF2Wva6m for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 13:51:30 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBFA93A152A for <dmarc@ietf.org>; Wed, 20 Jan 2021 13:51:30 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id lw17so3755622pjb.0 for <dmarc@ietf.org>; Wed, 20 Jan 2021 13:51:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=XHlmb0bll8e/DG7O3Y3X2A5y2giprFi1K8IGCxX7sUs=; b=U79t6/DC6jlrenoqTCZycsyHjf1zEHbm18N8B/tanDPRyqDRKVkH1L7VYNEoy9KA4P /MvtrV2dOG0emtt5bMtw4YPR9UVcS6fmZLmLMrWwfYVKNrq7wV0ER80qaHUHGdKxLj/i MVz+x2IfwUWmcglAu1e6Yc1hbBYl/WTSWZFAL3CAsgjkSS1xwhwf9s7LC+v72XOdSg80 O2ixdOR2jA6s1bh8tTtATdgbvR0v77+dEwBsrY+xsbv9FiPGT56ZP0fRG/w4ig0NGz5W amY7xeBkabnCUAkxTjOcSMhWtQz51Nog5SX1kh0ZwfHjdfW+xX0x+oAp2265dSb3NmO7 qQ1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=XHlmb0bll8e/DG7O3Y3X2A5y2giprFi1K8IGCxX7sUs=; b=AkJ4/huw2B1FsQTmNwpGX1oAWvyCyWReRqb1pKBw/kmyxFYRqFgygsoZPbcocv9lks sgl7Fd7IpgfsOd2eViBvzvE6CVnsglNxMr2Wrfliw6WSRzJeP4IGGRI/20t7BjzFOezN ulLgbVFDgoKYfjGIpnR4sTJAdaOXYUUagBs8LOdTR1c4JlR0w68ndqK5+H/W+eo+0iNJ kgL9JgpJly5Z+M6RKf2QdO/sl2AVCe4oyr7yMzqmmxjY64pC9tYPqYA8mZPECrkXcwse xuETx42jbf7TDElwbW2OVQDLQOjCJlnzJ2C2lNsohX7YfP/3MbrOXTuETBYQN0+zgBlO LQ0w==
X-Gm-Message-State: AOAM531Tn0Y8X1WiCOxoAo9/2aUUGgKnptqeWS++2Me1OHxvDVAnJy5p q/G1Lf8VYjzpa0beBDYMyQZjXkc5xWiLYA==
X-Google-Smtp-Source: ABdhPJyyXdXsvMRwY28Ob/kSheess7j+u2hViHQ1T5txIzMF9GThJL6iRQtm5NW/1E6bNlVfK47p8w==
X-Received: by 2002:a17:902:d48f:b029:de:8c5b:656 with SMTP id c15-20020a170902d48fb02900de8c5b0656mr11805473plg.51.1611179489470;  Wed, 20 Jan 2021 13:51:29 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id j14sm3261429pjl.35.2021.01.20.13.51.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 13:51:28 -0800 (PST)
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210120213742.991976BC1F90@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <1cb8436f-fd22-e215-9620-9540c28e8321@mtcc.com>
Date: Wed, 20 Jan 2021 13:51:27 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210120213742.991976BC1F90@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xkJo5LvK9y0I9z4jE_Ud7yLYP6Y>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 21:51:32 -0000

On 1/20/21 1:37 PM, John Levine wrote:
> In article <78ab729e-7ec5-b154-8e29-b02197933f59@mtcc.com> you write:
>> A little off topic, but is there any normative text in DMARC about the
>> authenticity of the reporting?
> See section 7.2.


Sorry, I'm not seeing it.

>
>   It seems like there ought to be normative
>> text that the report should have a valid DKIM signature from the domain
>> reporting.
> I've been getting DMARC reports for nearly a decade and do not ever
> remember getting one that looked fake. What would be the point? I
> don't see this as a problem that needs solving.
>
What could possibly go wrong has an extremely poor track record. In the 
case of email it's an easy fix.

Mike


From nobody Wed Jan 20 14:56:47 2021
Return-Path: <superuser@gmail.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 B63A33A15AF for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 14:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cjEgDQV5LQKu for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 14:56:44 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFFB43A15AD for <dmarc@ietf.org>; Wed, 20 Jan 2021 14:56:43 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id j17so36547vso.9 for <dmarc@ietf.org>; Wed, 20 Jan 2021 14:56:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UlnepI50Pbm7nlUD7T2+iQWuE8+81RKjSDLTl3EXkO0=; b=PS5c7oYOcZraXx/9KIfW1wWcB0tWUjSuoKypoyY45FsLNaCXMjZVnsNfg4TBuzpJOj JD8e/jKBdNjQD41HnJHW6eboerdDK+6t83Z6WoL2IVAPklpRyqYef3+wXntYhHuBzD1g hShCBGiRZ5YttscZ7LdSXJQ6RUsn8btPBxxPdKSVre04XZGsJMc8pic+EHvsUxlIbXF3 q0lBvX5YiYxHzfPgjecAFH28NevGlrT/ZMg0onZTOPwCLIc+KQjoNrYktO6x4XhA9Y+U okUHcIZRmq1NQficRqAhX0HXuc1OT1Ub08rapK8rMHpIYeZhjW5l4K6qm+RJVZWlBt+2 Wy1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UlnepI50Pbm7nlUD7T2+iQWuE8+81RKjSDLTl3EXkO0=; b=LriuwqgOfpgcc+Hqg4idR/NzB8zZnrETH1WBYS4IdTv0zQRhQkSV7ZD5PLXrjEzmfx L9xpfc5d/W0ohcO7Sp2qC6O9MqIW7fgljWRwSTPpIn3LciUXdaUQubjsCeKS/+DtYHj/ JfY+PMJythLNHcuNkJOS0SPOPiTcLniE2M6XySsjYjVzABxhjxeDiONQ6KkIohfKzhk2 Y3Uu6MF+j8UFzSXR8N2wNCj9Bel4K0FppH1sfisfFyVvvyBDPAmxdx39vU6/xX+2NSUY cB8qhC6frxjICgtyYt0/jfq0Ac287hXc20wlkh96nSMonNFXlvzKIHdAB6mheXQ0vjfP dlbQ==
X-Gm-Message-State: AOAM531oMhWsnALpwg4i8aeZASmaLKSfVm16acXinacW7RCXY85XbyRe IoPRtXff7gHyOTT7o7lbHddTYcQK6MZd/Wx1dVPDE8PWIa4=
X-Google-Smtp-Source: ABdhPJwk/3E2MRPNNus1iesFHJTp6FR95bB5EG32GXcsxyHo9Vur4jl/dkjiIbIHE4Xm/ddU2Lj6V/I0m0pVwNxqKWY=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr8504840vsy.54.1611183402743;  Wed, 20 Jan 2021 14:56:42 -0800 (PST)
MIME-Version: 1.0
References: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com>
In-Reply-To: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 20 Jan 2021 14:56:31 -0800
Message-ID: <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000063808e05b95cdefa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/RykZYRzKXytx9eLlVK6Nm_yktc0>
Subject: Re: [dmarc-ietf] Authentication of reports
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: Wed, 20 Jan 2021 22:56:46 -0000

--00000000000063808e05b95cdefa
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 20, 2021 at 1:21 PM Michael Thomas <mike@mtcc.com> wrote:

> I just scanned through DMARC and I couldn't find any security
> requirements/mechanisms for the failure reports. I would think at the
> very least the receiver consuming the reports ought make certain that
> the report at the very least have either a valid DKIM signature or a SPF
> pass. Unauthenticated data is always the source of mischief, and I'm
> sure that there have to be attacks that are possible with
> unauthenticated reports. At the very least this should be a security
> consideration, and most likely should have some normative language to
> back it up.
>

I thought the usual rules about when you should or shouldn't trust a
message ought to be applied, but I guess we never actually said that in the
document.  We certainly could.

Since I'm sort of new, it's been unclear to me whether whether having a
> new https transport mechanism is in scope or not -- it seems to come up
> pretty often -- but I'm not sure how people would propose to
> authenticate the report sending client. That seems to me to be a basic
> security requirement for any new delivery method. The problem here is
> there isn't a client certificate to determine where the report is coming
> from or any other identifying mechanism. An alternative might be to DKIM
> sign the report itself, but the long and short is that it would need to
> be addressed.
>

As I recall DMARC originally (in its pre-RFC versions) did have "https" as
a supported scheme for "rua", but since nobody implemented it during the
years DMARC was in development, it got dropped before publication.

-MSK

--00000000000063808e05b95cdefa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jan 20, 2021 at 1:21 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">I just scanned through DMARC and I couldn&#39;t find any security <=
br>
requirements/mechanisms for the failure reports. I would think at the <br>
very least the receiver consuming the reports ought make certain that <br>
the report at the very least have either a valid DKIM signature or a SPF <b=
r>
pass. Unauthenticated data is always the source of mischief, and I&#39;m <b=
r>
sure that there have to be attacks that are possible with <br>
unauthenticated reports. At the very least this should be a security <br>
consideration, and most likely should have some normative language to <br>
back it up.<br></blockquote><div><br></div><div>I thought the usual rules a=
bout when you should or shouldn&#39;t trust a message ought to be applied, =
but I guess we never actually said that in the document.=C2=A0 We certainly=
 could.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
Since I&#39;m sort of new, it&#39;s been unclear to me whether whether havi=
ng a <br>
new https transport mechanism is in scope or not -- it seems to come up <br=
>
pretty often -- but I&#39;m not sure how people would propose to <br>
authenticate the report sending client. That seems to me to be a basic <br>
security requirement for any new delivery method. The problem here is <br>
there isn&#39;t a client certificate to determine where the report is comin=
g <br>
from or any other identifying mechanism. An alternative might be to DKIM <b=
r>
sign the report itself, but the long and short is that it would need to <br=
>
be addressed.<br></blockquote><div><br></div><div>As I recall DMARC origina=
lly (in its pre-RFC versions) did have &quot;https&quot; as a supported sch=
eme for &quot;rua&quot;, but since nobody implemented it during the years D=
MARC was in development, it got dropped before publication.<br></div><div><=
br></div><div>-MSK<br></div></div></div>

--00000000000063808e05b95cdefa--


From nobody Wed Jan 20 15:00:08 2021
Return-Path: <seth@valimail.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 742793A15B1 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:00:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 9I2CveJwLJlp for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:00:03 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D5D43A15B0 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:00:02 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id n18so31635vsa.12 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:00:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=jwxJZoK2Jlzi3ytfQONIq1XCD4jVtkIkDMjORE9Avs8=; b=fJC4Q8+D+4NNqlLTRy9mwvkwiopEKXYUhybx5qq4OeEE7AMPCXiCZqxa0UNdxI7z7r SxcPvIBo+Lo9kDLisp+ooC7BkR6soPk9lqHNnrigV9ocoAbkUWa7Rlq9d0NsSYRU5oei eIls2iJeZZ8/3Cg9VUEEr99a5xKzH/Htz+mZjYVTDxm1NunaktW9gu+PIAk/OSeoRPqg gJT7UEuUXFB+hE0fb/YIAlsJisbwQVUiDtY+SYme9M9U6oZWZrqlYVOmfpa1WQxukug8 5S3EkPUA+sqnyYXFh0IkwAQkEo7bv3oVoVDYpLTa6eMmHwRrgad6a2Q15fXKGcq3M0pe OBtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=jwxJZoK2Jlzi3ytfQONIq1XCD4jVtkIkDMjORE9Avs8=; b=jN4Q88nfUGLFWWiXX6A43oQp4eeTWW894YP1QRkfbByuF6zkWMXbHK56dC/M+WvRZa uS1aR/cXm83aixc7Av68Y83AkZhxIy1K4eiosvVuVC8n7WC41cWjIyMzQrWFwpn6QPZg 9V9MqbjJkesMacR5D/w2QxcdmC6VLUJGd1iIKtvj1j6RIlzcq5PICLsZD3jqr7KlBQfA 8PoOrcaOKElu6E9NwRvDqIMsC2qpUtsfD9uNe1/nDL5hns2Sed0Djj3p6mizSN5T5V8i nQ2RJQ4jfYzd0ukJ2Go9A1l3Nt3mtcrhKlFOnIa75vSUo3xojED0p4TNAu3iCGL0jyE8 eptQ==
X-Gm-Message-State: AOAM5335n63qh8Bk7po+T2y7523iaepN3yK7XiT6Mi0KptwEZe7KZyVO N4XUyc1XyRWLlQDbFUDRG1hvgGHFlj5OmZOIlVtwnPSepQo=
X-Google-Smtp-Source: ABdhPJzZMXkRq5tlJts0hM7dMWpibJjWo60u6pnWvnYdm/HO/kHJd5V50UMKyYAkA3pXqsnAQdtMzN4LbjLYd5ucybU=
X-Received: by 2002:a67:efd9:: with SMTP id s25mr8187952vsp.56.1611183601538;  Wed, 20 Jan 2021 15:00:01 -0800 (PST)
MIME-Version: 1.0
References: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com> <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com>
In-Reply-To: <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com>
From: Seth Blank <seth@valimail.com>
Date: Wed, 20 Jan 2021 14:59:50 -0800
Message-ID: <CAOZAAfNw1amAfubGBMXY_FzDOaPzKkBb0TiaexZhk+JZXeFZ=Q@mail.gmail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003ce6f405b95ceaa2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YgyiZ8qFz9elHjbTXc7WAJpBGCM>
Subject: Re: [dmarc-ietf] Authentication of reports
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: Wed, 20 Jan 2021 23:00:06 -0000

--0000000000003ce6f405b95ceaa2
Content-Type: text/plain; charset="UTF-8"

Michael, please open a ticket. I think you're right and some consideration
around this is needed in the document.

On Wed, Jan 20, 2021 at 2:56 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Wed, Jan 20, 2021 at 1:21 PM Michael Thomas <mike@mtcc.com> wrote:
>
>> I just scanned through DMARC and I couldn't find any security
>> requirements/mechanisms for the failure reports. I would think at the
>> very least the receiver consuming the reports ought make certain that
>> the report at the very least have either a valid DKIM signature or a SPF
>> pass. Unauthenticated data is always the source of mischief, and I'm
>> sure that there have to be attacks that are possible with
>> unauthenticated reports. At the very least this should be a security
>> consideration, and most likely should have some normative language to
>> back it up.
>>
>
> I thought the usual rules about when you should or shouldn't trust a
> message ought to be applied, but I guess we never actually said that in the
> document.  We certainly could.
>
> Since I'm sort of new, it's been unclear to me whether whether having a
>> new https transport mechanism is in scope or not -- it seems to come up
>> pretty often -- but I'm not sure how people would propose to
>> authenticate the report sending client. That seems to me to be a basic
>> security requirement for any new delivery method. The problem here is
>> there isn't a client certificate to determine where the report is coming
>> from or any other identifying mechanism. An alternative might be to DKIM
>> sign the report itself, but the long and short is that it would need to
>> be addressed.
>>
>
> As I recall DMARC originally (in its pre-RFC versions) did have "https" as
> a supported scheme for "rua", but since nobody implemented it during the
> years DMARC was in development, it got dropped before publication.
>
> -MSK
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000003ce6f405b95ceaa2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Michael, please open a ticket. I think you&#39;re right an=
d some consideration around this is needed in the document.</div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 20, =
2021 at 2:56 PM Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@gmail.c=
om">superuser@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jan 20, 20=
21 at 1:21 PM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=3D=
"_blank">mike@mtcc.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">I just scanned through DMA=
RC and I couldn&#39;t find any security <br>
requirements/mechanisms for the failure reports. I would think at the <br>
very least the receiver consuming the reports ought make certain that <br>
the report at the very least have either a valid DKIM signature or a SPF <b=
r>
pass. Unauthenticated data is always the source of mischief, and I&#39;m <b=
r>
sure that there have to be attacks that are possible with <br>
unauthenticated reports. At the very least this should be a security <br>
consideration, and most likely should have some normative language to <br>
back it up.<br></blockquote><div><br></div><div>I thought the usual rules a=
bout when you should or shouldn&#39;t trust a message ought to be applied, =
but I guess we never actually said that in the document.=C2=A0 We certainly=
 could.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
Since I&#39;m sort of new, it&#39;s been unclear to me whether whether havi=
ng a <br>
new https transport mechanism is in scope or not -- it seems to come up <br=
>
pretty often -- but I&#39;m not sure how people would propose to <br>
authenticate the report sending client. That seems to me to be a basic <br>
security requirement for any new delivery method. The problem here is <br>
there isn&#39;t a client certificate to determine where the report is comin=
g <br>
from or any other identifying mechanism. An alternative might be to DKIM <b=
r>
sign the report itself, but the long and short is that it would need to <br=
>
be addressed.<br></blockquote><div><br></div><div>As I recall DMARC origina=
lly (in its pre-RFC versions) did have &quot;https&quot; as a supported sch=
eme for &quot;rua&quot;, but since nobody implemented it during the years D=
MARC was in development, it got dropped before publication.<br></div><div><=
br></div><div>-MSK<br></div></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--0000000000003ce6f405b95ceaa2--


From nobody Wed Jan 20 15:01:19 2021
Return-Path: <mike@fresheez.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 0A7833A166E for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 OxAmtORpJ3qC for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:01:09 -0800 (PST)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF4C23A1632 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:01:02 -0800 (PST)
Received: by mail-pg1-x532.google.com with SMTP id c22so16229541pgg.13 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:01:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=HK2VUEdVyLbUF0/RP2lksbtroikA+3xndvLo6oHKmRI=; b=me1SvSSbn4uRd8O9hzf/+Ej2yCqU7mVLuqHTgWHzZKNFNb2O/iCjEjntEpDS3k9wjw cTS6MQJkkMQ+SjPesZgEzxxhPYqgFeeid9+q3tg/CSDCYZkDzgdj6tc4wRcbmPyMGic/ lC1FPuBL+7Bw84w/Ll0hwfC+dcel8z0uFUvLw60MxrOh+9xGwA0iUHC6Oxb5k5NYC8QS JToAsfwf70OpZDKr5rZOpzDcBQQLtGDJ7yy5eGAvxvw3zufFH22guwvWowpzi5ghlR6N PPqum4wx7zz0SucnFsLVG8pZsS85XHX6Oj5ftaIzIisJiUBpk7asw4YeT7fRsmWd3g77 1IYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=HK2VUEdVyLbUF0/RP2lksbtroikA+3xndvLo6oHKmRI=; b=VfDQEv/epEcUNRcX5APw7fGJihxBv3rZPvw3219rvWmZyDGR9wXzkpWXSVFYee/BUI 1Ggiy1j/k/HFqe1OWSOvJUZ4dc4M4zdGrfr4djS+9hqCWdP8uYZ0qBPLmtQAW9XwATUm SykwhX97nCb8Pr8eCmBfLy6EuJ2NeT7EaiIrLOy/TUzYthjFbleT1bYqI/PgPwhPVWG2 O7G7L4J0sHwYyBSUDK+S8s2tKMf1lkP5JhIDls2kXmjD2VUkyw5zVmyjwQZ/qJKAEq4J QiDaVFlkPeCh8/U1DbDBi5x3WMROxgUEyxr+P720tHOI6GgtvteWTzG+zoghCVFexopV olMg==
X-Gm-Message-State: AOAM532Wdg9LnwILvMNWjWZS6lE+uo5hJFUW7pawUnY7Zqjy05fTTe3F KazM0L991LiHLueqGc0jWSM5VnGGF48/0Q==
X-Google-Smtp-Source: ABdhPJycv9hPB2gcm4Avolnzo4oUcf9xTSZ81k2cQNy8iAR4anaDFszQrgoYBP3feRVI3mu5+o329A==
X-Received: by 2002:a63:1c13:: with SMTP id c19mr11349720pgc.359.1611183661498;  Wed, 20 Jan 2021 15:01:01 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id w184sm3542671pgb.71.2021.01.20.15.00.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 15:01:00 -0800 (PST)
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
References: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com> <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <d2cb4ce1-a3d4-08a2-917d-0e1fdb71d400@mtcc.com>
Date: Wed, 20 Jan 2021 15:00:57 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------F4A978B212652DC0C5C27BD7"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/h53mMBZsmKnR3tzT8d7FH5Y4Cfo>
Subject: Re: [dmarc-ietf] Authentication of reports
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: Wed, 20 Jan 2021 23:01:17 -0000

This is a multi-part message in MIME format.
--------------F4A978B212652DC0C5C27BD7
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/20/21 2:56 PM, Murray S. Kucherawy wrote:
> On Wed, Jan 20, 2021 at 1:21 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>     I just scanned through DMARC and I couldn't find any security
>     requirements/mechanisms for the failure reports. I would think at the
>     very least the receiver consuming the reports ought make certain that
>     the report at the very least have either a valid DKIM signature or
>     a SPF
>     pass. Unauthenticated data is always the source of mischief, and I'm
>     sure that there have to be attacks that are possible with
>     unauthenticated reports. At the very least this should be a security
>     consideration, and most likely should have some normative language to
>     back it up.
>
>
> I thought the usual rules about when you should or shouldn't trust a 
> message ought to be applied, but I guess we never actually said that 
> in the document.  We certainly could.


DKIM is pretty nebulous about what it's results should used for, but as 
an authentication mechanism for another protocol it seem like it would 
be good say that explicitly. In this case it's a little more complicated 
since the thing processing the reports is almost certainly not at the 
boundary MTA verifying signatures.

>
>     Since I'm sort of new, it's been unclear to me whether whether
>     having a
>     new https transport mechanism is in scope or not -- it seems to
>     come up
>     pretty often -- but I'm not sure how people would propose to
>     authenticate the report sending client. That seems to me to be a
>     basic
>     security requirement for any new delivery method. The problem here is
>     there isn't a client certificate to determine where the report is
>     coming
>     from or any other identifying mechanism. An alternative might be
>     to DKIM
>     sign the report itself, but the long and short is that it would
>     need to
>     be addressed.
>
>
> As I recall DMARC originally (in its pre-RFC versions) did have 
> "https" as a supported scheme for "rua", but since nobody implemented 
> it during the years DMARC was in development, it got dropped before 
> publication.
>
>
So is it in scope or not? It's confusing if it's not because there seem 
to have been several open tickets about it.

Mike


--------------F4A978B212652DC0C5C27BD7
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/20/21 2:56 PM, Murray S. Kucherawy
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Wed, Jan 20, 2021 at 1:21 PM Michael Thomas
          &lt;<a href="mailto:mike@mtcc.com" moz-do-not-send="true">mike@mtcc.com</a>&gt;
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">I just scanned through
            DMARC and I couldn't find any security <br>
            requirements/mechanisms for the failure reports. I would
            think at the <br>
            very least the receiver consuming the reports ought make
            certain that <br>
            the report at the very least have either a valid DKIM
            signature or a SPF <br>
            pass. Unauthenticated data is always the source of mischief,
            and I'm <br>
            sure that there have to be attacks that are possible with <br>
            unauthenticated reports. At the very least this should be a
            security <br>
            consideration, and most likely should have some normative
            language to <br>
            back it up.<br>
          </blockquote>
          <div><br>
          </div>
          <div>I thought the usual rules about when you should or
            shouldn't trust a message ought to be applied, but I guess
            we never actually said that in the document.  We certainly
            could.</div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>DKIM is pretty nebulous about what it's results should used for,
      but as an authentication mechanism for another protocol it seem
      like it would be good say that explicitly. In this case it's a
      little more complicated since the thing processing the reports is
      almost certainly not at the boundary MTA verifying signatures.<br>
    </p>
    <blockquote type="cite"
cite="mid:CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <div><br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            Since I'm sort of new, it's been unclear to me whether
            whether having a <br>
            new https transport mechanism is in scope or not -- it seems
            to come up <br>
            pretty often -- but I'm not sure how people would propose to
            <br>
            authenticate the report sending client. That seems to me to
            be a basic <br>
            security requirement for any new delivery method. The
            problem here is <br>
            there isn't a client certificate to determine where the
            report is coming <br>
            from or any other identifying mechanism. An alternative
            might be to DKIM <br>
            sign the report itself, but the long and short is that it
            would need to <br>
            be addressed.<br>
          </blockquote>
          <div><br>
          </div>
          <div>As I recall DMARC originally (in its pre-RFC versions)
            did have "https" as a supported scheme for "rua", but since
            nobody implemented it during the years DMARC was in
            development, it got dropped before publication.<br>
          </div>
          <div><br>
          </div>
          <div><br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>So is it in scope or not? It's confusing if it's not because
      there seem to have been several open tickets about it.</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------F4A978B212652DC0C5C27BD7--


From nobody Wed Jan 20 15:02:23 2021
Return-Path: <mike@fresheez.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 5DF443A15B1 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 RfGSr0UB0KZH for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:02:15 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0DE3A15B5 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:01:58 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id o20so178096pfu.0 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:01:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=HeREI6fdD9pWnDlC9ESWy65+ZWTxeynEXD6NNjiT+7Y=; b=PmvYMJ+FzSs08JJCnZ3/bzYhcirlAJ7FRe3u3jwU0YgOjySdFNHFPQYCgeV+sXLFW/ igEI+iHS+3jShNBVbNJHfKWlJMGn9RJht/IQ1IoK3Mcym6Qg8xJHk9s+gExqXP6cE5Cl Woh4wxoO3q0lLyt8TBQ0Z1KfPfB30weQ4gXCln+nP66BQkwhzQXqhK9YI7H5vSIpeEhB uNUniNxGIwWiWmk6hRf4PGzRaeI4Uex0aXpRthe3BGkBzqGEd9OXp5FWGweNljR/h4O7 kztkce1u0tEqNGfyk5X7VWMmLZw3Q+sTo1QIM5hxaaNeChrgdo3o592nTyIFDYxHRGyf S/Fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=HeREI6fdD9pWnDlC9ESWy65+ZWTxeynEXD6NNjiT+7Y=; b=pw1SlebTGpKbpO8mqv4+NRHFGF9RDyObE/eiLSaUHtoRk0zRUayrUrDvMKeNBxqRyE CM7AJwASG1G6TctMsHhrKAWAswHqZXB1LBDhDW1cXOOLJkKnc0GqcZdCLDDYVgUlUwbw AGxHPvG90kxDH52R8okb+qvWydF9ylaJglzWk9ryOVbviUcR4vE9Rj3qU92lgcZqYMZA oJbfWp6HmIhwarkAyvJrKlqkblueLIdsXuISiTKKWPUbFLJR/94LJmyxtS8+3u9R3rA5 BnJz8gSMXdin6SQ0rTWQZD0D3wQmAbMdV1gTjHzSpLrHcRZDvqK7lUA0EK59DK3FXaES pPTQ==
X-Gm-Message-State: AOAM533B8LgfwX0DlrFQFnD28IGnnYvq6jO/ZSWijqr6W6GBAHW1xf3t A7nwoV5jk2Pe1n7mOY0Irn9e6Jh9uKiUiA==
X-Google-Smtp-Source: ABdhPJzjTEueVy7a565AuB2nvT0Xhtsoxx47BfyQsykIwmUsrR2ESVqTyxWmH1duRb+LIm61Fq+5eQ==
X-Received: by 2002:a63:ce42:: with SMTP id r2mr11717344pgi.8.1611183717244; Wed, 20 Jan 2021 15:01:57 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id 85sm3478746pfc.39.2021.01.20.15.01.55 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 15:01:56 -0800 (PST)
To: dmarc@ietf.org
References: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com> <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com> <CAOZAAfNw1amAfubGBMXY_FzDOaPzKkBb0TiaexZhk+JZXeFZ=Q@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <ac8530f6-e8c9-bb6b-d20a-2635d997e149@mtcc.com>
Date: Wed, 20 Jan 2021 15:01:55 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfNw1amAfubGBMXY_FzDOaPzKkBb0TiaexZhk+JZXeFZ=Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------C205B6CA1CF1729ECBE2D21C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mci3wd6bcskONIULSeEviOFKgX8>
Subject: Re: [dmarc-ietf] Authentication of reports
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: Wed, 20 Jan 2021 23:02:17 -0000

This is a multi-part message in MIME format.
--------------C205B6CA1CF1729ECBE2D21C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/20/21 2:59 PM, Seth Blank wrote:
> Michael, please open a ticket. I think you're right and some 
> consideration around this is needed in the document.

What about the https part? If it's not in scope I don't want to add noise.

Mike

>
> On Wed, Jan 20, 2021 at 2:56 PM Murray S. Kucherawy 
> <superuser@gmail.com <mailto:superuser@gmail.com>> wrote:
>
>     On Wed, Jan 20, 2021 at 1:21 PM Michael Thomas <mike@mtcc.com
>     <mailto:mike@mtcc.com>> wrote:
>
>         I just scanned through DMARC and I couldn't find any security
>         requirements/mechanisms for the failure reports. I would think
>         at the
>         very least the receiver consuming the reports ought make
>         certain that
>         the report at the very least have either a valid DKIM
>         signature or a SPF
>         pass. Unauthenticated data is always the source of mischief,
>         and I'm
>         sure that there have to be attacks that are possible with
>         unauthenticated reports. At the very least this should be a
>         security
>         consideration, and most likely should have some normative
>         language to
>         back it up.
>
>
>     I thought the usual rules about when you should or shouldn't trust
>     a message ought to be applied, but I guess we never actually said
>     that in the document.  We certainly could.
>
>         Since I'm sort of new, it's been unclear to me whether whether
>         having a
>         new https transport mechanism is in scope or not -- it seems
>         to come up
>         pretty often -- but I'm not sure how people would propose to
>         authenticate the report sending client. That seems to me to be
>         a basic
>         security requirement for any new delivery method. The problem
>         here is
>         there isn't a client certificate to determine where the report
>         is coming
>         from or any other identifying mechanism. An alternative might
>         be to DKIM
>         sign the report itself, but the long and short is that it
>         would need to
>         be addressed.
>
>
>     As I recall DMARC originally (in its pre-RFC versions) did have
>     "https" as a supported scheme for "rua", but since nobody
>     implemented it during the years DMARC was in development, it got
>     dropped before publication.
>
>     -MSK
>     _______________________________________________
>     dmarc mailing list
>     dmarc@ietf.org <mailto:dmarc@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dmarc
>     <https://www.ietf.org/mailman/listinfo/dmarc>
>
>
>
> -- 
> *Seth Blank*| VP, Standards and New Technologies
> *e:*seth@valimail.com <mailto:seth@valimail.com>
> *p:*415.273.8818
>
>
> This email and all data transmitted with it contains confidential 
> and/or proprietary information intended solely for the use of 
> individual(s) authorized to receive it. If you are not an intended and 
> authorized recipient you are hereby notified of any use, disclosure, 
> copying or distribution of the information included in this 
> transmission is prohibited and may be unlawful. Please immediately 
> notify the sender by replying to this email and then delete it from 
> your system.
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc

--------------C205B6CA1CF1729ECBE2D21C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/20/21 2:59 PM, Seth Blank wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOZAAfNw1amAfubGBMXY_FzDOaPzKkBb0TiaexZhk+JZXeFZ=Q@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Michael, please open a ticket. I think you're right
        and some consideration around this is needed in the document.</div>
    </blockquote>
    <p>What about the https part? If it's not in scope I don't want to
      add noise.</p>
    <p>Mike<br>
    </p>
    <blockquote type="cite"
cite="mid:CAOZAAfNw1amAfubGBMXY_FzDOaPzKkBb0TiaexZhk+JZXeFZ=Q@mail.gmail.com"><br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Wed, Jan 20, 2021 at 2:56
          PM Murray S. Kucherawy &lt;<a
            href="mailto:superuser@gmail.com" moz-do-not-send="true">superuser@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir="ltr">
            <div dir="ltr">On Wed, Jan 20, 2021 at 1:21 PM Michael
              Thomas &lt;<a href="mailto:mike@mtcc.com" target="_blank"
                moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
            </div>
            <div class="gmail_quote">
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">I just scanned
                through DMARC and I couldn't find any security <br>
                requirements/mechanisms for the failure reports. I would
                think at the <br>
                very least the receiver consuming the reports ought make
                certain that <br>
                the report at the very least have either a valid DKIM
                signature or a SPF <br>
                pass. Unauthenticated data is always the source of
                mischief, and I'm <br>
                sure that there have to be attacks that are possible
                with <br>
                unauthenticated reports. At the very least this should
                be a security <br>
                consideration, and most likely should have some
                normative language to <br>
                back it up.<br>
              </blockquote>
              <div><br>
              </div>
              <div>I thought the usual rules about when you should or
                shouldn't trust a message ought to be applied, but I
                guess we never actually said that in the document.  We
                certainly could.</div>
              <div><br>
              </div>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">
                Since I'm sort of new, it's been unclear to me whether
                whether having a <br>
                new https transport mechanism is in scope or not -- it
                seems to come up <br>
                pretty often -- but I'm not sure how people would
                propose to <br>
                authenticate the report sending client. That seems to me
                to be a basic <br>
                security requirement for any new delivery method. The
                problem here is <br>
                there isn't a client certificate to determine where the
                report is coming <br>
                from or any other identifying mechanism. An alternative
                might be to DKIM <br>
                sign the report itself, but the long and short is that
                it would need to <br>
                be addressed.<br>
              </blockquote>
              <div><br>
              </div>
              <div>As I recall DMARC originally (in its pre-RFC
                versions) did have "https" as a supported scheme for
                "rua", but since nobody implemented it during the years
                DMARC was in development, it got dropped before
                publication.<br>
              </div>
              <div><br>
              </div>
              <div>-MSK<br>
              </div>
            </div>
          </div>
          _______________________________________________<br>
          dmarc mailing list<br>
          <a href="mailto:dmarc@ietf.org" target="_blank"
            moz-do-not-send="true">dmarc@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/dmarc"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"><span>
          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
          </span>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
        </span></div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
dmarc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dmarc@ietf.org">dmarc@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dmarc">https://www.ietf.org/mailman/listinfo/dmarc</a>
</pre>
    </blockquote>
  </body>
</html>

--------------C205B6CA1CF1729ECBE2D21C--


From nobody Wed Jan 20 15:08:29 2021
Return-Path: <seth@valimail.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 AFCDD3A15BE for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:08:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 zYc-y9DDx5Tu for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:08:23 -0800 (PST)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FF9C3A15D9 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:08:23 -0800 (PST)
Received: by mail-vs1-xe2c.google.com with SMTP id p20so57687vsq.7 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:08:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mSzavoFpWFJWzUp7AoyQoenPZ5Sujc7pIW8bLb2GZt0=; b=c4bIkxJ4KYccNyrknYB93YR8jLdAd9PKit8eztusPcOMyPf0RmAAjRKkkNXrMgpvrc ajuMLtg6Fn0C7Calya9iaF7s1k56x5v9spL/fdRHTc+7qnvOJGzvnLDs8tDYQYXgLOhF d/X95QLfHhXyVtRrhD7DErn6GsOjaSnIkCirL/Vhjokfft20W5pB9fyhx4cEbwnQfI58 LH2PaXNEdy2jDZf4oeg+nMpa3TqLRyvnmpqEJXskjRIYILDRgWt1RVor2NjET5iuvCvQ qqC9/VIqpGSouwSdNMLxZYsZQEq2dQCgLzFl8KBzveGvu5nalpfw5A7o+Ez/I3qQhDjK wadw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mSzavoFpWFJWzUp7AoyQoenPZ5Sujc7pIW8bLb2GZt0=; b=pRCpT3Nk85ZyaQk+aReG5ToobiqbTXDwRIAAvl2JV9nXk/+/FyORHXjjSwaCWT3s2S SP7yHyjRN2sll+gGEwhSlR91Y5pMnh5X7cw0B3AOkRGaH/8R15wSceUVWxFddpzjIvf9 vLC7rgHqnNjMvc3OK9O+HOLAGcEsNySJMRY9tVw856sbLjEkfQ3NuJr7jkYc/tGz/MFI INhGB39JItIg+t86iZJjuToXP9TmqoZhUp/aMHoIgl6my1hVdfxnbV8mMM0IiE2oD5Ni wJyUSJTEd/5k72bqvTkio9pMcPSfQEvvD0fssAZNgtU1/1zka1r7FNWs+T+8nttID4ZU TQkQ==
X-Gm-Message-State: AOAM531meeTod7EOiDc3vRLc3rSBJtta8xOlO5RQOeC2qF5dy5x9paTq RV0UE7AHyqUwiF1KZ1XTStUh6Tzw926P/M+Jy9GXqg==
X-Google-Smtp-Source: ABdhPJzcIGWWHCmL4GIeuYzzDj8eqbmja2rCqJsVm+rDTvj9//QfD476oVA3cRed4ExAO57zhG6FO2kLLsyVad8atW4=
X-Received: by 2002:a05:6102:1c8:: with SMTP id s8mr8551735vsq.52.1611184102406;  Wed, 20 Jan 2021 15:08:22 -0800 (PST)
MIME-Version: 1.0
References: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com> <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com> <CAOZAAfNw1amAfubGBMXY_FzDOaPzKkBb0TiaexZhk+JZXeFZ=Q@mail.gmail.com> <ac8530f6-e8c9-bb6b-d20a-2635d997e149@mtcc.com>
In-Reply-To: <ac8530f6-e8c9-bb6b-d20a-2635d997e149@mtcc.com>
From: Seth Blank <seth@valimail.com>
Date: Wed, 20 Jan 2021 15:08:11 -0800
Message-ID: <CAOZAAfPS92sdataw5G9RJd=nY5iQXFBO3PY1iEDUkSrHMTJJLA@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000017926005b95d0806"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/64KWZfwiAG9S3fVot6dxMpkdUeo>
Subject: Re: [dmarc-ietf] Authentication of reports
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: Wed, 20 Jan 2021 23:08:26 -0000

--00000000000017926005b95d0806
Content-Type: text/plain; charset="UTF-8"

Discussion is in scope, per: https://trac.ietf.org/trac/dmarc/ticket/42

This topic has come up before, and there's always general interest in
pursuing it, and absolutely no one who puts their hand up for either it
being impactful for them or having any interest in implementing it. i.e. it
seems interesting to people, but there seems to be no use case with
operational support to actually add it.

So from those previous discussions, I don't think it's likely that we'll
add reporting beyond mailto:, but it is certainly a conversation that's in
scope when either ticket is opened.

Seth

On Wed, Jan 20, 2021 at 3:02 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/20/21 2:59 PM, Seth Blank wrote:
>
> Michael, please open a ticket. I think you're right and some consideration
> around this is needed in the document.
>
> What about the https part? If it's not in scope I don't want to add noise.
>
> Mike
>
>
> On Wed, Jan 20, 2021 at 2:56 PM Murray S. Kucherawy <superuser@gmail.com>
> wrote:
>
>> On Wed, Jan 20, 2021 at 1:21 PM Michael Thomas <mike@mtcc.com> wrote:
>>
>>> I just scanned through DMARC and I couldn't find any security
>>> requirements/mechanisms for the failure reports. I would think at the
>>> very least the receiver consuming the reports ought make certain that
>>> the report at the very least have either a valid DKIM signature or a SPF
>>> pass. Unauthenticated data is always the source of mischief, and I'm
>>> sure that there have to be attacks that are possible with
>>> unauthenticated reports. At the very least this should be a security
>>> consideration, and most likely should have some normative language to
>>> back it up.
>>>
>>
>> I thought the usual rules about when you should or shouldn't trust a
>> message ought to be applied, but I guess we never actually said that in the
>> document.  We certainly could.
>>
>> Since I'm sort of new, it's been unclear to me whether whether having a
>>> new https transport mechanism is in scope or not -- it seems to come up
>>> pretty often -- but I'm not sure how people would propose to
>>> authenticate the report sending client. That seems to me to be a basic
>>> security requirement for any new delivery method. The problem here is
>>> there isn't a client certificate to determine where the report is coming
>>> from or any other identifying mechanism. An alternative might be to DKIM
>>> sign the report itself, but the long and short is that it would need to
>>> be addressed.
>>>
>>
>> As I recall DMARC originally (in its pre-RFC versions) did have "https"
>> as a supported scheme for "rua", but since nobody implemented it during the
>> years DMARC was in development, it got dropped before publication.
>>
>> -MSK
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>
>
> --
> *Seth Blank* | VP, Standards and New Technologies
> *e:* seth@valimail.com
> *p:* 415.273.8818
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
>
> _______________________________________________
> dmarc mailing listdmarc@ietf.orghttps://www.ietf.org/mailman/listinfo/dmarc
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--00000000000017926005b95d0806
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Discussion is in scope, per:=C2=A0<a href=3D"https://trac.=
ietf.org/trac/dmarc/ticket/42">https://trac.ietf.org/trac/dmarc/ticket/42</=
a><div><br></div><div>This topic has come up before, and there&#39;s always=
 general interest in pursuing it, and absolutely no one who puts their hand=
 up for either it being impactful for them or having any interest in implem=
enting it. i.e. it seems interesting to people, but there seems to be no us=
e case with operational support to actually add it.</div><div><br></div><di=
v>So from those previous discussions, I don&#39;t think it&#39;s likely tha=
t we&#39;ll add reporting beyond mailto:, but it is certainly a conversatio=
n that&#39;s in scope when either ticket is opened.</div><div><br></div><di=
v>Seth</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Wed, Jan 20, 2021 at 3:02 PM Michael Thomas &lt;<a href=3D"m=
ailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/20/21 2:59 PM, Seth Blank wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Michael, please open a ticket. I think you&#39;re ri=
ght
        and some consideration around this is needed in the document.</div>
    </blockquote>
    <p>What about the https part? If it&#39;s not in scope I don&#39;t want=
 to
      add noise.</p>
    <p>Mike<br>
    </p>
    <blockquote type=3D"cite"><br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 20, 2021 at 2:56
          PM Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com"=
 target=3D"_blank">superuser@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir=3D"ltr">
            <div dir=3D"ltr">On Wed, Jan 20, 2021 at 1:21 PM Michael
              Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"_blank"=
>mike@mtcc.com</a>&gt; wrote:<br>
            </div>
            <div class=3D"gmail_quote">
              <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I just scan=
ned
                through DMARC and I couldn&#39;t find any security <br>
                requirements/mechanisms for the failure reports. I would
                think at the <br>
                very least the receiver consuming the reports ought make
                certain that <br>
                the report at the very least have either a valid DKIM
                signature or a SPF <br>
                pass. Unauthenticated data is always the source of
                mischief, and I&#39;m <br>
                sure that there have to be attacks that are possible
                with <br>
                unauthenticated reports. At the very least this should
                be a security <br>
                consideration, and most likely should have some
                normative language to <br>
                back it up.<br>
              </blockquote>
              <div><br>
              </div>
              <div>I thought the usual rules about when you should or
                shouldn&#39;t trust a message ought to be applied, but I
                guess we never actually said that in the document.=C2=A0 We
                certainly could.</div>
              <div><br>
              </div>
              <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                Since I&#39;m sort of new, it&#39;s been unclear to me whet=
her
                whether having a <br>
                new https transport mechanism is in scope or not -- it
                seems to come up <br>
                pretty often -- but I&#39;m not sure how people would
                propose to <br>
                authenticate the report sending client. That seems to me
                to be a basic <br>
                security requirement for any new delivery method. The
                problem here is <br>
                there isn&#39;t a client certificate to determine where the
                report is coming <br>
                from or any other identifying mechanism. An alternative
                might be to DKIM <br>
                sign the report itself, but the long and short is that
                it would need to <br>
                be addressed.<br>
              </blockquote>
              <div><br>
              </div>
              <div>As I recall DMARC originally (in its pre-RFC
                versions) did have &quot;https&quot; as a supported scheme =
for
                &quot;rua&quot;, but since nobody implemented it during the=
 years
                DMARC was in development, it got dropped before
                publication.<br>
              </div>
              <div><br>
              </div>
              <div>-MSK<br>
              </div>
            </div>
          </div>
          _______________________________________________<br>
          dmarc mailing list<br>
          <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.or=
g</a><br>
          <a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a>=
<br>
        </blockquote>
      </div>
      <br clear=3D"all">
      <div><br>
      </div>
      -- <br>
      <div dir=3D"ltr"><span>
          <div style=3D"text-align:left"><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank<=
/b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"> | VP, Standards and New Technologies</span><=
/div>
          <span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D=
"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:bas=
eline"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank">seth@valimai=
l.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></s=
pan></div>
          </span>
          <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;f=
ont-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-ali=
gn:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent=
.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSX=
prAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=
=3D"border: none; height: 40px; width: 177px;"></span></p>
          <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><font face=3D"Arial" color=3D"#=
666666"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email=
 and all data transmitted with it contains confidential and/or proprietary =
information intended solely for the use of individual(s) authorized to rece=
ive it. If you are not an intended and authorized recipient you are hereby =
notified of any use, disclosure, copying or distribution of the information=
 included in this transmission is prohibited and may be unlawful. Please im=
mediately notify the sender by replying to this email and then delete it fr=
om your system.</span></font></p>
        </span></div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
dmarc mailing list
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dmarc</a>
</pre>
    </blockquote>
  </div>

_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--00000000000017926005b95d0806--


From nobody Wed Jan 20 15:10:12 2021
Return-Path: <mike@fresheez.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 4CAF33A15C0 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:10:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 IvO-WWxB0OuE for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:10:08 -0800 (PST)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DDBF3A15BF for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:10:08 -0800 (PST)
Received: by mail-pl1-x636.google.com with SMTP id x18so50691pln.6 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:10:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=ZDpxsmFAlznIwQgMgLsXInJjDnGosiGaOVskV9+MgKU=; b=NuO6EEU7KbNyhwWU+8oxUCXyqhAuU8M3c3fj+N31eXvBw2Dse3sowi0T1YAMeXJhXP qoa4lbSw0FQ5bt3kXPKSuamESNId6zt/OxkQ4DFJU5KASivMVfEHn8RqpY04pNnSH3Ay undVRZEtcPYRKi4Y9YZIIiiGml3LsOJnHWznXWA10daYLh7RBMF9rByIKdjNjpDeImxn Yg5VMZJCmk+4Pv0ZT3IHCqp0eBcGNTG2sK5w7U1UCZNPELKTv021YXbRDqcHgEyPiXsJ RR9P771ZSBBCFzjtVRX0lZoXcjPafbAnaIfd+dw+Q4LAj+K44IQTHVDRJ+iu8rRMD1uE 7D/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=ZDpxsmFAlznIwQgMgLsXInJjDnGosiGaOVskV9+MgKU=; b=DnPNOwMUTDOgNUxdO2yqnbsjMPnGCgi0FDF9DJsYV30ShImeDDR/T8eWmwdGRv8z7M 2PRESushgwyWq5Odmin08PI0bRyDM14RLMuAtjFRbUGDvFjjpeQwEhinbXEMa1BTozfS yQl0Ix5MBnVP8PZrHsmEWIsCN1dWdPzNXrKkmh5lW9Iqx+VNCwgCGVdSUK5aQzfuxWg+ ZzBB88/xBj+jkCujZQhIC5BAjTvDsalHXY8UaIoeiC0iUigJdUTWVAU/xMbPaSRTDEXw LTg2F8jvMsFwyIVZKwFjucnafcRvohzMlICUq2WMeTpQ1swWnBAak1d+BNg5LWvLSjww CRhA==
X-Gm-Message-State: AOAM532mz5xQYV1cM/GAeCTbYMKuhLWdLnle90V/g44JMBA7tBnbjSzN GR20wNwrCyxW/bALPM/3GnUdkt/JbZLCXg==
X-Google-Smtp-Source: ABdhPJz1q52Qv9M/u9hixeWkgM74r4SVLkjKy0oTT6JgcbO7qfLVmFNann03nMAycuWcEj4GkRS65g==
X-Received: by 2002:a17:902:b213:b029:db:3a3e:d8ad with SMTP id t19-20020a170902b213b02900db3a3ed8admr11989261plr.73.1611184207288;  Wed, 20 Jan 2021 15:10:07 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id m4sm3469863pgu.4.2021.01.20.15.10.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 15:10:06 -0800 (PST)
To: Seth Blank <seth@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com> <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com> <CAOZAAfNw1amAfubGBMXY_FzDOaPzKkBb0TiaexZhk+JZXeFZ=Q@mail.gmail.com> <ac8530f6-e8c9-bb6b-d20a-2635d997e149@mtcc.com> <CAOZAAfPS92sdataw5G9RJd=nY5iQXFBO3PY1iEDUkSrHMTJJLA@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <899b9882-efe9-0ce3-5e6e-bef7e21354dd@mtcc.com>
Date: Wed, 20 Jan 2021 15:10:05 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfPS92sdataw5G9RJd=nY5iQXFBO3PY1iEDUkSrHMTJJLA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A1B5BE0E547E810373AD88EB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/I_kTTx8TVvYckNYAAUQ01M1M3aw>
Subject: Re: [dmarc-ietf] Authentication of reports
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: Wed, 20 Jan 2021 23:10:10 -0000

This is a multi-part message in MIME format.
--------------A1B5BE0E547E810373AD88EB
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Ok, i'll break it into two separate issues as they are related but not 
the same.

Mike

On 1/20/21 3:08 PM, Seth Blank wrote:
> Discussion is in scope, per: 
> https://trac.ietf.org/trac/dmarc/ticket/42 
> <https://trac.ietf.org/trac/dmarc/ticket/42>
>
> This topic has come up before, and there's always general interest in 
> pursuing it, and absolutely no one who puts their hand up for either 
> it being impactful for them or having any interest in implementing it. 
> i.e. it seems interesting to people, but there seems to be no use case 
> with operational support to actually add it.
>
> So from those previous discussions, I don't think it's likely that 
> we'll add reporting beyond mailto:, but it is certainly a conversation 
> that's in scope when either ticket is opened.
>
> Seth
>
> On Wed, Jan 20, 2021 at 3:02 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     On 1/20/21 2:59 PM, Seth Blank wrote:
>>     Michael, please open a ticket. I think you're right and some
>>     consideration around this is needed in the document.
>
>     What about the https part? If it's not in scope I don't want to
>     add noise.
>
>     Mike
>
>>
>>     On Wed, Jan 20, 2021 at 2:56 PM Murray S. Kucherawy
>>     <superuser@gmail.com <mailto:superuser@gmail.com>> wrote:
>>
>>         On Wed, Jan 20, 2021 at 1:21 PM Michael Thomas <mike@mtcc.com
>>         <mailto:mike@mtcc.com>> wrote:
>>
>>             I just scanned through DMARC and I couldn't find any
>>             security
>>             requirements/mechanisms for the failure reports. I would
>>             think at the
>>             very least the receiver consuming the reports ought make
>>             certain that
>>             the report at the very least have either a valid DKIM
>>             signature or a SPF
>>             pass. Unauthenticated data is always the source of
>>             mischief, and I'm
>>             sure that there have to be attacks that are possible with
>>             unauthenticated reports. At the very least this should be
>>             a security
>>             consideration, and most likely should have some normative
>>             language to
>>             back it up.
>>
>>
>>         I thought the usual rules about when you should or shouldn't
>>         trust a message ought to be applied, but I guess we never
>>         actually said that in the document.  We certainly could.
>>
>>             Since I'm sort of new, it's been unclear to me whether
>>             whether having a
>>             new https transport mechanism is in scope or not -- it
>>             seems to come up
>>             pretty often -- but I'm not sure how people would propose to
>>             authenticate the report sending client. That seems to me
>>             to be a basic
>>             security requirement for any new delivery method. The
>>             problem here is
>>             there isn't a client certificate to determine where the
>>             report is coming
>>             from or any other identifying mechanism. An alternative
>>             might be to DKIM
>>             sign the report itself, but the long and short is that it
>>             would need to
>>             be addressed.
>>
>>
>>         As I recall DMARC originally (in its pre-RFC versions) did
>>         have "https" as a supported scheme for "rua", but since
>>         nobody implemented it during the years DMARC was in
>>         development, it got dropped before publication.
>>
>>         -MSK
>>         _______________________________________________
>>         dmarc mailing list
>>         dmarc@ietf.org <mailto:dmarc@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/dmarc
>>         <https://www.ietf.org/mailman/listinfo/dmarc>
>>
>>
>>
>>     -- 
>>     *Seth Blank*| VP, Standards and New Technologies
>>     *e:*seth@valimail.com <mailto:seth@valimail.com>
>>     *p:*415.273.8818
>>
>>
>>     This email and all data transmitted with it contains confidential
>>     and/or proprietary information intended solely for the use of
>>     individual(s) authorized to receive it. If you are not an
>>     intended and authorized recipient you are hereby notified of any
>>     use, disclosure, copying or distribution of the information
>>     included in this transmission is prohibited and may be unlawful.
>>     Please immediately notify the sender by replying to this email
>>     and then delete it from your system.
>>
>>
>>     _______________________________________________
>>     dmarc mailing list
>>     dmarc@ietf.org  <mailto:dmarc@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/dmarc  <https://www.ietf.org/mailman/listinfo/dmarc>
>     _______________________________________________
>     dmarc mailing list
>     dmarc@ietf.org <mailto:dmarc@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dmarc
>     <https://www.ietf.org/mailman/listinfo/dmarc>
>
>
>
> -- 
> *Seth Blank*| VP, Standards and New Technologies
> *e:*seth@valimail.com <mailto:seth@valimail.com>
> *p:*415.273.8818
>
>
> This email and all data transmitted with it contains confidential 
> and/or proprietary information intended solely for the use of 
> individual(s) authorized to receive it. If you are not an intended and 
> authorized recipient you are hereby notified of any use, disclosure, 
> copying or distribution of the information included in this 
> transmission is prohibited and may be unlawful. Please immediately 
> notify the sender by replying to this email and then delete it from 
> your system.
>

--------------A1B5BE0E547E810373AD88EB
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Ok, i'll break it into two separate issues as they are related
      but not the same.</p>
    <p>Mike<br>
    </p>
    <div class="moz-cite-prefix">On 1/20/21 3:08 PM, Seth Blank wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOZAAfPS92sdataw5G9RJd=nY5iQXFBO3PY1iEDUkSrHMTJJLA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Discussion is in scope, per: <a
          href="https://trac.ietf.org/trac/dmarc/ticket/42"
          moz-do-not-send="true">https://trac.ietf.org/trac/dmarc/ticket/42</a>
        <div><br>
        </div>
        <div>This topic has come up before, and there's always general
          interest in pursuing it, and absolutely no one who puts their
          hand up for either it being impactful for them or having any
          interest in implementing it. i.e. it seems interesting to
          people, but there seems to be no use case with operational
          support to actually add it.</div>
        <div><br>
        </div>
        <div>So from those previous discussions, I don't think it's
          likely that we'll add reporting beyond mailto:, but it is
          certainly a conversation that's in scope when either ticket is
          opened.</div>
        <div><br>
        </div>
        <div>Seth</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Wed, Jan 20, 2021 at 3:02
          PM Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
            moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p><br>
            </p>
            <div>On 1/20/21 2:59 PM, Seth Blank wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">Michael, please open a ticket. I think
                you're right and some consideration around this is
                needed in the document.</div>
            </blockquote>
            <p>What about the https part? If it's not in scope I don't
              want to add noise.</p>
            <p>Mike<br>
            </p>
            <blockquote type="cite"><br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Wed, Jan 20, 2021
                  at 2:56 PM Murray S. Kucherawy &lt;<a
                    href="mailto:superuser@gmail.com" target="_blank"
                    moz-do-not-send="true">superuser@gmail.com</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">
                    <div dir="ltr">On Wed, Jan 20, 2021 at 1:21 PM
                      Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
                        target="_blank" moz-do-not-send="true">mike@mtcc.com</a>&gt;
                      wrote:<br>
                    </div>
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px 0.8ex;border-left:1px solid
                        rgb(204,204,204);padding-left:1ex">I just
                        scanned through DMARC and I couldn't find any
                        security <br>
                        requirements/mechanisms for the failure reports.
                        I would think at the <br>
                        very least the receiver consuming the reports
                        ought make certain that <br>
                        the report at the very least have either a valid
                        DKIM signature or a SPF <br>
                        pass. Unauthenticated data is always the source
                        of mischief, and I'm <br>
                        sure that there have to be attacks that are
                        possible with <br>
                        unauthenticated reports. At the very least this
                        should be a security <br>
                        consideration, and most likely should have some
                        normative language to <br>
                        back it up.<br>
                      </blockquote>
                      <div><br>
                      </div>
                      <div>I thought the usual rules about when you
                        should or shouldn't trust a message ought to be
                        applied, but I guess we never actually said that
                        in the document.  We certainly could.</div>
                      <div><br>
                      </div>
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px 0.8ex;border-left:1px solid
                        rgb(204,204,204);padding-left:1ex"> Since I'm
                        sort of new, it's been unclear to me whether
                        whether having a <br>
                        new https transport mechanism is in scope or not
                        -- it seems to come up <br>
                        pretty often -- but I'm not sure how people
                        would propose to <br>
                        authenticate the report sending client. That
                        seems to me to be a basic <br>
                        security requirement for any new delivery
                        method. The problem here is <br>
                        there isn't a client certificate to determine
                        where the report is coming <br>
                        from or any other identifying mechanism. An
                        alternative might be to DKIM <br>
                        sign the report itself, but the long and short
                        is that it would need to <br>
                        be addressed.<br>
                      </blockquote>
                      <div><br>
                      </div>
                      <div>As I recall DMARC originally (in its pre-RFC
                        versions) did have "https" as a supported scheme
                        for "rua", but since nobody implemented it
                        during the years DMARC was in development, it
                        got dropped before publication.<br>
                      </div>
                      <div><br>
                      </div>
                      <div>-MSK<br>
                      </div>
                    </div>
                  </div>
                  _______________________________________________<br>
                  dmarc mailing list<br>
                  <a href="mailto:dmarc@ietf.org" target="_blank"
                    moz-do-not-send="true">dmarc@ietf.org</a><br>
                  <a href="https://www.ietf.org/mailman/listinfo/dmarc"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
                </blockquote>
              </div>
              <br clear="all">
              <div><br>
              </div>
              -- <br>
              <div dir="ltr"><span>
                  <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
                  <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
                    <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
                  </span>
                  <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
                  <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
                  </p>
                  <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
                      face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
                </span></div>
              <br>
              <fieldset></fieldset>
              <pre>_______________________________________________
dmarc mailing list
<a href="mailto:dmarc@ietf.org" target="_blank" moz-do-not-send="true">dmarc@ietf.org</a>
<a href="https://www.ietf.org/mailman/listinfo/dmarc" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a>
</pre>
            </blockquote>
          </div>
          _______________________________________________<br>
          dmarc mailing list<br>
          <a href="mailto:dmarc@ietf.org" target="_blank"
            moz-do-not-send="true">dmarc@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/dmarc"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"><span>
          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
          </span>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
        </span></div>
    </blockquote>
  </body>
</html>

--------------A1B5BE0E547E810373AD88EB--


From nobody Wed Jan 20 15:10:32 2021
Return-Path: <smj@crash.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 7DF323A15C0 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:10:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 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.262, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=crash.com
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 H2rtK2Ygn8YG for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:10:28 -0800 (PST)
Received: from segv.crash.com (segv.crash.com [IPv6:2001:470:1:1e9::4415]) (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 6F3DD3A15BF for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:10:28 -0800 (PST)
Received: from shiny.crash.com (192-184-141-33.static.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.7) with ESMTPSA id 10KNAFn5047395 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 20 Jan 2021 23:10:23 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 10KNAFn5047395
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1611184225; bh=OAxRfli3owxOBBzgBC8kh/n/sEKwYJqLPhiXmV0STHw=; h=Subject:To:References:From:Date:In-Reply-To; b=lBx4CAC4p5gPQ1gtmN9QNdhNocCZ2g5eBzlmsjWES0VTshZDBIhXgKDAjCARs8UJf AfmKXk1m3ESwzjl1QbTVeb+BPrVqF/rI7LmwcILEJVf5CRBNKsT1/h1vamhcr8eoCx o4GseR6dJBXahf2fewkn23VorknzQq9xaErOLzV/sUn8TKtZkN6grj9rZ4zRnDiecU CajQohI5ADUz9Qc0SPyerH8K7myFA3bhDteuKSsdDib1bNsPRrA7EAXg6u6hF1lng0 jAkhq6PJgJIyjLR9RO4ujuRRw6T2COPi/A4t3bHA2cYWSofp8q4Fk8APW8mthnlOSb D+L1tL8tYkp2Q==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.static.sonic.net [192.184.141.33] claimed to be shiny.crash.com
To: dmarc@ietf.org
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it> <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <f03aa3ae-2e6a-b095-39a2-837bfe2cabc4@crash.com>
Date: Wed, 20 Jan 2021 15:10:14 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Wed, 20 Jan 2021 23:10:23 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/cUHhwOo4dXTKCNkqHkiL277iam4>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 23:10:31 -0000

On 1/19/21 06:02, Todd Herr wrote:
> Picking up the thread on a ticket that was brought before the group
> pre-holidays and has lain fallow since the end of 2020...

Prompted me to read from the start of the thread through:

On 1/20/21 11:19, John R Levine wrote:
> On Wed, 20 Jan 2021, Alessandro Vesely wrote:
>> John's record looks more workable, but it's still fluffy:
>>
>> "v=DMARC1; p=none; rf=afrf;
>> rua=mailto:dmarc-a@abuse.net,https://dmreport.abuse.net/dmreport/;
>> ruf=mailto:dmarc-f@abuse.net"
>
> Whaddaya mean fluffy?  Try a PUT or POST to that URI and it'll work.


I think we should specify HTTPS URIs, and following 7489 section 12.6
"Secure Protocols" and current practices, HTTP should not be
specified/permitted.

However I don't yet see a compelling case for the OR- syntax or a
separate "ruap" tag. Duplicate reports to the same destination are not
the base case, and the bandwidth for unintended duplicates will likely
be much smaller than, say, per-message DNS tree walks being discussed
elsewhere. Report processors annoyed by receiving duplicates can work
with the domain owners in question, and if that doesn't work they can
withdraw their report authorization record.

--S.



From nobody Wed Jan 20 15:20:19 2021
Return-Path: <smj@crash.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 7DB603A15C7 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:20:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 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.262, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=crash.com
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 NiBCletMS2oq for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 15:20:17 -0800 (PST)
Received: from segv.crash.com (segv.crash.com [IPv6:2001:470:1:1e9::4415]) (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 4BF873A15C6 for <dmarc@ietf.org>; Wed, 20 Jan 2021 15:20:17 -0800 (PST)
Received: from shiny.crash.com (192-184-141-33.static.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.7) with ESMTPSA id 10KNK42q055288 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 20 Jan 2021 23:20:12 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 10KNK42q055288
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1611184813; bh=aDluuwJHVNvY4wiJ2Mr1zVa8bOZ75VX9rS7kC5jViEA=; h=Subject:From:To:References:Date:In-Reply-To; b=cyGrLos0UMqUaKaIN2ZbDXkZ6KnrcTTO/h3XVSIy/GVgDkDWI37TwFKRcZWqHwwFJ VPmdNfRmdT8L+iTx9tqYPnFGPiW4xGb6cGUhBYFMFzjBgUTAYJ8zhDchSQb5+NEq57 hTnRtTKqHpuZ8ltdcmHMNt0iSkQEu78tTEnSVEcZnECc6AHxggEBCpc5n9eaNlz8QO tuM6x8oUInylxD9Rg1frno5x/eACInnT16yItMIIv1pimuLewwB7LN9fEfcpzE92pN gqb7i5OWSzVLfuslaZ342S8miPAydLqbYxhiAaIOxSaoWGrLH32hyFNuI02KlvRQAV QTrvRAwYHhHAA==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.static.sonic.net [192.184.141.33] claimed to be shiny.crash.com
From: Steven M Jones <smj@crash.com>
To: dmarc@ietf.org
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it> <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com> <f03aa3ae-2e6a-b095-39a2-837bfe2cabc4@crash.com>
Message-ID: <3c89c5f8-853e-8a8a-d026-3a834d26eccd@crash.com>
Date: Wed, 20 Jan 2021 15:20:04 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <f03aa3ae-2e6a-b095-39a2-837bfe2cabc4@crash.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Wed, 20 Jan 2021 23:20:13 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/azkMrvjh0Su4v6us4BTwWfp1JFI>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Wed, 20 Jan 2021 23:20:19 -0000

On 1/20/21 15:10, Steven M Jones wrote:
>
> Duplicate reports to the same destination are not
> the base case


I may be an idiot, or at least too quick to hit Send. Since nobody
implements https:// yet, what does the transition look like? Likely two
URIs to the same report processor, using each method.

But I suspect the specification can deal with preferring one method over
the other when both are present and the report generator supports both.

--S.



From nobody Wed Jan 20 16:01:12 2021
Return-Path: <mike@fresheez.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 86B1A3A1605 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 16:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 HS2WBVAaSgG7 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 16:01:10 -0800 (PST)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CD733A1602 for <dmarc@ietf.org>; Wed, 20 Jan 2021 16:01:10 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id p15so208547pjv.3 for <dmarc@ietf.org>; Wed, 20 Jan 2021 16:01:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=q9lfg0ORo0ObIqhJGf+82pXhpeNBwTWqD/l8J2Blk9I=; b=XoApGUJJrKpx1xbKQeH9T/0GyKewwLCjsXWhFhYdLz7TrUNGUUsepuzCcnpTf0Fr+Y NVj0kFDWpIQ0T6YIJ9PDe7CgIPaMP9fQIXCcHUuLBCA3Ri6+WhclT6d56ZYjEY9u7Eym JB1Rqzlj9PkMnAvkQLadNmwb0PbOYULPdQ+St+tZZlg6DATD2sWiXJEdtBmrSuzZJCrw DiRunRUHvry1+BbVhXy7f+XYDks5jbXj4pnUhzoIj45pq3Oj2DRER9njq8uFXdK31oTN rnPpfjp49C1PUkoyQnUMO1JwYE387rZF6Orbccl2r3u5pMbAmLd5SIVWcjYA1uLIC3mL pKBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=q9lfg0ORo0ObIqhJGf+82pXhpeNBwTWqD/l8J2Blk9I=; b=L0qKEdyUusFkH99uU9zwBsoXddcvbqvNNIda9+O5ta31WfOiD8QMrasB88fIzDpyr0 rZ1jSLcqDbVEMUo3QSrNg2c+5TjCnu6wGqsaVMfE2hn4CFOyjDMhxGjagEKPs+633eE6 sLQNHorCWKkwfQl/lPCJxbf8AA3DAXytQAVbxRqIdGcju884DW9MR6/ezRhcl3aVM8wm QK8ry+jqvpmwIyZr/7PXn6KZeTweo6dyOIb1KGgy9eUSabyKXzX7jjBLnGS9w8iDkFlT 5Dfa/WgQ5WMEIE3CFS35RcnRgUT0FIZMnjOiIVY+5IUcB1RtupKCu8tiOl7R13puMo/D mrKQ==
X-Gm-Message-State: AOAM532Soc6+lLDkikMkhbV/KhMltTzoh0YT+igVGOkgrDPY+aB1d5e3 jOq5YMUSyJzqSPi8KOaaTrZWh1eYrWAP9Q==
X-Google-Smtp-Source: ABdhPJyq/MMAZjLhpz7dpia3prPXmmOJMrdLvMgewz59jju1KMfOt/DrsvuQDPtdYFfB17RYvoyS4g==
X-Received: by 2002:a17:902:8e85:b029:de:23f0:f342 with SMTP id bg5-20020a1709028e85b02900de23f0f342mr11942561plb.69.1611187268978;  Wed, 20 Jan 2021 16:01:08 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id c8sm2255102pfo.148.2021.01.20.16.01.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 16:01:08 -0800 (PST)
To: Seth Blank <seth@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <af4c2a23-4a55-9103-487c-72a394fa594f@mtcc.com> <CAL0qLwaAptLh9OFr4VdzyPV4KV1M8vbMSw8DWZCf4zqVbfaT5w@mail.gmail.com> <CAOZAAfNw1amAfubGBMXY_FzDOaPzKkBb0TiaexZhk+JZXeFZ=Q@mail.gmail.com> <ac8530f6-e8c9-bb6b-d20a-2635d997e149@mtcc.com> <CAOZAAfPS92sdataw5G9RJd=nY5iQXFBO3PY1iEDUkSrHMTJJLA@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <9fb3fc89-2323-6621-8fdc-d6da0c23487a@mtcc.com>
Date: Wed, 20 Jan 2021 16:01:06 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfPS92sdataw5G9RJd=nY5iQXFBO3PY1iEDUkSrHMTJJLA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ypvUxauQ025G_7PGsBSr3gqLec0>
Subject: Re: [dmarc-ietf] Authentication of reports
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: Thu, 21 Jan 2021 00:01:12 -0000

On 1/20/21 3:08 PM, Seth Blank wrote:
> Discussion is in scope, per: 
> https://trac.ietf.org/trac/dmarc/ticket/42 
> <https://trac.ietf.org/trac/dmarc/ticket/42>
>
> This topic has come up before, and there's always general interest in 
> pursuing it, and absolutely no one who puts their hand up for either 
> it being impactful for them or having any interest in implementing it. 
> i.e. it seems interesting to people, but there seems to be no use case 
> with operational support to actually add it.
>
> So from those previous discussions, I don't think it's likely that 
> we'll add reporting beyond mailto:, but it is certainly a conversation 
> that's in scope when either ticket is opened.
>
>
Done.

Mike


From nobody Wed Jan 20 16:06:00 2021
Return-Path: <mike@fresheez.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 387593A1610 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 16:05:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level: 
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 QnGZPp1wKLqG for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 16:05:56 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CA9A3A144E for <dmarc@ietf.org>; Wed, 20 Jan 2021 16:05:56 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id x20so246864pjh.3 for <dmarc@ietf.org>; Wed, 20 Jan 2021 16:05:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Heh5qAx4olpX85rrWcalcCS4QhBvqmSK2g7JP7FNFRU=; b=mBK+kjRnz3i5MGE8xYZ0XMjb4D1xFINk0kp0OwdpbIm0NDfgf2iVR/Q6sfnHoz8wLI aKfgP0utZrZJi0UJbXZuH7OZtJ2CDOQtBQwEbpFnz7+5dOWtGSG+0O9cXZhcHY+L7WlR CCCFRL0/HkKfrciRlPO/EavPPDNX5wIvxeNpPxgCthpWW+E2ozq/9vGAYH36p3npOfuo v6Big9/51WeP2dzIMlMou3FtnhkuHcEWKxP753RqPBbNjPSknFpNxIU/Zd1wX3Rwu3uU hRTiFQDUn0JwqKu8+8QGp5Kvfr7FrCnivN9zF7njnxfejjIR3IbuA6/flggGeG6q04kl x1Mw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Heh5qAx4olpX85rrWcalcCS4QhBvqmSK2g7JP7FNFRU=; b=f0dkW1MqON0l62nAOz6bT5o1xieTkekOwjquPYo+D35YFcZRlsHERif/JK+4OlGukq sESY1G0sQQAZy+G0qeLLg1igJ12D5YtkbEXWqQSv8/SwyFvGtxxWHlRr7xDk0womiyXc m18IooNhqnVcwqjLEi6HLgDTeY9jk4er38pTQbxG4Rzwcmtw9espkIbD++RJori7tFAw lsBg48zSsG1b0SAemT5kp21iRmFztv1AWhbeg3Y3923ULOLvco1VyW1IXFOlCrmUeiYU jO9x9KkXEghnUGlNzLAvoqQpP9Z5+Ujnfqo0Lr97jMQ1i3lW+ICoP12aZOFoD8LGCiqO 7C+w==
X-Gm-Message-State: AOAM531sbl7NQs9Dg4NPUtL4GZ3I9IYHDQLsGuOEeoF8sxYBbjcpftVw n2Ad+oHygbcXmJKQYfVnsMSzsKB86hNlnQ==
X-Google-Smtp-Source: ABdhPJz+a+s4dEqx5F6gzohaF2pMdtx2KHj64EQTPqApnIoKxi+1QE40QLAsLxruypejlXFjZB6Wog==
X-Received: by 2002:a17:90a:517:: with SMTP id h23mr8482948pjh.108.1611187555632;  Wed, 20 Jan 2021 16:05:55 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id a31sm3368043pgb.93.2021.01.20.16.05.54 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jan 2021 16:05:55 -0800 (PST)
To: dmarc@ietf.org
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it> <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com> <f03aa3ae-2e6a-b095-39a2-837bfe2cabc4@crash.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <eb2c5c9e-48a1-76a7-aba7-0bb73eebc765@mtcc.com>
Date: Wed, 20 Jan 2021 16:05:53 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f03aa3ae-2e6a-b095-39a2-837bfe2cabc4@crash.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/RH0rU9rDBbQxUTwQwMbeARL9EGY>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Thu, 21 Jan 2021 00:05:58 -0000

On 1/20/21 3:10 PM, Steven M Jones wrote:
>
> I think we should specify HTTPS URIs, and following 7489 section 12.6
> "Secure Protocols" and current practices, HTTP should not be
> specified/permitted.
>
> However I don't yet see a compelling case for the OR- syntax or a
> separate "ruap" tag. Duplicate reports to the same destination are not
> the base case, and the bandwidth for unintended duplicates will likely
> be much smaller than, say, per-message DNS tree walks being discussed
> elsewhere. Report processors annoyed by receiving duplicates can work
> with the domain owners in question, and if that doesn't work they can
> withdraw their report authorization record.

See this before spending too much time. It's probably better to just 
junk this enhancement.

https://trac.ietf.org/trac/dmarc/ticket/99

Mike



From nobody Wed Jan 20 16:48:20 2021
Return-Path: <johnl@iecc.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 A45633A1657 for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 16:48:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=tXbyARrj; dkim=pass (2048-bit key) header.d=taugh.com header.b=LVfg3/71
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 akKPMczoG2vk for <dmarc@ietfa.amsl.com>; Wed, 20 Jan 2021 16:48:17 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 943F93A1655 for <dmarc@ietf.org>; Wed, 20 Jan 2021 16:48:17 -0800 (PST)
Received: (qmail 97835 invoked from network); 21 Jan 2021 00:48:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=17e13.6008cf50.k2101; bh=FWyVTE1HxXdzdiHSdRCkY+4nPgyhjS/uDgKzLNjB+MA=; b=tXbyARrjFpI9zPXqYLNzAlOMgZ52pP7qcKn75fVHcPmc5vFp+68N5snL+YvkFpv8xNN7JAmnLnmiuGcVbqDvx/LdUvp0DH76W+SnQoAnhOPqrFhwDBm/eQVWyhnCh3lyMY96DhJJutVJ2d/9lWyo+Dz2bMkE1wzslOhKNXq7fhz2JPOhoUzIuBTQUrKhODJYQj8wcfZi4wfvLz4YEw+8VPWzFnDkJLzEKi7iDjRdtC7xKMxygYwm8r1HnDEHGnJr01N8E8LVuRqBNeOBZjWja1+X2PaDpBtOvI6o6a4lnAvda/FqrgzdP3+U3gr7EJhIFbCuXhw98TG7sPp1ZPs46A==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=17e13.6008cf50.k2101; bh=FWyVTE1HxXdzdiHSdRCkY+4nPgyhjS/uDgKzLNjB+MA=; b=LVfg3/71Ve0g8tPBALMEKakJDkk4MaIv0nMKphFDgTUklZPFCsBCshaWiws0HKTBzHIpxRlgEjl9Te7dqBTMj+akGrxmkjNkpPamtSGjVqA2f/aHw6OtXa1ZMSlCdP2tSAxuXFAHKsqOle2ddevlZHN4XvC/klvrXELRNF5O+yyvzRPpLw3uuTiaC1w4/kiHIottdELPLDQT56k896Ayy2sMuN7WiFcMKeHNe6l5VwUez7/nsImixZr4GDdWer7xXk29pMrAqAoNDULiYbh7+YEggzlB7WnvBgWjJi4IB102TtgeDvmnoCMvc+ZyPGuDRULBovZV+czq/YJpeHlkRw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 21 Jan 2021 00:48:15 -0000
Received: by ary.qy (Postfix, from userid 501) id 5ED4F6BC714B; Wed, 20 Jan 2021 19:48:16 -0500 (EST)
Date: 20 Jan 2021 19:48:16 -0500
Message-Id: <20210121004816.5ED4F6BC714B@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: smj@crash.com
In-Reply-To: <3c89c5f8-853e-8a8a-d026-3a834d26eccd@crash.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4Rj4uIw6iaF7ho4Bhiw9n5Phvic>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Thu, 21 Jan 2021 00:48:20 -0000

In article <3c89c5f8-853e-8a8a-d026-3a834d26eccd@crash.com> you write:
>On 1/20/21 15:10, Steven M Jones wrote:
>>
>> Duplicate reports to the same destination are not
>> the base case
>
>I may be an idiot, or at least too quick to hit Send. Since nobody
>implements https:// yet, what does the transition look like? Likely two
>URIs to the same report processor, using each method.

Right, that's the question. I suppose we could do some hack like
saying that you process the URIs from left to right, and if you
succesfully do an https report, skip all subsequent mailto's, or
subsequent mailto's in the same domain.

For the specific details of https reporting, here's the two options (both
already implemented):

A) Do an HTTPS POST to the URL with application/gzip contents. This is
similar to MTA-STS but has the disadvantage that you don't get the
filename of the report.

B) Do an HTTPS PUT to the URL appending the filename from sec 7.2.1.1,
also with application/gzip contents.

I mildly prefer B since the filename can be useful, and this makes it
idempotent, since two PUTs of the same filename only store it once.

R's,
John


From nobody Thu Jan 21 01:24:31 2021
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 69A973A185A for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 01:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 ug9TOiXEb_o3 for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 01:24:28 -0800 (PST)
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 B6AE83A0D25 for <dmarc@ietf.org>; Thu, 21 Jan 2021 01:24:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611221064; bh=gl1SdCn87GoxgJwc0KgvYY/a28dg8vl1nq++e1erN8c=; l=1433; h=To:References:From:Date:In-Reply-To; b=AjKlKQ9M7Q3ZFSO44EEh3kIAvkVCX8u1mOL2tupGV91xv3/dtmMbr0uKCZphF1McP u/KkuvKYzR0b7W6PeSbl6FnFJvhRTIosEnT+sykAaEzHjqs6QI9xXL4xUUNWTt5MFy tIzkDObKg5bdNUivRGR+h5bFlibOEN1CYrNlbJp4wpPZQ/aipsb4TdPwz2JUU
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC056.0000000060094847.000070CD; Thu, 21 Jan 2021 10:24:23 +0100
To: dmarc@ietf.org
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <45b3df7-5c6-9744-2ca8-1542e1b33e7b@taugh.com> <478c7b56-f2b4-c7c1-7722-27fdce4bb8e9@tana.it> <CAHej_8=UTfpVBZJnP6anWshO+6ytU7jb4nybru2gmkFDHZwH5w@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <ebf4303b-88e0-4caa-267c-30c2c7516f24@tana.it>
Date: Thu, 21 Jan 2021 10:24:22 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8=UTfpVBZJnP6anWshO+6ytU7jb4nybru2gmkFDHZwH5w@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/yqIzhKIyBC_8qRQt7CpjzlpzmVo>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Thu, 21 Jan 2021 09:24:30 -0000

On Tue 19/Jan/2021 22:26:09 +0100 Todd Herr wrote:
> Picking up the thread on another ticket that was brought before the group
> pre-holidays and has lain fallow since the end of 2020...
> 
> John Levine asserted that there wasn't a lot of strong opinion on the
> matter, and therefore we'd be leaving the spec as is, with the MAIL FROM
> SPF check the only one that matters for DMARC.
> 
> Ale replied, but I don't interpret his reply as challenging John's
> assertion.


The thread went off-topic w.r.t. the purpose of ticket #1.


> Can this ticket be closed?


I agree that the spec needs some text somewhere to counter the passage in 
Section 2.3 of RFC 7208.  This, methinks, is the intended semantics of the 
second paragraph of section 3.1.2 of dmarcbis:

OLD:
    Note that the RFC5321.HELO identity is not typically used in the
    context of DMARC (except when required to "fake" an otherwise null
    reverse-path), even though a "pure SPF" implementation according to
    [RFC7208] would check that identifier.

I'd rather replace that paragraph and leave item 4 of Section 6.6.2 as is.  For 
a possibly less confusing wording:

NEW:

    Even tough a "pure SPF" implementation, according to [RFC7208], would
    avoid to check the RFC5321.MailFrom identity if the RFC5321.HELO was
    conclusively determined to pass, DMARC authentication requires the
    authenticated identity to be aligned.


Best
Ale
-- 




















From nobody Thu Jan 21 01:44:42 2021
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 BC7D63A1865 for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 01:44:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 l1p8oqZYbRbY for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 01:44:39 -0800 (PST)
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 C8D5C3A1864 for <dmarc@ietf.org>; Thu, 21 Jan 2021 01:44:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611222276; bh=1VvUanyV8SnyxUKAOAf6Q6U7o7+xgIWYNHLrptNgp2Q=; l=589; h=To:References:From:Date:In-Reply-To; b=Bb08pMwJQLBBWIQppNEsu+z8GwEceaJX4opPunKjmExMWKOQj42TVDw9PjL9c3lHB krJSlbkpTom7lQv8N0zmNCPME7njIO8i4TYZlJVhh6cym9u/qD70t/iAoLymQ0Y9Hb 1NcxSeByxAhm5K2smrsyAmIydX636sBCkMT5tyCAR3ipAKsKQPaIJMq+aQDKn
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC056.0000000060094D04.00007320; Thu, 21 Jan 2021 10:44:36 +0100
To: John R Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it> <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <a18942d2-817d-4771-4466-6aaa07dfd707@tana.it>
Date: Thu, 21 Jan 2021 10:44:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZJ75kdF_7HaAsJredE44T0rCCdk>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Thu, 21 Jan 2021 09:44:41 -0000

On Wed 20/Jan/2021 20:19:23 +0100 John R Levine wrote:
> On Wed, 20 Jan 2021, Alessandro Vesely wrote:
>> John's record looks more workable, but it's still fluffy:
>>
>> "v=DMARC1; p=none; rf=afrf; 
>> rua=mailto:dmarc-a@abuse.net,https://dmreport.abuse.net/dmreport/; 
>> ruf=mailto:dmarc-f@abuse.net"
> 
> Whaddaya mean fluffy?  Try a PUT or POST to that URI and it'll work.


Surely you don't expect a DMARC report generator to parse https: and scream out 
"Oh Gosh, here's what I've been hopelessly waiting for...".  For non-human 
parsers, it's fluff, no?


Best
Ale
-- 


















From nobody Thu Jan 21 02:06:33 2021
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 65E0E3A186E for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 02:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 fiRzcMJjTPCr for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 02:06:29 -0800 (PST)
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 95D803A186C for <dmarc@ietf.org>; Thu, 21 Jan 2021 02:06:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611223587; bh=vgHvNnAGdEIde6/hYA7kAfmp7NQ4lpQtBMH8E+sDLxw=; l=1494; h=To:References:From:Date:In-Reply-To; b=BZEurB5+QgQEknDPmgoopS5YdqwtnNZpWjJNELzz36wHfLamYG9VP+53d79afEZey sl9+QDWTd3v09AAz2B1tlofpdkQ5OAxKctNG91xwuKkLlOeg0vh1pXVAij7K5kwP96 siSimEd61ppFiwVf6f3UwhZSx5IiwcsCRAoZZDrsivjZzyf/ILMJzVYlLmncG
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0CC.0000000060095223.000076EE; Thu, 21 Jan 2021 11:06:27 +0100
To: dmarc@ietf.org
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it> <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com> <f03aa3ae-2e6a-b095-39a2-837bfe2cabc4@crash.com> <eb2c5c9e-48a1-76a7-aba7-0bb73eebc765@mtcc.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <edec6fe7-4c69-510b-4613-d000c4ca924b@tana.it>
Date: Thu, 21 Jan 2021 11:06:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <eb2c5c9e-48a1-76a7-aba7-0bb73eebc765@mtcc.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/jkXeGytwNFjOH3728CtBkkdaUaM>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Thu, 21 Jan 2021 10:06:31 -0000

On Thu 21/Jan/2021 01:05:53 +0100 Michael Thomas wrote:
> On 1/20/21 3:10 PM, Steven M Jones wrote:
>>
>> I think we should specify HTTPS URIs, and following 7489 section 12.6
>> "Secure Protocols" and current practices, HTTP should not be
>> specified/permitted.
>>
>> However I don't yet see a compelling case for the OR- syntax or a
>> separate "ruap" tag. Duplicate reports to the same destination are not
>> the base case, and the bandwidth for unintended duplicates will likely
>> be much smaller than, say, per-message DNS tree walks being discussed
>> elsewhere. Report processors annoyed by receiving duplicates can work
>> with the domain owners in question, and if that doesn't work they can
>> withdraw their report authorization record.


The point is that if you specify both mailto: and https:, a compliant report 
generator should send to both URLs.  OTOH, if you only specify https:, you are 
going to miss a lot of reports.


> See this before spending too much time. It's probably better to just junk this 
> enhancement.
> 
> https://trac.ietf.org/trac/dmarc/ticket/99


The proposed workaround implies sending base64, which is what https: is meant 
to avoid.  Your suggestion to use it as an authentication mechanism for https: 
sounds better.  You just need to add From: and DKIM-Signature: header fields, 
where the binary body is hashed as-is, that is, with no canonicalization.  It 
seems to require an easy software enhancement.


Best
Ale
-- 



















From nobody Thu Jan 21 11:11:54 2021
Return-Path: <johnl@taugh.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 3D5C53A0A3E for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 11:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=IaendPij; dkim=pass (2048-bit key) header.d=taugh.com header.b=IqQ8er19
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 DmYzkkRKMth3 for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 11:11:50 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 924F93A0A26 for <dmarc@ietf.org>; Thu, 21 Jan 2021 11:11:49 -0800 (PST)
Received: (qmail 1409 invoked from network); 21 Jan 2021 19:11:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=57f.6009d1f4.k2101; bh=KfwlNxf3Xv4U0NYmgDi7enBcCDh11IiHIa2xQn+4U3Q=; b=IaendPijxTuOv+teBzsYHJz1evZaT/fr2t1BEo2rT8xtD5d35iuKJShKcsknWEk4l2gIBq5ixwbfhipI/SJclnQSHVm1bDmCnGfq7PitTRonzRRVG3qp9MNpyJEt34izz58jYhsl16EJ+d9IngQg4+MoGtR65zx8+Uw/pE3PBJt9WHFz/jFJ4B/92dW1winlDg9HdbY8PxlVttlbuhzdwiQMW/lQkRr+RccFG04s7uJJs1g9vx0O5Btda4fqn4FzxPjwGh75KuNakExkC52/c5mRrcAbhzVNkVpflRVrhSq8750MLzwuwjReyS8lR1ltsAf0RnTuijInmzm6vf9GUA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=57f.6009d1f4.k2101; bh=KfwlNxf3Xv4U0NYmgDi7enBcCDh11IiHIa2xQn+4U3Q=; b=IqQ8er1941RMi0b2InbvD4Q4wPyu55f4AK4o0C9XC3kWmAoaCSPJDy2hIwh9CuQNvzaS/L4vSU/9CiqLXbI/EhxzAVt27kwrKZqD1C2noY/sPdABi3/Ee6/FbcZjq2pAkWUMYW4qIUvBg3c4S/K/b0ue98S5CBwZUFer6wuo6BJqDsFIa97ns8Y/1H13DgpHnyvjCAYV9/ticu2VxqApv0soqNqlXZD4WbT0Jz7ZNYOmJpx0MNo2IojgSqT0nWZqe/Ap4QVL/eSI4o3LW8rgn1iSbuxqCM+1DqO/RwEyyaHslxAWqMOZvLIq6RqNqxe3C90/Jck2VI7EKe9wUejFYw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 21 Jan 2021 19:11:48 -0000
Received: by ary.qy (Postfix, from userid 501) id 33D626BE30ED; Thu, 21 Jan 2021 14:11:47 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 234566BE30EC; Thu, 21 Jan 2021 14:11:47 -0500 (EST)
Date: 21 Jan 2021 14:11:46 -0500
Message-ID: <d971a5d0-1616-733a-f9f2-6699277d228@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <a18942d2-817d-4771-4466-6aaa07dfd707@tana.it>
References: <20210120023151.3C86A6B7C86C@ary.qy> <ccc2489b-742d-acca-58db-55519764b02f@tana.it> <132aa0a-bd63-9ed1-e3d-75b23f46f15@taugh.com> <a18942d2-817d-4771-4466-6aaa07dfd707@tana.it>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-31652168-1611256307=:48424"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xd1W755VozhsbUWp65Uj8cgZslI>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Thu, 21 Jan 2021 19:11:52 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-31652168-1611256307=:48424
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Thu, 21 Jan 2021, Alessandro Vesely wrote:
>> Whaddaya mean fluffy?  Try a PUT or POST to that URI and it'll work.
>
> Surely you don't expect a DMARC report generator to parse https: and scream 
> out "Oh Gosh, here's what I've been hopelessly waiting for...".  For 
> non-human parsers, it's fluff, no?

I didn't know whether anyone had implemented the https reports in the 
early drafts of 7489.  Given that I haven't gotten any of them, apparently 
not.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
--0-31652168-1611256307=:48424--


From nobody Thu Jan 21 13:00:02 2021
Return-Path: <Alex_Brotman@comcast.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 5A8143A0C8A for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 13:00:01 -0800 (PST)
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_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.com
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 xmYOUHpDk7ik for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 13:00:00 -0800 (PST)
Received: from mx0a-00143702.pphosted.com (mx0a-00143702.pphosted.com [148.163.145.77]) (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 3C94F3A0C40 for <dmarc@ietf.org>; Thu, 21 Jan 2021 13:00:00 -0800 (PST)
Received: from pps.filterd (m0184894.ppops.net [127.0.0.1]) by mx0a-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10LKu4QT022517 for <dmarc@ietf.org>; Thu, 21 Jan 2021 15:59:59 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.com; h=from : to : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=20190412; bh=ynqYXG/sCMjFuyUNLbzSc5TGvTUezbUO7mboFDf5/yA=; b=zezC31kPF72T9cS7GEBn/JJlEmYQ3bLCDXz4MOjJtDAZpe9bBKu+gB0TdXZs41TcIkpH FWKcje48xSiveSi6JKU4fdkoGt0ADchgR7iTYqwoVp0ICTj7IrPuFswNnIKCo37O2emS 1Qx45zm98+JIuKsyzQpE/ybQjuSLb3YY3MdYRjj+R4gbOlegbs3VK7lFUXxjfwX6M+fw qMF8vZsdPX5dal48kVze9nxlUWKLlwWP2/iAO/8jB+vhhSLd4J22EZ6j8t7l31r+zJke v3kxLWALehQ0Df7431X8bK9B7n5J6b5GSA6TPA6q4YWdCozmPyVpLcwN4oxEk3PXBOc8 CQ== 
Received: from copdcexc36.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0a-00143702.pphosted.com with ESMTP id 3668pxx0rd-18 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Thu, 21 Jan 2021 15:59:59 -0500
Received: from copdcexc33.cable.comcast.com (147.191.125.132) by COPDCEXC36.cable.comcast.com (147.191.125.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 21 Jan 2021 13:59:55 -0700
Received: from COPDCEXEDGE01.cable.comcast.com (96.114.158.213) by copdcexc33.cable.comcast.com (147.191.125.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Thu, 21 Jan 2021 13:59:55 -0700
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (104.47.66.45) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 21 Jan 2021 15:59:56 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4080.namprd11.prod.outlook.com (2603:10b6:208:137::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.13; Thu, 21 Jan 2021 20:59:41 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42%7]) with mapi id 15.20.3784.013; Thu, 21 Jan 2021 20:59:41 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: Reports helping spammers? (#81)
Thread-Index: AdbwN7eHzVTBNYjVTlSst7HV1ZiSWA==
Date: Thu, 21 Jan 2021 20:59:41 +0000
Message-ID: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:cc0c:4516:4bee:da79]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6b1996a5-931f-471d-0982-08d8be4f78de
x-ms-traffictypediagnostic: MN2PR11MB4080:
x-microsoft-antispam-prvs: <MN2PR11MB4080226DD256916BFDFB3213F7A19@MN2PR11MB4080.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: V/utwQxC7y0D/5TNvd2xzFYhre1zmHGsdLtS4wRZDpspmXf/Otox0r9Pc/irxw91Wzj59cOHFDZhADTdjxyA+cm/ggied8GUdwj6DGY8o9s1RUYs3GKEcnDUeMda5SoFyC4E/YL8mK/tHywW4un/Qr83Jkq+IrJT/ayjlfO7UkotGaI422tRujfg/22yjidHAQPn57F8BZLrG4LUWQJakEYKogdGvRzCgwCRXYXWoAIq03E+Vy8FliL9SonYkqV0+MPSadS7rqyE3XjtGKQvOmCwPWDoPjwWPBrdWneJ+m3iYFuXvalOLUyTWSucvkIt9MRdNT4iVLXHML1oPuNXcc/LUxdY8pluM2z0/TTHTi5KYVgvk8v2P/e7ioWpgDlfGL3Hh0LrJlpZIqDcbZ7B+Q==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(136003)(376002)(396003)(366004)(346002)(6916009)(66476007)(33656002)(8676002)(66946007)(6506007)(64756008)(186003)(66446008)(66556008)(7696005)(76116006)(316002)(5660300002)(8936002)(2906002)(52536014)(86362001)(83380400001)(9686003)(71200400001)(55016002)(478600001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?FitFLPZs64lozMKFWmZp26b9k7UKOYB3zp6JV51Vr+uBJF7W4N0Jy9g3KoZX?= =?us-ascii?Q?Fw+Lr87dTBZOVUDQwquc3mWWDFY185ii9lJY0QIxqRVulXKz6aS+AuRdrcEK?= =?us-ascii?Q?PjVU/5stuKgDfd4T9XWDWD3wUhvYlvjpPMRpjRYUiDc7UaQpchtEpYwRfDa5?= =?us-ascii?Q?T9Eo4rKJdn+Fq+qC9Ij2M58ldlIDO37XVZefi7K6IJAD+gvT6/4cU6dR36U2?= =?us-ascii?Q?VT6cBG7aJtbaXaTh8BMnbtfLsE8lUKnHDulL9sJZvVrNv6Vbu0Y172vuWy3A?= =?us-ascii?Q?8ycNPEHlqOnNgLO8Y3GZoocPAfOGoV6ZCJGt8CGnqHV1eHqCgJcA+9NDksQY?= =?us-ascii?Q?/tkwzXWpmT/hJtUXXgmLid38AzHrWVnxi9HD/J9nrtvSa8mj+7ygREa4AMIF?= =?us-ascii?Q?2ZKP41CEvtpzMzndT9FYOYXRdyZcadLNL4JG4sBX7AM5qrnK2q7QvB9PZYx1?= =?us-ascii?Q?z1pGu2/B2n+PycOWSLjZn/J1kp/xCVo7nh+dQ8boupJYZ/i6fKFyWDco+jen?= =?us-ascii?Q?RIR8cfyLxfnDy2RE+tIl9y4Kxw3vyWmNeuI2jVJundppCR7PnJU4EVVHEF+y?= =?us-ascii?Q?dxPf8zyb5NJjRnxjM2y3aaSdOCRLdvkkDKn6zAzDBRnm4G4n/aJe9MtPrAHT?= =?us-ascii?Q?izv0tnGqt++BcbanguF60Dmy4qxcCbGnjRY18zYFTo1IIv2Lf/lzAUJPMsgL?= =?us-ascii?Q?yR99OaRDmNCpSaMHEhw7gEEs14TDQgrY9dVj9v7udxsBIZa/bCDqorTSmLHv?= =?us-ascii?Q?f9+EMWRLHDrurUNs+YQBHZ615w2RBaqHZR7+hXppcy6hIEPRFwvDwrruUYX/?= =?us-ascii?Q?JYSDdABBB5RfUDYbCbwisfMEcs0dK8hVuKVo7dsYeaE91SsqHqhKk8Ig3h9S?= =?us-ascii?Q?8wqFxf3rstmL5XQiz7QjDTjsVgImSbKLaMVS6qjhN53TuZm5yR1AOAtKwGpI?= =?us-ascii?Q?o7tb9SCdYM5w3IjI09UYZTff8LkQcjzexA4I6IgTOpyVI+qFrRbfzQypT+po?= =?us-ascii?Q?XiaX3ktMhf1CaskkHiS7SBSlAQ7+7zulWOV7WDqR4dGH1pM=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bCcjFzYC7Tw95TcD13IheBaCaA3YDj6GgmV4tO9GS704t7nBGxhsOfEyQWI3rgwDlFhB+HwAB32D3iUuAPLNOApFJuLTqtYTUdB708sCr2Tt6V8Ln0db5Jodt7UVRalMITJPDw8SKB0knT37oS2/dJl4yzYBw9UcA6ZEN0ttan1LBL5XMECBMwT42vdAEB2gNQHszWeb9Mn5WNewkpRHB5qvtIp9rIzKtibRcBPFn/8DWdFmuKJeycXzoE6N6P0h7Dfj9x3hpvXEa7fvweTSr2Ugh9Jcoi6e9M28Jbj3DKLjG76YbcjV5KfDkM9UZrwEPtgPAayUkmyyN8e0YG4ZPg==
arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Fnwhv3ne5Oy0UY2fMtcPpCEmbuqj+uYX78rfAbV03XA=; b=PCxhZYjJaH9OoajHMgA7KVX9SbUZO+/B6/PxtKKX4uBYwqIsK5xVwn0keWMUBrSOOXPGFVP0fnTYCYc+UKj92hVrZyYxp085YWbFC0adPwAMSdR4m7wZBlYIRMoftTZLJWsh7kAzPThHP3TucY51OvQPshQU50xXd4RLzOUed341YeXj4hXVE7hdGJX6Flk6YTpBT1YQlGqej/fpGmVjJcIh29NdE+XhwLRqOqzfAYj99cO/8IQ0mgt8JyiFW2mIol6S/5LdDwvrOJ8+z57U3JKqSntXgLWWN2wUy7hN9BOP3vxHutklSpfg2MMFz/9fUfLVgMkn50891rQ5UqzSow==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=comcast.com; dmarc=pass action=none header.from=comcast.com; dkim=pass header.d=comcast.com; arc=none
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: MN2PR11MB4351.namprd11.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: 6b1996a5-931f-471d-0982-08d8be4f78de
x-ms-exchange-crosstenant-originalarrivaltime: 21 Jan 2021 20:59:41.2106 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 906aefe9-76a7-4f65-b82d-5ec20775d5aa
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: Et2QyZSfKyWUI+OT+F7ZOD5XxlGYJjMcdBVRrPxU/5r5VLvJB9YKBZ7h9/1vGoKKkhG6KRlNT9tVzstgPQGLEr+yLx+BYk2epnpFnLiA1/A=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4080
x-originatororg: comcast.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWO
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-21_10:2021-01-21, 2021-01-21 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/1y0c4xG7bN0rHR1Fi2Kuv5MxlGQ>
Subject: [dmarc-ietf] Reports helping spammers? (#81)
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: Thu, 21 Jan 2021 21:00:01 -0000

Hello folks,

Thought I'd see if we could come to a conclusion on this ticket.  The gist =
is that the reporter believes that (aggregate?) reports can help spammers t=
o determine some effectiveness of their message attempts.

Full Text:
-------------
Spammers could use DMARC reports to monitor the effectiveness of their camp=
aigns, and we do not want to help them. Do existing implementations send re=
ports to any domain that requests them, or only to those domains that are c=
onsidered "acceptable"? If reports are only sent to acceptable domains, wha=
t sort of criteria have been useful?

System administrators will appreciate such advice. Product developers will =
need guidance about the features they should provide so that a system admin=
istrator can control which domains do not receive reports.
-------------

>From an operator side, I don't agree with this assessment.  The reports do =
not show if/why a MBP may place a message in the Junk folder.  Could it be =
DMARC quarantine?  Sure.  It could also be any number of things from a larg=
e matrix of decisions, none of which are shown in a DMARC report.  Also, th=
e reports are typically sent once per day (seems like most ignore the 'ri')=
, quite likely some time after the end of the reporting period.  Additional=
ly, they probably have more efficient/immediate methods of evaluating their=
 success rate.

If you believe something has been overlooked, please feel free to share.

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast


From nobody Thu Jan 21 13:42:40 2021
Return-Path: <seth@valimail.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 C07A23A0CD6 for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 13:42:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 3deQ7yLfNBVn for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 13:42:37 -0800 (PST)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B29E23A0CFC for <dmarc@ietf.org>; Thu, 21 Jan 2021 13:42:37 -0800 (PST)
Received: by mail-vk1-xa2f.google.com with SMTP id d6so874105vkb.13 for <dmarc@ietf.org>; Thu, 21 Jan 2021 13:42:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=CY1G39QbzMJWYjU4mHpTWyt1r5XeiwvPkqsdghVqdlw=; b=NQTnuEIv74/vJ9pnVSXpb6cIwQ2esVYKrHLWRl/Pku+sIRY5P1ivJ1THq64QdcbTiU u/Ht3+kUKh1q9c0CDbndkmyjpBVmacuYYDzL/EpY9X9l5HrMXoNcnR/ahgzgUIooKPz/ MZ3Kd2l2KK5je2SnnhaMlI5X0/lCzgSiyWCWBF/rNK1z+d4+x22VYsy2Tr2CsELp9Fd1 laUs9dtg+EV9K8QJVX92JcK+aL96Jr7kXvJbuViEh5T+0KlCFViI4eaE3M4FY87ZI682 bhtGQs2GQvI1lTqAOJHL7xfhoNcIg5jtZEG3pJagDNt3dFHsnPiIBCvIN1SMFBXnLzXy 7L+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=CY1G39QbzMJWYjU4mHpTWyt1r5XeiwvPkqsdghVqdlw=; b=Q2n30Xd7i1XVDTunjLv8L3QtoU3oLiRJQ7Su4z1M5obwUyOZOoir/zh7T+TkTxJR15 MFaWtaLj+SvRPUktmBPEtbxoo5UHiaOr0o5q8NEu4D9vZ2Us/kpbFQ+hw1jPjF4hZ1U/ ZAr9z36Ig5BX7vPJr7okcsawQ/o2zaq9o2+Qpbq/tO9SpTaizo/jy857T7xclhazMOcd T4gds120TKKHGSCYVO/K4taI7AxxMAGQkFaDlUUGcV+rSwuk0ypCg2SnDeqQFvxCSPVV VeEWchI58+i9bAcYzs7j0dH3J/G2o5QLlpDHDEDgeziv6C9lJPvYFgsIAo340PS39nZ+ Bs8A==
X-Gm-Message-State: AOAM530gz/RNiofARg6olQcj+4i9ymj2iuk9JPOujgOsITzUbldkg41J gu7Fzyiyo4SpMpGWpBSE+CPpurlYoRkoi8d4t1d3RoXvd10=
X-Google-Smtp-Source: ABdhPJw0ARB8k+DocN8xAnqw6aaXZTIs651SmrIBrVdD2unZ0OBuKd2NzS5pYBVk9m4+2ygceaQVIDtgVCW++G1oMFo=
X-Received: by 2002:a1f:198f:: with SMTP id 137mr1239167vkz.2.1611265356312; Thu, 21 Jan 2021 13:42:36 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Seth Blank <seth@valimail.com>
Date: Thu, 21 Jan 2021 13:42:25 -0800
Message-ID: <CAOZAAfMDK=oz10O+jMyG5wvYyKpVpoOCyQxQv1_kokWutffXuQ@mail.gmail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000033c64d05b96ff39d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Lobz_6_rn_O1kUrSlk6v45YlYX4>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Thu, 21 Jan 2021 21:42:40 -0000

--00000000000033c64d05b96ff39d
Content-Type: text/plain; charset="UTF-8"

I don't understand this concern. The data in a DMARC report speaks to the
underlying authentication of a message on receipt, and nothing about the
"spaminess" or not of a message as it's processed.

On Thu, Jan 21, 2021 at 1:00 PM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Hello folks,
>
> Thought I'd see if we could come to a conclusion on this ticket.  The gist
> is that the reporter believes that (aggregate?) reports can help spammers
> to determine some effectiveness of their message attempts.
>
> Full Text:
> -------------
> Spammers could use DMARC reports to monitor the effectiveness of their
> campaigns, and we do not want to help them. Do existing implementations
> send reports to any domain that requests them, or only to those domains
> that are considered "acceptable"? If reports are only sent to acceptable
> domains, what sort of criteria have been useful?
>
> System administrators will appreciate such advice. Product developers will
> need guidance about the features they should provide so that a system
> administrator can control which domains do not receive reports.
> -------------
>
> >From an operator side, I don't agree with this assessment.  The reports
> do not show if/why a MBP may place a message in the Junk folder.  Could it
> be DMARC quarantine?  Sure.  It could also be any number of things from a
> large matrix of decisions, none of which are shown in a DMARC report.
> Also, the reports are typically sent once per day (seems like most ignore
> the 'ri'), quite likely some time after the end of the reporting period.
> Additionally, they probably have more efficient/immediate methods of
> evaluating their success rate.
>
> If you believe something has been overlooked, please feel free to share.
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--00000000000033c64d05b96ff39d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t understand this concern. The data in a DMARC r=
eport speaks to the underlying authentication of a message on receipt, and =
nothing about the &quot;spaminess&quot; or not of a message as it&#39;s pro=
cessed.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Thu, Jan 21, 2021 at 1:00 PM Brotman, Alex &lt;Alex_Brotman=3D<a =
href=3D"mailto:40comcast.com@dmarc.ietf.org">40comcast.com@dmarc.ietf.org</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">He=
llo folks,<br>
<br>
Thought I&#39;d see if we could come to a conclusion on this ticket.=C2=A0 =
The gist is that the reporter believes that (aggregate?) reports can help s=
pammers to determine some effectiveness of their message attempts.<br>
<br>
Full Text:<br>
-------------<br>
Spammers could use DMARC reports to monitor the effectiveness of their camp=
aigns, and we do not want to help them. Do existing implementations send re=
ports to any domain that requests them, or only to those domains that are c=
onsidered &quot;acceptable&quot;? If reports are only sent to acceptable do=
mains, what sort of criteria have been useful?<br>
<br>
System administrators will appreciate such advice. Product developers will =
need guidance about the features they should provide so that a system admin=
istrator can control which domains do not receive reports.<br>
-------------<br>
<br>
&gt;From an operator side, I don&#39;t agree with this assessment.=C2=A0 Th=
e reports do not show if/why a MBP may place a message in the Junk folder.=
=C2=A0 Could it be DMARC quarantine?=C2=A0 Sure.=C2=A0 It could also be any=
 number of things from a large matrix of decisions, none of which are shown=
 in a DMARC report.=C2=A0 Also, the reports are typically sent once per day=
 (seems like most ignore the &#39;ri&#39;), quite likely some time after th=
e end of the reporting period.=C2=A0 Additionally, they probably have more =
efficient/immediate methods of evaluating their success rate.<br>
<br>
If you believe something has been overlooked, please feel free to share.<br=
>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--00000000000033c64d05b96ff39d--


From nobody Thu Jan 21 15:03:22 2021
Return-Path: <todd.herr@valimail.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 227963A0AFB for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 15:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 lb3K9-lk2wid for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 15:03:18 -0800 (PST)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BB6C3A0B05 for <dmarc@ietf.org>; Thu, 21 Jan 2021 15:03:18 -0800 (PST)
Received: by mail-qk1-x72d.google.com with SMTP id x81so601190qkb.0 for <dmarc@ietf.org>; Thu, 21 Jan 2021 15:03:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4z0Vpv/opZLCK864JsbKhLC6JK1HJ6D+BIpX7U2nm8g=; b=Mc3cnW8M//oJnVywuUTF1WV+DmchSt8MhwnIIdkRcQDf4QnvR2CxTzJirn0PYV1P+y ImronLquDNsd5PGgYA8NxHwFdxNAi5mHZcxRCYBPh8WZQUzM/syJkL3A5LbLv5235W3x zlIC62Vhz/xhf9C0noc1Aci//n6zCP8d6AdB2c0MPS9nQb12xoboywh52M7Eq11IFmZ5 CLkTo+p5hvvC14mJ3pWFe5VnJixF+hf8q2psyAPLGl2FhsySQdKyWf/pTvuvCZXX0DLU 07GrYeDaa58BXs4dmFNWtkCUvKwsUtw9QJ5NWFAxDrbU7fUBelc8ZOcWovthS1gHs5T3 a2gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4z0Vpv/opZLCK864JsbKhLC6JK1HJ6D+BIpX7U2nm8g=; b=Avt/RoE8oPcusG3gMgJy5N1mTjE0rx4XOui7sShshaXhSWBAgLK6Anm+QNVlJRzuLg aCYWWF0o96NNw5CFgIvPLEhu4bZTfOsAmFDiKysgEViD9l+QcjHOF0Jh+Nl1wuChvPHo l0Qhewyk71BCg+lQo3yjldqdgETSJju+lg5kWZ5W//rLTWzCnLj1CGX/cPr+E/BVf+3r HlVnTW6PxUbXJy6lWJgDWRk1abzZbcLNpufv2BUcfTLu4yU2qWXfM6Q/3gNTLGkuPlbW ff4cbAbXu3WYeVjan1CxdZRuRbpFXOIUuQmlUJTv2S5eUj8zeEou0kdyxnP2XURIUPig Dtbg==
X-Gm-Message-State: AOAM530zPgMUrY2UTMf1nvYUNPlkYcttCTAwdV+Gt0ZJhbeJx/ftgUl5 y2R3zBd+KeJQhohA32Y8BWPVvq09bwiFP1fSSp+smA==
X-Google-Smtp-Source: ABdhPJyrlX7VYJzro0+shTFGVz9nmVhua4bMCM+BUhG59BAm+Mco9pCPEwYrKY6nmEMgVdYByA+JvvVHbm7ssgsFtbI=
X-Received: by 2002:a37:e20d:: with SMTP id g13mr2217929qki.325.1611270196233;  Thu, 21 Jan 2021 15:03:16 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAOZAAfMDK=oz10O+jMyG5wvYyKpVpoOCyQxQv1_kokWutffXuQ@mail.gmail.com>
In-Reply-To: <CAOZAAfMDK=oz10O+jMyG5wvYyKpVpoOCyQxQv1_kokWutffXuQ@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Thu, 21 Jan 2021 18:03:00 -0500
Message-ID: <CAHej_8n9crrj6xypUJeMJT+5G+8UVPhKLKScHqtcXzJTe7utLg@mail.gmail.com>
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000af20a405b97113c6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/CjaQXb0Mpy5gYj73inc8RlwOi4U>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Thu, 21 Jan 2021 23:03:21 -0000

--000000000000af20a405b97113c6
Content-Type: text/plain; charset="UTF-8"

I would submit that it would be in the best interests of mailbox providers
and others who are in the business of making acceptance and filtering
decisions to ensure that spammers properly authenticate their email, so as
to better and more reliably assign a poor reputation to the associated
domains and make it easier to identify them.

On Thu, Jan 21, 2021 at 4:42 PM Seth Blank <seth=
40valimail.com@dmarc.ietf.org> wrote:

> I don't understand this concern. The data in a DMARC report speaks to the
> underlying authentication of a message on receipt, and nothing about the
> "spaminess" or not of a message as it's processed.
>
> On Thu, Jan 21, 2021 at 1:00 PM Brotman, Alex <Alex_Brotman=
> 40comcast.com@dmarc.ietf.org> wrote:
>
>> Hello folks,
>>
>> Thought I'd see if we could come to a conclusion on this ticket.  The
>> gist is that the reporter believes that (aggregate?) reports can help
>> spammers to determine some effectiveness of their message attempts.
>>
>> Full Text:
>> -------------
>> Spammers could use DMARC reports to monitor the effectiveness of their
>> campaigns, and we do not want to help them. Do existing implementations
>> send reports to any domain that requests them, or only to those domains
>> that are considered "acceptable"? If reports are only sent to acceptable
>> domains, what sort of criteria have been useful?
>>
>> System administrators will appreciate such advice. Product developers
>> will need guidance about the features they should provide so that a system
>> administrator can control which domains do not receive reports.
>> -------------
>>
>> >From an operator side, I don't agree with this assessment.  The reports
>> do not show if/why a MBP may place a message in the Junk folder.  Could it
>> be DMARC quarantine?  Sure.  It could also be any number of things from a
>> large matrix of decisions, none of which are shown in a DMARC report.
>> Also, the reports are typically sent once per day (seems like most ignore
>> the 'ri'), quite likely some time after the end of the reporting period.
>> Additionally, they probably have more efficient/immediate methods of
>> evaluating their success rate.
>>
>> If you believe something has been overlooked, please feel free to share.
>>
>> --
>> Alex Brotman
>> Sr. Engineer, Anti-Abuse & Messaging Policy
>> Comcast
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>
>
> --
>
> *Seth Blank* | VP, Standards and New Technologies
> *e:* seth@valimail.com
> *p:* 415.273.8818
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000af20a405b97113c6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I would submit that it would be in the best interests of m=
ailbox providers and others who are in the business of making acceptance an=
d filtering decisions to ensure that spammers properly authenticate their e=
mail, so as to better and more reliably assign a poor reputation to the ass=
ociated domains and make it easier to identify them.</div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 21, 2021 at=
 4:42 PM Seth Blank &lt;seth=3D<a href=3D"mailto:40valimail.com@dmarc.ietf.=
org">40valimail.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"ltr">I don&#39;t understand t=
his concern. The data in a DMARC report speaks to the underlying authentica=
tion of a message on receipt, and nothing about the &quot;spaminess&quot; o=
r not of a message as it&#39;s processed.</div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 21, 2021 at 1:00 PM Br=
otman, Alex &lt;Alex_Brotman=3D<a href=3D"mailto:40comcast.com@dmarc.ietf.o=
rg" target=3D"_blank">40comcast.com@dmarc.ietf.org</a>&gt; wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">Hello folks,<br>
<br>
Thought I&#39;d see if we could come to a conclusion on this ticket.=C2=A0 =
The gist is that the reporter believes that (aggregate?) reports can help s=
pammers to determine some effectiveness of their message attempts.<br>
<br>
Full Text:<br>
-------------<br>
Spammers could use DMARC reports to monitor the effectiveness of their camp=
aigns, and we do not want to help them. Do existing implementations send re=
ports to any domain that requests them, or only to those domains that are c=
onsidered &quot;acceptable&quot;? If reports are only sent to acceptable do=
mains, what sort of criteria have been useful?<br>
<br>
System administrators will appreciate such advice. Product developers will =
need guidance about the features they should provide so that a system admin=
istrator can control which domains do not receive reports.<br>
-------------<br>
<br>
&gt;From an operator side, I don&#39;t agree with this assessment.=C2=A0 Th=
e reports do not show if/why a MBP may place a message in the Junk folder.=
=C2=A0 Could it be DMARC quarantine?=C2=A0 Sure.=C2=A0 It could also be any=
 number of things from a large matrix of decisions, none of which are shown=
 in a DMARC report.=C2=A0 Also, the reports are typically sent once per day=
 (seems like most ignore the &#39;ri&#39;), quite likely some time after th=
e end of the reporting period.=C2=A0 Additionally, they probably have more =
efficient/immediate methods of evaluating their success rate.<br>
<br>
If you believe something has been overlooked, please feel free to share.<br=
>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bott=
om:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical-align:ba=
seline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blan=
k</b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;fon=
t-size:small;font-family:Arial"> | VP, Standards and New Technologies</span=
></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-siz=
e:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D"ve=
rtical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:baseli=
ne"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank">seth@valimail.c=
om</a></span></div></span><span><div><span><b>p:</b></span><span> 415.273.8=
818 </span><span></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,3=
4,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-col=
or:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><spa=
n style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;vertical-align:baseline;white-space:pre-wrap"><img src=3D"ht=
tps://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh=
0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5=
EcZV3rjz19-Dx9rESL" style=3D"border: none; height: 40px; width: 177px;"></s=
pan></p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helve=
tica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-heig=
ht:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"b=
ackground-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bot=
tom:0pt"><font color=3D"#666666" face=3D"Arial"><span style=3D"font-size:10=
.6667px;white-space:pre-wrap">This email and all data transmitted with it c=
ontains confidential and/or proprietary information intended solely for the=
 use of individual(s) authorized to receive it. If you are not an intended =
and authorized recipient you are hereby notified of any use, disclosure, co=
pying or distribution of the information included in this transmission is p=
rohibited and may be unlawful. Please immediately notify the sender by repl=
ying to this email and then delete it from your system.</span></font></p></=
span></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Sr. Technical P=
rogram Manager</span></div><span style=3D"vertical-align:baseline;white-spa=
ce:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-align:lef=
t"><span style=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"v=
ertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" target=
=3D"_blank">todd.herr@valimail.com</a></span></div></span><span><div><span>=
<b>p:</b></span><span> 703.220.4153 </span><span></span></div></span><p dir=
=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-seri=
f;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin=
-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial=
;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;whit=
e-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfm=
T2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7=
n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; =
height: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(3=
4,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-=
color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><=
br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Ar=
ial"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email an=
d all data transmitted with it contains confidential and/or proprietary inf=
ormation intended solely for the use of individual(s) authorized to receive=
 it. If you are not an intended and authorized recipient you are hereby not=
ified of any use, disclosure, copying or distribution of the information in=
cluded in this transmission is prohibited and may be unlawful. Please immed=
iately notify the sender by replying to this email and then delete it from =
your system.</span></font></p></span></div>

--000000000000af20a405b97113c6--


From nobody Thu Jan 21 20:11:52 2021
Return-Path: <emgu@google.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 9C6653A0D42 for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 20:11:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 sPbJ0i4rQHNi for <dmarc@ietfa.amsl.com>; Thu, 21 Jan 2021 20:11:49 -0800 (PST)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83DC93A0D00 for <dmarc@ietf.org>; Thu, 21 Jan 2021 20:11:49 -0800 (PST)
Received: by mail-ot1-x32d.google.com with SMTP id v1so3897772ott.10 for <dmarc@ietf.org>; Thu, 21 Jan 2021 20:11:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QH62jdaDn8GGCYJ9ryGBpfN+EDJxYwTMYZfW6MqZn1U=; b=Re7OvQR4IFW/x3Wf7pRLQxn0IJnfDgS6PvETkwL3muZzDuJR3q0x1IsunJvZ/tEFL1 kuoAho5xAyykPeL1GcRwl5vYxKrf2QlBLzrrlCW5WBeRhdygMPGhT/EU+bg5wpB4RMXC x7VmmKsXms7ic/69aT6UTk7PdPPbFzf1vHlv5ar0AXIXDqehTcg/nkEz9CXhHHaOsisa 1QCVrvuf3mnoc6CtOB7B/1ARIoIL4aMTN4Bz6iMqcvUDwv1uWMbp7EoRRjEnd3+l7y4D aeTLtWvjuPjoGfWL+G41RKF2PC8OLRcJ1s2kDHW/Pw5h+N9tBZQZnImbudJHGRtUP3n6 GcMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QH62jdaDn8GGCYJ9ryGBpfN+EDJxYwTMYZfW6MqZn1U=; b=EFJps67DYBege3UxsDtT4PIZT7/v6vHXRPJUGdb6STfbAU2Czi31t7RK+ymS16SG27 dRwKYNFAd2oMRW903N570Rm/11pmcJDaweYJ9u2ekC8pKgMffxZm/1vGltuakNeW1EJI Hzfh4Kg7feZD4/zLeo3hzSdPP84AaJUtd5mKR2kjB1AuxDJwMSL1c74wJS/XUY1upzxh CP1kh1S0l7S8Vg0LybHjRzulZ4vbTqkY+wke/cRWarZ0w6ZWAFQ1Pjh5+OOZ/GrAMZnD JAo0NfrY4tY6o564qXuPyvMO2IJxO62FBVuDDpgTw993Rcha6IsPTzD78diOt2+N9Byi lzQg==
X-Gm-Message-State: AOAM532zF5TLfc2SzZjKR00V5sTZ+lkdHXG7JJTL9nzokEXJMofKLL0k Nsi3vfyx6P7ed2pRMGSFSN2EEBGsum76bL0aJC6IkdsXmmE=
X-Google-Smtp-Source: ABdhPJyYI19VGwolcmJNeJUIe1ySiLvjSqmBhkDJWlG98mIZJIYD+Uk9Vq1EagqfnH2hMapIrLniRIWdBOsE2wAiSyU=
X-Received: by 2002:a9d:c43:: with SMTP id 61mr1982463otr.195.1611288708486; Thu, 21 Jan 2021 20:11:48 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAOZAAfMDK=oz10O+jMyG5wvYyKpVpoOCyQxQv1_kokWutffXuQ@mail.gmail.com> <CAHej_8n9crrj6xypUJeMJT+5G+8UVPhKLKScHqtcXzJTe7utLg@mail.gmail.com>
In-Reply-To: <CAHej_8n9crrj6xypUJeMJT+5G+8UVPhKLKScHqtcXzJTe7utLg@mail.gmail.com>
From: Emil Gustafsson <emgu@google.com>
Date: Thu, 21 Jan 2021 20:11:37 -0800
Message-ID: <CABZJ8knVg4TYbRzPUCjKSCMD8keHw49oeJr5DiS3UzAQGSuV7g@mail.gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Cc: Seth Blank <seth=40valimail.com@dmarc.ietf.org>, "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="00000000000021962e05b975637a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/hnV3wzo7eF255xiNh3Eli46GlHU>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 04:11:52 -0000

--00000000000021962e05b975637a
Content-Type: multipart/alternative; boundary="0000000000001a326d05b97563fa"

--0000000000001a326d05b97563fa
Content-Type: text/plain; charset="UTF-8"

I think spammers would only get two things from the DMARC reports:
1) Have they setup their configuration correctly?
2) Consume resources from the mailbox provider to generate reports.

Only if #2 is a concern for the mailbox provider I think there is a need to
filter who gets a report and who does not.

/E

On Thu, Jan 21, 2021 at 3:03 PM Todd Herr <todd.herr=
40valimail.com@dmarc.ietf.org> wrote:

> I would submit that it would be in the best interests of mailbox providers
> and others who are in the business of making acceptance and filtering
> decisions to ensure that spammers properly authenticate their email, so as
> to better and more reliably assign a poor reputation to the associated
> domains and make it easier to identify them.
>
> On Thu, Jan 21, 2021 at 4:42 PM Seth Blank <seth=
> 40valimail.com@dmarc.ietf.org> wrote:
>
>> I don't understand this concern. The data in a DMARC report speaks to the
>> underlying authentication of a message on receipt, and nothing about the
>> "spaminess" or not of a message as it's processed.
>>
>> On Thu, Jan 21, 2021 at 1:00 PM Brotman, Alex <Alex_Brotman=
>> 40comcast.com@dmarc.ietf.org> wrote:
>>
>>> Hello folks,
>>>
>>> Thought I'd see if we could come to a conclusion on this ticket.  The
>>> gist is that the reporter believes that (aggregate?) reports can help
>>> spammers to determine some effectiveness of their message attempts.
>>>
>>> Full Text:
>>> -------------
>>> Spammers could use DMARC reports to monitor the effectiveness of their
>>> campaigns, and we do not want to help them. Do existing implementations
>>> send reports to any domain that requests them, or only to those domains
>>> that are considered "acceptable"? If reports are only sent to acceptable
>>> domains, what sort of criteria have been useful?
>>>
>>> System administrators will appreciate such advice. Product developers
>>> will need guidance about the features they should provide so that a system
>>> administrator can control which domains do not receive reports.
>>> -------------
>>>
>>> >From an operator side, I don't agree with this assessment.  The reports
>>> do not show if/why a MBP may place a message in the Junk folder.  Could it
>>> be DMARC quarantine?  Sure.  It could also be any number of things from a
>>> large matrix of decisions, none of which are shown in a DMARC report.
>>> Also, the reports are typically sent once per day (seems like most ignore
>>> the 'ri'), quite likely some time after the end of the reporting period.
>>> Additionally, they probably have more efficient/immediate methods of
>>> evaluating their success rate.
>>>
>>> If you believe something has been overlooked, please feel free to share.
>>>
>>> --
>>> Alex Brotman
>>> Sr. Engineer, Anti-Abuse & Messaging Policy
>>> Comcast
>>>
>>> _______________________________________________
>>> dmarc mailing list
>>> dmarc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dmarc
>>>
>>
>>
>> --
>>
>> *Seth Blank* | VP, Standards and New Technologies
>> *e:* seth@valimail.com
>> *p:* 415.273.8818 <(415)%20273-8818>
>>
>>
>> This email and all data transmitted with it contains confidential and/or
>> proprietary information intended solely for the use of individual(s)
>> authorized to receive it. If you are not an intended and authorized
>> recipient you are hereby notified of any use, disclosure, copying or
>> distribution of the information included in this transmission is prohibited
>> and may be unlawful. Please immediately notify the sender by replying to
>> this email and then delete it from your system.
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>
>
> --
>
> *Todd Herr* | Sr. Technical Program Manager
> *e:* todd.herr@valimail.com
> *p:* 703.220.4153 <(703)%20220-4153>
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--0000000000001a326d05b97563fa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think spammers would only get two things from the DMARC =
reports:<div>1) Have they setup their configuration correctly?</div><div>2)=
 Consume resources from the mailbox provider to generate reports.</div><div=
><br></div><div>Only if #2 is a concern for the mailbox provider I think th=
ere is a need to filter who gets a report and who does not.</div><div><br><=
/div><div>/E</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Thu, Jan 21, 2021 at 3:03 PM Todd Herr &lt;todd.herr=
=3D<a href=3D"mailto:40valimail.com@dmarc.ietf.org">40valimail.com@dmarc.ie=
tf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"ltr">I would submit that it would be in the best interest=
s of mailbox providers and others who are in the business of making accepta=
nce and filtering decisions to ensure that spammers properly authenticate t=
heir email, so as to better and more reliably assign a poor reputation to t=
he associated domains and make it easier to identify them.</div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 21, 2=
021 at 4:42 PM Seth Blank &lt;seth=3D<a href=3D"mailto:40valimail.com@dmarc=
.ietf.org" target=3D"_blank">40valimail.com@dmarc.ietf.org</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">=
I don&#39;t understand this concern. The data in a DMARC report speaks to t=
he underlying authentication of a message on receipt, and nothing about the=
 &quot;spaminess&quot; or not of a message as it&#39;s processed.</div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Ja=
n 21, 2021 at 1:00 PM Brotman, Alex &lt;Alex_Brotman=3D<a href=3D"mailto:40=
comcast.com@dmarc.ietf.org" target=3D"_blank">40comcast.com@dmarc.ietf.org<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">H=
ello folks,<br>
<br>
Thought I&#39;d see if we could come to a conclusion on this ticket.=C2=A0 =
The gist is that the reporter believes that (aggregate?) reports can help s=
pammers to determine some effectiveness of their message attempts.<br>
<br>
Full Text:<br>
-------------<br>
Spammers could use DMARC reports to monitor the effectiveness of their camp=
aigns, and we do not want to help them. Do existing implementations send re=
ports to any domain that requests them, or only to those domains that are c=
onsidered &quot;acceptable&quot;? If reports are only sent to acceptable do=
mains, what sort of criteria have been useful?<br>
<br>
System administrators will appreciate such advice. Product developers will =
need guidance about the features they should provide so that a system admin=
istrator can control which domains do not receive reports.<br>
-------------<br>
<br>
&gt;From an operator side, I don&#39;t agree with this assessment.=C2=A0 Th=
e reports do not show if/why a MBP may place a message in the Junk folder.=
=C2=A0 Could it be DMARC quarantine?=C2=A0 Sure.=C2=A0 It could also be any=
 number of things from a large matrix of decisions, none of which are shown=
 in a DMARC report.=C2=A0 Also, the reports are typically sent once per day=
 (seems like most ignore the &#39;ri&#39;), quite likely some time after th=
e end of the reporting period.=C2=A0 Additionally, they probably have more =
efficient/immediate methods of evaluating their success rate.<br>
<br>
If you believe something has been overlooked, please feel free to share.<br=
>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bott=
om:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical-align:ba=
seline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blan=
k</b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;fon=
t-size:small;font-family:Arial"> | VP, Standards and New Technologies</span=
></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-siz=
e:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D"ve=
rtical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:baseli=
ne"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank">seth@valimail.c=
om</a></span></div></span><span><div><span><b>p:</b></span><span> <a href=
=3D"tel:(415)%20273-8818" value=3D"+14152738818" target=3D"_blank">415.273.=
8818</a> </span><span></span></div></span><p dir=3D"ltr" style=3D"color:rgb=
(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;backgroun=
d-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"=
><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgroun=
d-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src=
=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS=
6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8=
ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; height: 40px; width: 177px=
;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial=
,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" styl=
e=3D"background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;marg=
in-bottom:0pt"><font color=3D"#666666" face=3D"Arial"><span style=3D"font-s=
ize:10.6667px;white-space:pre-wrap">This email and all data transmitted wit=
h it contains confidential and/or proprietary information intended solely f=
or the use of individual(s) authorized to receive it. If you are not an int=
ended and authorized recipient you are hereby notified of any use, disclosu=
re, copying or distribution of the information included in this transmissio=
n is prohibited and may be unlawful. Please immediately notify the sender b=
y replying to this email and then delete it from your system.</span></font>=
</p></span></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bott=
om:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical-align:ba=
seline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr=
</b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;font=
-size:small;font-family:Arial"> | Sr. Technical Program Manager</span></div=
><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:smal=
l;font-family:Arial"><div style=3D"text-align:left"><span style=3D"vertical=
-align:baseline"><b>e:</b></span><span style=3D"vertical-align:baseline"> <=
a href=3D"mailto:todd.herr@valimail.com" target=3D"_blank">todd.herr@valima=
il.com</a></span></div></span><span><div><span><b>p:</b></span><span> <a hr=
ef=3D"tel:(703)%20220-4153" value=3D"+17032204153" target=3D"_blank">703.22=
0.4153</a> </span><span></span></div></span><p dir=3D"ltr" style=3D"color:r=
gb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;backgro=
und-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0p=
t"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgro=
und-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img sr=
c=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5Qlp=
S6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg=
8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; height: 40px; width: 177p=
x;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Aria=
l,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);li=
ne-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" sty=
le=3D"background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;mar=
gin-bottom:0pt"><font color=3D"#666666" face=3D"Arial"><span style=3D"font-=
size:10.6667px;white-space:pre-wrap">This email and all data transmitted wi=
th it contains confidential and/or proprietary information intended solely =
for the use of individual(s) authorized to receive it. If you are not an in=
tended and authorized recipient you are hereby notified of any use, disclos=
ure, copying or distribution of the information included in this transmissi=
on is prohibited and may be unlawful. Please immediately notify the sender =
by replying to this email and then delete it from your system.</span></font=
></p></span></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--0000000000001a326d05b97563fa--

--00000000000021962e05b975637a
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIPlAYJKoZIhvcNAQcCoIIPhTCCD4ECAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ggzuMIIEtjCCA56gAwIBAgIQeAMYYHb81ngUVR0WyMTzqzANBgkqhkiG9w0BAQsFADBMMSAwHgYD
VQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEGA1UE
AxMKR2xvYmFsU2lnbjAeFw0yMDA3MjgwMDAwMDBaFw0yOTAzMTgwMDAwMDBaMFQxCzAJBgNVBAYT
AkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSowKAYDVQQDEyFHbG9iYWxTaWduIEF0bGFz
IFIzIFNNSU1FIENBIDIwMjAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCvLe9xPU9W
dpiHLAvX7kFnaFZPuJLey7LYaMO8P/xSngB9IN73mVc7YiLov12Fekdtn5kL8PjmDBEvTYmWsuQS
6VBo3vdlqqXZ0M9eMkjcKqijrmDRleudEoPDzTumwQ18VB/3I+vbN039HIaRQ5x+NHGiPHVfk6Rx
c6KAbYceyeqqfuJEcq23vhTdium/Bf5hHqYUhuJwnBQ+dAUcFndUKMJrth6lHeoifkbw2bv81zxJ
I9cvIy516+oUekqiSFGfzAqByv41OrgLV4fLGCDH3yRh1tj7EtV3l2TngqtrDLUs5R+sWIItPa/4
AJXB1Q3nGNl2tNjVpcSn0uJ7aFPbAgMBAAGjggGKMIIBhjAOBgNVHQ8BAf8EBAMCAYYwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMBIGA1UdEwEB/wQIMAYBAf8CAQAwHQYDVR0OBBYEFHzM
CmjXouseLHIb0c1dlW+N+/JjMB8GA1UdIwQYMBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MHsGCCsG
AQUFBwEBBG8wbTAuBggrBgEFBQcwAYYiaHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL3Jvb3Ry
MzA7BggrBgEFBQcwAoYvaHR0cDovL3NlY3VyZS5nbG9iYWxzaWduLmNvbS9jYWNlcnQvcm9vdC1y
My5jcnQwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9yb290LXIz
LmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5n
bG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEANyYcO+9JZYyqQt41
TMwvFWAw3vLoLOQIfIn48/yea/ekOcParTb0mbhsvVSZ6sGn+txYAZb33wIb1f4wK4xQ7+RUYBfI
TuTPL7olF9hDpojC2F6Eu8nuEf1XD9qNI8zFd4kfjg4rb+AME0L81WaCL/WhP2kDCnRU4jm6TryB
CHhZqtxkIvXGPGHjwJJazJBnX5NayIce4fGuUEJ7HkuCthVZ3Rws0UyHSAXesT/0tXATND4mNr1X
El6adiSQy619ybVERnRi5aDe1PTwE+qNiotEEaeujz1a/+yYaaTY+k+qJcVxi7tbyQ0hi0UB3myM
A/z2HmGEwO8hx7hDjKmKbDCCA18wggJHoAMCAQICCwQAAAAAASFYUwiiMA0GCSqGSIb3DQEBCwUA
MEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWdu
MRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTA5MDMxODEwMDAwMFoXDTI5MDMxODEwMDAwMFowTDEg
MB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24xEzAR
BgNVBAMTCkdsb2JhbFNpZ24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDMJXaQeQZ4
Ihb1wIO2hMoonv0FdhHFrYhy/EYCQ8eyip0EXyTLLkvhYIJG4VKrDIFHcGzdZNHr9SyjD4I9DCuu
l9e2FIYQebs7E4B3jAjhSdJqYi8fXvqWaN+JJ5U4nwbXPsnLJlkNc96wyOkmDoMVxu9bi9IEYMpJ
pij2aTv2y8gokeWdimFXN6x0FNx04Druci8unPvQu7/1PQDhBjPogiuuU6Y6FnOM3UEOIDrAtKeh
6bJPkC4yYOlXy7kEkmho5TgmYHWyn3f/kRTvriBJ/K1AFUjRAjFhGV64l++td7dkmnq/X8ET75ti
+w1s4FRpFqkD2m7pg5NxdsZphYIXAgMBAAGjQjBAMA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8E
BTADAQH/MB0GA1UdDgQWBBSP8Et/qC5FJK5NUPpjmove4t0bvDANBgkqhkiG9w0BAQsFAAOCAQEA
S0DbwFCq/sgM7/eWVEVJu5YACUGssxOGhigHM8pr5nS5ugAtrqQK0/Xx8Q+Kv3NnSoPHRHt44K9u
bG8DKY4zOUXDjuS5V2yq/BKW7FPGLeQkbLmUY/vcU2hnVj6DuM81IcPJaP7O2sJTqsyQiunwXUaM
ld16WCgaLx3ezQA3QY/tRG3XUyiXfvNnBB4V14qWtNPeTCekTBtzc3b0F5nCH3oO4y0IrQocLP88
q1UOD5F+NuvDV0m+4S4tfGCLw0FREyOdzvcya5QBqJnnLDMfOjsl0oZAzjsshnjJYS8Uuu7bVW/f
hO4FCU29KNhyztNiUGUe65KXgzHZs7XKR1g/XzCCBM0wggO1oAMCAQICEAGNZbQJqBdAMtoTq8Du
WfEwDQYJKoZIhvcNAQELBQAwVDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYt
c2ExKjAoBgNVBAMTIUdsb2JhbFNpZ24gQXRsYXMgUjMgU01JTUUgQ0EgMjAyMDAeFw0yMDA5MDgy
MzM5MzBaFw0yMTAzMDcyMzM5MzBaMCAxHjAcBgkqhkiG9w0BCQEWD2VtZ3VAZ29vZ2xlLmNvbTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOdltLLFkDZcnb4L/2kIWbg7aaipTwuyhHkV
r/fuG6W0W6tdDF1vUAG6RDO1eMG6ePrZMjGzB9Pu7kzZGN+glhn6k6a/Ef8uFKmOFH2XwJewg4VE
QFAdSoq9cpbWds2cNIn0OKj+VNyqlahB2+WzlarkxSePUqp3kQrplF4wsgEf1GwBw19OA2dScLBE
kGaSdZN1jxVQQ3/3ReVFuTg7b5CYDrpVgkzPpGqMCsK5aVTrAbrKV/EfT3IZix0OUXH3VzRO34q8
CHqUaX1EQ9wB5n/sHAgOzhvKrVmUN6UtEa+yMKBLFnwCUqik0GOKhIpzocxiLz/7rfDOt4gImc1D
6JcCAwEAAaOCAc0wggHJMBoGA1UdEQQTMBGBD2VtZ3VAZ29vZ2xlLmNvbTAOBgNVHQ8BAf8EBAMC
BaAwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMB0GA1UdDgQWBBQmzfIaY6uE4rvRwKBy
PY89Q+o//DBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3
dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMIGaBggrBgEFBQcBAQSBjTCB
ijA+BggrBgEFBQcwAYYyaHR0cDovL29jc3AuZ2xvYmFsc2lnbi5jb20vY2EvZ3NhdGxhc3Izc21p
bWVjYTIwMjAwSAYIKwYBBQUHMAKGPGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0
L2dzYXRsYXNyM3NtaW1lY2EyMDIwLmNydDAfBgNVHSMEGDAWgBR8zApo16LrHixyG9HNXZVvjfvy
YzBGBgNVHR8EPzA9MDugOaA3hjVodHRwOi8vY3JsLmdsb2JhbHNpZ24uY29tL2NhL2dzYXRsYXNy
M3NtaW1lY2EyMDIwLmNybDANBgkqhkiG9w0BAQsFAAOCAQEADr/e4M1+D/oNeKTsHqGHJsCiJ294
gqHJxZMx/LZcBXqrvI26AFr+qwal/GD0M1LJYzZI4XO5Bt2S06+yDd58jEARFo487jZzvrKuVakW
S55g9vER08AkFsV2sMG5DRewCaQYQPc5uJce1IOX+PdGZlDdJImxenpfdKRqTfJC5hoeeY1JSSlV
/91lFpQ3g5z1MLCwbF7O17pApsSOqJk6kfMDpKiub29C2egC+Z3Rl2skPAkrJa/pZqrViuB7QDhM
9rlr7OOWXRtQYR+lES69+oB5sf15gxDeW7idWNOjFKLfHrW2+kZyg3B/aIKiOhbJG8gbuXBEFh7t
yOXQWmR0CDGCAmowggJmAgEBMGgwVDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExKjAoBgNVBAMTIUdsb2JhbFNpZ24gQXRsYXMgUjMgU01JTUUgQ0EgMjAyMAIQAY1ltAmo
F0Ay2hOrwO5Z8TANBglghkgBZQMEAgEFAKCB1DAvBgkqhkiG9w0BCQQxIgQgGNGFp+8+UaW6dhWR
aztlJ1dm5+4tiZ05n5PqqZlW7F4wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B
CQUxDxcNMjEwMTIyMDQxMTQ5WjBpBgkqhkiG9w0BCQ8xXDBaMAsGCWCGSAFlAwQBKjALBglghkgB
ZQMEARYwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMAsGCSqGSIb3DQEBCjALBgkqhkiG9w0BAQcw
CwYJYIZIAWUDBAIBMA0GCSqGSIb3DQEBAQUABIIBALHUjq9aRdWZ5i1/dV8WGllA1dopvtf1zHeP
HzmNs6ZtXqukfjrnEwFYG1cvPiA9gTnzSRAJ0FNAMF5VZB7B5aqsPLxSD0MmXvXsg1/IRpUnJhju
huO5Va+xuESr3jIu5O/DSLBlngqRBYrb/jEJqIOsfWKKav40buloY4THjnE39CXJgw649iswJypx
w5+55TsUBPqy/g5PtgS/tT3R3TAEOfmXF+/8ZsfkzVNb9zdiIN1kcB4PD756vv++hN81jUQ63Syx
J/ZX9cyr+eXJzkk0Gc8F+jrZhgiQJhOyXS+Qbmle9BSv7jRUdorsv5NNjNGBULtetltqpbWGdXn/
21A=
--00000000000021962e05b975637a--


From nobody Fri Jan 22 04:00:46 2021
Return-Path: <dougfoster.emailstandards@gmail.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 3B28D3A114D for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 04:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Speg0zl3YOPm for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 04:00:42 -0800 (PST)
Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3197C3A1145 for <dmarc@ietf.org>; Fri, 22 Jan 2021 04:00:42 -0800 (PST)
Received: by mail-ua1-x932.google.com with SMTP id t15so1735355ual.6 for <dmarc@ietf.org>; Fri, 22 Jan 2021 04:00:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eURGtIiO83gutt9qswPTlQmVXGhmk1+cIhkIsSGqHQk=; b=OR5/8bts7i9YA9fibktm57IWx3fgxtJDpGB+/GvcP4K7v6DHrpWRm6ybt/rSLuNPtH sFFpNQATF16d3uHlOAAmURgAXf4GfFcI23xdgBtVYXyUihGcT/FG6Zl0Z/B6OTYMK5A8 y/aOjqfS73MA2BIRD3nBKAoOumGPTws4gNdoHUXFU+d8+gxQKQZJfTfjTsBgq8xSwyE9 ReOPlgESkQvisqv9ggt0/baPG+s3IAGdwCC6Egaw6zr7DTA1OUaVpEQDTJnqcEVF+l5+ 7hzCI/tXRPDpWzCu/vLN+yFNSNSNr8tBOJ9mQtouRuwb497b6s5+HadcEN+ajIlecUXW fLzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eURGtIiO83gutt9qswPTlQmVXGhmk1+cIhkIsSGqHQk=; b=Fq2n5lXiboRanOfMziZNC+bOc4k/yhx+jZrkWF0ZsmhW5ewjNud16S5uuEPWdM2FfW 62+ywm6fvqSrEy7mP7rY+HlPIRRxccYRDH2wpuqMBZbCK0qxX018mw0d27uqchdTnvdv 5Zqb2P8B8uSJ3Exva2ccCkDX1cyTX5Ne7DvNPRBj8jSBhyuKWDSa6yVaHl+uByXk/OJp nI1j+vlOOmfcWZASzCLsd5TDR4IQTDa1iGlxnTyxPoPZ5TBNSLH+jDdrMlciduAgx60l xUcqL3ewHEa9+ruyEZmyCFS4x5nLcqYpW6K9XeH5RjvtsnAKW7pGMGTSpIPtVzuT4BvY tRMQ==
X-Gm-Message-State: AOAM53206MhVbv2iaLvLkED4Zd9fZBfSMmlKX3lqRZbNn+5uG0Vn+byu VI9aRm7etdWAmyCTQOQXAa2TpctF/qrpAGl4SjRVZFzeVmM=
X-Google-Smtp-Source: ABdhPJwbzLWHRrFnoaVQYE80iReAOW/gz3qb61cn0SqTK0mFCuNzP4nOu1RS+0XHdPjOzvIYZuwnNZQWBTks4qjB3O4=
X-Received: by 2002:ab0:5e6:: with SMTP id e93mr96418uae.109.1611316841001; Fri, 22 Jan 2021 04:00:41 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Fri, 22 Jan 2021 07:00:30 -0500
Message-ID: <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com>
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000edb96e05b97bef06"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rSXEifCWd3yYn96WDchlsloddfY>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 12:00:44 -0000

--000000000000edb96e05b97bef06
Content-Type: text/plain; charset="UTF-8"

My specific concern is with disposition information.    Whether the message
presents with acceptable credentials is the sender's responsibility, and I
have no problem with documenting whether it passed SPF or DKIM or both,
including which DKIM scope was used for the evaluation.     I have no
problem with reporting the sender policy that I retrieved from DNS.

But should I report the disposition applied, and the reason that my
disposition was different from the sender policy?    That seems like
information leakage about my defenses which should only be revealed to
highly trusted correspondent domains.

Consider what is likely to happen If I call an organization's help desk and
say,
     "My emails to Sally are not getting delivered, and I want to know why?"
The answer should be, and usually is,
     "Have Sally open a ticket and we will discuss the problem with her!"
Should not the same policy apply here?

Possible misuse of disposition information:
- DMARC=(Fail), Disposition = (120 delivered) -- probably means that my
system does not enforce DMARC at all
- DMARC=(Pass), Disposition = (20 delivered, 100 rejected)  -- possibly
means that my system needs 20 messages to learn how to identify bad content

I suggest that disposition information should be redacted by default, and
only included on an exception basis for highly trusted source domains.

Doug Foster

On Thu, Jan 21, 2021 at 4:00 PM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Hello folks,
>
> Thought I'd see if we could come to a conclusion on this ticket.  The gist
> is that the reporter believes that (aggregate?) reports can help spammers
> to determine some effectiveness of their message attempts.
>
> Full Text:
> -------------
> Spammers could use DMARC reports to monitor the effectiveness of their
> campaigns, and we do not want to help them. Do existing implementations
> send reports to any domain that requests them, or only to those domains
> that are considered "acceptable"? If reports are only sent to acceptable
> domains, what sort of criteria have been useful?
>
> System administrators will appreciate such advice. Product developers will
> need guidance about the features they should provide so that a system
> administrator can control which domains do not receive reports.
> -------------
>
> >From an operator side, I don't agree with this assessment.  The reports
> do not show if/why a MBP may place a message in the Junk folder.  Could it
> be DMARC quarantine?  Sure.  It could also be any number of things from a
> large matrix of decisions, none of which are shown in a DMARC report.
> Also, the reports are typically sent once per day (seems like most ignore
> the 'ri'), quite likely some time after the end of the reporting period.
> Additionally, they probably have more efficient/immediate methods of
> evaluating their success rate.
>
> If you believe something has been overlooked, please feel free to share.
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000edb96e05b97bef06
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">My specific concern is with disposition information.=C2=A0=
 =C2=A0 Whether the message presents with acceptable credentials is the sen=
der&#39;s responsibility, and I have no problem with documenting whether it=
 passed SPF or DKIM or both, including which DKIM scope was used for the ev=
aluation.=C2=A0 =C2=A0 =C2=A0I have no problem with reporting the sender=C2=
=A0policy that I retrieved from DNS.<div><br></div><div>But should I report=
 the disposition applied, and the reason that my disposition was different =
from the sender policy?=C2=A0 =C2=A0 That seems like information leakage ab=
out my defenses which should only be revealed to highly trusted corresponde=
nt domains.</div><div><br></div><div>Consider what is likely to happen If I=
 call an organization&#39;s help desk and say,=C2=A0</div><div>=C2=A0 =C2=
=A0 =C2=A0&quot;My emails to Sally are not getting delivered, and I want to=
 know why?&quot;</div><div>The answer should be, and usually is,=C2=A0</div=
><div>=C2=A0 =C2=A0 =C2=A0&quot;Have Sally open a ticket and we will discus=
s the problem with her!&quot;</div><div><div>Should not the same policy app=
ly here?=C2=A0 =C2=A0 =C2=A0</div><div></div></div><div><br></div><div>Poss=
ible misuse of disposition information:</div><div>- DMARC=3D(Fail), Disposi=
tion =3D (120 delivered) -- probably means that my system does not enforce =
DMARC at all</div><div>- DMARC=3D(Pass), Disposition =3D (20 delivered, 100=
 rejected)=C2=A0 -- possibly means that my system needs 20 messages to lear=
n how to identify bad content</div><div><br></div><div>I suggest that dispo=
sition information should be redacted by default, and only included on an e=
xception basis for highly trusted source domains.</div><div><br></div><div>=
Doug Foster</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Thu, Jan 21, 2021 at 4:00 PM Brotman, Alex &lt;Alex_Bro=
tman=3D<a href=3D"mailto:40comcast.com@dmarc.ietf.org" target=3D"_blank">40=
comcast.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">Hello folks,<br>
<br>
Thought I&#39;d see if we could come to a conclusion on this ticket.=C2=A0 =
The gist is that the reporter believes that (aggregate?) reports can help s=
pammers to determine some effectiveness of their message attempts.<br>
<br>
Full Text:<br>
-------------<br>
Spammers could use DMARC reports to monitor the effectiveness of their camp=
aigns, and we do not want to help them. Do existing implementations send re=
ports to any domain that requests them, or only to those domains that are c=
onsidered &quot;acceptable&quot;? If reports are only sent to acceptable do=
mains, what sort of criteria have been useful?<br>
<br>
System administrators will appreciate such advice. Product developers will =
need guidance about the features they should provide so that a system admin=
istrator can control which domains do not receive reports.<br>
-------------<br>
<br>
&gt;From an operator side, I don&#39;t agree with this assessment.=C2=A0 Th=
e reports do not show if/why a MBP may place a message in the Junk folder.=
=C2=A0 Could it be DMARC quarantine?=C2=A0 Sure.=C2=A0 It could also be any=
 number of things from a large matrix of decisions, none of which are shown=
 in a DMARC report.=C2=A0 Also, the reports are typically sent once per day=
 (seems like most ignore the &#39;ri&#39;), quite likely some time after th=
e end of the reporting period.=C2=A0 Additionally, they probably have more =
efficient/immediate methods of evaluating their success rate.<br>
<br>
If you believe something has been overlooked, please feel free to share.<br=
>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000edb96e05b97bef06--


From nobody Fri Jan 22 05:15:57 2021
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 7161D3A1201 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 05:15:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 U7AnR4q-RWFT for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 05:15:53 -0800 (PST)
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 83DB13A11F9 for <dmarc@ietf.org>; Fri, 22 Jan 2021 05:15:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611321349; bh=HhnzYIKR+eEIwOW+D0r1jnParHXv2zIeZOceKxuMgfM=; l=1831; h=To:References:From:Date:In-Reply-To; b=BMKTXJubIoU5rLa7ao2THuaWuPZmumOLCVXb3+JZwUmchxTHMlmD8p2V5wsmAozTQ PLq6Ec5OVpJr36h6PrYS2O0VcFRbyaam5F0pyhmVbbb6hQ7cEixVo7dlWBQ6IgnUZb UjNl7+Fi1NNQhkfu/dzVLNwvlfMBC/KMzcuWA+Bg4Ur0SewTYbjH0DgkUsboU
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0CE.00000000600AD005.00006709; Fri, 22 Jan 2021 14:15:49 +0100
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>, "dmarc@ietf.org" <dmarc@ietf.org>
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <51e4528e-6517-869d-40ae-b987362cb9ea@tana.it>
Date: Fri, 22 Jan 2021 14:15:48 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/HRAR3hSdckw3mU_Gebh8vcYOjm4>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 13:15:56 -0000

On Fri 22/Jan/2021 13:00:30 +0100 Douglas Foster wrote:
> 
> Possible misuse of disposition information:
> - DMARC=(Fail), Disposition = (120 delivered) -- probably means that my system 
> does not enforce DMARC at all
> - DMARC=(Pass), Disposition = (20 delivered, 100 rejected)  -- possibly means 
> that my system needs 20 messages to learn how to identify bad content
> 
> I suggest that disposition information should be redacted by default, and only 
> included on an exception basis for highly trusted source domains.


There is a paragraraph in RFC 7489 that I cannot find in the draft:

    Aggregate reports are limited in scope to DMARC policy and
    disposition results, to information pertaining to the underlying
    authentication mechanisms, and to the identifiers involved in DMARC
    validation.

Can that be clarified better?  Se spec sometimes uses the term "final 
disposition" to mean what Doug calls "disposition information" in the text 
quoted above.

To wit, a DMARC filter acting between DATA and end-of-data doesn't actually 
know about final disposition.  It can reject, but cannot deliver to Inbox.

In fact, the <disposition> field refers to what the filter is configured to do, 
except that quarantine can only be signaled to downstream processes.  It 
reports "quarantine" if it did that signaling.  It reports "reject" if it 
rejects.  Otherwise reports "none".  (Did we conclude we want "pass"?)

Identifying bad content, possibly based on DMARC having identified a bad actor, 
or after actual content inspection, happens downstream.  A DMARC filter doesn't 
know and doesn't want to know the final outcome, and doesn't report it.

It is important to be very clear on this point, to avoid that receivers fail to 
enable aggregate reporting for fear of helping spammers.


Best
Ale
-- 





















From nobody Fri Jan 22 05:40:32 2021
Return-Path: <todd.herr@valimail.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 06D953A12B0 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 05:40:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 GgMAE3c4N3PZ for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 05:40:28 -0800 (PST)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A23993A12AF for <dmarc@ietf.org>; Fri, 22 Jan 2021 05:40:28 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id o18so4039362qtp.10 for <dmarc@ietf.org>; Fri, 22 Jan 2021 05:40:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=b+QI96/jUrAviaaICsa0QYhYQDQmyjwMTjrv7oU4/5o=; b=bFpTUHINySgHq4jVKkI9SHtJVkcqly//Dtrf2FHQysr9JPKuCZC2f16GTomOM82izi eBxxPMtrlSsOWBNfFWLcgB1OPwsdU8oMbg8wc5A549oWjNYMgflb8BESpbJK/j/rPGlx v5uMg/6wtSpVRyVCrfQLpmvYCtcCKReaPkICMDUJE3+s/QEWfr27KIWJQUk1xxqVjpYO yW2ye5LS/10HN+HrpEQzidxMUzkiLidhzeLW45+GmbQ0aqQjfQ6Lm7DlJ/rRQkL2N4BA uD3KEbwn6/CaEiViyeIPA7IV4wsIkLdDgU6OT2Twh1IM6chY7DGhAO+5nQgFTkyUH7cp C5Ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=b+QI96/jUrAviaaICsa0QYhYQDQmyjwMTjrv7oU4/5o=; b=VuoS7FniqU7zpC0073bPT1L3zTGW+pLJO82R/HaE0vQPfnuzGTQFUAkJ4tWyKN1cfm ZA9JTzZZUt5QTwlaXtUxW9jDOD0BtSuOV0fdJZvNE9hfunusHg9co9HZlri+lZgXL7gB iV+ZOTFfIxaALxWn9nuF6vMmMXFAH2y10gasKjHXL1k72nVP/75xEtFuDD+/ESv4+WOq EQLPFTNE6YhR3T+vu+onyHmTffsq74LBPsfP1js/SibFKtFdmo0yDn037hBL6DQfMEeC jnDkPzWDCphbg6p4oWe7ESzNiGQRBq32KkcRj+RT2aclvrPDl0GAj77BT31d9ONfl7v2 Idkw==
X-Gm-Message-State: AOAM532nnGD7Ah/oJ7HV7jeA5ib4/oiG/lqgUv0UGZGLpEplhW9TAR5P qlcptrphjsUBLBusvb4xrpmPUOqGnL1dWog7cMs43N10zfg=
X-Google-Smtp-Source: ABdhPJwwYJYltZJ3wBf2s1yzkonBrMuKw9Dq2+RCbsqbRS5+AiMMUl4YOLqW4gpqrUlAYYf2xu2mitNsoDxGX97ycos=
X-Received: by 2002:ac8:6b4b:: with SMTP id x11mr4263072qts.220.1611322827288;  Fri, 22 Jan 2021 05:40:27 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com>
In-Reply-To: <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Fri, 22 Jan 2021 08:40:11 -0500
Message-ID: <CAHej_8nJ60G+OHa=5OHXABHzG4wNSNhJ3mvME6Rk=U4z_GbyjA@mail.gmail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bd4b7105b97d547c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/XMPB4py-jwiTSm2pjGhpn01Lcf4>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 13:40:31 -0000

--000000000000bd4b7105b97d547c
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 7:00 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> My specific concern is with disposition information.    Whether the
> message presents with acceptable credentials is the sender's
> responsibility, and I have no problem with documenting whether it passed
> SPF or DKIM or both, including which DKIM scope was used for the
> evaluation.     I have no problem with reporting the sender policy that I
> retrieved from DNS.
>
> But should I report the disposition applied, and the reason that my
> disposition was different from the sender policy?    That seems like
> information leakage about my defenses which should only be revealed to
> highly trusted correspondent domains.
>
> Consider what is likely to happen If I call an organization's help desk
> and say,
>      "My emails to Sally are not getting delivered, and I want to know
> why?"
> The answer should be, and usually is,
>      "Have Sally open a ticket and we will discuss the problem with her!"
> Should not the same policy apply here?
>



>
> Possible misuse of disposition information:
> - DMARC=(Fail), Disposition = (120 delivered) -- probably means that my
> system does not enforce DMARC at all
> - DMARC=(Pass), Disposition = (20 delivered, 100 rejected)  -- possibly
> means that my system needs 20 messages to learn how to identify bad content
>
> I suggest that disposition information should be redacted by default, and
> only included on an exception basis for highly trusted source domains.
>
>
You're using the phrase "disposition was different from the sender policy"
in a way that I don't understand.

Sender policy is a request for handling when a message fails DMARC
validation checks. In your examples of possible misuse of disposition
information, one you're citing is 100 rejected messages when DMARC passes;
that's not a disposition that's different from sender policy, because DMARC
pass is no guarantee of a message being accepted, and again, sender policy
only concerns the state of DMARC failing validation checks. The DMARC
policy statement isn't a vehicle for requesting handling when the message
passes DMARC checks. Beyond that, I'm not even sure that a condition exists
where a message would have a disposition of "rejected due to DMARC" when
the DMARC validation result is pass, but I've been accused in the past of
lacking imagination, so perhaps it could happen.

For your example of DMARC failing and all 120 messages being delivered,
I've never personally met a spammer (every conversation I ever had started
with "I'm not a spammer")  but I can't conceive of a spammer configuring
his domain with a DMARC policy of p=reject and sending mail that doesn't
authenticate as a way of probing things, but I suppose it could happen.
Because aggregate reports only come in once every 24 hours from most
places, he's not going to get immediate gratification like he would simply
by having a few test or seed accounts at the target domain, but maybe he's
patient. Of course, DMARC isn't the sole arbiter of whether or not the
message made it to the Inbox and not the Junk or Spam folder, so results
would be inconclusive at best. His test accounts will tell him much more
than DMARC reports will tell him.

I can't speak for any mailbox providers, but I suspect that the work of
updating their reporting tools to handle an exception list and curating
such a list is more expensive to them than whatever risk might exist in
generating a DMARC aggregate report for a few spam sending domains. Maybe a
note in Security Considerations or something? *shrug*


-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000bd4b7105b97d547c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 7:00 AM Douglas F=
oster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfoster=
.emailstandards@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">My spe=
cific concern is with disposition information.=C2=A0 =C2=A0 Whether the mes=
sage presents with acceptable credentials is the sender&#39;s responsibilit=
y, and I have no problem with documenting whether it passed SPF or DKIM or =
both, including which DKIM scope was used for the evaluation.=C2=A0 =C2=A0 =
=C2=A0I have no problem with reporting the sender=C2=A0policy that I retrie=
ved from DNS.<div><br></div><div>But should I report the disposition applie=
d, and the reason that my disposition was different from the sender policy?=
=C2=A0 =C2=A0 That seems like information leakage about my defenses which s=
hould only be revealed to highly trusted correspondent domains.</div><div><=
br></div><div>Consider what is likely to happen If I call an organization&#=
39;s help desk and say,=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0&quot;My emails=
 to Sally are not getting delivered, and I want to know why?&quot;</div><di=
v>The answer should be, and usually is,=C2=A0</div><div>=C2=A0 =C2=A0 =C2=
=A0&quot;Have Sally open a ticket and we will discuss the problem with her!=
&quot;</div><div><div>Should not the same policy apply here?=C2=A0 =C2=A0 =
=C2=A0</div></div></div></blockquote><div><br></div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><div></di=
v></div><div><br></div><div>Possible misuse of disposition information:</di=
v><div>- DMARC=3D(Fail), Disposition =3D (120 delivered) -- probably means =
that my system does not enforce DMARC at all</div><div>- DMARC=3D(Pass), Di=
sposition =3D (20 delivered, 100 rejected)=C2=A0 -- possibly means that my =
system needs 20 messages to learn how to identify bad content</div><div><br=
></div><div>I suggest that disposition information should be redacted by de=
fault, and only included on an exception basis for highly trusted source do=
mains.</div><div><br></div></div></blockquote><div><br></div><div>You&#39;r=
e using the phrase &quot;disposition was different from the sender policy&q=
uot; in a way that I don&#39;t understand.</div><div><br></div><div>Sender =
policy is a request for handling when a message fails DMARC validation chec=
ks. In your examples of possible misuse of disposition information, one you=
&#39;re citing is 100 rejected messages when DMARC passes; that&#39;s not a=
 disposition that&#39;s different from sender policy, because DMARC pass is=
 no guarantee of a message being accepted, and again, sender policy only co=
ncerns the state of DMARC failing validation checks. The DMARC policy state=
ment isn&#39;t a vehicle for requesting handling when the message passes DM=
ARC checks. Beyond that, I&#39;m not even sure that a condition exists wher=
e a message would have a disposition of &quot;rejected due to DMARC&quot; w=
hen the DMARC validation result is pass, but I&#39;ve been accused in the p=
ast of lacking imagination, so perhaps it could happen.</div><div><br></div=
><div>For your example of DMARC failing and all 120 messages being delivere=
d, I&#39;ve never personally met a spammer (every conversation I ever had s=
tarted with &quot;I&#39;m not a spammer&quot;)=C2=A0 but I can&#39;t concei=
ve of a spammer configuring his domain with a DMARC policy of p=3Dreject an=
d sending mail that doesn&#39;t authenticate as a way of probing things, bu=
t I suppose it could happen. Because aggregate reports only come in once ev=
ery 24 hours from most places, he&#39;s not going to get immediate gratific=
ation like he would simply by having a few test or seed accounts at the tar=
get domain, but maybe he&#39;s patient. Of course, DMARC isn&#39;t the sole=
 arbiter of whether or not the message made it to the Inbox and not the Jun=
k or Spam folder, so results would be inconclusive at best. His test accoun=
ts will tell him much more than DMARC reports will tell him.</div><div><br>=
</div><div>I can&#39;t speak for any mailbox providers, but I suspect that =
the work of updating their reporting tools to handle an exception list and =
curating such a list is more expensive to them than whatever risk might exi=
st in generating a DMARC aggregate report for a few spam sending domains. M=
aybe a note in Security Considerations or something? *shrug*</div></div><br=
 clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr" class=3D"gmail_signat=
ure"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-=
bottom:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical-alig=
n:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd =
Herr</b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;=
font-size:small;font-family:Arial"> | Sr. Technical Program Manager</span><=
/div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:=
small;font-family:Arial"><div style=3D"text-align:left"><span style=3D"vert=
ical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:baseline=
"> <a href=3D"mailto:todd.herr@valimail.com" target=3D"_blank">todd.herr@va=
limail.com</a></span></div></span><span><div><span><b>p:</b></span><span> 7=
03.220.4153 </span><span></span></div></span><p dir=3D"ltr" style=3D"color:=
rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;backgr=
ound-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgr=
ound-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img s=
rc=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5Ql=
pS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQans=
g8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; height: 40px; width: 177=
px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Ari=
al,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);l=
ine-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" st=
yle=3D"background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;ma=
rgin-bottom:0pt"><font color=3D"#666666" face=3D"Arial"><span style=3D"font=
-size:10.6667px;white-space:pre-wrap">This email and all data transmitted w=
ith it contains confidential and/or proprietary information intended solely=
 for the use of individual(s) authorized to receive it. If you are not an i=
ntended and authorized recipient you are hereby notified of any use, disclo=
sure, copying or distribution of the information included in this transmiss=
ion is prohibited and may be unlawful. Please immediately notify the sender=
 by replying to this email and then delete it from your system.</span></fon=
t></p></span></div></div>

--000000000000bd4b7105b97d547c--


From nobody Fri Jan 22 06:02:53 2021
Return-Path: <dougfoster.emailstandards@gmail.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 45EE03A0C9C for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 06:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 QnQF9fGF5yRK for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 06:02:49 -0800 (PST)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E01D13A0C47 for <dmarc@ietf.org>; Fri, 22 Jan 2021 06:02:48 -0800 (PST)
Received: by mail-vs1-xe2c.google.com with SMTP id o186so3052792vso.1 for <dmarc@ietf.org>; Fri, 22 Jan 2021 06:02:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2VQ57Q+peRBSDsExcQurgF7t7N0pxrAVpgOM0+wqN2Y=; b=JosS4NkQluyweREdNUO4zMUH24OOGc9yPMs2mY1K/qCdrWDHiTmEGaAV8U/lHJ3wsB tPHk89YMUEdQcaz1lpzXFGZ0/LbOw/sxU7cEwRX6IR4jT1fSEOPcnghCbwfEvkklPHuq NDeFsvXnIcaeLFXGqJyCHOkR8uJfkIVZTkqDL/xfkSWtvRFfRKWCyQBxrpKpz5khD5Bb b2rGSyy7jwiWO6+EBOnrB/dQ554RlzUXJDWRDanyN224DpB+DaU1GWvgYwoMz1ZTXq/K e9WuO3oGuoiZNeLOrAQlDeUbjl/WghOGSWD2nIbqK2UhCjnWOQHGwnd1+d5GipbW5Vgg czAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2VQ57Q+peRBSDsExcQurgF7t7N0pxrAVpgOM0+wqN2Y=; b=e171gAO1FwV3UqAjMzLLL2coJZDZ10HaPtXHK94zlCi5W11gGurqzmf2vd7Ycrs9FJ z9t0Mi9jwxb4isIlZEkEGceMwwOrm3tG2LGlbPl+bCzxxzdwvFnPfPgpWvqv+wNhHkP8 EKgMQ+gW+ZFazI4y712LrFFjYge5flXouddazPv6NF3FgjTEHxWSx/6uw4zcJOjNvIV5 Jv9bPh4U8mALUtTJSO2PV6y/4GY9aha6zNKa8ztoZt1ev+d2puE9d7HV5EON1dDxpNNE ab7hIlOHYSRQaj7KapqCv7P0Ba+qqgPns1IL7UgdXfg4HwOAypfvpItx+ECBmfot4gaL z6GQ==
X-Gm-Message-State: AOAM531M74ZyETS/WaGVRxlD3eH6n8sHX3mJ2RPnsnCHWLPtihwjtBFd lFrsq68fItq1WULx2jpllp8fiqhngbUkxsC/Ub4=
X-Google-Smtp-Source: ABdhPJwQvDRYzAjMcwx0iBCoa5OqUNLkLQV4Rm6zB9BHfJ6AIn70LyiK3AtG5lzigQ5Y++HfnOT6wMd6eUVjmAOtRNE=
X-Received: by 2002:a67:507:: with SMTP id 7mr761023vsf.42.1611324167688; Fri, 22 Jan 2021 06:02:47 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com> <CAHej_8nJ60G+OHa=5OHXABHzG4wNSNhJ3mvME6Rk=U4z_GbyjA@mail.gmail.com>
In-Reply-To: <CAHej_8nJ60G+OHa=5OHXABHzG4wNSNhJ3mvME6Rk=U4z_GbyjA@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Fri, 22 Jan 2021 09:02:35 -0500
Message-ID: <CAH48ZfxMs+M48-C0MEPBRY1fBDiuOQrnQ_BFtXbc=G+0bCJasg@mail.gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a2170305b97da455"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3vZiBtv_FouJsWVYFAvqUVY-pmc>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 14:02:51 -0000

--000000000000a2170305b97da455
Content-Type: text/plain; charset="UTF-8"

Not sure what is unclear about my concern.

The spec provides for reporting whether the actual disposition was
different from the sender policy request, and the reason that this was done.

Ale suggests that "disposition" must be narrowly defined to mean only the
disposition based on DMARC staus.  This still means that local policy is
revealed under some circumstances.

I do not see why local policy should be revealed at all.

On Fri, Jan 22, 2021, 8:41 AM Todd Herr <todd.herr=
40valimail.com@dmarc.ietf.org> wrote:

> On Fri, Jan 22, 2021 at 7:00 AM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> My specific concern is with disposition information.    Whether the
>> message presents with acceptable credentials is the sender's
>> responsibility, and I have no problem with documenting whether it passed
>> SPF or DKIM or both, including which DKIM scope was used for the
>> evaluation.     I have no problem with reporting the sender policy that I
>> retrieved from DNS.
>>
>> But should I report the disposition applied, and the reason that my
>> disposition was different from the sender policy?    That seems like
>> information leakage about my defenses which should only be revealed to
>> highly trusted correspondent domains.
>>
>> Consider what is likely to happen If I call an organization's help desk
>> and say,
>>      "My emails to Sally are not getting delivered, and I want to know
>> why?"
>> The answer should be, and usually is,
>>      "Have Sally open a ticket and we will discuss the problem with her!"
>> Should not the same policy apply here?
>>
>
>
>
>>
>> Possible misuse of disposition information:
>> - DMARC=(Fail), Disposition = (120 delivered) -- probably means that my
>> system does not enforce DMARC at all
>> - DMARC=(Pass), Disposition = (20 delivered, 100 rejected)  -- possibly
>> means that my system needs 20 messages to learn how to identify bad content
>>
>> I suggest that disposition information should be redacted by default, and
>> only included on an exception basis for highly trusted source domains.
>>
>>
> You're using the phrase "disposition was different from the sender policy"
> in a way that I don't understand.
>
> Sender policy is a request for handling when a message fails DMARC
> validation checks. In your examples of possible misuse of disposition
> information, one you're citing is 100 rejected messages when DMARC passes;
> that's not a disposition that's different from sender policy, because DMARC
> pass is no guarantee of a message being accepted, and again, sender policy
> only concerns the state of DMARC failing validation checks. The DMARC
> policy statement isn't a vehicle for requesting handling when the message
> passes DMARC checks. Beyond that, I'm not even sure that a condition exists
> where a message would have a disposition of "rejected due to DMARC" when
> the DMARC validation result is pass, but I've been accused in the past of
> lacking imagination, so perhaps it could happen.
>
> For your example of DMARC failing and all 120 messages being delivered,
> I've never personally met a spammer (every conversation I ever had started
> with "I'm not a spammer")  but I can't conceive of a spammer configuring
> his domain with a DMARC policy of p=reject and sending mail that doesn't
> authenticate as a way of probing things, but I suppose it could happen.
> Because aggregate reports only come in once every 24 hours from most
> places, he's not going to get immediate gratification like he would simply
> by having a few test or seed accounts at the target domain, but maybe he's
> patient. Of course, DMARC isn't the sole arbiter of whether or not the
> message made it to the Inbox and not the Junk or Spam folder, so results
> would be inconclusive at best. His test accounts will tell him much more
> than DMARC reports will tell him.
>
> I can't speak for any mailbox providers, but I suspect that the work of
> updating their reporting tools to handle an exception list and curating
> such a list is more expensive to them than whatever risk might exist in
> generating a DMARC aggregate report for a few spam sending domains. Maybe a
> note in Security Considerations or something? *shrug*
>
>
> --
>
> *Todd Herr* | Sr. Technical Program Manager
> *e:* todd.herr@valimail.com
> *p:* 703.220.4153
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000a2170305b97da455
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Not sure what is unclear about my concern.<div dir=3D"aut=
o"><br></div><div dir=3D"auto">The spec provides for reporting whether the =
actual disposition was different from the sender policy request, and the re=
ason that this was done.</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>Ale suggests that &quot;disposition&quot; must be narrowly defined to mean=
 only the disposition based on DMARC staus.=C2=A0 This still means that loc=
al policy is revealed under some circumstances.=C2=A0=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">I do not see why local policy should =
be revealed at all.</div></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Fri, Jan 22, 2021, 8:41 AM Todd Herr &lt;todd.h=
err=3D<a href=3D"mailto:40valimail.com@dmarc.ietf.org">40valimail.com@dmarc=
.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 7:00 AM Douglas Foster &l=
t;<a href=3D"mailto:dougfoster.emailstandards@gmail.com" target=3D"_blank" =
rel=3D"noreferrer">dougfoster.emailstandards@gmail.com</a>&gt; wrote:<br></=
div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"ltr">My specific concern is with disposition information.=
=C2=A0 =C2=A0 Whether the message presents with acceptable credentials is t=
he sender&#39;s responsibility, and I have no problem with documenting whet=
her it passed SPF or DKIM or both, including which DKIM scope was used for =
the evaluation.=C2=A0 =C2=A0 =C2=A0I have no problem with reporting the sen=
der=C2=A0policy that I retrieved from DNS.<div><br></div><div>But should I =
report the disposition applied, and the reason that my disposition was diff=
erent from the sender policy?=C2=A0 =C2=A0 That seems like information leak=
age about my defenses which should only be revealed to highly trusted corre=
spondent domains.</div><div><br></div><div>Consider what is likely to happe=
n If I call an organization&#39;s help desk and say,=C2=A0</div><div>=C2=A0=
 =C2=A0 =C2=A0&quot;My emails to Sally are not getting delivered, and I wan=
t to know why?&quot;</div><div>The answer should be, and usually is,=C2=A0<=
/div><div>=C2=A0 =C2=A0 =C2=A0&quot;Have Sally open a ticket and we will di=
scuss the problem with her!&quot;</div><div><div>Should not the same policy=
 apply here?=C2=A0 =C2=A0 =C2=A0</div></div></div></blockquote><div><br></d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div =
dir=3D"ltr"><div><div></div></div><div><br></div><div>Possible misuse of di=
sposition information:</div><div>- DMARC=3D(Fail), Disposition =3D (120 del=
ivered) -- probably means that my system does not enforce DMARC at all</div=
><div>- DMARC=3D(Pass), Disposition =3D (20 delivered, 100 rejected)=C2=A0 =
-- possibly means that my system needs 20 messages to learn how to identify=
 bad content</div><div><br></div><div>I suggest that disposition informatio=
n should be redacted by default, and only included on an exception basis fo=
r highly trusted source domains.</div><div><br></div></div></blockquote><di=
v><br></div><div>You&#39;re using the phrase &quot;disposition was differen=
t from the sender policy&quot; in a way that I don&#39;t understand.</div><=
div><br></div><div>Sender policy is a request for handling when a message f=
ails DMARC validation checks. In your examples of possible misuse of dispos=
ition information, one you&#39;re citing is 100 rejected messages when DMAR=
C passes; that&#39;s not a disposition that&#39;s different from sender pol=
icy, because DMARC pass is no guarantee of a message being accepted, and ag=
ain, sender policy only concerns the state of DMARC failing validation chec=
ks. The DMARC policy statement isn&#39;t a vehicle for requesting handling =
when the message passes DMARC checks. Beyond that, I&#39;m not even sure th=
at a condition exists where a message would have a disposition of &quot;rej=
ected due to DMARC&quot; when the DMARC validation result is pass, but I&#3=
9;ve been accused in the past of lacking imagination, so perhaps it could h=
appen.</div><div><br></div><div>For your example of DMARC failing and all 1=
20 messages being delivered, I&#39;ve never personally met a spammer (every=
 conversation I ever had started with &quot;I&#39;m not a spammer&quot;)=C2=
=A0 but I can&#39;t conceive of a spammer configuring his domain with a DMA=
RC policy of p=3Dreject and sending mail that doesn&#39;t authenticate as a=
 way of probing things, but I suppose it could happen. Because aggregate re=
ports only come in once every 24 hours from most places, he&#39;s not going=
 to get immediate gratification like he would simply by having a few test o=
r seed accounts at the target domain, but maybe he&#39;s patient. Of course=
, DMARC isn&#39;t the sole arbiter of whether or not the message made it to=
 the Inbox and not the Junk or Spam folder, so results would be inconclusiv=
e at best. His test accounts will tell him much more than DMARC reports wil=
l tell him.</div><div><br></div><div>I can&#39;t speak for any mailbox prov=
iders, but I suspect that the work of updating their reporting tools to han=
dle an exception list and curating such a list is more expensive to them th=
an whatever risk might exist in generating a DMARC aggregate report for a f=
ew spam sending domains. Maybe a note in Security Considerations or somethi=
ng? *shrug*</div></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"=
ltr"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-=
bottom:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical-alig=
n:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd =
Herr</b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;=
font-size:small;font-family:Arial"> | Sr. Technical Program Manager</span><=
/div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:=
small;font-family:Arial"><div style=3D"text-align:left"><span style=3D"vert=
ical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:baseline=
"> <a href=3D"mailto:todd.herr@valimail.com" target=3D"_blank" rel=3D"noref=
errer">todd.herr@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 703.220.4153 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border:none;height:=
40px;width:177px"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);fo=
nt-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(2=
55,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p d=
ir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.38;marg=
in-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial"><span =
style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all data =
transmitted with it contains confidential and/or proprietary information in=
tended solely for the use of individual(s) authorized to receive it. If you=
 are not an intended and authorized recipient you are hereby notified of an=
y use, disclosure, copying or distribution of the information included in t=
his transmission is prohibited and may be unlawful. Please immediately noti=
fy the sender by replying to this email and then delete it from your system=
.</span></font></p></span></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank" rel=3D"noreferrer">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div>

--000000000000a2170305b97da455--


From nobody Fri Jan 22 06:15:52 2021
Return-Path: <todd.herr@valimail.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 0012C3A12E7 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 06:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 VARLL26iPTCb for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 06:15:47 -0800 (PST)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7EB33A12ED for <dmarc@ietf.org>; Fri, 22 Jan 2021 06:15:47 -0800 (PST)
Received: by mail-qt1-x82a.google.com with SMTP id z22so4138640qto.7 for <dmarc@ietf.org>; Fri, 22 Jan 2021 06:15:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=6sa2zTUMdrTujsalFhaoRW1+uQOaFiKjwyRNMOVZGc0=; b=WtM/unnYavts7S2K6HbubLwPYyWZtqAaCMOjYhqU5A9PVqvH5i8th8uJoX42nx+D7o eMAZsseO9kEZFsp9HwKFXaF62m7B3U8qtR/IdJTSgWy/WO2shIHrCJIUGBOuku2KXTQb vOR0HiiWOtJlVkGUPgm5f+HEwQ12IB8lVNSgqBg6pFEa3MGKf2SR6zzayS4rLTw7Zuu/ 6OX5+F8xvTrcEQXveow5bt2jdEjQUZrpsEsMvuwtHsA6rznMk+5+4ixO/XpvR5ogS2Uw +hLQgq4C1wnTPrRScS790qUlP8rIXgC279qNT+8O4vN/hER7MgLpMf5Dl3uPrJ4/Ltid R95w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=6sa2zTUMdrTujsalFhaoRW1+uQOaFiKjwyRNMOVZGc0=; b=a+ZR/1vxVu4g5i43q8MerOEVXpHofDGV3b5Q9HClAIyKxmiJXbJKyQfLfr18kpmxYo fJ+mgKF7roy8KcuLAxa03QlnotrQ0B4ARclqUmyrigeFVUJcYXjauTmlNnchj7DMvUg3 eH/RquEYrjyssoFUdRuic15MdcM37xize53+aoG9ARTj/5zNCgASEdfm3qeLoPb4E5xu Gc4dLI3DOdySvk73H5BzKxBt6I4jKhdsgL6+t2ytmfuQTjWHAl9zucGFORecr/RLvRGc zH8s7xtuCej3brpGkJP1CQwTYy1gZbshVH3Ldz+4JuI9jOXL3KxU/1uPGh7choyAoY5Y 1SLw==
X-Gm-Message-State: AOAM531GoPAj1GXH2iv4oXTGPOAt/Vib6UdKQZTDXbJ6n9u6hiO7gyjU i17SmhdrYob4WNGWd3JOBtcO4lO/ep4JcZDIsCKgvCpE5jzj4w==
X-Google-Smtp-Source: ABdhPJzuo1KFRgmjcaB0W6JCmDe/W6IO/04dmLt8/AYC0Uxc/IpLLr+s2ACHOsN3ufrS4vpMgtmyN9ZqGyqVhlfszho=
X-Received: by 2002:ac8:6b44:: with SMTP id x4mr4467877qts.224.1611324945718;  Fri, 22 Jan 2021 06:15:45 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com> <CAHej_8nJ60G+OHa=5OHXABHzG4wNSNhJ3mvME6Rk=U4z_GbyjA@mail.gmail.com> <CAH48ZfxMs+M48-C0MEPBRY1fBDiuOQrnQ_BFtXbc=G+0bCJasg@mail.gmail.com>
In-Reply-To: <CAH48ZfxMs+M48-C0MEPBRY1fBDiuOQrnQ_BFtXbc=G+0bCJasg@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Fri, 22 Jan 2021 09:15:29 -0500
Message-ID: <CAHej_8nGRmzus23z9C0A58D7ZSAgNsiFO+DeQj3t=0zs6nx=_Q@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000001f6b805b97dd332"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/v0CBCArlVBFXuwtzqGTxXzo5qZY>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 14:15:50 -0000

--00000000000001f6b805b97dd332
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 9:02 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> Not sure what is unclear about my concern.
>
> The spec provides for reporting whether the actual disposition was
> different from the sender policy request, and the reason that this was done.
>
>
"DMARC=(Pass), Disposition = (20 delivered, 100 rejected)  -- possibly
means that my system needs 20 messages to learn how to identify bad content"


As I said, the above is not an example of the 'actual disposition being
different from the sender policy request', because the sender policy
request does not cover the scenario where DMARC passed. It only applies to
those cases where DMARC fails. There is no facility for a domain owner to
use DMARC to request message treatment when the DMARC validation result is
'pass', nor should a domain owner assume that a message that passes DMARC
checks will be accepted solely based on that information.



> Ale suggests that "disposition" must be narrowly defined to mean only the
> disposition based on DMARC staus.  This still means that local policy is
> revealed under some circumstances.
>
> I do not see why local policy should be revealed at all.
>

Consider the opposite case, one where a hypothetical financial institution
publishes a policy of p=reject and receives aggregate reports showing mail
that it did not originate failing DMARC but not being rejected. That is
information that might prompt a conversation between the financial
institution and the DMARC validator, in an effort to ensure that its mutual
customers aren't exposed to possible abuse vectors.

Yes, that would still be communicated in your scenario of highly trusted
correspondent domains, but I don't believe that the work necessary to
curate such a list provides enough ROI for the report generator to override
whatever minimal risk there might be in revealing its DMARC handling
policies to miscreants. DMARC aggregate reports are not the only source of
such information for the miscreant; the bad guys already have accounts at
their target mailbox providers, and they're sending mail to those accounts
and learning what happens from those accounts and from their own bounce
logs.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--00000000000001f6b805b97dd332
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 9:02 AM Douglas F=
oster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfoster=
.emailstandards@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">Not s=
ure what is unclear about my concern.<div dir=3D"auto"><br></div></div></bl=
ockquote></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"auto"><div dir=3D"auto"></div><div dir=3D"auto=
">The spec provides for reporting whether the actual disposition was differ=
ent from the sender policy request, and the reason that this was done.</div=
><div dir=3D"auto"><br></div></div></blockquote><div><br></div><blockquote =
style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div class=3D"gma=
il_quote"><div><span style=3D"color:rgb(80,0,80)">&quot;DMARC=3D(Pass), Dis=
position =3D (20 delivered, 100 rejected)=C2=A0 -- possibly means that my s=
ystem needs 20 messages to learn how to identify bad content&quot;</span></=
div></div></blockquote><div class=3D"gmail_quote"><div><br></div></div><div=
>As I said, the above is not an example of the &#39;actual disposition bein=
g different from the sender policy request&#39;, because the sender policy =
request does not cover the scenario where DMARC passed. It only applies to =
those cases where DMARC fails. There is no facility for a domain owner to u=
se DMARC to request message treatment when the DMARC validation result is &=
#39;pass&#39;, nor should a domain owner assume that a message that passes =
DMARC checks will be accepted solely based on that=C2=A0information.</div><=
div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"auto"><div dir=3D"auto"></div><div dir=3D"auto">Ale sugge=
sts that &quot;disposition&quot; must be narrowly defined to mean only the =
disposition based on DMARC staus.=C2=A0 This still means that local policy =
is revealed under some circumstances.=C2=A0=C2=A0</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">I do not see why local policy should be revealed =
at all.</div></div></blockquote><div><br></div><div>Consider the opposite c=
ase, one where a hypothetical financial institution publishes a policy of p=
=3Dreject and receives aggregate reports showing mail that it did not origi=
nate failing DMARC but not being rejected. That is information that might p=
rompt a conversation between the financial institution and the DMARC valida=
tor, in an effort to ensure that its mutual customers aren&#39;t exposed to=
 possible abuse vectors.</div><div><br></div><div>Yes, that would still be =
communicated in your scenario of highly trusted correspondent domains, but =
I don&#39;t believe that the work necessary to curate such a list provides =
enough ROI for the report generator to override whatever minimal risk there=
 might be in revealing its DMARC handling policies to miscreants. DMARC agg=
regate reports are not the only source of such information for the miscrean=
t; the bad guys already have accounts at their target mailbox providers, an=
d they&#39;re sending mail to those accounts and learning what happens from=
 those accounts and from their own bounce logs.</div><div><br></div></div>-=
- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p dir=3D"ltr" style=
=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"t=
ext-align:left"><span style=3D"vertical-align:baseline;white-space:pre-wrap=
;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span style=3D"v=
ertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Ari=
al"> | Sr. Technical Program Manager</span></div><span style=3D"vertical-al=
ign:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div s=
tyle=3D"text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b><=
/span><span style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@=
valimail.com" target=3D"_blank">todd.herr@valimail.com</a></span></div></sp=
an><span><div><span><b>p:</b></span><span> 703.220.4153 </span><span></span=
></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial=
,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical=
-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercon=
tent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0Lh=
bnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" sty=
le=3D"border: none; height: 40px; width: 177px;"></span></p><p dir=3D"ltr" =
style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-si=
ze:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;=
margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255=
,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D=
"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre=
-wrap">This email and all data transmitted with it contains confidential an=
d/or proprietary information intended solely for the use of individual(s) a=
uthorized to receive it. If you are not an intended and authorized recipien=
t you are hereby notified of any use, disclosure, copying or distribution o=
f the information included in this transmission is prohibited and may be un=
lawful. Please immediately notify the sender by replying to this email and =
then delete it from your system.</span></font></p></span></div></div>

--00000000000001f6b805b97dd332--


From nobody Fri Jan 22 07:19:19 2021
Return-Path: <dougfoster.emailstandards@gmail.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 9E9283A1304 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 07:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 GipzpO7x2fyf for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 07:19:16 -0800 (PST)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90E783A1244 for <dmarc@ietf.org>; Fri, 22 Jan 2021 07:19:16 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id w187so3177446vsw.5 for <dmarc@ietf.org>; Fri, 22 Jan 2021 07:19:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rg+mwezUY0oegqCHyoe32kt7iXzqZ7/K7KvPwiNcjcw=; b=f0H17OeNvN3GhXih9fWtra7gDOFHDp1W2bwjW0r3Sd+VPLUiBkk9mzS+a69oFi+9qc XCs1a/FPDp5zwfFR0q7PwxtuhP4TAIL7e/vb90pjwWDMmyEIIhTp1URUkpbq7tNn7K+J 2kriJvbfkVgwePsDvgBGEFyG0ZO3Uy2I/QYiw5B2pdOCvwf8SWvrbOv2STsC/9UOpGE9 ZcG+0aAkH8eCJv5KbZBq0ufEBxsMPzMsIdnkU7p9b4do9z3cDmOT/9FQFWnWW/QtLJuo v5s5E8yuI0Cuvj2Bi818YBMZHD7jheLLuXkg3TWlv7BZTpjEkEQ88feFCRfhub1oAOxp XwBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rg+mwezUY0oegqCHyoe32kt7iXzqZ7/K7KvPwiNcjcw=; b=lDLGbDpfch90jfwASVxdSBQF5daPwpRW4p39MMJ/U7MuLfBWYr0QumCFK2K/IlKIQa ZK91qzaIQAQNf1pP9hxaY9Yr1pqf9rzfJ8GKO30ZDUKMy7s0g5ocWYWMwYE3XWDLnQOg STQhNaot10CYzXAs0rAI9FJvn/wjYzHkTIV7YXGaDdC0gx+MoxAkQ47LkqrTA7yQicru aIPAyIcQ/05H5Mi6XMOvPwaAnQE5uOT31vOa1PWb7K2bQY0MWG83s19KynnY3eUs/wes uX2A9cF5n4NXM8ONv3KqWb0+NrIkoX5B1jUiJbDX+cuvOeCC+gWa/RF87BHQEe7uJKB3 bktg==
X-Gm-Message-State: AOAM530v57pmNnSQVihcchNHuSzLIL42ZWPwpX00mnLm0bsTVpyFm6XN /Ooyd3RsLB9Y7o+m7cDWMpsfoC8OAldE57fVmAfyTYQw
X-Google-Smtp-Source: ABdhPJwStiNqaorvUJ2mdoMDRurFIansbh6tVbE8spfI2j8ieV8noyKXiyA4P6IQqqM+NYZPx38+U2CzGnT2KygDAWU=
X-Received: by 2002:a67:507:: with SMTP id 7mr187180vsf.42.1611328755604; Fri, 22 Jan 2021 07:19:15 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com> <CAHej_8nJ60G+OHa=5OHXABHzG4wNSNhJ3mvME6Rk=U4z_GbyjA@mail.gmail.com> <CAH48ZfxMs+M48-C0MEPBRY1fBDiuOQrnQ_BFtXbc=G+0bCJasg@mail.gmail.com> <CAHej_8nGRmzus23z9C0A58D7ZSAgNsiFO+DeQj3t=0zs6nx=_Q@mail.gmail.com>
In-Reply-To: <CAHej_8nGRmzus23z9C0A58D7ZSAgNsiFO+DeQj3t=0zs6nx=_Q@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Fri, 22 Jan 2021 10:19:02 -0500
Message-ID: <CAH48ZfxUAhfdTmPLU1Titj3M3BBtMQ5C3C7bnQv3c4vN1Hadcw@mail.gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000018219a05b97eb654"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/G1fmT6DQ2IbpEK2jRcuwtsnBw0w>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 15:19:19 -0000

--00000000000018219a05b97eb654
Content-Type: text/plain; charset="UTF-8"

Your second point seems to address my question, asserting that the value of
information sharing exceeds the risk.   This is debatable, so I think it
should be documented in security considerations and reacting options should
be articulated.

The first point still escapes me.  If we are providing information about
all messages received, and are providing disposition information about all
those messages, then it includes information about messages that were
acceptably authorized.  Sender policy is irrelevant.  All that matters is
which messages are reported with disposition results.

On Fri, Jan 22, 2021, 9:16 AM Todd Herr <todd.herr=
40valimail.com@dmarc.ietf.org> wrote:

> On Fri, Jan 22, 2021 at 9:02 AM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> Not sure what is unclear about my concern.
>>
>> The spec provides for reporting whether the actual disposition was
>> different from the sender policy request, and the reason that this was done.
>>
>>
> "DMARC=(Pass), Disposition = (20 delivered, 100 rejected)  -- possibly
> means that my system needs 20 messages to learn how to identify bad content"
>
>
> As I said, the above is not an example of the 'actual disposition being
> different from the sender policy request', because the sender policy
> request does not cover the scenario where DMARC passed. It only applies to
> those cases where DMARC fails. There is no facility for a domain owner to
> use DMARC to request message treatment when the DMARC validation result is
> 'pass', nor should a domain owner assume that a message that passes DMARC
> checks will be accepted solely based on that information.
>
>
>
>> Ale suggests that "disposition" must be narrowly defined to mean only the
>> disposition based on DMARC staus.  This still means that local policy is
>> revealed under some circumstances.
>>
>> I do not see why local policy should be revealed at all.
>>
>
> Consider the opposite case, one where a hypothetical financial institution
> publishes a policy of p=reject and receives aggregate reports showing mail
> that it did not originate failing DMARC but not being rejected. That is
> information that might prompt a conversation between the financial
> institution and the DMARC validator, in an effort to ensure that its mutual
> customers aren't exposed to possible abuse vectors.
>
> Yes, that would still be communicated in your scenario of highly trusted
> correspondent domains, but I don't believe that the work necessary to
> curate such a list provides enough ROI for the report generator to override
> whatever minimal risk there might be in revealing its DMARC handling
> policies to miscreants. DMARC aggregate reports are not the only source of
> such information for the miscreant; the bad guys already have accounts at
> their target mailbox providers, and they're sending mail to those accounts
> and learning what happens from those accounts and from their own bounce
> logs.
>
> --
>
> *Todd Herr* | Sr. Technical Program Manager
> *e:* todd.herr@valimail.com
> *p:* 703.220.4153
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--00000000000018219a05b97eb654
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Your second point seems to address my question, asserting=
 that the value of information sharing exceeds the risk.=C2=A0 =C2=A0This i=
s debatable, so I think it should be documented in security considerations =
and reacting options should be articulated.<div dir=3D"auto"><br></div><div=
 dir=3D"auto">The first point still escapes=C2=A0me.=C2=A0 If we are provid=
ing information about all messages received, and are providing disposition =
information about all those messages, then it includes information about me=
ssages that were acceptably authorized.=C2=A0 Sender policy is irrelevant.=
=C2=A0 All that matters is which messages are reported with disposition res=
ults.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Fri, Jan 22, 2021, 9:16 AM Todd Herr &lt;todd.herr=3D<a href=
=3D"mailto:40valimail.com@dmarc.ietf.org" target=3D"_blank" rel=3D"noreferr=
er">40valimail.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 9:0=
2 AM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.c=
om" rel=3D"noreferrer noreferrer" target=3D"_blank">dougfoster.emailstandar=
ds@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">Not sure what is u=
nclear about my concern.<div dir=3D"auto"><br></div></div></blockquote></di=
v><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div dir=3D"auto"><div dir=3D"auto"></div><div dir=3D"auto">The spec pr=
ovides for reporting whether the actual disposition was different from the =
sender policy request, and the reason that this was done.</div><div dir=3D"=
auto"><br></div></div></blockquote><div><br></div><blockquote style=3D"marg=
in:0px 0px 0px 40px;border:none;padding:0px"><div class=3D"gmail_quote"><di=
v><span style=3D"color:rgb(80,0,80)">&quot;DMARC=3D(Pass), Disposition =3D =
(20 delivered, 100 rejected)=C2=A0 -- possibly means that my system needs 2=
0 messages to learn how to identify bad content&quot;</span></div></div></b=
lockquote><div class=3D"gmail_quote"><div><br></div></div><div>As I said, t=
he above is not an example of the &#39;actual disposition being different f=
rom the sender policy request&#39;, because the sender policy request does =
not cover the scenario where DMARC passed. It only applies to those cases w=
here DMARC fails. There is no facility for a domain owner to use DMARC to r=
equest message treatment when the DMARC validation result is &#39;pass&#39;=
, nor should a domain owner assume that a message that passes DMARC checks =
will be accepted solely based on that=C2=A0information.</div><div><br></div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"auto"><div dir=3D"auto"></div><div dir=3D"auto">Ale suggests that &quo=
t;disposition&quot; must be narrowly defined to mean only the disposition b=
ased on DMARC staus.=C2=A0 This still means that local policy is revealed u=
nder some circumstances.=C2=A0=C2=A0</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">I do not see why local policy should be revealed at all.</div>=
</div></blockquote><div><br></div><div>Consider the opposite case, one wher=
e a hypothetical financial institution publishes a policy of p=3Dreject and=
 receives aggregate reports showing mail that it did not originate failing =
DMARC but not being rejected. That is information that might prompt a conve=
rsation between the financial institution and the DMARC validator, in an ef=
fort to ensure that its mutual customers aren&#39;t exposed to possible abu=
se vectors.</div><div><br></div><div>Yes, that would still be communicated =
in your scenario of highly trusted correspondent domains, but I don&#39;t b=
elieve that the work necessary to curate such a list provides enough ROI fo=
r the report generator to override whatever minimal risk there might be in =
revealing its DMARC handling policies to miscreants. DMARC aggregate report=
s are not the only source of such information for the miscreant; the bad gu=
ys already have accounts at their target mailbox providers, and they&#39;re=
 sending mail to those accounts and learning what happens from those accoun=
ts and from their own bounce logs.</div><div><br></div></div>-- <br><div di=
r=3D"ltr"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;ma=
rgin-bottom:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical=
-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>=
Todd Herr</b></span><span style=3D"vertical-align:baseline;white-space:pre-=
wrap;font-size:small;font-family:Arial"> | Sr. Technical Program Manager</s=
pan></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D=
"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:bas=
eline"> <a href=3D"mailto:todd.herr@valimail.com" rel=3D"noreferrer norefer=
rer" target=3D"_blank">todd.herr@valimail.com</a></span></div></span><span>=
<div><span><b>p:</b></span><span> 703.220.4153 </span><span></span></div></=
span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetic=
a,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:=
1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-f=
amily:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:ba=
seline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/=
_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4=
yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"bor=
der:none;height:40px;width:177px"></span></p><p dir=3D"ltr" style=3D"color:=
rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;backgr=
ound-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0=
pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-=
height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=
=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This em=
ail and all data transmitted with it contains confidential and/or proprieta=
ry information intended solely for the use of individual(s) authorized to r=
eceive it. If you are not an intended and authorized recipient you are here=
by notified of any use, disclosure, copying or distribution of the informat=
ion included in this transmission is prohibited and may be unlawful. Please=
 immediately notify the sender by replying to this email and then delete it=
 from your system.</span></font></p></span></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/dmarc</a><br>
</blockquote></div>

--00000000000018219a05b97eb654--


From nobody Fri Jan 22 07:31:34 2021
Return-Path: <seth@valimail.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 6E3373A1315 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 07:31:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 bapjwMdk2Daz for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 07:31:31 -0800 (PST)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04C8A3A0F22 for <dmarc@ietf.org>; Fri, 22 Jan 2021 07:31:30 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id j138so2859054vsd.8 for <dmarc@ietf.org>; Fri, 22 Jan 2021 07:31:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oL5m1BvPtXO1q0sDqqdCDUV7t7x5Ca5xGoZl3LXxrOE=; b=Kzy8+vFrJnlLYqHQsRUIr0niuuYcOTNtv1HiofZ6DmWU0FapQr44jvpDXXi3M4L2Th JfmD0ROxplU3KN6EaiQAa4ye/yIqToYo1wGQhFwJ6MGpwhpJQcC2tkzZ1CjusVcBkv10 9bfylhk/87wud2KnrvFog0voWvDqoR7z9Yc4q+fDS/XiTgVTpBfCsYJMtTekkrzLoiQY U1Db147jkUOJ7kQo1dh+FutvIng5fg6zdcI0YH0eIeK75ZPReXOiG/oxvu8KPciaTVz9 Fp/YOOIh+nzSriapzO8T39X1MEZm+vWcskFu3Zr52cxu5sKl7QoHfWov5oNo4xjmSd5I NWog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oL5m1BvPtXO1q0sDqqdCDUV7t7x5Ca5xGoZl3LXxrOE=; b=bCJt4Zqok8htvzAAEyC2gJ2y6SDSOgIN2VEYfxJVvLqHhwn3yyYPWQuRvB4Qo2JzHD jHeRwFbLuQR4G31ZbER6vPrMjtXzVGQhSUkyUD8puRrp43K1GuwO4JSNXKVOiz4N6E9V nPxc9IWx09Dx4auk0+EpCyG5hxA1naWaKVWZaBSb618CFsCmjLU+ojMSNQUTxvRncMsd 6bZWUkAmkko2AximRMAyz+P7tyTCBvWgOQR6lKiiUWqfLWzHTwnaWQnSWKB+V0Rl5IOV HFLUAxcuQ3R6LnKXHf4qTAM9fLkHYFwGSp8B4ahh0xo6FAW6ZjWjSOlO9Q5YtZ+8vN/H eixQ==
X-Gm-Message-State: AOAM532NQD3j2tyjhCgboo07bFhidqz7IaCIYsEYR8B9CDLH+/wFpxPU /qE+4Nk0lMWjBCxUHgigF+i9pIEdhCiGd9lRgf4XHQ==
X-Google-Smtp-Source: ABdhPJy/Hj3oVHCRpgISEQnF5aK9y9rySqg8WerHcRmdWODjJQaQEN4tZDtYuOfzNty0av5zB17wcSlupRdre5efNE8=
X-Received: by 2002:a67:fd5a:: with SMTP id g26mr3632955vsr.35.1611329489717;  Fri, 22 Jan 2021 07:31:29 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com> <CAHej_8nJ60G+OHa=5OHXABHzG4wNSNhJ3mvME6Rk=U4z_GbyjA@mail.gmail.com> <CAH48ZfxMs+M48-C0MEPBRY1fBDiuOQrnQ_BFtXbc=G+0bCJasg@mail.gmail.com> <CAHej_8nGRmzus23z9C0A58D7ZSAgNsiFO+DeQj3t=0zs6nx=_Q@mail.gmail.com> <CAH48ZfxUAhfdTmPLU1Titj3M3BBtMQ5C3C7bnQv3c4vN1Hadcw@mail.gmail.com>
In-Reply-To: <CAH48ZfxUAhfdTmPLU1Titj3M3BBtMQ5C3C7bnQv3c4vN1Hadcw@mail.gmail.com>
From: Seth Blank <seth@valimail.com>
Date: Fri, 22 Jan 2021 07:31:18 -0800
Message-ID: <CAOZAAfMZ3wBQ9sp_8an0dUPPLtAPH6=fo4ZWDzQm=xvk80sjyw@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d9dd5e05b97ee18b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Yq9jnn4mZZA9W6gajiNQRkcCT08>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 15:31:33 -0000

--000000000000d9dd5e05b97ee18b
Content-Type: text/plain; charset="UTF-8"

Douglas, what I'm hearing in this thread is that the information in a DMARC
report is well understood, and mailbox receivers are especially sensitive
to information leakages to spammers who could abuse that, and after seven
years of operational experience, are telling you such leakage does not
occur from DMARC aggregate reports.

I'm not opposed to saying such a thing in the considerations if there's
group consensus to do so, but let's wrap this thread and move on to others
tickets now, please.

Seth, as Chair

On Fri, Jan 22, 2021 at 7:19 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> Your second point seems to address my question, asserting that the value
> of information sharing exceeds the risk.   This is debatable, so I think it
> should be documented in security considerations and reacting options should
> be articulated.
>
> The first point still escapes me.  If we are providing information about
> all messages received, and are providing disposition information about all
> those messages, then it includes information about messages that were
> acceptably authorized.  Sender policy is irrelevant.  All that matters is
> which messages are reported with disposition results.
>
> On Fri, Jan 22, 2021, 9:16 AM Todd Herr <todd.herr=
> 40valimail.com@dmarc.ietf.org> wrote:
>
>> On Fri, Jan 22, 2021 at 9:02 AM Douglas Foster <
>> dougfoster.emailstandards@gmail.com> wrote:
>>
>>> Not sure what is unclear about my concern.
>>>
>>> The spec provides for reporting whether the actual disposition was
>>> different from the sender policy request, and the reason that this was done.
>>>
>>>
>> "DMARC=(Pass), Disposition = (20 delivered, 100 rejected)  -- possibly
>> means that my system needs 20 messages to learn how to identify bad content"
>>
>>
>> As I said, the above is not an example of the 'actual disposition being
>> different from the sender policy request', because the sender policy
>> request does not cover the scenario where DMARC passed. It only applies to
>> those cases where DMARC fails. There is no facility for a domain owner to
>> use DMARC to request message treatment when the DMARC validation result is
>> 'pass', nor should a domain owner assume that a message that passes DMARC
>> checks will be accepted solely based on that information.
>>
>>
>>
>>> Ale suggests that "disposition" must be narrowly defined to mean only
>>> the disposition based on DMARC staus.  This still means that local policy
>>> is revealed under some circumstances.
>>>
>>> I do not see why local policy should be revealed at all.
>>>
>>
>> Consider the opposite case, one where a hypothetical financial
>> institution publishes a policy of p=reject and receives aggregate reports
>> showing mail that it did not originate failing DMARC but not being
>> rejected. That is information that might prompt a conversation between the
>> financial institution and the DMARC validator, in an effort to ensure that
>> its mutual customers aren't exposed to possible abuse vectors.
>>
>> Yes, that would still be communicated in your scenario of highly trusted
>> correspondent domains, but I don't believe that the work necessary to
>> curate such a list provides enough ROI for the report generator to override
>> whatever minimal risk there might be in revealing its DMARC handling
>> policies to miscreants. DMARC aggregate reports are not the only source of
>> such information for the miscreant; the bad guys already have accounts at
>> their target mailbox providers, and they're sending mail to those accounts
>> and learning what happens from those accounts and from their own bounce
>> logs.
>>
>> --
>>
>> *Todd Herr* | Sr. Technical Program Manager
>> *e:* todd.herr@valimail.com
>> *p:* 703.220.4153
>>
>>
>> This email and all data transmitted with it contains confidential and/or
>> proprietary information intended solely for the use of individual(s)
>> authorized to receive it. If you are not an intended and authorized
>> recipient you are hereby notified of any use, disclosure, copying or
>> distribution of the information included in this transmission is prohibited
>> and may be unlawful. Please immediately notify the sender by replying to
>> this email and then delete it from your system.
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000d9dd5e05b97ee18b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Douglas, what I&#39;m hearing in this thread is that the i=
nformation in a DMARC report is well understood, and mailbox receivers are =
especially sensitive to information leakages to spammers who could abuse th=
at, and after seven years of operational experience, are telling you such l=
eakage does not occur from DMARC aggregate reports.<div><br></div><div>I&#3=
9;m not opposed to saying such a thing in the considerations if there&#39;s=
 group consensus to do so, but let&#39;s wrap this thread and move on to ot=
hers tickets now, please.</div><div><br></div><div>Seth, as Chair</div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On F=
ri, Jan 22, 2021 at 7:19 AM Douglas Foster &lt;<a href=3D"mailto:dougfoster=
.emailstandards@gmail.com">dougfoster.emailstandards@gmail.com</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"a=
uto">Your second point seems to address my question, asserting that the val=
ue of information sharing exceeds the risk.=C2=A0 =C2=A0This is debatable, =
so I think it should be documented in security considerations and reacting =
options should be articulated.<div dir=3D"auto"><br></div><div dir=3D"auto"=
>The first point still escapes=C2=A0me.=C2=A0 If we are providing informati=
on about all messages received, and are providing disposition information a=
bout all those messages, then it includes information about messages that w=
ere acceptably authorized.=C2=A0 Sender policy is irrelevant.=C2=A0 All tha=
t matters is which messages are reported with disposition results.</div></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Fri, Jan 22, 2021, 9:16 AM Todd Herr &lt;todd.herr=3D<a href=3D"mailto:40va=
limail.com@dmarc.ietf.org" rel=3D"noreferrer" target=3D"_blank">40valimail.=
com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at=
 9:02 AM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailstandards@gma=
il.com" rel=3D"noreferrer noreferrer" target=3D"_blank">dougfoster.emailsta=
ndards@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">Not sure what =
is unclear about my concern.<div dir=3D"auto"><br></div></div></blockquote>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"auto"><div dir=3D"auto"></div><div dir=3D"auto">The spe=
c provides for reporting whether the actual disposition was different from =
the sender policy request, and the reason that this was done.</div><div dir=
=3D"auto"><br></div></div></blockquote><div><br></div><blockquote style=3D"=
margin:0px 0px 0px 40px;border:none;padding:0px"><div class=3D"gmail_quote"=
><div><span style=3D"color:rgb(80,0,80)">&quot;DMARC=3D(Pass), Disposition =
=3D (20 delivered, 100 rejected)=C2=A0 -- possibly means that my system nee=
ds 20 messages to learn how to identify bad content&quot;</span></div></div=
></blockquote><div class=3D"gmail_quote"><div><br></div></div><div>As I sai=
d, the above is not an example of the &#39;actual disposition being differe=
nt from the sender policy request&#39;, because the sender policy request d=
oes not cover the scenario where DMARC passed. It only applies to those cas=
es where DMARC fails. There is no facility for a domain owner to use DMARC =
to request message treatment when the DMARC validation result is &#39;pass&=
#39;, nor should a domain owner assume that a message that passes DMARC che=
cks will be accepted solely based on that=C2=A0information.</div><div><br><=
/div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><di=
v dir=3D"auto"><div dir=3D"auto"></div><div dir=3D"auto">Ale suggests that =
&quot;disposition&quot; must be narrowly defined to mean only the dispositi=
on based on DMARC staus.=C2=A0 This still means that local policy is reveal=
ed under some circumstances.=C2=A0=C2=A0</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">I do not see why local policy should be revealed at all.</=
div></div></blockquote><div><br></div><div>Consider the opposite case, one =
where a hypothetical financial institution publishes a policy of p=3Dreject=
 and receives aggregate reports showing mail that it did not originate fail=
ing DMARC but not being rejected. That is information that might prompt a c=
onversation between the financial institution and the DMARC validator, in a=
n effort to ensure that its mutual customers aren&#39;t exposed to possible=
 abuse vectors.</div><div><br></div><div>Yes, that would still be communica=
ted in your scenario of highly trusted correspondent domains, but I don&#39=
;t believe that the work necessary to curate such a list provides enough RO=
I for the report generator to override whatever minimal risk there might be=
 in revealing its DMARC handling policies to miscreants. DMARC aggregate re=
ports are not the only source of such information for the miscreant; the ba=
d guys already have accounts at their target mailbox providers, and they&#3=
9;re sending mail to those accounts and learning what happens from those ac=
counts and from their own bounce logs.</div><div><br></div></div>-- <br><di=
v dir=3D"ltr"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0p=
t;margin-bottom:0pt"></p><div style=3D"text-align:left"><span style=3D"vert=
ical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"=
><b>Todd Herr</b></span><span style=3D"vertical-align:baseline;white-space:=
pre-wrap;font-size:small;font-family:Arial"> | Sr. Technical Program Manage=
r</span></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;f=
ont-size:small;font-family:Arial"><div style=3D"text-align:left"><span styl=
e=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align=
:baseline"> <a href=3D"mailto:todd.herr@valimail.com" rel=3D"noreferrer nor=
eferrer" target=3D"_blank">todd.herr@valimail.com</a></span></div></span><s=
pan><div><span><b>p:</b></span><span> 703.220.4153 </span><span></span></di=
v></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helv=
etica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-alig=
n:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.=
com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXp=
rAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D=
"border: none; height: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=
=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:sm=
all;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,=
255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666=
666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre-wrap=
">This email and all data transmitted with it contains confidential and/or =
proprietary information intended solely for the use of individual(s) author=
ized to receive it. If you are not an intended and authorized recipient you=
 are hereby notified of any use, disclosure, copying or distribution of the=
 information included in this transmission is prohibited and may be unlawfu=
l. Please immediately notify the sender by replying to this email and then =
delete it from your system.</span></font></p></span></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/dmarc</a><br>
</blockquote></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--000000000000d9dd5e05b97ee18b--


From nobody Fri Jan 22 07:40:58 2021
Return-Path: <dougfoster.emailstandards@gmail.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 25D173A131F for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 07:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 SeoY0pChL8JM for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 07:40:55 -0800 (PST)
Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 122D23A131B for <dmarc@ietf.org>; Fri, 22 Jan 2021 07:40:54 -0800 (PST)
Received: by mail-ua1-x930.google.com with SMTP id u27so1933237uaa.13 for <dmarc@ietf.org>; Fri, 22 Jan 2021 07:40:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WIvXZC5LpVMnfCmozERJj8NJ54jXDn/Sku1hhSlLfws=; b=gQPek2qqPAOE4lHkxblvE32AamBCRt5t2I6r9bYEWLG/Nr968eeE7lgzfroNlTpZ8R mLv2GR9KBE6MJnyz9Coe3P8Ce4QS0KJNF4qduhwtTou4s2D6X2h9FVMpUTORUKluptuQ 2/xJqM1u2nDW5s1620SQsKsCThGTtVJDqu0NeJgp6GwGNaGz8hTzNKpNkyZCLxNcMrqL DxdcdpPMmYMmOWDSOSVZ1qVhEepqmEnkRjqglNJNKpXLS/w9K3lDnEIoD7MPC0+okpVc ljgEw2VJA844qmOk5Lwp+X8MCzLW4Tg5c9skFNJWoX3ZT5r9oqF2Tp80d6jWdaaJbuMK pUxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WIvXZC5LpVMnfCmozERJj8NJ54jXDn/Sku1hhSlLfws=; b=dM7gAYaAFxycbqnKSGSgjgIosPcZ2075OGv6yjdBLlqVqTiyeRBixPeMxFcp67Z1Wu p/hNp9H7XgnoGSLb4Tp/Y9M1EYaMMnSEdt2YCTtuMLMR3WA/iOjuovoms/8PxI4wlESl Ua2oXmiVXg8/fFIFaVCnqRJirzO2ReDwpzM3lICG9PnXUJ/leJPyrXH6QVWPARPwWlnx 2cktCcpikfvZGjXKqKLPeyfu4jwhwK07cf+DMfbDImudaAafO6srrcz/BhmfzRDz2r/5 UYtgDcg+1qOJ2dTeVtSEk2dKNfErx7Tfxw0I5c1X+faRnJZU0iWMezOSk7iTH3k5fjMd PE+g==
X-Gm-Message-State: AOAM532yNQBi1ONcTmfNcoe3ygkfrbx9pGMhJp4/Rein9mCWsr7mNC5Z tL8iiQ8vri/d1+ED1uSz6n2mrwz1q3AstHTWzeY=
X-Google-Smtp-Source: ABdhPJx24YWmJQIt3OmbbmZzZzP5yaQdc/pMT8o6ToL+zlYyaL3SPMRDpAkNXBujSRcO6RB7jrWPnAXsDN5CickoCO4=
X-Received: by 2002:ab0:3043:: with SMTP id x3mr366826ual.88.1611330053812; Fri, 22 Jan 2021 07:40:53 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB43515A1079F57BD6F6EE0A80F7A19@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48ZfyJDB9r5-2u2xQF_Dk+UBCz2TTD2WLkbd08NAUNwThWbA@mail.gmail.com> <CAHej_8nJ60G+OHa=5OHXABHzG4wNSNhJ3mvME6Rk=U4z_GbyjA@mail.gmail.com> <CAH48ZfxMs+M48-C0MEPBRY1fBDiuOQrnQ_BFtXbc=G+0bCJasg@mail.gmail.com> <CAHej_8nGRmzus23z9C0A58D7ZSAgNsiFO+DeQj3t=0zs6nx=_Q@mail.gmail.com> <CAH48ZfxUAhfdTmPLU1Titj3M3BBtMQ5C3C7bnQv3c4vN1Hadcw@mail.gmail.com> <CAOZAAfMZ3wBQ9sp_8an0dUPPLtAPH6=fo4ZWDzQm=xvk80sjyw@mail.gmail.com>
In-Reply-To: <CAOZAAfMZ3wBQ9sp_8an0dUPPLtAPH6=fo4ZWDzQm=xvk80sjyw@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Fri, 22 Jan 2021 10:40:35 -0500
Message-ID: <CAH48ZfzMG4zBBS55K7OODjaf+D0ZMy41kFnknJxrWjRfU6DtcA@mail.gmail.com>
To: Seth Blank <seth@valimail.com>
Cc: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007938c505b97f0376"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/MZ4N_JcM-3m_CP-WvNNcrfDe2Ak>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 15:40:57 -0000

--0000000000007938c505b97f0376
Content-Type: text/plain; charset="UTF-8"

Ok

On Fri, Jan 22, 2021, 10:31 AM Seth Blank <seth@valimail.com> wrote:

> Douglas, what I'm hearing in this thread is that the information in a
> DMARC report is well understood, and mailbox receivers are especially
> sensitive to information leakages to spammers who could abuse that, and
> after seven years of operational experience, are telling you such leakage
> does not occur from DMARC aggregate reports.
>
> I'm not opposed to saying such a thing in the considerations if there's
> group consensus to do so, but let's wrap this thread and move on to others
> tickets now, please.
>
> Seth, as Chair
>
> On Fri, Jan 22, 2021 at 7:19 AM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> Your second point seems to address my question, asserting that the value
>> of information sharing exceeds the risk.   This is debatable, so I think it
>> should be documented in security considerations and reacting options should
>> be articulated.
>>
>> The first point still escapes me.  If we are providing information about
>> all messages received, and are providing disposition information about all
>> those messages, then it includes information about messages that were
>> acceptably authorized.  Sender policy is irrelevant.  All that matters is
>> which messages are reported with disposition results.
>>
>> On Fri, Jan 22, 2021, 9:16 AM Todd Herr <todd.herr=
>> 40valimail.com@dmarc.ietf.org> wrote:
>>
>>> On Fri, Jan 22, 2021 at 9:02 AM Douglas Foster <
>>> dougfoster.emailstandards@gmail.com> wrote:
>>>
>>>> Not sure what is unclear about my concern.
>>>>
>>>> The spec provides for reporting whether the actual disposition was
>>>> different from the sender policy request, and the reason that this was done.
>>>>
>>>>
>>> "DMARC=(Pass), Disposition = (20 delivered, 100 rejected)  -- possibly
>>> means that my system needs 20 messages to learn how to identify bad content"
>>>
>>>
>>> As I said, the above is not an example of the 'actual disposition being
>>> different from the sender policy request', because the sender policy
>>> request does not cover the scenario where DMARC passed. It only applies to
>>> those cases where DMARC fails. There is no facility for a domain owner to
>>> use DMARC to request message treatment when the DMARC validation result is
>>> 'pass', nor should a domain owner assume that a message that passes DMARC
>>> checks will be accepted solely based on that information.
>>>
>>>
>>>
>>>> Ale suggests that "disposition" must be narrowly defined to mean only
>>>> the disposition based on DMARC staus.  This still means that local policy
>>>> is revealed under some circumstances.
>>>>
>>>> I do not see why local policy should be revealed at all.
>>>>
>>>
>>> Consider the opposite case, one where a hypothetical financial
>>> institution publishes a policy of p=reject and receives aggregate reports
>>> showing mail that it did not originate failing DMARC but not being
>>> rejected. That is information that might prompt a conversation between the
>>> financial institution and the DMARC validator, in an effort to ensure that
>>> its mutual customers aren't exposed to possible abuse vectors.
>>>
>>> Yes, that would still be communicated in your scenario of highly trusted
>>> correspondent domains, but I don't believe that the work necessary to
>>> curate such a list provides enough ROI for the report generator to override
>>> whatever minimal risk there might be in revealing its DMARC handling
>>> policies to miscreants. DMARC aggregate reports are not the only source of
>>> such information for the miscreant; the bad guys already have accounts at
>>> their target mailbox providers, and they're sending mail to those accounts
>>> and learning what happens from those accounts and from their own bounce
>>> logs.
>>>
>>> --
>>>
>>> *Todd Herr* | Sr. Technical Program Manager
>>> *e:* todd.herr@valimail.com
>>> *p:* 703.220.4153
>>>
>>>
>>> This email and all data transmitted with it contains confidential and/or
>>> proprietary information intended solely for the use of individual(s)
>>> authorized to receive it. If you are not an intended and authorized
>>> recipient you are hereby notified of any use, disclosure, copying or
>>> distribution of the information included in this transmission is prohibited
>>> and may be unlawful. Please immediately notify the sender by replying to
>>> this email and then delete it from your system.
>>> _______________________________________________
>>> dmarc mailing list
>>> dmarc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dmarc
>>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>
>
> --
>
> *Seth Blank* | VP, Standards and New Technologies
> *e:* seth@valimail.com
> *p:* 415.273.8818
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
>

--0000000000007938c505b97f0376
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Ok</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Fri, Jan 22, 2021, 10:31 AM Seth Blank &lt;<a href=
=3D"mailto:seth@valimail.com">seth@valimail.com</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><div dir=3D"ltr">Douglas, what I&#39;m hearing =
in this thread is that the information in a DMARC report is well understood=
, and mailbox receivers are especially sensitive to information leakages to=
 spammers who could abuse that, and after seven years of operational experi=
ence, are telling you such leakage does not occur from DMARC aggregate repo=
rts.<div><br></div><div>I&#39;m not opposed to saying such a thing in the c=
onsiderations if there&#39;s group consensus to do so, but let&#39;s wrap t=
his thread and move on to others tickets now, please.</div><div><br></div><=
div>Seth, as Chair</div></div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Fri, Jan 22, 2021 at 7:19 AM Douglas Foster &lt;=
<a href=3D"mailto:dougfoster.emailstandards@gmail.com" target=3D"_blank" re=
l=3D"noreferrer">dougfoster.emailstandards@gmail.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">Your =
second point seems to address my question, asserting that the value of info=
rmation sharing exceeds the risk.=C2=A0 =C2=A0This is debatable, so I think=
 it should be documented in security considerations and reacting options sh=
ould be articulated.<div dir=3D"auto"><br></div><div dir=3D"auto">The first=
 point still escapes=C2=A0me.=C2=A0 If we are providing information about a=
ll messages received, and are providing disposition information about all t=
hose messages, then it includes information about messages that were accept=
ably authorized.=C2=A0 Sender policy is irrelevant.=C2=A0 All that matters =
is which messages are reported with disposition results.</div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 2=
2, 2021, 9:16 AM Todd Herr &lt;todd.herr=3D<a href=3D"mailto:40valimail.com=
@dmarc.ietf.org" rel=3D"noreferrer noreferrer" target=3D"_blank">40valimail=
.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 a=
t 9:02 AM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailstandards@gm=
ail.com" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">dougfos=
ter.emailstandards@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">No=
t sure what is unclear about my concern.<div dir=3D"auto"><br></div></div><=
/blockquote></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"auto"><div dir=3D"auto"></div><div dir=3D"a=
uto">The spec provides for reporting whether the actual disposition was dif=
ferent from the sender policy request, and the reason that this was done.</=
div><div dir=3D"auto"><br></div></div></blockquote><div><br></div><blockquo=
te style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div class=3D"=
gmail_quote"><div><span style=3D"color:rgb(80,0,80)">&quot;DMARC=3D(Pass), =
Disposition =3D (20 delivered, 100 rejected)=C2=A0 -- possibly means that m=
y system needs 20 messages to learn how to identify bad content&quot;</span=
></div></div></blockquote><div class=3D"gmail_quote"><div><br></div></div><=
div>As I said, the above is not an example of the &#39;actual disposition b=
eing different from the sender policy request&#39;, because the sender poli=
cy request does not cover the scenario where DMARC passed. It only applies =
to those cases where DMARC fails. There is no facility for a domain owner t=
o use DMARC to request message treatment when the DMARC validation result i=
s &#39;pass&#39;, nor should a domain owner assume that a message that pass=
es DMARC checks will be accepted solely based on that=C2=A0information.</di=
v><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"auto"><div dir=3D"auto"></div><div dir=3D"auto">Ale =
suggests that &quot;disposition&quot; must be narrowly defined to mean only=
 the disposition based on DMARC staus.=C2=A0 This still means that local po=
licy is revealed under some circumstances.=C2=A0=C2=A0</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">I do not see why local policy should be reve=
aled at all.</div></div></blockquote><div><br></div><div>Consider the oppos=
ite case, one where a hypothetical financial institution publishes a policy=
 of p=3Dreject and receives aggregate reports showing mail that it did not =
originate failing DMARC but not being rejected. That is information that mi=
ght prompt a conversation between the financial institution and the DMARC v=
alidator, in an effort to ensure that its mutual customers aren&#39;t expos=
ed to possible abuse vectors.</div><div><br></div><div>Yes, that would stil=
l be communicated in your scenario of highly trusted correspondent domains,=
 but I don&#39;t believe that the work necessary to curate such a list prov=
ides enough ROI for the report generator to override whatever minimal risk =
there might be in revealing its DMARC handling policies to miscreants. DMAR=
C aggregate reports are not the only source of such information for the mis=
creant; the bad guys already have accounts at their target mailbox provider=
s, and they&#39;re sending mail to those accounts and learning what happens=
 from those accounts and from their own bounce logs.</div><div><br></div></=
div>-- <br><div dir=3D"ltr"><span><p dir=3D"ltr" style=3D"line-height:1.656=
;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span=
 style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font=
-family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | Sr. Technical =
Program Manager</span></div><span style=3D"vertical-align:baseline;white-sp=
ace:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-align:le=
ft"><span style=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"=
vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" rel=3D"=
noreferrer noreferrer noreferrer" target=3D"_blank">todd.herr@valimail.com<=
/a></span></div></span><span><div><span><b>p:</b></span><span> 703.220.4153=
 </span><span></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,3=
4);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:=
rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span s=
tyle=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:=
transparent;vertical-align:baseline;white-space:pre-wrap"><img src=3D"https=
://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv=
4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZ=
V3rjz19-Dx9rESL" style=3D"border:none;height:40px;width:177px"></span></p><=
p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans=
-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;m=
argin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background=
-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt">=
<font color=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px;w=
hite-space:pre-wrap">This email and all data transmitted with it contains c=
onfidential and/or proprietary information intended solely for the use of i=
ndividual(s) authorized to receive it. If you are not an intended and autho=
rized recipient you are hereby notified of any use, disclosure, copying or =
distribution of the information included in this transmission is prohibited=
 and may be unlawful. Please immediately notify the sender by replying to t=
his email and then delete it from your system.</span></font></p></span></di=
v></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer noreferrer noreferrer" =
target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mai=
lman/listinfo/dmarc</a><br>
</blockquote></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank" rel=3D"noreferrer">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bott=
om:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical-align:ba=
seline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blan=
k</b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;fon=
t-size:small;font-family:Arial"> | VP, Standards and New Technologies</span=
></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-siz=
e:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D"ve=
rtical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:baseli=
ne"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank" rel=3D"noreferr=
er">seth@valimail.com</a></span></div></span><span><div><span><b>p:</b></sp=
an><span> 415.273.8818 </span><span></span></div></span><p dir=3D"ltr" styl=
e=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:s=
mall;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;marg=
in-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,=
0,0);background-color:transparent;vertical-align:baseline;white-space:pre-w=
rap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nE=
opl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuh=
edthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border:none;height:40px;wid=
th:177px"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-famil=
y:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,2=
55);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"lt=
r" style=3D"background-color:rgb(255,255,255);line-height:1.38;margin-top:0=
pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial"><span style=3D=
"font-size:10.6667px;white-space:pre-wrap">This email and all data transmit=
ted with it contains confidential and/or proprietary information intended s=
olely for the use of individual(s) authorized to receive it. If you are not=
 an intended and authorized recipient you are hereby notified of any use, d=
isclosure, copying or distribution of the information included in this tran=
smission is prohibited and may be unlawful. Please immediately notify the s=
ender by replying to this email and then delete it from your system.</span>=
</font></p></span></div>
</blockquote></div>

--0000000000007938c505b97f0376--


From nobody Fri Jan 22 12:35:14 2021
Return-Path: <tjw.ietf@gmail.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 533B33A14EB for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 12:35:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kZJFizoof0KH for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 12:35:07 -0800 (PST)
Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1867D3A14E9 for <dmarc@ietf.org>; Fri, 22 Jan 2021 12:35:07 -0800 (PST)
Received: by mail-oi1-x230.google.com with SMTP id x137so6193705oix.11 for <dmarc@ietf.org>; Fri, 22 Jan 2021 12:35:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kTnJfWaApVmeF5sP6tdjCF9qD24FXMNWJrRSs77zFN8=; b=egQv0izODZ2jwXfPusmRDDNmQacb3VlE9NaaRpM3xa1D0AYCPCzeSIgzKu1jnKS3qn eLzL5jWHVYMj8A7dFzsDNX46fYAg7MRJjFvJ8ENOWsxQt19Jl5rAoZjqRROpsXIOyFpn eHsIWKgtgy6XfV0uGvCFKDCAtXCfiQ/VO8TwTZHTfanhb0EfTHmNxzM7euEhPmhDHbEZ yeVs5yiOb6WlQqfRGoR89VOcmYScxlErNFTvvI/RETQGWKHQiBOn7oE4/RJGyr2igY3N uvIetVGILEB1nCcM5uT+QSbMiuxsuaIbBaE4yYTLYaYNbYF1uNfImEnj/wOPXRz7CLLv VleA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kTnJfWaApVmeF5sP6tdjCF9qD24FXMNWJrRSs77zFN8=; b=FkqlRhS8NE89RPyffsRe0JkVSWkZOTtQ3Ob2AvISdN4C5qBEPHxKKzF9swprIWD/E6 AUjrQkFpwJQfDkFFJZG04V3QtQL7JeCQsk+0IKK8q14EzBIX6UjvXkVFR8faVMYIIzeQ 7t6gL2WAOd0BYgJGyKNHVZY4QV5EwVeppRXftzkm3SlXoW+HPAERFfnP5A2L8tarrrnQ yHtWKohny9VIsPXU9lqtvEKArqyfrbsfJxEL3SBSWM1JjjBrA0Cnst3MlJTVGiNV/g4P i98+vHEjvBrfzC+zyao8KlYnU5nQPNo9sulT8S3zitY2THNua2n5VaT4cglcGlBdVdBg q7RQ==
X-Gm-Message-State: AOAM531M8pV7DTaZwVxpyTtqBfAEf4gvg1w5SQ0it/r0mLd8zX42nzi/ 2jveEigw3Aj4RBbOSmlycb1dzhazaB1HItEVg3M=
X-Google-Smtp-Source: ABdhPJyRhyUncFet3C5ATV9Z2/Wns7gVPW/b7ExayBaTDqspIycVQ8RsfihPELLQU7YYS+TuA7WkIBTQj9WsLCqkhHk=
X-Received: by 2002:aca:54d1:: with SMTP id i200mr4420503oib.21.1611347706242;  Fri, 22 Jan 2021 12:35:06 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com>
In-Reply-To: <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 22 Jan 2021 15:34:55 -0500
Message-ID: <CADyWQ+FvLx_dZc8e7cLdtSeeEF4Ba2toDic1SAbsbqX0GBCvmA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/mixed; boundary="000000000000a4a38d05b9831fd3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/kuQINDJiySP5vjRPIL45gjn_8KQ>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 22 Jan 2021 20:35:12 -0000

--000000000000a4a38d05b9831fd3
Content-Type: multipart/alternative; boundary="000000000000a4a38705b9831fd1"

--000000000000a4a38705b9831fd1
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 19, 2021 at 1:43 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> In the interests of getting this document on its way, I'd like to suggest
> the following edits in response to Dale's most recent message.  If the
> working group concurs, we can finally get this out to Last Call.
>
> My goal as an AD here is just to get the GenART feedback addressed, but
> the text is being submitted as a WG contribution for discussion and
> consensus consideration, not as a demand.   Please process accordingly; I
> believe the agreement is to do another WGLC on the document before it goes
> on its way, so the sooner consensus is reached on all of this, the sooner
> it goes.
>
> First, a suggestion of my own that I think I saw elsewhere, but it's not
> in Dale's reply: In several places there's a reference to "DMARC
> [RFC7489]".  That's appropriate the first time the reference is made, but I
> think after that you can just say "DMARC" when referring to the protocol
> generally, or to "RFC 7489" when you need to make a specific section or
> text reference.  They don't need to appear together everywhere.
>
> I think Dave's original feedback has been addressed -- good stuff -- so
> here are my suggestions around what's left:
>
> On Mon, Nov 16, 2020 at 7:16 PM Dale R. Worley <worley@ariadne.com> wrote:
>
>> My apologies for not tending to this promptly.
>>
>> In regard to the description of the experiments, the result criteria are
>> rather subjective, but I don't see that as a problem.  It does seem to
>> me that the title "PSD DMARC Privacy Concern Mitigation Experiment" is
>> too narrow, as only the 3rd experiment seems to be about privacy
>> issues.  A title as generic as "PSD DMARC Experiments" would be fine.
>>
>
> That's OK with me, or "DMARC PSD Experiments" or "DMARC PSD Experiment" if
> we want to treat it all as one common thing.
>
>
>> Although I note that even the -09 does not define "PSD", only "longest
>> PSD", even though "PSD" is used in section 2.5.  I suspect that PSD is
>> equal to "PSO Controlled Domain Name", though, or rather to some related
>> set of them.  That needs to be cleaned up in some way.
>>
>
> PSD appears to be well defined in Section 2.2.
>
> In section 3.5 and later there is the phrase "[this document] longest
>> PSD".  I'm not sure, but I think this is supposed to be "longest PSD
>> ([this document] section NN.NN)".
>>
>
> Agreed.
>
> I believe that my strongest critique was that section 1 is difficult to
>> understand if one does not already understand DMARC, and it does not
>> seem that the section has been revised.  Re-reading it, I notice that it
>> says "DMARC leverages public suffix lists to determine which domains are
>> organizational domains."  Ignoring that I dislike this use of
>> "leverage", a critical point is that it takes the existence of public
>> suffix lists a priori -- indeed, this use of "leverage" generally means
>> that the leveraged thing already exists and one is now extracting
>> additional benefit from that.  Whereas I've never heard of public suffix
>> lists and would naively expect that they are difficult to create and
>> maintain.  It might be better to say "DMARC uses public suffix lists to
>> determine which domains are organizational domains.  Public suffix lists
>> are obtained/maintained/distributed by ..."
>>
>
> Replace all of Section 1 with this (ignore funny line wrapping):
>
>    DMARC [RFC7489 <https://tools.ietf.org/html/rfc7489>] provides a mechanism for publishing organizational
>    policy information to email receivers.  DMARC allows policy to be
>    specified for both individual domains and for organizational domains
>    and their sub-domains within a single organization.
>
>    To determine the organizational domain for a message under evaluation,
>    and thus where to look for a policy statement, DMARC makes use of a Public Suffix List.
>    The process for doing this can be found in Section 3.2 of the DMARC specification.
>
>    DMARC as specified presumes that domain names present in a PSL are not
>    organizational domains and thus not subject to DMARC processing; domains
>    are either organizational domains, sub-domains of organizational
>    domains, or listed on a PSL.  For domains listed in a
>    PSL, i.e., TLDs and domains that exist between TLDs and
>    organization level domains, policy can only be published for the
>    exact domain.  No method is available for these domains to express
>    policy or receive feedback reporting for sub-domains.  This missing
>    method allows for the abuse of non-existent organizational-level
>    domains and prevents identification of domain abuse in email.
>
>    This document specifies experimental updates to the DMARC and PSL algorithm cited
>    above, in an attempt to mitigate this abuse.
>
>
Done

>
> Looking at the second paragraph of section 1, I notice that despite all
>> the special terms for classifying domain names in section 2, the example
>> in this section does not describe which of the domain names that it
>> mentions fall into which of these classes.  E.g. "tax.gov.example" is
>> said to be registered, but it looks like it is also the organizational
>> domain, and "gov.example" is its longest PSD.  It would also help to
>> mention that "tax.gov.example" is "registered at" "gov.example" to
>> introduce the details of the usage "registered at".
>>
>>     Suppose there exists a domain "tax.gov.example" (registered at
>>     "gov.example") ...
>>
>
> Introduce a new Section 1.1: "Example" with this:
>
>    As an example, imagine a country code TLD (ccTLD) which has public
>    subdomains for government and commercial use (".gov.example" and
>    ".com.example").  A PSL whose maintainer is aware of this country's domain structure
>    would include entries for both of these in the PSL, indicating that they are
>    PSDs below which registrations can occur.  Suppose further that there exists a domain
>    "tax.gov.example", registered within ".gov.example", that is
>    responsible for taxation in this imagined
>    country.
>
>    However, by exploiting the typically unauthenticated nature
>    of email, there are regular malicious campaigns to impersonate this
>    organization that use similar-looking ("cousin") domains such as
>    "t4x.gov.example".  Such domains are not registered.
>
>    Within the
>    ".gov.example" public suffix, use of DMARC has been mandated, so
>    "gov.example" publishes the following DMARC DNS record:
>
>    [remainder of -09's page 3, the example, unchanged]
>
>
done

> Introduce a new Section 1.2: "Discussion" comprising the remainder of -09's Section 1.  In the first paragraph, between "simple" and "extension", add "experimental".
>
> A suggestion for 2.4:
>
> NEW:
>
> The longest PSD is the Organizational Domain with one label removed.  It names the immediate parent node of the Organizational Domain in the DNS namespace tree.
>
>
Done

I also changed the title to "Experimental DMARC Extension for Public Suffix
Domains"

I need to go over the next batch.

I have the XML in my repo:
https://github.com/moonshiner/draft-ietf-dmarc-psd/
and will send a pull request when i've gone back over things.

I do attach the rfcdiff I created locally for folks.  that may help

big thanks Murray

--000000000000a4a38705b9831fd1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:monospace"><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Tue, Jan 19, 2021 at 1:43 AM Murray S. Kuc=
herawy &lt;<a href=3D"mailto:superuser@gmail.com" target=3D"_blank">superus=
er@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">In the interests of getting t=
his document on its way, I&#39;d like to suggest the following edits in res=
ponse to Dale&#39;s most recent message.=C2=A0 If the working group concurs=
, we can finally get this out to Last Call.</div><div dir=3D"ltr"><br></div=
><div>My goal as an AD here is just to get the GenART feedback addressed, b=
ut the text is being submitted as a WG contribution for discussion and cons=
ensus consideration, not as a demand.=C2=A0=C2=A0 Please process accordingl=
y; I believe the agreement is to do another WGLC on the document before it =
goes on its way, so the sooner consensus is reached on all of this, the soo=
ner it goes.<br></div><div><br></div><div>First, a suggestion of my own tha=
t I think I saw elsewhere, but it&#39;s not in Dale&#39;s reply: In several=
 places there&#39;s a reference to &quot;DMARC [RFC7489]&quot;.=C2=A0 That&=
#39;s appropriate the first time the reference is made, but I think after t=
hat you can just say &quot;DMARC&quot; when referring to the protocol gener=
ally, or to &quot;RFC 7489&quot; when you need to make a specific section o=
r text reference.=C2=A0 They don&#39;t need to appear together everywhere.<=
/div><div><br></div><div>I think Dave&#39;s original feedback has been addr=
essed -- good stuff -- so here are my suggestions around what&#39;s left:<b=
r></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">On Mon, Nov 16, 2020 at 7:16 PM Dale R. Worley &lt;<a href=3D"mailto:worl=
ey@ariadne.com" target=3D"_blank">worley@ariadne.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">My apologies for not te=
nding to this promptly.<br>
<br>
In regard to the description of the experiments, the result criteria are<br=
>
rather subjective, but I don&#39;t see that as a problem.=C2=A0 It does see=
m to<br>
me that the title &quot;PSD DMARC Privacy Concern Mitigation Experiment&quo=
t; is<br>
too narrow, as only the 3rd experiment seems to be about privacy<br>
issues.=C2=A0 A title as generic as &quot;PSD DMARC Experiments&quot; would=
 be fine.<br></blockquote><div><br></div><div>That&#39;s OK with me, or &qu=
ot;DMARC PSD Experiments&quot; or &quot;DMARC PSD Experiment&quot; if we wa=
nt to treat it all as one common thing.<br></div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
Although I note that even the -09 does not define &quot;PSD&quot;, only &qu=
ot;longest<br>
PSD&quot;, even though &quot;PSD&quot; is used in section 2.5.=C2=A0 I susp=
ect that PSD is<br>
equal to &quot;PSO Controlled Domain Name&quot;, though, or rather to some =
related<br>
set of them.=C2=A0 That needs to be cleaned up in some way.<br></blockquote=
><div><br></div><div>PSD appears to be well defined in Section 2.2.</div><d=
iv> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
In section 3.5 and later there is the phrase &quot;[this document] longest<=
br>
PSD&quot;.=C2=A0 I&#39;m not sure, but I think this is supposed to be &quot=
;longest PSD<br>
([this document] section NN.NN)&quot;.<br></blockquote><div><br></div><div>=
Agreed.</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
I believe that my strongest critique was that section 1 is difficult to<br>
understand if one does not already understand DMARC, and it does not<br>
seem that the section has been revised.=C2=A0 Re-reading it, I notice that =
it<br>
says &quot;DMARC leverages public suffix lists to determine which domains a=
re<br>
organizational domains.&quot;=C2=A0 Ignoring that I dislike this use of<br>
&quot;leverage&quot;, a critical point is that it takes the existence of pu=
blic<br>
suffix lists a priori -- indeed, this use of &quot;leverage&quot; generally=
 means<br>
that the leveraged thing already exists and one is now extracting<br>
additional benefit from that.=C2=A0 Whereas I&#39;ve never heard of public =
suffix<br>
lists and would naively expect that they are difficult to create and<br>
maintain.=C2=A0 It might be better to say &quot;DMARC uses public suffix li=
sts to<br>
determine which domains are organizational domains.=C2=A0 Public suffix lis=
ts<br>
are obtained/maintained/distributed by ...&quot;<br></blockquote><div><br><=
/div><div>Replace all of Section 1 with this (ignore funny line wrapping):<=
br></div><div>
<pre>   DMARC [<a href=3D"https://tools.ietf.org/html/rfc7489" title=3D"&qu=
ot;Domain-based Message Authentication, Reporting, and Conformance (DMARC)&=
quot;" target=3D"_blank">RFC7489</a>] provides a mechanism for publishing o=
rganizational
   policy information to email receivers.  DMARC allows policy to be
   specified for both individual domains and for organizational domains
   and their sub-domains within a single organization.<br><br>   To determi=
ne the organizational domain for a message under evaluation,<br>   and thus=
 where to look for a policy statement, DMARC makes use of a Public Suffix L=
ist.<br>   The process for doing this can be found in Section 3.2 of the DM=
ARC specification.<br></pre><pre>   DMARC as specified presumes that domain=
 names present in a PSL are not
   organizational domains and thus not subject to DMARC processing; domains
   are either organizational domains, sub-domains of organizational
   domains, or listed on a PSL.  For domains listed in a
   PSL, i.e., TLDs and domains that exist between TLDs and
   organization level domains, policy can only be published for the
   exact domain.  No method is available for these domains to express
   policy or receive feedback reporting for sub-domains.  This missing
   method allows for the abuse of non-existent organizational-level
   domains and prevents identification of domain abuse in email.<br><br></p=
re><pre>   This document specifies experimental updates to the DMARC and PS=
L algorithm cited<br>   above, in an attempt to mitigate this abuse.<br></p=
re></div></div></div></blockquote><div><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:monospace">Done</div><div class=3D"gmail_default" s=
tyle=3D"font-family:monospace"></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div><pre></pre>

</div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Looking at the second paragraph of section 1, I notice that despite all<br>
the special terms for classifying domain names in section 2, the example<br=
>
in this section does not describe which of the domain names that it<br>
mentions fall into which of these classes.=C2=A0 E.g. &quot;tax.gov.example=
&quot; is<br>
said to be registered, but it looks like it is also the organizational<br>
domain, and &quot;gov.example&quot; is its longest PSD.=C2=A0 It would also=
 help to<br>
mention that &quot;tax.gov.example&quot; is &quot;registered at&quot; &quot=
;gov.example&quot; to<br>
introduce the details of the usage &quot;registered at&quot;.<br>
<br>
=C2=A0 =C2=A0 Suppose there exists a domain &quot;tax.gov.example&quot; (re=
gistered at<br>
=C2=A0 =C2=A0 &quot;gov.example&quot;) ...<br></blockquote><div><br></div><=
div>Introduce a new Section 1.1: &quot;Example&quot; with this:<br>
<pre>   As an example, imagine a country code TLD (ccTLD) which has public
   subdomains for government and commercial use (&quot;.gov.example&quot; a=
nd
   &quot;.com.example&quot;).  A PSL whose maintainer is aware of this coun=
try&#39;s domain structure<br>   would include entries for both of these in=
 the PSL, indicating that they are<br>   PSDs below which registrations can=
 occur.  Suppose further that there exists a domain
   &quot;tax.gov.example&quot;, registered within &quot;.gov.example&quot;,=
 that is<br>   responsible for taxation in this imagined
   country.<br><br>   However, by exploiting the typically unauthenticated =
nature
   of email, there are regular malicious campaigns to impersonate this
   organization that use similar-looking (&quot;cousin&quot;) domains such =
as
   &quot;t4x.gov.example&quot;.  Such domains are not registered.<br></pre>=
<pre>   Within the
   &quot;.gov.example&quot; public suffix, use of DMARC has been mandated, =
so
   &quot;gov.example&quot; publishes the following DMARC DNS record:<br></p=
re><pre>   [remainder of -09&#39;s page 3, the example, unchanged]<br></pre=
></div></div></div></blockquote><div><br></div><div class=3D"gmail_default"=
 style=3D"font-family:monospace">done</div><div class=3D"gmail_default" sty=
le=3D"font-family:monospace"></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div><pre><span styl=
e=3D"font-family:arial,sans-serif">Introduce a new Section 1.2: &quot;Discu=
ssion&quot; comprising the remainder of -09&#39;s Section 1.  In the first =
paragraph, between &quot;simple&quot; and &quot;extension&quot;, add &quot;=
experimental&quot;.<br></span></pre><pre><span style=3D"font-family:arial,s=
ans-serif">A suggestion for 2.4:<br><br>NEW:<br><br><span style=3D"font-fam=
ily:monospace"><span>The longest PSD is the Organizat<span class=3D"gmail_d=
efault" style=3D"font-family:monospace"></span>ional Domain with one label =
removed.</span>  It names the immediate parent node of the Organizational D=
omain in the DNS namespace tree.</span></span></pre></div></div></div></blo=
ckquote><div><br></div><div class=3D"gmail_default" style=3D"font-family:mo=
nospace">Done</div><div class=3D"gmail_default" style=3D"font-family:monosp=
ace"><br></div><div class=3D"gmail_default" style=3D""><font face=3D"monosp=
ace">I also changed the title to=C2=A0&quot;Experimental DMARC Extension fo=
r Public Suffix Domains&quot;</font></div><div class=3D"gmail_default" styl=
e=3D""><font face=3D"monospace"><br></font></div><div class=3D"gmail_defaul=
t" style=3D""><font face=3D"monospace">I need to go over the next batch.</f=
ont></div><div class=3D"gmail_default" style=3D""><font face=3D"monospace">=
<br></font></div><div class=3D"gmail_default" style=3D""><font face=3D"mono=
space">I have the XML in my repo:=C2=A0=C2=A0<a href=3D"https://github.com/=
moonshiner/draft-ietf-dmarc-psd/">https://github.com/moonshiner/draft-ietf-=
dmarc-psd/</a><br>and will send a pull request when i&#39;ve gone back over=
 things.</font></div><div class=3D"gmail_default" style=3D""><font face=3D"=
monospace"><br></font></div><div class=3D"gmail_default" style=3D""><font f=
ace=3D"monospace">I do attach the rfcdiff I created locally for folks.=C2=
=A0 that may help</font></div><div class=3D"gmail_default" style=3D""><font=
 face=3D"monospace"><br></font></div><div class=3D"gmail_default" style=3D"=
"><font face=3D"monospace">big thanks Murray</font></div></div></div>

--000000000000a4a38705b9831fd1--

--000000000000a4a38d05b9831fd3
Content-Type: text/html; charset="US-ASCII"; 
 name="draft-ietf-dmarc-psd-09.tx-from-f.ou.diff.html"
Content-Disposition: attachment; 
 filename="draft-ietf-dmarc-psd-09.tx-from-f.ou.diff.html"
Content-Transfer-Encoding: base64
Content-ID: <f_kk8qppzx0>
X-Attachment-Id: f_kk8qppzx0

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5zaXRpb25h
bC5kdGQiPiAKPCEtLSBHZW5lcmF0ZWQgYnkgcmZjZGlmZiAxLjM0OiByZmNkaWZmICAtLT4gCjwh
LS0gPCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlv
bmFsIiA+IC0tPgo8IS0tIFN5c3RlbTogRGFyd2luIGJvaWxlci5sb2NhbCAyMC4yLjAgRGFyd2lu
IEtlcm5lbCBWZXJzaW9uIDIwLjIuMDogV2VkIERlYyAgMiAyMDozOTo1OSBQU1QgMjAyMDsgcm9v
dDp4bnUtNzE5NS42MC43NX4xL1JFTEVBU0VfWDg2XzY0IHg4Nl82NCAtLT4gCjwhLS0gVXNpbmcg
YXdrOiAvb3B0L2xvY2FsL2Jpbi9nYXdrOiBHTlUgQXdrIDUuMS4wLCBBUEk6IDMuMCAtLT4gCjwh
LS0gVXNpbmcgZGlmZjogL3Vzci9iaW4vZGlmZjogZGlmZiAoR05VIGRpZmZ1dGlscykgMi44LjEg
LS0+IAo8IS0tIFVzaW5nIHdkaWZmOiAvb3B0L2xvY2FsL2Jpbi93ZGlmZjogd2RpZmYgKEdOVSB3
ZGlmZikgMS4yLjIgLS0+IAo8aHRtbD4gCjxoZWFkPiAKICA8bWV0YSBodHRwLWVxdWl2PSJDb250
ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1pc28tODg1OS0xIiAvPiAKICA8
bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVN0eWxlLVR5cGUiIGNvbnRlbnQ9InRleHQvY3NzIiAv
PiAKICA8dGl0bGU+RGlmZjogZi5vdXQgLSBkcmFmdC1pZXRmLWRtYXJjLXBzZC0wOS50eHQ8L3Rp
dGxlPiAKICA8c3R5bGUgdHlwZT0idGV4dC9jc3MiPiAKICAgIGJvZHkgICAgeyBtYXJnaW46IDAu
NGV4OyBtYXJnaW4tcmlnaHQ6IGF1dG87IH0gCiAgICB0ciAgICAgIHsgfSAKICAgIHRkICAgICAg
eyB3aGl0ZS1zcGFjZTogcHJlOyBmb250LWZhbWlseTogbW9ub3NwYWNlOyB2ZXJ0aWNhbC1hbGln
bjogdG9wOyBmb250LXNpemU6IDAuODZlbTt9IAogICAgdGggICAgICB7IGZvbnQtc2l6ZTogMC44
NmVtOyB9IAogICAgLnNtYWxsICB7IGZvbnQtc2l6ZTogMC42ZW07IGZvbnQtc3R5bGU6IGl0YWxp
YzsgZm9udC1mYW1pbHk6IFZlcmRhbmEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgfSAKICAgIC5s
ZWZ0ICAgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRUVFOyB9IAogICAgLnJpZ2h0ICB7IGJhY2tncm91
bmQtY29sb3I6ICNGRkY7IH0gCiAgICAuZGlmZiAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0NDRjsg
fSAKICAgIC5sYmxvY2sgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQkZCOyB9IAogICAgLnJibG9jayB7
IGJhY2tncm91bmQtY29sb3I6ICNGRjg7IH0gCiAgICAuaW5zZXJ0IHsgYmFja2dyb3VuZC1jb2xv
cjogIzhGRjsgfSAKICAgIC5kZWxldGUgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUNGOyB9IAogICAg
LnZvaWQgICB7IGJhY2tncm91bmQtY29sb3I6ICNGRkI7IH0gCiAgICAuY29udCAgIHsgYmFja2dy
b3VuZC1jb2xvcjogI0VFRTsgfSAKICAgIC5saW5lYnIgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUFB
OyB9IAogICAgLmxpbmVubyB7IGNvbG9yOiByZWQ7IGJhY2tncm91bmQtY29sb3I6ICNGRkY7IGZv
bnQtc2l6ZTogMC43ZW07IHRleHQtYWxpZ246IHJpZ2h0OyBwYWRkaW5nOiAwIDJweDsgfSAKICAg
IC5lbGlwc2lzeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUFBOyB9IAogICAgLmxlZnQgLmNvbnQgeyBi
YWNrZ3JvdW5kLWNvbG9yOiAjREREOyB9IAogICAgLnJpZ2h0IC5jb250IHsgYmFja2dyb3VuZC1j
b2xvcjogI0VFRTsgfSAKICAgIC5sYmxvY2sgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjOUQ5
OyB9IAogICAgLnJibG9jayAuY29udCB7IGJhY2tncm91bmQtY29sb3I6ICNERDY7IH0gCiAgICAu
aW5zZXJ0IC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogIzBERDsgfSAKICAgIC5kZWxldGUgLmNv
bnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjOEFEOyB9IAogICAgLnN0YXRzLCAuc3RhdHMgdGQsIC5z
dGF0cyB0aCB7IGJhY2tncm91bmQtY29sb3I6ICNFRUU7IHBhZGRpbmc6IDJweCAwOyB9IAogIDwv
c3R5bGU+IAo8L2hlYWQ+IAo8Ym9keSA+IAogIDx0YWJsZSBib3JkZXI9IjAiIGNlbGxwYWRkaW5n
PSIwIiBjZWxsc3BhY2luZz0iMCI+IAogIDx0ciBiZ2NvbG9yPSJvcmFuZ2UiPjx0aD48L3RoPjx0
aD4mbmJzcDtmLm91dCZuYnNwOzwvdGg+PHRoPiA8L3RoPjx0aD4mbmJzcDtkcmFmdC1pZXRmLWRt
YXJjLXBzZC0wOS50eHQmbmJzcDs8L3RoPjx0aD48L3RoPjwvdHI+IAogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIFMuIEtpdHRlcm1hbjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIFMuIEtpdHRlcm1hbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5JbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIGZUTEQgUmVnaXN0cnkgU2VydmljZXM8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij5JbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIGZUTEQgUmVnaXN0cnkgU2VydmljZXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDAxIiAv
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+SW50ZW5kZWQgc3RhdHVzOiBFeHBlcmltZW50YWwgICAgICAg
ICAgICAgICAgICAgICAgICAgIFNlcHRlbWJlciA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xLDwvc3Bh
bj4gMjAyMDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj5JbnRlbmRlZCBzdGF0dXM6
IEV4cGVyaW1lbnRhbCAgICAgICAgICAgICAgICAgICAgICAgICBTZXB0ZW1iZXIgPHNwYW4gY2xh
c3M9Imluc2VydCI+MjIsPC9zcGFuPiAyMDIwPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+RXhwaXJlczogTWFyY2ggPHNwYW4gY2xhc3M9ImRl
bGV0ZSI+NSw8L3NwYW4+IDIwMjE8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+RXhw
aXJlczogTWFyY2ggPHNwYW4gY2xhc3M9Imluc2VydCI+MjYsPC9zcGFuPiAyMDIxPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlmZjAwMDIiIC8+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj4gICAgICAgICA8c3BhbiBjbGFzcz0iZGVsZXRlIj5FeHBlcmltZW50YWw8L3Nw
YW4+IERNQVJDIEV4dGVuc2lvbiBGb3IgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+UHVibGljPC9zcGFu
PiBTdWZmaXggPHNwYW4gY2xhc3M9ImRlbGV0ZSI+RG9tYWluczwvc3Bhbj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+RE1BUkMgPHNwYW4gY2xhc3M9Imluc2VydCI+KERvbWFpbi1i
YXNlZCBNZXNzYWdlIEF1dGhlbnRpY2F0aW9uLCBSZXBvcnRpbmcsIGFuZCBDb25mb3JtYW5jZSk8
L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgICAgICAgIEV4
dGVuc2lvbiBGb3IgPHNwYW4gY2xhc3M9Imluc2VydCI+UFNEcyAoUHVibGljPC9zcGFuPiBTdWZm
aXggPHNwYW4gY2xhc3M9Imluc2VydCI+RG9tYWlucyk8L3NwYW4+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAg
ICAgIGRyYWZ0LWlldGYtZG1hcmMtcHNkLTA5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgICAgICAgICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1kbWFyYy1wc2QtMDk8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPkFic3RyYWN0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+QWJzdHJhY3Q8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIERNQVJDIChEb21h
aW4tYmFzZWQgTWVzc2FnZSBBdXRoZW50aWNhdGlvbiwgUmVwb3J0aW5nLCBhbmQ8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBETUFSQyAoRG9tYWluLWJhc2VkIE1lc3NhZ2UgQXV0
aGVudGljYXRpb24sIFJlcG9ydGluZywgYW5kPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIENvbmZvcm1hbmNlKSBpcyBhIHNjYWxhYmxlIG1l
Y2hhbmlzbSBieSB3aGljaCBhIG1haWwtb3JpZ2luYXRpbmc8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBDb25mb3JtYW5jZSkgaXMgYSBzY2FsYWJsZSBtZWNoYW5pc20gYnkgd2hp
Y2ggYSBtYWlsLW9yaWdpbmF0aW5nPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG9yZ2FuaXphdGlvbiBjYW4gZXhwcmVzcyBkb21haW4tbGV2
ZWwgcG9saWNpZXMgYW5kIHByZWZlcmVuY2VzIGZvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIG9yZ2FuaXphdGlvbiBjYW4gZXhwcmVzcyBkb21haW4tbGV2ZWwgcG9saWNpZXMg
YW5kIHByZWZlcmVuY2VzIGZvcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBtZXNzYWdlIHZhbGlkYXRpb24sIGRpc3Bvc2l0aW9uLCBhbmQg
cmVwb3J0aW5nLCB0aGF0IGEgbWFpbC1yZWNlaXZpbmc8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBtZXNzYWdlIHZhbGlkYXRpb24sIGRpc3Bvc2l0aW9uLCBhbmQgcmVwb3J0aW5n
LCB0aGF0IGEgbWFpbC1yZWNlaXZpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgb3JnYW5pemF0aW9uIGNhbiB1c2UgdG8gaW1wcm92ZSBt
YWlsIGhhbmRsaW5nLiAgVGhlIGRlc2lnbiBvZiBETUFSQzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIG9yZ2FuaXphdGlvbiBjYW4gdXNlIHRvIGltcHJvdmUgbWFpbCBoYW5kbGlu
Zy4gIFRoZSBkZXNpZ24gb2YgRE1BUkM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcHJlc3VtZXMgdGhhdCBkb21haW4gbmFtZXMgcmVwcmVz
ZW50IGVpdGhlciBub2RlcyBpbiB0aGUgdHJlZSBiZWxvdzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIHByZXN1bWVzIHRoYXQgZG9tYWluIG5hbWVzIHJlcHJlc2VudCBlaXRoZXIg
bm9kZXMgaW4gdGhlIHRyZWUgYmVsb3c8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBiZ2NvbG9yPSJncmF5IiA+PHRkPjwvdGQ+PHRo
PjxhIG5hbWU9InBhcnQtbDIiIC8+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+
PGVtPiBwYWdlIDEsIGxpbmUgNDg8L2VtPjwvdGg+PHRoPiA8L3RoPjx0aD48YSBuYW1lPSJwYXJ0
LXIyIiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxlbT4gcGFnZSAxLCBs
aW5lIDQ5PC9lbT48L3RoPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBJbnRlcm5ldC1EcmFmdHMg
YXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZzwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBk
b2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nPC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRhc2sgRm9yY2UgKElFVEYpLiAg
Tm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRoYXQgb3RoZXIg
Z3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQt
RHJhZnRzLiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC08L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBU
aGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0LTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBEcmFmdHMgaXMgYXQgaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kcmFmdHMvY3VycmVudC8uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgRHJhZnRzIGlzIGF0IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRz
L2N1cnJlbnQvLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgSW50ZXJuZXQtRHJhZnRz
IGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFm
dCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzPC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGFuZCBtYXkgYmUg
dXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYW5kIG1heSBiZSB1cGRhdGVkLCBy
ZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnk8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGltZS4gIEl0
IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2U8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0
ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtYXRlcmlhbCBvciB0byBjaXRl
IHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMg
IndvcmsgaW4gcHJvZ3Jlc3MuIjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxh
IG5hbWU9ImRpZmYwMDAzIiAvPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgVGhpcyBJbnRlcm5ldC1E
cmFmdCB3aWxsIGV4cGlyZSBvbiBNYXJjaCA8c3BhbiBjbGFzcz0iZGVsZXRlIj41PC9zcGFuPiwg
MjAyMS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgVGhpcyBJbnRlcm5ldC1E
cmFmdCB3aWxsIGV4cGlyZSBvbiBNYXJjaCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4yNjwvc3Bhbj4s
IDIwMjEuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5Db3B5cmlnaHQgTm90aWNlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Q29weXJpZ2h0IE5vdGljZTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgQ29weXJpZ2h0IChjKSAyMDIwIElFVEYgVHJ1c3QgYW5kIHRoZSBw
ZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgQ29weXJpZ2h0IChjKSAyMDIwIElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZp
ZWQgYXMgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIGRvY3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRzIHJlc2VydmVkLjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGRvY3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRz
IHJlc2VydmVkLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBp
cyBzdWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbDwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1Ag
NzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRG
IERvY3VtZW50czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFByb3Zpc2lvbnMg
UmVsYXRpbmcgdG8gSUVURiBEb2N1bWVudHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgKGh0dHBzOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNl
bnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIChodHRwczovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBl
ZmZlY3Qgb24gdGhlIGRhdGUgb2Y8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFz
ZSByZXZpZXcgdGhlc2UgZG9jdW1lbnRzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9j
dW1lbnRzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIGNhcmVmdWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVzdHJp
Y3Rpb25zIHdpdGggcmVzcGVjdDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGNh
cmVmdWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVzdHJpY3Rpb25zIHdp
dGggcmVzcGVjdDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICB0byB0aGlzIGRvY3VtZW50LiAgQ29kZSBDb21wb25lbnRzIGV4dHJhY3RlZCBm
cm9tIHRoaXMgZG9jdW1lbnQgbXVzdDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IHRvIHRoaXMgZG9jdW1lbnQuICBDb2RlIENvbXBvbmVudHMgZXh0cmFjdGVkIGZyb20gdGhpcyBk
b2N1bWVudCBtdXN0PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0IGFzIGRlc2Ny
aWJlZCBpbiBTZWN0aW9uIDQuZSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0IGFzIGRlc2NyaWJlZCBpbiBTZWN0
aW9uIDQuZSBvZjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICB0aGUgVHJ1c3QgTGVnYWwgUHJvdmlzaW9ucyBhbmQgYXJlIHByb3ZpZGVkIHdp
dGhvdXQgd2FycmFudHkgYXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aGUg
VHJ1c3QgTGVnYWwgUHJvdmlzaW9ucyBhbmQgYXJlIHByb3ZpZGVkIHdpdGhvdXQgd2FycmFudHkg
YXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgZGVzY3JpYmVkIGluIHRoZSBTaW1wbGlmaWVkIEJTRCBMaWNlbnNlLjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIGRlc2NyaWJlZCBpbiB0aGUgU2ltcGxpZmllZCBCU0QgTGlj
ZW5zZS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPlRhYmxlIG9mIENvbnRlbnRzPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+VGFibGUgb2YgQ29udGVudHM8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIDEuICBJbnRyb2R1Y3Rpb24gIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgMzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIDEuICBJbnRyb2R1Y3Rpb24gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuICAgMzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlmZjAwMDQiIC8+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj4gICAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPjEuMS4gIEV4YW1wbGUgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDM8L3NwYW4+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgICAg
MS4yLiAgRGlzY3Vzc2lvbiAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAgNDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIDIuICBU
ZXJtaW5vbG9neSBhbmQgRGVmaW5pdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAgNTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIDIuICBUZXJtaW5vbG9n
eSBhbmQgRGVmaW5pdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNTwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
IDIuMS4gIENvbnZlbnRpb25zIFVzZWQgaW4gVGhpcyBEb2N1bWVudCAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgIDU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDIuMS4gIENv
bnZlbnRpb25zIFVzZWQgaW4gVGhpcyBEb2N1bWVudCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
IDU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgICAyLjIuICBQdWJsaWMgU3VmZml4IERvbWFpbiAoUFNEKSAgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gICA1PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAyLjIu
ICBQdWJsaWMgU3VmZml4IERvbWFpbiAoUFNEKSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gICA1PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAwNSIgLz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAg
Mi4zLiAgT3JnYW5pemF0aW9uYWwgRG9tYWluIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+Njwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+ICAgICAyLjMuICBPcmdhbml6YXRpb25hbCBEb21haW4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij41PC9zcGFu
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PiAgICAgMi40LiAgTG9uZ2VzdCBQU0QgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+Njwvc3Bhbj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAyLjQuICBMb25nZXN0IFBTRCAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij41
PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgIDIuNS4gIFB1YmxpYyBTdWZmaXggT3BlcmF0b3IgKFBTTykgIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgIDY8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
IDIuNS4gIFB1YmxpYyBTdWZmaXggT3BlcmF0b3IgKFBTTykgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgIDY8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgICAyLjYuICBQU08gQ29udHJvbGxlZCBEb21haW4gTmFtZXMgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gICA2PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICAyLjYuICBQU08gQ29udHJvbGxlZCBEb21haW4gTmFtZXMgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gICA2PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgICAgMi43LiAgTm9uLWV4aXN0ZW50IERvbWFpbnMgIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgMi43LiAgTm9uLWV4aXN0ZW50IERvbWFpbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICAgNjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAzLiAgUFNEIERNQVJDIFVwZGF0ZXMgdG8gRE1BUkMgUmVxdWly
ZW1lbnRzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDY8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAzLiAgUFNEIERNQVJDIFVwZGF0ZXMgdG8gRE1BUkMgUmVxdWlyZW1lbnRzIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgIDY8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDA2IiAvPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xh
c3M9ImxibG9jayI+ICAgICAzLjEuICBHZW5lcmFsIFVwZGF0ZXMgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA8c3BhbiBjbGFzcz0iZGVsZXRlIj43PC9zcGFuPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDMuMS4gIEdlbmVyYWwgVXBkYXRl
cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDxzcGFuIGNsYXNz
PSJpbnNlcnQiPjY8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgICAzLjIuICBDaGFuZ2VzIGluIFNlY3Rpb24gNi4zICJHZW5l
cmFsIFJlY29yZCBGb3JtYXQiICAuIC4gLiAuIC4gICA8c3BhbiBjbGFzcz0iZGVsZXRlIj43PC9z
cGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDMuMi4gIENoYW5nZXMg
aW4gU2VjdGlvbiA2LjMgIkdlbmVyYWwgUmVjb3JkIEZvcm1hdCIgIC4gLiAuIC4gLiAgIDxzcGFu
IGNsYXNzPSJpbnNlcnQiPjY8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMy4zLiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDYuNSAi
RG9tYWluIE93bmVyIEFjdGlvbnMiIC4gLiAuIC4gLiAuICAgNzwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgMy4zLiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDYuNSAiRG9tYWluIE93
bmVyIEFjdGlvbnMiIC4gLiAuIC4gLiAuICAgNzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDMuNC4gIENoYW5nZXMgaW4gU2VjdGlvbiA2
LjYuMSAiRXh0cmFjdCBBdXRob3IgRG9tYWluIiAgLiAuIC4gLiAgIDc8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDMuNC4gIENoYW5nZXMgaW4gU2VjdGlvbiA2LjYuMSAiRXh0
cmFjdCBBdXRob3IgRG9tYWluIiAgLiAuIC4gLiAgIDc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDA3IiAv
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAzLjUuICBDaGFuZ2VzIGluIFNlY3Rpb24gNi42LjMg
IlBvbGljeSBEaXNjb3ZlcnkiIC4gLiAuIC4gLiAuIC4gICA8c3BhbiBjbGFzcz0iZGVsZXRlIj44
PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDMuNS4gIENoYW5n
ZXMgaW4gU2VjdGlvbiA2LjYuMyAiUG9saWN5IERpc2NvdmVyeSIgLiAuIC4gLiAuIC4gLiAgIDxz
cGFuIGNsYXNzPSJpbnNlcnQiPjc8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMy42LiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDcg
IkRNQVJDIEZlZWRiYWNrIiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgODwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgICAgMy42LiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDcgIkRNQVJDIEZl
ZWRiYWNrIiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgODwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICA0LiAgUHJpdmFjeSBDb25zaWRlcmF0aW9u
cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDg8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICA0LiAgUHJpdmFjeSBDb25zaWRlcmF0aW9ucyAgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDg8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDA4
IiAvPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICA0LjEuICBGZWVkYmFjayBsZWFrYWdlICAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA8c3BhbiBjbGFzcz0iZGVsZXRl
Ij45PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDQuMS4gIEZl
ZWRiYWNrIGxlYWthZ2UgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
IDxzcGFuIGNsYXNzPSJpbnNlcnQiPjg8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgNS4gIFNlY3VyaXR5IENvbnNpZGVyYXRp
b25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJk
ZWxldGUiPjEwPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA1LiAg
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjk8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgNi4gIElBTkEgQ29uc2lkZXJh
dGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNs
YXNzPSJkZWxldGUiPjEwPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4g
ICA2LiAgSUFOQSBDb25zaWRlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjk8L3NwYW4+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgNi4xLiAgU3ViZG9t
YWluIFBvbGljeSBUYWcgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgNi4xLiAgU3ViZG9tYWluIFBvbGlj
eSBUYWcgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICA3LiAgUmVmZXJl
bmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
MTA8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICA3LiAgUmVmZXJlbmNlcyAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTA8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICA3LjEu
ICBOb3JtYXRpdmUgUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gIDEwPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICA3LjEuICBOb3JtYXRp
dmUgUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEwPC90
ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZD48YSBuYW1lPSJkaWZmMDAwOSIgLz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgNy4yLiAgSW5m
b3JtYXRpdmUgUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8
c3BhbiBjbGFzcz0iZGVsZXRlIj4xMTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+ICAgICA3LjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjEwPC9zcGFuPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIEFwcGVu
ZGl4IEEuICBQU0QgRE1BUkMgUHJpdmFjeSBDb25jZXJuIE1pdGlnYXRpb24gRXhwZXJpbWVudCAg
LiAuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4xMjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+ICAgQXBwZW5kaXggQS4gIFBTRCBETUFSQyBQcml2YWN5IENvbmNlcm4gTWl0
aWdhdGlvbiBFeHBlcmltZW50ICAuIC4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjExPC9zcGFuPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBB
cHBlbmRpeCBCLiAgRE1BUkMgUFNEIFJlZ2lzdHJ5IEV4YW1wbGVzICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgMTI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBcHBlbmRpeCBC
LiAgRE1BUkMgUFNEIFJlZ2lzdHJ5IEV4YW1wbGVzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
MTI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgICBCLjEuICBETUFSQyBQU0QgRE5TIFF1ZXJ5IFNlcnZpY2UgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gIDEyPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICBCLjEu
ICBETUFSQyBQU0QgRE5TIFF1ZXJ5IFNlcnZpY2UgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gIDEyPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgQi4yLiAgRE1BUkMgUHVibGljIFN1ZmZpeCBEb21haW4gKFBTRCkgUmVnaXN0cnkg
LiAuIC4gLiAuIC4gLiAuICAxMjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAg
Qi4yLiAgRE1BUkMgUHVibGljIFN1ZmZpeCBEb21haW4gKFBTRCkgUmVnaXN0cnkgLiAuIC4gLiAu
IC4gLiAuICAxMjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgIEIuMy4gIERNQVJDIFBTRCBQU0wgRXh0ZW5zaW9uIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgMTM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgIEIuMy4gIERNQVJDIFBTRCBQU0wgRXh0ZW5zaW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgMTM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgQXBwZW5kaXggQy4gIEltcGxlbWVudGF0aW9ucyAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgQXBwZW5kaXggQy4gIEltcGxlbWVudGF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gIDEzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgQy4xLiAgQXV0aGhlYWRlcnMgTW9kdWxlICAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgQy4xLiAgQXV0aGhlYWRlcnMgTW9kdWxlICAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuICAxMzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlmZjAwMTAiIC8+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj4gICAgIEMuMi4gIFpka2ltZmlsdGVyIE1vZHVsZSAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MTQ8L3NwYW4+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgQy4yLiAgWmRraW1maWx0ZXIgTW9k
dWxlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBjbGFzcz0i
aW5zZXJ0Ij4xMzwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGJsb2NrIj4gICBBY2tub3dsZWRnZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MTQ8L3Nw
YW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIEFja25vd2xlZGdlbWVudHMg
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA8c3BhbiBj
bGFzcz0iaW5zZXJ0Ij4xMzwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgQXV0aG9yJ3MgQWRkcmVzcyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE0PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgQXV0aG9yJ3MgQWRkcmVzcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE0PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4x
LiAgSW50cm9kdWN0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+MS4gIEludHJv
ZHVjdGlvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgRE1BUkMgW1JGQzc0ODldIHBy
b3ZpZGVzIGEgbWVjaGFuaXNtIGZvciBwdWJsaXNoaW5nIG9yZ2FuaXphdGlvbmFsPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgRE1BUkMgW1JGQzc0ODldIHByb3ZpZGVzIGEgbWVj
aGFuaXNtIGZvciBwdWJsaXNoaW5nIG9yZ2FuaXphdGlvbmFsPC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHBvbGljeSBpbmZvcm1hdGlvbiB0
byBlbWFpbCByZWNlaXZlcnMuICBETUFSQyBhbGxvd3MgcG9saWN5IHRvIGJlPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcG9saWN5IGluZm9ybWF0aW9uIHRvIGVtYWlsIHJlY2Vp
dmVycy4gIERNQVJDIGFsbG93cyBwb2xpY3kgdG8gYmU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgc3BlY2lmaWVkIGZvciBib3RoIGluZGl2
aWR1YWwgZG9tYWlucyBhbmQgZm9yIG9yZ2FuaXphdGlvbmFsIGRvbWFpbnM8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBzcGVjaWZpZWQgZm9yIGJvdGggaW5kaXZpZHVhbCBkb21h
aW5zIGFuZCBmb3Igb3JnYW5pemF0aW9uYWwgZG9tYWluczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlmZjAwMTEi
IC8+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBhbmQgdGhlaXIgc3ViLWRvbWFpbnMgd2l0aGluIGEg
c2luZ2xlIG9yZ2FuaXphdGlvbi48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
YW5kIHRoZWlyIHN1Yi1kb21haW5zIHdpdGhpbiBhIHNpbmdsZSBvcmdhbml6YXRpb24uICA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5ETUFSQyBsZXZlcmFnZXM8L3NwYW4+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBw
dWJsaWMgc3VmZml4IGxpc3RzIHRvPC9zcGFuPiBkZXRlcm1pbmUgPHNwYW4gY2xhc3M9Imluc2Vy
dCI+d2hpY2ggZG9tYWlucyBhcmU8L3NwYW4+IG9yZ2FuaXphdGlvbmFsPC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgPHNwYW4gY2xhc3M9
ImRlbGV0ZSI+VG88L3NwYW4+IGRldGVybWluZSA8c3BhbiBjbGFzcz0iZGVsZXRlIj50aGU8L3Nw
YW4+IG9yZ2FuaXphdGlvbmFsIDxzcGFuIGNsYXNzPSJkZWxldGUiPmRvbWFpbiBmb3IgYSBtZXNz
YWdlIHVuZGVyPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5kb21haW5zLiAgSXQ8L3NwYW4+IHByZXN1bWVzIHRoYXQgPHNwYW4g
Y2xhc3M9Imluc2VydCI+cHVibGljIHN1ZmZpeCBsaXN0IGxpc3RlZCBkb21haW5zPC9zcGFuPiBh
cmUgbm90PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgZXZhbHVhdGlvbiwgYW5kIHRodXMgd2hlcmUg
dG8gbG9vayBmb3IgYSBwb2xpY3kgc3RhdGVtZW50LCBETUFSQzwvc3Bhbj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+ICAgb3JnYW5pemF0aW9uYWwgZG9tYWlucyBhbmQgbm90IHN1
YmplY3QgdG8gRE1BUkMgcHJvY2Vzc2luZzsgZG9tYWluczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAg
IG1ha2VzIHVzZSBvZiBhIFB1YmxpYyBTdWZmaXggTGlzdC4gIFRoZSBwcm9jZXNzIGZvciBkb2lu
ZyB0aGlzIGNhbiBiZTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
YXJlIGVpdGhlciBvcmdhbml6YXRpb25hbCBkb21haW5zLCBzdWItZG9tYWlucyBvZiBvcmdhbml6
YXRpb25hbDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
YmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIGZvdW5kIGluIFNlY3Rpb24gMy4yIG9mIHRo
ZSBETUFSQyBzcGVjaWZpY2F0aW9uLjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+ICAgZG9tYWlucywgb3IgbGlzdGVkIG9uIGEgPHNwYW4gY2xhc3M9Imluc2VydCI+cHVi
bGljIHN1ZmZpeCBsaXN0Ljwvc3Bhbj4gIEZvciBkb21haW5zIGxpc3RlZCBpbiBhPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xh
c3M9ImRlbGV0ZSI+PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA8
c3BhbiBjbGFzcz0iaW5zZXJ0Ij5wdWJsaWMgc3VmZml4IGxpc3QsIGkuZS48L3NwYW4+IFRMRHMg
YW5kIGRvbWFpbnMgdGhhdCBleGlzdCBiZXR3ZWVuIFRMRHMgYW5kPC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0
ZSI+ICAgRE1BUkMgYXMgc3BlY2lmaWVkPC9zcGFuPiBwcmVzdW1lcyB0aGF0IDxzcGFuIGNsYXNz
PSJkZWxldGUiPmRvbWFpbiBuYW1lcyBwcmVzZW50IGluIGEgUFNMPC9zcGFuPiBhcmU8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgb3JnYW5pemF0aW9uIGxldmVsIGRvbWFpbnMs
IHBvbGljeSBjYW4gb25seSBiZSBwdWJsaXNoZWQgZm9yIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIG5vdCBvcmdhbml6YXRpb25h
bCBkb21haW5zIGFuZCA8c3BhbiBjbGFzcz0iZGVsZXRlIj50aHVzPC9zcGFuPiBub3Qgc3ViamVj
dCB0byBETUFSQyBwcm9jZXNzaW5nOzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4g
ICBleGFjdCBkb21haW4uICBObyBtZXRob2QgaXMgYXZhaWxhYmxlIGZvciB0aGVzZSBkb21haW5z
IHRvIGV4cHJlc3M8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj4gICBkb21haW5zIGFyZSBlaXRoZXIgb3JnYW5pemF0aW9uYWwgZG9tYWlucywg
c3ViLWRvbWFpbnMgb2Y8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgcG9saWN5
IG9yIHJlY2VpdmUgZmVlZGJhY2sgcmVwb3J0aW5nIGZvciBzdWItZG9tYWlucy4gIFRoaXMgbWlz
c2luZzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPiAgIG9yZ2FuaXphdGlvbmFsIGRvbWFpbnMsIG9yIGxpc3RlZCBvbiBhIDxzcGFuIGNsYXNz
PSJkZWxldGUiPlBTTC48L3NwYW4+ICBGb3IgZG9tYWlucyBsaXN0ZWQgaW4gYTwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBtZXRob2QgYWxsb3dzIGZvciB0aGUgYWJ1c2Ugb2Yg
bm9uLWV4aXN0ZW50IG9yZ2FuaXphdGlvbmFsLWxldmVsPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+
UFNMLCBpLmUuLDwvc3Bhbj4gVExEcyBhbmQgZG9tYWlucyB0aGF0IGV4aXN0IGJldHdlZW4gVExE
cyBhbmQgb3JnYW5pemF0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGRv
bWFpbnMgYW5kIHByZXZlbnRzIGlkZW50aWZpY2F0aW9uIG9mIGRvbWFpbiBhYnVzZSBpbiBlbWFp
bC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij4gICBsZXZlbCBkb21haW5zLCBwb2xpY3kgY2FuIG9ubHkgYmUgcHVibGlzaGVkIGZvciB0aGUg
ZXhhY3QgZG9tYWluLiAgTm88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgbWV0
aG9kIGlzIGF2YWlsYWJsZSBmb3IgdGhlc2UgZG9tYWlucyB0byBleHByZXNzIHBvbGljeSBvciBy
ZWNlaXZlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIGZlZWRiYWNrIHJlcG9y
dGluZyBmb3Igc3ViLWRvbWFpbnMuICBUaGlzIG1pc3NpbmcgbWV0aG9kIGFsbG93cyBmb3I8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgdGhlIGFidXNlIG9mIG5vbi1leGlzdGVu
dCBvcmdhbml6YXRpb25hbC1sZXZlbCBkb21haW5zIGFuZCBwcmV2ZW50czwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBpZGVudGlmaWNhdGlvbiBvZiBkb21haW4gYWJ1c2UgaW4g
ZW1haWwuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+
VGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgZXhwZXJpbWVudGFsIHVwZGF0ZXMgdG8gdGhlIERNQVJD
IGFuZCBQU0w8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNs
YXNzPSJkZWxldGUiPiAgIGFsZ29yaXRobSBjaXRlZCBhYm92ZSwgaW4gYW4gYXR0ZW1wdCB0byBt
aXRpZ2F0ZSB0aGlzIGFidXNlLjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4xLjEuICBFeGFtcGxlPC9zcGFuPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IEFzIGFuIGV4YW1wbGUsIGltYWdpbmUgYSBjb3VudHJ5IGNvZGUgVExEIChjY1RMRCkgd2hpY2gg
aGFzIHB1YmxpYzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEFzIGFuIGV4YW1w
bGUsIGltYWdpbmUgYSBjb3VudHJ5IGNvZGUgVExEIChjY1RMRCkgd2hpY2ggaGFzIHB1YmxpYzwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQ+PGEgbmFtZT0iZGlmZjAwMTIiIC8+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBzdWJkb21haW5z
IGZvciBnb3Zlcm5tZW50IGFuZCBjb21tZXJjaWFsIHVzZSA8c3BhbiBjbGFzcz0iZGVsZXRlIj4o
Ii5nb3YuZXhhbXBsZSI8L3NwYW4+IGFuZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij4gICBzdWJkb21haW5zIGZvciBnb3Zlcm5tZW50IGFuZCBjb21tZXJjaWFsIHVzZSA8c3BhbiBj
bGFzcz0iaW5zZXJ0Ij4oLmdvdi5leGFtcGxlPC9zcGFuPiBhbmQ8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA8c3BhbiBjbGFzcz0iZGVs
ZXRlIj4iLmNvbS5leGFtcGxlIikuICBBIFBTTCB3aG9zZSBtYWludGFpbmVyIGlzIGF3YXJlIG9m
IHRoaXMgY291bnRyeSdzPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4g
ICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4uY29tLmV4YW1wbGUpLjwvc3Bhbj4gIFN1cHBvc2UgdGhl
cmUgZXhpc3RzIGEgcmVnaXN0ZXJlZCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5kb21haW48L3NwYW4+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgZG9tYWluIHN0cnVjdHVyZXdvdWxkIGluY2x1ZGUgZW50
cmllcyBmb3IgYm90aCBvZiB0aGVzZSBpbiB0aGUgUFNMLDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgInRheC5nb3YuZXhhbXBs
ZSI8L3NwYW4+IHRoYXQgaXMgcmVzcG9uc2libGUgZm9yIHRheGF0aW9uIGluIHRoaXMgaW1hZ2lu
ZWQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBpbmRpY2F0aW5nIHRoYXQgdGhleSBhcmUgUFNEcyBi
ZWxvdyB3aGljaCByZWdpc3RyYXRpb25zIGNhbiBvY2N1ci48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyYmxvY2siPiAgIGNvdW50cnkuICBIb3dldmVyLCBieSBleHBsb2l0aW5nIHRo
ZSB0eXBpY2FsbHkgdW5hdXRoZW50aWNhdGVkIG5hdHVyZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFN1cHBvc2UgPHNwYW4gY2xhc3M9
ImRlbGV0ZSI+ZnVydGhlciB0aGF0PC9zcGFuPiB0aGVyZSBleGlzdHMgYSA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj5kb21haW4gInRheC5nb3YuZXhhbXBsZSIsPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmJsb2NrIj4gICBvZiBlbWFpbCwgdGhlcmUgYXJlIHJlZ3VsYXIgbWFsaWNpb3Vz
IGNhbXBhaWducyB0byBpbXBlcnNvbmF0ZSB0aGlzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgcmVnaXN0ZXJlZCA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj53aXRoaW4gIi5nb3YuZXhhbXBsZSIsPC9zcGFuPiB0aGF0IGlzIHJlc3BvbnNpYmxl
IGZvciB0YXhhdGlvbiBpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICB0aGlz
IGltYWdpbmVkIGNvdW50cnkuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICA8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgSG93ZXZlciwg
YnkgZXhwbG9pdGluZyB0aGUgdHlwaWNhbGx5IHVuYXV0aGVudGljYXRlZCBuYXR1cmUgb2YgZW1h
aWwsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIHRoZXJlIGFyZSByZWd1bGFy
IG1hbGljaW91cyBjYW1wYWlnbnMgdG8gaW1wZXJzb25hdGUgdGhpczwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgb3JnYW5pemF0aW9uIHRoYXQgdXNlIHNpbWlsYXItbG9va2luZyAo
ImNvdXNpbiIpIGRvbWFpbnMgc3VjaCBhczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIG9yZ2FuaXphdGlvbiB0aGF0IHVzZSBzaW1pbGFyLWxvb2tpbmcgKCJjb3VzaW4iKSBkb21h
aW5zIHN1Y2ggYXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDEzIiAvPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
ICAgInQ0eC5nb3YuZXhhbXBsZSIuICA8c3BhbiBjbGFzcz0iZGVsZXRlIj5TdWNoPC9zcGFuPiBk
b21haW5zIGFyZSBub3QgcmVnaXN0ZXJlZC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+ICAgInQ0eC5nb3YuZXhhbXBsZSIuICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5UaGVzZTwvc3Bh
bj4gZG9tYWlucyBhcmUgbm90IHJlZ2lzdGVyZWQuICBXaXRoaW4gdGhlPC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAiLmdvdi5leGFtcGxlIiBwdWJs
aWMgc3VmZml4LCB1c2Ugb2YgRE1BUkMgaGFzIGJlZW4gbWFuZGF0ZWQsIHNvPC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgV2l0aGluIHRo
ZSAiLmdvdi5leGFtcGxlIiBwdWJsaWMgc3VmZml4LCB1c2Ugb2YgRE1BUkMgaGFzIGJlZW48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgImdvdi5leGFtcGxlIiBwdWJsaXNoZXMg
dGhlIGZvbGxvd2luZyBETUFSQyBETlMgcmVjb3JkOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIG1hbmRhdGVkLCBzbyAiZ292LmV4YW1w
bGUiIHB1Ymxpc2hlcyB0aGUgZm9sbG93aW5nIERNQVJDIEROUyByZWNvcmQ6PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgX2Rt
YXJjLmdvdi5leGFtcGxlLiBJTiBUWFQgKCAidj1ETUFSQzE7IHA9cmVqZWN0OyAiPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgX2RtYXJjLmdvdi5leGFtcGxlLiBJTiBUWFQgKCAi
dj1ETUFSQzE7IHA9cmVqZWN0OyAiPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgInJ1YT1t
YWlsdG86ZG1jQGRtYXJjLnN2Yy5nb3YuZXhhbXBsZSIgKTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgInJ1YT1tYWlsdG86ZG1j
QGRtYXJjLnN2Yy5nb3YuZXhhbXBsZSIgKTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
VGhpcyBETUFSQyByZWNvcmQgcHJvdmlkZXMgcG9saWN5IGFuZCBhIHJlcG9ydGluZyBkZXN0aW5h
dGlvbiBmb3I8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGlzIERNQVJDIHJl
Y29yZCBwcm92aWRlcyBwb2xpY3kgYW5kIGEgcmVwb3J0aW5nIGRlc3RpbmF0aW9uIGZvcjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtYWls
IHNlbnQgZnJvbSBAZ292LmV4YW1wbGUuICBIb3dldmVyLCBkdWUgdG8gRE1BUkMncyBjdXJyZW50
IG1ldGhvZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG1haWwgc2VudCBmcm9t
IEBnb3YuZXhhbXBsZS4gIEhvd2V2ZXIsIGR1ZSB0byBETUFSQydzIGN1cnJlbnQgbWV0aG9kPC90
ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG9m
IGRpc2NvdmVyaW5nIGFuZCBhcHBseWluZyBwb2xpY3kgYXQgdGhlIG9yZ2FuaXphdGlvbmFsIGRv
bWFpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG9mIGRpc2NvdmVyaW5nIGFu
ZCBhcHBseWluZyBwb2xpY3kgYXQgdGhlIG9yZ2FuaXphdGlvbmFsIGRvbWFpbjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBsZXZlbCwgdGhl
IG5vbi1leGlzdGVudCBvcmdhbml6YXRpb25hbCBkb21haW4gb2YgQHQ0eC5nb3YuZXhhbXBsZTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGxldmVsLCB0aGUgbm9uLWV4aXN0ZW50
IG9yZ2FuaXphdGlvbmFsIGRvbWFpbiBvZiBAdDR4Lmdvdi5leGFtcGxlPC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGRvZXMgbm90IGFuZCBj
YW5ub3QgZmFsbCB1bmRlciBhIERNQVJDIHBvbGljeS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBkb2VzIG5vdCBhbmQgY2Fubm90IGZhbGwgdW5kZXIgYSBETUFSQyBwb2xpY3ku
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBEZWZlbnNpdmVseSByZWdpc3RlcmluZyBh
bGwgdmFyaWFudHMgb2YgInRheCIgaXMgb2J2aW91c2x5IG5vdCBhPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgRGVmZW5zaXZlbHkgcmVnaXN0ZXJpbmcgYWxsIHZhcmlhbnRzIG9m
ICJ0YXgiIGlzIG9idmlvdXNseSBub3QgYTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBzY2FsYWJsZSBzdHJhdGVneS4gIFRoZSBpbnRlbnQg
b2YgdGhpcyBzcGVjaWZpY2F0aW9uLCB0aGVyZWZvcmUsIGlzPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgc2NhbGFibGUgc3RyYXRlZ3kuICBUaGUgaW50ZW50IG9mIHRoaXMgc3Bl
Y2lmaWNhdGlvbiwgdGhlcmVmb3JlLCBpczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0byBlbmhhbmNlIHRoZSBETUFSQyBhbGdvcml0aG0g
YnkgZW5hYmxpbmcgYW4gYWdlbnQgcmVjZWl2aW5nIHN1Y2ggYTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIHRvIGVuaGFuY2UgdGhlIERNQVJDIGFsZ29yaXRobSBieSBlbmFibGlu
ZyBhbiBhZ2VudCByZWNlaXZpbmcgc3VjaCBhPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG1lc3NhZ2UgdG8gYmUgYWJsZSB0byBkZXRlcm1p
bmUgdGhhdCBhIHJlbGV2YW50IHBvbGljeSBpcyBwcmVzZW50IGF0PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgbWVzc2FnZSB0byBiZSBhYmxlIHRvIGRldGVybWluZSB0aGF0IGEg
cmVsZXZhbnQgcG9saWN5IGlzIHByZXNlbnQgYXQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgImdvdi5leGFtcGxlIiwgd2hpY2ggaXMgcHJl
Y2x1ZGVkIGJ5IHRoZSBjdXJyZW50IERNQVJDIGFsZ29yaXRobS48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAiZ292LmV4YW1wbGUiLCB3aGljaCBpcyBwcmVjbHVkZWQgYnkgdGhl
IGN1cnJlbnQgRE1BUkMgYWxnb3JpdGhtLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkPjxhIG5hbWU9ImRpZmYwMDE0IiAvPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9
ImRlbGV0ZSI+MS4yLiAgRGlzY3Vzc2lvbjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgVGhpcyBkb2N1bWVudCBwcm92aWRlcyBhIHNpbXBsZSBleHRlbnNpb24gdG8gRE1BUkMgW1JG
Qzc0ODldIHRvIGFsbG93PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhpcyBk
b2N1bWVudCBwcm92aWRlcyBhIHNpbXBsZSBleHRlbnNpb24gdG8gRE1BUkMgW1JGQzc0ODldIHRv
IGFsbG93PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIG9wZXJhdG9ycyBvZiBQdWJsaWMgU3VmZml4IERvbWFpbnMgKFBTRHMpIHRvOjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG9wZXJhdG9ycyBvZiBQdWJsaWMgU3VmZml4
IERvbWFpbnMgKFBTRHMpIHRvOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAgRXhw
cmVzcyBwb2xpY3kgYXQgdGhlIGxldmVsIG9mIHRoZSBQU0QgdGhhdCBjb3ZlcnMgYWxsPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbyAgRXhwcmVzcyBwb2xpY3kgYXQgdGhlIGxl
dmVsIG9mIHRoZSBQU0QgdGhhdCBjb3ZlcnMgYWxsPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIG9yZ2FuaXphdGlvbmFsIGRvbWFpbnMg
dGhhdCBkbyBub3QgZXhwbGljaXRseSBwdWJsaXNoIERNQVJDPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgb3JnYW5pemF0aW9uYWwgZG9tYWlucyB0aGF0IGRvIG5vdCBleHBs
aWNpdGx5IHB1Ymxpc2ggRE1BUkM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgcmVjb3JkczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgIHJlY29yZHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG8gIEV4
dGVuZHMgdGhlIERNQVJDIHBvbGljeSBxdWVyeSBmdW5jdGlvbmFsaXR5IHRvIGRldGVjdCBhbmQg
cHJvY2VzczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG8gIEV4dGVuZHMgdGhl
IERNQVJDIHBvbGljeSBxdWVyeSBmdW5jdGlvbmFsaXR5IHRvIGRldGVjdCBhbmQgcHJvY2Vzczwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICBzdWNoIGEgcG9saWN5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgc3Vj
aCBhIHBvbGljeTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAgRGVzY3JpYmVzIHJl
Y2VpdmVyIGZlZWRiYWNrIGZvciBzdWNoIHBvbGljaWVzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgbyAgRGVzY3JpYmVzIHJlY2VpdmVyIGZlZWRiYWNrIGZvciBzdWNoIHBvbGlj
aWVzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBvICBQcm92aWRlcyBjb250cm9scyB0
byBtaXRpZ2F0ZSBwb3RlbnRpYWwgcHJpdmFjeSBjb25zaWRlcmF0aW9uczwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIG8gIFByb3ZpZGVzIGNvbnRyb2xzIHRvIG1pdGlnYXRlIHBv
dGVudGlhbCBwcml2YWN5IGNvbnNpZGVyYXRpb25zPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGFzc29jaWF0ZWQgd2l0aCB0aGlzIGV4
dGVuc2lvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGFzc29jaWF0ZWQg
d2l0aCB0aGlzIGV4dGVuc2lvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxh
IG5hbWU9ImRpZmYwMDE1IiAvPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgVGhpcyBkb2N1bWVudCBh
bHNvIHByb3ZpZGVzIGEgbmV3IERNQVJDIHRhZyB0byBpbmRpY2F0ZSByZXF1ZXN0ZWQ8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgVGhpcyBkb2N1bWVudCBhbHNvIHByb3ZpZGVz
IGEgbmV3IERNQVJDIDxzcGFuIGNsYXNzPSJpbnNlcnQiPltSRkM3NDg5XTwvc3Bhbj4gdGFnIHRv
IGluZGljYXRlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+ICAgaGFuZGxpbmcgcG9saWN5IGZvciBub24tZXhpc3RlbnQgc3ViZG9tbWFpbnMu
ICBUaGlzIGlzIHByb3ZpZGVkPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHJl
cXVlc3RlZCBoYW5kbGluZyBwb2xpY3kgZm9yIG5vbi1leGlzdGVudCBzdWJkb21tYWlucy4gIFRo
aXMgaXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj4gICBzcGVjaWZpY2FsbHkgdG8gc3VwcG9ydCBwaGFzZWQgZGVwbG95bWVudCBvZiBQU0Qg
RE1BUkMsIGJ1dCBpczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBwcm92aWRl
ZCBzcGVjaWZpY2FsbHkgdG8gc3VwcG9ydCBwaGFzZWQgZGVwbG95bWVudCBvZiBQU0QgRE1BUkMs
IGJ1dDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPiAgIGV4cGVjdGVkIHRvIGJlIHVzZWZ1bCBtb3JlIGdlbmVyYWxseS4gIFVuZGVzaXJlZCBy
ZWplY3Rpb24gcmlza3MgZm9yPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGlz
IGV4cGVjdGVkIHRvIGJlIHVzZWZ1bCBtb3JlIGdlbmVyYWxseS4gIFVuZGVzaXJlZCByZWplY3Rp
b24gcmlza3M8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj4gICBtYWlsIHB1cnBvcnRpbmcgdG8gYmUgZnJvbSBkb21haW5zIHRoYXQgZG8gbm90
IGV4aXN0IGFyZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBmb3IgbWFpbCBw
dXJwb3J0aW5nIHRvIGJlIGZyb20gZG9tYWlucyB0aGF0IGRvIG5vdCBleGlzdCBhcmU8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgc3Vic3Rh
bnRpYWxseSBsb3dlciB0aGFuIGZvciB0aG9zZSB0aGF0IGRvLCBzbyB0aGUgb3BlcmF0aW9uYWwg
cmlzazwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHN1YnN0YW50aWFsbHkgbG93
ZXIgdGhhbiBmb3IgdGhvc2UgdGhhdCBkbywgc28gdGhlIG9wZXJhdGlvbmFsIHJpc2s8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgb2YgcmVx
dWVzdGluZyBoYXJzaCBwb2xpY3kgdHJlYXRtZW50IChlLmcuIHJlamVjdCkgaXMgbG93ZXIuPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgb2YgcmVxdWVzdGluZyBoYXJzaCBwb2xp
Y3kgdHJlYXRtZW50IChlLmcuIHJlamVjdCkgaXMgbG93ZXIuPC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBBcyBhbiBhZGRpdGlvbmFsIGJlbmVmaXQsIHRoZSBQU0QgRE1BUkMgZXh0ZW5z
aW9uIGNsYXJpZmllcyBleGlzdGluZzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IEFzIGFuIGFkZGl0aW9uYWwgYmVuZWZpdCwgdGhlIFBTRCBETUFSQyBleHRlbnNpb24gY2xhcmlm
aWVzIGV4aXN0aW5nPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIHJlcXVpcmVtZW50cy4gIEJhc2VkIG9uIHRoZSByZXF1aXJlbWVudHMgb2Yg
RE1BUkMgW1JGQzc0ODldLCBETUFSQzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IHJlcXVpcmVtZW50cy4gIEJhc2VkIG9uIHRoZSByZXF1aXJlbWVudHMgb2YgRE1BUkMgW1JGQzc0
ODldLCBETUFSQzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBzaG91bGQgZnVuY3Rpb24gYWJvdmUgdGhlIG9yZ2FuaXphdGlvbmFsIGxldmVs
IGZvciBleGFjdCBkb21haW48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBzaG91
bGQgZnVuY3Rpb24gYWJvdmUgdGhlIG9yZ2FuaXphdGlvbmFsIGxldmVsIGZvciBleGFjdCBkb21h
aW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgbWF0Y2hlcyAoaS5lLiBpZiBhIERNQVJDIHJlY29yZCB3ZXJlIHB1Ymxpc2hlZCBmb3IgJ2V4
YW1wbGUnLCB0aGVuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWF0Y2hlcyAo
aS5lLiBpZiBhIERNQVJDIHJlY29yZCB3ZXJlIHB1Ymxpc2hlZCBmb3IgJ2V4YW1wbGUnLCB0aGVu
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IG1haWwgZnJvbSBleGFtcGxlQGV4YW1wbGUgc2hvdWxkIGJlIHN1YmplY3QgdG8gRE1BUkMgcHJv
Y2Vzc2luZykuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWFpbCBmcm9tIGV4
YW1wbGVAZXhhbXBsZSBzaG91bGQgYmUgc3ViamVjdCB0byBETUFSQyBwcm9jZXNzaW5nKS48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
PjxhIG5hbWU9ImRpZmYwMDE2IiAvPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRl
bGV0ZSI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIFRlc3RpbmcgaGFkIHJldmVhbGVkIHRoYXQgdGhpcyBpcyBub3QgY29uc2lzdGVudGx5
IGFwcGxpZWQgaW48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUZXN0aW5nIGhh
ZCByZXZlYWxlZCB0aGF0IHRoaXMgaXMgbm90IGNvbnNpc3RlbnRseSBhcHBsaWVkIGluPC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGRpZmZl
cmVudCBpbXBsZW1lbnRhdGlvbnMuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
ZGlmZmVyZW50IGltcGxlbWVudGF0aW9ucy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IFRoZXJlIGFyZSB0d28gdHlwZXMgb2YgUHVibGljIFN1ZmZpeCBPcGVyYXRvcnMgKFBTT3MpIGZv
ciB3aGljaCB0aGlzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhlcmUgYXJl
IHR3byB0eXBlcyBvZiBQdWJsaWMgU3VmZml4IE9wZXJhdG9ycyAoUFNPcykgZm9yIHdoaWNoIHRo
aXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgZXh0ZW5zaW9uIHdvdWxkIGJlIHVzZWZ1bCBhbmQgYXBwcm9wcmlhdGU6PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZXh0ZW5zaW9uIHdvdWxkIGJlIHVzZWZ1bCBhbmQgYXBw
cm9wcmlhdGU6PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBvICBCcmFuZGVkIFBTRHMg
KGUuZy4sICIuZ29vZ2xlIik6IFRoZXNlIGRvbWFpbnMgYXJlIGVmZmVjdGl2ZWx5PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbyAgQnJhbmRlZCBQU0RzIChlLmcuLCAiLmdvb2ds
ZSIpOiBUaGVzZSBkb21haW5zIGFyZSBlZmZlY3RpdmVseTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBPcmdhbml6YXRpb25hbCBEb21h
aW5zIGFzIGRpc2N1c3NlZCBpbiBETUFSQyBbUkZDNzQ4OV0uICBUaGV5PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgT3JnYW5pemF0aW9uYWwgRG9tYWlucyBhcyBkaXNjdXNz
ZWQgaW4gRE1BUkMgW1JGQzc0ODldLiAgVGhleTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBjb250cm9sIGFsbCBzdWJkb21haW5zIG9m
IHRoZSB0cmVlLiAgVGhlc2UgYXJlIGVmZmVjdGl2ZWx5IHByaXZhdGU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBjb250cm9sIGFsbCBzdWJkb21haW5zIG9mIHRoZSB0cmVl
LiAgVGhlc2UgYXJlIGVmZmVjdGl2ZWx5IHByaXZhdGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgZG9tYWlucywgYnV0IGxpc3RlZCBp
biB0aGUgUHVibGljIFN1ZmZpeCBMaXN0LiAgVGhleSBhcmUgdHJlYXRlZDwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGRvbWFpbnMsIGJ1dCBsaXN0ZWQgaW4gdGhlIFB1Ymxp
YyBTdWZmaXggTGlzdC4gIFRoZXkgYXJlIHRyZWF0ZWQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBiZ2NvbG9yPSJncmF5IiA+PHRk
PjwvdGQ+PHRoPjxhIG5hbWU9InBhcnQtbDMiIC8+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBh
dDwvc21hbGw+PGVtPiBwYWdlIDUsIGxpbmUgMjY8L2VtPjwvdGg+PHRoPiA8L3RoPjx0aD48YSBu
YW1lPSJwYXJ0LXIzIiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxlbT4g
cGFnZSA1LCBsaW5lIDU8L2VtPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGFzIERN
QVJDIE9yZ2FuaXphdGlvbmFsIERvbWFpbnMsIGJ1dCBhcmUgY3VycmVudGx5IHVuYWJsZSB0bzwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGFzIERNQVJDIE9yZ2FuaXphdGlv
bmFsIERvbWFpbnMsIGJ1dCBhcmUgY3VycmVudGx5IHVuYWJsZSB0bzwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBiZW5lZml0IGZyb20g
RE1BUkMuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgYmVuZWZpdCBmcm9t
IERNQVJDLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAgTXVsdGktb3JnYW5pemF0
aW9uIFBTRHMgdGhhdCByZXF1aXJlIERNQVJDIHVzYWdlIChlLmcuLCAiLmJhbmsiKTo8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBvICBNdWx0aS1vcmdhbml6YXRpb24gUFNEcyB0
aGF0IHJlcXVpcmUgRE1BUkMgdXNhZ2UgKGUuZy4sICIuYmFuayIpOjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBCZWNhdXNlIGV4aXN0
aW5nIE9yZ2FuaXphdGlvbmFsIERvbWFpbnMgdXNpbmcgdGhpcyBQU0QgaGF2ZSB0aGVpcjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIEJlY2F1c2UgZXhpc3RpbmcgT3JnYW5p
emF0aW9uYWwgRG9tYWlucyB1c2luZyB0aGlzIFBTRCBoYXZlIHRoZWlyPC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIG93biBETUFSQyBw
b2xpY3ksIHRoZSBhcHBsaWNhYmlsaXR5IG9mIHRoaXMgZXh0ZW5zaW9uIGlzIGZvciBub24tPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgb3duIERNQVJDIHBvbGljeSwgdGhl
IGFwcGxpY2FiaWxpdHkgb2YgdGhpcyBleHRlbnNpb24gaXMgZm9yIG5vbi08L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgZXhpc3RlbnQg
ZG9tYWlucy4gIFRoZSBleHRlbnNpb24gYWxsb3dzIHRoZSBicmFuZCBwcm90ZWN0aW9uPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgZXhpc3RlbnQgZG9tYWlucy4gIFRoZSBl
eHRlbnNpb24gYWxsb3dzIHRoZSBicmFuZCBwcm90ZWN0aW9uPC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGJlbmVmaXRzIG9mIERNQVJD
IHRvIGV4dGVuZCB0byB0aGUgZW50aXJlIFBTRCwgaW5jbHVkaW5nIGNvdXNpbjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGJlbmVmaXRzIG9mIERNQVJDIHRvIGV4dGVuZCB0
byB0aGUgZW50aXJlIFBTRCwgaW5jbHVkaW5nIGNvdXNpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBkb21haW5zIG9mIHJlZ2lzdGVy
ZWQgb3JnYW5pemF0aW9ucy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBk
b21haW5zIG9mIHJlZ2lzdGVyZWQgb3JnYW5pemF0aW9ucy48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAxNyIgLz48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAg
IER1ZSB0byB0aGUgZGVzaWduIG9mIERNQVJDIGFuZCB0aGUgbmF0dXJlIG9mIHRoZSBJbnRlcm5l
dCBlbWFpbDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBEdWUgdG8gdGhlIGRl
c2lnbiBvZiBETUFSQyA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5bUkZDNzQ4OV08L3NwYW4+IGFuZCB0
aGUgbmF0dXJlIG9mIHRoZSBJbnRlcm5ldDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIGFyY2hpdGVjdHVyZSBbUkZDNTU5OF0sIHRoZXJl
IGFyZSBpbnRlcm9wZXJhYmlsaXR5IGlzc3VlcyBhc3NvY2lhdGVkPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPiAgIGVtYWlsIGFyY2hpdGVjdHVyZSBbUkZDNTU5OF0sIHRoZXJlIGFy
ZSBpbnRlcm9wZXJhYmlsaXR5IGlzc3VlczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIHdpdGggRE1BUkMgW1JGQzc0ODldIGRlcGxveW1l
bnQuICBUaGVzZSBhcmUgZGlzY3Vzc2VkIGluPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPiAgIGFzc29jaWF0ZWQgd2l0aCBETUFSQyBbUkZDNzQ4OV0gZGVwbG95bWVudC4gIFRoZXNl
IGFyZSBkaXNjdXNzZWQgaW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgSW50ZXJvcGVyYWJpbGl0eSBJc3N1ZXMgYmV0d2VlbiBETUFSQyBh
bmQgSW5kaXJlY3QgRW1haWwgRmxvd3M8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBJbnRlcm9wZXJhYmlsaXR5IElzc3VlcyBiZXR3ZWVuIERNQVJDIGFuZCBJbmRpcmVjdCBFbWFp
bCBGbG93czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBbUkZDNzk2MF0uICBUaGVzZSBpc3N1ZXMgYXJlIG5vdCB0eXBpY2FsbHkgYXBwbGlj
YWJsZSB0byBQU0RzLCBzaW5jZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtS
RkM3OTYwXS4gIFRoZXNlIGlzc3VlcyBhcmUgbm90IHR5cGljYWxseSBhcHBsaWNhYmxlIHRvIFBT
RHMsIHNpbmNlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIHRoZXkgKGUuZy4sIHRoZSAiLmdvdi5leGFtcGxlIiB1c2VkIGFib3ZlKSBkbyBu
b3QgdHlwaWNhbGx5IHNlbmQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aGV5
IChlLmcuLCB0aGUgIi5nb3YuZXhhbXBsZSIgdXNlZCBhYm92ZSkgZG8gbm90IHR5cGljYWxseSBz
ZW5kPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIG1haWwuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWFpbC48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjIuICBUZXJtaW5vbG9neSBhbmQgRGVmaW5pdGlvbnM8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4yLiAgVGVybWlub2xvZ3kgYW5kIERlZmluaXRp
b25zPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGlzIHNlY3Rpb24gZGVmaW5lcyB0
ZXJtcyB1c2VkIGluIHRoZSByZXN0IG9mIHRoZSBkb2N1bWVudC48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBUaGlzIHNlY3Rpb24gZGVmaW5lcyB0ZXJtcyB1c2VkIGluIHRoZSBy
ZXN0IG9mIHRoZSBkb2N1bWVudC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjIuMS4gIENv
bnZlbnRpb25zIFVzZWQgaW4gVGhpcyBEb2N1bWVudDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjIuMS4gIENvbnZlbnRpb25zIFVzZWQgaW4gVGhpcyBEb2N1bWVudDwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGJnY29s
b3I9ImdyYXkiID48dGQ+PC90ZD48dGg+PGEgbmFtZT0icGFydC1sNCIgLz48c21hbGw+c2tpcHBp
bmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48ZW0+IHBhZ2UgNiwgbGluZSAyMzwvZW0+PC90aD48dGg+
IDwvdGg+PHRoPjxhIG5hbWU9InBhcnQtcjQiIC8+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBh
dDwvc21hbGw+PGVtPiBwYWdlIDYsIGxpbmUgNDwvZW0+PC90aD48dGQ+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgUFNELjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFBTRC48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjIuMy4gIE9yZ2FuaXphdGlvbmFsIERvbWFpbjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjIuMy4gIE9yZ2FuaXphdGlvbmFsIERvbWFpbjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhlIHRlcm0gT3JnYW5pemF0aW9uYWwgRG9tYWlu
cyBpcyBkZWZpbmVkIGluIERNQVJDIFtSRkM3NDg5XTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIFRoZSB0ZXJtIE9yZ2FuaXphdGlvbmFsIERvbWFpbnMgaXMgZGVmaW5lZCBpbiBE
TUFSQyBbUkZDNzQ4OV08L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgU2VjdGlvbiAzLjIuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgU2VjdGlvbiAzLjIuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4yLjQuICBMb25n
ZXN0IFBTRDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjIuNC4gIExvbmdlc3QgUFNE
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGUgbG9uZ2VzdCBQU0QgaXMgdGhlIE9y
Z2FuaXphdGlvbmFsIERvbWFpbiB3aXRoIG9uZSBsYWJlbCByZW1vdmVkLjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoZSBsb25nZXN0IFBTRCBpcyB0aGUgT3JnYW5pemF0aW9u
YWwgRG9tYWluIHdpdGggb25lIGxhYmVsIHJlbW92ZWQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAxOCIg
Lz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPkl0IG5hbWVzIHRo
ZSBpbW1lZGlhdGUgcGFyZW50IG5vZGUgb2YgdGhlIE9yZ2FuaXphdGlvbmFsIERvbWFpbiBpbjwv
c3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0
ZSI+ICAgdGhlIEROUyBuYW1lc3BhY2UgdHJlZS48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+Mi41LiAgUHVibGljIFN1
ZmZpeCBPcGVyYXRvciAoUFNPKTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjIuNS4g
IFB1YmxpYyBTdWZmaXggT3BlcmF0b3IgKFBTTyk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIEEgUHVibGljIFN1ZmZpeCBPcGVyYXRvciBpcyBhbiBvcmdhbml6YXRpb24gd2hpY2ggbWFu
YWdlcyBvcGVyYXRpb25zPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQSBQdWJs
aWMgU3VmZml4IE9wZXJhdG9yIGlzIGFuIG9yZ2FuaXphdGlvbiB3aGljaCBtYW5hZ2VzIG9wZXJh
dGlvbnM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgd2l0aGluIGEgUFNELCBwYXJ0aWN1bGFybHkgdGhlIEROUyByZWNvcmRzIHB1Ymxpc2hl
ZCBmb3IgbmFtZXMgYXQgYW5kPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgd2l0
aGluIGEgUFNELCBwYXJ0aWN1bGFybHkgdGhlIEROUyByZWNvcmRzIHB1Ymxpc2hlZCBmb3IgbmFt
ZXMgYXQgYW5kPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIHVuZGVyIHRoYXQgZG9tYWluIG5hbWUuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgdW5kZXIgdGhhdCBkb21haW4gbmFtZS48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjIuNi4gIFBTTyBDb250cm9sbGVkIERvbWFpbiBOYW1lczwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPjIuNi4gIFBTTyBDb250cm9sbGVkIERvbWFpbiBOYW1lczwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUFNPIENvbnRyb2xsZWQgRG9tYWluIE5hbWVzIGFyZSBu
YW1lcyBpbiB0aGUgRE5TIHRoYXQgYXJlIG1hbmFnZWQgYnk8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBQU08gQ29udHJvbGxlZCBEb21haW4gTmFtZXMgYXJlIG5hbWVzIGluIHRo
ZSBETlMgdGhhdCBhcmUgbWFuYWdlZCBieTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGJnY29sb3I9ImdyYXkiID48dGQ+PC90ZD48
dGg+PGEgbmFtZT0icGFydC1sNSIgLz48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFs
bD48ZW0+IHBhZ2UgNiwgbGluZSA0NzwvZW0+PC90aD48dGg+IDwvdGg+PHRoPjxhIG5hbWU9InBh
cnQtcjUiIC8+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGVtPiBwYWdlIDYs
IGxpbmUgMjY8L2VtPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICIuY28udWsiKSBuYW1l
IGNvbXBvbmVudHMsIGRlcGVuZGluZyBvbiBQU0QgcG9saWN5LjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICIuY28udWsiKSBuYW1lIGNvbXBvbmVudHMsIGRlcGVuZGluZyBvbiBQ
U0QgcG9saWN5LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+Mi43LiAgTm9uLWV4aXN0ZW50
IERvbWFpbnM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4yLjcuICBOb24tZXhpc3Rl
bnQgRG9tYWluczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgRm9yIERNQVJDIHB1cnBv
c2VzLCBhIG5vbi1leGlzdGVudCBkb21haW4gaXMgYSBkb21haW4gZm9yIHdoaWNoIHRoZXJlPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgRm9yIERNQVJDIHB1cnBvc2VzLCBhIG5v
bi1leGlzdGVudCBkb21haW4gaXMgYSBkb21haW4gZm9yIHdoaWNoIHRoZXJlPC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGlzIGFuIE5YRE9N
QUlOIG9yIE5PREFUQSByZXNwb25zZSBmb3IgQSwgQUFBQSwgYW5kIE1YIHJlY29yZHMuICBUaGlz
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgaXMgYW4gTlhET01BSU4gb3IgTk9E
QVRBIHJlc3BvbnNlIGZvciBBLCBBQUFBLCBhbmQgTVggcmVjb3Jkcy4gIFRoaXM8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgaXMgYSBicm9h
ZGVyIGRlZmluaXRpb24gdGhhbiB0aGF0IGluIE5YRE9NQUlOIFtSRkM4MDIwXS48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBpcyBhIGJyb2FkZXIgZGVmaW5pdGlvbiB0aGFuIHRo
YXQgaW4gTlhET01BSU4gW1JGQzgwMjBdLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+My4g
IFBTRCBETUFSQyBVcGRhdGVzIHRvIERNQVJDIFJlcXVpcmVtZW50czwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPjMuICBQU0QgRE1BUkMgVXBkYXRlcyB0byBETUFSQyBSZXF1aXJlbWVu
dHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAxOSIg
Lz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFRoaXMgZG9jdW1lbnQgdXBkYXRlcyBETUFSQyBhcyBm
b2xsb3dzOjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBUaGlzIGRvY3VtZW50
IHVwZGF0ZXMgRE1BUkMgPHNwYW4gY2xhc3M9Imluc2VydCI+W1JGQzc0ODldIDwvc3Bhbj5hcyBm
b2xsb3dzOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+My4xLiAgR2VuZXJhbCBVcGRhdGVz
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+My4xLiAgR2VuZXJhbCBVcGRhdGVzPC90
ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBSZWZlcmVuY2VzIHRvICJEb21haW4gT3duZXJz
IiBhbHNvIGFwcGx5IHRvIFBTT3MuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
UmVmZXJlbmNlcyB0byAiRG9tYWluIE93bmVycyIgYWxzbyBhcHBseSB0byBQU09zLjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+My4yLiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDYuMyAiR2VuZXJh
bCBSZWNvcmQgRm9ybWF0IjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjMuMi4gIENo
YW5nZXMgaW4gU2VjdGlvbiA2LjMgIkdlbmVyYWwgUmVjb3JkIEZvcm1hdCI8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIEEgbmV3IHRhZyBpcyBhZGRlZCBhZnRlciAiZm8iOjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEEgbmV3IHRhZyBpcyBhZGRlZCBhZnRlciAiZm8i
OjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbnA6ICBSZXF1ZXN0ZWQgTWFpbCBSZWNl
aXZlciBwb2xpY3kgZm9yIG5vbi1leGlzdGVudCBzdWJkb21haW5zPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgbnA6ICBSZXF1ZXN0ZWQgTWFpbCBSZWNlaXZlciBwb2xpY3kgZm9y
IG5vbi1leGlzdGVudCBzdWJkb21haW5zPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIChwbGFpbi10ZXh0OyBPUFRJT05BTCkuICBJbmRp
Y2F0ZXMgdGhlIHBvbGljeSB0byBiZSBlbmFjdGVkIGJ5IHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgIChwbGFpbi10ZXh0OyBPUFRJT05BTCkuICBJbmRpY2F0ZXMgdGhl
IHBvbGljeSB0byBiZSBlbmFjdGVkIGJ5IHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBSZWNlaXZlciBhdCB0aGUgcmVxdWVzdCBv
ZiB0aGUgRG9tYWluIE93bmVyLiAgSXQgYXBwbGllcyBvbmx5IHRvPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgUmVjZWl2ZXIgYXQgdGhlIHJlcXVlc3Qgb2YgdGhlIERvbWFp
biBPd25lci4gIEl0IGFwcGxpZXMgb25seSB0bzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBub24tZXhpc3RlbnQgc3ViZG9tYWlucyBv
ZiB0aGUgZG9tYWluIHF1ZXJpZWQgYW5kIG5vdCB0byBlaXRoZXI8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgICBub24tZXhpc3RlbnQgc3ViZG9tYWlucyBvZiB0aGUgZG9tYWlu
IHF1ZXJpZWQgYW5kIG5vdCB0byBlaXRoZXI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgZXhpc3Rpbmcgc3ViZG9tYWlucyBvciB0aGUg
ZG9tYWluIGl0c2VsZi4gIEl0cyBzeW50YXggaXMgaWRlbnRpY2FsPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgZXhpc3Rpbmcgc3ViZG9tYWlucyBvciB0aGUgZG9tYWluIGl0
c2VsZi4gIEl0cyBzeW50YXggaXMgaWRlbnRpY2FsPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIHRvIHRoYXQgb2YgdGhlICJwIiB0YWcg
ZGVmaW5lZCBiZWxvdy4gIElmIHRoZSAnbnAnIHRhZyBpcyBhYnNlbnQsPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgdG8gdGhhdCBvZiB0aGUgInAiIHRhZyBkZWZpbmVkIGJl
bG93LiAgSWYgdGhlICducCcgdGFnIGlzIGFic2VudCw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgdGhlIHBvbGljeSBzcGVjaWZpZWQg
YnkgdGhlICJzcCIgdGFnIChpZiB0aGUgJ3NwJyB0YWcgaXMgcHJlc2VudCk8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICB0aGUgcG9saWN5IHNwZWNpZmllZCBieSB0aGUgInNw
IiB0YWcgKGlmIHRoZSAnc3AnIHRhZyBpcyBwcmVzZW50KTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBvciB0aGUgcG9saWN5IHNwZWNp
ZmllZCBieSB0aGUgInAiIHRhZywgaWYgdGhlICdzcCcgdGFnIGlzIG5vdDwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIG9yIHRoZSBwb2xpY3kgc3BlY2lmaWVkIGJ5IHRoZSAi
cCIgdGFnLCBpZiB0aGUgJ3NwJyB0YWcgaXMgbm90PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIHByZXNlbnQsIE1VU1QgYmUgYXBwbGll
ZCBmb3Igbm9uLWV4aXN0ZW50IHN1YmRvbWFpbnMuICBOb3RlIHRoYXQ8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBwcmVzZW50LCBNVVNUIGJlIGFwcGxpZWQgZm9yIG5vbi1l
eGlzdGVudCBzdWJkb21haW5zLiAgTm90ZSB0aGF0PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICJucCIgd2lsbCBiZSBpZ25vcmVkIGZv
ciBETUFSQyByZWNvcmRzIHB1Ymxpc2hlZCBvbiBzdWJkb21haW5zIG9mPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgIm5wIiB3aWxsIGJlIGlnbm9yZWQgZm9yIERNQVJDIHJl
Y29yZHMgcHVibGlzaGVkIG9uIHN1YmRvbWFpbnMgb2Y8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgT3JnYW5pemF0aW9uYWwgRG9tYWlu
cyBhbmQgUFNEcyBkdWUgdG8gdGhlIGVmZmVjdCBvZiB0aGUgRE1BUkM8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBPcmdhbml6YXRpb25hbCBEb21haW5zIGFuZCBQU0RzIGR1
ZSB0byB0aGUgZWZmZWN0IG9mIHRoZSBETUFSQzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlmZjAwMjAiIC8+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGJsb2NrIj4gICAgICBwb2xpY3kgZGlzY292ZXJ5IG1lY2hhbmlzbSBkZXNjcmli
ZWQgaW4gRE1BUkMgU2VjdGlvbiA2LjYuMy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+ICAgICAgcG9saWN5IGRpc2NvdmVyeSBtZWNoYW5pc20gZGVzY3JpYmVkIGluIERNQVJDIDxz
cGFuIGNsYXNzPSJpbnNlcnQiPltSRkM3NDg5XTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+ICAgICAgU2VjdGlvbiA2LjYuMy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAyMSIgLz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFRo
ZSBmb2xsb3dpbmcgdGFnIGRlZmluaXRpb25zIGZyb20gRE1BUkMgYXJlIHVwZGF0ZWQ6PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFRoZSBmb2xsb3dpbmcgdGFnIGRlZmluaXRp
b25zIGZyb20gRE1BUkMgPHNwYW4gY2xhc3M9Imluc2VydCI+W1JGQzc0ODldIDwvc3Bhbj5hcmUg
dXBkYXRlZDo8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHA6IFRoZSBzZW50ZW5jZSAn
UG9saWN5IGFwcGxpZXMgdG8gdGhlIGRvbWFpbiBxdWVyaWVkIGFuZCB0bzwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIHA6IFRoZSBzZW50ZW5jZSAnUG9saWN5IGFwcGxpZXMgdG8g
dGhlIGRvbWFpbiBxdWVyaWVkIGFuZCB0bzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBzdWJkb21haW5zLCB1bmxlc3Mgc3ViZG9tYWlu
IHBvbGljeSBpcyBleHBsaWNpdGx5IGRlc2NyaWJlZCB1c2luZzwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgIHN1YmRvbWFpbnMsIHVubGVzcyBzdWJkb21haW4gcG9saWN5IGlz
IGV4cGxpY2l0bHkgZGVzY3JpYmVkIHVzaW5nPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIHRoZSAic3AiIHRhZycgaXMgdXBkYXRlZCB0
byByZWFkICdQb2xpY3kgYXBwbGllcyB0byB0aGUgZG9tYWluPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgdGhlICJzcCIgdGFnJyBpcyB1cGRhdGVkIHRvIHJlYWQgJ1BvbGlj
eSBhcHBsaWVzIHRvIHRoZSBkb21haW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgcXVlcmllZCBhbmQgdG8gc3ViZG9tYWlucywgdW5s
ZXNzIHN1YmRvbWFpbiBwb2xpY3kgaXMgZXhwbGljaXRseTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgICAgIHF1ZXJpZWQgYW5kIHRvIHN1YmRvbWFpbnMsIHVubGVzcyBzdWJkb21h
aW4gcG9saWN5IGlzIGV4cGxpY2l0bHk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgZGVzY3JpYmVkIHVzaW5nIHRoZSAic3AiIG9yICJu
cCIgdGFncy4nPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgZGVzY3JpYmVk
IHVzaW5nIHRoZSAic3AiIG9yICJucCIgdGFncy4nPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBzcDogIFRoZSBzZW50ZW5jZSAnSWYgYWJzZW50LCB0aGUgcG9saWN5IHNwZWNpZmllZCBi
eSB0aGUgInAiIHRhZzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHNwOiAgVGhl
IHNlbnRlbmNlICdJZiBhYnNlbnQsIHRoZSBwb2xpY3kgc3BlY2lmaWVkIGJ5IHRoZSAicCIgdGFn
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgIE1VU1QgYmUgYXBwbGllZCBmb3Igc3ViZG9tYWlucycgaXMgdXBkYXRlZCB0byByZWFkICdJ
ZiBib3RoIHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIE1VU1QgYmUg
YXBwbGllZCBmb3Igc3ViZG9tYWlucycgaXMgdXBkYXRlZCB0byByZWFkICdJZiBib3RoIHRoZTwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICAnc3AnIHRhZyBpcyBhYnNlbnQgYW5kIHRoZSAnbnAnIHRhZyBpcyBlaXRoZXIgYWJzZW50IG9y
IG5vdDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICdzcCcgdGFnIGlzIGFi
c2VudCBhbmQgdGhlICducCcgdGFnIGlzIGVpdGhlciBhYnNlbnQgb3Igbm90PC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgYmdjb2xv
cj0iZ3JheSIgPjx0ZD48L3RkPjx0aD48YSBuYW1lPSJwYXJ0LWw2IiAvPjxzbWFsbD5za2lwcGlu
ZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxlbT4gcGFnZSA4LCBsaW5lIDY8L2VtPjwvdGg+PHRoPiA8
L3RoPjx0aD48YSBuYW1lPSJwYXJ0LXI2IiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8
L3NtYWxsPjxlbT4gcGFnZSA3LCBsaW5lIDMyPC9lbT48L3RoPjx0ZD48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBmb3IgZG9pbmcgc28uICBTZWUgdGhlIFt0aGlzIGRvY3VtZW50XSBleHBlcmltZW50IGRl
c2NyaXB0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZm9yIGRvaW5nIHNv
LiAgU2VlIHRoZSBbdGhpcyBkb2N1bWVudF0gZXhwZXJpbWVudCBkZXNjcmlwdGlvbjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAoQXBwZW5k
aXggQSkuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgKEFwcGVuZGl4IEEpLjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+My40LiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDYuNi4x
ICJFeHRyYWN0IEF1dGhvciBEb21haW4iPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
My40LiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDYuNi4xICJFeHRyYWN0IEF1dGhvciBEb21haW4iPC90
ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBFeHBlcmllbmNlIHdpdGggRE1BUkMgaGFzIHNo
b3duIHRoYXQgc29tZSBpbXBsZW1lbnRhdGlvbnMgc2hvcnQtPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgRXhwZXJpZW5jZSB3aXRoIERNQVJDIGhhcyBzaG93biB0aGF0IHNvbWUg
aW1wbGVtZW50YXRpb25zIHNob3J0LTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBjaXJjdWl0IG1lc3NhZ2VzLCBieXBhc3NpbmcgRE1BUkMg
cG9saWN5IGFwcGxpY2F0aW9uLCB3aGVuIHRoZSBkb21haW48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBjaXJjdWl0IG1lc3NhZ2VzLCBieXBhc3NpbmcgRE1BUkMgcG9saWN5IGFw
cGxpY2F0aW9uLCB3aGVuIHRoZSBkb21haW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbmFtZSBleHRyYWN0ZWQgYnkgdGhlIHJlY2VpdmVy
IChmcm9tIHRoZSBSRkM1MzIyLkZyb20pIGlzIG9uIHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIG5hbWUgZXh0cmFjdGVkIGJ5IHRoZSByZWNlaXZlciAoZnJvbSB0aGUgUkZD
NTMyMi5Gcm9tKSBpcyBvbiB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgcHVibGljIHN1ZmZpeCBsaXN0IHVzZWQgYnkgdGhlIHJlY2Vp
dmVyLiAgVGhpcyBuZWdhdGVzIHRoZSBjYXBhYmlsaXR5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgcHVibGljIHN1ZmZpeCBsaXN0IHVzZWQgYnkgdGhlIHJlY2VpdmVyLiAgVGhp
cyBuZWdhdGVzIHRoZSBjYXBhYmlsaXR5PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGJlaW5nIGNyZWF0ZWQgYnkgdGhpcyBzcGVjaWZpY2F0
aW9uLiAgVGhlcmVmb3JlLCB0aGUgZm9sbG93aW5nPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgYmVpbmcgY3JlYXRlZCBieSB0aGlzIHNwZWNpZmljYXRpb24uICBUaGVyZWZvcmUs
IHRoZSBmb2xsb3dpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDIyIiAvPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+ICAgcGFyYWdyYXBoIGlzIGFwcGVuZGVkIHRvIFNlY3Rpb24gNi42LjEgb2YgRE1BUkM6PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHBhcmFncmFwaCBpcyBhcHBlbmRlZCB0
byBTZWN0aW9uIDYuNi4xIG9mIERNQVJDPHNwYW4gY2xhc3M9Imluc2VydCI+IFtSRkM3NDg5XTwv
c3Bhbj46PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBOb3RlIHRoYXQgZG9tYWluIG5h
bWVzIHRoYXQgYXBwZWFyIG9uIGEgcHVibGljIHN1ZmZpeCBsaXN0IGFyZSBub3Q8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBOb3RlIHRoYXQgZG9tYWluIG5hbWVzIHRoYXQgYXBw
ZWFyIG9uIGEgcHVibGljIHN1ZmZpeCBsaXN0IGFyZSBub3Q8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZXhlbXB0IGZyb20gRE1BUkMgcG9s
aWN5IGFwcGxpY2F0aW9uIGFuZCByZXBvcnRpbmcuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgZXhlbXB0IGZyb20gRE1BUkMgcG9saWN5IGFwcGxpY2F0aW9uIGFuZCByZXBvcnRp
bmcuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4zLjUuICBDaGFuZ2VzIGluIFNlY3Rpb24g
Ni42LjMgIlBvbGljeSBEaXNjb3ZlcnkiPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
My41LiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDYuNi4zICJQb2xpY3kgRGlzY292ZXJ5IjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgQSBuZXcgc3RlcCBiZXR3ZWVuIHN0ZXAgMyBhbmQgNCBp
cyBhZGRlZDo8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBIG5ldyBzdGVwIGJl
dHdlZW4gc3RlcCAzIGFuZCA0IGlzIGFkZGVkOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgM0EuICBJZiB0aGUgc2V0IGlzIG5vdyBlbXB0eSBhbmQgdGhlIGxvbmdlc3QgUFNEIChTZWN0
aW9uIDIuNCkgb2YgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgM0EuICBJ
ZiB0aGUgc2V0IGlzIG5vdyBlbXB0eSBhbmQgdGhlIGxvbmdlc3QgUFNEIChTZWN0aW9uIDIuNCkg
b2YgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgIE9yZ2FuaXphdGlvbmFsIERvbWFpbiBpcyBvbmUgdGhhdCB0aGUgcmVjZWl2ZXIg
aGFzIGRldGVybWluZWQgaXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBP
cmdhbml6YXRpb25hbCBEb21haW4gaXMgb25lIHRoYXQgdGhlIHJlY2VpdmVyIGhhcyBkZXRlcm1p
bmVkIGlzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KCiAg
ICAgPHRyPjx0ZD48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQ+PC90ZD48L3RyPgogICAgIDx0ciBiZ2NvbG9yPSJncmF5Ij48dGgg
Y29sc3Bhbj0iNSIgYWxpZ249ImNlbnRlciI+PGEgbmFtZT0iZW5kIj4mbmJzcDtFbmQgb2YgY2hh
bmdlcy4gMjIgY2hhbmdlIGJsb2Nrcy4mbmJzcDs8L2E+PC90aD48L3RyPgogICAgIDx0ciBjbGFz
cz0ic3RhdHMiPjx0ZD48L3RkPjx0aD48aT43MSBsaW5lcyBjaGFuZ2VkIG9yIGRlbGV0ZWQ8L2k+
PC90aD48dGg+PGk+IDwvaT48L3RoPjx0aD48aT41MCBsaW5lcyBjaGFuZ2VkIG9yIGFkZGVkPC9p
PjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICA8dHI+PHRkIGNvbHNwYW49IjUiIGFsaWduPSJjZW50
ZXIiIGNsYXNzPSJzbWFsbCI+PGJyLz5UaGlzIGh0bWwgZGlmZiB3YXMgcHJvZHVjZWQgYnkgcmZj
ZGlmZiAxLjM0LiBUaGUgbGF0ZXN0IHZlcnNpb24gaXMgYXZhaWxhYmxlIGZyb20gPGEgaHJlZj0i
aHR0cDovL3d3dy50b29scy5pZXRmLm9yZy90b29scy9yZmNkaWZmLyIgPmh0dHA6Ly90b29scy5p
ZXRmLm9yZy90b29scy9yZmNkaWZmLzwvYT4gPC90ZD48L3RyPgogICA8L3RhYmxlPgogICA8L2Jv
ZHk+CiAgIDwvaHRtbD4K
--000000000000a4a38d05b9831fd3--


From nobody Fri Jan 22 14:36:10 2021
Return-Path: <tjw.ietf@gmail.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 3FF173A09A4 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 14:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 NLGXUxmJGP-O for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 14:36:07 -0800 (PST)
Received: from mail-oo1-xc2f.google.com (mail-oo1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE0F13A07F7 for <dmarc@ietf.org>; Fri, 22 Jan 2021 14:36:07 -0800 (PST)
Received: by mail-oo1-xc2f.google.com with SMTP id y14so1782750oom.10 for <dmarc@ietf.org>; Fri, 22 Jan 2021 14:36:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q+2z+L0GeIgDK+z786OhUd9rS3CTmU+I3Bl9nV7BT00=; b=S0Ivhs03IcRQF47TRsKXz7mt6w2Nx/ctgqHX8F+4YROnAG/NV4oaFhuv9se2r2WuGD HIripruaSg/zoquzk2dWhCYUNT6BgpZGierL23nzXW3wLx72zP5FedRUHvsWkQMr/8Bw bzPZTfxmniTZ90hLu14M3Sefq28FgrXAUBDSrao9/yKzlLu1D29v/+vIuWg4Q9lpS3WQ 8E1yy3+W9eJNUjEOLfPxzkEagbDsQPxVyoeiOhAlzsgeYyGLvHjCRupPwbl690N9+lAF ooJbius5UAluJsN7J4IB9UabX4yOvf52pbFyBaOSzv3e7OyjEzMfnrvEIjgq3Ys03BLL 4Siw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q+2z+L0GeIgDK+z786OhUd9rS3CTmU+I3Bl9nV7BT00=; b=J5QJuuDrF6TSta6MitY1KHa0wvc5ZzeuJ7UeEMqWp7WwnuXeWp+levKC3aNyJQELny b5quN0wAtfYRasfnJY+VjGbUEftbDw2j7pCdQZMZlEFtR3I/yxKFxn7VI6Nlsc3dVcMS YsZeePQqKT3wmXKkf275gBXpPecQWroNaXeC+i50YqKgCsYQRZN+8HpJs5amt22tENXa +YlGF3yQ349CfntjL2SDAijDztRXzTK0KFd29dlegvOuIGqDSneeUVH+xMjPwP9Rx5gc uU/nMJPhS/mLKsfr2MCHAeCxM0raE+h6Uac3UbpFGvmdUPi98/IdN2SGvXF6+KL0oIF0 2y/w==
X-Gm-Message-State: AOAM5306++8tzddDhMv4FhoXPJn9emqZa5vivFwParKEOseo2iLE+9Vu fTSSVlR90ejxtkRw/I5ugHc7zVmGAIcY012i8Duu8YY/Dwc=
X-Google-Smtp-Source: ABdhPJzy9EnaXZQR2ty6ra1GQjDZD9pKgpCpYjIBnb93IVU2vvBUgnQmn+sfSw3F0gYpE9kDWJI8jRlYShmboPEjY/U=
X-Received: by 2002:a4a:bc12:: with SMTP id i18mr2727455oop.90.1611354967089;  Fri, 22 Jan 2021 14:36:07 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it>
In-Reply-To: <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 22 Jan 2021 17:35:56 -0500
Message-ID: <CADyWQ+HntwpgakHxjxvojXMg_w5kMoxJ=fFq+yOPHb6WdMQTjg@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006ba4b005b984d0df"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wKkjDRVo2PYy9e6uL3LumtciTEo>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 22 Jan 2021 22:36:09 -0000

--0000000000006ba4b005b984d0df
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 19, 2021 at 5:31 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Tue 19/Jan/2021 07:43:01 +0100 Murray S. Kucherawy wrote:
> > [...]
>
>
> I guess "[this document]" refers to the RFC number to be.  I think it's
> useless
> and can be safely removed, all of the five occurrences of it.
>
> It is clearer and more useful to specify the referred document when it is
> /not/
> this document.  For example:
>
>      Changes in Section 6.5 of RFC 7489 "Domain Owner Actions"
>
> The above is going to be rendered with the correct anchor in the htmlized
> version of the document.  It can be expressed in xml as:
>
>      <xref target="RFC7489" sectionFormat="of" section="6.5"/>
>
> so as to generate correct links whenever possible.
>

two things:  1) to be accurate I would want to target the section anchor.
But actually the real answer is 2) the RFC editor owns the final XML and I
believe
they perform a bunch of this work during the AUTH48 process.

Now saying that, someone will politely explain how wrong I am.

In fact, those are the two terms appearing in the title.  BTW, I'd change
> the
> title to:
>
>      Domain-based Message Authentication, Reporting, and Conformance
> (DMARC)
>      Extension For Public Suffix Domains (PSDs)
>

I went with the Murray;s "Experimental DMARC Extension For Public Suffix
Domains"

And Murray restructured the Intro and it feels much cleaner.

tim

--0000000000006ba4b005b984d0df
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:monospace"><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Tue, Jan 19, 2021 at 5:31 AM Alessandro Ve=
sely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue 19/Jan/2021=
 07:43:01 +0100 Murray S. Kucherawy wrote:<br>
&gt; [...]<br><br>
<span class=3D"gmail_default" style=3D"font-family:monospace"></span><br>
I guess &quot;[this document]&quot; refers to the RFC number to be.=C2=A0 I=
 think it&#39;s useless <br>
and can be safely removed, all of the five occurrences of it.<br>
<br>
It is clearer and more useful to specify the referred document when it is /=
not/ <br>
this document.=C2=A0 For example:<br>
<br>
=C2=A0 =C2=A0 =C2=A0Changes in Section 6.5 of RFC 7489 &quot;Domain Owner A=
ctions&quot;<br>
<br>
The above is going to be rendered with the correct anchor in the htmlized <=
br>
version of the document.=C2=A0 It can be expressed in xml as:<br>
<br>
=C2=A0 =C2=A0 =C2=A0&lt;xref target=3D&quot;RFC7489&quot; sectionFormat=3D&=
quot;of&quot; section=3D&quot;6.5&quot;/&gt;<br>
<br>
so as to generate correct links whenever possible.<br></blockquote><div><br=
></div><div class=3D"gmail_default" style=3D"font-family:monospace">two thi=
ngs:=C2=A0 1) to be accurate I would want to target the section anchor.=C2=
=A0</div><div class=3D"gmail_default" style=3D"font-family:monospace">But a=
ctually the real answer is 2) the RFC editor owns the final XML and I belie=
ve</div><div class=3D"gmail_default" style=3D"font-family:monospace">they p=
erform a bunch of this work during the AUTH48 process.=C2=A0=C2=A0</div><di=
v class=3D"gmail_default" style=3D"font-family:monospace"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-family:monospace">Now saying that, some=
one will politely explain how wrong I am.</div><div class=3D"gmail_default"=
 style=3D"font-family:monospace"><br></div><div class=3D"gmail_default" sty=
le=3D"font-family:monospace"></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
In fact, those are the two terms appearing in the title.=C2=A0 BTW, I&#39;d=
 change the <br>
title to:<br>
<br>
=C2=A0 =C2=A0 =C2=A0Domain-based Message Authentication, Reporting, and Con=
formance (DMARC)<br>
=C2=A0 =C2=A0 =C2=A0Extension For Public Suffix Domains (PSDs)<br></blockqu=
ote><div><br></div><div class=3D"gmail_default" style=3D"font-family:monosp=
ace">I went with the Murray;s &quot;Experimental DMARC Extension For Public=
 Suffix Domains&quot;</div><div class=3D"gmail_default" style=3D"font-famil=
y:monospace"><br></div><div class=3D"gmail_default" style=3D"font-family:mo=
nospace">And Murray restructured the Intro and it feels much cleaner.=C2=A0=
</div><div class=3D"gmail_default" style=3D"font-family:monospace"><br></di=
v><div class=3D"gmail_default" style=3D"font-family:monospace">tim</div></d=
iv></div>

--0000000000006ba4b005b984d0df--


From nobody Fri Jan 22 14:40:26 2021
Return-Path: <johnl@iecc.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 262373A12B5 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 14:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=KEQ5Ua8N; dkim=pass (2048-bit key) header.d=taugh.com header.b=6MW168fN
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 7eg6xTU3GVES for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 14:40:22 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 715693A0E94 for <dmarc@ietf.org>; Fri, 22 Jan 2021 14:40:22 -0800 (PST)
Received: (qmail 64273 invoked from network); 22 Jan 2021 22:40:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=fb0d.600b5453.k2101; bh=71+GgnqaqqAuI0pUR+JEL35tR4NvMSOWkPplkAOrDVk=; b=KEQ5Ua8NWpil+GtLXm28+Y7Rf6b1TZDJqKoDCxOJgTayywKRWcY6sOGuWXfB0uYzAF2hgTQK/TTysibFN14P/3JVmkNrgK85GLn8Xas+ws0yMRNd9fiFUp5/c5WYqR3SgxcqTyHGQ9+3FlrebhRVj2/+fMllv7boTO0HYpe0kUCZ2SWsP5vyJNf/c8rPCm0MP+B5j0JSGml5cXXjpSDRlw7IDjCTAMjWQ/j1cKEERm3JUFP4cTv8Qj/uqnH/ullVzP/0t45iIbmhsPPepuzEQw/ImKbhCOgDTUuuol+Mr6BF4swptBKKuWfnIMwcsGRzvM8CFnfWLSFPJ747yjIJpA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=fb0d.600b5453.k2101; bh=71+GgnqaqqAuI0pUR+JEL35tR4NvMSOWkPplkAOrDVk=; b=6MW168fN5tAKZAnhHsHAUs5gBd4zPp8kU6/95wyb5/5Bd0VxCThj1p9CtmSds6Euo9qhnfOpcVL9CBharxZ6MiD1DmZaiPkuMvBRlSYqkSVMgaQy1g47mh7XOySUUh7IyeC3sNsQbdYp6HpXrab/D/75CZq4XEh4guZ08Zj9/W+ZgHXipFJzzv0mXYlytYNyyJ1DZx+ioXk/50o8QkfufVgptSHHIGVOZTlvPDwHHjbul9aYzikWQ+Hf9tmNIMqP5kCnAVZqVsR7EuBSfgSigDN0ROc3bgGkbmcHHWD7pIR7TJNiPbbFcqWtng8LaTg+29rMDyn9posHyToswOx6JQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 22 Jan 2021 22:40:19 -0000
Received: by ary.qy (Postfix, from userid 501) id E63E06BF246B; Fri, 22 Jan 2021 17:40:18 -0500 (EST)
Date: 22 Jan 2021 17:40:18 -0500
Message-Id: <20210122224018.E63E06BF246B@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: emgu@google.com
In-Reply-To: <CABZJ8knVg4TYbRzPUCjKSCMD8keHw49oeJr5DiS3UzAQGSuV7g@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DIVSZhJzHc3lXrJt-OXPYafQEK8>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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: Fri, 22 Jan 2021 22:40:24 -0000

In article <CABZJ8knVg4TYbRzPUCjKSCMD8keHw49oeJr5DiS3UzAQGSuV7g@mail.gmail.com> you write:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>I think spammers would only get two things from the DMARC reports:
>1) Have they setup their configuration correctly?
>2) Consume resources from the mailbox provider to generate reports.
>
>Only if #2 is a concern for the mailbox provider I think there is a need to
>filter who gets a report and who does not.

We have a decade of experience with DMARC and I don't ever recall
anyone having a practical issue with who they send reports to.

As someone said, the better the spammers align their stuff, the better
we can filter it.

Close this, please.

R's,
John


From nobody Fri Jan 22 15:05:59 2021
Return-Path: <tjw.ietf@gmail.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 B0D6A3A1544 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 15:05:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 aU9uThWOlrXq for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 15:05:56 -0800 (PST)
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CBF03A1547 for <dmarc@ietf.org>; Fri, 22 Jan 2021 15:05:56 -0800 (PST)
Received: by mail-ot1-x332.google.com with SMTP id 63so6766813oty.0 for <dmarc@ietf.org>; Fri, 22 Jan 2021 15:05:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z1PFPiz3p7+ZFQ/l2X8vIgPfJCvcP8K8aydZdXKCoeE=; b=YSfRShnIT25F6CAVT8Uk6ZjeaMCj0xDOw+ffQQ38GWcd4YkkbscVXxCdsaHbm49cRn w+Mb6O2bWZ9WVRkrK4KqLK4jeFLGfEnPSBa6ayiQMnu//8wBL9hwO7aowBHLeFgKksF5 ikqCadSOcuKXo/FKELgIoCprFOKA8kOdCIxOLe2AQsyu9VFaHmVNZmIsjIZc1Z6m9hq3 UC4QYtrnbuU6mrytA+pIN5VJrI8+4wEo2uWkYBIX0Nn9x16xKJ6Zdurd+Wc8Ibv5FCMm 5/qqpANnmRSOD0yvM06yJHQaQ3FTTq4iQoobSaW452vgWbab+q2q39PpMcWYvZmtmJ/2 /MSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z1PFPiz3p7+ZFQ/l2X8vIgPfJCvcP8K8aydZdXKCoeE=; b=eMwTOOONUIlmtLAeztrDv+iAqa5OFVBrYbNLrgBpVxv9P+459oE/a4JhhSucR8y6cq lphGOLh5hgKAHO/87C6+RpdYbz3BLIAH5tUzrsMZqUWvWqUeg13b+WoATrOkWBLgRQjR 3LIfzIkm/UZs0uxbJsEdcvRKmdxxp0ks3/f+DNYobBl+JCEX+wmisKA7uMu70Qfp82Gc 6O88iXVFfObIsJiIkcY215xx2QgFiRRzc+etATRidcgW8xpQmVFJyTy7ElrWJONsVn0W Ns18XMLuz0AS5MMR/x9lR8FcGZFuWwEjU7TiJrVrL0cYVV/HXFQOBPw3rn1nUgIzGqDD tJeA==
X-Gm-Message-State: AOAM530oQYkKM5fs5svzp1IsXeo9FthUQvrbhIcSzg5O0AJkXpYSNh/J yQowNNAnIyysCbUCrB3UvPjj69IqfZp0xAREFMr0Bmg8UE4=
X-Google-Smtp-Source: ABdhPJwjimZ18mwTLsuKUQzMZJEWVXtPWNYCASyVDDiDTkC4ql8kI8utOt+gTAlZ1NZAEXixBCZZJyY6mKkTkL2Q+zA=
X-Received: by 2002:a05:6830:1254:: with SMTP id s20mr5066384otp.155.1611356755858;  Fri, 22 Jan 2021 15:05:55 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com>
In-Reply-To: <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 22 Jan 2021 18:05:44 -0500
Message-ID: <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Alessandro Vesely <vesely@tana.it>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000a178f05b9853b31"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Af3ZDDndKmUns1qLk-N3S6MTOlE>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 22 Jan 2021 23:05:58 -0000

--0000000000000a178f05b9853b31
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 19, 2021 at 9:19 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Tue, Jan 19, 2021 at 2:31 AM Alessandro Vesely <vesely@tana.it> wrote:
>
> >     To determine the organizational domain for a message under
>> evaluation,
>> >     and thus where to look for a policy statement, DMARC makes use of a
>> >     Public Suffix List.
>> >     The process for doing this can be found in Section 3.2 of the DMARC
>> >     specification.
>>
>> Couldn't we skip that kind of functional intro and say something general,
>> such
>> as anticipating Section 2.2:
>>
>>      Public Suffix Domains (PSDs) are domain names publicly accessible for
>>      domain registration.  As explained in Section 2.2, they include all
>> top
>>      level domains and some more.  The way delegations occur on the global
>>      Internet makes it difficult to establish whether a domain is a PSD.
>> A
>>      community maintained Public Suffix List (PSL) exists for that
>> purpose.
>>
>> Thinking twice, perhaps we don't need to introduce the PSL until Section
>> 3.4.
>> In that case, strike the last two sentences of the above paragraph.
>>
>
> It's not obvious to me that this is better, but sure, let's discuss it.
>
>> Here's the paragraph in question

     <t>To determine the organizational domain for a message under
evaluation,
        and thus where to look for a policy statement, DMARC makes use of a
Public Suffix
        List. The process for doing this can be found in Section 3.2 of the
DMARC
        specification.</t>



The more I look at this, you need it near the top because that is where the
discussion
of the policy.  But also open to be convinced.

tim



>>

--0000000000000a178f05b9853b31
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:monospace"><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Tue, Jan 19, 2021 at 9:19 AM Murray S. Kuc=
herawy &lt;<a href=3D"mailto:superuser@gmail.com">superuser@gmail.com</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d=
ir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 19, 2021 at 2:31 AM Alessandro Vese=
ly &lt;<a href=3D"mailto:vesely@tana.it" target=3D"_blank">vesely@tana.it</=
a>&gt; wrote:<br></div><div class=3D"gmail_quote"><div><br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">&gt;=C2=A0 =C2=A0 =C2=A0To determin=
e the organizational domain for a message under evaluation,<br>
&gt;=C2=A0 =C2=A0 =C2=A0and thus where to look for a policy statement, DMAR=
C makes use of a<br>
&gt;=C2=A0 =C2=A0 =C2=A0Public Suffix List.<br>
&gt;=C2=A0 =C2=A0 =C2=A0The process for doing this can be found in Section =
3.2 of the DMARC<br>
&gt;=C2=A0 =C2=A0 =C2=A0specification.<br>
<br>
Couldn&#39;t we skip that kind of functional intro and say something genera=
l, such <br>
as anticipating Section 2.2:<br>
<br>
=C2=A0 =C2=A0 =C2=A0Public Suffix Domains (PSDs) are domain names publicly =
accessible for<br>
=C2=A0 =C2=A0 =C2=A0domain registration.=C2=A0 As explained in Section 2.2,=
 they include all top<br>
=C2=A0 =C2=A0 =C2=A0level domains and some more.=C2=A0 The way delegations =
occur on the global<br>
=C2=A0 =C2=A0 =C2=A0Internet makes it difficult to establish whether a doma=
in is a PSD.=C2=A0 A<br>
=C2=A0 =C2=A0 =C2=A0community maintained Public Suffix List (PSL) exists fo=
r that purpose.<br>
<br>
Thinking twice, perhaps we don&#39;t need to introduce the PSL until Sectio=
n 3.4. <br>
In that case, strike the last two sentences of the above paragraph.<br></bl=
ockquote><div><br></div><div>It&#39;s not obvious to me that this is better=
, but sure, let&#39;s discuss it.</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><span class=3D"gmail_default" style=3D"font-family:monospace"=
></span></blockquote></div></div></blockquote><font face=3D"monospace"><spa=
n class=3D"gmail_default" style=3D"font-family:monospace"></span><div class=
=3D"gmail_quote"><font face=3D"monospace"><span class=3D"gmail_default" sty=
le=3D"font-family:monospace">Here&#39;s the paragraph in question</span><br=
></font></div><br>=C2=A0 =C2=A0 =C2=A0&lt;t&gt;To determine the organizatio=
nal domain for a message under evaluation,<br><span class=3D"gmail_default"=
 style=3D"font-family:monospace"></span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 and thu=
s where to look for a policy statement, DMARC makes use of a Public Suffix<=
br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 List. The process for doing this can be foun=
d in Section 3.2 of the DMARC<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification.=
&lt;/t&gt;</font><div class=3D"gmail_default" style=3D"font-family:monospac=
e"><p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;fo=
nt-variant-east-asian:normal;font-stretch:normal;font-size:13px;line-height=
:normal;font-family:&quot;Helvetica Neue&quot;"><br></p><p class=3D"gmail-p=
1" style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:13px;line-height:normal;font-family:&q=
uot;Helvetica Neue&quot;"><br></p></div><div class=3D"gmail_default" style=
=3D"font-family:monospace">The more I look at this, you need it near the to=
p because that is where the discussion</div><div class=3D"gmail_default" st=
yle=3D"font-family:monospace">of the policy.=C2=A0 But also open to be conv=
inced.=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:monospa=
ce"><br></div><div class=3D"gmail_default" style=3D"font-family:monospace">=
tim</div><div class=3D"gmail_default" style=3D"font-family:monospace"><br><=
/div><div class=3D"gmail_default" style=3D"font-family:monospace"><br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span=
 class=3D"gmail_default" style=3D"font-family:monospace"></span><br></block=
quote></div></div>
</blockquote></div></div>

--0000000000000a178f05b9853b31--


From nobody Fri Jan 22 15:25:59 2021
Return-Path: <superuser@gmail.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 1FD4E3A154F for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 15:25:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level: 
X-Spam-Status: No, score=-2.089 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qFPs_TmEEg3X for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 15:25:53 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A037A3A1570 for <dmarc@ietf.org>; Fri, 22 Jan 2021 15:25:53 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id e15so3985506vsa.0 for <dmarc@ietf.org>; Fri, 22 Jan 2021 15:25:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ekdRJYArC0aWN7dppFlGcHd0lSekivaGNi66LRrOe9w=; b=QpV4YiJr56uOjSZK8/QIJ0anwvU0rhwz40ErhL29F6ArruH7JDySEwFbwXRqbCut6u BeWmlmSe3lPOAOt0RsBdV/3917LNIbpqI8IvdSsNGADsIoVWpspKaYdxsKhML8yxeuoI CPNRtupezU98E0rwz0p+v+8l5bTmciXe02e9nrqVdJ/8bN9Ofq3pBGKWkRy4gnGwvjEW HsnJLAs1kAh8nT93dgC8vOeY4/kxesf10CzYz0M69u3/t30yAZvl594iTchsEJWIC04M 3/OiiRspw4yj+fy6JvG2QSWmdZw9NYZgwVigJPwz+a5AUiSHFomXqc1NKNMB7nkinOY3 +IKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ekdRJYArC0aWN7dppFlGcHd0lSekivaGNi66LRrOe9w=; b=JV8bD6nQdchxoLIBGMF6Hb1XthAdL0CP+DKStX0S1tWjAush7pJup5S1KMqZi2lInu 2tyiXv9wJviAg8is7JvXjpSJyTczAbU6RrGl+WH72C9bIcoNFbGpIavezMEi4qa5Gp/R wFW7jAPcdv9hBuTccYrnifQf88sojUI3FseHRhiNjeFQhlqRbbI7olXJc7SqnU9y7DZm 2oU7qdoZ/fIFhPJOAHDcjM+9GGSIk8/byCGyGtW56BtRs/ajKHjLviZ79y+7uOb/XlvM 438vG6kpLPTfE3ogE60lYwp5P8fa0kdtZcTC9UTXNf/iqPyA2xsILCKMazzCIq+qNWbu 6wDg==
X-Gm-Message-State: AOAM532hx2rP0eq/D1cNJb4vBcHp/mRheSZxLLbV01KI1lUzWO1UKtpn rVURpmrCByDgC4z0gYRY9b3uNieDxFEP/iisI/A=
X-Google-Smtp-Source: ABdhPJzhItuMd260gNBv6Epg/ueJmf/1CRtFpcFFLszF/oNQSg+bf/wnzprCUi/g1RthfKMSZ23IO/2N/U5kPRcbF1c=
X-Received: by 2002:a67:882:: with SMTP id 124mr251666vsi.33.1611357952504; Fri, 22 Jan 2021 15:25:52 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com>
In-Reply-To: <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 22 Jan 2021 15:25:41 -0800
Message-ID: <CAL0qLwbhhh8k-1TN6G=UX84v-92fP22=D+Q61OL2zS_9mJmUHg@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: Alessandro Vesely <vesely@tana.it>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005d7b1505b98582ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/71Cj0x5WFh7GMYEBSbL9hMoZ5ZM>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 22 Jan 2021 23:25:58 -0000

--0000000000005d7b1505b98582ed
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 3:05 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:

>
> Thinking twice, perhaps we don't need to introduce the PSL until Section
>>> 3.4.
>>> In that case, strike the last two sentences of the above paragraph.
>>>
>>
>> It's not obvious to me that this is better, but sure, let's discuss it.
>>
>>> Here's the paragraph in question
>
>      <t>To determine the organizational domain for a message under
> evaluation,
>         and thus where to look for a policy statement, DMARC makes use of
> a Public Suffix
>         List. The process for doing this can be found in Section 3.2 of
> the DMARC
>         specification.</t>
>
>
>
> The more I look at this, you need it near the top because that is where
> the discussion
> of the policy.  But also open to be convinced.
>

Looks good to me where it is.  I would add "(PSL)", introducing the
acronym, right after its first use if we decide to leave it there.

A formatting thing to take care of at some point: Anyplace you refer to
DMARC, the protocol, just have it as "DMARC" (e.g., "not exempt from DMARC
policy"); anyplace you refer to DMARC, the specification (e.g., "Section
a.b.c of DMARC" or similar), it should be the <xref target="..."> ...
</xref> sorta deal so that it pops out as a reference.

-MSK, hatless

--0000000000005d7b1505b98582ed
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 3:05 PM Tim Wicin=
ski &lt;<a href=3D"mailto:tjw.ietf@gmail.com">tjw.ietf@gmail.com</a>&gt; wr=
ote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail=
_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thinking twice, perhaps we don&#39;t need to introduce the PSL until Sectio=
n 3.4. <br>
In that case, strike the last two sentences of the above paragraph.<br></bl=
ockquote><div><br></div><div>It&#39;s not obvious to me that this is better=
, but sure, let&#39;s discuss it.</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><span class=3D"gmail_default" style=3D"font-family:monospace"=
></span></blockquote></div></div></blockquote><font face=3D"monospace"><spa=
n class=3D"gmail_default" style=3D"font-family:monospace"></span><div class=
=3D"gmail_quote"><font face=3D"monospace"><span class=3D"gmail_default" sty=
le=3D"font-family:monospace">Here&#39;s the paragraph in question</span><br=
></font></div><br>=C2=A0 =C2=A0 =C2=A0&lt;t&gt;To determine the organizatio=
nal domain for a message under evaluation,<br><span class=3D"gmail_default"=
 style=3D"font-family:monospace"></span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 and thu=
s where to look for a policy statement, DMARC makes use of a Public Suffix<=
br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 List. The process for doing this can be foun=
d in Section 3.2 of the DMARC<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification.=
&lt;/t&gt;</font><div style=3D"font-family:monospace"><p style=3D"margin:0p=
x;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:n=
ormal;font-size:13px;line-height:normal;font-family:&quot;Helvetica Neue&qu=
ot;"><br></p><p style=3D"margin:0px;font-variant-numeric:normal;font-varian=
t-east-asian:normal;font-stretch:normal;font-size:13px;line-height:normal;f=
ont-family:&quot;Helvetica Neue&quot;"><br></p></div><div style=3D"font-fam=
ily:monospace">The more I look at this, you need it near the top because th=
at is where the discussion</div><div style=3D"font-family:monospace">of the=
 policy.=C2=A0 But also open to be convinced. <br></div></div></div></block=
quote><div><br></div><div>Looks good to me where it is.=C2=A0 I would add &=
quot;(PSL)&quot;, introducing the acronym, right after its first use if we =
decide to leave it there.</div><div><br></div><div>A formatting thing to ta=
ke care of at some point: Anyplace you refer to DMARC, the protocol, just h=
ave it as &quot;DMARC&quot; (e.g., &quot;not exempt from DMARC policy&quot;=
); anyplace you refer to DMARC, the specification (e.g., &quot;Section a.b.=
c of DMARC&quot; or similar), it should be the &lt;xref target=3D&quot;...&=
quot;&gt; ... &lt;/xref&gt; sorta deal so that it pops out as a reference.<=
br></div><div><br></div><div>-MSK, hatless<br></div></div></div>

--0000000000005d7b1505b98582ed--


From nobody Fri Jan 22 15:28:48 2021
Return-Path: <tjw.ietf@gmail.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 809353A1574 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 15:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 bYnxZ0Jn7uq8 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 15:28:46 -0800 (PST)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F0D03A1572 for <dmarc@ietf.org>; Fri, 22 Jan 2021 15:28:45 -0800 (PST)
Received: by mail-ot1-x32c.google.com with SMTP id s2so4591800otp.5 for <dmarc@ietf.org>; Fri, 22 Jan 2021 15:28:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=S6NEuUQ2X3J2nbE7MKPy7zLu7HwPf+UeGWHJ5HwJV3Y=; b=uKl0auOaFIk8iwl2MM2Gjs6VkC2xYpYDiwMHwk2sp6NHx8lNWm17aBccuo6HgqF/aL ZYmVkDYO9ov6uVd2pupJdOuEuO76H7NgB/rdBGXjCV7Fkubpx9d7ObS6cESSMW0R4qSm 6pl4/ddpyKHNWp4pQhJS669RCWBKBMze9zlBnlWHC5AxQZTntlJJ1Co0TJbsbEj/0wa3 3U70R3P0jVDxUGMpORBxh+3N0/N5jlYHFnsbTE43QWr3Mjg2tA38TgC3wKmHfstC0bhm 4xuZwwR8WyZQvNWGVnysLKuubDsH4y12gmKCQUGB2Myrq8qXsrCYBlrNNaB+zVb8hUE/ xFRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=S6NEuUQ2X3J2nbE7MKPy7zLu7HwPf+UeGWHJ5HwJV3Y=; b=ne1sSIRUdaXDzbyehfcaUbD+Rih37z2IAWPAW0xznYmuQtpKq9wjtHZgTYLwtSGNfy CW33brgmwC13XEmaSx7qbYHYQ7MN1vdCl1VX9gA2hqlyGrHmjY41WY4sKG45RnGdwxQD iGFm4+rBgWEbs8gRoJ3G/In51EdHOKmhOD3i5OGsyOhDJWCSQHC/Dnfm9tgz6/xks8ds WP7/Yj2vWHqFiMdL0emENN7fVCadfD8WKfuESos95cgxuagIGl0vc3lBUTruueudZb1N 64i12sbvB4fRBs45KQO1M0LSQdxUYz947TeHDWon3lF6qBC7jZVyb5MXGgufB3qO/Lcw u+1A==
X-Gm-Message-State: AOAM531vnfdy1P+I1M3a0zQ5q/cun4PgtczjbweVg/NHYGClIIkyrEYb 9YFnHDfhrwRHRs52hbxUIM9h8C0mZPVF0vNsuwZw7S0L
X-Google-Smtp-Source: ABdhPJyOdVHFGgYWM4uQAOF/vuD4S1bJja6P+3GoRBZgnrlfwZ+nXXsURjT4eyw+OcPnmGCsQRkozdlzRVpXrdxdPjs=
X-Received: by 2002:a9d:3ef6:: with SMTP id b109mr5179727otc.288.1611358124474;  Fri, 22 Jan 2021 15:28:44 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CAL0qLwbhhh8k-1TN6G=UX84v-92fP22=D+Q61OL2zS_9mJmUHg@mail.gmail.com>
In-Reply-To: <CAL0qLwbhhh8k-1TN6G=UX84v-92fP22=D+Q61OL2zS_9mJmUHg@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 22 Jan 2021 18:28:32 -0500
Message-ID: <CADyWQ+HmH7f-3fQS0p2wHbojMkehPf50EBHTFR57cLYqVYbs3Q@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Alessandro Vesely <vesely@tana.it>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009da14405b9858c7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3NI0hCP5SKB0qmFmDBuO3zUmClc>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 22 Jan 2021 23:28:48 -0000

--0000000000009da14405b9858c7c
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 6:25 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Fri, Jan 22, 2021 at 3:05 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>
>>
>> Thinking twice, perhaps we don't need to introduce the PSL until Section
>>>> 3.4.
>>>> In that case, strike the last two sentences of the above paragraph.
>>>>
>>>
>>> It's not obvious to me that this is better, but sure, let's discuss it.
>>>
>>>> Here's the paragraph in question
>>
>>      <t>To determine the organizational domain for a message under
>> evaluation,
>>         and thus where to look for a policy statement, DMARC makes use of
>> a Public Suffix
>>         List. The process for doing this can be found in Section 3.2 of
>> the DMARC
>>         specification.</t>
>>
>>
>>
>> The more I look at this, you need it near the top because that is where
>> the discussion
>> of the policy.  But also open to be convinced.
>>
>
> Looks good to me where it is.  I would add "(PSL)", introducing the
> acronym, right after its first use if we decide to leave it there.
>

Will do


> A formatting thing to take care of at some point: Anyplace you refer to
> DMARC, the protocol, just have it as "DMARC" (e.g., "not exempt from DMARC
> policy"); anyplace you refer to DMARC, the specification (e.g., "Section
> a.b.c of DMARC" or similar), it should be the <xref target="..."> ...
> </xref> sorta deal so that it pops out as a reference.
>
>
Argh yes - I was removing the RFC7489 references which had the XML  bits.
 oh let me do that fix up

tim

--0000000000009da14405b9858c7c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:monospace"><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Fri, Jan 22, 2021 at 6:25 PM Murray S. Kuc=
herawy &lt;<a href=3D"mailto:superuser@gmail.com">superuser@gmail.com</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d=
ir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 3:05 PM Tim Wicinski &l=
t;<a href=3D"mailto:tjw.ietf@gmail.com" target=3D"_blank">tjw.ietf@gmail.co=
m</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thinking twice, perhaps we don&#39;t need to introduce the PSL until Sectio=
n 3.4. <br>
In that case, strike the last two sentences of the above paragraph.<br></bl=
ockquote><div><br></div><div>It&#39;s not obvious to me that this is better=
, but sure, let&#39;s discuss it.</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><span class=3D"gmail_default" style=3D"font-family:monospace"=
></span></blockquote></div></div></blockquote><font face=3D"monospace"><spa=
n class=3D"gmail_default" style=3D"font-family:monospace"></span><div class=
=3D"gmail_quote"><font face=3D"monospace"><span class=3D"gmail_default" sty=
le=3D"font-family:monospace">Here&#39;s the paragraph in question</span><br=
></font></div><br>=C2=A0 =C2=A0 =C2=A0&lt;t&gt;To determine the organizatio=
nal domain for a message under evaluation,<br><span class=3D"gmail_default"=
 style=3D"font-family:monospace"></span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 and thu=
s where to look for a policy statement, DMARC makes use of a Public Suffix<=
br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 List. The process for doing this can be foun=
d in Section 3.2 of the DMARC<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification.=
&lt;/t&gt;</font><div style=3D"font-family:monospace"><p style=3D"margin:0p=
x;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:n=
ormal;font-size:13px;line-height:normal;font-family:&quot;Helvetica Neue&qu=
ot;"><br></p><p style=3D"margin:0px;font-variant-numeric:normal;font-varian=
t-east-asian:normal;font-stretch:normal;font-size:13px;line-height:normal;f=
ont-family:&quot;Helvetica Neue&quot;"><br></p></div><div style=3D"font-fam=
ily:monospace">The more I look at this, you need it near the top because th=
at is where the discussion</div><div style=3D"font-family:monospace">of the=
 policy.=C2=A0 But also open to be convinced. <br></div></div></div></block=
quote><div><br></div><div>Looks good to me where it is.=C2=A0 I would add &=
quot;(PSL)&quot;, introducing the acronym, right after its first use if we =
decide to leave it there.</div></div></div></blockquote><div><br></div><div=
 class=3D"gmail_default" style=3D"font-family:monospace">Will do</div><div =
class=3D"gmail_default" style=3D"font-family:monospace"><br></div><div clas=
s=3D"gmail_default" style=3D"font-family:monospace"></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote=
"><div><br></div><div>A formatting thing to take care of at some point: Any=
place you refer to DMARC, the protocol, just have it as &quot;DMARC&quot; (=
e.g., &quot;not exempt from DMARC policy&quot;); anyplace you refer to DMAR=
C, the specification (e.g., &quot;Section a.b.c of DMARC&quot; or similar),=
 it should be the &lt;xref target=3D&quot;...&quot;&gt; ... &lt;/xref&gt; s=
orta deal so that it pops out as a reference.<br></div><div><br></div></div=
></div></blockquote><div><br></div><div class=3D"gmail_default" style=3D"fo=
nt-family:monospace">Argh yes - I was removing the RFC7489 references which=
 had the XML=C2=A0 bits.=C2=A0 =C2=A0oh let me do that fix up</div><div cla=
ss=3D"gmail_default" style=3D"font-family:monospace"><br></div><div class=
=3D"gmail_default" style=3D"font-family:monospace">tim</div><div class=3D"g=
mail_default" style=3D"font-family:monospace"></div></div></div>

--0000000000009da14405b9858c7c--


From nobody Fri Jan 22 16:55:26 2021
Return-Path: <kurta@drkurt.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 774323A15E6 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 16:55:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.com
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 GVQz1stMl18H for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 16:55:23 -0800 (PST)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ACD33A15E7 for <dmarc@ietf.org>; Fri, 22 Jan 2021 16:55:22 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id h11so14882112ioh.11 for <dmarc@ietf.org>; Fri, 22 Jan 2021 16:55:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z/oBPeY9dQTN7IFmrsCsxPlKO7PPW2Z+WMfMFHFxZpk=; b=DhD/WUl3adkJmRK2UPd3pHNrAzKSG8gNgz1LWRJ0v/8ZV9x9h4Hh1zqZwaXaDlrQEw QCyxdXu8zFO23sl3sVkWA+03LlQVeoMseyKpqXSEDcnEnL6sV7LCMzzyF3WcBLP0/KBn VE/srgnaL9089jcSpD5goJ4MGD4IM4ksgwo/E=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z/oBPeY9dQTN7IFmrsCsxPlKO7PPW2Z+WMfMFHFxZpk=; b=icyC80txhCzio3RkHYuOr1H07w9fAhh7z4UHKUsqTgaKd+7REZ/0SNV1ZlUjFKNss7 t8UlwO/J5BsZ5ftzdd4HMlhLrjiAxyGrBaMOkq5nu+sqnbs+RNBSl8fTZoif7YdGq8Pw STefxgyJzX4nUhX1pEIgRMGKJL1/7jIScw+zAfmsNX/G37xN7yToWXUG9hDH06AQusCK nDiF+Pi0dPGEKDvKKNGK5WDxKcyqSxNieo2ecqS9m+5C4BfhetBEID9k8vrsHcE8V04U deqU71QoWWiqpmycBKbljgGTMlCQU4CX6Fj2KhSEI+Q9XViQFVINz94KTz/rlsgOcGHU BoMA==
X-Gm-Message-State: AOAM531L9gnsYZo6dgGcIxQqbx2sfR9RyZekg3AV0tLlsdeGWB4GgoUS rZTxHeusWW33DU9Yf3H96Nj3c/nOthzi+2HolOwX8A==
X-Google-Smtp-Source: ABdhPJxMb2hYOEEOdZsCaMNwDblgNxx2qVkxzEoXFuDPcm2Rj3Qp31FiOwBP6Q6MIEU5IsRxp0jS8e8mLmo0CyWsTJk=
X-Received: by 2002:a5d:8ac8:: with SMTP id e8mr1635302iot.163.1611363322031;  Fri, 22 Jan 2021 16:55:22 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com>
In-Reply-To: <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Fri, 22 Jan 2021 16:55:05 -0800
Message-ID: <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>, Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="0000000000006a07dd05b986c20f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Te87X4zE8GnoT9e9qYrVWM08YsE>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 23 Jan 2021 00:55:25 -0000

--0000000000006a07dd05b986c20f
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:

>
> Here's the paragraph in question
>
>      <t>To determine the organizational domain for a message under
> evaluation,
>         and thus where to look for a policy statement, DMARC makes use of
> a Public Suffix
>         List. The process for doing this can be found in Section 3.2 of
> the DMARC
>         specification.</t>
>

The concern that I have with this wording is that it is (potentially)
misleading. "How" DMARC determines the org domain does not matter at all to
this spec. The important point is that we go to "org-1" in the tree for
this extra lookup.

--Kurt

--0000000000006a07dd05b986c20f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 3:06 PM Tim Wicin=
ski &lt;<a href=3D"mailto:tjw.ietf@gmail.com">tjw.ietf@gmail.com</a>&gt; wr=
ote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"font-family=
:monospace"><br></div></div><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail_defau=
lt" style=3D"font-family:monospace"></span></blockquote></div></div></block=
quote><font face=3D"monospace"><span class=3D"gmail_default" style=3D"font-=
family:monospace"></span><div class=3D"gmail_quote"><font face=3D"monospace=
"><span class=3D"gmail_default" style=3D"font-family:monospace">Here&#39;s =
the paragraph in question</span><br></font></div><br>=C2=A0 =C2=A0 =C2=A0&l=
t;t&gt;To determine the organizational domain for a message under evaluatio=
n,<br><span class=3D"gmail_default" style=3D"font-family:monospace"></span>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 and thus where to look for a policy statement, =
DMARC makes use of a Public Suffix<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 List. The=
 process for doing this can be found in Section 3.2 of the DMARC<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 specification.&lt;/t&gt;</font></div></div></blockquot=
e><div><br></div><div>The concern that I have with this wording is that it =
is (potentially) misleading. &quot;How&quot; DMARC determines the org domai=
n does not matter at all to this spec. The important point is that we go to=
 &quot;org-1&quot; in the tree for this extra lookup.</div><div><br></div><=
div>--Kurt=C2=A0</div></div></div>

--0000000000006a07dd05b986c20f--


From nobody Fri Jan 22 16:57:16 2021
Return-Path: <superuser@gmail.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 295CC3A15EB for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 16:57:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 L14DIYW-GWxF for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 16:57:12 -0800 (PST)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C64A53A15E7 for <dmarc@ietf.org>; Fri, 22 Jan 2021 16:57:12 -0800 (PST)
Received: by mail-vs1-xe2b.google.com with SMTP id e15so4069328vsa.0 for <dmarc@ietf.org>; Fri, 22 Jan 2021 16:57:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HLsH44nsfI2mAjRCxyIr5Y6zxZpkkrG5nGuDZ2jR8Ho=; b=Vco3sED+Cw/XgbadHp0xY88VS5N/U4+Qaeu2FzKNQEnim2RFLAYq5nxKYhBl0JmQr5 2wOy75wbfi0090uBN7xTJLaFK5HtI8O96tALjS79cFj5JdeaMM8TkRKKeWP+WGl6nwwD h7eqHLFWAiXRgzAbYP8ojJopr6pyw612rcIwsouy2I5O6PxWFuf0L5kaF1gyEw2CIsoT mnXvhKLV87Gnm52/z+1jHm2HiN2NkGiOryUfIixMZxpf8Flfh4nwVoXIuHRbLgHExycV KIB9AaxRdv8awC8B/LEF1Al14EBvxrUsTpNlc66WJh8A/SwcG2EzVIqk2j8bWyJ1+OaO 34nA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HLsH44nsfI2mAjRCxyIr5Y6zxZpkkrG5nGuDZ2jR8Ho=; b=DhEvfuWJHhf/I9JK9yPnJZom4batQUsKfDRUwTqZlcWyDwX3xfnehlEreFnUOvEMUz COYZUuXkfjaSiMdLedy+cOwHGRvjzNt9pv6I018WyDz9L1PrBmSfBqePewm+FDG8TkOI tEjO+22d4DuCQidJ60jgnfLwvR5JybnNS2wZHeizoQf/+KXth2RPoL2mVebgKVDiHBt2 XrWHb1tH3E1S8ASspfCP6nmcrEt2Gzp4drFaa7KcAI3Fpx8of5uOaQ8CbAUxB/L4aD3D vb0QnrGxv7YqZa7bXEJifdN1S3BLxXKHavY13Yyl7YyFfeIuI11ApPaMwr0LdJicvERt H2/A==
X-Gm-Message-State: AOAM530OK6MnOql8zpm8tW3TeVHJmsxuGqsd/JyHMOuKSNtgJ5lH/V2q rCmP0dLwmXfj+Dz1JvdBocPEOz78rZ7VnODf8VY=
X-Google-Smtp-Source: ABdhPJxcQvvSuRgZkil8eBGHYJa/SLtMK8SRh27Ld7Eq2KHz3jA+JJrZ1EPQbHnmzHTkSp2UXptHMEW45NT2fdKu/nY=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr335991vsy.54.1611363431582; Fri, 22 Jan 2021 16:57:11 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com>
In-Reply-To: <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 22 Jan 2021 16:57:00 -0800
Message-ID: <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com>
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,  Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="000000000000f190f805b986c8a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/5MwvzsFTrTybyXx_LP-7L4-6RW4>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 23 Jan 2021 00:57:14 -0000

--000000000000f190f805b986c8a3
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 4:55 PM Kurt Andersen (b) <kboth@drkurt.com> wrote:

> On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>
>>
>> Here's the paragraph in question
>>
>>      <t>To determine the organizational domain for a message under
>> evaluation,
>>         and thus where to look for a policy statement, DMARC makes use of
>> a Public Suffix
>>         List. The process for doing this can be found in Section 3.2 of
>> the DMARC
>>         specification.</t>
>>
>
> The concern that I have with this wording is that it is (potentially)
> misleading. "How" DMARC determines the org domain does not matter at all to
> this spec. The important point is that we go to "org-1" in the tree for
> this extra lookup.
>

This is just establishing context for why we're doing what the rest of the
document says (i.e., what problem we're solving).  Leaving this out seems
to me to paint an incomplete picture; Section 3 basically describes a
delta, but a delta to what?

-MSK

--000000000000f190f805b986c8a3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 4:55 PM Kurt Ande=
rsen (b) &lt;<a href=3D"mailto:kboth@drkurt.com">kboth@drkurt.com</a>&gt; w=
rote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at =
3:06 PM Tim Wicinski &lt;<a href=3D"mailto:tjw.ietf@gmail.com" target=3D"_b=
lank">tjw.ietf@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div di=
r=3D"ltr"><div style=3D"font-family:monospace"><br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><span class=3D"gmail_default" style=3D"font-family:monospace"></=
span></blockquote></div></div></blockquote><font face=3D"monospace"><span c=
lass=3D"gmail_default" style=3D"font-family:monospace"></span><div class=3D=
"gmail_quote"><font face=3D"monospace"><span class=3D"gmail_default" style=
=3D"font-family:monospace">Here&#39;s the paragraph in question</span><br><=
/font></div><br>=C2=A0 =C2=A0 =C2=A0&lt;t&gt;To determine the organizationa=
l domain for a message under evaluation,<br><span class=3D"gmail_default" s=
tyle=3D"font-family:monospace"></span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 and thus =
where to look for a policy statement, DMARC makes use of a Public Suffix<br=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 List. The process for doing this can be found =
in Section 3.2 of the DMARC<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification.&l=
t;/t&gt;</font></div></div></blockquote><div><br></div><div>The concern tha=
t I have with this wording is that it is (potentially) misleading. &quot;Ho=
w&quot; DMARC determines the org domain does not matter at all to this spec=
. The important point is that we go to &quot;org-1&quot; in the tree for th=
is extra lookup.</div></div></div></blockquote><div><br></div><div>This is =
just establishing context for why we&#39;re doing what the rest of the docu=
ment says (i.e., what problem we&#39;re solving).=C2=A0 Leaving this out se=
ems to me to paint an incomplete picture; Section 3 basically describes a d=
elta, but a delta to what?<br></div><div><br></div><div>-MSK<br></div></div=
></div>

--000000000000f190f805b986c8a3--


From nobody Fri Jan 22 16:58:42 2021
Return-Path: <kurta@drkurt.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 8B15A3A15F1 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 16:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.com
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 ueCZcIlY0e8E for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 16:58:39 -0800 (PST)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA19B3A15EC for <dmarc@ietf.org>; Fri, 22 Jan 2021 16:58:38 -0800 (PST)
Received: by mail-io1-xd2b.google.com with SMTP id n2so14960535iom.7 for <dmarc@ietf.org>; Fri, 22 Jan 2021 16:58:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=67R968Fo03106ubNP/Lyvw0+C+MwPryotAh3qv2o+h4=; b=ICqhDaCsXKf08P9PjBo/2p3MNFnJO0JCdGNPlrF9Wu5O7TLfQAuYk5OuWctBWdciCx 23GJR1c3ZTDG2UHb0mrvbaievCHlfJVzRGdpbdFVMmRhDHJ673rdbtgRyhrnLDt87hur bx3hRq59k/VVwkxdTMjp1BPimCwGYw3V1jQjA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=67R968Fo03106ubNP/Lyvw0+C+MwPryotAh3qv2o+h4=; b=LR51XEdjxnpjJRu8BporCVqQDubQnW9j6VQLkvEhQuynvTqGzht188PRo6Dn5PfRF9 aAhjTATf/DVvh88R4U3mdzG7oNhpNnzSsFEC0W5Tu39N0uzUsjg0JiM34YAp2k/Gsteu Hlg8rbVMTNhHH7grZbHRPPOey2/DLmkjZNsm873N7baTylBC2POqkzJn2TXafZH3QWNV TTNPAwoD7Hlkf3aTZocyDNlFHA2j7yadNLTduO0zebD44POUsFHMNjct4DksrDjjLsuP q6jFC5xIQZD57efOJN6OaHY1nxIpdp1cFS8SPVCzx8FY3cPdoZz89eBlIDbmBG+v8+Xf +jZA==
X-Gm-Message-State: AOAM531bljYGI2tX0JDWtb0JaMXwA/5dZf3AbXMr5nxg/TcZuFe0ReEL 5iBWZ6c6ABk5BDK5E15oo0mZl+qc75buU5SsdkC1gw==
X-Google-Smtp-Source: ABdhPJw2NFOQ0t2uk7LfT8nuXV65HmyoW3RrBAiZv8+6gP965ihzPapuUhdp/N/M+oz+lPqGD0S0ZHSM08qEdUeoVVU=
X-Received: by 2002:a02:d06:: with SMTP id 6mr952386jax.111.1611363518209; Fri, 22 Jan 2021 16:58:38 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com>
In-Reply-To: <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Fri, 22 Jan 2021 16:58:22 -0800
Message-ID: <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,  Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="0000000000001b762505b986ceb8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9uAd-uUgdbE7u70VX2D5qqLZP94>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 23 Jan 2021 00:58:41 -0000

--0000000000001b762505b986ceb8
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 4:57 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Fri, Jan 22, 2021 at 4:55 PM Kurt Andersen (b) <kboth@drkurt.com>
> wrote:
>
>> On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>
>>>
>>> Here's the paragraph in question
>>>
>>>      <t>To determine the organizational domain for a message under
>>> evaluation,
>>>         and thus where to look for a policy statement, DMARC makes use
>>> of a Public Suffix
>>>         List. The process for doing this can be found in Section 3.2 of
>>> the DMARC
>>>         specification.</t>
>>>
>>
>> The concern that I have with this wording is that it is (potentially)
>> misleading. "How" DMARC determines the org domain does not matter at all to
>> this spec. The important point is that we go to "org-1" in the tree for
>> this extra lookup.
>>
>
> This is just establishing context for why we're doing what the rest of the
> document says (i.e., what problem we're solving).  Leaving this out seems
> to me to paint an incomplete picture; Section 3 basically describes a
> delta, but a delta to what?
>

And if DMARC changes how it determines the org domain, where does that
leave this spec?

--Kurt

--0000000000001b762505b986ceb8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 4:57 PM Murray S.=
 Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com">superuser@gmail.com</=
a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, =
2021 at 4:55 PM Kurt Andersen (b) &lt;<a href=3D"mailto:kboth@drkurt.com" t=
arget=3D"_blank">kboth@drkurt.com</a>&gt; wrote:<br></div><div class=3D"gma=
il_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski &lt;<a href=
=3D"mailto:tjw.ietf@gmail.com" target=3D"_blank">tjw.ietf@gmail.com</a>&gt;=
 wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"font-fam=
ily:monospace"><br></div></div><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail_de=
fault" style=3D"font-family:monospace"></span></blockquote></div></div></bl=
ockquote><font face=3D"monospace"><span class=3D"gmail_default" style=3D"fo=
nt-family:monospace"></span><div class=3D"gmail_quote"><font face=3D"monosp=
ace"><span class=3D"gmail_default" style=3D"font-family:monospace">Here&#39=
;s the paragraph in question</span><br></font></div><br>=C2=A0 =C2=A0 =C2=
=A0&lt;t&gt;To determine the organizational domain for a message under eval=
uation,<br><span class=3D"gmail_default" style=3D"font-family:monospace"></=
span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 and thus where to look for a policy statem=
ent, DMARC makes use of a Public Suffix<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 List=
. The process for doing this can be found in Section 3.2 of the DMARC<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification.&lt;/t&gt;</font></div></div></bl=
ockquote><div><br></div><div>The concern that I have with this wording is t=
hat it is (potentially) misleading. &quot;How&quot; DMARC determines the or=
g domain does not matter at all to this spec. The important point is that w=
e go to &quot;org-1&quot; in the tree for this extra lookup.</div></div></d=
iv></blockquote><div><br></div><div>This is just establishing context for w=
hy we&#39;re doing what the rest of the document says (i.e., what problem w=
e&#39;re solving).=C2=A0 Leaving this out seems to me to paint an incomplet=
e picture; Section 3 basically describes a delta, but a delta to what?</div=
></div></div></blockquote><div><br></div><div>And if DMARC changes how it d=
etermines the org domain, where does that leave this spec?</div><div><br></=
div><div>--Kurt=C2=A0</div></div></div>

--0000000000001b762505b986ceb8--


From nobody Fri Jan 22 17:01:57 2021
Return-Path: <tjw.ietf@gmail.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 B848B3A15F6 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 17:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 imETPtfY0fBD for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 17:01:54 -0800 (PST)
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 530073A15F5 for <dmarc@ietf.org>; Fri, 22 Jan 2021 17:01:54 -0800 (PST)
Received: by mail-ot1-x332.google.com with SMTP id v21so6959829otj.3 for <dmarc@ietf.org>; Fri, 22 Jan 2021 17:01:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bmW8NF4YbTgZMrFAK3D9I2DPObZhZT09dPDmOb5Wt70=; b=oGkj86eFSutvAOlFtM5faj43gmWPafGaBXYS5reZJFh8d+JW6uHzKVSvhf6SIDRCTk asMb40u/1Dm7dV0LYLy5z8o1C5odXU0Z53t7ZZf8KsLYzuV2F4Vd2evx3PdpWrEKafdx UCcvWa5TnO3Wtt2+QpntYi1At904Y7/N8HZtJ7abzfy9gbceeOKDZeOjVHrXAJ1ySKk8 77YvSSJOKIbsqEa9pnuWWHqIx7qesLs3IUoFODv5uwptV3AkM6SJOdzmza7drphwrK27 ZEBuUVOws0t4K0EfA6QBQdfHxl8fmoLfyguuBgp9KyLjRFrvLri5zm0A5/LgZXvAfAWk asfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bmW8NF4YbTgZMrFAK3D9I2DPObZhZT09dPDmOb5Wt70=; b=WraB8u/5mtX10gd2XQP59pzehxewXQhVh+1IXiAUT3mrj+YNp6i6jtS+YUNiVZVMMA 43k6Hn5rUzUVJ2Smm2pHd7UgqzWofAWQMX9hZJZwIPGDNzpCyf9TcE1ZG/DKklRWdd/p GYJ7El1OrtegGLAlQMz/JH0umiulgvevB9qH+xQQLg7EqL9q/+CKvpR3jm6oZ5SWN70M x6P/IB0fIjfYsXGLi5FQPttMkk3yAe6rOlz5MW2mBswYcoxci3uw9p7d8C/87pgRMLSy Sl3m6t+t6UOrC06tdhdNQO++fHk1lfjxFu4ODZ1TjNfhyc4HGxF0hTsVRbZ1h6LlVwoB UI5Q==
X-Gm-Message-State: AOAM5330hFdc4bQbD+zTAhxlmQN68e3F8S4eH1lMz7XdoTQThPjaGMaH HtwobAPelewdMb1h3P3IxqQD/KxqMQ9aDstisa8=
X-Google-Smtp-Source: ABdhPJzrUw4r/Gik4sdcOPR4WzRJEz/RgUFgkq+tVVVptgd+PDScy4472yci9Qm/UlcI5/lPepaURVmd+eZjg3HdBus=
X-Received: by 2002:a05:6830:1254:: with SMTP id s20mr5333557otp.155.1611363713161;  Fri, 22 Jan 2021 17:01:53 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com> <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com>
In-Reply-To: <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 22 Jan 2021 20:01:41 -0500
Message-ID: <CADyWQ+FejAGbv8TLrGXpV_Crgi1KErKK_1-6=2jzZh+QbguK6Q@mail.gmail.com>
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>, Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="000000000000ba1d7205b986d9ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-gkTsxvXajoTnTtf_sMtjejNqcw>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 23 Jan 2021 01:01:56 -0000

--000000000000ba1d7205b986d9ce
Content-Type: text/plain; charset="UTF-8"

Kurt

Since this is an experiment, Appendix A discusses the updates that happen.
we don't actually say explicitly "if the experiment is a success, the
following changes will be made" and perhaps I should add some wording like
that.

On Fri, Jan 22, 2021 at 7:58 PM Kurt Andersen (b) <kboth@drkurt.com> wrote:

> On Fri, Jan 22, 2021 at 4:57 PM Murray S. Kucherawy <superuser@gmail.com>
> wrote:
>
>> On Fri, Jan 22, 2021 at 4:55 PM Kurt Andersen (b) <kboth@drkurt.com>
>> wrote:
>>
>>> On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>>
>>>>
>>>> Here's the paragraph in question
>>>>
>>>>      <t>To determine the organizational domain for a message under
>>>> evaluation,
>>>>         and thus where to look for a policy statement, DMARC makes use
>>>> of a Public Suffix
>>>>         List. The process for doing this can be found in Section 3.2 of
>>>> the DMARC
>>>>         specification.</t>
>>>>
>>>
>>> The concern that I have with this wording is that it is (potentially)
>>> misleading. "How" DMARC determines the org domain does not matter at all to
>>> this spec. The important point is that we go to "org-1" in the tree for
>>> this extra lookup.
>>>
>>
>> This is just establishing context for why we're doing what the rest of
>> the document says (i.e., what problem we're solving).  Leaving this out
>> seems to me to paint an incomplete picture; Section 3 basically describes a
>> delta, but a delta to what?
>>
>
> And if DMARC changes how it determines the org domain, where does that
> leave this spec?
>
> --Kurt
>

--000000000000ba1d7205b986d9ce
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e"><br></div><div class=3D"gmail_default" style=3D"font-family:monospace"><=
br></div><div class=3D"gmail_default" style=3D"font-family:monospace">Kurt<=
/div><div class=3D"gmail_default" style=3D"font-family:monospace"><br></div=
><div class=3D"gmail_default" style=3D"font-family:monospace">Since this is=
 an experiment, Appendix A discusses the updates that happen.=C2=A0 we don&=
#39;t actually=C2=A0say explicitly=C2=A0&quot;if the experiment is a succes=
s, the following changes will be made&quot; and perhaps I should add some w=
ording like that.=C2=A0</div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Fri, Jan 22, 2021 at 7:58 PM Kurt Andersen=
 (b) &lt;<a href=3D"mailto:kboth@drkurt.com">kboth@drkurt.com</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"lt=
r"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 4:57 PM Murray S. Kucherawy &lt=
;<a href=3D"mailto:superuser@gmail.com" target=3D"_blank">superuser@gmail.c=
om</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan =
22, 2021 at 4:55 PM Kurt Andersen (b) &lt;<a href=3D"mailto:kboth@drkurt.co=
m" target=3D"_blank">kboth@drkurt.com</a>&gt; wrote:<br></div><div class=3D=
"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski &lt;<a =
href=3D"mailto:tjw.ietf@gmail.com" target=3D"_blank">tjw.ietf@gmail.com</a>=
&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"font=
-family:monospace"><br></div></div><div class=3D"gmail_quote"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmai=
l_default" style=3D"font-family:monospace"></span></blockquote></div></div>=
</blockquote><font face=3D"monospace"><span class=3D"gmail_default" style=
=3D"font-family:monospace"></span><div class=3D"gmail_quote"><font face=3D"=
monospace"><span class=3D"gmail_default" style=3D"font-family:monospace">He=
re&#39;s the paragraph in question</span><br></font></div><br>=C2=A0 =C2=A0=
 =C2=A0&lt;t&gt;To determine the organizational domain for a message under =
evaluation,<br><span class=3D"gmail_default" style=3D"font-family:monospace=
"></span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 and thus where to look for a policy st=
atement, DMARC makes use of a Public Suffix<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
List. The process for doing this can be found in Section 3.2 of the DMARC<b=
r>=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification.&lt;/t&gt;</font></div></div></=
blockquote><div><br></div><div>The concern that I have with this wording is=
 that it is (potentially) misleading. &quot;How&quot; DMARC determines the =
org domain does not matter at all to this spec. The important point is that=
 we go to &quot;org-1&quot; in the tree for this extra lookup.</div></div><=
/div></blockquote><div><br></div><div>This is just establishing context for=
 why we&#39;re doing what the rest of the document says (i.e., what problem=
 we&#39;re solving).=C2=A0 Leaving this out seems to me to paint an incompl=
ete picture; Section 3 basically describes a delta, but a delta to what?</d=
iv></div></div></blockquote><div><br></div><div>And if DMARC changes how it=
 determines the org domain, where does that leave this spec?</div><div><br>=
</div><div>--Kurt=C2=A0</div></div></div>
</blockquote></div>

--000000000000ba1d7205b986d9ce--


From nobody Fri Jan 22 17:33:28 2021
Return-Path: <superuser@gmail.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 2B2E63A1622 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 17:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mp3OFhnTlvkf for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 17:33:25 -0800 (PST)
Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A82B93A1621 for <dmarc@ietf.org>; Fri, 22 Jan 2021 17:33:25 -0800 (PST)
Received: by mail-vs1-xe2d.google.com with SMTP id n18so4062652vsa.12 for <dmarc@ietf.org>; Fri, 22 Jan 2021 17:33:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ha7PNFjq0fBArZ8gK6EihWzSlCkJz+OB9DFCBC60Vsw=; b=OLTXnvN1PayuDGLopG2OpRNOvfDSWPqIbj/ajklI7FmVwPT7nncDBcebJ82pYbdy3N nnOtXBKvuMF7FQjiMgLXE4RSTYPAFoOopkTCUmgw4jbWbToVUJPZLcxeRf8J5O5j9VD8 fOlXlrOi88tSiD+An5XJLA71arJkTJvIdYsYRPM8eC/61nZyqkV6CNYUlRufjJp5F+F1 zIpMqD++uFM1qJe+CIywyqW1LAK9bEjkjoaKHLEnw0mxrudN3qv6aTx/4hTPeBYVYwpU VEgXnqNnXJTISOxN0RoK+I2vNkcc+Az8waJaI8ZJIxI8sGctFkIRGFujsZA4vMO/yXaD JMXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ha7PNFjq0fBArZ8gK6EihWzSlCkJz+OB9DFCBC60Vsw=; b=I8Z1jTNbN+vvXS8yw8V3mI4OxQxDhxoOU7gOx71BYxwEDzhBwrvGh16+9eAYM/5IAr RCDmj68Tr7bprAwqp9GgF1dnzKLQJ24Roju2V7A16fNbfS6IFY/pFAOGyaIPXhv68zBf wR9iRQ9cif08wA9wKJei5eKHVhxOOF4ciVAIxTFcWkHoReXuNJb1qPhcttdvOFU4i7a8 9ny1mctaMrqbXQL4AAjz9DI8pvlKxjqpMu38r89zf7A/6bWH9Na26nPC3k68tdszboDw fYlVEyOZT1sK+pCcWDs+k/8265Dnxm1nxoGVjNvqDthu+TjOKhuIg3bOD/78w0KYnvOO 2wVg==
X-Gm-Message-State: AOAM533PxuLl6Pbl+NxOoOdIcSCQVm9t6NTZsvrES8NFNu9eLf3QqWA+ XwH+ZGlbceDwJawxsyEkoX9TT/kta6hlDAL+RNU=
X-Google-Smtp-Source: ABdhPJx3h7jqQzTpABBS5Q4815KJ7eI4DjYJHUjMZu+UnZ810qXwM1cYa3vmBgB8QdnOb45eS4CCEPRUvI9jEZeKyWU=
X-Received: by 2002:a05:6102:808:: with SMTP id g8mr277373vsb.0.1611365604689;  Fri, 22 Jan 2021 17:33:24 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com> <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com>
In-Reply-To: <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 22 Jan 2021 17:33:13 -0800
Message-ID: <CAL0qLwZseBvzGWihW20RZpTJeQde9WfxtPhze9dNAiGuLtGYYA@mail.gmail.com>
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,  Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="000000000000788df305b9874a8f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_ZpIkVke3SIO3FUzIPS6QEfhdw8>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 23 Jan 2021 01:33:27 -0000

--000000000000788df305b9874a8f
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 4:58 PM Kurt Andersen (b) <kboth@drkurt.com> wrote:

> On Fri, Jan 22, 2021 at 4:57 PM Murray S. Kucherawy <superuser@gmail.com>
> wrote:
>
>> On Fri, Jan 22, 2021 at 4:55 PM Kurt Andersen (b) <kboth@drkurt.com>
>> wrote:
>>
>>> On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>>
>>>>
>>>> Here's the paragraph in question
>>>>
>>>>      <t>To determine the organizational domain for a message under
>>>> evaluation,
>>>>         and thus where to look for a policy statement, DMARC makes use
>>>> of a Public Suffix
>>>>         List. The process for doing this can be found in Section 3.2 of
>>>> the DMARC
>>>>         specification.</t>
>>>>
>>>
>>> The concern that I have with this wording is that it is (potentially)
>>> misleading. "How" DMARC determines the org domain does not matter at all to
>>> this spec. The important point is that we go to "org-1" in the tree for
>>> this extra lookup.
>>>
>>
>> This is just establishing context for why we're doing what the rest of
>> the document says (i.e., what problem we're solving).  Leaving this out
>> seems to me to paint an incomplete picture; Section 3 basically describes a
>> delta, but a delta to what?
>>
>
> And if DMARC changes how it determines the org domain, where does that
> leave this spec?
>

Do we need more than the reference(s) to RFC 7489?

-MSK

--000000000000788df305b9874a8f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 4:58 PM Kurt Ande=
rsen (b) &lt;<a href=3D"mailto:kboth@drkurt.com">kboth@drkurt.com</a>&gt; w=
rote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at =
4:57 PM Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com" targ=
et=3D"_blank">superuser@gmail.com</a>&gt; wrote:<br></div><div class=3D"gma=
il_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 4:55 PM Kurt Andersen (b) &lt;<a=
 href=3D"mailto:kboth@drkurt.com" target=3D"_blank">kboth@drkurt.com</a>&gt=
; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 =
at 3:06 PM Tim Wicinski &lt;<a href=3D"mailto:tjw.ietf@gmail.com" target=3D=
"_blank">tjw.ietf@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div style=3D"font-family:monospace"><br></div></div><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><span class=3D"gmail_default" style=3D"font-family:monospace"><=
/span></blockquote></div></div></blockquote><font face=3D"monospace"><span =
class=3D"gmail_default" style=3D"font-family:monospace"></span><div class=
=3D"gmail_quote"><font face=3D"monospace"><span class=3D"gmail_default" sty=
le=3D"font-family:monospace">Here&#39;s the paragraph in question</span><br=
></font></div><br>=C2=A0 =C2=A0 =C2=A0&lt;t&gt;To determine the organizatio=
nal domain for a message under evaluation,<br><span class=3D"gmail_default"=
 style=3D"font-family:monospace"></span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 and thu=
s where to look for a policy statement, DMARC makes use of a Public Suffix<=
br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 List. The process for doing this can be foun=
d in Section 3.2 of the DMARC<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification.=
&lt;/t&gt;</font></div></div></blockquote><div><br></div><div>The concern t=
hat I have with this wording is that it is (potentially) misleading. &quot;=
How&quot; DMARC determines the org domain does not matter at all to this sp=
ec. The important point is that we go to &quot;org-1&quot; in the tree for =
this extra lookup.</div></div></div></blockquote><div><br></div><div>This i=
s just establishing context for why we&#39;re doing what the rest of the do=
cument says (i.e., what problem we&#39;re solving).=C2=A0 Leaving this out =
seems to me to paint an incomplete picture; Section 3 basically describes a=
 delta, but a delta to what?</div></div></div></blockquote><div><br></div><=
div>And if DMARC changes how it determines the org domain, where does that =
leave this spec?</div></div></div></blockquote><div><br></div><div>Do we ne=
ed more than the reference(s) to RFC 7489?</div><div><br></div><div>-MSK<br=
></div></div></div>

--000000000000788df305b9874a8f--


From nobody Fri Jan 22 18:44:19 2021
Return-Path: <tjw.ietf@gmail.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 966D43A09E7 for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 18:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 lNDeHYceS0wl for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 18:44:17 -0800 (PST)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DC7F3A09E3 for <dmarc@ietf.org>; Fri, 22 Jan 2021 18:44:17 -0800 (PST)
Received: by mail-ot1-x333.google.com with SMTP id v21so7115490otj.3 for <dmarc@ietf.org>; Fri, 22 Jan 2021 18:44:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MnXW4tJ6tu+n6fVBJgXPlDBDrRJr+GM5G3ZaQAysFvo=; b=LmV2/yJkdDIKq+1bkQR/y3oxU/GrMfoIGqpqlnIZx6wec1DElV4KmRSIpJu/eZj7Iz xx9ZMnF/03DkP9+IfmzNg0IbIPtz9FrFe4YZxImcGpbYAynOCXCfawV/vb/ztovG2ug5 KoVuppZGxxxTmKlIdHeBgJijZ+OEDUR9voln2r+qggaN6qAXSzaZSV13xBB/ki7JwqhI RnoNw/2rWfA0u8jnzt6dM1JrygBWQYVBY/XqhUye44VBc09lzyCyo4MAaZTs8Pxio2U+ wEPHOtNM2Wd3gSlpjEfg/S9H9F4uy0zL++XLb7ZZTc1ENy1q7VXOfyQVKbHuSEt5r1c5 V4lQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MnXW4tJ6tu+n6fVBJgXPlDBDrRJr+GM5G3ZaQAysFvo=; b=Y9nRkwdr7VSXuNgWUH2Tnulfc/j1BiV33Y95UWLXCyNoXwfg7RLZ9U5gvds4dmj4ho UKf6laSTT8Vcl7nlBXFO8ZLvh2tRxLSd17MyyAGQhj3kYfIaPwN5TOtbh3eFWZVrKWy2 rvHFqU9ClSXTaDL/qeyI7LwxlO/mnA4TJohcz3AIzVW0+bF9LzfP+riBgIRzI5jVab5+ TWoAJBuGTNHeQb+L/dheZn+wO/7ZK/h8aXn8lG0mk34bwe/4z7gQ15fRcAiLk8hq0RT2 K9wXD780paEL2j08Bs/i8QkRnv3ozCTx1VTTCpuFPPszkKM86xRKKwMR9L91dVBM25Tz XZCQ==
X-Gm-Message-State: AOAM533Ws/BDnRI61tzymZ2y+/oAXe+XpzrH2iPs5/Rrrp7OshgbV+vr +pO8/g/ZhJYfFzWsqUWQkTc3RbpOuyMES7GVMO0=
X-Google-Smtp-Source: ABdhPJyWYUFj3Hqb8uMbg7Y+1f9VbNauOghQkVS4urSlnEtGs+QuKpDN0YQaSLpG4bL7dkR/mnwKd9KAXjog89tw5Xw=
X-Received: by 2002:a05:6830:1254:: with SMTP id s20mr5564321otp.155.1611369856527;  Fri, 22 Jan 2021 18:44:16 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CAL0qLwbhhh8k-1TN6G=UX84v-92fP22=D+Q61OL2zS_9mJmUHg@mail.gmail.com>
In-Reply-To: <CAL0qLwbhhh8k-1TN6G=UX84v-92fP22=D+Q61OL2zS_9mJmUHg@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 22 Jan 2021 21:44:05 -0500
Message-ID: <CADyWQ+GoHDt=MUo=XeF9Bfi8yO8C1VB=+vynXtV6Ebb900z7sA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Alessandro Vesely <vesely@tana.it>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e66fa905b98847d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZuMXQx51BBJsYOfPiein3YHSVJU>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 23 Jan 2021 02:44:19 -0000

--000000000000e66fa905b98847d7
Content-Type: text/plain; charset="UTF-8"

(this is really for Murray)

On Fri, Jan 22, 2021 at 6:25 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

>
> Looks good to me where it is.  I would add "(PSL)", introducing the
> acronym, right after its first use if we decide to leave it there.
>
> A formatting thing to take care of at some point: Anyplace you refer to
> DMARC, the protocol, just have it as "DMARC" (e.g., "not exempt from DMARC
> policy"); anyplace you refer to DMARC, the specification (e.g., "Section
> a.b.c of DMARC" or similar), it should be the <xref target="..."> ...
> </xref> sorta deal so that it pops out as a reference.
>
>
So the xref for RFC7489 were created of this form:

<xref target="RFC7489">DMARC</xref>

and submitted into the submission system, the HTML document will have this look:


DMARC [RFC7489]   (Link is mapped to [RFC7489])

and the HTML is

[<a href="./rfc7489" title="&quot;Domain-based Message Authentication,
Reporting, and Conformance (DMARC)&quot;">RFC7489</a>]However, when I
run xml2rfc (v3.5.0) locally the


However, when I run xml2rfc (v3.5.0) locally, the HTML shows the text
"DMARC" as a link

and the HTML is

<a href="#RFC7489" class="xref">DMARC</a>


So this makes my brain hurt. I'm going to revisit this in the morning.

tim

--000000000000e66fa905b98847d7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:monospace">(this is really=C2=A0for Murray)</div></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 22, 2=
021 at 6:25 PM Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@gmail.co=
m">superuser@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div><br>=
</div><div>Looks good to me where it is.=C2=A0 I would add &quot;(PSL)&quot=
;, introducing the acronym, right after its first use if we decide to leave=
 it there.</div><div><br></div><div>A formatting thing to take care of at s=
ome point: Anyplace you refer to DMARC, the protocol, just have it as &quot=
;DMARC&quot; (e.g., &quot;not exempt from DMARC policy&quot;); anyplace you=
 refer to DMARC, the specification (e.g., &quot;Section a.b.c of DMARC&quot=
; or similar), it should be the &lt;xref target=3D&quot;...&quot;&gt; ... &=
lt;/xref&gt; sorta deal so that it pops out as a reference.<br></div><div><=
br></div></div></div></blockquote><div><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:monospace">So the xref for RFC7489=C2=A0were create=
d of this form:</div><div class=3D"gmail_default" style=3D"font-family:mono=
space"><br></div></div><blockquote style=3D"margin:0 0 0 40px;border:none;p=
adding:0px"><div class=3D"gmail_quote"><div class=3D"gmail_default" style=
=3D"font-family:monospace">&lt;xref target=3D&quot;RFC7489&quot;&gt;DMARC&l=
t;/xref&gt;</div><div class=3D"gmail_default" style=3D"font-family:monospac=
e"><span style=3D"white-space:pre-wrap;color:rgb(0,0,0)"></span><br></div><=
/div></blockquote><pre class=3D"gmail-newpage" style=3D"margin-top:0px;marg=
in-bottom:0px;break-before:page;color:rgb(0,0,0)"><span class=3D"gmail_defa=
ult" style=3D"font-family:monospace">and submitted into the submission syst=
em, the HTML document will have this look:</span></pre><pre class=3D"gmail-=
newpage" style=3D"margin-top:0px;margin-bottom:0px;break-before:page;color:=
rgb(0,0,0)"><br></pre><blockquote style=3D"margin:0 0 0 40px;border:none;pa=
dding:0px"><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px">=
</blockquote></blockquote><blockquote style=3D"margin:0 0 0 40px;border:non=
e;padding:0px"><span style=3D"font-family:monospace">DMARC [RFC7489]<span c=
lass=3D"gmail_default" style=3D"font-family:monospace">=C2=A0 =C2=A0</span>=
</span><span class=3D"gmail_default" style=3D""><font face=3D"monospace">(L=
ink is mapped to [RFC7489])</font></span><span style=3D"font-family:monospa=
ce">=C2=A0</span></blockquote><font face=3D"monospace"><span class=3D"gmail=
_default" style=3D"font-family:monospace"></span></font><div><font face=3D"=
monospace"><span class=3D"gmail_default" style=3D"font-family:monospace">an=
d the HTML is=C2=A0</span></font></div><div><font face=3D"monospace"><span =
class=3D"gmail_default" style=3D"font-family:monospace"></span><br></font><=
/div><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px"><div><=
pre class=3D"gmail-newpage" style=3D"margin-top:0px;margin-bottom:0px;break=
-before:page;color:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34)">[&lt;a h=
ref=3D&quot;./rfc7489&quot; title=3D&quot;&amp;quot;Domain-based Message Au=
thentication, Reporting, and Conformance (DMARC)&amp;quot;&quot;&gt;RFC7489=
&lt;/a&gt;]</span><span style=3D"color:rgb(34,34,34)">However, when I run x=
ml2rfc (v3.5.0) locally the </span></pre></div></blockquote><div><div><pre =
id=3D"gmail-line1"><br></pre><pre id=3D"gmail-line1"><span class=3D"gmail_d=
efault" style=3D"font-family:monospace">However, when I run xml2rfc (v3.5.0=
) locally, the HTML shows the text &quot;DMARC&quot; as a link </span><br><=
/pre><pre id=3D"gmail-line1"><span class=3D"gmail_default" style=3D"font-fa=
mily:monospace"></span><span class=3D"gmail_default" style=3D"font-family:m=
onospace">and the HTML is </span></pre></div></div><blockquote style=3D"mar=
gin:0 0 0 40px;border:none;padding:0px"><div><div><pre id=3D"gmail-line1">&=
lt;<span class=3D"gmail-start-tag">a</span> <span class=3D"gmail-attribute-=
name">href</span>=3D&quot;<a class=3D"gmail-attribute-value">#RFC7489</a>&q=
uot; <span class=3D"gmail-attribute-name">class</span>=3D&quot;<a class=3D"=
gmail-attribute-value">xref</a>&quot;&gt;DMARC&lt;/<span class=3D"end-tag">=
a</span>&gt; <span class=3D"gmail_default" style=3D"font-family:monospace">=
</span></pre></div></div></blockquote><font face=3D"monospace"><span style=
=3D"white-space:pre"><br></span></font><div><font face=3D"monospace"><span =
style=3D"white-space:pre"><span class=3D"gmail_default" style=3D"font-famil=
y:monospace">So this makes my brain hurt.  I&#39;m going to revisit this in=
 the morning.</span><br></span></font></div><div><font face=3D"monospace"><=
span style=3D"white-space:pre"><span class=3D"gmail_default" style=3D"font-=
family:monospace"><br></span></span></font></div><div><font face=3D"monospa=
ce"><span style=3D"white-space:pre"><span class=3D"gmail_default" style=3D"=
font-family:monospace">tim</span></span></font></div><div><font face=3D"mon=
ospace"><span style=3D"white-space:pre"><span class=3D"gmail_default" style=
=3D"font-family:monospace"><br></span></span></font></div></div>

--000000000000e66fa905b98847d7--


From nobody Fri Jan 22 20:13:21 2021
Return-Path: <superuser@gmail.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 E30863A0B3A for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 20:13:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4QGhNHW-hhfm for <dmarc@ietfa.amsl.com>; Fri, 22 Jan 2021 20:13:18 -0800 (PST)
Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62F003A0B41 for <dmarc@ietf.org>; Fri, 22 Jan 2021 20:13:18 -0800 (PST)
Received: by mail-vk1-xa2d.google.com with SMTP id q66so1869062vke.0 for <dmarc@ietf.org>; Fri, 22 Jan 2021 20:13:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tc4WniwVZujzhSdC+HKsw0nk9rxeS2uz1vLtMgy/YEw=; b=meSrF8tJs/KeM2Eiv3U06cajiQnohxPqHiu/Q+6o93ZOE8SIYzXgweWqvkUh0SgHGS 8Y0AFmE40qLoHOoqhUhUVeO6ckMXn+7HtppkttLUAZR+q8m0M23SoQd/oHcBucJeEQ5x ygyFEfYVEgIqlfFw5OLTjoaE/CHTfgPZvdhH1yn28eMCTBYvCbXsKY1o3DRYGGl+n7bI svKwIHhqUhb9sBchaPLUxOQjNlWMCfW0V0jsnBy4bUYBabSQp3JXjNehpJtKkXOEbDBR 4N+leFkQR6KLNeFJtBKu/0465LbeHxhI2DUBb8SI0A1wojyy+NoK0y9md7ZSv6/pcpKA 0H6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tc4WniwVZujzhSdC+HKsw0nk9rxeS2uz1vLtMgy/YEw=; b=jQr98B57OCL53rr8JnV+tLRv23HmiSuJ7BEbKsRgNQefREZE4oZmwDlpi7caJxOu68 Af5dlqudQXai+dKkL6/nMyiYtg9tUMnnfX0u/4lMsDTRQlzvHOLN2HX7PrKnZsnXXAKv vUeKmqqmjiOD+hw6a5G8WEYeLr6fzAjW44vSOC3gx07cvskdWwkGxx3PJqZENHTtRCke I4HNO0f+1LQBUSXGDgFdfyFk9yV1UMuDNcuQX+BTL43t7GNVNtkoPJ8GUDbC3SpIkojF gnBkE7wudqAUcHpeZHQlAOv+Es9hr/nMrWS1RyuzKKxln+HXRsBW2deMNweHmXJCCzq3 7etA==
X-Gm-Message-State: AOAM532q4TZjoufGrCQIX0hRqZZB/j6GandVPxqPeN+a6y9GXXVeCdy2 p2k3RR8hbvnx4lTKk4SRIjP4563Xz7nr4QKYfPc=
X-Google-Smtp-Source: ABdhPJy2MWBtFoC0xnl1Wuvx6hXfDqPnjUlq5+9lpnaKa0RLmvsBmmC01uE/+acToyNIjLIfcFpPg4OjJ6+DF0ti8uM=
X-Received: by 2002:a1f:30cd:: with SMTP id w196mr61507vkw.13.1611375197182; Fri, 22 Jan 2021 20:13:17 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CAL0qLwbhhh8k-1TN6G=UX84v-92fP22=D+Q61OL2zS_9mJmUHg@mail.gmail.com> <CADyWQ+GoHDt=MUo=XeF9Bfi8yO8C1VB=+vynXtV6Ebb900z7sA@mail.gmail.com>
In-Reply-To: <CADyWQ+GoHDt=MUo=XeF9Bfi8yO8C1VB=+vynXtV6Ebb900z7sA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 22 Jan 2021 20:13:03 -0800
Message-ID: <CAL0qLwYBzqsS1FMOFEVgCuiKFgAKbUCja0i4361qqvKo+nYbOg@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: Alessandro Vesely <vesely@tana.it>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003a612605b98986f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/V5Pe8HjZfOK0DkpB4yna60LIGik>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 23 Jan 2021 04:13:20 -0000

--0000000000003a612605b98986f5
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 6:44 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:

> (this is really for Murray)
>
> On Fri, Jan 22, 2021 at 6:25 PM Murray S. Kucherawy <superuser@gmail.com>
> wrote:
>
>>
>> Looks good to me where it is.  I would add "(PSL)", introducing the
>> acronym, right after its first use if we decide to leave it there.
>>
>> A formatting thing to take care of at some point: Anyplace you refer to
>> DMARC, the protocol, just have it as "DMARC" (e.g., "not exempt from DMARC
>> policy"); anyplace you refer to DMARC, the specification (e.g., "Section
>> a.b.c of DMARC" or similar), it should be the <xref target="..."> ...
>> </xref> sorta deal so that it pops out as a reference.
>>
>>
> So the xref for RFC7489 were created of this form:
>
> <xref target="RFC7489">DMARC</xref>
>
> and submitted into the submission system, the HTML document will have this look:
>
>
> DMARC [RFC7489]   (Link is mapped to [RFC7489])
>
> and the HTML is
>
> [<a href="./rfc7489" title="&quot;Domain-based Message Authentication, Reporting, and Conformance (DMARC)&quot;">RFC7489</a>]However, when I run xml2rfc (v3.5.0) locally the
>
>
> However, when I run xml2rfc (v3.5.0) locally, the HTML shows the text "DMARC" as a link
>
> and the HTML is
>
> <a href="#RFC7489" class="xref">DMARC</a>
>
>
> So this makes my brain hurt. I'm going to revisit this in the morning.
>

For the ones that should actually be document references, try just <xref
target="RFC7489"/>.

-MSK

--0000000000003a612605b98986f5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 6:44 PM Tim Wicin=
ski &lt;<a href=3D"mailto:tjw.ietf@gmail.com">tjw.ietf@gmail.com</a>&gt; wr=
ote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"font-family=
:monospace">(this is really=C2=A0for Murray)</div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 22, 2021 at 6=
:25 PM Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com" targe=
t=3D"_blank">superuser@gmail.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote=
"><div><br></div><div>Looks good to me where it is.=C2=A0 I would add &quot=
;(PSL)&quot;, introducing the acronym, right after its first use if we deci=
de to leave it there.</div><div><br></div><div>A formatting thing to take c=
are of at some point: Anyplace you refer to DMARC, the protocol, just have =
it as &quot;DMARC&quot; (e.g., &quot;not exempt from DMARC policy&quot;); a=
nyplace you refer to DMARC, the specification (e.g., &quot;Section a.b.c of=
 DMARC&quot; or similar), it should be the &lt;xref target=3D&quot;...&quot=
;&gt; ... &lt;/xref&gt; sorta deal so that it pops out as a reference.<br><=
/div><div><br></div></div></div></blockquote><div><br></div><div style=3D"f=
ont-family:monospace">So the xref for RFC7489=C2=A0were created of this for=
m:</div><div style=3D"font-family:monospace"><br></div></div><blockquote st=
yle=3D"margin:0px 0px 0px 40px;border:medium none;padding:0px"><div class=
=3D"gmail_quote"><div style=3D"font-family:monospace">&lt;xref target=3D&qu=
ot;RFC7489&quot;&gt;DMARC&lt;/xref&gt;</div><div style=3D"font-family:monos=
pace"><span style=3D"white-space:pre-wrap;color:rgb(0,0,0)"></span><br></di=
v></div></blockquote><pre style=3D"margin-top:0px;margin-bottom:0px;break-b=
efore:page;color:rgb(0,0,0)"><span class=3D"gmail_default" style=3D"font-fa=
mily:monospace">and submitted into the submission system, the HTML document=
 will have this look:</span></pre><pre style=3D"margin-top:0px;margin-botto=
m:0px;break-before:page;color:rgb(0,0,0)"><br></pre><blockquote style=3D"ma=
rgin:0px 0px 0px 40px;border:medium none;padding:0px"><blockquote style=3D"=
margin:0px 0px 0px 40px;border:medium none;padding:0px"></blockquote></bloc=
kquote><blockquote style=3D"margin:0px 0px 0px 40px;border:medium none;padd=
ing:0px"><span style=3D"font-family:monospace">DMARC [RFC7489]<span class=
=3D"gmail_default" style=3D"font-family:monospace">=C2=A0 =C2=A0</span></sp=
an><span class=3D"gmail_default"><font face=3D"monospace">(Link is mapped t=
o [RFC7489])</font></span><span style=3D"font-family:monospace">=C2=A0</spa=
n></blockquote><font face=3D"monospace"><span class=3D"gmail_default" style=
=3D"font-family:monospace"></span></font><div><font face=3D"monospace"><spa=
n class=3D"gmail_default" style=3D"font-family:monospace">and the HTML is=
=C2=A0</span></font></div><div><font face=3D"monospace"><span class=3D"gmai=
l_default" style=3D"font-family:monospace"></span><br></font></div><blockqu=
ote style=3D"margin:0px 0px 0px 40px;border:medium none;padding:0px"><div><=
pre style=3D"margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0=
,0,0)"><span style=3D"color:rgb(34,34,34)">[&lt;a href=3D&quot;./rfc7489&qu=
ot; title=3D&quot;&amp;quot;Domain-based Message Authentication, Reporting,=
 and Conformance (DMARC)&amp;quot;&quot;&gt;RFC7489&lt;/a&gt;]</span><span =
style=3D"color:rgb(34,34,34)">However, when I run xml2rfc (v3.5.0) locally =
the </span></pre></div></blockquote><div><div><pre id=3D"gmail-m_-802480920=
3178754767gmail-line1"><br></pre><pre id=3D"gmail-m_-8024809203178754767gma=
il-line1"><span class=3D"gmail_default" style=3D"font-family:monospace">How=
ever, when I run xml2rfc (v3.5.0) locally, the HTML shows the text &quot;DM=
ARC&quot; as a link </span><br></pre><pre id=3D"gmail-m_-802480920317875476=
7gmail-line1"><span class=3D"gmail_default" style=3D"font-family:monospace"=
></span><span class=3D"gmail_default" style=3D"font-family:monospace">and t=
he HTML is </span></pre></div></div><blockquote style=3D"margin:0px 0px 0px=
 40px;border:medium none;padding:0px"><div><div><pre id=3D"gmail-m_-8024809=
203178754767gmail-line1">&lt;<span>a</span> <span>href</span>=3D&quot;<a>#R=
FC7489</a>&quot; <span>class</span>=3D&quot;<a>xref</a>&quot;&gt;DMARC&lt;/=
<span>a</span>&gt; <span class=3D"gmail_default" style=3D"font-family:monos=
pace"></span></pre></div></div></blockquote><font face=3D"monospace"><span =
style=3D"white-space:pre-wrap"><br></span></font><div><font face=3D"monospa=
ce"><span style=3D"white-space:pre-wrap"><span class=3D"gmail_default" styl=
e=3D"font-family:monospace">So this makes my brain hurt.  I&#39;m going to =
revisit this in the morning.</span><br></span></font></div></div></blockquo=
te><div><br></div><div>For the ones that should actually be document refere=
nces, try just &lt;xref target=3D&quot;RFC7489&quot;/&gt;.</div><div><br></=
div><div>-MSK<br></div></div></div>

--0000000000003a612605b98986f5--


From nobody Sat Jan 23 03:20:59 2021
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 50F533A0FD1 for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 03:20:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 X3Ie_KYoyqc9 for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 03:20:55 -0800 (PST)
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 AF1013A0FD0 for <dmarc@ietf.org>; Sat, 23 Jan 2021 03:20:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611400852; bh=tK7ly/WzesLCMwAKCdi4vYk+eEyoO3ZpZVyzsBfXNF0=; l=500; h=To:References:From:Date:In-Reply-To; b=CogNPU7hSNYbmVDYLUJEET6zRsmJG97omdp3GEyy4rEBh4RaKiQktFVqISwNqoW1N 1ib7OYQ/tNoesmfC6WEGCMtyCMpBG1GavZa84uh4G0V1ICX3fh6cT6RZaxv0V63Qsy Ns2zn57IKrEFGL4NlzWqFRASWJVyVmy08S2z3uvTvliqrF20hdAyMmCOAKFhp
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0CF.00000000600C0694.00000312; Sat, 23 Jan 2021 12:20:52 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org, emgu@google.com
References: <20210122224018.E63E06BF246B@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it>
Date: Sat, 23 Jan 2021 12:20:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210122224018.E63E06BF246B@ary.qy>
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/P7ON8LTfnDEVTNo9D3GXeWxioDs>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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, 23 Jan 2021 11:20:57 -0000

On Fri 22/Jan/2021 23:40:18 +0100 John Levine wrote:
> 
> As someone said, the better the spammers align their stuff, the better
> we can filter it.


100% agreed.


> Close this, please.


Please don't.  That such a doubt can cross the minds even of knowledgeable 
people is a real issue.  At a minimum, the paragraph I cited[*] should be 
restored.  A crispy further clarification is welcome.

Best
Ale
-- 

[*] https://mailarchive.ietf.org/arch/msg/dmarc/HRAR3hSdckw3mU_Gebh8vcYOjm4















From nobody Sat Jan 23 03:28:52 2021
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 178A43A0FF0 for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 03:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 91KfOORtzWE6 for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 03:28:49 -0800 (PST)
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 A14FA3A0FEF for <dmarc@ietf.org>; Sat, 23 Jan 2021 03:28:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611401327; bh=WPdSlYGxRPjcxxNXW87YzUMOcvtlCBq/Yv6ocVsG4kQ=; l=950; h=To:References:From:Date:In-Reply-To; b=AClaklc5Sx0uMf+LyNXjl2bOY7cQa9qwbScR5g/1uktpjOSxteD1YX22xEGN+ERF8 XHdMlwgrqI+8v7SiaK6XdcWTHBR2mjhPHSnvjIFtx+tz993izn4fpymdXS4SLoBWgV kfs0EVID2n6pVomBjHVToLvwnXpGCfSFL0zqWlHAVFK0JOElCL4htyeOUbNhc
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000600C086F.000003BF; Sat, 23 Jan 2021 12:28:47 +0100
To: dmarc@ietf.org
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <70f6215a-4796-f3ee-3a18-5b91f553f4ca@tana.it>
Date: Sat, 23 Jan 2021 12:28:45 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@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/aFhoZs29C4jlGn8XBW3paAFLkao>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 23 Jan 2021 11:28:51 -0000

On Sat 23/Jan/2021 01:55:05 +0100 Kurt Andersen (b) wrote:
> On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
> 
>> Here's the paragraph in question
>>
>>      <t>To determine the organizational domain for a message under evaluation,
>>         and thus where to look for a policy statement, DMARC makes use of a Public Suffix
>>         List. The process for doing this can be found in Section 3.2 of the DMARC
>>         specification.</t>
>>
> 
> The concern that I have with this wording is that it is (potentially)
> misleading. "How" DMARC determines the org domain does not matter at all to
> this spec. The important point is that we go to "org-1" in the tree for
> this extra lookup.


+1.  If we don't assume that readers already know what the PSL is, trying to 
establish that context in the Introduction is only a complication.  Later on, 
when Section 3 explains technicalities, the PSL has full citizenship.


jm2c
Ale
-- 














From nobody Sat Jan 23 06:14:07 2021
Return-Path: <dougfoster.emailstandards@gmail.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 3D50D3A11E8 for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 06:14:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 5gatjGK4PcSM for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 06:14:04 -0800 (PST)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B6B43A11E7 for <dmarc@ietf.org>; Sat, 23 Jan 2021 06:14:04 -0800 (PST)
Received: by mail-ua1-x92a.google.com with SMTP id k47so2842485uad.1 for <dmarc@ietf.org>; Sat, 23 Jan 2021 06:14:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1IWNeey2qnWyK+WqzHd9D+g6P9EVm3I+BIfeqXBOrR0=; b=UQXmuSKo16SlqikKO3u2A0adHZi10pakTQCwe8cu4zNRwJDPmU5pVQr5cwPQb8yueY ROnOWCBKEkxO3Ng8fwl7m4NDDOb86+83HF854oeQfcwqlWxFUExgT0DWcNVFao1sFH2K brzqyUlcjkQi239wtfVkcFofnGcxTWF7wLtV90k6955/tY0Iqg9CDivkiYSGS6oiItnt b4gQbeZzFLLes5fmLiknHQaqWYaSl0mWKzvKksGJRLRr07EoPiI7cfT1PwZBGMOE2EAh lyWn1FFAX0nv/0+WPQm837lAqduphBsJghp+ny/0vr2BO79P4LGs5pCw6VNeoxJqMo7q GvuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1IWNeey2qnWyK+WqzHd9D+g6P9EVm3I+BIfeqXBOrR0=; b=KZH7e65+WcXY64LuumFa8POJQraD6IV2xvWAGDHaQdH0Rtq76IJP72+qwZPCCfDUxd SP21PHMOI5bMsau8jTZBXOZlToNnMEPObv+rP1bmRpDQAurjMQ+6BAX0L75KF/oRPAZr BvEcNQhg6IS5LetGMzbLW5SOowU0Ewsp0uiifjxIYW52dgX5dKjfv89/wISS1SHr5W8d +UbSMQXEg+h0xznYFKGze1MHwr7bNsYNQw7tBaN5mFrfHB7Sp0sk+dNbyNOHgCo9ESMO lGEUSGpQJqrZIQjk0QPKdW1r5+KNKBQPeIzIpcDEzwDY8zgPjvwoEAc1f9cMesKjPsm3 QCKg==
X-Gm-Message-State: AOAM530kQPafcpVhK3/iUpAc+dGdC/FHLwHqejwulMHaqxD6h/19ugLn ggO4M05J1gN9S7noy1d9k+FzL4Z3sdSFE37RKOA=
X-Google-Smtp-Source: ABdhPJyEI3QpV+MFngQ9hamgF2eH2E4JlbQy/xPwQA2XXXvuvTtuZPlbkdCMd8sW90lesCDE+LNWDd4KNzpMXF5qBMo=
X-Received: by 2002:ab0:768:: with SMTP id h95mr347643uah.104.1611411243292; Sat, 23 Jan 2021 06:14:03 -0800 (PST)
MIME-Version: 1.0
References: <20210122224018.E63E06BF246B@ary.qy> <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it>
In-Reply-To: <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 23 Jan 2021 09:13:53 -0500
Message-ID: <CAH48ZfyvjDQoqQp29LG07tz4g_eRMRboJdQ=qK8kzhyyknbMCg@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: John Levine <johnl@taugh.com>, IETF DMARC WG <dmarc@ietf.org>, emgu@google.com
Content-Type: multipart/alternative; boundary="000000000000be5a6305b991ea54"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Kru-hg0e1-1ffJkYVxV3sl7c53M>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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, 23 Jan 2021 14:14:06 -0000

--000000000000be5a6305b991ea54
Content-Type: text/plain; charset="UTF-8"

The zeal with which the status quo is being defended suggests that
disposition reporting is pretty valuable to legitimate sending domains.
However, this situation complicates any effort to argue that such
information is useless and harmless for malicious domains.   Such a fine
distinction has not yet been justified.

I can fully endorse Murray's position that alignment reporting is
beneficial, even when the sending domain is malicious.   However, it is
also off-topic.   My focus is on disposition reporting, not alignment
reporting.

Bottom line:  The perceived risk of disposition reporting will differ with
each person, and therefore with each reporting domain.    The specification
would be improved by providing a way for skeptical domain owners to redact
information that they do not wish to disclose.   Currently, the options are
to (a) not report at all, or (b) report ambiguous and slightly misleading
information such as "dispostion=quarantine, overridereason=other".   A
better option would be to have options to state
"dispositioin=not specified, overridereason=not specified".


On Sat, Jan 23, 2021 at 6:21 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Fri 22/Jan/2021 23:40:18 +0100 John Levine wrote:
> >
> > As someone said, the better the spammers align their stuff, the better
> > we can filter it.
>
>
> 100% agreed.
>
>
> > Close this, please.
>
>
> Please don't.  That such a doubt can cross the minds even of knowledgeable
> people is a real issue.  At a minimum, the paragraph I cited[*] should be
> restored.  A crispy further clarification is welcome.
>
> Best
> Ale
> --
>
> [*]
> https://mailarchive.ietf.org/arch/msg/dmarc/HRAR3hSdckw3mU_Gebh8vcYOjm4
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000be5a6305b991ea54
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The zeal with which the status quo is being defended sugge=
sts that disposition reporting is pretty valuable to legitimate sending dom=
ains.<div>However, this situation complicates any effort to argue that such=
 information is useless and harmless for malicious domains.=C2=A0 =C2=A0Suc=
h a fine distinction has not yet been justified.</div><div><br></div><div>I=
 can fully endorse Murray&#39;s position that alignment=C2=A0reporting is b=
eneficial, even when the sending=C2=A0domain is malicious.=C2=A0 =C2=A0Howe=
ver, it is also off-topic.=C2=A0 =C2=A0My focus is on disposition reporting=
, not alignment reporting.</div><div><br></div><div>Bottom line:=C2=A0 The =
perceived risk of disposition reporting will differ with each person, and t=
herefore with each reporting domain.=C2=A0 =C2=A0 The specification would b=
e improved by providing a way for skeptical domain owners to redact informa=
tion=C2=A0that they do not wish to disclose.=C2=A0 =C2=A0Currently, the opt=
ions=C2=A0are to (a) not report at all, or (b) report ambiguous and slightl=
y misleading information such as &quot;dispostion=3Dquarantine, overriderea=
son=3Dother&quot;.=C2=A0 =C2=A0A better option would be to have options to =
state &quot;dispositioin=3Dnot=C2=A0specified, overridereason=3Dnot specifi=
ed&quot;.</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Sat, Jan 23, 2021 at 6:21 AM Alessandro Ve=
sely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri 22/Jan/2021=
 23:40:18 +0100 John Levine wrote:<br>
&gt; <br>
&gt; As someone said, the better the spammers align their stuff, the better=
<br>
&gt; we can filter it.<br>
<br>
<br>
100% agreed.<br>
<br>
<br>
&gt; Close this, please.<br>
<br>
<br>
Please don&#39;t.=C2=A0 That such a doubt can cross the minds even of knowl=
edgeable <br>
people is a real issue.=C2=A0 At a minimum, the paragraph I cited[*] should=
 be <br>
restored.=C2=A0 A crispy further clarification is welcome.<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
[*] <a href=3D"https://mailarchive.ietf.org/arch/msg/dmarc/HRAR3hSdckw3mU_G=
ebh8vcYOjm4" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.=
org/arch/msg/dmarc/HRAR3hSdckw3mU_Gebh8vcYOjm4</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000be5a6305b991ea54--


From nobody Sat Jan 23 15:26:05 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dmarc@ietf.org
Delivered-To: dmarc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB873A0D48; Sat, 23 Jan 2021 15:26:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dmarc@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dmarc@ietf.org
Message-ID: <161144436332.13490.10651420808048876097@ietfa.amsl.com>
Date: Sat, 23 Jan 2021 15:26:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/L4h1u9he5l3medu24q8EXEATS-c>
Subject: [dmarc-ietf] I-D Action: draft-ietf-dmarc-psd-10.txt
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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, 23 Jan 2021 23:26:03 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain-based Message Authentication, Reporting & Conformance WG of the IETF.

        Title           : Experimental DMARC Extension For Public Suffix Domains
        Author          : Scott Kitterman
	Filename        : draft-ietf-dmarc-psd-10.txt
	Pages           : 14
	Date            : 2021-01-23

Abstract:
   DMARC (Domain-based Message Authentication, Reporting, and
   Conformance) is a scalable mechanism by which a mail-originating
   organization can express domain-level policies and preferences for
   message validation, disposition, and reporting, that a mail-receiving
   organization can use to improve mail handling.  The design of DMARC
   presumes that domain names represent either nodes in the tree below
   which registrations occur, or nodes where registrations have
   occurred; it does not permit a domain name to have both of these
   properties simultaneously.  Since its deployment in 2015, use of
   DMARC has shown a clear need for the ability to express policy for
   these domains as well.

   Domains at which registrations can occur are referred to as Public
   Suffix Domains (PSDs).  This document describes an extension to DMARC
   to enable DMARC functionality for PSDs.

   This document also seeks to address implementations that consider a
   domain on a public Suffix list to be ineligible for DMARC
   enforcement.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmarc-psd/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dmarc-psd-10
https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-psd-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmarc-psd-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Sat Jan 23 16:49:17 2021
Return-Path: <superuser@gmail.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 8F90F3A0E65 for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 16:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 uZfIzxyXm82j for <dmarc@ietfa.amsl.com>; Sat, 23 Jan 2021 16:49:14 -0800 (PST)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D36F3A0E63 for <dmarc@ietf.org>; Sat, 23 Jan 2021 16:49:14 -0800 (PST)
Received: by mail-vs1-xe2a.google.com with SMTP id e15so5269689vsa.0 for <dmarc@ietf.org>; Sat, 23 Jan 2021 16:49:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PdmnDIzV1fUKBfkuYgm4ZlqeRSLDRfgyCI4WdZigOmc=; b=HQ0kp6fw8k+KPb6bAd4w16tbfcv4YzJrszy2Ozkn86+sQH5TUD72p+bme8sKulagS8 /isJ6MLdXaU/Gy5SD5LELYDcZ7pBtez9obEtYiW42IrVZDTr/RNpPwl1b2dFVMb6yJcT T2ywU5VqCaZwVohiAp0280c61euefnolUv84APvJJCyAl849308S7ksRlZdDWj5D0D4H 3I4jCsLFlWgN9kkI1v0gLDqK55ySkpR4oMZ8spcXBROOZr+XtnVsghswAueRjizOUQjz F4pSftCvjKbaY+1OdDjVALu9ToX3/+r6yOIhZteIwlvAsuE/LtyNzGUHb4WD96x2s0ZG lWWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PdmnDIzV1fUKBfkuYgm4ZlqeRSLDRfgyCI4WdZigOmc=; b=uRw1dk4bGLZvmxoesi7fZNKBvXfvVgqws5Z/SJSXD6bi86I2eyjRkKECE4kxO8JUbs FbMomlsCMcb5h91cVdRW6dpKj4492upmpEZb/TZJLSNfX5PlQoCf/Ujv5xdxS4jwLTC/ rFEzYN55veeL103AHwP4g0l5nrpc2g7nlpqU3t5RdoG7LPr9QvyRUNOk0m6FG1YZvb9C LOWVQFhum3SeqKsO7Huo65rETJbZPhrFinMJxyx7wglskDEwiPFSiQVyPd5I27ZoJUkM SvSPjqEECAQ7AExAPpJ1HfvYULCkN66Gc8aNs5wVNTsHfoiIax/KK8e/8Ws3lHW/1Xo7 mvXg==
X-Gm-Message-State: AOAM531k+pJSxxhmwexF+aCjgeWGY++BCsXAnRPmMc4/qtOlTwJx4SfV ZjkrsLir29pYIWAdpOIRbnCg2JGS4DHiaBkoGOwjlBIDeo0=
X-Google-Smtp-Source: ABdhPJy0EysImIDxNCK1SZb/dOgm+awIONE34wgF4dOniewAV1ksizqiBtRXN5TxedHaz8/AQHf0uaUgvblFhIIgLVU=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr314477vsy.54.1611449352825; Sat, 23 Jan 2021 16:49:12 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <70f6215a-4796-f3ee-3a18-5b91f553f4ca@tana.it>
In-Reply-To: <70f6215a-4796-f3ee-3a18-5b91f553f4ca@tana.it>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sat, 23 Jan 2021 16:48:55 -0800
Message-ID: <CAL0qLwaz+NMEQD=dgQMKdb7LfwsEL+-b7kFeE+fjWyPp3+4_1g@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003fafad05b99aca00"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/eetPRaK6WX7Xe30ThvirXMBLluw>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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, 24 Jan 2021 00:49:16 -0000

--0000000000003fafad05b99aca00
Content-Type: text/plain; charset="UTF-8"

On Sat, Jan 23, 2021 at 3:29 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Sat 23/Jan/2021 01:55:05 +0100 Kurt Andersen (b) wrote:
> > On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
> >
> >> Here's the paragraph in question
> >>
> >>      <t>To determine the organizational domain for a message under
> evaluation,
> >>         and thus where to look for a policy statement, DMARC makes use
> of a Public Suffix
> >>         List. The process for doing this can be found in Section 3.2 of
> the DMARC
> >>         specification.</t>
> >>
> >
> > The concern that I have with this wording is that it is (potentially)
> > misleading. "How" DMARC determines the org domain does not matter at all
> to
> > this spec. The important point is that we go to "org-1" in the tree for
> > this extra lookup.
>
> +1.  If we don't assume that readers already know what the PSL is, trying
> to
> establish that context in the Introduction is only a complication.  Later
> on,
> when Section 3 explains technicalities, the PSL has full citizenship.
>

In the interest of getting this done finally, could you or Kurt please
propose specific changes, maybe in OLD/NEW form, that you think fixes the
problem?

-MSK

--0000000000003fafad05b99aca00
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Jan 23, 2021 at 3:29 AM Alessandr=
o Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote=
:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">On Sat 23/Jan/2021 01:55:05 +0100 Kurt Andersen (b) wrote:<br>
&gt; On Fri, Jan 22, 2021 at 3:06 PM Tim Wicinski &lt;<a href=3D"mailto:tjw=
.ietf@gmail.com" target=3D"_blank">tjw.ietf@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt;&gt; Here&#39;s the paragraph in question<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &lt;t&gt;To determine the organizational domai=
n for a message under evaluation,<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0and thus where to look for a poli=
cy statement, DMARC makes use of a Public Suffix<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0List. The process for doing this =
can be found in Section 3.2 of the DMARC<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0specification.&lt;/t&gt;<br>
&gt;&gt;<br>
&gt; <br>
&gt; The concern that I have with this wording is that it is (potentially)<=
br>
&gt; misleading. &quot;How&quot; DMARC determines the org domain does not m=
atter at all to<br>
&gt; this spec. The important point is that we go to &quot;org-1&quot; in t=
he tree for<br>
&gt; this extra lookup.<br>
<br>
+1.=C2=A0 If we don&#39;t assume that readers already know what the PSL is,=
 trying to <br>
establish that context in the Introduction is only a complication.=C2=A0 La=
ter on, <br>
when Section 3 explains technicalities, the PSL has full citizenship.<br></=
blockquote><div><br></div><div>In the interest of getting this done finally=
, could you or Kurt please propose specific changes, maybe in OLD/NEW form,=
 that you think fixes the problem?</div><div><br></div><div>-MSK<br></div><=
/div></div>

--0000000000003fafad05b99aca00--


From nobody Sun Jan 24 03:00:10 2021
Return-Path: <johnl@taugh.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 A16BD3A12F0 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 03:00:08 -0800 (PST)
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, 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 IGljEYVUueXS for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 03:00:07 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 BD96E3A12EF for <dmarc@ietf.org>; Sun, 24 Jan 2021 03:00:06 -0800 (PST)
Received: (qmail 52900 invoked by uid 100); 24 Jan 2021 11:00:05 -0000
Date: 24 Jan 2021 10:59:41 -0000
Message-ID: <20210124105941.52884.qmail@submit.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LafozPYI-rFyICDdYlHvZp_ZkP4>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jan 24 06:00:05 2021
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, 24 Jan 2021 11:00:09 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 13 (16.5%) |  70012 ( 7.7%) | Alessandro Vesely <vesely@tana.it>
 11 (13.9%) |  53486 ( 5.9%) | John Levine <johnl@taugh.com>
 10 (12.7%) | 110098 (12.1%) | Murray S. Kucherawy <superuser@gmail.com>
  8 (10.1%) | 123186 (13.5%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  8 (10.1%) | 117041 (12.9%) | Todd Herr <todd.herr@valimail.com>
  8 (10.1%) |  81598 ( 9.0%) | Michael Thomas <mike@mtcc.com>
  6 ( 7.6%) | 187108 (20.6%) | Tim Wicinski <tjw.ietf@gmail.com>
  4 ( 5.1%) |  66911 ( 7.3%) | Seth Blank <seth@valimail.com>
  2 ( 2.5%) |  20781 ( 2.3%) | Hector Santos <hsantos@isdg.net>
  2 ( 2.5%) |  16744 ( 1.8%) | Kurt Andersen (b) <kboth@drkurt.com>
  2 ( 2.5%) |   9580 ( 1.1%) | Steven M Jones <smj@crash.com>
  1 ( 1.3%) |  25180 ( 2.8%) | Emil Gustafsson <emgu@google.com>
  1 ( 1.3%) |  11590 ( 1.3%) | Brotman, Alex <alex_brotman@comcast.com>
  1 ( 1.3%) |   7014 ( 0.8%) | Dotzero <dotzero@gmail.com>
  1 ( 1.3%) |   6414 ( 0.7%) | Juri Haberland <juri@sapienti-sat.org>
  1 ( 1.3%) |   3612 ( 0.4%) |  <internet-drafts@ietf.org>


From nobody Sun Jan 24 03:50:20 2021
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 E4D913A07FC for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 03:50:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 iHG2vHMPIVll for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 03:50:18 -0800 (PST)
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 3CF593A07EB for <dmarc@ietf.org>; Sun, 24 Jan 2021 03:50:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611489016; bh=VoSxXuEwBtUi7PYmddLXve+I2RkPcC8D4hRt6o3dChU=; l=504; h=To:From:Date; b=DPe4tbS0Fa3rz9B6AaSNN+JVzERfKDsiEaE29k3MY5IjsMjmlEBJrdCWUufbAQfe/ CZnKpOVQLXMweuXUM9vxiviKDKeLxEuDl5fPouY5r0FzXZQIClVa6dG+XD6TE+TueP I38AEbY/ZXuKRcZLq1YSK/H+sgpWlTRDlB01cYHQ1k1O1LoCu1f1l6Km2LQ3R
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC026.00000000600D5EF7.00005B7C; Sun, 24 Jan 2021 12:50:15 +0100
To: IETF DMARC WG <dmarc@ietf.org>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <8423eb32-2e45-77d9-dda0-306bacdd4981@tana.it>
Date: Sun, 24 Jan 2021 12:50:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
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/pZOvBQMkSmertwebUseq1eIdJxI>
Subject: [dmarc-ietf] Ticket #55, closing
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, 24 Jan 2021 11:50:20 -0000

Hi all,

I'm going to post version -01 of failure reporting before 22 February.  Please express consensus or ask for changes.

MD version:
https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-failure-reporting/blob/main/draft-ietf-dmarc-failure-reporting.md

Current diff:
https://tools.ietf.org/rfcdiff?url1=draft-ietf-dmarc-failure-reporting-00&url2=https://raw.githubusercontent.com/ietf-wg-dmarc/draft-ietf-dmarc-failure-reporting/main/draft-ietf-dmarc-failure-reporting-01.txt

Best
Ale
-- 















From nobody Sun Jan 24 09:05:12 2021
Return-Path: <johnl@iecc.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 AB8EE3A0E7B for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 09:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=OsOc1Qi5; dkim=pass (2048-bit key) header.d=taugh.com header.b=E8UJgzAD
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 NMcNqlUenGMW for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 09:05:07 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 6A2B63A0E7A for <dmarc@ietf.org>; Sun, 24 Jan 2021 09:05:06 -0800 (PST)
Received: (qmail 24903 invoked from network); 24 Jan 2021 17:05:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=6144.600da8c1.k2101; bh=C/OdGJrZ6o1mM7pfLEzfzuRhxTHPfHW6mqpIvmPzRJc=; b=OsOc1Qi5okjEYGk1Cf9WQ2DoCbdfH+avGw84g7jjmXMKJWkVfz0BH3pr609jWSK0wdlXkZ2i7g6OMZwOZgKhlittyoLsMXdQ8DSDAf1PBNm5joCPzm9SsH9ZbUJg5OsJrsqXcRtFVcCJeR7i/9MPyWnD3wDmdUkAO6ok6xEtpUrZigPW+xfGeknVtKJh9tflw6juGsjIfLbzUAr0CkNZYvq5M2Tjveq5pKi7oXCe/cOsXbXslj3nZupoBnhhQjK+KdnMWY7I/pPxeyIPmjz6zfNmJqtxN3fYwS7SWqWUlFxD2/hiwfTmPu48VjWDKvGBoEZ/sSP3MReA4GPeUBdjmw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=6144.600da8c1.k2101; bh=C/OdGJrZ6o1mM7pfLEzfzuRhxTHPfHW6mqpIvmPzRJc=; b=E8UJgzADQyJoTwZcqxjfBAIDHZrqCE1gO+IOqjK7klM66Bv+8lv3nPk934lKZ5TvMfZcXPTE3Rka538PXX6uXL+9Pz8P9yW9BpuhvJ/7znVrM5A/LmLcWVUczAt5/ZAl9A9+arAo8w3xYqSJCnF+YowPY1303CF/1gKiMVyEkYFvlXgrpHQZJVcLiq/LLIwxQJOUlkR22kEleuoggMclvpbmhTSbcNzGTR9PD8v8Ee5GloU9amSCay8dAy2Wo38C0RKGUKdXr1Bn3rr+mYzgN9xdwXyRMBbpPLoS6vtVw5q3A5trJONoyJSmhE/I0zaQ9Ldr440wNM1fUAuYyWzhfg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 24 Jan 2021 17:05:05 -0000
Received: by ary.qy (Postfix, from userid 501) id 07A236C05685; Sun, 24 Jan 2021 12:05:03 -0500 (EST)
Date: 24 Jan 2021 12:05:03 -0500
Message-Id: <20210124170505.07A236C05685@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <8423eb32-2e45-77d9-dda0-306bacdd4981@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/q2tfUzyirswrAPQS-MktWsilSZo>
Subject: Re: [dmarc-ietf] Ticket #55, closing
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, 24 Jan 2021 17:05:11 -0000

In article <8423eb32-2e45-77d9-dda0-306bacdd4981@tana.it> you write:
>Hi all,
>
>I'm going to post version -01 of failure reporting before 22 February.  Please express consensus or ask for changes.
>
>MD version:
>https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-failure-reporting/blob/main/draft-ietf-dmarc-failure-reporting.md

My main concern continues to me that we should not have made this a
separate draft, but we should put all of the reporting in one document.

In sec 3 it says the reports SHOULD include all URIs.  That is a privacy problem since it is common
for unsubscribe URIs to contain the recipient address in plain text or an easily reversed encoding
such as base32.

The privacy considerations miss the fact that organization domains are
only an approximation to actual domain ownership, and reports may be
sent to someone unrelated to the actual sender. This is not
hypothetical; I get reports for subdomains who are not me all the time.


From nobody Sun Jan 24 10:27:33 2021
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 4BBE13A0F0F for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 7M5tAIc8OzVL for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:27:30 -0800 (PST)
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 F01EC3A0EE6 for <dmarc@ietf.org>; Sun, 24 Jan 2021 10:27:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611512845; bh=h9aaC+rwpBu5EJbHiZLN1xBYwVleNlFP3nbAnXDW8Ck=; l=1574; h=To:References:From:Date:In-Reply-To; b=Bag5BFwAw7UyTMS/dq6xGqYyzfPDBTbuNHq++2xUgBts/xE7eQCUfUubksHyuBPoW 06uPGiG8f9xFOe2XwlWfK/6DRQqw87xQgLt1Kqymhyu+/RmulbD22s+rF1sOtzGzmj ke6TFxsSBzQ9f+HbjVT2aG798aGiGZbt4Qs03wPVrU/kz9ZLqxZGDPQQ5uvS4
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0B0.00000000600DBC0D.00000150; Sun, 24 Jan 2021 19:27:25 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210124170505.07A236C05685@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <580831bc-ae5b-de09-e473-39c1a13a8107@tana.it>
Date: Sun, 24 Jan 2021 19:27:23 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210124170505.07A236C05685@ary.qy>
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/i0SqrZepOLmDh4FJ9wHE2o530KU>
Subject: Re: [dmarc-ietf] Ticket #55, closing
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, 24 Jan 2021 18:27:31 -0000

On Sun 24/Jan/2021 18:05:03 +0100 John Levine wrote:
> In article <8423eb32-2e45-77d9-dda0-306bacdd4981@tana.it> you write:
>>
>>I'm going to post version -01 of failure reporting before 22 February.  Please express consensus or ask for changes.
>>
>>MD version:
>>https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-failure-reporting/blob/main/draft-ietf-dmarc-failure-reporting.md
> 
> My main concern continues to me that we should not have made this a
> separate draft, but we should put all of the reporting in one document.


That cannot be expressed in the draft itself...


> In sec 3 it says the reports SHOULD include all URIs.  That is a privacy problem since it is common
> for unsubscribe URIs to contain the recipient address in plain text or an easily reversed encoding
> such as base32.


Would something generic as the following do?

    These reports SHOULD include any URI(s) from the message that failed
    authentication, unless privacy reasons suggest otherwise.  [...]


> The privacy considerations miss the fact that organization domains are
> only an approximation to actual domain ownership, and reports may be
> sent to someone unrelated to the actual sender. This is not
> hypothetical; I get reports for subdomains who are not me all the time.


Shall I add that verbatim as a second paragraph in Security Considerations?

    In addition, note that Organizational Domains are only an approximation
    to actual domain ownership  Therefore, reports may be sent to someone
    unrelated to the actual sender.


Best
Ale
-- 









From nobody Sun Jan 24 10:47:05 2021
Return-Path: <johnl@iecc.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 9EA983A0FD9 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=aQYruate; dkim=pass (2048-bit key) header.d=taugh.com header.b=MD6ICqRT
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 LXMOlQpo-pqv for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:47:03 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 27C613A0FD2 for <dmarc@ietf.org>; Sun, 24 Jan 2021 10:47:02 -0800 (PST)
Received: (qmail 46924 invoked from network); 24 Jan 2021 18:46:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b74a.600dc0a3.k2101; bh=fmLV8+ny3MNXoA/SRLMHgReusqLaQKEjCVInq62v8Ew=; b=aQYruateHKkZ5vTLHfImuiC61Xg7VsGZAC4BEPZ+ltfFvTkKkH3v4CEUskux3oJ7+Hk4kk2F/+F1iiTOvORlrOGD5eVg/F9PDX6qJ0GXzeB6RkIeNDa5hoVLXOPxawLAUXcfTNP2nGL+rCt/9wBTRkpenlEp8BMbkYrEWav+SobMdx8+6gxemVHKzCPalGaaCIZhS8BbqC0rSekZl2Ys+qM/yGHo+2vffYT/7rQutm+o0xK9dTuf7MzU6CYrklMzN/V4VKuKhXHJK7DldIJH1gVvACHRH5VzyKpk+OAvAAq+RbKzYtK1cqU5gyBMuAFdb/cFQEJZaFGLzkj4x32V3w==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b74a.600dc0a3.k2101; bh=fmLV8+ny3MNXoA/SRLMHgReusqLaQKEjCVInq62v8Ew=; b=MD6ICqRTtNqX6i6RmUpRrCzQzSKne9WsdFX4R5+R5lwbt4/PfsnqJmL+5LRzFmSM2fBgZ+2YQreCcxcAO4Q5vvI48p8C4/sq68x7Ng8HIF7cbRVJUsrvXUOpY8Em4Vw6RQfw1Km+I3I1+iCcRetu6AkA76PrkoCsEn43bs53xtOJ+e1V9d5+KhmxEh4YQrjoqecyAaANkx3JDq6jBLXRHLXBUS54zL+N9tSeNnFonhl4Q67IoQG9IlEtRAOaoNXx8HxHO3P3LhK+bnzq0aL4K4L1gcQwSDVhzTrQzTAzYBQJ88NwVmCbHeytZyQXZdE98bmHmtCCPXiAh+lpI41CuQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 24 Jan 2021 18:46:59 -0000
Received: by ary.qy (Postfix, from userid 501) id 12DF46C068F5; Sun, 24 Jan 2021 13:46:58 -0500 (EST)
Date: 24 Jan 2021 13:46:58 -0500
Message-Id: <20210124184659.12DF46C068F5@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: johnl@taugh.com
In-Reply-To: <f12991fe-fded-6c0-528c-3b879b4a670@taugh.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/cqU3RQOVCNeK1EAIc2vUon0A3Os>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 24 Jan 2021 18:47:05 -0000

Here's a concrete proposal for https reporting:

In draft-ietf-dmarc-aggregate-reporting, in the transport section,
between Email and Other Methods add:

Https POST

The message is an XML file with GZIP compression, sent with an https POST message
to the given URI as media type application/gzip.
The data SHOULD contain the filename described in Email transport
above as the filename in the gzip header. The filename helps recipient
hosts recognize duplicate reports.

In draft-ietf-dmarc-dmarcbis section 6.3 under the rua tag, add:

If there is more than one URI in the value, the URIs are conceptually evaluated from
left to right and each report is delivered to each URI in turn.
If a delivery to an "https:" URI succeeds, any subsequent URIs that are not "https:" are ignored.
This allows a report recipient to prefer https reports while falling back to mailto reports.

R's,
John


From nobody Sun Jan 24 10:49:05 2021
Return-Path: <johnl@iecc.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 4B95D3A0E25 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=DZ0cMhpA; dkim=pass (2048-bit key) header.d=taugh.com header.b=aJUfjQWL
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 njjRSrPqrkAb for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:49:03 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D8DE63A0E23 for <dmarc@ietf.org>; Sun, 24 Jan 2021 10:49:02 -0800 (PST)
Received: (qmail 47289 invoked from network); 24 Jan 2021 18:49:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b8b7.600dc11d.k2101; bh=poJ8K8Wvcu8VY8okTXdXiIgfgGz1J2IDMAvY/x/lJsw=; b=DZ0cMhpAHYblC4m46cQs1qIYjoDXe2+cYinkiDixmvUgNtPVanYhI9D/0GHN3/JTp4RxxV+KdH+iyp8tCjNidah9ib9OcgaGATxSg0/SI1wtsKZsX3M5PcRSaARhD9Ua6fhL5MJRWuyjngWL66id/6K2yJWqy3pguzuLbtJSaq6uEag2JJJn39dwCdq1VCCA1/LbobhB+VPDXxaP+UtakUnLl4eJ8SrCnQLbdvFbeGtPYIwYC8fSQovjvc7msoCZn4l7QhXqsb93xe1g8dP74fV/+FZm0vIfE4nL3AijOXMWJV61nU/rXModLF2QN0znfvB3/bqVCLjvadWs2rO4ow==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b8b7.600dc11d.k2101; bh=poJ8K8Wvcu8VY8okTXdXiIgfgGz1J2IDMAvY/x/lJsw=; b=aJUfjQWLmVWAgJ8E/hQgKGxeXXOIkxOMsvmTPGN8uRyJBQVuL4Qnr4HXIFYlj+M4RRXDzcv8eqI/fpIe7cxG0xbI9iNjIwVLfqw7PpmUgzyltvJmqA5+Fu4xzU0+zXAqUDSUOrYUiYohY+UJi8bitNjwk7y4vtvbTJ6U1aVeyxrvKetE7aOlXl5fP85mkH0FtVp+0GIkQXMvP//L92+rv3E8iZ+2p5Vc55gKy5QGoiSgHu7wh+6xBDXLsteORAcA6WFIlphSpHDPPnZ38A8bK3Zi/6+jjwqetMbqQCQVPsDrT6IEJY0v9yhjOQQfvoUM+ABkPce2YhGDPJiAao/VCA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 24 Jan 2021 18:49:01 -0000
Received: by ary.qy (Postfix, from userid 501) id 10BDD6C0693D; Sun, 24 Jan 2021 13:49:00 -0500 (EST)
Date: 24 Jan 2021 13:49:00 -0500
Message-Id: <20210124184901.10BDD6C0693D@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <580831bc-ae5b-de09-e473-39c1a13a8107@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mFk0qiTCy8tzghRvcxus01W_Blw>
Subject: Re: [dmarc-ietf] Ticket #55, closing
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, 24 Jan 2021 18:49:04 -0000

In article <580831bc-ae5b-de09-e473-39c1a13a8107@tana.it> you write:
>> In sec 3 it says the reports SHOULD include all URIs.  That is a privacy problem since it is common
>> for unsubscribe URIs to contain the recipient address in plain text or an easily reversed encoding
>> such as base32.
>
>
>Would something generic as the following do?
>
>    These reports SHOULD include any URI(s) from the message that failed
>    authentication, unless privacy reasons suggest otherwise.  [...]

Why are we telling people to send URIs in preference to any other part
of the message?  I don't see the point.

>Shall I add that verbatim as a second paragraph in Security Considerations?
>
>    In addition, note that Organizational Domains are only an approximation
>    to actual domain ownership  Therefore, reports may be sent to someone
>    unrelated to the actual sender or domain owner.

Sure, with the correction above.

R's,
John


From nobody Sun Jan 24 10:49:40 2021
Return-Path: <mike@fresheez.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 B90833A0F46 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 5t6fjMZKYUI7 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 10:49:37 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 480513A0F35 for <dmarc@ietf.org>; Sun, 24 Jan 2021 10:49:37 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id n7so7442816pgg.2 for <dmarc@ietf.org>; Sun, 24 Jan 2021 10:49:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=KLNBN0VOaRSegwn9LZf56RfUd3xqLOg5k5eajIH8NsQ=; b=kbtO9dN1imR2ArqaUc2eLHnMX10lbBDX4472aDUeVWOZIVjpLsueqL0YxyVWUPUCFv sC4gw4eXbDvkkdmVOV3gEPMUivazrfo19MpP2TjAwBYFzOC23/yLKlKH1C++WGENraWh Jnlft+zVibZC3XrQV82wFfGon1dW1+OXJtB7zPGZNZW+aLy7M/EEMDQ5WvVllVA4jVsm ZVqYTtJqp4lB1S+IQO0WjrMLezIFrF1xZuot33pzfFFqPH3nQ0ruWvy3o0w1yLXwtjYZ z6MGnyW5fHr6PmxexPHtj1vBBM6xZuw/hivxAtBvt4TXA9kaLjp5dnK2XDOlVbh7BuZI KeNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=KLNBN0VOaRSegwn9LZf56RfUd3xqLOg5k5eajIH8NsQ=; b=LNYBNCORQ6vX8QgBXKxtW0XwOUAD7MdX1riBk6tciLVwvpvWeDNSM77+4Y1NR/x0oT xgU/1CAVftblgrYLT8pEU7b0NMKKXDcPn88h0tsFbHzrGcvKqaJMOXmnBFuE7/zA4hBq /FPG5Kf9GRvQUJ36n5LMvdVMmATbgaaLHuzHY+L7FBQ1BpV0gSGAM8/C6vnfxIvNLhnM xR0Mt1ocwzBm8hj3cFupjgiA1cuYrEP2sHhKIThsJuOB6B5cWkZ+95dtCvrxjxUpoPle LlV+35jrQX8TTVZShA19uyHUq05nRi8L1VkarboZn4psO1OBD2ifaYq60Azoaw6Ob68x 7spA==
X-Gm-Message-State: AOAM530cs3Nm/2BuAGHikbC91umLJv9RxiQIMs9bJbofHXW+FHcfgSpt bFIkno8vQc54kHb2hnr2JMe3oHvDL17IlQ==
X-Google-Smtp-Source: ABdhPJzogoCCIgqvUA4chLBN4uLcGPhp5IIzcxBiPAIgsYcXrQbr1QRW+SWqFlggh5sBPS4wM25uqg==
X-Received: by 2002:a63:4517:: with SMTP id s23mr1470346pga.267.1611514176330;  Sun, 24 Jan 2021 10:49:36 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id 6sm16713820pjm.31.2021.01.24.10.49.35 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 24 Jan 2021 10:49:35 -0800 (PST)
To: dmarc@ietf.org
References: <20210124184659.12DF46C068F5@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com>
Date: Sun, 24 Jan 2021 10:49:34 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210124184659.12DF46C068F5@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wWiUnSweo5RXd8TMfr3cgvvTYAY>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 24 Jan 2021 18:49:39 -0000

issue #99 needs to be addressed.

On 1/24/21 10:46 AM, John Levine wrote:
> Here's a concrete proposal for https reporting:
>
> In draft-ietf-dmarc-aggregate-reporting, in the transport section,
> between Email and Other Methods add:
>
> Https POST
>
> The message is an XML file with GZIP compression, sent with an https POST message
> to the given URI as media type application/gzip.
> The data SHOULD contain the filename described in Email transport
> above as the filename in the gzip header. The filename helps recipient
> hosts recognize duplicate reports.
>
> In draft-ietf-dmarc-dmarcbis section 6.3 under the rua tag, add:
>
> If there is more than one URI in the value, the URIs are conceptually evaluated from
> left to right and each report is delivered to each URI in turn.
> If a delivery to an "https:" URI succeeds, any subsequent URIs that are not "https:" are ignored.
> This allows a report recipient to prefer https reports while falling back to mailto reports.
>
> R's,
> John
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Sun Jan 24 11:08:30 2021
Return-Path: <johnl@iecc.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 A9A283A0FF0 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 11:08:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=X63fzQdr; dkim=pass (2048-bit key) header.d=taugh.com header.b=P8nggnld
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 9hTBt-Io5CNc for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 11:08:28 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 EAEB93A0FEF for <dmarc@ietf.org>; Sun, 24 Jan 2021 11:08:27 -0800 (PST)
Received: (qmail 51106 invoked from network); 24 Jan 2021 19:08:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=c79d.600dc5ab.k2101; bh=F2jJ3GjX4O7a4Ms7aFZfMjjWs527i0Gas8F3jbycjSk=; b=X63fzQdr4kNgmOxJ45yrK5pkbeIRCRJ74LVNW2OJtl7bf1ZNWCaf1HXa3ON4fxlp8mSCHOnTQy74TDYeT/mHrRE9DNJAjvQUnvpjLCI2B0rCn2BCQpkouDCqwZpcrqSGr1TU4k1PhQ4zPze7zbLycl9G0dA7JssP0i9diRkjk46rHJcnEgi7Ni1R+bZPmXy21m58VTRePs4l6DN4zpVSUSBVIgqlV7zhId9gzXpqoCgXc53cdp+/f9Ib5Xfhnwbj9UYdlFU3UoipO9WKzpbOioySwVOVt6hYqyUmk9eTcPc44guCEY7O8w/vbkp59GZMlllTzQqbbQNeTV+b/CGuVg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=c79d.600dc5ab.k2101; bh=F2jJ3GjX4O7a4Ms7aFZfMjjWs527i0Gas8F3jbycjSk=; b=P8nggnldmbZ2khCX2wnTtrP/exxiQwksjUT3WJ0E9rIvFtQVT4OzfifSO/sxXPsN5ZUEfN87TZEZkBDIVcUO2fEEi6peUX6AbP1ZF9R3ijyjyRHLrcqY//Ns1sVHcFKsydscoaZVYMnfK6A4eggqEymUEG2t+1Q0ZeRiQW4RjdMMlX3/847sw6ISXFO+4N9dJx3wEy/gXgJUAMyLh0zvn5mTzzjU8yuE+zAyGyLtTsfXu+4zsjNEzjMH4VUlx5SS0OYbOfXBxwyJYYoxPHiuyBBdicrjRAjJY0zbB2Flc8pf+SKMYASOG/goPI9Rf0R5nQeLgtGoPOdc4sjNRnMQdQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 24 Jan 2021 19:08:26 -0000
Received: by ary.qy (Postfix, from userid 501) id 380E26C07CF4; Sun, 24 Jan 2021 14:08:25 -0500 (EST)
Date: 24 Jan 2021 14:08:25 -0500
Message-Id: <20210124190826.380E26C07CF4@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: mike@mtcc.com
In-Reply-To: <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DPniKp2QBtTKmDnzEpamiWT7Srg>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 24 Jan 2021 19:08:30 -0000

In article <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com> you write:
>issue #99 needs to be addressed.

I don't see any connection between issue 99 and this proposal.  This is not about failure reports.

R's,
John

>On 1/24/21 10:46 AM, John Levine wrote:
>> Here's a concrete proposal for https reporting:
>>
>> In draft-ietf-dmarc-aggregate-reporting, in the transport section,
>> between Email and Other Methods add:
>>
>> Https POST
>>
>> The message is an XML file with GZIP compression, sent with an https POST message
>> to the given URI as media type application/gzip.
>> The data SHOULD contain the filename described in Email transport
>> above as the filename in the gzip header. The filename helps recipient
>> hosts recognize duplicate reports.
>>
>> In draft-ietf-dmarc-dmarcbis section 6.3 under the rua tag, add:
>>
>> If there is more than one URI in the value, the URIs are conceptually evaluated from
>> left to right and each report is delivered to each URI in turn.
>> If a delivery to an "https:" URI succeeds, any subsequent URIs that are not "https:" are ignored.
>> This allows a report recipient to prefer https reports while falling back to mailto reports.
>>
>> R's,
>> John
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>



From nobody Sun Jan 24 11:10:37 2021
Return-Path: <mike@fresheez.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 A47FF3A0FF1 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 11:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 5AKzy3XYFRQR for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 11:10:34 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E2A63A0FF0 for <dmarc@ietf.org>; Sun, 24 Jan 2021 11:10:34 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id j12so6976192pjy.5 for <dmarc@ietf.org>; Sun, 24 Jan 2021 11:10:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=4MviK1euX6FbQjFiveXT99o4DKUgMTjOSBcTpFFNryw=; b=kcoF70JGurCXFhFMn2qgKVYjhD7IouzU9jrvE+IWU26kjETfpwiJVT3DAahaB6QO2e D03fdwe8qgjrh2MySM5Rb7W2NU3AyXe/Duqb+w1kg6X5J3rkx+HbeyXTTUjrDzEgj3++ rpnA8AI8NRC9CnEe9F3ox6APTxBg3W2Cjy9foYePASYfNT1Jq0+ZMNZLxohZ+yiFjWkK BXgDz4teCmQzqz3wM+hGpdlJSPuei4Q6Rv6+fsFp8jqwcaqvAajD3xwPm17KI+1iOQkB XI2vVyElqhgVOzgC7BHMpTaoRyHhftGphHF1C/HVEzlKjbJMwIUMGuLUtjW1OAj5c/GO ytdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=4MviK1euX6FbQjFiveXT99o4DKUgMTjOSBcTpFFNryw=; b=pbgBuwWwwunzcn6Wq32QFIoJTzfr4yZ+uVojU4h7Vs1+MuvvmGYWf4bo9FYuxZzhGs pTnUsv0fUfulgGlAQnxoiuNTATwrtya/Re/Bvq3G8ur109GABidUlMCI46+xAVdbydT/ S4l3tYtbi/qM1cOpP3QQv8KWvKyh/MUEQ3La1OIraH4sCmbztolwurs/Rm6/qw+s9z4Q zlsRLOLKmvnpGqsiGafn4t8guaWzLvw4IBhJjiofYV/y5iDyKEh3WMepQyURGGYZmxeI PdOeGi1yCxfecinaDGRytHlGDn5l4bQgJtxt9lnvMKM43PmJpb9PWHmHDsWK98JSgs9K BC5Q==
X-Gm-Message-State: AOAM531befKwTTTqYMtjOPq6DPyDT+i4indNIqMZlOhfPjgsN6IN/pUs wQQMnnsoNNJEdshTPdyCD0CU3rYzdut+kA==
X-Google-Smtp-Source: ABdhPJxXcKAc8R/I2vGUE9IJtElDpbo8sMrp88xSajFy8aEmM2jf/b7xCSOW2zL8pz7abEtj11TbRA==
X-Received: by 2002:a17:90a:6407:: with SMTP id g7mr8277145pjj.56.1611515433439;  Sun, 24 Jan 2021 11:10:33 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id n1sm13910917pfu.28.2021.01.24.11.10.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 24 Jan 2021 11:10:32 -0800 (PST)
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210124190826.380E26C07CF4@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <c682449b-6e7a-60b5-73a8-8497aa3a1929@mtcc.com>
Date: Sun, 24 Jan 2021 11:10:31 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210124190826.380E26C07CF4@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/zKPa24R2pE4w9T3nVgEP7MRh5iA>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 24 Jan 2021 19:10:36 -0000

any reporting needs to be authenticated. if you're going to use http, 
you need to show how you're going to do that.

Mike

On 1/24/21 11:08 AM, John Levine wrote:
> In article <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com> you write:
>> issue #99 needs to be addressed.
> I don't see any connection between issue 99 and this proposal.  This is not about failure reports.
>
> R's,
> John
>
>> On 1/24/21 10:46 AM, John Levine wrote:
>>> Here's a concrete proposal for https reporting:
>>>
>>> In draft-ietf-dmarc-aggregate-reporting, in the transport section,
>>> between Email and Other Methods add:
>>>
>>> Https POST
>>>
>>> The message is an XML file with GZIP compression, sent with an https POST message
>>> to the given URI as media type application/gzip.
>>> The data SHOULD contain the filename described in Email transport
>>> above as the filename in the gzip header. The filename helps recipient
>>> hosts recognize duplicate reports.
>>>
>>> In draft-ietf-dmarc-dmarcbis section 6.3 under the rua tag, add:
>>>
>>> If there is more than one URI in the value, the URIs are conceptually evaluated from
>>> left to right and each report is delivered to each URI in turn.
>>> If a delivery to an "https:" URI succeeds, any subsequent URIs that are not "https:" are ignored.
>>> This allows a report recipient to prefer https reports while falling back to mailto reports.
>>>
>>> R's,
>>> John
>>>
>>> _______________________________________________
>>> dmarc mailing list
>>> dmarc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dmarc
>


From nobody Sun Jan 24 13:36:52 2021
Return-Path: <johnl@iecc.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 184923A0B92 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 13:36:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=oKNZQyBz; dkim=pass (2048-bit key) header.d=taugh.com header.b=nb1vy86O
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 UL7L5uCyOJ5Q for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 13:36:49 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 72BD73A0B8F for <dmarc@ietf.org>; Sun, 24 Jan 2021 13:36:49 -0800 (PST)
Received: (qmail 80079 invoked from network); 24 Jan 2021 21:36:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=138cc.600de86e.k2101; bh=mggwmud3u8P1fIxmwgK10JPHOcR28+xL/+i7dPGC1bA=; b=oKNZQyBzpFcn7xocHFIeRzsmQtOpFKpsDvNVjfSLvx064asFkO1TvZx7b/zbE70FC6WrV9vNntuAMpm7+f/6CEPjCMeuHh6cK/cxfGuqkJEma1WMva8SoePEGSg/Yyu8zqmso45SN3MkZg6isigQzhaRtfq/Lq/61hJvfdHAVm7VJJ+idgwIaSLIx8AVAGWUx/dorrLWQVkTE99oKC+iPpKVAvGGL2yPmf2WVcXY3drVoy89wq9doHIkY1WCyBfgdvvjEWiuXCPuV0Pu0TOtUUBOdJ4Bs3cWMtFx/T9OTZhM2TaJ3+HCYath5ySFsmtg9qRdMxRZMk5DBwTAoL7hoQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=138cc.600de86e.k2101; bh=mggwmud3u8P1fIxmwgK10JPHOcR28+xL/+i7dPGC1bA=; b=nb1vy86O/0fWbF9pislLXwK9oZBqG9nwA47xzXCBJbLj11Idoro6VkD8r/vGvmqdw/6jkTcnWm0hPrQmn7nsAxK55ftS4OI9Lygm2BlgT5JlPbQTy9vdzvmpNUYhRhmZkk0dzj4SI4mwEFK25pycFTRxMImOEzP/lmOoLI4YgqCk61qRj3g9daHuu6oeKFOQNYp1qcb4ROCkCwhGLjNFkKUXvMx2C4jerYvaH7W0+48WD3iFeeuVvH3URW0o7CEK9vvjqpJFPXhQtHDSDQhSzNE8yu5YdXuIumW5/LYWQH7YRvVI9Ncn/92gaTBqN5MydtnYb0+zzVpAB3oOxvJSQQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 24 Jan 2021 21:36:46 -0000
Received: by ary.qy (Postfix, from userid 501) id CAD5E6C0889D; Sun, 24 Jan 2021 16:36:45 -0500 (EST)
Date: 24 Jan 2021 16:36:45 -0500
Message-Id: <20210124213645.CAD5E6C0889D@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: mike@mtcc.com
In-Reply-To: <c682449b-6e7a-60b5-73a8-8497aa3a1929@mtcc.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qOLByxB0YjTWYfsLER08zAUXjeg>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 24 Jan 2021 21:36:51 -0000

In article <c682449b-6e7a-60b5-73a8-8497aa3a1929@mtcc.com> you write:
>any reporting needs to be authenticated. if you're going to use http, 
>you need to show how you're going to do that.

DMARC systems have been producing and consuming reports for a decade
without authentication, without any problems I am aware of other than
the occasional failure report loop, so we have practical experience
telling us this assertion is not true.

R's,
John


From nobody Sun Jan 24 13:41:46 2021
Return-Path: <mike@fresheez.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 76D7E3A0B9E for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 13:41:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 mvDZk8Q6jI6S for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 13:41:43 -0800 (PST)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EE173A0B9B for <dmarc@ietf.org>; Sun, 24 Jan 2021 13:41:43 -0800 (PST)
Received: by mail-pj1-x102b.google.com with SMTP id a20so4166985pjs.1 for <dmarc@ietf.org>; Sun, 24 Jan 2021 13:41:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=srsSLjmpmaSERgqAnodXGPkO1Wp6IY9GjiyvDYE30RU=; b=CWSoAUfiiPNB9MboncGGdjnvBbS3k+/e94mSrPLUyNO/3iNIFjvkY+lO+H4jCKe7Nf pJYmT0Ke8kgnFhQ6mLnbWsmchfraSw7SkXIYPQoWDRpzTQEczGa/LGKhQT+WWvK9F/c/ 4eEcoCoLkfeGoS42VdjQlABg8rzF7OLpsvZkYv3ZBbeS7hTvs0o3UaTD84fNBnrZNdR/ 2LRyPbPgTX4StSChtIXehDLDYwR2Lcd15RdbO5AlBO1QkjfLUjiD6UetPw0lEMgm41zS poPIMidyYOPbKxSJGEza3fgPe5aIOGINkY5tmQHMM7wo5X2hF5Kw4Z3yKDnRn6pv2DSZ /y8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=srsSLjmpmaSERgqAnodXGPkO1Wp6IY9GjiyvDYE30RU=; b=RcO5dlIuzME4xvhewnkyNbRb6+9wY99zMWgSslBqQ0UBZLLZ4+2Yn8dsg4948a6txh urcouS6RX2bGRrEoFb8BYqLImMid3OU0lPVVXnjO4uT5Vn4W1bWBtqwp3C9g5Qxcqp1L QCRsuHMn9xJFUyzyEDp08gtOgeUxxyEaNyVvX8GjDOUdaqEyiaePJAdzCMBTzi8aU3yR reBXwEPCjxurF6krTKP3j2r2U75mpMrdpooCFhK1XzqUteBE+C0qanTohAwi5mQo39LZ 4vZKaGVbGWjL21m1m8x1gjldPV9mUzwLWX+vEWcawlaAKcIniH9Vq3OGe28ckbwt+n20 gv9Q==
X-Gm-Message-State: AOAM533tWFryiPa2ZnxHxOJExtRVaob//7rePuRw0rH641ILeyMaiW2O jX8FmIDJiwbLse4ehkRZSXuI6BpV4lQmTQ==
X-Google-Smtp-Source: ABdhPJzaJCmWKU62R4AqVASl473R2LnO2+WMGWa8VeNG5MaAZ/6iBqowoLo70WW0V8ZFuJGFKD5mLw==
X-Received: by 2002:a17:902:14f:b029:de:c703:3045 with SMTP id 73-20020a170902014fb02900dec7033045mr16744795plb.14.1611524502270;  Sun, 24 Jan 2021 13:41:42 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id k141sm13060071pfd.9.2021.01.24.13.41.41 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 24 Jan 2021 13:41:41 -0800 (PST)
To: dmarc@ietf.org
References: <20210124213645.CAD5E6C0889D@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <241051cd-d4db-b5cb-fa4b-c94e58e6cb51@mtcc.com>
Date: Sun, 24 Jan 2021 13:41:40 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210124213645.CAD5E6C0889D@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/oXJkKsDj7lLCTTVvG8P4NENawss>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 24 Jan 2021 21:41:44 -0000

On 1/24/21 1:36 PM, John Levine wrote:
> In article <c682449b-6e7a-60b5-73a8-8497aa3a1929@mtcc.com> you write:
>> any reporting needs to be authenticated. if you're going to use http,
>> you need to show how you're going to do that.
> DMARC systems have been producing and consuming reports for a decade
> without authentication, without any problems I am aware of other than
> the occasional failure report loop, so we have practical experience
> telling us this assertion is not true.
>
"That i'm aware of" doesn't count for anything in the security realm. If 
this document intends to be standards track the default security posture 
is that everything needs authentication. Good luck getting it through 
the IESG handwaving the problem away. At least with mail a little 
normative texts fixes the problem. That won't be the case for http.

Mike


From nobody Sun Jan 24 16:25:22 2021
Return-Path: <Alex_Brotman@comcast.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 406963A0408 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 16:25:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.com
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 65G9_uZnb679 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 16:25:20 -0800 (PST)
Received: from mx0b-00143702.pphosted.com (mx0b-00143702.pphosted.com [148.163.141.77]) (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 E6D0B3A03F2 for <dmarc@ietf.org>; Sun, 24 Jan 2021 16:25:19 -0800 (PST)
Received: from pps.filterd (m0156896.ppops.net [127.0.0.1]) by mx0b-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10P0HWWU024561 for <dmarc@ietf.org>; Sun, 24 Jan 2021 19:25:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.com; h=from : to : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=20190412; bh=zsmLj1Qa8nx7OItVdwr9nEKA7/tpA+3OTxrqHr+xzhQ=; b=FEJmXxYMWPMotd/BJZIekj6qcaOIkuExXfc7Rg24bMfaiNK0fmFoBeUIUQbokH8OcNgH wqGENuzdAWrjeqkf+pB4YCX2BKzjG3SG03VtI8JMYG6/JqLQEPstI0SAGun/Firg9oZa kz8qo1uUlcaNFWpUBtkM3cg0/xgvasyZp2FixxmP2BZqmaNE53rhZRWcaemIpCZyfi95 byf3prIv4pcPkL86dt6r15MlGCe711CInj6hwULEb0qld6vPmdW2Chm8yHHp8z7JAtLb OUaFPdTtDm4edsv1y6AMh3ctp5vPUWg64dzKs4oKqFMOQXAKc/6suAy15+Q/HquK2dzO PA== 
Received: from copdcexc33.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0b-00143702.pphosted.com with ESMTP id 368fpdfefh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Sun, 24 Jan 2021 19:25:18 -0500
Received: from copdcexc33.cable.comcast.com (147.191.125.132) by copdcexc33.cable.comcast.com (147.191.125.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Sun, 24 Jan 2021 17:25:17 -0700
Received: from COPDCEXEDGE01.cable.comcast.com (96.114.158.213) by copdcexc33.cable.comcast.com (147.191.125.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Sun, 24 Jan 2021 17:25:17 -0700
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.100) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 24 Jan 2021 19:25:34 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4301.namprd11.prod.outlook.com (2603:10b6:208:188::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.13; Mon, 25 Jan 2021 00:25:13 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42%7]) with mapi id 15.20.3784.017; Mon, 25 Jan 2021 00:25:13 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: Which DKIM(s) should be reported? (Ticket #38)
Thread-Index: AdbysIxA8zFO9cEQSfqEK/Gf/4kCJw==
Date: Mon, 25 Jan 2021 00:25:13 +0000
Message-ID: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:3dad:1098:6838:177c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2ec25933-f636-4fcb-5457-08d8c0c7aeec
x-ms-traffictypediagnostic: MN2PR11MB4301:
x-microsoft-antispam-prvs: <MN2PR11MB4301EB8AE0CC30C92B5BFA5DF7BD9@MN2PR11MB4301.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 0waspDlO4rIYJbWQrml+glaEwWnPNKvz1pEUlFJIPyaRuJG7bZ+P8fbeJxlCDxS8b4gKjqtaiLgO7zWCfoAqMXdZjmq3tjmJSaLnXeecur6t0Rd+6d2NpR+H2ea4MVQF+xcHsbBYUVrew8Tpvx2oG9CCyinruUnEFBAd7GSl5tHETxJUtok0JCuAeKlLRrgN2poOITDn2usQQiPI8hRFL7914H8ycx37Y7nEjxB+wH/F/j2q9kl6VjSMwGxPbghUOAkRftNoJgQn2fmqVL9L6dbvyqu0qyvA8N+4ofcqww0SvfmpFsnDL6yrqpHKfssB2/6OlV5gBR4ZsmOF9O4WyPia157hv8sOCLPTPq9Rkq8OTi4eGfH+hj6B4M93TqEMsruO26EvYvKHGqeiJvNljPxa0X5fOYa2rh42TFf6Xo2SuJ4dEt2j6jbtBMB6J2TZQfIiRZo4o1s9wIR+eF0N5Q==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(366004)(376002)(346002)(136003)(396003)(316002)(6506007)(8676002)(6916009)(86362001)(83380400001)(186003)(52536014)(4744005)(478600001)(7696005)(5660300002)(966005)(66946007)(2906002)(66446008)(71200400001)(64756008)(8936002)(9686003)(33656002)(55016002)(66476007)(66556008)(76116006); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?xivu8QdccCZBla6gHU96t8bqs/+9iDSugrhkUFT2YLZTsIjH3GWm/b5/5cOz?= =?us-ascii?Q?g/UfcqGc3JuejlNlP2Y833MaFis4lxEsEv1W1HxT5/QPUrIVoVIT653Wle1h?= =?us-ascii?Q?KHtOo5Zykm3QuHs5q3IGK+Y/XoIPYc1NhWbd6aDuQxOzW56enbIO/QD4ihzj?= =?us-ascii?Q?9hW3P8cuB3cU9Q6/O04YaCd2GFnnDvysJjjOIJxkg6X3WS/u/hHtAtd0PiB5?= =?us-ascii?Q?yH2+TOlnEH5fyBEQ9UfQ2SDWv3/JsqZrKNStwoyIPChNBtwD9psi+fVRT/F5?= =?us-ascii?Q?MYNDDQNrFdrus/yFGZb9ZlYRS/8F7MV0eYIA2bj0EUe23wA9pONf0EQqyk1v?= =?us-ascii?Q?HOaO6Pl3lZlrk8awxfG+ewDnctLW/fBmEGYxIzbaTZFeM07z0Jxw6ta0gbVS?= =?us-ascii?Q?hBxkJMJOkFV+K0CCbeMgQY14BOMzLMPcXoWYssaK4FjjkI4FPzXQVaxsPter?= =?us-ascii?Q?n3q44t6ZBWxjqbLeoytOCAp8rUiKkfJXFp9yaJUhl8H1wjCDtBL4dV66dkhs?= =?us-ascii?Q?heEHY8f+gV9UT7dqg/wTtIGO/HOqt+gL+eICHN+TlTgLx57id/Hd2u+94H2C?= =?us-ascii?Q?nJc5OhDN8sH8jpqxSXi2AO87w6YAgziRqrC1LY/ANNo4cSk1RMuQhWSicAL1?= =?us-ascii?Q?EKJw7k+onWdkF3izmSQOBMhghESU7PWA6JyQQfe+nk/3uY6z7W47keQD9Ypu?= =?us-ascii?Q?opOAIh64oCyKLtNePvKmXslEqU+W1NxA1YjMh25NPLsiD4pkI8HEZm98EF+y?= =?us-ascii?Q?P2sWA/yTWr4TNry0B1YkfxSCGVInQoQPYkmVnhQH33I5pRNXue3tODywQ5iM?= =?us-ascii?Q?ZF1l+dxVcnFss3dBEVnSI0f7iHNW4VAls2xP4nzPRgjyhLEi45sLgiJBvb+2?= =?us-ascii?Q?EZvoKEk5KD1iE5HU2bkIuTCFVxQC15MvI05Yx/1rdSp9+2mfptwx18EPDgCv?= =?us-ascii?Q?rkFhy0PQFLjEW93uiHKlaU8DRRAbblPd+Y167oB+n82kzoGfp92QHnVSgIOn?= =?us-ascii?Q?KOCJY7AUQI6/HJSR9EUyIpTY9witSEIrpzjqJwIw4qhnsCM=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SiIZutniNvj2nQ5fBEZeuEj4H/ZjHG3ZX11FIGYd6tW70l6+/TqEElLUTooormjvXPDCGDe/+0jyQuS5z2oBpBGtP4NA1Uk/JolWkQKGvPFxAGc3jryR1mSfnOAB3q5ckHUGl0Ujm8Q1+wy0pepYnO8xtuUkdX8+pxpQV92xazPhDYTH6S4fgZVUPQQZcwDFjK2VfM7OdD4uYzaZPubkUTbnCSgr9goVmCwn2GrW67Wc3ne+m2tRQBFgsaSEPrloeKTyMmkD/fugpNb37ub2R9+JGR26lKFeNYKTTQiGdiPhgKQkoe+UBggZTksnZvP/zUCK7XTLM9YpP6XO2j6Elw==
arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6PqdAOQH2BYa3TYDwWVYGVQSivAhfaBpccfDYPXLRvY=; b=dKP/CUOJLGX6T4TUZCCP8wghGbphylkmVhL8+6FTAE0lgz7TdO0/zz0+cDYPdIC6fy0FdlxrlEFyiQ1wBwz5PjE+bn9/dzkfzvnnscM4p6AJZONpyhVXOxaNF8cYr+PjTwi//sJYlqFSTJxHKGwpszeqXyg8xZt6fJx9CbyH5zMH41imkg894GjxVwmoGGZwKP1fLvTyEL/lTBEaczkWbzu2fi20InVyfthyQNm2ii/NzXDFX5C5uoY4AS/yhzUG4z1DUF7TYFY5joA6PwvA7gHHcsYi3Nmjc8dd5cVHw6HMk6Nb2BXdJRTqSo+AqV+oo80vtoELR61Kp3deSVtTvg==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=comcast.com; dmarc=pass action=none header.from=comcast.com; dkim=pass header.d=comcast.com; arc=none
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: MN2PR11MB4351.namprd11.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: 2ec25933-f636-4fcb-5457-08d8c0c7aeec
x-ms-exchange-crosstenant-originalarrivaltime: 25 Jan 2021 00:25:13.8204 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 906aefe9-76a7-4f65-b82d-5ec20775d5aa
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: bRn6lZqpToLI9EYuLo5zPfaKVZi1juLrrXmA3K+adS6PLRaU/wz33zosuqSCOJNrVWRFs4QQq1wmsc3GJn85E/A5FYwEcqC/5GM3ky8zjuM=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4301
x-originatororg: comcast.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWC
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-24_13:2021-01-22, 2021-01-24 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/oN8jMt0kuLZVSu7yy2BCaFHoQuA>
Subject: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 00:25:21 -0000

Hello folks,

Some time ago, an issue[1] was brought to the list where which DKIM(s) bein=
g reported is not clear in RFC7489 [2].  There was a short discussion, thou=
gh no clear resolution before conversation trailed off.  It seems like ther=
e were points that may need to be discussed.  One was whether the reporting=
 SHOULD report all signatures, regardless of alignment or validity, or perh=
aps just the one that aligns (if there is one).  There was also another que=
stion if there should be a limit to the number of signatures reported so th=
at it remains sane.

We'd like to try to get this resolved within about two weeks.  Thank you fo=
r your feedback.

1: https://mailarchive.ietf.org/arch/msg/dmarc/9-V596yl2BBaUzCNaDZB1Tg1s4c/
2: https://tools.ietf.org/html/rfc7489#section-7.2

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast


From nobody Sun Jan 24 16:32:10 2021
Return-Path: <Alex_Brotman@comcast.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 7FEE43A098C for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 16:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.com
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 J4_8kbF89aiJ for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 16:32:07 -0800 (PST)
Received: from mx0b-00143702.pphosted.com (mx0b-00143702.pphosted.com [148.163.141.77]) (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 E3AAD3A0983 for <dmarc@ietf.org>; Sun, 24 Jan 2021 16:32:06 -0800 (PST)
Received: from pps.filterd (m0184889.ppops.net [127.0.0.1]) by mx0b-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10P0GCr8017193; Sun, 24 Jan 2021 19:32:03 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=20190412; bh=fr6sh+ngUZIkQjIfOWpDNrMFlANCivW7xF60bV8uOug=; b=lz9blhZgfq4Rpy5z6p45s9b/EqjbV/vZWvlFyc0HhHlXXs2YTp9YUJ0v0JcXG1Tsoc07 itYgIpRNjPHk9iM4+6CGx87DKdFQYqylWB884F7WfoTzXy85GrnaC0S+D8fjJhjtYRn8 8qxfB2hIhrjy4cQk9SFaDx1ZmQuPbN5iDNbDn2o1+2uzhVckdsspoqYvSasdMeXyhcSG UKUfLqJNNOun77yK3be4t5nRn9eFuNh3ujl+FDaCHzlwwCDSYPplEhDylqepcIRkQMXs BdNszLZ4yqzxki73Fzmg820pxHV9/eAKRx8juO15qln4BKlvvWYsetoP5QVdGy+rS31r IQ== 
Received: from pacdcex52.cable.comcast.com (dlppfpt-wc-1p.slb.comcast.com [96.99.226.136]) by mx0b-00143702.pphosted.com with ESMTP id 368ehe7qp4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 24 Jan 2021 19:32:03 -0500
Received: from PACDCEX49.cable.comcast.com (24.40.2.148) by PACDCEX52.cable.comcast.com (24.40.2.151) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 24 Jan 2021 19:32:02 -0500
Received: from PACDCEXEDGE01.cable.comcast.com (76.96.78.71) by PACDCEX49.cable.comcast.com (24.40.2.148) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sun, 24 Jan 2021 19:32:02 -0500
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.176) by webmail.comcast.com (76.96.78.71) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 24 Jan 2021 19:31:59 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by BL0PR11MB3025.namprd11.prod.outlook.com (2603:10b6:208:79::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.17; Mon, 25 Jan 2021 00:31:58 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42%7]) with mapi id 15.20.3784.017; Mon, 25 Jan 2021 00:31:58 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: Alessandro Vesely <vesely@tana.it>, John Levine <johnl@taugh.com>, "dmarc@ietf.org" <dmarc@ietf.org>, "emgu@google.com" <emgu@google.com>
Thread-Topic: [dmarc-ietf] Reports helping spammers? (#81)
Thread-Index: AdbwN7eHzVTBNYjVTlSst7HV1ZiSWAABpb+AAALQeQAACsc/gAAmuGcAABqPswAATcAWUA==
Date: Mon, 25 Jan 2021 00:31:58 +0000
Message-ID: <MN2PR11MB4351BC07E9D31B0268634B08F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <20210122224018.E63E06BF246B@ary.qy> <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it>
In-Reply-To: <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: tana.it; dkim=none (message not signed) header.d=none;tana.it; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:3dad:1098:6838:177c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: aef23476-205c-43b0-4f1c-08d8c0c89ffc
x-ms-traffictypediagnostic: BL0PR11MB3025:
x-microsoft-antispam-prvs: <BL0PR11MB3025075BEF686D87E14B808EF7BD9@BL0PR11MB3025.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: ZipCeSZFTGJgVsubZbrFQTip5tf7MzentpGqYlp3O0s+VApq4/CwWBpQIqNlzVcZS9HnmGDBGG8okcXS+q9+XRRJbzr7QhmPQULIuj3JKUYZI91GansuZriYk/TTRK03W5VHbJ/7ginhYLgje7/8cwoOdEV//EGkIMX7W9NamA1HOezTX4Mt8SPvctHWP99NCDKqtWf55y28QcENyNOFvfzmaCU8GDPcluRtJAL0kkFOgOncSV66weakFZT1liELRyUB5JseSljkPGxMwspa0AOnpX14v2oPcNLjPq5R7WIK+sF8l7g4XEcKqXL0gvRDpFMrB+lfAMRZAZobAqLQRjEBl/LyMiKW3HEqS9Vd/SicyLsqPbfRl71OyJCbP/5JyZ0lrLhXi1PA1oNqf+738dmJsbtwkCBpb2awaEwKSTRq+K74jo/4Bg4+Asxp3TJgrQ24Szn1YTfkaLz3YmGNLQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(396003)(39860400002)(346002)(376002)(136003)(76116006)(83380400001)(186003)(66446008)(66946007)(64756008)(52536014)(9686003)(7696005)(2906002)(55016002)(53546011)(8936002)(33656002)(8676002)(66556008)(478600001)(66476007)(966005)(5660300002)(86362001)(71200400001)(110136005)(6506007)(316002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?vzfYZw9VfBtQz858ZkvSYDiXvOdC1gb6/cRt/Ni0ePLr/mGiu7BtGiTbTRBM?= =?us-ascii?Q?wX9hTNmoJl+eIN2xoivD0fltcCo2NIeWcXq/qa7lqul6+BLoyUs/yGpIh5/q?= =?us-ascii?Q?o61MoO+v3ZlMOyzRNm3igxWv/sqbTWEnaZKK6oZ6CqcBDNXZph8cCVytjjsL?= =?us-ascii?Q?Kpz52Wml4Izf/VzT+3GCSBJVY7jMkwW6A7i/xAAKa3CriKAlpjlcIzuXD6Gx?= =?us-ascii?Q?WlvMFNOvD9eVhlosVFbgdorgf3TuByfBIfSyQW5MDLPN7gwdXHscYVbvqVoP?= =?us-ascii?Q?8P5DaFwEn70uQpyECE+90VFtRU9iozuwY46teOAXhET8stvs7wjafSU/t7Iy?= =?us-ascii?Q?ORyteXsJ+6Xwh0PzGeaCyrjp7K7U992HFkaT/nETPQEnk3dDQqh4xj8du1nQ?= =?us-ascii?Q?iybMU29uAJbEREnQT/DWCEGI6x3yMg9D6+lW94xLM7SqUYm7exNP9bYeZSzw?= =?us-ascii?Q?+l/P8NXt59l0G5LrWdRLJjOzcVpSZu1bxp+KpuCDgNPtZizxcjygdpwhLXfq?= =?us-ascii?Q?2AZ5G7XdD4pBWPmRt86/C7qIJSh4MMWuqsiyVSPVo0Li5rHd6ae3JpFhY87V?= =?us-ascii?Q?7TgeYKSZRm09pRCuQpRLCMPWP5AcxRo/E1kI7pwWsNWZRBeT18BFk+F3FwCZ?= =?us-ascii?Q?s/qyFpXATRjt7DIzB/AoMWY8ai9OhLNvtEfmKjJxTtPHGb0wtCQGUof6sOHc?= =?us-ascii?Q?Qe25HnLKUnWAZHqywKq+g0Bq1nYEt2mAm4/hC+C6fwp4WwUQbkzKjD+YhWsV?= =?us-ascii?Q?X2L9sd9MALzruRWD/M32L7lTZoPmWykp3JerH8/icW2b4H9OoMiYcMFzhTVo?= =?us-ascii?Q?TvJ0ED6WbE7vAl8X8cTF3lL1eRQhkaolQYbkwO4+IsAZKFzKKRyFSX8wtxBA?= =?us-ascii?Q?UBUS2bK7qph0TfuVbTAwb4pPwxUuUMlRa9PaBtrPLmGa/6nKfLK5ro/zWI1Z?= =?us-ascii?Q?/PnBk/CQCs/BhIfO1PSmenHR5Smu1ZGr96Y0xbuAAkLH1FZrPpzO5yPf/93j?= =?us-ascii?Q?c/m2N30yfQJLEwSHF10sy9a4IUXOmnHLsWm/oANfQV3aO5s=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U2TJBVqc2s7tNBsQ9IhTDcTd+zbmm5qkcqDiSj2qUdq2dj8+YFiANBqtAFaX6lkLP/nYx7eP8u7z5ze01ULdeqx6lR2eBC+4urs14XS2zO5JP4Y80x0LsTpeQAWEVQBpmQs6gxDdYKZurdqTMdvtJdeonDi28fRxuWk6+lOG8PK2VEBgwN3RZXd5msSeOrPh13vcVKkY09vaFH35hwysjcq2XQ5b65jhNe+rsCaV7Z3YpXKxkpivI5WHF6m7AkOo/4mSqD8CcMXGozeg9Mj1UgRoeZYgzfbE4CJQf2VkVbJY2u7LtZJ3IH2VVsg4on451gZgYlw70rSOvoK00wnlDQ==
arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DGl3DSyXuKPnhuqBqAZFAQZzlkj5XnKxT768gdYfswQ=; b=EeVWPVkWGP8aLXA+dhqpedqZ3CcJi9egB3aBiPGDjkw+L5jbbwnUNpEnkuhHTIPZTpAXhxQ3Zzk3Ud45fSvEmZCgTZKtkij++4+c278vpjfxwhSw3A3cP4NuoAJLLPQMGXoIp4J0p8KIHpPFZbsZxJvQsYv7KqPPdlC0qz1CbEmW7b3cicxNR2tv2aBJPuIJYgFgJTs2rTxWg0Rh0tGniW4LKzyn6qRxZyGlriWsp6ACbUqrqZDbw7XIl5GzIXg/AmicW/8AbWmtKc/WtRdTrYh6EybA+m6mm3/Xd/tnQYbXFx/8ZfBFEHyxgfv6uEn8d+4u7vNaRjKvZox4+MD2KA==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=comcast.com; dmarc=pass action=none header.from=comcast.com; dkim=pass header.d=comcast.com; arc=none
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: MN2PR11MB4351.namprd11.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: aef23476-205c-43b0-4f1c-08d8c0c89ffc
x-ms-exchange-crosstenant-originalarrivaltime: 25 Jan 2021 00:31:58.1900 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 906aefe9-76a7-4f65-b82d-5ec20775d5aa
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: V2egoZIvnxRQhwxMakjXA4Wzohq8JQyMFAglG2mpUrpeZLQwS7HXr2BnDIdQTtwME/w3eWj27BEDBiIOpMz+mG8vslp5CxByvy1Ve/3/1D4=
x-ms-exchange-transport-crosstenantheadersstamped: BL0PR11MB3025
x-originatororg: comcast.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWS
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-24_13:2021-01-22, 2021-01-24 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/8aduXESBhWEk1oAAE10ji-b7e1I>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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, 25 Jan 2021 00:32:09 -0000

Ale,

I didn't incorporate that section as I thought that section about Privacy C=
onsiderations might be in the main document as it applies to both rua/ruf. =
 I'll work to add something similar for the coming revision, thank you for =
the note.

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

> -----Original Message-----
> From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Alessandro Vesely
> Sent: Saturday, January 23, 2021 6:21 AM
> To: John Levine <johnl@taugh.com>; dmarc@ietf.org; emgu@google.com
> Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
>
> On Fri 22/Jan/2021 23:40:18 +0100 John Levine wrote:
> >
> > As someone said, the better the spammers align their stuff, the better
> > we can filter it.
>
>
> 100% agreed.
>
>
> > Close this, please.
>
>
> Please don't.  That such a doubt can cross the minds even of knowledgeabl=
e
> people is a real issue.  At a minimum, the paragraph I cited[*] should be
> restored.  A crispy further clarification is welcome.
>
> Best
> Ale
> --
>
> [*]
> https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/dmarc/H=
RA
> R3hSdckw3mU_Gebh8vcYOjm4__;!!CQl3mcHX2A!VZ89uCnai2kVE35KuFXiBNx_0
> VGYmUVnYzQbjqBfthrbcZ3wazcjrZ0hgM9i2T4iF5MP$
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dmarc__=
;!
> !CQl3mcHX2A!VZ89uCnai2kVE35KuFXiBNx_0VGYmUVnYzQbjqBfthrbcZ3wazcjrZ0
> hgM9i2d5OX4cb$


From nobody Sun Jan 24 18:29:42 2021
Return-Path: <johnl@iecc.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 32D1C3A0CAF for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 18:29:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com
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 7UO16fS1SQ_u for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 18:29:39 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D32843A0CAC for <dmarc@ietf.org>; Sun, 24 Jan 2021 18:29:38 -0800 (PST)
Received: (qmail 61956 invoked from network); 25 Jan 2021 02:29:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type; s=f201.600e2d11.k2101; bh=mud01kN81NTSeZ8MYnttC36L+4uLt6oDaZXKQgBvwRQ=; b=rvoaw7aeGzWxEokbBeP9L4F34ffUC9BK/C0zxJrA8tdQFbhYDLWB8IjHN+GVo/OYVEetsUpS95W/CWkfLdCDK050JlrZUA2L6c2810BZeQCWNiKqRuBEL0sRdMx+oDIzRxDjyjg4OKwAT32PyO/uyXw2KlsmAwuVf7onK8zhKnBqxPfCvNsFC+3HTIctB2DPgS8QK1XDdo2VscRN+NSKPoAWqjuDCby2Fxr1rVr6JogC+0AhPxxKVt9q64aQRAONqm4dM8SAG5bkLu57LHm/E6YtSGQLfAoS8Neo0uB5hqNsXvh89o57XOKVZuzFxTdo6smR/I4U2cav9Wm2CKRrWQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 02:29:36 -0000
Received: by ary.qy (Postfix, from userid 501) id 14AB26C0B79E; Sun, 24 Jan 2021 21:29:35 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id C93C96C0B780 for <dmarc@ietf.org>; Sun, 24 Jan 2021 21:29:35 -0500 (EST)
Date: 24 Jan 2021 21:29:35 -0500
Message-ID: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: dmarc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vW3NSwAqfg218Nho3JGqxOdW58A>
Subject: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 02:29:41 -0000

I realized why the arguments about whether to require authentication on 
reports are pointless.

If you actually look at reports, for the most part the address sending the
report is not the recipient domain or anything like it.

For example, recent failure reports I got from solarwinds.com (yes, them) 
are about mail to cisp.co.za which was forwarded to spamexperts.com. 
Reports from seznam.cz are about mail to email.cz.  Reports from 
manthorp.com are about mail to streamingco.net.

Aggregate reports don't even include the recipient domains, and tell me 
about sending IPs some of which are mine but most of which are not as mail 
bounces around through mailing lists and forwarders, or spammers just send 
spam with my domain on the From line.

As we all know, bad guys are at least as good at authentication as good 
guys, probably better.  So if someone for some reason wanted to send me 
fake reports of either kind, they could send them with perfect DMARC 
alignment and they'd still be fake.  If they report spam with one of my 
domains on the From line, there's no way at all to tell whether those 
reports are real.  I can use heuristics to recognize mail my system 
actually sent that went through mailing lists I know about, but DKIM 
signing the reports wouldn't help.

So I suggest that we close tickets 98 and 99.  They don't identify a real 
problem, and if they did. they wouldn't fix it.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Sun Jan 24 18:53:30 2021
Return-Path: <mike@fresheez.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 8CDF63A0D2F for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 18:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 r4veegyPuB-f for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 18:53:27 -0800 (PST)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 818773A0D2E for <dmarc@ietf.org>; Sun, 24 Jan 2021 18:53:27 -0800 (PST)
Received: by mail-pl1-x633.google.com with SMTP id s15so6687367plr.9 for <dmarc@ietf.org>; Sun, 24 Jan 2021 18:53:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=k8RbCrfCL6mEF3SoYLSu2bC0lqvYu4UelBtzUYGZAkY=; b=XzNVs2eqxk3wtM9Ifk+aP3etZCk7S1pfDQq7HBZC6Kvjh0Ifav/iFIC6tpwsRm0e+z G371/hW/PuhEr5FeVahi/KFsjqptDY4g747gUOLQ1hcPuwPSnPYPGGV4utVUDTAZpLta wXNd5/hiijDcJyUD7ijwGfEKg2t0QLEU+VgVYcwB4curdU00X2Rv/Pg1bI4+Evryv2bi tLU0OGl50sVRq6KJxqzsefu1mUMR6A0aS51PN4IGza37ux7Uq0fLopfRJk2umY1PI0JD /ARvg64qSbT8rxjeuNh4/QuFC35wX5aKJuKIlhiwNi1/1dgBtaJ5uvqlgr0zKJdNQISL CBXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=k8RbCrfCL6mEF3SoYLSu2bC0lqvYu4UelBtzUYGZAkY=; b=kFfaHjg27kyrDeHXbr5YwxB2krZyilJ3JonV+fDtBAXq2Z/RJAM4/HCoeqw8vw243Q fcRZ4ZXbv6A00xc+pXQAHsOSoniLRLi8ebhtlgY8iaW7JVHKVS13S65xpWt8+XEIsOd9 sJklpyiuVJvCpd41URQy3sRkUF6eJIlmSiGVqlbZCTPciV3GVQboWtiWacV3zN2M1ccT ALBcu7C9stDAaW2VBpfV+8FYMVKYjJ8ZA690BFMzxuB74acGGfRHM0MN+nKvRn7BbjV0 /42VFlJCsmMJe9QMVSOKquowNHP7ZHTRJRwWwbkjN4gfD9IncbT1wlM6dFXIovbFMy+E tA7A==
X-Gm-Message-State: AOAM533vIyfyKf3qgriOnfO9uxJEn/3D38gkAdghGld25aJOcUa7DGeq gP3XSqF8DNDBnAMerqnECYtO5hatxZvj/Q==
X-Google-Smtp-Source: ABdhPJxY5Zejd8P8CYoHn4HI/XPvxlMKx6QH1RFZUo3iw4QEAU/hl6uG3N3j7wXxQ8ra/Cr5e3WlYg==
X-Received: by 2002:a17:90a:1109:: with SMTP id d9mr5294729pja.94.1611543206642;  Sun, 24 Jan 2021 18:53:26 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id gt21sm15990328pjb.56.2021.01.24.18.53.25 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 24 Jan 2021 18:53:26 -0800 (PST)
To: dmarc@ietf.org
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com>
Date: Sun, 24 Jan 2021 18:53:24 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WKSlVs9jSbUljaouxx2W4nMVPDQ>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 02:53:29 -0000

On 1/24/21 6:29 PM, John R. Levine wrote:
> I realized why the arguments about whether to require authentication 
> on reports are pointless.
>
A blatant assertion. The onus of proof is with people who say we should 
accept information from unknown sources. Extraordinary claims require 
extraordinary evidence. I have been doing security related stuff for 
long enough to know that being humble in the face of adversaries is the 
most prudent course. State actors can get involved when they figure they 
can game things to their advantage. To be dismissive is complete hubris.

Mike


From nobody Sun Jan 24 18:57:51 2021
Return-Path: <mike@fresheez.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 1B53A3A0D31 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 18:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 0a1QTT0ctuiS for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 18:57:49 -0800 (PST)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D4E3A0B28 for <dmarc@ietf.org>; Sun, 24 Jan 2021 18:57:49 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id 30so7953385pgr.6 for <dmarc@ietf.org>; Sun, 24 Jan 2021 18:57:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=2Y5vWi/baBytDrskVlr4scc1qFbj7bk5D4KW0npxhpU=; b=OjWLhO6Q5vJXM3Q5TLIxKU38MewlMeXtwZfRsIaspIgNu8kFJd2SH0c3G62ngfn3Dn tRPqSIcgkL8ypmdeKsfeKnSsCSTIMU0iQx77wl0TjCGwJ1GyILUYCvnAk9YSukgcLM+S N67lwYHXOvTqGAZJ3udH8UiaJ3XGGWL0yNkUBPxZ1w4RHESnN2IZk1zg4eDt/iYeMLlh GA0Rrl56oNKtg6iFI359vg1/8rbckp0yOgZ6a3mUTa5UesBpSxNX2QPYs6/atI0AE6Z9 eXPJ63EdYhhH3lxDCsp0MS4Nzb92eT07gH9Y4DH/S4U4s1GuiR5HrRkHmegjtO24pv55 mStQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=2Y5vWi/baBytDrskVlr4scc1qFbj7bk5D4KW0npxhpU=; b=pECzq0av1ccmhZQvabnXQ6Pxx4WCze9GTH7r05131eqiGECWB3BDfKkOcX7lZQmKwv GMhSou6kM9u8LFnEBRlMBncqiovaXRmIJhnVb//6VaFel+Ha+GEr6P7Se/CeQjpWRXRF sB0QWOkUA/khdjIEZXHixSB7inTE/9DextvrhmP1r1Sh5VNk1pLknfmbBfPigSGKupSv jJBsxjAGjzgPioOZtrIKtdkw1NArRJj0RDgqPCE5INKujCUy1l9vO8zqMwMflh5zK9P9 XfvUk3T3ZbP/GbRYG1I6xQ1WfiwCzdMnmMG/W5BlAGZUKeCrz/Eob9bycvcONjrRobd4 K7oA==
X-Gm-Message-State: AOAM530qWAxKtol4oXW4hDfrfyMR7RcM0fhOf+9d5rCOArM7fIl3yNjO LMdAk0Wh1zQ0rvohZwSb32hzHSK9TnCxjA==
X-Google-Smtp-Source: ABdhPJyrfVLUnpNbEPMrLjJ1pnge8EGsG8cEhkiiGsiEYqHWyqGX6c19MZeWqWW4uz7JSkoeZGIECw==
X-Received: by 2002:a63:5221:: with SMTP id g33mr57201pgb.202.1611543467879; Sun, 24 Jan 2021 18:57:47 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id d16sm14790672pfn.160.2021.01.24.18.57.46 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 24 Jan 2021 18:57:47 -0800 (PST)
To: dmarc@ietf.org
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <ff074ea6-19a8-e152-a775-4bbb1b94d93f@mtcc.com>
Date: Sun, 24 Jan 2021 18:57:45 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/hvxmn_PYMbsDvSQOpZsb9n9JDrs>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 02:57:50 -0000

On 1/24/21 6:29 PM, John R. Levine wrote:
>
> As we all know, bad guys are at least as good at authentication as 
> good guys, probably better.


PS: if this were true, DKIM would be useless too.

Mike


From nobody Sun Jan 24 19:27:17 2021
Return-Path: <dougfoster.emailstandards@gmail.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 3972A3A0D81 for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 19:27:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WFvhmzaU8cFl for <dmarc@ietfa.amsl.com>; Sun, 24 Jan 2021 19:27:14 -0800 (PST)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83CA73A0D7A for <dmarc@ietf.org>; Sun, 24 Jan 2021 19:27:14 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id n18so6436472vsa.12 for <dmarc@ietf.org>; Sun, 24 Jan 2021 19:27:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=+Etsfql0YmKJqy6LzrQSZ6QI2UNcTJwfGLALVTTU7pU=; b=OVpLfJ2fCEXsowcQltulXqMP+k58VzriDpLHQAtF7+NMtwIPmyb+MdeT85rACdJtSm mNpyvz+0tzU/k/G/wncM4ZsP6NjwkOduDY950/lFvn/+5KQ3lfi9q+Psv9vQBjO1zxGh AkHZfSStGNI+EzSgC3rSJ3wliAWybfAXsZh2QWIYXNOEQTfN/f9D1HXarm91ApUOyNIl 9bRuQrVEK04QTdoUDQbTaywAezmGyATUxoqxf6y+yi3gWky2ThiCK6S8+wC+9dXxzDQa JdA8VPoEcOkJvSWk90DkBxYgF/4j+6L6EfBootgyj3Kh65Pa0feoHMG8sO0KhlqC6nR7 FUgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+Etsfql0YmKJqy6LzrQSZ6QI2UNcTJwfGLALVTTU7pU=; b=iu2zKItkZ7NfDRFUFSl4Z8utplDlXa2bBtEYG2cuOpZQAdQhpYaUeje2AfRTEcop7c JjY8AsPHlzqsZhYZUmK1jstQbd6g+u93tqJB4a2AjGXFCWpaM8VXla+lj+tuIZmPEPhB 4gdyOnpExXGXG/QObdJkmknKDdI1dbRpR2k0C7zkcjKQxCii8gIjSY6NjqRh/x7yqq8/ c/32CRhB4dK5ioYxMG1DR3Sb90xuPI2ELhOGLn4QJ3ifbJERViQhVtYoimlPe5gMpFLw VGMhF+mxgOwX6UrIRGzf/x2VDyjcpwabnz21Jlj2KUHKhVSVad0Vi/Vq9HaoptBj/8wq nDiw==
X-Gm-Message-State: AOAM533WZeNOINrPy9QJN5RyRy6okXU1neNE7rKIL0BdtPt4Mn31vC4w FJkI9Wl2q5W0/AlMShG+LCqgLere37budX2bX86rzRe/ZJA=
X-Google-Smtp-Source: ABdhPJxfjQWPRrMRZoc3FMRfhqFV/FUh9k/Fkr+b1KFodG3tM9SwIf25ruMYTNtAuH7/MlY926k5KXxlF67Y8sWxQ7E=
X-Received: by 2002:a67:24c5:: with SMTP id k188mr590400vsk.16.1611545233187;  Sun, 24 Jan 2021 19:27:13 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sun, 24 Jan 2021 22:27:03 -0500
Message-ID: <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000029e7f005b9b11db6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/h8VClwjxikLE0Y3qhVC4Qxuke3Y>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 03:27:16 -0000

--00000000000029e7f005b9b11db6
Content-Type: text/plain; charset="UTF-8"

Currently, my filter only evaluates signatures that are relevant to From
alignment, and stops after the first success.   For that decision process,
all that I need returned (and stored) is a Pass/Fail result; I don't need
the details of the algorithm evaluated.  Any additional information
collection is for the benefit of someone else, not the needs of my own
organization.

The burden of data collection is proportionate  to the amount of data
collected.  DMARC reporting is a courtesy service from the data collector
to the domain owner.  Each effort to increase the precision of the data may
reduce the number of domains willing to provide that information.

I suggest that we need report consumers in this group to discuss how they
use the current data and the proposed additions to that data, so that a
cost/benefit assessment can be made.   At least some of that justification
should be included in the final document, since one purpose of that
document will be to convince non-reporting entities to begin sending
reports.

Doug Foster


On Sun, Jan 24, 2021 at 7:25 PM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Hello folks,
>
> Some time ago, an issue[1] was brought to the list where which DKIM(s)
> being reported is not clear in RFC7489 [2].  There was a short discussion,
> though no clear resolution before conversation trailed off.  It seems like
> there were points that may need to be discussed.  One was whether the
> reporting SHOULD report all signatures, regardless of alignment or
> validity, or perhaps just the one that aligns (if there is one).  There was
> also another question if there should be a limit to the number of
> signatures reported so that it remains sane.
>
> We'd like to try to get this resolved within about two weeks.  Thank you
> for your feedback.
>
> 1:
> https://mailarchive.ietf.org/arch/msg/dmarc/9-V596yl2BBaUzCNaDZB1Tg1s4c/
> 2: https://tools.ietf.org/html/rfc7489#section-7.2
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--00000000000029e7f005b9b11db6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Currently, my filter only evaluates signatures that are re=
levant to From alignment, and stops after the first success.=C2=A0 =C2=A0Fo=
r that decision process, all that I need returned (and stored) is a Pass/Fa=
il result; I don&#39;t need the details of the algorithm evaluated.=C2=A0 A=
ny additional information collection is for the benefit of someone else, no=
t the needs of my own organization.<div><br></div><div>The burden of data c=
ollection is proportionate=C2=A0 to the amount of data collected.=C2=A0 DMA=
RC reporting is a courtesy service from the data collector to the domain ow=
ner.=C2=A0 Each effort to increase the precision of the data may reduce the=
 number of domains willing to provide that information.</div><div><br></div=
><div>I suggest that we need report consumers in this group to discuss how =
they use the current data and the proposed additions to that data, so that =
a cost/benefit assessment can be made.=C2=A0 =C2=A0At least some of that ju=
stification should be included in the final document, since one purpose of =
that document will be to convince non-reporting entities to begin sending r=
eports.</div><div><br></div><div>Doug Foster<br><div><br></div></div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun=
, Jan 24, 2021 at 7:25 PM Brotman, Alex &lt;Alex_Brotman=3D<a href=3D"mailt=
o:40comcast.com@dmarc.ietf.org">40comcast.com@dmarc.ietf.org</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello folks,<br=
>
<br>
Some time ago, an issue[1] was brought to the list where which DKIM(s) bein=
g reported is not clear in RFC7489 [2].=C2=A0 There was a short discussion,=
 though no clear resolution before conversation trailed off.=C2=A0 It seems=
 like there were points that may need to be discussed.=C2=A0 One was whethe=
r the reporting SHOULD report all signatures, regardless of alignment or va=
lidity, or perhaps just the one that aligns (if there is one).=C2=A0 There =
was also another question if there should be a limit to the number of signa=
tures reported so that it remains sane.<br>
<br>
We&#39;d like to try to get this resolved within about two weeks.=C2=A0 Tha=
nk you for your feedback.<br>
<br>
1: <a href=3D"https://mailarchive.ietf.org/arch/msg/dmarc/9-V596yl2BBaUzCNa=
DZB1Tg1s4c/" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.=
org/arch/msg/dmarc/9-V596yl2BBaUzCNaDZB1Tg1s4c/</a><br>
2: <a href=3D"https://tools.ietf.org/html/rfc7489#section-7.2" rel=3D"noref=
errer" target=3D"_blank">https://tools.ietf.org/html/rfc7489#section-7.2</a=
><br>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--00000000000029e7f005b9b11db6--


From nobody Sun Jan 24 21:10:17 2021
Return-Path: <dilyan.palauzov@aegee.org>
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 25E613A0E39; Sun, 24 Jan 2021 21:10:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.204
X-Spam-Level: 
X-Spam-Status: No, score=0.204 tagged_above=-999 required=5 tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAY_BE_FORGED=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (4096-bit key) reason="fail (message has been altered)" header.d=aegee.org
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 nCEsdEZFg5rM; Sun, 24 Jan 2021 21:10:13 -0800 (PST)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (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 786063A0E37; Sun, 24 Jan 2021 21:10:11 -0800 (PST)
Authentication-Results: mail.aegee.org/10P59uV24178984; auth=pass (PLAIN) smtp.auth=didopalauzov@aegee.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1611551397; i=dkim+MSA-tls@aegee.org; bh=PUlbFp6+Ql/qty164mPVeC4eOq97oGtpC91CZZrlazY=; h=Date:In-Reply-To:References:Subject:To:CC:From; b=DzjDH7k5srjTLaqlxroraSMlgUrpn7TFFZWid0H9atbLXhab1F2mjei0ddNAX0qEJ MjRwyWak/F54DGfEwwtFYQ+pQ70TvklVWAzSHK3+N6wbD+i+TVTzwUCrersSkwIXR8 +bSicZbC9wOuOTBMU9dfJEXmAFFuA3H77Y6/DMEQ1nzTRe1DBNhljlEXhLC5k4jZ5E KBP9ycc5fnO4n84b6/I/95tzOTh9w1Jfvfv8rkGHr7EFOh5NgxOsE5OSCxzIi9wviD jdTYA2LvU2cGH1Osp/PR55qp4ZQOUl5z5Q9XPejBl/nhs5R/E0fzD0jJc47VXLRjrJ XaKmUoen0pqr221JIkr2I4pImfXGGVGfpA4MI5GXfYYUL53WEmaHakDDnQzeCoHB1m szYbFpLykePKZSPD/DgZGzYbKnwXsoxv7FU6hf5qkBtAcQ1t3Lgo+F55RPj6JyIoj5 mWcjB+yQx7/H3I09ypHBT/xTAP+eVHEEiMmO8wY1eB4pejhCWo/NadFqjBSx+Oo/O/ ANgIEoniAfFdxW17qXEWh4Jnf6n60BUOdY3He1aQh7NuVddISMDu8SDvyJvxFN2jff CUV56szqqgnsOKNl1YqE9zlG+5nBAc73qKi2orCNNT1ayAEcbplt+pkPKg8Oo76Bar Le5wdI/PETU3d7NfVruPljUY=
Authentication-Results: mail.aegee.org/10P59uV24178984; dkim=none
Received: from [192.168.0.236] (87.118.146.153.topnet.bg [87.118.146.153] (may be forged)) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id 10P59uV24178984 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 25 Jan 2021 05:09:56 GMT
Date: Mon, 25 Jan 2021 07:09:52 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----OKPAYHLI0QLA2QZF1DQBHYYXP2ZMLX"
Content-Transfer-Encoding: 7bit
To: dmarc@ietf.org, "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>
CC: Tomki <tki@tomki.com>
From: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= <dilyan.palauzov@aegee.org>
Message-ID: <A551B531-BFCA-466A-8E8D-4EA4EF9FC82C@aegee.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/5wikO78tFQio9yoa8ViLntj8BMQ>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 05:10:15 -0000

------OKPAYHLI0QLA2QZF1DQBHYYXP2ZMLX
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hello,

lets say a site signs an email with both rsa and ed25519 algorithms=2E  Th=
is site wants to know, whether the recipient can validate the ed25519 signa=
tures, so that in the future rsa signing for that receiving site can be ski=
pped (or errors in the ed25519 implementation fixed)=2E

For this to work the receiving site must put in the report information abo=
ut each aligned dkim signature, saying which public key-name was used=2E

Greetings
  =D0=94=D0=B8=D0=BB=D1=8F=D0=BD

On January 25, 2021 2:25:13 AM GMT+02:00, "Brotman, Alex" <Alex_Brotman=3D=
40comcast=2Ecom@dmarc=2Eietf=2Eorg> wrote:
>Hello folks,
>
>Some time ago, an issue[1] was brought to the list where which DKIM(s)
>being reported is not clear in RFC7489 [2]=2E  There was a short
>discussion, though no clear resolution before conversation trailed off=2E
>It seems like there were points that may need to be discussed=2E  One was
>whether the reporting SHOULD report all signatures, regardless of
>alignment or validity, or perhaps just the one that aligns (if there is
>one)=2E  There was also another question if there should be a limit to
>the number of signatures reported so that it remains sane=2E
>
>We'd like to try to get this resolved within about two weeks=2E  Thank
>you for your feedback=2E
>
>1:
>https://mailarchive=2Eietf=2Eorg/arch/msg/dmarc/9-V596yl2BBaUzCNaDZB1Tg1s=
4c/
>2: https://tools=2Eietf=2Eorg/html/rfc7489#section-7=2E2
>
>--
>Alex Brotman
>Sr=2E Engineer, Anti-Abuse & Messaging Policy
>Comcast
>
>_______________________________________________
>dmarc mailing list
>dmarc@ietf=2Eorg
>https://www=2Eietf=2Eorg/mailman/listinfo/dmarc

------OKPAYHLI0QLA2QZF1DQBHYYXP2ZMLX
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body>Hello,<br><br>lets say a site signs an email with =
both rsa and ed25519 algorithms=2E  This site wants to know, whether the re=
cipient can validate the ed25519 signatures, so that in the future rsa sign=
ing for that receiving site can be skipped (or errors in the ed25519 implem=
entation fixed)=2E<br><br>For this to work the receiving site must put in t=
he report information about each aligned dkim signature, saying which publi=
c key-name was used=2E<br><br>Greetings<br>  =D0=94=D0=B8=D0=BB=D1=8F=D0=BD=
<br><br><div class=3D"gmail_quote">On January 25, 2021 2:25:13 AM GMT+02:00=
, "Brotman, Alex" &lt;Alex_Brotman=3D40comcast=2Ecom@dmarc=2Eietf=2Eorg&gt;=
 wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0=2E8=
ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class=3D"k9mail">Hello folks,<br><br>Some time ago, an issue[1] was b=
rought to the list where which DKIM(s) being reported is not clear in RFC74=
89 [2]=2E  There was a short discussion, though no clear resolution before =
conversation trailed off=2E  It seems like there were points that may need =
to be discussed=2E  One was whether the reporting SHOULD report all signatu=
res, regardless of alignment or validity, or perhaps just the one that alig=
ns (if there is one)=2E  There was also another question if there should be=
 a limit to the number of signatures reported so that it remains sane=2E<br=
><br>We'd like to try to get this resolved within about two weeks=2E  Thank=
 you for your feedback=2E<br><br>1: <a href=3D"https://mailarchive=2Eietf=
=2Eorg/arch/msg/dmarc/9-V596yl2BBaUzCNaDZB1Tg1s4c/">https://mailarchive=2Ei=
etf=2Eorg/arch/msg/dmarc/9-V596yl2BBaUzCNaDZB1Tg1s4c/</a><br>2: <a href=3D"=
https://tools=2Eietf=2Eorg/html/rfc7489#section-7=2E2">https://tools=2Eietf=
=2Eorg/html/rfc7489#section-7=2E2</a><br><br>--<br>Alex Brotman<br>Sr=2E En=
gineer, Anti-Abuse &amp; Messaging Policy<br>Comcast<hr>dmarc mailing list<=
br>dmarc@ietf=2Eorg<br><a href=3D"https://www=2Eietf=2Eorg/mailman/listinfo=
/dmarc">https://www=2Eietf=2Eorg/mailman/listinfo/dmarc</a><br></pre></bloc=
kquote></div></body></html>
------OKPAYHLI0QLA2QZF1DQBHYYXP2ZMLX--


From nobody Mon Jan 25 03:03:49 2021
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 05D043A0EDA for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 03:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.22
X-Spam-Level: 
X-Spam-Status: No, score=-0.22 tagged_above=-999 required=5 tests=[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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 0e1Hs4ObHKnw for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 03:03:46 -0800 (PST)
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 5DB343A0ED7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 03:03:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611572622; bh=2N+rj+RJwOvVqgPVn/TwvhXaIIOey3zNJ5MECOiExvo=; l=1321; h=To:References:From:Date:In-Reply-To; b=CnLSCou0n+OaTCfQpV1vb0HPDNsSAmPe5P0o2gs1dO03tuKTCViLKJaIoUhlZtrJn 1eFNjzFPB2WguKRQeyZbHJUOV8sMFLt1xkNJOFBYQKSTp4RhbdoNNZvG3T4CgPHMa9 m3rb3F4OQ48UWNsYFEC9nFVaFoIhw77s6NTeieKcl02OyZUZezrION18YsdVi
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000600EA58E.00002B84; Mon, 25 Jan 2021 12:03:42 +0100
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, emgu@google.com, IETF DMARC WG <dmarc@ietf.org>, John Levine <johnl@taugh.com>
References: <20210122224018.E63E06BF246B@ary.qy> <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it> <CAH48ZfyvjDQoqQp29LG07tz4g_eRMRboJdQ=qK8kzhyyknbMCg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <e9f251cb-a823-4933-2ea2-4cd258bba8e0@tana.it>
Date: Mon, 25 Jan 2021 12:03:41 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfyvjDQoqQp29LG07tz4g_eRMRboJdQ=qK8kzhyyknbMCg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/hjFiAJXY9rQW6Gn7dGPoe9cZlzs>
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
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, 25 Jan 2021 11:03:48 -0000

On Sat 23/Jan/2021 15:13:53 +0100 Douglas Foster wrote:
> 
> I can fully endorse Murray's position that alignment reporting is beneficial, 
> even when the sending domain is malicious.   However, it is also off-topic.  
>   My focus is on disposition reporting, not alignment reporting.


I see.


> Bottom line:  The perceived risk of disposition reporting will differ with each 
> person, and therefore with each reporting domain.    The specification would be 
> improved by providing a way for skeptical domain owners to redact 
> information that they do not wish to disclose.   Currently, the options are to 
> (a) not report at all, or (b) report ambiguous and slightly misleading 
> information such as "dispostion=quarantine, overridereason=other".   A better 
> option would be to have options to state "dispositioin=not specified, 
> overridereason=not specified".


The information that reports actually disclose is when they say why the 
disposition differs from what the author's domain asked.  That info is given in 
the comment field, which can be "forwarded", "sampled_out", 
"trusted_forwarder", "mailing_list", "local_policy", or any other reason.  This 
field is already optional.

Saying "none" without explaining why doesn't really disclose much, does it?


Best
Ale
-- 













From nobody Mon Jan 25 04:21:53 2021
Return-Path: <dougfoster.emailstandards@gmail.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 8DF963A1171 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 04:21:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 leUuBO6EzZyb for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 04:21:49 -0800 (PST)
Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FB133A1170 for <dmarc@ietf.org>; Mon, 25 Jan 2021 04:21:49 -0800 (PST)
Received: by mail-vs1-xe33.google.com with SMTP id 186so7015846vsz.13 for <dmarc@ietf.org>; Mon, 25 Jan 2021 04:21:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=fRLJYcu8hPQFVy2OOmDbEXdvf+hn97I+vzCvmXNaMt0=; b=Z430CwyP+BkLHxaCeESaCGyKq5Hc+P+IeQ6o7P3AK4usPKNLh7BPfxnKK4pLjER+ze sY1RArk4OiXMDBgBH5zMp7vEsLALms3sYU6WAvMcV8NWRRCOImv+HVT9mvgNyV4NQ9rj GQkP/XjQ9w6P8DC4y16lOclUGeBKfTMsdTWVCGMDptePg76U1uFjGGdAX0qQON3aL2Wl hqjq2AaVesHea3V7GGi2LI2YS4BZGD3cszLZH4R+g2xmHy5R9tVtYhGn8c/3p+sX2EfS 3C2C03e4bjTBsJESTI8Kwg2lC/desOCxRehdVAZFLX/zXVuG3iTDWNNUJ0ntMXsifsmM Juag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=fRLJYcu8hPQFVy2OOmDbEXdvf+hn97I+vzCvmXNaMt0=; b=ZEx+IQbv3cgEzLrsdEW3nQRzQvxvAgkKZioJBeNPVfm1CAH+6GiUCUM61ogFZpeCfz e7XW9sXDTmkXv4C/muX76guSOvtblcOojryt37ltEQI7ie+0DKi/hy3GxXZcyR4rpuGM k51DAYXMpgew8qJlMvoiLgdmzJtIjuLjGtoHZM/ON9fu03e6vLA1cFapu13fC8SRi6CF jIavsSGKBG1BysxVUdG7a4W6yJq4I04heqezSyum6bNnVO6oVsgPU4yVMdwiFN9v43Xz R1TEcsZ4OVJt2+v5lZ2tgMJmAdZueRu8YTX2gxUzISPw6BrTrOGW8lcyhrwy0Ibknapl JlKA==
X-Gm-Message-State: AOAM532/PBaNrJN7RB/0i/HFGdVivVsp9JrEvJfpU2w7L84eufNeTWTu fb345MUoJ3EdQEjKQK+MwRKwLsczG0iE8E7uE2wU6E3nMVU=
X-Google-Smtp-Source: ABdhPJzKRlIqsGjXNmD+Qivc8+tHX2dzU7FC6s2Wm+VQFhhJz/A131gY4JhzfaBlwFL+kNCo1fRHKbgIlofExGwcQ98=
X-Received: by 2002:a67:87c2:: with SMTP id j185mr160495vsd.25.1611577308089;  Mon, 25 Jan 2021 04:21:48 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <A551B531-BFCA-466A-8E8D-4EA4EF9FC82C@aegee.org>
In-Reply-To: <A551B531-BFCA-466A-8E8D-4EA4EF9FC82C@aegee.org>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 25 Jan 2021 07:21:37 -0500
Message-ID: <CAH48ZfwONFvCunEmD2=PFjbKfb55A=mSB-kjEK-mipWQXx_ahg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fa10f105b9b8948a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qkif2M5vguYVBCrDosu_Wr0R3OY>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 12:21:52 -0000

--000000000000fa10f105b9b8948a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This is an interesting issue.   Perhaps we need another ticket just to
discuss how to handle signature transition.  My first thought is that it
will be more effective to announce support for ed25519 in the report
header, rather than in each message result.  Another possibility is for a
recipient to indicate support for new signatures in the DMARC policy record=
.

Any report recipient will have difficulty knowing how to extrapolate from a
single result or even a single report to a general rule.    John has
observed that the RUA report does not even indicate the target domain(s)
being reported.  I would think this data inadequacy should be a priority
for correction.   For any multi-server configuration, knowing that one IP
supports the new signatures does not mean that all servers do so.    The
challenge becomes knowing whether the domain is fully transitioned, and we
don't even know the domain being evaluated.

I suspect that a day will come when a research presents evidence that the
old signatures can no longer be trusted.  At that point, PCI DSS or GDPR
will require us to quickly deprecate the old signatures, and compliant
systems will simply ignore the RSA signatures.   At that point, transition
planning is simplified.

Dual signatures also create some challenges for ARC.  I don't think an ARC
Set can reasonably include signatures under both algorithms.

Doug Foster

On Mon, Jan 25, 2021 at 12:10 AM =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0=
=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2 <dilyan.palauzov@aegee.org>
wrote:

> Hello,
>
> lets say a site signs an email with both rsa and ed25519 algorithms. This
> site wants to know, whether the recipient can validate the ed25519
> signatures, so that in the future rsa signing for that receiving site can
> be skipped (or errors in the ed25519 implementation fixed).
>
> For this to work the receiving site must put in the report information
> about each aligned dkim signature, saying which public key-name was used.
>
> Greetings
> =D0=94=D0=B8=D0=BB=D1=8F=D0=BD
>
> On January 25, 2021 2:25:13 AM GMT+02:00, "Brotman, Alex" <Alex_Brotman=
=3D
> 40comcast.com@dmarc.ietf.org> wrote:
>>
>> Hello folks,
>>
>> Some time ago, an issue[1] was brought to the list where which DKIM(s) b=
eing reported is not clear in RFC7489 [2].  There was a short discussion, t=
hough no clear resolution before conversation trailed off.  It seems like t=
here were points that may need to be discussed.  One was whether the report=
ing SHOULD report all signatures, regardless of alignment or validity, or p=
erhaps just the one that aligns (if there is one).  There was also another =
question if there should be a limit to the number of signatures reported so=
 that it remains sane.
>>
>> We'd like to try to get this resolved within about two weeks.  Thank you=
 for your feedback.
>>
>> 1: https://mailarchive.ietf.org/arch/msg/dmarc/9-V596yl2BBaUzCNaDZB1Tg1s=
4c/
>> 2: https://tools.ietf.org/html/rfc7489#section-7.2
>>
>> --
>> Alex Brotman
>> Sr. Engineer, Anti-Abuse & Messaging Policy
>> Comcast
>> ------------------------------
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000fa10f105b9b8948a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This is an interesting issue.=C2=A0 =C2=A0Perhaps we need =
another ticket just to discuss how to handle signature transition.=C2=A0 My=
 first thought is that it will be more effective to announce support for ed=
25519 in the report header, rather than in each message result.=C2=A0 Anoth=
er possibility is for a recipient to indicate support for new signatures in=
 the DMARC policy record.<div><div><br></div><div>Any report recipient will=
 have difficulty knowing how to extrapolate from a single result or even a =
single report to a general rule.=C2=A0 =C2=A0 John has observed that the RU=
A report does not even indicate the target domain(s) being reported.=C2=A0 =
I would think this data inadequacy should be a priority for correction.=C2=
=A0 =C2=A0For any multi-server configuration, knowing that one IP supports =
the new signatures does not mean that all servers do so.=C2=A0 =C2=A0 The c=
hallenge becomes knowing whether the domain is fully transitioned, and we d=
on&#39;t even know the domain being evaluated.=C2=A0</div><div><br></div><d=
iv>I suspect that a day will come when a research presents evidence that th=
e old signatures can no longer be trusted.=C2=A0 At that point, PCI DSS or =
GDPR will require us to quickly deprecate the old signatures, and compliant=
 systems will simply ignore the RSA signatures.=C2=A0 =C2=A0At that point, =
transition planning is simplified.</div></div><div><br></div><div>Dual sign=
atures also create some challenges for ARC.=C2=A0 I don&#39;t think an ARC =
Set can reasonably include signatures under both algorithms.</div><div><br>=
</div><div>Doug Foster</div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 12:10 AM =D0=94=D0=B8=
=D0=BB=D1=8F=D0=BD =D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2 &lt;<a =
href=3D"mailto:dilyan.palauzov@aegee.org">dilyan.palauzov@aegee.org</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hel=
lo,<br><br>lets say a site signs an email with both rsa and ed25519 algorit=
hms.  This site wants to know, whether the recipient can validate the ed255=
19 signatures, so that in the future rsa signing for that receiving site ca=
n be skipped (or errors in the ed25519 implementation fixed).<br><br>For th=
is to work the receiving site must put in the report information about each=
 aligned dkim signature, saying which public key-name was used.<br><br>Gree=
tings<br>  =D0=94=D0=B8=D0=BB=D1=8F=D0=BD<br><br><div class=3D"gmail_quote"=
>On January 25, 2021 2:25:13 AM GMT+02:00, &quot;Brotman, Alex&quot; &lt;Al=
ex_Brotman=3D<a href=3D"mailto:40comcast.com@dmarc.ietf.org" target=3D"_bla=
nk">40comcast.com@dmarc.ietf.org</a>&gt; wrote:<blockquote class=3D"gmail_q=
uote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
<pre>Hello folks,<br><br>Some time ago, an issue[1] was brought to the list=
 where which DKIM(s) being reported is not clear in RFC7489 [2].  There was=
 a short discussion, though no clear resolution before conversation trailed=
 off.  It seems like there were points that may need to be discussed.  One =
was whether the reporting SHOULD report all signatures, regardless of align=
ment or validity, or perhaps just the one that aligns (if there is one).  T=
here was also another question if there should be a limit to the number of =
signatures reported so that it remains sane.<br><br>We&#39;d like to try to=
 get this resolved within about two weeks.  Thank you for your feedback.<br=
><br>1: <a href=3D"https://mailarchive.ietf.org/arch/msg/dmarc/9-V596yl2BBa=
UzCNaDZB1Tg1s4c/" target=3D"_blank">https://mailarchive.ietf.org/arch/msg/d=
marc/9-V596yl2BBaUzCNaDZB1Tg1s4c/</a><br>2: <a href=3D"https://tools.ietf.o=
rg/html/rfc7489#section-7.2" target=3D"_blank">https://tools.ietf.org/html/=
rfc7489#section-7.2</a><br><br>--<br>Alex Brotman<br>Sr. Engineer, Anti-Abu=
se &amp; Messaging Policy<br>Comcast<hr>dmarc mailing list<br><a href=3D"ma=
ilto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/dmarc" target=3D"_blank">https://www.iet=
f.org/mailman/listinfo/dmarc</a><br></pre></blockquote></div></div>________=
_______________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000fa10f105b9b8948a--


From nobody Mon Jan 25 04:54:02 2021
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 B84DD3A11A2 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 04:54:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 Pt1nubTmqeUO for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 04:53:58 -0800 (PST)
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 9B2653A11A1 for <dmarc@ietf.org>; Mon, 25 Jan 2021 04:53:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611579236; bh=ZwAb9pcW92MlIwVlYud8v1rD1NSmxptqgdPPKyN3jxg=; l=2199; h=To:References:From:Date:In-Reply-To; b=A5GXZdu6TqyKMCq8IqerW7BBVvlGNW+T7mbjNop8Uq+eJ1myHSNUSghEpsOqQoN2K wSco1L7njJtrRbq2gz3K3MwSaBTs4BJWn1RHX6YpGSSGBPhdZNjdB+zRysGjGTBsOi 64SenLXDUncLkccuaksVlBembuodmDZ3AMew1KZDiJNQSiw0DnH3z81tRjgoN
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0BB.00000000600EBF64.0000381D; Mon, 25 Jan 2021 13:53:56 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210124184901.10BDD6C0693D@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <63451726-124b-c24f-3be1-d6435e12c22e@tana.it>
Date: Mon, 25 Jan 2021 13:53:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210124184901.10BDD6C0693D@ary.qy>
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/X8AdQzplRGy1H5uJtSG9GrhYUwg>
Subject: Re: [dmarc-ietf] Ticket #55, closing
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, 25 Jan 2021 12:54:01 -0000

On Sun 24/Jan/2021 19:49:00 +0100 John Levine wrote:
> In article <580831bc-ae5b-de09-e473-39c1a13a8107@tana.it> you write:
>>> In sec 3 it says the reports SHOULD include all URIs.  That is a privacy problem since it is common
>>> for unsubscribe URIs to contain the recipient address in plain text or an easily reversed encoding
>>> such as base32.
>>
>>
>>Would something generic as the following do?
>>
>>    These reports SHOULD include any URI(s) from the message that failed
>>    authentication, unless privacy reasons suggest otherwise.  [...]
> 
> Why are we telling people to send URIs in preference to any other part
> of the message?  I don't see the point.

Dunno.  In draft-kucherawy-dmarc-base-02 the whole paragraph was:

OLDER:
    These reports SHOULD include the "call-to-action" URI(s) from inside
    messages that failed to authenticate.

Gradually, it took the current shape:

OLD:
    These reports SHOULD include any URI(s) from the message that failed
    authentication.  These reports SHOULD include as much of the message
    and message header as is reasonable to support the Domain Owner's
    investigation into what caused the message to fail authentication and
    track down the sender.

Shall we replace it with the following?

NEW:
    These reports SHOULD include as much of the message and message header
    as is reasonable to support the Domain Owner's investigation into what
    caused the message to fail authentication and track down the sender,
    unless privacy reasons suggest otherwise.


>>Shall I add that verbatim as a second paragraph in Security Considerations?
>>
>>    In addition, note that Organizational Domains are only an approximation
>>    to actual domain ownership  Therefore, reports may be sent to someone
>>    unrelated to the actual sender or domain owner.
> 
> Sure, with the correction above.


I committed both updates in:
https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-failure-reporting

diff:
https://tools.ietf.org/rfcdiff?url1=draft-ietf-dmarc-failure-reporting-00&url2=https://raw.githubusercontent.com/ietf-wg-dmarc/draft-ietf-dmarc-failure-reporting/main/draft-ietf-dmarc-failure-reporting-01.txt


Best
Ale
-- 





















From nobody Mon Jan 25 05:25:45 2021
Return-Path: <todd.herr@valimail.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 252D93A11D7 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 05:25:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 WHOxP96rRtNq for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 05:25:40 -0800 (PST)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C522E3A11D6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 05:25:40 -0800 (PST)
Received: by mail-qk1-x730.google.com with SMTP id 19so12379051qkh.3 for <dmarc@ietf.org>; Mon, 25 Jan 2021 05:25:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=cVYiSTnyVjN49uRpsLZylRtVoJACjf9ScgmqxSnBm88=; b=NQyOv7FtDZGcEN7hsKefOpXMIAjSWa/pzhqecgKEIBLTG2dPoLr6dUwsWD18Phgarc 2K3uO5OThdYOltGO7cs8n1BLVK0AbOpYvm72BKxMhsVFbQfB2g/KUHp0QrC2nvo56k9v HNHNzhvgWH7zcWlWiodk5XWRVwQM18bBJMPcaMEh48kWeRgTUCHc1UYp3laITxDNFM6a YFXzBZA4C1blDv5zZ6fGhlfgNl/E6+vGFe0/U9NbF5gggyL2q77BGfx7chtcVnLyx+JM 0OPuK6hy6BKTRVZNnMArgwAFSXFAsoWPcUtpr3LNe4Legw0KHDDheY1UBoCPmhOQYyHR qVsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=cVYiSTnyVjN49uRpsLZylRtVoJACjf9ScgmqxSnBm88=; b=RN96r5Fj458weFbT6GHRLaYnKtNs8LhRy6KcFy+gk76XrkTT4sPsks1NTZdue/GTqY atiFf/WnZpMA2ynYFLmPtE7DSOhjh4BRMIWYrGOFeuBM/oXLbyguSgKXHhO2qlSfxKba Ba57fRG18mjmvvvt4KaMTT6oimLM+rl8OsptTM5c3BYDaKYrdweRNuoh00SRpHGvnRQH VGxYZywRhKkpMtyWLqZ6mA3YnFlNnXVTdB4vHcxKUil82mASjJNP5cIRvlmlvDyex32O +1CRcr0370yTQQxAFbORfKtTKc85RJ9HjhNnqJxOHLvarJLXpoX8BSheFK6H6VLYfZ7n ExRQ==
X-Gm-Message-State: AOAM5335U4UpiQrjw9XzF3rhm6pIhmYgeh6MGrYNTLF7P6ycLkH6lZ8U t5bhPBl+wXsbCv+DmzWH6XDowO6MGYvYSeUrqY9xqUgV+VlpMA==
X-Google-Smtp-Source: ABdhPJy26EkjsTMoUGTG7vOy+V2Z4QpgG18D/dyicrDoMtifY5vAyZVeguJIr7CM86duVDepsFCJT24fiut7oG3EV3w=
X-Received: by 2002:a05:620a:210e:: with SMTP id l14mr633623qkl.387.1611581139543;  Mon, 25 Jan 2021 05:25:39 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com>
In-Reply-To: <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 25 Jan 2021 08:25:23 -0500
Message-ID: <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005978bd05b9b979af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Se1FV2yA5CA-H9-7Z0t3vu16NIk>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 13:25:43 -0000

--0000000000005978bd05b9b979af
Content-Type: text/plain; charset="UTF-8"

On Sun, Jan 24, 2021 at 9:53 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/24/21 6:29 PM, John R. Levine wrote:
> > I realized why the arguments about whether to require authentication
> > on reports are pointless.
> >
> A blatant assertion. The onus of proof is with people who say we should
> accept information from unknown sources. Extraordinary claims require
> extraordinary evidence. I have been doing security related stuff for
> long enough to know that being humble in the face of adversaries is the
> most prudent course. State actors can get involved when they figure they
> can game things to their advantage. To be dismissive is complete hubris.
>
>
I've spent several days thinking about these tickets, and for the life of
me I can't see what the payoff might be for someone to forge a DMARC report.

I suppose nominally there's a denial of service risk, where a bad actor
could flood a rua or ruf mailbox with forged reports or just email in
general, but that's going to exist whether or not the "reports" are
DKIM-signed.

My first question for aggregate reports would focus on the DKIM signing
domain - Should it align with the RFC5322.From domain that sent the report,
or with the org_name or email fields in the report_metadata bits in the XML
itself? John has demonstrated that there's no alignment now in many cases
between the domain generating reports and the domain(s) about which the
reports are generated. You almost have to require that the signing domain
align with the RFC5322.From domain, because DKIM validation is likely to be
done by different infrastructure than does the report processing (see
below) and the DKIM validation layer isn't likely to be able to read the
reports, while the report processing layer may be a simple tool that
doesn't care to do DKIM validation.

About that, aggregate reports are meant to be machine-parsed, and in my own
experience that's accomplished by running a cron job a couple times a day
to process the rua mailbox. (Personally, I favored Mark Overmeer's perl
stuff; open the mailbox, cycle through each message, strip off the
attachment, unzip it, and pass it to the tools that John wrote to read the
XML and store the results in a database, but I was working at a relatively
small site.) If the message isn't crafted specifically to match the format
mandated in the DMARC spec, it's not going to get processed; if the bad
actor takes the time to properly format an aggregate report and forge it to
appear to be from a given entity, what does the bad actor gain? If the
report contains data showing illegitimate mail that's not authenticating,
the target yawns. Best case for the bad guy, his report appears to contain
legit data showing that the target is sending email that isn't passing
authentication checks, and it causes someone at the target to try to chase
down a mailflow that isn't really there. And then what? The bad actor could
keep being a nuisance, but I suspect eventually he'd get bored, because
he's not going to have any visibility into the results of his actions.

As for forging failure reports, again what's in it for the actor doing the
forging? If the faked failure report is crafted to appear to contain
actionable data (something that's rare these days), the most likely
responses to that are one of the following:

   - In the case of the failure report appearing to show a message that
   forges domain A's identity and originated from a network run by B, maybe it
   fosters ill will between A and B's abuse desk, with A providing evidence of
   forged mail being emitted by B and asking B to take action, and B saying
   "not our problem"
   - In the case of the failure report appearing to show an unauthenticated
   message sent by A, again it's another case of someone at A trying to chase
   down and fix a phantom mail flow.

Unless our bad guy is playing a long game that I can't conceive of (and my
imagination can be limited) then I don't see that there's any money in it
for the bad guy, so I don't see why he'd bother to forge reports.

What threats do you have in mind, Michael?

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000005978bd05b9b979af
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, Jan 24, 2021 at 9:53 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"_blank">mike@mtcc.com<=
/a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex"><br>
On 1/24/21 6:29 PM, John R. Levine wrote:<br>
&gt; I realized why the arguments about whether to require authentication <=
br>
&gt; on reports are pointless.<br>
&gt;<br>
A blatant assertion. The onus of proof is with people who say we should <br=
>
accept information from unknown sources. Extraordinary claims require <br>
extraordinary evidence. I have been doing security related stuff for <br>
long enough to know that being humble in the face of adversaries is the <br=
>
most prudent course. State actors can get involved when they figure they <b=
r>
can game things to their advantage. To be dismissive is complete hubris.<br=
>
<br></blockquote><div><br></div><div>I&#39;ve spent several days thinking a=
bout these tickets, and for the life of me I can&#39;t see what the payoff =
might be for someone to forge a DMARC report.</div><div><br></div><div><div=
>I suppose nominally=C2=A0there&#39;s a denial of service risk, where a bad=
 actor could flood a rua or ruf mailbox with forged reports or just email i=
n general, but that&#39;s going to exist whether or not the &quot;reports&q=
uot; are DKIM-signed.</div><div><br></div><div>My first question for aggreg=
ate reports would focus on the DKIM signing domain - Should it align with t=
he RFC5322.From domain that sent the report, or with the org_name or email =
fields in the report_metadata bits in the XML itself? John has demonstrated=
 that there&#39;s no alignment now=C2=A0in many cases between the domain ge=
nerating reports and the domain(s) about which the reports are generated. Y=
ou almost have to require that the signing domain align with the RFC5322.Fr=
om domain, because DKIM validation is likely to be done by different infras=
tructure than does the report processing (see below) and the DKIM validatio=
n layer isn&#39;t likely to be able to read the reports, while the report p=
rocessing layer may be a simple tool that doesn&#39;t care to do DKIM valid=
ation.</div><div><br></div><div>About that, aggregate reports are meant to =
be machine-parsed, and in my own experience that&#39;s accomplished by runn=
ing a cron job a couple times a day to process the rua mailbox. (Personally=
, I favored Mark Overmeer&#39;s perl stuff; open the mailbox, cycle through=
 each message, strip off the attachment, unzip it, and pass it to the tools=
 that John wrote to read the XML and store the results in a database, but I=
 was working at a relatively small site.) If the message isn&#39;t crafted =
specifically to match the format mandated in the DMARC spec, it&#39;s not g=
oing to get processed; if the bad actor takes the time to properly format a=
n aggregate report and forge it to appear to be from a given entity, what d=
oes the bad actor gain? If the report contains data showing illegitimate ma=
il that&#39;s not authenticating, the target yawns. Best case for the bad g=
uy, his report appears to contain legit data showing that the target is sen=
ding email that isn&#39;t passing authentication checks, and it causes some=
one at the target to try to chase down a mailflow that isn&#39;t really the=
re. And then what? The bad actor could keep being a nuisance, but I suspect=
 eventually he&#39;d get bored, because he&#39;s not going to have any visi=
bility into the results of his actions.</div><div><br></div><div>As for for=
ging failure reports, again what&#39;s in it for the actor doing the forgin=
g? If the faked failure report is crafted to appear to contain actionable d=
ata (something that&#39;s rare these days), the most likely responses to th=
at are one of the following:</div><div><ul><li>In the case of the failure r=
eport appearing to show a message that forges domain A&#39;s identity and o=
riginated from a network run by B, maybe it fosters ill will between A and =
B&#39;s abuse desk, with A providing evidence of forged mail being emitted =
by B and asking B to take action, and B saying &quot;not our problem&quot;<=
/li><li>In the case of the failure report appearing to show an unauthentica=
ted message sent by A, again it&#39;s another case of someone at A trying t=
o chase down and fix a phantom mail flow.</li></ul><div>Unless our bad guy =
is playing a long game that I can&#39;t conceive of (and my imagination can=
 be limited) then I don&#39;t see that there&#39;s any money in it for the =
bad guy, so I don&#39;t see why he&#39;d bother to forge reports.</div></di=
v></div><div><br></div><div>What threats do you have in mind, Michael?</div=
><div>=C2=A0</div></div>-- <br><div dir=3D"ltr"><span><p dir=3D"ltr" style=
=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"t=
ext-align:left"><span style=3D"vertical-align:baseline;white-space:pre-wrap=
;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span style=3D"v=
ertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Ari=
al"> | Sr. Technical Program Manager</span></div><span style=3D"vertical-al=
ign:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div s=
tyle=3D"text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b><=
/span><span style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@=
valimail.com" target=3D"_blank">todd.herr@valimail.com</a></span></div></sp=
an><span><div><span><b>p:</b></span><span> 703.220.4153 </span><span></span=
></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial=
,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical=
-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercon=
tent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0Lh=
bnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" sty=
le=3D"border:none;height:40px;width:177px"></span></p><p dir=3D"ltr" style=
=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:sm=
all;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,=
255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666=
666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre-wrap=
">This email and all data transmitted with it contains confidential and/or =
proprietary information intended solely for the use of individual(s) author=
ized to receive it. If you are not an intended and authorized recipient you=
 are hereby notified of any use, disclosure, copying or distribution of the=
 information included in this transmission is prohibited and may be unlawfu=
l. Please immediately notify the sender by replying to this email and then =
delete it from your system.</span></font></p></span></div></div>

--0000000000005978bd05b9b979af--


From nobody Mon Jan 25 07:18:03 2021
Return-Path: <mike@fresheez.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 E8C6F3A1474 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 07:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.151
X-Spam-Level: 
X-Spam-Status: No, score=0.151 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 g6ePK_ZtU6k7 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 07:17:59 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 837473A146E for <dmarc@ietf.org>; Mon, 25 Jan 2021 07:17:59 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id t25so1160076pga.2 for <dmarc@ietf.org>; Mon, 25 Jan 2021 07:17:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=Xq/56F7cgAQd9hIgU/jVf7p5hHdUJLss9scp6TJ0HZk=; b=ByBHNMmmqGfGrHA18+f8dDkG4/4sI1qoysJOfIpw3XxqkV7A3zuOBGvyFkCXj8yipY bSW3yyjx4SRiLO7BRm8hRwUZKCQzv5cC+p5/puJKtJ3Nprl0+LCQszPDYqSyE+aRWeBy STjsSVQdt4MNNx807L437o1jjSbdTfPyQueeZFH/z2tmBRgZAy/K4sJOS3rJkKOEBu5p 6vm63udDAlQT2206bUhfw12CjuDsThFVMPp3HtlDcmaQGipH3DtT3wGmG6ZvjrM2umTB vH8Q2dahQf0izGPR5tNQjD0/TWux+KtDpK3SZL0CT6qWKU7FhpvlHsz7iurACm4x9zWO 5zhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=Xq/56F7cgAQd9hIgU/jVf7p5hHdUJLss9scp6TJ0HZk=; b=aF2cruJXyXmZMMskWS3bzrHUtcTIlT3B02k2QVDeUvR3+EbS+3Ac5fVPriPcvwL/Qw fuTskVtNNdzYrNidPjUq02zKm4I/gVfpKG2CDcoABEO0B+Y+IcDkQMgp0z6atQgXtWgr V/ex0l4JsZZyd0RiSorLJlYPM+YfANrn2JboY5UakeYRwMbJsEBY3YX9c63TqrCImqR5 omfSP0Y5v/l7p+P9vbSfTNjwrO6gL0CUub1vX8m9ClZlTblXEEmSHAzIl5UpbrzXPEnc btcB8wWiLsnsUSnGGgGRa3QUzbvZkuDh6wv8ENiih2X1q+12WgDw6s3/iT73gerFWDgC XB8w==
X-Gm-Message-State: AOAM533eKuIzXQTBEtpwLv/+B2Ie8n7hZxu0NVIpVUDBIFkdOkVoXl8Z /GpoRbJJhL2QJW0yhYEkpsJ/nV/hxFSLjA==
X-Google-Smtp-Source: ABdhPJwp+zYC7BDkO7YBqcjAFs2gZ+TOnc5uCm70MWFVVCrYyswLtNnsPNyKXGDi4IxiUu6uNPVlHw==
X-Received: by 2002:a62:a508:0:b029:1ba:621:ff29 with SMTP id v8-20020a62a5080000b02901ba0621ff29mr918997pfm.44.1611587878497;  Mon, 25 Jan 2021 07:17:58 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id hs21sm18953170pjb.6.2021.01.25.07.17.57 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 07:17:57 -0800 (PST)
To: dmarc@ietf.org
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com>
Date: Mon, 25 Jan 2021 07:17:56 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A56748F1AAF581010D9F620E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/H13Gxh7PTIt_YqR1WGOeBOsWkjs>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 15:18:01 -0000

This is a multi-part message in MIME format.
--------------A56748F1AAF581010D9F620E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/25/21 5:25 AM, Todd Herr wrote:
> On Sun, Jan 24, 2021 at 9:53 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     On 1/24/21 6:29 PM, John R. Levine wrote:
>     > I realized why the arguments about whether to require
>     authentication
>     > on reports are pointless.
>     >
>     A blatant assertion. The onus of proof is with people who say we
>     should
>     accept information from unknown sources. Extraordinary claims require
>     extraordinary evidence. I have been doing security related stuff for
>     long enough to know that being humble in the face of adversaries
>     is the
>     most prudent course. State actors can get involved when they
>     figure they
>     can game things to their advantage. To be dismissive is complete
>     hubris.
>
>
> I've spent several days thinking about these tickets, and for the life 
> of me I can't see what the payoff might be for someone to forge a 
> DMARC report.
>
> I suppose nominally there's a denial of service risk, where a bad 
> actor could flood a rua or ruf mailbox with forged reports or just 
> email in general, but that's going to exist whether or not the 
> "reports" are DKIM-signed.

The main thing I've learned over the years of dealing with security is 
to not underestimate what a motivated attacker can do. Your imagination 
is not the same as their imagination. Closing #98 in particular is 
absolutely ridiculous: the report should already have a DKIM signature 
or SPF so it's just a matter of making sure its valid. Why would you 
*not* want to insure that? The amount of justification for *not* having 
the receiver authenticate it is a mountain. The amount of effort to 
authenticate it is trivial for mail. Levine's dismissal of security 
concerns because he has anecdotal "evidence" from a backwater domain 
carries no weight at all.

Mike

--------------A56748F1AAF581010D9F620E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 5:25 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Sun, Jan 24, 2021 at 9:53 PM Michael Thomas
          &lt;<a href="mailto:mike@mtcc.com" target="_blank"
            moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex"><br>
            On 1/24/21 6:29 PM, John R. Levine wrote:<br>
            &gt; I realized why the arguments about whether to require
            authentication <br>
            &gt; on reports are pointless.<br>
            &gt;<br>
            A blatant assertion. The onus of proof is with people who
            say we should <br>
            accept information from unknown sources. Extraordinary
            claims require <br>
            extraordinary evidence. I have been doing security related
            stuff for <br>
            long enough to know that being humble in the face of
            adversaries is the <br>
            most prudent course. State actors can get involved when they
            figure they <br>
            can game things to their advantage. To be dismissive is
            complete hubris.<br>
            <br>
          </blockquote>
          <div><br>
          </div>
          <div>I've spent several days thinking about these tickets, and
            for the life of me I can't see what the payoff might be for
            someone to forge a DMARC report.</div>
          <div><br>
          </div>
          <div>
            <div>I suppose nominally there's a denial of service risk,
              where a bad actor could flood a rua or ruf mailbox with
              forged reports or just email in general, but that's going
              to exist whether or not the "reports" are DKIM-signed.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>The main thing I've learned over the years of dealing with
      security is to not underestimate what a motivated attacker can do.
      Your imagination is not the same as their imagination. Closing #98
      in particular is absolutely ridiculous: the report should already
      have a DKIM signature or SPF so it's just a matter of making sure
      its valid. Why would you *not* want to insure that? The amount of
      justification for *not* having the receiver authenticate it is a
      mountain. The amount of effort to authenticate it is trivial for
      mail. Levine's dismissal of security concerns because he has
      anecdotal "evidence" from a backwater domain carries no weight at
      all. <br>
    </p>
    Mike<br>
  </body>
</html>

--------------A56748F1AAF581010D9F620E--


From nobody Mon Jan 25 08:44:25 2021
Return-Path: <todd.herr@valimail.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 A1FE73A14F7 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 08:44:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 te9gvlFAYeaW for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 08:44:21 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85EC93A14F6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 08:44:21 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id l23so7633057qtq.13 for <dmarc@ietf.org>; Mon, 25 Jan 2021 08:44:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=+bgW2O+z7O5D8NPxqS/w2MWH+fpc0n5+McvXjTLPrC8=; b=B5DI/H3J46f2AQNYx0oivOOOodt5D4mwyAuScXZX+8m9RG1CZLZ5aBd2qyRBhCgE/x SHig2WCXtrU1TBPGV1gFAh/7SxnR/6wqCt+jcHoqg7AM87i9sE6CHO0120N4+pIOF4iN /SLWgTxT6gk+6/6trZtVODoAhi2rrSSFSFObp/CPY/arwXXB93d692hPN3rklgoPlnbj 6r6yt8SqT7dOL6xFgYcWaRR/D72/3spiXtVCRsILSnzU122fQDmwNPF7YHTOLVhJ2Bg8 f07vMVaeGtNQYL03lMai/gQnLSAy13874mCFD+xvRMvwORTTdgZCCatyOwl+z0xhRMXh MGPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+bgW2O+z7O5D8NPxqS/w2MWH+fpc0n5+McvXjTLPrC8=; b=Cdl9mnTLOJmEvzCAp3S0hKxIOgWJC/Oj6No34KkUdMiSwLKA8WodHW9oYwp0RvpePH kZ5dwDdOfCDdzDKbp3p6qJCU/gUiXdnvSPvN68M8Isq6Y9SBZvcgcHdr03jcNOXEIYz3 zz6ZphiqDp0hZg8pYoN4T8q4r5U/ae8/KMa4xbNs/lE9uXccA2MGhpXYwJ11xmsx48Pm djkTBP3fSwG95J6wjR1i0Ov46e1Geb8lT81KnCTwAx2w7qltakrt4nJKuO7TpxzPJJ5E oUmh4Gh/17V7ZjPamm9rBLuc00P0bdmAka121m+7AWqmr+0bBV8Jj4DAp/smRrtRSsTh 0/FQ==
X-Gm-Message-State: AOAM530+vswAvCubVrtPVjL0Nfzb9fqgXTCspzI604+27fdhYU3PHmaP N5HC0+kJOXHyCTGKoNiDal0Z6Lf3NREyF9aQc/UmSwLoms0=
X-Google-Smtp-Source: ABdhPJxE4QV6vGF8kfVbnhgsbKrY+Ys7XiSoBV6BirTmZClH9BHL/YmsWp+YuoW+ECZYs+Y/C8ukYKRJJK7/hDGnVtw=
X-Received: by 2002:ac8:3a66:: with SMTP id w93mr1281152qte.220.1611593060076;  Mon, 25 Jan 2021 08:44:20 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com>
In-Reply-To: <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 25 Jan 2021 11:44:04 -0500
Message-ID: <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de621105b9bc3f0d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZAgtD4MgiJvNhrOxftuGcsVezNI>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 16:44:24 -0000

--000000000000de621105b9bc3f0d
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/25/21 5:25 AM, Todd Herr wrote:
>
> On Sun, Jan 24, 2021 at 9:53 PM Michael Thomas <mike@mtcc.com> wrote:
>
>>
>> On 1/24/21 6:29 PM, John R. Levine wrote:
>> > I realized why the arguments about whether to require authentication
>> > on reports are pointless.
>> >
>> A blatant assertion. The onus of proof is with people who say we should
>> accept information from unknown sources. Extraordinary claims require
>> extraordinary evidence. I have been doing security related stuff for
>> long enough to know that being humble in the face of adversaries is the
>> most prudent course. State actors can get involved when they figure they
>> can game things to their advantage. To be dismissive is complete hubris.
>>
>>
> I've spent several days thinking about these tickets, and for the life of
> me I can't see what the payoff might be for someone to forge a DMARC report.
>
> I suppose nominally there's a denial of service risk, where a bad actor
> could flood a rua or ruf mailbox with forged reports or just email in
> general, but that's going to exist whether or not the "reports" are
> DKIM-signed.
>
> The main thing I've learned over the years of dealing with security is to
> not underestimate what a motivated attacker can do. Your imagination is not
> the same as their imagination. Closing #98 in particular is absolutely
> ridiculous: the report should already have a DKIM signature or SPF so it's
> just a matter of making sure its valid. Why would you *not* want to insure
> that? The amount of justification for *not* having the receiver
> authenticate it is a mountain. The amount of effort to authenticate it is
> trivial for mail. Levine's dismissal of security concerns because he has
> anecdotal "evidence" from a backwater domain carries no weight at all.
>

That's all well and good, but you haven't answered the question I asked.

What threats do you have in mind? Put another way, how do you envision an
attacker exploiting the lack of authentication in a DMARC report to his or
her gain?

I recognize that my imagination, or yours, may not match what a motivated
attacker can do. I have presented some possible scenarios that might result
from a forged DMARC report, and in them I don't see a gain for the
attacker, unless his or her goal is to be an annoyance to the target.

Can you please describe a scenario where an attacker might use a forged
DMARC report to gain something of value from the target of his/her forgery?

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000de621105b9bc3f0d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 25, 2021 at 10:18 AM Michael =
Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"_blank">mike@mtcc.com=
</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/25/21 5:25 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Sun, Jan 24, 2021 at 9:53 PM Michael Thomas
          &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"_blank">mike@mtcc.=
com</a>&gt; wrote:<br>
        </div>
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
            On 1/24/21 6:29 PM, John R. Levine wrote:<br>
            &gt; I realized why the arguments about whether to require
            authentication <br>
            &gt; on reports are pointless.<br>
            &gt;<br>
            A blatant assertion. The onus of proof is with people who
            say we should <br>
            accept information from unknown sources. Extraordinary
            claims require <br>
            extraordinary evidence. I have been doing security related
            stuff for <br>
            long enough to know that being humble in the face of
            adversaries is the <br>
            most prudent course. State actors can get involved when they
            figure they <br>
            can game things to their advantage. To be dismissive is
            complete hubris.<br>
            <br>
          </blockquote>
          <div><br>
          </div>
          <div>I&#39;ve spent several days thinking about these tickets, an=
d
            for the life of me I can&#39;t see what the payoff might be for
            someone to forge a DMARC report.</div>
          <div><br>
          </div>
          <div>
            <div>I suppose nominally=C2=A0there&#39;s a denial of service r=
isk,
              where a bad actor could flood a rua or ruf mailbox with
              forged reports or just email in general, but that&#39;s going
              to exist whether or not the &quot;reports&quot; are DKIM-sign=
ed.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>The main thing I&#39;ve learned over the years of dealing with
      security is to not underestimate what a motivated attacker can do.
      Your imagination is not the same as their imagination. Closing #98
      in particular is absolutely ridiculous: the report should already
      have a DKIM signature or SPF so it&#39;s just a matter of making sure
      its valid. Why would you *not* want to insure that? The amount of
      justification for *not* having the receiver authenticate it is a
      mountain. The amount of effort to authenticate it is trivial for
      mail. Levine&#39;s dismissal of security concerns because he has
      anecdotal &quot;evidence&quot; from a backwater domain carries no wei=
ght at
      all.</p></div></blockquote><div><br></div><div>That&#39;s all well an=
d good, but you haven&#39;t answered the question I asked.</div><div><br></=
div><div>What threats do you have in mind? Put another way, how do you envi=
sion an attacker exploiting the lack of authentication in a DMARC report to=
 his or her gain?</div><div><br></div><div>I recognize that my imagination,=
 or yours, may not match what a motivated attacker can do. I have presented=
 some possible scenarios that might result from a forged DMARC report, and =
in them I don&#39;t see a gain for the attacker, unless his or her goal is =
to be an annoyance to the target.</div><div><br></div><div>Can you please d=
escribe a scenario where an attacker might use a forged DMARC report to gai=
n something of value from the target of his/her forgery?</div></div><div><b=
r></div>-- <br><div dir=3D"ltr"><span><p dir=3D"ltr" style=3D"line-height:1=
.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><=
span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;=
font-family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:bas=
eline;white-space:pre-wrap;font-size:small;font-family:Arial"> | Sr. Techni=
cal Program Manager</span></div><span style=3D"vertical-align:baseline;whit=
e-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-alig=
n:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span style=
=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" tar=
get=3D"_blank">todd.herr@valimail.com</a></span></div></span><span><div><sp=
an><b>p:</b></span><span> 703.220.4153 </span><span></span></div></span><p =
dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-s=
erif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;w=
hite-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iR=
jfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_T=
c_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border:none=
;height:40px;width:177px"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,3=
4,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-col=
or:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>=
</p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1=
.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial=
"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and a=
ll data transmitted with it contains confidential and/or proprietary inform=
ation intended solely for the use of individual(s) authorized to receive it=
. If you are not an intended and authorized recipient you are hereby notifi=
ed of any use, disclosure, copying or distribution of the information inclu=
ded in this transmission is prohibited and may be unlawful. Please immediat=
ely notify the sender by replying to this email and then delete it from you=
r system.</span></font></p></span></div></div>

--000000000000de621105b9bc3f0d--


From nobody Mon Jan 25 08:51:47 2021
Return-Path: <mike@fresheez.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 B663D3A1500 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 08:51:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 kXaAySy-BDfc for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 08:51:43 -0800 (PST)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 729893A1501 for <dmarc@ietf.org>; Mon, 25 Jan 2021 08:51:43 -0800 (PST)
Received: by mail-pl1-x633.google.com with SMTP id b17so1462638plz.6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 08:51:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=VnYACN6hynDE3NN+G9XMvb12VM7s9nnvVj0eeOSSLU4=; b=aotBWd2kfEjyF1TjXRJVoq6KwRD5IqhDbnrdUj9EVMMlIYohQyuLG4zIPscadmKtC/ 18irXlnRkMAVDrmQaE4oC5JwvUZnYIJcOUvvltL5JWHorFWE+IPBv51Jh1dZbDxMC0UU 3nsaLdxxxrmNjwPLGDSX/7d6o5uYnWgW/kp2YgZ1VKwH49uITAzKVzB65RlpprCSQwiF s8RioONk519YNCg7tJTP414LN+9zKiAYpjBO6CKvEFhfp+TumobSP8vfXFOtDe5/h4N4 NAtE9CCEBiVUM30r+XVFFSLrtMF+1Kvu/H6Ydy2Zu9BUYHdgSQrgYBpUy/FD51VSY+lC HANQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=VnYACN6hynDE3NN+G9XMvb12VM7s9nnvVj0eeOSSLU4=; b=YK+9J7IDY3X6mfRv1IthwlazFNUIZ7L/ZTUI7vCpz8vkRSFv5dfSFPBU4+fr+4oumE iU7IA0EmB9v8e11jSEM25NZTEnki4dvxN9WSh/0hqUMCXRud3ZplV1pDDD0hDLwj6Kiu NqlxLEgcsSF2M+FPOIHtvns8pCUfniODJ/hAOAmbmipyRd5EqPTnSrmH5RNsUHKjdQY8 ZA6+kBv5LGJhBE6CAd7cZNVXri2n8BIFdpcIC5NRlEtKTvgk4dnEXDjPXnyNazlIfncR YSRiMorGVxFB311vIRtvkc5ylBKrRDZ5u3ETlpFlam7mLSFfXkCb2ZEvK92qtvppm6Kj DCkA==
X-Gm-Message-State: AOAM530qxRIgzV/AoiD4WojZgdze08TM9buykwPFc+O7I/eXHs1rM9ai 2qx2KSdLO5aNOKEyYuSy19uiksPaMjv89g==
X-Google-Smtp-Source: ABdhPJzpDW0Mha2sR6u5k+2FGutvZuIeZHqulqzN/Xh0XM7mNtvBHywfgYxEeVhYvhF/jqSYOC/OEA==
X-Received: by 2002:a17:90b:94c:: with SMTP id dw12mr1076937pjb.77.1611593502485;  Mon, 25 Jan 2021 08:51:42 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id z2sm17626891pgl.49.2021.01.25.08.51.40 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 08:51:41 -0800 (PST)
To: dmarc@ietf.org
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com>
Date: Mon, 25 Jan 2021 08:51:39 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8C7D0FBF14E723DD74B4241A"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Vn-MKb1QRtkwu2rfijULJOssLbU>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 16:51:45 -0000

This is a multi-part message in MIME format.
--------------8C7D0FBF14E723DD74B4241A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/25/21 8:44 AM, Todd Herr wrote:
> On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     The main thing I've learned over the years of dealing with
>     security is to not underestimate what a motivated attacker can do.
>     Your imagination is not the same as their imagination. Closing #98
>     in particular is absolutely ridiculous: the report should already
>     have a DKIM signature or SPF so it's just a matter of making sure
>     its valid. Why would you *not* want to insure that? The amount of
>     justification for *not* having the receiver authenticate it is a
>     mountain. The amount of effort to authenticate it is trivial for
>     mail. Levine's dismissal of security concerns because he has
>     anecdotal "evidence" from a backwater domain carries no weight at all.
>
>
> That's all well and good, but you haven't answered the question I asked.
>
> What threats do you have in mind? Put another way, how do you envision 
> an attacker exploiting the lack of authentication in a DMARC report to 
> his or her gain?
>
No, sorry, the onus is on the people who don't think it can be gamed. A 
bald assertion that it can't be gamed is very unconvincing. You need to 
lay out a miles long case for why it cannot be gamed. And to what end? 
#98 has a simple piece of text that should be added to DMARC to 
eliminate the possibility of forgery. You'd need a 10 page threat I-D to 
explain why it's not necessary. What is the point of that? For email, 
it's trivial to prevent forgeries. Why would anybody argue against that?

Mike


--------------8C7D0FBF14E723DD74B4241A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 8:44 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas
          &lt;<a href="mailto:mike@mtcc.com" target="_blank"
            moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div><br>
              <p>The main thing I've learned over the years of dealing
                with security is to not underestimate what a motivated
                attacker can do. Your imagination is not the same as
                their imagination. Closing #98 in particular is
                absolutely ridiculous: the report should already have a
                DKIM signature or SPF so it's just a matter of making
                sure its valid. Why would you *not* want to insure that?
                The amount of justification for *not* having the
                receiver authenticate it is a mountain. The amount of
                effort to authenticate it is trivial for mail. Levine's
                dismissal of security concerns because he has anecdotal
                "evidence" from a backwater domain carries no weight at
                all.</p>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>That's all well and good, but you haven't answered the
            question I asked.</div>
          <div><br>
          </div>
          <div>What threats do you have in mind? Put another way, how do
            you envision an attacker exploiting the lack of
            authentication in a DMARC report to his or her gain?</div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>No, sorry, the onus is on the people who don't think it can be
      gamed. A bald assertion that it can't be gamed is very
      unconvincing. You need to lay out a miles long case for why it
      cannot be gamed. And to what end? #98 has a simple piece of text
      that should be added to DMARC to eliminate the possibility of
      forgery. You'd need a 10 page threat I-D to explain why it's not
      necessary. What is the point of that? For email, it's trivial to
      prevent forgeries. Why would anybody argue against that?</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------8C7D0FBF14E723DD74B4241A--


From nobody Mon Jan 25 09:10:50 2021
Return-Path: <dougfoster.emailstandards@gmail.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 8F9273A1566 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KNFKA7vdFWm9 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:10:46 -0800 (PST)
Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A97793A0E7E for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:10:46 -0800 (PST)
Received: by mail-ua1-x935.google.com with SMTP id u27so4656781uaa.13 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:10:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=idPqu0iOSxZBU+InP0ksal+CQHMO/rQgXroVtmKKp1A=; b=fiXWQ86vjtZNEBYfbYyh9WQ0ORd4MmSRvplGRONicQPX5lwMC9ACcyRZ4hawLeEW8b v1UXInMFLfzWXDXMyqt1dn8eB/NnSjnsq2I1r8Xd0Sa6+OLW2+2ZVLNlcObUa6rODGmE LaoNY+dwzSNGtESWl6gr+Me1qm5d9wyazKi+cQ+/xh+ejRXAITTj3baVdRFzSYPlblqO uz70z+mBM8mYFFUF4Nqo3FYHYDY5DX+OlWb5DbhQNpgFPevuF/KhTbbbm76dZ2N165Ce xELRhQpCWajM4iYhZTCLCsMxY9pZI6ulceQKk9nZStQu1SlD8RQXDhv81dQAf6Z/9iOu bmAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=idPqu0iOSxZBU+InP0ksal+CQHMO/rQgXroVtmKKp1A=; b=PmDoxajz6BiZmgJwmd24pwJQgLqRiVK5echrxMxWA5xC4nMxZzQad2QV1PanPr5j2i 0FUWp0HYw3i/S8WaB/gqosrzP8G+nMZClZD99Wp/yc/fCxBUf6Xjb5rRYT4b16ZSmFnm /1lbEtRKH69gbIDZgLssC5hMxnMccBwzGWbszF20euT+/57JSFp9VZIBQXAd62mwDGPh oHq4YezFeggXb+7JbmdEreD9al0xlJ2m2bZyG4D/dfAKE45624d64Twk0zBCR/3K/tmy FkZvZXcrCL1VMvoH5s77QWnv5nyFQnecTwcSjGRgligZbRFM1+HRy9STdqZ4bWPGGcm8 90bQ==
X-Gm-Message-State: AOAM532VOVDf9HoY3Em5nON/uKzViTjLasdo2Oj4juO8wYQbKwS5Fk6/ 4ASsEr0OMBtOLIvt+r/F7R0vLvOJ1rIhd//qtWyqh/N2
X-Google-Smtp-Source: ABdhPJx2GTy0W/82nHGXQ2EJ5aLGRq03fdWrNWDMhaNaxPPaIEyFM5IWCc8MyJnHOjnTcXAnv/Z0BHgkjLfdnTQEZZA=
X-Received: by 2002:ab0:7547:: with SMTP id k7mr1347387uaq.95.1611594645050; Mon, 25 Jan 2021 09:10:45 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com>
In-Reply-To: <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 25 Jan 2021 12:10:30 -0500
Message-ID: <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005719e005b9bc9e2e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rJRK0AdEMI2CV0-1hoziUIEMEmM>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:10:49 -0000

--0000000000005719e005b9bc9e2e
Content-Type: text/plain; charset="UTF-8"

Since the status quo is unauthenticated, I wonder if adding a signing
requirement will help.
Will recipients discad unsigned messages, or accept whatever is available
to maximize their information capture?  I suspect they will conrinye to
accept everything.

I think we would need an identified threat before recipients would be
motivated to discard.

But what about John's problems with receiving reports that should not have
gone to him?   I did not understand the root cause, but I would hope there
is something that can be done.  Would signing help receiving sites, those
with less sophistication than he has, be able to sort out noise more
effectively?


On Mon, Jan 25, 2021, 11:51 AM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/25/21 8:44 AM, Todd Herr wrote:
>
> On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas <mike@mtcc.com> wrote:
>
>>
>> The main thing I've learned over the years of dealing with security is to
>> not underestimate what a motivated attacker can do. Your imagination is not
>> the same as their imagination. Closing #98 in particular is absolutely
>> ridiculous: the report should already have a DKIM signature or SPF so it's
>> just a matter of making sure its valid. Why would you *not* want to insure
>> that? The amount of justification for *not* having the receiver
>> authenticate it is a mountain. The amount of effort to authenticate it is
>> trivial for mail. Levine's dismissal of security concerns because he has
>> anecdotal "evidence" from a backwater domain carries no weight at all.
>>
>
> That's all well and good, but you haven't answered the question I asked.
>
> What threats do you have in mind? Put another way, how do you envision an
> attacker exploiting the lack of authentication in a DMARC report to his or
> her gain?
>
> No, sorry, the onus is on the people who don't think it can be gamed. A
> bald assertion that it can't be gamed is very unconvincing. You need to lay
> out a miles long case for why it cannot be gamed. And to what end? #98 has
> a simple piece of text that should be added to DMARC to eliminate the
> possibility of forgery. You'd need a 10 page threat I-D to explain why it's
> not necessary. What is the point of that? For email, it's trivial to
> prevent forgeries. Why would anybody argue against that?
>
> Mike
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--0000000000005719e005b9bc9e2e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Since the status quo is unauthenticated, I wonder if addi=
ng a signing requirement will help.<div dir=3D"auto">Will recipients discad=
 unsigned messages, or accept whatever is available to maximize their infor=
mation capture?=C2=A0 I suspect they will conrinye to accept everything.</d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">I think we would need an i=
dentified threat before recipients would be motivated to discard.</div><div=
 dir=3D"auto"><br></div><div dir=3D"auto">But what about John&#39;s problem=
s with receiving reports that should not have gone to him?=C2=A0 =C2=A0I di=
d not understand the root cause, but I would hope there is something that c=
an be done.=C2=A0 Would signing help receiving sites, those with less sophi=
stication than he has, be able to sort out noise more effectively?</div><di=
v dir=3D"auto"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Mon, Jan 25, 2021, 11:51 AM Michael Thomas &lt;=
<a href=3D"mailto:mike@mtcc.com" target=3D"_blank" rel=3D"noreferrer">mike@=
mtcc.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/25/21 8:44 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas
          &lt;<a href=3D"mailto:mike@mtcc.com" rel=3D"noreferrer noreferrer=
" target=3D"_blank">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div><br>
              <p>The main thing I&#39;ve learned over the years of dealing
                with security is to not underestimate what a motivated
                attacker can do. Your imagination is not the same as
                their imagination. Closing #98 in particular is
                absolutely ridiculous: the report should already have a
                DKIM signature or SPF so it&#39;s just a matter of making
                sure its valid. Why would you *not* want to insure that?
                The amount of justification for *not* having the
                receiver authenticate it is a mountain. The amount of
                effort to authenticate it is trivial for mail. Levine&#39;s
                dismissal of security concerns because he has anecdotal
                &quot;evidence&quot; from a backwater domain carries no wei=
ght at
                all.</p>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>That&#39;s all well and good, but you haven&#39;t answered t=
he
            question I asked.</div>
          <div><br>
          </div>
          <div>What threats do you have in mind? Put another way, how do
            you envision an attacker exploiting the lack of
            authentication in a DMARC report to his or her gain?</div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>No, sorry, the onus is on the people who don&#39;t think it can be
      gamed. A bald assertion that it can&#39;t be gamed is very
      unconvincing. You need to lay out a miles long case for why it
      cannot be gamed. And to what end? #98 has a simple piece of text
      that should be added to DMARC to eliminate the possibility of
      forgery. You&#39;d need a 10 page threat I-D to explain why it&#39;s =
not
      necessary. What is the point of that? For email, it&#39;s trivial to
      prevent forgeries. Why would anybody argue against that?</p>
    <p>Mike<br>
    </p>
  </div>

_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/dmarc</a><br>
</blockquote></div>

--0000000000005719e005b9bc9e2e--


From nobody Mon Jan 25 09:19:33 2021
Return-Path: <seth@valimail.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 68B643A15D4 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:19:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 zQjgGmsLIH9e for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:19:30 -0800 (PST)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE1F13A1657 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:19:21 -0800 (PST)
Received: by mail-vs1-xe34.google.com with SMTP id e15so7583317vsa.0 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:19:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+9BdNjqRzVWakKdMtHj60gQajrJzqgd/UWLr0fUXO/E=; b=UM0BEG18a6CCfTSFB1H5hmA2tY/LPtLQqLv0ST/BbSYUUoVPIeG4VecwG6QgJnCwT3 Le29/3oLYM8kHk944mw7jCorkrhgcXjNacnC7JoR1l+XEJzT9eqeGrJWGJ/D2FRzPbvB rvby1mkgxo/cX7Il3bXbqE0KwJaeQz1NtPaqyXTwHyzXhNrYvr09UiIrcnpAFh4OFhVo 7CzS6LTI5kEAbjcvp+nNNJJulijtxZA2FKpcGyDAYXEOMx5oOh7PaSNb8sYYeS6Ifd4X HumcO+LZHaLh1DxiJ1iepmYekT0bPy14W0sUi1dnSD+OH/d2ZB83yz16OrtvYoYysopt y54g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+9BdNjqRzVWakKdMtHj60gQajrJzqgd/UWLr0fUXO/E=; b=U+xtGopCGa0uf/dXV/GJAzcGskVh90CSYe3t9jnt9notV2UPGGCq6D0xMCejtZUICk P3K695MRqz43mhgvYnk60OT/WxRMRh33dnh6KwroEn/6On60ukaGpwv6OtB1gP+s4eRB YrK/c5uhyTEgDyuS5Tczk5zPhIZYWsC84gal1/Gsdqi/weerXVRcoNg+UB87MlPs00ya n5kjpI78LUz1MQHuqA+R6+KxSOzHD6NOM+tvBMYAv2yOBGSxqUtOSxU/qiPlOaqLwvM5 kgEl+pCEoBtiOhEP5un5cnxegNVJtgIPq/kYmWsDKAcOtBQ8eFuW2w2f32e/YX6ndJYb GRxw==
X-Gm-Message-State: AOAM530bDZRTbEeeFLkjzdGZo4liEdzO44ujEyXz76T98CvGM23Yaz56 01ePxz9tS0/2bfrt8LVuzK2Th5BdOSJBMiR2jspi1C9lMV5OOw==
X-Google-Smtp-Source: ABdhPJzYaFPT/6f/QMYPZhcQ/mWe1Pi2cfoCPT7OXO8aqkPZ8eS7wXUcEBpyzkXBL5DQs0SFn++Ovhn9RTmRvMbKhXM=
X-Received: by 2002:a67:fd5a:: with SMTP id g26mr1718509vsr.35.1611595160385;  Mon, 25 Jan 2021 09:19:20 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com>
In-Reply-To: <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 25 Jan 2021 09:19:09 -0800
Message-ID: <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Michael Thomas <mike@mtcc.com>
Content-Type: multipart/alternative; boundary="0000000000000e960c05b9bcbd9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/it3v99syJQXN2C74Q6p3Rp3w2sE>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:19:32 -0000

--0000000000000e960c05b9bcbd9d
Content-Type: text/plain; charset="UTF-8"

What operational problem are we solving here? Absent evidence of a problem
and strong consensus on the solution, let's close these tickets and move on.

On Mon, Jan 25, 2021 at 9:10 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> Since the status quo is unauthenticated, I wonder if adding a signing
> requirement will help.
> Will recipients discad unsigned messages, or accept whatever is available
> to maximize their information capture?  I suspect they will conrinye to
> accept everything.
>
> I think we would need an identified threat before recipients would be
> motivated to discard.
>
> But what about John's problems with receiving reports that should not have
> gone to him?   I did not understand the root cause, but I would hope there
> is something that can be done.  Would signing help receiving sites, those
> with less sophistication than he has, be able to sort out noise more
> effectively?
>
>
> On Mon, Jan 25, 2021, 11:51 AM Michael Thomas <mike@mtcc.com> wrote:
>
>>
>> On 1/25/21 8:44 AM, Todd Herr wrote:
>>
>> On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas <mike@mtcc.com> wrote:
>>
>>>
>>> The main thing I've learned over the years of dealing with security is
>>> to not underestimate what a motivated attacker can do. Your imagination is
>>> not the same as their imagination. Closing #98 in particular is absolutely
>>> ridiculous: the report should already have a DKIM signature or SPF so it's
>>> just a matter of making sure its valid. Why would you *not* want to insure
>>> that? The amount of justification for *not* having the receiver
>>> authenticate it is a mountain. The amount of effort to authenticate it is
>>> trivial for mail. Levine's dismissal of security concerns because he has
>>> anecdotal "evidence" from a backwater domain carries no weight at all.
>>>
>>
>> That's all well and good, but you haven't answered the question I asked.
>>
>> What threats do you have in mind? Put another way, how do you envision an
>> attacker exploiting the lack of authentication in a DMARC report to his or
>> her gain?
>>
>> No, sorry, the onus is on the people who don't think it can be gamed. A
>> bald assertion that it can't be gamed is very unconvincing. You need to lay
>> out a miles long case for why it cannot be gamed. And to what end? #98 has
>> a simple piece of text that should be added to DMARC to eliminate the
>> possibility of forgery. You'd need a 10 page threat I-D to explain why it's
>> not necessary. What is the point of that? For email, it's trivial to
>> prevent forgeries. Why would anybody argue against that?
>>
>> Mike
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000000e960c05b9bcbd9d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What operational problem are we solving here?=C2=A0Absent =
evidence of a problem and strong consensus on the solution, let&#39;s close=
 these tickets and move on.<div></div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 9:10 AM Dougl=
as Foster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfo=
ster.emailstandards@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"auto">Since the status quo is unau=
thenticated, I wonder if adding a signing requirement will help.<div dir=3D=
"auto">Will recipients discad unsigned messages, or accept whatever is avai=
lable to maximize their information capture?=C2=A0 I suspect they will conr=
inye to accept everything.</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">I think we would need an identified threat before recipients would be mo=
tivated to discard.</div><div dir=3D"auto"><br></div><div dir=3D"auto">But =
what about John&#39;s problems with receiving reports that should not have =
gone to him?=C2=A0 =C2=A0I did not understand the root cause, but I would h=
ope there is something that can be done.=C2=A0 Would signing help receiving=
 sites, those with less sophistication than he has, be able to sort out noi=
se more effectively?</div><div dir=3D"auto"><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021=
, 11:51 AM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com" rel=3D"noref=
errer" target=3D"_blank">mike@mtcc.com</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/25/21 8:44 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas
          &lt;<a href=3D"mailto:mike@mtcc.com" rel=3D"noreferrer noreferrer=
" target=3D"_blank">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div><br>
              <p>The main thing I&#39;ve learned over the years of dealing
                with security is to not underestimate what a motivated
                attacker can do. Your imagination is not the same as
                their imagination. Closing #98 in particular is
                absolutely ridiculous: the report should already have a
                DKIM signature or SPF so it&#39;s just a matter of making
                sure its valid. Why would you *not* want to insure that?
                The amount of justification for *not* having the
                receiver authenticate it is a mountain. The amount of
                effort to authenticate it is trivial for mail. Levine&#39;s
                dismissal of security concerns because he has anecdotal
                &quot;evidence&quot; from a backwater domain carries no wei=
ght at
                all.</p>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>That&#39;s all well and good, but you haven&#39;t answered t=
he
            question I asked.</div>
          <div><br>
          </div>
          <div>What threats do you have in mind? Put another way, how do
            you envision an attacker exploiting the lack of
            authentication in a DMARC report to his or her gain?</div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>No, sorry, the onus is on the people who don&#39;t think it can be
      gamed. A bald assertion that it can&#39;t be gamed is very
      unconvincing. You need to lay out a miles long case for why it
      cannot be gamed. And to what end? #98 has a simple piece of text
      that should be added to DMARC to eliminate the possibility of
      forgery. You&#39;d need a 10 page threat I-D to explain why it&#39;s =
not
      necessary. What is the point of that? For email, it&#39;s trivial to
      prevent forgeries. Why would anybody argue against that?</p>
    <p>Mike<br>
    </p>
  </div>

_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/dmarc</a><br>
</blockquote></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--0000000000000e960c05b9bcbd9d--


From nobody Mon Jan 25 09:20:07 2021
Return-Path: <superuser@gmail.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 8B2943A0E61 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9p4iRfRBVVCF for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:20:03 -0800 (PST)
Received: from mail-vk1-xa2b.google.com (mail-vk1-xa2b.google.com [IPv6:2607:f8b0:4864:20::a2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFDD13A15C7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:20:02 -0800 (PST)
Received: by mail-vk1-xa2b.google.com with SMTP id e1so2171040vkd.10 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:20:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RCzr+hi9P/s5nuwFYyfcxKkBWYM+ebei/C5j66jMV0o=; b=RwxDadPARzzt8shsLKlHlrSeyxhYdhm5xLPrGj8vPC2V9hkZKAAOssq6FRqEVbqe36 4j9wD9MlMtpVOykyoUouS+sMc7hmaekPKLeNI0MfiwKFONr0EwHYT0/zH0Ss7dIwLBro NSKUv6y1ak9bP+zSKmO/i1RZ/vclNWhGBU5T9q5AhK5d48sRNQ87jjtVaKRC+X1FkAI6 1ViyINC8WoEgjPNVA1iXab2wp8sCp6w8kU1A4Sxw6D7eU8sodmTar5RMIl8/nbguvT5H DmyHtpPrAzeH5brCPbTtLW+FFTW6opauZc0p75P11uz9MfNolG2AF/P57pnM9LhFeu4Z fzeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RCzr+hi9P/s5nuwFYyfcxKkBWYM+ebei/C5j66jMV0o=; b=hiDZi+pVPhXtRVGTv6ZDIS5Hufg4bvDdB/EQ8zS2MkrqpVNi61jtB34J0Fq7gSCfuo rntCydsAeK8PWvslF3BlYVDXGKkwo/q4wNG2vs+nDGPfd4KtxWIJ7smsRRQa0GxX+MeD GHe3AiI+0vbXNR3WRAqFkoajZSymN0IkfWxPcOjguUyfpzg2AQxPvav8I+fvH8ckrtMr HEfj4icrw2gSpN9izE8Nen+/6AVVtX68iCdRuUL2dLrKKilZOBOTo7fCBqkI/ifakynH I7/qMb8wMXPPiCfqOUxVaZgX92IlkopP4oeKJi8ewx+DrdWB87K0hFw0UQvDCWNjLKIp duhA==
X-Gm-Message-State: AOAM53230FN/Dx3l++0IhaPAic+q6vj5v3E0ve/rctHQfIJ3PUP6YhGJ asYBWeQFCvWObr3hFiLnGneu5Jdq1nUJMzyRfnBezvB7w48=
X-Google-Smtp-Source: ABdhPJz4j1ZpGq1+q7Z5AZOWEmq6bOaszXulb88OzaxIdD/BHtY6FpfPmOmMmMpphKqB8rEv8toz1hmJVd7jQ0t5nOI=
X-Received: by 2002:ac5:c3d0:: with SMTP id t16mr1555646vkk.5.1611595201835; Mon, 25 Jan 2021 09:20:01 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 25 Jan 2021 09:19:50 -0800
Message-ID: <CAL0qLwYHsZuOAi+ewvaXc_upXAMQ_eGwpw3VgxsnUsrqCYTNdw@mail.gmail.com>
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000086f74d05b9bcbf53"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/b8_r_IKkOfX72o41sf6j7aV_iBU>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 17:20:05 -0000

--00000000000086f74d05b9bcbf53
Content-Type: text/plain; charset="UTF-8"

On Sun, Jan 24, 2021 at 4:25 PM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Some time ago, an issue[1] was brought to the list where which DKIM(s)
> being reported is not clear in RFC7489 [2].  There was a short discussion,
> though no clear resolution before conversation trailed off.  It seems like
> there were points that may need to be discussed.  One was whether the
> reporting SHOULD report all signatures, regardless of alignment or
> validity, or perhaps just the one that aligns (if there is one).  There was
> also another question if there should be a limit to the number of
> signatures reported so that it remains sane.
>

A warning about use of "SHOULD" (or "RECOMMENDED") with respect to
protocols: Text saying "implementers SHOULD do foobar" presents the
implementer with a choice.  If you're going to say that, you need to
explain the choice; in particular, an implementer should have some idea of
the circumstances under which she might legitimately not do what it says
and what the implications of doing so are with respect to interoperability.

A bare SHOULD, meant to be hand-wavy like "you really ought to do this, but
you don't actually have to if you don't want to" is likely to draw
attention.  I've been kind of picky about this lately during IESG
Evaluation.

In this case, "reporting SHOULD report all signatures" -- why would you not?

-MSK

--00000000000086f74d05b9bcbf53
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, Jan 24, 2021 at 4:25 PM Brotman, =
Alex &lt;Alex_Brotman=3D<a href=3D"mailto:40comcast.com@dmarc.ietf.org">40c=
omcast.com@dmarc.ietf.org</a>&gt; wrote:<br></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">Some time ago, an issue=
[1] was brought to the list where which DKIM(s) being reported is not clear=
 in RFC7489 [2].=C2=A0 There was a short discussion, though no clear resolu=
tion before conversation trailed off.=C2=A0 It seems like there were points=
 that may need to be discussed.=C2=A0 One was whether the reporting SHOULD =
report all signatures, regardless of alignment or validity, or perhaps just=
 the one that aligns (if there is one).=C2=A0 There was also another questi=
on if there should be a limit to the number of signatures reported so that =
it remains sane.<br></blockquote><div><br></div>A warning about use of &quo=
t;SHOULD&quot; (or &quot;RECOMMENDED&quot;) with respect to protocols: Text=
 saying &quot;implementers SHOULD do foobar&quot; presents the implementer =
with a choice.=C2=A0 If you&#39;re going to say that, you need to explain t=
he choice; in particular, an implementer should have some idea of the circu=
mstances under which she might legitimately not do what it says and what th=
e implications of doing so are with respect to interoperability.<div><br></=
div><div>A bare SHOULD, meant to be hand-wavy like &quot;you really ought t=
o do this, but you don&#39;t actually have to if you don&#39;t want to&quot=
; is likely to draw attention.=C2=A0 I&#39;ve been kind of picky about this=
 lately during IESG Evaluation.</div><div><br></div><div>In this case, &quo=
t;reporting SHOULD report all signatures&quot; -- why would you not?<br></d=
iv><div><br></div><div>-MSK<br></div></div></div>

--00000000000086f74d05b9bcbf53--


From nobody Mon Jan 25 09:22:16 2021
Return-Path: <seth@valimail.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 777913A15C7 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:22:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 R4pdBRM9UJS1 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:22:11 -0800 (PST)
Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 904583A15C8 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:22:11 -0800 (PST)
Received: by mail-vs1-xe2d.google.com with SMTP id m13so2443813vsr.2 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:22:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k0y3a5EC/CS8XmHXFm3mbzKASgYksui1yt3NayjzGYM=; b=O/ggIzLoTneFSj4Babq4OTIGgV8tif/0rz1T97gTktiG8Vp6Yb9UgqInpnzTC+3egQ MiHyU8ZlaiKKwDT9GoayDs+gOYxRLC7npnqB7FiGsz/SThsdQ6+46kNDgxfFOkJCKkT/ BxnxD1py23GgZALsNMQSEu2HSHHmdZ2y4xMJy9+RaIGhs10OMQrhdbK3miaNtUZPVWtx qLsrt09Q9xyhtPcZjH7Pa1sDBuYabkTF5Vg12ff3V7Bl8TQJtEQ+lKbfHfU34LDPaBXR aYfQummexucLRDbNxK2jFjOk67XZ3VcmzGfn97G377Z7eS0EqSBvQTnQCx5EN8D/8p07 9ing==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k0y3a5EC/CS8XmHXFm3mbzKASgYksui1yt3NayjzGYM=; b=hm+OgW1xxHxra+ZIF30KDf3Bx3kxjkVe9YO3hMrD6o/oZhg2YPVcmb2YmG2WsD2ELO 1d8PDMWFPo9KDefDKMwtyyzkL3lJ3NszPl/fDTyWUXh7g4KgfGQ/0c2y3QACPc/+Tm8r afhrGtEKvVXn9b2bNxs8wCjiMJpCqockIoemz+Ir4uKvZ3/USjHjnflv7ipGTQIK+7KX YsFOlUFA+m5Q3yBpAoYDDWBuF+PV+rBawHtqisMKOADSgb802ZekFzasMObLsQm5OHnO 0J/ArT+xsLj2IemClrcnvYlGJk33D3naZe9ac2FiERbutbocODXHEl65qKILayj6FSA7 jbWw==
X-Gm-Message-State: AOAM532bYAPj+9eixU2JU5ETNlol+4M+bHl2zZYwtOzSsiYAaIQoEBQt N5XVZFmy3AgSBy1lWfGSIU64QgbR8zf+yQQZgDsV2OuRlv8=
X-Google-Smtp-Source: ABdhPJwscdqP4KuJ1FkOhZmllKVzB7R2mcnV1xcTjKVdpxztZgPT21E1QrB6X3zlwGWU6nJrkNe84zmvE2XNbV83miQ=
X-Received: by 2002:a05:6102:22da:: with SMTP id a26mr1550870vsh.56.1611595330327;  Mon, 25 Jan 2021 09:22:10 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <ff074ea6-19a8-e152-a775-4bbb1b94d93f@mtcc.com>
In-Reply-To: <ff074ea6-19a8-e152-a775-4bbb1b94d93f@mtcc.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 25 Jan 2021 09:21:59 -0800
Message-ID: <CAOZAAfPawUx5QVLS0inH5SqaGEYCgaQghknwWYiPQexYBgLVhA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Cc: Michael Thomas <mike@mtcc.com>
Content-Type: multipart/alternative; boundary="0000000000002fa0f705b9bcc710"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/s5Sb19YqvFplNDDlZ6UThZak5og>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:22:14 -0000

--0000000000002fa0f705b9bcc710
Content-Type: text/plain; charset="UTF-8"

Mike, this comment is unproductive and false.

It is well known that bad actors are the first and heartiest adopters of
authentication. This has been discussed with ample evidence for years. We
are not litigating this fact on this list.

Please stick to the merits of the discussion and bring operational evidence
to support your concern, or let's move on to another ticket.

Seth, as Chair

On Sun, Jan 24, 2021 at 6:57 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/24/21 6:29 PM, John R. Levine wrote:
> >
> > As we all know, bad guys are at least as good at authentication as
> > good guys, probably better.
>
>
> PS: if this were true, DKIM would be useless too.
>
> Mike
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000002fa0f705b9bcc710
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Mike, this comment is unproductive and false.<div><br></di=
v><div>It is well known that bad actors are the first and heartiest adopter=
s of authentication. This has been discussed with ample evidence for years.=
 We are not litigating this fact on this list.</div><div><br></div><div>Ple=
ase stick to the merits of the discussion and bring operational evidence to=
 support your concern, or let&#39;s move on to another ticket.</div><div><b=
r></div><div>Seth, as Chair</div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Sun, Jan 24, 2021 at 6:57 PM Michael Th=
omas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On 1/24/21 6:29 PM, John R. Levine wrote:<br>
&gt;<br>
&gt; As we all know, bad guys are at least as good at authentication as <br=
>
&gt; good guys, probably better.<br>
<br>
<br>
PS: if this were true, DKIM would be useless too.<br>
<br>
Mike<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--0000000000002fa0f705b9bcc710--


From nobody Mon Jan 25 09:22:38 2021
Return-Path: <mike@fresheez.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 B294F3A15C4 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 9qSLdIksfsRr for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:22:32 -0800 (PST)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E65B3A15C6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:22:29 -0800 (PST)
Received: by mail-pj1-x102f.google.com with SMTP id j12so8807812pjy.5 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:22:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=0LS4pTj4o50sqlVIdi4GnvCEwdSBh6mxUNN0/iIpZss=; b=a9AWiay+EPruvb7MQ/2FT0BiTAMSr7oWqbxpvxrn1JY0Uyi+FbYhcvTq5L4vhYHBxZ /p/SewMqQr2EhLJT3v/wt14Vf7n1fun/AMtLUFG3Af3Xra3X9NkMFqOEmuSgSoOq6OM1 IWfQafhF5oYGOuYTZ69Yv5vFViz1dgBh0EO4n/z+ux/phZ7Z0zEXoiVXyiGNzIAqXAVo lom62bWFk+M21bQenfc9zPT+TbACLq2TC19ejoRPSbN+7Cu54AKGCcTL6GHCBMYt36n7 8gcA8m7hCSjjA6M+wwHqRYAEopPGXEM/JUB1ubBkd/ovqklD9x5z7u1mEX0a7Vwj+rUj cLJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=0LS4pTj4o50sqlVIdi4GnvCEwdSBh6mxUNN0/iIpZss=; b=HqjiKHv59r51B++6k3V1LeM4lY0Bf1ugZf+igAe6qPiVCg2fLrHpk1cBqDPYh16T0e 0HkuX66YSFYzU0R3IWC16l83wBJXtEkqMAggRcQ0QUxIc3cPniEFXlApDgQBgWZRRki6 vZPqF9J42bw6A9Hf6EkaLdP2Jw3t7p7Be+acfF+Bd8VhEPPtVKBbH1hzmfB6tSv4+Jom zHsoTFDchPQRFSxvf3GS8sCga0HZxuC0W2WW+VfFjyQQR2S57fGfWkLoUojK+ernVas4 K6b/++r+ZfVXXIPfFOKkSoyXC//8QD9QzPwKdx+egMi905JQae6qxC7wMYC+DA+hIfQm IIiw==
X-Gm-Message-State: AOAM530PS9THOHBYQuHC+ohppm/edznLpNmgfVYCrQ5sVcM6s4RZndm5 A5oZReVy19LPqK2xdZG1Z3RH+Q==
X-Google-Smtp-Source: ABdhPJxoe79Xy/wG+FA8GO4Dquhq/DERdzIEk0pR5B/fXEPcAdbpEZmDY99r5jIvp8kESadPydWysA==
X-Received: by 2002:a17:902:9b90:b029:e0:6c0:df4f with SMTP id y16-20020a1709029b90b02900e006c0df4fmr1705536plp.60.1611595349281;  Mon, 25 Jan 2021 09:22:29 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id w66sm17160980pfd.48.2021.01.25.09.22.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 09:22:28 -0800 (PST)
To: Seth Blank <seth@valimail.com>, IETF DMARC WG <dmarc@ietf.org>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com>
Date: Mon, 25 Jan 2021 09:22:27 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8E3CC247D68B014F6C3E8E13"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/fAmw7gy6AnXkts-f7N9H5I2wbOM>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:22:34 -0000

This is a multi-part message in MIME format.
--------------8E3CC247D68B014F6C3E8E13
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Taking in information from unauthenticated sources and acting on it is 
an operational problem per se. Have we learned nothing in the last 30 years?

Mike

On 1/25/21 9:19 AM, Seth Blank wrote:
> What operational problem are we solving here? Absent evidence of a 
> problem and strong consensus on the solution, let's close these 
> tickets and move on.
>
> On Mon, Jan 25, 2021 at 9:10 AM Douglas Foster 
> <dougfoster.emailstandards@gmail.com 
> <mailto:dougfoster.emailstandards@gmail.com>> wrote:
>
>     Since the status quo is unauthenticated, I wonder if adding a
>     signing requirement will help.
>     Will recipients discad unsigned messages, or accept whatever is
>     available to maximize their information capture?  I suspect they
>     will conrinye to accept everything.
>
>     I think we would need an identified threat before recipients would
>     be motivated to discard.
>
>     But what about John's problems with receiving reports that should
>     not have gone to him?   I did not understand the root cause, but I
>     would hope there is something that can be done.  Would signing
>     help receiving sites, those with less sophistication than he has,
>     be able to sort out noise more effectively?
>
>
>     On Mon, Jan 25, 2021, 11:51 AM Michael Thomas <mike@mtcc.com
>     <mailto:mike@mtcc.com>> wrote:
>
>
>         On 1/25/21 8:44 AM, Todd Herr wrote:
>>         On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas
>>         <mike@mtcc.com <mailto:mike@mtcc.com>> wrote:
>>
>>
>>             The main thing I've learned over the years of dealing
>>             with security is to not underestimate what a motivated
>>             attacker can do. Your imagination is not the same as
>>             their imagination. Closing #98 in particular is
>>             absolutely ridiculous: the report should already have a
>>             DKIM signature or SPF so it's just a matter of making
>>             sure its valid. Why would you *not* want to insure that?
>>             The amount of justification for *not* having the receiver
>>             authenticate it is a mountain. The amount of effort to
>>             authenticate it is trivial for mail. Levine's dismissal
>>             of security concerns because he has anecdotal "evidence"
>>             from a backwater domain carries no weight at all.
>>
>>
>>         That's all well and good, but you haven't answered the
>>         question I asked.
>>
>>         What threats do you have in mind? Put another way, how do you
>>         envision an attacker exploiting the lack of authentication in
>>         a DMARC report to his or her gain?
>>
>         No, sorry, the onus is on the people who don't think it can be
>         gamed. A bald assertion that it can't be gamed is very
>         unconvincing. You need to lay out a miles long case for why it
>         cannot be gamed. And to what end? #98 has a simple piece of
>         text that should be added to DMARC to eliminate the
>         possibility of forgery. You'd need a 10 page threat I-D to
>         explain why it's not necessary. What is the point of that? For
>         email, it's trivial to prevent forgeries. Why would anybody
>         argue against that?
>
>         Mike
>
>         _______________________________________________
>         dmarc mailing list
>         dmarc@ietf.org <mailto:dmarc@ietf.org>
>         https://www.ietf.org/mailman/listinfo/dmarc
>         <https://www.ietf.org/mailman/listinfo/dmarc>
>
>     _______________________________________________
>     dmarc mailing list
>     dmarc@ietf.org <mailto:dmarc@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dmarc
>     <https://www.ietf.org/mailman/listinfo/dmarc>
>
>
>
> -- 
> *Seth Blank*| VP, Standards and New Technologies
> *e:*seth@valimail.com <mailto:seth@valimail.com>
> *p:*415.273.8818
>
>
> This email and all data transmitted with it contains confidential 
> and/or proprietary information intended solely for the use of 
> individual(s) authorized to receive it. If you are not an intended and 
> authorized recipient you are hereby notified of any use, disclosure, 
> copying or distribution of the information included in this 
> transmission is prohibited and may be unlawful. Please immediately 
> notify the sender by replying to this email and then delete it from 
> your system.
>

--------------8E3CC247D68B014F6C3E8E13
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Taking in information from unauthenticated sources and acting on
      it is an operational problem per se. Have we learned nothing in
      the last 30 years?</p>
    <p>Mike<br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 9:19 AM, Seth Blank wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">What operational problem are we solving
        here? Absent evidence of a problem and strong consensus on the
        solution, let's close these tickets and move on.</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021 at 9:10
          AM Douglas Foster &lt;<a
            href="mailto:dougfoster.emailstandards@gmail.com"
            moz-do-not-send="true">dougfoster.emailstandards@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir="auto">Since the status quo is unauthenticated, I
            wonder if adding a signing requirement will help.
            <div dir="auto">Will recipients discad unsigned messages, or
              accept whatever is available to maximize their information
              capture?  I suspect they will conrinye to accept
              everything.</div>
            <div dir="auto"><br>
            </div>
            <div dir="auto">I think we would need an identified threat
              before recipients would be motivated to discard.</div>
            <div dir="auto"><br>
            </div>
            <div dir="auto">But what about John's problems with
              receiving reports that should not have gone to him?   I
              did not understand the root cause, but I would hope there
              is something that can be done.  Would signing help
              receiving sites, those with less sophistication than he
              has, be able to sort out noise more effectively?</div>
            <div dir="auto"><br>
            </div>
          </div>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021,
              11:51 AM Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
                rel="noreferrer" target="_blank" moz-do-not-send="true">mike@mtcc.com</a>&gt;
              wrote:<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div>
                <p><br>
                </p>
                <div>On 1/25/21 8:44 AM, Todd Herr wrote:<br>
                </div>
                <blockquote type="cite">
                  <div dir="ltr">
                    <div dir="ltr">On Mon, Jan 25, 2021 at 10:18 AM
                      Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
                        rel="noreferrer noreferrer" target="_blank"
                        moz-do-not-send="true">mike@mtcc.com</a>&gt;
                      wrote:<br>
                    </div>
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px 0.8ex;border-left:1px solid
                        rgb(204,204,204);padding-left:1ex">
                        <div><br>
                          <p>The main thing I've learned over the years
                            of dealing with security is to not
                            underestimate what a motivated attacker can
                            do. Your imagination is not the same as
                            their imagination. Closing #98 in particular
                            is absolutely ridiculous: the report should
                            already have a DKIM signature or SPF so it's
                            just a matter of making sure its valid. Why
                            would you *not* want to insure that? The
                            amount of justification for *not* having the
                            receiver authenticate it is a mountain. The
                            amount of effort to authenticate it is
                            trivial for mail. Levine's dismissal of
                            security concerns because he has anecdotal
                            "evidence" from a backwater domain carries
                            no weight at all.</p>
                        </div>
                      </blockquote>
                      <div><br>
                      </div>
                      <div>That's all well and good, but you haven't
                        answered the question I asked.</div>
                      <div><br>
                      </div>
                      <div>What threats do you have in mind? Put another
                        way, how do you envision an attacker exploiting
                        the lack of authentication in a DMARC report to
                        his or her gain?</div>
                      <br>
                    </div>
                  </div>
                </blockquote>
                <p>No, sorry, the onus is on the people who don't think
                  it can be gamed. A bald assertion that it can't be
                  gamed is very unconvincing. You need to lay out a
                  miles long case for why it cannot be gamed. And to
                  what end? #98 has a simple piece of text that should
                  be added to DMARC to eliminate the possibility of
                  forgery. You'd need a 10 page threat I-D to explain
                  why it's not necessary. What is the point of that? For
                  email, it's trivial to prevent forgeries. Why would
                  anybody argue against that?</p>
                <p>Mike<br>
                </p>
              </div>
              _______________________________________________<br>
              dmarc mailing list<br>
              <a href="mailto:dmarc@ietf.org" rel="noreferrer
                noreferrer" target="_blank" moz-do-not-send="true">dmarc@ietf.org</a><br>
              <a href="https://www.ietf.org/mailman/listinfo/dmarc"
                rel="noreferrer noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
            </blockquote>
          </div>
          _______________________________________________<br>
          dmarc mailing list<br>
          <a href="mailto:dmarc@ietf.org" target="_blank"
            moz-do-not-send="true">dmarc@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/dmarc"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"><span>
          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
          </span>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
        </span></div>
    </blockquote>
  </body>
</html>

--------------8E3CC247D68B014F6C3E8E13--


From nobody Mon Jan 25 09:25:31 2021
Return-Path: <seth@valimail.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 60E3B3A15CC for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 7dJLjKviuvPb for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:25:26 -0800 (PST)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A6B03A15C8 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:25:26 -0800 (PST)
Received: by mail-ua1-x92a.google.com with SMTP id v23so4686042uam.8 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:25:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2L1vDtPQxSx58chs6n33NgK7yyF/VFzPYbjzjP/vDn4=; b=Rl7C2DXuVTRszMUGDp8ZH3jaerRcTb5+EV5mmLE9pcWmIyHRdY3ExKyMxoTNTCBCPB ZjtKXGupcZ/s6KCTWODxVHDuDhpQXNtl/vsBKFeEZSFnmOL+RV9o/hU7uQmlfhil8jG5 V6BqXKAqUpHC+FJ83Fe9wQt0jZihuXH+nNsCughsLu7l0+k5iScenBdxA/3ZTNiqG40/ xu5Is3VuWaTINYUyX/FiMFUX8WN6spXm267eRQrmZeD0ZJy8E4dWay2bsDbZNQ+BhnEb 9HnWtAbV596BhLyt31CiT8J6+xkTMNtbKDbdDyjGLRTXGSojZ218H+amJqoXCyvT84sV 5QyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2L1vDtPQxSx58chs6n33NgK7yyF/VFzPYbjzjP/vDn4=; b=F0vGuwSxzktubafK41TqV5x9Y9XLd9SuzgHQd+Mm8OYnndwVJumPXRmEC/yWaiPBk/ 0lrD5P5+5UrZ3FvtOWIUxQSvxXZDco4fZxwTchDtW9/b9V+YPzMkX3qI4pUWj+zY8RRy qyjNjdbHZWcW5qJ+U5mz+ThqhPWF6MwKu8hxBBvwDfKHOvF/XBuDgcq5Sxe+6UiXY531 e/FpPXpFdEmtwllhLgFImdXSPqdSXJnlBdIAt75ZWKnlrNRDBFqfFbZcUQ2fFcwHH3Cv HWAZ0i17+c9P/DZunH8G2gFDSoHg0KqLDtQkhOIQ8b8kclgcwVuIx3gyOGLlr+hi5kL8 SPuw==
X-Gm-Message-State: AOAM533rbOlw1COOinkiS0xWBuum5j0CybL3lPCDBvSxrU2ypVwVF2Us mV6uyJTuYIyIsqHa9BWIXdcObBHQb17yK3ZeWSESUg==
X-Google-Smtp-Source: ABdhPJyV4aeNJDfceY1awyca5dDXlhLM/oUJQMWSBPiNeUtKguaReyF2yjFDqeObeLuWKNQ9uui8fYBzTy9mjCb+W70=
X-Received: by 2002:ab0:3043:: with SMTP id x3mr1413545ual.88.1611595525056; Mon, 25 Jan 2021 09:25:25 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com>
In-Reply-To: <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 25 Jan 2021 09:25:14 -0800
Message-ID: <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, Douglas Foster <dougfoster.emailstandards@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000caf63f05b9bcd2f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/kb1pil97QlQXHA1m4IO2Ry27T0Q>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:25:28 -0000

--000000000000caf63f05b9bcd2f2
Content-Type: text/plain; charset="UTF-8"

Mike, how do you believe DMARC reports are consumed and utilized? I think
you have a misunderstanding here which is why you're going down this path
and everyone else is pushing back.

On Mon, Jan 25, 2021 at 9:22 AM Michael Thomas <mike@mtcc.com> wrote:

> Taking in information from unauthenticated sources and acting on it is an
> operational problem per se. Have we learned nothing in the last 30 years?
>
> Mike
> On 1/25/21 9:19 AM, Seth Blank wrote:
>
> What operational problem are we solving here? Absent evidence of a problem
> and strong consensus on the solution, let's close these tickets and move on.
>
> On Mon, Jan 25, 2021 at 9:10 AM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> Since the status quo is unauthenticated, I wonder if adding a signing
>> requirement will help.
>> Will recipients discad unsigned messages, or accept whatever is available
>> to maximize their information capture?  I suspect they will conrinye to
>> accept everything.
>>
>> I think we would need an identified threat before recipients would be
>> motivated to discard.
>>
>> But what about John's problems with receiving reports that should not
>> have gone to him?   I did not understand the root cause, but I would hope
>> there is something that can be done.  Would signing help receiving sites,
>> those with less sophistication than he has, be able to sort out noise more
>> effectively?
>>
>>
>> On Mon, Jan 25, 2021, 11:51 AM Michael Thomas <mike@mtcc.com> wrote:
>>
>>>
>>> On 1/25/21 8:44 AM, Todd Herr wrote:
>>>
>>> On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas <mike@mtcc.com> wrote:
>>>
>>>>
>>>> The main thing I've learned over the years of dealing with security is
>>>> to not underestimate what a motivated attacker can do. Your imagination is
>>>> not the same as their imagination. Closing #98 in particular is absolutely
>>>> ridiculous: the report should already have a DKIM signature or SPF so it's
>>>> just a matter of making sure its valid. Why would you *not* want to insure
>>>> that? The amount of justification for *not* having the receiver
>>>> authenticate it is a mountain. The amount of effort to authenticate it is
>>>> trivial for mail. Levine's dismissal of security concerns because he has
>>>> anecdotal "evidence" from a backwater domain carries no weight at all.
>>>>
>>>
>>> That's all well and good, but you haven't answered the question I asked.
>>>
>>> What threats do you have in mind? Put another way, how do you envision
>>> an attacker exploiting the lack of authentication in a DMARC report to his
>>> or her gain?
>>>
>>> No, sorry, the onus is on the people who don't think it can be gamed. A
>>> bald assertion that it can't be gamed is very unconvincing. You need to lay
>>> out a miles long case for why it cannot be gamed. And to what end? #98 has
>>> a simple piece of text that should be added to DMARC to eliminate the
>>> possibility of forgery. You'd need a 10 page threat I-D to explain why it's
>>> not necessary. What is the point of that? For email, it's trivial to
>>> prevent forgeries. Why would anybody argue against that?
>>>
>>> Mike
>>> _______________________________________________
>>> dmarc mailing list
>>> dmarc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dmarc
>>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>
>
> --
> *Seth Blank* | VP, Standards and New Technologies
> *e:* seth@valimail.com
> *p:* 415.273.8818
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
>
>

-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000caf63f05b9bcd2f2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Mike, how do you believe DMARC reports are consumed and ut=
ilized? I think you have a misunderstanding here which is why you&#39;re go=
ing down this path and everyone else is pushing back.</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021=
 at 9:22 AM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
 =20
   =20
 =20
  <div>
    <p>Taking in information from unauthenticated sources and acting on
      it is an operational problem per se. Have we learned nothing in
      the last 30 years?</p>
    <p>Mike<br>
    </p>
    <div>On 1/25/21 9:19 AM, Seth Blank wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">What operational problem are we solving
        here?=C2=A0Absent evidence of a problem and strong consensus on the
        solution, let&#39;s close these tickets and move on.</div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 9:10
          AM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailstandards=
@gmail.com" target=3D"_blank">dougfoster.emailstandards@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir=3D"auto">Since the status quo is unauthenticated, I
            wonder if adding a signing requirement will help.
            <div dir=3D"auto">Will recipients discad unsigned messages, or
              accept whatever is available to maximize their information
              capture?=C2=A0 I suspect they will conrinye to accept
              everything.</div>
            <div dir=3D"auto"><br>
            </div>
            <div dir=3D"auto">I think we would need an identified threat
              before recipients would be motivated to discard.</div>
            <div dir=3D"auto"><br>
            </div>
            <div dir=3D"auto">But what about John&#39;s problems with
              receiving reports that should not have gone to him?=C2=A0 =C2=
=A0I
              did not understand the root cause, but I would hope there
              is something that can be done.=C2=A0 Would signing help
              receiving sites, those with less sophistication than he
              has, be able to sort out noise more effectively?</div>
            <div dir=3D"auto"><br>
            </div>
          </div>
          <br>
          <div class=3D"gmail_quote">
            <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021,
              11:51 AM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com" =
rel=3D"noreferrer" target=3D"_blank">mike@mtcc.com</a>&gt;
              wrote:<br>
            </div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
              <div>
                <p><br>
                </p>
                <div>On 1/25/21 8:44 AM, Todd Herr wrote:<br>
                </div>
                <blockquote type=3D"cite">
                  <div dir=3D"ltr">
                    <div dir=3D"ltr">On Mon, Jan 25, 2021 at 10:18 AM
                      Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com" r=
el=3D"noreferrer noreferrer" target=3D"_blank">mike@mtcc.com</a>&gt;
                      wrote:<br>
                    </div>
                    <div class=3D"gmail_quote">
                      <blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                        <div><br>
                          <p>The main thing I&#39;ve learned over the years
                            of dealing with security is to not
                            underestimate what a motivated attacker can
                            do. Your imagination is not the same as
                            their imagination. Closing #98 in particular
                            is absolutely ridiculous: the report should
                            already have a DKIM signature or SPF so it&#39;=
s
                            just a matter of making sure its valid. Why
                            would you *not* want to insure that? The
                            amount of justification for *not* having the
                            receiver authenticate it is a mountain. The
                            amount of effort to authenticate it is
                            trivial for mail. Levine&#39;s dismissal of
                            security concerns because he has anecdotal
                            &quot;evidence&quot; from a backwater domain ca=
rries
                            no weight at all.</p>
                        </div>
                      </blockquote>
                      <div><br>
                      </div>
                      <div>That&#39;s all well and good, but you haven&#39;=
t
                        answered the question I asked.</div>
                      <div><br>
                      </div>
                      <div>What threats do you have in mind? Put another
                        way, how do you envision an attacker exploiting
                        the lack of authentication in a DMARC report to
                        his or her gain?</div>
                      <br>
                    </div>
                  </div>
                </blockquote>
                <p>No, sorry, the onus is on the people who don&#39;t think
                  it can be gamed. A bald assertion that it can&#39;t be
                  gamed is very unconvincing. You need to lay out a
                  miles long case for why it cannot be gamed. And to
                  what end? #98 has a simple piece of text that should
                  be added to DMARC to eliminate the possibility of
                  forgery. You&#39;d need a 10 page threat I-D to explain
                  why it&#39;s not necessary. What is the point of that? Fo=
r
                  email, it&#39;s trivial to prevent forgeries. Why would
                  anybody argue against that?</p>
                <p>Mike<br>
                </p>
              </div>
              _______________________________________________<br>
              dmarc mailing list<br>
              <a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer
                noreferrer" target=3D"_blank">dmarc@ietf.org</a><br>
              <a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=
=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://www.ietf.or=
g/mailman/listinfo/dmarc</a><br>
            </blockquote>
          </div>
          _______________________________________________<br>
          dmarc mailing list<br>
          <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.or=
g</a><br>
          <a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a>=
<br>
        </blockquote>
      </div>
      <br clear=3D"all">
      <div><br>
      </div>
      -- <br>
      <div dir=3D"ltr"><span>
          <div style=3D"text-align:left"><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank<=
/b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"> | VP, Standards and New Technologies</span><=
/div>
          <span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D=
"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:bas=
eline"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank">seth@valimai=
l.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></s=
pan></div>
          </span>
          <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;f=
ont-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-ali=
gn:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent=
.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSX=
prAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=
=3D"border: none; height: 40px; width: 177px;"></span></p>
          <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><font face=3D"Arial" color=3D"#=
666666"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email=
 and all data transmitted with it contains confidential and/or proprietary =
information intended solely for the use of individual(s) authorized to rece=
ive it. If you are not an intended and authorized recipient you are hereby =
notified of any use, disclosure, copying or distribution of the information=
 included in this transmission is prohibited and may be unlawful. Please im=
mediately notify the sender by replying to this email and then delete it fr=
om your system.</span></font></p>
        </span></div>
    </blockquote>
  </div>

</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--000000000000caf63f05b9bcd2f2--


From nobody Mon Jan 25 09:32:08 2021
Return-Path: <mike@fresheez.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 C68F03A15D9 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:32:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 mL0ifsAuwGTa for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:32:04 -0800 (PST)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CEEE3A15D6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:32:04 -0800 (PST)
Received: by mail-pj1-x1029.google.com with SMTP id e9so16126pjj.0 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:32:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=mjfqRLCQ32gcNPiR7cLVIJaULtdCOPBt7f+Niirz/K4=; b=jlFgf93SETyG3Kcp/QgcxA++8E+3Se7WpnY5N8G6YLh9lP8tO55OaO5gL3tVr/+MXG rqT8jsuBehczBTW0qp2OWLCgR9ocl+tfhAQwfIhFpN4hqFKCQenEGTvUe2Yfnfqt6RTy gxUtR9v0W4XjM7ZgfElG1n8xa2quMtzHSBir6lK8aesfYJUjb/UfRvGjA2UV9fSIFafk vQhFs1VrbG2S4g6Kig7G32ar55CoW3/HT4142FKuS1Kf7OdEZMgUJPcdxz06VkNOJ7iR F3q15bo7qb9U4ArTApx5RhpQIgcnCyBQ67ggX7pC1Y0F2mPexrdQKyA2nLhGCGebHeqg sb7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=mjfqRLCQ32gcNPiR7cLVIJaULtdCOPBt7f+Niirz/K4=; b=n7/1GhfNoLLHnRojM1qIYCwc3jtbOJplaBw5ZRqQjHTWwZVo7B3KSV3Yuf+QitvbB3 VC/8rNd7532tut48juIa2IKiRl8jOUBOFcQPdoK3t/dJ9SMd1GwzTsLgBpHUfBI0WRsg 7lmEQNqTTjUE1SB44zWqyYM2gJfMAaQVKKQ9tlgKoY/OBVrlsw8tZqvNpxypgb/2y6mv SOu5rhUS+uItTbS2ml2RVuGJbNqHm/KoTm9e9lN879zf2Hv5pZ8C1d/KZ2pvK9De3Gas u/OBTVWXzFDLbva+bHSEzF8EVoyyixnWKPokfmdTDiXsuIK5cSRUg3aVi0bXb6V7O4re 2k9g==
X-Gm-Message-State: AOAM5311bRmYQjFpf3kBKjJC1j5Vy6DqXr5TcgekE9tqXNGx4Q+iFn3t RgooVOdsaEKXzAiE/9128mRfDU/ap9bHxA==
X-Google-Smtp-Source: ABdhPJw0J1KFoMYNHt6mOoer7STK/ilTVHVPfTIAfnP4frPhPiRdCqoxye5d7/W5yqt3baWNTPuClg==
X-Received: by 2002:a17:90a:9414:: with SMTP id r20mr1260206pjo.222.1611595923936;  Mon, 25 Jan 2021 09:32:03 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id s24sm4766641pfd.118.2021.01.25.09.32.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 09:32:03 -0800 (PST)
To: Seth Blank <seth@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, Douglas Foster <dougfoster.emailstandards@gmail.com>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com>
Date: Mon, 25 Jan 2021 09:32:01 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------34AE3435089922E4931EC1B0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/dpgc7eBR5g1RV7CFPPz-KnQk5vk>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:32:07 -0000

This is a multi-part message in MIME format.
--------------34AE3435089922E4931EC1B0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Why is this controversial? Seriously. What is controversial about saying 
that the a report should authenticate? The onus is on the people who say 
it does not to lay out the case for why it's not a problem, not me. #98 
has a simple piece of text to remedy this. it's 2021. You don't use 
unauthenticated data if you can possibly help it.

Mike

On 1/25/21 9:25 AM, Seth Blank wrote:
> Mike, how do you believe DMARC reports are consumed and utilized? I 
> think you have a misunderstanding here which is why you're going down 
> this path and everyone else is pushing back.
>
> On Mon, Jan 25, 2021 at 9:22 AM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>     Taking in information from unauthenticated sources and acting on
>     it is an operational problem per se. Have we learned nothing in
>     the last 30 years?
>
>     Mike
>
>     On 1/25/21 9:19 AM, Seth Blank wrote:
>>     What operational problem are we solving here? Absent evidence of
>>     a problem and strong consensus on the solution, let's close these
>>     tickets and move on.
>>
>>     On Mon, Jan 25, 2021 at 9:10 AM Douglas Foster
>>     <dougfoster.emailstandards@gmail.com
>>     <mailto:dougfoster.emailstandards@gmail.com>> wrote:
>>
>>         Since the status quo is unauthenticated, I wonder if adding a
>>         signing requirement will help.
>>         Will recipients discad unsigned messages, or accept whatever
>>         is available to maximize their information capture?  I
>>         suspect they will conrinye to accept everything.
>>
>>         I think we would need an identified threat before recipients
>>         would be motivated to discard.
>>
>>         But what about John's problems with receiving reports that
>>         should not have gone to him?   I did not understand the root
>>         cause, but I would hope there is something that can be done.
>>         Would signing help receiving sites, those with less
>>         sophistication than he has, be able to sort out noise more
>>         effectively?
>>
>>
>>         On Mon, Jan 25, 2021, 11:51 AM Michael Thomas <mike@mtcc.com
>>         <mailto:mike@mtcc.com>> wrote:
>>
>>
>>             On 1/25/21 8:44 AM, Todd Herr wrote:
>>>             On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas
>>>             <mike@mtcc.com <mailto:mike@mtcc.com>> wrote:
>>>
>>>
>>>                 The main thing I've learned over the years of
>>>                 dealing with security is to not underestimate what a
>>>                 motivated attacker can do. Your imagination is not
>>>                 the same as their imagination. Closing #98 in
>>>                 particular is absolutely ridiculous: the report
>>>                 should already have a DKIM signature or SPF so it's
>>>                 just a matter of making sure its valid. Why would
>>>                 you *not* want to insure that? The amount of
>>>                 justification for *not* having the receiver
>>>                 authenticate it is a mountain. The amount of effort
>>>                 to authenticate it is trivial for mail. Levine's
>>>                 dismissal of security concerns because he has
>>>                 anecdotal "evidence" from a backwater domain carries
>>>                 no weight at all.
>>>
>>>
>>>             That's all well and good, but you haven't answered the
>>>             question I asked.
>>>
>>>             What threats do you have in mind? Put another way, how
>>>             do you envision an attacker exploiting the lack of
>>>             authentication in a DMARC report to his or her gain?
>>>
>>             No, sorry, the onus is on the people who don't think it
>>             can be gamed. A bald assertion that it can't be gamed is
>>             very unconvincing. You need to lay out a miles long case
>>             for why it cannot be gamed. And to what end? #98 has a
>>             simple piece of text that should be added to DMARC to
>>             eliminate the possibility of forgery. You'd need a 10
>>             page threat I-D to explain why it's not necessary. What
>>             is the point of that? For email, it's trivial to prevent
>>             forgeries. Why would anybody argue against that?
>>
>>             Mike
>>
>>             _______________________________________________
>>             dmarc mailing list
>>             dmarc@ietf.org <mailto:dmarc@ietf.org>
>>             https://www.ietf.org/mailman/listinfo/dmarc
>>             <https://www.ietf.org/mailman/listinfo/dmarc>
>>
>>         _______________________________________________
>>         dmarc mailing list
>>         dmarc@ietf.org <mailto:dmarc@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/dmarc
>>         <https://www.ietf.org/mailman/listinfo/dmarc>
>>
>>
>>
>>     -- 
>>     *Seth Blank*| VP, Standards and New Technologies
>>     *e:*seth@valimail.com <mailto:seth@valimail.com>
>>     *p:*415.273.8818
>>
>>
>>     This email and all data transmitted with it contains confidential
>>     and/or proprietary information intended solely for the use of
>>     individual(s) authorized to receive it. If you are not an
>>     intended and authorized recipient you are hereby notified of any
>>     use, disclosure, copying or distribution of the information
>>     included in this transmission is prohibited and may be unlawful.
>>     Please immediately notify the sender by replying to this email
>>     and then delete it from your system.
>>
>
>
> -- 
> *Seth Blank*| VP, Standards and New Technologies
> *e:*seth@valimail.com <mailto:seth@valimail.com>
> *p:*415.273.8818
>
>
> This email and all data transmitted with it contains confidential 
> and/or proprietary information intended solely for the use of 
> individual(s) authorized to receive it. If you are not an intended and 
> authorized recipient you are hereby notified of any use, disclosure, 
> copying or distribution of the information included in this 
> transmission is prohibited and may be unlawful. Please immediately 
> notify the sender by replying to this email and then delete it from 
> your system.
>

--------------34AE3435089922E4931EC1B0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Why is this controversial? Seriously. What is controversial about
      saying that the a report should authenticate? The onus is on the
      people who say it does not to lay out the case for why it's not a
      problem, not me. #98 has a simple piece of text to remedy this.
      it's 2021. You don't use unauthenticated data if you can possibly
      help it.<br>
    </p>
    <p>Mike<br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 9:25 AM, Seth Blank wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Mike, how do you believe DMARC reports are consumed
        and utilized? I think you have a misunderstanding here which is
        why you're going down this path and everyone else is pushing
        back.</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021 at 9:22
          AM Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
            moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p>Taking in information from unauthenticated sources and
              acting on it is an operational problem per se. Have we
              learned nothing in the last 30 years?</p>
            <p>Mike<br>
            </p>
            <div>On 1/25/21 9:19 AM, Seth Blank wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">What operational problem are we solving
                here? Absent evidence of a problem and strong consensus
                on the solution, let's close these tickets and move on.</div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021
                  at 9:10 AM Douglas Foster &lt;<a
                    href="mailto:dougfoster.emailstandards@gmail.com"
                    target="_blank" moz-do-not-send="true">dougfoster.emailstandards@gmail.com</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div dir="auto">Since the status quo is
                    unauthenticated, I wonder if adding a signing
                    requirement will help.
                    <div dir="auto">Will recipients discad unsigned
                      messages, or accept whatever is available to
                      maximize their information capture?  I suspect
                      they will conrinye to accept everything.</div>
                    <div dir="auto"><br>
                    </div>
                    <div dir="auto">I think we would need an identified
                      threat before recipients would be motivated to
                      discard.</div>
                    <div dir="auto"><br>
                    </div>
                    <div dir="auto">But what about John's problems with
                      receiving reports that should not have gone to
                      him?   I did not understand the root cause, but I
                      would hope there is something that can be done. 
                      Would signing help receiving sites, those with
                      less sophistication than he has, be able to sort
                      out noise more effectively?</div>
                    <div dir="auto"><br>
                    </div>
                  </div>
                  <br>
                  <div class="gmail_quote">
                    <div dir="ltr" class="gmail_attr">On Mon, Jan 25,
                      2021, 11:51 AM Michael Thomas &lt;<a
                        href="mailto:mike@mtcc.com" rel="noreferrer"
                        target="_blank" moz-do-not-send="true">mike@mtcc.com</a>&gt;
                      wrote:<br>
                    </div>
                    <blockquote class="gmail_quote" style="margin:0px
                      0px 0px 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex">
                      <div>
                        <p><br>
                        </p>
                        <div>On 1/25/21 8:44 AM, Todd Herr wrote:<br>
                        </div>
                        <blockquote type="cite">
                          <div dir="ltr">
                            <div dir="ltr">On Mon, Jan 25, 2021 at 10:18
                              AM Michael Thomas &lt;<a
                                href="mailto:mike@mtcc.com"
                                rel="noreferrer noreferrer"
                                target="_blank" moz-do-not-send="true">mike@mtcc.com</a>&gt;
                              wrote:<br>
                            </div>
                            <div class="gmail_quote">
                              <blockquote class="gmail_quote"
                                style="margin:0px 0px 0px
                                0.8ex;border-left:1px solid
                                rgb(204,204,204);padding-left:1ex">
                                <div><br>
                                  <p>The main thing I've learned over
                                    the years of dealing with security
                                    is to not underestimate what a
                                    motivated attacker can do. Your
                                    imagination is not the same as their
                                    imagination. Closing #98 in
                                    particular is absolutely ridiculous:
                                    the report should already have a
                                    DKIM signature or SPF so it's just a
                                    matter of making sure its valid. Why
                                    would you *not* want to insure that?
                                    The amount of justification for
                                    *not* having the receiver
                                    authenticate it is a mountain. The
                                    amount of effort to authenticate it
                                    is trivial for mail. Levine's
                                    dismissal of security concerns
                                    because he has anecdotal "evidence"
                                    from a backwater domain carries no
                                    weight at all.</p>
                                </div>
                              </blockquote>
                              <div><br>
                              </div>
                              <div>That's all well and good, but you
                                haven't answered the question I asked.</div>
                              <div><br>
                              </div>
                              <div>What threats do you have in mind? Put
                                another way, how do you envision an
                                attacker exploiting the lack of
                                authentication in a DMARC report to his
                                or her gain?</div>
                              <br>
                            </div>
                          </div>
                        </blockquote>
                        <p>No, sorry, the onus is on the people who
                          don't think it can be gamed. A bald assertion
                          that it can't be gamed is very unconvincing.
                          You need to lay out a miles long case for why
                          it cannot be gamed. And to what end? #98 has a
                          simple piece of text that should be added to
                          DMARC to eliminate the possibility of forgery.
                          You'd need a 10 page threat I-D to explain why
                          it's not necessary. What is the point of that?
                          For email, it's trivial to prevent forgeries.
                          Why would anybody argue against that?</p>
                        <p>Mike<br>
                        </p>
                      </div>
                      _______________________________________________<br>
                      dmarc mailing list<br>
                      <a href="mailto:dmarc@ietf.org" rel="noreferrer
                        noreferrer" target="_blank"
                        moz-do-not-send="true">dmarc@ietf.org</a><br>
                      <a
                        href="https://www.ietf.org/mailman/listinfo/dmarc"
                        rel="noreferrer noreferrer noreferrer"
                        target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
                    </blockquote>
                  </div>
                  _______________________________________________<br>
                  dmarc mailing list<br>
                  <a href="mailto:dmarc@ietf.org" target="_blank"
                    moz-do-not-send="true">dmarc@ietf.org</a><br>
                  <a href="https://www.ietf.org/mailman/listinfo/dmarc"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
                </blockquote>
              </div>
              <br clear="all">
              <div><br>
              </div>
              -- <br>
              <div dir="ltr"><span>
                  <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
                  <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
                    <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
                  </span>
                  <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
                  <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
                  </p>
                  <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
                      face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
                </span></div>
            </blockquote>
          </div>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"><span>
          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
          </span>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
        </span></div>
    </blockquote>
  </body>
</html>

--------------34AE3435089922E4931EC1B0--


From nobody Mon Jan 25 09:39:01 2021
Return-Path: <superuser@gmail.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 970723A15FA for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:38:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 rwQ-Ehiqp4h5 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:38:58 -0800 (PST)
Received: from mail-ua1-x936.google.com (mail-ua1-x936.google.com [IPv6:2607:f8b0:4864:20::936]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEBA53A15F7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:38:57 -0800 (PST)
Received: by mail-ua1-x936.google.com with SMTP id k22so4715077ual.0 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:38:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jqnAG9qQ6SLaRoGrp9YH+uTcxYzw7cZuvXHrAwIKH2o=; b=Hv2Gp6eFgDzuYM6VpRDLPeYZJTkVdKEQn4Kwe5omm2UjtwvIumOpDRcxJjFWIop6D2 kSM5Dff58LxMp+GcGd0DZh7ElGdk0qzQT6claHt9a3IsX1XayrrinQCuLjfOn1+tj21U S1wFGFmvB2oHwPh0Sde68fOYClPGtztYeY6HfE/X3ydDIw1v4P95kX+lZi1tYuLS3qQL xqThWQAvPLS/JvqgvwOQMKRX9XPDDvaYGEqNG7gapbHeuEKFGR3X70dJtlIggxsaL1fk /0IiHYaF6LXe9yrnBS1PJ62IjGjDGDGe1Qxz+hAhZLV5Yf+DKM/Gx0DWHqi+3DOwIxpD kCzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jqnAG9qQ6SLaRoGrp9YH+uTcxYzw7cZuvXHrAwIKH2o=; b=tC+36jvck0PZyNu6NWX4JvpIwIa9l+ulA0cmjPRQsrw0WDA0am7+2A8g84Tis6WxtP GkzLpx9mi6+FZIUHYe7db2JYNXVMxcfZuGaHNfVrPOpww0W7CL+01+saM9vdtXM5eYn9 zven8Jb1Zy2DIk3l8ndGfl/rJMVZyro4ch5CO/n2rr1zn8PhT4jA6nEA5PKjmoH3N47N Ez0/vZZf/w9mafc7M4soAp5ilPqkdfEv2ZJvVUKaJdmV/1wQpQYLyY+1T8QwjQpUxLzF TR1AQeHsNvpzGHdBl/BVTUpTB/+F3vMMuarkTO1gi+rWyx5RccbtxWbIaRuzuB8YkTCF Ub8w==
X-Gm-Message-State: AOAM5321r6zbIV4miihJAd4SxnmsnfWlcACHlXyZkZlidnlh+Dfg4J0l MTRGpBfHdGLF7mFSgTgg9B/9i6jxDensdhTCFnQ=
X-Google-Smtp-Source: ABdhPJz2R7Lc0FxC7uCCSYjyJpduXxvVUTYkOvt2ZFkwDAvBMo7Q2JffKKe9vu6yd03g3+FmAM4XyBJiTpAQVrvGHv0=
X-Received: by 2002:a9f:2628:: with SMTP id 37mr1420964uag.87.1611596336803; Mon, 25 Jan 2021 09:38:56 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com>
In-Reply-To: <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 25 Jan 2021 09:38:45 -0800
Message-ID: <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: Seth Blank <seth@valimail.com>, Douglas Foster <dougfoster.emailstandards@gmail.com>,  IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002d36c505b9bd03d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/7AzcMm4GnQs1OFigeIGNV9M4gsY>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:39:00 -0000

--0000000000002d36c505b9bd03d2
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 25, 2021 at 9:32 AM Michael Thomas <mike@mtcc.com> wrote:

> Why is this controversial? Seriously. What is controversial about saying
> that the a report should authenticate? The onus is on the people who say it
> does not to lay out the case for why it's not a problem, not me. #98 has a
> simple piece of text to remedy this. it's 2021. You don't use
> unauthenticated data if you can possibly help it.
>
I'm not taking a position at this point on the issue, but I think you
should expect that this will come up in external reviews.  If consensus is
to maintain the status quo, we might want to say so explicitly (and why)
rather than saying nothing, as the latter might be interpreted as it having
gotten no consideration at all.

-MSK

--0000000000002d36c505b9bd03d2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 25, 2021 at 9:32 AM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
 =20
   =20
 =20
  <div>
    <p>Why is this controversial? Seriously. What is controversial about
      saying that the a report should authenticate? The onus is on the
      people who say it does not to lay out the case for why it&#39;s not a
      problem, not me. #98 has a simple piece of text to remedy this.
      it&#39;s 2021. You don&#39;t use unauthenticated data if you can poss=
ibly
      help it.<br>
    </p></div></blockquote><div>I&#39;m not taking a position at this point=
 on the issue, but I think you should expect that this will come up in exte=
rnal reviews.=C2=A0 If consensus is to maintain the status quo, we might wa=
nt to say so explicitly (and why) rather than saying nothing, as the latter=
 might be interpreted as it having gotten no consideration at all.</div><di=
v><br></div><div>-MSK<br></div></div></div>

--0000000000002d36c505b9bd03d2--


From nobody Mon Jan 25 09:40:38 2021
Return-Path: <seth@valimail.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 934193A15FB for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 AdGvbssZg1Hr for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:40:34 -0800 (PST)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11C993A15F7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:40:33 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id h11so7597057vsa.10 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:40:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vJNoIaqOCOrMCaf/sJMZSgzmiI6OKL40+iNnTFgAjfQ=; b=Gs13rxf0Qa0p//LSFmO2F6Ay7hNsH5qK99xHf8/HkDFnWSKQh/EMsFuLsHwq3cgFKv +3r+J9SCFZXGgrES5XaEjKvjjyDgNCzBaCJDEfpz+QckuO4TTMliUplR7aST5PlgUA1J nXdWaGRNA1jA27eHyRf748m1hwI5vEjbwppoaOWWMyFyRzmtnf8/vd46yqccKxIGHi+3 15m5yIbE0yoyzo31MLclgaPQTKYjr3T/r7dQyBYOZaArWttBAeMdPeQNSSfPGqTNOggO U7lxO71t/1XQruIimnC9g2GkboWQiwtcT8NuXA1hyGp0gEV0R/FLA0dyBu8DGRe6BC/B 8gxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vJNoIaqOCOrMCaf/sJMZSgzmiI6OKL40+iNnTFgAjfQ=; b=Co4TFW2cKeJzzXI9eEX2aiN/+qJ16Ykau8n7rm0t2vK6zctRloQxk+9tz784SEsrdA 0XkAMPmm4lHlJtRZICjumidzPmoiQMyGolL7q4HyzyjFfdMm/W9OKiMXoJ21lx9K9Z7x CFFrbwCLRyOv3rNA3IPn6fMiPUivOy+kZcTTT5piaIVn92m0ceUZT1EkLZuQsiIGfDTz WihBM+wR3HPhJYpcqZNjLaAeOmO9lSo20k9fMgrmGMkoQBklzruCeiUXFaFBhZSQ9V0t b/2PzYj4ITSkVgmVfvMBQ6GbYvvpcVl/rMypowNBOwhPY490W5Ryoi5LAV24On5S6wxA lgPA==
X-Gm-Message-State: AOAM532alMvbZRGb25FNqsogDR9TczCR/sNQXKnhw7Ss+n/C13vTUs4N NnYfGYNwGTLxIpSRJ5PvS6w4Dlzzt/TZu4WrRqMKmg==
X-Google-Smtp-Source: ABdhPJxelFGc51cJKNNM3tw6hKLVROQEct9Z8XMMwdbc3LgHXWXVBN5L8NDd2Bt1kfAOdTHAbGSunZ8otC1RaQHC3y8=
X-Received: by 2002:a67:62c4:: with SMTP id w187mr1759286vsb.43.1611596432970;  Mon, 25 Jan 2021 09:40:32 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com>
In-Reply-To: <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 25 Jan 2021 09:40:22 -0800
Message-ID: <CAOZAAfP7oMCtV_1E4+8kZS5Jb1C-nddR_QtLauF6shGY9z7Bqw@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, Douglas Foster <dougfoster.emailstandards@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000e8a96905b9bd081f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VLZ7MdJQXA41xbqf-5nNaVwNVVY>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:40:37 -0000

--000000000000e8a96905b9bd081f
Content-Type: text/plain; charset="UTF-8"

Michael, as an individual, I don't disagree. What's not clear about the
current text?

https://tools.ietf.org/html/rfc7489#section-7.2.1.1

   Email streams carrying DMARC feedback data MUST conform to the DMARC
   mechanism, thereby resulting in an aligned "pass" (see Section 3.1
<https://tools.ietf.org/html/rfc7489#section-3.1>).
   This practice minimizes the risk of report consumers processing
   fraudulent reports.


On Mon, Jan 25, 2021 at 9:32 AM Michael Thomas <mike@mtcc.com> wrote:

> Why is this controversial? Seriously. What is controversial about saying
> that the a report should authenticate? The onus is on the people who say it
> does not to lay out the case for why it's not a problem, not me. #98 has a
> simple piece of text to remedy this. it's 2021. You don't use
> unauthenticated data if you can possibly help it.
>
> Mike
> On 1/25/21 9:25 AM, Seth Blank wrote:
>
> Mike, how do you believe DMARC reports are consumed and utilized? I think
> you have a misunderstanding here which is why you're going down this path
> and everyone else is pushing back.
>
> On Mon, Jan 25, 2021 at 9:22 AM Michael Thomas <mike@mtcc.com> wrote:
>
>> Taking in information from unauthenticated sources and acting on it is an
>> operational problem per se. Have we learned nothing in the last 30 years?
>>
>> Mike
>> On 1/25/21 9:19 AM, Seth Blank wrote:
>>
>> What operational problem are we solving here? Absent evidence of a
>> problem and strong consensus on the solution, let's close these tickets and
>> move on.
>>
>> On Mon, Jan 25, 2021 at 9:10 AM Douglas Foster <
>> dougfoster.emailstandards@gmail.com> wrote:
>>
>>> Since the status quo is unauthenticated, I wonder if adding a signing
>>> requirement will help.
>>> Will recipients discad unsigned messages, or accept whatever is
>>> available to maximize their information capture?  I suspect they will
>>> conrinye to accept everything.
>>>
>>> I think we would need an identified threat before recipients would be
>>> motivated to discard.
>>>
>>> But what about John's problems with receiving reports that should not
>>> have gone to him?   I did not understand the root cause, but I would hope
>>> there is something that can be done.  Would signing help receiving sites,
>>> those with less sophistication than he has, be able to sort out noise more
>>> effectively?
>>>
>>>
>>> On Mon, Jan 25, 2021, 11:51 AM Michael Thomas <mike@mtcc.com> wrote:
>>>
>>>>
>>>> On 1/25/21 8:44 AM, Todd Herr wrote:
>>>>
>>>> On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas <mike@mtcc.com> wrote:
>>>>
>>>>>
>>>>> The main thing I've learned over the years of dealing with security is
>>>>> to not underestimate what a motivated attacker can do. Your imagination is
>>>>> not the same as their imagination. Closing #98 in particular is absolutely
>>>>> ridiculous: the report should already have a DKIM signature or SPF so it's
>>>>> just a matter of making sure its valid. Why would you *not* want to insure
>>>>> that? The amount of justification for *not* having the receiver
>>>>> authenticate it is a mountain. The amount of effort to authenticate it is
>>>>> trivial for mail. Levine's dismissal of security concerns because he has
>>>>> anecdotal "evidence" from a backwater domain carries no weight at all.
>>>>>
>>>>
>>>> That's all well and good, but you haven't answered the question I asked.
>>>>
>>>> What threats do you have in mind? Put another way, how do you envision
>>>> an attacker exploiting the lack of authentication in a DMARC report to his
>>>> or her gain?
>>>>
>>>> No, sorry, the onus is on the people who don't think it can be gamed. A
>>>> bald assertion that it can't be gamed is very unconvincing. You need to lay
>>>> out a miles long case for why it cannot be gamed. And to what end? #98 has
>>>> a simple piece of text that should be added to DMARC to eliminate the
>>>> possibility of forgery. You'd need a 10 page threat I-D to explain why it's
>>>> not necessary. What is the point of that? For email, it's trivial to
>>>> prevent forgeries. Why would anybody argue against that?
>>>>
>>>> Mike
>>>> _______________________________________________
>>>> dmarc mailing list
>>>> dmarc@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dmarc
>>>>
>>> _______________________________________________
>>> dmarc mailing list
>>> dmarc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dmarc
>>>
>>
>>
>> --
>> *Seth Blank* | VP, Standards and New Technologies
>> *e:* seth@valimail.com
>> *p:* 415.273.8818
>>
>>
>> This email and all data transmitted with it contains confidential and/or
>> proprietary information intended solely for the use of individual(s)
>> authorized to receive it. If you are not an intended and authorized
>> recipient you are hereby notified of any use, disclosure, copying or
>> distribution of the information included in this transmission is prohibited
>> and may be unlawful. Please immediately notify the sender by replying to
>> this email and then delete it from your system.
>>
>>
>
> --
> *Seth Blank* | VP, Standards and New Technologies
> *e:* seth@valimail.com
> *p:* 415.273.8818
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
>
>

-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000e8a96905b9bd081f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Michael, as an individual, I don&#39;t disagree. What&#39;=
s not clear about the current text?<div><br></div><div><a href=3D"https://t=
ools.ietf.org/html/rfc7489#section-7.2.1.1">https://tools.ietf.org/html/rfc=
7489#section-7.2.1.1</a><br></div><div><br></div><div><pre class=3D"gmail-n=
ewpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break=
-before:page;color:rgb(0,0,0)">   Email streams carrying DMARC feedback dat=
a MUST conform to the DMARC
   mechanism, thereby resulting in an aligned &quot;pass&quot; (see <a href=
=3D"https://tools.ietf.org/html/rfc7489#section-3.1">Section 3.1</a>).
   This practice minimizes the risk of report consumers processing
   fraudulent reports.</pre></div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 9:32 AM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p>Why is this controversial? Seriously. What is controversial about
      saying that the a report should authenticate? The onus is on the
      people who say it does not to lay out the case for why it&#39;s not a
      problem, not me. #98 has a simple piece of text to remedy this.
      it&#39;s 2021. You don&#39;t use unauthenticated data if you can poss=
ibly
      help it.<br>
    </p>
    <p>Mike<br>
    </p>
    <div>On 1/25/21 9:25 AM, Seth Blank wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Mike, how do you believe DMARC reports are consumed
        and utilized? I think you have a misunderstanding here which is
        why you&#39;re going down this path and everyone else is pushing
        back.</div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 9:22
          AM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"=
_blank">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p>Taking in information from unauthenticated sources and
              acting on it is an operational problem per se. Have we
              learned nothing in the last 30 years?</p>
            <p>Mike<br>
            </p>
            <div>On 1/25/21 9:19 AM, Seth Blank wrote:<br>
            </div>
            <blockquote type=3D"cite">
              <div dir=3D"ltr">What operational problem are we solving
                here?=C2=A0Absent evidence of a problem and strong consensu=
s
                on the solution, let&#39;s close these tickets and move on.=
</div>
              <br>
              <div class=3D"gmail_quote">
                <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021
                  at 9:10 AM Douglas Foster &lt;<a href=3D"mailto:dougfoste=
r.emailstandards@gmail.com" target=3D"_blank">dougfoster.emailstandards@gma=
il.com</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                  <div dir=3D"auto">Since the status quo is
                    unauthenticated, I wonder if adding a signing
                    requirement will help.
                    <div dir=3D"auto">Will recipients discad unsigned
                      messages, or accept whatever is available to
                      maximize their information capture?=C2=A0 I suspect
                      they will conrinye to accept everything.</div>
                    <div dir=3D"auto"><br>
                    </div>
                    <div dir=3D"auto">I think we would need an identified
                      threat before recipients would be motivated to
                      discard.</div>
                    <div dir=3D"auto"><br>
                    </div>
                    <div dir=3D"auto">But what about John&#39;s problems wi=
th
                      receiving reports that should not have gone to
                      him?=C2=A0 =C2=A0I did not understand the root cause,=
 but I
                      would hope there is something that can be done.=C2=A0
                      Would signing help receiving sites, those with
                      less sophistication than he has, be able to sort
                      out noise more effectively?</div>
                    <div dir=3D"auto"><br>
                    </div>
                  </div>
                  <br>
                  <div class=3D"gmail_quote">
                    <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25,
                      2021, 11:51 AM Michael Thomas &lt;<a href=3D"mailto:m=
ike@mtcc.com" rel=3D"noreferrer" target=3D"_blank">mike@mtcc.com</a>&gt;
                      wrote:<br>
                    </div>
                    <blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                      <div>
                        <p><br>
                        </p>
                        <div>On 1/25/21 8:44 AM, Todd Herr wrote:<br>
                        </div>
                        <blockquote type=3D"cite">
                          <div dir=3D"ltr">
                            <div dir=3D"ltr">On Mon, Jan 25, 2021 at 10:18
                              AM Michael Thomas &lt;<a href=3D"mailto:mike@=
mtcc.com" rel=3D"noreferrer noreferrer" target=3D"_blank">mike@mtcc.com</a>=
&gt;
                              wrote:<br>
                            </div>
                            <div class=3D"gmail_quote">
                              <blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
                                <div><br>
                                  <p>The main thing I&#39;ve learned over
                                    the years of dealing with security
                                    is to not underestimate what a
                                    motivated attacker can do. Your
                                    imagination is not the same as their
                                    imagination. Closing #98 in
                                    particular is absolutely ridiculous:
                                    the report should already have a
                                    DKIM signature or SPF so it&#39;s just =
a
                                    matter of making sure its valid. Why
                                    would you *not* want to insure that?
                                    The amount of justification for
                                    *not* having the receiver
                                    authenticate it is a mountain. The
                                    amount of effort to authenticate it
                                    is trivial for mail. Levine&#39;s
                                    dismissal of security concerns
                                    because he has anecdotal &quot;evidence=
&quot;
                                    from a backwater domain carries no
                                    weight at all.</p>
                                </div>
                              </blockquote>
                              <div><br>
                              </div>
                              <div>That&#39;s all well and good, but you
                                haven&#39;t answered the question I asked.<=
/div>
                              <div><br>
                              </div>
                              <div>What threats do you have in mind? Put
                                another way, how do you envision an
                                attacker exploiting the lack of
                                authentication in a DMARC report to his
                                or her gain?</div>
                              <br>
                            </div>
                          </div>
                        </blockquote>
                        <p>No, sorry, the onus is on the people who
                          don&#39;t think it can be gamed. A bald assertion
                          that it can&#39;t be gamed is very unconvincing.
                          You need to lay out a miles long case for why
                          it cannot be gamed. And to what end? #98 has a
                          simple piece of text that should be added to
                          DMARC to eliminate the possibility of forgery.
                          You&#39;d need a 10 page threat I-D to explain wh=
y
                          it&#39;s not necessary. What is the point of that=
?
                          For email, it&#39;s trivial to prevent forgeries.
                          Why would anybody argue against that?</p>
                        <p>Mike<br>
                        </p>
                      </div>
                      _______________________________________________<br>
                      dmarc mailing list<br>
                      <a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer
                        noreferrer" target=3D"_blank">dmarc@ietf.org</a><br=
>
                      <a href=3D"https://www.ietf.org/mailman/listinfo/dmar=
c" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://www.i=
etf.org/mailman/listinfo/dmarc</a><br>
                    </blockquote>
                  </div>
                  _______________________________________________<br>
                  dmarc mailing list<br>
                  <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc=
@ietf.org</a><br>
                  <a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" r=
el=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/d=
marc</a><br>
                </blockquote>
              </div>
              <br clear=3D"all">
              <div><br>
              </div>
              -- <br>
              <div dir=3D"ltr"><span>
                  <div style=3D"text-align:left"><span style=3D"vertical-al=
ign:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Set=
h Blank</b></span><span style=3D"vertical-align:baseline;white-space:pre-wr=
ap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies=
</span></div>
                  <span style=3D"vertical-align:baseline;white-space:pre-wr=
ap;font-size:small;font-family:Arial"><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-a=
lign:baseline"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank">seth=
@valimail.com</a></span></div></span><span>
                    <div><span><b>p:</b></span><span> 415.273.8818 </span><=
span></span></div>
                  </span>
                  <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:A=
rial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255)=
;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-siz=
e:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vert=
ical-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleuse=
rcontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOq=
e0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL"=
 style=3D"border: none; height: 40px; width: 177px;"></span></p>
                  <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:A=
rial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255)=
;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
                  </p>
                  <p dir=3D"ltr" style=3D"background-color:rgb(255,255,255)=
;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font face=3D"Arial" co=
lor=3D"#666666"><span style=3D"font-size:10.6667px;white-space:pre-wrap">Th=
is email and all data transmitted with it contains confidential and/or prop=
rietary information intended solely for the use of individual(s) authorized=
 to receive it. If you are not an intended and authorized recipient you are=
 hereby notified of any use, disclosure, copying or distribution of the inf=
ormation included in this transmission is prohibited and may be unlawful. P=
lease immediately notify the sender by replying to this email and then dele=
te it from your system.</span></font></p>
                </span></div>
            </blockquote>
          </div>
        </blockquote>
      </div>
      <br clear=3D"all">
      <div><br>
      </div>
      -- <br>
      <div dir=3D"ltr"><span>
          <div style=3D"text-align:left"><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank<=
/b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"> | VP, Standards and New Technologies</span><=
/div>
          <span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D=
"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:bas=
eline"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank">seth@valimai=
l.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></s=
pan></div>
          </span>
          <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;f=
ont-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-ali=
gn:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent=
.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSX=
prAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=
=3D"border: none; height: 40px; width: 177px;"></span></p>
          <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><font face=3D"Arial" color=3D"#=
666666"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email=
 and all data transmitted with it contains confidential and/or proprietary =
information intended solely for the use of individual(s) authorized to rece=
ive it. If you are not an intended and authorized recipient you are hereby =
notified of any use, disclosure, copying or distribution of the information=
 included in this transmission is prohibited and may be unlawful. Please im=
mediately notify the sender by replying to this email and then delete it fr=
om your system.</span></font></p>
        </span></div>
    </blockquote>
  </div>

</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--000000000000e8a96905b9bd081f--


From nobody Mon Jan 25 09:41:45 2021
Return-Path: <seth@valimail.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 EA0ED3A16A4 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 9-WKM_5ygyCw for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:41:36 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC8793A16FC for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:41:23 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id f22so7605519vsk.11 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:41:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=imYu5jeAqQ95Oc+/WxsaC/CIdkuYJ5tzHryye5rF8r8=; b=YhlNItUIUGaFncoqiSuaknWbHmSpUADzVhrt1K/hqi5HR+75vUJJpC4dUojHXZiBtn fW1F/cwdPlYguslUCjCSfslc/Kv9Druq4Ttio2hIevSy7eL5iwyPCFmq0HzS0nLo2rHb KE2YlNtxLR6LpFZ41IHHDhmb42MJrPgLdxCZ7xZlgNjiaHA3OFmMu8GRkwN46Aiv/+QN yauBeJ2jMvQ/5adGTPJ5zeRQByYDaKZ5YlLlcWLjO4zCAxv1P3xfC63myo6/bCOT+2ca BLK7kjWdV1lSPAvdzJVseQH5c+V8ruDnivoCc0LOY9CDaunq0w3MmIBE7hC+XIBj0Fd/ wohQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=imYu5jeAqQ95Oc+/WxsaC/CIdkuYJ5tzHryye5rF8r8=; b=MhsHTj+Eknck2kXRbL502Dako9/mLUjMasLmou3/7ykZl2pQxfs86A6Mm3dga+aSPk drXx/ojKR9V0knO6FYasDRNom3yX99w83QoM0o/MLLIrnzf1Rk8+CCfB/CUUjvaVbk2Q 7oDHTp4iHabEsO8SvDusu5+1rkpRqkWyB0kV8I0lcq1wsTKPYolt45g0dQJD67iti5bz 2UjEjCxFtmtDDhqYRd2WqQkThvlGrupJ6ond85XWJ1OOnlyAtdJUc+zfhzCSKv+7YaWR KbSpzBACmtkV5rkyoOoRBWPNPBb/LdCX4XeML9Z5b+kC87Rb9V7qt3FZ5CR2lbhxHLbA cFNA==
X-Gm-Message-State: AOAM533P0Bik2+XVqXmP9JR0KJgOA5kz/yb993sFo7xoOHHEcc+Y50Pl aoBGt8MY9QAWDfi9mWav3C7cESamdZXSNBzdjsVFIg==
X-Google-Smtp-Source: ABdhPJwRC6UE8Dm+0a98P++CaQTrgEvAELe+o4KBwnURznbTy96rwcLXQZQJgfEdjQrX/D+fPyBsJnFbBlXQX3TGnIk=
X-Received: by 2002:a05:6102:1c8:: with SMTP id s8mr1677708vsq.52.1611596482630;  Mon, 25 Jan 2021 09:41:22 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com>
In-Reply-To: <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 25 Jan 2021 09:41:11 -0800
Message-ID: <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Michael Thomas <mike@mtcc.com>, Douglas Foster <dougfoster.emailstandards@gmail.com>,  IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de715205b9bd0b7d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/yj2iYyDNAek9tn6JS3TaV8_iCVY>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:41:43 -0000

--000000000000de715205b9bd0b7d
Content-Type: text/plain; charset="UTF-8"

Realized I think we're going in circles. Just posted text that is status
quo that I believe already addresses Michael's concern.

On Mon, Jan 25, 2021 at 9:38 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Mon, Jan 25, 2021 at 9:32 AM Michael Thomas <mike@mtcc.com> wrote:
>
>> Why is this controversial? Seriously. What is controversial about saying
>> that the a report should authenticate? The onus is on the people who say it
>> does not to lay out the case for why it's not a problem, not me. #98 has a
>> simple piece of text to remedy this. it's 2021. You don't use
>> unauthenticated data if you can possibly help it.
>>
> I'm not taking a position at this point on the issue, but I think you
> should expect that this will come up in external reviews.  If consensus is
> to maintain the status quo, we might want to say so explicitly (and why)
> rather than saying nothing, as the latter might be interpreted as it having
> gotten no consideration at all.
>
> -MSK
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000de715205b9bd0b7d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Realized I think we&#39;re going in circles. Just posted t=
ext that is status quo that I believe already addresses Michael&#39;s conce=
rn.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Mon, Jan 25, 2021 at 9:38 AM Murray S. Kucherawy &lt;<a href=3D"mailt=
o:superuser@gmail.com">superuser@gmail.com</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"=
>On Mon, Jan 25, 2021 at 9:32 AM Michael Thomas &lt;<a href=3D"mailto:mike@=
mtcc.com" target=3D"_blank">mike@mtcc.com</a>&gt; wrote:<br></div><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p>Why is this controversial? Seriously. What is controversial about
      saying that the a report should authenticate? The onus is on the
      people who say it does not to lay out the case for why it&#39;s not a
      problem, not me. #98 has a simple piece of text to remedy this.
      it&#39;s 2021. You don&#39;t use unauthenticated data if you can poss=
ibly
      help it.<br>
    </p></div></blockquote><div>I&#39;m not taking a position at this point=
 on the issue, but I think you should expect that this will come up in exte=
rnal reviews.=C2=A0 If consensus is to maintain the status quo, we might wa=
nt to say so explicitly (and why) rather than saying nothing, as the latter=
 might be interpreted as it having gotten no consideration at all.</div><di=
v><br></div><div>-MSK<br></div></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--000000000000de715205b9bd0b7d--


From nobody Mon Jan 25 09:48:50 2021
Return-Path: <mike@fresheez.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 798083A1627 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 OKbN9ucBw_dH for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:48:40 -0800 (PST)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D8DF3A160F for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:48:40 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id u11so8082686plg.13 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:48:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=kDVga8Si80Oz6emNYPxGLtgtUmTDlv+RFoLYrPRSSJM=; b=ehrYZXIA7r6uBffZ/dZOLlTmWKl+Kpgz/KbCttw34BtKWTI0sdl6HMSfNISCUIPqP/ awG5eGMJGsug4x8uZiQSbO4xtf7e7SIERUcmW+Z4EXCXFMIhBMH5iP5ZHpVC3b4VFC1O C6b2/xY6KAX8mCp5j5Rt1qLTlscC9f8ZJzQPFn6xLJAGpZKElKEZHrJbNESmeNrBtjow 6BAl5mC+25MiY0i+mAaNhET/G5Hk98HUq8juHF39CMrNnd1LvIfQOqHC7So9KY9jnAg/ B08YNreX2gIL6RwVRZAYXbNXBwH4LYGkFSjaIdJl54pFad9jHWkFpjo82Seg2+L4fiTA j3vA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=kDVga8Si80Oz6emNYPxGLtgtUmTDlv+RFoLYrPRSSJM=; b=kmOFgF8PWwEtXoqMDfNyd58qcsEk6hjrGepXWKpRXqSXdn3DejCIfteCXAIGRbml2J MCMrcVGgpVwzig/k0sjXDigI7kY6Kwh6A5/XBVJIPqsQOaLnzKTaHdWZS/F/cuBOiu82 aBWjPScWGDtE7KbA8mVvoX+jQXbwLOXNdppnKkmifrrJSjJqxgL1BOYeEufDpcZ/o2ts xyLNNqOc3Fu4kVfsrFiuJgxbSotw8v5jZNB7X/7TdNbHdvGNZiOAV8b0MeTWtXBm6zc9 iNEnyDzBuj4zqLU98ldOhY8+vPis/f0Qk0cjqaY5HXwu5EOyNm1ihWFOs2yuqqERLoCD sXcg==
X-Gm-Message-State: AOAM532RI7tt63QXIRlYov2eyvqjvCVJqsuIXgCx4YuIMQ3i5jj5JjA1 4pEjqLwG6uioNT6moUOaZ7VkOgk8f+Z4WQ==
X-Google-Smtp-Source: ABdhPJzVbEE3tv9YH9AhHsQwuR+Y46HP1YIoOycCPwObi2Fx1BYG1VWHgyX5IF7CJIGK+AzGUL3cdw==
X-Received: by 2002:a17:90a:4209:: with SMTP id o9mr1396869pjg.75.1611596919745;  Mon, 25 Jan 2021 09:48:39 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id g17sm18080660pgg.78.2021.01.25.09.48.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 09:48:39 -0800 (PST)
To: Seth Blank <seth@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, Douglas Foster <dougfoster.emailstandards@gmail.com>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAOZAAfP7oMCtV_1E4+8kZS5Jb1C-nddR_QtLauF6shGY9z7Bqw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <e27b3887-fb7f-6203-bbc3-9911b4bcb8ad@mtcc.com>
Date: Mon, 25 Jan 2021 09:48:37 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfP7oMCtV_1E4+8kZS5Jb1C-nddR_QtLauF6shGY9z7Bqw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------321B764A515C7788CDAE896D"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YPyzL49wbl4aeSuCwUobkNn1mYk>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:48:49 -0000

This is a multi-part message in MIME format.
--------------321B764A515C7788CDAE896D
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

That text is not very clear to say the least. It's written in a very 
passive voice. What is wrong with the text I provided? It should be made 
very explicit like I did with what the responsibility of the sender and 
receiver is.

Mike

On 1/25/21 9:40 AM, Seth Blank wrote:
> Michael, as an individual, I don't disagree. What's not clear about 
> the current text?
>
> https://tools.ietf.org/html/rfc7489#section-7.2.1.1 
> <https://tools.ietf.org/html/rfc7489#section-7.2.1.1>
>
>     Email streams carrying DMARC feedback data MUST conform to the DMARC
>     mechanism, thereby resulting in an aligned "pass" (seeSection 3.1  <https://tools.ietf.org/html/rfc7489#section-3.1>).
>     This practice minimizes the risk of report consumers processing
>     fraudulent reports.
>
> On Mon, Jan 25, 2021 at 9:32 AM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>     Why is this controversial? Seriously. What is controversial about
>     saying that the a report should authenticate? The onus is on the
>     people who say it does not to lay out the case for why it's not a
>     problem, not me. #98 has a simple piece of text to remedy this.
>     it's 2021. You don't use unauthenticated data if you can possibly
>     help it.
>
>     Mike
>
>     On 1/25/21 9:25 AM, Seth Blank wrote:
>>     Mike, how do you believe DMARC reports are consumed and utilized?
>>     I think you have a misunderstanding here which is why you're
>>     going down this path and everyone else is pushing back.
>>
>>     On Mon, Jan 25, 2021 at 9:22 AM Michael Thomas <mike@mtcc.com
>>     <mailto:mike@mtcc.com>> wrote:
>>
>>         Taking in information from unauthenticated sources and acting
>>         on it is an operational problem per se. Have we learned
>>         nothing in the last 30 years?
>>
>>         Mike
>>
>>         On 1/25/21 9:19 AM, Seth Blank wrote:
>>>         What operational problem are we solving here? Absent
>>>         evidence of a problem and strong consensus on the solution,
>>>         let's close these tickets and move on.
>>>
>>>         On Mon, Jan 25, 2021 at 9:10 AM Douglas Foster
>>>         <dougfoster.emailstandards@gmail.com
>>>         <mailto:dougfoster.emailstandards@gmail.com>> wrote:
>>>
>>>             Since the status quo is unauthenticated, I wonder if
>>>             adding a signing requirement will help.
>>>             Will recipients discad unsigned messages, or accept
>>>             whatever is available to maximize their information
>>>             capture?  I suspect they will conrinye to accept everything.
>>>
>>>             I think we would need an identified threat before
>>>             recipients would be motivated to discard.
>>>
>>>             But what about John's problems with receiving reports
>>>             that should not have gone to him?   I did not understand
>>>             the root cause, but I would hope there is something that
>>>             can be done. Would signing help receiving sites, those
>>>             with less sophistication than he has, be able to sort
>>>             out noise more effectively?
>>>
>>>
>>>             On Mon, Jan 25, 2021, 11:51 AM Michael Thomas
>>>             <mike@mtcc.com <mailto:mike@mtcc.com>> wrote:
>>>
>>>
>>>                 On 1/25/21 8:44 AM, Todd Herr wrote:
>>>>                 On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas
>>>>                 <mike@mtcc.com <mailto:mike@mtcc.com>> wrote:
>>>>
>>>>
>>>>                     The main thing I've learned over the years of
>>>>                     dealing with security is to not underestimate
>>>>                     what a motivated attacker can do. Your
>>>>                     imagination is not the same as their
>>>>                     imagination. Closing #98 in particular is
>>>>                     absolutely ridiculous: the report should
>>>>                     already have a DKIM signature or SPF so it's
>>>>                     just a matter of making sure its valid. Why
>>>>                     would you *not* want to insure that? The amount
>>>>                     of justification for *not* having the receiver
>>>>                     authenticate it is a mountain. The amount of
>>>>                     effort to authenticate it is trivial for mail.
>>>>                     Levine's dismissal of security concerns because
>>>>                     he has anecdotal "evidence" from a backwater
>>>>                     domain carries no weight at all.
>>>>
>>>>
>>>>                 That's all well and good, but you haven't answered
>>>>                 the question I asked.
>>>>
>>>>                 What threats do you have in mind? Put another way,
>>>>                 how do you envision an attacker exploiting the lack
>>>>                 of authentication in a DMARC report to his or her gain?
>>>>
>>>                 No, sorry, the onus is on the people who don't think
>>>                 it can be gamed. A bald assertion that it can't be
>>>                 gamed is very unconvincing. You need to lay out a
>>>                 miles long case for why it cannot be gamed. And to
>>>                 what end? #98 has a simple piece of text that should
>>>                 be added to DMARC to eliminate the possibility of
>>>                 forgery. You'd need a 10 page threat I-D to explain
>>>                 why it's not necessary. What is the point of that?
>>>                 For email, it's trivial to prevent forgeries. Why
>>>                 would anybody argue against that?
>>>
>>>                 Mike
>>>
>>>                 _______________________________________________
>>>                 dmarc mailing list
>>>                 dmarc@ietf.org <mailto:dmarc@ietf.org>
>>>                 https://www.ietf.org/mailman/listinfo/dmarc
>>>                 <https://www.ietf.org/mailman/listinfo/dmarc>
>>>
>>>             _______________________________________________
>>>             dmarc mailing list
>>>             dmarc@ietf.org <mailto:dmarc@ietf.org>
>>>             https://www.ietf.org/mailman/listinfo/dmarc
>>>             <https://www.ietf.org/mailman/listinfo/dmarc>
>>>
>>>
>>>
>>>         -- 
>>>         *Seth Blank*| VP, Standards and New Technologies
>>>         *e:*seth@valimail.com <mailto:seth@valimail.com>
>>>         *p:*415.273.8818
>>>
>>>
>>>         This email and all data transmitted with it contains
>>>         confidential and/or proprietary information intended solely
>>>         for the use of individual(s) authorized to receive it. If
>>>         you are not an intended and authorized recipient you are
>>>         hereby notified of any use, disclosure, copying or
>>>         distribution of the information included in this
>>>         transmission is prohibited and may be unlawful. Please
>>>         immediately notify the sender by replying to this email and
>>>         then delete it from your system.
>>>
>>
>>
>>     -- 
>>     *Seth Blank*| VP, Standards and New Technologies
>>     *e:*seth@valimail.com <mailto:seth@valimail.com>
>>     *p:*415.273.8818
>>
>>
>>     This email and all data transmitted with it contains confidential
>>     and/or proprietary information intended solely for the use of
>>     individual(s) authorized to receive it. If you are not an
>>     intended and authorized recipient you are hereby notified of any
>>     use, disclosure, copying or distribution of the information
>>     included in this transmission is prohibited and may be unlawful.
>>     Please immediately notify the sender by replying to this email
>>     and then delete it from your system.
>>
>
>
> -- 
> *Seth Blank*| VP, Standards and New Technologies
> *e:*seth@valimail.com <mailto:seth@valimail.com>
> *p:*415.273.8818
>
>
> This email and all data transmitted with it contains confidential 
> and/or proprietary information intended solely for the use of 
> individual(s) authorized to receive it. If you are not an intended and 
> authorized recipient you are hereby notified of any use, disclosure, 
> copying or distribution of the information included in this 
> transmission is prohibited and may be unlawful. Please immediately 
> notify the sender by replying to this email and then delete it from 
> your system.
>

--------------321B764A515C7788CDAE896D
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>That text is not very clear to say the least. It's written in a
      very passive voice. What is wrong with the text I provided? It
      should be made very explicit like I did with what the
      responsibility of the sender and receiver is.</p>
    <p>Mike<br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 9:40 AM, Seth Blank wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOZAAfP7oMCtV_1E4+8kZS5Jb1C-nddR_QtLauF6shGY9z7Bqw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Michael, as an individual, I don't disagree. What's
        not clear about the current text?
        <div><br>
        </div>
        <div><a
            href="https://tools.ietf.org/html/rfc7489#section-7.2.1.1"
            moz-do-not-send="true">https://tools.ietf.org/html/rfc7489#section-7.2.1.1</a><br>
        </div>
        <div><br>
        </div>
        <div>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">   Email streams carrying DMARC feedback data MUST conform to the DMARC
   mechanism, thereby resulting in an aligned "pass" (see <a href="https://tools.ietf.org/html/rfc7489#section-3.1" moz-do-not-send="true">Section 3.1</a>).
   This practice minimizes the risk of report consumers processing
   fraudulent reports.</pre>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021 at 9:32
          AM Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
            moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p>Why is this controversial? Seriously. What is
              controversial about saying that the a report should
              authenticate? The onus is on the people who say it does
              not to lay out the case for why it's not a problem, not
              me. #98 has a simple piece of text to remedy this. it's
              2021. You don't use unauthenticated data if you can
              possibly help it.<br>
            </p>
            <p>Mike<br>
            </p>
            <div>On 1/25/21 9:25 AM, Seth Blank wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">Mike, how do you believe DMARC reports are
                consumed and utilized? I think you have a
                misunderstanding here which is why you're going down
                this path and everyone else is pushing back.</div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021
                  at 9:22 AM Michael Thomas &lt;<a
                    href="mailto:mike@mtcc.com" target="_blank"
                    moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div>
                    <p>Taking in information from unauthenticated
                      sources and acting on it is an operational problem
                      per se. Have we learned nothing in the last 30
                      years?</p>
                    <p>Mike<br>
                    </p>
                    <div>On 1/25/21 9:19 AM, Seth Blank wrote:<br>
                    </div>
                    <blockquote type="cite">
                      <div dir="ltr">What operational problem are we
                        solving here? Absent evidence of a problem and
                        strong consensus on the solution, let's close
                        these tickets and move on.</div>
                      <br>
                      <div class="gmail_quote">
                        <div dir="ltr" class="gmail_attr">On Mon, Jan
                          25, 2021 at 9:10 AM Douglas Foster &lt;<a
                            href="mailto:dougfoster.emailstandards@gmail.com"
                            target="_blank" moz-do-not-send="true">dougfoster.emailstandards@gmail.com</a>&gt;
                          wrote:<br>
                        </div>
                        <blockquote class="gmail_quote"
                          style="margin:0px 0px 0px
                          0.8ex;border-left:1px solid
                          rgb(204,204,204);padding-left:1ex">
                          <div dir="auto">Since the status quo is
                            unauthenticated, I wonder if adding a
                            signing requirement will help.
                            <div dir="auto">Will recipients discad
                              unsigned messages, or accept whatever is
                              available to maximize their information
                              capture?  I suspect they will conrinye to
                              accept everything.</div>
                            <div dir="auto"><br>
                            </div>
                            <div dir="auto">I think we would need an
                              identified threat before recipients would
                              be motivated to discard.</div>
                            <div dir="auto"><br>
                            </div>
                            <div dir="auto">But what about John's
                              problems with receiving reports that
                              should not have gone to him?   I did not
                              understand the root cause, but I would
                              hope there is something that can be done. 
                              Would signing help receiving sites, those
                              with less sophistication than he has, be
                              able to sort out noise more effectively?</div>
                            <div dir="auto"><br>
                            </div>
                          </div>
                          <br>
                          <div class="gmail_quote">
                            <div dir="ltr" class="gmail_attr">On Mon,
                              Jan 25, 2021, 11:51 AM Michael Thomas &lt;<a
                                href="mailto:mike@mtcc.com"
                                rel="noreferrer" target="_blank"
                                moz-do-not-send="true">mike@mtcc.com</a>&gt;
                              wrote:<br>
                            </div>
                            <blockquote class="gmail_quote"
                              style="margin:0px 0px 0px
                              0.8ex;border-left:1px solid
                              rgb(204,204,204);padding-left:1ex">
                              <div>
                                <p><br>
                                </p>
                                <div>On 1/25/21 8:44 AM, Todd Herr
                                  wrote:<br>
                                </div>
                                <blockquote type="cite">
                                  <div dir="ltr">
                                    <div dir="ltr">On Mon, Jan 25, 2021
                                      at 10:18 AM Michael Thomas &lt;<a
                                        href="mailto:mike@mtcc.com"
                                        rel="noreferrer noreferrer"
                                        target="_blank"
                                        moz-do-not-send="true">mike@mtcc.com</a>&gt;
                                      wrote:<br>
                                    </div>
                                    <div class="gmail_quote">
                                      <blockquote class="gmail_quote"
                                        style="margin:0px 0px 0px
                                        0.8ex;border-left:1px solid
                                        rgb(204,204,204);padding-left:1ex">
                                        <div><br>
                                          <p>The main thing I've learned
                                            over the years of dealing
                                            with security is to not
                                            underestimate what a
                                            motivated attacker can do.
                                            Your imagination is not the
                                            same as their imagination.
                                            Closing #98 in particular is
                                            absolutely ridiculous: the
                                            report should already have a
                                            DKIM signature or SPF so
                                            it's just a matter of making
                                            sure its valid. Why would
                                            you *not* want to insure
                                            that? The amount of
                                            justification for *not*
                                            having the receiver
                                            authenticate it is a
                                            mountain. The amount of
                                            effort to authenticate it is
                                            trivial for mail. Levine's
                                            dismissal of security
                                            concerns because he has
                                            anecdotal "evidence" from a
                                            backwater domain carries no
                                            weight at all.</p>
                                        </div>
                                      </blockquote>
                                      <div><br>
                                      </div>
                                      <div>That's all well and good, but
                                        you haven't answered the
                                        question I asked.</div>
                                      <div><br>
                                      </div>
                                      <div>What threats do you have in
                                        mind? Put another way, how do
                                        you envision an attacker
                                        exploiting the lack of
                                        authentication in a DMARC report
                                        to his or her gain?</div>
                                      <br>
                                    </div>
                                  </div>
                                </blockquote>
                                <p>No, sorry, the onus is on the people
                                  who don't think it can be gamed. A
                                  bald assertion that it can't be gamed
                                  is very unconvincing. You need to lay
                                  out a miles long case for why it
                                  cannot be gamed. And to what end? #98
                                  has a simple piece of text that should
                                  be added to DMARC to eliminate the
                                  possibility of forgery. You'd need a
                                  10 page threat I-D to explain why it's
                                  not necessary. What is the point of
                                  that? For email, it's trivial to
                                  prevent forgeries. Why would anybody
                                  argue against that?</p>
                                <p>Mike<br>
                                </p>
                              </div>
_______________________________________________<br>
                              dmarc mailing list<br>
                              <a href="mailto:dmarc@ietf.org"
                                rel="noreferrer noreferrer"
                                target="_blank" moz-do-not-send="true">dmarc@ietf.org</a><br>
                              <a
                                href="https://www.ietf.org/mailman/listinfo/dmarc"
                                rel="noreferrer noreferrer noreferrer"
                                target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
                            </blockquote>
                          </div>
_______________________________________________<br>
                          dmarc mailing list<br>
                          <a href="mailto:dmarc@ietf.org"
                            target="_blank" moz-do-not-send="true">dmarc@ietf.org</a><br>
                          <a
                            href="https://www.ietf.org/mailman/listinfo/dmarc"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
                        </blockquote>
                      </div>
                      <br clear="all">
                      <div><br>
                      </div>
                      -- <br>
                      <div dir="ltr"><span>
                          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
                          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
                            <div><span><b>p:</b></span><span>
                                415.273.8818 </span><span></span></div>
                          </span>
                          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
                          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
                          </p>
                          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
                              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
                        </span></div>
                    </blockquote>
                  </div>
                </blockquote>
              </div>
              <br clear="all">
              <div><br>
              </div>
              -- <br>
              <div dir="ltr"><span>
                  <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
                  <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
                    <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
                  </span>
                  <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
                  <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
                  </p>
                  <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
                      face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
                </span></div>
            </blockquote>
          </div>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"><span>
          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
          </span>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
        </span></div>
    </blockquote>
  </body>
</html>

--------------321B764A515C7788CDAE896D--


From nobody Mon Jan 25 09:53:39 2021
Return-Path: <mike@fresheez.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 8FD813A15FE for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 TblJs1S_Hf37 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:53:36 -0800 (PST)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E4453A1602 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:53:36 -0800 (PST)
Received: by mail-pl1-x632.google.com with SMTP id j21so3507798pls.7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:53:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=ZDTxfqhVlBE/CiOViaccH4vSzqTTZ2VcmbIqAD7Wa5U=; b=G2J/X7ZGZKJnT9m/ob7VD4shlNh1gereWd3gL3azbCbGbZGbUsiFo7kld/lm7PxFNo i6rZ0bps9q1NYJmk3YA7M+ZzbcKj+Vd20aaWOwxCeiO65iolRIMuJ5svBDLKwN51Ex2x XWodPA5QltGqGp28WTRvxmkjZCgu62Q0N2kdoFC4RlwwLS1U/KinAlhHv4EO7FXipn1/ yM0heYeTGxQ3+nm+wpI3Z49E5R9ivAJKoNte0pVuH0ccQXE0KXHyspdEqSUNXV0u1nx0 ziEQEszYeCTh6LmOVgHnH40qMTXUz9k9uSPfRl85qXrwFEt3DDbjf43OqeG1GG9yD01s EcVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=ZDTxfqhVlBE/CiOViaccH4vSzqTTZ2VcmbIqAD7Wa5U=; b=gWNNJAa3uQL2UFPb4Kr/agCvkMQNrvsa3yzHFN88FI2JqcCExdaIAAB+xme/Jnb2Yz WaCsP8dFQQt7DCzOGX5jv+XpvLBcLM+YTfVa5c0QVgRJlakhVz7R/lK3KyiDzz2oI+cM PC5+y14GQ4m6GS5fN8WVUUBecUp5MPyDt55nHhJbo02TRBD+4HBMSNwJAM1zvquYLRv2 HWjHNif5trq/M3r5oW57uHZeJcF3cGK7/JqIH9xUll8yvqAcd9ZI8teIlP6RyWZ3IuX/ 4bHB5c8UB+CdRwQtey9QZp1YyKQgfRTtFhG/69vKPqDAQv3B48Y6IUcWZ7wLxeB51Auh js0w==
X-Gm-Message-State: AOAM5303Ghk5Mc1uPtuhMBilrfzYBZfUMmxGL9GTkLch/O4GBLTMFO4F SF5GxMnm+BwiaPCLu0i4X33Btw==
X-Google-Smtp-Source: ABdhPJzR+g86Xtip1LZMpsn3ScNZQy4Up1kwePMXQ3kOSwgzlmQ8Plip4/hXd+CkdEt/0LZ4OplT6w==
X-Received: by 2002:a17:902:694c:b029:da:afba:beab with SMTP id k12-20020a170902694cb02900daafbabeabmr1660054plt.32.1611597216004;  Mon, 25 Jan 2021 09:53:36 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id b65sm18676006pga.54.2021.01.25.09.53.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 09:53:35 -0800 (PST)
To: Seth Blank <seth@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, Douglas Foster <dougfoster.emailstandards@gmail.com>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <dd98f7ca-1088-8a1a-c69d-e2b723543cb1@mtcc.com>
Date: Mon, 25 Jan 2021 09:53:33 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------D2A21DE13B0E8B6F4CEAE395"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Wxqc-T4CgQ0qbIcMH4uy8Jum4nM>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 17:53:38 -0000

This is a multi-part message in MIME format.
--------------D2A21DE13B0E8B6F4CEAE395
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

But just as an example, suppose I'm trying to get to a position to use 
p=reject, but some bad actor doesn't want me to do that so they can keep 
phishing me. All they have to do is keep sending forged message reports 
from gmail which makes me think I've got a problem. Seriously, this is 
not rocket science.

Mike

On 1/25/21 9:25 AM, Seth Blank wrote:
> Mike, how do you believe DMARC reports are consumed and utilized? I 
> think you have a misunderstanding here which is why you're going down 
> this path and everyone else is pushing back.
>
> On Mon, Jan 25, 2021 at 9:22 AM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>     Taking in information from unauthenticated sources and acting on
>     it is an operational problem per se. Have we learned nothing in
>     the last 30 years?
>
>     Mike
>
>     On 1/25/21 9:19 AM, Seth Blank wrote:
>>     What operational problem are we solving here? Absent evidence of
>>     a problem and strong consensus on the solution, let's close these
>>     tickets and move on.
>>
>>     On Mon, Jan 25, 2021 at 9:10 AM Douglas Foster
>>     <dougfoster.emailstandards@gmail.com
>>     <mailto:dougfoster.emailstandards@gmail.com>> wrote:
>>
>>         Since the status quo is unauthenticated, I wonder if adding a
>>         signing requirement will help.
>>         Will recipients discad unsigned messages, or accept whatever
>>         is available to maximize their information capture?  I
>>         suspect they will conrinye to accept everything.
>>
>>         I think we would need an identified threat before recipients
>>         would be motivated to discard.
>>
>>         But what about John's problems with receiving reports that
>>         should not have gone to him?   I did not understand the root
>>         cause, but I would hope there is something that can be done.
>>         Would signing help receiving sites, those with less
>>         sophistication than he has, be able to sort out noise more
>>         effectively?
>>
>>
>>         On Mon, Jan 25, 2021, 11:51 AM Michael Thomas <mike@mtcc.com
>>         <mailto:mike@mtcc.com>> wrote:
>>
>>
>>             On 1/25/21 8:44 AM, Todd Herr wrote:
>>>             On Mon, Jan 25, 2021 at 10:18 AM Michael Thomas
>>>             <mike@mtcc.com <mailto:mike@mtcc.com>> wrote:
>>>
>>>
>>>                 The main thing I've learned over the years of
>>>                 dealing with security is to not underestimate what a
>>>                 motivated attacker can do. Your imagination is not
>>>                 the same as their imagination. Closing #98 in
>>>                 particular is absolutely ridiculous: the report
>>>                 should already have a DKIM signature or SPF so it's
>>>                 just a matter of making sure its valid. Why would
>>>                 you *not* want to insure that? The amount of
>>>                 justification for *not* having the receiver
>>>                 authenticate it is a mountain. The amount of effort
>>>                 to authenticate it is trivial for mail. Levine's
>>>                 dismissal of security concerns because he has
>>>                 anecdotal "evidence" from a backwater domain carries
>>>                 no weight at all.
>>>
>>>
>>>             That's all well and good, but you haven't answered the
>>>             question I asked.
>>>
>>>             What threats do you have in mind? Put another way, how
>>>             do you envision an attacker exploiting the lack of
>>>             authentication in a DMARC report to his or her gain?
>>>
>>             No, sorry, the onus is on the people who don't think it
>>             can be gamed. A bald assertion that it can't be gamed is
>>             very unconvincing. You need to lay out a miles long case
>>             for why it cannot be gamed. And to what end? #98 has a
>>             simple piece of text that should be added to DMARC to
>>             eliminate the possibility of forgery. You'd need a 10
>>             page threat I-D to explain why it's not necessary. What
>>             is the point of that? For email, it's trivial to prevent
>>             forgeries. Why would anybody argue against that?
>>
>>             Mike
>>
>>             _______________________________________________
>>             dmarc mailing list
>>             dmarc@ietf.org <mailto:dmarc@ietf.org>
>>             https://www.ietf.org/mailman/listinfo/dmarc
>>             <https://www.ietf.org/mailman/listinfo/dmarc>
>>
>>         _______________________________________________
>>         dmarc mailing list
>>         dmarc@ietf.org <mailto:dmarc@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/dmarc
>>         <https://www.ietf.org/mailman/listinfo/dmarc>
>>
>>
>>
>>     -- 
>>     *Seth Blank*| VP, Standards and New Technologies
>>     *e:*seth@valimail.com <mailto:seth@valimail.com>
>>     *p:*415.273.8818
>>
>>
>>     This email and all data transmitted with it contains confidential
>>     and/or proprietary information intended solely for the use of
>>     individual(s) authorized to receive it. If you are not an
>>     intended and authorized recipient you are hereby notified of any
>>     use, disclosure, copying or distribution of the information
>>     included in this transmission is prohibited and may be unlawful.
>>     Please immediately notify the sender by replying to this email
>>     and then delete it from your system.
>>
>
>
> -- 
> *Seth Blank*| VP, Standards and New Technologies
> *e:*seth@valimail.com <mailto:seth@valimail.com>
> *p:*415.273.8818
>
>
> This email and all data transmitted with it contains confidential 
> and/or proprietary information intended solely for the use of 
> individual(s) authorized to receive it. If you are not an intended and 
> authorized recipient you are hereby notified of any use, disclosure, 
> copying or distribution of the information included in this 
> transmission is prohibited and may be unlawful. Please immediately 
> notify the sender by replying to this email and then delete it from 
> your system.
>

--------------D2A21DE13B0E8B6F4CEAE395
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>But just as an example, suppose I'm trying to get to a position
      to use p=reject, but some bad actor doesn't want me to do that so
      they can keep phishing me. All they have to do is keep sending
      forged message reports from gmail which makes me think I've got a
      problem. Seriously, this is not rocket science.<br>
    </p>
    <p>Mike<br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 9:25 AM, Seth Blank wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Mike, how do you believe DMARC reports are consumed
        and utilized? I think you have a misunderstanding here which is
        why you're going down this path and everyone else is pushing
        back.</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021 at 9:22
          AM Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
            moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p>Taking in information from unauthenticated sources and
              acting on it is an operational problem per se. Have we
              learned nothing in the last 30 years?</p>
            <p>Mike<br>
            </p>
            <div>On 1/25/21 9:19 AM, Seth Blank wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">What operational problem are we solving
                here? Absent evidence of a problem and strong consensus
                on the solution, let's close these tickets and move on.</div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021
                  at 9:10 AM Douglas Foster &lt;<a
                    href="mailto:dougfoster.emailstandards@gmail.com"
                    target="_blank" moz-do-not-send="true">dougfoster.emailstandards@gmail.com</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div dir="auto">Since the status quo is
                    unauthenticated, I wonder if adding a signing
                    requirement will help.
                    <div dir="auto">Will recipients discad unsigned
                      messages, or accept whatever is available to
                      maximize their information capture?  I suspect
                      they will conrinye to accept everything.</div>
                    <div dir="auto"><br>
                    </div>
                    <div dir="auto">I think we would need an identified
                      threat before recipients would be motivated to
                      discard.</div>
                    <div dir="auto"><br>
                    </div>
                    <div dir="auto">But what about John's problems with
                      receiving reports that should not have gone to
                      him?   I did not understand the root cause, but I
                      would hope there is something that can be done. 
                      Would signing help receiving sites, those with
                      less sophistication than he has, be able to sort
                      out noise more effectively?</div>
                    <div dir="auto"><br>
                    </div>
                  </div>
                  <br>
                  <div class="gmail_quote">
                    <div dir="ltr" class="gmail_attr">On Mon, Jan 25,
                      2021, 11:51 AM Michael Thomas &lt;<a
                        href="mailto:mike@mtcc.com" rel="noreferrer"
                        target="_blank" moz-do-not-send="true">mike@mtcc.com</a>&gt;
                      wrote:<br>
                    </div>
                    <blockquote class="gmail_quote" style="margin:0px
                      0px 0px 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex">
                      <div>
                        <p><br>
                        </p>
                        <div>On 1/25/21 8:44 AM, Todd Herr wrote:<br>
                        </div>
                        <blockquote type="cite">
                          <div dir="ltr">
                            <div dir="ltr">On Mon, Jan 25, 2021 at 10:18
                              AM Michael Thomas &lt;<a
                                href="mailto:mike@mtcc.com"
                                rel="noreferrer noreferrer"
                                target="_blank" moz-do-not-send="true">mike@mtcc.com</a>&gt;
                              wrote:<br>
                            </div>
                            <div class="gmail_quote">
                              <blockquote class="gmail_quote"
                                style="margin:0px 0px 0px
                                0.8ex;border-left:1px solid
                                rgb(204,204,204);padding-left:1ex">
                                <div><br>
                                  <p>The main thing I've learned over
                                    the years of dealing with security
                                    is to not underestimate what a
                                    motivated attacker can do. Your
                                    imagination is not the same as their
                                    imagination. Closing #98 in
                                    particular is absolutely ridiculous:
                                    the report should already have a
                                    DKIM signature or SPF so it's just a
                                    matter of making sure its valid. Why
                                    would you *not* want to insure that?
                                    The amount of justification for
                                    *not* having the receiver
                                    authenticate it is a mountain. The
                                    amount of effort to authenticate it
                                    is trivial for mail. Levine's
                                    dismissal of security concerns
                                    because he has anecdotal "evidence"
                                    from a backwater domain carries no
                                    weight at all.</p>
                                </div>
                              </blockquote>
                              <div><br>
                              </div>
                              <div>That's all well and good, but you
                                haven't answered the question I asked.</div>
                              <div><br>
                              </div>
                              <div>What threats do you have in mind? Put
                                another way, how do you envision an
                                attacker exploiting the lack of
                                authentication in a DMARC report to his
                                or her gain?</div>
                              <br>
                            </div>
                          </div>
                        </blockquote>
                        <p>No, sorry, the onus is on the people who
                          don't think it can be gamed. A bald assertion
                          that it can't be gamed is very unconvincing.
                          You need to lay out a miles long case for why
                          it cannot be gamed. And to what end? #98 has a
                          simple piece of text that should be added to
                          DMARC to eliminate the possibility of forgery.
                          You'd need a 10 page threat I-D to explain why
                          it's not necessary. What is the point of that?
                          For email, it's trivial to prevent forgeries.
                          Why would anybody argue against that?</p>
                        <p>Mike<br>
                        </p>
                      </div>
                      _______________________________________________<br>
                      dmarc mailing list<br>
                      <a href="mailto:dmarc@ietf.org" rel="noreferrer
                        noreferrer" target="_blank"
                        moz-do-not-send="true">dmarc@ietf.org</a><br>
                      <a
                        href="https://www.ietf.org/mailman/listinfo/dmarc"
                        rel="noreferrer noreferrer noreferrer"
                        target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
                    </blockquote>
                  </div>
                  _______________________________________________<br>
                  dmarc mailing list<br>
                  <a href="mailto:dmarc@ietf.org" target="_blank"
                    moz-do-not-send="true">dmarc@ietf.org</a><br>
                  <a href="https://www.ietf.org/mailman/listinfo/dmarc"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
                </blockquote>
              </div>
              <br clear="all">
              <div><br>
              </div>
              -- <br>
              <div dir="ltr"><span>
                  <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
                  <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
                    <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
                  </span>
                  <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
                  <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
                  </p>
                  <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
                      face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
                </span></div>
            </blockquote>
          </div>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"><span>
          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
          </span>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
        </span></div>
    </blockquote>
  </body>
</html>

--------------D2A21DE13B0E8B6F4CEAE395--


From nobody Mon Jan 25 09:58:34 2021
Return-Path: <johnl@iecc.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 597A43A1639 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:58:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=HtFTHhrq; dkim=pass (2048-bit key) header.d=taugh.com header.b=ku4Ifa9K
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 VmqyhYihD0oU for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:58:30 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 C204B3A161D for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:58:27 -0800 (PST)
Received: (qmail 68088 invoked from network); 25 Jan 2021 17:58:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=109f5.600f06c2.k2101; bh=p73ciA6isC4qn3jtwJ07wEuH1mxRi7CwylIUNs2EVJI=; b=HtFTHhrqRU0ZjH8qkRdOnz0TnQ6nijL3Wqg+vJ3EonOs/PNESeWZEtHQCKib3X0zSBG3Q4QEH38pwRsdqO3bMbZG6EFPXMeSNwfTe6xU21omz6UG58MQQnPuys//rakwE24C9kNh4BCprjnDNtVYSa4GVIpxZT0AA0K98cLzEwm9XWhgp+RJt76QpXiBrK9YLCo/A2UNZNbq9mmGFv+qFtd2rtVVNbV28Sc+jGGtSOUjiV4XOFz2ouFL4XxZp4jj+PMECt9xm4B+zd8isRHTmvPQSOtGlKT0nHwbze9kvK2zHxVO9ZWFknSIZtNmVuhnLd3OdaB7IsdRpOK6vPLpaQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=109f5.600f06c2.k2101; bh=p73ciA6isC4qn3jtwJ07wEuH1mxRi7CwylIUNs2EVJI=; b=ku4Ifa9KrnhtWGY4/c9opKf7cfgjem9qwQNsNyM7bZx+7JVH7GZvVgnBQUtThirZxxUayBC+SPXEbiOmDB4Tr9DngKx94r02iV0RDa6gPqFGDThijv8KNB4LmKs3UqwPWGUIbAD6ZHXkX2I11eBujf4SFGZpG8F2mb5IJFRgEWO1TO41PXn52gEXjtvL4dbzMzosB2sM6M3v9+CfoPjQvCjiHDpmmTV/RLka5K9jVxBtlaXoVw0DCeTdR9aGLnELUUBXT2VH4s9CruAd2jn7bf+HyFExdchXRxHDpZAvRp7yrL8C3P6eIEaOrPrpm8EZd3wYOZM0pI77nlsLeF5T4A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 17:58:26 -0000
Received: by ary.qy (Postfix, from userid 501) id 03E766C12FF3; Mon, 25 Jan 2021 12:58:25 -0500 (EST)
Date: 25 Jan 2021 12:58:25 -0500
Message-Id: <20210125175826.03E766C12FF3@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dilyan.palauzov@aegee.org
In-Reply-To: <A551B531-BFCA-466A-8E8D-4EA4EF9FC82C@aegee.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/czgVZGvBw4UEzT0CzVIBuab7zh4>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 17:58:32 -0000

In article <A551B531-BFCA-466A-8E8D-4EA4EF9FC82C@aegee.org> you write:
>lets say a site signs an email with both rsa and ed25519 algorithms.  This site wants to know, whether the recipient can
>validate the ed25519 signatures, so that in the future rsa signing for that receiving site can be skipped (or errors in the
>ed25519 implementation fixed).

That strikes me as severe mission creep. It's something you certainly
might want to know, but it's not DMARC's job to solve it.


-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Mon Jan 25 09:59:57 2021
Return-Path: <Alex_Brotman@comcast.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 20F273A1643 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:59:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.com
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 p3TLpEfM9vWh for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 09:59:32 -0800 (PST)
Received: from mx0b-00143702.pphosted.com (mx0b-00143702.pphosted.com [148.163.141.77]) (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 BFF4D3A1645 for <dmarc@ietf.org>; Mon, 25 Jan 2021 09:59:31 -0800 (PST)
Received: from pps.filterd (m0184891.ppops.net [127.0.0.1]) by mx0b-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10PHvjKh026834; Mon, 25 Jan 2021 12:59:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=20190412; bh=vaJHtDlhkkN0zPfJtGqwDtgIgYVKiFaUUkW9IBv+MdY=; b=mT8WqljNWNTYtd6EIHb3geGexxFEx8zdEk4gj1w+MDVZQYOQDj8Rb46FwjnLtbwoXatl MkA0BEm/M7fJ2dYL0cOdjDAMd1n5nhP4Rw6PbIQVL3DtU4pHyjkS1yD5HvAzYFC0dnTo Le42etk2read1XyfUlkp6lB299ESAmyINdG7473Ys3s2zHVrqbcVSGW5ZxHK2KuX6VP+ hLOSdpRkhgBx90OX0kbogsoccVDzU4yX7dCI8FuxBW0MRQ0njB6zEvriHt+OTigajZDB NeVxYv9iOwYAr0bH8QoawU8b0tlbn7IdiNG0nfxrpPT7Qg/wKUpHgCov9+ureWU9qH+q aw== 
Received: from pacdcex56.cable.comcast.com (dlppfpt-wc-1p.slb.comcast.com [96.99.226.136]) by mx0b-00143702.pphosted.com with ESMTP id 368jqabaxc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 25 Jan 2021 12:59:30 -0500
Received: from PACDCEX49.cable.comcast.com (24.40.2.148) by PACDCEX56.cable.comcast.com (24.40.2.155) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Jan 2021 12:59:28 -0500
Received: from PACDCEXEDGE01.cable.comcast.com (76.96.78.71) by PACDCEX49.cable.comcast.com (24.40.2.148) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 25 Jan 2021 12:59:28 -0500
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.172) by webmail.comcast.com (76.96.78.71) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Jan 2021 12:59:17 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by BL0PR11MB3444.namprd11.prod.outlook.com (2603:10b6:208:6f::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.15; Mon, 25 Jan 2021 17:59:17 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42%7]) with mapi id 15.20.3784.017; Mon, 25 Jan 2021 17:59:16 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
Thread-Index: AdbysIxA8zFO9cEQSfqEK/Gf/4kCJwAGWaOAAB4tRFA=
Date: Mon, 25 Jan 2021 17:59:16 +0000
Message-ID: <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com>
In-Reply-To: <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:a15b:1edf:6851:816e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 090bb6cf-099d-476e-5086-08d8c15aeec0
x-ms-traffictypediagnostic: BL0PR11MB3444:
x-microsoft-antispam-prvs: <BL0PR11MB344491D3B5DBEE40EAE81986F7BD9@BL0PR11MB3444.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:159;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: v1VVLZ4w9BSRDpXsojdbq4mcHbzwHPuQg3BQ+C825cQRQOhpldZafrrMeSv/kY7QmwsU+nFKoYC63D0FwWi4oWQhzvLoRkr365UHNJ9o+lSel3D8G8lgpU9AKZVaPncH2A3mokdDnelm4rWiMm7soqvVVGEVQVei6/URVrPukdeH79d5/O4wYYZyS5uenFOzJF0NLF1bDzzdocyqvB+vWcwut05oPAHNiIc7W6DZ8OiTfSqZpRWxXcmCOjXfNwiPeMSXNhobdAgPH5dgMcXEzHdiiF5tjpnWf6UAL3kpjk2XEBkSibMlHZ2vKVWZIKRya1RTDe6mInlXN7N8Iq+peaHZOY8JefuflivUB0pRjuI6/s49O9/GdcpL/QX6UJV4J85hQUG8Hma0k+Zbh+3XWL68JXvf0OBgBJXaJqq9PUIo1f35KieySqQmDsaQ6yy8bUYsxNFtSxKtfYAnDMDavQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(376002)(366004)(136003)(396003)(39860400002)(86362001)(8936002)(66476007)(186003)(5660300002)(110136005)(66556008)(66446008)(966005)(53546011)(71200400001)(64756008)(83380400001)(478600001)(166002)(55016002)(76116006)(316002)(9686003)(6506007)(52536014)(66946007)(8676002)(7696005)(33656002)(2906002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: 6efwXVfNUNeJFNEP4w7nd5n4/KAJxXE03mJ2m7+OmxKBKnMZlltdauN/pdRJ/B4joR85ACfuPND3KrhiUEEXiY9F9N3ydWMTWLvQv4ZB9WktT+es+SXeMhuwavXc6NL8aCGhRhA0jSH33S6i9uJLAtFNvLEzMB1b8fQu4+qIZj+3rWwFuMEEgSxm/NNmKQ8F/CkTBqB4XDLv3zl51WTDanOLXEywQ2M2pDtScqA7NssqIR+6C+0JDMsIjkjPZuPwYThTxfYOSJuw2INDTnEykaNAcjMq2I17TybowU5FCD+rNykq/zxrTeldxptH2LC6wSE+I3d1pa0rnG15gSkRT+bhb2oqqmVwgbANfba4/822CHxjUPU9KsPyIF2S9o22IjJPCe48DAqDofdeHRU7ho5SjbABZs3ppeTZJUJuq4kC06O/WHOjCW3xg/Ki2IMGfdiAok5a84t9WJuIlhftOvDrHFZM5RC4KXthzTbN5r+yiDQPoJHYEQaDohcylLKAYKvsHsId5I6EGcRujDe16c4fZphfWybpUIklP9WSbapFbp/fKcaFzyvxyJ0nPcTUrE1g0qvgXMbSDad+bvnOuTkm3hrSKlK4fuxVynaM9xmsMGZWcF/Bdd5SWPvqaLnPm83sevEgq6uJfQ/wx3M780HkTVuKxqPSFkOAc9yixJode/bx1VBlmQtqDe8KH6mZYZnBguYP+gF6Q8Oe1hM6Y1McHIZWJXuxv5S+cBoOb/MDQ4qBuPKG3dZLWH846+CP0djsqTon30x9v7SJ3b2EcbLWzm9T8InrxFlkDv/dOx0=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bmisAF+Gq/P6kd7IOTkqZdbblu8xc9JaaAI69TCsOzcjAIk2vC/tEmUizYMuKkY9QKBvL8VC8a3QWmYYn/MR4cqa+l+T/gyb44mJHKrrjLjqU2fEvFx9TDNxMfFFDL9QJ2pRW9kVhjpuxCyCj4eFa2VMWZO/q3ia2h8kblPUwTGjowt31T4NCHKwJ6SBabtadVM84NZUbpnyDDIHWF+yfRHraa61/Iv5lj+OUF2kule+RHVAvVlSkH4Oo/+fWj3UjdeoWBc4+Rl9w2URdxxF9UdnJ7e7Je10L14rh0TCETHPX93IuhadBAOPk0XFuvKTayC8hhZ3vviiho+o7XC4vQ==
arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kfscsfj2fyK8/2OP/qySMgC0wCAoDSw79b7UAhqAxWU=; b=CnAfLzvTkExwQphS0NfKgb/p/T93x7kGGciFs9kjX37pxA4ebrNnmVPNcMnMUVobDryEs8EglG1TjvPbKOoR6jkoPuirsgw1IYIiXvzpSZ2c6cIa/TspUuKhuuyp6PFeyfW4TO6p2Qlj3jwfvCcJbbaA9GwaAs4P1R+nTGncpKBFk6ExM72xxXkbr+EIeEFZXwAksLIDx6za+QFbc11yvEN7y2BuvNtIJH/02Dhsy+jXssv3NkAI42Psey7FoDBm3IWn4WbLTpK3Y6nPeKTxjhXcJi9yqX0d+yBSAQOYD3RCJEQAc3g15CpYCtGOvxFj/x8kB/OCp9ZD/D6cjy2glQ==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=comcast.com; dmarc=pass action=none header.from=comcast.com; dkim=pass header.d=comcast.com; arc=none
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: MN2PR11MB4351.namprd11.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: 090bb6cf-099d-476e-5086-08d8c15aeec0
x-ms-exchange-crosstenant-originalarrivaltime: 25 Jan 2021 17:59:16.8804 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 906aefe9-76a7-4f65-b82d-5ec20775d5aa
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: 3Kfn7AmJ2klG8f41G5D3VHL7sM9AVedBB4InhLIwjWb0/UYFA/Grs3tHQ/VUrvOSDk6GpzXLuBDtEnYnNp9GB/LgkWsPg0C0IZGL0iiGAPs=
x-ms-exchange-transport-crosstenantheadersstamped: BL0PR11MB3444
x-originatororg: comcast.com
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB43513C20B5A598496FFBA4AAF7BD9MN2PR11MB4351namp_"
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWH
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-25_07:2021-01-25, 2021-01-25 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/6jpMee-_gz0yKrsVd_2ATqtrAfU>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 17:59:34 -0000

--_000_MN2PR11MB43513C20B5A598496FFBA4AAF7BD9MN2PR11MB4351namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RG91ZywNCg0KQW5kIEkgZG9u4oCZdCB0aGluayB3aGF0IHlvdeKAmXJlIGRvaW5nIGlzIG5lY2Vz
c2FyaWx5IGJhZCBmcm9tIGFuIG9wZXJhdGlvbmFsIHN0YW5kcG9pbnQuICBJIHRoaW5rIHRoZSBx
dWVzdGlvbiBjZW50ZXJzIGFyb3VuZCB3aGV0aGVyIHRoYXQgYWxpZ25pbmcgc2lnbmF0dXJlIGlz
IHN1ZmZpY2llbnQsIG9yIHNob3VsZCB5b3UgcmVwb3J0IGFsbCB0aGUgc2lnbmF0dXJlcyB0aGUg
cmVjZWl2ZXIgYXR0ZW1wdGVkIHRvIHZlcmlmeT8gIEnigJltIG5vdCBzdWdnZXN0aW5nIHRoYXQg
d2UgYWRkIGFueXRoaW5nIHRoYXQgd291bGQgcmVwb3J0IOKAnFNpZ25hdHVyZSB2YWxpZGF0aW9u
IG5vdCBhdHRlbXB0ZWTigJ0sIHRoYXQgc291bmRzIGhvcnJpYmxlLiAgV2lsbCB0aGUgb3JpZ2lu
YWwgc291cmNlIHBvdGVudGlhbGx5IGNhcmUgdGhhdCB0aGUgbWVzc2FnZSB3YXMgc2lnbmVkIGlu
IHRocmVlIG90aGVyIHBsYWNlcyBhcyB0aGUgbWVzc2FnZSBib3VuY2VkIGFyb3VuZD8gIFNob3Vs
ZCB3ZSBwdXQgdGhlIG9udXMgb24gdGhlIHJlcG9ydGluZyBlbnRpdHkgdG8gZG8gdGhlIGZpbHRl
ciBvdXQgdGhlIG5vbi1hbGlnbmVkICh3aGF0IGlmIG5vbmUgYWxpZ25lZCkgc2lnbmF0dXJlcywg
b3IganVzdCByZWFsaXplIGl04oCZcyBzb21lIGF1dG9tYXRlZCBqb2IgYW5kIGluY2x1ZGluZyBh
bGwgbG9nZ2VkL3ZhbGlkYXRlZCBzaWduYXR1cmVzIGlzIHRoZSBiZXR0ZXIgd2F5Pw0KDQotLQ0K
QWxleCBCcm90bWFuDQpTci4gRW5naW5lZXIsIEFudGktQWJ1c2UgJiBNZXNzYWdpbmcgUG9saWN5
DQpDb21jYXN0DQoNCkZyb206IGRtYXJjIDxkbWFyYy1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhh
bGYgT2YgRG91Z2xhcyBGb3N0ZXINClNlbnQ6IFN1bmRheSwgSmFudWFyeSAyNCwgMjAyMSAxMDoy
NyBQTQ0KVG86IElFVEYgRE1BUkMgV0cgPGRtYXJjQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFtk
bWFyYy1pZXRmXSBXaGljaCBES0lNKHMpIHNob3VsZCBiZSByZXBvcnRlZD8gKFRpY2tldCAjMzgp
DQoNCkN1cnJlbnRseSwgbXkgZmlsdGVyIG9ubHkgZXZhbHVhdGVzIHNpZ25hdHVyZXMgdGhhdCBh
cmUgcmVsZXZhbnQgdG8gRnJvbSBhbGlnbm1lbnQsIGFuZCBzdG9wcyBhZnRlciB0aGUgZmlyc3Qg
c3VjY2Vzcy4gICBGb3IgdGhhdCBkZWNpc2lvbiBwcm9jZXNzLCBhbGwgdGhhdCBJIG5lZWQgcmV0
dXJuZWQgKGFuZCBzdG9yZWQpIGlzIGEgUGFzcy9GYWlsIHJlc3VsdDsgSSBkb24ndCBuZWVkIHRo
ZSBkZXRhaWxzIG9mIHRoZSBhbGdvcml0aG0gZXZhbHVhdGVkLiAgQW55IGFkZGl0aW9uYWwgaW5m
b3JtYXRpb24gY29sbGVjdGlvbiBpcyBmb3IgdGhlIGJlbmVmaXQgb2Ygc29tZW9uZSBlbHNlLCBu
b3QgdGhlIG5lZWRzIG9mIG15IG93biBvcmdhbml6YXRpb24uDQoNClRoZSBidXJkZW4gb2YgZGF0
YSBjb2xsZWN0aW9uIGlzIHByb3BvcnRpb25hdGUgIHRvIHRoZSBhbW91bnQgb2YgZGF0YSBjb2xs
ZWN0ZWQuICBETUFSQyByZXBvcnRpbmcgaXMgYSBjb3VydGVzeSBzZXJ2aWNlIGZyb20gdGhlIGRh
dGEgY29sbGVjdG9yIHRvIHRoZSBkb21haW4gb3duZXIuICBFYWNoIGVmZm9ydCB0byBpbmNyZWFz
ZSB0aGUgcHJlY2lzaW9uIG9mIHRoZSBkYXRhIG1heSByZWR1Y2UgdGhlIG51bWJlciBvZiBkb21h
aW5zIHdpbGxpbmcgdG8gcHJvdmlkZSB0aGF0IGluZm9ybWF0aW9uLg0KDQpJIHN1Z2dlc3QgdGhh
dCB3ZSBuZWVkIHJlcG9ydCBjb25zdW1lcnMgaW4gdGhpcyBncm91cCB0byBkaXNjdXNzIGhvdyB0
aGV5IHVzZSB0aGUgY3VycmVudCBkYXRhIGFuZCB0aGUgcHJvcG9zZWQgYWRkaXRpb25zIHRvIHRo
YXQgZGF0YSwgc28gdGhhdCBhIGNvc3QvYmVuZWZpdCBhc3Nlc3NtZW50IGNhbiBiZSBtYWRlLiAg
IEF0IGxlYXN0IHNvbWUgb2YgdGhhdCBqdXN0aWZpY2F0aW9uIHNob3VsZCBiZSBpbmNsdWRlZCBp
biB0aGUgZmluYWwgZG9jdW1lbnQsIHNpbmNlIG9uZSBwdXJwb3NlIG9mIHRoYXQgZG9jdW1lbnQg
d2lsbCBiZSB0byBjb252aW5jZSBub24tcmVwb3J0aW5nIGVudGl0aWVzIHRvIGJlZ2luIHNlbmRp
bmcgcmVwb3J0cy4NCg0KRG91ZyBGb3N0ZXINCg0KDQpPbiBTdW4sIEphbiAyNCwgMjAyMSBhdCA3
OjI1IFBNIEJyb3RtYW4sIEFsZXggPEFsZXhfQnJvdG1hbj00MGNvbWNhc3QuY29tQGRtYXJjLmll
dGYub3JnPG1haWx0bzo0MGNvbWNhc3QuY29tQGRtYXJjLmlldGYub3JnPj4gd3JvdGU6DQpIZWxs
byBmb2xrcywNCg0KU29tZSB0aW1lIGFnbywgYW4gaXNzdWVbMV0gd2FzIGJyb3VnaHQgdG8gdGhl
IGxpc3Qgd2hlcmUgd2hpY2ggREtJTShzKSBiZWluZyByZXBvcnRlZCBpcyBub3QgY2xlYXIgaW4g
UkZDNzQ4OSBbMl0uICBUaGVyZSB3YXMgYSBzaG9ydCBkaXNjdXNzaW9uLCB0aG91Z2ggbm8gY2xl
YXIgcmVzb2x1dGlvbiBiZWZvcmUgY29udmVyc2F0aW9uIHRyYWlsZWQgb2ZmLiAgSXQgc2VlbXMg
bGlrZSB0aGVyZSB3ZXJlIHBvaW50cyB0aGF0IG1heSBuZWVkIHRvIGJlIGRpc2N1c3NlZC4gIE9u
ZSB3YXMgd2hldGhlciB0aGUgcmVwb3J0aW5nIFNIT1VMRCByZXBvcnQgYWxsIHNpZ25hdHVyZXMs
IHJlZ2FyZGxlc3Mgb2YgYWxpZ25tZW50IG9yIHZhbGlkaXR5LCBvciBwZXJoYXBzIGp1c3QgdGhl
IG9uZSB0aGF0IGFsaWducyAoaWYgdGhlcmUgaXMgb25lKS4gIFRoZXJlIHdhcyBhbHNvIGFub3Ro
ZXIgcXVlc3Rpb24gaWYgdGhlcmUgc2hvdWxkIGJlIGEgbGltaXQgdG8gdGhlIG51bWJlciBvZiBz
aWduYXR1cmVzIHJlcG9ydGVkIHNvIHRoYXQgaXQgcmVtYWlucyBzYW5lLg0KDQpXZSdkIGxpa2Ug
dG8gdHJ5IHRvIGdldCB0aGlzIHJlc29sdmVkIHdpdGhpbiBhYm91dCB0d28gd2Vla3MuICBUaGFu
ayB5b3UgZm9yIHlvdXIgZmVlZGJhY2suDQoNCjE6IGh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5v
cmcvYXJjaC9tc2cvZG1hcmMvOS1WNTk2eWwyQkJhVXpDTmFEWkIxVGcxczRjLzxodHRwczovL3Vy
bGRlZmVuc2UuY29tL3YzL19faHR0cHM6L21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL2Rt
YXJjLzktVjU5NnlsMkJCYVV6Q05hRFpCMVRnMXM0Yy9fXzshIUNRbDNtY0hYMkEhUXBvLWtmSnZf
NVV4RFV6Z0lCUm9ySWR4ejdDZXRkUnBGWmRKR3NicDEtamFqQktvSFA0VVU3Q3pyMGx6c1JSczYx
em96bFlpWXckPg0KMjogaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzc0ODkjc2VjdGlv
bi03LjI8aHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHBzOi90b29scy5pZXRmLm9yZy9o
dG1sL3JmYzc0ODkqc2VjdGlvbi03LjJfXztJdyEhQ1FsM21jSFgyQSFRcG8ta2ZKdl81VXhEVXpn
SUJSb3JJZHh6N0NldGRScEZaZEpHc2JwMS1qYWpCS29IUDRVVTdDenIwbHpzUlJzNjF5SXg3LWJK
dyQ+DQoNCi0tDQpBbGV4IEJyb3RtYW4NClNyLiBFbmdpbmVlciwgQW50aS1BYnVzZSAmIE1lc3Nh
Z2luZyBQb2xpY3kNCkNvbWNhc3QNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCmRtYXJjIG1haWxpbmcgbGlzdA0KZG1hcmNAaWV0Zi5vcmc8bWFpbHRv
OmRtYXJjQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9k
bWFyYzxodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cHM6L3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2RtYXJjX187ISFDUWwzbWNIWDJBIVFwby1rZkp2XzVVeERVemdJQlJvcklk
eHo3Q2V0ZFJwRlpkSkdzYnAxLWphakJLb0hQNFVVN0N6cjBsenNSUnM2MXdNbnQ1VVRRJD4NCg==

--_000_MN2PR11MB43513C20B5A598496FFBA4AAF7BD9MN2PR11MB4351namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndp
bmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24x
DQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBzdHlsZT0id29yZC13
cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkRvdWcsPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFuZCBJIGRvbuKAmXQgdGhp
bmsgd2hhdCB5b3XigJlyZSBkb2luZyBpcyBuZWNlc3NhcmlseSBiYWQgZnJvbSBhbiBvcGVyYXRp
b25hbCBzdGFuZHBvaW50LiZuYnNwOyBJIHRoaW5rIHRoZSBxdWVzdGlvbiBjZW50ZXJzIGFyb3Vu
ZCB3aGV0aGVyIHRoYXQgYWxpZ25pbmcgc2lnbmF0dXJlIGlzIHN1ZmZpY2llbnQsIG9yIHNob3Vs
ZCB5b3UgcmVwb3J0IGFsbCB0aGUgc2lnbmF0dXJlcyB0aGUgcmVjZWl2ZXIgYXR0ZW1wdGVkIHRv
DQogdmVyaWZ5PyZuYnNwOyBJ4oCZbSBub3Qgc3VnZ2VzdGluZyB0aGF0IHdlIGFkZCBhbnl0aGlu
ZyB0aGF0IHdvdWxkIHJlcG9ydCDigJxTaWduYXR1cmUgdmFsaWRhdGlvbiBub3QgYXR0ZW1wdGVk
4oCdLCB0aGF0IHNvdW5kcyBob3JyaWJsZS4mbmJzcDsgV2lsbCB0aGUgb3JpZ2luYWwgc291cmNl
IHBvdGVudGlhbGx5IGNhcmUgdGhhdCB0aGUgbWVzc2FnZSB3YXMgc2lnbmVkIGluIHRocmVlIG90
aGVyIHBsYWNlcyBhcyB0aGUgbWVzc2FnZSBib3VuY2VkIGFyb3VuZD8mbmJzcDsgU2hvdWxkDQog
d2UgcHV0IHRoZSBvbnVzIG9uIHRoZSByZXBvcnRpbmcgZW50aXR5IHRvIGRvIHRoZSBmaWx0ZXIg
b3V0IHRoZSBub24tYWxpZ25lZCAod2hhdCBpZiBub25lIGFsaWduZWQpIHNpZ25hdHVyZXMsIG9y
IGp1c3QgcmVhbGl6ZSBpdOKAmXMgc29tZSBhdXRvbWF0ZWQgam9iIGFuZCBpbmNsdWRpbmcgYWxs
IGxvZ2dlZC92YWxpZGF0ZWQgc2lnbmF0dXJlcyBpcyB0aGUgYmV0dGVyIHdheT88bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+LS08bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFs
ZXggQnJvdG1hbjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U3IuIEVuZ2lu
ZWVyLCBBbnRpLUFidXNlICZhbXA7IE1lc3NhZ2luZyBQb2xpY3k8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkNvbWNhc3Q8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxk
aXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4w
cHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5G
cm9tOjwvYj4gZG1hcmMgJmx0O2RtYXJjLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IDxiPk9uIEJlaGFs
ZiBPZiA8L2I+DQpEb3VnbGFzIEZvc3Rlcjxicj4NCjxiPlNlbnQ6PC9iPiBTdW5kYXksIEphbnVh
cnkgMjQsIDIwMjEgMTA6MjcgUE08YnI+DQo8Yj5Ubzo8L2I+IElFVEYgRE1BUkMgV0cgJmx0O2Rt
YXJjQGlldGYub3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW2RtYXJjLWlldGZdIFdo
aWNoIERLSU0ocykgc2hvdWxkIGJlIHJlcG9ydGVkPyAoVGlja2V0ICMzOCk8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5DdXJyZW50bHksIG15IGZpbHRlciBv
bmx5IGV2YWx1YXRlcyBzaWduYXR1cmVzIHRoYXQgYXJlIHJlbGV2YW50IHRvIEZyb20gYWxpZ25t
ZW50LCBhbmQgc3RvcHMgYWZ0ZXIgdGhlIGZpcnN0IHN1Y2Nlc3MuJm5ic3A7ICZuYnNwO0ZvciB0
aGF0IGRlY2lzaW9uIHByb2Nlc3MsIGFsbCB0aGF0IEkgbmVlZCByZXR1cm5lZCAoYW5kIHN0b3Jl
ZCkgaXMgYSBQYXNzL0ZhaWwgcmVzdWx0OyBJIGRvbid0IG5lZWQgdGhlIGRldGFpbHMgb2YNCiB0
aGUgYWxnb3JpdGhtIGV2YWx1YXRlZC4mbmJzcDsgQW55IGFkZGl0aW9uYWwgaW5mb3JtYXRpb24g
Y29sbGVjdGlvbiBpcyBmb3IgdGhlIGJlbmVmaXQgb2Ygc29tZW9uZSBlbHNlLCBub3QgdGhlIG5l
ZWRzIG9mIG15IG93biBvcmdhbml6YXRpb24uPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5UaGUgYnVyZGVuIG9mIGRhdGEgY29sbGVjdGlvbiBpcyBwcm9wb3J0
aW9uYXRlJm5ic3A7IHRvIHRoZSBhbW91bnQgb2YgZGF0YSBjb2xsZWN0ZWQuJm5ic3A7IERNQVJD
IHJlcG9ydGluZyBpcyBhIGNvdXJ0ZXN5IHNlcnZpY2UgZnJvbSB0aGUgZGF0YSBjb2xsZWN0b3Ig
dG8gdGhlIGRvbWFpbiBvd25lci4mbmJzcDsgRWFjaCBlZmZvcnQgdG8gaW5jcmVhc2UgdGhlIHBy
ZWNpc2lvbiBvZiB0aGUgZGF0YSBtYXkgcmVkdWNlIHRoZSBudW1iZXINCiBvZiBkb21haW5zIHdp
bGxpbmcgdG8gcHJvdmlkZSB0aGF0IGluZm9ybWF0aW9uLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHN1Z2dlc3QgdGhhdCB3ZSBuZWVkIHJl
cG9ydCBjb25zdW1lcnMgaW4gdGhpcyBncm91cCB0byBkaXNjdXNzIGhvdyB0aGV5IHVzZSB0aGUg
Y3VycmVudCBkYXRhIGFuZCB0aGUgcHJvcG9zZWQgYWRkaXRpb25zIHRvIHRoYXQgZGF0YSwgc28g
dGhhdCBhIGNvc3QvYmVuZWZpdCBhc3Nlc3NtZW50IGNhbiBiZSBtYWRlLiZuYnNwOyAmbmJzcDtB
dCBsZWFzdCBzb21lIG9mIHRoYXQganVzdGlmaWNhdGlvbiBzaG91bGQgYmUgaW5jbHVkZWQNCiBp
biB0aGUgZmluYWwgZG9jdW1lbnQsIHNpbmNlIG9uZSBwdXJwb3NlIG9mIHRoYXQgZG9jdW1lbnQg
d2lsbCBiZSB0byBjb252aW5jZSBub24tcmVwb3J0aW5nIGVudGl0aWVzIHRvIGJlZ2luIHNlbmRp
bmcgcmVwb3J0cy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+RG91ZyBGb3N0ZXI8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBTdW4sIEphbiAyNCwgMjAyMSBhdCA3OjI1IFBNIEJyb3Rt
YW4sIEFsZXggJmx0O0FsZXhfQnJvdG1hbj08YSBocmVmPSJtYWlsdG86NDBjb21jYXN0LmNvbUBk
bWFyYy5pZXRmLm9yZyI+NDBjb21jYXN0LmNvbUBkbWFyYy5pZXRmLm9yZzwvYT4mZ3Q7IHdyb3Rl
OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+SGVsbG8gZm9sa3MsPGJyPg0KPGJyPg0KU29tZSB0aW1lIGFnbywgYW4gaXNzdWVbMV0gd2Fz
IGJyb3VnaHQgdG8gdGhlIGxpc3Qgd2hlcmUgd2hpY2ggREtJTShzKSBiZWluZyByZXBvcnRlZCBp
cyBub3QgY2xlYXIgaW4gUkZDNzQ4OSBbMl0uJm5ic3A7IFRoZXJlIHdhcyBhIHNob3J0IGRpc2N1
c3Npb24sIHRob3VnaCBubyBjbGVhciByZXNvbHV0aW9uIGJlZm9yZSBjb252ZXJzYXRpb24gdHJh
aWxlZCBvZmYuJm5ic3A7IEl0IHNlZW1zIGxpa2UgdGhlcmUgd2VyZSBwb2ludHMgdGhhdCBtYXkg
bmVlZCB0byBiZQ0KIGRpc2N1c3NlZC4mbmJzcDsgT25lIHdhcyB3aGV0aGVyIHRoZSByZXBvcnRp
bmcgU0hPVUxEIHJlcG9ydCBhbGwgc2lnbmF0dXJlcywgcmVnYXJkbGVzcyBvZiBhbGlnbm1lbnQg
b3IgdmFsaWRpdHksIG9yIHBlcmhhcHMganVzdCB0aGUgb25lIHRoYXQgYWxpZ25zIChpZiB0aGVy
ZSBpcyBvbmUpLiZuYnNwOyBUaGVyZSB3YXMgYWxzbyBhbm90aGVyIHF1ZXN0aW9uIGlmIHRoZXJl
IHNob3VsZCBiZSBhIGxpbWl0IHRvIHRoZSBudW1iZXIgb2Ygc2lnbmF0dXJlcyByZXBvcnRlZA0K
IHNvIHRoYXQgaXQgcmVtYWlucyBzYW5lLjxicj4NCjxicj4NCldlJ2QgbGlrZSB0byB0cnkgdG8g
Z2V0IHRoaXMgcmVzb2x2ZWQgd2l0aGluIGFib3V0IHR3byB3ZWVrcy4mbmJzcDsgVGhhbmsgeW91
IGZvciB5b3VyIGZlZWRiYWNrLjxicj4NCjxicj4NCjE6IDxhIGhyZWY9Imh0dHBzOi8vdXJsZGVm
ZW5zZS5jb20vdjMvX19odHRwczovbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9tc2cvZG1hcmMv
OS1WNTk2eWwyQkJhVXpDTmFEWkIxVGcxczRjL19fOyEhQ1FsM21jSFgyQSFRcG8ta2ZKdl81VXhE
VXpnSUJSb3JJZHh6N0NldGRScEZaZEpHc2JwMS1qYWpCS29IUDRVVTdDenIwbHpzUlJzNjF6b3ps
WWlZdyQiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJj
aC9tc2cvZG1hcmMvOS1WNTk2eWwyQkJhVXpDTmFEWkIxVGcxczRjLzwvYT48YnI+DQoyOiA8YSBo
cmVmPSJodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cHM6L3Rvb2xzLmlldGYub3JnL2h0
bWwvcmZjNzQ4OSpzZWN0aW9uLTcuMl9fO0l3ISFDUWwzbWNIWDJBIVFwby1rZkp2XzVVeERVemdJ
QlJvcklkeHo3Q2V0ZFJwRlpkSkdzYnAxLWphakJLb0hQNFVVN0N6cjBsenNSUnM2MXlJeDctYkp3
JCIgdGFyZ2V0PSJfYmxhbmsiPg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzc0ODkj
c2VjdGlvbi03LjI8L2E+PGJyPg0KPGJyPg0KLS08YnI+DQpBbGV4IEJyb3RtYW48YnI+DQpTci4g
RW5naW5lZXIsIEFudGktQWJ1c2UgJmFtcDsgTWVzc2FnaW5nIFBvbGljeTxicj4NCkNvbWNhc3Q8
YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xzxicj4NCmRtYXJjIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpkbWFyY0BpZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmRtYXJjQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0
dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vZG1hcmNfXzshIUNRbDNtY0hYMkEhUXBvLWtmSnZfNVV4RFV6Z0lCUm9ySWR4ejdDZXRk
UnBGWmRKR3NicDEtamFqQktvSFA0VVU3Q3pyMGx6c1JSczYxd01udDVVVFEkIiB0YXJnZXQ9Il9i
bGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbWFyYzwvYT48bzpw
PjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9k
eT4NCjwvaHRtbD4NCg==

--_000_MN2PR11MB43513C20B5A598496FFBA4AAF7BD9MN2PR11MB4351namp_--


From nobody Mon Jan 25 10:01:37 2021
Return-Path: <mike@fresheez.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 7552D3A195B for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 jmvYXmVR1WVB for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:01:29 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4B313A1640 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:00:49 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id q20so8836902pfu.8 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:00:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=xl6ElGHdFKqsxEIPCZAkRVrAEHSNFewlbPLexCB3f44=; b=kFH6tF3V31pEA82gfhenBT0sKdIpxgzeeQoao9MXnGpNm9ypBWsurBPy3oejYBsRAu FgpuGsqOGI444v4tQfAzECPde+i5LpkjCraa7qf0LhdoBX4I2EvH3SRteukL/9N8Yq5j NAB3kCz7L53z3mLyBWpC2/z7zrv3zPVj4DlaeWVESgIdUBKDN+zMCXqmtiuVjbIuARsQ oaUbuTpuiMrmoxw8hSVHI8eiTgkHENTxL8k7FDrzMJ6QdgaPgGi9C1jL2arhCWRn9gt+ RU/hyEGEDPqnwL2FM72alwek+LC5C9XsiwpoZPVUdCyiFj69N9JTJgEjRc3Rj97/28MG 6qew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=xl6ElGHdFKqsxEIPCZAkRVrAEHSNFewlbPLexCB3f44=; b=Xdnwmy+W2FWKyhBCsqLHmgpVU5daxXDuCJLFhyxN+aESclFiZhwynbWAh2GOfCsHNz pii4XheMtpHPmOuo++1IS5Ac6wkNtctMQsMAjJ7xTEC4UeB1HUVfF0GE8DPZqVTK71Js V7ydOfLx0Sis1hdIIDldDrVgRWyDqo4gtdS61I4DkkPcRtBuXZelgziu8MGMRL3sR2Ct Lkbh5hmtH2kuEiz3PE643/R3BwxzQ0LVirydxHtD2p71sPRwXaZgkjdgJRzXi3olEzoT 4Q8/jCRxPrSa1jzDqdlxPhN0we5+8kpQ3BLCJBOK42+ZH5r7lBFomDCyHeYnGw1ew5z7 rroQ==
X-Gm-Message-State: AOAM5306KuudJrpj/Hq0a4tAJEJmns2MPJ7Um4VaoeCHxhHKsZOJ1HZY W+AKe2EkZwHEGXRx74GggGnEuq9yBjgLyA==
X-Google-Smtp-Source: ABdhPJytipc6lvCgxfNR2+K/Gpb94w+vhmyTr6eDSTqIqubcImt+Oq9McKig/6fIkCYA/WKwWjg9kA==
X-Received: by 2002:a63:4301:: with SMTP id q1mr1703750pga.430.1611597648711;  Mon, 25 Jan 2021 10:00:48 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id f36sm28369pjk.52.2021.01.25.10.00.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 10:00:48 -0800 (PST)
To: Seth Blank <seth@valimail.com>, "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com> <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <25ea488b-e432-75c4-c57a-01d03308208c@mtcc.com>
Date: Mon, 25 Jan 2021 10:00:46 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------4F6517150436DF6A498BFA0F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QCbFI-GRMkKGw0xXicrkAlIrKQc>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 18:01:37 -0000

This is a multi-part message in MIME format.
--------------4F6517150436DF6A498BFA0F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Issue #99 would need to be resolved if you want to use https as well. 
That's really why I brought up the entire issue. It's an easy fix for 
email, and not obvious how you fix it for https.

Mike

On 1/25/21 9:41 AM, Seth Blank wrote:
> Realized I think we're going in circles. Just posted text that is 
> status quo that I believe already addresses Michael's concern.
>
> On Mon, Jan 25, 2021 at 9:38 AM Murray S. Kucherawy 
> <superuser@gmail.com <mailto:superuser@gmail.com>> wrote:
>
>     On Mon, Jan 25, 2021 at 9:32 AM Michael Thomas <mike@mtcc.com
>     <mailto:mike@mtcc.com>> wrote:
>
>         Why is this controversial? Seriously. What is controversial
>         about saying that the a report should authenticate? The onus
>         is on the people who say it does not to lay out the case for
>         why it's not a problem, not me. #98 has a simple piece of text
>         to remedy this. it's 2021. You don't use unauthenticated data
>         if you can possibly help it.
>
>     I'm not taking a position at this point on the issue, but I think
>     you should expect that this will come up in external reviews.  If
>     consensus is to maintain the status quo, we might want to say so
>     explicitly (and why) rather than saying nothing, as the latter
>     might be interpreted as it having gotten no consideration at all.
>
>     -MSK
>
>
>
> -- 
> *Seth Blank*| VP, Standards and New Technologies
> *e:*seth@valimail.com <mailto:seth@valimail.com>
> *p:*415.273.8818
>
>
> This email and all data transmitted with it contains confidential 
> and/or proprietary information intended solely for the use of 
> individual(s) authorized to receive it. If you are not an intended and 
> authorized recipient you are hereby notified of any use, disclosure, 
> copying or distribution of the information included in this 
> transmission is prohibited and may be unlawful. Please immediately 
> notify the sender by replying to this email and then delete it from 
> your system.
>

--------------4F6517150436DF6A498BFA0F
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Issue #99 would need to be resolved if you want to use https as
      well. That's really why I brought up the entire issue. It's an
      easy fix for email, and not obvious how you fix it for https.</p>
    <p>Mike<br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 9:41 AM, Seth Blank wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Realized I think we're going in circles. Just
        posted text that is status quo that I believe already addresses
        Michael's concern.</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021 at 9:38
          AM Murray S. Kucherawy &lt;<a
            href="mailto:superuser@gmail.com" moz-do-not-send="true">superuser@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir="ltr">
            <div dir="ltr">On Mon, Jan 25, 2021 at 9:32 AM Michael
              Thomas &lt;<a href="mailto:mike@mtcc.com" target="_blank"
                moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
            </div>
            <div class="gmail_quote">
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">
                <div>
                  <p>Why is this controversial? Seriously. What is
                    controversial about saying that the a report should
                    authenticate? The onus is on the people who say it
                    does not to lay out the case for why it's not a
                    problem, not me. #98 has a simple piece of text to
                    remedy this. it's 2021. You don't use
                    unauthenticated data if you can possibly help it.<br>
                  </p>
                </div>
              </blockquote>
              <div>I'm not taking a position at this point on the issue,
                but I think you should expect that this will come up in
                external reviews.  If consensus is to maintain the
                status quo, we might want to say so explicitly (and why)
                rather than saying nothing, as the latter might be
                interpreted as it having gotten no consideration at all.</div>
              <div><br>
              </div>
              <div>-MSK<br>
              </div>
            </div>
          </div>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"><span>
          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
          </span>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border: none; height: 40px; width: 177px;" moz-do-not-send="true"></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
        </span></div>
    </blockquote>
  </body>
</html>

--------------4F6517150436DF6A498BFA0F--


From nobody Mon Jan 25 10:02:44 2021
Return-Path: <johnl@iecc.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 A96923A1C68 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:02:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=KyxIaIwB; dkim=pass (2048-bit key) header.d=taugh.com header.b=GmZaAGl0
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 umKwis4mK7vI for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:02:33 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 AA32F3A1928 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:01:30 -0800 (PST)
Received: (qmail 68857 invoked from network); 25 Jan 2021 18:01:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=10cf7.600f0779.k2101; bh=hUFpvu0xUE63joJ3ugTHzOJm85CSB0Iz6fzklwOny6A=; b=KyxIaIwBE3hio1PgiP313lFTcSTwLu775PYdoUcZFtwJyhG+hDiyAjjE/MTDE8vWjdiBdGdKyGBEUMERjQ9GqbcIMOoLap5a8HhX3fcndU72oeM5AAC8tmW0/iRGCsb88CmcQI41NiLBpIJ834Ak09jWCpOfkXkutiTwzOacLLAEH2Iu9JzXKmFqB4HcXoo3wi4KsgqP/w/hrif7zV6o3shC8m2E6vtqZI1oOSTmqwME9LXdcpUsSR+EURHnpv9oMxz4gEv8IH/p5K0dC5qNjE+Hk/MeeIW/HyqdkQEROSp4Rv4BTPLHVBzwNeWvjbXByyHY9byuZzSxukwzFHsUYQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=10cf7.600f0779.k2101; bh=hUFpvu0xUE63joJ3ugTHzOJm85CSB0Iz6fzklwOny6A=; b=GmZaAGl05AWf5ieQJTSFNm/ScA/XQhgQecCdK5HUSX5RefLkQ5JwFOWmJt+6hnxrx2/wNGDendtA8327VlVQVu/8HCjX395DqSTxs0OWRbn/UPvChXCx0cG3ViWJDyloYlAupFvAeZY0LkQWqm6/lIEfOZHRcpDTyozBSzBGAINLFAgFfJ5nAS8KnmfX+IJ/BurT/a9pv3RcLm+XstsEBK16u8piWGO/aVuF6jFffnNURre8UoZJKTV0SExpL/SG3MJi/TzvtV+3ITYGiIekmna5++6dJziUprkQBo95n0ps8gJBahMQohEBApZ+8J4ks5w8k8yxx+J6smfqv/fvYw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 18:01:29 -0000
Received: by ary.qy (Postfix, from userid 501) id D48E86C13032; Mon, 25 Jan 2021 13:01:28 -0500 (EST)
Date: 25 Jan 2021 13:01:28 -0500
Message-Id: <20210125180128.D48E86C13032@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <63451726-124b-c24f-3be1-d6435e12c22e@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jVhyFtDUrfE_LMhKAQ3j4Vs4mjE>
Subject: Re: [dmarc-ietf] Ticket #55, closing
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, 25 Jan 2021 18:02:40 -0000

In article <63451726-124b-c24f-3be1-d6435e12c22e@tana.it> you write:
>OLDER:
>    These reports SHOULD include the "call-to-action" URI(s) from inside
>    messages that failed to authenticate.

Well, you can guess where that came from.

>NEW:
>    These reports SHOULD include as much of the message and message header
>    as is reasonable to support the Domain Owner's investigation into what
>    caused the message to fail authentication and track down the sender,
>    unless privacy reasons suggest otherwise.

I'd strip it down more.

 These reports should include as much of the message header and body as
 possible, consistent with the reporting party's privacy policies, to
 enable the Domain Owner to diagnose the authentication failure.

The "should" is deliberately lower case since it's not something you can
describe mechanically.

R's,
John


From nobody Mon Jan 25 10:03:59 2021
Return-Path: <seth@valimail.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 3543F3A16B1 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:03:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 NAsei8oc3stb for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:03:56 -0800 (PST)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC8AF3A175F for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:02:25 -0800 (PST)
Received: by mail-vs1-xe31.google.com with SMTP id e15so7659023vsa.0 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:02:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=J954iBVFrzOkUV/KX6b3nNuRLBvKqcOgZ/RtLzLc274=; b=bBe7ccWel4ZqS7mI12Up33ZDwvacnX9v1fRsBzkIPvUqHpeg0gvxg22ux+x26LU7JN bD2LRYXK6A618TsNEOFIpXehtllPDV1APjwXAMM6DIz72GvLf3fRLKs2mSjs1zZVT9fM UVwVc3oBe3VxED+7SlYtP82IukG0/stS6q6PZrqRNQscg9srLL0XEm8vuI4fYKRDHI/4 I27HTw+g14Wz1APS0GbXqFG2NjvPqw6EOR1h2kK0js9WRM2gYdkPfmgqnXNuJEmFxp/y Zy0+fhHfELKeL0xiwL8mWFi44PEcqbdzjFrR5OzgEWzYOeG+rasI9/+TLq3bR4LDprTA 6z2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=J954iBVFrzOkUV/KX6b3nNuRLBvKqcOgZ/RtLzLc274=; b=LJsCHVCHojlSVXrNl7b05kJTS4LIcX52ZTvj0zAkUYbiSrL4dkELWIpQN6MMvjhfbl ekANBxA6BqWQdpeqQtS2IIpzvsM34mPvXN9I9UqNVNAUHl1wRYo67zSHrS325V8iwhXQ VogUtwsKbsmxVsyCi58AUB962n3WN/w5eibqaiIdDM3gJzyHiBIQmRDNymPdeHOG/sKJ D4EPmZA4COJ9Lk/ChvVDgL0dd7l9uANTi+CBrdeRoCF4Sushwj0dIkxg+u6DV5dFZyJK NtyTd1FH32nZ+XsKFr5uSw7o94sZ0TzuhmcT5ebAedHFOEzHwtmR0XN8xyQfaDlyU9aD CYlQ==
X-Gm-Message-State: AOAM532DGqjV9DPAQrlZKa+RaCU64nCH/RZN9BrNhLIVLNcIYHzTZN1K hxz3ClTrEN+8+A28fRQJLO9AFAiqYen5Eh8ty33ugA==
X-Google-Smtp-Source: ABdhPJx/5RZPt/sqtXOO/ZLOUrsJvcNTq/k60eD3E8XpkRtlZFDGYA9wEnxRXSXOHD5gmqNzfGjPuvxoavYr5zOh17U=
X-Received: by 2002:a67:9c1:: with SMTP id 184mr1654287vsj.41.1611597744795; Mon, 25 Jan 2021 10:02:24 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com> <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com> <25ea488b-e432-75c4-c57a-01d03308208c@mtcc.com>
In-Reply-To: <25ea488b-e432-75c4-c57a-01d03308208c@mtcc.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 25 Jan 2021 10:02:13 -0800
Message-ID: <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>,  Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000019887505b9bd57cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/71iYtEhZslfyPpmPOLZZKbGOrLI>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 18:03:58 -0000

--00000000000019887505b9bd57cb
Content-Type: text/plain; charset="UTF-8"

Michael, are you aware of anyone not following the guidance in the
document? This thread feels like we're discussing a non-issue. Aggregate
reports are already required to be authenticated and I'm unaware of anyone
sending failure reports, let along unauthenticated ones. Is the language
causing problems? Such problems have not been brought to the list, and
would be a good place to start if you want to build consensus.

The list seems to be digging in because no one has raised a use case that
shows a need to revisit the text. This was made worse by asserting that
reports must be authenticated, when the text already makes that clear.

It is likely in scope to discuss if the current text needs to be moved from
7.2.1.1 to 7.1, but let's please be careful to focus on operational
feedback and not personal opinions.

To be exceedingly clear: if this thread doesn't focus and come to
consensus quickly, then ticket #98 should be closed, unless a use case is
raised and supported by operational parties, that there is an issue here
requiring further clarification.

Ticket 99 is still in play, if and only if we decide on adding an HTTPS
transport for DMARC reports, of which historical consensus shows this is
unlikely. Let's press pause on that until the other discussion is
concluded, please.

Seth, as chair

On Mon, Jan 25, 2021 at 10:00 AM Michael Thomas <mike@mtcc.com> wrote:

> Issue #99 would need to be resolved if you want to use https as well.
> That's really why I brought up the entire issue. It's an easy fix for
> email, and not obvious how you fix it for https.
>
> Mike
> On 1/25/21 9:41 AM, Seth Blank wrote:
>
> Realized I think we're going in circles. Just posted text that is status
> quo that I believe already addresses Michael's concern.
>
> On Mon, Jan 25, 2021 at 9:38 AM Murray S. Kucherawy <superuser@gmail.com>
> wrote:
>
>> On Mon, Jan 25, 2021 at 9:32 AM Michael Thomas <mike@mtcc.com> wrote:
>>
>>> Why is this controversial? Seriously. What is controversial about saying
>>> that the a report should authenticate? The onus is on the people who say it
>>> does not to lay out the case for why it's not a problem, not me. #98 has a
>>> simple piece of text to remedy this. it's 2021. You don't use
>>> unauthenticated data if you can possibly help it.
>>>
>> I'm not taking a position at this point on the issue, but I think you
>> should expect that this will come up in external reviews.  If consensus is
>> to maintain the status quo, we might want to say so explicitly (and why)
>> rather than saying nothing, as the latter might be interpreted as it having
>> gotten no consideration at all.
>>
>> -MSK
>>
>
>
> --
> *Seth Blank* | VP, Standards and New Technologies
> *e:* seth@valimail.com
> *p:* 415.273.8818
>
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
>
>

-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--00000000000019887505b9bd57cb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Michael, are you aware of anyone not following the guidanc=
e in the document? This thread feels like we&#39;re discussing a non-issue.=
 Aggregate reports are already required to be authenticated and I&#39;m una=
ware of anyone sending failure reports, let along unauthenticated ones. Is =
the language causing problems? Such problems have not been brought to the l=
ist, and would be a good place to start if you want to build consensus.<div=
><br></div><div>The list seems to be digging in because no one has raised a=
 use case that shows a need to revisit the text. This was made worse by ass=
erting that reports must be authenticated, when the text already makes that=
 clear.</div><div><br></div><div>It is likely in scope to discuss if the cu=
rrent text needs to be moved from 7.2.1.1 to 7.1, but let&#39;s please be c=
areful to focus on operational feedback and not personal opinions.<br><div>=
<br></div><div>To be exceedingly=C2=A0clear: if this thread doesn&#39;t foc=
us and come to consensus=C2=A0quickly, then ticket #98 should be closed, un=
less a use case is raised and supported by operational parties, that there =
is an issue here requiring further clarification.</div><div><br></div><div>=
Ticket 99 is still in play, if and only if we decide on adding an HTTPS tra=
nsport for DMARC reports, of which historical consensus shows this is unlik=
ely. Let&#39;s press pause on that until the other discussion is concluded,=
 please.</div><div><br></div><div>Seth, as chair</div></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25,=
 2021 at 10:00 AM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com">mike@=
mtcc.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
 =20
   =20
 =20
  <div>
    <p>Issue #99 would need to be resolved if you want to use https as
      well. That&#39;s really why I brought up the entire issue. It&#39;s a=
n
      easy fix for email, and not obvious how you fix it for https.</p>
    <p>Mike<br>
    </p>
    <div>On 1/25/21 9:41 AM, Seth Blank wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Realized I think we&#39;re going in circles. Just
        posted text that is status quo that I believe already addresses
        Michael&#39;s concern.</div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 9:38
          AM Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com"=
 target=3D"_blank">superuser@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir=3D"ltr">
            <div dir=3D"ltr">On Mon, Jan 25, 2021 at 9:32 AM Michael
              Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"_blank"=
>mike@mtcc.com</a>&gt; wrote:<br>
            </div>
            <div class=3D"gmail_quote">
              <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                <div>
                  <p>Why is this controversial? Seriously. What is
                    controversial about saying that the a report should
                    authenticate? The onus is on the people who say it
                    does not to lay out the case for why it&#39;s not a
                    problem, not me. #98 has a simple piece of text to
                    remedy this. it&#39;s 2021. You don&#39;t use
                    unauthenticated data if you can possibly help it.<br>
                  </p>
                </div>
              </blockquote>
              <div>I&#39;m not taking a position at this point on the issue=
,
                but I think you should expect that this will come up in
                external reviews.=C2=A0 If consensus is to maintain the
                status quo, we might want to say so explicitly (and why)
                rather than saying nothing, as the latter might be
                interpreted as it having gotten no consideration at all.</d=
iv>
              <div><br>
              </div>
              <div>-MSK<br>
              </div>
            </div>
          </div>
        </blockquote>
      </div>
      <br clear=3D"all">
      <div><br>
      </div>
      -- <br>
      <div dir=3D"ltr"><span>
          <div style=3D"text-align:left"><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank<=
/b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"> | VP, Standards and New Technologies</span><=
/div>
          <span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D=
"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:bas=
eline"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank">seth@valimai=
l.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></s=
pan></div>
          </span>
          <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;f=
ont-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-ali=
gn:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent=
.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSX=
prAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=
=3D"border: none; height: 40px; width: 177px;"></span></p>
          <p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Hel=
vetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><font face=3D"Arial" color=3D"#=
666666"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email=
 and all data transmitted with it contains confidential and/or proprietary =
information intended solely for the use of individual(s) authorized to rece=
ive it. If you are not an intended and authorized recipient you are hereby =
notified of any use, disclosure, copying or distribution of the information=
 included in this transmission is prohibited and may be unlawful. Please im=
mediately notify the sender by replying to this email and then delete it fr=
om your system.</span></font></p>
        </span></div>
    </blockquote>
  </div>

</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--00000000000019887505b9bd57cb--


From nobody Mon Jan 25 10:05:55 2021
Return-Path: <Alex_Brotman@comcast.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 ADE743A16CB for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.com
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 Dz0qi0jSDV2d for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:05:50 -0800 (PST)
Received: from mx0a-00143702.pphosted.com (mx0a-00143702.pphosted.com [148.163.145.77]) (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 A73663A163F for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:05:37 -0800 (PST)
Received: from pps.filterd (m0156892.ppops.net [127.0.0.1]) by mx0a-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10PHvBUM008286; Mon, 25 Jan 2021 13:05:36 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=20190412; bh=GQSzZXcUZ6bEEjYz6bZb7HK1TREHoYf3q1BApL4kPwA=; b=M4shMf5wpx9Jx9xD/B39h0oVLl1eaphmBRaAHqh25L6/hKH/Z0UABnlHBLgMa69A8fgf K3Uph9IWjSLPZ48ayLlAnr0p5JytOzP6v/LMBPv0KNyWZq1exczrtVRTwMwQml5t/dgX Nvok8py0DwsaQ1dbwZ0ejh2ypho9NgdUGKZHF3UzjRL5cws+ZMa7s1eUCqpuITPjHKx2 MYgkHiEJt8f8uT1ZfyfvmoJUqjMdQTl3cCcVep0HBbJ+gjXoLFF2KXgLTMI0Jd4Fk6oS 38IgLD+HINyDh2/d3CSzl4y7QHVrS/cj8Pme7DIEh5EbSxoUR9RQzUA36uCzo0cMWLFt Qw== 
Received: from copdcexc36.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0a-00143702.pphosted.com with ESMTP id 368g0qc344-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 25 Jan 2021 13:05:36 -0500
Received: from copdcexc33.cable.comcast.com (147.191.125.132) by COPDCEXC36.cable.comcast.com (147.191.125.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 25 Jan 2021 11:05:34 -0700
Received: from COPDCEXEDGE01.cable.comcast.com (96.114.158.213) by copdcexc33.cable.comcast.com (147.191.125.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Mon, 25 Jan 2021 11:05:34 -0700
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (104.47.44.51) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Jan 2021 13:05:40 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4175.namprd11.prod.outlook.com (2603:10b6:208:153::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.9; Mon, 25 Jan 2021 18:05:21 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42%7]) with mapi id 15.20.3784.017; Mon, 25 Jan 2021 18:05:20 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
CC: "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
Thread-Index: AdbysIxA8zFO9cEQSfqEK/Gf/4kCJwAjb00AAAFjs5A=
Date: Mon, 25 Jan 2021 18:05:20 +0000
Message-ID: <MN2PR11MB4351CF66E49EE202C9F1EB3FF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAL0qLwYHsZuOAi+ewvaXc_upXAMQ_eGwpw3VgxsnUsrqCYTNdw@mail.gmail.com>
In-Reply-To: <CAL0qLwYHsZuOAi+ewvaXc_upXAMQ_eGwpw3VgxsnUsrqCYTNdw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:a15b:1edf:6851:816e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 71f11586-86e5-4cef-6ab4-08d8c15bc7b6
x-ms-traffictypediagnostic: MN2PR11MB4175:
x-microsoft-antispam-prvs: <MN2PR11MB4175F03BBA852576FBF71D65F7BD0@MN2PR11MB4175.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: EdI4zge5HWx0lwq+5q7luPvlINuKfeFNl/9RSVRsSrFaD0IVxPs8fulyRTOLDam1oT4SmSKbfr2QtYROw/FOAWA3T4z0ToOtTkOnRcxM8fkqW9nPJwTZnIBbV+8W7RutbmqqQ0kJcY7Y42LxyzUzs6caLQ77aU4kN1U94/61Bq2cxGpElvaaN8s84kuq+wdxByWSNxkKDH83dIghFfH0BeAKn0luw28dpqWw89oOeolXVcbTvQgttbSWyBusyOEEPRPQwcOKiiwSVH6m0Q4uiMjJTU39rXqz30esFaYic6RKZ+HxPyyPLpHZk4/AvhWyC1MuGaNJ+DCWBj1hIJEIPNZATAv3rSd4+Ll4mLZtNY8eB9svUsHt469UScNNHOfl9iiqMVVWCRFIZmOzRX477A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(366004)(39860400002)(396003)(346002)(136003)(84050400001)(7696005)(478600001)(6916009)(52536014)(186003)(71200400001)(4326008)(33656002)(5660300002)(86362001)(2906002)(66946007)(66446008)(55016002)(66556008)(64756008)(83380400001)(66476007)(316002)(8936002)(8676002)(6506007)(9686003)(53546011)(76116006); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: Nit4vG+hFQocRJSQJBgKu3YJ2tbTLb1ro4rtqJgnTR/ChljhdBQgIod1k6HSmg8A01RHvc1an7hg933k/4bgW70u4oGubwIsiVAFhHBwUKrYW0HRJ7SRy9I/obkvTii3xWf6R80cc/vDHpROPv0i0Zfdb/XCQq5PAwN8WX4uFsb0bucxgNrEwozPwINzki/XlMNX63ZdpX1rx3z+yF3j4vDFke+OgrV1MCziOtqS2MjP+amJbH3ZzxE3yK8WGQN0l7szGj+YXxswdJ2T6y6JcBQvhwP+4p0HZhqLW3CIxGWXnpDDSahQZth+B35xGf1JZ4ChR7I7gcXJ4ONRkNMXjrvyy3Jr1qGKn98q8itV2UEbXyGTGBnYldertxVriYhbM8FZfb7OTRQM39rmUXxxJR6gYi9Ex8NIDIdAmp6ozQxnR/lHyZBs1YM0eXvzpwPTNxMN6jKWiRzau4Fagq3gvXNjbe8Uj15SQu258MkU9v0YYkhu0JzgThN4qgfs1MJQeR4h/B2ogCvwzQmV/DrkLtWBdZ3xcA8QTiW77gBtIxz6+eSQSHY2E4r/pSUbDIQVTot/mo/cdAII2j00T7Y/qRSGiZrkG2XTcxLUYBfDBJdigfsGB+yFTASm2G5ahjoPUSgBLSRMPNlq6OKeWkG1mpMy4gk9JNCcwtWwcFx9ZagpWYpLhpYpft3MrnmtGPaRSL89Q9dEi7EdlJ3GxC53xB9lEZJ6xebXYopjkdheQhdlR0yh2rzS6+FPc2ECOym6HGzeePRCv8Q4PjNXivw+vNw2wOS//WtuolZFH2et8Cg=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CcXwEkAklDauyghXrciMwNpyH0tfB5TRlss8v7e8HWP+8Heyzmy/be0t0OJmCpPYjVlT5/QhD/FoqeCQZnKsCp779BTXf6jAedRam7U7ceebDgccUFCnByRWWhIw8ihBlkNlfuZCY54W9BIE2mq/KRFRJ7bIqJrXg1V3yLXZpB3h4L6Bwgnf8uzyHXJTZm48cnsZgl9AGxhFMZJoUxT1nbximQL6SlKpp/QjxXJkN6bKZzO70XOe3oNUrF521jdNTK3qge1fuR7LtiIhoTaT60c8k2KFnC5SBhuw97EjoFZ9+jtBE89qACu89fQe0CooZ6FpQrWP7we7pDs7q0y3Jg==
arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1zUYzvZRjPsDzqnxFcVmkf6vdZ63zNekMdi6dtvMN5Q=; b=TJ2c98bZbH9FO53BHib9tu+eo/uIBnfGCl/MRkcLT2Xc2RklkTmNTlWhu85nzuiKOX4acMaiJpbhv8UudV2spfJy/Ft5UhZ9ZJLioyEfQA08AVsZhvqYsOSsLTx8W6sN9ZM88G1iAZ4nAPQf2t73SvH28GTTxR0cLsk8quxVfdtdKIxqIKHuRFLdOQlETEgik3nSzy0AfFEj++GrtGKhemcpQzaSZpUqfM0Otiwz6OHoSGzoKoPm5eLpB7ExxKvJEb0NaWzR6KfUJQbvv7NaRP9AmjdvOeOcEC2EBRHzCLJ5aHthkH75k11XNOEtshz418HSw3XVxR9FCYcKWmjXPw==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=comcast.com; dmarc=pass action=none header.from=comcast.com; dkim=pass header.d=comcast.com; arc=none
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: MN2PR11MB4351.namprd11.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: 71f11586-86e5-4cef-6ab4-08d8c15bc7b6
x-ms-exchange-crosstenant-originalarrivaltime: 25 Jan 2021 18:05:20.9430 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 906aefe9-76a7-4f65-b82d-5ec20775d5aa
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: xGWf+qYhFyeIl+kCnfetdyfVOhxAFRBtHfGBhU8dOjRrt9hCyEtmcHtCXDIf7sj0B4OPY26bOEU6x9MyBCuAFe4b+obPL7hcpPcivUWAD7M=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4175
x-originatororg: comcast.com
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB4351CF66E49EE202C9F1EB3FF7BD9MN2PR11MB4351namp_"
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWA
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-25_07:2021-01-25, 2021-01-25 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-Vi4W29ZDgROEIVrN8BeLN4DFmA>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 18:05:53 -0000

--_000_MN2PR11MB4351CF66E49EE202C9F1EB3FF7BD9MN2PR11MB4351namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TXVycmF5LA0KDQpQZXJzb25hbGx5LCBhcyBhIHJlcG9ydCByZXBvcnRlciAmIHJlcG9ydCByZWNl
aXZlciwgSSB3b3VsZCBwcmVmZXIgdG8gbm90IHRyeSB0byBmaWd1cmUgdGhhdCBhbGwgb3V0IGR1
cmluZyBnZW5lcmF0aW9uL2luZ2VzdGlvbi4gIEnigJltIHN1cmUgdGhlcmUgc29tZSB1c2UgY2Fz
ZSB0byBiZSBzdGF0ZWQgZm9yIHN0b3JpbmcvcmVwb3J0aW5nIHVubmVjZXNzYXJ5IGRhdGEgZWxl
bWVudHMgdGhhdCBoYXZlIOKAnG5vIGJlYXJpbmfigJ0gb24gdGhlIG91dGNvbWUgZm9yIERNQVJD
LiAgT3IgcGVyaGFwcyBpdCBjb3VsZCBiZSBwZXJjZWl2ZWQgYXMgYSBkYXRhIGxlYWsgdG8gc2hv
dyB3aGVyZSBtZXNzYWdlcyBoYXZlIHBhc3NlZCBvbiB0aGUgd2F5IHRvIHRoZWlyIGZpbmFsIGRl
c3RpbmF0aW9uLiAgQnV0IHBvaW50IG1hZGUsIGFuZCBpZiB3ZSBnbyB0aGF0IHJvdXRlLCB3ZeKA
mWxsIGJlIHN1cmUgdG8gaW5jbHVkZSBwcm9zL2NvbnMuICBUaGFuayB5b3UNCg0KLS0NCkFsZXgg
QnJvdG1hbg0KU3IuIEVuZ2luZWVyLCBBbnRpLUFidXNlICYgTWVzc2FnaW5nIFBvbGljeQ0KQ29t
Y2FzdA0KDQpGcm9tOiBNdXJyYXkgUy4gS3VjaGVyYXd5IDxzdXBlcnVzZXJAZ21haWwuY29tPg0K
U2VudDogTW9uZGF5LCBKYW51YXJ5IDI1LCAyMDIxIDEyOjIwIFBNDQpUbzogQnJvdG1hbiwgQWxl
eCA8QWxleF9Ccm90bWFuQGNvbWNhc3QuY29tPg0KQ2M6IGRtYXJjQGlldGYub3JnDQpTdWJqZWN0
OiBSZTogW2RtYXJjLWlldGZdIFdoaWNoIERLSU0ocykgc2hvdWxkIGJlIHJlcG9ydGVkPyAoVGlj
a2V0ICMzOCkNCg0KT24gU3VuLCBKYW4gMjQsIDIwMjEgYXQgNDoyNSBQTSBCcm90bWFuLCBBbGV4
IDxBbGV4X0Jyb3RtYW49NDBjb21jYXN0LmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86NDBjb21j
YXN0LmNvbUBkbWFyYy5pZXRmLm9yZz4+IHdyb3RlOg0KU29tZSB0aW1lIGFnbywgYW4gaXNzdWVb
MV0gd2FzIGJyb3VnaHQgdG8gdGhlIGxpc3Qgd2hlcmUgd2hpY2ggREtJTShzKSBiZWluZyByZXBv
cnRlZCBpcyBub3QgY2xlYXIgaW4gUkZDNzQ4OSBbMl0uICBUaGVyZSB3YXMgYSBzaG9ydCBkaXNj
dXNzaW9uLCB0aG91Z2ggbm8gY2xlYXIgcmVzb2x1dGlvbiBiZWZvcmUgY29udmVyc2F0aW9uIHRy
YWlsZWQgb2ZmLiAgSXQgc2VlbXMgbGlrZSB0aGVyZSB3ZXJlIHBvaW50cyB0aGF0IG1heSBuZWVk
IHRvIGJlIGRpc2N1c3NlZC4gIE9uZSB3YXMgd2hldGhlciB0aGUgcmVwb3J0aW5nIFNIT1VMRCBy
ZXBvcnQgYWxsIHNpZ25hdHVyZXMsIHJlZ2FyZGxlc3Mgb2YgYWxpZ25tZW50IG9yIHZhbGlkaXR5
LCBvciBwZXJoYXBzIGp1c3QgdGhlIG9uZSB0aGF0IGFsaWducyAoaWYgdGhlcmUgaXMgb25lKS4g
IFRoZXJlIHdhcyBhbHNvIGFub3RoZXIgcXVlc3Rpb24gaWYgdGhlcmUgc2hvdWxkIGJlIGEgbGlt
aXQgdG8gdGhlIG51bWJlciBvZiBzaWduYXR1cmVzIHJlcG9ydGVkIHNvIHRoYXQgaXQgcmVtYWlu
cyBzYW5lLg0KDQpBIHdhcm5pbmcgYWJvdXQgdXNlIG9mICJTSE9VTEQiIChvciAiUkVDT01NRU5E
RUQiKSB3aXRoIHJlc3BlY3QgdG8gcHJvdG9jb2xzOiBUZXh0IHNheWluZyAiaW1wbGVtZW50ZXJz
IFNIT1VMRCBkbyBmb29iYXIiIHByZXNlbnRzIHRoZSBpbXBsZW1lbnRlciB3aXRoIGEgY2hvaWNl
LiAgSWYgeW91J3JlIGdvaW5nIHRvIHNheSB0aGF0LCB5b3UgbmVlZCB0byBleHBsYWluIHRoZSBj
aG9pY2U7IGluIHBhcnRpY3VsYXIsIGFuIGltcGxlbWVudGVyIHNob3VsZCBoYXZlIHNvbWUgaWRl
YSBvZiB0aGUgY2lyY3Vtc3RhbmNlcyB1bmRlciB3aGljaCBzaGUgbWlnaHQgbGVnaXRpbWF0ZWx5
IG5vdCBkbyB3aGF0IGl0IHNheXMgYW5kIHdoYXQgdGhlIGltcGxpY2F0aW9ucyBvZiBkb2luZyBz
byBhcmUgd2l0aCByZXNwZWN0IHRvIGludGVyb3BlcmFiaWxpdHkuDQoNCkEgYmFyZSBTSE9VTEQs
IG1lYW50IHRvIGJlIGhhbmQtd2F2eSBsaWtlICJ5b3UgcmVhbGx5IG91Z2h0IHRvIGRvIHRoaXMs
IGJ1dCB5b3UgZG9uJ3QgYWN0dWFsbHkgaGF2ZSB0byBpZiB5b3UgZG9uJ3Qgd2FudCB0byIgaXMg
bGlrZWx5IHRvIGRyYXcgYXR0ZW50aW9uLiAgSSd2ZSBiZWVuIGtpbmQgb2YgcGlja3kgYWJvdXQg
dGhpcyBsYXRlbHkgZHVyaW5nIElFU0cgRXZhbHVhdGlvbi4NCg0KSW4gdGhpcyBjYXNlLCAicmVw
b3J0aW5nIFNIT1VMRCByZXBvcnQgYWxsIHNpZ25hdHVyZXMiIC0tIHdoeSB3b3VsZCB5b3Ugbm90
Pw0KDQotTVNLDQo=

--_000_MN2PR11MB4351CF66E49EE202C9F1EB3FF7BD9MN2PR11MB4351namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5k
b3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0K
CXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIgc3R5bGU9IndvcmQtd3Jh
cDpicmVhay13b3JkIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5NdXJyYXksPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBlcnNvbmFsbHksIGFzIGEg
cmVwb3J0IHJlcG9ydGVyICZhbXA7IHJlcG9ydCByZWNlaXZlciwgSSB3b3VsZCBwcmVmZXIgdG8g
bm90IHRyeSB0byBmaWd1cmUgdGhhdCBhbGwgb3V0IGR1cmluZyBnZW5lcmF0aW9uL2luZ2VzdGlv
bi4mbmJzcDsgSeKAmW0gc3VyZSB0aGVyZSBzb21lIHVzZSBjYXNlIHRvIGJlIHN0YXRlZCBmb3Ig
c3RvcmluZy9yZXBvcnRpbmcgdW5uZWNlc3NhcnkgZGF0YSBlbGVtZW50cyB0aGF0IGhhdmUg4oCc
bm8gYmVhcmluZ+KAnQ0KIG9uIHRoZSBvdXRjb21lIGZvciBETUFSQy4gJm5ic3A7T3IgcGVyaGFw
cyBpdCBjb3VsZCBiZSBwZXJjZWl2ZWQgYXMgYSBkYXRhIGxlYWsgdG8gc2hvdyB3aGVyZSBtZXNz
YWdlcyBoYXZlIHBhc3NlZCBvbiB0aGUgd2F5IHRvIHRoZWlyIGZpbmFsIGRlc3RpbmF0aW9uLiZu
YnNwOyBCdXQgcG9pbnQgbWFkZSwgYW5kIGlmIHdlIGdvIHRoYXQgcm91dGUsIHdl4oCZbGwgYmUg
c3VyZSB0byBpbmNsdWRlIHByb3MvY29ucy4mbmJzcDsgVGhhbmsgeW91PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPi0tPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbGV4IEJy
b3RtYW48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNyLiBFbmdpbmVlciwg
QW50aS1BYnVzZSAmYW1wOyBNZXNzYWdpbmcgUG9saWN5PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5Db21jYXN0PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1s
ZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3Bh
ZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8
L2I+IE11cnJheSBTLiBLdWNoZXJhd3kgJmx0O3N1cGVydXNlckBnbWFpbC5jb20mZ3Q7IDxicj4N
CjxiPlNlbnQ6PC9iPiBNb25kYXksIEphbnVhcnkgMjUsIDIwMjEgMTI6MjAgUE08YnI+DQo8Yj5U
bzo8L2I+IEJyb3RtYW4sIEFsZXggJmx0O0FsZXhfQnJvdG1hbkBjb21jYXN0LmNvbSZndDs8YnI+
DQo8Yj5DYzo8L2I+IGRtYXJjQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbZG1h
cmMtaWV0Zl0gV2hpY2ggREtJTShzKSBzaG91bGQgYmUgcmVwb3J0ZWQ/IChUaWNrZXQgIzM4KTxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBT
dW4sIEphbiAyNCwgMjAyMSBhdCA0OjI1IFBNIEJyb3RtYW4sIEFsZXggJmx0O0FsZXhfQnJvdG1h
bj08YSBocmVmPSJtYWlsdG86NDBjb21jYXN0LmNvbUBkbWFyYy5pZXRmLm9yZyI+NDBjb21jYXN0
LmNvbUBkbWFyYy5pZXRmLm9yZzwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0Ljhw
dDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNvbWUgdGltZSBhZ28s
IGFuIGlzc3VlWzFdIHdhcyBicm91Z2h0IHRvIHRoZSBsaXN0IHdoZXJlIHdoaWNoIERLSU0ocykg
YmVpbmcgcmVwb3J0ZWQgaXMgbm90IGNsZWFyIGluIFJGQzc0ODkgWzJdLiZuYnNwOyBUaGVyZSB3
YXMgYSBzaG9ydCBkaXNjdXNzaW9uLCB0aG91Z2ggbm8gY2xlYXIgcmVzb2x1dGlvbiBiZWZvcmUg
Y29udmVyc2F0aW9uIHRyYWlsZWQgb2ZmLiZuYnNwOyBJdCBzZWVtcyBsaWtlIHRoZXJlIHdlcmUg
cG9pbnRzDQogdGhhdCBtYXkgbmVlZCB0byBiZSBkaXNjdXNzZWQuJm5ic3A7IE9uZSB3YXMgd2hl
dGhlciB0aGUgcmVwb3J0aW5nIFNIT1VMRCByZXBvcnQgYWxsIHNpZ25hdHVyZXMsIHJlZ2FyZGxl
c3Mgb2YgYWxpZ25tZW50IG9yIHZhbGlkaXR5LCBvciBwZXJoYXBzIGp1c3QgdGhlIG9uZSB0aGF0
IGFsaWducyAoaWYgdGhlcmUgaXMgb25lKS4mbmJzcDsgVGhlcmUgd2FzIGFsc28gYW5vdGhlciBx
dWVzdGlvbiBpZiB0aGVyZSBzaG91bGQgYmUgYSBsaW1pdCB0byB0aGUgbnVtYmVyDQogb2Ygc2ln
bmF0dXJlcyByZXBvcnRlZCBzbyB0aGF0IGl0IHJlbWFpbnMgc2FuZS48bzpwPjwvbzpwPjwvcD4N
CjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QSB3YXJuaW5nIGFib3V0IHVz
ZSBvZiAmcXVvdDtTSE9VTEQmcXVvdDsgKG9yICZxdW90O1JFQ09NTUVOREVEJnF1b3Q7KSB3aXRo
IHJlc3BlY3QgdG8gcHJvdG9jb2xzOiBUZXh0IHNheWluZyAmcXVvdDtpbXBsZW1lbnRlcnMgU0hP
VUxEIGRvIGZvb2JhciZxdW90OyBwcmVzZW50cyB0aGUgaW1wbGVtZW50ZXIgd2l0aCBhIGNob2lj
ZS4mbmJzcDsgSWYgeW91J3JlIGdvaW5nIHRvIHNheSB0aGF0LCB5b3UgbmVlZCB0byBleHBsYWlu
IHRoZSBjaG9pY2U7IGluIHBhcnRpY3VsYXIsDQogYW4gaW1wbGVtZW50ZXIgc2hvdWxkIGhhdmUg
c29tZSBpZGVhIG9mIHRoZSBjaXJjdW1zdGFuY2VzIHVuZGVyIHdoaWNoIHNoZSBtaWdodCBsZWdp
dGltYXRlbHkgbm90IGRvIHdoYXQgaXQgc2F5cyBhbmQgd2hhdCB0aGUgaW1wbGljYXRpb25zIG9m
IGRvaW5nIHNvIGFyZSB3aXRoIHJlc3BlY3QgdG8gaW50ZXJvcGVyYWJpbGl0eS48bzpwPjwvbzpw
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkEgYmFyZSBTSE9VTEQsIG1lYW50
IHRvIGJlIGhhbmQtd2F2eSBsaWtlICZxdW90O3lvdSByZWFsbHkgb3VnaHQgdG8gZG8gdGhpcywg
YnV0IHlvdSBkb24ndCBhY3R1YWxseSBoYXZlIHRvIGlmIHlvdSBkb24ndCB3YW50IHRvJnF1b3Q7
IGlzIGxpa2VseSB0byBkcmF3IGF0dGVudGlvbi4mbmJzcDsgSSd2ZSBiZWVuIGtpbmQgb2YgcGlj
a3kgYWJvdXQgdGhpcyBsYXRlbHkgZHVyaW5nIElFU0cgRXZhbHVhdGlvbi48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SW4gdGhpcyBjYXNlLCAm
cXVvdDtyZXBvcnRpbmcgU0hPVUxEIHJlcG9ydCBhbGwgc2lnbmF0dXJlcyZxdW90OyAtLSB3aHkg
d291bGQgeW91IG5vdD88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+LU1TSzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_MN2PR11MB4351CF66E49EE202C9F1EB3FF7BD9MN2PR11MB4351namp_--


From nobody Mon Jan 25 10:05:59 2021
Return-Path: <todd.herr@valimail.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 D225B3A163D for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 agwKKxqHNcfo for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:05:54 -0800 (PST)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 631883A168D for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:05:41 -0800 (PST)
Received: by mail-qv1-xf29.google.com with SMTP id s6so6593819qvn.6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:05:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=c9WAsURKA+hP152vjcwDyJoduXqCTxVP1UlkwW5uQ/c=; b=AwsXeS46TJ9iXGH1e3nR5UVugUQCOJy42cwVwCL+/10QQZNr7fifbeHt/yTb6kxHro LhKfqols0kGDXR/LrNhbInPIaLWfNKETM5S+K1p2anjXBb48SPtR6ZIz19PsK3l3d3hG dGG4VA6K0gmPcYXbmvS6TaPAdjZ2Fnrfc4orEiLW4YV03TN5eh/ZCq4BGWGYa32+Guq2 zpZATc1MDNn0Tat9I7sN52kcle6li0mSWS3Ar7KRSKfQri0cyhXhFREEEQY0RWkC0FrA HAuwlzEjLfo03iIMr7u/EEZp4A+Amd7wlIKtfz9/5ati77aKtX4HWp9f4BkP2LhZvaZv IoDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=c9WAsURKA+hP152vjcwDyJoduXqCTxVP1UlkwW5uQ/c=; b=lTCGBZsP39I/mtVTMOMsdZd9w3MMqj/lSpm2SnnmDF8Ua5iKJ1MnAu1SXjI+39Hc1l FjxCtuLigZefF8sAJtAx1m1MJo9Ffusoh0IRN6ieN7I5IDQ63F9P/fWsM9+01rSrqIa7 Nz2jv4FzkSGuzHAZHJ1sTnitXS/e+vdeV+j2TWi3ZSzOPYwAEQfOtMMe/QcDLSn0/mgR iW40/mH6w9Ss9hK/x8zVXT9WsQosqaJLBprzrLLRWNkeJVmG7sACUXe2E3yTAzyJX4eb JYinaRwE8ftn9SxHhdAwKVqCi3HxIOr4lfCTe12IURg3WbIZMyaFp0EIpuJCwP6UifVx +Tmg==
X-Gm-Message-State: AOAM530AkiCdpFM0+mkpwqzeo3+GJaTpEFCfac3eam26rOsIBBCXa3kf +fYBeH9beqJ+uqzOK7gKqzQh0gGM+c+To7kHod/JM2256us=
X-Google-Smtp-Source: ABdhPJw3FjQlJcTglAJbe3/H3R2NhZ1kvL3U2AxcWkZBUmW5+W+Vs8r7FPBkTGrFDuEWXtA7ryoptSB5sUlmnkPNoGY=
X-Received: by 2002:a0c:fe0b:: with SMTP id x11mr1950722qvr.18.1611597940041;  Mon, 25 Jan 2021 10:05:40 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <dd98f7ca-1088-8a1a-c69d-e2b723543cb1@mtcc.com>
In-Reply-To: <dd98f7ca-1088-8a1a-c69d-e2b723543cb1@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 25 Jan 2021 13:05:24 -0500
Message-ID: <CAHej_8meTdGM7we_PdTroZ4dikY4gC5ZQGnb0N4xKpSo9xtxkg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bcc05305b9bd6205"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/L2_kOryRcAiePBJTKom2C7zbEqs>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 18:05:58 -0000

--000000000000bcc05305b9bd6205
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 25, 2021 at 12:53 PM Michael Thomas <mike@mtcc.com> wrote:

> But just as an example, suppose I'm trying to get to a position to use
> p=reject, but some bad actor doesn't want me to do that so they can keep
> phishing me. All they have to do is keep sending forged message reports
> from gmail which makes me think I've got a problem. Seriously, this is not
> rocket science.
>
>
>
Thank you for answering my question.


-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000bcc05305b9bd6205
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 25, 2021 at 12:53 PM Michael =
Thomas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br=
></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
 =20
   =20
 =20
  <div>
    <p>But just as an example, suppose I&#39;m trying to get to a position
      to use p=3Dreject, but some bad actor doesn&#39;t want me to do that =
so
      they can keep phishing me. All they have to do is keep sending
      forged message reports from gmail which makes me think I&#39;ve got a
      problem. Seriously, this is not rocket science.<br>
    </p>
    <p><br></p></div></blockquote><div><br></div><div>Thank you for answeri=
ng my question.=C2=A0</div></div><br clear=3D"all"><div><br></div>-- <br><d=
iv dir=3D"ltr" class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line=
-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-alig=
n:left"><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-si=
ze:small;font-family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-=
align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | S=
r. Technical Program Manager</span></div><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"=
text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><s=
pan style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail=
.com" target=3D"_blank">todd.herr@valimail.com</a></span></div></span><span=
><div><span><b>p:</b></span><span> 703.220.4153 </span><span></span></div><=
/span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helveti=
ca,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height=
:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-=
family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:b=
aseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com=
/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx=
4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"bo=
rder: none; height: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D=
"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small=
;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-b=
ottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255=
);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666=
" face=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre-wrap">T=
his email and all data transmitted with it contains confidential and/or pro=
prietary information intended solely for the use of individual(s) authorize=
d to receive it. If you are not an intended and authorized recipient you ar=
e hereby notified of any use, disclosure, copying or distribution of the in=
formation included in this transmission is prohibited and may be unlawful. =
Please immediately notify the sender by replying to this email and then del=
ete it from your system.</span></font></p></span></div></div>

--000000000000bcc05305b9bd6205--


From nobody Mon Jan 25 10:10:46 2021
Return-Path: <mike@fresheez.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 59D723A16E3 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 EANelKeFfZYV for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:10:44 -0800 (PST)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 043533A16E4 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:10:40 -0800 (PST)
Received: by mail-pj1-x102a.google.com with SMTP id p15so81219pjv.3 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:10:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=OLObngR+qWtgTlJX5qCePd1tdJzc6DJiPBoQrRaUavE=; b=DcnDIMWDgCwkw/281AJwN+Nt4Tm93kEpRxIvA8TCTslNB0Zd3LLp1XEDKcN4sfJWEo DyjKAac3dwbVKhuzkOTVF5lrS7EVFrmexFVyx7dfvGjlyQdLavGaKxrhfbLcjrgP//9s 0yI+D4N+hAGcoj6YgiTJIPNiFIyBwB60sVs9l2wYojlV9KIjC+K1JPw2sjMRNcWz92vA c7DrI7hn6GeQlSdC5LDDKFG3i9Xs+fX83vSYpYpa0/dkPOz9ZnAwxpmvZDoR4f2zK1pa QD8/eQYFWijA6oM4kzDrCcKYFddSbSSin2yGGxNDhUv2B1x7zM83HoLYE0pSA2T/jd75 OpDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=OLObngR+qWtgTlJX5qCePd1tdJzc6DJiPBoQrRaUavE=; b=Yvc+2qA5wTvSHqEySAvA/eVZrCXQfKekgc/k7YO/j8HftMSavybmzGmIA/liB4rF/6 HIAgR5zmIrZvXF6ePsx+A//x0UA0wediQmtdrp6Z/9iIjQGLtxAgaZ8Ynz8v6KNaHA2p zf2q5ovrY/r0NvFtdSzSfzF3pLA3AgqIJB1qc0CMGRPIr8VRCim8j14IdrHZDxUwouzk pHe85LGzvY1vhXXvCFM31tTkibGhhriTrDBa0K2pci4zUOBhumZIQF+WBUeI848IvMJ/ VmSzY0R0boPV6ncn1aBASGKL8W6j+jpTpiGDVa8/a8TTPrJoc8H+1AE91xulBxeRg/aH Icvg==
X-Gm-Message-State: AOAM533yVM5S7BU989VVABLqIFEMqWpaYQEsfXwtv5V+K5RhBIEikrkF xGLBYzEO8dPvoKp6zrgOyqiQ8Q8isPJJTw==
X-Google-Smtp-Source: ABdhPJxSde5WXMJ6/+KXhxnJOji5lDYLVHc8B9lVQA+2qRDXqW3R2FW4wCn0alDebKtbEtI6NDs2Fg==
X-Received: by 2002:a17:90a:ab8e:: with SMTP id n14mr1416975pjq.96.1611598240254;  Mon, 25 Jan 2021 10:10:40 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id x81sm17369056pfc.46.2021.01.25.10.10.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 10:10:39 -0800 (PST)
To: Seth Blank <seth@valimail.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com> <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com> <25ea488b-e432-75c4-c57a-01d03308208c@mtcc.com> <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <08263091-46d9-5973-c46d-7aad083c2dcb@mtcc.com>
Date: Mon, 25 Jan 2021 10:10:38 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xfEE3gpLY4Lglrm9A90S17-YZwI>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 18:10:45 -0000

On 1/25/21 10:02 AM, Seth Blank wrote:
> Michael, are you aware of anyone not following the guidance in the 
> document? This thread feels like we're discussing a non-issue. 
> Aggregate reports are already required to be authenticated and I'm 
> unaware of anyone sending failure reports, let along unauthenticated 
> ones. Is the language causing problems? Such problems have not been 
> brought to the list, and would be a good place to start if you want to 
> build consensus.
>
> The list seems to be digging in because no one has raised a use case 
> that shows a need to revisit the text. This was made worse by 
> asserting that reports must be authenticated, when the text already 
> makes that clear.

Obviously it isn't that clear. I looked for it and didn't find it. 
Several people just asserted that it wasn't a problem instead of 
pointing at the relevant text requiring it. Murray didn't seem to know 
about it either. That tells me that the current text is not specific enough.

> Ticket 99 is still in play, if and only if we decide on adding an 
> HTTPS transport for DMARC reports, of which historical consensus shows 
> this is unlikely. Let's press pause on that until the other discussion 
> is concluded, please.
>
This entire thread was by way of John Levine's proposing text for http 
and me responding about how to authenticate it. If you have a problem 
with that, take it up with him.

Mike


From nobody Mon Jan 25 10:18:18 2021
Return-Path: <kurta@drkurt.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 3D2843A1702 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:18:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.com
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 2oI0pGq8L54m for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:18:14 -0800 (PST)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C97473A16D4 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:18:14 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id u17so28534223iow.1 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:18:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=30Xxt2cnI3A+hGx1k8/MQ5nnm7JzVn8uzqBwc4Uhs5Q=; b=Z0WnYTv0gpOmiqo3nPuNjgn934xLCfRw1eGWCvcZBHvwup32sJMGt2eTnFb4RRrb2m ABJJoMJJWBDZOXbLt59Jc5OmB4AUgmeWybjfHtLkpX9jtwqfw9bPIFC9jsrwauxtr0A7 BVsPO7XrqiUgDDMec2IIp5pyfBY7D5gBDNaN4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=30Xxt2cnI3A+hGx1k8/MQ5nnm7JzVn8uzqBwc4Uhs5Q=; b=IvlWHwAwSiFCIae3EG6Ng2x3VrZospfyoQoW5UgsgmQIli4FRILpYfgadAhefQFHmy v0PNQcyMbvoM2XTO7VsvhdEHAUK5S5VtYNsooT7Fx1M/m4F9D2LIcZdBlDh7Qy0D/ltn xk55TA9iebGFaInY5lIGIUEiamUlRWsiXltnJHh2ar9ybgxaDXpWAvtLfbGNx4XOiMzk DhMMlM/JUM8ieysJlYJBYwj7PlOKXIG9RYs2Zo2Txip+izlx9ZizpwJ54W/hBM3g4jh6 PsPnsfGISlnl2GOonbsMT5AL2yzyP9pbLpFYLOnHee7op04G4OdeMovoXP75dCQvOUn7 jBWw==
X-Gm-Message-State: AOAM53280ZnTpMUrnhhhnw69mpmS+/XepZDqsCxk9B9ITUsLcvBT++M0 TbLsNj2X/RfvGomYSacOKfl2wv4vpLKATTSjr5ENhw==
X-Google-Smtp-Source: ABdhPJytMscKGhQqWgcYH2zwYMtTrvZxgYzfStjV4DRo+7U0fNjS6Uda1EI9ufnH8f15NmTni/oowPZ11Hs4k8/oKwE=
X-Received: by 2002:a92:484a:: with SMTP id v71mr1406849ila.263.1611598693595;  Mon, 25 Jan 2021 10:18:13 -0800 (PST)
MIME-Version: 1.0
References: <63451726-124b-c24f-3be1-d6435e12c22e@tana.it> <20210125180128.D48E86C13032@ary.qy>
In-Reply-To: <20210125180128.D48E86C13032@ary.qy>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Mon, 25 Jan 2021 10:17:56 -0800
Message-ID: <CABuGu1rx82iab9Lpweth_z6cZ1XPyshVawukNqnuPZQHhrKaJA@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="000000000000a7151405b9bd8fa2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4StLLY72VvZDA7n2Wd2M0VnLG2E>
Subject: Re: [dmarc-ietf] Ticket #55, closing
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, 25 Jan 2021 18:18:16 -0000

--000000000000a7151405b9bd8fa2
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 25, 2021 at 10:05 AM John Levine <johnl@taugh.com> wrote:

> In article <63451726-124b-c24f-3be1-d6435e12c22e@tana.it> you write:
> >OLDER:
> >    These reports SHOULD include the "call-to-action" URI(s) from inside
> >    messages that failed to authenticate.
>

The intent of calling out CTA links was to facilitate takedown efforts
against fraudulent domains rather than being strictly concerned about why
otherwise valid messages failed to authenticate.

--Kurt

--000000000000a7151405b9bd8fa2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 25, 2021 at 10:05 AM John Lev=
ine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:<b=
r></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">In article &lt;<a href=3D"mailto:63451726-124b-c24f-3be1-d6435e1=
2c22e@tana.it" target=3D"_blank">63451726-124b-c24f-3be1-d6435e12c22e@tana.=
it</a>&gt; you write:<br>
&gt;OLDER:<br>
&gt;=C2=A0 =C2=A0 These reports SHOULD include the &quot;call-to-action&quo=
t; URI(s) from inside<br>
&gt;=C2=A0 =C2=A0 messages that failed to authenticate.<br></blockquote><di=
v><br></div><div>The intent of calling out CTA links was to facilitate take=
down efforts against fraudulent domains rather than being strictly concerne=
d about why otherwise valid messages failed to authenticate.</div><div><br>=
</div><div>--Kurt=C2=A0</div></div></div>

--000000000000a7151405b9bd8fa2--


From nobody Mon Jan 25 10:23:55 2021
Return-Path: <johnl@iecc.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 7DFF43A171A for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:23:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=pIUJxWgF; dkim=pass (2048-bit key) header.d=taugh.com header.b=IRVo4HOV
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 8bKyTYYk8n9f for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:23:53 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 2AB2F3A1716 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:23:52 -0800 (PST)
Received: (qmail 73568 invoked from network); 25 Jan 2021 18:23:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=11f5e.600f0cb7.k2101; bh=kTq9m3N8kIYCFNF2cxyztc5k7BgUBoglvE4+dl+N578=; b=pIUJxWgFWw0gst31CUijb0x9OOAAwAdQSF0bDphSfpEvTGaR4tR8qYvj6gD3u7XL6Ikto7cUUnNF/P+Fu2oH8ZuH8vgNFY2vUyz/13SvciKQyRFSU3ZxRcwWU4WvJBSlHR2RLpwZ1RkxehfQ95V2WKOCRWgAfaHwnBfCzslZ41cCZqrqRVeRqfYP1XFzORRuWFLIZBBZdhTSv8wdQKEUgfpyKPcyKxwoqqs7vt17nw2BB7xRwxk4l2PkdAYqH2CKYMh9jKdPruxnSCfu5NjeFUyXks4fmcEt1obxJwG8W84t3tNPVWQ+1QzBiH+ySsU+g3IeOEO4NpYEQSY1UllfHw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=11f5e.600f0cb7.k2101; bh=kTq9m3N8kIYCFNF2cxyztc5k7BgUBoglvE4+dl+N578=; b=IRVo4HOVFmjr/mQ8kg4aI30Z/hlINRSW0AFIfL8Dp3drJcGLrXIstqSgWtsWa2zPxz3zFMQ4bBYz82TTV6FbVGmD297UtMmdlZQkj5hthQxiROygnE815kryPoysccKjnVY65Y/2JmwSCBp5b6lVvfQBNRXzdLUj2h55dD0bggBEJ++Ho1j5JWJVojtivNpNm927KlXpErAKzTpt6WZfcu7mTz6yYgj0zzS5AJGnoQSCv79uzeANYHYNDQ1/4LoAcKHR7pXV5Mi7HkAuWpIG4yYYKgt7uHcxJ0O9yagO+Qmw8AFTvwaBBXR8Ng2QZ2LbtjKUBV1Vu9hKzz00FItuiQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 18:23:51 -0000
Received: by ary.qy (Postfix, from userid 501) id DE0FE6C131FB; Mon, 25 Jan 2021 13:23:49 -0500 (EST)
Date: 25 Jan 2021 13:23:49 -0500
Message-Id: <20210125182350.DE0FE6C131FB@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: seth@valimail.com
In-Reply-To: <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/bhPte_l9HQeg5tbdR7Vs0vgIDUw>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 18:23:54 -0000

>The list seems to be digging in because no one has raised a use case that
>shows a need to revisit the text. This was made worse by asserting that
>reports must be authenticated, when the text already makes that clear.

I think the use case is my proposed https reporting. If you think it
would be useful to allow domain authentication, it's easy enough to
say that the client SHOULD send a client certificate. Nobody will, but
every https server and client library I know supports client certs so
it's not hard to implement.

I continue to believe that authenticating the domain sending reports
is of no value, since there is no way to tell what if any connection
that domain has to the IPs in an aggregate report or the IPs or
domains in a failure report. If I wanted to send fake gmail failure
reports, I would register gmail-reports.com and send 100% perfectly
aligned fake reports from that domain.

R's,
John


From nobody Mon Jan 25 10:26:01 2021
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 DAA543A171C for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 7M9-KNsZjqmR for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:25:58 -0800 (PST)
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 567463A171B for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:25:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611599155; bh=d6fplJWl82RFTsk+ZeUXQaH2wfQA7KNAsKYVsaUstEY=; l=1773; h=To:References:From:Date:In-Reply-To; b=AMl9zcZ3frsvsBpTtEah/7v/1WcJKvfoQ4efLAXEUG4fI0zEGnvcAiN0OQuFtRQd2 BwfgZvscH0A114W+pgYvN+ybOGPNyc2OZEuUgzFd/F/DCRoNelSUiC19sham1c5AEL 58WqUwDSkxNrS8Rg2pA4rs1/rCdFJS86UX4nobzVKQgTfDkRl+AtVoJqVNx+i
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0E0.00000000600F0D33.00000245; Mon, 25 Jan 2021 19:25:55 +0100
To: dmarc@ietf.org
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <8f7226cc-6ce4-d633-e77e-0a7f7c328d7e@tana.it>
Date: Mon, 25 Jan 2021 19:25:53 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.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/BZBfG3BrgSMDlLYetln0fKXYlNE>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 18:26:00 -0000

On Mon 25/Jan/2021 01:25:13 +0100 Brotman, Alex wrote:
> 
> Some time ago, an issue[1] was brought to the list where which DKIM(s) being reported is not clear in RFC7489 [2].  There was a short discussion, though no clear resolution before conversation trailed off.  It seems like there were points that may need to be discussed.  One was whether the reporting SHOULD report all signatures, regardless of alignment or validity, or perhaps just the one that aligns (if there is one).


I think that, in principle, it is good to report all signatures.  Within a 
report, signatures should be ordered by importance.  If the number of 
signatures per report is limited, it is paramount that they be ordered, so that 
the most important ones are reported.

How to define importance is subjective.  A report generators decides the order 
based on internal policies or criteria.  The order in which signatures are 
reported is an additional information, as if each record contained a sort of 
approval index, irrespective of the total number of signatures being reported.

For example, my report generator orders signatures by domain, putting author's 
domain first, and then taking into account alignment and a sort of reputation. 
  That's the order in which validation is attempted.  Afterwards, valid 
signatures are put before invalid ones.  The number of reported signatures is 
limited to 4, because of SQL query limits (the query itself is configurable; it 
does a number of LEFT JOIN, which can be increased.)


>  There was also another question if there should be a limit to the number of signatures reported so that it remains sane.


Yes, I think it's sane to put a limit.  I'd reject messages with more than 128 
signatures.  It never happened.


Best
Ale
-- 




















From nobody Mon Jan 25 10:29:05 2021
Return-Path: <mike@fresheez.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 F19173A1763 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 ExQeMdyIsVrs for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:28:58 -0800 (PST)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45BB83A175C for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:28:58 -0800 (PST)
Received: by mail-pg1-x52f.google.com with SMTP id n10so9483513pgl.10 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:28:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=HORb7wLodWTHino1PQMessNnxrlZuGlRpAhith443OA=; b=U0nuk7Fxi0K27FOeORY+jCcfklW8qcd+5KJFqZwRG9LOcvB0BnX95nNmD39ZYyy+l3 qR6SNM93TNSfIDnwiBct4zrFHAOMnlqGMI2mzFLYWt56KuRxuZ0fBujpWI3c/D16Q3tW hAm/qnqHRj8GrJsz4SljW4qXmvA13aNR7YxKZG/xB02JilMxBnmiXfE1KZzQ1qpgq8g7 /pvUjPX7/HrxOZyNbueNAIjsY51Op7/X3SgDmoKCjb58bQYqT6daaRQRwB4KZv6wlRmD 0k+V9JauJSbzhv3cNmfJIAZ5Deou22GpXIKh11beYHs2DiRjIhTu1yrQ4lWUo66/pPdy GIMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=HORb7wLodWTHino1PQMessNnxrlZuGlRpAhith443OA=; b=dwvcXXhgjRnAFe+RgICRk2QLVcUEgdnTAljIzBBliwdYtlxrTSf1MvQmPGavQyr9Ho dfEH5Ep58IxrY7POW1fDItNCeoG/Uy+fR2Lq5y2h7dx2RWSIjVZY22C4+bD0F7VdoJtD 3JgIu3Dsxqj2hrVxKSDdlTSkFPU+EDAE8woey2FWh8h2j6IwxPhGJZUOKrPtWxVWH5iL srK01eZtHsaRkGr/X+9OBYt5a16WtoXu/oeb62oPck0gj/5OD80FRx4Kin4b0p1/1jYW 88mYk/axg3QR8WScKIOvu3QibrjMs47PXWxIoZ7o7dZtlSFtph0TEvb1Hqlm/5jO9Ssw DqKg==
X-Gm-Message-State: AOAM530cNzDxlY46WD11gVeOtcWGUHd09s3Vjtf2hw3oue/CkkUxIXtv SF3Om+p+LUCEuXqvPfpgtArmsPvLDs//xQ==
X-Google-Smtp-Source: ABdhPJxltzMwMAgdEJDL97LhZSpuoQu+oInwfyBtvihkOurgSlwJyYnZcAngBIuquqDBlxR+rKpIeQ==
X-Received: by 2002:a62:6503:0:b029:1b4:4580:1abd with SMTP id z3-20020a6265030000b02901b445801abdmr1584122pfb.30.1611599336896;  Mon, 25 Jan 2021 10:28:56 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id a72sm10471163pfa.126.2021.01.25.10.28.55 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 10:28:56 -0800 (PST)
To: dmarc@ietf.org
References: <20210125182350.DE0FE6C131FB@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <ddb67702-01e7-783d-9fa6-3e427542092c@mtcc.com>
Date: Mon, 25 Jan 2021 10:28:55 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210125182350.DE0FE6C131FB@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/kwsIW3cxASQs-3Adv4c5jsk5YQs>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 18:29:05 -0000

On 1/25/21 10:23 AM, John Levine wrote:
>> The list seems to be digging in because no one has raised a use case that
>> shows a need to revisit the text. This was made worse by asserting that
>> reports must be authenticated, when the text already makes that clear.
> I think the use case is my proposed https reporting. If you think it
> would be useful to allow domain authentication, it's easy enough to
> say that the client SHOULD send a client certificate. Nobody will, but
> every https server and client library I know supports client certs so
> it's not hard to implement.

Which means that is done completely in bad faith. No thanks.

>
> I continue to believe that authenticating the domain sending reports
> is of no value, since there is no way to tell what if any connection
> that domain has to the IPs in an aggregate report or the IPs or
> domains in a failure report. If I wanted to send fake gmail failure
> reports, I would register gmail-reports.com and send 100% perfectly
> aligned fake reports from that domain.
>
I send mail to gmail. I send no mail to gmail-reports. If anything you 
are demonstrating even further that this is at best underspecified.

Mike


From nobody Mon Jan 25 10:31:32 2021
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 9B2B03A1720 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 G0WHyEla4gj3 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:31:30 -0800 (PST)
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 473D63A171F for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:31:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611599488; bh=fe+9TM5soLAd78+r4HXwZURdERAYYFSswGkX4jcHL/c=; l=249; h=To:References:From:Date:In-Reply-To; b=BcZCLcOypmkZhk1z8faxjb74SOEXtz5Wn5DYYMCqTzVmbG6izPy6y9HxLJ0S9xpsd 2eYUHmlsEFhz184HiIJ+/Nyj8MS4zugmH3qZdnYVMv1+Tj4MSJhtU+WPbdRwIMtccB 7jgPgnb4JT6qrLXfwCnIScnusO52/7N/eqw6+UjdCBvkH2orntVaojcMI6MKK
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC028.00000000600F0E80.000002D6; Mon, 25 Jan 2021 19:31:28 +0100
To: dmarc@ietf.org
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <A551B531-BFCA-466A-8E8D-4EA4EF9FC82C@aegee.org> <CAH48ZfwONFvCunEmD2=PFjbKfb55A=mSB-kjEK-mipWQXx_ahg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <2a3c4fc5-8ab2-7d58-d24c-54690fe4ff82@tana.it>
Date: Mon, 25 Jan 2021 19:31:28 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfwONFvCunEmD2=PFjbKfb55A=mSB-kjEK-mipWQXx_ahg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Qh3-OMO6_Buubw09Eoqup9JfkW8>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 18:31:32 -0000

On Mon 25/Jan/2021 13:21:37 +0100 Douglas Foster wrote:
> This is an interesting issue.   Perhaps we need another ticket just to discuss 
> how to handle signature transition.


Reporting the selector suffices.  Ticket #57.


Best
Ale
-- 



















From nobody Mon Jan 25 10:38:04 2021
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 86F7E3A172E for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:38:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 CUphxpxB4QDv for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:38:02 -0800 (PST)
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 2D8233A172C for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:38:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611599880; bh=T/3VSrmItLMljK7wDsKpXUPqk+HFeazYaxsUL0dYBkA=; l=812; h=To:References:From:Date:In-Reply-To; b=CKIh+rrs8VdxZZAVZf92ZQITP5NQlfngY6fkdEUvknwa+V4jtH2TmXSs0OdWE+QAj fuDYZItS3R2ilTFs4CEMmHDNQMA4Nc38ps0t00wROm0/goUnS+oxxGFXS5hTsHkTG+ vn5schxXQ33GykGWlugUWg/oVTFoU+/3POV/8CVt5ZpmoLL5prCPFqvU7/0M7
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC028.00000000600F1008.000003CC; Mon, 25 Jan 2021 19:38:00 +0100
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>, Douglas Foster <dougfoster.emailstandards@gmail.com>
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it>
Date: Mon, 25 Jan 2021 19:37:59 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/yTLz-TGBMi-II56HgUoi3UOHrz4>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 18:38:04 -0000

On Mon 25/Jan/2021 18:59:16 +0100 Brotman, Alex wrote:
> 
> I’m not suggesting that we add anything that would report “Signature
> validation not attempted”, that sounds horrible.  Will the original source
> potentially care that the message was signed in three other places as the
> message bounced around?

It can be useful to understand the mail flow.  For example, a signature by a 
Mediator can reveal a mailing list, even if the receiver didn't evaluate it.


> Should we put the onus on the reporting entity to do the filter out the
> non-aligned (what if none aligned) signatures, or just realize it’s some
> automated job and including all logged/validated signatures is the better
> way?

The order in which signatures appear in a report can be significant too.


Best
Ale
-- 









From nobody Mon Jan 25 10:48:00 2021
Return-Path: <johnl@iecc.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 F10D33A1735 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=OFZjOm+t; dkim=pass (2048-bit key) header.d=taugh.com header.b=IWkf8l9g
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 8LC90HEH6SQc for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:47:58 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 8C7503A0F06 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:47:58 -0800 (PST)
Received: (qmail 79694 invoked from network); 25 Jan 2021 18:47:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=13749.600f125d.k2101; bh=f0xrmXSIn2WZ6ANCVpikY5yDbXgM6ZTkr0J4XLzlEkA=; b=OFZjOm+tK2JpZok3L8YlVrWUfwqRpqOJ07aO13EE8b27exMR8/EpbeH/CsxiOGuKPQFu44/9DV5FR2+6r/Sfu8RP8Oh6eAazTIpNiBysSQceM6nv2guK7q9IQdQ12uI2NPEadKvm9Lrby2rI96qMaoBgjo8wYiRjZj1anu/NkZSgpk01MKLFXGZpRy4Wr9PTSOB6T7c2Rn/J6FvF6h10u4y6+VBc5cnXn7xs3E6M8WKzgGDqKvWbGEzp7P7mzUTHwwc74eJ8fmdyfNbuQod6fjK1jq8/nz+WOwAGV7YNMEAkZinnKT0n2AhHm0xsv2+0zzFLSHyPpY3PyQ2r4+7Whg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=13749.600f125d.k2101; bh=f0xrmXSIn2WZ6ANCVpikY5yDbXgM6ZTkr0J4XLzlEkA=; b=IWkf8l9gjTnzWspudW8MtHZDhStc0QiZ20dlVhs+8VDyfe2uokYLowX33fTuUTZGQCtvKwDFzaenYXOWAs+B4FcA4A9GL9QEOKTkhIttiR0dHzV/h1OPtNIzHcHcPw0K9GmQXPCSZRz14ikJLpmOt0f5t0LV9JLFS42dhZJ/cgnZs1v/LxH7OkeQJlAol4kaE48Qqi72tlSrKoF+9SBGHl3MdJowuaA0KbwjKSEl4HkZckI++42vr2Uq9ZOXtflgayRCH1M/ltakGKSk85bfaXt28h57HK5u2yGMp/9XwKB5kJF663vGEJ3FrB/ipfXlTuDBfKpiebtytp2TSxagkw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 18:47:56 -0000
Received: by ary.qy (Postfix, from userid 501) id A13A76C1384D; Mon, 25 Jan 2021 13:47:55 -0500 (EST)
Date: 25 Jan 2021 13:47:55 -0500
Message-Id: <20210125184756.A13A76C1384D@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: mike@mtcc.com
In-Reply-To: <ddb67702-01e7-783d-9fa6-3e427542092c@mtcc.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/cl4OK6dGdtYseH4uL2cBcryCSIY>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 18:48:00 -0000

In article <ddb67702-01e7-783d-9fa6-3e427542092c@mtcc.com> you write:
>> I continue to believe that authenticating the domain sending reports
>> is of no value, since there is no way to tell what if any connection
>> that domain has to the IPs in an aggregate report or the IPs or
>> domains in a failure report. If I wanted to send fake gmail failure
>> reports, I would register gmail-reports.com and send 100% perfectly
>> aligned fake reports from that domain.
>>
>I send mail to gmail. I send no mail to gmail-reports. If anything you 
>are demonstrating even further that this is at best underspecified.

Hi, Mike. When Google sends aggregate reports, what address do you
think they send them from? It should be easy enough to look at some of
the reports you've gotten and check.

R's,
John


From nobody Mon Jan 25 10:52:19 2021
Return-Path: <dougfoster.emailstandards@gmail.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 CE8763A174C for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:52:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 AyjjmhCGKrVm for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:52:15 -0800 (PST)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F1993A174B for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:52:15 -0800 (PST)
Received: by mail-ej1-x62b.google.com with SMTP id gx5so19541345ejb.7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:52:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=UKH9DvbG01VMYzb56TY/fpTUhI4lFjcH6Sv1jpqxww0=; b=NXmPUE0UboBexZYpxUcjmfJe9KUrxpZ96k+6p6n+KsrWbmMsFKjDsK5l7OOurFdniB IWOthO7We6gPk0rNvbb2lXXUqIqvd9mv3t2jcBDvz04A5xyYkyoye6de4ogydjUyBi2q pNfOT/j4SzzfPVovky1rPMGLwWFXEh/f2xWnLB2+tG5i+RxASsacF0DW7Zt/+XGA1EwJ KXdCR6c7FtjbNBM62ohMBtK1HvLb7tyZolaToqprYptuIr6XIGb/M84TcdRvb4i2fpQT umx4R8FusD4fTJPvY0wP83rlvCtB1riTQmnQ5acDlbsZrsmr33dHPDptSXLiYRbxucVZ oBVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=UKH9DvbG01VMYzb56TY/fpTUhI4lFjcH6Sv1jpqxww0=; b=qGPKHWUCRTuCZNqKJbnx9t/9DZij3sC1Mqi4CV2iG+ot2cCUt6qCPeEnWFsLRaeMHC dn7yv11Ca8+93IfLwrLI9nj66tZ7YOGIHGZouFnXVbZikAROjDBttQVpEinZPexCxqMk BSOdEWehcRvxwbit+GZOtP6zD0LVrRoqVOIvZlarPGfvVKBjUU8N68KhqJLiJ0rxdMS+ 1I1rVcrG5Lcwbl4Y/p9WykoBX9Q8opVnO2iZyVAa8tpXbGI2lJl14GBApL4K8nuztWWt ssuAr/eguXiNesdYJZBVzKxMPjDZ9rLohKMutrbZFURIzw6i0dTEljqnLVIqkbbQIEBG JGPg==
X-Gm-Message-State: AOAM532MeJC05NDvKF8JepDEGCIKtcCyGDbod64xxR7+b/ccI5OWXYBb z8T3fk8I24YsT80bTQQQCA6W8/7pUSVOjwGX1YfPakeA
X-Google-Smtp-Source: ABdhPJxSv39gI+rWE2Cr1WxLFEu3rU5UI04KpW6RYYdGRIfxLVMih59KGDjaTUSDF2saGWYM+PSsr8rVoboQRKOmkRM=
X-Received: by 2002:a17:906:ff43:: with SMTP id zo3mr1204382ejb.542.1611600733642;  Mon, 25 Jan 2021 10:52:13 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it>
In-Reply-To: <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 25 Jan 2021 13:51:59 -0500
Message-ID: <CAH48ZfyCNmYMqe_5NP84DtLAm1P8r5HPwVS_JBsBc3SXZfWOtg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003fa40b05b9be099f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/e88KGdDc66quKJm-XnsE-BYTh18>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 25 Jan 2021 18:52:17 -0000

--0000000000003fa40b05b9be099f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Can we go slightly off topic to review why the report does not include the
destination domain?

That data element seems a lot more relevant than a tertiary signature.

I can see that domain identification and disaggregation could significantly
increase the size of reports from Gsuite and Office365, assuming that they
currently aggregate all domains.   This could be problematic for both them
and for the recipient.

On Mon, Jan 25, 2021, 1:38 PM Alessandro Vesely <vesely@tana.it> wrote:

> On Mon 25/Jan/2021 18:59:16 +0100 Brotman, Alex wrote:
> >
> > I=E2=80=99m not suggesting that we add anything that would report =E2=
=80=9CSignature
> > validation not attempted=E2=80=9D, that sounds horrible.  Will the orig=
inal
> source
> > potentially care that the message was signed in three other places as t=
he
> > message bounced around?
>
> It can be useful to understand the mail flow.  For example, a signature b=
y
> a
> Mediator can reveal a mailing list, even if the receiver didn't evaluate
> it.
>
>
> > Should we put the onus on the reporting entity to do the filter out the
> > non-aligned (what if none aligned) signatures, or just realize it=E2=80=
=99s some
> > automated job and including all logged/validated signatures is the bett=
er
> > way?
>
> The order in which signatures appear in a report can be significant too.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>

--0000000000003fa40b05b9be099f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Can we go slightly off topic to review why the report doe=
s not include the destination domain?=C2=A0=C2=A0<div dir=3D"auto"><br></di=
v><div dir=3D"auto">That data element seems a lot more relevant than a tert=
iary signature.</div><div dir=3D"auto"><br></div><div dir=3D"auto">I can se=
e that domain identification and disaggregation could significantly increas=
e the size of reports from Gsuite and Office365, assuming that they current=
ly aggregate all domains.=C2=A0 =C2=A0This could be problematic for both th=
em and for the recipient.</div></div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021, 1:38 PM Alessandro Ves=
ely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">On Mon 25/Jan/2021 18:59:16 +0100 Brot=
man, Alex wrote:<br>
&gt; <br>
&gt; I=E2=80=99m not suggesting that we add anything that would report =E2=
=80=9CSignature<br>
&gt; validation not attempted=E2=80=9D, that sounds horrible.=C2=A0 Will th=
e original source<br>
&gt; potentially care that the message was signed in three other places as =
the<br>
&gt; message bounced around?<br>
<br>
It can be useful to understand the mail flow.=C2=A0 For example, a signatur=
e by a <br>
Mediator can reveal a mailing list, even if the receiver didn&#39;t evaluat=
e it.<br>
<br>
<br>
&gt; Should we put the onus on the reporting entity to do the filter out th=
e<br>
&gt; non-aligned (what if none aligned) signatures, or just realize it=E2=
=80=99s some<br>
&gt; automated job and including all logged/validated signatures is the bet=
ter<br>
&gt; way?<br>
<br>
The order in which signatures appear in a report can be significant too.<br=
>
<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div>

--0000000000003fa40b05b9be099f--


From nobody Mon Jan 25 10:55:32 2021
Return-Path: <dougfoster.emailstandards@gmail.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 92B173A174D for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:55:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 fK5SvIzVMWkD for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 10:55:29 -0800 (PST)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6E803A13AB for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:55:28 -0800 (PST)
Received: by mail-ed1-x533.google.com with SMTP id n6so16752699edt.10 for <dmarc@ietf.org>; Mon, 25 Jan 2021 10:55:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=3K8StACYWuHQVCYWbpoe5ir22YpM26px0+M/MosKpMk=; b=bKFrMPvSwSICuW+WXmKqWv8lPbxvFv2wdQCjxgCfpS+ZB6BF4Si2xX+oPugOO2kgFX //u7w9IraxEwwXIJKLIKv056MPzLx2jkYMupHsRsQl6+RciIaJXZMt0R6eH6hDqoWr8H WJ8b3fkdoNleXDFYJ87ayycEP5P6r0nY/q6jBEBZqREI/D7+t5uLpTqQ6hp8hwYC351F 1afgaV2WbHNTYkfeOhmG8W/+Ks22sFB4nAxDuGcgUFQRR82+due1ho3aKUtDu3i/sblZ 3W5CK+TJyy/J/gSMN+1cNTWcLpPvlsYslF+X8XPhGzo4TD4dI59Sj+7au/qbOG+FS7o1 7Wvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=3K8StACYWuHQVCYWbpoe5ir22YpM26px0+M/MosKpMk=; b=APYb+maftXB8vd7v6mHKb7XlGJ3KkhW8CYO/qE4gImM/BE2919DMv1VETPcZ5tfmBw AS+yi3R6HZEEBqSQj1dkmUB9TqawIAECRxwBoihyCu0xrVV2U2s9FQIgAhhUS/1vxK0a q8jl8AwFftda7+bGhsR8O2MlFar3ahNdYCFWklZkNTifq9W+F0Ax7Dzt/wX08xY77KV/ qXQAx7V5iMQ5kty/aTj7ZVjPTG7IkLcM2nSd3EuVAkv9DdHN/ycAEvK6jo/3WKZs72lz LQx/8Rs1s7JD21feInvf7Ys22LrOUH5c5SLIQd/bbm6lc4Llg2zpdkf1C4PhdXGoFSXp A3DA==
X-Gm-Message-State: AOAM532Gx9OJw4P2Gn/g269tSqGz51FtvCVcsBfyAr2AwoSkErQDUPwF 4upLnekDNxwBjVLfz89TJqiJfJmU9DOI41L3CQTWArty
X-Google-Smtp-Source: ABdhPJxl/6qRfxXFil9BeOD04+9mqYF+SMsyVdZkwUKlw+YJrUKkmfO5PwH6UnQtTMTELR3iWun5OuWItawNdsDKFto=
X-Received: by 2002:a50:bf4a:: with SMTP id g10mr1604724edk.201.1611600926611;  Mon, 25 Jan 2021 10:55:26 -0800 (PST)
MIME-Version: 1.0
References: <20210125182350.DE0FE6C131FB@ary.qy> <ddb67702-01e7-783d-9fa6-3e427542092c@mtcc.com>
In-Reply-To: <ddb67702-01e7-783d-9fa6-3e427542092c@mtcc.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 25 Jan 2021 13:55:12 -0500
Message-ID: <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c01b1f05b9be146e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/iSgpRqc8xqVmP0cebnUa494Qk2I>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 18:55:31 -0000

--000000000000c01b1f05b9be146e
Content-Type: text/plain; charset="UTF-8"

DMARC alignment on the report seems of limited value unless it is aligned
to the domain being reported.  But that change would require every unique
domain to generate a unique report.   Gsuite and Office365 would probably
consider that unacceptable.

On Mon, Jan 25, 2021, 1:29 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/25/21 10:23 AM, John Levine wrote:
> >> The list seems to be digging in because no one has raised a use case
> that
> >> shows a need to revisit the text. This was made worse by asserting that
> >> reports must be authenticated, when the text already makes that clear.
> > I think the use case is my proposed https reporting. If you think it
> > would be useful to allow domain authentication, it's easy enough to
> > say that the client SHOULD send a client certificate. Nobody will, but
> > every https server and client library I know supports client certs so
> > it's not hard to implement.
>
> Which means that is done completely in bad faith. No thanks.
>
> >
> > I continue to believe that authenticating the domain sending reports
> > is of no value, since there is no way to tell what if any connection
> > that domain has to the IPs in an aggregate report or the IPs or
> > domains in a failure report. If I wanted to send fake gmail failure
> > reports, I would register gmail-reports.com and send 100% perfectly
> > aligned fake reports from that domain.
> >
> I send mail to gmail. I send no mail to gmail-reports. If anything you
> are demonstrating even further that this is at best underspecified.
>
> Mike
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000c01b1f05b9be146e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">DMARC alignment on the report seems of limited value unle=
ss it is aligned to the domain being reported.=C2=A0 But that change would =
require every unique domain to generate a unique report.=C2=A0 =C2=A0Gsuite=
 and Office365 would probably consider that unacceptable.</div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 20=
21, 1:29 PM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On 1/25/21 10:23 AM, John Levine wrote:<br>
&gt;&gt; The list seems to be digging in because no one has raised a use ca=
se that<br>
&gt;&gt; shows a need to revisit the text. This was made worse by asserting=
 that<br>
&gt;&gt; reports must be authenticated, when the text already makes that cl=
ear.<br>
&gt; I think the use case is my proposed https reporting. If you think it<b=
r>
&gt; would be useful to allow domain authentication, it&#39;s easy enough t=
o<br>
&gt; say that the client SHOULD send a client certificate. Nobody will, but=
<br>
&gt; every https server and client library I know supports client certs so<=
br>
&gt; it&#39;s not hard to implement.<br>
<br>
Which means that is done completely in bad faith. No thanks.<br>
<br>
&gt;<br>
&gt; I continue to believe that authenticating the domain sending reports<b=
r>
&gt; is of no value, since there is no way to tell what if any connection<b=
r>
&gt; that domain has to the IPs in an aggregate report or the IPs or<br>
&gt; domains in a failure report. If I wanted to send fake gmail failure<br=
>
&gt; reports, I would register <a href=3D"http://gmail-reports.com" rel=3D"=
noreferrer noreferrer" target=3D"_blank">gmail-reports.com</a> and send 100=
% perfectly<br>
&gt; aligned fake reports from that domain.<br>
&gt;<br>
I send mail to gmail. I send no mail to gmail-reports. If anything you <br>
are demonstrating even further that this is at best underspecified.<br>
<br>
Mike<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank" rel=3D"noreferrer">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div>

--000000000000c01b1f05b9be146e--


From nobody Mon Jan 25 11:02:09 2021
Return-Path: <mike@fresheez.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 BFFAD3A1754 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:02:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 si6B8xQKHlDK for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:02:06 -0800 (PST)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE3BF3A174E for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:02:06 -0800 (PST)
Received: by mail-pg1-x52b.google.com with SMTP id z21so9571805pgj.4 for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:02:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Pc8PoCil635Y5KRVpMW4K2kAu1KgNjre1DNuDnOF6e4=; b=CDWBpaxWqvngrdmB4xpYCbvJCrPywpuq1lJCHWyUlSP84QgOHWo1T2NuolFUFoIIGg 27RmWzqnJCBvx6bMl3eFp7DNiY8ZVr3GpZp4+1unqB1ebQ4oimT5zq5zxXe0PxhMyUZh EC8yrH3M8cGbMphE6oagcaEOWMaFgkBomvCgOQTAoSM2YORF6nRQf3bcv4/7cUQbYWYS N4RA+y8IACn4qzcMDrmrmvyum4ulFpYkJIML9qcJmUciRf8DEZwTU+3XefgUHtC1AWMj h4nGI9E9l+LTN3jK9qo969JM5AQaLiROo+BZRUOW+gDajaExoOjKeyxRwzyh48j+XBg4 DB4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Pc8PoCil635Y5KRVpMW4K2kAu1KgNjre1DNuDnOF6e4=; b=cVyezdGs8zVPwMn155/WXHoNdZ2MS5qbOtPF9zdzwWG+QfXVl0PFNQxtpDftzj6c5K AHG3VFhgD+v8abgPwofilh3xdJh1rXa/nqlnDk2UnvbfiTdyInI3zgynCcNHrxJc8ehg fhTNEjUe+Impw7pPHjkAzGM9uLdI4hxkpT6fNFERKuhUftN11rVQenf1hVpTi79BH7Wf SoFxo/tVVf03q3w+JNrgFuk3gjncCSeJfSrDVNMuT57I7Iz/EFHUklyM7ZCElTpKH9wR cDCxh8BxeM90iaqyIZnlG9Dt7poxXULf1JR9uZOFsmCb6K+23p0x8geYlXIROV91C3Pn g9Sw==
X-Gm-Message-State: AOAM530y4w1IBzWXAMBRWFUR9wGvAbtMGvsC9aouCIrnmOrWvoqZDw3Q X6mlFYfJNbxFL9ec3zCcxF1Dr/fdbEADlQ==
X-Google-Smtp-Source: ABdhPJyXrz7Fm0n6ms+n2Q/ialCCaIMNT6O5YkhOxGajCGVbLuX5pTESQ2slm5ZW4oEolHKtCtFyzQ==
X-Received: by 2002:a63:db54:: with SMTP id x20mr1939745pgi.200.1611601325750;  Mon, 25 Jan 2021 11:02:05 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id x19sm863715pff.192.2021.01.25.11.02.04 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 11:02:04 -0800 (PST)
To: dmarc@ietf.org
References: <20210125182350.DE0FE6C131FB@ary.qy> <ddb67702-01e7-783d-9fa6-3e427542092c@mtcc.com> <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <26931c0b-9475-ffd5-a996-cc6ffad3a304@mtcc.com>
Date: Mon, 25 Jan 2021 11:02:03 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com>
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/OxIjH2X67sG8J6oiOOVx7jEAYeg>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 19:02:08 -0000

On 1/25/21 10:55 AM, Douglas Foster wrote:
> DMARC alignment on the report seems of limited value unless it is 
> aligned to the domain being reported.  But that change would require 
> every unique domain to generate a unique report.   Gsuite and 
> Office365 would probably consider that unacceptable.
>
Google already has my signing keys. This is an implementation detail on 
their part. If they want to host a domain, they should host a domain. 
Laziness is not an excuse for spoofing.

Mike


From nobody Mon Jan 25 11:04:32 2021
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 4BF083A1757 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 IeC_DjkNd7gT for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:04:30 -0800 (PST)
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 C81BB3A1754 for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:04:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611601467; bh=d1CN0igSYLJbz2qdkTeaqQ5bsCiP57/OtDxlFjU17wo=; l=1097; h=To:References:From:Date:In-Reply-To; b=B6ZRkwtHa1FPXHwxAaTwHDEvlva2J7eATMpIeMQT3iOG+WUL6pkAqs8nUXKfw53zz aluFrDt2mINt0/OGZi3ChESTpFMCGpC2e1NxIgOpsTV0oh2Uu5GQbHNuC3RAcFf0jL EFSeFRQ6XPYwwG9urHeWmbX/PsnqXDNvc12+hom0qk4o3t4xDtdVgJc/PY3wO
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000600F163B.000007A0; Mon, 25 Jan 2021 20:04:27 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org, "Kurt Andersen (b)" <kboth@drkurt.com>
References: <20210125180128.D48E86C13032@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <dc04b0e1-cc19-9009-cef8-42f2ea863e7c@tana.it>
Date: Mon, 25 Jan 2021 20:04:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210125180128.D48E86C13032@ary.qy>
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/2U76Bm63aKioLBp4cd0KQXkBN0w>
Subject: Re: [dmarc-ietf] Ticket #55, closing
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, 25 Jan 2021 19:04:31 -0000

On Mon 25/Jan/2021 19:01:28 +0100 John Levine wrote:
> In article <63451726-124b-c24f-3be1-d6435e12c22e@tana.it> you write:
>>OLDER:
>>    These reports SHOULD include the "call-to-action" URI(s) from inside
>>    messages that failed to authenticate.
> 
> Well, you can guess where that came from.


Should we mention fraudster takedowns among the purpose of failure reports?


>>NEW:
>>    These reports SHOULD include as much of the message and message header
>>    as is reasonable to support the Domain Owner's investigation into what
>>    caused the message to fail authentication and track down the sender,
>>    unless privacy reasons suggest otherwise.
> 
> I'd strip it down more.
> 
>   These reports should include as much of the message header and body as
>   possible, consistent with the reporting party's privacy policies, to
>   enable the Domain Owner to diagnose the authentication failure.


committed.


> The "should" is deliberately lower case since it's not something you can
> describe mechanically.


Someone will question it anyway, I'd guess.


Best
Ale
-- 



















From nobody Mon Jan 25 11:06:49 2021
Return-Path: <johnl@taugh.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 502923A1759 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:06:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=e+XflRa5; dkim=pass (2048-bit key) header.d=taugh.com header.b=zvbcb2BX
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 M0673rMrcmMM for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:06:45 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 A271F3A1758 for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:06:45 -0800 (PST)
Received: (qmail 84421 invoked from network); 25 Jan 2021 19:06:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=149c3.600f16c3.k2101; bh=BgCqOecfKKcRY9cOj5UIfoC0vOcsQ10s1HrMaPl9lhU=; b=e+XflRa51qGuK8F0gHvR80VP0t10EJE+bXzAte6gsgI8Qj2mrUafRMJHFgQXuGBktfSbzPmZ/8MW04Q+iktCIRVU4lDLDUDpty29UfOueUQRHG//L/+MFtdo7OU9VPLH/VOPspsBn8Hg7h2XTNQ+aEDKi9y5dPyUaTtTUh0CO46w3K7sMqhv2paOiyO5kGFlyBXd6eynjNx/Xx1nF7MqsCWzkxldxsjxAOiBx1icV10QqWAqqjZfeKgfzERKLBGB1LW5bcnySx2JguhH5rChNfTjaQIy+43FqJts5e159kbuDzQYca8JUy2g4ZhKiXs2LmN2NGTTkyHyqtf2oJBlYg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=149c3.600f16c3.k2101; bh=BgCqOecfKKcRY9cOj5UIfoC0vOcsQ10s1HrMaPl9lhU=; b=zvbcb2BXg6ELQ2NeG0J6QAcrWqM584u+Rv9/jbdpgJp6UJs/BxgWDnVcMsdMekQvDHvM/T1d4Di+9G1KsHHVySHxJYFCKQe9G7ex3jlaGgykTIfREzELGOZ5mEkldHt0xMTkWIWRMpDMpJXAkUXoB3dD9EDSwLSXd42OmnqUvDwT1iCdKT9WE5PJE6H56wFKmF/zIRRRbsI2kMyHbjh+3GQWSl8hGonucTmeXqBt/WA4kPJpzc5uifTLLSHbUU2U9YllS3IDpyLUlLQ1OfGkG7dep9k+4ON/Ki2m1XKe65Hao639seHDpXoMtVYaB2Sxt3X7Y+9gemzR+SPk1NiZXA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 19:06:42 -0000
Received: by ary.qy (Postfix, from userid 501) id 5F7B26C13A3C; Mon, 25 Jan 2021 14:06:41 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id C20FA6C13A1E; Mon, 25 Jan 2021 14:06:41 -0500 (EST)
Date: 25 Jan 2021 14:06:41 -0500
Message-ID: <e6f64ccf-7ba8-dc83-d333-5bbf8e3eb68b@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org, "Kurt Andersen (b)" <kboth@drkurt.com>
In-Reply-To: <dc04b0e1-cc19-9009-cef8-42f2ea863e7c@tana.it>
References: <20210125180128.D48E86C13032@ary.qy> <dc04b0e1-cc19-9009-cef8-42f2ea863e7c@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/z7OpRvypsRXy305ZR2MELWCMaSQ>
Subject: Re: [dmarc-ietf] Ticket #55, closing
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, 25 Jan 2021 19:06:47 -0000

> On Mon 25/Jan/2021 19:01:28 +0100 John Levine wrote:
>> In article <63451726-124b-c24f-3be1-d6435e12c22e@tana.it> you write:
>>> OLDER:
>>>    These reports SHOULD include the "call-to-action" URI(s) from inside
>>>    messages that failed to authenticate.
>> 
>> Well, you can guess where that came from.
>
> Should we mention fraudster takedowns among the purpose of failure reports?

Again, seems like mission creep.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Mon Jan 25 11:42:01 2021
Return-Path: <dougfoster.emailstandards@gmail.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 7F4CC3A1842 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:42:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BWQxA0Y9jhvI for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:41:59 -0800 (PST)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1D163A1841 for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:41:58 -0800 (PST)
Received: by mail-vs1-xe31.google.com with SMTP id b5so3219942vsh.3 for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:41:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=THrDBbeZ1XoieayfhI1CJpPbLzyz0OSNCyDzYyEbxkk=; b=VQW8gBZ3CSABQTbf0wSe9EEbWnA2b14VMt22P40Va2JOp6tTX89i0CXOCE2bkGcR/2 l1p9Cs7jJ2/8TxALLJdkuxW2rGaT6N7j6cqSBGAGHHib7W9nsNkj4mEx9ukUZ/Vcc/mn PisjACPYaOGKDuddy/gHPJ50czmUNpNXdSyDE/11eBDC3LIlbZa01csruXOPBTnR/TFi vt7JkU3BHzXuBckQkU9KAMrSj5ZeDGCYJoi8fOp0Jro2k5Fo2eL1WlCrrLJAb51WrUqh o2OaEfYupMy25AD9kpe7/kYL0vwvmH/xJINyz9um/VrPlvMv6zMhnJs/j3eiEDzZ0z1i j9IA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=THrDBbeZ1XoieayfhI1CJpPbLzyz0OSNCyDzYyEbxkk=; b=W3jdPR5fyIOmFoNNHHuNP2RdZaUB+bcETfQoOWXzcCpFzxcrL5REaSAbxvB4EVP3LB 1UO1HL09hL92ZjVTN/WgPm4R0BlwMcfw+o5r9MSI2qcd7UhFQUFqYh3IVA3h52M1ii73 upv2/AagYmpJQxSs8Wh+qNWg/Wf0OCE4vWgMiDMhVNSNh0GwAw+TgEX9nHXc11LcB6fk nOgifIKbkC2Thp1sD+XrUGgdN6PHS87tUfmIFQJb3xfxziSnEbEfZtmDrDAT4HnTVyYD WAlY+qbhCE19ozIECjJF8VaGgdk18r3jGNwSU7L3oLjcMnr2L8aQW+V1aJPUxVkQ8kN8 CK2A==
X-Gm-Message-State: AOAM530EjG8sUYwr/aCUM7Qx5RcKKM+mEtZgMIl9zwf7FR1B8BdByo63 UmP4SD92mi4PrZvbu+EKv1015Q7EtNNbvHNvB3IBz/8WCi0=
X-Google-Smtp-Source: ABdhPJwzFvoyv6O+IJvf7kP6K3vCL9ULVFWtIoFSlVnKYuPyCJF6CxIvoLrB3JxcjX2tNU8vvIdcGcCp8WOUJGpWR1A=
X-Received: by 2002:a67:87c2:: with SMTP id j185mr1970265vsd.25.1611603717718;  Mon, 25 Jan 2021 11:41:57 -0800 (PST)
MIME-Version: 1.0
References: <20210125182350.DE0FE6C131FB@ary.qy> <ddb67702-01e7-783d-9fa6-3e427542092c@mtcc.com> <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com> <26931c0b-9475-ffd5-a996-cc6ffad3a304@mtcc.com>
In-Reply-To: <26931c0b-9475-ffd5-a996-cc6ffad3a304@mtcc.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 25 Jan 2021 14:41:43 -0500
Message-ID: <CAH48ZfyVO3wHjKg-Dj01UgSKkK0sOPE-2pOBvwp--xRkJLjL=A@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001d088d05b9bebba6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/fmed2ZLRRm-xWHVPqRFvF4hC4Mg>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 19:42:00 -0000

--0000000000001d088d05b9bebba6
Content-Type: text/plain; charset="UTF-8"

So if a newsletter goes to 10,000 Gsuite domains, Google sends 10,000
reports instead of just one?   I don't think either Google or the
newsletter domain would consider that an improvement.   But perhaps they
will speak for themselves.

On Mon, Jan 25, 2021, 2:02 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/25/21 10:55 AM, Douglas Foster wrote:
> > DMARC alignment on the report seems of limited value unless it is
> > aligned to the domain being reported.  But that change would require
> > every unique domain to generate a unique report.   Gsuite and
> > Office365 would probably consider that unacceptable.
> >
> Google already has my signing keys. This is an implementation detail on
> their part. If they want to host a domain, they should host a domain.
> Laziness is not an excuse for spoofing.
>
> Mike
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--0000000000001d088d05b9bebba6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto">So if a newsletter goes to 10,000 Gsuit=
e domains, Google sends 10,000 reports instead of just one?=C2=A0 =C2=A0I d=
on&#39;t think either Google or the newsletter domain would consider that a=
n improvement.=C2=A0 =C2=A0But perhaps they will speak for themselves.</div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mo=
n, Jan 25, 2021, 2:02 PM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">mike@mtcc.com</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><br>
On 1/25/21 10:55 AM, Douglas Foster wrote:<br>
&gt; DMARC alignment on the report seems of limited value unless it is <br>
&gt; aligned to the domain being reported.=C2=A0 But that change would requ=
ire <br>
&gt; every unique domain to generate a unique report.=C2=A0 =C2=A0Gsuite an=
d <br>
&gt; Office365 would probably consider that unacceptable.<br>
&gt;<br>
Google already has my signing keys. This is an implementation detail on <br=
>
their part. If they want to host a domain, they should host a domain. <br>
Laziness is not an excuse for spoofing.<br>
<br>
Mike<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer noreferrer noreferrer" =
target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mai=
lman/listinfo/dmarc</a><br>
</blockquote></div></div>

--0000000000001d088d05b9bebba6--


From nobody Mon Jan 25 11:51:50 2021
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 905303A184B for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:51:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 TokILfDl9f6O for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:51:47 -0800 (PST)
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 36D243A1848 for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:51:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611604305; bh=mdaevzbvYDSMipWarh8jHoT2O/GXx3sdNjI+G+xDRpw=; l=1563; h=To:References:From:Date:In-Reply-To; b=Chv7sHA7DjOttl05wcIQpvt29sypVML7qT/FlpIeK69wt9VdS3NNUK06SypBlMFsS KnQwCJ43M1o0GA404YuL1pVrCVNscpC1b6cw4HhBAdV5rBTr6iEQMnggf4kw6nRy5x xP9kFY2Yd4+9S6jI9MTGjNz+oUOAHcJDT2bKtbg1DnZLEnTYA0XRh4CbA9Ant
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000600F2150.00000C8D; Mon, 25 Jan 2021 20:51:44 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210124184659.12DF46C068F5@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <7d631821-0dbd-1ac3-5f3f-8fdc3d166a13@tana.it>
Date: Mon, 25 Jan 2021 20:51:43 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210124184659.12DF46C068F5@ary.qy>
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/DtkAAcZe1GDmPsUTFnOw3culSVA>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 25 Jan 2021 19:51:49 -0000

On Sun 24/Jan/2021 19:46:58 +0100 John Levine wrote:
> Here's a concrete proposal for https reporting:
> 
> In draft-ietf-dmarc-aggregate-reporting, in the transport section,
> between Email and Other Methods add:
> 
> Https POST
> 
> The message is an XML file with GZIP compression, sent with an https POST message
> to the given URI as media type application/gzip.
> The data SHOULD contain the filename described in Email transport
> above as the filename in the gzip header. The filename helps recipient
> hosts recognize duplicate reports.
> 
> In draft-ietf-dmarc-dmarcbis section 6.3 under the rua tag, add:
> 
> If there is more than one URI in the value, the URIs are conceptually evaluated from
> left to right and each report is delivered to each URI in turn.
> If a delivery to an "https:" URI succeeds, any subsequent URIs that are not "https:" are ignored.
> This allows a report recipient to prefer https reports while falling back to mailto reports.


Good!  That's much better than any other idea we've been discussing.

Say an external URI overrides a mailto:"u" with a pair https:,mailto: and the 
https: succeeds.  Are mailto: URIs following "u" to be ignored?  Answering yes 
eases the job of a report generator, as it is enough to produce a report and a 
verified list of URIs.  Answering no may seem to ease the composition of DMARC 
records; otherwise one has to pay attention to put external URIs toward the 
end.  Some examples are needed anyway.

You'll have to revert the order in your DMARC record.

Best
Ale
-- 

















From nobody Mon Jan 25 11:52:38 2021
Return-Path: <johnl@iecc.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 109DE3A184D for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=UNZXq1tn; dkim=pass (2048-bit key) header.d=taugh.com header.b=2SaQJ6Xj
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 oyLWTlOF5ItE for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:52:34 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 A85743A184C for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:52:34 -0800 (PST)
Received: (qmail 93606 invoked from network); 25 Jan 2021 19:52:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=16da3.600f2180.k2101; bh=TJII+uxsGPoR7+tJ1Nww6GXYw+KQoELDsfNmaLB4Uyg=; b=UNZXq1tnBKQvWxl6q6Qj2ziDnmcJQMND9j+Ixol2iqDdadI/k8HBBRxB/goq1n17JIj/2n9OZC4gronFJ0BakFn00Oq47dTLa8yGWTXhjzgHzUepzAam0lBv96yEjcwUd/n3hcdFLTeRaEeUZsAr7q8lMhGOP50fxpZWHO785RCsx+8TYjCzX55DFlGYi/vHrLZTaus+zBiFiyfAQvBY7RyIDS4thhN6VlEJJRZTv/ZrdIUMuSROKJQyXKPwuApwrGLddNRrOYzpuSPzLSnlkhw4UBJ4jqwF1/dc+k5cptoDCpXyiQAfqJTCLpN/ldX72gRBrDLowRZ1Pcsz0JI5mA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=16da3.600f2180.k2101; bh=TJII+uxsGPoR7+tJ1Nww6GXYw+KQoELDsfNmaLB4Uyg=; b=2SaQJ6XjJS+oHkykEqDqvOmgUPYXfiXAPrjXI1BSg3iFEvg8tYNoo7pzApU1SD+uRQkax9ZIVisvs/Pq7ICwnDwIkA3WDIvAjAP7Zw/Co3BIRyBP+qKMLRgjJdk4Pb5QqYnaXn4oAnA241kxb+/LQRmqQlIuj7Ou0jT9BEUC+3+2rqrMCpkLvixLGUTc1n1osyffiziQZuxDW3LF0EgEq6h6vfIsZBtBYyAuAP8CgmOurnD+PQ25Um60DK2eJx78f5xMLVnPB2R/tbVI6kG9BxYhzG8+SfSOeFGjuyxoJ7SQBx2/u584HjUFjyz/J5Pp+Zk1VGcMDkOPYcST8xVz7g==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 19:52:32 -0000
Received: by ary.qy (Postfix, from userid 501) id E0DE16C13E26; Mon, 25 Jan 2021 14:52:31 -0500 (EST)
Date: 25 Jan 2021 14:52:31 -0500
Message-Id: <20210125195231.E0DE16C13E26@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dougfoster.emailstandards@gmail.com
In-Reply-To: <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WNAhvY94kg7VQueMzgUsM-ZwvnI>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 19:52:37 -0000

In article <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>DMARC alignment on the report seems of limited value unless it is aligned
>to the domain being reported. ...

I'm getting the impression that some of us have not looked at any DMARC reports.

Aggregate reports contain the domain of the reporter, and the domain
of the sender to whom they are sending the report. They do NOT have
the domains to which the messages were sent or where they were
received, which are often different for forwarded or mailing list mail.

For at least the third time, there is no "domain being reported". When
I get reports from Google or any other multi-tenant mail provider,
they do not say to which of their gazillion hosted domains the mail
was sent. That is not a bug, and it's been like that for a decade. 

R's,
John


From nobody Mon Jan 25 11:53:24 2021
Return-Path: <Alex_Brotman@comcast.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 772C13A1850 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.109
X-Spam-Level: *
X-Spam-Status: No, score=1.109 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, MISSING_HEADERS=1.207, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.com
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 1EaE9chuoHJM for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:53:21 -0800 (PST)
Received: from mx0a-00143702.pphosted.com (mx0a-00143702.pphosted.com [148.163.145.77]) (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 023CC3A184F for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:53:20 -0800 (PST)
Received: from pps.filterd (m0156891.ppops.net [127.0.0.1]) by mx0a-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10PJjpWs019272 for <dmarc@ietf.org>; Mon, 25 Jan 2021 14:53:20 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.com; h=from : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=20190412; bh=qbU2cPwiJLpaQhYUOsvPkE1EIU+jNfqXEIqvMK2MKGk=; b=T+7yhMqz1R2g1UnEbOYAmkFNyeHdTgW2M57NR/nTKxMGnq7wo9idVfrmaaM7Qxde8kV5 6ptAM/WyILwgtWMevHi9zkdVTyQWX+6FWrPcvLUKad0Wi0YLn5dSu9I1JSX8FV19dtq+ VMW8Ozt2Lszoh55EoDymEd9EHpstqmsP3S7ltQ9VEudikpVDC8+WZwufkpBqx3j+UP+6 R/eQ0JFmY9H0eTqt1+32u7Dq/MJeHsef39pM2kbGC443svwjc+PyfG2kCp1ZdzRjHdrl ZqD2Pau6jtHENIdD/9sRi+7YaH7+8UrvlGMH9Tno2ZWLVAXGrjHCI8GPTSErOYzjOH/R 4A== 
Received: from copdcexc35.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0a-00143702.pphosted.com with ESMTP id 368hh0cjxp-8 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Mon, 25 Jan 2021 14:53:20 -0500
Received: from copdcexc33.cable.comcast.com (147.191.125.132) by COPDCEXC35.cable.comcast.com (147.191.125.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 25 Jan 2021 12:53:08 -0700
Received: from COPDCEXEDGE01.cable.comcast.com (96.114.158.213) by copdcexc33.cable.comcast.com (147.191.125.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Mon, 25 Jan 2021 12:53:08 -0700
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.102) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Jan 2021 14:53:10 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by BL0PR11MB3506.namprd11.prod.outlook.com (2603:10b6:208:31::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.13; Mon, 25 Jan 2021 19:52:43 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42%7]) with mapi id 15.20.3784.017; Mon, 25 Jan 2021 19:52:43 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
CC: DMARC IETF <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Discussion - ARC/Extensible Reporting (Ticket #56)
Thread-Index: AdbI4+CbIMDOrFacSCuqUWajtLQ8TwAgvwMAAA97pBAAAfRzAADOhtAAAC42nxAC8UhBgAAllgIABlXaiUA=
Date: Mon, 25 Jan 2021 19:52:43 +0000
Message-ID: <MN2PR11MB43511F9FDADE0A6779870620F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB43512A1BB729A717B6E688DFF7F30@MN2PR11MB4351.namprd11.prod.outlook.com> <d14f03ef-f4fd-1b7a-699c-c670dcd9631c@tana.it> <MN2PR11MB4351A6BF2052A98DF95EA2C6F7F20@MN2PR11MB4351.namprd11.prod.outlook.com> <b00d374d-392c-5383-a4a1-31dc26d8e484@tana.it> <caa661e5-dead-493b-ad27-8fef74b5499f@beta.fastmail.com> <MN2PR11MB43511AD9A2B8C6CF1356491DF7CD0@MN2PR11MB4351.namprd11.prod.outlook.com> <CABZJ8knMmn-DmAQ_5TuDO13Rsu8=f9R2=XG3GFvpL=Uqy5RMJw@mail.gmail.com> <MN2PR11MB43518DB46CF9F6C5A6080C65F7D70@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB43518DB46CF9F6C5A6080C65F7D70@MN2PR11MB4351.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:a15b:1edf:6851:816e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c2daaba5-4d85-4a32-e6be-08d8c16ac789
x-ms-traffictypediagnostic: BL0PR11MB3506:
x-microsoft-antispam-prvs: <BL0PR11MB350667456116A9AC6B945B82F7BD9@BL0PR11MB3506.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FVsCIkNeWHm4h67h+pT+Hrns6AZHPXaCuUeUPa1gH5X3lz/F7J/w4N5WDFrxpBmi18RQaJxo2vE7b22mfN6N5Eo2es1wsjTlmET4Vyf6jfSaSILqKxPbcJSP1yFLTyvToYrzRvjAhMhzMevMZ3RWXHFyCU5b1p/F9IBM3gQc7w/8tixZ51m/FsBV+IVq5cMOcJaP+7ljlMV1/ML2xGy1/2P4Cvmq50NtmT6rWW7jSUFuZ//RtiVcwzHeqFnior+nrs42z19IhlmYJt0T/upewa7oPFEr7p5TewszGHZLAwR8KOWIB6ayPDQmUgqOxva9VLM9CUBNk03AWxAQhkafqL4xVJxkjaOYhp9nugIxZrIIayc0rlOzcIVOGzGev4nXGjm7+EVxATxwlCmXj/KzelyNdgRP7DXZPsKxOx9MVMQhkiAfg0VCEORJCXIzzUZ3yIOR2uEXag+iV3DsIgYoFw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(376002)(346002)(396003)(136003)(39860400002)(66556008)(53546011)(64756008)(66616009)(33656002)(7696005)(66946007)(76116006)(66476007)(99936003)(8676002)(66446008)(186003)(83380400001)(52536014)(6506007)(86362001)(71200400001)(5660300002)(2906002)(166002)(478600001)(4326008)(9686003)(109986005)(966005)(316002)(8936002)(55016002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?TXRsd1VkdE5zU0FZTXVyS1N0c1gzNUI1dHZlWEF4dFVaZjVvdVFTaVdlV003?= =?utf-8?B?K0JsYTZsNU9TSWpEdytrdS9VWTlmSnRnSVlvaTlMTXdXWWY3cUswc21Zd1Uw?= =?utf-8?B?dXp3WFBoUnMzMkRaLy9MU1MzSDBRQVNUMEsxZ2NJakc5TmJJVTRxMnRTdUl1?= =?utf-8?B?L29hQXB0d2JDeW5NNTY5eU94VUh0UXdlRzFpMm1CWjA4dk45dkNVeTNGTlY0?= =?utf-8?B?clpyMjVQZHhuUUFQRUlEZk5KWFcwcktCZlJvYjNmM2VZS0FsN1Vna3owYlBS?= =?utf-8?B?cXZ1cXZDMHFSZnNvQzJKRzZTdDJnaHAxV29GcHFHV2NlZE9LcHRzUHBZMmFr?= =?utf-8?B?NG95WWVpbzdYQWdtY08xZXFrNVB2TWRpQ3pMRlV0djZacFNpTWV5OXBYZCtw?= =?utf-8?B?cVI3MEVEOWF3WTBvd0t3ZWp3M2NCY3FTUWdpUmsxT0ZhVW9BaDFDSGhwMnBa?= =?utf-8?B?Rmd1cWVyK2RMZS9LaXZ4UUlNQk5HWnc3K2FKL0NZZzNhRkVBaWpWaXRGOTZl?= =?utf-8?B?Y1hQdTI5N3o5U1dOWUF2Z01pbVJRa3ExOWFnUzA2VVdTQ0dyZkp6bGlZWndF?= =?utf-8?B?NmJEQmpqZGtLSXl2NXVIMEJIM2lXRzVoam9jd2hZbWs0ajlzdWRSNXYxUVpL?= =?utf-8?B?TWlNK0VxZS9VOXVrUTJMSUtTOUx6QVpOVXMvRjM4bGIxQVJWZlhMSE5vQi9U?= =?utf-8?B?T2poUEZ3cU5mZlRPdUZSZytNM3FrY3FLOGh5dVp0emhQME5TT0dHOXBlN1k0?= =?utf-8?B?UkJXZ3BkdktXYlNiTEtBSGRORGZ3NUR1bnRlSUh4VUthU2hPMk1ub3lLRzVv?= =?utf-8?B?cmJzcXNoOFVVZ3hWbTRWQUk0UXFtcjdOeHBWZEEzekZKSzF2QVhYMzRuUDUr?= =?utf-8?B?L3ovcUYyNzE3SFg2WlR2OGgzZ2ZudTIyclhycmJFTUhwblBnRDliY2JmYVNy?= =?utf-8?B?RHRGQkFRTU1mYVZ1Y0d3cGJvNXB5ZXFmRDZkWHZpdjdKU21EQURoNmhsVVE2?= =?utf-8?B?Z0JCUWtwNHlUYkphL1B0VmlYRGhwUkJaNkJab2tGWllGWWo1eTdRMEk4Zklo?= =?utf-8?B?UW0vejFLWngxc1FrcFlVWWdRaWpsQUYxMHZtTk44L25Qc3VTK0lpRytwRmQw?= =?utf-8?B?ZFNDbHErSmhBTEVDTktpOUlPd0ZlUGszRnYvbE1KUDNuUnR6RXJtZVlaL3Bk?= =?utf-8?B?bU00Y2s5ajFzQlFZT0lKeVBON3pKYnExdW9Va2JzQkhONTFybWd2SFFDQTFI?= =?utf-8?B?MG5sWXBlbWgzSWsxZ1NJZ2o2bDZFNWdFSDBPS0cxbU9XZG1nZUFpbzZxYXBZ?= =?utf-8?B?MkFXVkJZd2gwNEhGN1lGM3QwUlhNZld2ajFzbzJtMGFDRHBXTk9ubzF4OFBZ?= =?utf-8?B?ckhIOXhCYlRpVkQ0NlNOTzhsS0JzdXFxYUc0bkNMWldYOVBNT09IdXBFbm9z?= =?utf-8?B?bG9KNmlqQnd0Z3U4ZE0vRGQ4clBWRmVMTVgyRXdsTEVIMUpOYzJ2c2hpSUYy?= =?utf-8?Q?j92VSxZUlxWU0fia3eGfvnPX9rT?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YsM8jPF9R7lGHlvTpS+BKBLHkOchSC+8TvJMISQmGPV0/nOzIOQcE6mwXI8GJ4XTrkas4tWIwNTZ9QQBx5XkjI3ZPxHYnHmF1lz+Erxj27LiufbJ4821qR119L86sztdgFx66WxrZAc0oPmwg/mvBlH7hgN6MDl0XKouLfn0NvMfkmHg0eA5GivCq7b3AILEqsUuGFdfy+Y/+TFPZtD8pBij65dgiw82g/zd7iLc5jMgcI/O1gULB2j84SGtFtjdG/Z25AgasRXgHRgDhXRwwKm2EsyHuFgii2QrPUnOnu+bvnkWItNTDNl4a+rsYc3jdYRq36T8s5H3kUWyZvw0qA==
arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RI+mpvA2vXS8bIkdwXqfUkm7dq0yo/PT3ltNXe8u6zE=; b=m8HZfAvP1ZaD5m0QrL2mcwOq+LRdPPfZQ5wMPpzSNcR6++xL+Xp/edrZwX6i67Quo/IS+gOXPxxcM6lSp2/8G1nLi/ChEJOnqNC1z1RqRUF6A7ffEGrkE/LfHeRY8O1iFDEnt2N5ItEgL5PLWYqJ4qmJIZpj0WbUr7d25Wljo9XMWM8lXxn88zNIUN2b3S4LwAzf659qKmELj5RGGCuNZhv+drlsnm1/Jf4y1aHtjs+4e0hwRSc+NLp189z3eDekdoLATVJ4u9+MPC5sHmYHvy3HxPq15TvMi/Ewwo5pxY+3jHodg0owP/fh5gVZRjI88g6GRn/vxNBTlPQ0oRvmIg==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=comcast.com; dmarc=pass action=none header.from=comcast.com; dkim=pass header.d=comcast.com; arc=none
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: MN2PR11MB4351.namprd11.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: c2daaba5-4d85-4a32-e6be-08d8c16ac789
x-ms-exchange-crosstenant-originalarrivaltime: 25 Jan 2021 19:52:43.0913 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 906aefe9-76a7-4f65-b82d-5ec20775d5aa
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: qSk5F1uxAWOPPHYPR+QNhH2cao4LLSHhC8zm6dnTKuWy62B7KsimBmN4ZbJM2BalxJyaMqQNLDCpMT6zAZga/jEEh9BkTA0q4Q59UIC5opA=
x-ms-exchange-transport-crosstenantheadersstamped: BL0PR11MB3506
x-originatororg: comcast.com
Content-Type: multipart/related; boundary="_004_MN2PR11MB43511F9FDADE0A6779870620F7BD9MN2PR11MB4351namp_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWA
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-25_08:2021-01-25, 2021-01-25 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QjPXfjKX1eO7MEcpxzjnaUHXDAw>
Subject: Re: [dmarc-ietf] Discussion - ARC/Extensible Reporting (Ticket #56)
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, 25 Jan 2021 19:53:23 -0000

--_004_MN2PR11MB43511F9FDADE0A6779870620F7BD9MN2PR11MB4351namp_
Content-Type: multipart/alternative;
 boundary="_000_MN2PR11MB43511F9FDADE0A6779870620F7BD9MN2PR11MB4351namp_"

--_000_MN2PR11MB43511F9FDADE0A6779870620F7BD9MN2PR11MB4351namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhpcyB0aHJlYWQgdGFpbGVkIG9mZiBvdmVyIHRoZSBob2xpZGF5cy4gIEZvciB0aGUgbW9tZW50
LCBJ4oCZdmUgaW5jbHVkZWQgYSBzbWFsbCBzZWN0aW9uIGluIHRoZSBkcmFmdCB0aGF0IGFsbG93
cyBmb3IgYW4gb3B0aW9uYWwg4oCcZXh0ZW5zaW9uc+KAnSBlbGVtZW50IGluIHRoZSBhZ2dyZWdh
dGUgZHJhZnQsIGJlaW5nIG9wdGlvbmFsIGZvciBib3RoIHJlcG9ydCBjcmVhdGlvbi9pbmdlc3Rp
b24uICAgSeKAmWQgYmUgaGFwcHkgdG8gd29yayB3aXRoIHNvbWVvbmUgd2hvIGhhcyBhbiBpZGVh
IG9mIHdoYXQgYW4gQVJDIHJlcG9ydCBzaG91bGQgbG9vayBsaWtlIGlmIGl0IHdlcmUgdG8gYmUg
YSBzZWxmLWNvbnRhaW5lZCBwaWVjZSBvZiBYTUwgd2l0aGluIHRoZSBtYWluIERNQVJDIHJlcG9y
dC4gIFRoYXQgY291bGQgaGVscCBkcml2ZSB0aGlzIHNlY3Rpb24gYXMgd2UgbW92ZSBmb3J3YXJk
Lg0KDQotLQ0KQWxleCBCcm90bWFuDQpTci4gRW5naW5lZXIsIEFudGktQWJ1c2UgJiBNZXNzYWdp
bmcgUG9saWN5DQpDb21jYXN0DQoNCkZyb206IGRtYXJjIDxkbWFyYy1ib3VuY2VzQGlldGYub3Jn
PiBPbiBCZWhhbGYgT2YgQnJvdG1hbiwgQWxleA0KU2VudDogV2VkbmVzZGF5LCBEZWNlbWJlciAz
MCwgMjAyMCA0OjQ5IFBNDQpUbzogRW1pbCBHdXN0YWZzc29uIDxlbWd1PTQwZ29vZ2xlLmNvbUBk
bWFyYy5pZXRmLm9yZz4NCkNjOiBNYXJjIEJyYWRzaGF3IDxtYXJjQG1hcmNicmFkc2hhdy5uZXQ+
OyBETUFSQyBJRVRGIDxkbWFyY0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbZG1hcmMtaWV0Zl0g
RGlzY3Vzc2lvbiAtIEFSQy9FeHRlbnNpYmxlIFJlcG9ydGluZyAoVGlja2V0ICM1NikNCg0KDQpX
ZeKAmXZlIGFscmVhZHkgbWVudGlvbmVkIEFSQy4gIENvdWxkIGl0IGFsc28gYmUgZXh0ZW5kZWQg
dG8gYWxsb3cgZm9yIERvbWFpbiBSZXB1dGF0aW9uIHJlcG9ydGluZyBiYWNrIHRvIHRoZSBzZW5k
ZXI/ICBJbnN0ZWFkIG9mIGEgY2VudHJhbCBhY2Nlc3MgcG9pbnQsIHRoZSBkYXRhIGlzIHNlbnQg
cGVyaW9kaWNhbGx5IHRvIHRoZSBkb21haW4gaG9sZGVyLCBhbmQgdGhleSBjYW4gdGhlbiB1dGls
aXplIHRoZSBkYXRhIGFzIHRoZXkgc2VlIGZpdC4gIEkgY291bGQgYWxzbyBzZWUgYSB1c2UgY2Fz
ZSBmb3IgQklNSSByZXBvcnRpbmcuICBJ4oCZbSBzdXJlIG90aGVycyBjb3VsZCB0aGluayBvZiBv
dGhlciB1c2UgY2FzZXMuDQoNCklmIHdlIHByZWZlciBpdCB0byBleGlzdCBvdXRzaWRlIG9mIHRo
ZSBtYWluIGJvZHkgb2YgZGF0YSwgaXQgbWF5IHJlc3VsdCBpbiBkdXBsaWNhdGlvbiBvZiBkYXRh
LCBidXQgYWxzbyBhbGxvd3MgZm9yIG1vcmUgZmxleGliaWxpdHkuIFRoaXMgYWxsb3dzIHRoZSBv
cmlnaW5hbCBETUFSQyBBZ2dyZWdhdGUgZGF0YSB0byByZW1haW4gY29uc2lzdGVudCBhcyB3ZWxs
LiAgT24gdGhlIG90aGVyIGhhbmQsIGFsbG93aW5nIGl0IHRvIGV4aXN0IHdpdGhpbiB0aGUgcmVj
b3JkIGVsZW1lbnRzIHdvdWxkIGFsbG93IGl0IHRvIGJlIG1vcmUgZWFzaWx5IGNvcnJlbGF0ZWQg
d2l0aCB0aGUgZXhpc3RpbmcgZGF0YS4gIEkgdGhpbmsgbXkgKHNsaWdodCkgcHJlZmVyZW5jZSAo
YXMgYSByZXBvcnQgaGFuZGxlcikgaXMgdG8gaGF2ZSBpdCBvdXRzaWRlIG9mIHRoZSBtYWluIGJv
ZHkgb2YgdGhlIHJlcG9ydCwgYnV0IEkgY291bGQgYmUgc3dheWVkLg0KDQoNCi0tDQpBbGV4IEJy
b3RtYW4NClNyLiBFbmdpbmVlciwgQW50aS1BYnVzZSAmIE1lc3NhZ2luZyBQb2xpY3kNCkNvbWNh
c3QNCg0KRnJvbTogRW1pbCBHdXN0YWZzc29uIDxlbWd1PTQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRm
Lm9yZzxtYWlsdG86ZW1ndT00MGdvb2dsZS5jb21AZG1hcmMuaWV0Zi5vcmc+Pg0KU2VudDogV2Vk
bmVzZGF5LCBEZWNlbWJlciAyMywgMjAyMCAyOjQ5IFBNDQpUbzogQnJvdG1hbiwgQWxleCA8QWxl
eF9Ccm90bWFuQGNvbWNhc3QuY29tPG1haWx0bzpBbGV4X0Jyb3RtYW5AY29tY2FzdC5jb20+Pg0K
Q2M6IE1hcmMgQnJhZHNoYXcgPG1hcmNAbWFyY2JyYWRzaGF3Lm5ldDxtYWlsdG86bWFyY0BtYXJj
YnJhZHNoYXcubmV0Pj47IERNQVJDIElFVEYgPGRtYXJjQGlldGYub3JnPG1haWx0bzpkbWFyY0Bp
ZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTogW2RtYXJjLWlldGZdIERpc2N1c3Npb24gLSBBUkMvRXh0
ZW5zaWJsZSBSZXBvcnRpbmcgKFRpY2tldCAjNTYpDQoNCldoaWxlIHRoZSBjb21tb24gZm9ybWF0
IHdvdWxkIGJlIGdyZWF0IGFzIGEgY29uc3VtZXIgb2YgcmVwb3J0cywgSSdtIHdvbmRlcmluZyBo
b3cgbWFueSBkaWZmZXJlbnQgcmVwb3J0cyB0aGVyZSB3b3VsZCBiZS4gTmV3IGF1dGggc3RhbmRh
cmRzIGRvbid0IHBvcCB1cCB0aGF0IG9mdGVuLCBzbyB3aGF0IG90aGVyIHJlcG9ydHMgYXJlIHlv
dSB0aGlua2luZyBhYm91dD8gSSBjYW4gc2VlIHR3byBvYnZpb3VzIGNhbmRpZGF0ZXM7IHRoZSBt
YWlsc2VydmVyIHNvZnR3YXJlIGFuZCB0aGUgc3BhbS9hYnVzZSBwcmV2ZW50aW9uIHNvZnR3YXJl
LiBJdCB3b3VsZCBiZSBpbnRlcmVzdGluZyB0byBzdXBwb3J0IHNvbWV0aGluZyBsaWtlIHRoYXQg
dG9vIGJ1dCBzaG91bGRuJ3QgdGhvc2UganVzdCBwdXQgdGhlIHJlc3VsdHMgaW5zaWRlIHRoZSBk
a2ltL3NwZi9hcmMgYXV0aF9yZXN1bHRzPw0KL0UNCg0KT24gVHVlLCBEZWMgOCwgMjAyMCBhdCAx
MjoyOSBQTSBCcm90bWFuLCBBbGV4IDxBbGV4X0Jyb3RtYW49NDBjb21jYXN0LmNvbUBkbWFyYy5p
ZXRmLm9yZzxtYWlsdG86NDBjb21jYXN0LmNvbUBkbWFyYy5pZXRmLm9yZz4+IHdyb3RlOg0KSSBm
ZWVsIChhcyBhIHJlY2VpdmVyIG9mIHJlcG9ydHMpIGFzIHRob3VnaCBhbm90aGVyIHJlYXNvbiB0
byBoYXZlIHRoZXNlIGFzIGEgc2luZ2xlIHJlcG9ydCBpcyBzbyB0aGF0IHRoZSByZWNlaXZlciBv
ZiB0aGUgcmVwb3J0IGlzIGFibGUgdG8gbW9yZSBlYXNpbHkgY29ycmVsYXRlIHRoZSBkYXRhL3Rp
bWVzLiAgSSBzaG91bGQgYmUgYWJsZSB0byBiZWxpZXZlIHRoYXQgYWxsIHJlcG9ydHMgKHdpdGhv
dXQgYSBzcGVjaWZpZWQgcmkpIHdpbGwgYmUgMDAwMC0yMzU5LCB0aG91Z2ggdGhpbmdzIGhhcHBl
biwgYW5kIHN5c3RlbXMgYnJlYWsgZG93bi4NCg0KLS0NCkFsZXggQnJvdG1hbg0KU3IuIEVuZ2lu
ZWVyLCBBbnRpLUFidXNlICYgTWVzc2FnaW5nIFBvbGljeQ0KQ29tY2FzdA0KDQpGcm9tOiBkbWFy
YyA8ZG1hcmMtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86ZG1hcmMtYm91bmNlc0BpZXRmLm9yZz4+
IE9uIEJlaGFsZiBPZiBNYXJjIEJyYWRzaGF3DQpTZW50OiBNb25kYXksIERlY2VtYmVyIDcsIDIw
MjAgNToxNyBQTQ0KVG86IERNQVJDIElFVEYgPGRtYXJjQGlldGYub3JnPG1haWx0bzpkbWFyY0Bp
ZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTogW2RtYXJjLWlldGZdIERpc2N1c3Npb24gLSBBUkMvRXh0
ZW5zaWJsZSBSZXBvcnRpbmcgKFRpY2tldCAjNTYpDQoNCg0KVGhlcmUgaXMgdmFsdWUgaW4gaW5j
bHVkaW5nIHRoZXNlIGluIG9uZSByZXBvcnQsIGVzcGVjaWFsbHkgd2hlcmUgdGhlIGV4dGVuZGVk
IHByb3BlcnR5IGJlaW5nIHJlcG9ydGVkIG9uIGluZmx1ZW5jZXMgaG93IERNQVJDIGlzIGV2YWx1
YXRlZC4NCg0KVXNpbmcgQVJDIGFzIHRoZSBleGFtcGxlLCB3aGVuIGEgcD1yZWplY3QgcG9saWN5
IHdhcyBvdmVycmlkZW4gYnkgdGhlIHJlY2VpdmVyIGJlY2F1c2Ugb2YgYW4gQVJDIGV2YWx1YXRp
b24sIHdoZW4gdGhhdCBkYXRhIGlzIGluY2x1ZGVkIGluIHRoZSByZXBvcnQgdGhlIGluZGlyZWN0
IG1haWwgZmxvdyBjYW4gYmUgY2xlYXJseSBzZWVuLCB3aGljaCB3b3VsZCBub3QgYmUgdGhlIGNh
c2UgaWYgQVJDIHdlcmUgaW5jbHVkZWQgYXMgYSBzZXBhcmF0ZSByZXBvcnQuDQoNClRoaXMgY291
bGQgYmUgaW5jbHVkZWQgaW4gYW4gPGV4dGVuc2lvbj4gZWxlbWVudCwgb3IgY291bGQgYmUgaW5j
bHVkZWQgZGlyZWN0bHkgaW4gdGhlIGF1dGhfcmVzdWx0cyBzZWN0aW9uIG9mIHRoZSByZXBvcnQs
IGJhc2VkIG9uIGFuIGFzc3VtcHRpb24gdGhhdCB0aGUgdGhpbmdzIGJlaW5nIHJlcG9ydGVkIFNI
T1VMRCBoYXZlIGFuIGF1dGhlbnRpY2F0aW9uIHJlc3VsdHMgZW50cnkgaW4gcHJvY2Vzc2VkIG1h
aWwuDQoNCjxhdXRoX3Jlc3VsdHM+DQo8ZGtpbT4uLi48L2RraW0+DQo8c3BmPi4uLjwvc3BmPg0K
PGFyYz4gKGFzIGRlZmluZWQgaW4gYXJjIHN0YW5kYXJkKSA8L2FyYz4NCjxmb28+IChhcyBkZWZp
bmVkIGluIGZvbyBzdGFuZGFyZCkgPC9mb28+DQo8L2F1dGhfcmVzdWx0cz4NCg0KVGhlc2Ugd291
bGQgYmUgZGVmaW5lZCBpbiBhIHJlZ2lzdHJ5IHdpdGggcmVmZXJlbmNlIHRvIGVhY2ggc3RhbmRh
cmQsIGFuZCBwYXJzZXJzIHdvdWxkIGlnbm9yZSBhbnkgc2VjdGlvbnMgdGhleSBkaWQgbm90IHVu
ZGVyc3RhbmQuDQoNCk9uIEZyaSwgNCBEZWMgMjAyMCwgYXQgNjo0MyBBTSwgQWxlc3NhbmRybyBW
ZXNlbHkgd3JvdGU6DQpPbiBUaHUgMDMvRGVjLzIwMjAgMTk6NTQ6NTEgKzAxMDAgQnJvdG1hbiwg
QWxleCB3cm90ZToNCj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiBGcm9tOiBk
bWFyYyA8ZG1hcmMtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86ZG1hcmMtYm91bmNlc0BpZXRmLm9y
Zz4+IE9uIEJlaGFsZiBPZiBBbGVzc2FuZHJvIFZlc2VseQ0KPj4gU2VudDogVGh1cnNkYXksIERl
Y2VtYmVyIDMsIDIwMjAgNjoyNCBBTQ0KPj4gVG86IGRtYXJjQGlldGYub3JnPG1haWx0bzpkbWFy
Y0BpZXRmLm9yZz4NCj4+IFN1YmplY3Q6IFJlOiBbZG1hcmMtaWV0Zl0gRGlzY3Vzc2lvbiAtIEFS
Qy9FeHRlbnNpYmxlIFJlcG9ydGluZyAoVGlja2V0ICM1NikNCj4+DQo+PiBPbiBXZWQgMDIvRGVj
LzIwMjAgMjA6NDY6NTQgKzAxMDAgQnJvdG1hbiwgQWxleCB3cm90ZToNCj4+Pg0KPj4+IFdoaWxl
IHRoaXMgdGlja2V0L2VuaGFuY2VtZW50IHNwZWNpZmljYWxseSBtZW50aW9ucyBBUkMsIEkgY291
bGQNCj4+PiBwZXJoYXBzIHNlZSB0aGUgdXNlZnVsbmVzcyBpbiBvdGhlciBwbGFjZXMuICBJdCBz
ZWVtcyBsaWtlIGl0IHdvdWxkIGJlDQo+Pj4gbW9yZSBiZW5lZmljaWFsIHRvIGNyZWF0ZSBhIG1l
dGhvZCBieSB3aGljaCBvdGhlciBkb2N1bWVudHMgY291bGQNCj4+PiBwcm92aWRlIFhNTC0gYmFz
ZWQgImV4dGVuc2lvbnMiIHRvIHRoZSByZXBvcnQuICBUaGlzIHdvdWxkIGFsbG93DQo+Pj4gbWVj
aGFuaXNtcyByZWx5aW5nIG9uIERNQVJDIHRvIGluZGVwZW5kZW50bHkgZGVmaW5lIHRoZWlyIHJl
cG9ydGluZw0KPj4+IHNjaGVtYSB0byBiZSBpbmNsdWRlZCBpbiBETUFSQyBhZ2dyZWdhdGUgcmVw
b3J0cy4gIEFsdGVybmF0ZWx5LCB3ZSBjb3VsZA0KPj4+IGZvY3VzIHNwZWNpZmljYWxseSBvbiBB
UkMsIGFuZCB3b3JrIHRvIGluY2x1ZGUgdGhhdCBpbiB0aGUgYmFzZSBYTUwuDQo+Pj4gVGhpcyBt
ZWFucyB0aGF0IGFueSBsYXRlciByZXBvcnRpbmcgcmVxdWlyZW1lbnRzIGNvdWxkIGFnYWluIHJl
cXVpcmUNCj4+PiBjaGFuZ2VzIHRvIHRoZSBjb3JlIGRyYWZ0cy4+Pj4NCj4+DQo+Pg0KPj4gQW5v
dGhlciBwb3NzaWJpbGl0eSBpcyBmb3IgQVJDIHRvIGRlZmluZSBpdHMgb3duIHJlcG9ydCBmb3Jt
YXQuICBIaWphY2tpbmcNCj4+IHJ1YT0gdGFyZ2V0cyB0byBzZW5kIGEgZGlmZmVyZW50IGtpbmQg
b2YgcmVwb3J0IHNob3VsZCBiZSBhbGxvd2VkLg0KPj4gT3RoZXJ3aXNlLCB3ZSBjb3VsZCBkZWZp
bmUgYSBuZXcgdGFnLCBlLmcuIHJ1ZT0gKGUgZm9yIEV4dGVuc2lvbikuPj4NCj4+IEluIGVpdGhl
ciBjYXNlLCBhcyB3ZSdyZSBpbnRyb2R1Y2UgdmFyaWF0aW9ucyBpbiBhZ2dyZWdhdGUgcmVwb3J0
IGNvbnRlbnQsDQo+PiB3ZSBoYXZlIHRvIGRldmlzZSBhIG1ldGhvZCBmb3IgZGV0ZXJtaW5pbmcg
d2hhdCB2ZXJzaW9uL2tpbmQgb2YgcmVwb3J0IGlzDQo+PiBhdHRhY2hlZCB0byBhIGdpdmVuIG1l
c3NhZ2UuPj4NCj4NCj4gV2UgY291bGQgYWRkIGFuIGVsZW1lbnQgY2FsbGVkICI8ZXh0ZW5zaW9u
cz4iLCBhbmQgd2UgYWxsb3cgQVJDIG9yIHdoYXRldmVyDQo+IGl0IG1heSBiZSB0byBleGlzdCB1
bmRlciB0aGF0IGVsZW1lbnQuICBUaGUgQWdncmVnYXRlIFJlcG9ydGluZyBkb2N1bWVudA0KPiBu
ZWVkcyB0byBzcGVjaWZ5IHRoYXQgYW55IGV4dGVuc2lvbnMgYXJlIGV4cGVjdGVkIHRvIGJlIHBy
b3BlciBYTUwsIGFuZCBpZg0KPiB0aGVyZSBhcmUgbm8gZXh0ZW5zaW9ucywgYW4gZW1wdHkgZWxl
bWVudCBpcyBzdWZmaWNpZW50LiAgV2UgY291bGQgY3JlYXRlIGENCj4gYml0IG1vcmUgc3RydWN0
dXJlIGFzIGEgcmVxdWlyZW1lbnQgaWYgd2Ugd2FudGVkOj4NCj4gPGV4dGVuc2lvbnM+DQo+ICAg
IDxleHRlbnNpb24gbmFtZT0iYXJjIiBzdGFuZGFyZD0iQVJDX0RNQVJDX1JFUE9SVElOR19FWFRF
TlNJT05fREVGSU5JVElPTiI+DQo+ICAgICAgLi4uIChhcyBkZWZpbmVkIGluIHJlZmVyZW5jZWQg
c3RhbmRhcmQpDQo+ICAgIDwvZXh0ZW5zaW9uPg0KPiA8L2V4dGVuc2lvbnM+DQo+DQo+IElmIGEg
cmVwb3J0IHBhcnNlciBkb2Vzbid0IGtub3cgd2hhdCBBUkMgaXMgKG9yIGFueSBvZiB0aGUgZXh0
ZW5zaW9ucyksIGl0IGNvdWxkIHNraXAgdGhlIHByb2Nlc3NpbmcuICBJIGRvIHVuZGVyc3RhbmQg
dGhpcyBtZWFucyB0aGF0IDxleHRlbnNpb25zPiBlbGVtZW50IG1heSBicmVhayBleGlzdGluZyBw
YXJzZXJzLCBldmVuIHdoZW4gZW1wdHksIHRob3VnaCwgSSBleHBlY3QgbWFueSBvZiB0aGUgdGhp
bmdzIHdlJ3JlIHByb3Bvc2luZyBtYXkgZnJhY3R1cmUgdGhlIGV4cGVjdGVkIFhNTC4NCg0KDQpX
ZSBjYW4gZG8gYSBiZXR0ZXIgam9iIGF0IHByb2R1Y2luZyBhZ2dyZWdhdGUgcmVwb3J0cyB3aXRo
IGFuIGF1dG9tYXRpY2FsbHkgdmVyaWZpYWJsZSBjb250ZW50LiAgRm9yIGV4YW1wbGUsIHByZXBl
bmRpbmcgc3R1ZmYgbGlrZSB0aGlzOg0KDQo8P3htbCB2ZXJzaW9uPSIxLjAiIGVuY29kaW5nPSJV
VEYtOCI/Pg0KPGRtYXJjOmZlZWRiYWNrIHhtbG5zOnhzPSJodHRwOi8vd3d3LnczLm9yZy8yMDAx
L1hNTFNjaGVtYS1pbnN0YW5jZTxodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cDovd3d3
LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZV9fOyEhQ1FsM21jSFgyQSFXX3hEWFZ4NzA3
Z2M2MU01VEFoMXQxQ0w2MXdwajU3QkhuZGJ0RnhVTG54THpnZ3JYblpmWExEUDVUNlBDVzVtcW1D
RSQ+Ig0KeG1sbnM6ZG1hcmM9Imh0dHA6Ly9kbWFyYy5vcmcvZG1hcmMteG1sLzAuMTxodHRwczov
L3VybGRlZmVuc2UuY29tL3YzL19faHR0cDovZG1hcmMub3JnL2RtYXJjLXhtbC8wLjFfXzshIUNR
bDNtY0hYMkEhV194RFhWeDcwN2djNjFNNVRBaDF0MUNMNjF3cGo1N0JIbmRidEZ4VUxueEx6Z2dy
WG5aZlhMRFA1VDZQQ1hfN0hDdl8kPiINCnhzOnNjaGVtYUxvY2F0aW9uPSJodHRwOi8vZG1hcmMu
b3JnL2RtYXJjLXhtbC8wLjE8aHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHA6L2RtYXJj
Lm9yZy9kbWFyYy14bWwvMC4xX187ISFDUWwzbWNIWDJBIVdfeERYVng3MDdnYzYxTTVUQWgxdDFD
TDYxd3BqNTdCSG5kYnRGeFVMbnhMemdnclhuWmZYTERQNVQ2UENYXzdIQ3ZfJD4gcnVhLnhzZCI+
DQo8cmVwb3J0X21ldGFkYXRhPg0KICAgICAgICAuLi4NCg0KKFBlcmhhcHMgc29tZXRoaW5nIGJl
dHRlciB0aGFuICJodHRwOi8vZG1hcmMub3JnL2RtYXJjLXhtbC8wLjE8aHR0cHM6Ly91cmxkZWZl
bnNlLmNvbS92My9fX2h0dHA6L2RtYXJjLm9yZy9kbWFyYy14bWwvMC4xX187ISFDUWwzbWNIWDJB
IVdfeERYVng3MDdnYzYxTTVUQWgxdDFDTDYxd3BqNTdCSG5kYnRGeFVMbnhMemdnclhuWmZYTERQ
NVQ2UENYXzdIQ3ZfJD4iIGZvciB0aGUgdmVyc2lvbikNCg0KQnV0IHRoZW4sIHdvdWxkIHRoZSA8
ZXh0ZW5zaW9ucz4gaW1wbHkgZG1hcmMteG1sIGdyYW1tYXIgc2hvdWxkIGJlIHVwZ3JhZGVkIGV2
ZXJ5IHRpbWUgQVJDIChvciB3aGF0ZXZlcikgaXMgdXBncmFkZWQ/DQoNClNlcGFyYXRlIHJlcG9y
dHMgc291bmRzIHNpbXBsZXIuDQoNCg0KQmVzdA0KQWxlDQotLQ0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQpkbWFyYyBtYWlsaW5nIGxpc3QNCmRtYXJjQGlldGYub3JnPG1haWx0bzpkbWFyY0Bp
ZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZG1hcmM8aHR0
cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHBzOi93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9kbWFyY19fOyEhQ1FsM21jSFgyQSFXX3hEWFZ4NzA3Z2M2MU01VEFoMXQxQ0w2MXdwajU3
QkhuZGJ0RnhVTG54THpnZ3JYblpmWExEUDVUNlBDY3A4SkFaciQ+DQoNCg0KLS0NCltJbWFnZSBy
ZW1vdmVkIGJ5IHNlbmRlci5dDQoNCiAgTWFyYyBCcmFkc2hhdw0KICBtYXJjYnJhZHNoYXcubmV0
PGh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwOi9tYXJjYnJhZHNoYXcubmV0L19fOyEh
Q1FsM21jSFgyQSFXX3hEWFZ4NzA3Z2M2MU01VEFoMXQxQ0w2MXdwajU3QkhuZGJ0RnhVTG54THpn
Z3JYblpmWExEUDVUNlBDY3duc1Q4WiQ+IHwgQG1hcmNicmFkc2hhdzxodHRwczovL3VybGRlZmVu
c2UuY29tL3YzL19faHR0cHM6L3R3aXR0ZXIuY29tL21hcmNicmFkc2hhd19fOyEhQ1FsM21jSFgy
QSFXX3hEWFZ4NzA3Z2M2MU01VEFoMXQxQ0w2MXdwajU3QkhuZGJ0RnhVTG54THpnZ3JYblpmWExE
UDVUNlBDWnNnNFA0diQ+DQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KZG1hcmMgbWFpbGluZyBsaXN0DQpkbWFyY0BpZXRmLm9yZzxtYWlsdG86
ZG1hcmNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2Rt
YXJjPGh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vZG1hcmNfXzshIUNRbDNtY0hYMkEhUTBrUjFwOXhHeG5XQUc0aGpsTHBwX3lp
c1cxRGhkNG4zbVJITWxCVGtqbGZyczV6TV9LdVRkOU1RVWR1azg4bVNCTUZJd2UzT3ckPg0K

--_000_MN2PR11MB43511F9FDADE0A6779870620F7BD9MN2PR11MB4351namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIg
MTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6TWVubG87fQ0K
LyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5N
c29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQpzcGFuLmdtYWlsLW0tNTIwOTk1MTIyMDI0NjA3NTg5MWZvbnQNCgl7bXNvLXN0eWxl
LW5hbWU6Z21haWwtbV8tNTIwOTk1MTIyMDI0NjA3NTg5MWZvbnQ7fQ0Kc3Bhbi5FbWFpbFN0eWxl
MjENCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXtt
c28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdv
cmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4w
aW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48
L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0i
ZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9
ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8
L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIgc3R5
bGU9IndvcmQtd3JhcDpicmVhay13b3JkIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIHRocmVhZCB0YWlsZWQgb2ZmIG92ZXIgdGhlIGhvbGlk
YXlzLiZuYnNwOyBGb3IgdGhlIG1vbWVudCwgSeKAmXZlIGluY2x1ZGVkIGEgc21hbGwgc2VjdGlv
biBpbiB0aGUgZHJhZnQgdGhhdCBhbGxvd3MgZm9yIGFuIG9wdGlvbmFsIOKAnGV4dGVuc2lvbnPi
gJ0gZWxlbWVudCBpbiB0aGUgYWdncmVnYXRlIGRyYWZ0LCBiZWluZyBvcHRpb25hbCBmb3IgYm90
aCByZXBvcnQgY3JlYXRpb24vaW5nZXN0aW9uLiAmbmJzcDsmbmJzcDtJ4oCZZCBiZSBoYXBweQ0K
IHRvIHdvcmsgd2l0aCBzb21lb25lIHdobyBoYXMgYW4gaWRlYSBvZiB3aGF0IGFuIEFSQyByZXBv
cnQgc2hvdWxkIGxvb2sgbGlrZSBpZiBpdCB3ZXJlIHRvIGJlIGEgc2VsZi1jb250YWluZWQgcGll
Y2Ugb2YgWE1MIHdpdGhpbiB0aGUgbWFpbiBETUFSQyByZXBvcnQuJm5ic3A7IFRoYXQgY291bGQg
aGVscCBkcml2ZSB0aGlzIHNlY3Rpb24gYXMgd2UgbW92ZSBmb3J3YXJkLjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+LS08bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkFsZXggQnJvdG1hbjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U3IuIEVu
Z2luZWVyLCBBbnRpLUFidXNlICZhbXA7IE1lc3NhZ2luZyBQb2xpY3k8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNvbWNhc3Q8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3Jk
ZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4g
NC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQg
I0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxiPkZyb206PC9iPiBkbWFyYyAmbHQ7ZG1hcmMtYm91bmNlc0BpZXRmLm9yZyZndDsg
PGI+T24gQmVoYWxmIE9mIDwvYj4NCkJyb3RtYW4sIEFsZXg8YnI+DQo8Yj5TZW50OjwvYj4gV2Vk
bmVzZGF5LCBEZWNlbWJlciAzMCwgMjAyMCA0OjQ5IFBNPGJyPg0KPGI+VG86PC9iPiBFbWlsIEd1
c3RhZnNzb24gJmx0O2VtZ3U9NDBnb29nbGUuY29tQGRtYXJjLmlldGYub3JnJmd0Ozxicj4NCjxi
PkNjOjwvYj4gTWFyYyBCcmFkc2hhdyAmbHQ7bWFyY0BtYXJjYnJhZHNoYXcubmV0Jmd0OzsgRE1B
UkMgSUVURiAmbHQ7ZG1hcmNAaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBb
ZG1hcmMtaWV0Zl0gRGlzY3Vzc2lvbiAtIEFSQy9FeHRlbnNpYmxlIFJlcG9ydGluZyAoVGlja2V0
ICM1Nik8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+V2XigJl2ZSBhbHJlYWR5IG1lbnRpb25l
ZCBBUkMuJm5ic3A7IENvdWxkIGl0IGFsc28gYmUgZXh0ZW5kZWQgdG8gYWxsb3cgZm9yIERvbWFp
biBSZXB1dGF0aW9uIHJlcG9ydGluZyBiYWNrIHRvIHRoZSBzZW5kZXI/Jm5ic3A7IEluc3RlYWQg
b2YgYSBjZW50cmFsIGFjY2VzcyBwb2ludCwgdGhlIGRhdGEgaXMgc2VudCBwZXJpb2RpY2FsbHkg
dG8gdGhlIGRvbWFpbiBob2xkZXIsIGFuZCB0aGV5IGNhbiB0aGVuIHV0aWxpemUgdGhlIGRhdGEN
CiBhcyB0aGV5IHNlZSBmaXQuJm5ic3A7IEkgY291bGQgYWxzbyBzZWUgYSB1c2UgY2FzZSBmb3Ig
QklNSSByZXBvcnRpbmcuJm5ic3A7IEnigJltIHN1cmUgb3RoZXJzIGNvdWxkIHRoaW5rIG9mIG90
aGVyIHVzZSBjYXNlcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SWYgd2UgcHJlZmVyIGl0IHRv
IGV4aXN0IG91dHNpZGUgb2YgdGhlIG1haW4gYm9keSBvZiBkYXRhLCBpdCBtYXkgcmVzdWx0IGlu
IGR1cGxpY2F0aW9uIG9mIGRhdGEsIGJ1dCBhbHNvIGFsbG93cyBmb3IgbW9yZSBmbGV4aWJpbGl0
eS4gVGhpcyBhbGxvd3MgdGhlIG9yaWdpbmFsIERNQVJDIEFnZ3JlZ2F0ZSBkYXRhIHRvIHJlbWFp
biBjb25zaXN0ZW50IGFzIHdlbGwuJm5ic3A7IE9uIHRoZSBvdGhlciBoYW5kLCBhbGxvd2luZw0K
IGl0IHRvIGV4aXN0IHdpdGhpbiB0aGUgcmVjb3JkIGVsZW1lbnRzIHdvdWxkIGFsbG93IGl0IHRv
IGJlIG1vcmUgZWFzaWx5IGNvcnJlbGF0ZWQgd2l0aCB0aGUgZXhpc3RpbmcgZGF0YS4mbmJzcDsg
SSB0aGluayBteSAoc2xpZ2h0KSBwcmVmZXJlbmNlIChhcyBhIHJlcG9ydCBoYW5kbGVyKSBpcyB0
byBoYXZlIGl0IG91dHNpZGUgb2YgdGhlIG1haW4gYm9keSBvZiB0aGUgcmVwb3J0LCBidXQgSSBj
b3VsZCBiZSBzd2F5ZWQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LS08bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkFsZXggQnJvdG1hbjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+U3IuIEVuZ2luZWVyLCBBbnRpLUFidXNlICZhbXA7IE1lc3NhZ2luZyBQb2xpY3k8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNvbWNhc3Q8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGlu
IDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlk
ICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48Yj5Gcm9tOjwvYj4gRW1pbCBHdXN0YWZzc29uICZsdDs8YSBocmVmPSJtYWlsdG86
ZW1ndT00MGdvb2dsZS5jb21AZG1hcmMuaWV0Zi5vcmciPmVtZ3U9NDBnb29nbGUuY29tQGRtYXJj
LmlldGYub3JnPC9hPiZndDsNCjxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIERlY2VtYmVy
IDIzLCAyMDIwIDI6NDkgUE08YnI+DQo8Yj5Ubzo8L2I+IEJyb3RtYW4sIEFsZXggJmx0OzxhIGhy
ZWY9Im1haWx0bzpBbGV4X0Jyb3RtYW5AY29tY2FzdC5jb20iPkFsZXhfQnJvdG1hbkBjb21jYXN0
LmNvbTwvYT4mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBNYXJjIEJyYWRzaGF3ICZsdDs8YSBocmVmPSJt
YWlsdG86bWFyY0BtYXJjYnJhZHNoYXcubmV0Ij5tYXJjQG1hcmNicmFkc2hhdy5uZXQ8L2E+Jmd0
OzsgRE1BUkMgSUVURiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRtYXJjQGlldGYub3JnIj5kbWFyY0Bp
ZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbZG1hcmMtaWV0Zl0gRGlz
Y3Vzc2lvbiAtIEFSQy9FeHRlbnNpYmxlIFJlcG9ydGluZyAoVGlja2V0ICM1Nik8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaGlsZSB0aGUgY29tbW9uIGZv
cm1hdCB3b3VsZCBiZSBncmVhdCBhcyBhIGNvbnN1bWVyIG9mIHJlcG9ydHMsIEknbSB3b25kZXJp
bmcgaG93IG1hbnkgZGlmZmVyZW50Jm5ic3A7cmVwb3J0cyB0aGVyZSB3b3VsZCBiZS4gTmV3IGF1
dGggc3RhbmRhcmRzIGRvbid0IHBvcCB1cCB0aGF0IG9mdGVuLCBzbyB3aGF0IG90aGVyIHJlcG9y
dHMgYXJlIHlvdSB0aGlua2luZyBhYm91dD8gSSBjYW4gc2VlIHR3byBvYnZpb3VzIGNhbmRpZGF0
ZXM7DQogdGhlIG1haWxzZXJ2ZXImbmJzcDtzb2Z0d2FyZSBhbmQgdGhlIHNwYW0vYWJ1c2UgcHJl
dmVudGlvbiBzb2Z0d2FyZS4gSXQgd291bGQgYmUgaW50ZXJlc3RpbmcgdG8gc3VwcG9ydCBzb21l
dGhpbmcgbGlrZSB0aGF0IHRvbyBidXQgc2hvdWxkbid0IHRob3NlIGp1c3QgcHV0IHRoZSByZXN1
bHRzIGluc2lkZSB0aGUgZGtpbS9zcGYvYXJjIGF1dGhfcmVzdWx0cz88bzpwPjwvbzpwPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4vRTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUdWUsIERlYyA4LCAyMDIwIGF0IDEyOjI5
IFBNIEJyb3RtYW4sIEFsZXggJmx0O0FsZXhfQnJvdG1hbj08YSBocmVmPSJtYWlsdG86NDBjb21j
YXN0LmNvbUBkbWFyYy5pZXRmLm9yZyI+NDBjb21jYXN0LmNvbUBkbWFyYy5pZXRmLm9yZzwvYT4m
Z3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4g
MGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0
OjBpbjttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj5JIGZlZWwgKGFzIGEgcmVjZWl2ZXIgb2YgcmVwb3J0cykgYXMgdGhvdWdoIGFub3Ro
ZXIgcmVhc29uIHRvIGhhdmUgdGhlc2UgYXMgYSBzaW5nbGUgcmVwb3J0IGlzIHNvIHRoYXQgdGhl
IHJlY2VpdmVyIG9mIHRoZSByZXBvcnQgaXMgYWJsZSB0byBtb3JlIGVhc2lseSBjb3JyZWxhdGUg
dGhlIGRhdGEvdGltZXMuJm5ic3A7DQogSSBzaG91bGQgYmUgYWJsZSB0byBiZWxpZXZlIHRoYXQg
YWxsIHJlcG9ydHMgKHdpdGhvdXQgYSBzcGVjaWZpZWQgcmkpIHdpbGwgYmUgMDAwMC0yMzU5LCB0
aG91Z2ggdGhpbmdzIGhhcHBlbiwgYW5kIHN5c3RlbXMgYnJlYWsgZG93bi48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj4tLTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj5BbGV4IEJyb3RtYW48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+U3IuIEVuZ2luZWVyLCBBbnRpLUFidXNlICZhbXA7IE1lc3NhZ2luZyBQb2xpY3k8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Q29tY2FzdDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPjxiPkZyb206PC9iPiBkbWFyYyAmbHQ7PGEgaHJlZj0ibWFp
bHRvOmRtYXJjLWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5kbWFyYy1ib3VuY2Vz
QGlldGYub3JnPC9hPiZndDsNCjxiPk9uIEJlaGFsZiBPZiA8L2I+TWFyYyBCcmFkc2hhdzxicj4N
CjxiPlNlbnQ6PC9iPiBNb25kYXksIERlY2VtYmVyIDcsIDIwMjAgNToxNyBQTTxicj4NCjxiPlRv
OjwvYj4gRE1BUkMgSUVURiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRtYXJjQGlldGYub3JnIiB0YXJn
ZXQ9Il9ibGFuayI+ZG1hcmNAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBS
ZTogW2RtYXJjLWlldGZdIERpc2N1c3Npb24gLSBBUkMvRXh0ZW5zaWJsZSBSZXBvcnRpbmcgKFRp
Y2tldCAjNTYpPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj5UaGVyZSBpcyB2YWx1ZSBpbiBpbmNsdWRpbmcgdGhlc2UgaW4gb25lIHJlcG9ydCwg
ZXNwZWNpYWxseSB3aGVyZSB0aGUgZXh0ZW5kZWQgcHJvcGVydHkgYmVpbmcgcmVwb3J0ZWQgb24g
aW5mbHVlbmNlcyBob3cgRE1BUkMgaXMgZXZhbHVhdGVkLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+VXNpbmcgQVJDIGFzIHRoZSBleGFt
cGxlLCB3aGVuIGEgcD1yZWplY3QgcG9saWN5IHdhcyBvdmVycmlkZW4gYnkgdGhlIHJlY2VpdmVy
IGJlY2F1c2Ugb2YgYW4gQVJDIGV2YWx1YXRpb24sIHdoZW4gdGhhdCBkYXRhIGlzIGluY2x1ZGVk
IGluIHRoZSByZXBvcnQgdGhlIGluZGlyZWN0IG1haWwgZmxvdyBjYW4NCiBiZSBjbGVhcmx5IHNl
ZW4sIHdoaWNoIHdvdWxkIG5vdCBiZSB0aGUgY2FzZSBpZiBBUkMgd2VyZSBpbmNsdWRlZCBhcyBh
IHNlcGFyYXRlIHJlcG9ydC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPlRoaXMgY291bGQgYmUgaW5jbHVkZWQgaW4gYW4gJmx0O2V4dGVu
c2lvbiZndDsgZWxlbWVudCwgb3IgY291bGQgYmUgaW5jbHVkZWQgZGlyZWN0bHkgaW4gdGhlIGF1
dGhfcmVzdWx0cyBzZWN0aW9uIG9mIHRoZSByZXBvcnQsIGJhc2VkIG9uIGFuIGFzc3VtcHRpb24g
dGhhdCB0aGUgdGhpbmdzIGJlaW5nIHJlcG9ydGVkDQogU0hPVUxEIGhhdmUgYW4gYXV0aGVudGlj
YXRpb24gcmVzdWx0cyBlbnRyeSBpbiBwcm9jZXNzZWQgbWFpbC48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGNsYXNzPSJnbWFp
bC1tLTUyMDk5NTEyMjAyNDYwNzU4OTFmb250Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6TWVu
bG8iPiZsdDthdXRoX3Jlc3VsdHMmZ3Q7PC9zcGFuPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gY2xhc3M9ImdtYWlsLW0t
NTIwOTk1MTIyMDI0NjA3NTg5MWZvbnQiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpNZW5sbyI+
Jmx0O2RraW0mZ3Q7Li4uJmx0Oy9ka2ltJmd0Ozwvc3Bhbj48L3NwYW4+PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGNsYXNzPSJnbWFp
bC1tLTUyMDk5NTEyMjAyNDYwNzU4OTFmb250Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6TWVu
bG8iPiZsdDtzcGYmZ3Q7Li4uJmx0Oy9zcGYmZ3Q7PC9zcGFuPjwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gY2xhc3M9Imdt
YWlsLW0tNTIwOTk1MTIyMDI0NjA3NTg5MWZvbnQiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpN
ZW5sbyI+Jmx0O2FyYyZndDsgKGFzIGRlZmluZWQgaW4gYXJjIHN0YW5kYXJkKSAmbHQ7L2FyYyZn
dDs8L3NwYW4+PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBjbGFzcz0iZ21haWwtbS01MjA5OTUxMjIwMjQ2MDc1ODkxZm9u
dCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5Ok1lbmxvIj4mbHQ7Zm9vJmd0OyAoYXMgZGVmaW5l
ZCBpbiBmb28gc3RhbmRhcmQpICZsdDsvZm9vJmd0Ozwvc3Bhbj48L3NwYW4+PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGNsYXNzPSJn
bWFpbC1tLTUyMDk5NTEyMjAyNDYwNzU4OTFmb250Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
TWVubG8iPiZsdDsvYXV0aF9yZXN1bHRzJmd0Ozwvc3Bhbj48L3NwYW4+PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaGVzZSB3b3VsZCBi
ZSBkZWZpbmVkIGluIGEgcmVnaXN0cnkgd2l0aCByZWZlcmVuY2UgdG8gZWFjaCBzdGFuZGFyZCwg
YW5kIHBhcnNlcnMgd291bGQgaWdub3JlIGFueSBzZWN0aW9ucyB0aGV5IGRpZCBub3QgdW5kZXJz
dGFuZC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPk9uIEZyaSwgNCBEZWMgMjAyMCwgYXQgNjo0MyBBTSwgQWxlc3NhbmRybyBWZXNlbHkg
d3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4t
dG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiIGlkPSJnbWFpbC1tXy01MjA5OTUxMjIwMjQ2
MDc1ODkxcXQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+T24gVGh1IDAzL0RlYy8y
MDIwIDE5OjU0OjUxICYjNDM7MDEwMCBCcm90bWFuLCBBbGV4IHdyb3RlOjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jm5ic3A7PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmZ3Q7
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmZ3Q7IEZyb206IGRtYXJjICZsdDs8YSBocmVm
PSJtYWlsdG86ZG1hcmMtYm91bmNlc0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmRtYXJjLWJv
dW5jZXNAaWV0Zi5vcmc8L2E+Jmd0OyBPbiBCZWhhbGYgT2YgQWxlc3NhbmRybyBWZXNlbHk8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jmd0OyZn
dDsgU2VudDogVGh1cnNkYXksIERlY2VtYmVyIDMsIDIwMjAgNjoyNCBBTTxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jmd0OyBUbzombmJz
cDs8YSBocmVmPSJtYWlsdG86ZG1hcmNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5kbWFyY0Bp
ZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jmd0OyZndDsgU3ViamVjdDogUmU6IFtkbWFyYy1pZXRmXSBEaXNjdXNzaW9uIC0g
QVJDL0V4dGVuc2libGUgUmVwb3J0aW5nIChUaWNrZXQgIzU2KTxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jmd0OyZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jmd0OyBP
biBXZWQgMDIvRGVjLzIwMjAgMjA6NDY6NTQgJiM0MzswMTAwIEJyb3RtYW4sIEFsZXggd3JvdGU6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZn
dDsmZ3Q7Jmd0OyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj4mZ3Q7Jmd0OyZndDsgV2hpbGUgdGhpcyB0aWNrZXQvZW5oYW5jZW1lbnQg
c3BlY2lmaWNhbGx5IG1lbnRpb25zIEFSQywgSSBjb3VsZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jmd0OyZndDsgcGVyaGFwcyBzZWUg
dGhlIHVzZWZ1bG5lc3MgaW4gb3RoZXIgcGxhY2VzLiZuYnNwOyBJdCBzZWVtcyBsaWtlIGl0IHdv
dWxkIGJlPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPiZndDsmZ3Q7Jmd0OyBtb3JlIGJlbmVmaWNpYWwgdG8gY3JlYXRlIGEgbWV0aG9kIGJ5IHdo
aWNoIG90aGVyIGRvY3VtZW50cyBjb3VsZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jmd0OyZndDsgcHJvdmlkZSBYTUwtIGJhc2VkICZx
dW90O2V4dGVuc2lvbnMmcXVvdDsgdG8gdGhlIHJlcG9ydC4mbmJzcDsgVGhpcyB3b3VsZCBhbGxv
dzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4m
Z3Q7Jmd0OyZndDsgbWVjaGFuaXNtcyByZWx5aW5nIG9uIERNQVJDIHRvIGluZGVwZW5kZW50bHkg
ZGVmaW5lIHRoZWlyIHJlcG9ydGluZzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jmd0OyZndDsgc2NoZW1hIHRvIGJlIGluY2x1ZGVkIGlu
IERNQVJDIGFnZ3JlZ2F0ZSByZXBvcnRzLiZuYnNwOyBBbHRlcm5hdGVseSwgd2UgY291bGQ8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jmd0OyZn
dDsmZ3Q7IGZvY3VzIHNwZWNpZmljYWxseSBvbiBBUkMsIGFuZCB3b3JrIHRvIGluY2x1ZGUgdGhh
dCBpbiB0aGUgYmFzZSBYTUwuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPiZndDsmZ3Q7Jmd0OyBUaGlzIG1lYW5zIHRoYXQgYW55IGxhdGVyIHJl
cG9ydGluZyByZXF1aXJlbWVudHMgY291bGQgYWdhaW4gcmVxdWlyZTxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jmd0OyZndDsgY2hhbmdl
cyB0byB0aGUgY29yZSBkcmFmdHMuJmd0OyZndDsmZ3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmZ3Q7Jm5ic3A7PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmZ3Q7Jm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZn
dDsmZ3Q7IEFub3RoZXIgcG9zc2liaWxpdHkgaXMgZm9yIEFSQyB0byBkZWZpbmUgaXRzIG93biBy
ZXBvcnQgZm9ybWF0LiZuYnNwOyBIaWphY2tpbmc8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jmd0OyZndDsgcnVhPSB0YXJnZXRzIHRvIHNlbmQg
YSBkaWZmZXJlbnQga2luZCBvZiByZXBvcnQgc2hvdWxkIGJlIGFsbG93ZWQuPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmZ3Q7IE90aGVy
d2lzZSwgd2UgY291bGQgZGVmaW5lIGEgbmV3IHRhZywgZS5nLiBydWU9IChlIGZvciBFeHRlbnNp
b24pLiZndDsmZ3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPiZndDsmZ3Q7IEluIGVpdGhlciBjYXNlLCBhcyB3ZSdyZSBpbnRyb2R1Y2UgdmFy
aWF0aW9ucyBpbiBhZ2dyZWdhdGUgcmVwb3J0IGNvbnRlbnQsPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmZ3Q7IHdlIGhhdmUgdG8gZGV2
aXNlIGEgbWV0aG9kIGZvciBkZXRlcm1pbmluZyB3aGF0IHZlcnNpb24va2luZCBvZiByZXBvcnQg
aXMmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+Jmd0OyZndDsgYXR0YWNoZWQgdG8gYSBnaXZlbiBtZXNzYWdlLiZndDsmZ3Q7PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
Jmd0OyBXZSBjb3VsZCBhZGQgYW4gZWxlbWVudCBjYWxsZWQgJnF1b3Q7Jmx0O2V4dGVuc2lvbnMm
Z3Q7JnF1b3Q7LCBhbmQgd2UgYWxsb3cgQVJDIG9yIHdoYXRldmVyPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsgaXQgbWF5IGJlIHRvIGV4
aXN0IHVuZGVyIHRoYXQgZWxlbWVudC4mbmJzcDsgVGhlIEFnZ3JlZ2F0ZSBSZXBvcnRpbmcgZG9j
dW1lbnQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jmd0OyBuZWVkcyB0byBzcGVjaWZ5IHRoYXQgYW55IGV4dGVuc2lvbnMgYXJlIGV4cGVjdGVk
IHRvIGJlIHByb3BlciBYTUwsIGFuZCBpZjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7IHRoZXJlIGFyZSBubyBleHRlbnNpb25zLCBhbiBl
bXB0eSBlbGVtZW50IGlzIHN1ZmZpY2llbnQuJm5ic3A7IFdlIGNvdWxkIGNyZWF0ZSBhPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsgYml0
IG1vcmUgc3RydWN0dXJlIGFzIGEgcmVxdWlyZW1lbnQgaWYgd2Ugd2FudGVkOiZndDsmbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jmd0
OyAmbHQ7ZXh0ZW5zaW9ucyZndDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyAmbHQ7ZXh0ZW5zaW9uIG5h
bWU9JnF1b3Q7YXJjJnF1b3Q7IHN0YW5kYXJkPSZxdW90O0FSQ19ETUFSQ19SRVBPUlRJTkdfRVhU
RU5TSU9OX0RFRklOSVRJT04mcXVvdDsmZ3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgLi4uIChhcyBkZWZpbmVkIGluIHJlZmVyZW5jZWQgc3RhbmRhcmQpPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsmbmJzcDsmbmJzcDsm
bmJzcDsgJmx0Oy9leHRlbnNpb24mZ3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsgJmx0Oy9leHRlbnNpb25zJmd0OzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mZ3Q7Jm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZndDsg
SWYgYSByZXBvcnQgcGFyc2VyIGRvZXNuJ3Qga25vdyB3aGF0IEFSQyBpcyAob3IgYW55IG9mIHRo
ZSBleHRlbnNpb25zKSwgaXQgY291bGQgc2tpcCB0aGUgcHJvY2Vzc2luZy4mbmJzcDsgSSBkbyB1
bmRlcnN0YW5kIHRoaXMgbWVhbnMgdGhhdCAmbHQ7ZXh0ZW5zaW9ucyZndDsgZWxlbWVudCBtYXkg
YnJlYWsgZXhpc3RpbmcNCiBwYXJzZXJzLCBldmVuIHdoZW4gZW1wdHksIHRob3VnaCwgSSBleHBl
Y3QgbWFueSBvZiB0aGUgdGhpbmdzIHdlJ3JlIHByb3Bvc2luZyBtYXkgZnJhY3R1cmUgdGhlIGV4
cGVjdGVkIFhNTC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj5XZSBjYW4gZG8gYSBiZXR0ZXIgam9iIGF0IHByb2R1Y2luZyBhZ2dy
ZWdhdGUgcmVwb3J0cyB3aXRoIGFuIGF1dG9tYXRpY2FsbHkgdmVyaWZpYWJsZSBjb250ZW50LiZu
YnNwOyBGb3IgZXhhbXBsZSwgcHJlcGVuZGluZyBzdHVmZiBsaWtlIHRoaXM6PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbHQ7P3htbCB2
ZXJzaW9uPSZxdW90OzEuMCZxdW90OyBlbmNvZGluZz0mcXVvdDtVVEYtOCZxdW90Oz8mZ3Q7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZsdDtk
bWFyYzpmZWVkYmFjayB4bWxuczp4cz0mcXVvdDs8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2Uu
Y29tL3YzL19faHR0cDovd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZV9fOyEhQ1Fs
M21jSFgyQSFXX3hEWFZ4NzA3Z2M2MU01VEFoMXQxQ0w2MXdwajU3QkhuZGJ0RnhVTG54THpnZ3JY
blpmWExEUDVUNlBDVzVtcW1DRSQiIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vd3d3LnczLm9yZy8y
MDAxL1hNTFNjaGVtYS1pbnN0YW5jZTwvYT4mcXVvdDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+eG1sbnM6ZG1hcmM9JnF1b3Q7PGEgaHJlZj0i
aHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHA6L2RtYXJjLm9yZy9kbWFyYy14bWwvMC4x
X187ISFDUWwzbWNIWDJBIVdfeERYVng3MDdnYzYxTTVUQWgxdDFDTDYxd3BqNTdCSG5kYnRGeFVM
bnhMemdnclhuWmZYTERQNVQ2UENYXzdIQ3ZfJCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly9kbWFy
Yy5vcmcvZG1hcmMteG1sLzAuMTwvYT4mcXVvdDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+eHM6c2NoZW1hTG9jYXRpb249JnF1b3Q7PGEgaHJl
Zj0iaHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHA6L2RtYXJjLm9yZy9kbWFyYy14bWwv
MC4xX187ISFDUWwzbWNIWDJBIVdfeERYVng3MDdnYzYxTTVUQWgxdDFDTDYxd3BqNTdCSG5kYnRG
eFVMbnhMemdnclhuWmZYTERQNVQ2UENYXzdIQ3ZfJCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly9k
bWFyYy5vcmcvZG1hcmMteG1sLzAuMTwvYT4NCiBydWEueHNkJnF1b3Q7Jmd0OzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbHQ7cmVwb3J0X21l
dGFkYXRhJmd0OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgLi4uPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4o
UGVyaGFwcyBzb21ldGhpbmcgYmV0dGVyIHRoYW4gJnF1b3Q7PGEgaHJlZj0iaHR0cHM6Ly91cmxk
ZWZlbnNlLmNvbS92My9fX2h0dHA6L2RtYXJjLm9yZy9kbWFyYy14bWwvMC4xX187ISFDUWwzbWNI
WDJBIVdfeERYVng3MDdnYzYxTTVUQWgxdDFDTDYxd3BqNTdCSG5kYnRGeFVMbnhMemdnclhuWmZY
TERQNVQ2UENYXzdIQ3ZfJCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly9kbWFyYy5vcmcvZG1hcmMt
eG1sLzAuMTwvYT4mcXVvdDsNCiBmb3IgdGhlIHZlcnNpb24pPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5CdXQgdGhlbiwgd291bGQgdGhl
ICZsdDtleHRlbnNpb25zJmd0OyBpbXBseSBkbWFyYy14bWwgZ3JhbW1hciBzaG91bGQgYmUgdXBn
cmFkZWQgZXZlcnkgdGltZSBBUkMgKG9yIHdoYXRldmVyKSBpcyB1cGdyYWRlZD88bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlNlcGFyYXRl
IHJlcG9ydHMgc291bmRzIHNpbXBsZXIuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+QmVzdDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5BbGU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+LS0mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5kbWFyYyBtYWlsaW5nIGxpc3Q8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PGEg
aHJlZj0ibWFpbHRvOmRtYXJjQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZG1hcmNAaWV0Zi5v
cmc8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vZG1hcmNfXzshIUNRbDNtY0hYMkEhV194RFhWeDcwN2djNjFN
NVRBaDF0MUNMNjF3cGo1N0JIbmRidEZ4VUxueEx6Z2dyWG5aZlhMRFA1VDZQQ2NwOEpBWnIkIiB0
YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbWFy
YzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
IGlkPSJnbWFpbC1tXy01MjA5OTUxMjIwMjQ2MDc1ODkxc2lnNjM2OTUxMTMiPg0KPGRpdiBpZD0i
Z21haWwtbV8tNTIwOTk1MTIyMDI0NjA3NTg5MXNpZzIxNTAzMzEzIj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPi0tPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8dGFibGUg
Y2xhc3M9Ik1zb05vcm1hbFRhYmxlIiBib3JkZXI9IjAiIGNlbGxzcGFjaW5nPSIzIiBjZWxscGFk
ZGluZz0iMCI+DQo8dGJvZHk+DQo8dHI+DQo8dGQgc3R5bGU9InBhZGRpbmc6Ljc1cHQgLjc1cHQg
Ljc1cHQgLjc1cHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iYm9yZGVy
OnNvbGlkIHdpbmRvd3RleHQgMS4wcHQ7cGFkZGluZzowaW4iPjxpbWcgYm9yZGVyPSIwIiB3aWR0
aD0iMTAwIiBoZWlnaHQ9IjEwMCIgc3R5bGU9IndpZHRoOjEuMDQxNmluO2hlaWdodDoxLjA0MTZp
biIgaWQ9ImdtYWlsLW1fLTUyMDk5NTEyMjAyNDYwNzU4OTFfeDAwNWZfeDAwMDBfaTEwMjUiIHNy
Yz0iY2lkOmltYWdlMDAxLmpwZ0AwMUQ2RjMyOS4zNDJGNDQ5MCIgYWx0PSJJbWFnZSByZW1vdmVk
IGJ5IHNlbmRlci4iPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvdGQ+DQo8dGQgc3R5bGU9InBh
ZGRpbmc6Ljc1cHQgLjc1cHQgLjc1cHQgLjc1cHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+Jm5ic3A7IE1hcmMgQnJhZHNoYXc8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly91cmxk
ZWZlbnNlLmNvbS92My9fX2h0dHA6L21hcmNicmFkc2hhdy5uZXQvX187ISFDUWwzbWNIWDJBIVdf
eERYVng3MDdnYzYxTTVUQWgxdDFDTDYxd3BqNTdCSG5kYnRGeFVMbnhMemdnclhuWmZYTERQNVQ2
UENjd25zVDhaJCIgdGFyZ2V0PSJfYmxhbmsiPm1hcmNicmFkc2hhdy5uZXQ8L2E+DQogfCZuYnNw
OzxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovdHdpdHRlci5jb20v
bWFyY2JyYWRzaGF3X187ISFDUWwzbWNIWDJBIVdfeERYVng3MDdnYzYxTTVUQWgxdDFDTDYxd3Bq
NTdCSG5kYnRGeFVMbnhMemdnclhuWmZYTERQNVQ2UENac2c0UDR2JCIgdGFyZ2V0PSJfYmxhbmsi
PkBtYXJjYnJhZHNoYXc8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvdGQ+DQo8L3RyPg0K
PC90Ym9keT4NCjwvdGFibGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KZG1hcmMgbWFpbGluZyBsaXN0PGJy
Pg0KPGEgaHJlZj0ibWFpbHRvOmRtYXJjQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZG1hcmNA
aWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0
dHBzOi93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbWFyY19fOyEhQ1FsM21jSFgyQSFR
MGtSMXA5eEd4bldBRzRoamxMcHBfeWlzVzFEaGQ0bjNtUkhNbEJUa2psZnJzNXpNX0t1VGQ5TVFV
ZHVrODhtU0JNRkl3ZTNPdyQiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2RtYXJjPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_MN2PR11MB43511F9FDADE0A6779870620F7BD9MN2PR11MB4351namp_--

--_004_MN2PR11MB43511F9FDADE0A6779870620F7BD9MN2PR11MB4351namp_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=823;
 creation-date="Mon, 25 Jan 2021 19:52:42 GMT";
 modification-date="Mon, 25 Jan 2021 19:52:42 GMT"
Content-ID: <image001.jpg@01D6F329.342F4490>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCABkAGQDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+iii
gAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKA
CiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAK
KKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAoo
ooAKKKKACiiigAooooAKKKKACiiigD//2Q==

--_004_MN2PR11MB43511F9FDADE0A6779870620F7BD9MN2PR11MB4351namp_--


From nobody Mon Jan 25 11:54:00 2021
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 14A753A1852 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:53:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 UvG-eHyYGTpV for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:53:58 -0800 (PST)
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 152DD3A1851 for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:53:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611604435; bh=MVBLuEgWip5YcojC0R1BD74k0xA3/uN9BKFZDuaEeKo=; l=169; h=To:References:From:Date:In-Reply-To; b=AbH5QuoIAhDE7eBI7+eI8/8NcbmVmefN5sI+PGN7w1/1mATV2jtCKXHqXZ48O0XsA Zov54jbcGcG212cwJ/VlpK8Mhzxu4MwfiarSSdqDbic6m7zOaKrJycJxTmh7l2R+YO DYy6UzJkdd+3Hl4M3w5J/RKtgv5FMeT46zYl1vttU/1qTZmK5EX/4b+5kjOOh
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0DC.00000000600F21D3.00000CF8; Mon, 25 Jan 2021 20:53:55 +0100
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210124184659.12DF46C068F5@ary.qy> <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <afe0e8fd-bbac-9e0d-859c-0fdfcf83978a@tana.it>
Date: Mon, 25 Jan 2021 20:53:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.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/r4jKrFkxIds-XkAK4nFhH4xhvzw>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 25 Jan 2021 19:53:59 -0000

On Sun 24/Jan/2021 19:49:34 +0100 Michael Thomas wrote:
> issue #99 needs to be addressed.


Won't we put a DKIM-Signature: in the http: header?


Best
Ale
-- 
















From nobody Mon Jan 25 11:55:46 2021
Return-Path: <mike@fresheez.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 3D98C3A174C for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:55:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 ffKVBG7XaEhe for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 11:55:38 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE00B3A187B for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:55:37 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id q131so9009712pfq.10 for <dmarc@ietf.org>; Mon, 25 Jan 2021 11:55:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=3P1uNJc+qB0GDXJU6+TH8ZPOim2oBdGx6sKghchMg0M=; b=fp1J8jbobMn4h/4yhir/rhVVegHJnNOGi+WnWQNN93uI/k2uQwZewEi1GGdQkVpZC9 B+0WKR+etPNvuh4FcFzOd9/6g2y1EIY2ZRVc4fxMPyCmVyUxt1KxM5hgwilM4ofJB1Gf A7oKimfPgGy/VZFPtVgqrnl3NncK/GQx4myZIkFSMqku6/DwV8Yjvb8/ydjm+/K3L3Sr kcE80NtdZnVEFnGsj5krkiCNrlmYZNmFA0Cf8qJgEzARrvcSazFvFp8UsY9IAUusCVMb GlqiGst1uB8YQxJZhf6LTakvDF0ThRlutaLypnPwr5n9F8EUbAVAiRZWxKhHlZ7nyt4S 0W6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=3P1uNJc+qB0GDXJU6+TH8ZPOim2oBdGx6sKghchMg0M=; b=nxy+LS+Yn+S86T3t9UbM1215orB8eeKeu5SuuLzaEJ+efABVDmon1Uk8G9RQW88aw4 AL9HmBa4dN28VRm+/+TWk8K9dJtjjRi6boNOw8mHWXaWJAKWLQ2sDYkCV1Ocrnh/loBG 4+aoaxwJzgm70ei9BUTpIlJZHUOfNj0/o2nGc/8AMEPwy+C8Uij0qNyW3kNT6nIt9uTz 07rG4XD7o22s1RR0LQR4u/SIbxZ72bSESa3Px+RlJXE3DtfL3mzk6MCOsZPbtU0O9+oE U212JnrJG0zUtMEBq8ijSnIwwAbTswdszKnu0UFlZUVVFtqskBUbwOupcigaNUd/rtbI gIow==
X-Gm-Message-State: AOAM530oaZ3Qn6cDSCv+SH1QkE6Ca3tCj/4lGr+ecckuROdt7g8qSYez AkWrKMqVfOfLSfKUiMukgYENS2I5cSshmg==
X-Google-Smtp-Source: ABdhPJxwHLmt/7+MCcXOiZ1QiRJKwp1TjklR1i7EegGa3Y2zez923SQFCC1WJJTRCGLoJoEfY+KCyQ==
X-Received: by 2002:a05:6a00:88b:b029:19c:780e:1cd with SMTP id q11-20020a056a00088bb029019c780e01cdmr1828166pfj.64.1611604537002;  Mon, 25 Jan 2021 11:55:37 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id x21sm17521810pgi.75.2021.01.25.11.55.35 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 11:55:36 -0800 (PST)
To: dmarc@ietf.org
References: <20210125195231.E0DE16C13E26@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <12abca41-4420-37c7-c903-7decc012027a@mtcc.com>
Date: Mon, 25 Jan 2021 11:55:35 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210125195231.E0DE16C13E26@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/L5cdWIbZLow-47Yw8Fc8bcFxsdw>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 19:55:44 -0000

On 1/25/21 11:52 AM, John Levine wrote:
> In article <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com> you write:
>> -=-=-=-=-=-
>>
>> DMARC alignment on the report seems of limited value unless it is aligned
>> to the domain being reported. ...
> I'm getting the impression that some of us have not looked at any DMARC reports.
>
> Aggregate reports contain the domain of the reporter, and the domain
> of the sender to whom they are sending the report. They do NOT have
> the domains to which the messages were sent or where they were
> received, which are often different for forwarded or mailing list mail.
>
> For at least the third time, there is no "domain being reported". When
> I get reports from Google or any other multi-tenant mail provider,
> they do not say to which of their gazillion hosted domains the mail
> was sent. That is not a bug, and it's been like that for a decade.
>
Sounds like a bug to me and an issue should be opened. Just because it's 
a 10 year old bug doesn't mean it's not a bug.

Mike


From nobody Mon Jan 25 12:06:10 2021
Return-Path: <johnl@taugh.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 E86713A186A for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:06:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=c1UOYTC1; dkim=pass (2048-bit key) header.d=taugh.com header.b=nJJ6EG2i
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 NoKVzfFHeKwr for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:06:07 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 3EB553A1868 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:06:07 -0800 (PST)
Received: (qmail 97651 invoked from network); 25 Jan 2021 20:06:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type; s=17d6a.600f24ae.k2101; bh=a6FGVL3aErlqKBxMdIOD1zyWfc7iWMMDb4fsrJWnhgk=; b=c1UOYTC1VZTc6IkzHtQQwAL9uTbVEq0rX1ikDP+Uht+G1vPnnMq3ROMRWOIU4jvvyIBBe1vtUe5r0cYd1LaZvMYZ8JRVIgMaMYpQbytTNJdPKm9Hjekalc4Ph+3pyp9cKeRcwf5/gmq5tsLmu+indQPD8yIehvbFd7YdUMjMG633KmdRSR7yZlfpGh9KqQjuwnT7qQSlWhhuUuSneQ81KDOF72r7zsw4WoDOhdqgFjFtD1uICR/xTTRykSXLO+X6sByCPXwlQsy8fZrhiF9WkZw9SJ6V1ORnF4wapq3AufCk9GWstIQXZJFEXMA/ZPfgqoJsHiZTsM1PlKjy6H1FJg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type; s=17d6a.600f24ae.k2101; bh=a6FGVL3aErlqKBxMdIOD1zyWfc7iWMMDb4fsrJWnhgk=; b=nJJ6EG2iIilVR/fbRrDS8Yy0CpFCzx/elTrH9KRel7SQ3pFVh7g6w1Y+ZP480wh8aQfSMj3LCiPNTEV0akGyfHS1VIJUEi6nLuA78jzpj9soJcgRlIOdPnPiOI4o8igWxY6DwgdUTyZX/RLN2VU1pkcM94j94QaiPreSKpVlr24v/2rUp65xJinhbbR+TjB1DPaNY6ksltjXg+mKsZptYQyiCUlsDmVpT3B/EG8oibz5vht5VNk1p2pwVlSPHaQhhQFsqxpU9L1rhBlsLIPsh9N1BAXxtRMCA8Gz16jeuVEOANMEe6mI4yNQDZgcR9c9BOuYIl01P9PyN/vqzhEoQg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 20:06:05 -0000
Received: by ary.qy (Postfix, from userid 501) id 9895D6C13FB1; Mon, 25 Jan 2021 15:06:05 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 6397F6C13F93 for <dmarc@ietf.org>; Mon, 25 Jan 2021 15:06:05 -0500 (EST)
Date: 25 Jan 2021 15:06:05 -0500
Message-ID: <ed9b7f7f-2737-257f-8148-d94a7c1d383@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: dmarc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/nBX1tmc95gdDyOJHVB1xSGu9-pM>
Subject: [dmarc-ietf] error report in 7.2.2
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, 25 Jan 2021 20:06:09 -0000

Does anyone send the error reports described in section 7.2.2 ?  I've 
never seen one but my reports are all quite small.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Mon Jan 25 12:07:07 2021
Return-Path: <mike@fresheez.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 BF40B3A186A for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:07:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 gtKf77kypqGU for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:07:05 -0800 (PST)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A88383A1868 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:07:05 -0800 (PST)
Received: by mail-pj1-x102d.google.com with SMTP id a20so275934pjs.1 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:07:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=TIABWy5eDnmRY9JZ+90sp8EQ2axQla/1j5/i5jl7yYw=; b=kaiFhsvwtwSr9Mzhh/CKWN9Wmy9oOAKSv9BC99dfaRSH00+1jn0Gi1ShGlAonQlrNX INT2VI7onmzISdjO9G5n6XpAdo683TaNv4c8gBFmYgqoMYEAwdkpCnBkTGw2QVGpX7zA OdqyM1vR8FGeO24DU7G7DO+I7YGGCfsv85RwLSIBgHUX6xw48lfG28Um6nHzoLTQkbPu D191RfjQjtc6lSo7ryqN/25n6aUa+cswHj1veYg19/1DphiA8Lpbn7eeQUsCeNuelVLJ u/KwNFYDYX97lJ6JO/ngn0RokLGIZDdloGyROPigB9EHhqpVMJov2BPrUYeHzyZGt6XD LXcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=TIABWy5eDnmRY9JZ+90sp8EQ2axQla/1j5/i5jl7yYw=; b=CInNu1WjKSZFK054wUcrm2K2L0hsS2m4Ul5g+UnfL0oeD8fNmgoOEAnqbJwScr0yK/ Ti1SJTwDRH/5wNH9kldNDk5zwVzEdmZflvdru8nP9KRCUVVez9+M2ANSxRZMDvprRkpR nwS6lNsvcMGjbb8De62e0pLsddqL505aRwlXdVRuELhDokKySmlVDRl5/CKYR1kbPwzG hyuuEWy6v0uTyrGRi7ncWCyXZqnyrstX1hKHPAi47ohQ4v6acPyAZuYPS4q/oaHF73IH 8FqruQbIRSNSfBeaRqk5jucScvF5o1GRE9YwUbOYvcl89L5x1zxY5gy/xwZELR8Ipf9Q BrXw==
X-Gm-Message-State: AOAM533PeD7XVgymLVBZpY9Uhb5osqu8UlRIRq88b8R8FP8KKYIy2Ouw kugfWtLD0X0ipyqCiWqIcvTQ0cXjOhgB0g==
X-Google-Smtp-Source: ABdhPJwTa8V7shoZO5wK9lqudB1YKKgtRN5yhDPR0zYmBBLPJnly12x3BfemOjyAKFR6SyNGeLiieg==
X-Received: by 2002:a17:90a:9a89:: with SMTP id e9mr1946406pjp.2.1611605224820;  Mon, 25 Jan 2021 12:07:04 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id e68sm16824431pfe.23.2021.01.25.12.07.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 12:07:04 -0800 (PST)
To: Alessandro Vesely <vesely@tana.it>, dmarc@ietf.org
References: <20210124184659.12DF46C068F5@ary.qy> <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com> <afe0e8fd-bbac-9e0d-859c-0fdfcf83978a@tana.it>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <b3c5f861-2a17-afa8-5f62-e9f152b58e1f@mtcc.com>
Date: Mon, 25 Jan 2021 12:07:01 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <afe0e8fd-bbac-9e0d-859c-0fdfcf83978a@tana.it>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/iXyhYxgcVj7Imux1JW5fI0pnJfo>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 25 Jan 2021 20:07:07 -0000

On 1/25/21 11:53 AM, Alessandro Vesely wrote:
> On Sun 24/Jan/2021 19:49:34 +0100 Michael Thomas wrote:
>> issue #99 needs to be addressed.
>
>
> Won't we put a DKIM-Signature: in the http: header?
>
I don't know. That would need to be specified. To me it sounds like a 
good reason to not try to specify http especially if there doesn't seem 
to be any clear desire for it.

Mike


From nobody Mon Jan 25 12:08:42 2021
Return-Path: <todd.herr@valimail.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 D37523A186A for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:08:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 DXISk71lBLrH for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:08:39 -0800 (PST)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEDE73A1868 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:08:38 -0800 (PST)
Received: by mail-qt1-x82c.google.com with SMTP id o18so10612397qtp.10 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:08:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=TQxz3IzuDm9EiiKBlSUzMvsvH22Cl1Rm/EOopvzymPc=; b=bT4MwNKM6/ORz5umoJas7iED8wxZeN2y3E/F7knflT7L7ENL/2aDGCaJS6/dYRf273 a3M3dkeRoawBJwg7siLytcwjyFtp9CgDO+peOXKZgO1kSK8xMcJZhUJ3TKCIhErK1fq0 jpMOwqRONvq+3J2/g8igjEtLV23Iu0gpPGaQdLgyoKORdNOkknzhaeHuI0NDhZN3oKb0 4634gZVy1oOGXEsLvrad9dgm2Vd/pGF7xiY18bn27SR53q9wflJ6BAe4HahUGxELqvV6 AgsirattaVnsMTL5K7Y7TQlkSYpdTfVTNgy4mIqLXw5pF0FhKBvbnr8WsDWkvc9qScbG bE2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=TQxz3IzuDm9EiiKBlSUzMvsvH22Cl1Rm/EOopvzymPc=; b=ps8YFA1YleKRCDIhcPC8RCyQ7UVmL4XBGxl7kaawAfuX8lQF9sQsxzV0digGqgAJen 7sDNS2PnuiBuLxLEh7VyfEdVTngFdROuSbHz+8PjlnKPIsd63jcAcI8ur/1KgKP3YJ28 iWZQ7i1kBT5BHcxKX3WArOhHcAEzis8pg5BHD9AFMflCdkDOhWFF5SirIVmb+DZ/J/tY J0+o4lQ3lcnRU8aNiqeXmjSd3I/85x3K5FfPdjvcUOBB9y2T+q6bpPZMZ4hyL8Y1d5Lg il1apUwnimEcUmwfYTrFBIg9tzAK3lXxFh3KiG2W+PMIguUSWaecY+WYNkrjMG/C5KCo EIfw==
X-Gm-Message-State: AOAM530FNrQKb8Rw7GH5WU8/ScsDiE8e2dd31rxAsr+pFwKKQD5Hmw0q CET2D1zW8LJ50WFt9JqN+q1PFLAOneA42qVzcIeWu0jQNRg=
X-Google-Smtp-Source: ABdhPJxkmfZGfkwc1u6AEuoetwEqXkE/SwDxgWcDGgAby2wA4D/ZN0NwBzjeOUxqzMx1aIs54FGGvMwhpVnpWrTcZcI=
X-Received: by 2002:ac8:4a82:: with SMTP id l2mr2193488qtq.298.1611605317407;  Mon, 25 Jan 2021 12:08:37 -0800 (PST)
MIME-Version: 1.0
References: <20210125195231.E0DE16C13E26@ary.qy> <12abca41-4420-37c7-c903-7decc012027a@mtcc.com>
In-Reply-To: <12abca41-4420-37c7-c903-7decc012027a@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 25 Jan 2021 15:08:21 -0500
Message-ID: <CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000766a1305b9bf1ad7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/idDtxf_80VdRV9wUhsLb6oMdM8I>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 20:08:41 -0000

--000000000000766a1305b9bf1ad7
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/25/21 11:52 AM, John Levine wrote:
> > In article <
> CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com> you
> write:
> >> -=-=-=-=-=-
> >>
> >> DMARC alignment on the report seems of limited value unless it is
> aligned
> >> to the domain being reported. ...
> > I'm getting the impression that some of us have not looked at any DMARC
> reports.
> >
> > Aggregate reports contain the domain of the reporter, and the domain
> > of the sender to whom they are sending the report. They do NOT have
> > the domains to which the messages were sent or where they were
> > received, which are often different for forwarded or mailing list mail.
> >
> > For at least the third time, there is no "domain being reported". When
> > I get reports from Google or any other multi-tenant mail provider,
> > they do not say to which of their gazillion hosted domains the mail
> > was sent. That is not a bug, and it's been like that for a decade.
> >
> Sounds like a bug to me and an issue should be opened. Just because it's
> a 10 year old bug doesn't mean it's not a bug.
>
>
I disagree.

Authentication results should not differ at a given provider based solely
on the destination domain, so there is no reason to report results
separately for each destination domain. Further, there's no value to the
report generators, especially at large sites like Google, to expend the
resources necessary to generate and send X reports when one will do.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000766a1305b9bf1ad7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 25, 2021 at 2:56 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><br>
On 1/25/21 11:52 AM, John Levine wrote:<br>
&gt; In article &lt;<a href=3D"mailto:CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHF=
JzAHWfy1jQ%2BNQg@mail.gmail.com" target=3D"_blank">CAH48ZfwejX1PHO7x1bjJTYy=
ehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com</a>&gt; you write:<br>
&gt;&gt; -=3D-=3D-=3D-=3D-=3D-<br>
&gt;&gt;<br>
&gt;&gt; DMARC alignment on the report seems of limited value unless it is =
aligned<br>
&gt;&gt; to the domain being reported. ...<br>
&gt; I&#39;m getting the impression that some of us have not looked at any =
DMARC reports.<br>
&gt;<br>
&gt; Aggregate reports contain the domain of the reporter, and the domain<b=
r>
&gt; of the sender to whom they are sending the report. They do NOT have<br=
>
&gt; the domains to which the messages were sent or where they were<br>
&gt; received, which are often different for forwarded or mailing list mail=
.<br>
&gt;<br>
&gt; For at least the third time, there is no &quot;domain being reported&q=
uot;. When<br>
&gt; I get reports from Google or any other multi-tenant mail provider,<br>
&gt; they do not say to which of their gazillion hosted domains the mail<br=
>
&gt; was sent. That is not a bug, and it&#39;s been like that for a decade.=
<br>
&gt;<br>
Sounds like a bug to me and an issue should be opened. Just because it&#39;=
s <br>
a 10 year old bug doesn&#39;t mean it&#39;s not a bug.<br>
<br></blockquote><div><br></div><div>I disagree.=C2=A0</div><div><br></div>=
<div>Authentication results should not differ at a given provider based sol=
ely on the destination domain, so there is no reason to report results sepa=
rately for each destination domain. Further, there&#39;s no value to the re=
port generators, especially at large sites like Google, to expend the resou=
rces necessary to generate and send X reports when one will do.</div></div>=
<div><br></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p d=
ir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p=
><div style=3D"text-align:left"><span style=3D"vertical-align:baseline;whit=
e-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span>=
<span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small=
;font-family:Arial"> | Sr. Technical Program Manager</span></div><span styl=
e=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-fami=
ly:Arial"><div style=3D"text-align:left"><span style=3D"vertical-align:base=
line"><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=3D"m=
ailto:todd.herr@valimail.com" target=3D"_blank">todd.herr@valimail.com</a><=
/span></div></span><span><div><span><b>p:</b></span><span> 703.220.4153 </s=
pan><span></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);f=
ont-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(=
255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;vertical-align:baseline;white-space:pre-wrap"><img src=3D"https://l=
h5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYn=
Zu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rj=
z19-Dx9rESL" style=3D"border: none; height: 40px; width: 177px;"></span></p=
><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sa=
ns-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38=
;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"backgrou=
nd-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt=
"><font color=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px=
;white-space:pre-wrap">This email and all data transmitted with it contains=
 confidential and/or proprietary information intended solely for the use of=
 individual(s) authorized to receive it. If you are not an intended and aut=
horized recipient you are hereby notified of any use, disclosure, copying o=
r distribution of the information included in this transmission is prohibit=
ed and may be unlawful. Please immediately notify the sender by replying to=
 this email and then delete it from your system.</span></font></p></span></=
div></div>

--000000000000766a1305b9bf1ad7--


From nobody Mon Jan 25 12:10:10 2021
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 EF2143A186A for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:10:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 bDIkhIkHB9jm for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:10:07 -0800 (PST)
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 9F7883A1868 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:10:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611605406; bh=eZur5Y28fp7wFQSOWnLyMjWPumoyOcS0X1q0PfXohoM=; l=659; h=To:References:From:Date:In-Reply-To; b=AOip8kOvfsuLzGueM5yaDcK6++f0hQnWltJuvqfxn2jRb35eZaRJrbA7psALtCHT/ SdUPPm7toko0CbCxuXGXul5m0rjqF8uPCFzsK3w7TMCTLac0TuzqNIsM/LH6k72uA8 pI31kPFUkfCyb3NxThu1zm51At7Oar1bNNcm09fr6i5Pm0q2BPH4XxnmvW4Lo
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000600F259D.00000FC8; Mon, 25 Jan 2021 21:10:05 +0100
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210124184659.12DF46C068F5@ary.qy> <dd3da825-bb39-6c37-762c-39ce5422f87a@mtcc.com> <afe0e8fd-bbac-9e0d-859c-0fdfcf83978a@tana.it> <b3c5f861-2a17-afa8-5f62-e9f152b58e1f@mtcc.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <14fba490-7b6b-39bc-9a88-7a28aad5c1d5@tana.it>
Date: Mon, 25 Jan 2021 21:10:05 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <b3c5f861-2a17-afa8-5f62-e9f152b58e1f@mtcc.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/1k9063PsZgsSg9KHkVH34ARmhy4>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 25 Jan 2021 20:10:09 -0000

On Mon 25/Jan/2021 21:07:01 +0100 Michael Thomas wrote:
> 
> On 1/25/21 11:53 AM, Alessandro Vesely wrote:
>> On Sun 24/Jan/2021 19:49:34 +0100 Michael Thomas wrote:
>>> issue #99 needs to be addressed.
>>
>> Won't we put a DKIM-Signature: in the http: header?
>>
> I don't know. That would need to be specified. To me it sounds like a good 
> reason to not try to specify http especially if there doesn't seem to be any 
> clear desire for it.


Yes, it needs a spec.  It doesn't seem to be overly difficult.

If we put authentication at SHOULD, the missing spec is a good reason to skip 
signing.  Meanwhile we can try https:.


Best
Ale
-- 



















From nobody Mon Jan 25 12:18:17 2021
Return-Path: <mike@fresheez.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 CF3753A187F for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 CeL_g1wXUmyt for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:18:14 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12BE53A187C for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:18:13 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id z21so9709532pgj.4 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:18:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=PQDHkyso95o66pSbzQIdy9UVxHxQx0iaJzaiJfxX/rA=; b=RMt6NKfrD22MNtqxyVSiwh9lNnIHGuinlrO9YQuzxNkRrQnUH+AVxh3sAXgRZ8FpcZ yq6VyTBU58sFSgEHIXsGoxVHsBnblA/UY0px2hzJGSQb7QwCw4/hEpbpF5srWxYVNlB3 4V41/SRC5frf1QlnpNiAWcyfS5mHlTP9jmYDMTfyRdhSOttUKnYoqcQwo6rrkNRh/+8W J5oqGzyiCizexX+UoVP6OI0xRdXzdwDCHGbmfoYW80bwK7Nymsqk8ZSJ2u9YItLfsBh9 23/rhZKr60QCg6hJLeDrvpyQ95OGUx53utN2aZeypQDa3hccbOP90GwesQ15Z/78fqcE aoTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=PQDHkyso95o66pSbzQIdy9UVxHxQx0iaJzaiJfxX/rA=; b=RmWXlAF00+7Zb/0pS6KACk7NYl9ldinVfJe+F8Nk02EsTV8zEsyXFwGUPGk/BTVkhV Xk/DYE5AqIEoN443SGGngk460BJYyRBQETJffNjfj/LHbGRsjz441L4DDNMxOSoiENle XKmvUVyaIWb0cSk/bemsFP7QKZfEZFKyFbdBdr18fAq5Uars3yiKdqYqObziw+FAmMjQ 2bd3aC9aeYnRcqLh9vZPnTZLDaFErs30GeDjluk4PEhI30JTSdLN4pGrSjOw8v6Tip5s i0uHo6yvKMt3QYLtAbrzbLSrKteojv5shAlQ5dKuUzxwgoneQJ/Ns4FXnSj8txXAKedm xE/g==
X-Gm-Message-State: AOAM533OmwYkoVT0HwIOU426bSlwED1DPtgnqTauUWkNtrGSVTZvy/97 0ZAG3WrF/igPD/eZEJ0NhixbaqRQcgqBWQ==
X-Google-Smtp-Source: ABdhPJzNLL1xyrjL9HuBFDrZ3zLLMv7Ejc7XnWC0dLRG2ftIBgu3JrLSoy1Lso/rW6xre4QMtXj42w==
X-Received: by 2002:a63:4966:: with SMTP id y38mr2182957pgk.428.1611605893158;  Mon, 25 Jan 2021 12:18:13 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id t20sm190012pjs.48.2021.01.25.12.18.12 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 12:18:12 -0800 (PST)
To: dmarc@ietf.org
References: <20210125195231.E0DE16C13E26@ary.qy> <12abca41-4420-37c7-c903-7decc012027a@mtcc.com> <CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com>
Date: Mon, 25 Jan 2021 12:18:11 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------7AC2053B546C2BFEFF16BF39"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WWOoBm6nK3g_Gidg-lEOUq3jylg>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 20:18:16 -0000

This is a multi-part message in MIME format.
--------------7AC2053B546C2BFEFF16BF39
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/25/21 12:08 PM, Todd Herr wrote:
> On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     On 1/25/21 11:52 AM, John Levine wrote:
>     > In article
>     <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com
>     <mailto:CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ%2BNQg@mail.gmail.com>>
>     you write:
>     >> -=-=-=-=-=-
>     >>
>     >> DMARC alignment on the report seems of limited value unless it
>     is aligned
>     >> to the domain being reported. ...
>     > I'm getting the impression that some of us have not looked at
>     any DMARC reports.
>     >
>     > Aggregate reports contain the domain of the reporter, and the domain
>     > of the sender to whom they are sending the report. They do NOT have
>     > the domains to which the messages were sent or where they were
>     > received, which are often different for forwarded or mailing
>     list mail.
>     >
>     > For at least the third time, there is no "domain being
>     reported". When
>     > I get reports from Google or any other multi-tenant mail provider,
>     > they do not say to which of their gazillion hosted domains the mail
>     > was sent. That is not a bug, and it's been like that for a decade.
>     >
>     Sounds like a bug to me and an issue should be opened. Just
>     because it's
>     a 10 year old bug doesn't mean it's not a bug.
>
>
> I disagree.
>
> Authentication results should not differ at a given provider based 
> solely on the destination domain, so there is no reason to report 
> results separately for each destination domain. Further, there's no 
> value to the report generators, especially at large sites like Google, 
> to expend the resources necessary to generate and send X reports when 
> one will do.
>
So you're saying I should be free to spoof any domain I want because 
Google might be inconvenienced?

Mike


--------------7AC2053B546C2BFEFF16BF39
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 12:08 PM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas
          &lt;<a href="mailto:mike@mtcc.com" moz-do-not-send="true">mike@mtcc.com</a>&gt;
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex"><br>
            On 1/25/21 11:52 AM, John Levine wrote:<br>
            &gt; In article &lt;<a
href="mailto:CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ%2BNQg@mail.gmail.com"
              target="_blank" moz-do-not-send="true">CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com</a>&gt;
            you write:<br>
            &gt;&gt; -=-=-=-=-=-<br>
            &gt;&gt;<br>
            &gt;&gt; DMARC alignment on the report seems of limited
            value unless it is aligned<br>
            &gt;&gt; to the domain being reported. ...<br>
            &gt; I'm getting the impression that some of us have not
            looked at any DMARC reports.<br>
            &gt;<br>
            &gt; Aggregate reports contain the domain of the reporter,
            and the domain<br>
            &gt; of the sender to whom they are sending the report. They
            do NOT have<br>
            &gt; the domains to which the messages were sent or where
            they were<br>
            &gt; received, which are often different for forwarded or
            mailing list mail.<br>
            &gt;<br>
            &gt; For at least the third time, there is no "domain being
            reported". When<br>
            &gt; I get reports from Google or any other multi-tenant
            mail provider,<br>
            &gt; they do not say to which of their gazillion hosted
            domains the mail<br>
            &gt; was sent. That is not a bug, and it's been like that
            for a decade.<br>
            &gt;<br>
            Sounds like a bug to me and an issue should be opened. Just
            because it's <br>
            a 10 year old bug doesn't mean it's not a bug.<br>
            <br>
          </blockquote>
          <div><br>
          </div>
          <div>I disagree. </div>
          <div><br>
          </div>
          <div>Authentication results should not differ at a given
            provider based solely on the destination domain, so there is
            no reason to report results separately for each destination
            domain. Further, there's no value to the report generators,
            especially at large sites like Google, to expend the
            resources necessary to generate and send X reports when one
            will do.</div>
        </div>
        <br>
      </div>
    </blockquote>
    <p>So you're saying I should be free to spoof any domain I want
      because Google might be inconvenienced?</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------7AC2053B546C2BFEFF16BF39--


From nobody Mon Jan 25 12:24:20 2021
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 CD6833A1860 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:24:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.201
X-Spam-Level: 
X-Spam-Status: No, score=-0.201 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 SV4u710jqEhp for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:24:14 -0800 (PST)
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 DE4243A0813 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:24:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611606251; bh=87CJZWwfFxQPoMvvuW38hA0thka3dPFFwl+GfEE92DI=; l=891; h=To:References:From:Date:In-Reply-To; b=DYxIRdTPgSLS/QjTk59Il+dHjVkk8az6t21Kxjhi6fi7P9v//RBECyA+a0FNMT26M vgFe3PQjV2wMN5RC5izeGOaGzODfLtAaLyIz8DxkP64F0+An424ErBSXwXF+WppCz9 VZgC6X/VLrBL4fjHtxpqRRGcZO3/Sa2Q0P9LnGfhBLQiabk5eo+dfhqQlQFhN
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000600F28EB.0000111B; Mon, 25 Jan 2021 21:24:11 +0100
To: Todd Herr <todd.herr@valimail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <97c58213-8de9-faf6-997d-25a1d13cca74@tana.it>
Date: Mon, 25 Jan 2021 21:24:10 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@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/Rlx0K-6vDOoFKk39ssnwlOA4AA8>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 20:24:19 -0000

On Mon 25/Jan/2021 14:25:23 +0100 Todd Herr wrote:
> About that, aggregate reports are meant to be machine-parsed, and in my own 
> experience that's accomplished by running a cron job a couple times a day to 
> process the rua mailbox. (Personally, I favored Mark Overmeer's perl stuff; 
> open the mailbox, cycle through each message, strip off the attachment, unzip 
> it, and pass it to the tools that John wrote to read the XML and store the 
> results in a database, but I was working at a relatively small site.)


For a counter example, I read aggregate reports one by one, if at all.  They 
get an automated HTML rendering that makes it easy to see success at a glance, 
and the mail site is small enough that I can afford doing so.  Authentication 
status is visible at a glance too, so I can judge the report's merit.

IMHO, reports SHOULD be authenticated.

Best
Ale
-- 














From nobody Mon Jan 25 12:27:43 2021
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 19ADE3A188D for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 tCcExqC-10n4 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:27:42 -0800 (PST)
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 072DC3A1860 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:27:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611606460; bh=uIiOZ7i9GJCc6YOf4PD/2a3tz4Bk60ztiBGSesZ55Po=; l=382; h=To:References:From:Date:In-Reply-To; b=AgEL05oU4f/rEmyo18/nQdi4WUNP7RM7nAd2wUv58iC3H7t0n4r7tvkRBtt+5DqaJ Fa+X0ssbuh05OP/Z9hlNi0W0rkybZDjzkYkS3V9WqGgV+HXBhcndGf0KegygHLed9R pnN8o78RAUb8y3PrchPTcVmZFTSScE5IvS6zQUK55vb60/nO7kfUoX4EaMXV/
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000600F29BC.00001179; Mon, 25 Jan 2021 21:27:40 +0100
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>, Douglas Foster <dougfoster.emailstandards@gmail.com>, Michael Thomas <mike@mtcc.com>, IETF DMARC WG <dmarc@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com> <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com> <25ea488b-e432-75c4-c57a-01d03308208c@mtcc.com> <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <d39eb5dd-f8b2-e263-026f-39cd8f5dc0fb@tana.it>
Date: Mon, 25 Jan 2021 21:27:38 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@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/nQq_zBukE93oyYTkLgEBF5DTpdg>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 20:27:43 -0000

On Mon 25/Jan/2021 19:02:13 +0100 Seth Blank wrote:
> It is likely in scope to discuss if the current text needs to be moved from 
> 7.2.1.1 to 7.1, but let's please be careful to focus on operational feedback 
> and not personal opinions.


I'd leave the MUST in 7.2.1.1.  If moved to 7.1 it should become a SHOULD.

Indeed, it can become a SHOULD anyway.


Best
Ale
-- 


















From nobody Mon Jan 25 12:39:05 2021
Return-Path: <superuser@gmail.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 D60F43A18A9 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 oL6wmB4kzBWd for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:39:02 -0800 (PST)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B2163A18A7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:39:02 -0800 (PST)
Received: by mail-vs1-xe2b.google.com with SMTP id e15so7908229vsa.0 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:39:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=git2s6zGixau+DiHdQwdZBqLBaPkgkwxvo1TSXcjqBk=; b=STf8MWMrDYUYhyLsZArQPQhNZ7zQdoobcQb+iw8YJVFyN6JCG5SepIJJNcMTLsIpNd 9KFojN10PwLnAb0QknzZC4drlshZSV0WELA1GHMYPnuEZFtMOpijt+XuWpgavEKcBjDq 3t5m+/nDLjzHtY18IlEO5TSCWS5sni009Mq23ZA1NA/dTU+fqp5tJmwIvp/mCXBDNHwU xi+uXmWIr6z3K9TVY0HmEtwJCDoxhdVKk+aVo8uuaDP9NGCqu7bPVWIIPzQS/IfZVBG4 YcUb8Zz/R5HffGwK2z473QTUMZg8Sk9AQJc1LBtyVbE6hbRPXaRwBAhvVBemYovB7W/B D7sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=git2s6zGixau+DiHdQwdZBqLBaPkgkwxvo1TSXcjqBk=; b=VE422D86c/bmfu03nJ7qYlGcXYvNMHtoZ1vQU2veYk7Z5TxOqUl6VGaxrro5NrMENK o4oL5TFtIHWGnQ97Cx8NssjSE69mYXaS0cWw6263HRJmS3vklv4pU6SMdXuIdyp7TwzF INGqqFdmg7YogMAv5KIML0pwWDfZ27LlSFl2O4wv1pA4NWOthprXbYLwNPjBjEr/l7+y Edchn2bKJptOijC4cx00Bpq5f9yT0NUZtMD7jIOx/nbQH7R4JRyhnGrZPHJZcgmeFqyx m9P8SKqi6on9nl9GgQaSDkWsLnhUg3K2ZkT2QMeZfmQLaZqL0tEdemw1dWHEgJgg9qIb oQXA==
X-Gm-Message-State: AOAM530y0kaoeJJeozK/W9XqR4xblxl7e1Jst+4kE5eu2dsKtdrK/cVz 5DL+6B0vockJanZ86AoRqZwY346tzldkPoyH6y0UYIBkYxA=
X-Google-Smtp-Source: ABdhPJw5b/IxnY/WdJUpNPNc/wEozjx0cnuog1iokdQkueHoFVP7xg1YtBYYpM1RlCJKpV5Zyed3tLROllXkz7UkZME=
X-Received: by 2002:a05:6102:808:: with SMTP id g8mr2216948vsb.0.1611607141382;  Mon, 25 Jan 2021 12:39:01 -0800 (PST)
MIME-Version: 1.0
References: <ed9b7f7f-2737-257f-8148-d94a7c1d383@taugh.com>
In-Reply-To: <ed9b7f7f-2737-257f-8148-d94a7c1d383@taugh.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 25 Jan 2021 12:38:50 -0800
Message-ID: <CAL0qLwbax6rkJuVhN50nLP=QV0dBkCM0272ZmFD7qQG1XPrbiA@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002dfdbf05b9bf8701"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3lWtRBFDyheL1fGPxO_n8dwt70g>
Subject: Re: [dmarc-ietf] error report in 7.2.2
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, 25 Jan 2021 20:39:04 -0000

--0000000000002dfdbf05b9bf8701
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 25, 2021 at 12:06 PM John R Levine <johnl@taugh.com> wrote:

> Does anyone send the error reports described in section 7.2.2 ?  I've
> never seen one but my reports are all quite small.
>

I've never seen one.  I imagine the logic goes something like "I was able
to at least submit the report to the submission server, so that's that."

-MSK

--0000000000002dfdbf05b9bf8701
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 25, 2021 at 12:06 PM John R L=
evine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:=
<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">Does anyone send the error reports described in section 7.2.2 ?=
=C2=A0 I&#39;ve <br>
never seen one but my reports are all quite small.<br></blockquote><div><br=
></div><div>I&#39;ve never seen one.=C2=A0 I imagine the logic goes somethi=
ng like &quot;I was able to at least submit the report to the submission se=
rver, so that&#39;s that.&quot;</div><div><br></div><div>-MSK<br></div></di=
v></div>

--0000000000002dfdbf05b9bf8701--


From nobody Mon Jan 25 12:39:11 2021
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 2D9BC3A18E4 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 oWIxTuScME6c for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:39:09 -0800 (PST)
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 DBF183A18E6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:39:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611607146; bh=bJfHW4aIsI0IQJcKUx4hVrXyg5f9XigWc0qq/60Cocc=; l=700; h=To:References:From:Date:In-Reply-To; b=Cgs22kMa2jlAJKY2fagcqLuB1q3rU2X7a0+eJp6GN4qhqAkiGHLnc3SmiG6WKAl/F RKel55y5oBAm3B8+pvyZ8sB0One5mJUPKRvnW+zf1M7wAlrDq9KbdmxpZKlPJjeFec 5f4NAsOYSO/zTE6HL+S7Vqw97/tKCwHcg25sdr9NWYhga2I3XjZ7GzCycjVLA
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000600F2C6A.0000132E; Mon, 25 Jan 2021 21:39:06 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org, dougfoster.emailstandards@gmail.com
References: <20210125195231.E0DE16C13E26@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <62e65ae9-f7d3-af7c-94f1-63bf07bd38cc@tana.it>
Date: Mon, 25 Jan 2021 21:39:05 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210125195231.E0DE16C13E26@ary.qy>
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/GaoToSC0gcbKtjYn2piKk4GOVag>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 20:39:11 -0000

On Mon 25/Jan/2021 20:52:31 +0100 John Levine wrote:
> In article <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com> you write:
>>
>>DMARC alignment on the report seems of limited value unless it is aligned
>>to the domain being reported. ...
> 
> [...]
> 
> For at least the third time, there is no "domain being reported". When
> I get reports from Google or any other multi-tenant mail provider,
> they do not say to which of their gazillion hosted domains the mail
> was sent. That is not a bug, and it's been like that for a decade.


Yet, an unauthenticated report from Google would prick up your ears.

DMARC authentication is a good thing.


Best
Ale
-- 













From nobody Mon Jan 25 12:41:41 2021
Return-Path: <mike@fresheez.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 AF7803A18B1 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:41:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 YXxSvzdGRZjl for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:41:38 -0800 (PST)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB6123A18A7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:41:38 -0800 (PST)
Received: by mail-pj1-x1029.google.com with SMTP id g15so370320pjd.2 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:41:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=BmxhTgnWLsZulRCZ89d0MFUr0Omq3jOCRLmiPbAJSSQ=; b=TK4IsoSsJgWiQSHUj9Jvn0W0iysEMMVQkbK8x6m3a0+46vFpK8FrVc+f/SFJrkbo+d Cmpeo9dEj2d7NSve8zq6j63mtqGl33ntgXEqIBmZz4l1GnJUqjXjNyJdgrUtWevVfZrA XV8aGjDD0OQvfOwO+2mv/pG/9NiIv5JdueO4czkf/6Dq8z9uDXqxdcwuY2SV4esqXhiX g0RiLOafURHcV7MZU7aJAopRGWeh6hXdXNLqZWo5M94GaaXWpTQKVEJuFPJo9yRwJpzr HGcmei7fVG8hJziJfQaVj386ls7pbMWRymVksGMscdYW9VW4AWaTQLNilk0r6rp/K2vN 0rzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=BmxhTgnWLsZulRCZ89d0MFUr0Omq3jOCRLmiPbAJSSQ=; b=TGpSTaPzIXf3/dRt7FjiV4Zx6lzRUhQ3odcRq+G+xfTNhdEFDXddtKNDeFtdy6USHR 9a7eW7EIhejWMBarG3E38Se414bNfi7qDOpDmckXmSGNrSLLt6Y5IB7a7LAebSDblVKO nR4x8qLJHA9hx4BIMQz40iBsNiDyKbYvvxIXfpnAD8DF1fdDhBm/msRxO3WNOmruC57z SprWIELoFfOV8hla/OIysR1k30sqoRNZ0c0p83sOHUr7kNS6ARDXXb8eFgv4D/K8+CNZ sQv1ZFyFT9TfgLNBd+qQq+DIY+8ml6lfHhgW1Uzcp/fKl6ODUoy96rYHJYAledf800b3 Wf9w==
X-Gm-Message-State: AOAM531+oZS23T2bUM1yajJgALNs8/LomNU90YxDSo9ANrJe0z3+tNXc ZZihdB9CL3JWLQSlyIrss0IAAYCXJzosog==
X-Google-Smtp-Source: ABdhPJxj/AXRTVuRXC9jaEIjLS1b8YbxSDx6S+WfvNnxeSi1StXqFcN9mP+bTL0SCcSrAHhsSY2W5A==
X-Received: by 2002:a17:902:bcc7:b029:de:3c03:f45f with SMTP id o7-20020a170902bcc7b02900de3c03f45fmr2290145pls.32.1611607297845;  Mon, 25 Jan 2021 12:41:37 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id s187sm17309016pfb.161.2021.01.25.12.41.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 12:41:37 -0800 (PST)
To: Seth Blank <seth@valimail.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com> <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com> <25ea488b-e432-75c4-c57a-01d03308208c@mtcc.com> <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <2f73843f-eaec-5bb7-c59c-08ff387418e3@mtcc.com>
Date: Mon, 25 Jan 2021 12:41:35 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Xz2FeBfU8ALzoOVGe01D0yuwbK0>
Subject: [dmarc-ietf] reporting security requirements
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, 25 Jan 2021 20:41:40 -0000

On 1/25/21 10:02 AM, Seth Blank wrote:
> Michael, are you aware of anyone not following the guidance in the 
> document? This thread feels like we're discussing a non-issue. 
> Aggregate reports are already required to be authenticated and I'm 
> unaware of anyone sending failure reports, let along unauthenticated 
> ones. Is the language causing problems? Such problems have not been 
> brought to the list, and would be a good place to start if you want to 
> build consensus.

 From the looks of it, it doesn't seem like the security requirements of 
reporting was ever undertaken. There seems to be a wide range of 
disagreement even if there was given the thread from which this came. 
 From there is actually text, to don't know if it's an issue, to there 
hasn't been a problem before (as if that were some sort of barometer), 
to authentication might inconvenience google, to contradicting your 
assertion that authentication in the way you mentioned can be done. 
Since this is going to proposed standard from informational, that is not 
a very good state of affairs, IMO.

Mike



From nobody Mon Jan 25 12:44:30 2021
Return-Path: <johnl@iecc.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 1BF953A18A7 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=QXXC9E6B; dkim=pass (2048-bit key) header.d=taugh.com header.b=xoPWaudG
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 OmCAI2tc-Sy6 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:44:26 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 7524A3A189B for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:44:26 -0800 (PST)
Received: (qmail 8322 invoked from network); 25 Jan 2021 20:44:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2080.600f2da8.k2101; bh=Os+vkJmFwu5Eg7q0XPHOdEw46LLgBKWpQafjv7/pbVo=; b=QXXC9E6BngK2fwU0QPvt1ydLRQlUTxN8y7hEQ48CjkAG0mdBpXONWRYF+ww4wP5SitczXQRgJ3XRHK4jnXb/k6aKdllX2ggSWxoXoPvabcqs10cnCp/0vtxiB/bjnuDb8LjaMNI05Z9z2dvByS12b85I9wWLKb4xfT3wa2VkVuMC4rqd9umytUK98ScdZy6TyhtJgipfwBsXMfcpPIoWSCGsdEamtO9mVshW13aOMZUpPrazpfpOCdKdgwcpCeGDzZtuKwWBiakXbjAlkxPTTWhmu5EjPSKCYwwlzO19UIRjkmbHgimL+cw5kaaKruwbej7ACw+VQT4xPkeygj4Aww==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2080.600f2da8.k2101; bh=Os+vkJmFwu5Eg7q0XPHOdEw46LLgBKWpQafjv7/pbVo=; b=xoPWaudGU7OpA2UUkcZ0TWDlq8jgzTarF46+RE/5AHyTVJ+tAUr4J145sepnynmlnfmKrygu/jGTzl2YwtCyto/BNyXg5oJywsNNLbUCfHtQZn8GV1nYqnewxGmpiVEEtWrjRi064NrHbPEhoueSSqUCwQ9cMY2wMFA807gyW7RBc5E+An6iN6eO+YrFLlGXFssr3sMevxJbwNcgMaTfals3CpTtJ/7ZkblffdMe1aFXM/ND56J+J1ivjZqyrWMifYw0L/aIFC79w9s0AHy5rLL+vITqEv816pUQ2/NJPQoBT7eGO71F37sCpoWD72VSc2UQHr2q0NMUGvU8TTjU8Q==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 20:44:24 -0000
Received: by ary.qy (Postfix, from userid 501) id 9FE546C14371; Mon, 25 Jan 2021 15:44:22 -0500 (EST)
Date: 25 Jan 2021 15:44:22 -0500
Message-Id: <20210125204423.9FE546C14371@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <afe0e8fd-bbac-9e0d-859c-0fdfcf83978a@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/U1OjMDB5fB24OO7k65MzQoJIO2o>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 25 Jan 2021 20:44:29 -0000

In article <afe0e8fd-bbac-9e0d-859c-0fdfcf83978a@tana.it> you write:
>On Sun 24/Jan/2021 19:49:34 +0100 Michael Thomas wrote:
>> issue #99 needs to be addressed.
>
>Won't we put a DKIM-Signature: in the http: header?

No, there's no spec for signing an http transaction.

If you want a client domain identity, It's easy enough to permit a
client SSL certificate, but as I have pointed out a few times, since
there are no recipient domains in an aggregate report, they don't
provide anything useful to link to.

R's,
John


From nobody Mon Jan 25 12:45:33 2021
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 888503A18B7 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:45:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 f63r86r8kV7g for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:45:31 -0800 (PST)
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 515233A18B5 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:45:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611607528; bh=FxykgYOBpfSp+7MBEJXwwhrLjjwVtX0HnYnAL61W7io=; l=568; h=To:Cc:References:From:Date:In-Reply-To; b=AJpDQ3HXLPCpMb8ta4LcVsL5R2uh9sajzNn7VhLUVqlabT7NFVP059/BHU/3Dz1UI jFMMEeeHFNO4ZHZhYgCX6+iv7c9d7uUOVVpVqUJfreXQ86OAAzXcMUJexV7iziebmC K0l1yNoBi54G05KktkVCEg/lxu1Ngfi7U9FyhVFHJ1tiT+MkvT575vM5rhfej
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Original-Cc: IETF DMARC WG <dmarc@ietf.org>
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 00000000005DC09F.00000000600F2DE8.0000142A; Mon, 25 Jan 2021 21:45:28 +0100
To: "Murray S. Kucherawy" <superuser@gmail.com>, John R Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <ed9b7f7f-2737-257f-8148-d94a7c1d383@taugh.com> <CAL0qLwbax6rkJuVhN50nLP=QV0dBkCM0272ZmFD7qQG1XPrbiA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <2c814e81-9094-c0d1-7244-847a978a340a@tana.it>
Date: Mon, 25 Jan 2021 21:45:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbax6rkJuVhN50nLP=QV0dBkCM0272ZmFD7qQG1XPrbiA@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/qI_JWzcVtTKONahG7dpvIqsJQxo>
Subject: Re: [dmarc-ietf] error report in 7.2.2
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, 25 Jan 2021 20:45:33 -0000

On Mon 25/Jan/2021 21:38:50 +0100 Murray S. Kucherawy wrote:
> On Mon, Jan 25, 2021 at 12:06 PM John R Levine <johnl@taugh.com> wrote:
> 
>> Does anyone send the error reports described in section 7.2.2 ?  I've
>> never seen one but my reports are all quite small.
> 
> I've never seen one.  I imagine the logic goes something like "I was able
> to at least submit the report to the submission server, so that's that."


"An attempt MUST be made to send this report to all listed "mailto" URIs", 
seems to also include the one which bounced.


Best
Ale
-- 












From nobody Mon Jan 25 12:47:47 2021
Return-Path: <seth@valimail.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 40A543A1946 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 CzB4-LkHvf1V for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:47:39 -0800 (PST)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BCBB3A1928 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:47:36 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id m13so2775967vsr.2 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:47:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9waooDmEJjmG+/vkiTjP5TdQrOLsqL6ceJ0wEBh1Xc8=; b=gSY9l6fdCad0A01kAgfRTQ0fZD/f4ZTFzDi4DA5Oo/DoLBjFcTvgOzpUD3zR+XAH6v z3yoTbyRwVksqR7lzU2es82+3NUospKoIB9IftPR5MUCwzzOGNwUvItXrH5epVsMvWDM nrKWGYeNd1eGz9ylf3HyDtw7wa1uDF9nHc2pGHu/7OYKZM3ODvWGcdrPcgJgZ3s1AQWM CuKsr/DV+b1/GgDlwijc8DFo6xLF6HsgRN/Z2QfoQL3PMxC4ff/WT1EZ6Q7t8WUXk2uV lgN1OnT7bCLTUwewzGtOi48e3CBsr0Oq8vMHc1qPwSIje0i2qLhRZAVVtgYaiIArkRv8 vmsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9waooDmEJjmG+/vkiTjP5TdQrOLsqL6ceJ0wEBh1Xc8=; b=MQrR/y/IopL6B5fW6ObQdwXb1HOojMF1vm/CsnzG4bt6Pkxqft2jsNLxX9S4bQRR5J 0QT8RL+TO1YWLBm6YNrDLNjLp74ZQvgQRM1fWX43ppZ8oujpX54DQcSb1IGE/kkx0sgM /V3uaKRFV7dJlaBG1vULYVsEnAHdxsHopMdt47U6D42eYPX69pypybxlCKULADSu3O6r PoVKoeHMGTC+SBrxC+S3UsPPhBC1eK7dVNa58TTDUVlF7YsMW61SbsH9S7OB1J7iLp0P t4C+5EV2S8KjkjmZsYcb8OeotDhxuGXeobgeapd+/3vWwA5KT+r0qnkDuXFZrpP5TMSy +0AQ==
X-Gm-Message-State: AOAM533J5rKtVvih2dbMQ+J3FetoGZ/IqV4w3mfje1rQzharyv85wx1B /aw/xbDfFYU1V4iWgDvM6RurhlPboneYzpluxVAXL3DerlM=
X-Google-Smtp-Source: ABdhPJzCUNWrSA7eey2ricSTFEYwf4Inqg+JJmfmTVdnikUlLoTUgbLfSOswfmt44s377K8nmecxlRduKrEykGB2Kc8=
X-Received: by 2002:a05:6102:1c8:: with SMTP id s8mr2201694vsq.52.1611607655239;  Mon, 25 Jan 2021 12:47:35 -0800 (PST)
MIME-Version: 1.0
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <9c84fa50-d23c-a794-fc62-09788ac383a9@mtcc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com> <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com> <25ea488b-e432-75c4-c57a-01d03308208c@mtcc.com> <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com> <2f73843f-eaec-5bb7-c59c-08ff387418e3@mtcc.com>
In-Reply-To: <2f73843f-eaec-5bb7-c59c-08ff387418e3@mtcc.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 25 Jan 2021 12:47:24 -0800
Message-ID: <CAOZAAfMBwuXEyxnCgObChb_irCME9w=5ZjedjdSz=0qzFj6uVw@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,  "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ceeeff05b9bfa588"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/0dIL68EWtHstv76HaUvQelkc2gk>
Subject: Re: [dmarc-ietf] reporting security requirements
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, 25 Jan 2021 20:47:47 -0000

--000000000000ceeeff05b9bfa588
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Entire sections of the document are devoted to preventing reporting abuse.
Of course reviewing the security recommendations are part of the process of
going standards track which we=E2=80=99ll be undertaking.

If there are seeing specific operational issues that you believe require
clarification in the document, please speak up.

Back to open tickets, please.

On Mon, Jan 25, 2021 at 12:41 Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/25/21 10:02 AM, Seth Blank wrote:
> > Michael, are you aware of anyone not following the guidance in the
> > document? This thread feels like we're discussing a non-issue.
> > Aggregate reports are already required to be authenticated and I'm
> > unaware of anyone sending failure reports, let along unauthenticated
> > ones. Is the language causing problems? Such problems have not been
> > brought to the list, and would be a good place to start if you want to
> > build consensus.
>
>  From the looks of it, it doesn't seem like the security requirements of
> reporting was ever undertaken. There seems to be a wide range of
> disagreement even if there was given the thread from which this came.
>  From there is actually text, to don't know if it's an issue, to there
> hasn't been a problem before (as if that were some sort of barometer),
> to authentication might inconvenience google, to contradicting your
> assertion that authentication in the way you mentioned can be done.
> Since this is going to proposed standard from informational, that is not
> a very good state of affairs, IMO.
>
> Mike
>
>
> --

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000ceeeff05b9bfa588
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Entire sections of the document are devoted to preventing=
 reporting abuse. Of course reviewing the security recommendations are part=
 of the process of going standards track which we=E2=80=99ll be undertaking=
.</div><div dir=3D"auto"><br></div><div dir=3D"auto">If there are seeing sp=
ecific operational issues that you believe require clarification in the doc=
ument, please speak up.</div><div dir=3D"auto"><br></div><div dir=3D"auto">=
Back to open tickets, please.</div><div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 12:41 Michael Tho=
mas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><br>
On 1/25/21 10:02 AM, Seth Blank wrote:<br>
&gt; Michael, are you aware of anyone not following the guidance in the <br=
>
&gt; document? This thread feels like we&#39;re discussing a non-issue. <br=
>
&gt; Aggregate reports are already required to be authenticated and I&#39;m=
 <br>
&gt; unaware of anyone sending failure reports, let along unauthenticated <=
br>
&gt; ones. Is the language causing problems? Such problems have not been <b=
r>
&gt; brought to the list, and would be a good place to start if you want to=
 <br>
&gt; build consensus.<br>
<br>
=C2=A0From the looks of it, it doesn&#39;t seem like the security requireme=
nts of <br>
reporting was ever undertaken. There seems to be a wide range of <br>
disagreement even if there was given the thread from which this came. <br>
=C2=A0From there is actually text, to don&#39;t know if it&#39;s an issue, =
to there <br>
hasn&#39;t been a problem before (as if that were some sort of barometer), =
<br>
to authentication might inconvenience google, to contradicting your <br>
assertion that authentication in the way you mentioned can be done. <br>
Since this is going to proposed standard from informational, that is not <b=
r>
a very good state of affairs, IMO.<br>
<br>
Mike<br>
<br>
<br>
</blockquote></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-heigh=
t:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left=
"><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:sma=
ll;font-family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align=
:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, St=
andards and New Technologies</span></div><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"=
text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><s=
pan style=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com"=
 target=3D"_blank">seth@valimail.com</a></span></div></span><span><div><spa=
n><b>p:</b></span><span> 415.273.8818 </span><span></span></div></span><p d=
ir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-se=
rif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;marg=
in-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Ari=
al;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;wh=
ite-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRj=
fmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc=
_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border:none;=
height:40px;width:177px"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34=
,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-colo=
r:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br><=
/p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial"=
><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and al=
l data transmitted with it contains confidential and/or proprietary informa=
tion intended solely for the use of individual(s) authorized to receive it.=
 If you are not an intended and authorized recipient you are hereby notifie=
d of any use, disclosure, copying or distribution of the information includ=
ed in this transmission is prohibited and may be unlawful. Please immediate=
ly notify the sender by replying to this email and then delete it from your=
 system.</span></font></p></span></div>

--000000000000ceeeff05b9bfa588--


From nobody Mon Jan 25 12:48:07 2021
Return-Path: <johnl@taugh.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 8988B3A1947 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:48:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=fGaS99SG; dkim=pass (2048-bit key) header.d=taugh.com header.b=KksmG+oc
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 s-lr1DSCTdAI for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:48:01 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D73853A192E for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:47:54 -0800 (PST)
Received: (qmail 9243 invoked from network); 25 Jan 2021 20:47:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=2417.600f2e79.k2101; bh=HDhKez3LFw9kvca/eAHB9u29zcv5vbcUCnkjRYaD9Qo=; b=fGaS99SG9AldJULk3DY/agI7W0x0B2CtlOQosxgZqlM3pC+UO4BSjRGJe+6SfmGaTdugOMi6RIfW199GQ6EIlYXJaU4fJpIFqJen0ZNoYxhEXy20Cc3t/Qxoe5EfJJFNzjaAkQrE0an7IuuXNvqozysUihK3mMQyHr/pI4x1K6o7kON2Ru+45Jw1l5agkc9LlQUoXHOKOXnC8uJ1yagFUVHJdAWy44M52xQzNoqksCo8mlfZyysxbJ4ChLSCLU9i4tJW1K+WH4quaTiPi4o7RsxObhXOAavxdDv+yDsrnUMfvQkQ5/bPL7fZIT/s39B1Gw0Oy4Bb9Jzw7f49BLTu8A==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=2417.600f2e79.k2101; bh=HDhKez3LFw9kvca/eAHB9u29zcv5vbcUCnkjRYaD9Qo=; b=KksmG+ocdVWWbRgdjbiqQxDp/wA+x4E+4M6rhXorDT0Rq5TeBDbetWvxzeCMOlBT/B8TAprI+aalV1bA78SFk579wsXxAvjUp+NXAZuKutNCbi/tOfEU9lRgYrBn3c7VIdwQGht01M+fLwEigwlyDuBCm/YNhvyB1r20q0KRp5zzE8YmtxvGMZMlC6SkvBZkLOrGg8KJfk247AZN7EfoSrcWCyhVtCzr2HPp9eJbvaPizoW+vOi3b791imm501ieM1zEDxpzlKh96IAupMmmVf6aBLmdYw9ecwVAud5WqnYT//mhIXGdojgdjmLSJzDYZb7WUdzt8wXNiJwXg027hA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 20:47:53 -0000
Received: by ary.qy (Postfix, from userid 501) id A17426C143BC; Mon, 25 Jan 2021 15:47:52 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 10B7A6C1439E; Mon, 25 Jan 2021 15:47:52 -0500 (EST)
Date: 25 Jan 2021 15:47:52 -0500
Message-ID: <b2ab99a1-7174-e027-903b-c112e2d77f73@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <62e65ae9-f7d3-af7c-94f1-63bf07bd38cc@tana.it>
References: <20210125195231.E0DE16C13E26@ary.qy> <62e65ae9-f7d3-af7c-94f1-63bf07bd38cc@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mOcYW39Z_RXh3xmUTAtctBOGQaw>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 20:48:06 -0000

On Mon, 25 Jan 2021, Alessandro Vesely wrote:
>> For at least the third time, there is no "domain being reported". When
>> I get reports from Google or any other multi-tenant mail provider,
>> they do not say to which of their gazillion hosted domains the mail
>> was sent. That is not a bug, and it's been like that for a decade.
>
> Yet, an unauthenticated report from Google would prick up your ears.

How about an authenticated report from google-reports.com ?

R's,
John

PS: this is getting awfully repetitive


From nobody Mon Jan 25 12:50:56 2021
Return-Path: <johnl@taugh.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 353353A183B for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:50:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=HZ7N5DEn; dkim=pass (2048-bit key) header.d=taugh.com header.b=28L8daVH
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 J18XgUMlqLfZ for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:50:53 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 91D9F3A189A for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:50:53 -0800 (PST)
Received: (qmail 10667 invoked from network); 25 Jan 2021 20:50:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=29a3.600f2f2c.k2101; bh=URFtBpy4C/V7cf697/a+OK7ULhCR1iBAjuq8KzYcd7M=; b=HZ7N5DEnGpO2uP3OF3O52q69CNqaLO9vD1KajuKMOG/4KUtaTJyAgT/S3C7S4EKOuv7pGnih1rl+97y/MyCqk8VV+xXdWMA9vz+W6E58n/hS0D9KvJHDBZNRbvEomIkZDG5lEpCd1ilBZZFckLzeZpcPiQ2IdlWAD70WdXV3QJJ0KSqE/+itxaUo03Ax4QFj6QFL5bF0siU2Y2JvW+vKeKh1HB85+RIEPY25D9yXVM2E1hfGkCJapCI+VVoB2dyqD8xBnWrNTaQX4kOPRcFikEziE95DI6DnizJ79eBF89axrJiSP/mknqiVQQmy/ah9C4eG3hWrUw8i8eQwic9d2A==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=29a3.600f2f2c.k2101; bh=URFtBpy4C/V7cf697/a+OK7ULhCR1iBAjuq8KzYcd7M=; b=28L8daVHJ+/Mrcsk51+tUwbIj8fh0E69+etg7D5f9air8G5GtrAciYJ9Or4C39TQra+QNfPXvSUpmB8rER8iLslap7RXzNRViueg33z+E3dIkvuIKQISvmX/EvhymNQ7XZj1iMAPMpbky5FLu0Du4MhqZDFb8JLFh8BHKLlg4vkhjhQ7ZjOrpoAbLkywZMI1jRdk2pkABZvh/9xplVfsClShwirS28ma/95uFy1A3rXrJ6CPIYmeVhF1CRQw9icBikRgfXWi2HxlmllV6Q7NV7M/bSbkKdEiRTJG6TVKn2mufDGEBkBdjIS3mxx8SldFuNxO66LcJxY8RgDCzkHogQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 20:50:52 -0000
Received: by ary.qy (Postfix, from userid 501) id B43B46C143FF; Mon, 25 Jan 2021 15:50:51 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 23E956C143E1; Mon, 25 Jan 2021 15:50:51 -0500 (EST)
Date: 25 Jan 2021 15:50:51 -0500
Message-ID: <54b1c5c9-34c4-7c90-952e-3b2ed0aca2b0@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "IETF DMARC WG" <dmarc@ietf.org>
In-Reply-To: <2c814e81-9094-c0d1-7244-847a978a340a@tana.it>
References: <ed9b7f7f-2737-257f-8148-d94a7c1d383@taugh.com> <CAL0qLwbax6rkJuVhN50nLP=QV0dBkCM0272ZmFD7qQG1XPrbiA@mail.gmail.com> <2c814e81-9094-c0d1-7244-847a978a340a@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/0s9yKSkEG1YQ0kYgVbDn_gQOr4A>
Subject: Re: [dmarc-ietf] error report in 7.2.2
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, 25 Jan 2021 20:50:55 -0000

On Mon, 25 Jan 2021, Alessandro Vesely wrote:
>>> Does anyone send the error reports described in section 7.2.2 ?  I've
>>> never seen one but my reports are all quite small.
>> 
>> I've never seen one.  I imagine the logic goes something like "I was able
>> to at least submit the report to the submission server, so that's that."
>
> "An attempt MUST be made to send this report to all listed "mailto" URIs", 
> seems to also include the one which bounced.

If you look at the last para in 7.2.1, the intention is also to tell 
recipients that you have a report but it is too big.  That's more what I 
was wondering about.

If nobody else has seen error reports, perhaps we could deprecate them.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Mon Jan 25 13:05:13 2021
Return-Path: <todd.herr@valimail.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 BA0FC3A18E8 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 DyknzZtqxgVH for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:05:08 -0800 (PST)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63EBC3A196C for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:04:50 -0800 (PST)
Received: by mail-qv1-xf2d.google.com with SMTP id h21so6879432qvb.8 for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:04:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=1XhCfLF6C0q2CciXPc4HWRaQEUUT/DMQkMxgseywUDA=; b=ABoo2lApYEzSJeQOXSgqKvGZgy9gITT9w5Gzs2qJgRKcxXhLTgIr/gi/ijBNopcM0L RKfALM9n8sos9N62XSu30FKucQubz/msnavv9S8Q8I1nWppu82Lx55h2+Bhg1tlcrYsN LVsuppxggtyZaYPq6e9x3u7lCgooUCRGSYIhF8FgQJuX7IjJh4+lyRChu6U7slM11pn0 Msh1pNEsi+mcTwJclqpwC1S0VBd2dvcNn/4fHk1StB2tFEXob2GczelETO+4x0s/U23E e250grWESvhA6h9qTrfsRp9pNWyjPw7s1k1OtTim5O4iE4gnREkhUr77VaPucNDosQnC YRmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=1XhCfLF6C0q2CciXPc4HWRaQEUUT/DMQkMxgseywUDA=; b=PHsfguczAOwO8W6YM6dbW6y2zv9LzwpygzUm/mp21924rf6zlOFAT2CJ0OfTKHnmLg 0ABnR7wEYNxobvVTAOG9T2l8h1FXUJc1fsQ8SXW6J5IrpR7bp7hsHAKyLtYigQTjBMQO 74XXDm51fQcT1xVRptifIVxg3S+f8/eOUKTGp7wx454Sn6nu9Yj8cho/bnSLglt5pv2W AScAXmIBKhW+0o3+llR5taUDDelp9c1HtUpjfBdBLCuPqM1Cm8iicrr3UQqJSBnhQ/3J IYIheGv9YAJ6KWqTUnr9m4DSCLwi8K9Es/LeUztL74ieWFd28LtOOIVf+28NiKnlOGnh OmRA==
X-Gm-Message-State: AOAM530+7sc4iCcBHY0VIKM884w4nlM2qViGfj5hAkT6+7XaoS2d1OwP +XorA1ejYPrudjEGWmyY1kfq3ccwxAzWzGwiIIZHn6yVx6I/Hg==
X-Google-Smtp-Source: ABdhPJw4w5xOnhvsz8hp9VYIVKAa/oLICGKP3WCSZAzRflSe9/0D+WUs1f993ND+/4w8Fo2HXf8aRuvQCBROP7+iOmY=
X-Received: by 2002:a0c:fe0b:: with SMTP id x11mr2694648qvr.18.1611608689022;  Mon, 25 Jan 2021 13:04:49 -0800 (PST)
MIME-Version: 1.0
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <45b3df7-5c6-9744-2ca8-1542e1b33e7b@taugh.com> <478c7b56-f2b4-c7c1-7722-27fdce4bb8e9@tana.it> <CAHej_8=UTfpVBZJnP6anWshO+6ytU7jb4nybru2gmkFDHZwH5w@mail.gmail.com> <ebf4303b-88e0-4caa-267c-30c2c7516f24@tana.it>
In-Reply-To: <ebf4303b-88e0-4caa-267c-30c2c7516f24@tana.it>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 25 Jan 2021 16:04:33 -0500
Message-ID: <CAHej_8nTCxAOZeT-3snPZ0c+pht=kLAX=J-cccUVHaY4c+cHCQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006d2e9705b9bfe312"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/KEgXmhBimyn4sb_WYbDJtiR8hwY>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 25 Jan 2021 21:05:11 -0000

--0000000000006d2e9705b9bfe312
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 21, 2021 at 4:24 AM Alessandro Vesely <vesely@tana.it> wrote

>
> I agree that the spec needs some text somewhere to counter the passage in
> Section 2.3 of RFC 7208.  This, methinks, is the intended semantics of the
> second paragraph of section 3.1.2 of dmarcbis:
>
> OLD:
>     Note that the RFC5321.HELO identity is not typically used in the
>     context of DMARC (except when required to "fake" an otherwise null
>     reverse-path), even though a "pure SPF" implementation according to
>     [RFC7208] would check that identifier.
>
> I'd rather replace that paragraph and leave item 4 of Section 6.6.2 as
> is.  For
> a possibly less confusing wording:
>
> NEW:
>
>     Even tough a "pure SPF" implementation, according to [RFC7208], would
>     avoid to check the RFC5321.MailFrom identity if the RFC5321.HELO was
>     conclusively determined to pass, DMARC authentication requires the
>     authenticated identity to be aligned.
>
>
May I propose that the section labeled "SPF-Authenticated Identifiers" be
rewritten as follows:

CURRENT:

   DMARC permits Identifier Alignment, based on the result of an SPF
   authentication, to be strict or relaxed.

   In relaxed mode, the [SPF
<https://tools.ietf.org/html/rfc7489#ref-SPF>]-authenticated domain
and RFC5322 <https://tools.ietf.org/html/rfc5322>.From
   domain must have the same Organizational Domain.  In strict mode,
   only an exact DNS domain match is considered to produce Identifier
   Alignment.

   Note that the RFC5321 <https://tools.ietf.org/html/rfc5321>.HELO
identity is not typically used in the
   context of DMARC (except when required to "fake" an otherwise null
   reverse-path), even though a "pure SPF" implementation according to
   [SPF <https://tools.ietf.org/html/rfc7489#ref-SPF>] would check
that identifier.

   For example, if a message passes an SPF check with an
   RFC5321 <https://tools.ietf.org/html/rfc5321>.MailFrom domain of
"cbg.bounces.example.com", and the address
   portion of the RFC5322 <https://tools.ietf.org/html/rfc5322>.From
field contains "payments@example.com",
   the Authenticated RFC5321
<https://tools.ietf.org/html/rfc5321>.MailFrom domain identifier and
the
   RFC5322 <https://tools.ietf.org/html/rfc5322>.From domain are
considered to be "in alignment" in relaxed

   mode, but not in strict mode.



NEW:

DMARC permits Identifier Alignment, based on the result of an SPF

authentication, to be strict or relaxed.


In relaxed mode, the [@!RFC3986]-authenticated domain and RFC5322.From

domain must have the same Organizational Domain.  In strict mode,

only an exact DNS domain match is considered to produce Identifier

Alignment.


For example, if a message passes an SPF check with an

RFC5321.MailFrom domain of "cbg.bounces.example.com", and the address

portion of the RFC5322.From field contains "payments@example.com",

the Authenticated RFC5321.MailFrom domain identifier and the

RFC5322.From domain are considered to be "in alignment" in relaxed

mode, but not in strict mode. In order for the two identifiers to

be considered "in alignment" in strict mode, the domain parts would

have to be identical.


The reader should note that SPF alignment checks in DMARC rely solely

on the RFC5321.MailFrom domain. This differs from section 2.3 of
[@!RFC7208],

which recommends that SPF checks be done on not only the "MAIL FROM"

but also on a separate check of the "HELO" identity.



-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000006d2e9705b9bfe312
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 21, 2021 at 4:24 AM Alessandr=
o Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I agree that the spec needs some text somewhere to counter the passage in <=
br>
Section 2.3 of RFC 7208.=C2=A0 This, methinks, is the intended semantics of=
 the <br>
second paragraph of section 3.1.2 of dmarcbis:<br>
<br>
OLD:<br>
=C2=A0 =C2=A0 Note that the RFC5321.HELO identity is not typically used in =
the<br>
=C2=A0 =C2=A0 context of DMARC (except when required to &quot;fake&quot; an=
 otherwise null<br>
=C2=A0 =C2=A0 reverse-path), even though a &quot;pure SPF&quot; implementat=
ion according to<br>
=C2=A0 =C2=A0 [RFC7208] would check that identifier.<br>
<br>
I&#39;d rather replace that paragraph and leave item 4 of Section 6.6.2 as =
is.=C2=A0 For <br>
a possibly less confusing wording:<br>
<br>
NEW:<br>
<br>
=C2=A0 =C2=A0 Even tough a &quot;pure SPF&quot; implementation, according t=
o [RFC7208], would<br>
=C2=A0 =C2=A0 avoid to check the RFC5321.MailFrom identity if the RFC5321.H=
ELO was<br>
=C2=A0 =C2=A0 conclusively determined to pass, DMARC authentication require=
s the<br>
=C2=A0 =C2=A0 authenticated identity to be aligned.<br><br></blockquote><di=
v><br></div><div>May I propose that the section labeled &quot;SPF-Authentic=
ated Identifiers&quot; be rewritten as follows:</div><div><br></div><div>CU=
RRENT:</div><div><br></div><pre class=3D"gmail-newpage" style=3D"margin-top=
:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><span style=3D"f=
ont-size:13.3333px">   </span>DMARC permits Identifier Alignment, based on =
the result of an SPF
   authentication, to be strict or relaxed.

   In relaxed mode, the [<a href=3D"https://tools.ietf.org/html/rfc7489#ref=
-SPF" title=3D"&quot;Sender Policy Framework (SPF) for Authorizing Use of D=
omains in Email, Version 1&quot;" style=3D"">SPF</a>]-authenticated domain =
and <a href=3D"https://tools.ietf.org/html/rfc5322" style=3D"">RFC5322</a>.=
From
   domain must have the same Organizational Domain.  In strict mode,
   only an exact DNS domain match is considered to produce Identifier
   Alignment.

   Note that the <a href=3D"https://tools.ietf.org/html/rfc5321" style=3D""=
>RFC5321</a>.HELO identity is not typically used in the
   context of DMARC (except when required to &quot;fake&quot; an otherwise =
null
   reverse-path), even though a &quot;pure SPF&quot; implementation accordi=
ng to
   [<a href=3D"https://tools.ietf.org/html/rfc7489#ref-SPF" title=3D"&quot;=
Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Vers=
ion 1&quot;" style=3D"">SPF</a>] would check that identifier.
</pre><pre class=3D"gmail-newpage" style=3D"margin-top:0px;margin-bottom:0p=
x;break-before:page;color:rgb(0,0,0)">   For example, if a message passes a=
n SPF check with an
   <a href=3D"https://tools.ietf.org/html/rfc5321">RFC5321</a>.MailFrom dom=
ain of &quot;<a href=3D"http://cbg.bounces.example.com">cbg.bounces.example=
.com</a>&quot;, and the address
   portion of the <a href=3D"https://tools.ietf.org/html/rfc5322">RFC5322</=
a>.From field contains &quot;<a href=3D"mailto:payments@example.com">paymen=
ts@example.com</a>&quot;,
   the Authenticated <a href=3D"https://tools.ietf.org/html/rfc5321">RFC532=
1</a>.MailFrom domain identifier and the
   <a href=3D"https://tools.ietf.org/html/rfc5322">RFC5322</a>.From domain =
are considered to be &quot;in alignment&quot; in relaxed=C2=A0=C2=A0 =C2=A0=
</pre><pre class=3D"gmail-newpage" style=3D"margin-top:0px;margin-bottom:0p=
x;break-before:page;color:rgb(0,0,0)">   mode, but not in strict mode.</pre=
><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;m=
argin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=
=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-botto=
m:0px;break-before:page;color:rgb(0,0,0)"><br></pre><div>NEW:</div><div><br=
></div></div><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px=
"><div class=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px=
;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:no=
rmal;line-height:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D=
"font-variant-ligatures:no-common-ligatures"><font face=3D"monospace" style=
=3D"">DMARC permits Identifier Alignment, based on the result of an SPF</fo=
nt></span></p></div></div><div class=3D"gmail_quote"><div><p class=3D"gmail=
-p1" style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asia=
n:normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span cla=
ss=3D"gmail-s1" style=3D"font-variant-ligatures:no-common-ligatures"><font =
face=3D"monospace">authentication, to be strict or relaxed.</font></span></=
p></div></div><div class=3D"gmail_quote"><div><p class=3D"gmail-p2" style=
=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;f=
ont-stretch:normal;line-height:normal;color:rgb(0,0,0);min-height:13px"><fo=
nt face=3D"monospace"><br></font></p></div></div><div class=3D"gmail_quote"=
><div><p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal=
;font-variant-east-asian:normal;font-stretch:normal;line-height:normal;colo=
r:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-ligatures:no-c=
ommon-ligatures"><font face=3D"monospace">In relaxed mode, the [@!RFC3986]-=
authenticated domain and RFC5322.From</font></span></p></div></div><div cla=
ss=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-vari=
ant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-=
height:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-vari=
ant-ligatures:no-common-ligatures"><font face=3D"monospace">domain must hav=
e the same Organizational Domain.<span class=3D"gmail-Apple-converted-space=
">=C2=A0 </span>In strict mode,</font></span></p></div></div><div class=3D"=
gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height=
:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-li=
gatures:no-common-ligatures"><font face=3D"monospace">only an exact DNS dom=
ain match is considered to produce Identifier</font></span></p></div></div>=
<div class=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;f=
ont-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:norm=
al;line-height:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"f=
ont-variant-ligatures:no-common-ligatures"><font face=3D"monospace">Alignme=
nt.</font></span></p></div></div><div class=3D"gmail_quote"><div><p class=
=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-variant-=
east-asian:normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0);m=
in-height:13px"><font face=3D"monospace"><br></font></p></div></div><div cl=
ass=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-var=
iant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line=
-height:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-var=
iant-ligatures:no-common-ligatures"><font face=3D"monospace">For example, i=
f a message passes an SPF check with an</font></span></p></div></div><div c=
lass=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-va=
riant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;lin=
e-height:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-va=
riant-ligatures:no-common-ligatures"><font face=3D"monospace">RFC5321.MailF=
rom domain of &quot;<a href=3D"http://cbg.bounces.example.com">cbg.bounces.=
example.com</a>&quot;, and the address</font></span></p></div></div><div cl=
ass=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-var=
iant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line=
-height:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-var=
iant-ligatures:no-common-ligatures"><font face=3D"monospace">portion of the=
 RFC5322.From field contains &quot;<a href=3D"mailto:payments@example.com">=
payments@example.com</a>&quot;,</font></span></p></div></div><div class=3D"=
gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height=
:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-li=
gatures:no-common-ligatures"><font face=3D"monospace">the Authenticated RFC=
5321.MailFrom domain identifier and the</font></span></p></div></div><div c=
lass=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-va=
riant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;lin=
e-height:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-va=
riant-ligatures:no-common-ligatures"><font face=3D"monospace">RFC5322.From =
domain are considered to be &quot;in alignment&quot; in relaxed</font></spa=
n></p></div></div><div class=3D"gmail_quote"><div><p class=3D"gmail-p1" sty=
le=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal=
;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span class=3D"gm=
ail-s1" style=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"=
monospace">mode, but not in strict mode. In order for the two identifiers t=
o</font></span></p></div></div><div class=3D"gmail_quote"><div><p class=3D"=
gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-variant-east=
-asian:normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><spa=
n class=3D"gmail-s1" style=3D"font-variant-ligatures:no-common-ligatures"><=
font face=3D"monospace">be considered &quot;in alignment&quot; in strict mo=
de, the domain parts would</font></span></p></div></div><div class=3D"gmail=
_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric=
:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:norm=
al;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-ligatur=
es:no-common-ligatures"><font face=3D"monospace">have to be identical.</fon=
t></span></p></div></div><div class=3D"gmail_quote"><div><p class=3D"gmail-=
p2" style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian=
:normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0);min-height:=
13px"><font face=3D"monospace"><br></font></p></div></div><div class=3D"gma=
il_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numer=
ic:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:no=
rmal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-ligat=
ures:no-common-ligatures"><font face=3D"monospace">The reader should note t=
hat SPF alignment checks in DMARC rely solely<span class=3D"gmail-Apple-con=
verted-space">=C2=A0</span></font></span></p></div></div><div class=3D"gmai=
l_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeri=
c:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:nor=
mal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-ligatu=
res:no-common-ligatures"><font face=3D"monospace">on the RFC5321.MailFrom d=
omain. This differs from section 2.3 of [@!RFC7208],<span class=3D"gmail-Ap=
ple-converted-space">=C2=A0</span></font></span></p></div></div><div class=
=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;font-varian=
t-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-he=
ight:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"font-varian=
t-ligatures:no-common-ligatures"><font face=3D"monospace">which recommends =
that SPF checks be done on not only the &quot;MAIL FROM&quot;<span class=3D=
"gmail-Apple-converted-space">=C2=A0</span></font></span></p></div></div><d=
iv class=3D"gmail_quote"><div><p class=3D"gmail-p1" style=3D"margin:0px;fon=
t-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal=
;line-height:normal;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"fon=
t-variant-ligatures:no-common-ligatures"><font face=3D"monospace" style=3D"=
">but also on a separate check of the &quot;HELO&quot; identity.</font></sp=
an></p></div></div></blockquote><div class=3D"gmail_quote"><div>







<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;line-height:normal;font-famil=
y:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gmail-s1" style=3D=
"font-variant-ligatures:no-common-ligatures"></span></p>
</div></div><div class=3D"gmail_quote"><div>



<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;line-height:normal;font-famil=
y:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gmail-s1" style=3D=
"font-variant-ligatures:no-common-ligatures"></span></p></div></div><div cl=
ass=3D"gmail_quote"><div><br></div><div>=C2=A0</div></div>-- <br><div dir=
=3D"ltr" class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-heigh=
t:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left=
"><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:sma=
ll;font-family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:=
baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | Sr. Tec=
hnical Program Manager</span></div><span style=3D"vertical-align:baseline;w=
hite-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-a=
lign:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span st=
yle=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" =
target=3D"_blank">todd.herr@valimail.com</a></span></div></span><span><div>=
<span><b>p:</b></span><span> 703.220.4153 </span><span></span></div></span>=
<p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,san=
s-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;=
margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family=
:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baselin=
e;white-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__=
6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTv=
q_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: =
none; height: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color=
:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;backg=
round-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:=
0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line=
-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=
=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This em=
ail and all data transmitted with it contains confidential and/or proprieta=
ry information intended solely for the use of individual(s) authorized to r=
eceive it. If you are not an intended and authorized recipient you are here=
by notified of any use, disclosure, copying or distribution of the informat=
ion included in this transmission is prohibited and may be unlawful. Please=
 immediately notify the sender by replying to this email and then delete it=
 from your system.</span></font></p></span></div></div>

--0000000000006d2e9705b9bfe312--


From nobody Mon Jan 25 13:06:20 2021
Return-Path: <mike@fresheez.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 44C853A18DC for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:06:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 g6eeR8EoWadr for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:06:16 -0800 (PST)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBF2C3A18DB for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:06:16 -0800 (PST)
Received: by mail-pl1-x633.google.com with SMTP id q2so5667308plk.4 for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:06:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=WvBNEVl2j8aMKAaFs/2NKPys9VhDapPZxWrEVEhN2LM=; b=BCcDepQLqqxnzhCdwNKp0gOm05EypkLYbxZ1d3BCvX9SRsiRNqbpOQMRRH3EvJisZf MCd1smo7x/+C27hyxKfieHJM2SlomzCE8IJ6lEqw8qExWMfQnrmxSm9/+uOBmJVlmJr+ rxxId3vjfKPzAI/BznXO6GwzhEtb0/TMEiPyw7fqLbEQcTvv8ttrisNJWwyG8aHlVDwn liP8l98lCylCuTCID3j/tAwp9Ij++JV3t+IsPIwhp+pdCYs8dqKhHOFEo8CRvMyvHQ7R OD6sS+2RgRzvKJpKTRjqGmjrnEIZnc4GEO7HrKl+oOQe6/phdl/D/UTRFeJ4C7Iw6h8o M0Pw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=WvBNEVl2j8aMKAaFs/2NKPys9VhDapPZxWrEVEhN2LM=; b=k0O2bUoXF21E886xVYdqYtohRB3ZKedDWGDi7LU43qJQqyo9KuiDpwf90H9RdaS5g5 CsMC6DisZIaxuZjySFDSIVNA5WzKTipn2+0ktrL6Cs/G6Hbq38vdZXVZOQSMSsPBjfHK d6YJ9pFFeQ0kMybZrNJHQ/V9gGbuq3wkbO4vJl0OWCGnngmzuekqX5p4zgybc3zwhIYS 51SW70gz4NQB5y9bN/cq/OWWY1wpVCdVpc2h2bhQbh8AW8CT813MzsTbP9dqCUOWrpDa ct+AXcm09S/gXlk8dCDfQoYiPs4L4ONCrV/KQmVijtErjxpwQGiXYxZab0uF8/PapjOf YWTw==
X-Gm-Message-State: AOAM531BmhPOA/6UWGpGbwzC3Xkh2v/HLNCdXQZkoQMkV1NgAQurJUO5 xAxer9ZhX+cprJNX9LnI5gi7e0SSJZzIlw==
X-Google-Smtp-Source: ABdhPJwzBokDXfi+SIMnfY8FIWvejZbD2pwcb9zdGx6u/dnpuUwVIb96R1nwuJ15FwPgbcKhv16NlQ==
X-Received: by 2002:a17:902:9888:b029:dc:374:bc8b with SMTP id s8-20020a1709029888b02900dc0374bc8bmr2344785plp.60.1611608776213;  Mon, 25 Jan 2021 13:06:16 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id 141sm17609907pfa.65.2021.01.25.13.06.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 13:06:15 -0800 (PST)
To: Seth Blank <seth@valimail.com>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <34317129-8225-fb38-4ad3-e1b9ffed21fb@iecc.com> <CAHej_8mTaFo7aESFk4pHjbqbheriYPoAy6f+HhcE6ASVJSyViA@mail.gmail.com> <df867378-5da0-b912-2a0f-b2081d1f2437@mtcc.com> <CAHej_8kfCC1H89pRjgxXK=+BizJHFdKgnr7Gxh_2wWq8P7L-0Q@mail.gmail.com> <a94cb6c0-0a32-da8d-4bd5-9c7ab2866c82@mtcc.com> <CAH48ZfxkQ9g-gmBOPdDsxr4RDvXOi56EaX=aJVDbuL_g7kR+xQ@mail.gmail.com> <CAOZAAfOB93fpYRjwxgQNkG-ydVHLtvgUp0LLROvv-F-amJVy4w@mail.gmail.com> <b9e8da8e-f46a-49c0-4196-1d50ed94d526@mtcc.com> <CAOZAAfPh4kYq0yXhtP9BaPmtP_rc7L-0f=r3Ff_P3oxrhYqvtw@mail.gmail.com> <fd74120f-bfad-ef51-64d7-2f8ec4f00fab@mtcc.com> <CAL0qLwaPmMGR48EUhNkmZTozjoiTMnC6Rfmjdo9vLYD6ZhNoAw@mail.gmail.com> <CAOZAAfMcQ3HCrQAgKWeK-n2Acf+COK+E3HuCauh8g44KiWj=ng@mail.gmail.com> <25ea488b-e432-75c4-c57a-01d03308208c@mtcc.com> <CAOZAAfP5n15=Ez6_SFmkyDOyF=mpD8npZJmJujKP1vw322fGLg@mail.gmail.com> <2f73843f-eaec-5bb7-c59c-08ff387418e3@mtcc.com> <CAOZAAfMBwuXEyxnCgObChb_irCME9w=5ZjedjdSz=0qzFj6uVw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <67e052b6-2556-2ded-6995-60ddbac28094@mtcc.com>
Date: Mon, 25 Jan 2021 13:06:14 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAOZAAfMBwuXEyxnCgObChb_irCME9w=5ZjedjdSz=0qzFj6uVw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------D769A999B39C69C518B2AAD6"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/bNHImrPlmyN_t-f2RgKqRrs3DhM>
Subject: Re: [dmarc-ietf] reporting security requirements
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, 25 Jan 2021 21:06:18 -0000

This is a multi-part message in MIME format.
--------------D769A999B39C69C518B2AAD6
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/25/21 12:47 PM, Seth Blank wrote:
> Entire sections of the document are devoted to preventing reporting 
> abuse. Of course reviewing the security recommendations are part of 
> the process of going standards track which we’ll be undertaking.

As I said, it doesn't appear that there is a whole lot of agreement of 
what the requirements are. Getting a DISCUSS from a security AD is not 
usually the best time to deal with security issues.

Mike


>
> If there are seeing specific operational issues that you believe 
> require clarification in the document, please speak up.
>
> Back to open tickets, please.
>
> On Mon, Jan 25, 2021 at 12:41 Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     On 1/25/21 10:02 AM, Seth Blank wrote:
>     > Michael, are you aware of anyone not following the guidance in the
>     > document? This thread feels like we're discussing a non-issue.
>     > Aggregate reports are already required to be authenticated and I'm
>     > unaware of anyone sending failure reports, let along
>     unauthenticated
>     > ones. Is the language causing problems? Such problems have not been
>     > brought to the list, and would be a good place to start if you
>     want to
>     > build consensus.
>
>      From the looks of it, it doesn't seem like the security
>     requirements of
>     reporting was ever undertaken. There seems to be a wide range of
>     disagreement even if there was given the thread from which this came.
>      From there is actually text, to don't know if it's an issue, to
>     there
>     hasn't been a problem before (as if that were some sort of
>     barometer),
>     to authentication might inconvenience google, to contradicting your
>     assertion that authentication in the way you mentioned can be done.
>     Since this is going to proposed standard from informational, that
>     is not
>     a very good state of affairs, IMO.
>
>     Mike
>
>
> -- 
> *Seth Blank*| VP, Standards and New Technologies
> *e:*seth@valimail.com <mailto:seth@valimail.com>
> *p:*415.273.8818
>
>
> This email and all data transmitted with it contains confidential 
> and/or proprietary information intended solely for the use of 
> individual(s) authorized to receive it. If you are not an intended and 
> authorized recipient you are hereby notified of any use, disclosure, 
> copying or distribution of the information included in this 
> transmission is prohibited and may be unlawful. Please immediately 
> notify the sender by replying to this email and then delete it from 
> your system.
>

--------------D769A999B39C69C518B2AAD6
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 12:47 PM, Seth Blank wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOZAAfMBwuXEyxnCgObChb_irCME9w=5ZjedjdSz=0qzFj6uVw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">Entire sections of the document are devoted to
        preventing reporting abuse. Of course reviewing the security
        recommendations are part of the process of going standards track
        which we’ll be undertaking.</div>
    </blockquote>
    <p>As I said, it doesn't appear that there is a whole lot of
      agreement of what the requirements are. Getting a DISCUSS from a
      security AD is not usually the best time to deal with security
      issues.<br>
    </p>
    <p>Mike<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
cite="mid:CAOZAAfMBwuXEyxnCgObChb_irCME9w=5ZjedjdSz=0qzFj6uVw@mail.gmail.com">
      <div dir="auto"><br>
      </div>
      <div dir="auto">If there are seeing specific operational issues
        that you believe require clarification in the document, please
        speak up.</div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">Back to open tickets, please.</div>
      <div><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Mon, Jan 25, 2021 at
            12:41 Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
              moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
            On 1/25/21 10:02 AM, Seth Blank wrote:<br>
            &gt; Michael, are you aware of anyone not following the
            guidance in the <br>
            &gt; document? This thread feels like we're discussing a
            non-issue. <br>
            &gt; Aggregate reports are already required to be
            authenticated and I'm <br>
            &gt; unaware of anyone sending failure reports, let along
            unauthenticated <br>
            &gt; ones. Is the language causing problems? Such problems
            have not been <br>
            &gt; brought to the list, and would be a good place to start
            if you want to <br>
            &gt; build consensus.<br>
            <br>
             From the looks of it, it doesn't seem like the security
            requirements of <br>
            reporting was ever undertaken. There seems to be a wide
            range of <br>
            disagreement even if there was given the thread from which
            this came. <br>
             From there is actually text, to don't know if it's an
            issue, to there <br>
            hasn't been a problem before (as if that were some sort of
            barometer), <br>
            to authentication might inconvenience google, to
            contradicting your <br>
            assertion that authentication in the way you mentioned can
            be done. <br>
            Since this is going to proposed standard from informational,
            that is not <br>
            a very good state of affairs, IMO.<br>
            <br>
            Mike<br>
            <br>
            <br>
          </blockquote>
        </div>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"
        data-smartmail="gmail_signature"><span>
          <div style="text-align:left"><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technologies</span></div>
          <span style="vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div style="text-align:left"><span style="vertical-align:baseline"><b>e:</b></span><span style="vertical-align:baseline"> <a href="mailto:seth@valimail.com" target="_blank" moz-do-not-send="true">seth@valimail.com</a></span></div></span><span>
            <div><span><b>p:</b></span><span> 415.273.8818 </span><span></span></div>
          </span>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style="border:none;height:40px;width:177px" moz-do-not-send="true"></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#666666"><span style="font-size:10.6667px;white-space:pre-wrap">This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.</span></font></p>
        </span></div>
    </blockquote>
  </body>
</html>

--------------D769A999B39C69C518B2AAD6--


From nobody Mon Jan 25 13:22:30 2021
Return-Path: <johnl@iecc.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 3CB463A18FB for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=KDdvcX0V; dkim=pass (2048-bit key) header.d=taugh.com header.b=l1aV/qC1
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 LjWys-Q0myBX for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:22:27 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 A36063A18F8 for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:22:27 -0800 (PST)
Received: (qmail 18734 invoked from network); 25 Jan 2021 21:22:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=492c.600f3692.k2101; bh=1ALZ0kQko0GKe9/6MHU+zqVxyi8tMFj7U4cfo1WTUZs=; b=KDdvcX0VPSGSV7t9NLFi5b9XlSR7WVudPTYD3fRQbCJkpIpQYDoYyGpGQAxLqOf8ioBaANzyi8r7xX9yih0IwDaE3y4HzK8U7VFBhhrNkkdl42uzUypyVA+6ruarZaEmWYdFTFSOsRqDohcborane5yAvDfJ+X+XT5+rl1AIAzVj7F0EZe6R3vv/CEIQejgmhekCFm2Rkejcb3wzNbCLIJx/hIJAq+iVNknCrfO2F4z3fCw3eoifamJrKKRFGFUnbeU1MLn9Z9Wu/8jsNjOUgiobo7e1Sb6OnX5rp7VxAGh7Xg6fpxK2Jtj1+/nRL66RQ3fPkRGJQnNWSXnKiNGhYQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=492c.600f3692.k2101; bh=1ALZ0kQko0GKe9/6MHU+zqVxyi8tMFj7U4cfo1WTUZs=; b=l1aV/qC1b+a//3Hj7D7VqiYAshqNPqD4OSLqvopEBQqojtVwXaA3eWusVMsYSpp5+iCnD+bg0h5K03ZvWI3699yhbOzbvvYCte8Wjgq6PqE1gqW6b12J0DYyen8/uYmNReu0XMxK+2RRExNollqY4lGRO2TFGRgwUvLDaxDEjPCCmvehs+1nle9mUXXwnmJXW7/3uc6yqwhxyAeY1eB1KJFb3ykDiPHHeXwrNYvjwCs7Ars/JTBpLC7UY06xFVJ67sVeTsm8inO1gsIY761RJ3AZDNcS6FGWPOlhEpdzjkhlkC2X4Ntd7jnI6lsJVVJRu63itC4kpTv7kumomG/XGQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Jan 2021 21:22:26 -0000
Received: by ary.qy (Postfix, from userid 501) id 9045B6C14E41; Mon, 25 Jan 2021 16:22:25 -0500 (EST)
Date: 25 Jan 2021 16:22:25 -0500
Message-Id: <20210125212225.9045B6C14E41@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <14fba490-7b6b-39bc-9a88-7a28aad5c1d5@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/keug59CMIiQzQQPCEjtvYxmjW0o>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 25 Jan 2021 21:22:29 -0000

In article <14fba490-7b6b-39bc-9a88-7a28aad5c1d5@tana.it> you write:
>On Mon 25/Jan/2021 21:07:01 +0100 Michael Thomas wrote:
>> 
>> On 1/25/21 11:53 AM, Alessandro Vesely wrote:
>>> On Sun 24/Jan/2021 19:49:34 +0100 Michael Thomas wrote:
>>>> issue #99 needs to be addressed.
>>>
>>> Won't we put a DKIM-Signature: in the http: header?
>>>
>> I don't know. That would need to be specified. To me it sounds like a good 
>> reason to not try to specify http especially if there doesn't seem to be any 
>> clear desire for it.
>
>Yes, it needs a spec.  It doesn't seem to be overly difficult.

Sheesh.  That isn't mission creep, it's mission gallop.

If you want a domain identity (even though in this case it provides
nothing useful), what's wrong with a client cert? They exist, they
work, they have software support everywhere.


From nobody Mon Jan 25 13:25:36 2021
Return-Path: <todd.herr@valimail.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 6D79B3A18FB for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 REJy5Mu2bVnD for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:25:32 -0800 (PST)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CECED3A18FE for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:25:31 -0800 (PST)
Received: by mail-qt1-x833.google.com with SMTP id c12so10836903qtv.5 for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:25:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bEVyDjuhk3OIdaGXrFxSSpBuZiCHdHg6LXQge4X63ys=; b=b/27zKV6llfh2M+109Kr0RUwgg0w682tF3WUKR2v/WjPC0MZlCxNU0Nu/9REgYY3cU JjtSJUq+yqvmLSqUlK8ji560ij2gX8LTMuVPL9utce0f5MRyUZsILkqiLhPmG3kG24CD BOjqKS0I8yRBgqxkDauwhCeqvRRYbnE8WFiYTGc+BSivxqGUiTSqlWzhwSeRZ60dyM96 WJ24kKCnd5KizaqlHeAJtWAWjWwt+fpKiBkej4MTi+aX/kpTqxl08aENUhRCtdc0zOFm fUYWot3KGnuGgb4j2BhVgcV9RI3IW62Vzjc+s4J4VzVB9/b6sl5UoCJVLUZp6vzCpq6e i4/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bEVyDjuhk3OIdaGXrFxSSpBuZiCHdHg6LXQge4X63ys=; b=NnR61s6mp8vL+aJkqr0q8VKUDwqfgoD/Fa4e4gNrL9mfmdyYv8OmOLZce10alxAVPK jptwLbnrY6+PyNlUU3+SwXTHPCLgX9vb1o1FoBHTKjTqYFtPMzVlsHkYiIREgRCIdM7A ReMD7H9e8OR/+rojBTHZI69POKjgpXU2BKSOxEC8a1YqfxWAIL13CDWzNEUL4Q5IYmat yDne7+KpnuattUOPUXGSbvcWUopnKHKLGhjDTMJnzJjAwy9gPorZ5JewLAvsqXMX8vUg qrqHgjHMOHz2xR5dvM5TI8TuSr9fO+MQRR6YRjAWcQp9RerEEGJAsqkOZHONMGP87k+q 5EPw==
X-Gm-Message-State: AOAM530VjHzlTMIPY9wLIfEHVF1f4qAsiHfeGfxj9orvjlUPDYcc4aE4 hNFz12miLUyEy2i3pyNW7NglEwOA4UoIatP5dYbwRB+Ijxs=
X-Google-Smtp-Source: ABdhPJxBUS1G/JqH1ru2XjKoiLduyr+UjcQiKok0MFv+dG/TKZHhHOS0mesn8lQTumCrUSSKPT8V9awXIlAUth3LNuA=
X-Received: by 2002:ac8:4a82:: with SMTP id l2mr2506138qtq.298.1611609930678;  Mon, 25 Jan 2021 13:25:30 -0800 (PST)
MIME-Version: 1.0
References: <20210125195231.E0DE16C13E26@ary.qy> <12abca41-4420-37c7-c903-7decc012027a@mtcc.com> <CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com> <84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com>
In-Reply-To: <84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 25 Jan 2021 16:25:14 -0500
Message-ID: <CAHej_8=HMV4=emDA8Cdxsq=zdmhJ_WOYU3sd_mN5ugTOOWSXPA@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006f580e05b9c02d27"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/noUQtbwuDdKGwRrk-N32mMASd0Y>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 21:25:35 -0000

--0000000000006f580e05b9c02d27
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 25, 2021 at 3:18 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/25/21 12:08 PM, Todd Herr wrote:
>
> On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas <mike@mtcc.com> wrote:
>
>>
>> On 1/25/21 11:52 AM, John Levine wrote:
>> > In article <
>> CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com> you
>> write:
>> >> -=-=-=-=-=-
>> >>
>> >> DMARC alignment on the report seems of limited value unless it is
>> aligned
>> >> to the domain being reported. ...
>> > I'm getting the impression that some of us have not looked at any DMARC
>> reports.
>> >
>> > Aggregate reports contain the domain of the reporter, and the domain
>> > of the sender to whom they are sending the report. They do NOT have
>> > the domains to which the messages were sent or where they were
>> > received, which are often different for forwarded or mailing list mail.
>> >
>> > For at least the third time, there is no "domain being reported". When
>> > I get reports from Google or any other multi-tenant mail provider,
>> > they do not say to which of their gazillion hosted domains the mail
>> > was sent. That is not a bug, and it's been like that for a decade.
>> >
>> Sounds like a bug to me and an issue should be opened. Just because it's
>> a 10 year old bug doesn't mean it's not a bug.
>>
>>
> I disagree.
>
> Authentication results should not differ at a given provider based solely
> on the destination domain, so there is no reason to report results
> separately for each destination domain. Further, there's no value to the
> report generators, especially at large sites like Google, to expend the
> resources necessary to generate and send X reports when one will do.
>
> So you're saying I should be free to spoof any domain I want because
> Google might be inconvenienced?
>
>
> I'm not at all following your point here. Let me explain what I'm trying
to say, then perhaps you can explain what you're trying to say in a way
that might make a dent in my seemingly-addled brain, and then we can move
forward.

As a domain owner who publishes a DMARC policy record, a DMARC aggregate
report tells me the results of authentication checks done by a given
reporter for mail claiming to be from my domain during a specified period
of time. These aggregate reports group the information by source IP,
telling me how many messages were seen from a given IP by that reporter,
what the policy evaluation results were, what the header from was, and what
the results of the "pure" authentication checks were.

If I were an owner of a domain of any reasonable size generating
non-trivial amounts of traffic on a daily basis, I would expect that some
of the traffic in a given aggregate report was stuff I'd sent, and some
would be stuff others had sent.

When it comes to a hosting provider, such as Google or any provider hosting
more than one domain, I do not expect that the authentication results
reported by the hosting provider about my domain will differ based on the
domain hosted by that provider to which the traffic was sent. If Google
reported mail from foo.com (my domain), I would expect that all mail I sent
from a given IP would show the same authentication results regardless of
whether it was sent to bar.org, baz.net, someotherdomain.com, whatever
domains Google might be hosting. I would further expect that any mail that
I didn't send would show in the report as failing authentication checks
(assuming I've got my authentication stuff set up correctly) regardless of
what domain it was sent to at Google.

The reasons for these expectations are several:

   1. SPF checks are based on the domain in the RFC5321.MailFrom header, or
   sometimes on the domain in the RFC5321.HELO; the destination domain has
   nothing to do with the success or failure of SPF
   2. DKIM checks are based on the DKIM-Signature header(s) in the message;
   the destination domain for the message has no role in the DKIM validation
   effort, as the public key is published by the signer
   3. DMARC checks are based on the From domain (which publishes the DMARC
   policy) and the results of the SPF and DKIM checks (did either pass, and
   does the domain that passed align with the From domain?). Again,
   destination domain doesn't play a role in the DMARC check

So, based on my understanding of how DMARC works and the information that
an aggregate report contains, I do not see how the lack of the destination
domain in an aggregate report gives one freedom to spoof any domain.

Can you please explain your position that the lack of destination domains
in aggregate reports gives one freedom to spoof any domain, and further can
you please specify which domain(s) in this scenario might be free to be
spoofed?

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000006f580e05b9c02d27
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jan 25, 2021 at 3:18 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/25/21 12:08 PM, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas
          &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"_blank">mike@mtcc.=
com</a>&gt;
          wrote:<br>
        </div>
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
            On 1/25/21 11:52 AM, John Levine wrote:<br>
            &gt; In article &lt;<a href=3D"mailto:CAH48ZfwejX1PHO7x1bjJTYye=
hXZWMuq3jrHFJzAHWfy1jQ%2BNQg@mail.gmail.com" target=3D"_blank">CAH48ZfwejX1=
PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com</a>&gt;
            you write:<br>
            &gt;&gt; -=3D-=3D-=3D-=3D-=3D-<br>
            &gt;&gt;<br>
            &gt;&gt; DMARC alignment on the report seems of limited
            value unless it is aligned<br>
            &gt;&gt; to the domain being reported. ...<br>
            &gt; I&#39;m getting the impression that some of us have not
            looked at any DMARC reports.<br>
            &gt;<br>
            &gt; Aggregate reports contain the domain of the reporter,
            and the domain<br>
            &gt; of the sender to whom they are sending the report. They
            do NOT have<br>
            &gt; the domains to which the messages were sent or where
            they were<br>
            &gt; received, which are often different for forwarded or
            mailing list mail.<br>
            &gt;<br>
            &gt; For at least the third time, there is no &quot;domain bein=
g
            reported&quot;. When<br>
            &gt; I get reports from Google or any other multi-tenant
            mail provider,<br>
            &gt; they do not say to which of their gazillion hosted
            domains the mail<br>
            &gt; was sent. That is not a bug, and it&#39;s been like that
            for a decade.<br>
            &gt;<br>
            Sounds like a bug to me and an issue should be opened. Just
            because it&#39;s <br>
            a 10 year old bug doesn&#39;t mean it&#39;s not a bug.<br>
            <br>
          </blockquote>
          <div><br>
          </div>
          <div>I disagree.=C2=A0</div>
          <div><br>
          </div>
          <div>Authentication results should not differ at a given
            provider based solely on the destination domain, so there is
            no reason to report results separately for each destination
            domain. Further, there&#39;s no value to the report generators,
            especially at large sites like Google, to expend the
            resources necessary to generate and send X reports when one
            will do.</div>
        </div>
        <br>
      </div>
    </blockquote>
    <p>So you&#39;re saying I should be free to spoof any domain I want
      because Google might be inconvenienced?</p>
    <p><br></p></div></blockquote><div>I&#39;m not at all following your po=
int here. Let me explain what I&#39;m trying to say, then perhaps you can e=
xplain what you&#39;re trying to say in a way that might make a dent in my =
seemingly-addled brain, and then we can move forward.</div><div><br></div><=
div>As a domain owner who publishes a DMARC policy record, a DMARC aggregat=
e report tells me the results of authentication checks done by a given repo=
rter for mail claiming to be from my domain during a specified period of ti=
me. These aggregate reports group the information by source IP, telling me =
how many messages were seen from a given IP by that reporter, what the poli=
cy evaluation results were, what the header from was, and what the results =
of the &quot;pure&quot; authentication checks were.=C2=A0</div><div><br></d=
iv><div>If I were an owner of a domain of any reasonable size generating no=
n-trivial amounts of traffic on a daily basis, I would expect that some of =
the traffic in a given aggregate report was stuff I&#39;d sent, and some wo=
uld be stuff others had sent.=C2=A0</div><div><br></div><div>When it comes =
to a hosting provider, such as Google or any provider hosting more than one=
 domain, I do not expect that the authentication results reported by the ho=
sting provider about my domain will differ based on the domain hosted by th=
at provider to which the traffic was sent. If Google reported mail from <a =
href=3D"http://foo.com">foo.com</a> (my domain), I would expect that all ma=
il I sent from a given IP would show the same authentication results regard=
less of whether it was sent to <a href=3D"http://bar.org">bar.org</a>, <a h=
ref=3D"http://baz.net">baz.net</a>, <a href=3D"http://someotherdomain.com">=
someotherdomain.com</a>, whatever domains Google might be hosting. I would =
further expect that any mail that I didn&#39;t send would show in the repor=
t as failing authentication checks (assuming I&#39;ve got my authentication=
 stuff set up correctly) regardless of what domain it was sent to at Google=
.</div><div><br></div><div>The reasons for these expectations are several:<=
/div><div><ol><li>SPF checks are based on the domain in the RFC5321.MailFro=
m header, or sometimes on the domain in the RFC5321.HELO; the destination d=
omain has nothing to do with the success or failure of SPF</li><li>DKIM che=
cks are based on the DKIM-Signature header(s) in the message; the destinati=
on domain for the message has no role in the DKIM validation effort, as the=
 public key is published by the signer</li><li>DMARC checks are based on th=
e From domain (which publishes the DMARC policy) and the results of the SPF=
 and DKIM checks (did either pass, and does the domain that passed align wi=
th the From domain?). Again, destination domain doesn&#39;t play a role in =
the DMARC check=C2=A0</li></ol><div>So, based on my understanding of how DM=
ARC works and the information that an aggregate report contains, I do not s=
ee how the lack of the destination domain in an aggregate report gives one =
freedom to spoof any domain.</div></div><div><br></div><div>Can you please =
explain your position that the lack of destination domains in aggregate rep=
orts gives one freedom to spoof any domain, and further can you please spec=
ify which domain(s) in this scenario might be free to be spoofed?</div><div=
><br></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p=
 dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"><=
/p><div style=3D"text-align:left"><span style=3D"vertical-align:baseline;wh=
ite-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></spa=
n><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:sma=
ll;font-family:Arial"> | Sr. Technical Program Manager</span></div><span st=
yle=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-fa=
mily:Arial"><div style=3D"text-align:left"><span style=3D"vertical-align:ba=
seline"><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=3D=
"mailto:todd.herr@valimail.com" target=3D"_blank">todd.herr@valimail.com</a=
></span></div></span><span><div><span><b>p:</b></span><span> 703.220.4153 <=
/span><span></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34)=
;font-family:Arial,Helvetica,sans-serif;font-size:small;background-color:rg=
b(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;vertical-align:baseline;white-space:pre-wrap"><img src=3D"https:/=
/lh5.googleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4T=
YnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3=
rjz19-Dx9rESL" style=3D"border: none; height: 40px; width: 177px;"></span><=
/p><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,=
sans-serif;font-size:small;background-color:rgb(255,255,255);line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"backgr=
ound-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0=
pt"><font color=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667=
px;white-space:pre-wrap">This email and all data transmitted with it contai=
ns confidential and/or proprietary information intended solely for the use =
of individual(s) authorized to receive it. If you are not an intended and a=
uthorized recipient you are hereby notified of any use, disclosure, copying=
 or distribution of the information included in this transmission is prohib=
ited and may be unlawful. Please immediately notify the sender by replying =
to this email and then delete it from your system.</span></font></p></span>=
</div></div>

--0000000000006f580e05b9c02d27--


From nobody Mon Jan 25 13:26:55 2021
Return-Path: <smj@crash.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 770423A18FE for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=crash.com
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 PoA8L6vN449E for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:26:52 -0800 (PST)
Received: from segv.crash.com (segv.crash.com [IPv6:2001:470:1:1e9::4415]) (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 120EC3A18FB for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:26:51 -0800 (PST)
Received: from [10.10.10.124] (192-184-141-33.static.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.7) with ESMTPSA id 10PLQbpr063604 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dmarc@ietf.org>; Mon, 25 Jan 2021 21:26:47 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 10PLQbpr063604
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1611610009; bh=uArxSRhtd98GICkt9hgN1eixM2hBDDZ1pSItvcyUGU8=; h=Subject:To:References:From:Date:In-Reply-To; b=ihtV3caqUGUT2Meh6tdQFtM4zg3e23rpsGGYK8UYMCW0qxjkFtVHSZAWge4NTPEfE FhbHqIP7XGx/5xiBM/15ODX8eA9DA8xoNBEaRygeK8v7FmFPp4wrU2GYSOkacqab4x o/9zNv3d1HQxTykeh3leOh7uW3RfNyDWOCFOIhpOoq83XhjF65HYMkaUQThCM5AL6h nbggdRuccSishsBeHpudz251FrrH8RlB9HDXbJ1oKXa9iH8YLuuqsxdvFYaNquwAOV k+M87T1eNcLlTvuHAkTQ7pxRFH4YKu0HIC0nSdj3k/YpmUaI4uMN68b3A45yd+zgFQ AtSatQ55Rllgg==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.static.sonic.net [192.184.141.33] claimed to be [10.10.10.124]
To: dmarc@ietf.org
References: <20210125195231.E0DE16C13E26@ary.qy> <12abca41-4420-37c7-c903-7decc012027a@mtcc.com> <CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com> <84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <3ff74c76-9ac9-d4ce-32aa-96fea9a8b0e3@crash.com>
Date: Mon, 25 Jan 2021 13:26:37 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com>
Content-Type: multipart/alternative; boundary="------------E3AEF1F3B410333A873C97E0"
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Mon, 25 Jan 2021 21:26:47 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/RsoKpJZFDjiIfu8xe0FJgBh96_E>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 21:26:53 -0000

This is a multi-part message in MIME format.
--------------E3AEF1F3B410333A873C97E0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 1/25/21 12:18 PM, Michael Thomas wrote:
>
> On 1/25/21 12:08 PM, Todd Herr wrote:
>> On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas <mike@mtcc.com 
>> <mailto:mike@mtcc.com>> wrote:
>>
>>
>>     Sounds like a bug to me and an issue should be opened. Just
>>     because it's
>>     a 10 year old bug doesn't mean it's not a bug.
>>
>>
>> I disagree.
>>
>> Authentication results should not differ at a given provider based 
>> solely on the destination domain, so there is no reason to report 
>> results separately for each destination domain. Further, there's no 
>> value to the report generators, especially at large sites like 
>> Google, to expend the resources necessary to generate and send X 
>> reports when one will do.
>>
> So you're saying I should be free to spoof any domain I want because 
> Google might be inconvenienced?
>

If the language in 7.2.1.1 that Seth cited is "working," then report 
generators are sending reports that pass DMARC and the report receivers 
are validating that before ingesting the attached reports. However this 
only provides some degree of attribution for the report itself...

We can certainly check with report receivers to confirm that they are 
doing that validation, and perhaps get some measure of how often they 
see reports that don't pass. What does that leave us with?

Assuming 7.2.1.1 "works," reports that don't pass DMARC won't be 
processed, and won't cause the confusion and/or delayed implementation 
you cited as the potential harm.

That leaves reports that pass DMARC, sent from domains that haven't 
actually handled the sending domain's email. This sounds to me like 
reports that contain false data. Reports containing false data are 
identified as a security consideration in RFC7489 Section 12.2, without 
a reference to 7.2.1.1 as the suggested mitigation.

I don't see where additional authentication of the report itself can 
address this concern, given the availability of disposable domains. That 
leaves report receivers with the need to track report senders' 
reputation, which might warrant a mention in the revised spec.

What did I miss?

--S.



--------------E3AEF1F3B410333A873C97E0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/25/21 12:18 PM, Michael Thomas
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div class="moz-cite-prefix"><br>
        On 1/25/21 12:08 PM, Todd Herr wrote:<br>
      </div>
      <blockquote type="cite"
cite="mid:CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com">
        <meta http-equiv="content-type" content="text/html;
          charset=UTF-8">
        <div dir="ltr">
          <div dir="ltr">On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas
            &lt;<a href="mailto:mike@mtcc.com" moz-do-not-send="true">mike@mtcc.com</a>&gt;
            wrote:<br>
          </div>
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex"><br>
              Sounds like a bug to me and an issue should be opened.
              Just because it's <br>
              a 10 year old bug doesn't mean it's not a bug.<br>
            </blockquote>
            <div><br>
            </div>
            <div>I disagree. </div>
            <div><br>
            </div>
            <div>Authentication results should not differ at a given
              provider based solely on the destination domain, so there
              is no reason to report results separately for each
              destination domain. Further, there's no value to the
              report generators, especially at large sites like Google,
              to expend the resources necessary to generate and send X
              reports when one will do.</div>
          </div>
          <br>
        </div>
      </blockquote>
      <p>So you're saying I should be free to spoof any domain I want
        because Google might be inconvenienced?</p>
    </blockquote>
    <p><br>
    </p>
    <p>If the language in 7.2.1.1 that Seth cited is "working," then
      report generators are sending reports that pass DMARC and the
      report receivers are validating that before ingesting the attached
      reports. However this only provides some degree of attribution for
      the report itself...<br>
    </p>
    <p>We can certainly check with report receivers to confirm that they
      are doing that validation, and perhaps get some measure of how
      often they see reports that don't pass. What does that leave us
      with?</p>
    <p>Assuming 7.2.1.1 "works," reports that don't pass DMARC won't be
      processed, and won't cause the confusion and/or delayed
      implementation you cited as the potential harm.<br>
    </p>
    <p>That leaves reports that pass DMARC, sent from domains that
      haven't actually handled the sending domain's email. This sounds
      to me like reports that contain false data. Reports containing
      false data are identified as a security consideration in RFC7489
      Section 12.2, without a reference to 7.2.1.1 as the suggested
      mitigation.</p>
    <p>I don't see where additional authentication of the report itself
      can address this concern, given the availability of disposable
      domains. That leaves report receivers with the need to track
      report senders' reputation, which might warrant a mention in the
      revised spec.<br>
    </p>
    <p>What did I miss?<br>
    </p>
    <p>--S.</p>
    <p><br>
    </p>
  </body>
</html>

--------------E3AEF1F3B410333A873C97E0--


From nobody Mon Jan 25 13:35:13 2021
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 EEA663A1924 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:35:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[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=bUbHMdze; dkim=pass (2048-bit key) header.d=kitterman.com header.b=NX72LOFn
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 M8g6Ni0jC2R2 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:35:11 -0800 (PST)
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 191FB3A1923 for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:35:10 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id BA5C1F80232 for <dmarc@ietf.org>; Mon, 25 Jan 2021 16:35:09 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1611610509; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=/4selV0E0Ign2QTpaDQO0dHP8nWT+yTdZ7FzXdCJiOw=; b=bUbHMdzerTpclnOHEgbs2rMTwUCiHD20xox4+W6dhVsdjma2zCNpVLxQACirpx6f1SKJ+ sK8WwVYlbPP92ckBw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1611610509; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=/4selV0E0Ign2QTpaDQO0dHP8nWT+yTdZ7FzXdCJiOw=; b=NX72LOFnWc8nGTENeRIxT/qp8fm2vkK1VGLKEObpYrOblU2OHQQrBpyPypVFeuaZsUnhu Ctitl2JkjSRakb0JvY5EkIlrIghtOaYO9WTofGJUIUoM9/uZlU5GVXnKoaJc9QbMe3Iak00 Kd0363b7BFQ3Q135gEGx+OSez6t1AeS8wck7BW2xJ6rf+9FZPavDL1+178Xviq1mHR0+UgI miA5E6s0PKYatYbJhrvTuD8m/yejLZcG5V1gf/RjG7yhke7cLrZPv9wap0jL2t7Df2QQ3aX LlPbsgcV2NrcpFLpJM7dZl1YJ/7586R+OJ6TsHvcOAuAXNZAYTXFvVI9K18g==
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 8AD9BF801FE for <dmarc@ietf.org>; Mon, 25 Jan 2021 16:35:09 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Mon, 25 Jan 2021 16:35:09 -0500
Message-ID: <1627293.fjaifilARp@zini-1880>
In-Reply-To: <CAHej_8nTCxAOZeT-3snPZ0c+pht=kLAX=J-cccUVHaY4c+cHCQ@mail.gmail.com>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <ebf4303b-88e0-4caa-267c-30c2c7516f24@tana.it> <CAHej_8nTCxAOZeT-3snPZ0c+pht=kLAX=J-cccUVHaY4c+cHCQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/gMcXDbQr1dxEKnrfNOwApI-X0pg>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 25 Jan 2021 21:35:13 -0000

On Monday, January 25, 2021 4:04:33 PM EST Todd Herr wrote:
> On Thu, Jan 21, 2021 at 4:24 AM Alessandro Vesely <vesely@tana.it> wrote
> 
> > I agree that the spec needs some text somewhere to counter the passage in
> > Section 2.3 of RFC 7208.  This, methinks, is the intended semantics of the
> > second paragraph of section 3.1.2 of dmarcbis:
> > 
> > OLD:
> >     Note that the RFC5321.HELO identity is not typically used in the
> >     context of DMARC (except when required to "fake" an otherwise null
> >     reverse-path), even though a "pure SPF" implementation according to
> >     [RFC7208] would check that identifier.
> > 
> > I'd rather replace that paragraph and leave item 4 of Section 6.6.2 as
> > is.  For
> > a possibly less confusing wording:
> > 
> > NEW:
> >     Even tough a "pure SPF" implementation, according to [RFC7208], would
> >     avoid to check the RFC5321.MailFrom identity if the RFC5321.HELO was
> >     conclusively determined to pass, DMARC authentication requires the
> >     authenticated identity to be aligned.
> 
> May I propose that the section labeled "SPF-Authenticated Identifiers" be
> rewritten as follows:
> 
> CURRENT:
> 
>    DMARC permits Identifier Alignment, based on the result of an SPF
>    authentication, to be strict or relaxed.
> 
>    In relaxed mode, the [SPF
> <https://tools.ietf.org/html/rfc7489#ref-SPF>]-authenticated domain
> and RFC5322 <https://tools.ietf.org/html/rfc5322>.From
>    domain must have the same Organizational Domain.  In strict mode,
>    only an exact DNS domain match is considered to produce Identifier
>    Alignment.
> 
>    Note that the RFC5321 <https://tools.ietf.org/html/rfc5321>.HELO
> identity is not typically used in the
>    context of DMARC (except when required to "fake" an otherwise null
>    reverse-path), even though a "pure SPF" implementation according to
>    [SPF <https://tools.ietf.org/html/rfc7489#ref-SPF>] would check
> that identifier.
> 
>    For example, if a message passes an SPF check with an
>    RFC5321 <https://tools.ietf.org/html/rfc5321>.MailFrom domain of
> "cbg.bounces.example.com", and the address
>    portion of the RFC5322 <https://tools.ietf.org/html/rfc5322>.From
> field contains "payments@example.com",
>    the Authenticated RFC5321
> <https://tools.ietf.org/html/rfc5321>.MailFrom domain identifier and
> the
>    RFC5322 <https://tools.ietf.org/html/rfc5322>.From domain are
> considered to be "in alignment" in relaxed
> 
>    mode, but not in strict mode.
> 
> 
> 
> NEW:
> 
> DMARC permits Identifier Alignment, based on the result of an SPF
> 
> authentication, to be strict or relaxed.
> 
> 
> In relaxed mode, the [@!RFC3986]-authenticated domain and RFC5322.From
> 
> domain must have the same Organizational Domain.  In strict mode,
> 
> only an exact DNS domain match is considered to produce Identifier
> 
> Alignment.
> 
> 
> For example, if a message passes an SPF check with an
> 
> RFC5321.MailFrom domain of "cbg.bounces.example.com", and the address
> 
> portion of the RFC5322.From field contains "payments@example.com",
> 
> the Authenticated RFC5321.MailFrom domain identifier and the
> 
> RFC5322.From domain are considered to be "in alignment" in relaxed
> 
> mode, but not in strict mode. In order for the two identifiers to
> 
> be considered "in alignment" in strict mode, the domain parts would
> 
> have to be identical.
> 
> 
> The reader should note that SPF alignment checks in DMARC rely solely
> 
> on the RFC5321.MailFrom domain. This differs from section 2.3 of
> [@!RFC7208],
> 
> which recommends that SPF checks be done on not only the "MAIL FROM"
> 
> but also on a separate check of the "HELO" identity.

I think this is fine, but there is a subtlety to be aware of.

If you look at RFC 7208 Section 2.4, when Mail From is null, postmaster@HELO 
is the mail from for SPF purposes.  DMARC really can't change that.

As a result, there are cases where Mail From results actually are derived from 
HELO and it's unavoidable.  I believe the proposed text is clear enough about 
not using separate HELO identity results and that's appropriate.

Scott K




From nobody Mon Jan 25 13:52:34 2021
Return-Path: <mike@fresheez.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 723223A19D0 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:52:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 FTIcG7B-olrU for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:52:27 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0B673A19DF for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:51:58 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id e9so8512206plh.3 for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:51:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=PK0B7LzcFiS0JvYWhyYDrEBiz3Bx4v/vLNik1QiEJ+c=; b=YDsqcrP0FHi/Nl1boETTESObAHbW0pybAIlyGzdM+0t3uMVpcmqKG8dM3wk675DL7V mR9MUqtO9g0syP1GgDz55MH5tkZ38+JS7WG6qsy5I2oTTBg/yMop48gOQKVLeLP/4hiv fFQzRMERcJgCw0PR/DqvT1Xs8CY6I8aSSzZCqTawoYqoIAhOFsj8QYU1W9OdnihChHFa VH0VF40G2Cssv+m53sGpk4VhMdFUIJm+sVAaBRIB7HxUzPfLlLW2sWAG3EjOsflCiq0r idjVH5Nwloym4/0Vt1GiWr3kxlcsEuIodU1uBssNkMdl6eKzF+Il4jb1W5aVZlsrg1Vl 2hCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=PK0B7LzcFiS0JvYWhyYDrEBiz3Bx4v/vLNik1QiEJ+c=; b=pPWrjylggOwT4XlprbYIMFADifbiLEUQ2TyNpuR837sJNe832iMYAcyK8W18JhmLFB 5nR+oOcXggCKU9QgTseWZVdcsGk+IahSYz4nw1lg8tuxnK/4dXrQO/OKidf5OK+0vgN+ wXiGRKXqQ7EoJnnc8afXtUaJvtZlzP3vAy1j6HKCdHSXgooF4yFIz8RpmzZhODEV/LGs Q1zRN1KBTfCQFowqfKagfj502Vu64+rPbG1l+jozjNKQipHTnNY7REeq/p3LdXF2goib B24KfvyiCbATvn6eZ8egyKuZyvpXEiPMgnA9q1NP7DoakmC2uTxHXsdB5hamUax26RcF AgmQ==
X-Gm-Message-State: AOAM530iZySgtKftGjs6D25nVrFXV7h063ztzpZwauBYUelLigwjsIfb eDPnKNX5aPMBdhGFnP0I9HLFeHC63iJOgA==
X-Google-Smtp-Source: ABdhPJzjGqgWss81NLwOveO726DShF/sQ+1LkEbNEm8yzHkd9SBpP1JKQxUjWzgI6TUj9YTciEXe2g==
X-Received: by 2002:a17:90a:c82:: with SMTP id v2mr2307245pja.171.1611611517790;  Mon, 25 Jan 2021 13:51:57 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id 5sm303861pjz.23.2021.01.25.13.51.56 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Jan 2021 13:51:57 -0800 (PST)
To: dmarc@ietf.org
References: <20210125195231.E0DE16C13E26@ary.qy> <12abca41-4420-37c7-c903-7decc012027a@mtcc.com> <CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com> <84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com> <3ff74c76-9ac9-d4ce-32aa-96fea9a8b0e3@crash.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <1767db9a-ce8a-7c85-0aec-7ebda4680ab2@mtcc.com>
Date: Mon, 25 Jan 2021 13:51:55 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <3ff74c76-9ac9-d4ce-32aa-96fea9a8b0e3@crash.com>
Content-Type: multipart/alternative; boundary="------------F7EFD4F82AFFA8B4B90D46F9"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/1m4BMqFKk-exDeH9rdhOCgKSDcY>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 21:52:34 -0000

This is a multi-part message in MIME format.
--------------F7EFD4F82AFFA8B4B90D46F9
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/25/21 1:26 PM, Steven M Jones wrote:
> On 1/25/21 12:18 PM, Michael Thomas wrote:
>>
>> On 1/25/21 12:08 PM, Todd Herr wrote:
>>> On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas <mike@mtcc.com 
>>> <mailto:mike@mtcc.com>> wrote:
>>>
>>>
>>>     Sounds like a bug to me and an issue should be opened. Just
>>>     because it's
>>>     a 10 year old bug doesn't mean it's not a bug.
>>>
>>>
>>> I disagree.
>>>
>>> Authentication results should not differ at a given provider based 
>>> solely on the destination domain, so there is no reason to report 
>>> results separately for each destination domain. Further, there's no 
>>> value to the report generators, especially at large sites like 
>>> Google, to expend the resources necessary to generate and send X 
>>> reports when one will do.
>>>
>> So you're saying I should be free to spoof any domain I want because 
>> Google might be inconvenienced?
>>
>
> If the language in 7.2.1.1 that Seth cited is "working," then report 
> generators are sending reports that pass DMARC and the report 
> receivers are validating that before ingesting the attached reports. 
> However this only provides some degree of attribution for the report 
> itself...
>
Yes, if that were enforced that would solve the problem. Given the 
confusion my guess that it is not. That paragraph could be a lot more 
specific about the mechanisms and motivations which I suggested in #98. 
It probably requires even more than my suggestion after seeing all of 
the list traffic going by. If gsuite is aggregating reports from all of 
their domains they host into one report, there is clearly a problem both 
with the text and with implementations.

And of course, any proposed http method would have to provide equivalent 
protection.

Mike



--------------F7EFD4F82AFFA8B4B90D46F9
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/25/21 1:26 PM, Steven M Jones
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:3ff74c76-9ac9-d4ce-32aa-96fea9a8b0e3@crash.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div class="moz-cite-prefix">On 1/25/21 12:18 PM, Michael Thomas
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com">
        <meta http-equiv="Content-Type" content="text/html;
          charset=UTF-8">
        <div class="moz-cite-prefix"><br>
          On 1/25/21 12:08 PM, Todd Herr wrote:<br>
        </div>
        <blockquote type="cite"
cite="mid:CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com">
          <meta http-equiv="content-type" content="text/html;
            charset=UTF-8">
          <div dir="ltr">
            <div dir="ltr">On Mon, Jan 25, 2021 at 2:56 PM Michael
              Thomas &lt;<a href="mailto:mike@mtcc.com"
                moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
            </div>
            <div class="gmail_quote">
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex"><br>
                Sounds like a bug to me and an issue should be opened.
                Just because it's <br>
                a 10 year old bug doesn't mean it's not a bug.<br>
              </blockquote>
              <div><br>
              </div>
              <div>I disagree. </div>
              <div><br>
              </div>
              <div>Authentication results should not differ at a given
                provider based solely on the destination domain, so
                there is no reason to report results separately for each
                destination domain. Further, there's no value to the
                report generators, especially at large sites like
                Google, to expend the resources necessary to generate
                and send X reports when one will do.</div>
            </div>
            <br>
          </div>
        </blockquote>
        <p>So you're saying I should be free to spoof any domain I want
          because Google might be inconvenienced?</p>
      </blockquote>
      <p><br>
      </p>
      <p>If the language in 7.2.1.1 that Seth cited is "working," then
        report generators are sending reports that pass DMARC and the
        report receivers are validating that before ingesting the
        attached reports. However this only provides some degree of
        attribution for the report itself...<br>
      </p>
    </blockquote>
    <p>Yes, if that were enforced that would solve the problem. Given
      the confusion my guess that it is not. That paragraph could be a
      lot more specific about the mechanisms and motivations which I
      suggested in #98. It probably requires even more than my
      suggestion after seeing all of the list traffic going by. If
      gsuite is aggregating reports from all of their domains they host
      into one report, there is clearly a problem both with the text and
      with implementations.<br>
    </p>
    <p>And of course, any proposed http method would have to provide
      equivalent protection.<br>
    </p>
    <p>Mike<br>
    </p>
    <br>
  </body>
</html>

--------------F7EFD4F82AFFA8B4B90D46F9--


From nobody Mon Jan 25 13:59:28 2021
Return-Path: <seth@valimail.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 A04783A197C for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:59:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 yswEn4eP2H_c for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 13:59:23 -0800 (PST)
Received: from mail-vk1-xa33.google.com (mail-vk1-xa33.google.com [IPv6:2607:f8b0:4864:20::a33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A14D43A197B for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:59:23 -0800 (PST)
Received: by mail-vk1-xa33.google.com with SMTP id e10so794860vkm.2 for <dmarc@ietf.org>; Mon, 25 Jan 2021 13:59:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=20XNU3AteZsV+g3cZx+AJpXB9WN00/nGu29Wmqj8LZU=; b=Y0nyjIinr7Rf3NlOYeKZldCloEKVYjKF25AQn47+NpIRsnJAI4nw6FaPc4VtlTaw2Z ozDvtw7cSzCU3DhVJQWG6wfpXF5v8zfCOTWFGsfU1UPjzgbV/gGLMU0889nE8K5QjQq2 Fi04BVVelbrv+UpXQiOrk/eksgJk+kCQQwg+kz87ZAGvL/K2afF9B/RTGxXUpSMnLJjK 9+8SlkaVpClkxGY382jM5vbbZdD7mgJh61zA558WD1tNYXkTY5AAKFgC1z9qDLankLE2 XpHi2YYTKoInfyy/sm8O2XGwZ0ARNX0hg4oha/SfPXC7UIg02RFjfQHLQkVMhtzm++fK eOfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=20XNU3AteZsV+g3cZx+AJpXB9WN00/nGu29Wmqj8LZU=; b=lnWyi3EFznz0LU33UfeZxPrCKY+JMzzUV3ntlkYVfukrxq8VpninegC3bKXBmdrFaj lgsqh/m6bxzM9RwBbramEtEkfqha5OhshiCTYf2idCesPiQQ9els0meK3Y12kqqKiNPb JKxt6bCWcXwkfE7fZE8H8hPFRURXn8Zorji87la8bF2dsuP0617xlo9Sqn11IbXtpV4u 6HMjzc/MXoP/0GVQSFUUiSJKx4xtOBsJMOvtLXhgpcK7tv5UGHejHicw/JejjXD4qWC4 WYncoAYPvU8pU0rY+mlRKont/8gL6IjzoRDFgCF7QqZnuMoRtXvIYqKulVE29G17YAs9 UL7g==
X-Gm-Message-State: AOAM532epLAj5OWTvCjISeVxSAgYxnRgIVmIVjQAUc91kjeT7U4qKsUn HJ6/XDCRDpZWApCsgHSRSsJjKoapeVyzWFG+yF4ceDYlbBA=
X-Google-Smtp-Source: ABdhPJxOHP5k/xnnoQ4hTYzc2UMUsngTEM/cuy4d0SKa+z00cgnKwOOV1NbKPE1dQdDXH0t7qDFwRjc2jJ/0mpvIKJM=
X-Received: by 2002:a1f:9705:: with SMTP id z5mr2400198vkd.3.1611611962504; Mon, 25 Jan 2021 13:59:22 -0800 (PST)
MIME-Version: 1.0
References: <20210125195231.E0DE16C13E26@ary.qy> <12abca41-4420-37c7-c903-7decc012027a@mtcc.com> <CAHej_8nr=SOuk0eUR481xMWhQ8JC5fjhHeE64w++Ltf0XM9TQw@mail.gmail.com> <84ffcfcd-d391-4382-6a23-dfe100407476@mtcc.com> <3ff74c76-9ac9-d4ce-32aa-96fea9a8b0e3@crash.com> <1767db9a-ce8a-7c85-0aec-7ebda4680ab2@mtcc.com>
In-Reply-To: <1767db9a-ce8a-7c85-0aec-7ebda4680ab2@mtcc.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 25 Jan 2021 13:59:11 -0800
Message-ID: <CAOZAAfMc8YO0ON581N3LwFqXnEBu5+QnUNDB6TAaNuYYnEEkJQ@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008a8b8505b9c0a6ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/61hgaF9KO676PZuDjFz7i5fPf3I>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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, 25 Jan 2021 21:59:26 -0000

--0000000000008a8b8505b9c0a6ac
Content-Type: text/plain; charset="UTF-8"

This thread is now counterproductive and needs to come to a close.

Michael, your continued assertion has been that unauthenticated reports are
an issue. But so far no evidence has been presented that reports are sent
without authentication, or that the text of the document is the cause.

This thread is going in circles. It's now official CLOSED, unless someone
returns with evidence of an actual problem here.

Move on to other tickets.

Seth, as Chair

On Mon, Jan 25, 2021 at 1:55 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/25/21 1:26 PM, Steven M Jones wrote:
>
> On 1/25/21 12:18 PM, Michael Thomas wrote:
>
>
> On 1/25/21 12:08 PM, Todd Herr wrote:
>
> On Mon, Jan 25, 2021 at 2:56 PM Michael Thomas <mike@mtcc.com> wrote:
>
>>
>> Sounds like a bug to me and an issue should be opened. Just because it's
>> a 10 year old bug doesn't mean it's not a bug.
>>
>
> I disagree.
>
> Authentication results should not differ at a given provider based solely
> on the destination domain, so there is no reason to report results
> separately for each destination domain. Further, there's no value to the
> report generators, especially at large sites like Google, to expend the
> resources necessary to generate and send X reports when one will do.
>
> So you're saying I should be free to spoof any domain I want because
> Google might be inconvenienced?
>
>
> If the language in 7.2.1.1 that Seth cited is "working," then report
> generators are sending reports that pass DMARC and the report receivers are
> validating that before ingesting the attached reports. However this only
> provides some degree of attribution for the report itself...
>
> Yes, if that were enforced that would solve the problem. Given the
> confusion my guess that it is not. That paragraph could be a lot more
> specific about the mechanisms and motivations which I suggested in #98. It
> probably requires even more than my suggestion after seeing all of the list
> traffic going by. If gsuite is aggregating reports from all of their
> domains they host into one report, there is clearly a problem both with the
> text and with implementations.
>
> And of course, any proposed http method would have to provide equivalent
> protection.
>
> Mike
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000008a8b8505b9c0a6ac
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This thread is now counterproductive and needs to come to =
a close.<div><br></div><div>Michael, your continued assertion has been that=
 unauthenticated reports are an issue. But so far no evidence has been pres=
ented that reports are sent without authentication, or that the text of the=
 document is the cause.</div><div><br></div><div>This thread is going in ci=
rcles. It&#39;s now official CLOSED, unless someone returns with evidence o=
f an actual problem here.</div><div><br></div><div>Move on to other tickets=
.</div><div><br></div><div>Seth, as Chair=C2=A0</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021=
 at 1:55 PM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/25/21 1:26 PM, Steven M Jones
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div>On 1/25/21 12:18 PM, Michael Thomas
        wrote:<br>
      </div>
      <blockquote type=3D"cite">
       =20
        <div><br>
          On 1/25/21 12:08 PM, Todd Herr wrote:<br>
        </div>
        <blockquote type=3D"cite">
         =20
          <div dir=3D"ltr">
            <div dir=3D"ltr">On Mon, Jan 25, 2021 at 2:56 PM Michael
              Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"_blank"=
>mike@mtcc.com</a>&gt; wrote:<br>
            </div>
            <div class=3D"gmail_quote">
              <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
                Sounds like a bug to me and an issue should be opened.
                Just because it&#39;s <br>
                a 10 year old bug doesn&#39;t mean it&#39;s not a bug.<br>
              </blockquote>
              <div><br>
              </div>
              <div>I disagree.=C2=A0</div>
              <div><br>
              </div>
              <div>Authentication results should not differ at a given
                provider based solely on the destination domain, so
                there is no reason to report results separately for each
                destination domain. Further, there&#39;s no value to the
                report generators, especially at large sites like
                Google, to expend the resources necessary to generate
                and send X reports when one will do.</div>
            </div>
            <br>
          </div>
        </blockquote>
        <p>So you&#39;re saying I should be free to spoof any domain I want
          because Google might be inconvenienced?</p>
      </blockquote>
      <p><br>
      </p>
      <p>If the language in 7.2.1.1 that Seth cited is &quot;working,&quot;=
 then
        report generators are sending reports that pass DMARC and the
        report receivers are validating that before ingesting the
        attached reports. However this only provides some degree of
        attribution for the report itself...<br>
      </p>
    </blockquote>
    <p>Yes, if that were enforced that would solve the problem. Given
      the confusion my guess that it is not. That paragraph could be a
      lot more specific about the mechanisms and motivations which I
      suggested in #98. It probably requires even more than my
      suggestion after seeing all of the list traffic going by. If
      gsuite is aggregating reports from all of their domains they host
      into one report, there is clearly a problem both with the text and
      with implementations.<br>
    </p>
    <p>And of course, any proposed http method would have to provide
      equivalent protection.<br>
    </p>
    <p>Mike<br>
    </p>
    <br>
  </div>

_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards =
and New Technologies</span></div><span style=3D"vertical-align:baseline;whi=
te-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-ali=
gn:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span styl=
e=3D"vertical-align:baseline"> <a href=3D"mailto:seth@valimail.com" target=
=3D"_blank">seth@valimail.com</a></span></div></span><span><div><span><b>p:=
</b></span><span> 415.273.8818 </span><span></span></div></span><p dir=3D"l=
tr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fon=
t-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-spa=
ce:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfmT2Ae5=
LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8y=
zGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; heigh=
t: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(34,34,=
34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-color=
:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></=
p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Arial">=
<span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and all=
 data transmitted with it contains confidential and/or proprietary informat=
ion intended solely for the use of individual(s) authorized to receive it. =
If you are not an intended and authorized recipient you are hereby notified=
 of any use, disclosure, copying or distribution of the information include=
d in this transmission is prohibited and may be unlawful. Please immediatel=
y notify the sender by replying to this email and then delete it from your =
system.</span></font></p></span></div>

--0000000000008a8b8505b9c0a6ac--


From nobody Mon Jan 25 17:33:57 2021
Return-Path: <dougfoster.emailstandards@gmail.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 780D73A1AA8 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 17:33:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 AfSOAsu0LSK8 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 17:33:54 -0800 (PST)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B79673A1AA7 for <dmarc@ietf.org>; Mon, 25 Jan 2021 17:33:54 -0800 (PST)
Received: by mail-vs1-xe36.google.com with SMTP id o125so8251715vsc.6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 17:33:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=+HsnORCwOJ5yYlEu4FcAu6xhqnazbX+y9Nz/nZRNDls=; b=TBKZbiSmfVlT/bVFlGuKOFByalWF4R8kfeSmF+UlNk43yyHRna8DuHFPGg4664aehK 1iN7RwGYTxzjp47g+/fNxnQVYAlX/quso+InhjpTpambIaApPpSya2xGkFCohLS+BRPV 1zwsyZQEPCUh7BoVN7zNuqHViVmT5eHe3wKYtF/yu24k79UMPRdXCFzWPwbeNGTh4laK UV6gb4ZzgG5M+S6zsJ+nlNflbHZMNyyyzIXCyGyQFeI6C5cO3/hnCBinh4EU8lqwwxEa S6xf8vl1GwU0PTOsXXR4qnxSbEcL2IUZzhRGUUevbH0hFdDIsDSpJuyk070Y73Kt8pqE NOwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+HsnORCwOJ5yYlEu4FcAu6xhqnazbX+y9Nz/nZRNDls=; b=OvUU4oiznN4tfuL4gKOOg8OUrJ+WbIiUkj6UbsspBFoUxYCuzrPY+TnjwuKhfp94pe 3WhS+HoPgQEmFbXpAbHJRd9xGuMlW0HcBeXZvtciOAOgGsEaOZoUUpFAQyhBB3HDnBHo gHFrjBrlikmb6cleK2cHd5LnJnEP4LDnU03g8pvn8D8sL17RF8lkpZPwrNNUclVsOFYC K26h2xNjKf1Ugh+bnSp+RVHGoRXSBV625XNhCVbPoydOg3HMqcI+baCFrrpJVX3iwlw4 XJXjceAjm8g5nfkL/cz/VpZBFM/soYivNI98oKKtGwhgphHyyaECFXKfOHiJSRRZLgfi 9RyQ==
X-Gm-Message-State: AOAM533Ft1yJU5KzQVmQzKPsmnLlMXOBmb7RU6FbFQUKrPFF94XHhNd8 sF2y+qSt4YBZsMpHTgLlje5dpRCY6No4rPsL1BCtrF9Ak7Y=
X-Google-Smtp-Source: ABdhPJyHYEJzcMh/1whxhbf4vR8WCyzKkWse1GG0285hPGgGduKdLj38GZjJnso5Ve6l7ViXC2BTRdoqkuE/tTIO7yA=
X-Received: by 2002:a67:c29e:: with SMTP id k30mr2868604vsj.45.1611624833437;  Mon, 25 Jan 2021 17:33:53 -0800 (PST)
MIME-Version: 1.0
References: <20210122224018.E63E06BF246B@ary.qy> <3a6b6650-0276-d59b-54fa-5a3ec41a44a0@tana.it> <CAH48ZfyvjDQoqQp29LG07tz4g_eRMRboJdQ=qK8kzhyyknbMCg@mail.gmail.com> <e9f251cb-a823-4933-2ea2-4cd258bba8e0@tana.it> <CAH48ZfwxJ4nNmGExCJ=n+Zgz95xwmTNKgr6DJbtE0nd9uJVf0A@mail.gmail.com>
In-Reply-To: <CAH48ZfwxJ4nNmGExCJ=n+Zgz95xwmTNKgr6DJbtE0nd9uJVf0A@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 25 Jan 2021 20:33:42 -0500
Message-ID: <CAH48ZfySsxEj3OOA8TEskm_MhMGKcTQUZWghcEZxTmoZJv1siA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b553f305b9c3a5de"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Z6B52tVuOiEBJ2dK35_Ze361tB0>
Subject: [dmarc-ietf] Fwd:  Reports helping spammers? (#81)
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, 26 Jan 2021 01:33:57 -0000

--000000000000b553f305b9c3a5de
Content-Type: text/plain; charset="UTF-8"

---------- Forwarded message ---------
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, Jan 25, 2021 at 8:32 PM
Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)
To: Alessandro Vesely <vesely@tana.it>


Yes, I think you are right, the information loss to bad actors is limited,
while the benefits of information release may be pretty valuable to good
actors.

For reporting users, a "non-aligned" raises important questions:   If it is
a legitimate forward, the sender probably wants it accepted.   If it is a
legitimate forward that the sender wants delivered, but the recipient
blocked because of DMARC, then the sender has to decide whether to drop
back to p=none or From rewrite.  All of this is much easier to evaluate if
the sender provides some disposition feedback.   I think we can say
something along these lines in the security considerations.

You said that the disposition="none" or "sampled out" should only mean "Not
blocked because of DMARC evaluation", without making any indication of
whether the message was blocked for any other reason.   I will rest easier
if this concept is articulated clearly in the document.  It is a big
document and I tend to read it in pieces, so perhaps it is there and I
missed it.

To my original question, I don't think I would ever send a report to a
domain that has a negative reputation, or a domain with no reputation that
came from a source with negative reputation.   I don't want those people
talking to me, so I have no intention of talking to them.   That still
allows for notifying positive-reputation domains if a negative-reputation
source abuses their domain.

Doug Foster


On Mon, Jan 25, 2021 at 6:03 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Sat 23/Jan/2021 15:13:53 +0100 Douglas Foster wrote:
> >
> > I can fully endorse Murray's position that alignment reporting is
> beneficial,
> > even when the sending domain is malicious.   However, it is also
> off-topic.
> >   My focus is on disposition reporting, not alignment reporting.
>
>
> I see.
>
>
> > Bottom line:  The perceived risk of disposition reporting will differ
> with each
> > person, and therefore with each reporting domain.    The specification
> would be
> > improved by providing a way for skeptical domain owners to redact
> > information that they do not wish to disclose.   Currently, the
> options are to
> > (a) not report at all, or (b) report ambiguous and slightly misleading
> > information such as "dispostion=quarantine, overridereason=other".   A
> better
> > option would be to have options to state "dispositioin=not specified,
> > overridereason=not specified".
>
>
> The information that reports actually disclose is when they say why the
> disposition differs from what the author's domain asked.  That info is
> given in
> the comment field, which can be "forwarded", "sampled_out",
> "trusted_forwarder", "mailing_list", "local_policy", or any other reason.
> This
> field is already optional.
>
> Saying "none" without explaining why doesn't really disclose much, does it?
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>

--000000000000b553f305b9c3a5de
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">---------- Forwarded message ---------<br>From: <strong cla=
ss=3D"gmail_sendername" dir=3D"auto">Douglas Foster</strong> <span dir=3D"a=
uto">&lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfoster.=
emailstandards@gmail.com</a>&gt;</span><br>Date: Mon, Jan 25, 2021 at 8:32 =
PM<br>Subject: Re: [dmarc-ietf] Reports helping spammers? (#81)<br>To: Ales=
sandro Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt;<=
br></div><br><br><div dir=3D"ltr">Yes, I think you are right, the informati=
on loss to bad actors is limited, while the benefits of information release=
 may be pretty valuable to good actors.<div><br></div><div>For reporting us=
ers, a &quot;non-aligned&quot; raises important questions:=C2=A0 =C2=A0If i=
t is a legitimate forward, the sender probably wants it accepted.=C2=A0 =C2=
=A0If it is a legitimate forward that the sender wants delivered, but the r=
ecipient blocked because of DMARC, then the sender has to decide whether to=
 drop back to p=3Dnone or From rewrite.=C2=A0 All of this is much easier to=
 evaluate if the sender provides some disposition feedback.=C2=A0 =C2=A0I t=
hink we can say something along these lines in the security considerations.=
</div><div><br></div><div>You said that the disposition=3D&quot;none&quot; =
or &quot;sampled out&quot; should only mean &quot;Not blocked because of DM=
ARC evaluation&quot;, without making any indication of whether the message =
was blocked for any other reason.=C2=A0 =C2=A0I will rest easier if this co=
ncept is articulated clearly in the document.=C2=A0 It is a big document an=
d I tend to read it in pieces, so perhaps it is there and I missed it.</div=
><div><br></div><div>To my original question, I don&#39;t think I would eve=
r send a report to a domain that has a negative reputation, or a domain wit=
h no reputation that came from a source with negative reputation.=C2=A0 =C2=
=A0I don&#39;t want those people talking to me, so I have no intention of t=
alking to them.=C2=A0 =C2=A0That still allows for notifying positive-reputa=
tion domains if a negative-reputation source abuses their domain.</div><div=
><br></div><div>Doug Foster</div><div><br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 6:0=
3 AM Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it" target=3D"_bla=
nk">vesely@tana.it</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">On Sat 23/Jan/2021 15:13:53 +0100 Douglas Foster wrote:<b=
r>
&gt; <br>
&gt; I can fully endorse Murray&#39;s position that alignment=C2=A0reportin=
g is beneficial, <br>
&gt; even when the sending=C2=A0domain is malicious.=C2=A0 =C2=A0However, i=
t is also off-topic.=C2=A0 <br>
&gt;=C2=A0 =C2=A0My focus is on disposition reporting, not alignment report=
ing.<br>
<br>
<br>
I see.<br>
<br>
<br>
&gt; Bottom line:=C2=A0 The perceived risk of disposition reporting will di=
ffer with each <br>
&gt; person, and therefore with each reporting domain.=C2=A0 =C2=A0 The spe=
cification would be <br>
&gt; improved by providing a way for skeptical domain owners to redact <br>
&gt; information=C2=A0that they do not wish to disclose.=C2=A0 =C2=A0Curren=
tly, the options=C2=A0are to <br>
&gt; (a) not report at all, or (b) report ambiguous and slightly misleading=
 <br>
&gt; information such as &quot;dispostion=3Dquarantine, overridereason=3Dot=
her&quot;.=C2=A0 =C2=A0A better <br>
&gt; option would be to have options to state &quot;dispositioin=3Dnot=C2=
=A0specified, <br>
&gt; overridereason=3Dnot specified&quot;.<br>
<br>
<br>
The information that reports actually disclose is when they say why the <br=
>
disposition differs from what the author&#39;s domain asked.=C2=A0 That inf=
o is given in <br>
the comment field, which can be &quot;forwarded&quot;, &quot;sampled_out&qu=
ot;, <br>
&quot;trusted_forwarder&quot;, &quot;mailing_list&quot;, &quot;local_policy=
&quot;, or any other reason.=C2=A0 This <br>
field is already optional.<br>
<br>
Saying &quot;none&quot; without explaining why doesn&#39;t really disclose =
much, does it?<br>
<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div>
</div></div>

--000000000000b553f305b9c3a5de--


From nobody Tue Jan 26 01:03:14 2021
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 4BAD73A03F3 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 01:03:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 ec2TUvWhNOoH for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 01:03:11 -0800 (PST)
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 C3BD63A03F2 for <dmarc@ietf.org>; Tue, 26 Jan 2021 01:03:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611651789; bh=Rk52OGSAjJ1E+70tELWAjCfZAQC8t1AZJK3Ygz9CZgA=; l=1679; h=To:References:From:Date:In-Reply-To; b=CQcpyNh5bgARKUp/uPds7+sDjlAIIyVYbQosTvMv3sz5hWhZg5C2k4dU1YR4hgGqn 3bNTYrhQLCbyxKQ8WkrshFEO1Nr4pXuU/Hv8cSDs6HZsGyeuMM0yIP7okNofEMYkf5 Vn+5Pxh5ErFlRExtYW840L3Soo1tFKDwR3TJTB8k4QX4vMctMnaOKTLPkr6Jy
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC08B.00000000600FDACC.00002E84; Tue, 26 Jan 2021 10:03:08 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210125212225.9045B6C14E41@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <5749790e-c305-b77d-a2f7-94c30579aa4e@tana.it>
Date: Tue, 26 Jan 2021 10:03:08 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210125212225.9045B6C14E41@ary.qy>
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/T12XVO3FQ9gOwYZdkjW_-XcHfIE>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 26 Jan 2021 09:03:13 -0000

On Mon 25/Jan/2021 22:22:25 +0100 John Levine wrote:
> In article <14fba490-7b6b-39bc-9a88-7a28aad5c1d5@tana.it> you write:
>>On Mon 25/Jan/2021 21:07:01 +0100 Michael Thomas wrote:
>>> 
>>> On 1/25/21 11:53 AM, Alessandro Vesely wrote:
>>>> On Sun 24/Jan/2021 19:49:34 +0100 Michael Thomas wrote:
>>>>> issue #99 needs to be addressed.
>>>>
>>>> Won't we put a DKIM-Signature: in the http: header?
>>>>
>>> I don't know. That would need to be specified. To me it sounds like a good 
>>> reason to not try to specify http especially if there doesn't seem to be any 
>>> clear desire for it.
>>
>>Yes, it needs a spec.  It doesn't seem to be overly difficult.
> 
> Sheesh.  That isn't mission creep, it's mission gallop.


The spec can be commissioned to a narrowly focused WG (like dcrup).

MIME provides for a binary Content-Transfer-Encoding, albeit unused.  To sign a 
message thus (un)encoded, it is unreal to try and apply a line-oriented 
canonicalization.  The new spec should just introduce a "binary" 
canonicalization, which can only be used for the body.  From a software POV, it 
is a trivial update, as it's enough to hash the data as-is.

With that addition, DKIM can be used with HTTP transport, which is an 
interesting point per se.  Meanwhile we can specify that https: SHOULD be DKIM 
signed.


> If you want a domain identity (even though in this case it provides
> nothing useful), what's wrong with a client cert? They exist, they
> work, they have software support everywhere.


Even if you can deduce a From: email address after the Subject Alt Name, you 
cannot reliably associate it to an organizational domain.


Best
Ale
-- 
























From nobody Tue Jan 26 03:55:02 2021
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 AF5163A0B8C for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 03:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level: 
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[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_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 drEy3L5Eo7rW for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 03:55:00 -0800 (PST)
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 5C37D3A0B83 for <dmarc@ietf.org>; Tue, 26 Jan 2021 03:54:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611662097; bh=hByzfJZVD/rPfE5kYeiAkR+Iq3qEqM1qPsVgk1ZJu50=; l=1400; h=To:References:From:Date:In-Reply-To; b=BkD7c2p94q9I0zaKNBMqkNoF9lcurpYk9gD7dE4tn7JlURpz7hirFkb9fBHyfssbJ zkmg40lB9tgFE7TnVYRpeO8QpJtLtIQSkN6xUEaw+VwLo2Uun+ZW4F7EGBeTi3GZzm NCMkk/XCTLYBFRac/zb8F0gBh05w+CGN12Z7RRCkLg6tB5wRoBqMIXSch7WV+
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC09F.0000000060100311.00004452; Tue, 26 Jan 2021 12:54:57 +0100
To: dmarc@ietf.org
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <ebf4303b-88e0-4caa-267c-30c2c7516f24@tana.it> <CAHej_8nTCxAOZeT-3snPZ0c+pht=kLAX=J-cccUVHaY4c+cHCQ@mail.gmail.com> <1627293.fjaifilARp@zini-1880>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <4563d5ac-f481-5af2-100d-4338f67c6da5@tana.it>
Date: Tue, 26 Jan 2021 12:54:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <1627293.fjaifilARp@zini-1880>
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/GLLbBuh-yXXHzZi4LNhV56OiqiY>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 26 Jan 2021 11:55:02 -0000

On Mon 25/Jan/2021 22:35:09 +0100 Scott Kitterman wrote:
> On Monday, January 25, 2021 4:04:33 PM EST Todd Herr wrote:
>> 
>> May I propose that the section labeled "SPF-Authenticated Identifiers" be
>> rewritten as follows:
>> 
>> [...]
>> 
>>    The reader should note that SPF alignment checks in DMARC rely solely
>>    on the RFC5321.MailFrom domain. This differs from section 2.3 of 
>>    [@!RFC7208], which recommends that SPF checks be done on not only the
>>    "MAIL FROM" but also on a separate check of the "HELO" identity. >
> I think this is fine, but there is a subtlety to be aware of.
> 
> If you look at RFC 7208 Section 2.4, when Mail From is null, postmaster@HELO
> is the mail from for SPF purposes.  DMARC really can't change that.
> 
> As a result, there are cases where Mail From results actually are derived from
> HELO and it's unavoidable.


I doubt that SPF filters report envelope-from=postmaster@HELO; more likely they 
write helo=HELO.  In that case, the paragraph quoted above is deceptive.


> I believe the proposed text is clear enough about not using separate HELO
> identity results and that's appropriate.

My filter collects SPF results recorded from an upstream SPF filter.  It writes 
Received-SPF: lines for each identity.  For NDNs, it writes a Received-SPF: for 
the HELO identity only.  Am I allowed to use that result for DMARC?


Best
Ale
-- 


















From nobody Tue Jan 26 04:03:02 2021
Return-Path: <dougfoster.emailstandards@gmail.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 AA3DA3A0BB2 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 04:03:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 px6rHKiR-CGO for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 04:02:58 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C84603A0BB1 for <dmarc@ietf.org>; Tue, 26 Jan 2021 04:02:58 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id o186so8871151vso.1 for <dmarc@ietf.org>; Tue, 26 Jan 2021 04:02:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=/QzyVfBgFnoo7Wk3jFukeuwocZKl39S7yXuPpAIlLAc=; b=tMkvm1cUO+MKISwf7z/zdEPu4DhJPCT4cBFecE7/K1j6lxHiDfIZYb7XRuqMtuIY8e z+A4a93+NFXBaHNYeY4lOEGG9LTfRVEQbQHCH/zd7wvCSMBZ0FhJYjObBPZ22tP6NXXI HQ9JTGzipNIsDrYkOtD02HF0xVWEZ/SKPAwBzfc2jkoMca8NQ1Lhsg8JKp3807UqHW9B MA3vTaJ3aDlFGrGR23u0PLyFf1p16haiHQgPyPtnbCb0R8V01kYgkb7cCTWDimU68/8s jdvp6CPN4XLVlwbecHvnYxuEC/kQUcOUfMrkHp+83UyXe+Lirt/+MpJoteKRzMxtLB7R txng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=/QzyVfBgFnoo7Wk3jFukeuwocZKl39S7yXuPpAIlLAc=; b=p398GcQ/k7P9Ishd7EkKy+VIyIBJajCp7Z3e4l9kTq67QHrxaWvM9KwaxR4Kesgf1O zuN4O6FqWqLK1rCeh267soZKJOVqzIpziOFWWGULTiVJZCeeCVshrQGgoBc5HaPwe0Gl E0+/F44rc3ausHh1M/6GcT21gw+zVBWsEpI1n/Ocojs/GkvX/DDyS37YrleUoph8+RrK Raomrk7r6KUgdmqAeDs312YrJ0OlZ9xWtAqzJWaW4zDQsTXvE4wfPiVTp3/JB19spuQ2 YxSzWSI5SsP1OFzMfcTlsBu7f0VRCBzL8SOLik9i8c7+cFqq24Mb9N4PNaedU8o5AQkr JgIQ==
X-Gm-Message-State: AOAM532vFSh1ETA0KlVTHceBGjkoSPQ2HsQ0C/W/Xqf9Mf79N55Aeei7 DF+vQWDRUUI7RlPTGhVaoggcrjqAjqETm7L4n6ZA7xb/hOs=
X-Google-Smtp-Source: ABdhPJz94Twt+py9Ye7rOZzfjQILCW6xPkv0nAUdUai2Eu4cRH63rs41IZSs+tk2pchcC7UKMjQIp7PLzHESGwG2mfM=
X-Received: by 2002:a67:24c5:: with SMTP id k188mr3984821vsk.16.1611662577419;  Tue, 26 Jan 2021 04:02:57 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it>
In-Reply-To: <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 26 Jan 2021 07:02:46 -0500
Message-ID: <CAH48ZfwvBj3abrAEz1uK2UNyMOBAM1q3pH8cOmazn8VBow3ACQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006cc87105b9cc6ff6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/J0gd8YxVJUkjPPEFDLZ60_QEM60>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 26 Jan 2021 12:03:01 -0000

--0000000000006cc87105b9cc6ff6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This topic becomes much more than "which signature".   It is really about
"what is needed to identify and correct alignment problems".

Based on the authentication discussion, we have several inter-related
issues:
- I started with a concern about putting excessive data collection
requirements on the reporting domain.

- Increased data collection causes data disaggregation.   This becomes a
technical problem as report sizes increase.   Disaggregation also allows
individual message characteristics to be revealed, which becomes a
potential privacy concern.

- In theory, very few attributes should be necessary to triage an alignment
problem:  Source IP, SMTP domain, From Domain, and DKIM scope.  In
practice, investigating root cause is difficult and as a result report
recipients crave maximum data.

My current perspective, still open to being convinced

DKIM Scopes
I have not heard a compelling argument to require information about
authentication tests that are unrelated to alignment testing.    For DKIM
specifically, I think one scope should be sufficient, on this hierarchy:

- The best-aligned scope that verified, or
- the best-aligned scope that failed verification, or
- a no-signature result otherwise.

Anything more complex imposes a gratuitous data collection burden on the
reporting domain and reduces aggregation significantly.   On the technical
side, it has already been noted that variable-length lists are particularly
problematic for calculating aggregates.

I would also suggest dropping the requirement to include all authentication
test results.   Only SPF and aligned DKIM are relevant, and anything more
causes disaggregation.


Aggregation Controls

We have discussed whether the target domain should be included in the
report.  I understand that doing so is not reasonable for the large hosting
services.   On the other hand, including the target domain would be a
trivial matter for smaller operations, and I think it would be valuable for
some research.    Similarly, DKIM scopes are known to be useful for most
investigations, but John has already observed that proliferation of DKIM
scopes can be used to force disaggregation down to the individual recipient
level.

I wonder if the solution to both of these is to use variable aggregation.
  When the number of target domains is small, reporting the source domain
is probably not an issue for either the report sender or the report
receiver.    So we could make the field optional, where some organizations
report an actual target domain and others report a placeholder, with the
level of aggregation chosen by the needs of the reporting organization and
by overall constraints on report size (probably based on number of result
rows).  The same could apply to DKIM:   If disaggregation by DKIM scope
provides a report that is too large, the scope can be replaced with a
placeholder to increase aggregation and reduce report size.

DF

On Mon, Jan 25, 2021 at 1:38 PM Alessandro Vesely <vesely@tana.it> wrote:

> On Mon 25/Jan/2021 18:59:16 +0100 Brotman, Alex wrote:
> >
> > I=E2=80=99m not suggesting that we add anything that would report =E2=
=80=9CSignature
> > validation not attempted=E2=80=9D, that sounds horrible.  Will the orig=
inal
> source
> > potentially care that the message was signed in three other places as t=
he
> > message bounced around?
>
> It can be useful to understand the mail flow.  For example, a signature b=
y
> a
> Mediator can reveal a mailing list, even if the receiver didn't evaluate
> it.
>
>
> > Should we put the onus on the reporting entity to do the filter out the
> > non-aligned (what if none aligned) signatures, or just realize it=E2=80=
=99s some
> > automated job and including all logged/validated signatures is the bett=
er
> > way?
>
> The order in which signatures appear in a report can be significant too.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>

--0000000000006cc87105b9cc6ff6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div>This topic becomes much more than &quo=
t;which signature&quot;.=C2=A0 =C2=A0It is really=C2=A0about &quot;what is =
needed to identify and correct alignment=C2=A0problems&quot;.</div><div><br=
></div>Based on the authentication discussion, we have several inter-relate=
d issues:<div>- I started with a concern about putting excessive data colle=
ction requirements on the reporting domain.</div><div><br></div><div>- Incr=
eased data collection causes data disaggregation.=C2=A0 =C2=A0This becomes =
a technical problem as report sizes increase.=C2=A0 =C2=A0Disaggregation al=
so allows individual message characteristics to be revealed, which becomes =
a potential privacy concern.</div><div><br></div><div>- In theory, very few=
 attributes should be necessary to triage an alignment problem:=C2=A0 Sourc=
e IP, SMTP domain, From Domain, and DKIM scope.=C2=A0 In practice, investig=
ating root cause is difficult and as a result report recipients crave maxim=
um data.</div><div><br></div><div>My current perspective, still open to bei=
ng convinced</div><div><br></div><div>DKIM Scopes</div><div>I have not hear=
d a compelling argument=C2=A0to require information about authentication te=
sts that are unrelated to alignment testing.=C2=A0 =C2=A0 For DKIM specific=
ally, I think one scope should be sufficient, on this hierarchy:=C2=A0 =C2=
=A0=C2=A0</div><div><br></div><div>- The best-aligned scope that verified, =
or=C2=A0</div><div>- the best-aligned scope that failed verification, or=C2=
=A0</div><div>- a no-signature result otherwise.=C2=A0=C2=A0</div><div><br>=
</div><div>Anything more complex imposes a gratuitous data collection burde=
n on the reporting domain and reduces aggregation significantly.=C2=A0 =C2=
=A0On the technical side, it has already been noted that variable-length li=
sts are particularly problematic for calculating aggregates.</div><div><br>=
</div><div>I would also suggest dropping the requirement to include all aut=
hentication test results.=C2=A0 =C2=A0Only SPF and aligned DKIM are relevan=
t, and anything more causes disaggregation.</div><div><br></div><div><br></=
div><div>Aggregation Controls</div><div><br></div><div>We have discussed wh=
ether the target domain should be included in the report.=C2=A0 I understan=
d that doing so is not reasonable for the large hosting services.=C2=A0 =C2=
=A0On the other hand, including the target domain would be a trivial matter=
 for smaller operations, and I think it would be valuable for some research=
.=C2=A0 =C2=A0 Similarly, DKIM scopes are known to be useful for most inves=
tigations, but John has already observed that proliferation of DKIM scopes =
can be used to force disaggregation down to the individual recipient level.=
</div><div><br></div><div>I wonder if the solution to both of these is to u=
se variable aggregation.=C2=A0 =C2=A0 When the number of target domains is =
small, reporting the source domain is probably not an issue for either the =
report sender or the report receiver.=C2=A0 =C2=A0 So we could make the fie=
ld optional, where some organizations report an actual target domain and ot=
hers report a placeholder, with the level of aggregation chosen by the need=
s of the reporting organization and by overall constraints on report size (=
probably based on number of result rows).=C2=A0 The same could apply to DKI=
M:=C2=A0 =C2=A0If disaggregation by DKIM scope provides a report that is to=
o large, the scope can be replaced with a placeholder to increase aggregati=
on and reduce report size.</div><div><br></div><div>DF</div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25,=
 2021 at 1:38 PM Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it">ve=
sely@tana.it</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">On Mon 25/Jan/2021 18:59:16 +0100 Brotman, Alex wrote:<br>
&gt; <br>
&gt; I=E2=80=99m not suggesting that we add anything that would report =E2=
=80=9CSignature<br>
&gt; validation not attempted=E2=80=9D, that sounds horrible.=C2=A0 Will th=
e original source<br>
&gt; potentially care that the message was signed in three other places as =
the<br>
&gt; message bounced around?<br>
<br>
It can be useful to understand the mail flow.=C2=A0 For example, a signatur=
e by a <br>
Mediator can reveal a mailing list, even if the receiver didn&#39;t evaluat=
e it.<br>
<br>
<br>
&gt; Should we put the onus on the reporting entity to do the filter out th=
e<br>
&gt; non-aligned (what if none aligned) signatures, or just realize it=E2=
=80=99s some<br>
&gt; automated job and including all logged/validated signatures is the bet=
ter<br>
&gt; way?<br>
<br>
The order in which signatures appear in a report can be significant too.<br=
>
<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div>

--0000000000006cc87105b9cc6ff6--


From nobody Tue Jan 26 04:50:40 2021
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 65C023A0AD6 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 04:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.21
X-Spam-Level: 
X-Spam-Status: No, score=-0.21 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=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 vVMM3rgtYc8B for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 04:50:37 -0800 (PST)
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 9D30E3A0AD5 for <dmarc@ietf.org>; Tue, 26 Jan 2021 04:50:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611665433; bh=w61rJ7hch0ZG098+JgT+tVnwqJUBjINQtGTuXAIYQXE=; l=7750; h=To:References:From:Date:In-Reply-To; b=Cwii0WQ2oYL149FAK8DykRvJexuEYPlwAG7WjPRVmziXLja9/GmQeml0J54MeU/xi /14F6+M3DXdPFrGfBlEXT1V47dikwLh6ym/t9xGGTClIiu4fJRQi+GuYQ1Bw80fO5B zGSxQ7LQGakYEZCs0M+UGiUgzAkq7NF1eMwZZVN2SGe/9z9LPA+HN847WhdXg
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0D6.0000000060101019.00004A43; Tue, 26 Jan 2021 13:50:33 +0100
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it> <CAH48ZfwvBj3abrAEz1uK2UNyMOBAM1q3pH8cOmazn8VBow3ACQ@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <adcede1d-a260-7b78-9439-63eb706989e2@tana.it>
Date: Tue, 26 Jan 2021 13:50:32 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfwvBj3abrAEz1uK2UNyMOBAM1q3pH8cOmazn8VBow3ACQ@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------6262F3770A673C70EF81536D"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/bYGXi5J6jjhbrYCLwwts2ke5EcQ>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 26 Jan 2021 12:50:39 -0000

This is a multi-part message in MIME format.
--------------6262F3770A673C70EF81536D
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On Tue 26/Jan/2021 13:02:46 +0100 Douglas Foster wrote:
> DKIM Scopes
> I have not heard a compelling argument to require information about 
> authentication tests that are unrelated to alignment testing.    For DKIM 
> specifically, I think one scope should be sufficient, on this hierarchy:
> 
> - The best-aligned scope that verified, or
> - the best-aligned scope that failed verification, or
> - a no-signature result otherwise.
> 
> Anything more complex imposes a gratuitous data collection burden on the 
> reporting domain and reduces aggregation significantly.   On the technical 
> side, it has already been noted that variable-length lists are particularly 
> problematic for calculating aggregates.


Let me attach an HTML rendering of a report I received today, so we can talk 
about something real.

Lines with IP 4.31.198.44 bear a ietf.org identifier.  I see no reason to 
remove it.  It is useful for understanding the mailflow, which is what DMARC 
reporting is designed to do.


> Aggregation Controls
> 
> We have discussed whether the target domain should be included in the
> report.  I understand that doing so is not reasonable for the large hosting
> services.   On the other hand, including the target domain would be a
> trivial matter for smaller operations, and I think it would be valuable for
> some research.    Similarly, DKIM scopes are known to be useful for most
> investigations, but John has already observed that proliferation of DKIM
> scopes can be used to force disaggregation down to the individual recipient
> level.


Even if this is a small example, learning the disaggregated, or even individual 
recipients does not help my understanding.  Authentication is obviously 
conditioned by how the Mediator treats my messages.

I expect that Fastmail Pty Ltd carries out SPF and DKIM validation using the 
same algorithm, irrespective of the recipient.  That is what I, as a sender, am 
interested in.  Splitting the report in 66 lines wouldn't tell me anything 
more, it would just consume more eyeballs.  And is useless for people who sum 
up all reports and just look at the totals.  In any case, I cannot verify if 
the messages I didn't send directly are real.

If a multi-domain host allows personalized validation algorithms for some 
domains, I'd expect they send separated aggregate reports, if any.


Best
Ale
-- 


--------------6262F3770A673C70EF81536D
Content-Type: text/html; charset=UTF-8;
 name="example.html"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="example.html"

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlv
bmFsLy9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5z
aXRpb25hbC5kdGQiPgo8aHRtbCB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94aHRt
bCIgeG1sbnM6ZGF0ZT0iaHR0cDovL2V4c2x0Lm9yZy9kYXRlcy1hbmQtdGltZXMiPjxoZWFk
PjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyAi
IC8+PHRpdGxlPgoJCQkJRmVlZGJhY2sgZnJvbQoJCQkJRmFzdG1haWwgUHR5IEx0ZDwvdGl0
bGU+PHN0eWxlIHR5cGU9InRleHQvY3NzIiBpZD0iaW50ZXJuYWwtc3R5bGUiPgoJCQkJCWJv
ZHkgewoJCQkJCQlmb250LWZhbWlseTogQXJpYWwsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsK
CQkJCQkJY29sb3I6ICMwMDMzMDA7CgkJCQkJCWJhY2tncm91bmQtY29sb3I6ICNmZmNjNjY7
CgkJCQkJfQoJCQkJCXRhYmxlLCBwIHsKCQkJCQkJbWFyZ2luOiAxZW07CgkJCQkJCXBhZGRp
bmc6IDRwdDsKCQkJCQkJYmFja2dyb3VuZC1jb2xvcjogI2ZmZWVhYTsKCQkJCQkJYm9yZGVy
OiAzcHQgc29saWQgIzc3NjYzMzsgCgkJCQkJfQoJCQkJCXRkLCB0aCB7CgkJCQkJCW1hcmdp
bjogMnB0OwoJCQkJCQlwYWRkaW5nOiAycHQ7CgkJCQkJCWJvcmRlcjogMXB0IHNvbGlkICM3
NzY2MzM7IAoJCQkJCX0KCQkJCQkucGFzcyB7CgkJCQkJCWJhY2tncm91bmQtY29sb3I6ICMx
MWJiMDA7CgkJCQkJfQoJCQkJCS5mYWlsIHsKCQkJCQkJYmFja2dyb3VuZC1jb2xvcjogI2Nj
MDAwMDsKCQkJCQl9CgkJCQkJLmRraW1wb2xpY3kgewoJCQkJCQliYWNrZ3JvdW5kLWNvbG9y
OiAjZmZmZjY2OwoJCQkJCX0KCQkJCQkuZXJyb3IgewoJCQkJCQliYWNrZ3JvdW5kLWNvbG9y
OiAjYmJhYWFhOwoJCQkJCQlmb250LXdlaWdodDogYm9sZDsKCQkJCQl9CgkJCQkJLnNvZnRm
YWlsIHsKCQkJCQkJYmFja2dyb3VuZC1jb2xvcjogI2ZmODg2NjsKCQkJCQl9CgkJCQkJLnJl
amVjdCB7CgkJCQkJCWJhY2tncm91bmQtY29sb3I6ICNjYzAwMDA7CgkJCQkJfQoJCQkJCS5x
dWFyYW50aW5lIHsKCQkJCQkJYmFja2dyb3VuZC1jb2xvcjogI2ZmODg2NjsKCQkJCQl9CgkJ
CQkJLm5vcm1hbCB7CgkJCQkJfQoJCQkJCS5maWVsZCB7CgkJCQkJCWZvbnQtd2VpZ2h0OiBi
b2xkOwoJCQkJCX0KCQkJCTwvc3R5bGU+PC9oZWFkPjxib2R5PjxoMT4KCQkJCUZlZWRiYWNr
IGZyb20KCQkJCUZhc3RtYWlsIFB0eSBMdGQ8L2gxPjxwPjxzcGFuIGNsYXNzPSJmaWVsZCI+
SWQ6IDwvc3Bhbj40MTk1ODgwNzI7IDxzcGFuIGNsYXNzPSJmaWVsZCI+YmVnaW46IDwvc3Bh
bj4yMDIxLTAxLTI1VDAwOjAwOjAwWjsgPHNwYW4gY2xhc3M9ImZpZWxkIj5lbmQ6IDwvc3Bh
bj4yMDIxLTAxLTI1VDIzOjU5OjU5WjxiciAvPjxzcGFuIGNsYXNzPSJmaWVsZCI+RG9tYWlu
OiA8L3NwYW4+dGFuYS5pdDsgPHNwYW4gY2xhc3M9ImZpZWxkIj5ES0lNOiA8L3NwYW4+OyA8
c3BhbiBjbGFzcz0iZmllbGQiPlNQRjogPC9zcGFuPjsgPHNwYW4gY2xhc3M9ImZpZWxkIj5w
b2xpY3kgcHVibGlzaGVkOiA8L3NwYW4+bm9uZSBub25lIDEwMDwvcD48dGFibGU+PHRyPjx0
aD4KCQkJCQkJCVJlbGF5aW5nIElQCgkJCQkJCTwvdGg+PHRoPgoJCQkJCQkJbWVzc2FnZSBj
b3VudAoJCQkJCQk8L3RoPjx0aD4KCQkJCQkJCXJlYXNvbiBhbmQgZGlzcG9zaXRpb24KCQkJ
CQkJPC90aD48dGg+CgkJCQkJCQlGcm9tIGhlYWRlcgoJCQkJCQkJPGJyIC8+CgkJCQkJCQko
b3B0LiBlbnZlbG9wZSkKCQkJCQkJPC90aD48dGg+CgkJCQkJCQlTUEYKCQkJCQkJPC90aD48
dGg+CgkJCQkJCQkJREtJTQoJCQkJCQkJPC90aD48dGg+CgkJCQkJCQkJCTJuZCBES0lNCgkJ
CQkJCQkJPC90aD48dGg+CgkJCQkJCQkJCQkzcmQgREtJTQoJCQkJCQkJCQk8L3RoPjwvdHI+
CgkJCQkJPHRyPjx0ZD42Mi45NC4yNDMuMjI2PC90ZD48dGQgYWxpZ249InJpZ2h0Ij4xPC90
ZD48dGQgY2xhc3M9Im5vcm1hbCI+PC90ZD48dGQ+dGFuYS5pdDwvdGQ+PHRkIGNsYXNzPSJw
YXNzIj50YW5hLml0PGJyIC8+bWZyb208YnIgLz48L3RkPjx0ZCBjbGFzcz0icGFzcyI+dGFu
YS5pdDxiciAvPmRlbHRhPGJyIC8+cGFzczwvdGQ+PC90cj4KCQk8dHI+PHRkPjQuMzEuMTk4
LjQ0PC90ZD48dGQgYWxpZ249InJpZ2h0Ij4xNTwvdGQ+PHRkIGNsYXNzPSJub3JtYWwiPnRy
dXN0ZWRfZm9yd2FyZGVyIFBvbGljeSBpZ25vcmVkIGR1ZSB0byBsb2NhbCB3aGl0ZSBsaXN0
PGJyIC8+PC90ZD48dGQ+dGFuYS5pdDwvdGQ+PHRkIGNsYXNzPSJwYXNzIj5pZXRmLm9yZzxi
ciAvPm1mcm9tPGJyIC8+PC90ZD48dGQgY2xhc3M9InBhc3MiPmlldGYub3JnPGJyIC8+aWV0
ZjE8YnIgLz5wYXNzPC90ZD48dGQgY2xhc3M9InBhc3MiPmlldGYub3JnPGJyIC8+aWV0ZjE8
YnIgLz5wYXNzPC90ZD48dGQgY2xhc3M9ImZhaWwiPnRhbmEuaXQ8YnIgLz5kZWx0YTxiciAv
PmZhaWwgKGJvZHkgaGFzIGJlZW4gYWx0ZXJlZCk8L3RkPjwvdHI+CgkJPHRyPjx0ZD40LjMx
LjE5OC40NDwvdGQ+PHRkIGFsaWduPSJyaWdodCI+NTA8L3RkPjx0ZCBjbGFzcz0ibm9ybWFs
Ij48L3RkPjx0ZD50YW5hLml0PC90ZD48dGQgY2xhc3M9InBhc3MiPmlldGYub3JnPGJyIC8+
bWZyb208YnIgLz48L3RkPjx0ZCBjbGFzcz0icGFzcyI+aWV0Zi5vcmc8YnIgLz5pZXRmMTxi
ciAvPnBhc3M8L3RkPjx0ZCBjbGFzcz0icGFzcyI+aWV0Zi5vcmc8YnIgLz5pZXRmMTxiciAv
PnBhc3M8L3RkPjx0ZCBjbGFzcz0icGFzcyI+dGFuYS5pdDxiciAvPmRlbHRhPGJyIC8+cGFz
czwvdGQ+PC90cj4KCQk8L3RhYmxlPjxwPjxiPjx1PkxlZ2VuZDwvdT48YnIgLz4KCQkJCQlk
aXNwb3NpdGlvbjogPC9iPjxzcGFuIGNsYXNzPSJxdWFyYW50aW5lIj5xdWFyYW50aW5lPC9z
cGFuPiwKCQkJCQk8c3BhbiBjbGFzcz0icmVqZWN0Ij5yZWplY3Q8L3NwYW4+LjxiciAvPjxi
PnNwZjogPC9iPjxzcGFuIGNsYXNzPSJwYXNzIj5wYXNzPC9zcGFuPiwKCQkJCQk8c3BhbiBj
bGFzcz0iZmFpbCI+ZmFpbDwvc3Bhbj4sCgkJCQkJPHNwYW4gY2xhc3M9InNvZnRmYWlsIj5z
b2Z0ZmFpbDwvc3Bhbj4sCgkJCQkJPHNwYW4gY2xhc3M9ImVycm9yIj50ZW1wZXJyb3Igb3Ig
cGVybWVycm9yPC9zcGFuPi48YnIgLz48Yj5ka2ltOiA8L2I+PHNwYW4gY2xhc3M9InBhc3Mi
PnBhc3M8L3NwYW4+LAoJCQkJCTxzcGFuIGNsYXNzPSJmYWlsIj5mYWlsPC9zcGFuPiwKCQkJ
CQk8c3BhbiBjbGFzcz0iZGtpbXBvbGljeSI+cG9saWN5PC9zcGFuPi4KCQkJCTwvcD48L2Jv
ZHk+PC9odG1sPgo8QlI+PEZJRUxEU0VUIENMQVNTPSJtaW1lQXR0YWNobWVudEhlYWRlciI+
PC9GSUVMRFNFVD48ZGl2IGNsYXNzPSJtb3otdGV4dC1wbGFpbiI+PHByZSB3cmFwIGNsYXNz
PSJtb3otcXVvdGUtcHJlIj4KClRoaXMgaXMgYSBETUFSQyBhZ2dyZWdhdGUgcmVwb3J0IGZv
ciB0YW5hLml0CgozIHJlY29yZHMuCjIgcGFzc2VkLgoxIGZhaWxlZC4KClN1Ym1pdHRlZCBi
eSBGYXN0bWFpbCBQdHkgTHRkCkdlbmVyYXRlZCB3aXRoIE1haWw6OkRNQVJDIDEuMjAxODA5
MTcKCjwvcHJlPjwvZGl2PjwvYm9keT4NCjwvaHRtbD4NCg==
--------------6262F3770A673C70EF81536D--


From nobody Tue Jan 26 05:14:52 2021
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 9A7063A0C58 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 05:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[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=KNBLNQUN; dkim=pass (2048-bit key) header.d=kitterman.com header.b=JDmxPE3p
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 QHUGq6g4L6Cf for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 05:14:47 -0800 (PST)
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 C5D273A0C56 for <dmarc@ietf.org>; Tue, 26 Jan 2021 05:14:47 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 4A96DF801F9 for <dmarc@ietf.org>; Tue, 26 Jan 2021 08:14:46 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1611666885; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=+KU/+Z/OxLX2c2jkXpGExY6bgMOMlquPGPv4hltj8Co=; b=KNBLNQUNi9YXDOc8SUmd3F44H2Xha8sNOX0IoPjS/C1j/VIis+a+pIHCYa6I5kZVTB09P K0smkVzUbph7rcPBQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1611666885; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=+KU/+Z/OxLX2c2jkXpGExY6bgMOMlquPGPv4hltj8Co=; b=JDmxPE3pbO3W5g5Q65FdoNnsQOsEKRRkOAqQmFxHZe/CUXX5lCiJdqOe/WoZ4iIUXxckq I6ODyGo1IPbChVyNO7Orm0ioYOnhAPO2/9xkavtvKZMc70YFYMYg6BppdFzoP2nffA7nQGH 04HK8G0JCWXhCVhmhNDshVPLikrJEOQBZoj5Md1OQD9HkwQL6OON9svXwxUfactvk4+QI1U MLWGlPhDEmq8UCfQtPUG0ZLG7gE6ZdPAugfD/kMGn6MVUCM/Bx82LlWol194eqQ62bUYX6L 8nPHvfEPWWrPa44FQ2WfL0ZAtNC85T4ZNGDs2xZg4pnyG4j+LeQqJGHPwf0g==
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 CC6D9F80052 for <dmarc@ietf.org>; Tue, 26 Jan 2021 08:14:45 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Tue, 26 Jan 2021 08:14:45 -0500
Message-ID: <1859075.lZWC7Mh21l@zini-1880>
In-Reply-To: <4563d5ac-f481-5af2-100d-4338f67c6da5@tana.it>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1627293.fjaifilARp@zini-1880> <4563d5ac-f481-5af2-100d-4338f67c6da5@tana.it>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/zSHatF4EpG8zt8VE2_vvPK9qR50>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 26 Jan 2021 13:14:51 -0000

On Tuesday, January 26, 2021 6:54:56 AM EST Alessandro Vesely wrote:
> On Mon 25/Jan/2021 22:35:09 +0100 Scott Kitterman wrote:
> > On Monday, January 25, 2021 4:04:33 PM EST Todd Herr wrote:
> >> May I propose that the section labeled "SPF-Authenticated Identifiers" be
> >> rewritten as follows:
> >> 
> >> [...]
> >> 
> >>    The reader should note that SPF alignment checks in DMARC rely solely
> >>    on the RFC5321.MailFrom domain. This differs from section 2.3 of
> >>    [@!RFC7208], which recommends that SPF checks be done on not only the
> >>    "MAIL FROM" but also on a separate check of the "HELO" identity. >
> > 
> > I think this is fine, but there is a subtlety to be aware of.
> > 
> > If you look at RFC 7208 Section 2.4, when Mail From is null,
> > postmaster@HELO is the mail from for SPF purposes.  DMARC really can't
> > change that.
> > 
> > As a result, there are cases where Mail From results actually are derived
> > from HELO and it's unavoidable.
> 
> I doubt that SPF filters report envelope-from=postmaster@HELO; more likely
> they write helo=HELO.  In that case, the paragraph quoted above is
> deceptive.
> > I believe the proposed text is clear enough about not using separate HELO
> > identity results and that's appropriate.
> 
> My filter collects SPF results recorded from an upstream SPF filter.  It
> writes Received-SPF: lines for each identity.  For NDNs, it writes a
> Received-SPF: for the HELO identity only.  Am I allowed to use that result
> for DMARC?

No.  You should only use Mail From results.

Scott K




From nobody Tue Jan 26 06:13:15 2021
Return-Path: <dougfoster.emailstandards@gmail.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 EAEAE3A0A3D for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 06:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 OL_PYad-Vs8S for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 06:13:12 -0800 (PST)
Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10B4E3A0A38 for <dmarc@ietf.org>; Tue, 26 Jan 2021 06:13:11 -0800 (PST)
Received: by mail-ua1-x935.google.com with SMTP id v23so5635072uam.8 for <dmarc@ietf.org>; Tue, 26 Jan 2021 06:13:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OXFE3/9dUnbXILj7S4kz9mIV5YbQn3kxk95Dsb8XTOY=; b=teEy5mIECXMQvPmgZ5kJ+Dh6tzn0krV0M0q6qsdbWjay0F0kN63arsG47tv4d09GOw aykAX0e1aKbrWg9i+RY4lwrOEsnt+40u8r9dq8+gI9AihhzAQ0c+hKFtg8m3P3+uGBNh 2CNyL+HfP6Su121Uv1muWUzD0rDDwea99NNAgjbB8gt9dvlHJe4pNv3mPDFgdrRuLwor BqUjGfEgiG8w3jx7XiqC6eRR2wOpfv8lDDv8qsYidNjoU9B93Ga9E60tubcf8PaVRDd+ 2DeKG7uyNy1tgMNx9k0CFuaZaV8PjJYEmKCo0W7DFJ4Ap1pbTIfxnBQPgmr2i5WAOzf4 buUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OXFE3/9dUnbXILj7S4kz9mIV5YbQn3kxk95Dsb8XTOY=; b=biz0/2//aeP6mz7riR5gehKa6SCeHG0CVtgQIQmvRdJsEoasRJ5V28oAgvgycrtjfa wbxkIlg4c3HkuQg1PuX84KYQcYDvQ1ArgmnMY/BjCTTeA1XeM8VHaxHxT2IzVcMmdcVH knN57pEwLIOQ/FUytgA9JkrSnfTOO/ZpEu60hNuaYqYew9ffCJXFriMtdYqCxDFYVgRv e54X1zBqfgGNp6GHmeHeL5wXupDq/yM/cgEXEmvG3XIu/CRB1z2/O/qTZeEHeWjugUvn Ft5LoQh2UEiT4dyT5x6Tc3J3OUbeUzejZUl2nBjFL0cVhXW4IdyM1pcwA/5/rkaRIAsK SARg==
X-Gm-Message-State: AOAM53000QOMe7odOzjOio6N6MZPYC9F3D3mHkSoIb8LnQbXU3/mCy0y qpLb+m8E7NGmnbsVcq+6ib6ziYaOISQoFNBoq2A=
X-Google-Smtp-Source: ABdhPJyAOo0ZJNDQL9dLEjyCFBbBOURCXjkIbKug91/y7Waq5NHquUGF/vUNdodFj9UXmygWwleWawHdn2sK6iMoT9A=
X-Received: by 2002:ab0:3043:: with SMTP id x3mr4280105ual.88.1611670390795; Tue, 26 Jan 2021 06:13:10 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it> <CAH48ZfwvBj3abrAEz1uK2UNyMOBAM1q3pH8cOmazn8VBow3ACQ@mail.gmail.com> <adcede1d-a260-7b78-9439-63eb706989e2@tana.it>
In-Reply-To: <adcede1d-a260-7b78-9439-63eb706989e2@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 26 Jan 2021 09:12:57 -0500
Message-ID: <CAH48ZfyOe2PkkAZ5yPqb3wP=WctnRMBLqt2bmyj_p7gd6nmRxQ@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000023722205b9ce41e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/iEdWa3N6Yu_lPJGA0KyZkp5REec>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 26 Jan 2021 14:13:14 -0000

--00000000000023722205b9ce41e3
Content-Type: text/plain; charset="UTF-8"

At some point, an investigator will ask, "which of our systems sent these
messages?"

I know how to search my logs for messages to domain example.com.  I do not
know how to search my logs for messages to domains hosted by
hostingservice.tld.  That is why I would expect SMTP To domain to be useful.

An rua report is not supposed to be substitute for a forensic report,.  All
possible details are not supposed to be presented.  Source IP, SMTP
MailFrom domain, and SPF status should be sufficient to identify the
organization responsible for the last hop.  Why is additional mailflow data
necessary?

The best mail flow data would be to report the entire Received chain, but
it would cause too much disaggregation.

On Tue, Jan 26, 2021, 7:50 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Tue 26/Jan/2021 13:02:46 +0100 Douglas Foster wrote:
> > DKIM Scopes
> > I have not heard a compelling argument to require information about
> > authentication tests that are unrelated to alignment testing.    For
> DKIM
> > specifically, I think one scope should be sufficient, on this hierarchy:
> >
> > - The best-aligned scope that verified, or
> > - the best-aligned scope that failed verification, or
> > - a no-signature result otherwise.
> >
> > Anything more complex imposes a gratuitous data collection burden on the
> > reporting domain and reduces aggregation significantly.   On the
> technical
> > side, it has already been noted that variable-length lists are
> particularly
> > problematic for calculating aggregates.
>
>
> Let me attach an HTML rendering of a report I received today, so we can
> talk
> about something real.
>
> Lines with IP 4.31.198.44 bear a ietf.org identifier.  I see no reason to
> remove it.  It is useful for understanding the mailflow, which is what
> DMARC
> reporting is designed to do.
>
>
> > Aggregation Controls
> >
> > We have discussed whether the target domain should be included in the
> > report.  I understand that doing so is not reasonable for the large
> hosting
> > services.   On the other hand, including the target domain would be a
> > trivial matter for smaller operations, and I think it would be valuable
> for
> > some research.    Similarly, DKIM scopes are known to be useful for most
> > investigations, but John has already observed that proliferation of DKIM
> > scopes can be used to force disaggregation down to the individual
> recipient
> > level.
>
>
> Even if this is a small example, learning the disaggregated, or even
> individual
> recipients does not help my understanding.  Authentication is obviously
> conditioned by how the Mediator treats my messages.
>
> I expect that Fastmail Pty Ltd carries out SPF and DKIM validation using
> the
> same algorithm, irrespective of the recipient.  That is what I, as a
> sender, am
> interested in.  Splitting the report in 66 lines wouldn't tell me anything
> more, it would just consume more eyeballs.  And is useless for people who
> sum
> up all reports and just look at the totals.  In any case, I cannot verify
> if
> the messages I didn't send directly are real.
>
> If a multi-domain host allows personalized validation algorithms for some
> domains, I'd expect they send separated aggregate reports, if any.
>
>
> Best
> Ale
> --
>
>

--00000000000023722205b9ce41e3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">At some point, an investigator will ask, &quot;which of o=
ur systems sent these messages?&quot;<div dir=3D"auto"><br></div><div dir=
=3D"auto">I know how to search my logs for messages to domain <a href=3D"ht=
tp://example.com" target=3D"_blank" rel=3D"noreferrer">example.com</a>.=C2=
=A0 I do not know how to search my logs for messages to domains hosted by h=
ostingservice.tld.=C2=A0 That is why I would expect SMTP To domain to be us=
eful.</div><div dir=3D"auto"><br></div><div dir=3D"auto">An rua report is n=
ot supposed to be substitute for a forensic report,.=C2=A0 All possible det=
ails are not supposed to be presented.=C2=A0 Source IP, SMTP MailFrom domai=
n, and SPF status should be sufficient to identify the organization respons=
ible for the last hop.=C2=A0 Why is additional mailflow data necessary?</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">The best mail flow data wou=
ld be to report the entire Received chain, but it would cause too much disa=
ggregation.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Tue, Jan 26, 2021, 7:50 AM Alessandro Vesely &lt;<a hre=
f=3D"mailto:vesely@tana.it" target=3D"_blank" rel=3D"noreferrer">vesely@tan=
a.it</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue 26/Jan/2=
021 13:02:46 +0100 Douglas Foster wrote:<br>
&gt; DKIM Scopes<br>
&gt; I have not heard a compelling argument=C2=A0to require information abo=
ut <br>
&gt; authentication tests that are unrelated to alignment testing.=C2=A0 =
=C2=A0 For DKIM <br>
&gt; specifically, I think one scope should be sufficient, on this hierarch=
y:<br>
&gt; <br>
&gt; - The best-aligned scope that verified, or<br>
&gt; - the best-aligned scope that failed verification, or<br>
&gt; - a no-signature result otherwise.<br>
&gt; <br>
&gt; Anything more complex imposes a gratuitous data collection burden on t=
he <br>
&gt; reporting domain and reduces aggregation significantly.=C2=A0 =C2=A0On=
 the technical <br>
&gt; side, it has already been noted that variable-length lists are particu=
larly <br>
&gt; problematic for calculating aggregates.<br>
<br>
<br>
Let me attach an HTML rendering of a report I received today, so we can tal=
k <br>
about something real.<br>
<br>
Lines with IP 4.31.198.44 bear a <a href=3D"http://ietf.org" rel=3D"norefer=
rer noreferrer noreferrer" target=3D"_blank">ietf.org</a> identifier.=C2=A0=
 I see no reason to <br>
remove it.=C2=A0 It is useful for understanding the mailflow, which is what=
 DMARC <br>
reporting is designed to do.<br>
<br>
<br>
&gt; Aggregation Controls<br>
&gt; <br>
&gt; We have discussed whether the target domain should be included in the<=
br>
&gt; report.=C2=A0 I understand that doing so is not reasonable for the lar=
ge hosting<br>
&gt; services.=C2=A0 =C2=A0On the other hand, including the target domain w=
ould be a<br>
&gt; trivial matter for smaller operations, and I think it would be valuabl=
e for<br>
&gt; some research.=C2=A0 =C2=A0 Similarly, DKIM scopes are known to be use=
ful for most<br>
&gt; investigations, but John has already observed that proliferation of DK=
IM<br>
&gt; scopes can be used to force disaggregation down to the individual reci=
pient<br>
&gt; level.<br>
<br>
<br>
Even if this is a small example, learning the disaggregated, or even indivi=
dual <br>
recipients does not help my understanding.=C2=A0 Authentication is obviousl=
y <br>
conditioned by how the Mediator treats my messages.<br>
<br>
I expect that Fastmail Pty Ltd carries out SPF and DKIM validation using th=
e <br>
same algorithm, irrespective of the recipient.=C2=A0 That is what I, as a s=
ender, am <br>
interested in.=C2=A0 Splitting the report in 66 lines wouldn&#39;t tell me =
anything <br>
more, it would just consume more eyeballs.=C2=A0 And is useless for people =
who sum <br>
up all reports and just look at the totals.=C2=A0 In any case, I cannot ver=
ify if <br>
the messages I didn&#39;t send directly are real.<br>
<br>
If a multi-domain host allows personalized validation algorithms for some <=
br>
domains, I&#39;d expect they send separated aggregate reports, if any.<br>
<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
</blockquote></div>

--00000000000023722205b9ce41e3--


From nobody Tue Jan 26 08:47:58 2021
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 188293A0A63 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 08:47:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 gyY_-Qlzo-0f for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 08:47:55 -0800 (PST)
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 24FAB3A0A4C for <dmarc@ietf.org>; Tue, 26 Jan 2021 08:47:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611679672; bh=liNs2TtN2Aod49sRH9uuXPCrnYQ7wZITOMvl5eneQ0w=; l=2682; h=To:References:From:Date:In-Reply-To; b=Bg+FvQ85UhSmVt+SqRhMv4Dxsl95szOMF4YxNSePCkGsPmRvaVR6tUIvOe6jLkNvy sLeSAWGNml1rb1vh3qhEc10FQ970xOsXCioAJz20nCgs9k9Vr67ixlzGHG8/9ki6P0 Hh+IJPL8AaUig8BtBFbtvf1+0F9wmzOnr2U60eGlEk8ZqUumQ15j7ILOgWNyj
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC028.00000000601047B8.00006497; Tue, 26 Jan 2021 17:47:52 +0100
To: dmarc@ietf.org
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1627293.fjaifilARp@zini-1880> <4563d5ac-f481-5af2-100d-4338f67c6da5@tana.it> <1859075.lZWC7Mh21l@zini-1880>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <3ed1bd47-43e9-3260-b2fe-567c967eede2@tana.it>
Date: Tue, 26 Jan 2021 17:47:51 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <1859075.lZWC7Mh21l@zini-1880>
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/pGx2xFxks5LJGy8avUhpeIsSJiQ>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 26 Jan 2021 16:47:57 -0000

On Tue 26/Jan/2021 14:14:45 +0100 Scott Kitterman wrote:
> On Tuesday, January 26, 2021 6:54:56 AM EST Alessandro Vesely wrote:
>> On Mon 25/Jan/2021 22:35:09 +0100 Scott Kitterman wrote:
>>> On Monday, January 25, 2021 4:04:33 PM EST Todd Herr wrote:
>>>> May I propose that the section labeled "SPF-Authenticated Identifiers" be
>>>> rewritten as follows:
>>>> 
>>>> [...]
>>>> 
>>>>    The reader should note that SPF alignment checks in DMARC rely solely
>>>>    on the RFC5321.MailFrom domain. This differs from section 2.3 of
>>>>    [@!RFC7208], which recommends that SPF checks be done on not only the
>>>>    "MAIL FROM" but also on a separate check of the "HELO" identity. >
>>> 
>>> I think this is fine, but there is a subtlety to be aware of.
>>> 
>>> If you look at RFC 7208 Section 2.4, when Mail From is null,
>>> postmaster@HELO is the mail from for SPF purposes.  DMARC really can't
>>> change that.
>>> 
>>> As a result, there are cases where Mail From results actually are derived
>>> from HELO and it's unavoidable.
>> 
>> I doubt that SPF filters report envelope-from=postmaster@HELO; more likely
>> they write helo=HELO.  In that case, the paragraph quoted above is
>> deceptive.
>>> I believe the proposed text is clear enough about not using separate HELO
>>> identity results and that's appropriate.
>> 
>> My filter collects SPF results recorded from an upstream SPF filter.  It
>> writes Received-SPF: lines for each identity.  For NDNs, it writes a
>> Received-SPF: for the HELO identity only.  Am I allowed to use that result
>> for DMARC?
> 
> No.  You should only use Mail From results.


So NDNs having only an aligned HELO will never pass DMARC?

And what is a <scope>helo</scope> element in aggregate reports provided for?

The spec says:

          [SPF] can authenticate either the domain that appears in the
    RFC5321.MailFrom (MAIL FROM) portion of [SMTP] or the RFC5321.EHLO/
    HELO domain, or both.

And then:

    In relaxed mode, the [SPF]-authenticated domain and RFC5322.From
    domain must have the same Organizational Domain.  In strict mode,
    only an exact DNS domain match is considered to produce Identifier
    Alignment.

So, consider the following message without DKIM signatures:

HELO example.org
MAIL FROM:<user@example.com>

Received-SPF: pass (domain example.org
   designates 192.0.2.1 as permitted sender)
   identity=helo; helo=example.org;
Received-SPF: fail (domain of user@example.com
   denies 192.0.2.1 as permitted sender)
   identity=mailfrom; envelope-from="user@example.com";
Subject: Not using a mail client for this example
From: different-user@example.org

Does it pass DMARC?

Best
Ale
-- 






















From nobody Tue Jan 26 09:01:21 2021
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 120A33A0B05 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 OhHmJqfnGaR8 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:01:18 -0800 (PST)
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 3EA883A0D04 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:01:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611680471; bh=L0adpvIS0QNhf4f2uJQ93d3OieLS4heLoj+Ch9vbER4=; l=1376; h=To:References:From:Date:In-Reply-To; b=Ad7gnuhW6MIDqVfbZw2JLPusTtes48B+6qthTNSfj1p5nM81CmLphXQl5rwW+rdNW cuEWqnmUlehh/QLhTdz3c8ivGu5DOAYEWxCuiseyc7hMmOg6SYgtSPJdxtnOfG0my4 NFO8t+3K2cGo8oFbJH/3uxGPyVr05i5pp5Lu78CngBR37503gcd7U/ZPBsNlQ
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC07E.0000000060104AD6.00006638; Tue, 26 Jan 2021 18:01:10 +0100
To: dmarc@ietf.org
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it> <CAH48ZfwvBj3abrAEz1uK2UNyMOBAM1q3pH8cOmazn8VBow3ACQ@mail.gmail.com> <adcede1d-a260-7b78-9439-63eb706989e2@tana.it> <CAH48ZfyOe2PkkAZ5yPqb3wP=WctnRMBLqt2bmyj_p7gd6nmRxQ@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <5d1a5c1f-99a5-37ac-4177-a995c71c4e42@tana.it>
Date: Tue, 26 Jan 2021 18:01:10 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfyOe2PkkAZ5yPqb3wP=WctnRMBLqt2bmyj_p7gd6nmRxQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Y780zwr-3rx1vDZAbgbqwNmH1cc>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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, 26 Jan 2021 17:01:20 -0000

On Tue 26/Jan/2021 15:12:57 +0100 Douglas Foster wrote:
> At some point, an investigator will ask, "which of our systems sent these 
> messages?"


Possibly none.  In that case this is either an abuse or a forward.  Or maybe 
the report generator lies.


> I know how to search my logs for messages to domain example.com I do not
> know how to search my logs for messages to domains hosted by
> hostingservice.tld.  That is why I would expect SMTP To domain to be
> useful.

A smart relay can put together in the same message several RCPT commands with 
different domains having the same MX.


> An rua report is not supposed to be substitute for a forensic report.  All 
> possible details are not supposed to be presented.  Source IP, SMTP MailFrom 
> domain, and SPF status should be sufficient to identify the organization 
> responsible for the last hop.  Why is additional mailflow data necessary?


In case of forwarding, the last hop is likely not to be aligned.  Previously in 
this thread you said reporting aligned identifiers only would suffice.  Aligned 
and last hop don't necessarily match.


> The best mail flow data would be to report the entire Received chain, but it 
> would cause too much disaggregation.


If every receiver generated aggregate reports, senders would get the whole 
chain, in different reports.


Best
Ale
-- 





















From nobody Tue Jan 26 09:16:44 2021
Return-Path: <johnl@taugh.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 AC8F43A0B8F for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=PV/XMWJF; dkim=pass (2048-bit key) header.d=taugh.com header.b=M1kxiUa6
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 yKNTYStkVJ3l for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:16:41 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 F16913A0B59 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:16:40 -0800 (PST)
Received: (qmail 68267 invoked from network); 26 Jan 2021 17:16:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=10aa9.60104e76.k2101; bh=FVTtN9V3WzHugwX7QGmguxfAVH/u1eFfR/za1sfdWic=; b=PV/XMWJFlvNX5BcR7Kg1Vb05FFYegVYSTtGPfq/eW3BP4zd5rriRomh7tCLtR3QeIfyTJxMfxVtBPMU7TsPnOhSpBj6xbkLZEGWMnekPGcNyVub/v95WdR6NLO89bYwdVy7apFbyEAue7j0QDhLE3BpDOzC7bRpZhi+ujbPGJVq5ZDOI5m/fVgHMNiw3Pe0Eux+bNtGfwFm2JqSSaNSeCkRk8TgQLzrh6b/wRQOUzyuqwvM/ws6ACXPldl9inDbkvjrxt/C1v8mCxNo8N+VQSPEP0DMHAyRF52RuRdg+qXy56C8m4iL3Hfyo/gqh8fcGs77RjhGCvC6SRdrn/G5WRQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=10aa9.60104e76.k2101; bh=FVTtN9V3WzHugwX7QGmguxfAVH/u1eFfR/za1sfdWic=; b=M1kxiUa6gV/GSKM8LrnK4SniMyDOvYtJG26PN0UnthL3xLM2jZNo8B4Io9+VC4mFA0jzHDdvT75LFphbHnN05trCWQW/1+w1L6B8TnlaxpfJyNHYvFUNP21NLZ5UMgf5jx8QyXZ/rTauKLlxacqDJEZ1XvKd2s1B3f83P71BY4LCpx1v3LjehbIGoOAe3YgqeY9Ba2VIYKmCz4EkuA57EvwE0lhk7GZwqL0y34CBJptpcOP2Jc0RX4NTSf9xkLY8s9rUv7mNaqZ0pf5kcV3fhGD7N+HZk7q7x912ArD7nyHRgACrXWyPQfRL+JGbGfODD8ib8B01uyABnCcg2QtQRg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 26 Jan 2021 17:16:38 -0000
Received: by ary.qy (Postfix, from userid 501) id B32896C1D8F8; Tue, 26 Jan 2021 12:16:37 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 2548A6C1D8DA; Tue, 26 Jan 2021 12:16:37 -0500 (EST)
Date: 26 Jan 2021 12:16:37 -0500
Message-ID: <bbff75e7-9580-cd37-da2-e797a53859f3@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <5749790e-c305-b77d-a2f7-94c30579aa4e@tana.it>
References: <20210125212225.9045B6C14E41@ary.qy> <5749790e-c305-b77d-a2f7-94c30579aa4e@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/16cRB5LQeJErAdoYAVoiIrIdKNM>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 26 Jan 2021 17:16:43 -0000

On Tue, 26 Jan 2021, Alessandro Vesely wrote:
>>>>> Won't we put a DKIM-Signature: in the http: header?

>> Sheesh.  That isn't mission creep, it's mission gallop.
> The spec can be commissioned to a narrowly focused WG (like dcrup).

Really, no.  It's something we might think about on its own merits some 
other time, but its absurd to try to do it as a detour from DMARC.

>> If you want a domain identity (even though in this case it provides
>> nothing useful), what's wrong with a client cert? They exist, they
>> work, they have software support everywhere.
>
> Even if you can deduce a From: email address after the Subject Alt Name, you 
> cannot reliably associate it to an organizational domain.

Sorry, that makes no sense at all.  The cert has a domain name, or a bunch 
of domain names.  You can do exactly as much or as little with those 
domain names as you can with the domain in an e-mail From: header.  Keep 
in mind, of course, that none of those domains have any connection at all 
with the contents of an aggregate report, no matter how it is delivered.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Tue Jan 26 09:23:51 2021
Return-Path: <superuser@gmail.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 A3E0D3A0BBC for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 fGbMcXiLwH7L for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:23:48 -0800 (PST)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 880663A0BB8 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:23:48 -0800 (PST)
Received: by mail-vs1-xe35.google.com with SMTP id n18so9405524vsa.12 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:23:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=v4BtxSnBWG2MXxBJPQXeNIOG5lgorkfKCqswbFc72rI=; b=DpGV50PWAi4MnJIIR9efqwYf5qNync6zPVkCFUP56Gr//Sray8BBee+MnV9LTxIdWW U69aZ4a4gh+HVHJEsKzGveQs7DwM2cCInj4HdTTjAGkW6ibi0pnz2Pq04YiPuJ4U2+I3 75pGvf8NBI/cl8pJllyZzXFscohyDtt9pHT/huHTQFKGlIrXn1JuOVa4MjFJ5LsL7o+l oy2I0kWNUQqcmrhVrfixXQm5jM1CPDBrnZTSqtTC/XZf05Xobk16q86XmhOGCbIpzEc0 RFCJnGh5JA1hcy1xdntYFxHBicd9mK9EpSEYoofqTYhT1XjcborbIqA3CmLOCM5wmH5Y kzJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v4BtxSnBWG2MXxBJPQXeNIOG5lgorkfKCqswbFc72rI=; b=Sa1z/heqSh1elziyygLEwGy+Y1KKy3xueZ8/QWF3HzYduRxd7Dbf/Os+kV0bKsXzoA lzEpQ/4h+Mtq3ziV/Axh8Srs5TU9B+6aR/awu93Jnb4lI+5Nmepwi0vSu63YZtjINKYw trJPh2S282BeEWgeVuCxV75tvBrykUVVS0j4Q9c7x6ngF+RtoPtPlf2VlIa31V0wWp/m ItA81kgfK/k8tVcNAWP3U9mfxdaBkPqsZBROisw3+pL4wljARlOzzYdUrxU0lM+2/9x2 iGXBfGxtHZ3ahRnuiD3wSsx4ykXKgcD8OQ2PLvcqPwxPILZF2M6YFaT8TK6HQpMW7njG 7iiQ==
X-Gm-Message-State: AOAM5301ynCnXQUJVcBWyQ3U4IB9sYZFNgvc9xv8FcQSWMNjobQ87qmY 5AOse95Aw93NrsygiJBG4ILLrnv+7Gf7BK9ZUvmkEZ/R8AY=
X-Google-Smtp-Source: ABdhPJy07HJf+B1ThpENgXcTJBRqegLzhMts8YpepDLHxXlOsTl7dtWv9kQd0ptEsZ+Dyznw8rP31S/od0bQmVy40/4=
X-Received: by 2002:a05:6102:808:: with SMTP id g8mr5528318vsb.0.1611681827315;  Tue, 26 Jan 2021 09:23:47 -0800 (PST)
MIME-Version: 1.0
References: <20210125212225.9045B6C14E41@ary.qy> <5749790e-c305-b77d-a2f7-94c30579aa4e@tana.it> <bbff75e7-9580-cd37-da2-e797a53859f3@taugh.com>
In-Reply-To: <bbff75e7-9580-cd37-da2-e797a53859f3@taugh.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 26 Jan 2021 09:23:35 -0800
Message-ID: <CAL0qLwbPNw-LaCJPUBNZk_ZNZ76bNTzb+7OHBWeiYsYyZQJZxA@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: Alessandro Vesely <vesely@tana.it>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cee2bc05b9d0ea04"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qRowKcYqh-LvIkV0mITmFNDkpbk>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 26 Jan 2021 17:23:50 -0000

--000000000000cee2bc05b9d0ea04
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 26, 2021 at 9:16 AM John R Levine <johnl@taugh.com> wrote:

> >> Sheesh.  That isn't mission creep, it's mission gallop.
> > The spec can be commissioned to a narrowly focused WG (like dcrup).
>
> Really, no.  It's something we might think about on its own merits some
> other time, but its absurd to try to do it as a detour from DMARC.
>

+1.  I don't see why we wouldn't just recharter this group (if that would
even be necessary) to do it.  The right audience is already here.

-MSK

--000000000000cee2bc05b9d0ea04
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 26, 2021 at 9:16 AM John R Le=
vine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:<=
br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">&gt;&gt; Sheesh.=C2=A0 That isn&#39;t mission creep, it&#39;s mi=
ssion gallop.<br>
&gt; The spec can be commissioned to a narrowly focused WG (like dcrup).<br=
>
<br>
Really, no.=C2=A0 It&#39;s something we might think about on its own merits=
 some <br>
other time, but its absurd to try to do it as a detour from DMARC.<br></blo=
ckquote><div><br></div><div>+1.=C2=A0 I don&#39;t see why we wouldn&#39;t j=
ust recharter this group (if that would even be necessary) to do it.=C2=A0 =
The right audience is already here.</div><div><br></div><div>-MSK<br></div>=
</div></div>

--000000000000cee2bc05b9d0ea04--


From nobody Tue Jan 26 09:24:59 2021
Return-Path: <mike@fresheez.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 9F6B83A0BC5 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 zt5L7jHb6XIU for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:24:56 -0800 (PST)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 997263A0BBC for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:24:56 -0800 (PST)
Received: by mail-pg1-x530.google.com with SMTP id t25so3930257pga.2 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:24:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=IIRnw5ra66e53xqPodx0NeItkzzFlCe1E9BLMFBb5hA=; b=CHwugga7VbmK9uIqoYkAtbUR1MWcLCQVVNuFwgyseno1d+7RRKRhHqXdPYZ+P4fs8g YrjQTDRgB33jAup9JjejeG9PmOlz+q4rXLGbIxsk5xzLbhqbOjdM4jaTBmugHoY8Srf0 kWUhMBbbSlP1rYb+yVYpQ/rJ9J2oKOCcbK63YVyn/3r4d0lT/RtEZojcQ/CNzcOnuKh9 KIW12DxOwDDFrvwmS7x+8sCvDMR3sM3cXXaS9RL6xVgIc9ELjGYp08CUhZBvbEjZgXd1 PkX+fgSrVmPwDEL0+LVSX5iJxwVKwqobzzYUVCmviwWgqPEECxlfEV6Pc5sGP6LD4W8k DvmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=IIRnw5ra66e53xqPodx0NeItkzzFlCe1E9BLMFBb5hA=; b=c2h+XudsEh615J7WeRP9SFpt5oKOyUaoh7Zw0Ebgca5VTTLuHXeWCmrw/uCHvbJVea v/ax4uN40Pd7cHjzgpEEfz38nwGRVaFkYB8Ar2Roa7HDI4YeiPXRa324JAgCZA6790/B djAYKLUTHRnOqmNwyfBiyWl81AxolC+2t88Jtt7eWvNDe16fRucATOe5N5AgEHuWnuCS E+W2PJD08Wx/ATf79ed1FhYlq9nzHlofGs9OIIc719g+E/qUkaPAK/4sA9/ppKyoEWoF isI68Jdudx6xtLl6UNjzHMSN/UUt0tOAg8CT7rhuVWptYDRvIKAr5POpXlVy2UctF8CA MBsg==
X-Gm-Message-State: AOAM530u+zP76rjerPXAVJ6w10a/XgmP2FmiPqcrUDfr71uxLhbCUSo3 7NM92gJaS4Cn4l/Cp/ynrH6O7KODzCQlVw==
X-Google-Smtp-Source: ABdhPJyJM6kphnnYACF0vlT5h0ioEZ0NJSzZvDuCiaV2OIHLILy/UWiLuGb866k2AtXiY+37rwv7xg==
X-Received: by 2002:a63:703:: with SMTP id 3mr6543231pgh.272.1611681895551; Tue, 26 Jan 2021 09:24:55 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id s73sm20205783pgc.46.2021.01.26.09.24.54 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 09:24:54 -0800 (PST)
To: "dmarc@ietf.org" <dmarc@ietf.org>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com>
Date: Tue, 26 Jan 2021 09:24:53 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/8e588uxX2eOmG5VQhbACUteQLNo>
Subject: [dmarc-ietf] attack on reports
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, 26 Jan 2021 17:24:58 -0000

This is different than yesterday. From what I can tell there is no 
identifying information of the original message like message-id in the 
report xml. If i'm wrong, please point me to it. Since the object of the 
reports is to have confidence so that I can set a p=reject policy, all 
an attacker needs to do is bombard $LARGEPROVIDER with bogus messages 
purportedly from my domain to make me not want to change over to reject 
for fear of large providers dumping legitimate email from my domain. 
This could be somewhat mitigated if you know all of the IP addresses 
that send for you domain, but that could be difficult with the use of 
outsourced email, etc and shouldn't be a requirement. Addition of the 
message-id would allow me to cross check from my logs, say, that it was 
a legitimate message from my domain or not. There may be other ways to 
solve this, but that is one.

Mike


From nobody Tue Jan 26 09:27:11 2021
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 A55143A0BDE for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 tuqalT1SAkfs for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:27:09 -0800 (PST)
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 19E963A0BC5 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:27:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611682027; bh=AEEOAyh9sqRyYZH72ZkzxtCAbXOO2uiry2jEIlbCWvA=; l=842; h=To:Cc:References:From:Date:In-Reply-To; b=DDhcS70c7+/MKAUFSTaPJcj1OfrhLuotjnHBK2dnyUzYCn2VKFgtywR8VZwZYZWYx sY0xDxmHk4tAWu+lKeOcisaq3keoKfxNyt1n6N6bB26lEMM0MkBNRjO3LST7/iofNX F9RpOV4MFvD3WgGW2uW86ITwgWmoFEhQUTA8EM+fNnCz55cabdGtOG6fY9miy
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Original-Cc: IETF DMARC WG <dmarc@ietf.org>
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.00000000601050EB.00006964; Tue, 26 Jan 2021 18:27:07 +0100
To: "Murray S. Kucherawy" <superuser@gmail.com>, John R Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <20210125212225.9045B6C14E41@ary.qy> <5749790e-c305-b77d-a2f7-94c30579aa4e@tana.it> <bbff75e7-9580-cd37-da2-e797a53859f3@taugh.com> <CAL0qLwbPNw-LaCJPUBNZk_ZNZ76bNTzb+7OHBWeiYsYyZQJZxA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <e1c50fe3-7a80-62e7-ae9d-6347f50d389e@tana.it>
Date: Tue, 26 Jan 2021 18:27:05 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbPNw-LaCJPUBNZk_ZNZ76bNTzb+7OHBWeiYsYyZQJZxA@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/G4JgW__IJaM3euKpl6eHJ409nZM>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 26 Jan 2021 17:27:11 -0000

On Tue 26/Jan/2021 18:23:35 +0100 Murray S. Kucherawy wrote:
> On Tue, Jan 26, 2021 at 9:16 AM John R Levine <johnl@taugh.com> wrote:
> 
>>>> Sheesh.  That isn't mission creep, it's mission gallop.
>>> The spec can be commissioned to a narrowly focused WG (like dcrup).
>>
>> Really, no.  It's something we might think about on its own merits some
>> other time, but its absurd to try to do it as a detour from DMARC.
> 
> +1.  I don't see why we wouldn't just recharter this group (if that would
> even be necessary) to do it.  The right audience is already here.


Doing it now might overload the WG.  If DKIM for binary has its own merit, we 
can just hypothesize we'll do.  Meanwhile we can mention it and suggest to use 
it for https: when it comes, if ever.  After all, that's what RFC 2045 does 
with "binary".


Best
Ale
-- 















From nobody Tue Jan 26 09:28:39 2021
Return-Path: <mike@fresheez.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 C290D3A0BF7 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:28:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 bX3izS2BQ2yt for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:28:36 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE40D3A0BE9 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:28:36 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id q131so10805984pfq.10 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:28:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=95gFZSwLpPE7ywiKaZxuFGxt3KWrLOT+GSmw7KCELoo=; b=PxtovwgvvNJWx0d0y5SsIs/eeD6cXShbXNAsWIPeNZlrO4Ie/HFIBnRlBvLfV76lHe 2+d2ByWoELD0xtXsyrB3otoK6Ow7w08fTCPYEOcHrvSNBe/dW6ejM+6ij74MS5NsICsX zzIEjvxfZ0uPKZl5OLMzLoMMWAGFE1e6+VbCYo/mq7OtRguyDTS9kuR6EeIlOhCcd6lz Zkqhwe/ez0GyrwtPqB4Om8IytC0ZOzDPBSSjk1ig/R958NXd5uNYmAZqwsqRBym8Q+eW Udl3Wdo9/1PozkBBcQMWKKzYy+EfwyJH/6aGdiS5Pj0kuCqrwogFVEd6R5cPOEx0OC9f Xt7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=95gFZSwLpPE7ywiKaZxuFGxt3KWrLOT+GSmw7KCELoo=; b=tak2PO8+qpNEQR82uQO1XwNumZAIsmJDTBaXiHrJrm9/49ja7z5LX78Nw0S2K18rbc CdL/EPCwO9MmBjKAv+sk0cZpchS8lz0jP+OnNjflPsU8eTMgD2jyuMcPcStz+ZwK0X8H FvIWq9qk6bJHYyrcOyc/d3TRDzHlnyQcmkLNt2lpZpu4F9X6GLM7vUZuV5qih3OyGPhL HIIwHqy5zitEoaRku4T7VfaryenMsuPVg3YHBTUj+sstTYoJt1LD3oFvJ/70Hi8nXnf8 zQHPBhVmyPKcL/IvNEATSTxswUWHf1GFSt9G0O0aWT9minMp9A9IDaRPC0O0fAu94fpJ kHaQ==
X-Gm-Message-State: AOAM5328RRRuTD9fPQjerxdzriPUtLqb7utBnKkyLGRx05wXjbBnwTlA l8csPe/gOuTe0E1UcvXGv0RzWum1VFzYtw==
X-Google-Smtp-Source: ABdhPJzZ9J5doC8RbmFO8rMsc3fRBSbZAdAwMeu89g2cYi9FzEce27S5JoX+19xugRO8akQ8Ao72pQ==
X-Received: by 2002:a63:a312:: with SMTP id s18mr1128372pge.229.1611682115846;  Tue, 26 Jan 2021 09:28:35 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id n7sm20112129pfn.141.2021.01.26.09.28.34 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 09:28:35 -0800 (PST)
To: dmarc@ietf.org
References: <20210125212225.9045B6C14E41@ary.qy> <5749790e-c305-b77d-a2f7-94c30579aa4e@tana.it> <bbff75e7-9580-cd37-da2-e797a53859f3@taugh.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <71efb988-6301-3189-0340-6898a7676cf3@mtcc.com>
Date: Tue, 26 Jan 2021 09:28:33 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <bbff75e7-9580-cd37-da2-e797a53859f3@taugh.com>
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/YNp_ODBrzefPAASX9TmrIRtYMQI>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 26 Jan 2021 17:28:38 -0000

On 1/26/21 9:16 AM, John R Levine wrote:
>
>> Even if you can deduce a From: email address after the Subject Alt 
>> Name, you cannot reliably associate it to an organizational domain.
>
> Sorry, that makes no sense at all.  The cert has a domain name, or a 
> bunch of domain names.  You can do exactly as much or as little with 
> those domain names as you can with the domain in an e-mail From: 
> header.  Keep in mind, of course, that none of those domains have any 
> connection at all with the contents of an aggregate report, no matter 
> how it is delivered.
>

Use of client certs is a non-starter. The use of http here is 
problematic and getting more so. This entire issue should just be junked.

Mike


From nobody Tue Jan 26 09:37:55 2021
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 3412C3A0C59 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:37:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 AYQ8XtEMyltQ for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:37:53 -0800 (PST)
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 246B03A0C55 for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:37:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611682671; bh=lp7pdXcjFt5T63zVZ74TP6zKRPBNUz5iE3TeOXBhmS8=; l=1394; h=To:References:From:Date:In-Reply-To; b=BXv4S1dzlB8vKcfvwcDvi5KQDL+SXiZ+H5WaY5DtHn4qpSJzTEzYFEjHE1M+uyoiY fKGtZ7Ccx4JOCDsAMLyf5xzrG6m+baUMBLaK10Sc8AeXA/xFlYG3en/dDc6F4PeUwL tV1Ah5cqMTt44sNt+H0g9JGvxnlFB8aXJXpd6yrb0fsvHRZJ3rcHjZDiWs9mU
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.000000006010536F.00006A97; Tue, 26 Jan 2021 18:37:51 +0100
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it>
Date: Tue, 26 Jan 2021 18:37:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.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/KzbI3hGzX4ravBEEBXigNfEDV9M>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 17:37:54 -0000

On Tue 26/Jan/2021 18:24:53 +0100 Michael Thomas wrote:
> 
> This is different than yesterday. From what I can tell there is no identifying 
> information of the original message like message-id in the report xml. If i'm 
> wrong, please point me to it.


With a record for each message it wouldn't be an *aggregate* report.

In addition, if I recover that message from the log, I might find no 
relationship with the reporting domain or the reported source IP.  That is to 
say, I won't be able to deduce if the report is fake or real.


> Since the object of the reports is to have confidence so that I can set a
> p=reject policy, all an attacker needs to do is bombard $LARGEPROVIDER with
> bogus messages purportedly from my domain to make me not want to change over
> to reject for fear of large providers dumping legitimate email from my
> domain. This could be somewhat mitigated if you know all of the IP addresses
> that send for you domain, but that could be difficult with the use of
> outsourced email, etc and shouldn't be a requirement.

$LARGEPROVIDER must use a reputation system to evaluate both the report 
generator domain and the reported IP numbers.


> Addition of the message-id would allow me to cross check from my logs, say,
> that it was a legitimate message from my domain or not.

Not if you take forwarding into account.


Best
Ale
-- 

















From nobody Tue Jan 26 09:38:06 2021
Return-Path: <johnl@taugh.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 ADD753A0D60 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:38:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=LyXqLczA; dkim=pass (2048-bit key) header.d=taugh.com header.b=jxzJr2ai
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 I9AxJFcwwarf for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 09:38:01 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 E39C13A0CFE for <dmarc@ietf.org>; Tue, 26 Jan 2021 09:38:00 -0800 (PST)
Received: (qmail 74901 invoked from network); 26 Jan 2021 17:37:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=12490.60105376.k2101; bh=73YXFIW0MfxOm5+hZHl+QZTgtmXzzvqfFr4eUMOQVwQ=; b=LyXqLczAPV5N+C0BmG12bUHbaQwmTRPNzQ1wYdPAHnXPibgOY6DTQRYzTBO/opdcBnDAMEjSUWIJG8LmQPPsHUYH4DybI6hPpUMehhBjOv+u55GA4Y4FIRJ0CB6tqt5DQlDakzHNkB8Nktph/NPPZ08nZnH6vgpo/q7GPYSMRKLVrR1eQ9uCYzsiy8mnUwFHK1FmCH2zsWgYmL3lW12U8YwrVaz8aZ9YK9ULAFpSICLdDAqTclOCyHL7noEavPIvd36JRnSBvg3NmddUjWZe7IbbuUo4hpA4uiski8BpYWw+DSlsGgPngqbj9KNr1MYTWqdEEI6SCWw0z0lOD9uzOw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=12490.60105376.k2101; bh=73YXFIW0MfxOm5+hZHl+QZTgtmXzzvqfFr4eUMOQVwQ=; b=jxzJr2ai6LdUqDjSmTq/45h0wHsOoiExz+u8DJ1MxDYJxfoI+P9J2bSse+Ch4OptkniuFnYHtxX3tkIsY6W50BhZruyUkkb2MuOCeVuQVIrOX0ooOwCbmLirh0bHSpXw6zu9/drUlFnA/lYHP8H34pY1r6sjejk9jlHweFB/uZHgOEs5/VjAwp7zylvuNeN0p+TjR34TrgqBBmvF3B2cSOtJabT7RTTvxWGE55KBqzoIl7LF2H3lystFaQ3dlYjQFRxwvF66hAALhdzHF42heQhsv3DJhDP0CP+kscHB0VurYonwzcFfYeFytQqL3X0FEAJy73XngOe7Zn7drX1eFQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 26 Jan 2021 17:37:58 -0000
Received: by ary.qy (Postfix, from userid 501) id 7C48E6C1E067; Tue, 26 Jan 2021 12:37:56 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 21AE36C1E049; Tue, 26 Jan 2021 12:37:56 -0500 (EST)
Date: 26 Jan 2021 12:37:56 -0500
Message-ID: <5dec91c8-fb2a-248e-36a3-59535fa689cf@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>
Cc: "IETF DMARC WG" <dmarc@ietf.org>
In-Reply-To: <e1c50fe3-7a80-62e7-ae9d-6347f50d389e@tana.it>
References: <20210125212225.9045B6C14E41@ary.qy> <5749790e-c305-b77d-a2f7-94c30579aa4e@tana.it> <bbff75e7-9580-cd37-da2-e797a53859f3@taugh.com> <CAL0qLwbPNw-LaCJPUBNZk_ZNZ76bNTzb+7OHBWeiYsYyZQJZxA@mail.gmail.com> <e1c50fe3-7a80-62e7-ae9d-6347f50d389e@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/2uqe2xlhEcUU6xxO32RDDagXtfo>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 26 Jan 2021 17:38:04 -0000

> Doing it now might overload the WG.  If DKIM for binary has its own merit, we 
> can just hypothesize we'll do.  Meanwhile we can mention it and suggest to 
> use it for https: when it comes, if ever.  After all, that's what RFC 2045 
> does with "binary".

Since client certificates exist and http DKIM signatures do not, that 
doesn't sound like a great plan.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Tue Jan 26 10:00:50 2021
Return-Path: <mike@fresheez.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 721E73A0D05 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 10:00:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 JrVh3Ti2AAWQ for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 10:00:48 -0800 (PST)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59F013A0CFF for <dmarc@ietf.org>; Tue, 26 Jan 2021 10:00:48 -0800 (PST)
Received: by mail-pg1-x534.google.com with SMTP id v19so11918978pgj.12 for <dmarc@ietf.org>; Tue, 26 Jan 2021 10:00:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=aZK7IBz0J+4SpVMvFw+Gioe9HE+rCoqnoBTTY2t8pDw=; b=C0Sl8oYfnjsOpYgyx1r1tO4mc3LIYT5JThRmKynpAPF8IlGMfNgQ8oPo9YLbcFD1ge ZeN/DvDzyo9twa7jrL/y/s4lK/s56iA5YM7bVt3MI4/jnq4BAkIb3XhAKsjUnZrgzzZM pX+yUvbo7df72Qh8cnz3MDtjYP5v1A8RKiE9u00gWMSahNBeO/eN/W9Is0CV0BLxGvid cPMroexpDmC/lIcSgC5N7ImUp0qp2tspTuxXB1KNX0KmM75PK9zSLT8HKNxs3N585d9i H1zhti9nV4yQq2dwK3VTFRJSyWBpRgG6HI4Sgcm+eFV9tYUt49TLLWhtiawJXYHLDYrQ zqzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=aZK7IBz0J+4SpVMvFw+Gioe9HE+rCoqnoBTTY2t8pDw=; b=IH0J4fR1x4j9BBQpWSHq1UJXwQqZKK02Qsix5jg8JM8ADYslMJkjnny56NSNsgmoxj PC9t9ialAR2pbNFo6SngfGmzIMPfR87mNToCI8/Mv/I6rk4+FaCI8mAp1z1y/uHLZQSl UdsVDHHbCAg8Y66UUIhkQJZKCK2ykctN/l1ACZ2vj2XHam3XZOqAEzjf5M3ru/CAUH2R aL1tpugamrkMDq4K3ljCEuMHjpTio5lJv1AumPlTyCIdYdOUB0StTOpstRb9AhdiOOei xyz+qcZ2ObxeVPuPLPKD3B868t0ErkkrU4XubMjwuj5nIXThn4ccI6GZ5OVrC/3rjqYK 64kQ==
X-Gm-Message-State: AOAM532U1K/YuaRPyt1Y5Ip621dk8CucetSwrmfgYfE+RaxO/VOhEF/f bGUfQHDHVq2PJxWsQAeUZofwHeBwJecQUw==
X-Google-Smtp-Source: ABdhPJxSJ0uspUlqU28abB48cYq+C883RNylXHhBKoS8grI4g+H2Q5LptPHxTs2J9tRndkueq73SJQ==
X-Received: by 2002:a62:86c4:0:b029:1b8:131e:540d with SMTP id x187-20020a6286c40000b02901b8131e540dmr6389182pfd.21.1611684046829;  Tue, 26 Jan 2021 10:00:46 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id 78sm15881286pfx.127.2021.01.26.10.00.45 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 10:00:46 -0800 (PST)
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com>
Date: Tue, 26 Jan 2021 10:00:44 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it>
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/UFAa5e0F4K47kGdwE8OAHwZ9EQg>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 18:00:49 -0000

On 1/26/21 9:37 AM, Alessandro Vesely wrote:
> On Tue 26/Jan/2021 18:24:53 +0100 Michael Thomas wrote:
>>
>> This is different than yesterday. From what I can tell there is no 
>> identifying information of the original message like message-id in 
>> the report xml. If i'm wrong, please point me to it.
>
>
> With a record for each message it wouldn't be an *aggregate* report.


 From section 7.2:

"Visibility comes in the form of daily (or more frequent) Mail 
Receiver-originated feedback reports that contain aggregate data on 
message streams relevant to the Domain Owner. This information includes 
data about messages that passed DMARC authentication as well as those 
that did not."

That sure sounds like it's on a message basis to me. How else could the 
reports get to be as big as megabytes?


>
> In addition, if I recover that message from the log, I might find no 
> relationship with the reporting domain or the reported source IP.  
> That is to say, I won't be able to deduce if the report is fake or real.


My main point here is to point out the attack.

Mike


From nobody Tue Jan 26 10:57:15 2021
Return-Path: <todd.herr@valimail.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 7F8F63A0D91 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 10:57:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 m3w1J0CmCYD8 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 10:57:12 -0800 (PST)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96CF43A0D8E for <dmarc@ietf.org>; Tue, 26 Jan 2021 10:57:03 -0800 (PST)
Received: by mail-qk1-x730.google.com with SMTP id r77so16816018qka.12 for <dmarc@ietf.org>; Tue, 26 Jan 2021 10:57:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=fM7hGt7ZxzxMmBk+o2DPyNLojfzd9J5F+ezoOwi2TcY=; b=emsTR7hrXF+OisndJzFMGa7RT5CqxtvySdbpf+EVlgLKSX8+kli8UhjrMf0GPuAP+7 c7Yma59Igj18KlGNqhcy17G/z9+JH98sRYvDwEowYUgYqbA+bJAHv87s/5h4NBbGos1h iTScmzRVrlEuDqGB/9OOkV3nODPmcIpnOs1NkF49nxD4k8Ka0g1PtdBlrG9J3LFAnumK NI/G0vbkVjREMS54vCbPNxXzpeDL8RRvhzl/qS4LUR2yBlukkXxAOgubB7P6WzfY8sJ8 4eVbq+INlCxeo8TDpqEAOnhtRZN9AsCoto55zVDbZCZzfhau7e2yriDd5H87xGryTI0G D/EQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=fM7hGt7ZxzxMmBk+o2DPyNLojfzd9J5F+ezoOwi2TcY=; b=B3TG8sadhBfhQ0xp+bwDJ22FdwyHNc5BuKH2UKIfGY3rkmqHahIXyNn14BIaysXQgX fXNGcJgR1Rn3pSRW7RmztubC1KkIFcyk0lt999IVhOnjWxosRRKUUMCZjG5FtZOqJVkh wdLJm1cQ/Mpy/WJKSNRqPzoRLirl+HD+gRrJPCC7iEJwWR2DLu6er47YZlJdstItMr/H PajH3/mkfhM4JIEkG23ppV25Yz2nmAFDZ7DP32DqbuguKf49GsmhRGQRYLFglh7Thkii REXAenrSPlrmnr29htCASQc/MhjwYnRMvUu9W4Bszaqsrx6/xD+LcCbNbm8MoWvAyg8g /C4g==
X-Gm-Message-State: AOAM533IH/Ia6OGv2XwjtlpQxcgGsfa/kLsEvdGtUZpCO2yk/IGWDoGn pNxI9Rbw3qknpOBNfEyfR1M71C4nLlSxqb102A2UwIHFU1w=
X-Google-Smtp-Source: ABdhPJxjBJiKzGw+W489nausFMuFYQiT1KFVzKfKmps9CrVG1WviBdNGCsdpXgLZ/64b89fJ1nMIQWEAji6CsMVZAzo=
X-Received: by 2002:a05:620a:1fb:: with SMTP id x27mr6924934qkn.456.1611687422328;  Tue, 26 Jan 2021 10:57:02 -0800 (PST)
MIME-Version: 1.0
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com>
In-Reply-To: <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 26 Jan 2021 13:56:46 -0500
Message-ID: <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004c149c05b9d23847"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/hTgEkC59rIQACbqon0jwNN1KmMI>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 18:57:15 -0000

--0000000000004c149c05b9d23847
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 26, 2021 at 1:01 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/26/21 9:37 AM, Alessandro Vesely wrote:
> > On Tue 26/Jan/2021 18:24:53 +0100 Michael Thomas wrote:
> >>
> >> This is different than yesterday. From what I can tell there is no
> >> identifying information of the original message like message-id in
> >> the report xml. If i'm wrong, please point me to it.
> >
> >
> > With a record for each message it wouldn't be an *aggregate* report.
>
>
>  From section 7.2:
>
> "Visibility comes in the form of daily (or more frequent) Mail
> Receiver-originated feedback reports that contain aggregate data on
> message streams relevant to the Domain Owner. This information includes
> data about messages that passed DMARC authentication as well as those
> that did not."
>
> That sure sounds like it's on a message basis to me. How else could the
> reports get to be as big as megabytes?
>

I don't believe they do reach megabytes in size. I wasn't present at the
creation, but I believe that the 10MB size limit was chosen as one to allow
for more than enough headroom for aggregate reports.

Adding message-ids to aggregate reports removes the aggregation feature of
the report, and would be an undue burden both for the report generator and
the report consumer, in my opinion, mostly due to the orders of magnitude
increase in storing the data. For example, where today I can represent
50,000 messages in one row in my data store based on the aggregation of
source IP, policy_evaluated, identifier, and auth_results I would instead
require 50,000 rows to do the same if message-ids were added to the
reports. Aggregate reports aren't used to troubleshoot authentication
failures for individual messages; they're meant to convey information about
whether a sending IP is transmitting messages that generally pass or fail
SPF and DKIM checks. If a source
IP/policy_evaludated/identifier/auth_results tuple shows as failing
authentication checks a high percentage of the time, and the source IP is
known to be one used by the organization, then that mailstream can be
examined and corrected.


>
>
> >
> > In addition, if I recover that message from the log, I might find no
> > relationship with the reporting domain or the reported source IP.
> > That is to say, I won't be able to deduce if the report is fake or real.
>
>
> My main point here is to point out the attack.
>
>
The attack scenario you have described relies on several possible but
perhaps implausible conditions all being true:

1. There exists a domain run by people who are savvy enough to want to
implement DMARC and can consume reports, but don't have a good grasp on
which IPs are likely to be theirs and which aren't, and don't have an
understanding of how to use common tools to figure out whether an IP
address might belong to their provider's ASN or one halfway around the
world, and
2. $LARGEPROVIDER is sophisticated enough to do DMARC validation and
reporting, but not so sophisticated as to notice that the bombardment of
mail generated by the criminal is different from other flows using that
domain, and so therefore won't take action to cut off its acceptance of
that flow in ways that would cause it to not be reported on (i.e., blocking
the source not because of DMARC, but because it's a known spam source, and
so the messages are never accepted nor run through DMARC validation
checks), and
3. There exists a criminal who, given the choice of squeezing through the
eye of a needle by somehow preventing a domain from reaching a p=reject
policy (which isn't always honored, anyway) using this bombardment
technique or driving a truck through the chasm of using cousin domains or
even look-alike domains that include homoglyphs that render them apparently
identical to the target domain (a problem DMARC is not designed to solve)
will choose the more difficult path.

I would think this scenario much more likely if DMARC were at this time a
purely hypothetical exercise. Given that we're years into implementation
already, I'm less confident that the above three conditions all exist at
the same time.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--0000000000004c149c05b9d23847
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 26, 2021 at 1:01 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><br>
On 1/26/21 9:37 AM, Alessandro Vesely wrote:<br>
&gt; On Tue 26/Jan/2021 18:24:53 +0100 Michael Thomas wrote:<br>
&gt;&gt;<br>
&gt;&gt; This is different than yesterday. From what I can tell there is no=
 <br>
&gt;&gt; identifying information of the original message like message-id in=
 <br>
&gt;&gt; the report xml. If i&#39;m wrong, please point me to it.<br>
&gt;<br>
&gt;<br>
&gt; With a record for each message it wouldn&#39;t be an *aggregate* repor=
t.<br>
<br>
<br>
=C2=A0From section 7.2:<br>
<br>
&quot;Visibility comes in the form of daily (or more frequent) Mail <br>
Receiver-originated feedback reports that contain aggregate data on <br>
message streams relevant to the Domain Owner. This information includes <br=
>
data about messages that passed DMARC authentication as well as those <br>
that did not.&quot;<br>
<br>
That sure sounds like it&#39;s on a message basis to me. How else could the=
 <br>
reports get to be as big as megabytes?<br></blockquote><div><br></div><div>=
I don&#39;t believe they do reach megabytes in size. I wasn&#39;t present a=
t the creation, but I believe that the 10MB size limit was chosen as one to=
 allow for more than enough headroom for aggregate reports.</div><div><br><=
/div><div>Adding message-ids to aggregate reports removes the aggregation f=
eature of the report, and would be an undue burden both for the report gene=
rator and the report consumer, in my opinion, mostly due to the orders of m=
agnitude increase in storing the data. For example, where today I can repre=
sent 50,000 messages in one row in my data store based on the aggregation o=
f source IP, policy_evaluated, identifier, and auth_results I would instead=
 require 50,000 rows to do the same if message-ids were added to the report=
s. Aggregate reports aren&#39;t used to troubleshoot authentication failure=
s for individual messages; they&#39;re meant to convey information about wh=
ether a sending IP is transmitting messages that generally pass or fail SPF=
 and DKIM checks. If a source IP/policy_evaludated/identifier/auth_results =
tuple shows as failing authentication checks a high percentage of the time,=
 and the source IP is known to be one used by the organization, then that m=
ailstream can be examined and corrected.</div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">
<br>
<br>
&gt;<br>
&gt; In addition, if I recover that message from the log, I might find no <=
br>
&gt; relationship with the reporting domain or the reported source IP.=C2=
=A0 <br>
&gt; That is to say, I won&#39;t be able to deduce if the report is fake or=
 real.<br>
<br>
<br>
My main point here is to point out the attack.<br>
<br></blockquote><div><br></div><div>The attack scenario you have described=
 relies on several possible but perhaps implausible conditions all being tr=
ue:</div><div><br></div><div>1. There exists a domain run by people who are=
 savvy enough to want to implement DMARC and can consume reports, but don&#=
39;t have a good grasp on which IPs are likely to be theirs and which aren&=
#39;t, and don&#39;t have an understanding of how to use common tools to fi=
gure out whether an IP address might belong to their provider&#39;s ASN or =
one halfway around the world, and</div><div>2. $LARGEPROVIDER is sophistica=
ted enough to do DMARC validation and reporting, but not so sophisticated a=
s to notice that the bombardment of mail generated by the criminal is diffe=
rent from other flows using that domain, and so therefore won&#39;t take ac=
tion to cut off its acceptance of that flow in ways that would cause it to =
not be reported on (i.e., blocking the source not because of DMARC, but bec=
ause it&#39;s a known spam source, and so the messages are never accepted n=
or run through DMARC validation checks), and</div><div>3. There exists a cr=
iminal who, given the choice of squeezing through the eye of a needle by so=
mehow preventing a domain from reaching a p=3Dreject policy (which isn&#39;=
t always honored, anyway) using this bombardment technique or driving a tru=
ck through the chasm of using cousin domains or even look-alike domains tha=
t include homoglyphs that render them apparently identical to the target do=
main (a problem DMARC is not designed to solve) will choose the more diffic=
ult path.</div><div><br></div><div>I would think this scenario much more li=
kely if DMARC were at this time a purely hypothetical exercise. Given that =
we&#39;re years into implementation already, I&#39;m less confident that th=
e above three conditions all exist at the same time.</div></div><div><br></=
div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p dir=3D"ltr" =
style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=
=3D"text-align:left"><span style=3D"vertical-align:baseline;white-space:pre=
-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span style=
=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-famil=
y:Arial"> | Sr. Technical Program Manager</span></div><span style=3D"vertic=
al-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><=
div style=3D"text-align:left"><span style=3D"vertical-align:baseline"><b>e:=
</b></span><span style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.=
herr@valimail.com" target=3D"_blank">todd.herr@valimail.com</a></span></div=
></span><span><div><span><b>p:</b></span><span> 703.220.4153 </span><span><=
/span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:=
Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255=
);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-si=
ze:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;ver=
tical-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleus=
ercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFO=
qe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL=
" style=3D"border: none; height: 40px; width: 177px;"></span></p><p dir=3D"=
ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;fo=
nt-size:small;background-color:rgb(255,255,255);line-height:1.38;margin-top=
:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rg=
b(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font col=
or=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-spac=
e:pre-wrap">This email and all data transmitted with it contains confidenti=
al and/or proprietary information intended solely for the use of individual=
(s) authorized to receive it. If you are not an intended and authorized rec=
ipient you are hereby notified of any use, disclosure, copying or distribut=
ion of the information included in this transmission is prohibited and may =
be unlawful. Please immediately notify the sender by replying to this email=
 and then delete it from your system.</span></font></p></span></div></div>

--0000000000004c149c05b9d23847--


From nobody Tue Jan 26 10:59:13 2021
Return-Path: <mike@fresheez.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 516133A0D8E for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 10:59:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.151
X-Spam-Level: 
X-Spam-Status: No, score=0.151 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 4o_StwCVQUnn for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 10:59:10 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D4FE3A0D44 for <dmarc@ietf.org>; Tue, 26 Jan 2021 10:58:39 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id jx18so2777560pjb.5 for <dmarc@ietf.org>; Tue, 26 Jan 2021 10:58:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=to:from:subject:message-id:date:user-agent:mime-version :content-language; bh=qehqsnVwHThaEWxXUiS5gw4mWhZIzXtwIiVETtABL1c=; b=OsjIUxJX1UzcFnMiiSPZPMLXWCY+dgog3FlQPxWiI7YUu6B3v2JX64hdCqU8rx1Rfo ABHm/YGmC5jjeCgkPacAmhofiCAH0RZwGdKz5S9lmlFFekdgd83eUTeZ3PvJoVT0iugU jW7e5LKQxpjNLGNDc4pAp618v+/T/ikGZVP37jgk80Egkro5UYl1HPVyN39NR/djmqz6 czY12gX1VzH3MCxLMfmqOEV2gPydmBOvPt9bUvf4S/H+k4tzxJ7ox6vvcMrO10s0L5K/ 3/HDQ3Wndx0eXLZT/1shRnUom8zmdGJiMgZeGKZFWcqPVai0NFEB1CfNO7hoCVdcnFtS mXYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language; bh=qehqsnVwHThaEWxXUiS5gw4mWhZIzXtwIiVETtABL1c=; b=j/zmbhUMRegTGDGJ9CTWRa8yYglbhqa7kdun1bwEmuCtRFJoB6SgmEpXagRBaAXJLM 6/9YZUDAancRhaDvGX0voBS8DC6lUljBE/b0dDR/738cAMZ9+q3GlXIJ7Y9+mE54iHqV eBfncerDRB0D8OGR+bREbqnyDEJGgKhN5L2Z+oZNnHk9JuEYCrGqpCI3usA3dPIuivEd cdytr1sUWmNbeHIHCFY46chPZKfu905PskN7W7HUCpveFvWBuioL3NLI5wUuQsll1HVT 55y6mGtWo5x2hdxJw9bShsHgxaIbR+EOZW8ikbB/t7kntlk/FqA5xY3/av7O15iBvWRV ymBA==
X-Gm-Message-State: AOAM533+btnFe6K3jl6lDJCa66Oez+66cSC5poeT2OjjXzMY/sD7F1xF NEZRHXp52Pp08qfve3E5g/2s6id3asJKFA==
X-Google-Smtp-Source: ABdhPJyFtIcFpqH8Pb+dExPRsEZEFkJOeh+0yqcnHfB0kCJVUJUGcdlwL22tRvdBGzXwGiTC1pq1SA==
X-Received: by 2002:a17:902:7207:b029:da:fd0c:521a with SMTP id ba7-20020a1709027207b02900dafd0c521amr7261516plb.45.1611687518671;  Tue, 26 Jan 2021 10:58:38 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id i4sm11256028pfo.40.2021.01.26.10.58.37 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 10:58:38 -0800 (PST)
To: "dmarc@ietf.org" <dmarc@ietf.org>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <71342cc2-9f87-89e4-42f1-1d617ee71f80@mtcc.com>
Date: Tue, 26 Jan 2021 10:58:36 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------7524E8103D99ABF82109734C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/lItL3BGKk3ZFlwMSXhDqK9UnUnQ>
Subject: [dmarc-ietf] nit in section 7.2
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, 26 Jan 2021 18:59:11 -0000

This is a multi-part message in MIME format.
--------------7524E8103D99ABF82109734C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

"The report SHOULD include the following data:"

Normative SHOULD here since very strange because what follows is informational, and why would it be SHOULD in the first place?

It seems to me it ought to be:

"The report includes the following data:"

If there are normative requirements, it seems like it would be better to put it into the XML section itself.
  
Mike


--------------7524E8103D99ABF82109734C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <pre class="newpage">"The report SHOULD include the following data:"

Normative SHOULD here since very strange because what follows is informational, and why would it be SHOULD in the first place?

It seems to me it ought to be:

"The report includes the following data:"

If there are normative requirements, it seems like it would be better to put it into the XML section itself.
 
Mike
</pre>
  </body>
</html>

--------------7524E8103D99ABF82109734C--


From nobody Tue Jan 26 11:04:42 2021
Return-Path: <mike@fresheez.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 0F7063A0E67 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 11:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 1OlgFz0z_W4D for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 11:04:35 -0800 (PST)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9A833A0EAD for <dmarc@ietf.org>; Tue, 26 Jan 2021 11:04:22 -0800 (PST)
Received: by mail-pg1-x529.google.com with SMTP id c132so12054010pga.3 for <dmarc@ietf.org>; Tue, 26 Jan 2021 11:04:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=yH0UnglDlY+WGqsTE3pMJLPdDxB7X3IuFq3nUpx4V/Y=; b=MWTnB4SgbFQ4eCNvOUYbOwkogDzHVzksOgdqvkC4jycJUFy4IYCF+TdGdLdR0cA7QA TUj2G9IQC7TgXOAr0GocgobpvoQb2p0h60v9t0o2GdqkckAKPfVTK5c9oDLmbL1y6hz8 PMWQefPlotZ+pkGas5mPqRLdMadnr+mOQRhRErGMnKuu73kr5W82Fe5xRngHhPSdo1Et 3Ex1KbZIaEQwuDI5pgPVgcZwgdYHFCWvApLOx1acnToHcVzqvwzJCfK37xTt65NjN3Sc jXeTaW+MZgZx2kMwZysvVY3btqCcUsIQhffyEFajMpuCF0tCvUD+rwEblzm3vsLUlzz6 4GEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=yH0UnglDlY+WGqsTE3pMJLPdDxB7X3IuFq3nUpx4V/Y=; b=HqcTSLzp9Ybpx05hlBrTrDyjdl4qjPpAzguE3nm/rd4yyHRHCYgosrfHATsTA//Tjg tTukEMZCBzeZ9Z0weuurWcnJqVGuOeSAUlRQsPcLbEs/E5jFwqoykv2gUKMkFau7AtpF bhJu18MUpvQTB0F0rkobhQaZGROhuajdQViN2H+z3IbKBquYE/zzAOL0uDkxNNdGFyyZ iXEQ4+mO/qn2LjGuZj0ZUUt4IbUoooI+AlqZtU8J/gZAMrhwAb42M/W2iEH52u7KLqH0 XVlYwToJQ9xZUK2EV9EU3VPBftVn4dR07dy/ACV5rZca1+ukpVxnKuyhZzdMlSEw/Pe5 1Pkw==
X-Gm-Message-State: AOAM533A7NEpychhR4x6eK5RG2GRY9JgtYQ99iueBj6pN2NxQaViaDT6 RRuNgy3NfECeKjiKekgJgtP02zQaVKeRtQ==
X-Google-Smtp-Source: ABdhPJxTz3DvzgWGbQDPK+YGe6/T4s1TK/lADhU5CYYF/RTkRV+oy+YQ5PHFtU4XbIm/xCNzJpkgNw==
X-Received: by 2002:a65:450d:: with SMTP id n13mr7030589pgq.208.1611687861808;  Tue, 26 Jan 2021 11:04:21 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id c5sm19517477pfi.5.2021.01.26.11.04.20 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 11:04:21 -0800 (PST)
To: "dmarc@ietf.org" <dmarc@ietf.org>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <2aaebb6b-6518-19cd-d32d-8370c0adb6d6@mtcc.com>
Date: Tue, 26 Jan 2021 11:04:19 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/XOABlenK3yX5LiOOU4ss2B2Bmh4>
Subject: [dmarc-ietf] understanding section 7.2
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, 26 Jan 2021 19:04:42 -0000

So I'm an outsider who has not tried to digest what's going on in the 
reports until recently so my eyes are fresh. Basically section 7.2 is 
extremely hard to understand what is in the reports. I know that the XML 
is what ought to be normative, but a little bit of ascii art could go a 
long way to helping people understand what the reports do and don't 
have. I've been staring at the XML all morning trying to understand it 
and it is very difficult when all you're trying to do is figure out what 
the reports supply or not. It would be extremely helpful to layout what 
is in each record for human consumption to just understand what the 
reports do and don't contain.

Mike


From nobody Tue Jan 26 11:24:45 2021
Return-Path: <mike@fresheez.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 755153A0DCF for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 11:24:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 hC0GOXU93ROz for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 11:24:42 -0800 (PST)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 572293A0DCD for <dmarc@ietf.org>; Tue, 26 Jan 2021 11:24:42 -0800 (PST)
Received: by mail-pj1-x1034.google.com with SMTP id gx1so2842422pjb.1 for <dmarc@ietf.org>; Tue, 26 Jan 2021 11:24:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=lpR5c18pXfl28hcTYsQ+racrTRUDoewdm2ooyfIPnm0=; b=YIsPhSxfS6WSI7cTlhOSNet+6YbrDjFfKsxlcbUxvdiK/rVmh+RvnOuvwgJ1PLRBEK lOI+Ws4d25Y9TjlcTnKJik7D1JgU31iiREZ/xRtgvFLGGlSCi+ZslXAZlOgRsztvuq0o dwXdFUzcuvYz/BGRXhyRa0xA9DJ7FL0+xqnrZPH4Yor5epYrX2ScGlIC9ySreYEJXlwB KedLBOttDfY4Lj91J8SrMnkg/EaJOm88BUvm/LMEIkWFZ3sfKx2cuZiSUTA0Y/31paSS GnKWddvcFsDfTTov45Qig2ZO7NjvSfUK6TD5NaY1Qbw7dijJCsojb2pteUDR7UZV+hwm 1geA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=lpR5c18pXfl28hcTYsQ+racrTRUDoewdm2ooyfIPnm0=; b=f9fspq/2gXOoGcU+Zcw0rNJw1dHotwLyQJGCSStui9dO4YzQtY/n9S7eBApHC34+w3 icayGiCk1lm9rBqDXQztXOgqcsn1GSL4GTwBr4Q9KRpmy4F2hhtDWVHp3BRbQK7Y7NRd exCtuPRlCE4KMyH+1XJkyiacTIqqP6lczRSR+pLOAaIbHi3pgLVswQxiA9nHtv7GSrvw SFC5ZKBW6arBTyog9IwAZwZrJX2F2jSFJCbwd/L0yJViKP1uSwZMY0RM6m+9oww6zGX+ WjHV1u2elnitPAUIHgrJES0zGKHMN0CQn0YPMftYIGJ0qFhfeU7CwZVGqnBUJ8fdHccY QAUA==
X-Gm-Message-State: AOAM530pTuPZGUMApbQ30D7CdJa7/DSs9CwqE6ICRkkVoNhAeHdAhye8 Mh28I2htNLVjkfuEXIi+MTf8pgg6iJsIHA==
X-Google-Smtp-Source: ABdhPJzlHNQTaLvc03/pPM1kw/ZCm3UCsEOiuv6FzrI45B8W2Ocb9TDy9uK1ZBL3eHvs7PCXtPneHg==
X-Received: by 2002:a17:902:a401:b029:dc:3e1d:234a with SMTP id p1-20020a170902a401b02900dc3e1d234amr7419218plq.48.1611689081307;  Tue, 26 Jan 2021 11:24:41 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id r189sm777008pgr.10.2021.01.26.11.24.40 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 11:24:40 -0800 (PST)
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com>
Date: Tue, 26 Jan 2021 11:24:39 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------763A1CE97BA16F75009DB887"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LgGs2clJLL2AA4HjciUsCLUR3CM>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 19:24:44 -0000

This is a multi-part message in MIME format.
--------------763A1CE97BA16F75009DB887
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/26/21 10:56 AM, Todd Herr wrote:

     > In addition, if I recover that message from the log, I might find no
     > relationship with the reporting domain or the reported source IP.
     > That is to say, I won't be able to deduce if the report is fake
    or real.


    My main point here is to point out the attack.

>
> The attack scenario you have described relies on several possible but 
> perhaps implausible conditions all being true:
>
> 1. There exists a domain run by people who are savvy enough to want to 
> implement DMARC and can consume reports, but don't have a good grasp 
> on which IPs are likely to be theirs and which aren't, and don't have 
> an understanding of how to use common tools to figure out whether an 
> IP address might belong to their provider's ASN or one halfway around 
> the world, and

Here's a very basic question: if I do not know all of the IP addresses 
that send on my behalf, are DMARC reports of any value? Enterprises farm 
out email all of the time and it could be difficult to know when they 
change their server addresses, etc. If the reporting is predicated on 
your having in effect and up to date SPF record (ie, do all of the work 
to be able to produce one), then that negates anybody who just uses DKIM 
alone which should be a completely acceptable use case. And no, the 
domain/selector tells you nothing when it doesn't verify.

If it is the case that you MUST know all of your sending IP addresses, 
that should be in blinking bold right up front in section 7.

Mike


--------------763A1CE97BA16F75009DB887
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/26/21 10:56 AM, Todd Herr wrote:<br>
    </div>
    <blockquote class="gmail_quote" style="margin:0px 0px 0px
      0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      &gt; In addition, if I recover that message from the log, I might
      find no <br>
      &gt; relationship with the reporting domain or the reported source
      IP.  <br>
      &gt; That is to say, I won't be able to deduce if the report is
      fake or real.<br>
      <br>
      <br>
      My main point here is to point out the attack.<br>
      <br>
    </blockquote>
    <blockquote type="cite"
cite="mid:CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <div><br>
          </div>
          <div>The attack scenario you have described relies on several
            possible but perhaps implausible conditions all being true:</div>
          <div><br>
          </div>
          <div>1. There exists a domain run by people who are savvy
            enough to want to implement DMARC and can consume reports,
            but don't have a good grasp on which IPs are likely to be
            theirs and which aren't, and don't have an understanding of
            how to use common tools to figure out whether an IP address
            might belong to their provider's ASN or one halfway around
            the world, and</div>
        </div>
      </div>
    </blockquote>
    <p>Here's a very basic question: if I do not know all of the IP
      addresses that send on my behalf, are DMARC reports of any value?
      Enterprises farm out email all of the time and it could be
      difficult to know when they change their server addresses, etc. If
      the reporting is predicated on your having in effect and up to
      date SPF record (ie, do all of the work to be able to produce
      one), then that negates anybody who just uses DKIM alone which
      should be a completely acceptable use case. And no, the
      domain/selector tells you nothing when it doesn't verify.<br>
    </p>
    <p>If it is the case that you MUST know all of your sending IP
      addresses, that should be in blinking bold right up front in
      section 7.</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------763A1CE97BA16F75009DB887--


From nobody Tue Jan 26 12:02:58 2021
Return-Path: <todd.herr@valimail.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 2EA533A0AF3 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 12:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 uyP23lqYK0U5 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 12:02:54 -0800 (PST)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6522E3A0E4A for <dmarc@ietf.org>; Tue, 26 Jan 2021 12:01:51 -0800 (PST)
Received: by mail-qk1-x72f.google.com with SMTP id r77so17041451qka.12 for <dmarc@ietf.org>; Tue, 26 Jan 2021 12:01:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z8aFzISjbd3k4wZkk2XNuvFZaJoQ3aa3gbspCsceowc=; b=FG2BzpJRifGVyEq3h9jr+J3r7Usl2uRU6SOm/N0z1DxYar5A+0ATEw4FVPn5zGcIWI rPq3DA71xE43FguCsJ3px9hVHClf4U4D++AptTsd7OWlevAO/qaiDQkzTVeAXQsGOZJ3 5wxd8saUVU4/iRnqJmepdfK9VeZEW+BRUiGUGN+Je5GK0G7K+ZbhZ8B3xWXO5Lhv2oEz O3pdt01AMuZYwQEu70d4GLeAMrzPdGKArdVRC+fj/1pRRG9zmHHItE7nXATG4eVR/hwB wZMShio8YHhLz3rpEzlB9PjwLs5jP0+KRkDe14JXrQBLVWArgV7C/N9vsFnMeR4SuD+j FmEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z8aFzISjbd3k4wZkk2XNuvFZaJoQ3aa3gbspCsceowc=; b=tW0CBEKP4W4L50lL7IvMCf033XVPNpbUMsOZhCx+Hc4njqrBndlWzP3oGwH+nxD0ob iZrMhruIF6aiiUTHsVhAoTjCIYrjZ5i5nHzZrOpVtGJ/5i/qYqGwQIcYOq67RwnbfswN qFdq1MoBtQbh2N3acZELEaohDiCRo5Hp0dJN4oHToEhN+qYZeUYgD2RdWAx62yZ7P01s TfUHpg+KWEjI7d461HedasVnyEmfGbpD1ZYA/pHu9Fy6+RJ585hJ+lpEeKMTK0fS1FBh 4iEEqcYv8UgDp8AznkuIQYUH/58NAsGVWmakUCapWQcRrBgV2FIMe7/VnH00kfeY3dNW TvRw==
X-Gm-Message-State: AOAM533e+JHtbLraxGEfko7WPHQklrSX+Lsm0coJ+YcUbORxkwOCfFkT H9DhHaEkl7lgaqD7AxIPCX12PJg+qP44Jk5z35kpJREa1f82Vg==
X-Google-Smtp-Source: ABdhPJz1dkbsyQPWNiBNhay5lDhpDP7rsZzz8fY22m1pQQgGJ2TsWZRqYZcw1adBR4sGMD3E7UwGFibaTc4RryxKRpQ=
X-Received: by 2002:a37:a245:: with SMTP id l66mr3200703qke.325.1611691310184;  Tue, 26 Jan 2021 12:01:50 -0800 (PST)
MIME-Version: 1.0
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com>
In-Reply-To: <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 26 Jan 2021 15:01:34 -0500
Message-ID: <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000080f1505b9d320fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PkcfzgGbc3pcgKmKVnyvZWa5Kfg>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 20:02:57 -0000

--000000000000080f1505b9d320fc
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 26, 2021 at 2:24 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/26/21 10:56 AM, Todd Herr wrote:
>
>> > In addition, if I recover that message from the log, I might find no
>> > relationship with the reporting domain or the reported source IP.
>> > That is to say, I won't be able to deduce if the report is fake or real.
>>
>>
>> My main point here is to point out the attack.
>>
>>
> The attack scenario you have described relies on several possible but
> perhaps implausible conditions all being true:
>
> 1. There exists a domain run by people who are savvy enough to want to
> implement DMARC and can consume reports, but don't have a good grasp on
> which IPs are likely to be theirs and which aren't, and don't have an
> understanding of how to use common tools to figure out whether an IP
> address might belong to their provider's ASN or one halfway around the
> world, and
>
> Here's a very basic question: if I do not know all of the IP addresses
> that send on my behalf, are DMARC reports of any value? Enterprises farm
> out email all of the time and it could be difficult to know when they
> change their server addresses, etc. If the reporting is predicated on your
> having in effect and up to date SPF record (ie, do all of the work to be
> able to produce one), then that negates anybody who just uses DKIM alone
> which should be a completely acceptable use case. And no, the
> domain/selector tells you nothing when it doesn't verify.
>
> If it is the case that you MUST know all of your sending IP addresses,
> that should be in blinking bold right up front in section 7.
>
>
> Yes, DMARC reports are of value if you don't know all of the IP addresses
that send on your behalf. Some have even written blog posts on the topic of
using DMARC aggregate reports as a tool to audit one's authentication
practices, by publishing a policy of p=none, collecting the reports,
analyzing the data, fixing problems, iterate, iterate, iterate until one is
ready to move on to the ultimate goal of p=reject.

In my experience, there is enough information in the DMARC aggregate
reports to allow for someone to make an educated guess as to whether an IP
that's generating mail that's not authenticating is perhaps a server
sending reports from the side of the desk of Emily in Engineering, or a
third party that Mike in Marketing contracted to send mail on the company's
behalf, or whether it's almost certainly an IP that's not one used by the
organization at all. This presumes, of course, that one at least has a clue
as to what public IP range(s) are in use by the organization, not just for
mail but for general connectivity, but with the security organization
and/or IT typically running (or at least ordering and participating in the
analysis of) the DMARC deployment, that seems a safe assumption. Having the
source IP in the aggregate report isn't necessarily just to make sure it
gets added to the SPF record, either; many times it (along with the other
information in that tuple) gives the report consumer a clue as to where to
start hunting in his infrastructure for the MTA that isn't correctly DKIM
signing mail at this time.

As to third parties changing email addresses all the time, you're correct,
they do, but they mitigate the impact on their customers by instructing
them to use the include: mechanism in their SPF records, rather than trying
to enumerate all of the vendor's IP ranges, e.g., include:_
spf.salesforce.com, include:_spf.google.com, etc.



-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000080f1505b9d320fc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 26, 2021 at 2:24 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/26/21 10:56 AM, Todd Herr wrote:<br>
    </div>
    <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">
     =20
      &gt; In addition, if I recover that message from the log, I might
      find no <br>
      &gt; relationship with the reporting domain or the reported source
      IP.=C2=A0 <br>
      &gt; That is to say, I won&#39;t be able to deduce if the report is
      fake or real.<br>
      <br>
      <br>
      My main point here is to point out the attack.<br>
      <br>
    </blockquote>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <div><br>
          </div>
          <div>The attack scenario you have described relies on several
            possible but perhaps implausible conditions all being true:</di=
v>
          <div><br>
          </div>
          <div>1. There exists a domain run by people who are savvy
            enough to want to implement DMARC and can consume reports,
            but don&#39;t have a good grasp on which IPs are likely to be
            theirs and which aren&#39;t, and don&#39;t have an understandin=
g of
            how to use common tools to figure out whether an IP address
            might belong to their provider&#39;s ASN or one halfway around
            the world, and</div>
        </div>
      </div>
    </blockquote>
    <p>Here&#39;s a very basic question: if I do not know all of the IP
      addresses that send on my behalf, are DMARC reports of any value?
      Enterprises farm out email all of the time and it could be
      difficult to know when they change their server addresses, etc. If
      the reporting is predicated on your having in effect and up to
      date SPF record (ie, do all of the work to be able to produce
      one), then that negates anybody who just uses DKIM alone which
      should be a completely acceptable use case. And no, the
      domain/selector tells you nothing when it doesn&#39;t verify.<br>
    </p>
    <p>If it is the case that you MUST know all of your sending IP
      addresses, that should be in blinking bold right up front in
      section 7.</p>
    <p><br></p></div></blockquote><div>Yes, DMARC reports are of value if y=
ou don&#39;t know all of the IP addresses that send on your behalf. Some ha=
ve even written blog posts on the topic of using DMARC aggregate reports as=
 a tool to audit one&#39;s authentication practices, by publishing a policy=
 of p=3Dnone, collecting the reports, analyzing the data, fixing problems, =
iterate, iterate, iterate until one is ready to move on to the ultimate goa=
l of p=3Dreject.</div><div><br></div><div>In my experience, there is enough=
 information in the DMARC aggregate reports to allow for someone to make an=
 educated guess as to whether an IP that&#39;s generating mail that&#39;s n=
ot authenticating is perhaps a server sending reports from the side of the =
desk of Emily in Engineering, or a third party that Mike in Marketing contr=
acted to send mail on the company&#39;s behalf, or whether it&#39;s almost =
certainly an IP that&#39;s not one used by the organization at all. This pr=
esumes, of course, that one at least has a clue as to what public IP range(=
s) are in use by the organization, not just for mail but for general connec=
tivity, but with the security organization and/or IT typically running (or =
at least ordering and participating in the analysis of) the DMARC deploymen=
t, that seems a safe assumption. Having the source IP in the aggregate repo=
rt isn&#39;t necessarily just to make sure it gets added to the SPF record,=
 either; many times it (along with the other information in that tuple) giv=
es the report consumer a clue as to where to start hunting in his infrastru=
cture for the MTA that isn&#39;t correctly DKIM signing mail at this time.<=
/div><div><br></div><div>As to third parties changing email addresses all t=
he time, you&#39;re correct, they do, but they mitigate the impact on their=
 customers by instructing them to use the include: mechanism in their SPF r=
ecords, rather than trying to enumerate all of the vendor&#39;s IP ranges, =
e.g., include:_<a href=3D"http://spf.salesforce.com">spf.salesforce.com</a>=
, include:_<a href=3D"http://spf.google.com">spf.google.com</a>, etc.</div>=
<div><br></div><div>=C2=A0</div></div><div><br></div>-- <br><div dir=3D"ltr=
" class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656=
;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span=
 style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font=
-family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | Sr. Technical =
Program Manager</span></div><span style=3D"vertical-align:baseline;white-sp=
ace:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-align:le=
ft"><span style=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"=
vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" target=
=3D"_blank">todd.herr@valimail.com</a></span></div></span><span><div><span>=
<b>p:</b></span><span> 703.220.4153 </span><span></span></div></span><p dir=
=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-seri=
f;font-size:small;background-color:rgb(255,255,255);line-height:1.38;margin=
-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial=
;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;whit=
e-space:pre-wrap"><img src=3D"https://lh5.googleusercontent.com/_vs__6iRjfm=
T2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7=
n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" style=3D"border: none; =
height: 40px; width: 177px;"></span></p><p dir=3D"ltr" style=3D"color:rgb(3=
4,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small;background-=
color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><=
br></p><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#666666" face=3D"Ar=
ial"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email an=
d all data transmitted with it contains confidential and/or proprietary inf=
ormation intended solely for the use of individual(s) authorized to receive=
 it. If you are not an intended and authorized recipient you are hereby not=
ified of any use, disclosure, copying or distribution of the information in=
cluded in this transmission is prohibited and may be unlawful. Please immed=
iately notify the sender by replying to this email and then delete it from =
your system.</span></font></p></span></div></div>

--000000000000080f1505b9d320fc--


From nobody Tue Jan 26 12:17:01 2021
Return-Path: <mike@fresheez.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 E3BE23A0E32 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 12:16:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 vrauvkhAgAPW for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 12:16:57 -0800 (PST)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CDA03A0E2F for <dmarc@ietf.org>; Tue, 26 Jan 2021 12:16:57 -0800 (PST)
Received: by mail-pl1-x634.google.com with SMTP id d4so10405956plh.5 for <dmarc@ietf.org>; Tue, 26 Jan 2021 12:16:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=e5NzvnK8Vh1XdsPHZHE0AWKAPRRV+Gak+eyY/lmH7Yw=; b=M9JoIX/ZaI8iou2x7yj+ic58yaQtpH8kBhhgSmSTry2/f7p3+Cy6XUFWBxGyy9ur6A IUuvBQgTGCfK1Rg+qUYFn6sDWl0IGvAWireD3P2/Zr0XeoY056AVehPubpB2/0ZBAnNF fqUWOWhsOVqd8DNkUwmdq6fV11YTeKQN2LoF+PlthDkUy0nOfvh/DghJJaeVxrzJzF8k V4rBcBUSbq6ShdLCwrq/ENbOPdPvji4ip+WkwJc1dBXTOLCKD6TbkBezfBSivIJ21bSp tyKVTFZ8UsY52B2uWzHBhFVPpb5Kr7Z/WtT3vg8xnjOTb4S4qGvQLd3k7C9w3Vu5MO80 ufMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=e5NzvnK8Vh1XdsPHZHE0AWKAPRRV+Gak+eyY/lmH7Yw=; b=HvGUlicIh8PcyS4Y3A6CDNJlH1seD5ynNozYorvVCVV37Oxj9OxIT8y5nfBwfNB7ds uf9pmzO5U29fawnSonzOMrOipp50mKodnaaE8+oyw5SkVndo8zettKGVu10FNXVus/RV 6OWhnQ55HOayl62KLOP4MJcJ0cWT8F2oAZRMsfh2SpprXqSUsrYcUgBOqiO4CZxYbZwt v+qcfHSWPQgjX86eVurIbgTtmj5diysqcI45Z2RfzGSuiqeBeRgSeH1KWezgyxRJ8M3J ICj69lOKsLUy4W7Ez7S4v8iGX3xFrw1U4seRZjtQ5vN5OuWcdeK8ClO7+iuRl3Zcmak+ xs5w==
X-Gm-Message-State: AOAM533o6Vv/J1idSK6YyYGIqP3yG/0kVXKP+v18k0pIQ8m2aBb9zrje V8Jwwh2eyofDWpipuZwkk6QkzNDknMyKuQ==
X-Google-Smtp-Source: ABdhPJzpw80n2Nm3ySWwyiOsD6r0MSgvEPd+cSUIj1B5Mi8MuIStYsEjONF1FbR5fO/CBCtMM/CY6w==
X-Received: by 2002:a17:90b:3284:: with SMTP id ks4mr1582164pjb.216.1611692216255;  Tue, 26 Jan 2021 12:16:56 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id 141sm20069140pfa.65.2021.01.26.12.16.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 12:16:55 -0800 (PST)
To: Todd Herr <todd.herr@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com>
Date: Tue, 26 Jan 2021 12:16:54 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------0923B1F51C472FC7C9DF8DE4"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/pGtjpvMBawPeTybCUeiwLAEXwco>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 20:16:59 -0000

This is a multi-part message in MIME format.
--------------0923B1F51C472FC7C9DF8DE4
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/26/21 12:01 PM, Todd Herr wrote:
> On Tue, Jan 26, 2021 at 2:24 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     On 1/26/21 10:56 AM, Todd Herr wrote:
>
>         > In addition, if I recover that message from the log, I might
>         find no
>         > relationship with the reporting domain or the reported
>         source IP.
>         > That is to say, I won't be able to deduce if the report is
>         fake or real.
>
>
>         My main point here is to point out the attack.
>
>>
>>     The attack scenario you have described relies on several possible
>>     but perhaps implausible conditions all being true:
>>
>>     1. There exists a domain run by people who are savvy enough to
>>     want to implement DMARC and can consume reports, but don't have a
>>     good grasp on which IPs are likely to be theirs and which aren't,
>>     and don't have an understanding of how to use common tools to
>>     figure out whether an IP address might belong to their provider's
>>     ASN or one halfway around the world, and
>
>     Here's a very basic question: if I do not know all of the IP
>     addresses that send on my behalf, are DMARC reports of any value?
>     Enterprises farm out email all of the time and it could be
>     difficult to know when they change their server addresses, etc. If
>     the reporting is predicated on your having in effect and up to
>     date SPF record (ie, do all of the work to be able to produce
>     one), then that negates anybody who just uses DKIM alone which
>     should be a completely acceptable use case. And no, the
>     domain/selector tells you nothing when it doesn't verify.
>
>     If it is the case that you MUST know all of your sending IP
>     addresses, that should be in blinking bold right up front in
>     section 7.
>
>
> Yes, DMARC reports are of value if you don't know all of the IP 
> addresses that send on your behalf. Some have even written blog posts 
> on the topic of using DMARC aggregate reports as a tool to audit one's 
> authentication practices, by publishing a policy of p=none, collecting 
> the reports, analyzing the data, fixing problems, iterate, iterate, 
> iterate until one is ready to move on to the ultimate goal of p=reject.
>
How do I know when I'm done though if I don't know the IP addresses who 
send on my behalf? Is it an actual forgery or is it Marsha in marketing 
using a outsourced email blaster?

The larger point is that I should not have had to come to a working 
group mailing list to find out what should be in the document in the 
first place. Along with some ascii art in 7.2, there needs to be some 
explanation of the reporting's applicability and limitations. It doesn't 
need to be tome but some informative text goes a long way to helping 
people out who we're involved with the document from the beginning.

Mike


--------------0923B1F51C472FC7C9DF8DE4
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/26/21 12:01 PM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Tue, Jan 26, 2021 at 2:24 PM Michael Thomas
          &lt;<a href="mailto:mike@mtcc.com" moz-do-not-send="true">mike@mtcc.com</a>&gt;
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p><br>
              </p>
              <div>On 1/26/21 10:56 AM, Todd Herr wrote:<br>
              </div>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex"> &gt; In addition, if
                I recover that message from the log, I might find no <br>
                &gt; relationship with the reporting domain or the
                reported source IP.  <br>
                &gt; That is to say, I won't be able to deduce if the
                report is fake or real.<br>
                <br>
                <br>
                My main point here is to point out the attack.<br>
                <br>
              </blockquote>
              <blockquote type="cite">
                <div dir="ltr">
                  <div class="gmail_quote">
                    <div><br>
                    </div>
                    <div>The attack scenario you have described relies
                      on several possible but perhaps implausible
                      conditions all being true:</div>
                    <div><br>
                    </div>
                    <div>1. There exists a domain run by people who are
                      savvy enough to want to implement DMARC and can
                      consume reports, but don't have a good grasp on
                      which IPs are likely to be theirs and which
                      aren't, and don't have an understanding of how to
                      use common tools to figure out whether an IP
                      address might belong to their provider's ASN or
                      one halfway around the world, and</div>
                  </div>
                </div>
              </blockquote>
              <p>Here's a very basic question: if I do not know all of
                the IP addresses that send on my behalf, are DMARC
                reports of any value? Enterprises farm out email all of
                the time and it could be difficult to know when they
                change their server addresses, etc. If the reporting is
                predicated on your having in effect and up to date SPF
                record (ie, do all of the work to be able to produce
                one), then that negates anybody who just uses DKIM alone
                which should be a completely acceptable use case. And
                no, the domain/selector tells you nothing when it
                doesn't verify.<br>
              </p>
              <p>If it is the case that you MUST know all of your
                sending IP addresses, that should be in blinking bold
                right up front in section 7.</p>
              <p><br>
              </p>
            </div>
          </blockquote>
          <div>Yes, DMARC reports are of value if you don't know all of
            the IP addresses that send on your behalf. Some have even
            written blog posts on the topic of using DMARC aggregate
            reports as a tool to audit one's authentication practices,
            by publishing a policy of p=none, collecting the reports,
            analyzing the data, fixing problems, iterate, iterate,
            iterate until one is ready to move on to the ultimate goal
            of p=reject.</div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>How do I know when I'm done though if I don't know the IP
      addresses who send on my behalf? Is it an actual forgery or is it
      Marsha in marketing using a outsourced email blaster? <br>
    </p>
    <p>The larger point is that I should not have had to come to a
      working group mailing list to find out what should be in the
      document in the first place. Along with some ascii art in 7.2,
      there needs to be some explanation of the reporting's
      applicability and limitations. It doesn't need to be tome but some
      informative text goes a long way to helping people out who we're
      involved with the document from the beginning.</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------0923B1F51C472FC7C9DF8DE4--


From nobody Tue Jan 26 12:29:38 2021
Return-Path: <todd.herr@valimail.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 018843A0E79 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 12:29:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 QcagQNzpDgyo for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 12:29:32 -0800 (PST)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDCC13A0E5A for <dmarc@ietf.org>; Tue, 26 Jan 2021 12:29:31 -0800 (PST)
Received: by mail-qk1-x72d.google.com with SMTP id n15so12663066qkh.8 for <dmarc@ietf.org>; Tue, 26 Jan 2021 12:29:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Y8OL15iVr9H2n5QK63/ATMtdYXd4ZN7pFTCKPi/hyyI=; b=ZobgK4zViJQ1NCasZwDPaXwSjNrIMiF4szPQYCqmg/Pj37KXTrKY5oeohbSMO4VpSb T2hmbWAv1pYXYi/OI9QiXycCfB4MmQMSr/Zl9R7zmpolRTlzY7ocolHVBg/iR9p/n97j RywEiLfoWiCtXv1g1OALXkHmmjy739id1N8577qEg5uoO5Eim02YRj0Ty4QJsyzeI1lg Ry2VsP8ESDkoaWNGOCytIBNLhJcFVfYd4XnoidTs6QId59IyqTRGFLpHDpmdVAmlA+0L G1zwebRNUkyexBVVMwMuZ9FEAVKfA1piKUDPPgt+LMayEpe/GnDWgDjD3IfmiNeThTeS JMYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Y8OL15iVr9H2n5QK63/ATMtdYXd4ZN7pFTCKPi/hyyI=; b=PMVCcpUjPLd5HARnBBxm1bBdrTg4ti9lxAzP8ouaup03WMHE51mVKPPcLr2Ks9WWtO 6AGqtCtRbiaf3lTUGmROSR2fNJNOjN5oFcygKqP6yCLBrO8N/diokaQ35AOugVfkxn2n 2n9tLcadQzwEY6NlX/xZwpnwuuGFIdz9MbXPU64mcMpeINknHzQpDVKNa9VgPglE4dDS rgKUNnhGo9lcb+zpOsOGXCgsYgOkEVyntOm2eJDKsX5iK6KMQnpNh8AMzeXGZuwy/XJA GObaQLop1LPCygQFi5mMUNGvRkVBSs3pWaaLPN2Ags0dv1qNPNcX3o9kMDvdogyaASi2 /HXQ==
X-Gm-Message-State: AOAM5312HGba9TwokrLJa6KGMGIjnVszYY0uEHu9EEgcfEne8lAVpU1z +QTsUX/T1wj4MZm6awjdV+zBceFERmx297ncDXgHUutkV04=
X-Google-Smtp-Source: ABdhPJyY05S97yB5EUA3ZmfyrTkK1qkHSrMABoz0Xcy2A6KJFhHVWg84mEkY97zSgqCooQODafVP37KckrffdCUT5zw=
X-Received: by 2002:a37:a245:: with SMTP id l66mr3323527qke.325.1611692970517;  Tue, 26 Jan 2021 12:29:30 -0800 (PST)
MIME-Version: 1.0
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com> <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com>
In-Reply-To: <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 26 Jan 2021 15:29:14 -0500
Message-ID: <CAHej_8=jwMmMZLAUoKAXGgmn3va3R_nSYDgtM1U4ZG2s+uVz_Q@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000feb47c05b9d38220"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/zmpIk1Z3AZPkpaD26wAIjegA7_4>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 20:29:36 -0000

--000000000000feb47c05b9d38220
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 26, 2021 at 3:16 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/26/21 12:01 PM, Todd Herr wrote:
>
> On Tue, Jan 26, 2021 at 2:24 PM Michael Thomas <mike@mtcc.com> wrote:
>
>>
>> On 1/26/21 10:56 AM, Todd Herr wrote:
>>
>>> > In addition, if I recover that message from the log, I might find no
>>> > relationship with the reporting domain or the reported source IP.
>>> > That is to say, I won't be able to deduce if the report is fake or
>>> real.
>>>
>>>
>>> My main point here is to point out the attack.
>>>
>>>
>> The attack scenario you have described relies on several possible but
>> perhaps implausible conditions all being true:
>>
>> 1. There exists a domain run by people who are savvy enough to want to
>> implement DMARC and can consume reports, but don't have a good grasp on
>> which IPs are likely to be theirs and which aren't, and don't have an
>> understanding of how to use common tools to figure out whether an IP
>> address might belong to their provider's ASN or one halfway around the
>> world, and
>>
>> Here's a very basic question: if I do not know all of the IP addresses
>> that send on my behalf, are DMARC reports of any value? Enterprises farm
>> out email all of the time and it could be difficult to know when they
>> change their server addresses, etc. If the reporting is predicated on your
>> having in effect and up to date SPF record (ie, do all of the work to be
>> able to produce one), then that negates anybody who just uses DKIM alone
>> which should be a completely acceptable use case. And no, the
>> domain/selector tells you nothing when it doesn't verify.
>>
>> If it is the case that you MUST know all of your sending IP addresses,
>> that should be in blinking bold right up front in section 7.
>>
>>
>> Yes, DMARC reports are of value if you don't know all of the IP addresses
> that send on your behalf. Some have even written blog posts on the topic of
> using DMARC aggregate reports as a tool to audit one's authentication
> practices, by publishing a policy of p=none, collecting the reports,
> analyzing the data, fixing problems, iterate, iterate, iterate until one is
> ready to move on to the ultimate goal of p=reject.
>
> How do I know when I'm done though if I don't know the IP addresses who
> send on my behalf? Is it an actual forgery or is it Marsha in marketing
> using a outsourced email blaster?
>

Time.

Some industry experts have suggested that one budget twelve to eighteen
months between first publishing a DMARC policy record and the hoped-for
transition to p=reject. YMMV, and a lot depends on the types of messages
that the organization sends, and their cadence. At the extreme end of more
than a year would be larger companies doing seasonal or cyclical mailings,
ones that maybe only market to certain customer segments once or twice per
year, tops. The more one knows about one's mail flows and the better one's
authentication practices before deploying DMARC, the shorter that time can
be, but a year or more isn't unusual at all.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--000000000000feb47c05b9d38220
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 26, 2021 at 3:16 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 1/26/21 12:01 PM, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Tue, Jan 26, 2021 at 2:24 PM Michael Thomas
          &lt;<a href=3D"mailto:mike@mtcc.com" target=3D"_blank">mike@mtcc.=
com</a>&gt;
          wrote:<br>
        </div>
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <p><br>
              </p>
              <div>On 1/26/21 10:56 AM, Todd Herr wrote:<br>
              </div>
              <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> &gt; In ad=
dition, if
                I recover that message from the log, I might find no <br>
                &gt; relationship with the reporting domain or the
                reported source IP.=C2=A0 <br>
                &gt; That is to say, I won&#39;t be able to deduce if the
                report is fake or real.<br>
                <br>
                <br>
                My main point here is to point out the attack.<br>
                <br>
              </blockquote>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div class=3D"gmail_quote">
                    <div><br>
                    </div>
                    <div>The attack scenario you have described relies
                      on several possible but perhaps implausible
                      conditions all being true:</div>
                    <div><br>
                    </div>
                    <div>1. There exists a domain run by people who are
                      savvy enough to want to implement DMARC and can
                      consume reports, but don&#39;t have a good grasp on
                      which IPs are likely to be theirs and which
                      aren&#39;t, and don&#39;t have an understanding of ho=
w to
                      use common tools to figure out whether an IP
                      address might belong to their provider&#39;s ASN or
                      one halfway around the world, and</div>
                  </div>
                </div>
              </blockquote>
              <p>Here&#39;s a very basic question: if I do not know all of
                the IP addresses that send on my behalf, are DMARC
                reports of any value? Enterprises farm out email all of
                the time and it could be difficult to know when they
                change their server addresses, etc. If the reporting is
                predicated on your having in effect and up to date SPF
                record (ie, do all of the work to be able to produce
                one), then that negates anybody who just uses DKIM alone
                which should be a completely acceptable use case. And
                no, the domain/selector tells you nothing when it
                doesn&#39;t verify.<br>
              </p>
              <p>If it is the case that you MUST know all of your
                sending IP addresses, that should be in blinking bold
                right up front in section 7.</p>
              <p><br>
              </p>
            </div>
          </blockquote>
          <div>Yes, DMARC reports are of value if you don&#39;t know all of
            the IP addresses that send on your behalf. Some have even
            written blog posts on the topic of using DMARC aggregate
            reports as a tool to audit one&#39;s authentication practices,
            by publishing a policy of p=3Dnone, collecting the reports,
            analyzing the data, fixing problems, iterate, iterate,
            iterate until one is ready to move on to the ultimate goal
            of p=3Dreject.</div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>How do I know when I&#39;m done though if I don&#39;t know the IP
      addresses who send on my behalf? Is it an actual forgery or is it
      Marsha in marketing using a outsourced email blaster?</p></div></bloc=
kquote><div><br></div><div>Time.=C2=A0</div><div><br></div><div>Some indust=
ry experts have suggested that one budget twelve to eighteen months between=
 first publishing a DMARC policy record and the hoped-for transition to p=
=3Dreject. YMMV, and a lot depends on the types of messages that the organi=
zation sends, and their cadence. At the extreme end of more than a year wou=
ld be larger companies doing seasonal or cyclical mailings, ones that maybe=
 only market to certain customer segments once or twice per year, tops. The=
 more one knows about one&#39;s mail flows and the better one&#39;s authent=
ication practices before deploying DMARC, the shorter that time can be, but=
 a year or more isn&#39;t unusual at all.=C2=A0</div></div><div><br></div>-=
- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p dir=3D"ltr" style=
=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div style=3D"t=
ext-align:left"><span style=3D"vertical-align:baseline;white-space:pre-wrap=
;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span style=3D"v=
ertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Ari=
al"> | Sr. Technical Program Manager</span></div><span style=3D"vertical-al=
ign:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><div s=
tyle=3D"text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b><=
/span><span style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@=
valimail.com" target=3D"_blank">todd.herr@valimail.com</a></span></div></sp=
an><span><div><span><b>p:</b></span><span> 703.220.4153 </span><span></span=
></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial=
,Helvetica,sans-serif;font-size:small;background-color:rgb(255,255,255);lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical=
-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.googleusercon=
tent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mff2kDFOqe0Lh=
bnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-Dx9rESL" sty=
le=3D"border: none; height: 40px; width: 177px;"></span></p><p dir=3D"ltr" =
style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-si=
ze:small;background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;=
margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-color:rgb(255=
,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D=
"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-space:pre=
-wrap">This email and all data transmitted with it contains confidential an=
d/or proprietary information intended solely for the use of individual(s) a=
uthorized to receive it. If you are not an intended and authorized recipien=
t you are hereby notified of any use, disclosure, copying or distribution o=
f the information included in this transmission is prohibited and may be un=
lawful. Please immediately notify the sender by replying to this email and =
then delete it from your system.</span></font></p></span></div></div>

--000000000000feb47c05b9d38220--


From contact@emailkarma.net  Tue Jan 26 12:41:22 2021
Return-Path: <contact@emailkarma.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 BFB4C3A0E6F for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 12:41:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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 a1h7NhEfZuRl for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 12:41:21 -0800 (PST)
Received: from mail-ua1-f51.google.com (mail-ua1-f51.google.com [209.85.222.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BFDA3A0E6E for <dmarc@ietf.org>; Tue, 26 Jan 2021 12:41:21 -0800 (PST)
Received: by mail-ua1-f51.google.com with SMTP id d3so6091353uap.4 for <dmarc@ietf.org>; Tue, 26 Jan 2021 12:41:20 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=4Qhn1Q80qQ8UBPRRaWYUWYCbJRvGpRaiJiz60iK+kKc=; b=R4p3RSoPebIO+dTG6cc98vaJy+lekZIeF01N2boXaZn4dke2tRucLoQAFLBLpDn08u K+I4inD+N6HTJ+hAsnfFmVfwX8FH95GJJXpB2C1nu67+RSDAkLrmO3Dwj+tWsgr+j5o7 2u2faYsTd/mhjwbsI4RkFJtijKFsMc9wFn//O0MMSH7VTiVknqN6pLiDoajLEeEPq47l kXbJ7qgp5PXuN5xefR0oZKolPSt2QOEZx+csJ1opSyxBFt+dAciDEGdADdTFNZ50TMXj 4igZ6GwWqEC3UHnuxo+Jya5JG1r43vbB3RGeNFICI8PLwoKnlF+VCr2u8ChEWXmSUvZ0 SruA==
X-Gm-Message-State: AOAM530XfhS6rkbC68An45YRtUK7eHAghJqVtSwwQAnqDwUdgur8Mk7X wqng/uUG8ZN+MbSE7LWY5I7pLZAhJJ98VhaJV5epqAmQyszLvw==
X-Google-Smtp-Source: ABdhPJyGyeJGN7ICYYXIe4H1ITKEbSV6hWkj0Kdnznb0L1BtXEaWY0h/0SWHGb4y5h8zPYQVwSRUry+x35jXrPLlhSE=
X-Received: by 2002:a9f:2c07:: with SMTP id r7mr5958981uaj.4.1611693679621; Tue, 26 Jan 2021 12:41:19 -0800 (PST)
MIME-Version: 1.0
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com> <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com>
In-Reply-To: <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com>
From: Matt V <ietfdmarc@emailkarma.net>
Date: Tue, 26 Jan 2021 15:41:10 -0500
Message-ID: <CAPyMsDi_tVK7j_HjpAfLEcy=xCDPR4kPZs-5MOFVkQSgCjwsuQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000042ce3a05b9d3adc9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4et8YT2Yfoso7-y1WFgMtqhqG9M>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 20:42:32 -0000

--00000000000042ce3a05b9d3adc9
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 26, 2021 at 3:17 PM Michael Thomas <mike@mtcc.com> wrote:

> How do I know when I'm done though if I don't know the IP addresses who
> send on my behalf? Is it an actual forgery or is it Marsha in marketing
> using a outsourced email blaster?
>

This is solved with conversation with the relevant stakeholders in the
organization from IT, Marketing, PR, etc... along with security and brand
policies being enforced.

Ultimately only approved and official email sources will be authenticated -
random sales/marketing people don't get to make those types of decisions on
the day-to-day. You want an exemption for your support/marketing tools you
need to get it cleared, vetted and properly authenticated to play.

This is how most large companies resolve this issue.

~
*MATTHEW VERNHOUT*
Founder, Editor
EmailKarma.net <http://ekma.co/16G2Htm>
It's not the size of your list, it's how you use it!

t: @emailkarma <https://twitter.com/EmailKarma>

--00000000000042ce3a05b9d3adc9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 26, 2021 at 3:17 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
 =20
   =20
 =20
  <div>
    <p>How do I know when I&#39;m done though if I don&#39;t know the IP
      addresses who send on my behalf? Is it an actual forgery or is it
      Marsha in marketing using a outsourced email blaster?</p></div></bloc=
kquote><div><br></div><div>This is solved with conversation with the releva=
nt stakeholders=C2=A0in the organization from IT, Marketing, PR, etc... alo=
ng with security and brand policies being enforced.=C2=A0</div><div><br></d=
iv><div>Ultimately only approved and official email sources will be authent=
icated - random sales/marketing people don&#39;t get to make those types of=
 decisions=C2=A0on the day-to-day. You want an exemption for your support/m=
arketing tools you need to get it cleared, vetted and properly authenticate=
d to play.=C2=A0</div><div><br></div><div>This is how most large companies =
resolve this issue.=C2=A0</div><div><br></div></div><div><div dir=3D"ltr" c=
lass=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr=
"><div dir=3D"ltr"><div dir=3D"ltr">~ <b><br>MATTHEW VERNHOUT</b><br>
Founder, Editor<br><a href=3D"http://ekma.co/16G2Htm" target=3D"_blank">Ema=
ilKarma.net</a><br>
It&#39;s not the size of your list, it&#39;s how you use it!<br><br>t<span>=
</span><span></span>: <a href=3D"https://twitter.com/EmailKarma" target=3D"=
_blank">@emailkarma</a></div></div></div></div></div></div>

--00000000000042ce3a05b9d3adc9--


From nobody Tue Jan 26 13:01:32 2021
Return-Path: <smj@crash.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 4A5563A0EA5 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.201
X-Spam-Level: 
X-Spam-Status: No, score=-0.201 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=crash.com
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 ZPw8ac5qzn-T for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:01:30 -0800 (PST)
Received: from segv.crash.com (segv.crash.com [IPv6:2001:470:1:1e9::4415]) (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 23C453A0EA1 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:01:30 -0800 (PST)
Received: from shiny.crash.com (192-184-141-33.static.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.7) with ESMTPSA id 10QL1Ipw034548 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dmarc@ietf.org>; Tue, 26 Jan 2021 21:01:26 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 10QL1Ipw034548
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1611694888; bh=HSzgelhbv+5AIpHw5Ff8wV2DVkGj660xvoqWn73FFfE=; h=Subject:To:References:From:Date:In-Reply-To; b=eJ01rznQ5ewrR7xzClguL+RwIJvPL4wrATLxLMEnPdmrTf0kUZnNuzDZvrQWmxOqF 2nbqzLbFJo1w8Gg9RMpuC+XKjbVuT1rb9nqY1MCFQEvb6c0qtZTXPu6l6nCXWsptjZ 5TR0ToR4ztMX/htP+9hujUidXVyuLVocTHoppmT6UqsgWeP+ouqDTh6glrkGvXk26J jlmLZnFt+BMfjYDVwJ3N/Vf/wSql9dv7LggWvahZHzO14EsXtQ7eyBMfWKH472jHxj 6aDw+PdQBxZBpivKvlmNAOahbFexjxY3QNqL6V23d6lVKZDzUaa+IBuxXRA7ESF6H2 16bgmbhsZ57tQ==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.static.sonic.net [192.184.141.33] claimed to be shiny.crash.com
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <858a8e94-0101-ab61-dfbd-d7d7dc07e69b@crash.com>
Date: Tue, 26 Jan 2021 13:01:18 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Tue, 26 Jan 2021 21:01:26 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VgQFCVPheTkWMqiUC2wDBk68cdU>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 21:01:31 -0000

On 1/26/21 11:24, Michael Thomas wrote:
>
> Here's a very basic question: if I do not know all of the IP addresses
> that send on my behalf, are DMARC reports of any value?
>
No, an organization is not assumed to have perfect knowledge of all
their authorized sending sources. If that were common, there would have
been much less need for DMARC in the first place.

One of the primary goals of DMARC (IMO) is to help organizations
identify sending sources that have to be /investigated/. Some may be
vendors who were engaged outside the normal email operational processes,
most are likely just transient spam sources. But you won't know which is
which until you at least take a cursory look.

All of which requires those DMARC aggregate reports, and benefits from
failure reports if you can get them -- and that the domain owner, or
somebody acting on their behalf, *examines* those reports.

Organizations using email should have at least some policies and
procedures that cover all these things - and that is a very large topic
that this isn't the right place to explore. 


> Enterprises farm out email all of the time and it could be difficult
> to know when they change their server addresses, etc.
>
Yes, which is part of why even organizations that have gone through a
long deployment process and arrived at their desired "end state" find
value in continuing to receive and monitor reports. As you touch on,
vendors don't always tell you about such changes in advance.

You have to examine reports and, from time to time, take some action.

--S.



From nobody Tue Jan 26 13:19:21 2021
Return-Path: <mike@fresheez.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 96D873A0EF1 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 zuD1PrhhAyei for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:19:19 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 811473A0EF0 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:19:19 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id r38so45258pgk.13 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:19:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=GQ1WaUdMCv/2rMET5IBAYfHyDnoVAitBVgYcBH3atYk=; b=LY7dac+BoqXrL4cKkRo22yzAmtNSDQFbrwIqwv6JRN38TtjOB6iWK5Pz0ayQf3aOu7 +OH1z6kOv+k2EX8ELSeQtw08ZMmZXVmWYXn9MEjFXlaAg01XnavczZm6BXt2Ss2EGiiV mNukWejqaCSslMsXk33a8RuqqOOQ7tSkRC8OXPxuNHCPqk8lu9dCB1G51GHjIT6g3qYf DUV39car9hgpSuAEFdeEqnN4+99afrm8Y3MEAq2ytQU/9hs7l1RklSgGPM2PcpfaOUBZ 5f+7sU7bbgdFguCYBMOkQtPAPs44p06ehe5V9HbI3guBB4Dy1RVIUdAT1NB6L5eCCbGX kfpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GQ1WaUdMCv/2rMET5IBAYfHyDnoVAitBVgYcBH3atYk=; b=Rg7h9g3FXyHiaWBagXdeP/FcJE7kLiFu+xPhkF8tk8hfSJk1E7BiLVJUUH/BA+0Avw +nIxTEEl2QO0BjxpSGn9sjEvTMMpHDB7tTgiBwP3Te/OKSk3CiFGyAA/gvKQcWJ/YG1g aQPIxE0hpKXN6GYClUuZ9TORR/iFUdWCrav46QJOYD4HS/qZ4ebegy5G9eGPF7zlLTn2 8xFTz9WQ7Xg6WVfGck5IRm3ibfpB2rd0489PAE0Ey5cNvYv9xjJ8SoxrwGF3Oxd5FLOA 0lOjDnf2gI4JfWaoqvchQ5IHFfZVvGuJqXm2oZJ+CRf1WjzRCBEIIZPQxKelpllp+LZt pKvA==
X-Gm-Message-State: AOAM530PpiLa1/6eFlJmYo0IgHNonKdcEzr7voiIo5RZWgi+hN81WsLq 6kle3owSJWb4K0m83mSfmUHkdMCuE4tAEA==
X-Google-Smtp-Source: ABdhPJwWbDQ5PjzFOr8+SUc+FqKkd9ivqs/k++Y6WXg0F78VrdGlNdun6GbF6S3ZhW8wG0kxTqNj1w==
X-Received: by 2002:a62:7896:0:b029:1b6:7319:52a7 with SMTP id t144-20020a6278960000b02901b6731952a7mr7419247pfc.30.1611695958459;  Tue, 26 Jan 2021 13:19:18 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id y22sm42198pfb.132.2021.01.26.13.19.17 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 13:19:17 -0800 (PST)
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com> <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com> <CAHej_8=jwMmMZLAUoKAXGgmn3va3R_nSYDgtM1U4ZG2s+uVz_Q@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <c05c4fb1-514c-7312-1d5e-cdcf5fba6267@mtcc.com>
Date: Tue, 26 Jan 2021 13:19:16 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8=jwMmMZLAUoKAXGgmn3va3R_nSYDgtM1U4ZG2s+uVz_Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------4A49B698C8EF3EF31E060311"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/swR6_PB6RRmqzm-tQPaFEYLKMuI>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 21:19:21 -0000

This is a multi-part message in MIME format.
--------------4A49B698C8EF3EF31E060311
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/26/21 12:29 PM, Todd Herr wrote:
> On Tue, Jan 26, 2021 at 3:16 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>     Yes, DMARC reports are of value if you don't know all of the IP
>     addresses that send on your behalf. Some have even written blog
>     posts on the topic of using DMARC aggregate reports as a tool to
>     audit one's authentication practices, by publishing a policy of
>     p=none, collecting the reports, analyzing the data, fixing
>     problems, iterate, iterate, iterate until one is ready to move on
>     to the ultimate goal of p=reject.
>>
>     How do I know when I'm done though if I don't know the IP
>     addresses who send on my behalf? Is it an actual forgery or is it
>     Marsha in marketing using a outsourced email blaster?
>
>
> Time.
>
> Some industry experts have suggested that one budget twelve to 
> eighteen months between first publishing a DMARC policy record and the 
> hoped-for transition to p=reject. YMMV, and a lot depends on the types 
> of messages that the organization sends, and their cadence. At the 
> extreme end of more than a year would be larger companies doing 
> seasonal or cyclical mailings, ones that maybe only market to certain 
> customer segments once or twice per year, tops. The more one knows 
> about one's mail flows and the better one's authentication practices 
> before deploying DMARC, the shorter that time can be, but a year or 
> more isn't unusual at all.
>
I don't see how time helps anything if I can't differentiate between our 
legitimate traffic and attacker traffic. All an attacker would need to 
do is send a mail cannon to mimic Marsha in Marketing every once in a 
while and the entire thing resets. If it is a requirement to know all of 
the legitimate IP addresses in order to make use of the reports as an 
indicator, the draft should be very explicit about that.

Mike


--------------4A49B698C8EF3EF31E060311
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/26/21 12:29 PM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8=jwMmMZLAUoKAXGgmn3va3R_nSYDgtM1U4ZG2s+uVz_Q@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Tue, Jan 26, 2021 at 3:16 PM Michael Thomas
          &lt;<a href="mailto:mike@mtcc.com" moz-do-not-send="true">mike@mtcc.com</a>&gt;
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>Yes, DMARC reports are of value if you don't know all
              of the IP addresses that send on your behalf. Some have
              even written blog posts on the topic of using DMARC
              aggregate reports as a tool to audit one's authentication
              practices, by publishing a policy of p=none, collecting
              the reports, analyzing the data, fixing problems, iterate,
              iterate, iterate until one is ready to move on to the
              ultimate goal of p=reject.
              <blockquote type="cite">
                <div dir="ltr">
                  <div class="gmail_quote"> <br>
                  </div>
                </div>
              </blockquote>
              <p>How do I know when I'm done though if I don't know the
                IP addresses who send on my behalf? Is it an actual
                forgery or is it Marsha in marketing using a outsourced
                email blaster?</p>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Time. </div>
          <div><br>
          </div>
          <div>Some industry experts have suggested that one budget
            twelve to eighteen months between first publishing a DMARC
            policy record and the hoped-for transition to p=reject.
            YMMV, and a lot depends on the types of messages that the
            organization sends, and their cadence. At the extreme end of
            more than a year would be larger companies doing seasonal or
            cyclical mailings, ones that maybe only market to certain
            customer segments once or twice per year, tops. The more one
            knows about one's mail flows and the better one's
            authentication practices before deploying DMARC, the shorter
            that time can be, but a year or more isn't unusual at all. </div>
        </div>
        <br>
      </div>
    </blockquote>
    <p>I don't see how time helps anything if I can't differentiate
      between our legitimate traffic and attacker traffic. All an
      attacker would need to do is send a mail cannon to mimic Marsha in
      Marketing every once in a while and the entire thing resets. If it
      is a requirement to know all of the legitimate IP addresses in
      order to make use of the reports as an indicator, the draft should
      be very explicit about that.</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------4A49B698C8EF3EF31E060311--


From nobody Tue Jan 26 13:24:27 2021
Return-Path: <mike@fresheez.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 197CB3A0F06 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:24:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 vVk6tIljnh8f for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:24:25 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01F5A3A0F01 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:24:24 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id j21so5880273pls.7 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:24:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=G0xgmb1Nb0AC0LXtVV+J/ZxbcIZckN7KhQ7F9u9jEJM=; b=gABV23axW1Sh0o0i/4C5qWNJ124t1/vMXRaFiThpUyzZZDfcoqPk8sfc54UifTE08n dumqT/lwhQlOi+Nt0ID0vbMksYjbjubpanmQF/e5uzwRosxVGsdGt/VZkCLVZnIOYZvt jLlX1iMIxs9sxnXVsNBifRoUdVN0NCIFzlW7kbswskrU2CH9zTK0OySGP3I6JuO5U7Ej /V0VVPp90XknRbUX98bEQ2XWv51XMFd/FkBDX0ZLmSXPYIz9GJ0TPWIPX7ZLcOAiGyu9 dbU2H9nB11pgGsyupq+LeRE5JZJZdypd1NTvo0aZyrm630P15JzRmWNJVDtQzcdrbu6Y YOlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=G0xgmb1Nb0AC0LXtVV+J/ZxbcIZckN7KhQ7F9u9jEJM=; b=pbTxifBW4E/rXp8DeKBGHnnyF5bY/dN0+L1anK3tcise9HR/i/PVED0Z3fsq53Ivru qOY8po5MzPdffHeR1kT81aa2svDe1+V+TDp4X4nefz9jAvVV/bSa2Snb/CXOUqaw0mtC 78KxmU0UgccEB6U2GHwTDW+/FyKJsiuWT2NWAdwaN6UnTrXhx8+H/ECE3glWr6J/vNtH /8sE+HRdTXlaYnftJrBgB1ZAJO0jixogBI34uA/ztIuKlSxFVFBiroF5qNsW7SPtjjdD 8hXrYEyL9lvoLa1Or3NoU7K/iBo4Y7bmQeoHqiK3JpZgZiOsn8lwXLTGNNWhKvClEbmc mzEg==
X-Gm-Message-State: AOAM532vZ1HtxU3188bXKVfY1hKLuez6z0E6tuBF755r7B2mPD8OeFhZ xKu7daQbK5vcHDVw1QuHmSTn6BGdnXI0KA==
X-Google-Smtp-Source: ABdhPJwafSEs70AbG4nvVyKvvz3d481BoOLluy0kIaadRlcx3HSV2/+Q+3KcLdOsu5lpD3+PsTwdNg==
X-Received: by 2002:a17:902:e98d:b029:de:9a3a:1b8d with SMTP id f13-20020a170902e98db02900de9a3a1b8dmr7897771plb.3.1611696263947;  Tue, 26 Jan 2021 13:24:23 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id y26sm20289149pgk.42.2021.01.26.13.24.22 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 13:24:23 -0800 (PST)
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com> <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com> <CAPyMsDi_tVK7j_HjpAfLEcy=xCDPR4kPZs-5MOFVkQSgCjwsuQ@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <3624ea12-b3cf-a8fe-9b4b-442931eaa080@mtcc.com>
Date: Tue, 26 Jan 2021 13:24:21 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAPyMsDi_tVK7j_HjpAfLEcy=xCDPR4kPZs-5MOFVkQSgCjwsuQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------87F5F6B2C71CD02FCB9AC43F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Yd6s-9yzQoE6C5j2LT45j9KUvF0>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 21:24:26 -0000

This is a multi-part message in MIME format.
--------------87F5F6B2C71CD02FCB9AC43F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/26/21 12:41 PM, Matt V wrote:
> On Tue, Jan 26, 2021 at 3:17 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>     How do I know when I'm done though if I don't know the IP
>     addresses who send on my behalf? Is it an actual forgery or is it
>     Marsha in marketing using a outsourced email blaster?
>
>
> This is solved with conversation with the relevant stakeholders in the 
> organization from IT, Marketing, PR, etc... along with security and 
> brand policies being enforced.
>
> Ultimately only approved and official email sources will be 
> authenticated - random sales/marketing people don't get to make those 
> types of decisions on the day-to-day. You want an exemption for your 
> support/marketing tools you need to get it cleared, vetted and 
> properly authenticated to play.
>
> This is how most large companies resolve this issue.
>
>
I worked for a large company and that is much easier said than done 
having attempted to do so before the reporting was a twinkle in 
anybody's eye. Hence the low uptake of DMARC. Having to know all of the 
IP addresses that are legitimate senders for your domain is daunting for 
a large enterprise.

Mike


--------------87F5F6B2C71CD02FCB9AC43F
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/26/21 12:41 PM, Matt V wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAPyMsDi_tVK7j_HjpAfLEcy=xCDPR4kPZs-5MOFVkQSgCjwsuQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Tue, Jan 26, 2021 at 3:17 PM Michael Thomas
          &lt;<a href="mailto:mike@mtcc.com" moz-do-not-send="true">mike@mtcc.com</a>&gt;
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p>How do I know when I'm done though if I don't know the
                IP addresses who send on my behalf? Is it an actual
                forgery or is it Marsha in marketing using a outsourced
                email blaster?</p>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>This is solved with conversation with the relevant
            stakeholders in the organization from IT, Marketing, PR,
            etc... along with security and brand policies being
            enforced. </div>
          <div><br>
          </div>
          <div>Ultimately only approved and official email sources will
            be authenticated - random sales/marketing people don't get
            to make those types of decisions on the day-to-day. You want
            an exemption for your support/marketing tools you need to
            get it cleared, vetted and properly authenticated to play. </div>
          <div><br>
          </div>
          <div>This is how most large companies resolve this issue. </div>
          <div><br>
          </div>
        </div>
        <br>
      </div>
    </blockquote>
    <p>I worked for a large company and that is much easier said than
      done having attempted to do so before the reporting was a twinkle
      in anybody's eye. Hence the low uptake of DMARC. Having to know
      all of the IP addresses that are legitimate senders for your
      domain is daunting for a large enterprise.<br>
    </p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------87F5F6B2C71CD02FCB9AC43F--


From nobody Tue Jan 26 13:30:42 2021
Return-Path: <mike@fresheez.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 27D7F3A0F4D for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 10tD2J0JMaXv for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:30:39 -0800 (PST)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D33F3A0F4A for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:30:38 -0800 (PST)
Received: by mail-pf1-x436.google.com with SMTP id 11so11235351pfu.4 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:30:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Zo2ug7beuc6ZnuEYmjayRIn+/mh3NPR4EymfBHHPxm8=; b=YIq4RzvcxXXCqrGrc6r2Kui3HkFPQPOb1oPibjQFJ6TIgmoHpld3eUSenGC0oKdryC id0Nkdjd2rwlL0KxU/lYUa+jRdpgB1afp0C0QBTZHsxzaT5QDKEwc6oXSU+exX2UwB1O +OgpI1T/RzR2ZXsciXSpiHXAHsFLSHShx4Anz40lnulptJyJ3rubX+wc7UEo7fXxGy9/ KqdOgNDt6ry920ZCIHTS1/SMSGedIAKLXzFE61nT5ObCTfLM/DJqYVJA5AC9ZqBKh45b XEeSesgzQV2C4KGjb4OOYR52f/Io6FqiiKz2i8GWyNk19HegVPJapS65NrGnBgPA6SwY Xwnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Zo2ug7beuc6ZnuEYmjayRIn+/mh3NPR4EymfBHHPxm8=; b=pMI2XCAfcay7sQX4HpvVuV5UaYsRwF+W1VDK3gdI8rzShqGOu8Yd9k4S9alxtWxhjC tqkvtzHXkR0BIdUDTGgUQOwDLhlXMOh9fWYX4Jdvfpr9yBYHv58ntxM3iGt1JUf+bjbK 8mo9pCohc8kfum6lra3QGMKzI5zpVTlQgaLL+SJfkBKUZgigHoiN9b/nMikm7Fx13TWn 98UrpD+PcdXtyIPPWu4IC34qodXLusot1KvvlrmFE5IhEzC3iL4hkBZE4Q+LdxwNVwAs CVzfCrNLxCRIfrhTskC7CWYxKnODA9vuef6Yza5m3wdql/jtM7sPKeHN7GtlFGAAZcts +g2A==
X-Gm-Message-State: AOAM532BT5RNf5e3ZOfVhar6BjiUw2ITc2gBA70ND2cNpMMhG+7FfOvF Z2UPOpUtU+XOzKc6BxUL8Et72bXbksiRgQ==
X-Google-Smtp-Source: ABdhPJx4LzjWsAbLh9KdcbtZCxhUyPYD6TgIZYQZc7eHgF+Ju3uq1wIKLRC8B3nn7rPyQnv9Jz5h5A==
X-Received: by 2002:a62:cd02:0:b029:1bc:9fe2:b00c with SMTP id o2-20020a62cd020000b02901bc9fe2b00cmr6997225pfg.23.1611696638138;  Tue, 26 Jan 2021 13:30:38 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id m77sm58318pfd.82.2021.01.26.13.30.37 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 13:30:37 -0800 (PST)
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <858a8e94-0101-ab61-dfbd-d7d7dc07e69b@crash.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <ef20883c-ab7d-45f6-b651-f426829b8a9b@mtcc.com>
Date: Tue, 26 Jan 2021 13:30:36 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <858a8e94-0101-ab61-dfbd-d7d7dc07e69b@crash.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/6OBadflzsavUkBDGzuut8Zg87aY>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 21:30:40 -0000

On 1/26/21 1:01 PM, Steven M Jones wrote:
> On 1/26/21 11:24, Michael Thomas wrote:
>> Here's a very basic question: if I do not know all of the IP addresses
>> that send on my behalf, are DMARC reports of any value?
>>
> No, an organization is not assumed to have perfect knowledge of all
> their authorized sending sources. If that were common, there would have
> been much less need for DMARC in the first place.

In order to move from p=none to p=reject it seems like you need to know 
that. One of the big advantages of DKIM is that you don't need to have 
know the network configuration of outsiders; you just add a selector for 
them. Not accommodating people who don't or can't know all of the 
legitimate IP addresses seems like a defect in the design/architecture 
of DMARC reporting, and leads to why it can be attacked in the way I 
described.

Mike


From nobody Tue Jan 26 13:38:34 2021
Return-Path: <mike@fresheez.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 223F93A0FB8 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:38:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 KVE_l6wmnLF9 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:38:31 -0800 (PST)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 201493A0FB6 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:38:31 -0800 (PST)
Received: by mail-pf1-x429.google.com with SMTP id f63so11228231pfa.13 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:38:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=GRO0xsT+pYapPBiuFp1LrjeNRgDVTTfooUquDDaBedw=; b=Z4zyiG65ysh5UzpbSlomlyaZVZ8D35KZfFkBgxEs3xNeE7PlU94SdufZmb89x6NtnX JGMRVD0vHAYeJPUpm9uJJ5hbaw2z59y7NgocEHbHgfLGW6HrQFOGKgjQPiL6ijPppLra GFOGkBXqkRSSSiMI1Vzo7AQltVsW5ug8vZoz6dj0d02+t32yNvnRiv6F4Ek7SZj6xjbS yB6PnSEG30mp9OrQWEju6djzLJnefD1Uu/cSwl7TimMt+VzN1S7BOmY+oCtZCBK0cmba 6/HtCysBn3ZH8+0VeYywUuLrf1KJro5eARraGSN01kfAT9PKFPn9TgjAn+ILfpphYArH Q5Kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=GRO0xsT+pYapPBiuFp1LrjeNRgDVTTfooUquDDaBedw=; b=VjS/LpS9EVHMHhUku5dusUB+VvyfHQb5LmljQwpBidO3XPOP2ak1qbMyJ0/d5daiPa w1/GhMUVzIijWHz8tR3ZnXQCaKQhhhzPTNmqSBJ/Rl9Vk0Lp8ByomGTC56XwPEwEbqIV 0AnUdSDTfVteCtcG4E4JIqeKJOJ8PXMTFRMT7MppZktYnOy3KpU/N44JwmF8Ej/ov5jN U25YW0KrIR6b3zGg9B7JJDcyX6NAoWO88d1S6cp3Tbi7d8m9Hbse6PaiJ0rHpeotytck 0pdPGGgtmd0F/dWJuT3kYfBse7XIJsx+7Gg2LEvMxYG+omV030+jcteHmzGJ6ghkP1Lt PAJQ==
X-Gm-Message-State: AOAM530VX8HSAJZj/NbZFuC+uldoV0AVfOibLaKcy4S+8QRvzCt/B6hu zzZ3W1MXhcdMY+anW6SSqWpDcQ5DeKcd3Q==
X-Google-Smtp-Source: ABdhPJxYfkWq/4VWY2g5fA0uf+j4afNjN+qQRhZDOe5ytEf1Xi95qhNuk2PPgjaVqtlJixG8oZ8Sjw==
X-Received: by 2002:a05:6a00:2305:b029:1b4:8368:13fd with SMTP id h5-20020a056a002305b02901b4836813fdmr7093594pfh.0.1611697110218;  Tue, 26 Jan 2021 13:38:30 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id fr1sm3069525pjb.7.2021.01.26.13.38.29 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 13:38:29 -0800 (PST)
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <858a8e94-0101-ab61-dfbd-d7d7dc07e69b@crash.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <b86779b3-5ea8-a389-228e-c42720e78167@mtcc.com>
Date: Tue, 26 Jan 2021 13:38:28 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <858a8e94-0101-ab61-dfbd-d7d7dc07e69b@crash.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/OI43fAGg-tZrwBe5QXa0KrDhiR4>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 21:38:32 -0000

[]

Ok, I think I understand this enough now to write a ticket.

Mike


From nobody Tue Jan 26 13:44:22 2021
Return-Path: <todd.herr@valimail.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 5D08F3A0FBB for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
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 YTByHu4dX3dQ for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 13:44:18 -0800 (PST)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 516DA3A0FB9 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:44:18 -0800 (PST)
Received: by mail-qt1-x82a.google.com with SMTP id v3so13426072qtw.4 for <dmarc@ietf.org>; Tue, 26 Jan 2021 13:44:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=MdWffKlNa9AuvWgHpmBxfQ9/Cv616//43OIi/8jGLKg=; b=HoAHyAlyovEXXj4qsnAATzydGJF3FU8JDzQa15FhnBddKzrWnILj17BQ5BUj+wRQJV efu+tL2wZEOvQqXozgo2ewz+lZ3+s1rJTV6VqBJwzBKJrHmxkbWlaNYLD4o03GLbI4gO pzG9vwDFFTxQnAL69p9tAFy95RqDCsjN5FYtZQO4cjmQQAq4CiclaZmqmsU5TKrSv6eq 2HfUGS0IlM6jNwd2rqB8w60yheUxeUxHN34X1mb6Y+kY7OH1qsyZtDbuBrWbyqGtm52m cnxDGQ9xTZT2bUm8nwcSsOZVgZLfQVHIQ7JZm5Y4cB2CXjTpLyN6EReNGjc/eeFhHEHS 7QKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=MdWffKlNa9AuvWgHpmBxfQ9/Cv616//43OIi/8jGLKg=; b=c1Mni+Pw9LPaOPtCyo7pYhKIk62ckZLTE5KzDJJx6P6PDdX6aHV0u3F9UtNKjF/VJQ FERLXkHueDkxqSDOvIGbjohfflbNSfMhJTqRrDYcGu6gVEfT+hFnxVsgdUuZBrXGBsYT GfLpu19Fl4a+zAeaL89P+XXDOK9mR1ob4b60gUkbxcAMZimKKpFjYz9IPwSPjRw/eveA I0wjXlVM95cUOX8LDVsHpY+QxBFvGW6KQbX6ktZjdLHkW5/2MNaxmQbPpyt74eierJXV aKBvZjE/iRuNKKHXe6brPOEZAxGPqvDJQHxopTjKzbPoFVwLzJzkm6cjwkhVET0AQbFs J2MA==
X-Gm-Message-State: AOAM532R+tHNmca/O+HX49Z3+5jMNpAEafuldrSCU55zXwncYJhAbrVY cDiikwUeLQla+ZdJhzv5tl6+HBLIpRFEOZUqVMke2GC8dU0=
X-Google-Smtp-Source: ABdhPJxaqTo652crL/PBlQ3k/Y4KZ3CKUewrWu21ykKizF8nmjFsPSEaN9yURM8pUaLZ1fX9ZiYiX7Z+kqLYvDBelIM=
X-Received: by 2002:ac8:4a82:: with SMTP id l2mr7273388qtq.298.1611697456787;  Tue, 26 Jan 2021 13:44:16 -0800 (PST)
MIME-Version: 1.0
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com> <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com> <CAHej_8=jwMmMZLAUoKAXGgmn3va3R_nSYDgtM1U4ZG2s+uVz_Q@mail.gmail.com> <c05c4fb1-514c-7312-1d5e-cdcf5fba6267@mtcc.com>
In-Reply-To: <c05c4fb1-514c-7312-1d5e-cdcf5fba6267@mtcc.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 26 Jan 2021 16:44:00 -0500
Message-ID: <CAHej_8kBj5XHqjKa6FfyP1YRVApiJT_LwSCZ9EneZOUfRZKE=w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000065d01705b9d48ea9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/5loxtGAsgg6PWMFs9dGXK-fwtks>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 21:44:20 -0000

--00000000000065d01705b9d48ea9
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 26, 2021 at 4:19 PM Michael Thomas <mike@mtcc.com> wrote:

> I don't see how time helps anything if I can't differentiate between our
> legitimate traffic and attacker traffic. All an attacker would need to do
> is send a mail cannon to mimic Marsha in Marketing every once in a while
> and the entire thing resets. If it is a requirement to know all of the
> legitimate IP addresses in order to make use of the reports as an
> indicator, the draft should be very explicit about that.
>
>
> Forgive me; I have failed to get my point across in a way that conveyed my
meaning. Let me try again.

My use of the word "Time" was intended to mean, effectively, "experience,
wisdom, and knowledge" all of which would be gained through regular (for me
it was daily) analysis of the latest DMARC aggregate reports. Through the
time spent analyzing those reports, one would obtain a fuller picture of
one's organization's mail flows, gaining a knowledge that can really only
come from immersion in the data.

Once one gets past the first few weeks of the exercise, picking off any
low-hanging fruit, then one settles into a posture of monitoring for
anomalies, expecting to see no failures, and quickly addressing those that
need to be addressed.

At some point, one that is wholly dependent on the complexity of the
infrastructure and the personality of the observer, one becomes comfortable
enough with the data to confidently say, "Now is the time to move to
p=reject" and one makes the move.

After that, there's continued monitoring to make sure that no ill effects
have occurred due to the move, of course, and if there's need to roll back,
one rolls back.

If you're looking for an objective standard by which one can say "If X,
then it is safe to move to p=reject", there really isn't one, save for "If
the domain is newly registered and has never sent mail, then it is safe to
move to p=reject." For any domain that has sent mail prior to the
publishing of a DMARC record, then it's publish, monitor, iterate until one
is ready, and the only standard for that is "When you know, you know."

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.

--00000000000065d01705b9d48ea9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 26, 2021 at 4:19 PM Michael T=
homas &lt;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div><blockquote type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail=
_quote">
        </div>
       =20
      </div>
    </blockquote>
    <p>I don&#39;t see how time helps anything if I can&#39;t differentiate
      between our legitimate traffic and attacker traffic. All an
      attacker would need to do is send a mail cannon to mimic Marsha in
      Marketing every once in a while and the entire thing resets. If it
      is a requirement to know all of the legitimate IP addresses in
      order to make use of the reports as an indicator, the draft should
      be very explicit about that.</p>
    <p><br></p></div></blockquote><div>Forgive me; I have failed to get my =
point across in a way that conveyed my meaning. Let me try again.</div><div=
><br></div><div>My use of the word &quot;Time&quot; was intended to mean, e=
ffectively, &quot;experience, wisdom, and knowledge&quot; all of which woul=
d be gained through regular (for me it was daily) analysis of the latest DM=
ARC aggregate reports. Through the time spent analyzing those reports, one =
would obtain a fuller picture of one&#39;s organization&#39;s mail flows, g=
aining a knowledge that can really only come from immersion in the data.=C2=
=A0</div><div><br></div><div>Once one gets past the first few weeks of the =
exercise, picking off any low-hanging fruit, then one settles into a postur=
e of monitoring for anomalies, expecting to see no failures, and quickly ad=
dressing those that need to be addressed.</div><div><br></div><div>At some =
point, one that is wholly dependent on the complexity of the infrastructure=
 and the personality of the observer, one becomes comfortable enough with t=
he data to confidently say, &quot;Now is the time to move to p=3Dreject&quo=
t; and one makes the move.</div><div><br></div><div>After that, there&#39;s=
 continued monitoring to make sure that no ill effects have occurred due to=
 the move, of course, and if there&#39;s need to roll back, one rolls back.=
</div><div><br></div><div>If you&#39;re looking for an objective standard b=
y which one can say &quot;If X, then it is safe to move to p=3Dreject&quot;=
, there really isn&#39;t one, save for &quot;If the domain is newly registe=
red and has never sent mail, then it is safe to move to p=3Dreject.&quot; F=
or any domain that has sent mail prior to the publishing of a DMARC record,=
 then it&#39;s publish, monitor, iterate until one is ready, and the only s=
tandard for that is &quot;When you know, you know.&quot;</div><div>=C2=A0</=
div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p dir=3D=
"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div=
 style=3D"text-align:left"><span style=3D"vertical-align:baseline;white-spa=
ce:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span=
 style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font=
-family:Arial"> | Sr. Technical Program Manager</span></div><span style=3D"=
vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Ar=
ial"><div style=3D"text-align:left"><span style=3D"vertical-align:baseline"=
><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=3D"mailto=
:todd.herr@valimail.com" target=3D"_blank">todd.herr@valimail.com</a></span=
></div></span><span><div><span><b>p:</b></span><span> 703.220.4153 </span><=
span></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-f=
amily:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,2=
55,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"f=
ont-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transpare=
nt;vertical-align:baseline;white-space:pre-wrap"><img src=3D"https://lh5.go=
ogleusercontent.com/_vs__6iRjfmT2Ae5LLNBb8nEopl2M5Tl5QlpS6LS0Lh0vv4TYnZu-Mf=
f2kDFOqe0LhbnSXprAx4yoaTvq_Tc_7n1b8yzGIqoxuhedthDxYQansg8ChT2x5EcZV3rjz19-D=
x9rESL" style=3D"border: none; height: 40px; width: 177px;"></span></p><p d=
ir=3D"ltr" style=3D"color:rgb(34,34,34);font-family:Arial,Helvetica,sans-se=
rif;font-size:small;background-color:rgb(255,255,255);line-height:1.38;marg=
in-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"background-co=
lor:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><fo=
nt color=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px;whit=
e-space:pre-wrap">This email and all data transmitted with it contains conf=
idential and/or proprietary information intended solely for the use of indi=
vidual(s) authorized to receive it. If you are not an intended and authoriz=
ed recipient you are hereby notified of any use, disclosure, copying or dis=
tribution of the information included in this transmission is prohibited an=
d may be unlawful. Please immediately notify the sender by replying to this=
 email and then delete it from your system.</span></font></p></span></div><=
/div>

--00000000000065d01705b9d48ea9--


From nobody Tue Jan 26 14:15:13 2021
Return-Path: <mike@fresheez.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 8AC7C3A02BC for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 14:15:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.15
X-Spam-Level: 
X-Spam-Status: No, score=0.15 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 6XHTQ5fd2yT5 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 14:15:09 -0800 (PST)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42F763A017E for <dmarc@ietf.org>; Tue, 26 Jan 2021 14:15:09 -0800 (PST)
Received: by mail-pj1-x1032.google.com with SMTP id jx18so57813pjb.5 for <dmarc@ietf.org>; Tue, 26 Jan 2021 14:15:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=IkWzad5KR+hgPTgMGpbEYDmX7+btf8W7YbuhfRQUVK4=; b=jVTs6I4NuRi2Y2/Yl0TzBvgYii1BcjLw8o4mh7Nv3WCPnj5TVMv+FkJfYGp+yPkxkx j10X8G5ydsFvenF9pfCBDayAPoNmmZdSjwC1lslFZssXRo7wn++dceiIetJQ9fpQt39u 4r+vYnQa650eF5Amz8Agx5pdBv2CevKELUYRk2unpmKIkzjAw6I1pX9RuWJGfp1tvOay mY0+T27F+1mxUaByld/nRQf8kCrsCrDtANMzlhg3L9Bg1Elu6/fVHefQi2sh5szwDP3v QzU5VCIA7tkKWqbJPL/pARPBnHHQwXUI75nJP+mBJhchvbsBh2CFDx6gZnOXGzpzmobf DJ+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=IkWzad5KR+hgPTgMGpbEYDmX7+btf8W7YbuhfRQUVK4=; b=Fk2EWPRyaWNt2bPGt+2BF/nMDPRAewL+8xenGoGK8qZ1bKHQePmRf3unXL7PsBrqbN lM7hDF9Nzg8UU8m4a/0ahFoAk8APwqgiP1BsJOt3xMLGiP8WU2bWoe1/DyNoaWDp1MuN lxjIy1jpGM9MD9CVEQJaEvNeurHL4SM3qXg/KzYQsoxF2T1OTxPlKwjJ72Xmb9TXOz2/ sghZAteG28VeJHMkJBc0IQ8YDwqF44IJAIGKY4AbgpfWLEXujv/NKBqb0Mds7SNz63JH hJ+OPbSQiHgrregg8p9ITpMSsbr5noWjyasJBUCVlaQWxFBa/27hreP8Zemnx4EwxuSw z7gg==
X-Gm-Message-State: AOAM532iWXUg/nlO2s+jnPNfbMUhfOh234hEA9c6CaS2oHp+Gf2xMOKq DOOgme9Ye4dR9am3kxS2zLb7KMjjMPLx1Q==
X-Google-Smtp-Source: ABdhPJxKVMDaRbZ/2oDubsRgIYMT6erhOD/jrAhtWTs7AYSAwAK9zO8iH/khTkmUDoBTLIn7A2Bk8g==
X-Received: by 2002:a17:902:7148:b029:df:f45d:41c9 with SMTP id u8-20020a1709027148b02900dff45d41c9mr8262711plm.3.1611699308051;  Tue, 26 Jan 2021 14:15:08 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id a141sm92522pfa.189.2021.01.26.14.15.07 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jan 2021 14:15:07 -0800 (PST)
To: dmarc@ietf.org
References: <c049495f-faa2-c5f0-3e0a-7d8d86150568@mtcc.com> <aab313ee-4453-d97c-65ad-2a02d543c66c@tana.it> <24e8da5d-e306-7207-bb8f-74d44e4c5eaf@mtcc.com> <CAHej_8kS7hHR70LdcktuEtm08FyjsmqV17wHq21MdT=eNspCGw@mail.gmail.com> <f8f77f85-a2ae-3fb3-acb4-70d14a9da0f4@mtcc.com> <CAHej_8nZu3Fgj1=V8aQnho7LEc0Y12KfXa8b+xxXVDzDqe8Bxg@mail.gmail.com> <d181379e-8a3d-2865-53ca-709f679945ac@mtcc.com> <CAHej_8=jwMmMZLAUoKAXGgmn3va3R_nSYDgtM1U4ZG2s+uVz_Q@mail.gmail.com> <c05c4fb1-514c-7312-1d5e-cdcf5fba6267@mtcc.com> <CAHej_8kBj5XHqjKa6FfyP1YRVApiJT_LwSCZ9EneZOUfRZKE=w@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <81e96be0-989a-ac75-b6e2-3381d971e019@mtcc.com>
Date: Tue, 26 Jan 2021 14:15:06 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8kBj5XHqjKa6FfyP1YRVApiJT_LwSCZ9EneZOUfRZKE=w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------CD33CD99EFD92526A500AE2E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/f7TB6DIHMnQlaey9R5JwnUBBPHU>
Subject: Re: [dmarc-ietf] attack on reports
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, 26 Jan 2021 22:15:11 -0000

This is a multi-part message in MIME format.
--------------CD33CD99EFD92526A500AE2E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/26/21 1:44 PM, Todd Herr wrote:
> On Tue, Jan 26, 2021 at 4:19 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>     I don't see how time helps anything if I can't differentiate
>     between our legitimate traffic and attacker traffic. All an
>     attacker would need to do is send a mail cannon to mimic Marsha in
>     Marketing every once in a while and the entire thing resets. If it
>     is a requirement to know all of the legitimate IP addresses in
>     order to make use of the reports as an indicator, the draft should
>     be very explicit about that.
>
>
> Forgive me; I have failed to get my point across in a way that 
> conveyed my meaning. Let me try again.
>
> My use of the word "Time" was intended to mean, effectively, 
> "experience, wisdom, and knowledge" all of which would be gained 
> through regular (for me it was daily) analysis of the latest DMARC 
> aggregate reports. Through the time spent analyzing those reports, one 
> would obtain a fuller picture of one's organization's mail flows, 
> gaining a knowledge that can really only come from immersion in the data.
>
>
I have written this up and it is now issue #101.

Mike


--------------CD33CD99EFD92526A500AE2E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/26/21 1:44 PM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8kBj5XHqjKa6FfyP1YRVApiJT_LwSCZ9EneZOUfRZKE=w@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Tue, Jan 26, 2021 at 4:19 PM Michael Thomas
          &lt;<a href="mailto:mike@mtcc.com" moz-do-not-send="true">mike@mtcc.com</a>&gt;
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type="cite">
                <div dir="ltr">
                  <div class="gmail_quote"> </div>
                </div>
              </blockquote>
              <p>I don't see how time helps anything if I can't
                differentiate between our legitimate traffic and
                attacker traffic. All an attacker would need to do is
                send a mail cannon to mimic Marsha in Marketing every
                once in a while and the entire thing resets. If it is a
                requirement to know all of the legitimate IP addresses
                in order to make use of the reports as an indicator, the
                draft should be very explicit about that.</p>
              <p><br>
              </p>
            </div>
          </blockquote>
          <div>Forgive me; I have failed to get my point across in a way
            that conveyed my meaning. Let me try again.</div>
          <div><br>
          </div>
          <div>My use of the word "Time" was intended to mean,
            effectively, "experience, wisdom, and knowledge" all of
            which would be gained through regular (for me it was daily)
            analysis of the latest DMARC aggregate reports. Through the
            time spent analyzing those reports, one would obtain a
            fuller picture of one's organization's mail flows, gaining a
            knowledge that can really only come from immersion in the
            data. </div>
          <div><br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>I have written this up and it is now issue #101.</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------CD33CD99EFD92526A500AE2E--


From nobody Tue Jan 26 14:36:24 2021
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 A0B7A3A0A5E for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 14:36:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_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=H6Uk+8lC; dkim=pass (2048-bit key) header.d=kitterman.com header.b=dfbJpZ9+
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 D2v5FlLU9wpI for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 14:36:21 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25B3A3A0A3B for <dmarc@ietf.org>; Tue, 26 Jan 2021 14:36:20 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id B6995F801F9 for <dmarc@ietf.org>; Tue, 26 Jan 2021 17:36:19 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1611700579; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=qXKHpTMv36TXnTou14fe1Yq5eWHCR06X0hJq6hgn8Uo=; b=H6Uk+8lCF78KaxzmgPRaZuddfWMnvWt0J4PNrJpXe/0w5SPMMKtc4gz9JxYLym/6vtjVR lWNr4bV9BnVUdjbBg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1611700579; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=qXKHpTMv36TXnTou14fe1Yq5eWHCR06X0hJq6hgn8Uo=; b=dfbJpZ9+neSDHxy5rG2NgYNHlYmHnYbynhT2vFtQXiOKdHg7v800mi7xYXXfDmb0hI29s cWsKMeBbmJmMnsU30Alp/xFpAUbXYlwTT0QibMKD9i84nmP1J4UA3PcABT5czID97yKlEtn G0OU90p3B8GR2sF3Iv5IgkWcITsFnDuugAS4Y2JF/etQgXWGhFuesJZIyimmor5okKXD/6p eoP+grZogRU6DaIMIbwFrC6kfeNDtJr+sYvwSgYLV+LLVhF+kw6fyrsOuOqXHt3wIlUeL7M wmNxSSA4kJLfqTnq2C538AhFvAEiP3FEmi5YZOoSrJ+AStpiGI2Sl1oieW+g==
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 825AAF80052 for <dmarc@ietf.org>; Tue, 26 Jan 2021 17:36:19 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Tue, 26 Jan 2021 17:36:19 -0500
Message-ID: <1655426.E2olI3CrJK@zini-1880>
In-Reply-To: <3ed1bd47-43e9-3260-b2fe-567c967eede2@tana.it>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1859075.lZWC7Mh21l@zini-1880> <3ed1bd47-43e9-3260-b2fe-567c967eede2@tana.it>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/TZxs-XYagma9legYySanjsXglIg>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 26 Jan 2021 22:36:23 -0000

On Tuesday, January 26, 2021 11:47:51 AM EST Alessandro Vesely wrote:
> On Tue 26/Jan/2021 14:14:45 +0100 Scott Kitterman wrote:
> > On Tuesday, January 26, 2021 6:54:56 AM EST Alessandro Vesely wrote:
> >> On Mon 25/Jan/2021 22:35:09 +0100 Scott Kitterman wrote:
> >>> On Monday, January 25, 2021 4:04:33 PM EST Todd Herr wrote:
> >>>> May I propose that the section labeled "SPF-Authenticated Identifiers"
> >>>> be
> >>>> rewritten as follows:
> >>>> 
> >>>> [...]
> >>>> 
> >>>>    The reader should note that SPF alignment checks in DMARC rely
> >>>>    solely
> >>>>    on the RFC5321.MailFrom domain. This differs from section 2.3 of
> >>>>    [@!RFC7208], which recommends that SPF checks be done on not only
> >>>>    the
> >>>>    "MAIL FROM" but also on a separate check of the "HELO" identity. >
> >>> 
> >>> I think this is fine, but there is a subtlety to be aware of.
> >>> 
> >>> If you look at RFC 7208 Section 2.4, when Mail From is null,
> >>> postmaster@HELO is the mail from for SPF purposes.  DMARC really can't
> >>> change that.
> >>> 
> >>> As a result, there are cases where Mail From results actually are
> >>> derived
> >>> from HELO and it's unavoidable.
> >> 
> >> I doubt that SPF filters report envelope-from=postmaster@HELO; more
> >> likely
> >> they write helo=HELO.  In that case, the paragraph quoted above is
> >> deceptive.
> >> 
> >>> I believe the proposed text is clear enough about not using separate
> >>> HELO
> >>> identity results and that's appropriate.
> >> 
> >> My filter collects SPF results recorded from an upstream SPF filter.  It
> >> writes Received-SPF: lines for each identity.  For NDNs, it writes a
> >> Received-SPF: for the HELO identity only.  Am I allowed to use that
> >> result
> >> for DMARC?
> > 
> > No.  You should only use Mail From results.
> 
> So NDNs having only an aligned HELO will never pass DMARC?
> 
> And what is a <scope>helo</scope> element in aggregate reports provided for?
> 
> The spec says:
> 
>           [SPF] can authenticate either the domain that appears in the
>     RFC5321.MailFrom (MAIL FROM) portion of [SMTP] or the RFC5321.EHLO/
>     HELO domain, or both.
> 
> And then:
> 
>     In relaxed mode, the [SPF]-authenticated domain and RFC5322.From
>     domain must have the same Organizational Domain.  In strict mode,
>     only an exact DNS domain match is considered to produce Identifier
>     Alignment.
> 
> So, consider the following message without DKIM signatures:
> 
> HELO example.org
> MAIL FROM:<user@example.com>
> 
> Received-SPF: pass (domain example.org
>    designates 192.0.2.1 as permitted sender)
>    identity=helo; helo=example.org;
> Received-SPF: fail (domain of user@example.com
>    denies 192.0.2.1 as permitted sender)
>    identity=mailfrom; envelope-from="user@example.com";
> Subject: Not using a mail client for this example
> From: different-user@example.org
> 
> Does it pass DMARC?

No.

Scott K




From nobody Tue Jan 26 17:50:09 2021
Return-Path: <dougfoster.emailstandards@gmail.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 99CD03A1008 for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 17:50:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Hy9C3kcCgO0l for <dmarc@ietfa.amsl.com>; Tue, 26 Jan 2021 17:50:06 -0800 (PST)
Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BF363A1007 for <dmarc@ietf.org>; Tue, 26 Jan 2021 17:50:06 -0800 (PST)
Received: by mail-ua1-x930.google.com with SMTP id t43so213830uad.7 for <dmarc@ietf.org>; Tue, 26 Jan 2021 17:50:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=x87fpNcDEPMy+n/FEfbnF52eqfYXPI57LcpRixKNXF4=; b=OxmKJq8ib/k9x92+FLjt6izb5KNcG5Zrl7Mf9Mf6dnm4BR5PCsFXEo4GQhI4XgLFam IvliQZzpfTkOpxXcQLGIhW+B5rUrKalPHBm/nE16LEYQMX4jZVwA6uiMdZ8H890QNANL 5Em8U/gcapsZAiRilCjqZFsDAOLdLHplwzSzj726hddvzzIPTPhdv+WgAjUmLE/ur4OW ugryXm2PNmwuO5shNThEqXiWRSB3/f+151T2dYBPhqGmgyUeJ5fyqbzr96fgLciJLFgq E7/AGIR77etUebUTm2nEWfGvgzlYSj/7L7RIq60Hi2JriX+/v6ysKUieNvtzP2vyaH1o 4ffw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=x87fpNcDEPMy+n/FEfbnF52eqfYXPI57LcpRixKNXF4=; b=BgD6wpv30C2CHKNNc9zQtU6WSsPlvNVCP1f927XW7qvBnMPVpw1xzAAyyFDwhphKrg si7P8EVRL4MpH+ZMDq19kVocIctNZ+0y7deVhbXDH1Y+ueo5Fo83CvCE8x0/bmy0jMUb BL+1bsZxMC8y+utSxVQwirFx61iXarE9E8OWHrVYG61fyRxMhbAiuO+h04PD9/schD5L VU9KZkuRANVgtCMQis3ZcdtRsa1FNk1YwzQVLnLZd7rHgMlZxsj016gnHv/i+ZsQGTUX Yoapx/HV3RK8Eqmp6tY3AyT/JB812Li8BraEEM2HicQnCTy1ssspY/AcqNFcFexLeudw nNGA==
X-Gm-Message-State: AOAM533C77I7sLmGYQ+XGbhCOuyUjWtg7kpqGDkJe48JyVgsQIk1MtHR RKnyr5MtLsWNc0XP5zOW/occsv6EdijMFyLUqarQqU5P
X-Google-Smtp-Source: ABdhPJzPYPFV6ArKeLlmOGkAFSQlARt1sN8puksCuhHnUA6OIl3LFIoFt2HbiijuONQxpiaYT4X7s1Gm90kmnFJHKFU=
X-Received: by 2002:ab0:3043:: with SMTP id x3mr6744434ual.88.1611712205425; Tue, 26 Jan 2021 17:50:05 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it> <CAH48ZfwvBj3abrAEz1uK2UNyMOBAM1q3pH8cOmazn8VBow3ACQ@mail.gmail.com> <adcede1d-a260-7b78-9439-63eb706989e2@tana.it> <CAH48ZfyOe2PkkAZ5yPqb3wP=WctnRMBLqt2bmyj_p7gd6nmRxQ@mail.gmail.com> <5d1a5c1f-99a5-37ac-4177-a995c71c4e42@tana.it>
In-Reply-To: <5d1a5c1f-99a5-37ac-4177-a995c71c4e42@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 26 Jan 2021 20:49:52 -0500
Message-ID: <CAH48Zfy4xiaZ_7uo8rKyU7NJF2EpdK6A1UfV6CeB4s1pL6fwuQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007c119605b9d7fde2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZizryHXH7hB0RpJ5b_ggRAcOVe8>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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: Wed, 27 Jan 2021 01:50:08 -0000

--0000000000007c119605b9d7fde2
Content-Type: text/plain; charset="UTF-8"

For indirect mail, the aligned
signature selector tells you where to look for the message origin. The last
hop information tells you where it ended up.

For direct messages, the last hop tells you whether it came from a third
party or internal server, and the aligned signature selector confirms the
same.

In both cases,, verification is secondary, because it mostly indicates
whether the message was modified in transit.

Last hop and aligned selector still seems like a sufficient data set to me.

In fact, asking for extra signatures seems like a backhanded way of trying
to infer the original recipient, but supposedly the recipient is irrevant.

Remember that we are asking systems to collect data for others that they do
not need for themselves.   This is not the place to ask for the moon.

Maybe the massive organizations collect enough data so that the rest of us
do not need to participate.  If so, ask for anything, as the request will
probably not inconvenience them.

Doug Foster

--0000000000007c119605b9d7fde2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>For indirect mail, the aligned</div><div dir=3D"auto=
">signature selector tells you where to look for the message origin. The la=
st hop information tells you where it ended up.</div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">For direct messages, the last hop tells you whether=
 it came from a third party or internal server, and the aligned signature s=
elector confirms the same.</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">In both cases,, verification is secondary, because it mostly indicates w=
hether the message was modified in transit.=C2=A0=C2=A0</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Last hop and aligned selector still seems l=
ike a sufficient data set to me.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">In fact, asking for extra signatures seems like a backhanded way =
of trying to infer the original recipient, but supposedly the recipient is =
irrevant.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Remember that =
we are asking systems to collect data for others that they do not need for =
themselves.=C2=A0 =C2=A0This is not the place to ask for the moon.=C2=A0=C2=
=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Maybe the massive or=
ganizations collect enough data so that the rest of us do not need to parti=
cipate.=C2=A0 If so, ask for anything, as the request will probably not inc=
onvenience them.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Doug Fo=
ster</div><div dir=3D"auto"><div class=3D"gmail_quote" dir=3D"auto"><div di=
r=3D"ltr" class=3D"gmail_attr"><br></div></div></div></div>

--0000000000007c119605b9d7fde2--


From nobody Wed Jan 27 01:49:07 2021
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 DF76E3A0652 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 01:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 1NB9RxhUk_J8 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 01:49:05 -0800 (PST)
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 691EA3A0C4C for <dmarc@ietf.org>; Wed, 27 Jan 2021 01:49:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611740943; bh=bqOGGENUggyHmybo066Xqrbaqihwd0lJRP1gbZGRo+U=; l=2262; h=To:References:From:Date:In-Reply-To; b=DLqNYEn3nLgNseT6VjQ8pQMDOF8GsffnYWN18DIH2VvkKmMKSwdVSzGgVi8ePHF0u qhokCB+07bZ9NAPp12j5o82IbHR4vkzlEUJZXpWEGefI9biHi5Zh6rq/rHwfmloc+X XpIARfnP313urgDYqTSn+G+ShNXfvfpbpbzunk/ro2m5aimCGFFoQ0UDidp4W
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC09F.000000006011370F.00001E10; Wed, 27 Jan 2021 10:49:03 +0100
To: dmarc@ietf.org
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1859075.lZWC7Mh21l@zini-1880> <3ed1bd47-43e9-3260-b2fe-567c967eede2@tana.it> <1655426.E2olI3CrJK@zini-1880>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it>
Date: Wed, 27 Jan 2021 10:49:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <1655426.E2olI3CrJK@zini-1880>
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/FY14MkuV-q5OUpvFkw07MA1x_zM>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Wed, 27 Jan 2021 09:49:07 -0000

On Tue 26/Jan/2021 23:36:19 +0100 Scott Kitterman wrote:
> On Tuesday, January 26, 2021 11:47:51 AM EST Alessandro Vesely wrote:
>> On Tue 26/Jan/2021 14:14:45 +0100 Scott Kitterman wrote:
>>> On Tuesday, January 26, 2021 6:54:56 AM EST Alessandro Vesely wrote:
>>>> 
>>>> I doubt that SPF filters report envelope-from=postmaster@HELO; more 
>>>> likely they write helo=HELO.  In that case, the paragraph quoted above
>>>> is deceptive. >>>>
>>>>> I believe the proposed text is clear enough about not using
>>>>> separate HELO identity results and that's appropriate. >>>>
>>>> My filter collects SPF results recorded from an upstream SPF filter.
>>>> It writes Received-SPF: lines for each identity.  For NDNs, it writes
>>>> a Received-SPF: for the HELO identity only.  Am I allowed to use that 
>>>> result for DMARC? >>>
>>> No.  You should only use Mail From results.
>> 
>> So NDNs having only an aligned HELO will never pass DMARC?
>> 
>> And what is a <scope>helo</scope> element in aggregate reports provided for?
>> 
>> The spec says:
>> 
>>           [SPF] can authenticate either the domain that appears in the
>>     RFC5321.MailFrom (MAIL FROM) portion of [SMTP] or the RFC5321.EHLO/
>>     HELO domain, or both.
>> 
>> And then:
>> 
>>     In relaxed mode, the [SPF]-authenticated domain and RFC5322.From
>>     domain must have the same Organizational Domain.  In strict mode,
>>     only an exact DNS domain match is considered to produce Identifier
>>     Alignment.
>> 
>> So, consider the following message without DKIM signatures:
>> 
>> HELO example.org
>> MAIL FROM:<user@example.com>
>> 
>> Received-SPF: pass (domain example.org
>>    designates 192.0.2.1 as permitted sender)
>>    identity=helo; helo=example.org;
>> Received-SPF: fail (domain of user@example.com
>>    denies 192.0.2.1 as permitted sender)
>>    identity=mailfrom; envelope-from="user@example.com";
>> Subject: Not using a mail client for this example
>> From: different-user@example.org
>> 
>> Does it pass DMARC?
> 
> No.


Let's not be silly, Scott.  We have example.org as the SPF-authenticated domain 
and it is aligned with From:.  Are you saying that the message would pass if it 
had an empty bounce address, but since it can bounce it does not pass?!?


Best
Ale
-- 























From nobody Wed Jan 27 02:41:54 2021
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 9E4C43A0D50 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 02:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 SZJ_IOIto8pK for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 02:41:51 -0800 (PST)
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 134343A0D44 for <dmarc@ietf.org>; Wed, 27 Jan 2021 02:41:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611744107; bh=Rpf5kzED1802NdOrDnK+05zBBclyVNy0ASDMIRpT2j4=; l=894; h=To:References:From:Date:In-Reply-To; b=AoqOcWje3wLyZXLvb5nzjSfNvKrkpVNgYVhaz6x7wTLITElhHoMKk8b/DeL5aMba9 Ply7MkFrpLPK+bcb6kDpQWcBoSbx0Sd2YQBN23q6QsbI6ttYEVi0eVwMonElGAwuYD DsV0viH2YHv5w7n9BUoH1alJjacju9gk30hSIhYfQC2inQtYpAr03n4IXx0W5
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.000000006011436B.0000239E; Wed, 27 Jan 2021 11:41:47 +0100
To: dmarc@ietf.org
References: <71342cc2-9f87-89e4-42f1-1d617ee71f80@mtcc.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <6e4e3091-743d-570c-2cf9-459fea115d01@tana.it>
Date: Wed, 27 Jan 2021 11:41:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <71342cc2-9f87-89e4-42f1-1d617ee71f80@mtcc.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/XgeFVCLw-D_U4Yo-zMS7aaUCEfo>
Subject: Re: [dmarc-ietf] nit in section 7.2
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: Wed, 27 Jan 2021 10:41:53 -0000

On Tue 26/Jan/2021 19:58:36 +0100 Michael Thomas wrote:
> "The report SHOULD include the following data:"
> 
> Normative SHOULD here since very strange because what follows is informational, 
> and why would it be SHOULD in the first place?
> 
> It seems to me it ought to be:
> 
> "The report includes the following data:"


That list looks like a leftover from an earlier phase of analysis.

Alex added up-to-date descriptive text, which is going to complement or replace that list.  Let's refine that for version -02:
https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-aggregate-reporting/blob/main/draft-ietf-dmarc-aggregate-reporting.md#user-content-aggregate-reports


> If there are normative requirements, it seems like it would be better to put it 
> into the XML section itself.


The semantic of each field, however, is more readable in plain text.


Best
Ale
-- 
















From nobody Wed Jan 27 03:32:06 2021
Return-Path: <dougfoster.emailstandards@gmail.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 63F053A0E60 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 03:32:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gFup6ZcFyMCn for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 03:32:03 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFC7A3A0E5D for <dmarc@ietf.org>; Wed, 27 Jan 2021 03:32:02 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id o125so943878vsc.6 for <dmarc@ietf.org>; Wed, 27 Jan 2021 03:32:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=HV3REaRzWcZS8vBQKRCsdlFDooSgbatrkl2bGtQIKSQ=; b=MukkDdKHmIsDjfM3YG62FGMY/sc9qMpGYdyVnIAwAnB1gvEfWXanNLpu/0nCjmedvv zGh3h8cZhAmcZD7t4uzqaCF2q9UlQxGUhmXnPtL8JlrVWeHdUDSC+HXNfqPnPpcx3cB8 6jWt8pE9PEuid7zXKgODa+dxrVt7eQzOAuzdt/44hmDsKLpayIxVjujhW7CDK/8bvGxj p+O38TmOKm3udlFq7Mo1//2uRBKPxkaw86keMhgmYdEWllpK3J8JnP4nJoVVUZKX77lk nl5tOn6GZZZ5jiZbIFRvRpHFO5jjQf7VIrcso/Wq7xRkYmTGZmhGVFYpW5jzPMEpk2Ru pSGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=HV3REaRzWcZS8vBQKRCsdlFDooSgbatrkl2bGtQIKSQ=; b=rVzlqaglP6kkTlI6x05owN2g7N8D5Oupl4y4pBG+ooo/3+M5pP0e4KfPuCkf2fJ3DM fOxeVt6F6A5JM1jW0SMVgpWr0aCRTF7C9GZk0mvfSEAxx/KWEoKhYCmzZ4HYrzr95Ge9 krxNTnaVgum3b87U19nki8b+5U/B5J0YRrC9Z5YvZdLpvtM2XBb8PUt77WrFVAgUc2ZZ 4onqU2ikCg1fJY3qj+Li15OVqpzXOaElX7goKAKTtF2UVe/AMnM96J1qzv4sdOfnZkoI pO9pwTWvU7sQhGEon6Ph3q6kTEOxJ6U6EX3x1vXfhDXZElB7SFvg42EeK2JAjumybjGV 34NA==
X-Gm-Message-State: AOAM532if3pNdbLwiGFUINEJN4ZMtpHgdGfzp+x5mYDWpKClq6OwNK+v TPCIqGOQNOFh39nM5ua8agFqcsADzB43yPfTuQQp33pYBDv6qw==
X-Google-Smtp-Source: ABdhPJz/JRPWeORj4ngM0HwlVN2rPo7o63Q5QfQBYMa0jIczm29y6jeH+jhzeVSQN3oKfSFOMt1BnBThM5Rv+c0rAK8=
X-Received: by 2002:a67:c29e:: with SMTP id k30mr7833523vsj.45.1611747121522;  Wed, 27 Jan 2021 03:32:01 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it> <CAH48ZfwvBj3abrAEz1uK2UNyMOBAM1q3pH8cOmazn8VBow3ACQ@mail.gmail.com> <adcede1d-a260-7b78-9439-63eb706989e2@tana.it>
In-Reply-To: <adcede1d-a260-7b78-9439-63eb706989e2@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 27 Jan 2021 06:31:51 -0500
Message-ID: <CAH48Zfzp5zDpGkyOwud55-OgNqTkHO5Vo4yL0mT9o2DR+-P51Q@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a56e4d05b9e01e18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/90VoFX7k8Rlo37T1FpLhaZurdVs>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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: Wed, 27 Jan 2021 11:32:05 -0000

--000000000000a56e4d05b9e01e18
Content-Type: text/plain; charset="UTF-8"

Is this already a settled issue?  The specification already calls for a
complete A-R data set, so all signatures are supposed to be included if
they are evaluated.  Are the largest reporting sources already providing a
complete list of DKIM signatures?

However, there are significant technical problems with aggregating a list
with a variable number of members, because the list must be converted into
a list with a fixed number of elements before aggregation can be
performed.

- One technique is to convert the list into a variable-length text string,
so that the entire list is handled as one element.   Including all
signatures in an A-R record, and then grouping on the A-R text, would be an
example of this approach.  The technique will work up to the maximum
allowed text string supported by the data management system.   The maximum
number of list elements will depend on the mechanism used to build the text
string, the information being reported, and the maximum text size.   The
maximum number of supported list elements becomes unpredictable, but in
many data management systems will be larger than the expected number of
signatures in a message, unless a message is specifically constructed to
trigger a denial-of-service attack.

- Another approach, based on E.F.Codd's data normalization rules for
relational databases, is to have a table of messages which is keyed on a
message ID, and a table of signatures, which is keyed on message ID and
sequence number.   Then an outer join can be used to append the list
element with sequence number # to the message record.   A separate outer
join is required for each sequence number being appended, so the
implementation must choose a maximum number of list elements to append.
 One recent poster said that he was using this approach.    Outer joins are
generally inefficient, and this approach might work for up to 4 list
elements, but it will not work acceptable for a list with 100 elements.

For report sources with a fixed limit, it seems appropriate to have a
metadata element where the report provider states the maximum number of
signatures that might be reported by his system.   An indicator would be
needed to indicate "many, with no pre-determined limit"

Doug

On Tue, Jan 26, 2021 at 7:50 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Tue 26/Jan/2021 13:02:46 +0100 Douglas Foster wrote:
> > DKIM Scopes
> > I have not heard a compelling argument to require information about
> > authentication tests that are unrelated to alignment testing.    For
> DKIM
> > specifically, I think one scope should be sufficient, on this hierarchy:
> >
> > - The best-aligned scope that verified, or
> > - the best-aligned scope that failed verification, or
> > - a no-signature result otherwise.
> >
> > Anything more complex imposes a gratuitous data collection burden on the
> > reporting domain and reduces aggregation significantly.   On the
> technical
> > side, it has already been noted that variable-length lists are
> particularly
> > problematic for calculating aggregates.
>
>
> Let me attach an HTML rendering of a report I received today, so we can
> talk
> about something real.
>
> Lines with IP 4.31.198.44 bear a ietf.org identifier.  I see no reason to
> remove it.  It is useful for understanding the mailflow, which is what
> DMARC
> reporting is designed to do.
>
>
> > Aggregation Controls
> >
> > We have discussed whether the target domain should be included in the
> > report.  I understand that doing so is not reasonable for the large
> hosting
> > services.   On the other hand, including the target domain would be a
> > trivial matter for smaller operations, and I think it would be valuable
> for
> > some research.    Similarly, DKIM scopes are known to be useful for most
> > investigations, but John has already observed that proliferation of DKIM
> > scopes can be used to force disaggregation down to the individual
> recipient
> > level.
>
>
> Even if this is a small example, learning the disaggregated, or even
> individual
> recipients does not help my understanding.  Authentication is obviously
> conditioned by how the Mediator treats my messages.
>
> I expect that Fastmail Pty Ltd carries out SPF and DKIM validation using
> the
> same algorithm, irrespective of the recipient.  That is what I, as a
> sender, am
> interested in.  Splitting the report in 66 lines wouldn't tell me anything
> more, it would just consume more eyeballs.  And is useless for people who
> sum
> up all reports and just look at the totals.  In any case, I cannot verify
> if
> the messages I didn't send directly are real.
>
> If a multi-domain host allows personalized validation algorithms for some
> domains, I'd expect they send separated aggregate reports, if any.
>
>
> Best
> Ale
> --
>
>

--000000000000a56e4d05b9e01e18
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Is this already a settled issue?=C2=A0 The specification a=
lready calls for a complete A-R data set, so all signatures are supposed to=
 be included if they are evaluated.=C2=A0 Are the largest reporting sources=
 already providing a complete list of DKIM signatures?<div><br></div><div>H=
owever, there are significant technical problems with aggregating a list wi=
th a variable number of members, because the list must be converted into a =
list with a fixed number of elements before aggregation can be performed.=
=C2=A0 =C2=A0=C2=A0</div><div><br></div><div>- One technique is to convert =
the list into a variable-length text string, so that the entire=C2=A0list i=
s handled as one element.=C2=A0 =C2=A0Including all signatures in an A-R re=
cord, and then grouping on the A-R text, would be an example of this approa=
ch.=C2=A0 The technique will work up to the maximum allowed text string sup=
ported by the data management system.=C2=A0 =C2=A0The maximum number of lis=
t elements will depend on the mechanism used to build the text string,=C2=
=A0the information being reported, and the maximum text size.=C2=A0 =C2=A0T=
he maximum number of supported list=C2=A0elements becomes unpredictable, bu=
t in many=C2=A0data management systems will be larger than the expected num=
ber of signatures in a message, unless a message is specifically constructe=
d to trigger a denial-of-service attack.</div><div><br></div><div>- Another=
 approach, based on E.F.Codd&#39;s data normalization rules for relational =
databases, is to have a table of messages which is keyed on a message ID, a=
nd a table of signatures, which is keyed on message ID and sequence number.=
=C2=A0 =C2=A0Then an outer join can be used to append the list element with=
 sequence number # to the message record.=C2=A0 =C2=A0A separate outer join=
 is required for each sequence number being appended, so the implementation=
 must choose a maximum number of list elements to append.=C2=A0 =C2=A0One r=
ecent poster said that he was using this approach.=C2=A0 =C2=A0 Outer joins=
 are generally inefficient, and this approach might work for up to 4 list e=
lements, but it will not work acceptable for a list with 100 elements.</div=
><div><br></div><div>For report sources with a fixed limit, it seems approp=
riate to have a metadata element where the report provider states the maxim=
um number of signatures that might be reported by his system.=C2=A0 =C2=A0A=
n indicator would be needed to indicate &quot;many, with no pre-determined =
limit&quot;</div><div><br></div><div>Doug</div></div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 26, 2021 at 7:50=
 AM Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">O=
n Tue 26/Jan/2021 13:02:46 +0100 Douglas Foster wrote:<br>
&gt; DKIM Scopes<br>
&gt; I have not heard a compelling argument=C2=A0to require information abo=
ut <br>
&gt; authentication tests that are unrelated to alignment testing.=C2=A0 =
=C2=A0 For DKIM <br>
&gt; specifically, I think one scope should be sufficient, on this hierarch=
y:<br>
&gt; <br>
&gt; - The best-aligned scope that verified, or<br>
&gt; - the best-aligned scope that failed verification, or<br>
&gt; - a no-signature result otherwise.<br>
&gt; <br>
&gt; Anything more complex imposes a gratuitous data collection burden on t=
he <br>
&gt; reporting domain and reduces aggregation significantly.=C2=A0 =C2=A0On=
 the technical <br>
&gt; side, it has already been noted that variable-length lists are particu=
larly <br>
&gt; problematic for calculating aggregates.<br>
<br>
<br>
Let me attach an HTML rendering of a report I received today, so we can tal=
k <br>
about something real.<br>
<br>
Lines with IP 4.31.198.44 bear a <a href=3D"http://ietf.org" rel=3D"norefer=
rer" target=3D"_blank">ietf.org</a> identifier.=C2=A0 I see no reason to <b=
r>
remove it.=C2=A0 It is useful for understanding the mailflow, which is what=
 DMARC <br>
reporting is designed to do.<br>
<br>
<br>
&gt; Aggregation Controls<br>
&gt; <br>
&gt; We have discussed whether the target domain should be included in the<=
br>
&gt; report.=C2=A0 I understand that doing so is not reasonable for the lar=
ge hosting<br>
&gt; services.=C2=A0 =C2=A0On the other hand, including the target domain w=
ould be a<br>
&gt; trivial matter for smaller operations, and I think it would be valuabl=
e for<br>
&gt; some research.=C2=A0 =C2=A0 Similarly, DKIM scopes are known to be use=
ful for most<br>
&gt; investigations, but John has already observed that proliferation of DK=
IM<br>
&gt; scopes can be used to force disaggregation down to the individual reci=
pient<br>
&gt; level.<br>
<br>
<br>
Even if this is a small example, learning the disaggregated, or even indivi=
dual <br>
recipients does not help my understanding.=C2=A0 Authentication is obviousl=
y <br>
conditioned by how the Mediator treats my messages.<br>
<br>
I expect that Fastmail Pty Ltd carries out SPF and DKIM validation using th=
e <br>
same algorithm, irrespective of the recipient.=C2=A0 That is what I, as a s=
ender, am <br>
interested in.=C2=A0 Splitting the report in 66 lines wouldn&#39;t tell me =
anything <br>
more, it would just consume more eyeballs.=C2=A0 And is useless for people =
who sum <br>
up all reports and just look at the totals.=C2=A0 In any case, I cannot ver=
ify if <br>
the messages I didn&#39;t send directly are real.<br>
<br>
If a multi-domain host allows personalized validation algorithms for some <=
br>
domains, I&#39;d expect they send separated aggregate reports, if any.<br>
<br>
<br>
Best<br>
Ale<br>
-- <br>
<br>
</blockquote></div>

--000000000000a56e4d05b9e01e18--


From nobody Wed Jan 27 03:59:04 2021
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 BB1A83A0ED7 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 03:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 q-UD9ntsSRzU for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 03:59:01 -0800 (PST)
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 512333A0EC1 for <dmarc@ietf.org>; Wed, 27 Jan 2021 03:59:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611748738; bh=koSHjPy1VMzzjjePk4llrhZza/MPjcM31YkW0PauR6I=; l=2142; h=To:References:From:Date:In-Reply-To; b=C/DbchmZ2VRUBNUYAWK73/EV2evh051tn8v2/YZQuD61OY2pPyTFwWk7nOVaDlDnl vHprKICqB2x4tRS319XEAXGwPorJrTle5p32V0iBaKld1IawyBuMlXPW/nhScK9xhf tpOo1jFejvOehBDoB4RWxDAjU0zm2uWJrvG3l00HZqAsaBt24UqC0qBSyG5a4
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC026.0000000060115582.0000342E; Wed, 27 Jan 2021 12:58:58 +0100
To: "Murray S. Kucherawy" <superuser@gmail.com>, John Levine <johnl@taugh.com>, IETF DMARC WG <dmarc@ietf.org>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy> <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <29f5c140-6b07-e3be-f188-8b2104690385@tana.it>
Date: Wed, 27 Jan 2021 12:58:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@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/IXK_c3NXyuj9wKfwe5y7FgJN3J4>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Wed, 27 Jan 2021 11:59:03 -0000

On Sat 16/Jan/2021 22:30:56 +0100 Murray S. Kucherawy wrote:
> On Fri, Jan 15, 2021 at 7:40 PM John Levine <johnl@taugh.com> wrote:
> 
>> I still don't understand why anyone thinks there is a problem to be
>> fixed. If you don't want reports, don't ask for them. If you think the
>> mail you send shouldn't be provoking DMARC failure reports, adjust
>> whatever is sending the mail the mail is aligned, or get rid of the
>> ruf= that asks for the reports. What am I missing here?
> 
> You might be right, so I'll go back and ask this use case what the
> specifics are.
> 
> What I'm concerned about is that since this has come up before N times
> (for, admittedly, some currently small value of N), we've seen enough
> disparate cases of it that we may be missing something bigger, and if so,
> doing something defensive in the specification would be prudent.  There's
> smoke here, and there may be fire.
> 
> Will report back.


Examining my report folder, I note I'm sending one-liner aggregate reports to 
domains I never wrote to.  The pattern is their sending me feedback for one or 
more mailing list posts, followed by my one-liner acknowledging their report 
later on the same day or on the next day, depending on their sending time.

It is not a loop, because I send from noloop.tana.it, which has no rua=.  I'm 
not alone using this trick.  Two naive report generators would continue to send 
one-liners indefinitely.

While this is a minor problem for aggregate reports, it can be a real problem 
for naive failure reports generators.  Juri reported he had to target a 
specific address, attributing the loop to a remote misconfiguration.  However, 
if it is possible to screw up authentications, the probability to meet a loop 
is just its square, times the number of generators.

The only prevention in the spec is to apply rate limiting.

I'd add a couple of loop-specific provisions:

* send reports from a subdomain having a DMARC record without ruf=,

* configure the verifier to not generate failures of messages destined to one's 
own ruf= address.

I shouldn't hurt, should it?

Best
Ale
-- 














From nobody Wed Jan 27 04:33:58 2021
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 B7DCC3A0FEB for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 04:33:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 p4fAxEd4tlxx for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 04:33:55 -0800 (PST)
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 713333A0FDE for <dmarc@ietf.org>; Wed, 27 Jan 2021 04:33:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611750831; bh=QIl73DSQD5SOwg8fsE9t7HdVI9dRNmmCWWcvN50vOe4=; l=2076; h=To:References:From:Date:In-Reply-To; b=DV2ldsnnB4e6Ie2W4dUxttoKcmfde7spjxrdy/7AcVPq1fYjFt9UkgNt7Z/eIRwQ8 E3xYfQ4iZccwMGSVq6mNGC4QpOt91s6m7MSQZzEd/AQtnkpLhnrtukb8EEnCizfqEl h5JmIhL5QUvK4gsVy+9O1tg1gO/Arzg/8AP2zftQjjg4Eofx/zVjV3sShXJKL
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.0000000060115DAF.000037F3; Wed, 27 Jan 2021 13:33:51 +0100
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <MN2PR11MB4351BD7203D41DB25771D3B3F7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAH48Zfwat5MmXrvfEp-G=0pTZe2fwwDOJ6s6M1FSWs6M50yk0w@mail.gmail.com> <MN2PR11MB43513C20B5A598496FFBA4AAF7BD9@MN2PR11MB4351.namprd11.prod.outlook.com> <7231cfb1-1553-fd11-e356-57b960c5bfdc@tana.it> <CAH48ZfwvBj3abrAEz1uK2UNyMOBAM1q3pH8cOmazn8VBow3ACQ@mail.gmail.com> <adcede1d-a260-7b78-9439-63eb706989e2@tana.it> <CAH48Zfzp5zDpGkyOwud55-OgNqTkHO5Vo4yL0mT9o2DR+-P51Q@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <4c43b55a-674e-6aa3-a9f0-7e004c60e4ca@tana.it>
Date: Wed, 27 Jan 2021 13:33:51 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48Zfzp5zDpGkyOwud55-OgNqTkHO5Vo4yL0mT9o2DR+-P51Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/JoC3wGgDpTlrjqgMuLSLYN9r0DM>
Subject: Re: [dmarc-ietf] Which DKIM(s) should be reported? (Ticket #38)
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: Wed, 27 Jan 2021 12:33:57 -0000

On Wed 27/Jan/2021 12:31:51 +0100 Douglas Foster wrote:
> Is this already a settled issue?


There doesn't seem to be a consensus, yet.

I repeat what I already proposed:

*  max number of DKIM signatures: 1024 (say)
*  min number of DKIM signatures: 0
*  can report unverified signatures (<result>none</result>)
*  order signatures by descreasing importance (reporter POV)

Would the WG post some +/-1s, please?


> - Another approach, based on E.F.Codd's data normalization rules for relational 
> databases, is to have a table of messages which is keyed on a message ID, and a 
> table of signatures, which is keyed on message ID and sequence number.   Then 
> an outer join can be used to append the list element with sequence number # to 
> the message record.   A separate outer join is required for each sequence 
> number being appended, so the implementation must choose a maximum number of 
> list elements to append.   One recent poster said that he was using this 
> approach.    Outer joins are generally inefficient, and this approach might 
> work for up to 4 list elements, but it will not work acceptable for a list with 
> 100 elements.


Could fill the whole list using transitive closure.  MariaDB implements 
Recursive Common Table Expressions, which can be used for that purpose. 
Although that feature was implemented in 2016, it landed on the distribution I 
use quite recently.  I haven't yet looked at it.


> For report sources with a fixed limit, it seems appropriate to have a metadata 
> element where the report provider states the maximum number of signatures that 
> might be reported by his system.   An indicator would be needed to indicate 
> "many, with no pre-determined limit"


It is probably more useful to report the total number of signatures found.  The 
fixed limit of a given implementation can be deduced after it is hit.

OTOH, a reference to the software version that generated the report would be 
useful in general, and may lead to the documented fixed number in particular.


Best
Ale
-- 























From nobody Wed Jan 27 06:00:35 2021
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 41B913A119B for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 06:00:33 -0800 (PST)
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=cQCrHRpO; dkim=pass (2048-bit key) header.d=kitterman.com header.b=mz9eUBC1
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 nPqJBsYwXypo for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 06:00:31 -0800 (PST)
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 C8B4F3A0C68 for <dmarc@ietf.org>; Wed, 27 Jan 2021 06:00:31 -0800 (PST)
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 33CB0F80263 for <dmarc@ietf.org>; Wed, 27 Jan 2021 09:00:30 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1611756029; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=IAElUizHEY+UgkDdhb3sIRYQBupgFdgEap+AixAEyPc=; b=cQCrHRpOOUYi0kuVKSR9gAa/6VAxKggZZf4PRrf5/r0jmJis70izzj3MgTR1UO9Pt38VO Swf76uXEL4EEHD/AA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1611756029; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=IAElUizHEY+UgkDdhb3sIRYQBupgFdgEap+AixAEyPc=; b=mz9eUBC1Walk9CVoxo7I0xdgm8t/8vcV61t/jyHYgJ9/4yvv76jEULvG6Wv8DkLQs0RKG GD1vAosri8cyYTj0tEG50Tr34j+6pRkt3bl4mJqqEhSUJgIRQ0SyX6t9ZOnykYDBRB087Gt Nfuoxlpv6iCQdoGG4vVWZo038ndhjvE53AfwuBTIVjC5l4yu5uJ+R+64j2StV4tUsQ6NYye FXTgj2amblw3b7gCthrLzxYv+Sy7h2SNcoXJWCAQ8Tz8eWbLxArLKy9kRuh0B29X4+DX+uR x6pqmJ1oLmBLf+CXzFIy2jzcCQt+HPTDJQvviP0UMwAofRuvpcLx8LNc85PA==
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 8E0AFF80052 for <dmarc@ietf.org>; Wed, 27 Jan 2021 09:00:29 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Wed, 27 Jan 2021 09:00:29 -0500
Message-ID: <3776619.NdRDDhGtae@zini-1880>
In-Reply-To: <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/SncvE3d_Ai63GMqTu8s5xnHtXkE>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Wed, 27 Jan 2021 14:00:33 -0000

On Wednesday, January 27, 2021 4:49:02 AM EST Alessandro Vesely wrote:
> On Tue 26/Jan/2021 23:36:19 +0100 Scott Kitterman wrote:
> > On Tuesday, January 26, 2021 11:47:51 AM EST Alessandro Vesely wrote:
> >> On Tue 26/Jan/2021 14:14:45 +0100 Scott Kitterman wrote:
> >>> On Tuesday, January 26, 2021 6:54:56 AM EST Alessandro Vesely wrote:
> >>>> I doubt that SPF filters report envelope-from=postmaster@HELO; more
> >>>> likely they write helo=HELO.  In that case, the paragraph quoted above
> >>>> is deceptive. >>>>
> >>>> 
> >>>>> I believe the proposed text is clear enough about not using
> >>>>> separate HELO identity results and that's appropriate. >>>>
> >>>> 
> >>>> My filter collects SPF results recorded from an upstream SPF filter.
> >>>> It writes Received-SPF: lines for each identity.  For NDNs, it writes
> >>>> a Received-SPF: for the HELO identity only.  Am I allowed to use that
> >>>> result for DMARC? >>>
> >>> 
> >>> No.  You should only use Mail From results.
> >> 
> >> So NDNs having only an aligned HELO will never pass DMARC?
> >> 
> >> And what is a <scope>helo</scope> element in aggregate reports provided
> >> for?>> 
> >> The spec says:
> >>           [SPF] can authenticate either the domain that appears in the
> >>     
> >>     RFC5321.MailFrom (MAIL FROM) portion of [SMTP] or the RFC5321.EHLO/
> >>     HELO domain, or both.
> >> 
> >> And then:
> >>     In relaxed mode, the [SPF]-authenticated domain and RFC5322.From
> >>     domain must have the same Organizational Domain.  In strict mode,
> >>     only an exact DNS domain match is considered to produce Identifier
> >>     Alignment.
> >> 
> >> So, consider the following message without DKIM signatures:
> >> 
> >> HELO example.org
> >> MAIL FROM:<user@example.com>
> >> 
> >> Received-SPF: pass (domain example.org
> >> 
> >>    designates 192.0.2.1 as permitted sender)
> >>    identity=helo; helo=example.org;
> >> 
> >> Received-SPF: fail (domain of user@example.com
> >> 
> >>    denies 192.0.2.1 as permitted sender)
> >>    identity=mailfrom; envelope-from="user@example.com";
> >> 
> >> Subject: Not using a mail client for this example
> >> From: different-user@example.org
> >> 
> >> Does it pass DMARC?
> > 
> > No.
> 
> Let's not be silly, Scott.  We have example.org as the SPF-authenticated
> domain and it is aligned with From:.  Are you saying that the message would
> pass if it had an empty bounce address, but since it can bounce it does not
> pass?!?

All I'm saying is that DMARC only uses mail from results and that's 
appropriate.  I don't think the case of HELO name being aligned, but mail from 
domain is not is one to worry about.

Scott K



From nobody Wed Jan 27 08:17:44 2021
Return-Path: <johnl@taugh.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 188553A0B23 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 08:17:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=gaMuSTs+; dkim=pass (2048-bit key) header.d=taugh.com header.b=NVzWz5dr
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 5mLrOjOjeILn for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 08:17:41 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 02FBD3A0AFA for <dmarc@ietf.org>; Wed, 27 Jan 2021 08:17:40 -0800 (PST)
Received: (qmail 69222 invoked from network); 27 Jan 2021 16:17:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=10e64.60119223.k2101; bh=pcRTtF+ZNkovaIJiSh8cIOWV0qmOdP8y1IEypSh5hDg=; b=gaMuSTs+XYWqhjpwvtLx+tyOjIgW6py1R29+unJgNOXRbQe7IYrqOAkHJPKzd5jfPad17EhjYEzBFVXqtAWMT0iveJrQPZazRfWkBgAeOPW9uizKB0l3vU7cb5STmFtCJjst5DsyCRg4boU8StCqieZh65SPp8tD9QDaOI51NvobVJr6Xwm4yl26tNEJB/EqrXjXKvYGgayZszdpJt/XAqe9wxXK7A4+ETIwPiNfkvCiPpB4p/w+e/Dyt6a/k8fMkC7zYAf0SL5yFzrY9eprwKlV+mZRDB/cvVVSQoG3KLZDdknIju9exjpNfjxS9aOSCvTnTJTJEEEbmZ/lLWZzVw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=10e64.60119223.k2101; bh=pcRTtF+ZNkovaIJiSh8cIOWV0qmOdP8y1IEypSh5hDg=; b=NVzWz5drTpnpWmfR+6zzy+VCZSWPaBFsF++kDfJ3flFYiM0yL9ZU5t/D9cBzkcs54TN2ziTVnnFe1jdeG8+PR1iBWF98e+rH1M550L7DCcI8OqV+J2t3bLi1VqABtMyoaEpsQVBkTXKSDPHMOhvMKi0O8GWLCZV1LWXHgEb+Q9qAHmQHvD8cGH+x7HfiZCBK2FWR2+ImDfrCs6sqvq6ENJlrahchrlR/cdb+/LCJaxZi4KYBRa6UVnOLk5eh/3z8N5lsOJwbxOXeIevZSmnhq9JTChPcumc9RwxXDfM6p7gWn0IEqy72L00XIexLYUzckbybKvcX1O1fNqS3og5FtA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 27 Jan 2021 16:17:38 -0000
Received: by ary.qy (Postfix, from userid 501) id 6782B6C2CB34; Wed, 27 Jan 2021 11:17:38 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 37FA26C2CB16; Wed, 27 Jan 2021 11:17:38 -0500 (EST)
Date: 27 Jan 2021 11:17:38 -0500
Message-ID: <52ea482c-86f8-f879-eefb-ff14e8819b56@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, "IETF DMARC WG" <dmarc@ietf.org>
In-Reply-To: <29f5c140-6b07-e3be-f188-8b2104690385@tana.it>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy> <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com> <29f5c140-6b07-e3be-f188-8b2104690385@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WpL2Ae0h9258FKPohD91Yyw9b9E>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Wed, 27 Jan 2021 16:17:43 -0000

>> disparate cases of it that we may be missing something bigger, and if so,
>> doing something defensive in the specification would be prudent.  There's
>> smoke here, and there may be fire.
>> 
>> Will report back.

> Examining my report folder, I note I'm sending one-liner aggregate reports to 
> domains I never wrote to.  The pattern is their sending me feedback for one 
> or more mailing list posts, followed by my one-liner acknowledging their 
> report later on the same day or on the next day, depending on their sending 
> time.

That's not a "loop", it's the way that DMARC reports work.

> While this is a minor problem for aggregate reports, it can be a real problem 
> for naive failure reports generators.  Juri reported he had to target a 
> specific address, attributing the loop to a remote misconfiguration. 
> However, if it is possible to screw up authentications, the probability to 
> meet a loop is just its square, times the number of generators.

If the authentication is screwed up, sending a failure report is exactly 
the right thing to do.  That's what they're for.

I think we should close this.  DMARC is working the way it is supposed to, 
and people don't want to get reports about their reports, there are 
obvious ways to prevent them, like not sending unaligned reports, or 
sending reports from a domain that doesn't get reports back.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Wed Jan 27 09:26:06 2021
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 45D963A0CAF for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 09:26:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 LKN3hErEOLCi for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 09:26:03 -0800 (PST)
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 0C21F3A0CB1 for <dmarc@ietf.org>; Wed, 27 Jan 2021 09:26:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611768361; bh=DTqHQOZmNVEgAgt4l8tuQuphNyOuHNTbN+Pea6hoklQ=; l=3899; h=To:References:From:Date:In-Reply-To; b=AYpG8pPe+1Chloq7gy4CZdXYwL1eeaAP8CNcnsXC2vd0c7UrwFeuXo1o0DAUr2LuM nfCfaoyk/Wf3AvQHaATqGpjwmCd+j3EurImtsA6K/6AMJpCvCDAv3WepRGPcOoVqci GlIzMgC6NUuSaHuEFGN4h41o86jA8Q1x2qKKJkValDPxktFTWhZLt6SKdSPAc
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC026.000000006011A229.000057DB; Wed, 27 Jan 2021 18:26:01 +0100
To: dmarc@ietf.org
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it>
Date: Wed, 27 Jan 2021 18:25:59 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <3776619.NdRDDhGtae@zini-1880>
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/M10MgKzErR7vKhJQDWAyfIeah7Q>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Wed, 27 Jan 2021 17:26:05 -0000

On Wed 27/Jan/2021 15:00:29 +0100 Scott Kitterman wrote:
> On Wednesday, January 27, 2021 4:49:02 AM EST Alessandro Vesely wrote:
>> On Tue 26/Jan/2021 23:36:19 +0100 Scott Kitterman wrote:
>>> On Tuesday, January 26, 2021 11:47:51 AM EST Alessandro Vesely wrote:
>>>> On Tue 26/Jan/2021 14:14:45 +0100 Scott Kitterman wrote:
>>>>> On Tuesday, January 26, 2021 6:54:56 AM EST Alessandro Vesely wrote:
>>>>>> I doubt that SPF filters report envelope-from=postmaster@HELO; more
>>>>>> likely they write helo=HELO.  In that case, the paragraph quoted above
>>>>>> is deceptive.
>>>>>> 
>>>>>>> I believe the proposed text is clear enough about not using
>>>>>>> separate HELO identity results and that's appropriate. >>>>
>>>>>> 
>>>>>> My filter collects SPF results recorded from an upstream SPF filter.
>>>>>> It writes Received-SPF: lines for each identity.  For NDNs, it writes
>>>>>> a Received-SPF: for the HELO identity only.  Am I allowed to use that
>>>>>> result for DMARC?
>>>>> 
>>>>> No.  You should only use Mail From results.
>>>> 
>>>> So NDNs having only an aligned HELO will never pass DMARC?
>>>> 
>>>> And what is a <scope>helo</scope> element in aggregate reports provided
>>>> for?
>>>> 
>>>> The spec says:
>>>>           [SPF] can authenticate either the domain that appears in the
>>>>     RFC5321.MailFrom (MAIL FROM) portion of [SMTP] or the RFC5321.EHLO/
>>>>     HELO domain, or both.
>>>> 
>>>> And then:
>>>>     In relaxed mode, the [SPF]-authenticated domain and RFC5322.From
>>>>     domain must have the same Organizational Domain.  In strict mode,
>>>>     only an exact DNS domain match is considered to produce Identifier
>>>>     Alignment.
>>>> 
>>>> So, consider the following message without DKIM signatures:
>>>> 
>>>> HELO example.org
>>>> MAIL FROM:<user@example.com>
>>>> 
>>>> Received-SPF: pass (domain example.org
>>>>    designates 192.0.2.1 as permitted sender)
>>>>    identity=helo; helo=example.org;
>>>> Received-SPF: fail (domain of user@example.com
>>>>    denies 192.0.2.1 as permitted sender)
>>>>    identity=mailfrom; envelope-from="user@example.com";
>>>> Subject: Not using a mail client for this example
>>>> From: different-user@example.org
>>>> 
>>>> Does it pass DMARC?
>>> 
>>> No.
>> 
>> Let's not be silly, Scott.  We have example.org as the SPF-authenticated 
>> domain and it is aligned with From:.  Are you saying that the message
>> would pass if it had an empty bounce address, but since it can bounce it
>> does not pass?!? >
> All I'm saying is that DMARC only uses mail from results and that's 
> appropriate.  I don't think the case of HELO name being aligned, but mail
> from domain is not is one to worry about.

That's abnormal, not appropriate.

AFAIUI, there's no reason why SPF would work with a logic substantially 
different than DKIM's.  DKIM can provide n identifiers, if one of them is 
aligned and "pass", then DMARC is "pass".  SPF can provide 2 identifiers but 
one of them is of class B.  WTF?

Can anyone explain why we have a <scope>helo</scope> element in aggregate reports?

Can we fix this aberration?

The spec needs a fix anyway, because from the text I quoted above I understood 
that the example message passes DMARC.  Am I the only one?

In addition, as I said, SPF filters are likely to report HELO as helo and MAIL 
FROM as mailfrom.  If we want to carry over this quirk, the spec must say that 
a DMARC filter which gathers SPF authentication status from an upstream filter 
MUST make sure that mailfrom is empty before validating based on an aligned helo.

Dropping that absurd discrimination between SPF identifiers would make for a 
smoother spec.  Since non-null mailfroms are in most cases aligned with either 
From: or helo, the differences between existing compliant implementations and 
the smoother spec would be limited to a hardly noticeable set of test messages.


Best
Ale
-- 






















From nobody Wed Jan 27 10:08:53 2021
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 7E15F3A0D2E for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 10:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 8y8Fpq1QtzAB for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 10:08:49 -0800 (PST)
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 B4AC33A0D38 for <dmarc@ietf.org>; Wed, 27 Jan 2021 10:08:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611770927; bh=PNCIC0cnXHgibKJzUMWTQYfJ5a2eqewG6TZcHqve8X4=; l=1768; h=To:References:From:Date:In-Reply-To; b=ALEd13FJvKTmMZYu3/V23hZbMYMnaDRoS5fgjTmgmBPaF8nqPd6+MM1SQ23L/eNeD G9OBOR45kH1IJY1/tQSaqofJkGKObvacHkC5v8vSbUHcYZWbZ+V4CDXf+y91EQWW8t ooTw6DCpYLETU8d6/tVcQ4JX6doApPUFRFidx5VNyfkluxJM7hh4wy8lvxOGO
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC07E.000000006011AC2F.00005B99; Wed, 27 Jan 2021 19:08:47 +0100
To: John R Levine <johnl@taugh.com>, IETF DMARC WG <dmarc@ietf.org>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy> <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com> <29f5c140-6b07-e3be-f188-8b2104690385@tana.it> <52ea482c-86f8-f879-eefb-ff14e8819b56@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <d54e8930-5266-7622-183d-023f9e35e385@tana.it>
Date: Wed, 27 Jan 2021 19:08:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <52ea482c-86f8-f879-eefb-ff14e8819b56@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jfUcwVKXUdUpF0Cg5SHoWSZ3m4o>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Wed, 27 Jan 2021 18:08:52 -0000

On Wed 27/Jan/2021 17:17:38 +0100 John R Levine wrote:
> 
>> While [loops are] a minor problem for aggregate reports, it can be a real problem 
>> for naive failure reports generators.  Juri reported he had to target a 
>> specific address, attributing the loop to a remote misconfiguration. However, 
>> if it is possible to screw up authentications, the probability to meet a loop 
>> is just its square, times the number of generators.
> 
> If the authentication is screwed up, sending a failure report is exactly the 
> right thing to do.  That's what they're for.


Even if the screwed up message was a failure report itself?


> I think we should close this.  DMARC is working the way it is supposed to, and 
> people don't want to get reports about their reports, there are obvious ways to 
> prevent them, like not sending unaligned reports,


Oh, there is a sentence in the current spec:

    Email streams carrying DMARC feedback data MUST conform to the DMARC
    mechanism, thereby resulting in an aligned "pass" (see Section 3.1).

As it stands, it's valid for both aggregate and failure reports.  However, it 
happened to land on the aggregate-reporting I-D only.


> or sending reports from a domain that doesn't get reports back.

That was one of the hints I proposed.  Your wording is better.  Added this:

3.3.  Transport

    Email streams carrying DMARC failure reports MUST conform to the
    DMARC mechanism, thereby resulting in an aligned "pass".  Special
    care must be taken for authentication, as failure to authenticate
    failure reports may result in mail loops.  Besides rate limiting,
    such loops can also be avoided by sending reports from a domain that
    doesn't get reports back.

Is that all right?


Best
Ale
-- 












From nobody Wed Jan 27 10:38:15 2021
Return-Path: <johnl@taugh.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 75E813A0CF0 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 10:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=Z45DhHlA; dkim=pass (2048-bit key) header.d=taugh.com header.b=IEtAtRBI
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 y7LTh9-LeKSy for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 10:38:12 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 210D93A0CF1 for <dmarc@ietf.org>; Wed, 27 Jan 2021 10:38:11 -0800 (PST)
Received: (qmail 5319 invoked from network); 27 Jan 2021 18:38:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=14c5.6011b312.k2101; bh=lbENrye+2zmLIDJ70C2JQT/9ODXIJcPJKpdgpV2vbnA=; b=Z45DhHlAyTR4F13Pr1xuEmL1WNtjLUX2LMGMj2u+FEGGVNWBdPsm6A0Fi6X8hqOb49suHlb+Al/2byLzQ7ShdBlTwxmjN5Lajj9IWKFCPkpj9J9SilMHeliYUuw3VNgktaLOMV/5lZ1VKtSAAoGGUxA2XRXIRV3QGNRzOfC4Kse+3UPLLf/lyl+IEdB8Gga640aZHlwTNtUY9ETNVhEcPd6BzF7ff/MJrGnYAxFKXwkbAVytfSWvxTWs/NDpBVPN9xi9pwTiI0xZSgQKPsQl8QxEtoODswEJF8ieiKg6xm2J0SuPPhhkA4KKKn6sfe4Wm0+1W5y5ym43A4GfNP7T8w==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=14c5.6011b312.k2101; bh=lbENrye+2zmLIDJ70C2JQT/9ODXIJcPJKpdgpV2vbnA=; b=IEtAtRBIyK5SzfZ6ibr9OxOKsKNmGd/pWNja2D7R/52TdTY2z/RRSdyfIFdczE/mO7WbrVUvtFnzBYvYx7bBw4NGWxhy/ObaDaD5GPNmZth9WD3jJ1U9MVD/uRkezF4Qtr9Y7/PjNNJZ53NiZqHaSOmGb4OZfc0GHYeKM49l8vTYiR40aNQQpzrL6PmsMeb/qQNdvPJrLEvfyazWJwYV1MLamfU58YNs0RSiwEAmKRPhc+W9+d5/OBeunJWvyuKEwTmQ3tSISobrgzYv1me8GHhiC4/hOpkB2F0a9ixEOwR9QlablyzzEJ5zhdOI6JCbfSRQs93307DY4+oH32TiTg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 27 Jan 2021 18:38:09 -0000
Received: by ary.qy (Postfix, from userid 501) id 3C7A76C2E122; Wed, 27 Jan 2021 13:38:08 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 9741C6C2E104; Wed, 27 Jan 2021 13:38:08 -0500 (EST)
Date: 27 Jan 2021 13:38:08 -0500
Message-ID: <13f04f5a-4176-db79-ca4a-a99686e76edf@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, "IETF DMARC WG" <dmarc@ietf.org>
In-Reply-To: <d54e8930-5266-7622-183d-023f9e35e385@tana.it>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy> <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com> <29f5c140-6b07-e3be-f188-8b2104690385@tana.it> <52ea482c-86f8-f879-eefb-ff14e8819b56@taugh.com> <d54e8930-5266-7622-183d-023f9e35e385@tana.it>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1005787841-1611772688=:61371"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Owc2yYjM6WOYZb2ZZ6esoJlHX18>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Wed, 27 Jan 2021 18:38:15 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1005787841-1611772688=:61371
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Wed, 27 Jan 2021, Alessandro Vesely wrote:
>> If the authentication is screwed up, sending a failure report is exactly 
>> the right thing to do.  That's what they're for.
>
>   Email streams carrying DMARC feedback data MUST conform to the DMARC
>   mechanism, thereby resulting in an aligned "pass" (see Section 3.1).

> Even if the screwed up message was a failure report itself?

Of course.  The failure repoort is a new e-mail message.  If it's not 
aligned, your code needs to be fixed.

> 3.3.  Transport
>
>   Email streams carrying DMARC failure reports MUST conform to the
>   DMARC mechanism, thereby resulting in an aligned "pass".  Special
>   care must be taken for authentication, as failure to authenticate
>   failure reports may result in mail loops.

Stop there.  If you don't want failure reports, don't send unaligned 
messages.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
--0-1005787841-1611772688=:61371--


From nobody Wed Jan 27 11:24:11 2021
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 D87863A0DF7 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 11:24:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_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=cD75wfC/; dkim=pass (2048-bit key) header.d=kitterman.com header.b=DngScC7X
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 O8HMnUXI-L4p for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 11:24:08 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F41493A0DEC for <dmarc@ietf.org>; Wed, 27 Jan 2021 11:24:07 -0800 (PST)
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 6A579F80263 for <dmarc@ietf.org>; Wed, 27 Jan 2021 14:24:06 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1611775446; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=WyMXRDcUes55Y6nel3g/EawEAviAJA6pmDtMD+LM4pk=; b=cD75wfC/8FHogHzakIeFEHDgWiPFdOsU1EMwk5ywBwqFwG0PGpv6DBqygllWzEiEiwKQF FQGx2wd7zBTxM9JBg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1611775446; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=WyMXRDcUes55Y6nel3g/EawEAviAJA6pmDtMD+LM4pk=; b=DngScC7Xwv5EeptmwWgBwLcFteromS7iBCm85NZJCZVMTOlRDgbI9VIzyK/14yQEWNj/L l7ph8NBKkX01gzaA3wEAKn3tOJIf8jYAyc2/J5S8m8x6i1iscN4dxUqusZIWZPceyJXBtty 1hu52W64li/6OQkEQMtPupSGk5fNvEvsrwyPWZCUnSVTAtPdxqkHBlOBUiWE8HuXWT1U7Fi jklV7e5A/wQtkvH1aZ1zP5rgZWVYn1INrpPTtihFcl5yR/+yP6OFMxmkwKqvdTz2V/vwvUt NLde2FEvhZTqnNTiZkTdKNYg40R3xWu+2p7ixrew85Tf96a5deB54Pu4x/zg==
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 31C54F80052 for <dmarc@ietf.org>; Wed, 27 Jan 2021 14:24:06 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Wed, 27 Jan 2021 14:24:05 -0500
Message-ID: <11050391.cvU1rW7NdO@zini-1880>
In-Reply-To: <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/nTQIpDXlBAdqbzcbFZX4jrwSRPA>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Wed, 27 Jan 2021 19:24:10 -0000

On Wednesday, January 27, 2021 12:25:59 PM EST Alessandro Vesely wrote:
> On Wed 27/Jan/2021 15:00:29 +0100 Scott Kitterman wrote:
> > On Wednesday, January 27, 2021 4:49:02 AM EST Alessandro Vesely wrote:
> >> On Tue 26/Jan/2021 23:36:19 +0100 Scott Kitterman wrote:
> >>> On Tuesday, January 26, 2021 11:47:51 AM EST Alessandro Vesely wrote:
> >>>> On Tue 26/Jan/2021 14:14:45 +0100 Scott Kitterman wrote:
> >>>>> On Tuesday, January 26, 2021 6:54:56 AM EST Alessandro Vesely wrote:
> >>>>>> I doubt that SPF filters report envelope-from=postmaster@HELO; more
> >>>>>> likely they write helo=HELO.  In that case, the paragraph quoted
> >>>>>> above
> >>>>>> is deceptive.
> >>>>>> 
> >>>>>>> I believe the proposed text is clear enough about not using
> >>>>>>> separate HELO identity results and that's appropriate. >>>>
> >>>>>> 
> >>>>>> My filter collects SPF results recorded from an upstream SPF filter.
> >>>>>> It writes Received-SPF: lines for each identity.  For NDNs, it writes
> >>>>>> a Received-SPF: for the HELO identity only.  Am I allowed to use that
> >>>>>> result for DMARC?
> >>>>> 
> >>>>> No.  You should only use Mail From results.
> >>>> 
> >>>> So NDNs having only an aligned HELO will never pass DMARC?
> >>>> 
> >>>> And what is a <scope>helo</scope> element in aggregate reports provided
> >>>> for?
> >>>> 
> >>>> The spec says:
> >>>>           [SPF] can authenticate either the domain that appears in the
> >>>>     
> >>>>     RFC5321.MailFrom (MAIL FROM) portion of [SMTP] or the RFC5321.EHLO/
> >>>>     HELO domain, or both.
> >>>> 
> >>>> And then:
> >>>>     In relaxed mode, the [SPF]-authenticated domain and RFC5322.From
> >>>>     domain must have the same Organizational Domain.  In strict mode,
> >>>>     only an exact DNS domain match is considered to produce Identifier
> >>>>     Alignment.
> >>>> 
> >>>> So, consider the following message without DKIM signatures:
> >>>> 
> >>>> HELO example.org
> >>>> MAIL FROM:<user@example.com>
> >>>> 
> >>>> Received-SPF: pass (domain example.org
> >>>> 
> >>>>    designates 192.0.2.1 as permitted sender)
> >>>>    identity=helo; helo=example.org;
> >>>> 
> >>>> Received-SPF: fail (domain of user@example.com
> >>>> 
> >>>>    denies 192.0.2.1 as permitted sender)
> >>>>    identity=mailfrom; envelope-from="user@example.com";
> >>>> 
> >>>> Subject: Not using a mail client for this example
> >>>> From: different-user@example.org
> >>>> 
> >>>> Does it pass DMARC?
> >>> 
> >>> No.
> >> 
> >> Let's not be silly, Scott.  We have example.org as the SPF-authenticated
> >> domain and it is aligned with From:.  Are you saying that the message
> >> would pass if it had an empty bounce address, but since it can bounce it
> >> does not pass?!? >
> > 
> > All I'm saying is that DMARC only uses mail from results and that's
> > appropriate.  I don't think the case of HELO name being aligned, but mail
> > from domain is not is one to worry about.
> 
> That's abnormal, not appropriate.
> 
> AFAIUI, there's no reason why SPF would work with a logic substantially
> different than DKIM's.  DKIM can provide n identifiers, if one of them is
> aligned and "pass", then DMARC is "pass".  SPF can provide 2 identifiers but
> one of them is of class B.  WTF?
> 
> Can anyone explain why we have a <scope>helo</scope> element in aggregate
> reports?
> 
> Can we fix this aberration?
> 
> The spec needs a fix anyway, because from the text I quoted above I
> understood that the example message passes DMARC.  Am I the only one?
> 
> In addition, as I said, SPF filters are likely to report HELO as helo and
> MAIL FROM as mailfrom.  If we want to carry over this quirk, the spec must
> say that a DMARC filter which gathers SPF authentication status from an
> upstream filter MUST make sure that mailfrom is empty before validating
> based on an aligned helo.
> 
> Dropping that absurd discrimination between SPF identifiers would make for a
> smoother spec.  Since non-null mailfroms are in most cases aligned with
> either From: or helo, the differences between existing compliant
> implementations and the smoother spec would be limited to a hardly
> noticeable set of test messages.

Your absurd is my eminently reasonable.

I can't explain why it was added, but it makes sense, IMO, to have it there to 
aid in reconstructing the exact situation for trouble shooting purposes.

DMARC has always (for the SPF related portion) been about alignment of mail 
from and from.  I don't think adding HELO has appreciable value and is 
certainly not worth the added complexity to implement DMARC to include.

There are lots of ways that DMARC could have addressed SPF.  Personally I 
thought it might make sense to skip using the mail from SPF result and just 
check if the from address would pass if it were subjected to an SPF check, but 
that's not the existing design.  I don't think it should be changed now.

That said, I agree it's not 100% clear.  I too am interested in what others 
think.

Scott K



From nobody Wed Jan 27 12:10:53 2021
Return-Path: <superuser@gmail.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 5A9233A0EB5 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ags2y8xQ2MUY for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:10:50 -0800 (PST)
Received: from mail-vk1-xa35.google.com (mail-vk1-xa35.google.com [IPv6:2607:f8b0:4864:20::a35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEFAD3A0EB2 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:10:49 -0800 (PST)
Received: by mail-vk1-xa35.google.com with SMTP id m25so810905vkk.6 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:10:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/SL8q2dwvbYeVuTEnBKl6DpDMvlUzzgP15YR7GVxGo8=; b=jv34vQTflOBLP24E+ZJ0tSLDRUnR48HfbnCgTTP7HIuDlzvOWMT23snVbORdWTbDfJ n82ALJEGpN8/S730nGFdSPJd0uGPTA/aBB2K7/b65Rv5hKkr67uFZLKjzBMRud2WqPQf nPst+XbenqkULqbQKmGDZlVgadUsoD9hNzc3prrygtl6SEqsNcnG80m2MV9px5wZMv90 X/EzNeUZkV/BL1SQxSf1MXJ4MBqpiAgqAW/qs+HjemguWSBPcIYfrkmuCj+8H5iF5zwv Fkxh3jbom/es0GXZYeZF8kyoExgotdrTFr1ktfPSwQu6LoRYPnGM2XmsFC+rsIDIf3t3 PhMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/SL8q2dwvbYeVuTEnBKl6DpDMvlUzzgP15YR7GVxGo8=; b=o6UizGVYOn+ENhrp/Il6B8aU2Th7iishTgVDSlQvndj2gZH4gFcamlvlhvIzDnDW5U ODxNtZoX/D5okYMQehf/x8tt0MCsV8GrMF/+LgKbStkGK1Cl2c/m/umEDNtVrtvT62GS cY9nHJu3AdMgAmZpF3J00wCufz4AE/qF5Skqf9/phvTaOqL3RzPgiPdpnxMWqRVOY/pD blEH6ws/jugOtVrwUVm0+Ejj3IyXHTz8r6UbRx/aS3tFjmyaZW3jTkCw3/jwAccMjH2R Fhm3wXBEs3b8xO4DmStodD5huYF+Ofa9clnJYm5aMXSqogospXZQJBzTTpx5uORD9z0t 4Oag==
X-Gm-Message-State: AOAM532eQBntIJ3mdlpfzKQ2Ip7NJcAT+ChEnKMKg09brOu8jm08sxBg osg3uwV4yLXKUJd+2GozTr7xlFpCQm7r/fABBw8=
X-Google-Smtp-Source: ABdhPJz8Z75pOmvnc+HE3jwCO4IJ6GjyNM3AFIn4Z/6368bPjAsC0zmWoA6AAfl7ihUTGxfZslKR1RycN4fAmZhvTzg=
X-Received: by 2002:a1f:30cd:: with SMTP id w196mr9571428vkw.13.1611778248344;  Wed, 27 Jan 2021 12:10:48 -0800 (PST)
MIME-Version: 1.0
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it>
In-Reply-To: <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 27 Jan 2021 12:10:37 -0800
Message-ID: <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f3098205b9e75d65"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rrgj4YgioZE1VjDG-jSzLh4_Usw>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Wed, 27 Jan 2021 20:10:51 -0000

--000000000000f3098205b9e75d65
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 27, 2021 at 9:26 AM Alessandro Vesely <vesely@tana.it> wrote:

> AFAIUI, there's no reason why SPF would work with a logic substantially
> different than DKIM's.  DKIM can provide n identifiers, if one of them is
> aligned and "pass", then DMARC is "pass".  SPF can provide 2 identifiers
> but
> one of them is of class B.  WTF?
>

DKIM (in its simplest form) returns N tuples of the form (d= domain,
pass/fail).  All of them were run through exactly the same check; all of
them were attached to the message in exactly the same way; all of them have
essentially identical semantics.  Giving them equal footing makes sense to
me.

The two identifiers in SPF hold different places in the SMTP session, and
have different semantics.  I think treating them differently is also just
fine.

Can anyone explain why we have a <scope>helo</scope> element in aggregate
> reports?
>

Not off the top of my head.  If it's not meaningful, it should go.

In addition, as I said, SPF filters are likely to report HELO as helo and
> MAIL
> FROM as mailfrom.  If we want to carry over this quirk, the spec must say
> that
> a DMARC filter which gathers SPF authentication status from an upstream
> filter
> MUST make sure that mailfrom is empty before validating based on an
> aligned helo.
>

...or it doesn't evaluate against SPF at all in such a situation.

Dropping that absurd discrimination between SPF identifiers would make for
> a
> smoother spec.  Since non-null mailfroms are in most cases aligned with
> either
> From: or helo, the differences between existing compliant implementations
> and
> the smoother spec would be limited to a hardly noticeable set of test
> messages.
>

I don't think we should ignore what those two identifiers mean, how likely
they are to contain junk, how they are applied, outside of DMARC, etc.

-MSK, participating

--000000000000f3098205b9e75d65
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jan 27, 2021 at 9:26 AM Alessandr=
o Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote=
:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">AFAIUI, there&#39;s no reason why SPF would work with a logic =
substantially <br>
different than DKIM&#39;s.=C2=A0 DKIM can provide n identifiers, if one of =
them is <br>
aligned and &quot;pass&quot;, then DMARC is &quot;pass&quot;.=C2=A0 SPF can=
 provide 2 identifiers but <br>
one of them is of class B.=C2=A0 WTF?<br></blockquote><div><br></div><div>D=
KIM (in its simplest form) returns N tuples of the form (d=3D domain, pass/=
fail).=C2=A0 All of them were run through exactly the same check; all of th=
em were attached to the message in exactly the same way; all of them have e=
ssentially identical semantics.=C2=A0 Giving them equal footing makes sense=
 to me.<br></div><div><br></div><div>The two identifiers in SPF hold differ=
ent places in the SMTP session, and have different semantics.=C2=A0 I think=
 treating them differently is also just fine.<br></div><div><br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">
Can anyone explain why we have a &lt;scope&gt;helo&lt;/scope&gt; element in=
 aggregate reports?<br></blockquote><div><br></div><div>Not off the top of =
my head.=C2=A0 If it&#39;s not meaningful, it should go.</div><div> <br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">In addition, as I said=
, SPF filters are likely to report HELO as helo and MAIL <br>
FROM as mailfrom.=C2=A0 If we want to carry over this quirk, the spec must =
say that <br>
a DMARC filter which gathers SPF authentication status from an upstream fil=
ter <br>
MUST make sure that mailfrom is empty before validating based on an aligned=
 helo.<br></blockquote><div><br></div><div>...or it doesn&#39;t evaluate ag=
ainst SPF at all in such a situation.</div><div> <br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
Dropping that absurd discrimination between SPF identifiers would make for =
a <br>
smoother spec.=C2=A0 Since non-null mailfroms are in most cases aligned wit=
h either <br>
From: or helo, the differences between existing compliant implementations a=
nd <br>
the smoother spec would be limited to a hardly noticeable set of test messa=
ges.<br></blockquote><div><br></div><div>I don&#39;t think we should ignore=
 what those two identifiers mean, how likely they are to contain junk, how =
they are applied, outside of DMARC, etc.</div><div><br></div><div>-MSK, par=
ticipating<br></div></div></div>

--000000000000f3098205b9e75d65--


From nobody Wed Jan 27 12:13:22 2021
Return-Path: <superuser@gmail.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 0E5423A0ECB for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:13:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Xqnm4KCGHWHk for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:13:19 -0800 (PST)
Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61FAF3A0EC4 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:13:14 -0800 (PST)
Received: by mail-ua1-x92c.google.com with SMTP id i3so1193646uai.3 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:13:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3xfvEFOKChbQZQZE22PZykv7ACVV76y7WMwqZPuFzJ8=; b=ssF4DT5uRJNFvnJibff6963YH3uu9PNyCh9Q2uHKCLDT6yPCS/WxK0/GlP5/V0l7WX Up7QKkNSc2zjCGhuXr/73uavOwfeAa5Foauzu7FYUa+YdyaynPO7tZzgarOP6Mm3tH// 5GqRmQ35rzgRoJ1h9iI6+CMfgCEVajOXAlooAOdfee2YUrQlxSzSC8ezTYjmXRJgD8gy iutdwUWjW9LHJZQGPNM5XeRSZ0DmjSqO3fzS1LVdrThmmYc0XnpRFueWnEEVJOgizVVA aDmQgiMZSOypsDaDyk9LOHRV6FUUNCUJ+ltWFkAsI8jgX6uhFOOf7maORrl2pLqpMaM/ ET5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3xfvEFOKChbQZQZE22PZykv7ACVV76y7WMwqZPuFzJ8=; b=tXl13vHzkbYLjw8rmLL/t5gkZHu9XFmj0+ASJEj3RWX7dVcdH8rNtXs1iXueFlZWdb uXM7lOgUl1PErN/EA4SnAWyoyyQC/HdaEByBVWlZcB0J5wuSals+4+QxIqPCOVKZWeXC /W4iVoXD+SqQX5CpcvMXk5xJAJTfk4R9la4HSH5afOG/eP12IPAz9PuPiqkFRoksk6g7 gF5tG7WMNZqaA1AE4iOg/MPI3BQiWMhFpIneLxVpTFdSp0LbA2TvY+2e98DWNqVJYHY9 PNsx1YXobHAdnG5zAUK+WW9PA3tKh9/7Vsv9zgQCeEidiwI2qaqynfzvb5YRoreFliU9 0FAg==
X-Gm-Message-State: AOAM5306D5/OM0TWEtnsyA5z+NHkD8+cfVquNqFZSOc1yf1zcFW1w/2Z +c/SaUe5Bq6QT87qOoazQ4CnoN64ig0OTR9npBQ=
X-Google-Smtp-Source: ABdhPJz5yL08pizsfFY0ah0AHB2sIhYLOlzn0tRwi5GvpCJgjuPoOW+9ce4JzSvKsFXYmE0VXYsAdQs86bZ+zFFZGNQ=
X-Received: by 2002:ab0:581:: with SMTP id e1mr9399876uae.47.1611778393365; Wed, 27 Jan 2021 12:13:13 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <20210116034026.5C93F6AC0428@ary.qy> <CAL0qLwatEsNrfF5GeWoVhrk_By8K84mYdBNOUFiN7cBaAch8JQ@mail.gmail.com> <29f5c140-6b07-e3be-f188-8b2104690385@tana.it> <52ea482c-86f8-f879-eefb-ff14e8819b56@taugh.com> <d54e8930-5266-7622-183d-023f9e35e385@tana.it> <13f04f5a-4176-db79-ca4a-a99686e76edf@taugh.com>
In-Reply-To: <13f04f5a-4176-db79-ca4a-a99686e76edf@taugh.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 27 Jan 2021 12:13:02 -0800
Message-ID: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: Alessandro Vesely <vesely@tana.it>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000097e1bb05b9e766ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/De4bVfHFxcq9nKOS6MKVkhYXyzg>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Wed, 27 Jan 2021 20:13:21 -0000

--00000000000097e1bb05b9e766ed
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 27, 2021 at 10:38 AM John R Levine <johnl@taugh.com> wrote:

> Stop there.  If you don't want failure reports, don't send unaligned
> messages.
>

I could be sold on the idea that there's not a problem for us to fix in the
protocol here, but what about the notion that it's something that might
warrant a sentence or two of informative text (i.e., that this is a problem
that can occur and possibly cause operational pressure)?

-MSK

--00000000000097e1bb05b9e766ed
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jan 27, 2021 at 10:38 AM John R L=
evine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:=
<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">Stop there.=C2=A0 If you don&#39;t want failure reports, don&#3=
9;t send unaligned <br>
messages.<br></blockquote><div><br></div><div>I could be sold on the idea t=
hat there&#39;s not a problem for us to fix in the protocol here, but what =
about the notion that it&#39;s something that might warrant a sentence or t=
wo of informative text (i.e., that this is a problem that can occur and pos=
sibly cause operational pressure)?</div><div><br></div><div>-MSK<br></div><=
/div></div>

--00000000000097e1bb05b9e766ed--


From nobody Wed Jan 27 12:14:30 2021
Return-Path: <superuser@gmail.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 E2B743A0EC1 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:14:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 T_u42-4h2B7H for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:14:27 -0800 (PST)
Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88FBF3A0EBD for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:14:27 -0800 (PST)
Received: by mail-ua1-x933.google.com with SMTP id k22so1205018ual.0 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:14:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ndtMCPYPcinIFmQTFY06EdRY//FdkPY+kKQQXTgt9Iw=; b=VuJdai1Xj2kVTb20Vppv60Jkdlr3J9mwmjABVjosbpRxYoFfTeqsNN8d1zoVANWFwm YW2ioOyseEo17geDKn0bEileDE1LGaXScspjCllzFYkqfjxQWoVFXx3iU2hmjq1xoY7w pwL0LULhHaWymvZFXB9GrZio4goNlLTyuifqx7w+CEGsVbHjz1G2w7hGNscYXsNWLcHr ZSbZQWeKHqZHXSyNmrXnl0Bi0NSBSIFD3jMuPwcF5H9+JRhUm5KiVL/DeJyGvuVgFCl4 Ncl1qqaPFEnz/zSGO+PKzA+xlWB2wQ9EMKCv5lxWo6JbI7rZ2RU6KYuQnI5ya2yk8TkS ZlLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ndtMCPYPcinIFmQTFY06EdRY//FdkPY+kKQQXTgt9Iw=; b=oLijHUaE0T8kgUmorBxDIMfYUzyc8ns1gAbiolBrgYgMWLWl+WsBnTXSJnKMW3yYq9 rLC7X2V6QUS1gLu+qzFrpiq4LhLiMFuPmTAOekIxRAcOo5ZiIRCRi0nPeBNHN9BS5Ewn PfOdBYVmyxg9Ox4mQk3CffsLalimqbFri0fsh866NAwrwlGlhrfIJVKBUZ2BpPOPjXdW pGsPySy9ywjfoF8Au1cKWB0ROyseYODb9Zz97MRslcL0niMnDfMzRpGLLZexTkljDXGo dqeDXfEGPafskgzRZynrN7cSe510INiVS3G3H5XN5FIH1+prYEP57Q7krj0o4K18duHM pb4g==
X-Gm-Message-State: AOAM531ZCVtlgDxwP6Vp+QOjxJmm/Mri/Omi9vZVtf1OOA0rICFArhUA xHjMg/8lHcfpmVjpXuV/0PVx+P065SaMIUHIkYQ=
X-Google-Smtp-Source: ABdhPJwEOiSD4LClgYD/JGdJUeuzxMzbdum7CfkmUUPJeshyUyol6i9tXemIokAwPmiNj+XE4bzr9Fyfvm2FpP0OGA4=
X-Received: by 2002:ab0:2a1a:: with SMTP id o26mr9728287uar.101.1611778466167;  Wed, 27 Jan 2021 12:14:26 -0800 (PST)
MIME-Version: 1.0
References: <2aaebb6b-6518-19cd-d32d-8370c0adb6d6@mtcc.com>
In-Reply-To: <2aaebb6b-6518-19cd-d32d-8370c0adb6d6@mtcc.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 27 Jan 2021 12:14:14 -0800
Message-ID: <CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eec22105b9e76a0d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xac5cXVlTkIKKg0oIzIyebMNBDs>
Subject: Re: [dmarc-ietf] understanding section 7.2
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: Wed, 27 Jan 2021 20:14:29 -0000

--000000000000eec22105b9e76a0d
Content-Type: text/plain; charset="UTF-8"

The schema's already pretty large, and probably has to be, but maybe a
trivial example report would be reasonable to craft and include?

On Tue, Jan 26, 2021 at 11:05 AM Michael Thomas <mike@mtcc.com> wrote:

>
> So I'm an outsider who has not tried to digest what's going on in the
> reports until recently so my eyes are fresh. Basically section 7.2 is
> extremely hard to understand what is in the reports. I know that the XML
> is what ought to be normative, but a little bit of ascii art could go a
> long way to helping people understand what the reports do and don't
> have. I've been staring at the XML all morning trying to understand it
> and it is very difficult when all you're trying to do is figure out what
> the reports supply or not. It would be extremely helpful to layout what
> is in each record for human consumption to just understand what the
> reports do and don't contain.
>
> Mike
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000eec22105b9e76a0d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The schema&#39;s already pretty large, and probably has to=
 be, but maybe a trivial example report would be reasonable to craft and in=
clude?<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Tue, Jan 26, 2021 at 11:05 AM Michael Thomas &lt;<a href=3D"ma=
ilto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><br>
So I&#39;m an outsider who has not tried to digest what&#39;s going on in t=
he <br>
reports until recently so my eyes are fresh. Basically section 7.2 is <br>
extremely hard to understand what is in the reports. I know that the XML <b=
r>
is what ought to be normative, but a little bit of ascii art could go a <br=
>
long way to helping people understand what the reports do and don&#39;t <br=
>
have. I&#39;ve been staring at the XML all morning trying to understand it =
<br>
and it is very difficult when all you&#39;re trying to do is figure out wha=
t <br>
the reports supply or not. It would be extremely helpful to layout what <br=
>
is in each record for human consumption to just understand what the <br>
reports do and don&#39;t contain.<br>
<br>
Mike<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000eec22105b9e76a0d--


From nobody Wed Jan 27 12:18:56 2021
Return-Path: <mike@fresheez.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 60C693A0EE8 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 aOc12G-7STAA for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:18:53 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEADC3A0EE6 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:18:53 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id t29so1944317pfg.11 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:18:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=/kBUw+B/MtANDZxQujkhQ/EacExCW9cdYVIFdQKgAKk=; b=Bqg2HSofF7BVbY6c3L8/hv/1kr7IiIUDcl3w2CeVfp7DI5/uuwO94j0uxfUm03i0e3 zn57JU8iAYT+3pZVbxvRJe767Eqe+aaT8ovU15Zv+ek/OJ4kSNmkaRn26Orvz95u/Xax 77oSmkDJ/B7aIqJQf1WzjqG+l7yVkNTBy90HH+pi1/LAD2yUcQBlmuDAYyMKhe4W50y4 8QGsDN3MmaYLh2MWvkZmF0gzDcZWXDOhEF9F6KDFeUQ/vMt9f7E1AprfWHw3GwXYUsvf wTUa5lawGP3YYe9MBA7GT7QUmzEaLRnwC1Tp5LTMw8mZV0Q8n/SDu6b1cKlatE82pkKO hfIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=/kBUw+B/MtANDZxQujkhQ/EacExCW9cdYVIFdQKgAKk=; b=V/GoKP4UlV/JhOnfnX9f+JCcI9QXWR/doq5EgcHasyNk5CQT2g9MoRhCm3N6eP184+ rlX3eTvDcpPUCNGoB8EvPsu+iGnCVtQli8g2fHrliaCtQ90TswYFPFs1HHU9amqX6bAa 8xRA4nM2Zuq4hK2ONJ3yMM8uNiJVxsiaBhniNxrRiKNpr1X/1bgjYx8ZJ2JwRw+IWo8+ dTH9z0tC0KP+IMfrROauBMXIo6iBlqUXWlvXL0SyUFXRpZkg/VZYQM7BZA+q93XDkEvK eYKJzq9PhhsM+WT9WldXZoU5w8aWDXSeOkH6vbBDWi31JtrWyNkAW3jNwN3n7lNxxvk/ J0vA==
X-Gm-Message-State: AOAM532txXmYLfdYUax/tGWrADxdID7jqalY2sGR+ZCheUegPzP+iUQ5 EKaFv4TIff3guR5EymfI0vG+eB5RZR7EPw==
X-Google-Smtp-Source: ABdhPJzz8hW8SIEPkoG7udXKuTYi4HRZMme1XkDsdcplWgeqajhKz/acfr1xGWTRXgdNWf66JV71HQ==
X-Received: by 2002:a63:48b:: with SMTP id 133mr12808293pge.139.1611778732927;  Wed, 27 Jan 2021 12:18:52 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id t22sm3444945pgm.18.2021.01.27.12.18.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Jan 2021 12:18:52 -0800 (PST)
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
References: <2aaebb6b-6518-19cd-d32d-8370c0adb6d6@mtcc.com> <CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <204a52fc-92ef-bc3c-2870-12e14911ae11@mtcc.com>
Date: Wed, 27 Jan 2021 12:18:50 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------978D2CB66081987D4FBEA38C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YNB3tD-vyQvT66kid7tDXGFHU44>
Subject: Re: [dmarc-ietf] understanding section 7.2
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: Wed, 27 Jan 2021 20:18:55 -0000

This is a multi-part message in MIME format.
--------------978D2CB66081987D4FBEA38C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/27/21 12:14 PM, Murray S. Kucherawy wrote:
> The schema's already pretty large, and probably has to be, but maybe a 
> trivial example report would be reasonable to craft and include?

Yeah, that might do too. I think it's important that it be in section 
7.2 though because you should be able to read that section and 
understand what the report is and isn't.

Mike


>
> On Tue, Jan 26, 2021 at 11:05 AM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     So I'm an outsider who has not tried to digest what's going on in the
>     reports until recently so my eyes are fresh. Basically section 7.2 is
>     extremely hard to understand what is in the reports. I know that
>     the XML
>     is what ought to be normative, but a little bit of ascii art could
>     go a
>     long way to helping people understand what the reports do and don't
>     have. I've been staring at the XML all morning trying to
>     understand it
>     and it is very difficult when all you're trying to do is figure
>     out what
>     the reports supply or not. It would be extremely helpful to layout
>     what
>     is in each record for human consumption to just understand what the
>     reports do and don't contain.
>
>     Mike
>
>     _______________________________________________
>     dmarc mailing list
>     dmarc@ietf.org <mailto:dmarc@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dmarc
>     <https://www.ietf.org/mailman/listinfo/dmarc>
>

--------------978D2CB66081987D4FBEA38C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/27/21 12:14 PM, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">The schema's already pretty large, and probably has
        to be, but maybe a trivial example report would be reasonable to
        craft and include?<br>
      </div>
    </blockquote>
    <p>Yeah, that might do too. I think it's important that it be in
      section 7.2 though because you should be able to read that section
      and understand what the report is and isn't.<br>
    </p>
    <p>Mike<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
cite="mid:CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com"><br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Tue, Jan 26, 2021 at 11:05
          AM Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
            moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
          So I'm an outsider who has not tried to digest what's going on
          in the <br>
          reports until recently so my eyes are fresh. Basically section
          7.2 is <br>
          extremely hard to understand what is in the reports. I know
          that the XML <br>
          is what ought to be normative, but a little bit of ascii art
          could go a <br>
          long way to helping people understand what the reports do and
          don't <br>
          have. I've been staring at the XML all morning trying to
          understand it <br>
          and it is very difficult when all you're trying to do is
          figure out what <br>
          the reports supply or not. It would be extremely helpful to
          layout what <br>
          is in each record for human consumption to just understand
          what the <br>
          reports do and don't contain.<br>
          <br>
          Mike<br>
          <br>
          _______________________________________________<br>
          dmarc mailing list<br>
          <a href="mailto:dmarc@ietf.org" target="_blank"
            moz-do-not-send="true">dmarc@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/dmarc"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>

--------------978D2CB66081987D4FBEA38C--


From nobody Wed Jan 27 12:37:19 2021
Return-Path: <johnl@iecc.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 451623A03FA for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level: 
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=FkYIPMFX; dkim=pass (2048-bit key) header.d=taugh.com header.b=dA5v+byT
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 H0JOz-mAPNeX for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:37:16 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 A3F7C3A03F3 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:37:16 -0800 (PST)
Received: (qmail 38719 invoked from network); 27 Jan 2021 20:37:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=973c.6011cefb.k2101; bh=8w4SeMz/BfJIi0znR1et85e9OldGyqBiVRx0csAuT2Q=; b=FkYIPMFXEyHFxgOxUna8RQPDOybBQPF77TzfRYAFd3FD+/ezu+DbOr/VdXokzvzWUPke3Um/nqo9CkGA/yGx2Avfb8sq2YPsj6uNkX4o0PDUeQD8WaCO3fYfbOIvk9Ro7Utayu3CiMkl6j3NtZRO4za+kAoxIqiS3w2qgdo6PHUXJ0gH4J47Uv9MTzXYCtg6Ff3+MI85ReRbpQFa0Xf/3rL7ax/oe8iXRfFpKd1U2tSagvXpaZvlPk9chhjmwOyvSo70qS0JXWot6vi5i5/dhgdzKKfrqCt1gtzKx0UulbrJjPTuY2F8orPffQ2r9KBDhZ9hVoYe8XydSyZxaJECBw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=973c.6011cefb.k2101; bh=8w4SeMz/BfJIi0znR1et85e9OldGyqBiVRx0csAuT2Q=; b=dA5v+byTrVcRuO5IO7yVlhD7z/1Upe/0z1eXw0l99PiW2CITHWPL6iS9FFSJn8iyQ3mkfz08kIfPB/UTaRzc++5iF0qly1RK5LCf7Zv5W9XnH8vPGOl/e5BwcEKLOV2hqigHDLpMLVcuqe1fimtIBTJVCf/TauNi5LfmKmKI4YUXbCm64TERPNgxxTp3oYKkP1ndPe0LAXwit1JjWPWots4WA9HkH9b9+NKLI8J5maMkDrT4d0Bx59grgpLPy6Sybme1DUPAIKiA1nUCO1AQdWHQx3ByHWW6+LfUbqfovATTqC+OBj2ZQi+G246vMKC0hOHoUGBQqMypsa1wk9G4sw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 27 Jan 2021 20:37:14 -0000
Received: by ary.qy (Postfix, from userid 501) id 007C86CDB9CA; Wed, 27 Jan 2021 15:37:13 -0500 (EST)
Date: 27 Jan 2021 15:37:13 -0500
Message-Id: <20210127203714.007C86CDB9CA@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: superuser@gmail.com
In-Reply-To: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/FS9riHMFGX8EbmtJD2M2PATMRSg>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Wed, 27 Jan 2021 20:37:18 -0000

In article <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>On Wed, Jan 27, 2021 at 10:38 AM John R Levine <johnl@taugh.com> wrote:
>
>> Stop there.  If you don't want failure reports, don't send unaligned
>> messages.
>
>I could be sold on the idea that there's not a problem for us to fix in the
>protocol here, but what about the notion that it's something that might
>warrant a sentence or two of informative text (i.e., that this is a problem
>that can occur and possibly cause operational pressure)?

I still don't understand why failure reports about messages that
happen to be failure reports are in any way special.

The report is after all a brand new message which I would hope is sent
the way tou send any other message, and should be aligned if the rest
of your mail is.

R's,
John


From nobody Wed Jan 27 12:41:21 2021
Return-Path: <Alex_Brotman@comcast.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 41BE83A045E for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, MISSING_HEADERS=1.021, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.com
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 Gb-GmxKPb3CO for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:41:18 -0800 (PST)
Received: from mx0b-00143702.pphosted.com (mx0b-00143702.pphosted.com [148.163.141.77]) (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 8ECE93A0408 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:41:18 -0800 (PST)
Received: from pps.filterd (m0184890.ppops.net [127.0.0.1]) by mx0b-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10RKaMAG021161 for <dmarc@ietf.org>; Wed, 27 Jan 2021 15:41:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.com; h=from : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=20190412; bh=w6SdpDPxGc9hiTEbG1vRM+YS158L9TmLlZ1CWAJyTaM=; b=KQKYHh5azVxdozUTa84xQQt19OENbJ+XptQT/cK4kACJF6BAczm5VDp0VYv/cgl5N/gv 1Yz7e0Mjsb1teCwaOAwtRVKtznKh124C91WO30ZQZ+m2PpMxGCGD+SqJTqQykMamK3Vc 9ch9RJ1h9mGICoKNtiXz4RjfhorLJZwLmLhLeEaDEXn6M3VaU8TbCrOu2y5O7nxd1jAd CY4XpGU4WUj6j5bFYvHYQR5wSzrIrxoiLDDcupMySmcknyekLlNo4hNbTitGzPoJ5NrZ DohrFtiMosMgfVui+x1iciOV31E4A0nSUnqmelHaVqsnCjFYd0+gqYz7z1dk0ZRfD8WO JQ== 
Received: from copdcexc37.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0b-00143702.pphosted.com with ESMTP id 36bemagb6f-17 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Wed, 27 Jan 2021 15:41:17 -0500
Received: from copdcexc33.cable.comcast.com (147.191.125.132) by COPDCEXC37.cable.comcast.com (147.191.125.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 27 Jan 2021 13:41:03 -0700
Received: from COPDCEXEDGE01.cable.comcast.com (96.114.158.213) by copdcexc33.cable.comcast.com (147.191.125.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Wed, 27 Jan 2021 13:41:03 -0700
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (104.47.66.48) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 27 Jan 2021 15:41:04 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4079.namprd11.prod.outlook.com (2603:10b6:208:153::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.14; Wed, 27 Jan 2021 20:40:44 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::7ca6:b482:a6b0:4d42%7]) with mapi id 15.20.3784.019; Wed, 27 Jan 2021 20:40:44 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
CC: "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] understanding section 7.2
Thread-Index: AQHW9BZWdYYoQp/lmEWDwXUnt/mWM6o76ckAgAAHCSA=
Date: Wed, 27 Jan 2021 20:40:43 +0000
Message-ID: <MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <2aaebb6b-6518-19cd-d32d-8370c0adb6d6@mtcc.com> <CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com>
In-Reply-To: <CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:c3c:9b3f:bc45:71ca]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e14f7623-fe8a-4424-8297-08d8c303d18c
x-ms-traffictypediagnostic: MN2PR11MB4079:
x-microsoft-antispam-prvs: <MN2PR11MB407910B61C2470C54F8A0FB4F7BB9@MN2PR11MB4079.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 4mxLFPx2F3y9pTE6ubSvLosbI2JqheFO3wA0UdK0PB4ngl7+irOYVLKrQ4Aysr5c/6O6euFzp6ikmtL0pTJaamkO2kLORY2dld/n+S/J0DaLKtWhWgN9ZozTOXs1N02qJzpfcaIhiGeJ5bGAxv8vhunN4akxxHatgVfCoVwHKtgxQwzDhuvjbi5DzpimEJI5O8jy7qKOfDTnM7AdkCCKO/xE5fv+LbJ1ZoZi3CYKG3NbMh/4JEXQ1N17QuGV4iMdfk5YLTb3Coys4PfGRnscAmGe8qsjBH0eFtRUYv5dfEuXzoipDvHCt7Ukqyh3/8HVcHnomXnaTceLX4vp8DTpC+Mnn9Q8pLAyblZIyV0jn0sZoFBWvxsjShFiJxGTy4VCpLZ6sqOzgS8MfoWqaQQKYSh/2d8UfeAqE1Gf3OQUOq/e50vx/S7oPoNs8U/9szZJAk3myUecQ+AsjuwTXxeuxhCCbam0WyGeqSKiDuOtVzL59ebNQY+1z+f3Ez3Jlme2UGg6VDbSTjJf6SMggczWd4Oopoog9AZQEZasM0Q7gHeEzMxIHuDK+PEyuOLAJYPwbVPzT2DVz7FTlNjR6elD81RgSas6Po5UdobxxwtTD5I=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(376002)(136003)(346002)(396003)(366004)(76116006)(966005)(66946007)(2906002)(66556008)(64756008)(66446008)(83380400001)(33656002)(478600001)(166002)(5660300002)(52536014)(86362001)(7696005)(66476007)(53546011)(8676002)(55016002)(9686003)(6506007)(316002)(109986005)(186003)(8936002)(71200400001)(4326008); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?QzZzdnp1dzNVTHE3V3VnWG9zL2JCQlN0UlBCamtQb1lkSE12dUErMGJ2dmN6?= =?utf-8?B?cm8zV3ovQkZIdXA2VFIvTkxOSlluTmNOOUdpSFJwUDFQUCs5RzVMUlNRYVor?= =?utf-8?B?SVhGMy82YnN3MHJUWmcwajR6MjNQMFpvQXVHVU1WVko5KzJFdkEzdjE4bkF0?= =?utf-8?B?U3NYbnEyWFI1RlZQK1hramljU2tkSnlzdDhOL2JaVHVLR1dqNmx5NEw0azQx?= =?utf-8?B?cEVZdHdrZk5DdDlnMlJnc0RVT3g1SUxCY2llQ090akx5UEd4dHczdnhNcGtN?= =?utf-8?B?WmJna09tc1FZT1JNbElZdHlZa2V5U2kxU1dHQnNCUzJrRTNoT1YwWW11MmNJ?= =?utf-8?B?SmdzTklpWnludFdybTA5eFJpV2dLNnFFQVZCR014NjdlVkRkVjhVQUwzVWtU?= =?utf-8?B?N2xYSUdhT29EL3hXdkdOR0NuWUFRL1JEamxPTHIvTms5WVo3WE1yUEN2Q3d2?= =?utf-8?B?ckRDMlZYWHYvdzNOUk92YzRlZUtUVjN0SkVsYVRpNEVJUEpXOGFiZXFzNnpS?= =?utf-8?B?MzVpMDFqd1lBT21xMVJCY0N6bE1CNXlVMEhuYVJ5SzIvRGNwMStaajRiZzVU?= =?utf-8?B?enhyZWxGS3Vja2x2M3dxYm9GY1RISEhsNGIzYmZNMDcvQ2Y0QmpGNDlMSE1l?= =?utf-8?B?QWZUSTQ2d1MrTmFMNlk5aFBBS1V5eXpxb09JN2ZHeUFTVU00Mm9PYUpwNnJ6?= =?utf-8?B?T2dUZlZTK0V6dHNxVzc4Vyt6VkhVZmUzbHViMW8yQkVqU1pmTXZ1dmRzVy9u?= =?utf-8?B?amtBaXdGR2l3SG5kYUZKWW1HcmdQR3R4UHhuM3B5dVZvSTJRaVo5SjloNk1h?= =?utf-8?B?T3pVQTFYVEF5UjBPbkFOeUhVL0FOUmRIbTFwYWRYaFlJRTNOaFVaTWJ0S2pp?= =?utf-8?B?OW9mZjg0Q05aUkV6Q1N3bVZ1aDgrTXRwMXlDMVI3QXc2Q2pvOEFvUStlbFRY?= =?utf-8?B?UUNPcy9zck9VaGtsdWJ3QXB5Mjh1SDEwYTJ0aGZkTTBWVTZlSHhkeCtMTFh5?= =?utf-8?B?SFRTOXNBT0dnVHMwcnlRSmpXRzVtcmpESXBjQ2s4ckZzcUhuT1MvcGd1Lzlr?= =?utf-8?B?S0hTSnNIblk1VTZqRTV2MzEvSkl4SGZpMEthMjJSdUpoVmhmazJlbDhuVW5V?= =?utf-8?B?STN0alVjRk5yVWdScmhxTm5nZ0RCenIwYUptMVNacmxJZGpJUmI4bk5qdWZw?= =?utf-8?B?dkhTVllmWTdzWklic0p3dmZxdHd6Z0RoUGZxdGd5WHgrQWt1WWRsdDk2ZEtF?= =?utf-8?B?WkJWOXFDZVh6UDBkYWhxTnI5VVdyNjJkRFh4K1p1YXh1QVJzVERVS1FNUWFt?= =?utf-8?B?WWI4SGJFRGhXdDFwL2RsWG9ORjVaQVFLOHVPWTFiS01ZbHNmUjVVYmZpRjFa?= =?utf-8?B?NlJ5RitXbFF2R2tkZ3M1b0svaVMxWXQwTHpZbWE5VEhmSDZIdXJiQTJDRTZH?= =?utf-8?B?Rml5azdia0dEQys4eXBuL1RyZ2ZjQ3VRZWc4L05NN2d0amxvNVNzYXNZTEkz?= =?utf-8?Q?WD0hkQ=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BscKRSbhzIUN7LmGv3bQlv/RZ63ZFuglgTdg+r5dT6PEFupi49xK3WXGiFpaJQiiuOYGoV+XNfiWVZxXLtgJ3vg1bFG/U4RUXBKd/0RwigtMHeubMbKWU3W+kUyyeYak9OZtq95cEHVjyPoSLEXLt+xQWRZtv4/Hy3ekhRZSEBQHEYHEOCHKnbfIL/jLt+lzk+UaLfJpHSgW+0vddm7UXP64/b1zYLw/9T7pJ7tPMdddSbBlMQkyBJhr+8ooDpqdyxEO5S0rCc6EHzVY9juBxGgt7G7AHnBitdPBjmCGqFUjN+h8/4CTp6QCEZmip53SYvKg/LBcw4ptu3Fo3T4duA==
arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dpeHssMOVGQdef0CM/Qb8+rDVINMaEYfLzAtKGhB704=; b=Tm6oAEIRBTC7FCEjFJ9aOoFRfJJQpyeGHSmL6r5AtOyjjEONcenas0+X6rOYGKcTGzv4Qnw4LeivFp4M/Ef5Irx1wCvi0ju8EEPvNaYo/8/B507nQX4j3v4ksUur3v+rOf9mdokEaEeEEjyUrrawrRTfZWVOc4V8wBqD20iy92nYo8h6tRY2r86ZVvTXX8Dz6CWtzaAD/00h8L+2tZV9S3w7hiqhSIlYNO8KvU4xE+tp3kQOhFvXni0vEw/MJwqk9Tnz4G2UoNEpd3ZbzmW6zpy+zdO3Uitqek3Mpg01iZCXWR8hAGpkO2VfH03FHN88mIIzR7oDJBGkdKnqgMYIwg==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=comcast.com; dmarc=pass action=none header.from=comcast.com; dkim=pass header.d=comcast.com; arc=none
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: MN2PR11MB4351.namprd11.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: e14f7623-fe8a-4424-8297-08d8c303d18c
x-ms-exchange-crosstenant-originalarrivaltime: 27 Jan 2021 20:40:43.9210 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 906aefe9-76a7-4f65-b82d-5ec20775d5aa
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: GH0yZne5RZMS0PPGToUVLrADjHlbkwJjw1oUSuz3bFxwERQYFwhybbgr54uUm5rroCmfJTSvCRVHaWGXEEhLlM94TWANB4v6s73G+/MM6Gg=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4079
x-originatororg: comcast.com
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9MN2PR11MB4351namp_"
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWT
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-27_07:2021-01-27, 2021-01-27 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qSS69oMumEa1SF8j8tzgqT-_aTM>
Subject: Re: [dmarc-ietf] understanding section 7.2
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: Wed, 27 Jan 2021 20:41:20 -0000

--_000_MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9MN2PR11MB4351namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TXVycmF5LA0KDQpUaGF0IGlzIG9uIG15IHRvLWRvICh0aG91Z2ggbm90IHRpY2tldGVkKS4gIEni
gJltIG5vdCBxdWl0ZSBzdXJlIGhvdyBlbGFib3JhdGUgdGhlIGV4YW1wbGUgc2hvdWxkIGJlLCBi
dXQgYXQgbGVhc3QgZW5vdWdoIHRvIGRlbW9uc3RyYXRlIGEgYmFzaWMgcmVwb3J0Lg0KDQotLQ0K
QWxleCBCcm90bWFuDQpTci4gRW5naW5lZXIsIEFudGktQWJ1c2UgJiBNZXNzYWdpbmcgUG9saWN5
DQpDb21jYXN0DQoNCkZyb206IGRtYXJjIDxkbWFyYy1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhh
bGYgT2YgTXVycmF5IFMuIEt1Y2hlcmF3eQ0KU2VudDogV2VkbmVzZGF5LCBKYW51YXJ5IDI3LCAy
MDIxIDM6MTQgUE0NClRvOiBNaWNoYWVsIFRob21hcyA8bWlrZUBtdGNjLmNvbT4NCkNjOiBkbWFy
Y0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtkbWFyYy1pZXRmXSB1bmRlcnN0YW5kaW5nIHNlY3Rp
b24gNy4yDQoNClRoZSBzY2hlbWEncyBhbHJlYWR5IHByZXR0eSBsYXJnZSwgYW5kIHByb2JhYmx5
IGhhcyB0byBiZSwgYnV0IG1heWJlIGEgdHJpdmlhbCBleGFtcGxlIHJlcG9ydCB3b3VsZCBiZSBy
ZWFzb25hYmxlIHRvIGNyYWZ0IGFuZCBpbmNsdWRlPw0KDQpPbiBUdWUsIEphbiAyNiwgMjAyMSBh
dCAxMTowNSBBTSBNaWNoYWVsIFRob21hcyA8bWlrZUBtdGNjLmNvbTxtYWlsdG86bWlrZUBtdGNj
LmNvbT4+IHdyb3RlOg0KDQpTbyBJJ20gYW4gb3V0c2lkZXIgd2hvIGhhcyBub3QgdHJpZWQgdG8g
ZGlnZXN0IHdoYXQncyBnb2luZyBvbiBpbiB0aGUNCnJlcG9ydHMgdW50aWwgcmVjZW50bHkgc28g
bXkgZXllcyBhcmUgZnJlc2guIEJhc2ljYWxseSBzZWN0aW9uIDcuMiBpcw0KZXh0cmVtZWx5IGhh
cmQgdG8gdW5kZXJzdGFuZCB3aGF0IGlzIGluIHRoZSByZXBvcnRzLiBJIGtub3cgdGhhdCB0aGUg
WE1MDQppcyB3aGF0IG91Z2h0IHRvIGJlIG5vcm1hdGl2ZSwgYnV0IGEgbGl0dGxlIGJpdCBvZiBh
c2NpaSBhcnQgY291bGQgZ28gYQ0KbG9uZyB3YXkgdG8gaGVscGluZyBwZW9wbGUgdW5kZXJzdGFu
ZCB3aGF0IHRoZSByZXBvcnRzIGRvIGFuZCBkb24ndA0KaGF2ZS4gSSd2ZSBiZWVuIHN0YXJpbmcg
YXQgdGhlIFhNTCBhbGwgbW9ybmluZyB0cnlpbmcgdG8gdW5kZXJzdGFuZCBpdA0KYW5kIGl0IGlz
IHZlcnkgZGlmZmljdWx0IHdoZW4gYWxsIHlvdSdyZSB0cnlpbmcgdG8gZG8gaXMgZmlndXJlIG91
dCB3aGF0DQp0aGUgcmVwb3J0cyBzdXBwbHkgb3Igbm90LiBJdCB3b3VsZCBiZSBleHRyZW1lbHkg
aGVscGZ1bCB0byBsYXlvdXQgd2hhdA0KaXMgaW4gZWFjaCByZWNvcmQgZm9yIGh1bWFuIGNvbnN1
bXB0aW9uIHRvIGp1c3QgdW5kZXJzdGFuZCB3aGF0IHRoZQ0KcmVwb3J0cyBkbyBhbmQgZG9uJ3Qg
Y29udGFpbi4NCg0KTWlrZQ0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KZG1hcmMgbWFpbGluZyBsaXN0DQpkbWFyY0BpZXRmLm9yZzxtYWlsdG86ZG1h
cmNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RtYXJj
PGh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vZG1hcmNfXzshIUNRbDNtY0hYMkEhWEhCUm5tTnlnTjRYSkY0UkplWEc2UXNFbUQ1
aHF0aERPQ0w5R25UZ1RSV2JpT0YxWEpIemZqZVpVVkxVYXRWTVdPeGgkPg0K

--_000_MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9MN2PR11MB4351namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndp
bmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24x
DQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBzdHlsZT0id29yZC13
cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPk11cnJheSw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhdCBpcyBvbiBteSB0
by1kbyAodGhvdWdoIG5vdCB0aWNrZXRlZCkuJm5ic3A7IEnigJltIG5vdCBxdWl0ZSBzdXJlIGhv
dyBlbGFib3JhdGUgdGhlIGV4YW1wbGUgc2hvdWxkIGJlLCBidXQgYXQgbGVhc3QgZW5vdWdoIHRv
IGRlbW9uc3RyYXRlIGEgYmFzaWMgcmVwb3J0LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLTxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWxleCBCcm90bWFuPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Tci4gRW5naW5lZXIsIEFudGktQWJ1c2UgJmFt
cDsgTWVzc2FnaW5nIFBvbGljeTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
Q29tY2FzdDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBp
biAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBkbWFyYyAmbHQ7
ZG1hcmMtYm91bmNlc0BpZXRmLm9yZyZndDsgPGI+T24gQmVoYWxmIE9mIDwvYj4NCk11cnJheSBT
LiBLdWNoZXJhd3k8YnI+DQo8Yj5TZW50OjwvYj4gV2VkbmVzZGF5LCBKYW51YXJ5IDI3LCAyMDIx
IDM6MTQgUE08YnI+DQo8Yj5Ubzo8L2I+IE1pY2hhZWwgVGhvbWFzICZsdDttaWtlQG10Y2MuY29t
Jmd0Ozxicj4NCjxiPkNjOjwvYj4gZG1hcmNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4g
UmU6IFtkbWFyYy1pZXRmXSB1bmRlcnN0YW5kaW5nIHNlY3Rpb24gNy4yPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIHNjaGVtYSdzIGFscmVhZHkgcHJl
dHR5IGxhcmdlLCBhbmQgcHJvYmFibHkgaGFzIHRvIGJlLCBidXQgbWF5YmUgYSB0cml2aWFsIGV4
YW1wbGUgcmVwb3J0IHdvdWxkIGJlIHJlYXNvbmFibGUgdG8gY3JhZnQgYW5kIGluY2x1ZGU/PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUdWUsIEphbiAy
NiwgMjAyMSBhdCAxMTowNSBBTSBNaWNoYWVsIFRob21hcyAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1p
a2VAbXRjYy5jb20iPm1pa2VAbXRjYy5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0Ljhw
dDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NClNvIEknbSBh
biBvdXRzaWRlciB3aG8gaGFzIG5vdCB0cmllZCB0byBkaWdlc3Qgd2hhdCdzIGdvaW5nIG9uIGlu
IHRoZSA8YnI+DQpyZXBvcnRzIHVudGlsIHJlY2VudGx5IHNvIG15IGV5ZXMgYXJlIGZyZXNoLiBC
YXNpY2FsbHkgc2VjdGlvbiA3LjIgaXMgPGJyPg0KZXh0cmVtZWx5IGhhcmQgdG8gdW5kZXJzdGFu
ZCB3aGF0IGlzIGluIHRoZSByZXBvcnRzLiBJIGtub3cgdGhhdCB0aGUgWE1MIDxicj4NCmlzIHdo
YXQgb3VnaHQgdG8gYmUgbm9ybWF0aXZlLCBidXQgYSBsaXR0bGUgYml0IG9mIGFzY2lpIGFydCBj
b3VsZCBnbyBhIDxicj4NCmxvbmcgd2F5IHRvIGhlbHBpbmcgcGVvcGxlIHVuZGVyc3RhbmQgd2hh
dCB0aGUgcmVwb3J0cyBkbyBhbmQgZG9uJ3QgPGJyPg0KaGF2ZS4gSSd2ZSBiZWVuIHN0YXJpbmcg
YXQgdGhlIFhNTCBhbGwgbW9ybmluZyB0cnlpbmcgdG8gdW5kZXJzdGFuZCBpdCA8YnI+DQphbmQg
aXQgaXMgdmVyeSBkaWZmaWN1bHQgd2hlbiBhbGwgeW91J3JlIHRyeWluZyB0byBkbyBpcyBmaWd1
cmUgb3V0IHdoYXQgPGJyPg0KdGhlIHJlcG9ydHMgc3VwcGx5IG9yIG5vdC4gSXQgd291bGQgYmUg
ZXh0cmVtZWx5IGhlbHBmdWwgdG8gbGF5b3V0IHdoYXQgPGJyPg0KaXMgaW4gZWFjaCByZWNvcmQg
Zm9yIGh1bWFuIGNvbnN1bXB0aW9uIHRvIGp1c3QgdW5kZXJzdGFuZCB3aGF0IHRoZSA8YnI+DQpy
ZXBvcnRzIGRvIGFuZCBkb24ndCBjb250YWluLjxicj4NCjxicj4NCk1pa2U8YnI+DQo8YnI+DQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCmRtYXJj
IG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpkbWFyY0BpZXRmLm9yZyIgdGFyZ2V0
PSJfYmxhbmsiPmRtYXJjQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vdXJsZGVm
ZW5zZS5jb20vdjMvX19odHRwczovd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZG1hcmNf
XzshIUNRbDNtY0hYMkEhWEhCUm5tTnlnTjRYSkY0UkplWEc2UXNFbUQ1aHF0aERPQ0w5R25UZ1RS
V2JpT0YxWEpIemZqZVpVVkxVYXRWTVdPeGgkIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbWFyYzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvYmxv
Y2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9MN2PR11MB4351namp_--


From nobody Wed Jan 27 12:42:40 2021
Return-Path: <mike@fresheez.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 D8AE93A045E for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:42:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 Fh2BOUPmYHbm for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:42:36 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8ACE3A0408 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:42:36 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id q2so1718531plk.4 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:42:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=9aQk/KXte7TFQS/HYs8eryfTPBe8J6AwEdfFUvcZBXo=; b=PnF/ASNJkyz53A6QqzBSL3oCZdvQbIEOaq4mN32UV67zC3KbjXASHx27+3U6o2nwph s2us29mMzdLEfMuBrTo3f/QY9Vsg7pTSyWHau58rUCaNc2Dj6QF9FSObotEZ9Uf1qJx/ fOj/hD6XDp7FYH/FbJ5OlYBitLkTDLeYr/IHYI6/83WiJZgJUzt9eRBETvJ0jl2VeUbx ed9ZZ9M258PAb7rZ3+rhuxuECXWT4z23k3WjAna+Iy/FgCXKpPvQQ1hmGpo/5vulT1/3 70OdJF83l2mexUe2xSzFavypMuQi4G9YGIEhsEM72xWbvTNSPrEUBdEvnfxnwZy9DVpw 3Byg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=9aQk/KXte7TFQS/HYs8eryfTPBe8J6AwEdfFUvcZBXo=; b=YpK1fSSiGbVQ+PhejcR9P4QenYNG9FzKHf78EgdX6h1TZPaSqH8EFO0CZovT1o1OZv jlPPUGVxRtPgINC6rPE3a/pJD1bbRbafEPJP24sHw14v0J+jGuaMelZ5SppscpAgJGbS J/HPMC1Ovt1wzVaenhtXjubvfjbOIrEJSMW1gEMhm9imPFtiDley2k5Wxvf5AXgJjEA2 wU/jm9qoCtAKZuNkmrEmZwIMKXq2NfAV5CsZYs5QGs8U7yfk4DnpFD9OjQMcWz+MiRXO 1A+RKsMMFo0NeajWUeZtnw0pctXxDW4IWB5ZF7wH51hslnScZTmndwY4tb79VMpNN/Zw JQWg==
X-Gm-Message-State: AOAM532CfbGhpCneWge5m5K5XVI+qUC37uRzmXWU7hTJfczGXidN9orb mE2xJ5TQEVISoIEQ7jfsM062Fmx1oFGosQ==
X-Google-Smtp-Source: ABdhPJyiiGv6sT5LoTkeOxSI97YzA5vlwpEcK9JXBaSwbwVRI4+DXjFhHLv8fYUGLikIBFKpN2eWJw==
X-Received: by 2002:a17:90a:448f:: with SMTP id t15mr7763428pjg.159.1611780155709;  Wed, 27 Jan 2021 12:42:35 -0800 (PST)
Received: from mike-mac.lan (107-182-35-22.volcanocom.com. [107.182.35.22]) by smtp.gmail.com with ESMTPSA id y26sm3282448pgk.42.2021.01.27.12.42.34 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Jan 2021 12:42:35 -0800 (PST)
To: dmarc@ietf.org
References: <2aaebb6b-6518-19cd-d32d-8370c0adb6d6@mtcc.com> <CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com> <MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <b446c6da-36f3-6690-99fc-5926634242c2@mtcc.com>
Date: Wed, 27 Jan 2021 12:42:33 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9@MN2PR11MB4351.namprd11.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------E414AF0B0DA4986F99BA3323"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ehD9fZDOEgEnUMr6AKrygtK_xJM>
Subject: Re: [dmarc-ietf] understanding section 7.2
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: Wed, 27 Jan 2021 20:42:39 -0000

This is a multi-part message in MIME format.
--------------E414AF0B0DA4986F99BA3323
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/27/21 12:40 PM, Brotman, Alex wrote:
>
> Murray,
>
> That is on my to-do (though not ticketed). I’m not quite sure how 
> elaborate the example should be, but at least enough to demonstrate a 
> basic report.
>
I opened a ticket on this yesterday. I think it's 102.

Mike


> --
>
> Alex Brotman
>
> Sr. Engineer, Anti-Abuse & Messaging Policy
>
> Comcast
>
> *From:* dmarc <dmarc-bounces@ietf.org> *On Behalf Of * Murray S. Kucherawy
> *Sent:* Wednesday, January 27, 2021 3:14 PM
> *To:* Michael Thomas <mike@mtcc.com>
> *Cc:* dmarc@ietf.org
> *Subject:* Re: [dmarc-ietf] understanding section 7.2
>
> The schema's already pretty large, and probably has to be, but maybe a 
> trivial example report would be reasonable to craft and include?
>
> On Tue, Jan 26, 2021 at 11:05 AM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>     So I'm an outsider who has not tried to digest what's going on in the
>     reports until recently so my eyes are fresh. Basically section 7.2 is
>     extremely hard to understand what is in the reports. I know that
>     the XML
>     is what ought to be normative, but a little bit of ascii art could
>     go a
>     long way to helping people understand what the reports do and don't
>     have. I've been staring at the XML all morning trying to
>     understand it
>     and it is very difficult when all you're trying to do is figure
>     out what
>     the reports supply or not. It would be extremely helpful to layout
>     what
>     is in each record for human consumption to just understand what the
>     reports do and don't contain.
>
>     Mike
>
>     _______________________________________________
>     dmarc mailing list
>     dmarc@ietf.org <mailto:dmarc@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dmarc
>     <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/dmarc__;!!CQl3mcHX2A!XHBRnmNygN4XJF4RJeXG6QsEmD5hqthDOCL9GnTgTRWbiOF1XJHzfjeZUVLUatVMWOxh$>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc

--------------E414AF0B0DA4986F99BA3323
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/27/21 12:40 PM, Brotman, Alex
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9@MN2PR11MB4351.namprd11.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style>@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}div.WordSection1
	{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">Murray,<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">That is on my to-do (though not ticketed). 
          I’m not quite sure how elaborate the example should be, but at
          least enough to demonstrate a basic report.</p>
      </div>
    </blockquote>
    <p>I opened a ticket on this yesterday. I think it's 102.</p>
    <p>Mike<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
cite="mid:MN2PR11MB4351F737BBF93CC2E535D1E7F7BB9@MN2PR11MB4351.namprd11.prod.outlook.com">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">--<o:p></o:p></p>
        <p class="MsoNormal">Alex Brotman<o:p></o:p></p>
        <p class="MsoNormal">Sr. Engineer, Anti-Abuse &amp; Messaging
          Policy<o:p></o:p></p>
        <p class="MsoNormal">Comcast<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <div>
            <div style="border:none;border-top:solid #E1E1E1
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"><b>From:</b> dmarc
                <a class="moz-txt-link-rfc2396E" href="mailto:dmarc-bounces@ietf.org">&lt;dmarc-bounces@ietf.org&gt;</a> <b>On Behalf Of </b>
                Murray S. Kucherawy<br>
                <b>Sent:</b> Wednesday, January 27, 2021 3:14 PM<br>
                <b>To:</b> Michael Thomas <a class="moz-txt-link-rfc2396E" href="mailto:mike@mtcc.com">&lt;mike@mtcc.com&gt;</a><br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:dmarc@ietf.org">dmarc@ietf.org</a><br>
                <b>Subject:</b> Re: [dmarc-ietf] understanding section
                7.2<o:p></o:p></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <p class="MsoNormal">The schema's already pretty large, and
              probably has to be, but maybe a trivial example report
              would be reasonable to craft and include?<o:p></o:p></p>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <div>
              <p class="MsoNormal">On Tue, Jan 26, 2021 at 11:05 AM
                Michael Thomas &lt;<a href="mailto:mike@mtcc.com"
                  moz-do-not-send="true">mike@mtcc.com</a>&gt; wrote:<o:p></o:p></p>
            </div>
            <blockquote style="border:none;border-left:solid #CCCCCC
              1.0pt;padding:0in 0in 0in
              6.0pt;margin-left:4.8pt;margin-right:0in">
              <p class="MsoNormal"><br>
                So I'm an outsider who has not tried to digest what's
                going on in the <br>
                reports until recently so my eyes are fresh. Basically
                section 7.2 is <br>
                extremely hard to understand what is in the reports. I
                know that the XML <br>
                is what ought to be normative, but a little bit of ascii
                art could go a <br>
                long way to helping people understand what the reports
                do and don't <br>
                have. I've been staring at the XML all morning trying to
                understand it <br>
                and it is very difficult when all you're trying to do is
                figure out what <br>
                the reports supply or not. It would be extremely helpful
                to layout what <br>
                is in each record for human consumption to just
                understand what the <br>
                reports do and don't contain.<br>
                <br>
                Mike<br>
                <br>
                _______________________________________________<br>
                dmarc mailing list<br>
                <a href="mailto:dmarc@ietf.org" target="_blank"
                  moz-do-not-send="true">dmarc@ietf.org</a><br>
                <a
href="https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/dmarc__;!!CQl3mcHX2A!XHBRnmNygN4XJF4RJeXG6QsEmD5hqthDOCL9GnTgTRWbiOF1XJHzfjeZUVLUatVMWOxh$"
                  target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/dmarc</a><o:p></o:p></p>
            </blockquote>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
dmarc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dmarc@ietf.org">dmarc@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dmarc">https://www.ietf.org/mailman/listinfo/dmarc</a>
</pre>
    </blockquote>
  </body>
</html>

--------------E414AF0B0DA4986F99BA3323--


From nobody Wed Jan 27 12:47:28 2021
Return-Path: <superuser@gmail.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 A48463A07E2 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:47:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KO10RBdQPqat for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:47:26 -0800 (PST)
Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC5573A07DF for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:47:25 -0800 (PST)
Received: by mail-ua1-x932.google.com with SMTP id a31so1215999uae.11 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:47:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VJBnU2e69gb8thr0xFcYbPHTziJhdJawr5FUfxhKYA8=; b=C7I7+bWpch9w9JhP0tc2XPPhZ9gc5mGEDKet1YlyDGELAaUc5h0ErBbHJTvQz6lrZM iILjPu0zxjXSBTXzHIKqnRbCUw7DKmmhuagIwWZJC5KH3EEtQmccusVX65Ai9ihAMmdT ViTRKlCd0koS5dt0pNYJSvIP7Kt0+ayAFxK5tzY6yRzxRpRWTw/1OWRTo0fE67c6NKDE tedx4oL9Xn3k7v4qQ/XQVQmNC9O3rUQqklEJSj8qfFwP4UwKrweEvD+g7NGnphLWyxfF qY6BRo03/optKYwBcKlogTJX5weUi1xUXfu6zctCagZRT2nq6lBVojeHPDL3/3inWUWa V7PQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VJBnU2e69gb8thr0xFcYbPHTziJhdJawr5FUfxhKYA8=; b=m1HDUvLnEfR1ixonZGBRpzpzPfYTuaEvtUYbxYzbxJIUT4r/ATpYZ088KvPDZvBYu4 0bUlZNwQ7q/Q2QiX/oNtXOswrEhz/MBy3BL/u8wm5fNBIqr0s7+geXVfe8Z6HoQ6cBvJ a3gresFbcpc4rHq3qh2wdHPIW3ohTdot/2RRT8KFYigydjxxxVSUINA0LuLkzMFe3zcP H1YvwgnRHvgSguRND41tKYzDgk5za8ELwVVG20pxKtPi3b4ehz810TSQ6q4N9asYAoPt 0qwDbtgYaDDY/FlNYmUj+5E6pVAOSRloaRFEH8Z8ejWKFszoc5OtOCQNVqWH7xI3OCiI iJFw==
X-Gm-Message-State: AOAM532eCLUnwzDL0L0Mx4pePuuZNEnFwDrnlX0ZAdj2DJXknDcEstZU 9h0abFFV6KlHyrR0AVqVN5J0sbU3GsnbSz1OP8c=
X-Google-Smtp-Source: ABdhPJynTAujnLmUkCuOf5Bv0DFMYeEWL/OQjb6WU+DlsxMM/5lMz5HpOBIkHYyp6mlJeTIAWLkFV84WkTqMSK8lblk=
X-Received: by 2002:ab0:2a1a:: with SMTP id o26mr9818274uar.101.1611780444781;  Wed, 27 Jan 2021 12:47:24 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy>
In-Reply-To: <20210127203714.007C86CDB9CA@ary.qy>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 27 Jan 2021 12:47:13 -0800
Message-ID: <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de00af05b9e7e0c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/t3rwbli0vSWC6rng-oTSKy87XGc>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Wed, 27 Jan 2021 20:47:28 -0000

--000000000000de00af05b9e7e0c1
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 27, 2021 at 12:37 PM John Levine <johnl@taugh.com> wrote:

> I still don't understand why failure reports about messages that
> happen to be failure reports are in any way special.
>

Loop detection in RFC 5321 is a normative MUST because of the obvious
operational problems it creates.  Maybe I'm being thick, but right now I
don't see how this is different, apart from the fact that each message is
distinct; you're still causing a problem by turning this on without a care
in the world about whether two verifiers start spamming each other.

-MSK

--000000000000de00af05b9e7e0c1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Jan 27, 2021 at 12:37 PM John Levine &lt;<a href=
=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:<br><div class=3D=
"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I still don=
&#39;t understand why failure reports about messages that<br>
happen to be failure reports are in any way special.<br></blockquote><div><=
br></div><div>Loop detection in RFC 5321 is a normative MUST because of the=
 obvious operational problems it creates.=C2=A0 Maybe I&#39;m being thick, =
but right now I don&#39;t see how this is different, apart from the fact th=
at each message is distinct; you&#39;re still causing a problem by turning =
this on without a care in the world about whether two verifiers start spamm=
ing each other.<br></div><div><br></div><div>-MSK<br></div></div></div>

--000000000000de00af05b9e7e0c1--


From nobody Wed Jan 27 19:08:46 2021
Return-Path: <johnl@taugh.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 678693A1189 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 19:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=gL+xcm0j; dkim=pass (2048-bit key) header.d=taugh.com header.b=D3OZdQk2
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 FYoMA1EGN2ZP for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 19:08:42 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 7D5463A1188 for <dmarc@ietf.org>; Wed, 27 Jan 2021 19:08:41 -0800 (PST)
Received: (qmail 37418 invoked from network); 28 Jan 2021 03:08:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=9228.60122ab8.k2101; bh=KJbhMnH3rvjA2TUh4ja+GVQ7P+FXIxVOLbIRu5Bp9pk=; b=gL+xcm0jy4EaYKT1OaRpZLXwb+e44FPpAax9n4S5DaHDIzLMTc9376PO5eyo6S+izYsJoL5+2u5/TbYhxgGKSBSYIxbkUHLZDa5F8Fv/cXuR3IHEA0GecIMzm1srXLJxjNamVoqgiNd2NsSjbA1CfzUnkmcyFtSPrXtYNN1U1aOxd2qOnrrGGzGVkNq8TX4bD66iIpKLZQMF1oOM0QV4iafU6852INhjIFeN2PobZiY7N7QYt330oN6l5d2zUq2l90UhIgjlTP4qynQO6e0mlxImW+pN5p840vk9ryzlxO/3wLAZdWH97iYPNJQIkQXAya/TKUPnkAuG41AsyUTtqg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=9228.60122ab8.k2101; bh=KJbhMnH3rvjA2TUh4ja+GVQ7P+FXIxVOLbIRu5Bp9pk=; b=D3OZdQk2AtRPfV/nywofr1D7IK2cDDCKYgm9AbllOHqMgiLS120TqmQVY/cMXe7kcQL+S/0c/+F4WQ+OY5uDqI5dni2J25dro4rYs3A42SRqVEwEyOeW5GMW6lA6z7tCjeQLrNmaEEY81/kmqLr/5rT1vWXg6z5XuqRbe8ENrRAecPANvMut88bpQzeoJhI5SREaZ2FJcVIBn5Hy3iWhXOftoy7CfUoEuBe1eSkDxsNIo67UR2usfb4HgL3mdgLN26xlzlM8MsCAgRmh+2lPIe58v0TpLQjFj2xRzG3pD/Zcy0Ha6WYgiyuYTPnMf9YH/6cnb7SXgYOHlR1n/US5Sg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 28 Jan 2021 03:08:40 -0000
Received: by ary.qy (Postfix, from userid 501) id DEE576CDE11E; Wed, 27 Jan 2021 22:08:39 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 4DF476CDE100; Wed, 27 Jan 2021 22:08:39 -0500 (EST)
Date: 27 Jan 2021 22:08:39 -0500
Message-ID: <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "IETF DMARC WG" <dmarc@ietf.org>
In-Reply-To: <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com>
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/EkM2xtWHjpS62uOTDZ7bYPoobic>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Thu, 28 Jan 2021 03:08:44 -0000

On Wed, 27 Jan 2021, Murray S. Kucherawy wrote:
>> I still don't understand why failure reports about messages that happen 
>> to be failure reports are in any way special.
>
> Loop detection in RFC 5321 is a normative MUST because of the obvious
> operational problems it creates.  Maybe I'm being thick, but right now I
> don't see how this is different, apart from the fact that each message is
> distinct; ...

Here's perhaps another way to look at it.

Imagine that I am a semi-competent mail server operator.  I hear that 
DMARC is great stuff and I set up DMARC software on my server including 
sending and processing reports.

Unfortunately, my l33t coding skillz aren't quite up to it, and my failure 
reports are all unaligned.  Also, I'm not very good at reading specs and 
my reports aren't in the right format either.  (Not making this up, I have 
lots of failure reports that are not multipart/report.)

Oh, no!  People are sending me failure reports about my failure reports! 
Make it stop!

Which of these should we do:

A) Everyone in the world who produces failure reports adds special cases 
to look for incoming failure reports, and heuristics to try and recognize 
failure reports in the wrong format, and when it finds one of them, it 
makes a note not to send a failure report about it.

B) Someone slaps me upside the head and I fix my SPF record so my reports 
are sent correctly.

This does not strike me as a hard problem.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Wed Jan 27 19:17:21 2021
Return-Path: <smj@crash.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 67DC73A10CF for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 19:17:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=crash.com
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 6-rO4PgAVsFM for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 19:17:19 -0800 (PST)
Received: from segv.crash.com (segv.crash.com [IPv6:2001:470:1:1e9::4415]) (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 EFC643A119B for <dmarc@ietf.org>; Wed, 27 Jan 2021 19:17:18 -0800 (PST)
Received: from shiny.crash.com (192-184-141-33.static.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.7) with ESMTPSA id 10S3H6Ax069709 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dmarc@ietf.org>; Thu, 28 Jan 2021 03:17:14 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 10S3H6Ax069709
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1611803836; bh=58KUvoVREoMAfcutyimwxMta+rktYloA+fw5cANlOLQ=; h=Subject:To:References:From:Date:In-Reply-To; b=DAeKbf1xHbV++UoFGUc2PtP3qHCkVqgHdr8C2UeWX6exuM/79VdQ2LHMEj7h136U3 RukkK4ZyyuMskWXqfpIHN2QDaxGixvnsu9VUgUChpwhlrq9DH78L+WNwkRVaCayc9y tHvOZ1nNHofjj5ALr5bDGDAIFuC16YqBrUuM5Qfu7HEppfgLE8HUhaKBWAjYai8seK ve5Po/vL2TKe8vslurD9a1pEH1da6KrWaMknXsBfCeXiuzIb/lKl2uhUGJvMvpPiCC SQLJG9f/pW4mTo1RYL2MeO+QsZaLo/NioKSTMqKDNhQrOg268oUhs5msUlRfefQKNH Efqgg6JQvU+cg==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.static.sonic.net [192.184.141.33] claimed to be shiny.crash.com
To: dmarc@ietf.org
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <b7ea6cb8-ce79-7df7-c521-544358c1866e@crash.com>
Date: Wed, 27 Jan 2021 19:17:06 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A536FB636D3C75D0D25CA65E"
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Thu, 28 Jan 2021 03:17:14 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QYmF2JTskPIurbPWRmBsIUJr6mE>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Thu, 28 Jan 2021 03:17:20 -0000

This is a multi-part message in MIME format.
--------------A536FB636D3C75D0D25CA65E
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 1/27/21 12:47, Murray S. Kucherawy wrote:
> On Wed, Jan 27, 2021 at 12:37 PM John Levine <johnl@taugh.com
> <mailto:johnl@taugh.com>> wrote:
>
>     I still don't understand why failure reports about messages that
>     happen to be failure reports are in any way special.
>
>
> Loop detection in RFC 5321 is a normative MUST because of the obvious
> operational problems it creates.  Maybe I'm being thick, but right now
> I don't see how this is different, apart from the fact that each
> message is distinct; you're still causing a problem by turning this on
> without a care in the world about whether two verifiers start spamming
> each other.


There's coverage in 7489 Section 7.2 that a domain owner can
inadvertently DDoS themselves via failure reports. And that still
surprised many implementers, even though it seemed obvious to them in
retrospect.

This case is even less obvious, and we still have questions coming in
about it from new implementers.

I don't think it's a security consideration because it doesn't scale up
the way "ruf" can, so it deserves a brief mention here. But I would
rephrase Ale's last sentence:


3.3.  Transport

   Email streams carrying DMARC failure reports MUST conform to the
   DMARC mechanism, thereby resulting in an aligned "pass".  Special
   care must be taken for authentication, as failure to authenticate
   failure reports may result in mail loops.  These loops can be mitigated
   by sending reports from a domain or subdomain that doesn't request
   reports, or by performing rate limiting for report receiving mailboxes.


--S.



--------------A536FB636D3C75D0D25CA65E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/27/21 12:47, Murray S. Kucherawy
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">On Wed, Jan 27, 2021 at 12:37 PM John Levine &lt;<a
          href="mailto:johnl@taugh.com" moz-do-not-send="true">johnl@taugh.com</a>&gt;
        wrote:<br>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">I still don't understand
            why failure reports about messages that<br>
            happen to be failure reports are in any way special.<br>
          </blockquote>
          <div><br>
          </div>
          <div>Loop detection in RFC 5321 is a normative MUST because of
            the obvious operational problems it creates.  Maybe I'm
            being thick, but right now I don't see how this is
            different, apart from the fact that each message is
            distinct; you're still causing a problem by turning this on
            without a care in the world about whether two verifiers
            start spamming each other.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>There's coverage in 7489 Section 7.2 that a domain owner can
      inadvertently DDoS themselves via failure reports. And that still
      surprised many implementers, even though it seemed obvious to them
      in retrospect.<br>
    </p>
    <p>This case is even less obvious, and we still have questions
      coming in about it from new implementers.</p>
    <p>I don't think it's a security consideration because it doesn't
      scale up the way "ruf" can, so it deserves a brief mention here.
      But I would rephrase Ale's last sentence:</p>
    <p><br>
    </p>
    <p>3.3.  Transport
      <br>
      <br>
         Email streams carrying DMARC failure reports MUST conform to
      the
      <br>
         DMARC mechanism, thereby resulting in an aligned "pass". 
      Special
      <br>
         care must be taken for authentication, as failure to
      authenticate
      <br>
         failure reports may result in mail loops.  These loops can be
      mitigated<br>
         by sending reports from a domain or subdomain that doesn't
      request<br>
         reports, or by performing rate limiting for report receiving
      mailboxes.
    </p>
    <p><br>
    </p>
    <p>--S.</p>
    <p><br>
    </p>
  </body>
</html>

--------------A536FB636D3C75D0D25CA65E--


From nobody Wed Jan 27 19:20:18 2021
Return-Path: <smj@crash.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 1AC983A1182 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 19:20:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=crash.com
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 QPCVVU0jFJnK for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 19:20:15 -0800 (PST)
Received: from segv.crash.com (segv.crash.com [IPv6:2001:470:1:1e9::4415]) (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 EB4463A117F for <dmarc@ietf.org>; Wed, 27 Jan 2021 19:20:15 -0800 (PST)
Received: from shiny.crash.com (192-184-141-33.static.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.7) with ESMTPSA id 10S3K7oL090566 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dmarc@ietf.org>; Thu, 28 Jan 2021 03:20:15 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 10S3K7oL090566
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1611804016; bh=MCHioXpxY+ovH8FMZKHT9+KvjLeXACKHrLI9UdllUjM=; h=Subject:To:References:From:Date:In-Reply-To; b=VBPy9x9ad5PFMzvlkczYU/tWaAhsXSkzXTqWLZB0BnLbsIG7JHViwI1dMxMfdd8r3 GxC6fgHRHLdFtVD3TEGXjVUfDUh4fuO6mahF4+iM+zbWc44uWbN3j+CkImdwANZBr8 oF57G9G4vkALXHHNTw7lizjGscZKSl+XFLwyJCqHzKb5m9qe+kVxDIQzSVRwd7a63b 41ReU7u3B1fdPF9YiNtMv1r0GD7qXcF6RofW5rHvX4H3ucHsbXJKkkNBkPa/JgBOlL LFR2fJwjOwoIWfK004CdyJAuGqSV2E3J2YiWnRYAiUoMkjo69k/mv5O1i3eIW0+03a G9YNwK42JTTKw==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.static.sonic.net [192.184.141.33] claimed to be shiny.crash.com
To: dmarc@ietf.org
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <183c0bc7-48e1-52c1-2a19-cd74fe8e4521@crash.com>
Date: Wed, 27 Jan 2021 19:20:07 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Thu, 28 Jan 2021 03:20:15 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Z-QgppNXDZ375lXGII8w1itBeDs>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Thu, 28 Jan 2021 03:20:17 -0000

On 1/27/21 19:08, John R Levine wrote:
> On Wed, 27 Jan 2021, Murray S. Kucherawy wrote:
>>> I still don't understand why failure reports about messages that
>>> happen to be failure reports are in any way special.
>>
>> Loop detection in RFC 5321 is a normative MUST because of the obvious
>> operational problems it creates.  Maybe I'm being thick, but right now I
>> don't see how this is different, apart from the fact that each
>> message is
>> distinct; ...
>
> Here's perhaps another way to look at it.
>
> ...
>
> B) Someone slaps me upside the head and I fix my SPF record so my
> reports are sent correctly.
>
> This does not strike me as a hard problem.


It's not a hard problem. I see the last sentence in Section 3.3 as
reserving the right to deliver that slap...

--S.



From nobody Wed Jan 27 19:57:21 2021
Return-Path: <dougfoster.emailstandards@gmail.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 A5BBF3A1157 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 19:57:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TVLr9OV5rq-8 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 19:57:18 -0800 (PST)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCA493A11F1 for <dmarc@ietf.org>; Wed, 27 Jan 2021 19:57:17 -0800 (PST)
Received: by mail-vs1-xe2b.google.com with SMTP id h11so2318389vsa.10 for <dmarc@ietf.org>; Wed, 27 Jan 2021 19:57:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9s/6S9YcY4LKYu25Vk98LM5pLp2ycc035nCvMoV3cdg=; b=Oif23qcB9BYlG0R1Ld/i4tdS4FjCAeOvpAnDm8ktVsqiUliOkoO0oiKMiKezntWKKE +76uhsTgM2yCOsgbE58OH5ZU+67X9P26oxoR4UFjn8G2pMVK/CF5xsRFVzj+blotd6Ec ZNxfc0yvqOna4XpGyBrVh3cjv2tV8GMBbh3AMh6BjQ2M+ZkO77LzmvJPmA8GlZluelC0 LmNsOKySyXReCPMG5K2i7R0hhvpoLxJKfdbPP9TVRd8rox2HmfRlNmzT4H0EYpYHwKbN Z/FkP7b5kjcphYqo4y9mlV4CLoezXJVM2+p1vCusIgBYjWHGnPWhZAAggXXautv14GVh AglA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9s/6S9YcY4LKYu25Vk98LM5pLp2ycc035nCvMoV3cdg=; b=NPgH0X+YW/N4aj4dTlShDzGnDRkCkR6DPg6ByMsXdeOUJdZ1IEOPuGO9Hto5oanxoK 12Eca9lwcbHBx9E0dQQPX3pk2C0pgIdWqa3yxIDnylHi3z8KBr2P7Vaohs76+Oh1nWkR CshP5KjkFEszBaq6I6tBsoCOBKxMutQKpCqCOkzJrEd/BpfxQAXNivJWcJlVZ2ru+l5M y5dNqC+skmgKR1KjK3AEQPf1MRAhu4mv2hYgtYwa8qALS3Bmhhfs6QPGAL3cQTTn9cCe dx03ZuEwP/zEj/NTbEMzp339y40Y22RNj1ocbb2Offel6/IBWBINgff0nn3WcQqbAzPo +n1Q==
X-Gm-Message-State: AOAM533yaRc/uMuFQ6xfQ+NKABZggMhCEzimUC6chZud1mB8mSx0dV1r p8b+Ku9zVJCKylCUB/9w79DqgGqpjVJXkbIjCXkg/27G
X-Google-Smtp-Source: ABdhPJxtohfA5Yp9YrqArJ+XSt2y4eXko2Fcy+T4DvtVK6vE4+FeVOrgMPjo2YARI+wxR6n/tYiNlJsB1+4WRo2iFqg=
X-Received: by 2002:a67:24c5:: with SMTP id k188mr10316748vsk.16.1611806236824;  Wed, 27 Jan 2021 19:57:16 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com> <183c0bc7-48e1-52c1-2a19-cd74fe8e4521@crash.com>
In-Reply-To: <183c0bc7-48e1-52c1-2a19-cd74fe8e4521@crash.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 27 Jan 2021 22:57:03 -0500
Message-ID: <CAH48Zfy+WcoXCbHZpmGqYy8pUg2dveHY7cd96j5t1DB2rXLKEw@mail.gmail.com>
To: Steven M Jones <smj@crash.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000031590d05b9ede200"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/MzUQVACoXvXoQ0ypI1b5TWOKdl8>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Thu, 28 Jan 2021 03:57:20 -0000

--00000000000031590d05b9ede200
Content-Type: text/plain; charset="UTF-8"

Loops require two parties.  Any one party can protect both parties by
choosing to not perpetuate the loop.

Saying that "the other guy" should be smarter seems wishful thinking.  Of
course some other people will act stupidly.  Fixing that problem is not in
my scope.   Having their mistakes interfere with my system's normal
operation is not an option that I am willing to permit.

DF

On Wed, Jan 27, 2021, 10:20 PM Steven M Jones <smj@crash.com> wrote:

> On 1/27/21 19:08, John R Levine wrote:
> > On Wed, 27 Jan 2021, Murray S. Kucherawy wrote:
> >>> I still don't understand why failure reports about messages that
> >>> happen to be failure reports are in any way special.
> >>
> >> Loop detection in RFC 5321 is a normative MUST because of the obvious
> >> operational problems it creates.  Maybe I'm being thick, but right now I
> >> don't see how this is different, apart from the fact that each
> >> message is
> >> distinct; ...
> >
> > Here's perhaps another way to look at it.
> >
> > ...
> >
> > B) Someone slaps me upside the head and I fix my SPF record so my
> > reports are sent correctly.
> >
> > This does not strike me as a hard problem.
>
>
> It's not a hard problem. I see the last sentence in Section 3.3 as
> reserving the right to deliver that slap...
>
> --S.
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--00000000000031590d05b9ede200
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Loops require two parties.=C2=A0 Any one party can protec=
t both parties by choosing to not perpetuate the loop.<div dir=3D"auto"><di=
v dir=3D"auto"><div dir=3D"auto"><br></div><div dir=3D"auto">Saying that &q=
uot;the other guy&quot; should be smarter seems wishful thinking.=C2=A0 Of =
course some other people will act stupidly.=C2=A0 Fixing that problem is no=
t in my scope.=C2=A0 =C2=A0Having their mistakes interfere with my system&#=
39;s normal operation is not an option that I am willing to permit.</div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto">DF</div></div></div></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan=
 27, 2021, 10:20 PM Steven M Jones &lt;<a href=3D"mailto:smj@crash.com">smj=
@crash.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 1/27/=
21 19:08, John R Levine wrote:<br>
&gt; On Wed, 27 Jan 2021, Murray S. Kucherawy wrote:<br>
&gt;&gt;&gt; I still don&#39;t understand why failure reports about message=
s that<br>
&gt;&gt;&gt; happen to be failure reports are in any way special.<br>
&gt;&gt;<br>
&gt;&gt; Loop detection in RFC 5321 is a normative MUST because of the obvi=
ous<br>
&gt;&gt; operational problems it creates.=C2=A0 Maybe I&#39;m being thick, =
but right now I<br>
&gt;&gt; don&#39;t see how this is different, apart from the fact that each=
<br>
&gt;&gt; message is<br>
&gt;&gt; distinct; ...<br>
&gt;<br>
&gt; Here&#39;s perhaps another way to look at it.<br>
&gt;<br>
&gt; ...<br>
&gt;<br>
&gt; B) Someone slaps me upside the head and I fix my SPF record so my<br>
&gt; reports are sent correctly.<br>
&gt;<br>
&gt; This does not strike me as a hard problem.<br>
<br>
<br>
It&#39;s not a hard problem. I see the last sentence in Section 3.3 as<br>
reserving the right to deliver that slap...<br>
<br>
--S.<br>
<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank" rel=3D"noreferrer">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div>

--00000000000031590d05b9ede200--


From nobody Thu Jan 28 04:13:08 2021
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 520393A0FB9 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 04:13:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 oyH9NDymRkWE for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 04:13:05 -0800 (PST)
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 C77AA3A0FCA for <dmarc@ietf.org>; Thu, 28 Jan 2021 04:13:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611835981; bh=tUFfuh0IWwqJfbVOeQ7shNmTweskAEZY2CYhxTRc4qk=; l=2434; h=To:References:From:Date:In-Reply-To; b=AsH35zqQghC4xOfwVEFBlA1+vkPzaDkRPI0NdAW9oDy+Md5B3RCPCfm2zScuw70Cy Lp59PwOZAPzT3r9TNV/5PsSvvwcnA+9/zRW71k7IZVV6yDT9cl8FKhPKkwbDNl2778 L5P0gUqOwXqMfTwRSpaDvXuqGFTBR536Xqkg3wBJbqCQwOOT4R7xjL2SmIQq/
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.000000006012AA4D.00007F8B; Thu, 28 Jan 2021 13:13:01 +0100
To: dmarc@ietf.org
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <11050391.cvU1rW7NdO@zini-1880>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <0f95fd70-bb40-5713-2731-530c75835632@tana.it>
Date: Thu, 28 Jan 2021 13:13:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <11050391.cvU1rW7NdO@zini-1880>
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/dFAGAXCE7ths6jcL-1NRehI9AcE>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Thu, 28 Jan 2021 12:13:06 -0000

On Wed 27/Jan/2021 20:24:05 +0100 Scott Kitterman wrote:
> On Wednesday, January 27, 2021 12:25:59 PM EST Alessandro Vesely wrote:
>> 
>> Can we fix this aberration?
>> 
>> The spec needs a fix anyway, because from the text I quoted above I
>> understood that the example message passes DMARC.  Am I the only one?
>> 
>> In addition, as I said, SPF filters are likely to report HELO as helo and
>> MAIL FROM as mailfrom.  If we want to carry over this quirk, the spec must
>> say that a DMARC filter which gathers SPF authentication status from an
>> upstream filter MUST make sure that mailfrom is empty before validating
>> based on an aligned helo.
>> 
>> Dropping that absurd discrimination between SPF identifiers would make for a
>> smoother spec.  Since non-null mailfroms are in most cases aligned with
>> either From: or helo, the differences between existing compliant
>> implementations and the smoother spec would be limited to a hardly
>> noticeable set of test messages.
> 
> Your absurd is my eminently reasonable.
> 
> I can't explain why it was added, but it makes sense, IMO, to have it there to
> aid in reconstructing the exact situation for trouble shooting purposes.


Can you expand on how ignoring helo aids trouble shooting?


> DMARC has always (for the SPF related portion) been about alignment of mail
> from and from.  I don't think adding HELO has appreciable value and is
> certainly not worth the added complexity to implement DMARC to include.


 From an implementer POV, the complication stays in the idiosyncratic 
identifier processing.  I wonder how many do follow it strictly.  IMHO, a 
reasonable DMARC spec should either smooth out the discrimination or provide a 
clear explanation of why such peculiar processing is needed and what would 
happen if all identifiers were treated equal.


> There are lots of ways that DMARC could have addressed SPF.  Personally I
> thought it might make sense to skip using the mail from SPF result and just
> check if the from address would pass if it were subjected to an SPF check, but
> that's not the existing design.  I don't think it should be changed now.


Yeah, after you insisted, I vaguely recollected about an SPF argument that I 
had erased from memory.  I can't recall its merit.

DKIM'S d= are domains, and DKIM scope is exactly to identify a domain.  That's 
more akin to helo than mail from.


Best
Ale
-- 


























From nobody Thu Jan 28 04:13:17 2021
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 D5C333A10B4 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 04:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 csRTA2f7Znxa for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 04:13:07 -0800 (PST)
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 8D6DB3A0FB9 for <dmarc@ietf.org>; Thu, 28 Jan 2021 04:13:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611835987; bh=/i1HwjDAbQDwVomnuuWf1xwNJwhVl8akMnHkJ2l9u7E=; l=2075; h=To:References:From:Date:In-Reply-To; b=AfHLX6H0hqc5NnZSmVkvIA41rI3VC4pfviQJA8RRgcfO01ZjPVQt2nLhahVt+J225 43GX96XIpVxqXaygjFHwjyvSIKNOJbg0avJVmC+IMiHqjrrvuw/gC4SVKY1xarGaPG SXs98dtd7t/P+AoZn0KnHzAW1164sk/rZpNg7g1YZkKecWivnuLjolTxuCaYz
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0D3.000000006012AA52.00007F9F; Thu, 28 Jan 2021 13:13:06 +0100
To: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it>
Date: Thu, 28 Jan 2021 13:13:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@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/h4uMCHvOo0K9IydOFH7nMWS6yaU>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Thu, 28 Jan 2021 12:13:16 -0000

On Wed 27/Jan/2021 21:10:37 +0100 Murray S. Kucherawy wrote:
> On Wed, Jan 27, 2021 at 9:26 AM Alessandro Vesely <vesely@tana.it> wrote:
> 
>> AFAIUI, there's no reason why SPF would work with a logic substantially
>> different than DKIM's.  DKIM can provide n identifiers, if one of them is
>> aligned and "pass", then DMARC is "pass".  SPF can provide 2 identifiers
>> but one of them is of class B.  WTF?
> 
> DKIM (in its simplest form) returns N tuples of the form (d= domain,
> pass/fail).  All of them were run through exactly the same check; all of
> them were attached to the message in exactly the same way; all of them have
> essentially identical semantics.  Giving them equal footing makes sense to
> me.
> 
> The two identifiers in SPF hold different places in the SMTP session, and
> have different semantics.  I think treating them differently is also just
> fine.


It is relevant that both identifier come from /the same/ SMTP session.  That's 
not true for many DKIM signatures.


>> In addition, as I said, SPF filters are likely to report HELO as helo and 
>> MAIL FROM as mailfrom.  If we want to carry over this quirk, the spec must
>> say that a DMARC filter which gathers SPF authentication status from an
>> upstream filter MUST make sure that mailfrom is empty before validating
>> based on an aligned helo. >
> ...or it doesn't evaluate against SPF at all in such a situation.


Dropping SPF altogether is too much.  I'm querying about dropping just the 
idiosyncrasy...


>> Dropping that absurd discrimination between SPF identifiers would make
>> for a smoother spec.  Since non-null mailfroms are in most cases aligned
>> with either From: or helo, the differences between existing compliant
>> implementations and the smoother spec would be limited to a hardly
>> noticeable set of test messages. >
> I don't think we should ignore what those two identifiers mean, how likely
> they are to contain junk, how they are applied, outside of DMARC, etc.


How is that different from d= identifiers?


Best
Ale
-- 






















From nobody Thu Jan 28 04:24:20 2021
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 701D13A10A9 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 04:24:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 i2OKKVAST0cX for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 04:24:17 -0800 (PST)
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 F379B3A109C for <dmarc@ietf.org>; Thu, 28 Jan 2021 04:24:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611836654; bh=urD5LxM0w5ERqL0SeZwSnzXM6ctWg5Whd6P8xstPn9M=; l=908; h=To:References:From:Date:In-Reply-To; b=B8ROO5jzqJox2Z4KqkIQlG76iVTvqKmqPDSHVQX3eVvq7XtXJn16DSjvDuZssWfdr xcq6p+xNb2yrGA8DOAIuUUUydiRkpAxpQhQcazjX4dYQ3QEb57vnfSGL1/Wlh1CvD0 Ls8T1kPFtfa5aiJ95H+bJoMzwSn3aEfT/66fOnD01obamwvPhxymGG3dXSEKL
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC09F.000000006012ACEE.000001F3; Thu, 28 Jan 2021 13:24:14 +0100
To: Michael Thomas <mike@mtcc.com>, "Murray S. Kucherawy" <superuser@gmail.com>, "dmarc@ietf.org" <dmarc@ietf.org>
References: <2aaebb6b-6518-19cd-d32d-8370c0adb6d6@mtcc.com> <CAL0qLwbJcUCR6DykMQVe5d6rvdgiF=+cA+r65thx-Bub3qPZ7w@mail.gmail.com> <204a52fc-92ef-bc3c-2870-12e14911ae11@mtcc.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <07ab4ba5-d06e-576e-405f-d80121847788@tana.it>
Date: Thu, 28 Jan 2021 13:24:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <204a52fc-92ef-bc3c-2870-12e14911ae11@mtcc.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/o5IjmyBHqGKEoUMdL8Fsv0VQrEI>
Subject: Re: [dmarc-ietf] understanding section 7.2
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: Thu, 28 Jan 2021 12:24:18 -0000

On Wed 27/Jan/2021 21:18:50 +0100 Michael Thomas wrote:
> On 1/27/21 12:14 PM, Murray S. Kucherawy wrote:
>> The schema's already pretty large, and probably has to be, but maybe a 
>> trivial example report would be reasonable to craft and include?
> 
> Yeah, that might do too.


+1.  It can be produced starting from a real report and replacing IPs and 
domain names with exemplifying ones.


> I think it's important that it be in section 7.2 though because you should
> be able to read that section and understand what the report is and isn't.

The full report should go in an appendix, because it is too long to make sense 
in the middle of text.  Section 7.2 may show the corresponding tabular form[*], 
which provides for a visual summary of fields, and reference the appendix.


Best
Ale
-- 

[*] A tabular form is showed here:
https://en.wikipedia.org/wiki/DMARC#Aggregate_reports





















From nobody Thu Jan 28 04:41:59 2021
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 0E2053A1206 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 04:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 pTxhPsARn6id for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 04:41:57 -0800 (PST)
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 8ED4F3A11F6 for <dmarc@ietf.org>; Thu, 28 Jan 2021 04:41:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611837715; bh=mwKTIHy1NrJAQY9YOCIhxZ5++2hSzoFzlyPQ+NHXfkY=; l=2221; h=To:References:From:Date:In-Reply-To; b=A6Buh6JvYVGFB1g2VulcVSc2LH4NWv9jZ2KOLedl/mfjGAdCO5asTOvCFZyuWffkj HPvvHZaIjT3MH9mqku6JlEbep3SgEnZ5VnH6C2hLQQ4/CVmEzn3njMgpDFewQIpp9q uzPZnkqkDuR5pbmVztKIe099vD8DXf/HfUQC9V71dnyGgn87cenTcVeQWUFAP
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC0D1.000000006012B113.00000497; Thu, 28 Jan 2021 13:41:55 +0100
To: dmarc@ietf.org
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <b7ea6cb8-ce79-7df7-c521-544358c1866e@crash.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <db72db79-272e-5d52-8994-4da81c8723bd@tana.it>
Date: Thu, 28 Jan 2021 13:41:55 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <b7ea6cb8-ce79-7df7-c521-544358c1866e@crash.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/7oqtfyI-vA8Z5By0bk9rzR9OtQ0>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Thu, 28 Jan 2021 12:41:59 -0000

On Thu 28/Jan/2021 04:17:06 +0100 Steven M Jones wrote:
> On 1/27/21 12:47, Murray S. Kucherawy wrote:
>> On Wed, Jan 27, 2021 at 12:37 PM John Levine wrote:
>>
>>> I still don't understand why failure reports about messages that happen
>>> to be failure reports are in any way special. >>
>> Loop detection in RFC 5321 is a normative MUST because of the obvious 
>> operational problems it creates.  Maybe I'm being thick, but right now I
>> don't see how this is different, apart from the fact that each message is
>> distinct; you're still causing a problem by turning this on without a care
>> in the world about whether two verifiers start spamming each other. >
> There's coverage in 7489 Section 7.2 that a domain owner can inadvertently
> DDoS themselves via failure reports. And that still surprised many
> implementers, even though it seemed obvious to them in retrospect. >
> This case is even less obvious, and we still have questions coming in about
> it from new implementers. >
> I don't think it's a security consideration because it doesn't scale up
> the way "ruf" can, so it deserves a brief mention here. But I would
> rephrase Ale's last sentence:
> 
> 
> 3.3.  Transport
> 
>     Email streams carrying DMARC failure reports MUST conform to the
>     DMARC mechanism, thereby resulting in an aligned "pass".  Special
>     care must be taken for authentication, as failure to authenticate
>     failure reports may result in mail loops.  These loops can be mitigated
>     by sending reports from a domain or subdomain that doesn't request
>     reports, or by performing rate limiting for report receiving mailboxes.


I rephrased it further:

3.3.  Transport

    Email streams carrying DMARC failure reports MUST conform to the
    DMARC mechanism, thereby resulting in an aligned "pass".  Special
    care must be taken of authentication, as failure to authenticate
    failure reports may result in mail loops.  These loops can be
    mitigated by sending reports from a domain or subdomain that doesn't
    request reports, or by performing rate limiting especially for
    failures related to messages received at addresses published in a
    ruf= tag.


Best
Ale
-- 






















From nobody Thu Jan 28 12:41:05 2021
Return-Path: <superuser@gmail.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 7BB643A1729 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 12:41:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6NO2H8fqrQYZ for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 12:41:02 -0800 (PST)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 146413A1724 for <dmarc@ietf.org>; Thu, 28 Jan 2021 12:41:01 -0800 (PST)
Received: by mail-vs1-xe2a.google.com with SMTP id e15so3749438vsa.0 for <dmarc@ietf.org>; Thu, 28 Jan 2021 12:41:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bV+QmGCRuSzOHlZ/EGFMGCWukKj7S2O5pKycYI8mMV8=; b=s8AWQEF74pHhIApkIvxt77txB5SmrQkf228u1tT+NO1kUjyACAYjH7MHmacfmntGnQ TwV/EcsbaB/urOma0e1ezrCWr06pupkqnRDq1ygN9jhQVnSdHPzoQlHmEWcX/Z6dGeRB HI0Lb6c3NN4EHf1iNSx4pNj47E6vo1dITdSc/1lINmZqdvYX1ql37cLD5AM0pD1UCrNA gMasDtzSH3iJ4sBmulXnX+MHbDo8vcIXv0/ouicLQI/LjF7bveWGcWMqixNnqsKC9C6A oXrOK4ANXGPYQwSFeC2zdNBKPMEbGN9RXmQl9fFXBNz4KJuEgpENjT22WvKegFUmv313 3q/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bV+QmGCRuSzOHlZ/EGFMGCWukKj7S2O5pKycYI8mMV8=; b=PeOCKWPBpc7tTbNIX0J7JJVKfGoKkmqyVAvuBUdp3AHNgRE7OsWe1qSFbKQZqb/qeV kYUx3z9E1sSS3XNxSwK+E+qiBkOglHKeEuj2I2E9fJCJ22aR+05ezewfoq+kjibli2kc 3MVQBHeTPU80825L5gdFK0ajtiCdhs+BBoEnEd2EyAWieUh1rM62jWmIIqGg6jJ8cxHC FoGf49+OFs8zpjMsrRe9HlCB3xhLfOM1DU6BrMln1qQqrNe4+b9Rh+mYoLGG+LXGycCG iBcOn7ywvhhqBZF1fVtOrFzWWBTdGeQnka/ADoVo1MSqD8/ILxw436awMXWLTj+BeQfW ZeRA==
X-Gm-Message-State: AOAM532K/9s+rkImoqxTXvW+aYtBtRaCs9f9644vTZi4QsFdGuh3jKXc +PUp5d3jlcmBfHdyKe3gfMnicIBuD4tKEBGRxIqmRX7UUTU=
X-Google-Smtp-Source: ABdhPJx5HF6iaCuYxtwF/yNcSF+WuNgTV5CGmqEonwIHD0zXrNI96WTvmkbH+AKhWxCVO2ZdjY31t6O2PlRaAKkes5k=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr1274599vsy.54.1611866460822;  Thu, 28 Jan 2021 12:41:00 -0800 (PST)
MIME-Version: 1.0
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com> <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it>
In-Reply-To: <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 28 Jan 2021 12:40:49 -0800
Message-ID: <CAL0qLwbYxTXXXpx11L3f1CqBns=fSRho3C+S7q=-DmiPSvxKvg@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d2a2c005b9fbe7bd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VfqMsg3bHckQ7a0WSwPK-G-L_Dc>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Thu, 28 Jan 2021 20:41:04 -0000

--000000000000d2a2c005b9fbe7bd
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 28, 2021 at 4:13 AM Alessandro Vesely <vesely@tana.it> wrote:

> > DKIM (in its simplest form) returns N tuples of the form (d= domain,
> > pass/fail).  All of them were run through exactly the same check; all of
> > them were attached to the message in exactly the same way; all of them
> have
> > essentially identical semantics.  Giving them equal footing makes sense
> to
> > me.
> >
> > The two identifiers in SPF hold different places in the SMTP session, and
> > have different semantics.  I think treating them differently is also just
> > fine.
>
> It is relevant that both identifier come from /the same/ SMTP session.
> That's
> not true for many DKIM signatures.
>

I guess if report consumers really want this information, we can include
it.  I just don't see the value in the HELO parameter if it's effectively
random junk in the session.  At least a passing DKIM signature is
associated with a domain that existed at some point in time and whose DNS
contained apparently-valid public keys.  I can mostly type anything I want
to HELO or EHLO.

-MSK

--000000000000d2a2c005b9fbe7bd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 28, 2021 at 4:13 AM Alessandr=
o Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote=
:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">&gt; DKIM (in its simplest form) returns N tuples of the form =
(d=3D domain,<br>
&gt; pass/fail).=C2=A0 All of them were run through exactly the same check;=
 all of<br>
&gt; them were attached to the message in exactly the same way; all of them=
 have<br>
&gt; essentially identical semantics.=C2=A0 Giving them equal footing makes=
 sense to<br>
&gt; me.<br>
&gt; <br>
&gt; The two identifiers in SPF hold different places in the SMTP session, =
and<br>
&gt; have different semantics.=C2=A0 I think treating them differently is a=
lso just<br>
&gt; fine.<br>
<br>
It is relevant that both identifier come from /the same/ SMTP session.=C2=
=A0 That&#39;s <br>
not true for many DKIM signatures.<br></blockquote><div><br></div><div>I gu=
ess if report consumers really want this information, we can include it.=C2=
=A0 I just don&#39;t see the value in the HELO parameter if it&#39;s effect=
ively random junk in the session.=C2=A0 At least a passing DKIM signature i=
s associated with a domain that existed at some point in time and whose DNS=
 contained apparently-valid public keys.=C2=A0 I can mostly type anything I=
 want to HELO or EHLO.</div><div><br></div><div>-MSK<br></div></div></div>

--000000000000d2a2c005b9fbe7bd--


From nobody Thu Jan 28 12:59:52 2021
Return-Path: <superuser@gmail.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 533A03A1755 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 12:59:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Ew8xbVjBWFKx for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 12:59:49 -0800 (PST)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E33393A1751 for <dmarc@ietf.org>; Thu, 28 Jan 2021 12:59:48 -0800 (PST)
Received: by mail-vs1-xe2c.google.com with SMTP id s83so1408596vsc.4 for <dmarc@ietf.org>; Thu, 28 Jan 2021 12:59:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pHKavKndYEaa0zwj/n+dganQT06P1kIFQHPpFiBGZuo=; b=bdfkBd7iY/qcqeszwrMYt+WAppVvOEBVwSFIBMGElRX2DKTGMC6lSzimcfGFrlFQOc Fw+TYO1tevTJonIwFuSydFvxJuhVAcCt+d5j50t8isL8z3+Vn02mgVLbzTZK5ESvOVSW K5ccIU/Qg4tGccsEIOaJlt3VHBoIf1Yxshg9JWbU1EXS/cam2oaYqcgX2RNGlyQeisq/ ZE/lKLqveet6bjAcqq21VI88KIZvsABeJzWMGhrjDteC34ZI+FYcNogPnAIqEvX/RdhF 5vnuMcUfRIFscT/DQC0mubUXq5+w2nvw5tPdn84mIyVrVtnlICU+6ZZQrmOzLnXcNLCi FaRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pHKavKndYEaa0zwj/n+dganQT06P1kIFQHPpFiBGZuo=; b=d6Rn9Qv2OOp96lTcrOdeMEy3WVCMc4W194VNCzU3+ZDFBYbVxijjCcYYvqeNmrEgvq /Bt9oVSYTGxoVuyfVzbA/kEchGDh0OB/5d7QkHmWbNMzbNB8zxiyZXCW7wPkqCIfSVrs JeUKhSjX3lQ+a0oaAsjCdbi7uQ5s4mq6rXQSAEVPgy9HNsQbPIvu89NoR8tKKMn7sxBW 3d68ZkZFwYDiENAYjzedInnMLA8f92QGlEoKu8YqEFCYdyjzoOD6a607s8E/JvKR775w 5qHxORUODNM9HigxZziUL1+V/nPspb9iRtryLBeC88Z6h8GVyxtEg3UwkRTZYRflV5hi QWaA==
X-Gm-Message-State: AOAM532Rw9pJqb2BIgffNYwT2dablek6R+7x1892ADxBdx6Otfp3yv0O kFIQwKRRgr5KAuUXUvevhMH2zdfvHX2UXO8LhTn439oP86o=
X-Google-Smtp-Source: ABdhPJyNdYOWLMUTudR/Nw9gZtM0RN1oyAiK6HXvdjdVXKJbihQ8SXvJuHu2YPNmS1umJGTEEa3+oPr17zFDI61c04M=
X-Received: by 2002:a67:18c6:: with SMTP id 189mr1310287vsy.54.1611867587710;  Thu, 28 Jan 2021 12:59:47 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com>
In-Reply-To: <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 28 Jan 2021 12:59:36 -0800
Message-ID: <CAL0qLwb3Z6DbVCvhSF=G6dxjoYwjLvwzbG0OOAUbD=F8H6+wyg@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fd92f505b9fc2ac0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/CN43LDpqiLM9ZqbHVafrkjjWh6g>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Thu, 28 Jan 2021 20:59:50 -0000

--000000000000fd92f505b9fc2ac0
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 27, 2021 at 7:08 PM John R Levine <johnl@taugh.com> wrote:

> Which of these should we do:
>
> A) Everyone in the world who produces failure reports adds special cases
> to look for incoming failure reports, and heuristics to try and recognize
> failure reports in the wrong format, and when it finds one of them, it
> makes a note not to send a failure report about it.
>
> B) Someone slaps me upside the head and I fix my SPF record so my reports
> are sent correctly.
>

I'm suggesting:

C) Stipulate somehow that generated reports should not contain data about
received reports.  (If you do that, then you likely obviate the need to
generate a new report back to that operator in the first place.)

This to me is almost exactly the same thing as saying "Don't generate a
bounce about a bounce", which has been part of SMTP for decades (it's a
SHOULD NOT in 2821).  I don't understand why you're saying it's appropriate
in one but a non-issue in the other.

-MSK

--000000000000fd92f505b9fc2ac0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote">On Wed, Jan 27, 2021 at 7:08 PM=
 John R Levine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&g=
t; wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Which of the=
se should we do:<br>
<br>
A) Everyone in the world who produces failure reports adds special cases <b=
r>
to look for incoming failure reports, and heuristics to try and recognize <=
br>
failure reports in the wrong format, and when it finds one of them, it <br>
makes a note not to send a failure report about it.<br>
<br>
B) Someone slaps me upside the head and I fix my SPF record so my reports <=
br>
are sent correctly.<br></blockquote><div><br></div><div>I&#39;m suggesting:=
<br><br></div><div>C) Stipulate somehow that generated reports should not c=
ontain data about received reports.=C2=A0 (If you do that, then you likely =
obviate the need to generate a new report back to that operator in the firs=
t place.)<br></div><div><br></div><div>This to me is almost exactly the sam=
e thing as saying &quot;Don&#39;t generate a bounce about a bounce&quot;, w=
hich has been part of SMTP for decades (it&#39;s a SHOULD NOT in 2821).=C2=
=A0 I don&#39;t understand why you&#39;re saying it&#39;s appropriate in on=
e but a non-issue in the other.<br></div><div><br></div><div>-MSK<br></div>=
</div></div>

--000000000000fd92f505b9fc2ac0--


From nobody Thu Jan 28 13:42:14 2021
Return-Path: <johnl@taugh.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 2647A3A096C for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 13:42:14 -0800 (PST)
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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=M6+cJnMh; dkim=pass (2048-bit key) header.d=taugh.com header.b=ruDT3pl0
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 DNFmc31sQDkf for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 13:42:12 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 45D233A0C01 for <dmarc@ietf.org>; Thu, 28 Jan 2021 13:42:11 -0800 (PST)
Received: (qmail 94523 invoked from network); 28 Jan 2021 21:42:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=17138.60132fb2.k2101; bh=dwx7B4si8muTcw2EjNAASgCljQA/AcMj0g+maFXFXlE=; b=M6+cJnMh/gDAza4It+eeMlzMnbYozjp0rO1GSsWTpRhWj/5xtswxJYP8Z3IEyMtZck/iIhA2137NCfF59ZCeTRKpd4kUOgWK9QVmkw6TSjHvnIl8ezpKqJQM+I4SD54b1prrEPKhyTtMW8YCyrlml0eaPQX5mNZV2UCzfkxboVlzf7aZSATbqiABjtyWFecMVBKql0tDOBoEh9LMlrWMaR0G+ksBSjmHGKPQTn3oVPCVK553B7DJe2n+CYAk161nf9PVtg9FKz7HQlyXLBd9zySf4GDO7w+dIp+oRdINNRnG2Y0aGPdCCJ2K+F15tfxeMROpIUSZLn+crXPUpEzeJA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=17138.60132fb2.k2101; bh=dwx7B4si8muTcw2EjNAASgCljQA/AcMj0g+maFXFXlE=; b=ruDT3pl0EIluETrujXhr3BpZ0GZF7VYvSMf/3c9vgFpMyd4jGAzTxX/xDOZel8MFVShZv4/lsh4OMWyoaHfTQ46A/wKlP2NIXQE0xZDbJguvSmxM5PoQrA5fHQcGfe5kS9E3pgj2VgbKzgU87rOujVgidmUzpGjKFPe7eWA6VghMHH+NSiwwN4pWKPJBTzBWDGDARqpXFNUuSLDzoGbXNdPg4pkABEvuHGfVU0vdeXzbXeWEDkpMlOB6i2+LTsGGf8hb1TA6MGjo6BYT9bj9y4qpVRUu8Hmw3TVCQb//umC/l8DrAXDFGSKTOsB4B3KZnXnP3w1UbW1iiH7qqdzQvg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 28 Jan 2021 21:42:10 -0000
Received: by ary.qy (Postfix, from userid 501) id C79FA6CE660F; Thu, 28 Jan 2021 16:42:09 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 9148E6CE65F1; Thu, 28 Jan 2021 16:42:09 -0500 (EST)
Date: 28 Jan 2021 16:42:09 -0500
Message-ID: <661b7adf-fcf3-1ada-4b84-cb4ee23a48a@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "IETF DMARC WG" <dmarc@ietf.org>
In-Reply-To: <CAL0qLwb3Z6DbVCvhSF=G6dxjoYwjLvwzbG0OOAUbD=F8H6+wyg@mail.gmail.com>
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com> <CAL0qLwb3Z6DbVCvhSF=G6dxjoYwjLvwzbG0OOAUbD=F8H6+wyg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/RaTxq0xLmqKP2qiHLdWFkw811-Q>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Thu, 28 Jan 2021 21:42:14 -0000

> C) Stipulate somehow that generated reports should not contain data about
> received reports.  (If you do that, then you likely obviate the need to
> generate a new report back to that operator in the first place.)

I can't even tell what might be a failure report without deep parsing and 
heuristics.  And, of course, I am not inclined to add extra code to 
program around other people's bugs.


> This to me is almost exactly the same thing as saying "Don't generate a
> bounce about a bounce",

Because these are not bounces.  They are not even a little bit like 
bounces.  Bounces are about invalid recipient addresses, but these have no 
relation to anything about the recipient address.

They are fresh new messages sent from a system that presumably cares 
enough about DMARC to send reports about it, and presumably wants to send 
all of its mail with DMARC alignment.  If they are unaligned, that is 
because the sending system is broken, and if that systems publishes an 
ruf= tag, it is specifically asking to be inforned about exactly that 
breakage.

Maybe I'm dim, but I am having no success understanding the apparent 
interpretion of ruf as "tell me about the unaligned messages I'm sending, 
except for some that should be really easy for me to fix."

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Thu Jan 28 17:15:18 2021
Return-Path: <superuser@gmail.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 401473A0925 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 17:15:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qNKZHhcI7NcC for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 17:15:14 -0800 (PST)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF9B3A091C for <dmarc@ietf.org>; Thu, 28 Jan 2021 17:15:14 -0800 (PST)
Received: by mail-vk1-xa2f.google.com with SMTP id e1so1808165vkd.10 for <dmarc@ietf.org>; Thu, 28 Jan 2021 17:15:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L9sVRGaDN21l64bM39/PBLUZi6xK7Mh/nBIBmXgdkPw=; b=KC0XADpRffI73j+bcq7QE5eCB8jjWmUs5xwxpSBqG3E4MUJ7Z/40B4FSGukBGXYAJ+ 5YFZI1jKOCnnaulAPGcZixPaI1QP+qGQh8CYGhPydsKkF3fo8NN0RmKiYLu8rs38m77B yNDGwS/kOLoU/K3Ytpp9pTY8IU11vBTy9nQToRxqP/+iuujVevMTLKz0joIlpZhxOlPl +PxVkkZWfmWPaqivIOAQyokPzvZvJZfhNGz3tHhqkodvjEnI2/t220S+Rm7XAC7Gs40H su2coo4vkrSqprg70jmZd+q8i9EMUQeapb1wIAT9XnvaWjWVcr8JRlEEvqG/KAdbNjf2 uVYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L9sVRGaDN21l64bM39/PBLUZi6xK7Mh/nBIBmXgdkPw=; b=sGnxbHdjnv6xC8M+DZZEf+yUmd+PtHYS+hqzAyxGj/GXu0ZiQANVQGIUflb8i5WWR/ vIg9batlfh/3CRSZuzIvJkI4Ve0wkL36rnoPvM/oPSiNM15URMlPJZQ8gQjHCNlGh0Ar iGa+eTyuw9151yHZ0gvDn7rNWBRKBL1rfln3SRRHbKTX9OcNHMeqdPVqRA43whtjcmoY qxI42agQ3Z77eRuJXTF0eZ7s09PLdHJBktOk+wmsrNVmVA9oRsZrIq8o+fb4qGLXURwr DZZMrCXBSDAEbWquK+yhZ+062mRbAGU+dEdVm62yD5/5d4s/5cOr8A2KUSGk+VhnQkoR sJMA==
X-Gm-Message-State: AOAM533s5NvaHQDdiiKOvaIaO44UCrE4rFCi/53j5xp7PkgGQOVKaNwE YNic3xyNrhr+RBpr6GWANzWHRVY9FDiBV7mDH2qW9Yb5on4=
X-Google-Smtp-Source: ABdhPJwhQMb0idgg83y4ypHDidrNeiR9beRqllm6rzn0JhZMaGC9bjKILjulbdUNBjYEUIPqG3emWNa8lJ7prx0vBkI=
X-Received: by 2002:a1f:3889:: with SMTP id f131mr1641598vka.22.1611882913323;  Thu, 28 Jan 2021 17:15:13 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com> <CAL0qLwb3Z6DbVCvhSF=G6dxjoYwjLvwzbG0OOAUbD=F8H6+wyg@mail.gmail.com> <661b7adf-fcf3-1ada-4b84-cb4ee23a48a@taugh.com>
In-Reply-To: <661b7adf-fcf3-1ada-4b84-cb4ee23a48a@taugh.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 28 Jan 2021 17:15:01 -0800
Message-ID: <CAL0qLwZt6GNkDPrme5QuDqRCpZ3Tw5ESNqH_ehOBRT22w02WiQ@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000077de3305b9ffbc80"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PemBbK4Jt09eepJZRi1KWTNz-HE>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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: Fri, 29 Jan 2021 01:15:16 -0000

--00000000000077de3305b9ffbc80
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 28, 2021 at 1:42 PM John R Levine <johnl@taugh.com> wrote:

> > This to me is almost exactly the same thing as saying "Don't generate a
> > bounce about a bounce",
>
> Because these are not bounces.  They are not even a little bit like
> bounces.  Bounces are about invalid recipient addresses, but these have no
> relation to anything about the recipient address.
>

Yes, I realize the difference.  I was making an analogy.

They are fresh new messages sent from a system that presumably cares
> enough about DMARC to send reports about it, and presumably wants to send
> all of its mail with DMARC alignment.  If they are unaligned, that is
> because the sending system is broken, and if that systems publishes an
> ruf= tag, it is specifically asking to be inforned about exactly that
> breakage.
>

OK, let's hop into your example.  I care enough about DMARC to send reports
about it, and I want to send all of my mail aligned.  I send a test message
that ends up unaligned somehow, perhaps through a broken relay I don't own,
and I would ideally like to get one message back that tells me that.  If I
happen to send my test to a place that unintentionally sends an unaligned
report back to me, perhaps because of the same relay, I'm going to get
flooded, even though my local setup is verifiably correct.  And, probably,
so are they.

You're saying the only real answer here is that the two end operators in
this example need to fix their evidently-crappy setups, or change their DNS
records to remove the "ruf" value until they can get the guy in the middle
to fix whatever's broken?

Maybe I'm the dim one, but I can't see why it's manifestly absurd to think
we might somehow augment either the report or the message containing it by
adding just enough metadata someplace to signal one end or the other, or
both, to avert the flood.

-MSK

--00000000000077de3305b9ffbc80
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 28, 2021 at 1:42 PM John R Le=
vine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; wrote:<=
br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">&gt; This to me is almost exactly the same thing as saying &quot=
;Don&#39;t generate a<br>
&gt; bounce about a bounce&quot;,<br>
<br>
Because these are not bounces.=C2=A0 They are not even a little bit like <b=
r>
bounces.=C2=A0 Bounces are about invalid recipient addresses, but these hav=
e no <br>
relation to anything about the recipient address.<br></blockquote><div><br>=
</div><div>Yes, I realize the difference.=C2=A0 I was making an analogy.</d=
iv><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
They are fresh new messages sent from a system that presumably cares <br>
enough about DMARC to send reports about it, and presumably wants to send <=
br>
all of its mail with DMARC alignment.=C2=A0 If they are unaligned, that is =
<br>
because the sending system is broken, and if that systems publishes an <br>
ruf=3D tag, it is specifically asking to be inforned about exactly that <br=
>
breakage.<br></blockquote><div><br></div><div>OK, let&#39;s hop into your e=
xample.=C2=A0 I care enough about DMARC to send reports about it, and I wan=
t to send all of my mail aligned.=C2=A0 I send a test message that ends up =
unaligned somehow, perhaps through a broken relay I don&#39;t own, and I wo=
uld ideally like to get one message back that tells me that.=C2=A0 If I hap=
pen to send my test to a place that unintentionally sends an unaligned repo=
rt back to me, perhaps because of the same relay, I&#39;m going to get floo=
ded, even though my local setup is verifiably correct.=C2=A0 And, probably,=
 so are they.</div><div><br></div><div>You&#39;re saying the only real answ=
er here is that the two end operators in this example need to fix their evi=
dently-crappy setups, or change their DNS records to remove the &quot;ruf&q=
uot; value until they can get the guy in the middle to fix whatever&#39;s b=
roken?<br></div><div><br></div><div>Maybe I&#39;m the dim one, but I can&#3=
9;t see why it&#39;s manifestly absurd to think we might somehow augment ei=
ther the report or the message containing it by adding just enough metadata=
 someplace to signal one end or the other, or both, to avert the flood.<br>=
</div><div><br></div><div>-MSK<br></div></div></div>

--00000000000077de3305b9ffbc80--


From nobody Thu Jan 28 17:30:11 2021
Return-Path: <johnl@taugh.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 77D5E3A0981 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 17:30:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=KgyAOzjv; dkim=pass (2048-bit key) header.d=taugh.com header.b=hDwS7LCN
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 TCxdAmhd2gA6 for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 17:30:08 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 528AD3A0977 for <dmarc@ietf.org>; Thu, 28 Jan 2021 17:30:07 -0800 (PST)
Received: (qmail 50320 invoked from network); 29 Jan 2021 01:30:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=c48c.6013651d.k2101; bh=Br0udqHYpQHd1CMT9LqmatEPz2f6wd/VZZuu3AKwnE4=; b=KgyAOzjvKufWeaRWCkDTX2OwCLHVoW1g4e5uXUymRJPPO+xxQCuKOTxAEMPlEgyhUHzsEkr6GvkUwDee6NDt4LXhoG71IdAbrO2nGB2kawTi18UKhVJUNGxl+dx5lMepEiTValf1IYlEqGOlMI9bHTlqKuaZ9kgYZa/6Oq1J3KM6ujhTi5GeXA4lvacDN2rxVa3ZozLENhdzk22bzZ0HJC6rZHEun7RKbR0ZvguNMmvccXPyPLAS0peUcxnD4KzNWjLuZZ+w1uHGDglKwD/Qe4DBihqdlBPnPbaqg3ybgP1gAPXCdVDSjhfo5wJAMESgBfeoFiE5Vn8bKRDtm8smRQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=c48c.6013651d.k2101; bh=Br0udqHYpQHd1CMT9LqmatEPz2f6wd/VZZuu3AKwnE4=; b=hDwS7LCNLGY5H3SoTuggOwFgdK6UUPc2j+O2zENQBKysgOOWCxZdE/eri3dPCI5Phh+2Bzbb/UYuN56l5+4NhSlDyd/q8dInHUa/p0JyunsOhA9rBe0nSELzPpYJ7w7ibNxDA4YuMRh6BFkMetomgzl8VJnzdITuvH/UoTW7CWl2jGSXtD6rtRKj5ICFfIvA+Sr7HJHpyvpCqnV3Z8WmHCTHOt+3nF5bcMD7DLyAa5XFeD1KKn7ZJp7Nn+cV0pQwPC0FW1vvJdgP/jNiI9AZl3vd0vOvhWIg/qGTAZZjzGdWyssEKuczS1+Ldt6vJ0/Bx9H9qWXEUN/m3qGIU5WWPQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 29 Jan 2021 01:30:05 -0000
Received: by ary.qy (Postfix, from userid 501) id 0057F6CE8151; Thu, 28 Jan 2021 20:30:04 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 6917E6CE8133; Thu, 28 Jan 2021 20:30:04 -0500 (EST)
Date: 28 Jan 2021 20:30:04 -0500
Message-ID: <e4f1469b-1c42-24f6-f06a-b8bf12f7da0@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "IETF DMARC WG" <dmarc@ietf.org>
In-Reply-To: <CAL0qLwZt6GNkDPrme5QuDqRCpZ3Tw5ESNqH_ehOBRT22w02WiQ@mail.gmail.com>
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <526bf4d5-5a7d-5a91-b965-36ffeab933f7@taugh.com> <CAL0qLwb3Z6DbVCvhSF=G6dxjoYwjLvwzbG0OOAUbD=F8H6+wyg@mail.gmail.com> <661b7adf-fcf3-1ada-4b84-cb4ee23a48a@taugh.com> <CAL0qLwZt6GNkDPrme5QuDqRCpZ3Tw5ESNqH_ehOBRT22w02WiQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/sM59lruJ8bJsyt7eqZfCID77tPM>
Subject: Re: [dmarc-ietf] report floods, not Forensic report loops are a problem
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: Fri, 29 Jan 2021 01:30:11 -0000

> OK, let's hop into your example.  I care enough about DMARC to send reports
> about it, and I want to send all of my mail aligned.  I send a test message
> that ends up unaligned somehow, perhaps through a broken relay I don't own,
> and I would ideally like to get one message back that tells me that.  If I
> happen to send my test to a place that unintentionally sends an unaligned
> report back to me, perhaps because of the same relay, I'm going to get
> flooded, even though my local setup is verifiably correct.  And, probably,
> so are they.

Report floods could be a problem, but they're a general problem that don't 
have a lot to do with failure loops.  I used to get buckets of failure 
reports about random chinese spam that forged my domains on the From line.

It's reasonable to say that reporters should rate limit failure reports to 
avoid flooding recipients, but that's true no matter who sent the mail 
being reported.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Thu Jan 28 22:44:34 2021
Return-Path: <superuser@gmail.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 710FE3A0CDD for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 22:44:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WJdGibs24raR for <dmarc@ietfa.amsl.com>; Thu, 28 Jan 2021 22:44:32 -0800 (PST)
Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF3763A0CDC for <dmarc@ietf.org>; Thu, 28 Jan 2021 22:44:31 -0800 (PST)
Received: by mail-ua1-x935.google.com with SMTP id a31so2835754uae.11 for <dmarc@ietf.org>; Thu, 28 Jan 2021 22:44:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=v1OT/B1hSeKuptTuiV+UXv1zTU0hJIMAFdElqz08naY=; b=r3B/SBthFzXAbcAFPHuf6O19bCatEGLhQBO0gcuALl7bQWyZgTudJJ8uxEXASwfdkd Lqv5xUXVD14Nu02AC/GcSaNg9vuirHx1l+3b8J797vr62fHFK1vSG56SN0wkU2cTwnPa YNcYJjSYngPhMwuBpT0YwTeI/DxlBI15H8g/pt1P5iDTGkFH/A+Tih+eJEyUrkEmcGML epjJ1mG8m3/tMDs0x3vX9No4b7bLaRzn9XfHWqoetLApTQ6X1gpkP3zPjcD0bu+zR1Th tAbo+ytygbYEXVEy+sKcppNSSGOSBThjLR7A/n9cPnZe6Wpbm4Ma+ou7d5hcpdPjsGTa GAKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v1OT/B1hSeKuptTuiV+UXv1zTU0hJIMAFdElqz08naY=; b=af5CMQD9FyJWDrLKjb7LBfOQdq9242iPFaRMhj6n9sEpG4nVE2RRKRN2ynbWZbDRO+ bYklAx17rDrmz+Rf/IUPNc29J+g0QPs5oZBsjbAvTdKuhSIjPl1aFtvDqtzYDcFAku2S nlfZ8RHxQaRfM/xoQdNCPqsmEufbOAOJ8JvazpOSwSzydRI6Lu6uKeV4e/TuUyD/EN1Y R5kfRcYL6UxBo3TCCn3Ofqfq2s7LZCm2aspGHpDdo1fdnhBS/vkoAE7inpsD/2Z1cm7B Qm452D4zQkswgehM1pTrJJlqV7fE+3erVSoVRJr/9GSGqr9F6MikIYsNLDXswpnq9Xk3 w5Aw==
X-Gm-Message-State: AOAM532IRy7lUw7rFwAouUCU2kHreuHNP5hLH2GQIFwMfwHu6DsbDUf7 2P8scii2mAyl1zWFAWmVkpSu6rdWsrEKItz5F6Q=
X-Google-Smtp-Source: ABdhPJz2OiC/T3Q3vPErAZqAVOnLhB68qMsWwuRjm8BDKy/O13Ap9/g+poBqTKP2GFSRQXgTE4bnPvKOX08fbAoXGEs=
X-Received: by 2002:ab0:614d:: with SMTP id w13mr1853983uan.67.1611902670910;  Thu, 28 Jan 2021 22:44:30 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com> <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com> <CADyWQ+FejAGbv8TLrGXpV_Crgi1KErKK_1-6=2jzZh+QbguK6Q@mail.gmail.com>
In-Reply-To: <CADyWQ+FejAGbv8TLrGXpV_Crgi1KErKK_1-6=2jzZh+QbguK6Q@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 28 Jan 2021 22:44:19 -0800
Message-ID: <CAL0qLwYrXEaOVphUjAB1guQO=s+ppabP1q4Ne16rqF=e6JsqLw@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: "Kurt Andersen (b)" <kboth@drkurt.com>, IETF DMARC WG <dmarc@ietf.org>, Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="0000000000001cb80105ba0456f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/IasOBn_MSpPweunFV1uCYCTK3vo>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 29 Jan 2021 06:44:33 -0000

--0000000000001cb80105ba0456f6
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 22, 2021 at 5:01 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:

> Since this is an experiment, Appendix A discusses the updates that
> happen.  we don't actually say explicitly "if the experiment is a success,
> the following changes will be made" and perhaps I should add some wording
> like that.
>

Something like this, perhaps?

"A standards track update to [RFC7489] will take into account the results
of this experiment."

... somewhere in Section 1.

-MSK

--0000000000001cb80105ba0456f6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 5:01 PM Tim Wicin=
ski &lt;<a href=3D"mailto:tjw.ietf@gmail.com">tjw.ietf@gmail.com</a>&gt; wr=
ote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr">Since this is an experiment, Appendix A di=
scusses the updates that happen.=C2=A0 we don&#39;t actually=C2=A0say expli=
citly=C2=A0&quot;if the experiment is a success, the following changes will=
 be made&quot; and perhaps I should add some wording like that. <br></div><=
/blockquote><div><br></div><div>Something like this, perhaps?<br><br></div>=
<div>&quot;A standards track update to [RFC7489] will take into account the=
 results of this experiment.&quot;</div><div><br></div><div>... somewhere i=
n Section 1.<br></div><div><br></div><div>-MSK<br></div></div></div>

--0000000000001cb80105ba0456f6--


From nobody Fri Jan 29 03:03:03 2021
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 443363A0ADA for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 03:03:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 CLxjQepPa--P for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 03:03:00 -0800 (PST)
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 948243A0AD6 for <dmarc@ietf.org>; Fri, 29 Jan 2021 03:03:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611918176; bh=+5yJh4z+zsMeKC1ZHok4S3EbXasJnaNjkY+/PEwOhqA=; l=2460; h=To:References:From:Date:In-Reply-To; b=CXSNio3p6Vt5+ibMTg+BE3r0FxmbYFA/xHH1Nxy35oVGAdg1hmL6NE1NSKvsPDXmi 1RGpZzM2+eXATemobrQy+7jOLQB7b1tSWK0gkESzrLEcZ/AdpzQ54Cw5367P2erdfC bw6K0zulSJSlL29xFeOfjJYQSOLf7WGt7+uz1PzP4Qx1pal0bkCAiOzY24WcK
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC026.000000006013EB5F.00003F1C; Fri, 29 Jan 2021 12:02:55 +0100
To: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com> <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it> <CAL0qLwbYxTXXXpx11L3f1CqBns=fSRho3C+S7q=-DmiPSvxKvg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <cf51d6d4-0c7b-971d-bcac-743370f16433@tana.it>
Date: Fri, 29 Jan 2021 12:02:55 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbYxTXXXpx11L3f1CqBns=fSRho3C+S7q=-DmiPSvxKvg@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/vaxAF1uWuIc4_M2O0mBczgpUMgU>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Fri, 29 Jan 2021 11:03:02 -0000

On Thu 28/Jan/2021 21:40:49 +0100 Murray S. Kucherawy wrote:
> On Thu, Jan 28, 2021 at 4:13 AM Alessandro Vesely <vesely@tana.it> wrote:
> 
>>> DKIM (in its simplest form) returns N tuples of the form (d= domain, 
>>> pass/fail).  All of them were run through exactly the same check; all
>>> of them were attached to the message in exactly the same way; all of
>>> them have essentially identical semantics.  Giving them equal footing
>>> makes sense to me. >>>
>>> The two identifiers in SPF hold different places in the SMTP session,
>>> and have different semantics.  I think treating them differently is also
>>> just fine. >>
>> It is relevant that both identifier come from /the same/ SMTP session. 
>> That's not true for many DKIM signatures. >
> I guess if report consumers really want this information, we can include
> it.


Helo is essential if mfrom is missing.  A second SPF identifier is optional anyway.


> I just don't see the value in the HELO parameter if it's effectively
> random junk in the session.


Where does that notion come from?  Most mail admins choose the helo name 
carefully, possibly so that it resolves both ways to the IP number.

I just run a quick test on my current folder.  Out of 3879 messages I extracted 
944 unique helo names.  721 of these matched the reverse lookup exactly.  Out 
of the 223 remaining, 127 had an SPF pass for the helo identity anyway.  So in 
96 cases, roughly 10%, the helo name was indeed junk.  Isn't the remaining ~90% 
something worth considering?


> At least a passing DKIM signature is associated with a domain that existed
> at some point in time and whose DNS contained apparently-valid public keys.

Why cannot one type DKIM-Signature: d=anyrandomjunk ...?


> I can mostly type anything I want to HELO or EHLO.


That's true for any identifier.  We know an identifier is associated with a 
domain that existed at some point in time only after it's been authenticated.

One may say DKIM authentication is somewhat more precise, because the vogue is 
to include whole classes of IPs in SPF records.  But then, such lack of 
accuracy affects mfrom and helo alike.

The real difference between helo and mfrom is that the former is a 
configuration parameter of the sending relay, while the latter is set by the 
submission client.  The former is akin to d= and s=, while the latter is akin 
to From:.  No rationale to discard either, AFAICS.


Best
Ale
-- 
















From nobody Fri Jan 29 06:52:47 2021
Return-Path: <tjw.ietf@gmail.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 8BE773A0E18 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 06:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 hlFe7wJCtrfa for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 06:52:44 -0800 (PST)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 745383A1042 for <dmarc@ietf.org>; Fri, 29 Jan 2021 06:52:43 -0800 (PST)
Received: by mail-ot1-x330.google.com with SMTP id k8so8814152otr.8 for <dmarc@ietf.org>; Fri, 29 Jan 2021 06:52:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=My6EqM74goF+wLYeJMfR2IlDWvpDpl6p0pYGc4kacis=; b=jC/SUfScGTWaXDL1Y+4mq/fCX2lQAy+W4CJPyybHaNE+cmeMPwx0YbkJoPhaEP08Fk 9OYovColDBFbsps2AH5ZpY7Vuh/FlrMdtWQHy025+MShFB6pXuShn6S/ReH/YCzZdaaw 2WNEdNw+ihizwTob2rHnqumjjM3q47V1XfllEoowSajUeJ7CgIqQX6AQFWW/Ay+qEBKp ShuRnnATA+EOf9DuM61LwFqb3pYbZ2JxVmjqhL/Va/DHJGOOiSM3tx2X6JgbSbgtLfMQ U9CRGCm/g3p679rijsprdYdEp5HbRt87KHp56Wv6KTxOyq4RqyWveRehLlB/2EtACfAl 2BmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=My6EqM74goF+wLYeJMfR2IlDWvpDpl6p0pYGc4kacis=; b=WnJO7WY9HD3fFJXSXSzEUyImV4gDRZRRJWcbLtrO3J2TucQIf528yfqYHfPXf0wkGk 2IF/9UNVz5ydMzft5I8Q+YAyzCRGv1TfxT5ZOUqmivS3LBo9Ag5z/tqNqxxHnZ7AwNqX JCq3MJs974unr0QCwLiK0Baq7gXLhzpL3G0d28m+0NPORmYS+sIw8nfGclNNY6uQkugL 4FU1GyPNe9DIz60mq/lxQHY13zxmOfPpGuC3ImoZQPjmr/JWkmMGFBoaA69smW1Wylus Xvc+8jb3gwlgXgmN5M/CFm1sIgL8nj/jWAfDz2hUw6dNdB5aj68LbqzrNe6641ikLFJZ H5ZQ==
X-Gm-Message-State: AOAM532+ndN8MbEiG+8l98n/eq9ayFKsiwO9DiZ2kIReFTz+U4F7ijVP Bnwx7tdHU4rgNl15NFi2AyVQ1EYrtW0EffH7VKrSn6GNMkU=
X-Google-Smtp-Source: ABdhPJwJUkkuwHBBbHXxgAFR37JsPEeuAvIORtC9m7g7mE8gylSBSefbrp8n2bEjQ2gc0aWn6zjYdNxn/4gO25w17FM=
X-Received: by 2002:a05:6830:208d:: with SMTP id y13mr3203740otq.288.1611931962784;  Fri, 29 Jan 2021 06:52:42 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com> <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com> <CADyWQ+FejAGbv8TLrGXpV_Crgi1KErKK_1-6=2jzZh+QbguK6Q@mail.gmail.com> <CAL0qLwYrXEaOVphUjAB1guQO=s+ppabP1q4Ne16rqF=e6JsqLw@mail.gmail.com>
In-Reply-To: <CAL0qLwYrXEaOVphUjAB1guQO=s+ppabP1q4Ne16rqF=e6JsqLw@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 29 Jan 2021 09:52:31 -0500
Message-ID: <CADyWQ+Fx-jVGGgzf6-R6n1OzpwQR3akFJeVNqmq=XN_X=1B-Cg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "Kurt Andersen (b)" <kboth@drkurt.com>, IETF DMARC WG <dmarc@ietf.org>, Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="0000000000000b40d205ba0b28e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/uW-8CjfCBnNzO5Xofk_akOh2PiQ>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 29 Jan 2021 14:52:46 -0000

--0000000000000b40d205ba0b28e1
Content-Type: text/plain; charset="UTF-8"

I suggest adding it to this paragraph:

   This document specifies experimental updates to the DMARC and PSL
   algorithm cited above, in an attempt to mitigate this abuse.



On Fri, Jan 29, 2021 at 1:44 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Fri, Jan 22, 2021 at 5:01 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>
>> Since this is an experiment, Appendix A discusses the updates that
>> happen.  we don't actually say explicitly "if the experiment is a success,
>> the following changes will be made" and perhaps I should add some wording
>> like that.
>>
>
> Something like this, perhaps?
>
> "A standards track update to [RFC7489] will take into account the results
> of this experiment."
>
> ... somewhere in Section 1.
>
> -MSK
>

--0000000000000b40d205ba0b28e1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e"><br></div><div class=3D"gmail_default" style=3D"font-family:monospace">I=
 suggest adding it to this paragraph:</div><div class=3D"gmail_default" sty=
le=3D"font-family:monospace"><br></div><div class=3D"gmail_default" style=
=3D"font-family:monospace">=C2=A0 =C2=A0This document specifies experimenta=
l updates to the DMARC and PSL<br>=C2=A0 =C2=A0algorithm cited above, in an=
 attempt to mitigate this abuse.<br></div><div class=3D"gmail_default" styl=
e=3D"font-family:monospace"><br></div><div class=3D"gmail_default" style=3D=
"font-family:monospace"><br></div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 29, 2021 at 1:44 AM Murray S.=
 Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com">superuser@gmail.com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 5:01 PM Tim Wicinsk=
i &lt;<a href=3D"mailto:tjw.ietf@gmail.com" target=3D"_blank">tjw.ietf@gmai=
l.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr">Since this is an experime=
nt, Appendix A discusses the updates that happen.=C2=A0 we don&#39;t actual=
ly=C2=A0say explicitly=C2=A0&quot;if the experiment is a success, the follo=
wing changes will be made&quot; and perhaps I should add some wording like =
that. <br></div></blockquote><div><br></div><div>Something like this, perha=
ps?<br><br></div><div>&quot;A standards track update to [RFC7489] will take=
 into account the results of this experiment.&quot;</div><div><br></div><di=
v>... somewhere in Section 1.<br></div><div><br></div><div>-MSK<br></div></=
div></div>
</blockquote></div>

--0000000000000b40d205ba0b28e1--


From nobody Fri Jan 29 06:59:46 2021
Return-Path: <tjw.ietf@gmail.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 824833A1048 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 06:59:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 b7VOusrfVf3p for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 06:59:42 -0800 (PST)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAA073A1042 for <dmarc@ietf.org>; Fri, 29 Jan 2021 06:59:42 -0800 (PST)
Received: by mail-ot1-x330.google.com with SMTP id 36so8852032otp.2 for <dmarc@ietf.org>; Fri, 29 Jan 2021 06:59:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=riZ5+OCu7wvtKlxFx4PPZjLaCqw7UzbXTWuOBVLzOiE=; b=ocMfMmoXuUoFn+BfUUCpBoB+hpVCDcmD1Rz96j8ZSgPt4EyjYx2GRrHPuHakf0cbx+ diZ0sSBP49v7xNrOXBt8CsxhRLkymn1Z9yZxY2au5DpgD10mRiNYKrHunUPObQbhvd5m Ib8UBq3z5bq0+i9EM2fGJx/JUi/O05eFHfwXCYWB+21uo1Pip8hA6806J/1Sy5pX9Sj7 cFIfb+bjDwzOouYrWZODL7X9n7zlm7EX29X0zjMdIKlRp41EunNvRs8GCTb+TKfoHdZF RwO89eh9Quua6nsXgfHl/E+3hkyJLgzCi/ffgMJ4chFEsI1KZL6zpKUjCHScCVTuU2Vo NgKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=riZ5+OCu7wvtKlxFx4PPZjLaCqw7UzbXTWuOBVLzOiE=; b=XOy3J3eXDxkxfqF1N5djKVpaoFNaBjOnnOsfM9g1XzhEBXUPYhBLy2pEXfvD/wk0dB uaYDfjQLak/ggv75BkUswpmMQiJ4McA11q0EIhncaLgYkJiwRiKgVMpZVtZTu68v5nxl a9YIBd9lllee/r593QVK2vL+AOIHINeyNboc1k6BnZFgYJXzjbp6VUcYB3xJnVLyVfOI Ci8ckdMlulSxUChMnBFbtRLwLcO0HwqTSFyXtl5DIi7a0f+fEi/235Uunx5xCyN0v0mj Yn9htEq0wQUBc6GTx8gHW3fiupqyXHE5YKVNgkuNT5TmEYj4A/UE1WZvGm51pEYdENOy xksg==
X-Gm-Message-State: AOAM532kobrOYGzm0dmmpngXGU94HMlXHbadaNnAofADEMCGBKbfRYZq CEpJXnSYDPJD/dJH240NbdqNNKoP7cwZ0uFlJCdRsAw8dFA=
X-Google-Smtp-Source: ABdhPJxJX3rIlFp6RB/boVq+vnHywhfWFQa24ya+CcFu5A6j5cuiYeLWDMm8zmmB4kAb2LteNobI8bCnkPqhrDo01uw=
X-Received: by 2002:a05:6830:208d:: with SMTP id y13mr3220623otq.288.1611932381934;  Fri, 29 Jan 2021 06:59:41 -0800 (PST)
MIME-Version: 1.0
References: <161144436332.13490.10651420808048876097@ietfa.amsl.com>
In-Reply-To: <161144436332.13490.10651420808048876097@ietfa.amsl.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 29 Jan 2021 09:59:30 -0500
Message-ID: <CADyWQ+EhD0nz71dLtUFwb9V_6uuen-k6E5fpvrCg3ZYzfr2JSw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000006f8d505ba0b41f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/r9gyec6b6bq7Gwf2NX0xQOpXLPo>
Subject: [dmarc-ietf] Fwd:  I-D Action: draft-ietf-dmarc-psd-10.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: Fri, 29 Jan 2021 14:59:45 -0000

--00000000000006f8d505ba0b41f3
Content-Type: text/plain; charset="UTF-8"

All

We've done a number of updates to the PSD document to reflect the GEN-ART
review,
mostly to expand on the experiments.  There has been enough changes that we
want to do a short
working group last call.

https://tools.ietf.org/html/draft-ietf-dmarc-psd-10

To look at the differences, I would suggest looking at this diff from the
-08 version and the current version:

https://www.ietf.org/rfcdiff?url1=draft-ietf-dmarc-psd-08&url2=draft-ietf-dmarc-psd-10

This starts a *one week* Working Group Last Call.  Please review the
changes and offer up comments.
Offering suggestive text would be really useful as well.

This WGLC will end 5 February 2021

tim


---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Sat, Jan 23, 2021 at 6:26 PM
Subject: [dmarc-ietf] I-D Action: draft-ietf-dmarc-psd-10.txt
To: <i-d-announce@ietf.org>
Cc: <dmarc@ietf.org>



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Domain-based Message Authentication,
Reporting & Conformance WG of the IETF.

        Title           : Experimental DMARC Extension For Public Suffix
Domains
        Author          : Scott Kitterman
        Filename        : draft-ietf-dmarc-psd-10.txt
        Pages           : 14
        Date            : 2021-01-23

Abstract:
   DMARC (Domain-based Message Authentication, Reporting, and
   Conformance) is a scalable mechanism by which a mail-originating
   organization can express domain-level policies and preferences for
   message validation, disposition, and reporting, that a mail-receiving
   organization can use to improve mail handling.  The design of DMARC
   presumes that domain names represent either nodes in the tree below
   which registrations occur, or nodes where registrations have
   occurred; it does not permit a domain name to have both of these
   properties simultaneously.  Since its deployment in 2015, use of
   DMARC has shown a clear need for the ability to express policy for
   these domains as well.

   Domains at which registrations can occur are referred to as Public
   Suffix Domains (PSDs).  This document describes an extension to DMARC
   to enable DMARC functionality for PSDs.

   This document also seeks to address implementations that consider a
   domain on a public Suffix list to be ineligible for DMARC
   enforcement.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmarc-psd/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dmarc-psd-10
https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-psd-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmarc-psd-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

--00000000000006f8d505ba0b41f3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e">All</div><div class=3D"gmail_default" style=3D"font-family:monospace"><b=
r></div><div class=3D"gmail_default" style=3D"font-family:monospace">We&#39=
;ve done a number of updates to the PSD document to reflect the GEN-ART rev=
iew,</div><div class=3D"gmail_default" style=3D"font-family:monospace">most=
ly to expand on the experiments.=C2=A0 There has been enough changes that w=
e want to do a short</div><div class=3D"gmail_default" style=3D"font-family=
:monospace">working group last call.=C2=A0 =C2=A0</div><div class=3D"gmail_=
default" style=3D"font-family:monospace"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-family:monospace"><a href=3D"https://tools.ietf.org/html=
/draft-ietf-dmarc-psd-10">https://tools.ietf.org/html/draft-ietf-dmarc-psd-=
10</a><br></div><div class=3D"gmail_default" style=3D"font-family:monospace=
"><br></div><div class=3D"gmail_default" style=3D"font-family:monospace">To=
 look at the differences, I would suggest looking at this diff from the -08=
 version and the current version:</div><div class=3D"gmail_default" style=
=3D"font-family:monospace"><br></div><div><font face=3D"monospace"><a href=
=3D"https://www.ietf.org/rfcdiff?url1=3Ddraft-ietf-dmarc-psd-08&amp;url2=3D=
draft-ietf-dmarc-psd-10" target=3D"_blank">https://www.ietf.org/rfcdiff?url=
1=3Ddraft-ietf-dmarc-psd-08&amp;url2=3Ddraft-ietf-dmarc-psd-10</a><br></fon=
t></div><div><br></div><div><div class=3D"gmail_default" style=3D"font-fami=
ly:monospace">This starts a *one week* Working Group Last Call.=C2=A0 Pleas=
e review the changes and offer up comments.</div><div class=3D"gmail_defaul=
t" style=3D"font-family:monospace">Offering suggestive text would be really=
 useful as well.=C2=A0</div><div class=3D"gmail_default" style=3D"font-fami=
ly:monospace"><br></div><div class=3D"gmail_default" style=3D"font-family:m=
onospace">This WGLC will end 5 February 2021</div><div class=3D"gmail_defau=
lt" style=3D"font-family:monospace"><br></div><div class=3D"gmail_default" =
style=3D"font-family:monospace">tim</div><div class=3D"gmail_default" style=
=3D"font-family:monospace"><br></div><div class=3D"gmail_default" style=3D"=
font-family:monospace"><br></div></div><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">---------- Forwarded message ---------<br>Fro=
m: <span dir=3D"auto">&lt;<a href=3D"mailto:internet-drafts@ietf.org" targe=
t=3D"_blank">internet-drafts@ietf.org</a>&gt;</span><br>Date: Sat, Jan 23, =
2021 at 6:26 PM<br>Subject: [dmarc-ietf] I-D Action: draft-ietf-dmarc-psd-1=
0.txt<br>To:  &lt;<a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank=
">i-d-announce@ietf.org</a>&gt;<br>Cc:  &lt;<a href=3D"mailto:dmarc@ietf.or=
g" target=3D"_blank">dmarc@ietf.org</a>&gt;<br></div><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Domain-based Message Authentication, Repor=
ting &amp; Conformance WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Experimental DMARC Extension For Public Suffix Domains<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Scot=
t Kitterman<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-dmarc-psd-10.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 14<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2021-01-23<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0DMARC (Domain-based Message Authentication, Reporting, and<br>
=C2=A0 =C2=A0Conformance) is a scalable mechanism by which a mail-originati=
ng<br>
=C2=A0 =C2=A0organization can express domain-level policies and preferences=
 for<br>
=C2=A0 =C2=A0message validation, disposition, and reporting, that a mail-re=
ceiving<br>
=C2=A0 =C2=A0organization can use to improve mail handling.=C2=A0 The desig=
n of DMARC<br>
=C2=A0 =C2=A0presumes that domain names represent either nodes in the tree =
below<br>
=C2=A0 =C2=A0which registrations occur, or nodes where registrations have<b=
r>
=C2=A0 =C2=A0occurred; it does not permit a domain name to have both of the=
se<br>
=C2=A0 =C2=A0properties simultaneously.=C2=A0 Since its deployment in 2015,=
 use of<br>
=C2=A0 =C2=A0DMARC has shown a clear need for the ability to express policy=
 for<br>
=C2=A0 =C2=A0these domains as well.<br>
<br>
=C2=A0 =C2=A0Domains at which registrations can occur are referred to as Pu=
blic<br>
=C2=A0 =C2=A0Suffix Domains (PSDs).=C2=A0 This document describes an extens=
ion to DMARC<br>
=C2=A0 =C2=A0to enable DMARC functionality for PSDs.<br>
<br>
=C2=A0 =C2=A0This document also seeks to address implementations that consi=
der a<br>
=C2=A0 =C2=A0domain on a public Suffix list to be ineligible for DMARC<br>
=C2=A0 =C2=A0enforcement.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dmarc-psd/" rel=3D"n=
oreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-dm=
arc-psd/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-dmarc-psd-10" rel=3D"nore=
ferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-dmarc-psd-=
10</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-psd-10" r=
el=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/html/d=
raft-ietf-dmarc-psd-10</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dmarc-psd-10" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?url2=3Ddraft=
-ietf-dmarc-psd-10</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</div></div>

--00000000000006f8d505ba0b41f3--


From nobody Fri Jan 29 07:51:16 2021
Return-Path: <dcrocker@gmail.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 0FF343A10E5 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 07:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LyTxWrVlyGmv for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 07:51:13 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 880363A0D86 for <dmarc@ietf.org>; Fri, 29 Jan 2021 07:51:13 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id f6so8977344ots.9 for <dmarc@ietf.org>; Fri, 29 Jan 2021 07:51:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=gJxM51rXmWh3bCqiDWVjHPstmOskcehV9dHtQpsHQbI=; b=NTMyVPWeqvX1OcyIHB8D3vKr3QU4yYSfO5CwN7e2rGQXMkBC3g+PHp5EWkOuo+LP14 poEk1aqq9fJAaIAnqSSRvb56dOtkg+4f949O69Uiycy7h/1x2je3x5QnPD0YEahBi0Ct rMgTEzRdpGBjvf22IM0XfQNR7b7VeA7t47qxWsfvHX9Ww/W2gDE+BwJk98Ox2OgcUOO2 lS9LWtGyE4vPNCBUIFikJ+V6Sy8Bx5xIeMgNubv6ouPyElK+8KtvB6BqrFF/gqPwryg3 zELkpkU2mcDfPdRLgGvTOdVHmYzADCtynNEsq6hXafuIMrqPDP3nJZ1RcWs71qoISlP8 kWVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=gJxM51rXmWh3bCqiDWVjHPstmOskcehV9dHtQpsHQbI=; b=ug/jGjqZ24C9aGNSs+ZJE0Tde2zGwn+9+2dOl8/5+6Z85ciU9UTBuXuQgQsXrLSMg2 MaEhGE10MGNomnzoYUVUjywLqhto8tAdJ/9r/g+HPmWpy4Q5vuQA9HG3wvDz8wn/lr2J U76mHLc0af8YS2ioo+XaOaRP7F/qDBD3wRtMdt2SPkHpeZv4J9KBfhZKmqqb/w6pjjHn xW2t6KgW/6QhHAht7dgrRRSnm2RpdOHz2Och10mTI1CFzRb+z5sE3a3514p7599lDvrX ubHqC52OukxEH/PlauZwR22/SMnU3Nl7h9NpKgvWk8x1eyyFT7Mz7cNHPZN9jKMi4RIU 8l9g==
X-Gm-Message-State: AOAM530IJxWEswrxBMVEkz7KQB9s1F9+NfmqDS1pLfjG4lYEyPLGxN0O 6KQEvwLxs93q6GQPh1UznpzvfFqC50w=
X-Google-Smtp-Source: ABdhPJxH2Tk31BC79S+vMvyqNjFIaOdt/9R9QRiS+Yl2vYoskThoyJW2jUCjYzFBxDgsgi6WtPes8g==
X-Received: by 2002:a05:6830:2313:: with SMTP id u19mr3346428ote.321.1611935472513;  Fri, 29 Jan 2021 07:51:12 -0800 (PST)
Received: from [192.168.0.109] (108-226-162-63.lightspeed.sntcca.sbcglobal.net. [108.226.162.63]) by smtp.gmail.com with ESMTPSA id q20sm2177756otf.2.2021.01.29.07.51.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Jan 2021 07:51:11 -0800 (PST)
To: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <161144436332.13490.10651420808048876097@ietfa.amsl.com> <CADyWQ+EhD0nz71dLtUFwb9V_6uuen-k6E5fpvrCg3ZYzfr2JSw@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <ba38a9e4-7f43-c747-2d90-f35de22a8399@gmail.com>
Date: Fri, 29 Jan 2021 07:51:10 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <CADyWQ+EhD0nz71dLtUFwb9V_6uuen-k6E5fpvrCg3ZYzfr2JSw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------56A4D3C23C39B7803912D6FE"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/EC5Z0-MsvRPIoYdLOF6ouU9W1WI>
Subject: Re: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-10.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: Fri, 29 Jan 2021 15:51:15 -0000

This is a multi-part message in MIME format.
--------------56A4D3C23C39B7803912D6FE
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 1/29/2021 6:59 AM, Tim Wicinski wrote:
> This starts a *one week* Working Group Last Call. 


Sorry, but even the Abstract appears to be littered with problematic 
language.

I always try to provide alternate language, when I can, but in spite of 
having offered suggestions for this document in the past, I can't for 
this set.


> Abstract
>
>     DMARC (Domain-based Message Authentication, Reporting, and
>     Conformance) is a scalable mechanism by which a mail-originating
>     organization can express domain-level policies and preferences for
>     message validation, disposition, and reporting, that a mail-receiving
>     organization can use to improve mail handling.  The design of DMARC
>     presumes that domain names represent either nodes in the tree below
>     which registrations occur, or nodes where registrations have
DMARC does not have 'registrations'.

Also the occur/occured contrast has no obvious meaning to me. Really, I 
have no idea what's intended by it.


>     occurred; it does not permit a domain name to have both of these
"both" of what?  registration?


>     properties simultaneously.  Since its deployment in 2015, use of
>     DMARC has shown a clear need for the ability to express policy for
>     these domains as well.
Which domains?


>     Domains at which registrations can occur are referred to as Public
>     Suffix Domains (PSDs).  This document describes an extension to DMARC
>     to enable DMARC functionality for PSDs.
This is the definition of public suffix provided by the PSL folk:

"A public suffix is a set of DNS names or wildcards concatenated with 
dots. It represents the part of a domain name which is *not* under the 
control of the individual registrant."


>     This document also seeks to address implementations that consider a
>     domain on a public Suffix list to be ineligible for DMARC
>     enforcement.
seeks?

implementations don't 'consider' anything.

is 'ineligibility' really the essential issue?

d/


-- 

Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


--------------56A4D3C23C39B7803912D6FE
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/29/2021 6:59 AM, Tim Wicinski
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CADyWQ+EhD0nz71dLtUFwb9V_6uuen-k6E5fpvrCg3ZYzfr2JSw@mail.gmail.com">This
      starts a *one week* Working Group Last Call. </blockquote>
    <p><br>
    </p>
    <p>Sorry, but even the Abstract appears to be littered with
      problematic language.</p>
    <p>I always try to provide alternate language, when I can, but in
      spite of having offered suggestions for this document in the past,
      I can't for this set.</p>
    <p><br>
    </p>
    <p>
      <blockquote type="cite">
        <div class="content">
          <pre>Abstract

   DMARC (Domain-based Message Authentication, Reporting, and
   Conformance) is a scalable mechanism by which a mail-originating
   organization can express domain-level policies and preferences for
   message validation, disposition, and reporting, that a mail-receiving
   organization can use to improve mail handling.  The design of DMARC
   presumes that domain names represent either nodes in the tree below
   which registrations occur, or nodes where registrations have</pre>
        </div>
      </blockquote>
      DMARC does not have 'registrations'.</p>
    <p>Also the occur/occured contrast has no obvious meaning to me. 
      Really, I have no idea what's intended by it.<br>
    </p>
    <p><br>
      <blockquote type="cite">
        <div class="content">
          <pre>
   occurred; it does not permit a domain name to have both of these</pre>
        </div>
      </blockquote>
      "both" of what?  registration?</p>
    <p><br>
      <blockquote type="cite">
        <div class="content">
          <pre>   properties simultaneously.  Since its deployment in 2015, use of
   DMARC has shown a clear need for the ability to express policy for
   these domains as well.</pre>
        </div>
      </blockquote>
      Which domains?</p>
    <p><br>
      <blockquote type="cite">
        <div class="content">
          <pre>   Domains at which registrations can occur are referred to as Public
   Suffix Domains (PSDs).  This document describes an extension to DMARC
   to enable DMARC functionality for PSDs.</pre>
        </div>
      </blockquote>
      This is the definition of public suffix provided by the PSL folk:<br>
      <br>
      "A public suffix is a set of DNS names or wildcards concatenated
      with dots. It represents the part of a domain name which is <strong>not</strong>
      under the control of the individual registrant."</p>
    <p><br>
      <blockquote type="cite">
        <div class="content">
          <pre>   This document also seeks to address implementations that consider a
   domain on a public Suffix list to be ineligible for DMARC
   enforcement.</pre>
        </div>
      </blockquote>
      seeks?</p>
    <p>implementations don't 'consider' anything.  <br>
    </p>
    <p>is 'ineligibility' really the essential issue?</p>
    <p>d/<br>
    </p>
    <p><br>
    </p>
    <p>-- </p>
    <pre class="moz-signature" cols="72">Dave Crocker
<a class="moz-txt-link-abbreviated" href="mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------56A4D3C23C39B7803912D6FE--


From nobody Fri Jan 29 08:21:42 2021
Return-Path: <kurta@drkurt.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 93F063A1117 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 08:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.com
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 35WlIdwpNeSO for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 08:21:39 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A2FD3A1115 for <dmarc@ietf.org>; Fri, 29 Jan 2021 08:21:39 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id 16so9866055ioz.5 for <dmarc@ietf.org>; Fri, 29 Jan 2021 08:21:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MeJNXhYCo/v0LL7BQJ9ez9CqmVkaulCCcRJlDb8/kIg=; b=W/Xtc7e3AC0tHeeVKz+5MDVwfFzItDwSHY2eg0n4FfdUIN0AnUlCsNEBzYbZgKpLIJ Ei1D3vL0WZmrzFEU7qVtAQbW1128erH77YGtl19klInGrTDTiMiHj/2kCy5UpwDLwXyD +Sa6IeljDDuKbVQ3TiGBSat2Cfy/b11ZTdUT8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MeJNXhYCo/v0LL7BQJ9ez9CqmVkaulCCcRJlDb8/kIg=; b=CPW4wu8lA9sWjwcDInqUepSOUgEGSw02ZTSXUrNGQOLc/6nmZZrOA9XKjkdV2c3R0R id1drEyMUa+Y9rPNGyara4LwqnYHut9wYVpPjeiuLZivIzxN2PhDZKdaZesfbhNGalIs QteE2C83fXUo5mO/7fJyV6xkx1l5zrB9Sd5BjEfc4qmavipbhNicEvCHFdBkv4aaiRJQ dIk8IgrNUZOFmW3t+88xZ2On5U9W86ZnB2fX9xxcfwo81GFkMGIAs4ssZzXe1NFXarMx PA3HB7gKcNmqXZYN1r+++psTZSVfxlhPRvDQUgwA7qIkU3lPeCoOfnXACDIibDisZCXc R0FQ==
X-Gm-Message-State: AOAM530gqga5oW17EOXE2eSRCo83bGVHjLXpayLtwif/gMYSEW3Byv8W 36/rQ9dzoUfo2ksFV7TePLO8BHoKJyhJ7Ydz/1bTFA==
X-Google-Smtp-Source: ABdhPJzhpVbNC4t+78X3V8edoHvGyqr/qi+M0v+MOxE6FAsJd8u479hmQhIYAjUv+OcPvsDe0XZOUMAH59WqHoxNsOg=
X-Received: by 2002:a02:712e:: with SMTP id n46mr4285181jac.19.1611937298412;  Fri, 29 Jan 2021 08:21:38 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com> <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com> <CADyWQ+FejAGbv8TLrGXpV_Crgi1KErKK_1-6=2jzZh+QbguK6Q@mail.gmail.com> <CAL0qLwYrXEaOVphUjAB1guQO=s+ppabP1q4Ne16rqF=e6JsqLw@mail.gmail.com> <CADyWQ+Fx-jVGGgzf6-R6n1OzpwQR3akFJeVNqmq=XN_X=1B-Cg@mail.gmail.com>
In-Reply-To: <CADyWQ+Fx-jVGGgzf6-R6n1OzpwQR3akFJeVNqmq=XN_X=1B-Cg@mail.gmail.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Fri, 29 Jan 2021 08:21:19 -0800
Message-ID: <CABuGu1qj0Q5M9bbeUvxRb2ubSKZea+sPd-2Jv+8uYf2VaVfwhg@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>, Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="0000000000001291df05ba0c66e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/BlcKSpasvJfm91yGBhhmtlrQqyw>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 29 Jan 2021 16:21:41 -0000

--0000000000001291df05ba0c66e5
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 29, 2021 at 6:52 AM Tim Wicinski <tjw.ietf@gmail.com> wrote:

>
> I suggest adding it to this paragraph:
>
>    This document specifies experimental updates to the DMARC and PSL
>    algorithm cited above, in an attempt to mitigate this abuse.
>

update to DMARC = yes; update to PSL = no


> On Fri, Jan 29, 2021 at 1:44 AM Murray S. Kucherawy <superuser@gmail.com>
> wrote:
>
>> On Fri, Jan 22, 2021 at 5:01 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>
>>> Since this is an experiment, Appendix A discusses the updates that
>>> happen.  we don't actually say explicitly "if the experiment is a success,
>>> the following changes will be made" and perhaps I should add some wording
>>> like that.
>>>
>>
>> Something like this, perhaps?
>>
>> "A standards track update to [RFC7489] will take into account the results
>> of this experiment."
>>
>> ... somewhere in Section 1.
>>
>
A normative dependency from an experimental spec imposed upon a standards
track spec seems like a bad idea to me. At the very least it would impose a
timing constraint that DMARCbis could not be "completed" until after the
PSD experiment is "completed", analyzed and consensus achieved.

--Kurt

--0000000000001291df05ba0c66e5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 29, 2021 at 6:52 AM Tim Wicin=
ski &lt;<a href=3D"mailto:tjw.ietf@gmail.com">tjw.ietf@gmail.com</a>&gt; wr=
ote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div style=3D"font-family:monospace"><br><=
/div><div style=3D"font-family:monospace">I suggest adding it to this parag=
raph:</div><div style=3D"font-family:monospace"><br></div><div style=3D"fon=
t-family:monospace">=C2=A0 =C2=A0This document specifies experimental updat=
es to the DMARC and PSL<br>=C2=A0 =C2=A0algorithm cited above, in an attemp=
t to mitigate this abuse.</div></div></blockquote><div><br></div><div>updat=
e to DMARC =3D yes; update to PSL =3D no</div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Fri, Jan 29, 2021 at 1:44 AM Murray S. Kuc=
herawy &lt;<a href=3D"mailto:superuser@gmail.com" target=3D"_blank">superus=
er@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 5:01 =
PM Tim Wicinski &lt;<a href=3D"mailto:tjw.ietf@gmail.com" target=3D"_blank"=
>tjw.ietf@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Since this i=
s an experiment, Appendix A discusses the updates that happen.=C2=A0 we don=
&#39;t actually=C2=A0say explicitly=C2=A0&quot;if the experiment is a succe=
ss, the following changes will be made&quot; and perhaps I should add some =
wording like that. <br></div></blockquote><div><br></div><div>Something lik=
e this, perhaps?<br><br></div><div>&quot;A standards track update to [RFC74=
89] will take into account the results of this experiment.&quot;</div><div>=
<br></div><div>... somewhere in Section 1.</div></div></div></blockquote></=
div></blockquote><div><br></div><div>A normative dependency from an experim=
ental spec imposed upon a standards track spec seems like a bad idea to me.=
 At the very least it would impose a timing constraint that DMARCbis could =
not be &quot;completed&quot; until after the PSD experiment is &quot;comple=
ted&quot;, analyzed and consensus achieved.</div><div><br></div><div>--Kurt=
=C2=A0</div></div></div>

--0000000000001291df05ba0c66e5--


From nobody Fri Jan 29 10:12:05 2021
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 309113A11E5 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 10:12:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 uT19_d3CI5eU for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 10:12:01 -0800 (PST)
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 953283A11E4 for <dmarc@ietf.org>; Fri, 29 Jan 2021 10:12:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611943917; bh=hnX2H2b8+IWnsB11AS76E8wNpZuSgH7Dc+vQ2+k7Vzs=; l=12861; h=To:References:From:Date:In-Reply-To; b=Bf4zq6am3yFDoUTtrM3YQzYJKWaP5RgTR/fvX8iIj5zFs2ajq+XdoUT7UxJnzHhHg dFb0vhhJcJB66uRTw10CwIcuUIEwOhnr2yeD4yDPr/rqugUmBuFEe4YiWxJiRN4Wcu sBwe1sCKmReJQOLmoQ7uiLvpqCDX2JpD07jpG2gno0EUyAmBxGK2kUHrZr3Ws
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.0000000060144FED.00006DE4; Fri, 29 Jan 2021 19:11:57 +0100
To: "Kurt Andersen (b)" <kboth@drkurt.com>, Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com> <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com> <CADyWQ+FejAGbv8TLrGXpV_Crgi1KErKK_1-6=2jzZh+QbguK6Q@mail.gmail.com> <CAL0qLwYrXEaOVphUjAB1guQO=s+ppabP1q4Ne16rqF=e6JsqLw@mail.gmail.com> <CADyWQ+Fx-jVGGgzf6-R6n1OzpwQR3akFJeVNqmq=XN_X=1B-Cg@mail.gmail.com> <CABuGu1qj0Q5M9bbeUvxRb2ubSKZea+sPd-2Jv+8uYf2VaVfwhg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <f2fb34d7-a133-ad2d-aaab-444e162f6878@tana.it>
Date: Fri, 29 Jan 2021 19:11:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=_north-28132-1611943917-0001-2"
In-Reply-To: <CABuGu1qj0Q5M9bbeUvxRb2ubSKZea+sPd-2Jv+8uYf2VaVfwhg@mail.gmail.com>
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Gk-Q4wYBqDS4ud-1YqDhgGPgHgk>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 29 Jan 2021 18:12:04 -0000

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_north-28132-1611943917-0001-2
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

On Fri 29/Jan/2021 17:21:19 +0100 Kurt Andersen (b) wrote:
> On Fri, Jan 29, 2021 at 6:52 AM Tim Wicinski <tjw.ietf@gmail.com> wrote:
> 
>>
>> I suggest adding it to this paragraph:
>>
>>>    This document specifies experimental updates to the DMARC and PSL
>>>    algorithm cited above, in an attempt to mitigate this abuse.
>>
> 
> update to DMARC = yes; update to PSL = no


It is difficult to propose changes in OLD:/NEW: format.  I attach a patch.  It 
defers mentioning a PSL until Section 3.  That way it may address part of 
Dave's objections as well.


>> On Fri, Jan 29, 2021 at 1:44 AM Murray S. Kucherawy <superuser@gmail.com>
>> wrote:
>>
>>> On Fri, Jan 22, 2021 at 5:01 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>>
>>>> Since this is an experiment, Appendix A discusses the updates that
>>>> happen.  we don't actually say explicitly "if the experiment is a success,
>>>> the following changes will be made" and perhaps I should add some wording
>>>> like that.
>>>>
>>>
>>> Something like this, perhaps?
>>>
>>> "A standards track update to [RFC7489] will take into account the results
>>> of this experiment."
>>>
>>> ... somewhere in Section 1.
>>>
>>
> A normative dependency from an experimental spec imposed upon a standards
> track spec seems like a bad idea to me. At the very least it would impose a
> timing constraint that DMARCbis could not be "completed" until after the
> PSD experiment is "completed", analyzed and consensus achieved.


This could be weakened by saying "*may* take into account".  However, it's not 
needed, as the sentence doesn't say *the next* standards track update...


Best
Ale
-- 


--=_north-28132-1611943917-0001-2
Content-Type: text/plain; charset=utf-8; name="draft-ietf-psd.patch.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-psd.patch.txt"

LS0tIGRyYWZ0LWlldGYtZG1hcmMtcHNkLXRpbS54bWwJMjAyMS0wMS0yNCAxODo1MDoyOC4z
NTU4Mjk4MTcgKzAxMDAKKysrIGRyYWZ0LWlldGYtZG1hcmMtcHNkLWFsZS54bWwJMjAyMS0w
MS0yOSAxODo1ODozNS4zNDk0OTQ5NDYgKzAxMDAKQEAgLTQyLDE0ICs0MiwxNCBAQAogICAg
PGtleXdvcmQ+VExEPC9rZXl3b3JkPgogCiAgICA8YWJzdHJhY3Q+Ci0gICAgICA8dD5ETUFS
QyAoRG9tYWluLWJhc2VkIE1lc3NhZ2UgQXV0aGVudGljYXRpb24sIFJlcG9ydGluZywgYW5k
Ci0gICAgICAgICBDb25mb3JtYW5jZSkgaXMgYSBzY2FsYWJsZSBtZWNoYW5pc20gYnkgd2hp
Y2ggYSBtYWlsLW9yaWdpbmF0aW5nCisgICAgICA8dD5Eb21haW4tYmFzZWQgTWVzc2FnZSBB
dXRoZW50aWNhdGlvbiwgUmVwb3J0aW5nLCBhbmQKKyAgICAgICAgIENvbmZvcm1hbmNlIChE
TUFSQykgaXMgYSBzY2FsYWJsZSBtZWNoYW5pc20gYnkgd2hpY2ggYSBtYWlsLW9yaWdpbmF0
aW5nCiAgICAgICAgICBvcmdhbml6YXRpb24gY2FuIGV4cHJlc3MgZG9tYWluLWxldmVsIHBv
bGljaWVzIGFuZCBwcmVmZXJlbmNlcyBmb3IKICAgICAgICAgIG1lc3NhZ2UgdmFsaWRhdGlv
biwgZGlzcG9zaXRpb24sIGFuZCByZXBvcnRpbmcsIHRoYXQgYSBtYWlsLXJlY2VpdmluZwot
ICAgICAgICAgb3JnYW5pemF0aW9uIGNhbiB1c2UgdG8gaW1wcm92ZSBtYWlsIGhhbmRsaW5n
LiAgVGhlIGRlc2lnbiBvZiBETUFSQwotICAgICAgICAgcHJlc3VtZXMgdGhhdCBkb21haW4g
bmFtZXMgcmVwcmVzZW50IGVpdGhlciBub2RlcyBpbiB0aGUgdHJlZSBiZWxvdwotICAgICAg
ICAgd2hpY2ggcmVnaXN0cmF0aW9ucyBvY2N1ciwgb3Igbm9kZXMgd2hlcmUgcmVnaXN0cmF0
aW9ucyBoYXZlIG9jY3VycmVkOwotICAgICAgICAgaXQgZG9lcyBub3QgcGVybWl0IGEgZG9t
YWluIG5hbWUgdG8gaGF2ZSBib3RoIG9mIHRoZXNlIHByb3BlcnRpZXMKKyAgICAgICAgIG9y
Z2FuaXphdGlvbiBjYW4gdXNlIHRvIGltcHJvdmUgbWFpbCBoYW5kbGluZy48L3Q+CisgICAg
ICAgPHQ+SW50ZXJuZXQgZG9tYWluIG5hbWVzIGNhbiBiZSByZXByZXNlbnRlZCBieSBhIHRy
ZWUuICBUaGVyZSBhcmUgbm9kZXMgYmVsb3cKKyAgICAgICAgIHdoaWNoIHJlZ2lzdHJhdGlv
bnMgb2NjdXIsIGFuZCBub2RlcyB3aGVyZSByZWdpc3RyYXRpb25zIGhhdmUgb2NjdXJyZWQu
CisgICAgICAgICBETUFSQyBkb2VzIG5vdCBwZXJtaXQgYSBkb21haW4gbmFtZSB0byBoYXZl
IGJvdGggb2YgdGhlc2UgcHJvcGVydGllcwogICAgICAgICAgc2ltdWx0YW5lb3VzbHkuICBT
aW5jZSBpdHMgZGVwbG95bWVudCBpbiAyMDE1LCB1c2Ugb2YgRE1BUkMgaGFzIHNob3duCiAg
ICAgICAgICBhIGNsZWFyIG5lZWQgZm9yIHRoZSBhYmlsaXR5IHRvIGV4cHJlc3MgcG9saWN5
IGZvciB0aGVzZSBkb21haW5zIGFzCiAgICAgICAgICB3ZWxsLjwvdD4KQEAgLTU3LDcgKzU3
LDcgQEAKICAgICAgICAgIFN1ZmZpeCBEb21haW5zIChQU0RzKS4gIFRoaXMgZG9jdW1lbnQg
ZGVzY3JpYmVzIGFuIGV4dGVuc2lvbiB0byBETUFSQwogICAgICAgICAgdG8gZW5hYmxlIERN
QVJDIGZ1bmN0aW9uYWxpdHkgZm9yIFBTRHMuPC90PgogICAgICAgPHQ+VGhpcyBkb2N1bWVu
dCBhbHNvIHNlZWtzIHRvIGFkZHJlc3MgaW1wbGVtZW50YXRpb25zIHRoYXQgY29uc2lkZXIg
YQotICAgICAgICAgZG9tYWluIG9uIGEgcHVibGljIFN1ZmZpeCBsaXN0IHRvIGJlIGluZWxp
Z2libGUgZm9yIERNQVJDCisgICAgICAgICBQdWJsaWMgU3VmZml4IERvbWFpbiB0byBiZSBp
bmVsaWdpYmxlIGZvciBETUFSQwogICAgICAgICAgZW5mb3JjZW1lbnQuPC90PgogICAgPC9h
YnN0cmFjdD4KICA8L2Zyb250PgpAQCAtNjgsNDIgKzY4LDQ3IEBACiAgICAgICAgIG9yZ2Fu
aXphdGlvbmFsIHBvbGljeSBpbmZvcm1hdGlvbiB0byBlbWFpbCByZWNlaXZlcnMuICBETUFS
QyBhbGxvd3MgcG9saWN5IHRvIGJlCiAgICAgICAgIHNwZWNpZmllZCBmb3IgYm90aCBpbmRp
dmlkdWFsIGRvbWFpbnMgYW5kIGZvciBvcmdhbml6YXRpb25hbCBkb21haW5zCiAgICAgICAg
IGFuZCB0aGVpciBzdWItZG9tYWlucyB3aXRoaW4gYSBzaW5nbGUgb3JnYW5pemF0aW9uLjwv
dD4KLSAgICAgPHQ+VG8gZGV0ZXJtaW5lIHRoZSBvcmdhbml6YXRpb25hbCBkb21haW4gZm9y
IGEgbWVzc2FnZSB1bmRlciBldmFsdWF0aW9uLAotICAgICAgICBhbmQgdGh1cyB3aGVyZSB0
byBsb29rIGZvciBhIHBvbGljeSBzdGF0ZW1lbnQsIERNQVJDIG1ha2VzIHVzZSBvZiBhIFB1
YmxpYyBTdWZmaXgKLSAgICAgICAgTGlzdC4gVGhlIHByb2Nlc3MgZm9yIGRvaW5nIHRoaXMg
Y2FuIGJlIGZvdW5kIGluIFNlY3Rpb24gMy4yIG9mIHRoZSBETUFSQwotICAgICAgICBzcGVj
aWZpY2F0aW9uLjwvdD4KLSAgICAgPHQ+RE1BUkMgYXMgc3BlY2lmaWVkIHByZXN1bWVzIHRo
YXQgZG9tYWluIG5hbWVzIHByZXNlbnQgaW4gYSBQU0wgYXJlIG5vdAorICAgICA8dD5SZXBy
ZXNlbnRpbmcgSW50ZXJuZXQgZG9tYWluIG5hbWVzIGluIGEgdHJlZSwgUHVibGljIFN1ZmZp
eCBEb21haW5zIChQU0QpCisgICAgICAgIGFyZSB0aG9zZSByaWdodCBiZWxvdyBvciBuZWFy
IHRvIHRoZSB0b3Agb2YgdGhlIHRyZWUsIHdoaWNoIGlzIHRoZSByb290LgorICAgICAgICBE
TUFSQyBhbGxvd3MgT3JnYW5pemF0aW9uYWwgRG9tYWlucywgd2hpY2ggYXJlIHRob3NlIHJp
Z2h0IGJlbG93IGEgUFNELAorICAgICAgICB0byBwdWJsaXNoIGEgcG9saWN5LiAgU3ViZG9t
YWlucyBjYW4gcHVibGlzaCB0aGVpciBwb2xpY3kgdG9vLAorICAgICAgICBvdmVycmlkaW5n
IHRoZSBwb2xpY3kgb2YgdGhlaXIgT3JnYW5pemF0aW9uYWwgRG9tYWluLiAgSG93ZXZlciwK
KyAgICAgICAgUFNEIGN1cnJlbnRseSBjYW5ub3QuICBJbiBvdGhlciB3b3JkcywKKyAgICAg
ICAgRE1BUkMgYXMgc3BlY2lmaWVkIHByZXN1bWVzIHRoYXQgUFNEcyBhcmUgbm90CiAgICAg
ICAgIG9yZ2FuaXphdGlvbmFsIGRvbWFpbnMgYW5kIHRodXMgbm90IHN1YmplY3QgdG8gRE1B
UkMgcHJvY2Vzc2luZzsgZG9tYWlucwogICAgICAgICBhcmUgZWl0aGVyIG9yZ2FuaXphdGlv
bmFsIGRvbWFpbnMsIHN1Yi1kb21haW5zIG9mIG9yZ2FuaXphdGlvbmFsCi0gICAgICAgIGRv
bWFpbnMsIG9yIGxpc3RlZCBvbiBhIFBTTC4gIEZvciBkb21haW5zIGxpc3RlZCBpbiBhCi0g
ICAgICAgIFBTTCwgaS5lLiwgVExEcyBhbmQgZG9tYWlucyB0aGF0IGV4aXN0IGJldHdlZW4g
VExEcyBhbmQKKyAgICAgICAgZG9tYWlucywgb3IgUFNEcy4gIEZvciBhCisgICAgICAgIFBT
RCwgaS5lLiwgVExEcyBhbmQgZG9tYWlucyB0aGF0IGV4aXN0IGJldHdlZW4gVExEcyBhbmQK
ICAgICAgICAgb3JnYW5pemF0aW9uIGxldmVsIGRvbWFpbnMsIHBvbGljeSBjYW4gb25seSBi
ZSBwdWJsaXNoZWQgZm9yIHRoZQogICAgICAgICBleGFjdCBkb21haW4uICBObyBtZXRob2Qg
aXMgYXZhaWxhYmxlIGZvciB0aGVzZSBkb21haW5zIHRvIGV4cHJlc3MKICAgICAgICAgcG9s
aWN5IG9yIHJlY2VpdmUgZmVlZGJhY2sgcmVwb3J0aW5nIGZvciBzdWItZG9tYWlucy4gIFRo
aXMgbWlzc2luZwogICAgICAgICBtZXRob2QgYWxsb3dzIGZvciB0aGUgYWJ1c2Ugb2Ygbm9u
LWV4aXN0ZW50IG9yZ2FuaXphdGlvbmFsLWxldmVsCiAgICAgICAgIGRvbWFpbnMgYW5kIHBy
ZXZlbnRzIGlkZW50aWZpY2F0aW9uIG9mIGRvbWFpbiBhYnVzZSBpbiBlbWFpbC48L3Q+Ci0g
ICAgIDx0PlRoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIGV4cGVyaW1lbnRhbCB1cGRhdGVzIHRv
IHRoZSBETUFSQyBhbmQgUFNMCi0gICAgICAgIGFsZ29yaXRobSBjaXRlZCBhYm92ZSwgaW4g
YW4gYXR0ZW1wdCB0byBtaXRpZ2F0ZSB0aGlzIGFidXNlLjwvdD4KKyAgICAgPHQ+VGhpcyBk
b2N1bWVudCBzcGVjaWZpZXMgZXhwZXJpbWVudGFsIHVwZGF0ZXMgdG8gRE1BUkMgYW5kIHRv
IHRoZQorICAgICAgICBhbGdvcml0aG0gdG8gbG9jYXRlIE9yZ2FuaXphdGlvbmFsIERvbWFp
bnMsIGluIGFuIGF0dGVtcHQgdG8gbWl0aWdhdGUgdGhpcyBhYnVzZS4KKyAgICAgICAgQSBz
dGFuZGFyZHMgdHJhY2sgdXBkYXRlIHRvIDx4cmVmIHRhcmdldD0iUkZDNzQ4OSIvPiB3aWxs
IHRha2UKKyAgICAgICAgaW50byBhY2NvdW50IHRoZSByZXN1bHRzIG9mIHRoaXMgZXhwZXJp
bWVudC48L3Q+CiAgICA8c2VjdGlvbiBhbmNob3I9ImV4YW1wbGUiIHRpdGxlPSJFeGFtcGxl
Ij4KICAgICAgPHQ+QXMgYW4gZXhhbXBsZSwgaW1hZ2luZSBhIGNvdW50cnkgY29kZSBUTEQg
KGNjVExEKSB3aGljaCBoYXMgcHVibGljCiAgICAgICAgIHN1YmRvbWFpbnMgZm9yIGdvdmVy
bm1lbnQgYW5kIGNvbW1lcmNpYWwgdXNlICgiLmdvdi5leGFtcGxlIiBhbmQKLSAgICAgICAg
Ii5jb20uZXhhbXBsZSIpLiAgQSBQU0wgd2hvc2UgbWFpbnRhaW5lciBpcyBhd2FyZSBvZiB0
aGlzIGNvdW50cnkncwotICAgICAgICBkb21haW4gc3RydWN0dXJld291bGQgaW5jbHVkZSBl
bnRyaWVzIGZvciBib3RoIG9mIHRoZXNlIGluIHRoZSBQU0wsIGluZGljYXRpbmcgdGhhdCB0
aGV5IGFyZSBQU0RzIGJlbG93IHdoaWNoIHJlZ2lzdHJhdGlvbnMgY2FuIG9jY3VyLgorICAg
ICAgICAiLmNvbS5leGFtcGxlIikuCiAgICAgICAgIFN1cHBvc2UgZnVydGhlciB0aGF0IHRo
ZXJlIGV4aXN0cyBhIGRvbWFpbiAidGF4Lmdvdi5leGFtcGxlIiwKICAgICAgICAgcmVnaXN0
ZXJlZCB3aXRoaW4gIi5nb3YuZXhhbXBsZSIsIHRoYXQgaXMgcmVzcG9uc2libGUgZm9yIHRh
eGF0aW9uCiAgICAgICAgIGluIHRoaXMgaW1hZ2luZWQgY291bnRyeS48L3Q+Ci0gICAgIDx0
Pkhvd2V2ZXIsIGJ5IGV4cGxvaXRpbmcgdGhlIHR5cGljYWxseSB1bmF1dGhlbnRpY2F0ZWQg
bmF0dXJlCisgICAgIDx0PkJ5IGV4cGxvaXRpbmcgdGhlIHR5cGljYWxseSB1bmF1dGhlbnRp
Y2F0ZWQgbmF0dXJlCiAgICAgICAgb2YgZW1haWwsIHRoZXJlIGFyZSByZWd1bGFyIG1hbGlj
aW91cyBjYW1wYWlnbnMgdG8gaW1wZXJzb25hdGUgdGhpcwogICAgICAgIG9yZ2FuaXphdGlv
biB0aGF0IHVzZSBzaW1pbGFyLWxvb2tpbmcgKCJjb3VzaW4iKSBkb21haW5zIHN1Y2ggYXMK
ICAgICAgICAidDR4Lmdvdi5leGFtcGxlIi4gIFN1Y2ggZG9tYWlucyBhcmUgbm90IHJlZ2lz
dGVyZWQuPC90PgotICAgICA8dD5XaXRoaW4gdGhlICIuZ292LmV4YW1wbGUiIHB1YmxpYyBz
dWZmaXgsIHVzZSBvZiBETUFSQyBoYXMgYmVlbiBtYW5kYXRlZCwKLSAgICAgICAgc28gImdv
di5leGFtcGxlIiBwdWJsaXNoZXMgdGhlIGZvbGxvd2luZyBETUFSQyBETlMgcmVjb3JkOgor
ICAgICA8dD5UaGUgZG9tYWluICJnb3YuZXhhbXBsZSIgaXMgYSBQU0QsIGFsYmVpdCBwcmVz
dW1hYmx5IG9ubHkgcXVhbGlmaWVkCisgICAgICAgIG9yZ2FuaXphdGlvbnMgY2FuIHJlZ2lz
dGVyIGRvbWFpbnMgdW5kZXIgaXQuICBVc2Ugb2YgRE1BUkMgaGFzCisgICAgICAgIGJlZW4g
bWFuZGF0ZWQgZm9yIGRvbWFpbnMgcHVibGlzaGVkIHVuZGVyIGl0LgorICAgICAgICBzbyAi
dGF4Lmdvdi5leGFtcGxlIiBwdWJsaXNoZXMgdGhlIGZvbGxvd2luZyBETUFSQyBETlMgcmVj
b3JkOgogICAgICAgICAgPGZpZ3VyZT48YXJ0d29yaz4KIF9kbWFyYy5nb3YuZXhhbXBsZS4g
SU4gVFhUICggInY9RE1BUkMxOyBwPXJlamVjdDsgIgogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAicnVhPW1haWx0bzpkbWNAZG1hcmMuc3ZjLmdvdi5leGFtcGxlIiApCiAgICAg
ICAgIDwvYXJ0d29yaz48L2ZpZ3VyZT4KICAgICAgICAgIFRoaXMgRE1BUkMgcmVjb3JkIHBy
b3ZpZGVzIHBvbGljeSBhbmQgYSByZXBvcnRpbmcgZGVzdGluYXRpb24gZm9yCi0gICAgICAg
ICBtYWlsIHNlbnQgZnJvbSBAZ292LmV4YW1wbGUuIEhvd2V2ZXIsIGR1ZSB0byBETUFSQydz
IGN1cnJlbnQgbWV0aG9kCisgICAgICAgICBtYWlsIHNlbnQgZnJvbSBAdGF4Lmdvdi5leGFt
cGxlLiBIb3dldmVyLCBkdWUgdG8gRE1BUkMncyBjdXJyZW50IG1ldGhvZAogICAgICAgICAg
b2YgZGlzY292ZXJpbmcgYW5kIGFwcGx5aW5nIHBvbGljeSBhdCB0aGUgb3JnYW5pemF0aW9u
YWwgZG9tYWluCiAgICAgICAgICBsZXZlbCwgdGhlIG5vbi1leGlzdGVudCBvcmdhbml6YXRp
b25hbCBkb21haW4gb2YgQHQ0eC5nb3YuZXhhbXBsZQogICAgICAgICAgZG9lcyBub3QgYW5k
IGNhbm5vdCBmYWxsIHVuZGVyIGEgRE1BUkMgcG9saWN5LgpAQCAtMTExLDcgKzExNiw3IEBA
CiAgICAgIDx0PiBEZWZlbnNpdmVseSByZWdpc3RlcmluZyBhbGwgdmFyaWFudHMgb2YgInRh
eCIgaXMgb2J2aW91c2x5IG5vdCBhIHNjYWxhYmxlCiAgICAgICAgICBzdHJhdGVneS4gIFRo
ZSBpbnRlbnQgb2YgdGhpcyBzcGVjaWZpY2F0aW9uLCB0aGVyZWZvcmUsIGlzIHRvIGVuaGFu
Y2UgdGhlCiAgICAgICAgICBETUFSQyBhbGdvcml0aG0gYnkgZW5hYmxpbmcgYW4gYWdlbnQg
cmVjZWl2aW5nIHN1Y2ggYSBtZXNzYWdlIHRvIGJlIGFibGUgdG8KLSAgICAgICAgIGRldGVy
bWluZSB0aGF0IGEgcmVsZXZhbnQgcG9saWN5IGlzIHByZXNlbnQgYXQgImdvdi5leGFtcGxl
Iiwgd2hpY2ggaXMKKyAgICAgICAgIGRldGVybWluZSB3aGV0aGVyIGEgcmVsZXZhbnQgcG9s
aWN5IGlzIHByZXNlbnQgYXQgImdvdi5leGFtcGxlIiwgd2hpY2ggaXMKICAgICAgICAgIHBy
ZWNsdWRlZCBieSB0aGUgY3VycmVudCBETUFSQyBhbGdvcml0aG0uCiAgICAgIDwvdD4KICAg
IDwvc2VjdGlvbj4KQEAgLTE1Myw3ICsxNTgsNyBAQAogICAgICAgICAgICAgICAgICAgICAg
IGVmZmVjdGl2ZWx5IE9yZ2FuaXphdGlvbmFsIERvbWFpbnMgYXMgZGlzY3Vzc2VkIGluIDx4
cmVmCiAgICAgICAgICAgICAgICAgICAgICAgdGFyZ2V0PSJSRkM3NDg5Ij5ETUFSQzwveHJl
Zj4uICBUaGV5IGNvbnRyb2wgYWxsCiAgICAgICAgICAgICAgICAgICAgICAgc3ViZG9tYWlu
cyBvZiB0aGUgdHJlZS4gIFRoZXNlIGFyZSBlZmZlY3RpdmVseSBwcml2YXRlCi0gICAgICAg
ICAgICAgICAgICAgICAgZG9tYWlucywgYnV0IGxpc3RlZCBpbiB0aGUgUHVibGljIFN1ZmZp
eCBMaXN0LiAgVGhleSBhcmUKKyAgICAgICAgICAgICAgICAgICAgICBkb21haW5zLCBidXQg
Zm9ybWFsbHkgdGhleSBhcmUgUFNEcywgc28gdGhleSBhcmUKICAgICAgICAgICAgICAgICAg
ICAgICB0cmVhdGVkIGFzIFB1YmxpYyBmb3IgRE1BUkMKICAgICAgICAgICAgICAgICAgICAg
ICBwdXJwb3Nlcy4gIFRoZXkgcmVxdWlyZSB0aGUgc2FtZSBwcm90ZWN0aW9ucyBhcyBETUFS
QwogICAgICAgICAgICAgICAgICAgICAgIE9yZ2FuaXphdGlvbmFsIERvbWFpbnMsIGJ1dCBh
cmUgY3VycmVudGx5IHVuYWJsZSB0bwpAQCAtMjQ1LDYgKzI1MCwxMSBAQAogCiAgICA8c2Vj
dGlvbiB0aXRsZT0iUFNEIERNQVJDIFVwZGF0ZXMgdG8gRE1BUkMgUmVxdWlyZW1lbnRzIj4K
IAorICAgICA8dD5UaGUgYWxnb3JpdGhtIERNQVJDIHVzZXMgdG8gZmluZCB0aGUgT3JnYW5p
emF0aW9uYWwgRG9tYWluIG9mIGEKKyAgICAgICAgZ2l2ZW4gZG9tYWluIGhpbmdlcyBvbiBh
IFB1YmxpYyBTdWZmaXggTGlzdCAoUFNMKSwgd2hpY2ggaXMgYSBsaXN0CisgICAgICAgIG9m
IFBTRHMsIHBvc3NpYmx5IG1ha2luZyB1c2Ugb2Ygd2lsZGNhcmRzLiAgVGhlIHByb2Nlc3Mg
aXMgZGVzY3JpYmVkCisgICAgICAgIGluIFNlY3Rpb24gMy4yIG9mIHRoZSBETUFSQyBzcGVj
aWZpY2F0aW9uLjwvdD4KKwogICAgICA8dD5UaGlzIGRvY3VtZW50IHVwZGF0ZXMgRE1BUkMg
YXMgZm9sbG93czo8L3Q+CiAKICAgICAgPHNlY3Rpb24gdGl0bGU9IkdlbmVyYWwgVXBkYXRl
cyI+Cg==
--=_north-28132-1611943917-0001-2--


From nobody Fri Jan 29 10:14:47 2021
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 CB7E93A11E9 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 10:14:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 abuef0kAh4x9 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 10:14:44 -0800 (PST)
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 683DE3A11E6 for <dmarc@ietf.org>; Fri, 29 Jan 2021 10:14:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611944082; bh=1Hdm0nQdmZgHKXpKIRj1O+RZf4maaQf8uPiMoBR52Qg=; l=183; h=From:To:References:Date:In-Reply-To; b=Av7Txb5++YESawmR3SDL25RAy0XNvbjX4PF2TTPTZly7SUUnlCBnge99iEXSIKbSX dnmNR63ZzohYliThFDQOFIMDcFf1jcXowy2MZLarYnd876/Cl9oWCF/CDE3utHlDcr QsF44Nx8l+vH8bodS+rWHK4yFko6HV/Q5KEZeaW+5A/SIMBePKomIL4bFHlWR
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.0000000060145092.00006E4F; Fri, 29 Jan 2021 19:14:42 +0100
From: Alessandro Vesely <vesely@tana.it>
To: "Kurt Andersen (b)" <kboth@drkurt.com>, Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com> <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com> <CADyWQ+FejAGbv8TLrGXpV_Crgi1KErKK_1-6=2jzZh+QbguK6Q@mail.gmail.com> <CAL0qLwYrXEaOVphUjAB1guQO=s+ppabP1q4Ne16rqF=e6JsqLw@mail.gmail.com> <CADyWQ+Fx-jVGGgzf6-R6n1OzpwQR3akFJeVNqmq=XN_X=1B-Cg@mail.gmail.com> <CABuGu1qj0Q5M9bbeUvxRb2ubSKZea+sPd-2Jv+8uYf2VaVfwhg@mail.gmail.com> <f2fb34d7-a133-ad2d-aaab-444e162f6878@tana.it>
Message-ID: <2c31c741-9e64-b91b-6840-aecc357ab040@tana.it>
Date: Fri, 29 Jan 2021 19:14:41 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f2fb34d7-a133-ad2d-aaab-444e162f6878@tana.it>
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/TcLSIOhEctv84YC7QQ2OkhF0dj4>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 29 Jan 2021 18:14:46 -0000

On Fri 29/Jan/2021 19:11:56 +0100 I wrote:
> 
> I attach a patch.


P.S.  It also changed the example slightly.  It sounds wrong as is now.  Pls 
look at that...


Best
Ale
-- 


















From nobody Fri Jan 29 12:03:49 2021
Return-Path: <superuser@gmail.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 050823A1258 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 12:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qv9_g-ongGcr for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 12:03:46 -0800 (PST)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3201C3A129C for <dmarc@ietf.org>; Fri, 29 Jan 2021 12:03:27 -0800 (PST)
Received: by mail-ua1-x931.google.com with SMTP id k47so3592485uad.1 for <dmarc@ietf.org>; Fri, 29 Jan 2021 12:03:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Kp58T9K2hsEmuYanVCAEavzOwkEwKATZoNrNz1iW2Pk=; b=E2abmkDC2FgxUTyUcQ17z3Aa4AMaPJyTWvJLJGuHSLGoO5S5NhC6YWmIKF9XbZSIx4 wd0p6qgbDtBitKUSbCgGnqNZylDlA4ZOU8GOb8cTVGNM7Gc41vvEvEahabtGQkmClL7Q EJajW87tZJwHLn97V/oN90WandNhr583sd686yaG3zFPbHwYaKuno0NgG605kDpegCE5 RrCPblk983xm8oPJheD2g8p2Bp3gasGuSRkjZdYg3+d7DUWp1XQONQ8BwsdnNDOhiS+w lm/UMQz9iaLdtkEEkS/joRLLz/kpCN9FWuRKFDn6+/NtpvKi/y/iMn4z16SyioHo4IUJ H5bQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Kp58T9K2hsEmuYanVCAEavzOwkEwKATZoNrNz1iW2Pk=; b=PFiheref46DJWCc9cc7i4F0WxHycPGaIvPrwYHDdCZPaIh+h14PkXz4CwJRh95t1yd UWjtC+DYY+O0DYuoipuudGIKuCnyTzJyXcEIeiqirKCuWHkf14Fy2D+8voapS4YIGTdS VkYelzJBoKzTh/ZzaOcVd2xEqrmN/iLlkXDQETQKuoBgf/m+i7TeCS8F9XG7Jy5pSQOf PQIaGgJes4iWolTJttbWGF86l+JsokBbzMtEzUWZOOumKBikRorJVrKNujM4WUXgv0QW C78oDevauHQ98YSVe88UrrAI5M9iLpWWGOYHJA1OKe6+Xjku3gmuY2wnHfiDvSD60mxn /AHA==
X-Gm-Message-State: AOAM530MiHKd1uEoHotHJsIw4g5ERaAxX5JR9TKyTGhuj1kHsFcHGKdS Nzgyps7FI6gIFvLGhN8ArqFXU0YtGhv6DswHqcU=
X-Google-Smtp-Source: ABdhPJzZvSMWQAqBS2WpUC4AAz5XL9RRTEcXlGyedJI053WdfkRwSYDgqC4AfXbvZB3/2lnwZ1TGv5cQAGwObtRbOQY=
X-Received: by 2002:ab0:2a1a:: with SMTP id o26mr4030765uar.101.1611950605961;  Fri, 29 Jan 2021 12:03:25 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+Fb93SkiAnL4cuCfxC5Wi1ERLeKhguWqAp3j8YEa6JBSA@mail.gmail.com> <87ima4wu3s.fsf@hobgoblin.ariadne.com> <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> <44eec884-a3c7-f0e3-4545-1032369ad3fd@tana.it> <CAL0qLwavpE9r6+O+Dm5EyDYzP9_pTpTbbjMzL1mPTyJky5CKmA@mail.gmail.com> <CADyWQ+Hn5G_WSHjrD3gLL5HwZxDGoV_wxgAuiPc_sutQ4OYhNg@mail.gmail.com> <CABuGu1oxkNUB_E8Q5do5xCruxXGvqY2461u0ZMZ1J5BFE8dTqg@mail.gmail.com> <CAL0qLwb9RUBTTfwNNLn+do1iNE-A1Ke-NcW+SidqhJqd3BdPig@mail.gmail.com> <CABuGu1qLPkVQFDxUKXsgzqoK4Qcd7Rn5Q4bOed_4WkVv-FuB7w@mail.gmail.com> <CADyWQ+FejAGbv8TLrGXpV_Crgi1KErKK_1-6=2jzZh+QbguK6Q@mail.gmail.com> <CAL0qLwYrXEaOVphUjAB1guQO=s+ppabP1q4Ne16rqF=e6JsqLw@mail.gmail.com> <CADyWQ+Fx-jVGGgzf6-R6n1OzpwQR3akFJeVNqmq=XN_X=1B-Cg@mail.gmail.com> <CABuGu1qj0Q5M9bbeUvxRb2ubSKZea+sPd-2Jv+8uYf2VaVfwhg@mail.gmail.com>
In-Reply-To: <CABuGu1qj0Q5M9bbeUvxRb2ubSKZea+sPd-2Jv+8uYf2VaVfwhg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 29 Jan 2021 12:03:14 -0800
Message-ID: <CAL0qLwZwf+9sK_+cyaYd4eDuv9OpU9tJ+vBJjLs7oorf3yQOFQ@mail.gmail.com>
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,  Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="000000000000438baf05ba0f7f13"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qRW3h2JLrmFeLP6Sdl_mfOQO5dM>
Subject: Re: [dmarc-ietf] [Gen-art] [Last-Call] Genart last call review of draft-ietf-dmarc-psd-08
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: Fri, 29 Jan 2021 20:03:48 -0000

--000000000000438baf05ba0f7f13
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 29, 2021 at 8:21 AM Kurt Andersen (b) <kboth@drkurt.com> wrote:

> On Fri, Jan 29, 2021 at 6:52 AM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>
>>
>> I suggest adding it to this paragraph:
>>
>>    This document specifies experimental updates to the DMARC and PSL
>>    algorithm cited above, in an attempt to mitigate this abuse.
>>
>
> update to DMARC = yes; update to PSL = no
>

Why?


>
>> On Fri, Jan 29, 2021 at 1:44 AM Murray S. Kucherawy <superuser@gmail.com>
>> wrote:
>>
>>> On Fri, Jan 22, 2021 at 5:01 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>>
>>>> Since this is an experiment, Appendix A discusses the updates that
>>>> happen.  we don't actually say explicitly "if the experiment is a success,
>>>> the following changes will be made" and perhaps I should add some wording
>>>> like that.
>>>>
>>>
>>> Something like this, perhaps?
>>>
>>> "A standards track update to [RFC7489] will take into account the
>>> results of this experiment."
>>>
>>> ... somewhere in Section 1.
>>>
>>
> A normative dependency from an experimental spec imposed upon a standards
> track spec seems like a bad idea to me. At the very least it would impose a
> timing constraint that DMARCbis could not be "completed" until after the
> PSD experiment is "completed", analyzed and consensus achieved.
>

I thought that was exactly the intent here.

-MSK

--000000000000438baf05ba0f7f13
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 29, 2021 at 8:21 AM Kurt Ande=
rsen (b) &lt;<a href=3D"mailto:kboth@drkurt.com">kboth@drkurt.com</a>&gt; w=
rote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 29, 2021 at =
6:52 AM Tim Wicinski &lt;<a href=3D"mailto:tjw.ietf@gmail.com" target=3D"_b=
lank">tjw.ietf@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div st=
yle=3D"font-family:monospace"><br></div><div style=3D"font-family:monospace=
">I suggest adding it to this paragraph:</div><div style=3D"font-family:mon=
ospace"><br></div><div style=3D"font-family:monospace">=C2=A0 =C2=A0This do=
cument specifies experimental updates to the DMARC and PSL<br>=C2=A0 =C2=A0=
algorithm cited above, in an attempt to mitigate this abuse.</div></div></b=
lockquote><div><br></div><div>update to DMARC =3D yes; update to PSL =3D no=
</div></div></div></blockquote><div><br></div><div>Why?</div><div> <br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div c=
lass=3D"gmail_quote"><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Fri, Jan 29, 2021 at 1:44 AM Murray S. Kucherawy &lt;<a href=3D"mailt=
o:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
"><div dir=3D"ltr">On Fri, Jan 22, 2021 at 5:01 PM Tim Wicinski &lt;<a href=
=3D"mailto:tjw.ietf@gmail.com" target=3D"_blank">tjw.ietf@gmail.com</a>&gt;=
 wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr">Since this is an experiment, Appendix A=
 discusses the updates that happen.=C2=A0 we don&#39;t actually=C2=A0say ex=
plicitly=C2=A0&quot;if the experiment is a success, the following changes w=
ill be made&quot; and perhaps I should add some wording like that. <br></di=
v></blockquote><div><br></div><div>Something like this, perhaps?<br><br></d=
iv><div>&quot;A standards track update to [RFC7489] will take into account =
the results of this experiment.&quot;</div><div><br></div><div>... somewher=
e in Section 1.</div></div></div></blockquote></div></blockquote><div><br><=
/div><div>A normative dependency from an experimental spec imposed upon a s=
tandards track spec seems like a bad idea to me. At the very least it would=
 impose a timing constraint that DMARCbis could not be &quot;completed&quot=
; until after the PSD experiment is &quot;completed&quot;, analyzed and con=
sensus achieved.</div></div></div></blockquote><div><br></div><div>I though=
t that was exactly the intent here.</div><div><br></div><div>-MSK<br></div>=
</div></div>

--000000000000438baf05ba0f7f13--


From nobody Fri Jan 29 12:15:17 2021
Return-Path: <superuser@gmail.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 C3F423A12A0 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 12:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yu7hKXOZ6oB3 for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 12:15:14 -0800 (PST)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B0D13A129F for <dmarc@ietf.org>; Fri, 29 Jan 2021 12:15:14 -0800 (PST)
Received: by mail-vs1-xe31.google.com with SMTP id h11so5516218vsa.10 for <dmarc@ietf.org>; Fri, 29 Jan 2021 12:15:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EeThsgWYvE5P8nwuFUBEC/q82iGUrW4r3rbT6+zfDC0=; b=Ig57c/2SxiPbN1ow6JbrLuyHeL8r1NgmddQFKk9cgQNrg9IpLB0tCq65pqgNtzOYGw vlSEvOCM9zQNbQx2V8+k/QStxn/C5zBdbEBIebbfOzg1dcKPdP+6kueROWqszw7jTZEp s361fDUX5Vh9mcd7SdnggM5k5pv2mcXPDqaZEQ+0TrnE3LVQTrZeYFUewjEcMoAbGWhf PfOFTvC+dIIiZ23nolyVKdDB/PWEuUydWp4PrPeQJeKo3AbH5QmCLCS6hHGrgFn6GRBE 2zJ7eipsHvPNVxZRMVHCvz9mUJA0FzR0MinTxI5XtGyG47RnlFDqQ8tXUNKq1W4fZaL5 v+oA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EeThsgWYvE5P8nwuFUBEC/q82iGUrW4r3rbT6+zfDC0=; b=qhfiy1zOQtnwIekuFtXLWJuc5Xv+S+NwT0r4LfY3UrhDM0Lx0WIPseoQNeEdgiGnOC cEgy7udr5kOAHMYLNUyEbhl7muzjGANMVTQ0BM8PuMllF6S4MfhLgDb09utgLb+dwj09 LtP6GPnaQ9BPwAzCuWV5w0l/l/mMaqNSLN3IEGptvS+IpQwiK5pLDNUsZ190hGq2eimG GdFTg1o0/0ZDDzDnea68iVOBKMTsgBOj2ds5dx7PqjoIbWFgwTDDP/Cl29+0Liu0KFEB jPqnp9eXwE+Adahtd3YJCFrqnF6ZlO5w7HPw0qVdhvqn+hOOrAvufdwp5Nxsf2rwR8E9 OuvA==
X-Gm-Message-State: AOAM5311W5yWUqT3Daguy30c1hf7hLO8nCmEFzmjG4Jkr96ETUr81+wy oz6FXF5kHj35qpk8nNdYJ5TH43Enku6XOXuOgBbqRjqqrP4=
X-Google-Smtp-Source: ABdhPJzeZHPeMJfv4rYx3fOWsink/AteEvHlkPSoaA7ddQxdqDz/6ySGzAKrIhcW6luPS9bAnsj7783Wo8eILQv2FaA=
X-Received: by 2002:a67:2bc2:: with SMTP id r185mr4299474vsr.15.1611951313210;  Fri, 29 Jan 2021 12:15:13 -0800 (PST)
MIME-Version: 1.0
References: <161144436332.13490.10651420808048876097@ietfa.amsl.com> <CADyWQ+EhD0nz71dLtUFwb9V_6uuen-k6E5fpvrCg3ZYzfr2JSw@mail.gmail.com> <ba38a9e4-7f43-c747-2d90-f35de22a8399@gmail.com>
In-Reply-To: <ba38a9e4-7f43-c747-2d90-f35de22a8399@gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 29 Jan 2021 12:15:02 -0800
Message-ID: <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006b51d305ba0fa9a5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PLRvmJGE6Re2b2hHMsZ0A7KgS1s>
Subject: Re: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-10.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: Fri, 29 Jan 2021 20:15:16 -0000

--0000000000006b51d305ba0fa9a5
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 29, 2021 at 7:51 AM Dave Crocker <dcrocker@gmail.com> wrote:

>
> Abstract
>
>    DMARC (Domain-based Message Authentication, Reporting, and
>    Conformance) is a scalable mechanism by which a mail-originating
>    organization can express domain-level policies and preferences for
>    message validation, disposition, and reporting, that a mail-receiving
>    organization can use to improve mail handling.  The design of DMARC
>    presumes that domain names represent either nodes in the tree below
>    which registrations occur, or nodes where registrations have
>
> DMARC does not have 'registrations'.
>

It's referring to domain name registrations, not DMARC registrations.

Also the occur/occured contrast has no obvious meaning to me.  Really, I
> have no idea what's intended by it.
>
"exist"?
"take place"?
"are made"?
"are done"?

>
>    occurred; it does not permit a domain name to have both of these
>
> "both" of what?  registration?
>

It's describing properties of nodes in the domain name tree.  DMARC's
current design stipulates that every node is either (a) a node below which
registrations can occur, or (b) a node at which a registration has
occurred.  An example of the former is "org", and an example of the latter
is "ietf.org" and its entire subtree.

   properties simultaneously.  Since its deployment in 2015, use of
>    DMARC has shown a clear need for the ability to express policy for
>    these domains as well.
>
> Which domains?
>

The intent is to augment DMARC's ability to describe the domain name tree
such that a node can be both (a) and (b) at the same time, for the purposes
of policy expression.  So those are the nodes (domains) of interest.


>    Domains at which registrations can occur are referred to as Public
>    Suffix Domains (PSDs).  This document describes an extension to DMARC
>    to enable DMARC functionality for PSDs.
>
> This is the definition of public suffix provided by the PSL folk:
>
> "A public suffix is a set of DNS names or wildcards concatenated with
> dots. It represents the part of a domain name which is *not* under the
> control of the individual registrant."
>

That seems to say the same thing to me, though perhaps more crisply.

>
>    This document also seeks to address implementations that consider a
>    domain on a public Suffix list to be ineligible for DMARC
>    enforcement.
>
> seeks?
> [...]
>

Hmm.  Maybe that sentence can be struck entirely.  Is this a problem with
certain implementations only, or with DMARC as specified in 7489?  If the
latter, I think we can drop this because the main paragraph already says
this.

-MSK

--0000000000006b51d305ba0fa9a5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 29, 2021 at 7:51 AM Dave Croc=
ker &lt;<a href=3D"mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>&gt; wr=
ote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">
 =20
   =20
 =20
  <div><br><p>
      </p><blockquote type=3D"cite">
        <div>
          <pre>Abstract

   DMARC (Domain-based Message Authentication, Reporting, and
   Conformance) is a scalable mechanism by which a mail-originating
   organization can express domain-level policies and preferences for
   message validation, disposition, and reporting, that a mail-receiving
   organization can use to improve mail handling.  The design of DMARC
   presumes that domain names represent either nodes in the tree below
   which registrations occur, or nodes where registrations have</pre>
        </div>
      </blockquote>
      DMARC does not have &#39;registrations&#39;.</div></blockquote><div><=
br></div><div>It&#39;s referring to domain name registrations, not DMARC re=
gistrations.</div><div> <br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div>
    <p>Also the occur/occured contrast has no obvious meaning to me.=C2=A0
      Really, I have no idea what&#39;s intended by it.<br></p></div></bloc=
kquote><div>&quot;exist&quot;?</div><div>&quot;take place&quot;?</div><div>=
&quot;are made&quot;?</div><div>&quot;are done&quot;?<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div><p>
    </p>
    <p><br>
      </p><blockquote type=3D"cite">
        <div>
          <pre>   occurred; it does not permit a domain name to have both o=
f these</pre>
        </div>
      </blockquote>
      &quot;both&quot; of what?=C2=A0 registration?</div></blockquote><div>=
<br></div>It&#39;s describing properties of nodes in the domain name tree.=
=C2=A0 DMARC&#39;s current design stipulates that every node is either (a) =
a node below which registrations can occur, or (b) a node at which a regist=
ration has occurred.=C2=A0 An example of the former is &quot;org&quot;, and=
 an example of the latter is &quot;<a href=3D"http://ietf.org">ietf.org</a>=
&quot; and its entire subtree.</div><div class=3D"gmail_quote"><br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div><blockquote type=3D"cite">
        <div>
          <pre>   properties simultaneously.  Since its deployment in 2015,=
 use of
   DMARC has shown a clear need for the ability to express policy for
   these domains as well.</pre>
        </div>
      </blockquote>
      Which domains?</div></blockquote><div><br></div><div>The intent is to=
 augment DMARC&#39;s ability to describe the domain name tree such that a n=
ode can be both (a) and (b) at the same time, for the purposes of policy ex=
pression.=C2=A0 So those are the nodes (domains) of interest.<br></div><div=
><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
    <p><br>
      </p><blockquote type=3D"cite">
        <div>
          <pre>   Domains at which registrations can occur are referred to =
as Public
   Suffix Domains (PSDs).  This document describes an extension to DMARC
   to enable DMARC functionality for PSDs.</pre>
        </div>
      </blockquote>
      This is the definition of public suffix provided by the PSL folk:<br>
      <br>
      &quot;A public suffix is a set of DNS names or wildcards concatenated
      with dots. It represents the part of a domain name which is <b>not</b=
>
      under the control of the individual registrant.&quot;</div></blockquo=
te><div><br></div><div>That seems to say the same thing to me, though perha=
ps more crisply.<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><div>
    <p><br>
      </p><blockquote type=3D"cite">
        <div>
          <pre>   This document also seeks to address implementations that =
consider a
   domain on a public Suffix list to be ineligible for DMARC
   enforcement.</pre>
        </div>
      </blockquote>
      seeks?<br>[...]<br></div></blockquote><div><br></div>Hmm.=C2=A0 Maybe=
 that sentence can be struck entirely.=C2=A0 Is this a problem with certain=
 implementations only, or with DMARC as specified in 7489?=C2=A0 If the lat=
ter, I think we can drop this because the main paragraph already says this.=
</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">-MSK<=
br></div></div>

--0000000000006b51d305ba0fa9a5--


From nobody Fri Jan 29 12:31:04 2021
Return-Path: <superuser@gmail.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 4B0AD3A12AF for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 12:31:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 RIYNCs8ekUwk for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 12:31:02 -0800 (PST)
Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDB0C3A12AE for <dmarc@ietf.org>; Fri, 29 Jan 2021 12:31:01 -0800 (PST)
Received: by mail-ua1-x92c.google.com with SMTP id g13so3611413uaw.5 for <dmarc@ietf.org>; Fri, 29 Jan 2021 12:31:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eSEqgLZzjI+fpe/nhn+9SNtFTtNPDoGK99x9ykrkkyU=; b=dQmxmCt5deac59lNFxBfQO/cVRK1SnDQdu2mOyJBxOUT6yO1n1AWGgRnkLoedEWCzk u4o2jVqG2NPQ3lwLapdo2SyjHthaUphFj+BEfY3uUZ8bJ2hQL5FFBA+A/pMLQXT5DYLD /x6GNd3sDNyGG7z4Fjk+fDkyhWU3VUfHREEIXjqJFaEkPChGi/Ugd0ZlVrKLNUuS8Fxg EWWUs+EeaFwwJCy2VJUrFxyAfAPdwxB/JzUhRROf8BcLlK1F0uac555D7EpJAi2tl9vN p92WMkXbeUru9HE8oIW+GIp9qshxRCeupzRqKt6Vw+EKKMxUnB/J15FqM5DzuBJ3eE9B 4hwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eSEqgLZzjI+fpe/nhn+9SNtFTtNPDoGK99x9ykrkkyU=; b=QX+PX/rWS0vSxm2pjuRY9F+aAdcw6/cF79WnTp3CuhN5PAdlAlyfXZjPFKNDd/tA40 vdJ4AErNZnrApzVj2VTy/XN7fkD9z1TzJdQvn0LPdbugXUHjBdvJoCHZdAlBgcSEGVIf IP4mN4nBkOyaKuSvD0kPlNFQlGkVWM4q0ahC1PGMwDJGKPowC2ArkLO3XBQx0ACsX2lC fQ4IbgIzEUxF+eqWOkcobu3f6Uj7uYUsCncT0NMjfJ/N5RbLZWRe1yQHpghp3z4Mwcpv NU2crq4kEYevn0kaH5pwEK4Kv0xZKutQT8MWPtCnqd0meCKFjuhBMKhh8SJn1RH1xiLk zSyQ==
X-Gm-Message-State: AOAM531xMYeqYNMavrHgCwsBthGbZjvDGaPf2FFQzTcepQl+o4p8atDq RV685Y3v9/117yYSUqaMl+2P2hLj4UFwz3CCNkvHiKhSGsY=
X-Google-Smtp-Source: ABdhPJzQeYWOYyXtAyGASRXnUOCLqIV8LQbRHaDu3n8U/kD8jZi0RvHRVDL6DKNWflTVbR6iNHf5veV/sLxuvP00XRk=
X-Received: by 2002:a9f:2628:: with SMTP id 37mr3902932uag.87.1611952260802; Fri, 29 Jan 2021 12:31:00 -0800 (PST)
MIME-Version: 1.0
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com> <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it> <CAL0qLwbYxTXXXpx11L3f1CqBns=fSRho3C+S7q=-DmiPSvxKvg@mail.gmail.com> <cf51d6d4-0c7b-971d-bcac-743370f16433@tana.it>
In-Reply-To: <cf51d6d4-0c7b-971d-bcac-743370f16433@tana.it>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 29 Jan 2021 12:30:49 -0800
Message-ID: <CAL0qLwYK7SFfV5fOb7qhy5hVgR15z4HEJbAHv38OFMAfC=_j-Q@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e66d5e05ba0fe140"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/6u-cV8iFavjRMN_7OlSbpibS4do>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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: Fri, 29 Jan 2021 20:31:03 -0000

--000000000000e66d5e05ba0fe140
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 29, 2021 at 3:02 AM Alessandro Vesely <vesely@tana.it> wrote:

> I just run a quick test on my current folder.  Out of 3879 messages I
> extracted
> 944 unique helo names.  721 of these matched the reverse lookup exactly.
> Out
> of the 223 remaining, 127 had an SPF pass for the helo identity anyway.
> So in
> 96 cases, roughly 10%, the helo name was indeed junk.  Isn't the remaining
> ~90%
> something worth considering?
>

I am admittedly quite heavily biased against using the HELO/EHLO value for
anything.  I have simply never found value in it, probably because at the
SMTP layer it's simply a value that gets logged or used in cute ways in the
human-readable portion of SMTP.  I seem to recall (but cannot seem to find
at the moment) RFC 5321 saying you can't reject HELO/EHLO based on a bogus
value, so it's even explicitly not useful to me.

Even if it's not junk, there's pretty much always something else on which
to hang a pass/fail decision about the apparent authenticity of a message
that at least feels safer if not actually being more sound.  Or put another
way, if you present to me a DKIM-signed message with a MAIL FROM value and
the only thing that passes is an SPF check against HELO, I'm mighty
skeptical.

Anyway, I'll let consensus fall where it may.

-MSK

--000000000000e66d5e05ba0fe140
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 29, 2021 at 3:02 AM Alessandr=
o Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; wrote=
:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">I just run a quick test on my current folder.=C2=A0 Out of 387=
9 messages I extracted <br>
944 unique helo names.=C2=A0 721 of these matched the reverse lookup exactl=
y.=C2=A0 Out <br>
of the 223 remaining, 127 had an SPF pass for the helo identity anyway.=C2=
=A0 So in <br>
96 cases, roughly 10%, the helo name was indeed junk.=C2=A0 Isn&#39;t the r=
emaining ~90% <br>
something worth considering?<br></blockquote><div><br></div><div>I am admit=
tedly quite heavily biased against using the HELO/EHLO value for anything.=
=C2=A0 I have simply never found value in it, probably because at the SMTP =
layer it&#39;s simply a value that gets logged or used in cute ways in the =
human-readable portion of SMTP.=C2=A0 I seem to recall (but cannot seem to =
find at the moment) RFC 5321 saying you can&#39;t reject HELO/EHLO based on=
 a bogus value, so it&#39;s even explicitly not useful to me.<br></div><div=
><br></div><div>Even if it&#39;s not junk, there&#39;s pretty much always s=
omething else on which to hang a pass/fail decision about the apparent auth=
enticity of a message that at least feels safer if not actually being more =
sound.=C2=A0 Or put another way, if you present to me a DKIM-signed message=
 with a MAIL FROM value and the only thing that passes is an SPF check agai=
nst HELO, I&#39;m mighty skeptical.</div><div><br></div><div>Anyway, I&#39;=
ll let consensus fall where it may.</div><div><br></div><div>-MSK=C2=A0 <br=
></div></div></div>

--000000000000e66d5e05ba0fe140--


From nobody Fri Jan 29 12:56:16 2021
Return-Path: <dcrocker@gmail.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 7ECAC3A12DB for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 12:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 8gRhZXzdmt9D for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 12:56:12 -0800 (PST)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABE233A12D9 for <dmarc@ietf.org>; Fri, 29 Jan 2021 12:56:12 -0800 (PST)
Received: by mail-oi1-x231.google.com with SMTP id j25so11402365oii.0 for <dmarc@ietf.org>; Fri, 29 Jan 2021 12:56:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=GExAg8smGhBmD/xc/IvC+P9DdhHcMjmwU8stKvZndNo=; b=V1Sx5XaDpsJoBOSHjM4ZEHFSSGp/ZL4PZP3z0eWMO84RaO3kQjTTx7mBccZPUqqQy6 HDcG28M2cQds7L0AjXpfjr9y/MUWXMdZUPbholhqWpReGzOlYUms1I2h9Tk1PhQ+5Oza k6dSEY7cJN0HmVIFMXcMyNr2XFD9YgbQgDhPt+LKGPoLyPiwbcLfHttJo2YAzPLaQJzt vO4d7/mIuw5vNkP1EIhJSx9jGjvNozGYhhTLM6y8h1+OGfM8tmRAQ2nrAlhewAEeCr90 wtlH7FCFxN4SayYwRTQ6CTQdDgwFRHuBjf4IdAkLw48TYXE+sx0kFecWGWt3h/kyxUeB dksQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GExAg8smGhBmD/xc/IvC+P9DdhHcMjmwU8stKvZndNo=; b=Oq+PPYj54Kqu6Ydlwc+Nl8gejqxrMlJiuUtLAbZq1s0DDRh1PNoVyZnhwz2rBUvanm nGBEGr9ubFA7MtXxb8ZC0oWgOdsAgykRHAUCkEUlg0DzNOkX6Orh8f3FitOGPpVNHXEE 0aD7Yrq6NqYXfcPpfx7b5u2NjjjsIi6xCCkPr+20W6de26mIkMb+36xY9IPCBPkK3+Rf QIKoNpvVAEMIb+btnhDqA1x5NUxYDWV4Msu7SjDI/Fqo8usYPJpA8H+hsTX3AEF++BBp N58giIXDvHNywcS4/C8fs1ESMNfvaz3p7E42Gqu24IOTabncnlXOrI5Jc2SVcZ96dK68 iynA==
X-Gm-Message-State: AOAM532bkYYM9teiBMZglin6XfALe4rF0CvikqnVWw4Q+LSyKXqbXVbP u+/I0ZL5d6zJszHSv+rCrp5yERTs4ic=
X-Google-Smtp-Source: ABdhPJzToHtDxDw8Ke4Ru5mur2mwMkpYupNevyQ6gnVmRoorC5Lpi9Ux+0y/TwhH1Sl+Dp41SF+pBg==
X-Received: by 2002:aca:1211:: with SMTP id 17mr3797962ois.63.1611953771747; Fri, 29 Jan 2021 12:56:11 -0800 (PST)
Received: from [192.168.0.109] (108-226-162-63.lightspeed.sntcca.sbcglobal.net. [108.226.162.63]) by smtp.gmail.com with ESMTPSA id a28sm2652382ook.24.2021.01.29.12.56.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Jan 2021 12:56:10 -0800 (PST)
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <161144436332.13490.10651420808048876097@ietfa.amsl.com> <CADyWQ+EhD0nz71dLtUFwb9V_6uuen-k6E5fpvrCg3ZYzfr2JSw@mail.gmail.com> <ba38a9e4-7f43-c747-2d90-f35de22a8399@gmail.com> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com>
Date: Fri, 29 Jan 2021 12:56:09 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------316A07D9CBB049804459C49E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/pmkZ3zYmXTc4_-6LItpi1Ywz07U>
Subject: Re: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-10.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: Fri, 29 Jan 2021 20:56:15 -0000

This is a multi-part message in MIME format.
--------------316A07D9CBB049804459C49E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 1/29/2021 12:15 PM, Murray S. Kucherawy wrote:
> On Fri, Jan 29, 2021 at 7:51 AM Dave Crocker <dcrocker@gmail.com 
> <mailto:dcrocker@gmail.com>> wrote:
>
>
>>     Abstract
>>
>>         DMARC (Domain-based Message Authentication, Reporting, and
>>         Conformance) is a scalable mechanism by which a mail-originating
>>         organization can express domain-level policies and preferences for
>>         message validation, disposition, and reporting, that a mail-receiving
>>         organization can use to improve mail handling.  The design of DMARC
>>         presumes that domain names represent either nodes in the tree below
>>         which registrations occur, or nodes where registrations have
>     DMARC does not have 'registrations'.
>
>
> It's referring to domain name registrations, not DMARC registrations.
>
>     Also the occur/occured contrast has no obvious meaning to me. 
>     Really, I have no idea what's intended by it.
>
> "exist"?
> "take place"?
> "are made"?
> "are done"?

The issue wasn't synonyms but semantics.  'registrations occurred' has 
no obvious DMARC meaning.

unless, perhaps, the meaning is 'domain names exist', but that still 
doesn't explain the contrast being drawn.


>
>>         occurred; it does not permit a domain name to have both of these
>     "both" of what?  registration?
>
>
> It's describing properties of nodes in the domain name tree. DMARC's 
> current design stipulates that every node is either (a) a node below 
> which registrations can occur, or (b) a node at which a registration 
> has occurred.  An example of the former is "org", and an example of 
> the latter is "ietf.org <http://ietf.org>" and its entire subtree.

DMARC does not have 'registrations'.

The word in used in the spec as:

"


    3 <https://tools.ietf.org/html/rfc7489#section-3>. Terminology and
    Definitions

Domain Owner:  An entity or organization that owns a DNS domain.  The
       term "owns" here indicates that the entity or organization being
       referenced holds the registration of that DNS domain."


and:


"


      3.2 <https://tools.ietf.org/html/rfc7489#section-3.2>.
      Organizational Domain



    The Organizational Domain is determined using the following
    algorithm:

    1.  Acquire a "public suffix" list, i.e., a list of DNS domain names
        reserved for registrations. "

(The later reference to the Tag Registry is presumably irrelevant here.)


>
>>         properties simultaneously.  Since its deployment in 2015, use of
>>         DMARC has shown a clear need for the ability to express policy for
>>         these domains as well.
>     Which domains?
>
>
> The intent is to augment DMARC's ability to describe the domain name 
> tree such that a node can be both (a) and (b) at the same time, for 
> the purposes of policy expression.  So those are the nodes (domains) 
> of interest.


My frustration is that a document that reaches wg Last Call should not 
have language that is this confusing, especially about its fundamentals 
and especially given how much revision it has already gotten.



d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org


--------------316A07D9CBB049804459C49E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 1/29/2021 12:15 PM, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Fri, Jan 29, 2021 at 7:51 AM Dave Crocker &lt;<a
            href="mailto:dcrocker@gmail.com" moz-do-not-send="true">dcrocker@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div><br>
              <p> </p>
              <blockquote type="cite">
                <div>
                  <pre>Abstract

   DMARC (Domain-based Message Authentication, Reporting, and
   Conformance) is a scalable mechanism by which a mail-originating
   organization can express domain-level policies and preferences for
   message validation, disposition, and reporting, that a mail-receiving
   organization can use to improve mail handling.  The design of DMARC
   presumes that domain names represent either nodes in the tree below
   which registrations occur, or nodes where registrations have</pre>
                </div>
              </blockquote>
              DMARC does not have 'registrations'.</div>
          </blockquote>
          <div><br>
          </div>
          <div>It's referring to domain name registrations, not DMARC
            registrations.</div>
          <div> <br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p>Also the occur/occured contrast has no obvious meaning
                to me.  Really, I have no idea what's intended by it.<br>
              </p>
            </div>
          </blockquote>
          <div>"exist"?</div>
          <div>"take place"?</div>
          <div>"are made"?</div>
          <div>"are done"?<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>The issue wasn't synonyms but semantics.  'registrations
      occurred' has no obvious DMARC meaning.</p>
    <p>unless, perhaps, the meaning is 'domain names exist', but that
      still doesn't explain the contrast being drawn.</p>
    <p><br>
    </p>
    <blockquote type="cite"
cite="mid:CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <p> </p>
              <p><br>
              </p>
              <blockquote type="cite">
                <div>
                  <pre>   occurred; it does not permit a domain name to have both of these</pre>
                </div>
              </blockquote>
              "both" of what?  registration?</div>
          </blockquote>
          <div><br>
          </div>
          It's describing properties of nodes in the domain name tree. 
          DMARC's current design stipulates that every node is either
          (a) a node below which registrations can occur, or (b) a node
          at which a registration has occurred.  An example of the
          former is "org", and an example of the latter is "<a
            href="http://ietf.org" moz-do-not-send="true">ietf.org</a>"
          and its entire subtree.</div>
      </div>
    </blockquote>
    <p>DMARC does not have 'registrations'.</p>
    <p>The word in used in the spec as:</p>
    <p>"<br>
    </p>
    <pre class="newpage"><span class="h2"><h2><a class="selflink" name="section-3" href="https://tools.ietf.org/html/rfc7489#section-3">3</a>.  Terminology and Definitions</h2></span></pre>
    <pre class="newpage">Domain Owner:  An entity or organization that owns a DNS domain.  The
      term "owns" here indicates that the entity or organization being
      referenced holds the registration of that DNS domain."</pre>
    <p><br>
    </p>
    <p>and:</p>
    <p><br>
    </p>
    <p>"<br>
    </p>
    <pre class="newpage"><span class="h3"><h3><a class="selflink" name="section-3.2" href="https://tools.ietf.org/html/rfc7489#section-3.2">3.2</a>.  Organizational Domain</h3></span>

   The Organizational Domain is determined using the following
   algorithm:

   1.  Acquire a "public suffix" list, i.e., a list of DNS domain names
       reserved for registrations. "

(The later reference to the Tag Registry is presumably irrelevant here.)


</pre>
    <blockquote type="cite"
cite="mid:CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote"><br>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <blockquote type="cite">
                <div>
                  <pre>   properties simultaneously.  Since its deployment in 2015, use of
   DMARC has shown a clear need for the ability to express policy for
   these domains as well.</pre>
                </div>
              </blockquote>
              Which domains?</div>
          </blockquote>
          <div><br>
          </div>
          <div>The intent is to augment DMARC's ability to describe the
            domain name tree such that a node can be both (a) and (b) at
            the same time, for the purposes of policy expression.  So
            those are the nodes (domains) of interest.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>My frustration is that a document that reaches wg Last Call
      should not have language that is this confusing, especially about
      its fundamentals and especially given how much revision it has
      already gotten.</p>
    <p><br>
    </p>
    <p><br>
    </p>
    d/
    <pre class="moz-signature" cols="72">-- 
Dave Crocker
<a class="moz-txt-link-abbreviated" href="mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------316A07D9CBB049804459C49E--


From nobody Fri Jan 29 13:00:11 2021
Return-Path: <johnl@iecc.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 ED0543A12ED for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 13:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level: 
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=iT6tSswQ; dkim=pass (2048-bit key) header.d=taugh.com header.b=27UQ9Zgg
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 lJY8epGtRZ7a for <dmarc@ietfa.amsl.com>; Fri, 29 Jan 2021 13:00:08 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 DA5C33A12EA for <dmarc@ietf.org>; Fri, 29 Jan 2021 13:00:07 -0800 (PST)
Received: (qmail 76818 invoked from network); 29 Jan 2021 21:00:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=12c10.60147756.k2101; bh=ZrpgvzXSgeeS2X45mBD0lyBCLlHYwU4rH7zsxS0zkBc=; b=iT6tSswQNBVDOVnuBbQislrLpIfmztZXFR9tTz3X1gcjPpmHaFrJ0GBnK2hCh2wQEnp58annF1rg4oUmDekLYf1kX3VLScwqDtizJ8mmfhPFB2xKduTJrNCLyYtU+CgI4J5quC8PGEuJ8WihM19QHjYN+d1SXNZxiSjWQFhLHlsFdlCrPdWSIFPQyUO7SXewlTQFdnYCBMqVToKO/Fnc5xz57SVdR8Buj/fckbWY0+s5QhvgXlYoMeKn8JsqrjFMXdGkR8Z7Ceow3j8iXMWhpNtLjiVfmDzvSfZ8t5r9KVpiceMstC2w9Rg6VXitxPHgY5TXuVNPEwePv/ZsZcRgSQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=12c10.60147756.k2101; bh=ZrpgvzXSgeeS2X45mBD0lyBCLlHYwU4rH7zsxS0zkBc=; b=27UQ9Zgghih6Q7hP08cV3cXe2juy0xrR1eqOi1iCUOGb58MKaX+me3dQK7ro8MET9qecpWGGPyeOoy38NBlKgGBGO7sf4yzx4fhATYRZdQRDiSwFSnhF5+ABojVuLZAANE5ETBACHlVQERcwZuxfYMdxPRYzBKxGLvpquPVShsZVFezUoQjYpjdcFn3vd7VqpOQBZWueaSDL3M6SdSOYLdl1S8MydQvCoNsK/zfuLOb5OTiVAo0QwUVgtVZj2cwH5X/Koovryvc/rFOnuUcSDpKvT0wqIYyWFrwhhsXT8kDKOYcxD6LA2sAm5jOaildDRxFEVuQRGjaODYyvYZjRCg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 29 Jan 2021 21:00:06 -0000
Received: by ary.qy (Postfix, from userid 501) id 063C66CF2279; Fri, 29 Jan 2021 16:00:05 -0500 (EST)
Date: 29 Jan 2021 16:00:05 -0500
Message-Id: <20210129210006.063C66CF2279@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <db72db79-272e-5d52-8994-4da81c8723bd@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_mpPtFLukVPxRq7xL1JIc_WXyIc>
Subject: Re: [dmarc-ietf] Report bombing is a prolem, Forensic report loops are not
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: Fri, 29 Jan 2021 21:00:10 -0000

In article <db72db79-272e-5d52-8994-4da81c8723bd@tana.it> you write:
>3.3.  Transport
>
>    Email streams carrying DMARC failure reports MUST conform to the
>    DMARC mechanism, thereby resulting in an aligned "pass".  Special
>    care must be taken of authentication, as failure to authenticate
>    failure reports may provoke further reports.

    Reporters SHOULD rate limit the number of failure reports sent
    to any recipient to avoid overloading recipient systems.


Why would reports due to a mail loop be more of a problem than due to
some random spammer sending a lot of fake mail, or (real life) your
users send mail to mailing lists with thousands of subscribers? Rate
limit your reports, don't worry about where they came from.

R's,
John


From nobody Sat Jan 30 02:41:12 2021
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 9B2D03A0D3C for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 02:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 vDOYgB2YFOyt for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 02:41:08 -0800 (PST)
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 AA0923A0D39 for <dmarc@ietf.org>; Sat, 30 Jan 2021 02:41:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612003263; bh=H+ZkWFktSUiYJx/s0mwi+XdfoD//K9SjQRPWbGhL1Jc=; l=2031; h=To:References:From:Date:In-Reply-To; b=APV7ljG4EOVN4f00WyxMG0UQjfACiX+3fXTuOMT6q/ZeBMA47wgjDUzl96NgUhsbt BjsVvY2FGPVlpG2HNrQRXVYu9F94sIN/66CAQKWL5F3ixGv8LdocrMS1lb5afgeOc7 acSyEh2z4W62FSlg7PURmUo6UnMFRFKUSL9buNATxqhJJVKmM51u/8tbm7p6o
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.00000000601537BF.00002740; Sat, 30 Jan 2021 11:41:03 +0100
To: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com> <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it> <CAL0qLwbYxTXXXpx11L3f1CqBns=fSRho3C+S7q=-DmiPSvxKvg@mail.gmail.com> <cf51d6d4-0c7b-971d-bcac-743370f16433@tana.it> <CAL0qLwYK7SFfV5fOb7qhy5hVgR15z4HEJbAHv38OFMAfC=_j-Q@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <920ee8e1-2947-379e-5798-2a6818e69526@tana.it>
Date: Sat, 30 Jan 2021 11:41:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwYK7SFfV5fOb7qhy5hVgR15z4HEJbAHv38OFMAfC=_j-Q@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/XvVG2ujuYzUaecWYvvh-zhh9EPo>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 10:41:11 -0000

On Fri 29/Jan/2021 21:30:49 +0100 Murray S. Kucherawy wrote:
> On Fri, Jan 29, 2021 at 3:02 AM Alessandro Vesely <vesely@tana.it> wrote:
> 
>> I just run a quick test on my current folder.  Out of 3879 messages I 
>> extracted 944 unique helo names.  721 of these matched the reverse lookup
>> exactly. Out of the 223 remaining, 127 had an SPF pass for the helo
>> identity anyway. So in 96 cases, roughly 10%, the helo name was indeed
>> junk.  Isn't the remaining ~90% something worth considering? >
> I am admittedly quite heavily biased against using the HELO/EHLO value for
> anything.  I have simply never found value in it, probably because at the
> SMTP layer it's simply a value that gets logged or used in cute ways in the
> human-readable portion of SMTP.  I seem to recall (but cannot seem to find
> at the moment) RFC 5321 saying you can't reject HELO/EHLO based on a bogus
> value, so it's even explicitly not useful to me.


There seems to be consensus on changing the MUST NOT there to a SHOULD NOT. 
See ticket #19 of emailcore.


> Even if it's not junk, there's pretty much always something else on which
> to hang a pass/fail decision about the apparent authenticity of a message
> that at least feels safer if not actually being more sound.


I might understand being reluctant to spend a DNS lookup for a TXT record that 
many operators don't care to define.  However, we're discussing the case that 
an upstream SPF filter already acquired and evaluated that record.


> Or put another way, if you present to me a DKIM-signed message with a MAIL
> FROM value and the only thing that passes is an SPF check against HELO, I'm
> mighty skeptical.

We have helo as the only valid identifier in most DSNs.  What is idiosyncratic 
is that a message MUST be a DSN (i.e. have an empty mfrom) in order for an 
already authenticated helo to be considered significant.  What I'm proposing is 
actually a simplification.


> Anyway, I'll let consensus fall where it may.


Thank you
Ale
-- 




















From nobody Sat Jan 30 04:44:39 2021
Return-Path: <dougfoster.emailstandards@gmail.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 51F7C3A07DF for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 04:44:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mjXg6FTK9Fhu for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 04:44:35 -0800 (PST)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66A433A07C8 for <dmarc@ietf.org>; Sat, 30 Jan 2021 04:44:35 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id i12so3413947vsq.6 for <dmarc@ietf.org>; Sat, 30 Jan 2021 04:44:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=YwHSQndmuzVPa384Kc4koYwxpXMrbOYcCuj6UIQAgH8=; b=MAbLh4OygP9OLFsoxQe8yAvE24eGLQ+aK+8jogjkObXLOSibxxfyA0Mj0apTkmLkVi VH0OugV9TPP69UGrVYKqFewbHfwtpRtcjqRPe04SZImbdKw7CP+FAG3K9262BpZFWmKT rFe+L5dap4Od664PFMQ9Rln7m7vxa1EImZrB/ttMKnC7BpH22WkK/wWA6Dk5ANWrI8Rt jDAgYZDwUoLCgefw6Uv8UKSbmKAnm7XOkKzR7MxUKxU4kMG8Gqsfs11D9QBCT6XO9z5n 32LP4C4EFsptTsW6eKXVgXDy0fmrlOCyO4vtnyg4gGiNgr+LtAoECGWeak06uWwe63iU 8CwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=YwHSQndmuzVPa384Kc4koYwxpXMrbOYcCuj6UIQAgH8=; b=sMBJAoXWgVZsmZIpIIialrFY+RLfpXB3V/iD4KhSYwt8AgT71bWUsmLLQ+nffUo9XJ YDf1IDWKC5x+C2SSQkeag86Ws03Z9cqrPRpDe2QqYkAV03xyLjfHfBdFqXSvikf9Y1IJ ZB3I/HadDVdnhh1w7g9rvX3kpOudu9gdpmHCzmFCrMFWhf7pMCz6G2jy8zUuomTki5gA JvGvT0DSGS9VI+iFDj5WBOXcNtJAoXsClwnTpweMkLZuF4uhEYQv0I479biQrUDfGja0 XFOY8Ab7NDbP+TeltR1baIeVje27pMzcYB5Enu08A6V+O3uSCSp9w0CR63aGKikV0kkE 6fqw==
X-Gm-Message-State: AOAM531GjPH0UbG/pfwJycTJJxdAOw5AKnLtq+vqOSt1KVizYsV1M+TE vhL3mn/d4S5Vzn4cmM4Fuvyw68WchxU8wpm+0Z0qEVFghbCa3Q==
X-Google-Smtp-Source: ABdhPJySMJ5TSAVvZXjvf4pwzLmtTpoh0hQDPOgvDSp/T82IznpQawiHzB2vO47MxrckkxxEKrcC5u0CKJ9kHOusxPQ=
X-Received: by 2002:a67:c29e:: with SMTP id k30mr5241407vsj.45.1612010673948;  Sat, 30 Jan 2021 04:44:33 -0800 (PST)
MIME-Version: 1.0
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com> <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it> <CAL0qLwbYxTXXXpx11L3f1CqBns=fSRho3C+S7q=-DmiPSvxKvg@mail.gmail.com> <cf51d6d4-0c7b-971d-bcac-743370f16433@tana.it> <CAL0qLwYK7SFfV5fOb7qhy5hVgR15z4HEJbAHv38OFMAfC=_j-Q@mail.gmail.com> <920ee8e1-2947-379e-5798-2a6818e69526@tana.it>
In-Reply-To: <920ee8e1-2947-379e-5798-2a6818e69526@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 30 Jan 2021 07:44:24 -0500
Message-ID: <CAH48ZfyFB=ys44NwRB=j8h9t6XgfsC84JnOd6whFo4GM7-1xMg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000098490505ba1d7b7b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/TlftrWczMzhwR0zv7qgAJYbBLf4>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 12:44:37 -0000

--00000000000098490505ba1d7b7b
Content-Type: text/plain; charset="UTF-8"

I have been using forward-confirmed DNS in my filtering logic for a long
time.   These are my results from a recent time period:
4.5% neither name confirmed
9.6% reverse DNS confirmed only
39.7% Helo confirmed only
46.2% Both confirmed

Of the ones where both were confirmed:
96% had the same domain in both names,
4% had different domains between HELO and REVDNS

I apply my DNS blacklisting rules to both domain names.
I often use a verified DNS domain (either type) with SMTP domain to define
corrections for sender SPF policy.
HELO is part of the SPF algorithm that I use, but I do not track how often
it is used to generate SPF PASS.
I use BATV to I don't worry much about SPF or DMARC for automatic messages.

Overall, I don't know how important HELO is to SPF, but it is verifiable
and often useful.

Doug Foster

On Sat, Jan 30, 2021 at 5:41 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Fri 29/Jan/2021 21:30:49 +0100 Murray S. Kucherawy wrote:
> > On Fri, Jan 29, 2021 at 3:02 AM Alessandro Vesely <vesely@tana.it>
> wrote:
> >
> >> I just run a quick test on my current folder.  Out of 3879 messages I
> >> extracted 944 unique helo names.  721 of these matched the reverse
> lookup
> >> exactly. Out of the 223 remaining, 127 had an SPF pass for the helo
> >> identity anyway. So in 96 cases, roughly 10%, the helo name was indeed
> >> junk.  Isn't the remaining ~90% something worth considering? >
> > I am admittedly quite heavily biased against using the HELO/EHLO value
> for
> > anything.  I have simply never found value in it, probably because at the
> > SMTP layer it's simply a value that gets logged or used in cute ways in
> the
> > human-readable portion of SMTP.  I seem to recall (but cannot seem to
> find
> > at the moment) RFC 5321 saying you can't reject HELO/EHLO based on a
> bogus
> > value, so it's even explicitly not useful to me.
>
>
> There seems to be consensus on changing the MUST NOT there to a SHOULD
> NOT.
> See ticket #19 of emailcore.
>
>
> > Even if it's not junk, there's pretty much always something else on which
> > to hang a pass/fail decision about the apparent authenticity of a message
> > that at least feels safer if not actually being more sound.
>
>
> I might understand being reluctant to spend a DNS lookup for a TXT record
> that
> many operators don't care to define.  However, we're discussing the case
> that
> an upstream SPF filter already acquired and evaluated that record.
>
>
> > Or put another way, if you present to me a DKIM-signed message with a
> MAIL
> > FROM value and the only thing that passes is an SPF check against HELO,
> I'm
> > mighty skeptical.
>
> We have helo as the only valid identifier in most DSNs.  What is
> idiosyncratic
> is that a message MUST be a DSN (i.e. have an empty mfrom) in order for an
> already authenticated helo to be considered significant.  What I'm
> proposing is
> actually a simplification.
>
>
> > Anyway, I'll let consensus fall where it may.
>
>
> Thank you
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--00000000000098490505ba1d7b7b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I have been using forward-confirmed DNS in my filteri=
ng=C2=A0logic for a long time.=C2=A0 =C2=A0These are my results from a rece=
nt time period:<br></div><div>4.5% neither name confirmed</div><div>9.6% re=
verse DNS confirmed only</div><div>39.7% Helo confirmed only</div><div>46.2=
% Both confirmed</div><div><br></div><div>Of the ones where both were confi=
rmed:</div><div>96% had the same domain in both names,=C2=A0</div><div>4% h=
ad different domains between HELO and REVDNS</div><div><br></div><div>I app=
ly=C2=A0my DNS blacklisting rules to both domain names.=C2=A0 =C2=A0<br></d=
iv><div>I often use a verified DNS domain (either type) with SMTP domain to=
 define corrections for sender SPF policy.</div><div><div>HELO is part of t=
he SPF algorithm that I use, but I do not track how often it is used to gen=
erate SPF PASS.</div><div>I use BATV to I don&#39;t worry much about SPF or=
 DMARC for automatic messages.</div><div></div></div><div><br></div><div>Ov=
erall, I don&#39;t know how important HELO is to SPF, but it is verifiable =
and often useful.</div><div><br></div><div>Doug Foster</div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jan 30,=
 2021 at 5:41 AM Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it">ve=
sely@tana.it</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">On Fri 29/Jan/2021 21:30:49 +0100 Murray S. Kucherawy wrote:<br=
>
&gt; On Fri, Jan 29, 2021 at 3:02 AM Alessandro Vesely &lt;<a href=3D"mailt=
o:vesely@tana.it" target=3D"_blank">vesely@tana.it</a>&gt; wrote:<br>
&gt; <br>
&gt;&gt; I just run a quick test on my current folder.=C2=A0 Out of 3879 me=
ssages I <br>
&gt;&gt; extracted 944 unique helo names.=C2=A0 721 of these matched the re=
verse lookup<br>
&gt;&gt; exactly. Out of the 223 remaining, 127 had an SPF pass for the hel=
o<br>
&gt;&gt; identity anyway. So in 96 cases, roughly 10%, the helo name was in=
deed<br>
&gt;&gt; junk.=C2=A0 Isn&#39;t the remaining ~90% something worth consideri=
ng? &gt;<br>
&gt; I am admittedly quite heavily biased against using the HELO/EHLO value=
 for<br>
&gt; anything.=C2=A0 I have simply never found value in it, probably becaus=
e at the<br>
&gt; SMTP layer it&#39;s simply a value that gets logged or used in cute wa=
ys in the<br>
&gt; human-readable portion of SMTP.=C2=A0 I seem to recall (but cannot see=
m to find<br>
&gt; at the moment) RFC 5321 saying you can&#39;t reject HELO/EHLO based on=
 a bogus<br>
&gt; value, so it&#39;s even explicitly not useful to me.<br>
<br>
<br>
There seems to be consensus on changing the MUST NOT there to a SHOULD NOT.=
 <br>
See ticket #19 of emailcore.<br>
<br>
<br>
&gt; Even if it&#39;s not junk, there&#39;s pretty much always something el=
se on which<br>
&gt; to hang a pass/fail decision about the apparent authenticity of a mess=
age<br>
&gt; that at least feels safer if not actually being more sound.<br>
<br>
<br>
I might understand being reluctant to spend a DNS lookup for a TXT record t=
hat <br>
many operators don&#39;t care to define.=C2=A0 However, we&#39;re discussin=
g the case that <br>
an upstream SPF filter already acquired and evaluated that record.<br>
<br>
<br>
&gt; Or put another way, if you present to me a DKIM-signed message with a =
MAIL<br>
&gt; FROM value and the only thing that passes is an SPF check against HELO=
, I&#39;m<br>
&gt; mighty skeptical.<br>
<br>
We have helo as the only valid identifier in most DSNs.=C2=A0 What is idios=
yncratic <br>
is that a message MUST be a DSN (i.e. have an empty mfrom) in order for an =
<br>
already authenticated helo to be considered significant.=C2=A0 What I&#39;m=
 proposing is <br>
actually a simplification.<br>
<br>
<br>
&gt; Anyway, I&#39;ll let consensus fall where it may.<br>
<br>
<br>
Thank you<br>
Ale<br>
-- <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--00000000000098490505ba1d7b7b--


From nobody Sat Jan 30 04:52:10 2021
Return-Path: <dougfoster.emailstandards@gmail.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 672853A083E for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 04:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VCjxmp1var0J for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 04:52:07 -0800 (PST)
Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A02F73A0839 for <dmarc@ietf.org>; Sat, 30 Jan 2021 04:52:07 -0800 (PST)
Received: by mail-ua1-x935.google.com with SMTP id g5so4163122uak.10 for <dmarc@ietf.org>; Sat, 30 Jan 2021 04:52:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=K7CbGIS+B6Kd3OMrTaOlsMFrEqNkmGV+QtQeULZd2xs=; b=Lyf9QaUBg3BYWxDMUR34feXsyT3v+/Ur7vq4GR5MZvIFHr6aIu1H494VEGkgkbnuDM byUXRF84U1Ams9f2FEySgRYTDzN/NvirnepssTjpeEh6QOjK1eVSJ24GXBBWlcDR70pO Qk8WSvUTmN5q2JWM5fmF5SGUU7wQTOdKafrIZkyc/zAVa2PlLeTdePq47kNzxJABw8fU f+5ygbhUf8p59eczw1CF7FGEAvAgbj6YDz3FeuHB0mAMCnyYOwSewHgAdcmOyRPxKE8L WwK1f0tuEjmLrpjHqVaxBdJ8iRvHI9QvOjdGSflPF4w/5umHa8Ry7EIMOnOeBOG/6ryQ zxTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=K7CbGIS+B6Kd3OMrTaOlsMFrEqNkmGV+QtQeULZd2xs=; b=NnCfIBIucXMZNxE8RG90/0ZWIo7+2hSnDaJSgTM3Zk6ZtjYNi1A5juxzc2fIDExiiv cT6juTSkAIdqPrGahXF3sBKDsElSx1nG/so8akJSlH+2bFqxkPJHex1JWutVeppqScEz aUCSr8Q4X8wz6Run5C4C3SCgjkgbAaBbpXyTVUO2ptRSTHko2w2LE92xWGZ1YQ/oEyzB mvzNnNKg08Sp3ozjyOqby6EbDxXJB4mcfm0oFCUW1rG4+S6H3UH2ioYFNLHcuFXl41rQ TTq0rKSxwtp6gztDCWeJlasCIE0VoFefZHQVgVASyA7ulwQJPsMRxygaTFtklcP6b4aA Bzyg==
X-Gm-Message-State: AOAM5309eIIQcs3DTguNSyqhoqDJfGr0renU9e+JorKkQBU9ThW8DaEf GbfoWix1KaNufEC2h0ndKBxlWCRx0GV/G+fcfar93UdJY40=
X-Google-Smtp-Source: ABdhPJz+/GmHoQ5U43VSl6EVQna+S24Rd4S5VhAJVU3nuJhq0rr5WpXZo7QKR3dyIwkvQtqJx5X/owTeFb0rSj8loOk=
X-Received: by 2002:ab0:5e6:: with SMTP id e93mr5092380uae.109.1612011126412;  Sat, 30 Jan 2021 04:52:06 -0800 (PST)
MIME-Version: 1.0
References: <db72db79-272e-5d52-8994-4da81c8723bd@tana.it> <20210129210006.063C66CF2279@ary.qy>
In-Reply-To: <20210129210006.063C66CF2279@ary.qy>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 30 Jan 2021 07:51:56 -0500
Message-ID: <CAH48ZfxCpFjySAL06a9pDusX1FiuSuVsHkBZG-Zkvxgu3BJmcA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000905b0105ba1d9686"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/dn4RrEZjb5mz6O0RNjq1VkNFn5o>
Subject: Re: [dmarc-ietf] Report bombing is a prolem, Forensic report loops are not
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, 30 Jan 2021 12:52:09 -0000

--000000000000905b0105ba1d9686
Content-Type: text/plain; charset="UTF-8"

Interesting point.

In your experience, how often does reporting produce any change in sender
behavior?

I have made attempts both to help senders correct their own SPF or DMARC
policy, or to get them to stop violating my DMARC policy.   As best I can
recall, my success rate has been zero.

For a responsive organization, finding a problem and getting the change
approved is likely to be a time-consuming a quick process.   A week
turnaround would seem timely, unless they go into emergency mode because
lots of mail is being blocked.

The spec is confusing because it says (a) failure reports should be sent
immediately, (b) failure reports should be aggregated, and (c) failure
reports should be throttled but without specifying a limit.

Of course, if the cause is a spammer, there is nothing that the domain
owner can do at all.

I wonder if the rule should be one message per week per source, since any
large volume sender will be getting reports from multiple sources.   The
main problem with this is that law enforcement actions may want to be
bombed.

DF



On Fri, Jan 29, 2021 at 4:00 PM John Levine <johnl@taugh.com> wrote:

> In article <db72db79-272e-5d52-8994-4da81c8723bd@tana.it> you write:
> >3.3.  Transport
> >
> >    Email streams carrying DMARC failure reports MUST conform to the
> >    DMARC mechanism, thereby resulting in an aligned "pass".  Special
> >    care must be taken of authentication, as failure to authenticate
> >    failure reports may provoke further reports.
>
>     Reporters SHOULD rate limit the number of failure reports sent
>     to any recipient to avoid overloading recipient systems.
>
>
> Why would reports due to a mail loop be more of a problem than due to
> some random spammer sending a lot of fake mail, or (real life) your
> users send mail to mailing lists with thousands of subscribers? Rate
> limit your reports, don't worry about where they came from.
>
> R's,
> John
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000905b0105ba1d9686
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Interesting point.<div><br></div><div>In your experience, =
how often does reporting produce any change in sender behavior?=C2=A0 =C2=
=A0</div><div><br></div><div>I have made attempts both to help senders corr=
ect their own SPF or DMARC policy, or to get them to stop violating my DMAR=
C policy.=C2=A0 =C2=A0As best I can recall, my success rate has been zero.<=
/div><div><br></div><div>For a responsive organization, finding=C2=A0a prob=
lem and getting the change approved is likely to be a time-consuming a quic=
k process.=C2=A0 =C2=A0A week turnaround would seem timely, unless they go =
into emergency mode because lots of mail is being blocked.</div><div><br></=
div><div>The spec is confusing because it says (a) failure reports should b=
e sent immediately, (b) failure reports should be aggregated, and (c) failu=
re reports should be throttled but without specifying a limit.</div><div><b=
r></div><div>Of course, if the cause is a spammer, there is nothing that th=
e domain owner can do at all.</div><div><br></div><div>I wonder if the rule=
 should be one message per week per source,=C2=A0since any large volume sen=
der will be getting reports from multiple sources.=C2=A0 =C2=A0The main pro=
blem with=C2=A0this is that law enforcement actions may want to be bombed.<=
/div><div><br></div><div>DF</div><div><br></div><div><br></div></div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan =
29, 2021 at 4:00 PM John Levine &lt;<a href=3D"mailto:johnl@taugh.com">john=
l@taugh.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">In article &lt;<a href=3D"mailto:db72db79-272e-5d52-8994-4da81c8=
723bd@tana.it" target=3D"_blank">db72db79-272e-5d52-8994-4da81c8723bd@tana.=
it</a>&gt; you write:<br>
&gt;3.3.=C2=A0 Transport<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Email streams carrying DMARC failure reports MUST conform=
 to the<br>
&gt;=C2=A0 =C2=A0 DMARC mechanism, thereby resulting in an aligned &quot;pa=
ss&quot;.=C2=A0 Special<br>
&gt;=C2=A0 =C2=A0 care must be taken of authentication, as failure to authe=
nticate<br>
&gt;=C2=A0 =C2=A0 failure reports may provoke further reports.<br>
<br>
=C2=A0 =C2=A0 Reporters SHOULD rate limit the number of failure reports sen=
t<br>
=C2=A0 =C2=A0 to any recipient to avoid overloading recipient systems.<br>
<br>
<br>
Why would reports due to a mail loop be more of a problem than due to<br>
some random spammer sending a lot of fake mail, or (real life) your<br>
users send mail to mailing lists with thousands of subscribers? Rate<br>
limit your reports, don&#39;t worry about where they came from.<br>
<br>
R&#39;s,<br>
John<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000905b0105ba1d9686--


From nobody Sat Jan 30 11:59:21 2021
Return-Path: <fenton@bluepopcorn.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 938C23A10CA for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 11:59:20 -0800 (PST)
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_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 Z8SA5eY1MiBA for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 11:59:18 -0800 (PST)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 C883A3A10C5 for <dmarc@ietf.org>; Sat, 30 Jan 2021 11:59:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=o8ruw1lTNqiNRTK/LfcoqI8YmiGCIUWwI0dCPGHjR/w=; b=Eu7WZxA+4qhg9fsVHuHa+XD60Z TNUuhasGsnm4tatvZMm4GTZHWmEiqhj5t82bptQaQLRs6GXjGS0kPn923wsrbYUjnRG/Zi1bcjRGa ILtFSBpJUMM9d2JM9LwipvNSOMWjlTJS/VI9n456qVP+FQCUsoBh3m0iXr9mEW2XhfDU=;
Received: from [2601:647:4400:1261:30d3:3a9d:66d5:72cc] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1l5wOo-0007kh-AE; Sat, 30 Jan 2021 11:59:15 -0800
From: "Jim Fenton" <fenton@bluepopcorn.net>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: "Alessandro Vesely" <vesely@tana.it>, "IETF DMARC WG" <dmarc@ietf.org>
Date: Sat, 30 Jan 2021 11:59:13 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net>
In-Reply-To: <CAL0qLwYK7SFfV5fOb7qhy5hVgR15z4HEJbAHv38OFMAfC=_j-Q@mail.gmail.com>
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com> <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it> <CAL0qLwbYxTXXXpx11L3f1CqBns=fSRho3C+S7q=-DmiPSvxKvg@mail.gmail.com> <cf51d6d4-0c7b-971d-bcac-743370f16433@tana.it> <CAL0qLwYK7SFfV5fOb7qhy5hVgR15z4HEJbAHv38OFMAfC=_j-Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WpBH-jgw-7RWyRp__rZwpj_Y-ow>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 19:59:21 -0000

On 29 Jan 2021, at 12:30, Murray S. Kucherawy wrote:

> On Fri, Jan 29, 2021 at 3:02 AM Alessandro Vesely <vesely@tana.it> 
> wrote:
>
>> I just run a quick test on my current folder.  Out of 3879 messages I
>> extracted
>> 944 unique helo names.  721 of these matched the reverse lookup 
>> exactly.
>> Out
>> of the 223 remaining, 127 had an SPF pass for the helo identity 
>> anyway.
>> So in
>> 96 cases, roughly 10%, the helo name was indeed junk.  Isn't the 
>> remaining
>> ~90%
>> something worth considering?

The issue isn’t the existing use of HELO names, it’s how they could 
be (mis-)used. The fact that a message sender can put anything there 
makes HELO basically meaningless.

> I am admittedly quite heavily biased against using the HELO/EHLO value 
> for
> anything.  I have simply never found value in it, probably because at 
> the
> SMTP layer it's simply a value that gets logged or used in cute ways 
> in the
> human-readable portion of SMTP.  I seem to recall (but cannot seem to 
> find
> at the moment) RFC 5321 saying you can't reject HELO/EHLO based on a 
> bogus
> value, so it's even explicitly not useful to me.
>
> Even if it's not junk, there's pretty much always something else on 
> which
> to hang a pass/fail decision about the apparent authenticity of a 
> message
> that at least feels safer if not actually being more sound.  Or put 
> another
> way, if you present to me a DKIM-signed message with a MAIL FROM value 
> and
> the only thing that passes is an SPF check against HELO, I'm mighty
> skeptical.
>
> Anyway, I'll let consensus fall where it may.

+1 to Murray’s comments. I realize that null MAIL FROM on bounce 
messages is a problem for SPF, but relying on HELO is  not a reasonable 
substitute.

-Jim


From nobody Sat Jan 30 13:23:44 2021
Return-Path: <johnl@iecc.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 A631E3A117D for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level: 
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=QuqSi+QG; dkim=pass (2048-bit key) header.d=taugh.com header.b=ybyAyKXA
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 1Bwo9-JINIJR for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:23:41 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 E08F83A117C for <dmarc@ietf.org>; Sat, 30 Jan 2021 13:23:40 -0800 (PST)
Received: (qmail 1546 invoked from network); 30 Jan 2021 21:23:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=608.6015ce5c.k2101; bh=oGZoMQV0zwaHZ4tXQYNG6uJiiqT52tULN2m8LLmwA9A=; b=QuqSi+QGXNdgIeY5HZOMbrHDRAMXiptP2Xx0TVqHEkLCVC/sHpRnCgqH0X6hxoju9RMp8ym//xo/j6yJIz/LYu4ZUR2j7YiFWBPyGofF/MEUHz3CT7JToXN32TGz/uWa/V74Fgf31l7EPe/ngvURqMc5sGCZhFI8fTzfKUWez8xHLPzV20PeEif13YSZGktsNS2VdtTEjEEF0At37ONnbS5XR7+ldcQZH5kRwyxlkrC474FT14AWzGOYpzEd5QzyKSOofF7pLUAgTrxAAONRqmmcudbw5bfP1+pjdq9Yn949qqvUncX4S5qa0DfMTOdbulYdY1SkmjG3rHGkAlPpfQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=608.6015ce5c.k2101; bh=oGZoMQV0zwaHZ4tXQYNG6uJiiqT52tULN2m8LLmwA9A=; b=ybyAyKXA/Jljr6V2OXWA3+CusuooOnwxJhPZF4InokCFZeIce3m0I6s4qbNDUDcRJ+r0Rm8pVcd/+lVQ3FaegTYKDGaIh8n6pg+w3xTzn5I4p9zS3IYmOq6xW/+UuBaEzc6j0QtoP2hg3r0HHGt92s660ozXUqHxE87YtLTM89Gy4BBU31DNRvL8HuGjUdWzQCg9ryZNTYtrrSPty6f9adsCqQiB5PFgnlJMcjVnyrwkUAu8csV/EKO2bVfJYmHAGe7ALHA9Ww77fZH8gsgCuznRESALTgeE8lz2HAqOkDNqa3foeLzqab1aS0tvFpJMTHCsOC6T3za+m+L/cV6TKQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 30 Jan 2021 21:23:39 -0000
Received: by ary.qy (Postfix, from userid 501) id 447316D04763; Sat, 30 Jan 2021 16:23:38 -0500 (EST)
Date: 30 Jan 2021 16:23:38 -0500
Message-Id: <20210130212339.447316D04763@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: fenton@bluepopcorn.net
In-Reply-To: <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wdFAd8xT0tvwYWzT__BBXZUjFfA>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 21:23:43 -0000

In article <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net> you write:
>The issue isn’t the existing use of HELO names, it’s how they could 
>be (mis-)used. The fact that a message sender can put anything there 
>makes HELO basically meaningless.

This is DMARC -- the HELO domain has to match the header From: and there
has to be an SPF record that validates it.

The most plausible case is that it's a bounce messsage

 From: MAILER-DAEMON@mta27.foo.bar.example.com

the MAIL FROM is null, HELO is mta27.foo.bar.example.com, and the SPF
record for mta27.foo.bar.com says that IP is OK.

I don't feel strongly about whether to use the HELO name but it doesn't break anything.

R's,
John


From nobody Sat Jan 30 13:27:19 2021
Return-Path: <dougfoster.emailstandards@gmail.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 2D4083A1184 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:27:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 070SiunHA-m1 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:27:16 -0800 (PST)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531C33A1183 for <dmarc@ietf.org>; Sat, 30 Jan 2021 13:27:16 -0800 (PST)
Received: by mail-vs1-xe34.google.com with SMTP id p20so6932718vsq.7 for <dmarc@ietf.org>; Sat, 30 Jan 2021 13:27:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=RPAsEesQB8hUFVISIMxpXw1+G696ByvCymE6Rqdt/ew=; b=d1p4QRtl+7aWMtcpE5uJgdo6LxMOtdkEhovUtv11Jrtz1FXSG2S/544JoiIWH58kDQ KOtwDDh6ZwA/ZPKKF/zhBH6/IlAVVUfukkPO0KVC09jYB12lD5vB4EIIwMLeL6/BVFXY AxFCMvVPxxZJB9Gq3Jj+G5VPHIfQuW9FEFkRmWFqHkGQhwMpJZUktSENgkNpT4sFg3Bs Oojrn7uBmUuxKV6ReAZVxVMw8saxGAs4l8w1UY3DBqg1hNmZc4RxvzLVqLLyfO1v1PSv 59V4aKmY5HLXIuxa9hA4KMRrHmUebln9Y5zP/cJUWeEZ7umOu+/SjegyDohN78bQjEBN BjfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=RPAsEesQB8hUFVISIMxpXw1+G696ByvCymE6Rqdt/ew=; b=qc0JOVaad0FYPdxgm+itwYV2YJsis1liyMtIEToreDQeL0m3Qi1fqOeMzRnMnbrHdn QQafmKD4XyhQxhMagDL98kSuoPlss6dGy3LH1Yrb8VsLxc2Ji37NJuAXd6cPBFkXAXBk Ja5HJUYFGkC6n6P/PKyqcIqarghPaSnFP+1SIdr4r2P9WBEJIBcc/mzRCbiePZotxJq8 D//0PDph8ILohT4evUr2muL9LZCW4/eZah1IB0Hd1nZb4cDuwnFvXPfmXlRgBQV4G4BD 22taFDtczJOp3hJTcKOcZ+Q5230TqZ2AzgMgwPb+FyV4tF0/WVVB/Jzu7ltTaYFmOk8U Aw8A==
X-Gm-Message-State: AOAM531yBqwc6USTiYnRWbQeZa0wnUkKwRZKu+YjAAHadporXtFgiBnC XLE4zOmETmFfBxaSYY57Oog15PYw6DrOBQM44Sz86rYe
X-Google-Smtp-Source: ABdhPJzxYJroHtQPDYXlcwsOHI+wpuUW0o1k1RVqthJ2dNaPBJv7BnTx9oAi7KU9WaPDq4bRJc+TTEOzGoK4aTjqCQs=
X-Received: by 2002:a67:24c5:: with SMTP id k188mr6078114vsk.16.1612042035190;  Sat, 30 Jan 2021 13:27:15 -0800 (PST)
MIME-Version: 1.0
References: <bef64e7a-571b-a73f-dc91-aa402ca320c8@taugh.com> <1655426.E2olI3CrJK@zini-1880> <c39916f8-33f5-9876-c018-53085f5cc8f5@tana.it> <3776619.NdRDDhGtae@zini-1880> <81ab38a1-4b0a-3845-fc8c-7d49d7850c26@tana.it> <CAL0qLwZgB4iVSudbJeh8NGiKd1232SBTy4YDG6Zj-=LV+1m6Uw@mail.gmail.com> <fc735412-dfa2-20c8-087f-727b13eb3ad5@tana.it> <CAL0qLwbYxTXXXpx11L3f1CqBns=fSRho3C+S7q=-DmiPSvxKvg@mail.gmail.com> <cf51d6d4-0c7b-971d-bcac-743370f16433@tana.it> <CAL0qLwYK7SFfV5fOb7qhy5hVgR15z4HEJbAHv38OFMAfC=_j-Q@mail.gmail.com> <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net>
In-Reply-To: <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 30 Jan 2021 16:27:02 -0500
Message-ID: <CAH48Zfxg5L+W5fx4DPREXwOrvzUvyiy_O3zknuaBH31-_vJ5nA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dee04505ba24c840"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/c6mtss6nancxNcr68D53IrRpXdQ>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 21:27:18 -0000

--000000000000dee04505ba24c840
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

As long as Helo is forward confirmed to the source IP, why is it a risk to
use it to indicate the domain name?

On Sat, Jan 30, 2021, 2:59 PM Jim Fenton <fenton@bluepopcorn.net> wrote:

> On 29 Jan 2021, at 12:30, Murray S. Kucherawy wrote:
>
> > On Fri, Jan 29, 2021 at 3:02 AM Alessandro Vesely <vesely@tana.it>
> > wrote:
> >
> >> I just run a quick test on my current folder.  Out of 3879 messages I
> >> extracted
> >> 944 unique helo names.  721 of these matched the reverse lookup
> >> exactly.
> >> Out
> >> of the 223 remaining, 127 had an SPF pass for the helo identity
> >> anyway.
> >> So in
> >> 96 cases, roughly 10%, the helo name was indeed junk.  Isn't the
> >> remaining
> >> ~90%
> >> something worth considering?
>
> The issue isn=E2=80=99t the existing use of HELO names, it=E2=80=99s how =
they could
> be (mis-)used. The fact that a message sender can put anything there
> makes HELO basically meaningless.
>
> > I am admittedly quite heavily biased against using the HELO/EHLO value
> > for
> > anything.  I have simply never found value in it, probably because at
> > the
> > SMTP layer it's simply a value that gets logged or used in cute ways
> > in the
> > human-readable portion of SMTP.  I seem to recall (but cannot seem to
> > find
> > at the moment) RFC 5321 saying you can't reject HELO/EHLO based on a
> > bogus
> > value, so it's even explicitly not useful to me.
> >
> > Even if it's not junk, there's pretty much always something else on
> > which
> > to hang a pass/fail decision about the apparent authenticity of a
> > message
> > that at least feels safer if not actually being more sound.  Or put
> > another
> > way, if you present to me a DKIM-signed message with a MAIL FROM value
> > and
> > the only thing that passes is an SPF check against HELO, I'm mighty
> > skeptical.
> >
> > Anyway, I'll let consensus fall where it may.
>
> +1 to Murray=E2=80=99s comments. I realize that null MAIL FROM on bounce
> messages is a problem for SPF, but relying on HELO is  not a reasonable
> substitute.
>
> -Jim
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000dee04505ba24c840
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">As long as Helo is forward confirmed to the source IP, wh=
y is it a risk to use it to indicate the domain name?</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jan 30, 2021=
, 2:59 PM Jim Fenton &lt;<a href=3D"mailto:fenton@bluepopcorn.net">fenton@b=
luepopcorn.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 29=
 Jan 2021, at 12:30, Murray S. Kucherawy wrote:<br>
<br>
&gt; On Fri, Jan 29, 2021 at 3:02 AM Alessandro Vesely &lt;<a href=3D"mailt=
o:vesely@tana.it" target=3D"_blank" rel=3D"noreferrer">vesely@tana.it</a>&g=
t; <br>
&gt; wrote:<br>
&gt;<br>
&gt;&gt; I just run a quick test on my current folder.=C2=A0 Out of 3879 me=
ssages I<br>
&gt;&gt; extracted<br>
&gt;&gt; 944 unique helo names.=C2=A0 721 of these matched the reverse look=
up <br>
&gt;&gt; exactly.<br>
&gt;&gt; Out<br>
&gt;&gt; of the 223 remaining, 127 had an SPF pass for the helo identity <b=
r>
&gt;&gt; anyway.<br>
&gt;&gt; So in<br>
&gt;&gt; 96 cases, roughly 10%, the helo name was indeed junk.=C2=A0 Isn&#3=
9;t the <br>
&gt;&gt; remaining<br>
&gt;&gt; ~90%<br>
&gt;&gt; something worth considering?<br>
<br>
The issue isn=E2=80=99t the existing use of HELO names, it=E2=80=99s how th=
ey could <br>
be (mis-)used. The fact that a message sender can put anything there <br>
makes HELO basically meaningless.<br>
<br>
&gt; I am admittedly quite heavily biased against using the HELO/EHLO value=
 <br>
&gt; for<br>
&gt; anything.=C2=A0 I have simply never found value in it, probably becaus=
e at <br>
&gt; the<br>
&gt; SMTP layer it&#39;s simply a value that gets logged or used in cute wa=
ys <br>
&gt; in the<br>
&gt; human-readable portion of SMTP.=C2=A0 I seem to recall (but cannot see=
m to <br>
&gt; find<br>
&gt; at the moment) RFC 5321 saying you can&#39;t reject HELO/EHLO based on=
 a <br>
&gt; bogus<br>
&gt; value, so it&#39;s even explicitly not useful to me.<br>
&gt;<br>
&gt; Even if it&#39;s not junk, there&#39;s pretty much always something el=
se on <br>
&gt; which<br>
&gt; to hang a pass/fail decision about the apparent authenticity of a <br>
&gt; message<br>
&gt; that at least feels safer if not actually being more sound.=C2=A0 Or p=
ut <br>
&gt; another<br>
&gt; way, if you present to me a DKIM-signed message with a MAIL FROM value=
 <br>
&gt; and<br>
&gt; the only thing that passes is an SPF check against HELO, I&#39;m might=
y<br>
&gt; skeptical.<br>
&gt;<br>
&gt; Anyway, I&#39;ll let consensus fall where it may.<br>
<br>
+1 to Murray=E2=80=99s comments. I realize that null MAIL FROM on bounce <b=
r>
messages is a problem for SPF, but relying on HELO is=C2=A0 not a reasonabl=
e <br>
substitute.<br>
<br>
-Jim<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank" rel=3D"noreferrer">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div>

--000000000000dee04505ba24c840--


From nobody Sat Jan 30 13:29:51 2021
Return-Path: <johnl@iecc.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 914CC3A1187 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:29:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level: 
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=j6sySmdP; dkim=pass (2048-bit key) header.d=taugh.com header.b=mgJzgUO/
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 AYmmgN6bhQ_Q for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:29:48 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 F20F43A1186 for <dmarc@ietf.org>; Sat, 30 Jan 2021 13:29:47 -0800 (PST)
Received: (qmail 3215 invoked from network); 30 Jan 2021 21:29:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=c8d.6015cfcb.k2101; bh=LyFGHx69AC+b6G6hJDOJOo0LUunlyiPEbspfn/tOwVc=; b=j6sySmdP7DCCOBaWQMIHY5R8BeBO4KvgnjPVJximZAg/uO24CV9Gs3cFlkGTTGuq9I6KUAqx5d8qQC8IUw/bNhQ/5i1f2CKj3LuSjlZCgzU31nIRVAIJs9YqMPIwoSAfqF4HbUzLdHgHL/Ai358sLGJO9tZxO8lOMHJRyXzyKiPKHL3FU7vZrF39jFX4rB+r5thj/ZUmidWWzek7UR94MBJbQgebXHFHd2WLCnRkpzXLGQExA/n5ysZ7Ih/28NYLi16LbBcK3EeAzeJFUtMBrxhBhngVHZ84gMK34Krz4cJkRRzvrXce6GCvVwiN2ReLyB9V/ydce8UlW4PcOLrR2Q==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=c8d.6015cfcb.k2101; bh=LyFGHx69AC+b6G6hJDOJOo0LUunlyiPEbspfn/tOwVc=; b=mgJzgUO/iyIzj++zrkW//tO7ASgValG5wcjsxQGhVcjh3adr4017Z7dGy5gB9QZe7o0RNCiutIKMh72rNtrOuQRKdhZAQ0/BEYyulWCDBQTuDon5aympryJosfUElGkEybFqX9ET8qHwiVW59pdqF2NB41/RgOHaqzJzfzrwbOcvJGOn1FY+sPXu0lWm/IVwdj7Pm3gQEltzcdRGN/a5NWFl+jSasMPBaYMTywUT7nP/IjDjN6GSp2qjbofJ/zBHhrLNLa3u40emChBlAU9QHPS7bY0KymCTkGkveS9qKDPoOPQ9IP8JgoSS54d0phXe2agyw6ihB9d7hy7PCFikTA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 30 Jan 2021 21:29:46 -0000
Received: by ary.qy (Postfix, from userid 501) id 62E176D0481F; Sat, 30 Jan 2021 16:29:45 -0500 (EST)
Date: 30 Jan 2021 16:29:45 -0500
Message-Id: <20210130212946.62E176D0481F@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
In-Reply-To: <20210130212339.447316D04763@ary.qy>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YKmpHJQkQ4lpWRXxfzwAkU09_jI>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 21:29:50 -0000

In article <20210130212339.447316D04763@ary.qy> you write:
>In article <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net> you write:
>>The issue isn’t the existing use of HELO names, it’s how they could 
>>be (mis-)used. The fact that a message sender can put anything there 
>>makes HELO basically meaningless.
>
>This is DMARC -- the HELO domain has to match the header From: and there
>has to be an SPF record that validates it.
>
>The most plausible case is that it's a bounce messsage
>
> From: MAILER-DAEMON@mta27.foo.bar.example.com
>
>the MAIL FROM is null, HELO is mta27.foo.bar.example.com, and the SPF
>record for mta27.foo.bar.com says that IP is OK.

I wish I could type: ... for mta27.foo.bar.example.com says that the IP is OK.

>I don't feel strongly about whether to use the HELO name but it doesn't break anything.

R's,
John


From nobody Sat Jan 30 13:40:01 2021
Return-Path: <fenton@bluepopcorn.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 599783A1192 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:39:59 -0800 (PST)
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_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 FHO9lgQEn63D for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:39:58 -0800 (PST)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 17B313A1191 for <dmarc@ietf.org>; Sat, 30 Jan 2021 13:39:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=PYBT6Je0IOnIfG6wjV2WZJ+LJZuAc8h/HgkEmX4fi84=; b=erCwNB2nfOgavuBOqHG9l61Gjd XHEx60GYDZVBypAIWuq6jRyEADWB5MUkNuVEt1DQ/y1aUj/RnXK82ChPWqkBhuRj0aUkh5nzEJK7Z Khp6fBBkDXRlNUT8GjTLeNGfVlBtnVkILTDJ0U3jbkd2NCD6MBsnFAgR9+uBdDa7lmzo=;
Received: from [2601:647:4400:1261:30d3:3a9d:66d5:72cc] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1l5xyG-00087T-Oa; Sat, 30 Jan 2021 13:39:57 -0800
From: "Jim Fenton" <fenton@bluepopcorn.net>
To: "John Levine" <johnl@taugh.com>
Cc: dmarc@ietf.org
Date: Sat, 30 Jan 2021 13:39:56 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net>
In-Reply-To: <20210130212339.447316D04763@ary.qy>
References: <20210130212339.447316D04763@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/HQbbwNSrPBoY6R2luBtenfGKIU4>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 21:39:59 -0000

On 30 Jan 2021, at 13:23, John Levine wrote:

> In article <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net> you 
> write:
>> The issue isn’t the existing use of HELO names, it’s how they 
>> could
>> be (mis-)used. The fact that a message sender can put anything there
>> makes HELO basically meaningless.
>
> This is DMARC -- the HELO domain has to match the header From: and 
> there
> has to be an SPF record that validates it.

True, but only if the MAIL FROM address is null and there isn’t a 
valid aligned DKIM signature.

> The most plausible case is that it's a bounce messsage
>
>  From: MAILER-DAEMON@mta27.foo.bar.example.com
>
> the MAIL FROM is null, HELO is mta27.foo.bar.example.com, and the SPF
> record for mta27.foo.bar.com says that IP is OK.

So in this case, why involve the HELO at all? One could just check the 
SPF record of the header From: that it’s trying to align with. Except 
that’s probably SenderID, not SPF.

-Jim


From nobody Sat Jan 30 13:57:52 2021
Return-Path: <johnl@taugh.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 A44453A11B4 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=B4nuguMz; dkim=pass (2048-bit key) header.d=taugh.com header.b=KvgGNapm
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 FEqS8UxknPVZ for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:57:49 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 C269C3A11B2 for <dmarc@ietf.org>; Sat, 30 Jan 2021 13:57:48 -0800 (PST)
Received: (qmail 15074 invoked from network); 30 Jan 2021 21:57:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=3ae0.6015d659.k2101; bh=t12jVdXgZ5ADu3gcBngE5iO0XMcL9psOztSAGtYF4qk=; b=B4nuguMz59fppCioiUPFyDVU4J8j7hvWTx0la1bm7BD41JHUAieqR+MMopJC91YWqeJfUO3ikmW0RPbtHSS21rOfSh3vZTZd/pOnsABUq3bpZPw81QnuecShyK0HLwqeBxMnr7XXtqnGJ2nhm59ldYCyuY0xmnKkyhegpNv0tRKhS158LeeWVYi0TG6+Mo/x+a5eN7v5+r9z+SgFeBzPBNERYKgvDDJrVA59RFAegJK6Z+ZUMmlcrYS6GnurY8SAe15x5e50mo55MQAHALFyixgHzljkuIH1DVAOBhWNK2uzr1yklbrps4s8h82qOkBsNAcSYFk3h0x/6obx+6xN2A==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=3ae0.6015d659.k2101; bh=t12jVdXgZ5ADu3gcBngE5iO0XMcL9psOztSAGtYF4qk=; b=KvgGNapmpmjwSFA6LaxAk6OVu9LRFMbBIZcIDqEB+Lk5U8KgkUm7DEa9siSHMyClcIgEtmlybsgRgFggG3vYfQFJcqJBZEbLXGPw7+A16PSZA1+pZgcPfl3x3bw8IBjUcn15XHWWEG/j5dBFecfwKud9r3VEZLcJ/AjtppTSNLf8ZHkmwZZFiFkv86cPEDOa7XCKKWeIQdiMj7FQDX1Qrc1X2JFgeEZ/K9aty1OTXhT+TiRCT7KJ79FRP8FL6Cr221UufTy3M/TUt2hH9986rNAhr/gQ/xkvH+FwjMfel3AKTSM6bTYnJFLSCR0l6BFoox3oFkhXGFX5lB+yhh8eFg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 30 Jan 2021 21:57:45 -0000
Received: by ary.qy (Postfix, from userid 501) id CFF906D04E33; Sat, 30 Jan 2021 16:57:44 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 7FCB46D04E15; Sat, 30 Jan 2021 16:57:44 -0500 (EST)
Date: 30 Jan 2021 16:57:44 -0500
Message-ID: <1edea785-2420-9812-643-c38bc4bf9577@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Jim Fenton" <fenton@bluepopcorn.net>, "John Levine" <johnl@taugh.com>
Cc: dmarc@ietf.org
In-Reply-To: <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net>
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1702332684-1612043864=:95229"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YT4tVxYjNq2MeeQL_AYq8VagIhA>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 21:57:51 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1702332684-1612043864=:95229
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

>> This is DMARC -- the HELO domain has to match the header From: and there
>> has to be an SPF record that validates it.
>
> True, but only if the MAIL FROM address is null and there isn’t a valid 
> aligned DKIM signature.

True, but I don't see why that matters.

>> The most plausible case is that it's a bounce messsage
>>
>>  From: MAILER-DAEMON@mta27.foo.bar.example.com
>> 
>> the MAIL FROM is null, HELO is mta27.foo.bar.example.com, and the SPF
>> record for mta27.foo.bar.com says that IP is OK.
>
> So in this case, why involve the HELO at all? One could just check the SPF 
> record of the header From: that it’s trying to align with. Except that’s 
> probably SenderID, not SPF.

Because that's how DMARC works.  The header From has to match a DKIM or 
SPF identity.

Part of the problem here is that DMARC generally sits on top of an SPF 
library which doesn't tell you how it got its result.  My DMARC code just 
calls the SPF library and uses the result.  I suppose I could put in a 
hack to say don't use the SPF result if the MAIL FROM is null, but I don't 
think that's what 7489 says.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
--0-1702332684-1612043864=:95229--


From nobody Sat Jan 30 14:02:20 2021
Return-Path: <fenton@bluepopcorn.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 38AB73A11BD for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 14:02:19 -0800 (PST)
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_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 64hkfudZE8qX for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 14:02:18 -0800 (PST)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 617E03A11BB for <dmarc@ietf.org>; Sat, 30 Jan 2021 14:02:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=mpUOHkFqTlWdOFx4TUqLz13QdsPaLL7VhSPOGlbeQxM=; b=sH/1FrRNM3Xn2NlnwrtPZIrvkn 11BZ2qNxi8Bhwagw6T8ywnNywe5T7Oi3a01YD3iC3wM2lkDecDXma6eRMYRgDpSjHJJRHQqNvMuRP CffMeMBalhide2svaOUROy9CAkp3YboWa+Fb4wVNWbi1z0p+vAZRnrefr+rfrI/CTfuw=;
Received: from [2601:647:4400:1261:30d3:3a9d:66d5:72cc] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1l5yJt-0008AF-VK; Sat, 30 Jan 2021 14:02:18 -0800
From: "Jim Fenton" <fenton@bluepopcorn.net>
To: "John R Levine" <johnl@taugh.com>
Cc: dmarc@ietf.org
Date: Sat, 30 Jan 2021 14:02:17 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <892F89B5-F86C-4BAD-A88F-C7A48B930D04@bluepopcorn.net>
In-Reply-To: <1edea785-2420-9812-643-c38bc4bf9577@taugh.com>
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net> <1edea785-2420-9812-643-c38bc4bf9577@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZEakWQ7ZGoGh3yP6ueKXUCSk5Vo>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 22:02:19 -0000

On 30 Jan 2021, at 13:57, John R Levine wrote:

>>> This is DMARC -- the HELO domain has to match the header From: and 
>>> there
>>> has to be an SPF record that validates it.
>>
>> True, but only if the MAIL FROM address is null and there isn’t a 
>> valid aligned DKIM signature.
>
> True, but I don't see why that matters.

Just confirming the context of your earlier statement.

> Because that's how DMARC works.  The header From has to match a DKIM 
> or SPF identity.
>
> Part of the problem here is that DMARC generally sits on top of an SPF 
> library which doesn't tell you how it got its result.  My DMARC code 
> just calls the SPF library and uses the result.  I suppose I could put 
> in a hack to say don't use the SPF result if the MAIL FROM is null, 
> but I don't think that's what 7489 says.

Are changes to 7489 off the table here? I didn’t know.

-Jim


From nobody Sat Jan 30 14:09:14 2021
Return-Path: <johnl@taugh.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 C90DF3A11CB for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 14:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=eT8solQz; dkim=pass (2048-bit key) header.d=taugh.com header.b=mXdDDYIs
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 212p5j59IquS for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 14:09:10 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 6A6463A11CA for <dmarc@ietf.org>; Sat, 30 Jan 2021 14:09:10 -0800 (PST)
Received: (qmail 17414 invoked from network); 30 Jan 2021 22:09:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=437b.6015d903.k2101; bh=a/vQGy9CogTrDd+rmIyrwcVvjdn9s3nZosN3rmPHphI=; b=eT8solQzOQQBGcTVRJ2DJa4otBVxQylwgtShDBM+K+0kAU4wqO67fzyapjonbfqmS5AchjB6R4G8EqGWWEDRLma/RAN7spvnUBYGrvfuGtAoso1NdBHCIPAffrrdaU0nsabtkzPI41c+rJVI3eGiklYPmcks79ynPVVCuFpdldsgAmcIWcyN7GegPjAPGY4e8JVnz1JqpuKnxaVlur6NJnVixZeWXJJkg5CtUYAf97FppNgIIZtoINiECln5Wz2eFvo5m8iGUytmYbVtKnAeXMlBQGWbApXxBgqYPL28rAR1ZO0GPM6+ykLSnhI+6DS0LJPXvLZSaa6z39/zgdubHg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=437b.6015d903.k2101; bh=a/vQGy9CogTrDd+rmIyrwcVvjdn9s3nZosN3rmPHphI=; b=mXdDDYIsYVQvqO8bArdEORCEy7ngU+bbaE+R/4LL0isr1w1W8H0QzQVQ3aGVnRYS8oVskEa1MaX3SwJfXVLsuQv3ivJVHI8U1UwI8wo4TLT7hTYibdr4X1fH/U+KwWFebWtk1zI/1x5LA7ZOw3oRGo164eqjypXHVZwkq5VryRgaFiDCyl/IvbgN8ZBIvzM8Bi/dgzqpVeLeNNNEYXF0PR3tRtM0Jnks8SDlxUaPkKr0m4ZRCLuCoHX6EBLEBNkPX5RsRxF/OP4NXARzjGUm+b40SqTOTQDgD0RQHtBwye83hPcNb+fB7xKhz3uy8E+CWxNSCFDm/65ecbv/eZ9NKw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 30 Jan 2021 22:09:06 -0000
Received: by ary.qy (Postfix, from userid 501) id 8D1516D05156; Sat, 30 Jan 2021 17:09:06 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 51BCD6D05138; Sat, 30 Jan 2021 17:09:06 -0500 (EST)
Date: 30 Jan 2021 17:09:06 -0500
Message-ID: <ae9761b9-1560-da7e-89e5-34f570d24fc5@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Jim Fenton" <fenton@bluepopcorn.net>
Cc: dmarc@ietf.org
In-Reply-To: <892F89B5-F86C-4BAD-A88F-C7A48B930D04@bluepopcorn.net>
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net> <1edea785-2420-9812-643-c38bc4bf9577@taugh.com> <892F89B5-F86C-4BAD-A88F-C7A48B930D04@bluepopcorn.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1804830107-1612044546=:95381"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WWh1thKaemfqiaKtQAFG78Vea6Q>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 22:09:13 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1804830107-1612044546=:95381
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Sat, 30 Jan 2021, Jim Fenton wrote:
>> Part of the problem here is that DMARC generally sits on top of an SPF 
>> library which doesn't tell you how it got its result.  My DMARC code just 
>> calls the SPF library and uses the result.  I suppose I could put in a hack 
>> to say don't use the SPF result if the MAIL FROM is null, but I don't think 
>> that's what 7489 says.
>
> Are changes to 7489 off the table here? I didn’t know.

They are certainly possible, but I would want a good reason.  At this 
point, SPF using HELO seems harmless so I don't see a reason to disallow 
it.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
--0-1804830107-1612044546=:95381--


From nobody Sat Jan 30 14:44:54 2021
Return-Path: <mike@fresheez.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 802453A1201 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 14:44:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level: 
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.com
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 scJjB3wU9MJK for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 14:44:51 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E6283A1200 for <dmarc@ietf.org>; Sat, 30 Jan 2021 14:44:51 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id y205so8986706pfc.5 for <dmarc@ietf.org>; Sat, 30 Jan 2021 14:44:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=z3fPP+RD3AFlBM+Bjx+XOnN+3Dncn6tz0k0ZwqNdhJw=; b=P283X49k/jZ6MzV99YfXT0kWAid91lzpsnFML/jZTpfvJBhZjp775yPTqyvGrNfR4e 3zyJnomYCY4boeSv5TFnFmVmGKaUSuofTMTE7kMaZDWGt21CV5akqV5n/tQVKnoBlFkB /TsFxpXAIK/pUeofhPiCY8jM59wrTzcZ6bi6LH+UOmlVTHOrqbtutyLNXaw4LVNPRkOZ EzhQcE/ElprbOrdBdFe6c+k8PjKqpPjaD8WSWZs1aZayY/pAk2l+C4XRHMHdutWOOMmc 1plrDeTb/FoZAA2w/wZYdULmE98H/0iTLW+arOvKVGdjP+QKThiY14R1gLEZzw0tgGQR IYCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=z3fPP+RD3AFlBM+Bjx+XOnN+3Dncn6tz0k0ZwqNdhJw=; b=XEwfNG+EJ9ci8FXgQO8B5tzCKOsxa1BPOq235awBqBizREvzlqc4cw+9MPsopRcXKL JPRDQaRxO7ukQ9OZZuFI5zjbZlH2BfSTlG5K1fpUBo1sOfNDh4jO13bOI1sXzUBSYPGc zFttIoz08g9KU18NyxOE7Pn6ZugyeCUxhW9aBu/BcafmoSKu03qB5bWj2hpx5c2Cl9EI OMYH1evkYXlqBYW5CaB0PA5AmlQv5Vi8/SP/LiEho3/l9rnBvCwe63qR/CcG9k7Jp7WG JIjg3VdZoa8/asoB+Wf66CQ4hcnNvyNn2asY/sAploAvezTDUTPycFVKlHFdRBChg8h5 ga3Q==
X-Gm-Message-State: AOAM530Iq+yUTD6PZlPUPTicvgSTdfOzQChNG5GCQ8gWbA+JObYRc8eM pxfy9Z78ZQOLJUykfORlywqVslezpHBkhw==
X-Google-Smtp-Source: ABdhPJy7UPh1zkUGCGwx+aZvNFklH4zXlpuNl38nV6ksIvSBiJqDSzD2pUuqs1xtZ7wynz3yT4u2hQ==
X-Received: by 2002:a62:b410:0:b029:1a4:7868:7e4e with SMTP id h16-20020a62b4100000b02901a478687e4emr10123238pfn.62.1612046690351;  Sat, 30 Jan 2021 14:44:50 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id g17sm13259053pgg.78.2021.01.30.14.44.49 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 30 Jan 2021 14:44:49 -0800 (PST)
To: dmarc@ietf.org
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net> <1edea785-2420-9812-643-c38bc4bf9577@taugh.com> <892F89B5-F86C-4BAD-A88F-C7A48B930D04@bluepopcorn.net> <ae9761b9-1560-da7e-89e5-34f570d24fc5@taugh.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <9190a914-f037-8f44-d3a0-a454deab6371@mtcc.com>
Date: Sat, 30 Jan 2021 14:44:47 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <ae9761b9-1560-da7e-89e5-34f570d24fc5@taugh.com>
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/mr0S_znA4-vsfnqkg5PISklBxMY>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 22:44:53 -0000

On 1/30/21 2:09 PM, John R Levine wrote:
> On Sat, 30 Jan 2021, Jim Fenton wrote:
>>> Part of the problem here is that DMARC generally sits on top of an 
>>> SPF library which doesn't tell you how it got its result.  My DMARC 
>>> code just calls the SPF library and uses the result.  I suppose I 
>>> could put in a hack to say don't use the SPF result if the MAIL FROM 
>>> is null, but I don't think that's what 7489 says.
>>
>> Are changes to 7489 off the table here? I didn’t know.
>
> They are certainly possible, but I would want a good reason.  At this 
> point, SPF using HELO seems harmless so I don't see a reason to 
> disallow it.
>
>
 From a security standpoint, I wonder why you would want to allow 
something you know can be gamed. But that is probably more a question 
for SPF itself.

Mike


From nobody Sat Jan 30 15:06:22 2021
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 EF7FA3A1221 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 15:06:20 -0800 (PST)
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=ZqPhOb1g; dkim=pass (2048-bit key) header.d=kitterman.com header.b=NvOrx4iK
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 Cu6ubW6rWE15 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 15:06:19 -0800 (PST)
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 797B73A1220 for <dmarc@ietf.org>; Sat, 30 Jan 2021 15:06:19 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 00273F802B1 for <dmarc@ietf.org>; Sat, 30 Jan 2021 18:06:17 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1612047977; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=3UGFwuzsP3iznrRI14OrkaQcoVFn3wdvtlBanBvAx3U=; b=ZqPhOb1gbZEkullMfRtyZIGk+NYA7Ci+oTUywf8SOKq/r77WbvuwUGv/dSIiq/5aksWoj e/YnJYbQavk0p6pAg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1612047977; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=3UGFwuzsP3iznrRI14OrkaQcoVFn3wdvtlBanBvAx3U=; b=NvOrx4iK6K+V60mRCTun9MaNXIOZNozYrXeaIDllsH93s3D2XkQzDFkh0yz8YQS/1JG3q d00c7IZgEXnrXtjEQ0KRGQbTSV9aRfSFVoFSvHfuo/KTcqHbFTpjj3NGHoHKxKSJBzwQkvt 6Kr72MngfMLYgnqf8qvlUBSlLXdQ0yOqyytFigFf68uuRitRh54iFqFdyE6RByaO1tPPCcd IJBEAUSp/AWNOa4Pgd6WZ+5GGwJl2wXPCYUte3yD9WtRzRt7bt+VD7M0f+nQspVABo5otj9 q4GOmAbvO2Sf/T+oe2qs3vOYSwimDyoDmuq1dtgtAwmuS86qR9i9Rl1bj21g==
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 6BA38F80208 for <dmarc@ietf.org>; Sat, 30 Jan 2021 18:06:17 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sat, 30 Jan 2021 18:06:17 -0500
Message-ID: <1885308.pJOiFY7FxO@zini-1880>
In-Reply-To: <9190a914-f037-8f44-d3a0-a454deab6371@mtcc.com>
References: <20210130212339.447316D04763@ary.qy> <ae9761b9-1560-da7e-89e5-34f570d24fc5@taugh.com> <9190a914-f037-8f44-d3a0-a454deab6371@mtcc.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/E2Xto2z8v2sg81v2ZI844bmZppA>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 23:06:21 -0000

On Saturday, January 30, 2021 5:44:47 PM EST Michael Thomas wrote:
> On 1/30/21 2:09 PM, John R Levine wrote:
> > On Sat, 30 Jan 2021, Jim Fenton wrote:
> >>> Part of the problem here is that DMARC generally sits on top of an
> >>> SPF library which doesn't tell you how it got its result.  My DMARC
> >>> code just calls the SPF library and uses the result.  I suppose I
> >>> could put in a hack to say don't use the SPF result if the MAIL FROM
> >>> is null, but I don't think that's what 7489 says.
> >>=20
> >> Are changes to 7489 off the table here? I didn=E2=80=99t know.
> >=20
> > They are certainly possible, but I would want a good reason.  At this
> > point, SPF using HELO seems harmless so I don't see a reason to
> > disallow it.
>=20
>  From a security standpoint, I wonder why you would want to allow
> something you know can be gamed. But that is probably more a question
> for SPF itself.

=46rom a DMARC perspective, I don't think it can be in any useful way.  Agr=
ee=20
that digging into it further is more about SPF itself, presumably OT here.

Scott K



From nobody Sat Jan 30 16:45:03 2021
Return-Path: <dougfoster.emailstandards@gmail.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 C4FBC3A129A for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 16:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 iRS4CXEfppCW for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 16:45:00 -0800 (PST)
Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5A903A1298 for <dmarc@ietf.org>; Sat, 30 Jan 2021 16:44:59 -0800 (PST)
Received: by mail-ua1-x933.google.com with SMTP id g13so4599024uaw.5 for <dmarc@ietf.org>; Sat, 30 Jan 2021 16:44:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=s4BBYD5gGb98tnuippM/0H3Z1dBou3Q+cB035AqBHiI=; b=YoTQcAiZKlBIWIXaEYYa7ShW/AbUwCkEpdvwcYgkBlE4zQ6I4A9x5Qdib4qqcciD7u kt5DPo7Xv59aQGmbXAgp/884mWRzcCyiLZVYUd9FHHzW1A2+Xdc/i/1rUCO3VMW2eGmW nwcViPkFaQ3g6Kw0VU28Fy1h9H9YHuYB5U+jdkiYVOLCTHvpBHZr7OYO1W4s8a3TcU3c HmdTpFsnc7Ca06abu0dNV/CoM+BITnj3gMZwzlrVNyWfgT4l1tQgV+YY0ORB6GcHbNH1 CDZ2lZQWwNez4JwasNuSyZD350CuloMWceZH73YZ4D1Sf1kxvQwGh4pRZGdpChD9kKyO lyWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=s4BBYD5gGb98tnuippM/0H3Z1dBou3Q+cB035AqBHiI=; b=k686oSvrtr50GNiy22F11weE7YpX1pu1tCjUIAmXU1o5qMCJbha7P6ywaU+o/tXsFh UiygQgHyRSDcbGpJ3PKC+jthKnynV8J5GBoAGxazXp0PsdzQme6TSl04h3gaUKArQzTQ qAzUJuZNlIMCZk5gzAngDk/OUr1y+x8poCIZV2cHK4fbP30ATOZ5mKJYfS0W3kqDMEkE pON05Lj9E37OOPt4XXz4eWv2k8gOx4dyW9Gb7NKO5WAizlV4muZMdvvc740zd155/YrR QekMHyb7YG0HhBHWQPJAUQHY99/ssFQps32zZDZesq1oMu4felxZ+6bGnSyb+w6RbeX0 12ww==
X-Gm-Message-State: AOAM532z41S/jPsULWW7ZG+2rJDK/61xlQ+xV0oWGC0YKVjz/L8fbGK/ vBIH1NFM4WDagUn6T7hjsC2Ze/uQnhNs8bA7UkANRGS1
X-Google-Smtp-Source: ABdhPJxF9gnxFZNd+RVgl3k+jLn9Mi2L6axGreGQGADsXE9q+IGeTn01cWTDHqhw3At60gPQmZ8+m29xdVG3zmqJmfs=
X-Received: by 2002:ab0:5e6:: with SMTP id e93mr6102497uae.109.1612053898639;  Sat, 30 Jan 2021 16:44:58 -0800 (PST)
MIME-Version: 1.0
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net> <1edea785-2420-9812-643-c38bc4bf9577@taugh.com> <892F89B5-F86C-4BAD-A88F-C7A48B930D04@bluepopcorn.net> <ae9761b9-1560-da7e-89e5-34f570d24fc5@taugh.com> <9190a914-f037-8f44-d3a0-a454deab6371@mtcc.com>
In-Reply-To: <9190a914-f037-8f44-d3a0-a454deab6371@mtcc.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 30 Jan 2021 19:44:45 -0500
Message-ID: <CAH48ZfxUG2QL=GO3Rnya2uXTROYy=qWuoaN41Lk-ujPGZH8Exg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fcbf6305ba278be6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/36-pq7dmdMdlfrGGlfKimL5eaIk>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 31 Jan 2021 00:45:02 -0000

--000000000000fcbf6305ba278be6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Anything can be gamed if it is trusted without verification. But verifiable
data is hard to game.   If you ensure that Helo can be forward confirmed
before considering it trusted, how is it risky?


On Sat, Jan 30, 2021, 5:45 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 1/30/21 2:09 PM, John R Levine wrote:
> > On Sat, 30 Jan 2021, Jim Fenton wrote:
> >>> Part of the problem here is that DMARC generally sits on top of an
> >>> SPF library which doesn't tell you how it got its result.  My DMARC
> >>> code just calls the SPF library and uses the result.  I suppose I
> >>> could put in a hack to say don't use the SPF result if the MAIL FROM
> >>> is null, but I don't think that's what 7489 says.
> >>
> >> Are changes to 7489 off the table here? I didn=E2=80=99t know.
> >
> > They are certainly possible, but I would want a good reason.  At this
> > point, SPF using HELO seems harmless so I don't see a reason to
> > disallow it.
> >
> >
>  From a security standpoint, I wonder why you would want to allow
> something you know can be gamed. But that is probably more a question
> for SPF itself.
>
> Mike
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000fcbf6305ba278be6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Anything can be gamed if it is trusted without verificati=
on. But verifiable data is hard to game.=C2=A0 =C2=A0If you ensure that Hel=
o can be forward confirmed before considering it trusted, how is it risky?<=
div dir=3D"auto"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Sat, Jan 30, 2021, 5:45 PM Michael Thomas &lt=
;<a href=3D"mailto:mike@mtcc.com">mike@mtcc.com</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><br>
On 1/30/21 2:09 PM, John R Levine wrote:<br>
&gt; On Sat, 30 Jan 2021, Jim Fenton wrote:<br>
&gt;&gt;&gt; Part of the problem here is that DMARC generally sits on top o=
f an <br>
&gt;&gt;&gt; SPF library which doesn&#39;t tell you how it got its result.=
=C2=A0 My DMARC <br>
&gt;&gt;&gt; code just calls the SPF library and uses the result.=C2=A0 I s=
uppose I <br>
&gt;&gt;&gt; could put in a hack to say don&#39;t use the SPF result if the=
 MAIL FROM <br>
&gt;&gt;&gt; is null, but I don&#39;t think that&#39;s what 7489 says.<br>
&gt;&gt;<br>
&gt;&gt; Are changes to 7489 off the table here? I didn=E2=80=99t know.<br>
&gt;<br>
&gt; They are certainly possible, but I would want a good reason.=C2=A0 At =
this <br>
&gt; point, SPF using HELO seems harmless so I don&#39;t see a reason to <b=
r>
&gt; disallow it.<br>
&gt;<br>
&gt;<br>
=C2=A0From a security standpoint, I wonder why you would want to allow <br>
something you know can be gamed. But that is probably more a question <br>
for SPF itself.<br>
<br>
Mike<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank" rel=3D"noreferrer">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div>

--000000000000fcbf6305ba278be6--


From nobody Sat Jan 30 18:27:55 2021
Return-Path: <dougfoster.emailstandards@gmail.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 220F13A1399 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 18:27:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yMRze3MHeJOD for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 18:27:52 -0800 (PST)
Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 369E73A1398 for <dmarc@ietf.org>; Sat, 30 Jan 2021 18:27:52 -0800 (PST)
Received: by mail-vk1-xa2a.google.com with SMTP id d6so3112492vkb.13 for <dmarc@ietf.org>; Sat, 30 Jan 2021 18:27:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=7SgMAVYXC1tF/9tE0YlbVLdVz6b0tiyRoKBMhb9QOo0=; b=VnEUfe7jy/eSz1y66Z13GgCIgp15q5DHF1QO20hOFxnwOskDIC+Mzdfr5P+akbW6H+ POqs3DAI1DwQQyTY3HeVSLegpUPPGariPPMKCMvtWqV6xaYNE35mZD7epnfWDqS0zDUZ 4MxcrIjs6cSQlXkEm2XUTKXxdc5CO+/Bospi/rTEW39MwQ1Mb9rtMYARWvhlfwstoQ4n Wd9CivCjI7gF0737OiLp+jrpnIw6UY2VBkE6AZ22ZaImuXxVzbdDg/1fankLD+1ON80g ObZiLV7xS7QnzmWxV/Mk3uuNeNs0uO5K3QVuLQq/+jlEZQ58QI26uPMeZ/MJhl2bQHW3 hSjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=7SgMAVYXC1tF/9tE0YlbVLdVz6b0tiyRoKBMhb9QOo0=; b=Riw1LysfC9X3TZ/kGbDV705nOaOdJVpoVxy72ZDBvgi0K3OBcodwzJD/Qx3DUn4aya 2h9WGBiTpjrwJmMTCeUsRaY4JPKMeYWEDYZ7l2m28VIB3co/iBJBfUoJvR4ZiESuF6PS ASSQDCK+rq4LhDQvNTJeF6+UWm7oXCFzvFWPhUrS+89u9GhQAIvZRPFE9rV9GjpT1mgN T3qEbv0C83rsTQbMrQBzEQ55DV8Ex4DD5+mSq3hVed42nG0Xz55BfF5ng5UKVzYz7fEE Z+p1pOX+jydD+G4nIypuNsMjFgBAAImo2p0bKplCES7Yzq5mio3z+i9PE4XmztnTilbV HYGA==
X-Gm-Message-State: AOAM530oWAbh0F4evq6DLf+61V6llu5FRfg8COHddBv4E9gTsUSLT/tK falc5LFkswG23BkieiDebDHjgH/CIedxX0MZqXpWEp3iayo=
X-Google-Smtp-Source: ABdhPJw1eT20f2bPzo8tO1u3da/v1r4ZIeNtQVkfoCDIojLF1dj6VCQXItjK9vWf25/N5bjA+Hu+6+csmguqV3i6GKc=
X-Received: by 2002:a1f:3112:: with SMTP id x18mr6495035vkx.4.1612060070808; Sat, 30 Jan 2021 18:27:50 -0800 (PST)
MIME-Version: 1.0
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net> <1edea785-2420-9812-643-c38bc4bf9577@taugh.com> <892F89B5-F86C-4BAD-A88F-C7A48B930D04@bluepopcorn.net> <ae9761b9-1560-da7e-89e5-34f570d24fc5@taugh.com> <9190a914-f037-8f44-d3a0-a454deab6371@mtcc.com> <CAH48ZfxUG2QL=GO3Rnya2uXTROYy=qWuoaN41Lk-ujPGZH8Exg@mail.gmail.com>
In-Reply-To: <CAH48ZfxUG2QL=GO3Rnya2uXTROYy=qWuoaN41Lk-ujPGZH8Exg@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 30 Jan 2021 21:27:41 -0500
Message-ID: <CAH48Zfxdv+9nPYu9xdhJ9nYakicVUdT9hKQ766b11st7YtEgTw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e08f2105ba28fbb8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/q8qIsUu5ri06KBF6fzCjUdRxGBQ>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 31 Jan 2021 02:27:54 -0000

--000000000000e08f2105ba28fbb8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

The SMTP address and the HELO name are very similar in their trust
characteristics.
Both of them can be manipulated maliciously, but both can be verified with
similar techniques:   Using a DNS lookup to associate the name
assertion with the Source IP.
(We all know that the Source IP can be manipulated with a NAT device
sitting outside a network perimeter, but we ignore that possibility.   If
it is happening, there are worse things than email verification occurring.)

We do know that Reverse DNS is often outside the control of the mail
domain, so it is actually a less reliable indicator of domain ownership
than Helo.

Overall, the SPF design seems very intuitive and defensible.
I think it is unrealistic to expect rapid implementation of DKIM signatures
on null-address messages, and HELO is a good substitute.  Nor does it seem
necessary.  I see no problem using HELO in my DMARC evaluations when the
SMTP address is null.

My data, cited previously, indicates that HELO can be useful for both
blacklisting and whitelisting.   It should not be ignored.

Doug Foster
.

On Sat, Jan 30, 2021 at 7:44 PM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> Anything can be gamed if it is trusted without verification. But
> verifiable data is hard to game.   If you ensure that Helo can be forward
> confirmed before considering it trusted, how is it risky?
>
>
> On Sat, Jan 30, 2021, 5:45 PM Michael Thomas <mike@mtcc.com> wrote:
>
>>
>> On 1/30/21 2:09 PM, John R Levine wrote:
>> > On Sat, 30 Jan 2021, Jim Fenton wrote:
>> >>> Part of the problem here is that DMARC generally sits on top of an
>> >>> SPF library which doesn't tell you how it got its result.  My DMARC
>> >>> code just calls the SPF library and uses the result.  I suppose I
>> >>> could put in a hack to say don't use the SPF result if the MAIL FROM
>> >>> is null, but I don't think that's what 7489 says.
>> >>
>> >> Are changes to 7489 off the table here? I didn=E2=80=99t know.
>> >
>> > They are certainly possible, but I would want a good reason.  At this
>> > point, SPF using HELO seems harmless so I don't see a reason to
>> > disallow it.
>> >
>> >
>>  From a security standpoint, I wonder why you would want to allow
>> something you know can be gamed. But that is probably more a question
>> for SPF itself.
>>
>> Mike
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>

--000000000000e08f2105ba28fbb8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The SMTP address and the HELO name are very similar in the=
ir trust characteristics.<div>Both of them can be manipulated maliciously, =
but both can be verified with similar techniques:=C2=A0 =C2=A0Using a DNS l=
ookup to associate the name assertion=C2=A0with the Source IP.</div><div>(W=
e all know that the Source IP can be manipulated with a NAT device sitting =
outside a network perimeter, but we ignore that possibility.=C2=A0 =C2=A0If=
 it is happening, there are worse things than email verification occurring.=
)</div><div><br></div><div>We do know that Reverse DNS is often outside=C2=
=A0the control of the mail domain, so it is actually a less reliable indica=
tor of domain ownership than Helo.</div><div><br></div><div>Overall, the SP=
F design seems very intuitive and defensible.=C2=A0 =C2=A0</div><div>I thin=
k it is unrealistic to expect rapid implementation of DKIM signatures on nu=
ll-address messages, and HELO is a good substitute.=C2=A0 Nor does it seem =
necessary.=C2=A0 I see no problem using HELO in my DMARC evaluations when t=
he SMTP address is null.=C2=A0</div><div><br></div><div><div>My data, cited=
 previously, indicates that HELO can be useful for both blacklisting and wh=
itelisting.=C2=A0 =C2=A0It should not be ignored.</div><div><br></div><div>=
Doug Foster</div><div>.<br></div></div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jan 30, 2021 at 7:44 PM Doug=
las Foster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougf=
oster.emailstandards@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div dir=3D"auto">Anything can be gamed if it=
 is trusted without verification. But verifiable data is hard to game.=C2=
=A0 =C2=A0If you ensure that Helo can be forward confirmed before consideri=
ng it trusted, how is it risky?<div dir=3D"auto"><br></div></div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jan 30, =
2021, 5:45 PM Michael Thomas &lt;<a href=3D"mailto:mike@mtcc.com" target=3D=
"_blank">mike@mtcc.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><br>
On 1/30/21 2:09 PM, John R Levine wrote:<br>
&gt; On Sat, 30 Jan 2021, Jim Fenton wrote:<br>
&gt;&gt;&gt; Part of the problem here is that DMARC generally sits on top o=
f an <br>
&gt;&gt;&gt; SPF library which doesn&#39;t tell you how it got its result.=
=C2=A0 My DMARC <br>
&gt;&gt;&gt; code just calls the SPF library and uses the result.=C2=A0 I s=
uppose I <br>
&gt;&gt;&gt; could put in a hack to say don&#39;t use the SPF result if the=
 MAIL FROM <br>
&gt;&gt;&gt; is null, but I don&#39;t think that&#39;s what 7489 says.<br>
&gt;&gt;<br>
&gt;&gt; Are changes to 7489 off the table here? I didn=E2=80=99t know.<br>
&gt;<br>
&gt; They are certainly possible, but I would want a good reason.=C2=A0 At =
this <br>
&gt; point, SPF using HELO seems harmless so I don&#39;t see a reason to <b=
r>
&gt; disallow it.<br>
&gt;<br>
&gt;<br>
=C2=A0From a security standpoint, I wonder why you would want to allow <br>
something you know can be gamed. But that is probably more a question <br>
for SPF itself.<br>
<br>
Mike<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" rel=3D"noreferrer" target=3D"_blank">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div>
</blockquote></div>

--000000000000e08f2105ba28fbb8--


From nobody Sun Jan 31 03:00:10 2021
Return-Path: <johnl@taugh.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 177983A0BBC for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 03:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 bHaqkIcS4muh for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 03:00:07 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 8B50A3A0BB2 for <dmarc@ietf.org>; Sun, 31 Jan 2021 03:00:07 -0800 (PST)
Received: (qmail 91569 invoked by uid 100); 31 Jan 2021 11:00:06 -0000
Date: 31 Jan 2021 10:59:42 -0000
Message-ID: <20210131105942.91540.qmail@submit.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rSUVENBte6t4_QVIfi4dDN00rLQ>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jan 31 06:00:05 2021
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, 31 Jan 2021 11:00:09 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 36 (20.0%) | 363471 (22.2%) | Michael Thomas <mike@mtcc.com>
 36 (20.0%) | 202286 (12.4%) | Alessandro Vesely <vesely@tana.it>
 30 (16.7%) | 154197 ( 9.4%) | John Levine <johnl@taugh.com>
 17 ( 9.4%) | 181672 (11.1%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
 15 ( 8.3%) | 116957 ( 7.2%) | Murray S. Kucherawy <superuser@gmail.com>
 10 ( 5.6%) | 157962 ( 9.7%) | Todd Herr <todd.herr@valimail.com>
  8 ( 4.4%) | 134471 ( 8.2%) | Seth Blank <seth@valimail.com>
  6 ( 3.3%) | 152864 ( 9.3%) | Brotman, Alex <alex_brotman@comcast.com>
  6 ( 3.3%) |  43134 ( 2.6%) | Scott Kitterman <sklist@kitterman.com>
  4 ( 2.2%) |  29534 ( 1.8%) | Steven M Jones <smj@crash.com>
  3 ( 1.7%) |  14851 ( 0.9%) | Jim Fenton <fenton@bluepopcorn.net>
  2 ( 1.1%) |  26391 ( 1.6%) | Dave Crocker <dcrocker@gmail.com>
  2 ( 1.1%) |  22453 ( 1.4%) | Tim Wicinski <tjw.ietf@gmail.com>
  2 ( 1.1%) |  14895 ( 0.9%) | Kurt Andersen (b) <kboth@drkurt.com>
  1 ( 0.6%) |   8256 ( 0.5%) | Дилян Палаузов <dilyan.palauzov@aegee.org>
  1 ( 0.6%) |   6754 ( 0.4%) | Matt V <ietfdmarc@emailkarma.net>
  1 ( 0.6%) |   5039 ( 0.3%) | John R. Levine <johnl@iecc.com>


From nobody Sun Jan 31 03:31:03 2021
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 8C92A3A0C46 for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 03:31:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.421
X-Spam-Level: 
X-Spam-Status: No, score=-4.421 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_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 r3fc9aaVQT4i for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 03:31:01 -0800 (PST)
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 215203A0C44 for <dmarc@ietf.org>; Sun, 31 Jan 2021 03:31:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612092656; bh=lUprxi3y60qpUZUOQRn5tDVQOgbidpH18lHAHHiaLbo=; l=2171; h=To:References:From:Date:In-Reply-To; b=BfKX62uJd9vt3eYU1p07cj+nieo/4vJzLNvCZ/7ye4vsrjx3jbkYLrW6Av92udp7Z +GznTjUH7zPWe3k0vTw1jHNYd/fNUTUEn7V0/UclLoXJ2tQj0aMLdAzoN9vScSInOB sy48nQHkMTbRiXFMHRaY/5rfps7fdJEKMcBooeRX5NapVZnI38NKcv1Q6seVM
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC07E.00000000601694F0.0000555B; Sun, 31 Jan 2021 12:30:56 +0100
To: dmarc@ietf.org
References: <db72db79-272e-5d52-8994-4da81c8723bd@tana.it> <20210129210006.063C66CF2279@ary.qy> <CAH48ZfxCpFjySAL06a9pDusX1FiuSuVsHkBZG-Zkvxgu3BJmcA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <49b248dc-91a7-7f2d-ba28-72fe8d6d356a@tana.it>
Date: Sun, 31 Jan 2021 12:30:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfxCpFjySAL06a9pDusX1FiuSuVsHkBZG-Zkvxgu3BJmcA@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/i1g-9gzW63KGgUci7BxsW7HFfiI>
Subject: Re: [dmarc-ietf] Report bombing is a prolem, Forensic report loops are not
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, 31 Jan 2021 11:31:03 -0000

On Sat 30/Jan/2021 13:51:56 +0100 Douglas Foster wrote:
> Interesting point.
> [...]
> 
> The spec is confusing because it says (a) failure reports should be sent
> immediately, (b) failure reports should be aggregated, and (c) failure
> reports should be throttled but without specifying a limit.
> 
> I wonder if the rule should be one message per week per source, since any
> large volume sender will be getting reports from multiple sources.   The
> main problem with this is that law enforcement actions may want to be
> bombed.


This point deserves its own ticket.  While we have a ri= tag (to be revised, 
see Tickets #50 and #71) and !size limits for aggregate reports, failure report 
consumers don't have a way to express the amount or frequency of feedback they 
want.


> On Fri, Jan 29, 2021 at 4:00 PM John Levine <johnl@taugh.com> wrote:
>> In article <db72db79-272e-5d52-8994-4da81c8723bd@tana.it> you write:
>>>3.3.  Transport
>>>
>>>    Email streams carrying DMARC failure reports MUST conform to the
>>>    DMARC mechanism, thereby resulting in an aligned "pass".  Special
>>>    care must be taken of authentication, as failure to authenticate
>>>    failure reports may provoke further reports.
>>
>>     Reporters SHOULD rate limit the number of failure reports sent
>>     to any recipient to avoid overloading recipient systems.


I haven't yet modified this, but I mostly agree.


>> Why would reports due to a mail loop be more of a problem than due to
>> some random spammer sending a lot of fake mail, or (real life) your
>> users send mail to mailing lists with thousands of subscribers? Rate
>> limit your reports, don't worry about where they came from.


Rate limiting usually implies a number of buckets.  They are managed by 
imposing limits per time periods, which can be either server-global or per 
bucket.  Normally, for MSA usage, one has one bucket per user.  I have never 
implemented failure reporting, but I'd guess buckets may vary.  Besides the 
signing domain (which determines the report consumer), the receiving address, 
the sender and the spam flag may deserve their own buckets.

Thoughts?

Best
Ale
-- 




























From nobody Sun Jan 31 04:01:44 2021
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 9DE303A0CAC for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 04:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level: 
X-Spam-Status: No, score=-2.121 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, URIBL_BLOCKED=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 bmvjhJ0teznx for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 04:01:41 -0800 (PST)
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 3644F3A0CA2 for <dmarc@ietf.org>; Sun, 31 Jan 2021 04:01:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612094496; bh=FAPA/0tXnTBl2nHjZ5ib6j6pZumSMVh+iX3C+ZfpYQc=; l=1139; h=To:References:From:Date:In-Reply-To; b=CWWHarhaqNm+IT+odI+9b94AVq+lTRuB9Pz/5c8UrD3yxdNzQy8cpyFgEER0NHfnU HPjpWF7z/xfKs5oHq45zlpt/t6bIK8Bh+Ns2ejBv1ye7qZDw+kfFEpIOtO7gv/8XXC LFFTf/zQn7rAOxjdtTlyMxUqCNFmsrHak8t5HPdO44iHOzlsY11xWcR6OD1Cd
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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.0000000060169C20.0000585F; Sun, 31 Jan 2021 13:01:36 +0100
To: John R Levine <johnl@taugh.com>, Jim Fenton <fenton@bluepopcorn.net>, dmarc@ietf.org
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net> <1edea785-2420-9812-643-c38bc4bf9577@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <16d8c498-9eb2-78c7-1cd3-e390c3e4d3cb@tana.it>
Date: Sun, 31 Jan 2021 13:01:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <1edea785-2420-9812-643-c38bc4bf9577@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/lJSVDeeHP5FVKe8NuNhcwfJ7K0A>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 31 Jan 2021 12:01:43 -0000

On Sat 30/Jan/2021 22:57:44 +0100 John R Levine wrote:
> 
> Part of the problem here is that DMARC generally sits on top of an SPF library 
> which doesn't tell you how it got its result.  My DMARC code just calls the SPF 
> library and uses the result.  I suppose I could put in a hack to say don't use 
> the SPF result if the MAIL FROM is null, but I don't think that's what 7489 says.


One way to interpret RFC 7489 is that you can put dmarc=pass based on the helo 
identity *only if* MAIL FROM is null.  So the hack there is a bit more tricky. 
  You want to use the SPF result only if MAIL FROM is null, except in cases 
when you authenticate based on MAIL FROM.  That's idiosyncratic!



On Sat 30/Jan/2021 20:59:13 +0100 Jim Fenton wrote:
> The fact that a message sender can put anything there makes HELO basically
> meaningless.


Here "message sender" has to be a mail server admin.  Compare with MAIL FROM, 
where "message sender" is the actual author submitting a message.  How come 
that the same assertion being more widely true for MAIL FROM doesn't make the 
latter basically meaningless?



Best
Ale
-- 






















From nobody Sun Jan 31 08:52:17 2021
Return-Path: <johnl@taugh.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 C0F403A10FC for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 08:52:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=ZpkDKETw; dkim=pass (2048-bit key) header.d=taugh.com header.b=lITUjCKt
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 Nb-bDX4ys7d9 for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 08:52:13 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 440343A10FA for <dmarc@ietf.org>; Sun, 31 Jan 2021 08:52:12 -0800 (PST)
Received: (qmail 71855 invoked from network); 31 Jan 2021 16:52:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=118ab.6016e03c.k2101; bh=L9yM6koyTeSy0C+p3+3SB/U+xVqj/fkAiUhFMJvtZUw=; b=ZpkDKETwe6VfEwRQwiR2nqKGdxmajBuamNR9k1Wc55faxoDLYqsIAk9VozYOra/s9wQ/rPWSqITAPNCOyN3qZCGkmkvyc6bvUnomtom8PLPEvZdnWcJZq2CKqFmxWsH1UB4+qma5aHnOYgPC66VHv3vqPKtskUUoP36RwdWMvTkaJHz+2IR0tBui10cdpVZsA7ktYpGBv+rAfYnv3cJ63z67KlneX6ZZ4GmSN45bB7U4dwO36MFmTLmrpimSbGmIFswMblTHq1ANou7qVTlCUdVtsSKcvhyh0sB0rX7CPZ+gzhKcEJhSbxf0c7RcEng8iPWFDrT6HXxjLzyOm2upYw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=118ab.6016e03c.k2101; bh=L9yM6koyTeSy0C+p3+3SB/U+xVqj/fkAiUhFMJvtZUw=; b=lITUjCKtNGOD1QIOSjJYCUB/AAQiAl2NwXFphK0D8axtTR6p06B5KEN1UKLy3Lf9iXa/KlTjlY2zUD9dtJi9mKGpu/Y8mGFxWO4Ptg9tvTHJoqk3t0oY6FXKh7QaA/jOhlsCgnyeze4F0ZwFe7qA8Vy/QiTuShqe2xzBR7ma+SiQEr8AQuzHC3ZwrCDeAht/qJE7j8S5Ljn0BQz/0DzQMkmSPzwCGENbjMuOjrcUCVdPkW0PSUGHH1aOX8XFVSazWD5YBQ34SoWEaFsEKRdrMjBJatOQv+9AG07r4HvumWXttgsuwG3JWcgNe31BlElSBJVhxuq/nQCrZJsQItliJw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 31 Jan 2021 16:52:11 -0000
Received: by ary.qy (Postfix, from userid 501) id 3E56B6D0FAF5; Sun, 31 Jan 2021 11:52:10 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id F38006D0FAD7; Sun, 31 Jan 2021 11:52:10 -0500 (EST)
Date: 31 Jan 2021 11:52:10 -0500
Message-ID: <36a1c70-875d-89c8-7e95-a32324654275@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, "Jim Fenton" <fenton@bluepopcorn.net>, dmarc@ietf.org
In-Reply-To: <16d8c498-9eb2-78c7-1cd3-e390c3e4d3cb@tana.it>
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net> <1edea785-2420-9812-643-c38bc4bf9577@taugh.com> <16d8c498-9eb2-78c7-1cd3-e390c3e4d3cb@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/fW72kxIrscwrMXOWA36jlU7EphA>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 31 Jan 2021 16:52:16 -0000

On Sun, 31 Jan 2021, Alessandro Vesely wrote:
> One way to interpret RFC 7489 is that you can put dmarc=pass based on the 
> helo identity *only if* MAIL FROM is null.

That would be consistent with 7489.

Sec 3.1.2 says

    Note that the RFC5321.HELO identity is not typically used in the
    context of DMARC (except when required to "fake" an otherwise null
    reverse-path), even though a "pure SPF" implementation according to
    [SPF] would check that identifier.

But then 4.1 says

    o  [SPF], which can authenticate both the domain found in an [SMTP]
       HELO/EHLO command (the HELO identity) and the domain found in an
       SMTP MAIL command (the MAIL FROM identity).  DMARC uses the result
       of SPF authentication of the MAIL FROM identity.  Section 2.4 of
       [SPF] describes MAIL FROM processing for cases in which the MAIL
       command has a null path.

That section of 7208 says that if there's a null bounce address, SPF 
pretends that the MAIL FROM was postmaster@HELO.

If we want, we can say not to use the SPF HELO identity, but that would be 
an incompatible change to 7489 and I suspect would not match what most 
DMARC checking code does.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Sun Jan 31 11:04:01 2021
Return-Path: <dougfoster.emailstandards@gmail.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 910013A11C3 for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 11:03:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 DR4bYTvY6Ibr for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 11:03:57 -0800 (PST)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC5F43A11C2 for <dmarc@ietf.org>; Sun, 31 Jan 2021 11:03:57 -0800 (PST)
Received: by mail-ua1-x92f.google.com with SMTP id a16so5140702uad.9 for <dmarc@ietf.org>; Sun, 31 Jan 2021 11:03:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=AV9vw3TKVsrOgtk20k7ZOxk3EcMehNKGuNbqSF8VIsU=; b=EpMmmC3MqRD2NVEE5UjRpdbRj2WgjlcfwXgnZM5MGy5AO69PH9qCplDK/G0aVLPxxo f0cB+a5AyHGrU4yWLA0+S8ow+ppN4ofuVZOA8Al8pOEr2/eV2iRBV867/20XbbYxmqjZ qAajqK40vp2Zz0UN0qsxoLhJmV6qrmsWVcXJawKIHXP9+elUtSrIj/qRArR/+2Srclj9 0M+I8qkJDDE616BUvnbfk116WmTxWRoZN6kx1JZfmsqXKCOj8VTjwjODYdGkhkJxeMO8 dvB1h+GuCzOcFlGz4NWyaGid9vMYwjhQ3IGz28Flu8miOgu7JqzWejrPQMwtMNrwFvBo O9wA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=AV9vw3TKVsrOgtk20k7ZOxk3EcMehNKGuNbqSF8VIsU=; b=f9AACp2jDVauZTAQBqJ1Vw39pbMb3dR6cOiqa2G36zW8Pc/T4onlKjoUMSCFR/tYdm /IHkv7/ndICiUXUesB+N/K3CvsWeURT9QHDzOUNERA3+G7MkhCK5/Vct2ctwQLXXS4XQ Hsy6YpHcjvBVKAfHzh13XMt3GhrstnApR5fZs53M5iPV8HiOefmSo5fLMpk2aiucZr5V bneItj0uCYSX1PLOY3G9qHLP+0UpJBy9TLeSSch3dRkqbdC/bVZ7aNAN8/sZ/Yx1sbAR CP51SLUXT/zBFjXJnr5tK8A7vnT7qg//LHZglkzTTETKPIc2B5+ojIVNBtt+FqsgQKzm JlDg==
X-Gm-Message-State: AOAM530awmbrNAJyagjnNiMVkoDogLeP2DC2f5g+fQTs0b3s2hZgS35i Iyfd4JaslIgO+r/qIhakOJn+5INTAXfqcWabl36T/zPvOYk=
X-Google-Smtp-Source: ABdhPJyAwYVKyA25vUyNK3M4U1h9BxcBDazJTJ/acYTZV840iKr1nCDq+XarRkaj3p4S3T4PInKW9PY+SwXOwbXf/I4=
X-Received: by 2002:ab0:7547:: with SMTP id k7mr7719081uaq.95.1612119836217; Sun, 31 Jan 2021 11:03:56 -0800 (PST)
MIME-Version: 1.0
References: <20210130212339.447316D04763@ary.qy> <66EB1EFC-753D-49FA-8652-BABB10397990@bluepopcorn.net> <1edea785-2420-9812-643-c38bc4bf9577@taugh.com> <16d8c498-9eb2-78c7-1cd3-e390c3e4d3cb@tana.it> <36a1c70-875d-89c8-7e95-a32324654275@taugh.com>
In-Reply-To: <36a1c70-875d-89c8-7e95-a32324654275@taugh.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sun, 31 Jan 2021 14:03:45 -0500
Message-ID: <CAH48ZfwBKyA-TwSrr2422zmMO8wr1CKf2MiQZ3KvQu2hOH=_CA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002c531b05ba36e615"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rUhOmqgwGIcz3FfCfQ9igk8mgOU>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 31 Jan 2021 19:04:00 -0000

--0000000000002c531b05ba36e615
Content-Type: text/plain; charset="UTF-8"

I don't see any justification for using HELO unless the SMTP address is
null.  If the SPF RFC says otherwise, this should be corrected.   Proving
that the server domain can be tied to the IP address does nothing to prove
that the SMTP address can be tied to the Source IP.

For DMARC, HELO is only useful if the message's From domain and the
server's HELO domain are aligned.  A high percentage of email domains use
servers from a different DNS domain, so this will only be true on an
exception basis..   Consequently, software products that apply DKIM
signatures to messages MUST be able to them to automatic messages as well.
 Once developers provide MTA and mailstore products which service the needs
of hosted domains, then users of non-hosted domains will be able to sign
their automatic messages as well.   Ergo, any supposed need for HELO with
DMARC will go away.

DF


On Sun, Jan 31, 2021 at 11:52 AM John R Levine <johnl@taugh.com> wrote:

> On Sun, 31 Jan 2021, Alessandro Vesely wrote:
> > One way to interpret RFC 7489 is that you can put dmarc=pass based on
> the
> > helo identity *only if* MAIL FROM is null.
>
> That would be consistent with 7489.
>
> Sec 3.1.2 says
>
>     Note that the RFC5321.HELO identity is not typically used in the
>     context of DMARC (except when required to "fake" an otherwise null
>     reverse-path), even though a "pure SPF" implementation according to
>     [SPF] would check that identifier.
>
> But then 4.1 says
>
>     o  [SPF], which can authenticate both the domain found in an [SMTP]
>        HELO/EHLO command (the HELO identity) and the domain found in an
>        SMTP MAIL command (the MAIL FROM identity).  DMARC uses the result
>        of SPF authentication of the MAIL FROM identity.  Section 2.4 of
>        [SPF] describes MAIL FROM processing for cases in which the MAIL
>        command has a null path.
>
> That section of 7208 says that if there's a null bounce address, SPF
> pretends that the MAIL FROM was postmaster@HELO.
>
> If we want, we can say not to use the SPF HELO identity, but that would be
> an incompatible change to 7489 and I suspect would not match what most
> DMARC checking code does.
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--0000000000002c531b05ba36e615
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t see any justification for using HELO unless th=
e SMTP address is null.=C2=A0 If the SPF RFC says otherwise, this should be=
 corrected.=C2=A0 =C2=A0Proving that=C2=A0the server domain can be tied to =
the IP address does nothing to prove that the SMTP address can be tied to t=
he Source IP.=C2=A0 =C2=A0=C2=A0<div><br></div><div>For DMARC, HELO is only=
 useful if the message&#39;s From domain and the server&#39;s HELO domain a=
re aligned.=C2=A0 A high percentage of email domains use servers from a dif=
ferent DNS domain, so this will only be true on an exception basis..=C2=A0 =
=C2=A0Consequently, software products that apply DKIM signatures to message=
s MUST be able to them to automatic messages as well.=C2=A0 =C2=A0Once deve=
lopers provide MTA and mailstore products which service the needs of hosted=
 domains, then users of non-hosted domains will be able to sign their autom=
atic messages as well.=C2=A0 =C2=A0Ergo, any supposed need for HELO with DM=
ARC will go away.</div><div><br></div><div>DF</div><div><br></div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, J=
an 31, 2021 at 11:52 AM John R Levine &lt;<a href=3D"mailto:johnl@taugh.com=
">johnl@taugh.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">On Sun, 31 Jan 2021, Alessandro Vesely wrote:<br>
&gt; One way to interpret RFC 7489 is that you can put dmarc=3Dpass based o=
n the <br>
&gt; helo identity *only if* MAIL FROM is null.<br>
<br>
That would be consistent with 7489.<br>
<br>
Sec 3.1.2 says<br>
<br>
=C2=A0 =C2=A0 Note that the RFC5321.HELO identity is not typically used in =
the<br>
=C2=A0 =C2=A0 context of DMARC (except when required to &quot;fake&quot; an=
 otherwise null<br>
=C2=A0 =C2=A0 reverse-path), even though a &quot;pure SPF&quot; implementat=
ion according to<br>
=C2=A0 =C2=A0 [SPF] would check that identifier.<br>
<br>
But then 4.1 says<br>
<br>
=C2=A0 =C2=A0 o=C2=A0 [SPF], which can authenticate both the domain found i=
n an [SMTP]<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0HELO/EHLO command (the HELO identity) and the do=
main found in an<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0SMTP MAIL command (the MAIL FROM identity).=C2=
=A0 DMARC uses the result<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0of SPF authentication of the MAIL FROM identity.=
=C2=A0 Section 2.4 of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0[SPF] describes MAIL FROM processing for cases i=
n which the MAIL<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0command has a null path.<br>
<br>
That section of 7208 says that if there&#39;s a null bounce address, SPF <b=
r>
pretends that the MAIL FROM was postmaster@HELO.<br>
<br>
If we want, we can say not to use the SPF HELO identity, but that would be =
<br>
an incompatible change to 7489 and I suspect would not match what most <br>
DMARC checking code does.<br>
<br>
Regards,<br>
John Levine, <a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@tau=
gh.com</a>, Taughannock Networks, Trumansburg NY<br>
Please consider the environment before reading this e-mail. <a href=3D"http=
s://jl.ly" rel=3D"noreferrer" target=3D"_blank">https://jl.ly</a><br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--0000000000002c531b05ba36e615--


From nobody Sun Jan 31 12:02:47 2021
Return-Path: <johnl@iecc.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 D8D153A1205 for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 12:02:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level: 
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=YSfb9oFj; dkim=pass (2048-bit key) header.d=taugh.com header.b=IKCd5lEx
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 jLAJD_wmsSYQ for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 12:02:43 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 22D693A10E4 for <dmarc@ietf.org>; Sun, 31 Jan 2021 12:02:42 -0800 (PST)
Received: (qmail 19004 invoked from network); 31 Jan 2021 20:02:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=4a38.60170cdf.k2101; bh=Nh0a+Kr2qC6dC7LaEVfKsRqVNgyTg1T7HBhzRv/S3Og=; b=YSfb9oFjvb0CEJoHWAB0p5fVPQF5S6sg2wJYY4ach4AJZAX0m5pXI7iT49e1YaUzlZPdOcgs4v7pca4CohTfJ7DLJrOoVgcp3RKFWaxTcNwpVFCUb10X6BOX6M9ZNbS6GyY1nQ1ihR7s+qCzfy4WbVrArxz9jDGtBQhFG9wV42+VKC3FlQfavQs/kSSvh14o5/RUai/Fk56zkXEm/QyhiJ+XGG5Vr4Pi7H2SsOFWFk4OYBQCU1x/qwvrUHbz5yOjJkM0B6XJufrpq52kmcl0ywMcCasHna9ZkUUcHn1WrGBMYFR2qfh+7DMFm8D2UQ+Pa3XGkRfWU6t+KFUG1lVLTA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=4a38.60170cdf.k2101; bh=Nh0a+Kr2qC6dC7LaEVfKsRqVNgyTg1T7HBhzRv/S3Og=; b=IKCd5lEx+luUMwQugOOSGiuM8o+33pqf8hSRQverZeG3pw8+LSIaGZ5z8jt9H/5hlRHE7xY/3J9+QjSBNitOhEev1aYc9L71sX0FkpdrIhkMU3hX/gTzOFJRX8n3qxBkkKS5a5blgDsrBV0Y7SNfLLGmEUFl6S0pawX/gqhwCJnhILRaGsV4ejWmTpTasjkL5cgy2R3IhiILjtoVzr+CZYkYnxfDsjNF2+qLakgF6eN2xSg1WKx2KKkk5GZ6Xrmc71I2I7g+UhSRtEHNuPGg5/CFYoLTn0pIXdP9vB/jp1WrKpcnp0o+w/2kJH7KM4zz6f7CvVbGHC8E6pa9wWvJag==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 31 Jan 2021 20:02:39 -0000
Received: by ary.qy (Postfix, from userid 501) id 931356D11D79; Sun, 31 Jan 2021 15:02:38 -0500 (EST)
Date: 31 Jan 2021 15:02:38 -0500
Message-Id: <20210131200238.931356D11D79@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <49b248dc-91a7-7f2d-ba28-72fe8d6d356a@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/O_BqKx56WMwMP-lLUKp9mjgigKk>
Subject: Re: [dmarc-ietf] Report bombing is a prolem, Forensic report loops are not
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, 31 Jan 2021 20:02:45 -0000

In article <49b248dc-91a7-7f2d-ba28-72fe8d6d356a@tana.it> you write:
>Rate limiting usually implies a number of buckets.  They are managed by 
>imposing limits per time periods, which can be either server-global or per 
>bucket.  Normally, for MSA usage, one has one bucket per user.  I have never 
>implemented failure reporting, but I'd guess buckets may vary.  Besides the 
>signing domain (which determines the report consumer), the receiving address, 
>the sender and the spam flag may deserve their own buckets.

The only one that matters for DMARC reporting is the recipient
address, since the purpose of rate limiting is to avoid overloading
the recipient mail system. I wouldn't worry about trying to send a
"representative" set of reports.

Keep in mind that very few people send failure reports at all. In my
experience few of them are useful. Most of mine are ordinary mailing
list messages where the failure is not surprising and does not mean
that anything needs to be fixed.

R's,
John


From nobody Sun Jan 31 16:10:07 2021
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 0E6F73A1420 for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 16:10:06 -0800 (PST)
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=qSlqrajB; dkim=pass (2048-bit key) header.d=kitterman.com header.b=NtZ+G1Mm
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 YeWi35F6Au6U for <dmarc@ietfa.amsl.com>; Sun, 31 Jan 2021 16:10:03 -0800 (PST)
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 1488F3A141B for <dmarc@ietf.org>; Sun, 31 Jan 2021 16:10:02 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id B9865F80295 for <dmarc@ietf.org>; Sun, 31 Jan 2021 19:10:01 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1612138201; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=JJ9q+7I8qJ6vx29dQ7hcaIJg5oGBj/dmeKs5ZFy3GbQ=; b=qSlqrajB8TjQZZveUoSTOtysYsrHFdiD+urJaXCxaFIPeHEKiy/I1C0rf8CG56VR+sJ+d rmkiZfGFM1JCO1mDA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1612138201; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=JJ9q+7I8qJ6vx29dQ7hcaIJg5oGBj/dmeKs5ZFy3GbQ=; b=NtZ+G1MmPk7MvQaS872v5Lp+KEVKeLWDdjnQOPYOoDpjIantw5xgfe4TJp6A65T86cBtX FSnsVEdqtpcnKF+fGdPort47DZ/KUk95meJN3SnaemNyb4Xq6BSe/axyaXOhZu2RpI6sSAy CxSgwJwqtjwJpFf6heW06AqHLCNAgISCAfe5kx75M+hOF7srQwYgNEJCYxyt5xWV4MppwN9 5GDBnuTtyZYJULjHgN4Zazhn/i3Ukm4Af07EzXlBCAML57WeEktrUVnDcDK8RQaSgsFf+45 QFg0td6nTqYtMBjwjkFxcqHoKGlkfm9P986q9/jKHlPP23uRhzD/vXynTUAg==
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 7F511F80208 for <dmarc@ietf.org>; Sun, 31 Jan 2021 19:10:01 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sun, 31 Jan 2021 19:10:01 -0500
Message-ID: <1654196.ygyh55z74P@zini-1880>
In-Reply-To: <CAH48ZfwBKyA-TwSrr2422zmMO8wr1CKf2MiQZ3KvQu2hOH=_CA@mail.gmail.com>
References: <20210130212339.447316D04763@ary.qy> <36a1c70-875d-89c8-7e95-a32324654275@taugh.com> <CAH48ZfwBKyA-TwSrr2422zmMO8wr1CKf2MiQZ3KvQu2hOH=_CA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qRSbgEg6l7AaNWUYApzJle6uBz4>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 01 Feb 2021 00:10:06 -0000

I think that we're well past learning anything new in this thread.

SPF is what it is (RFC 7208).  DMARC doesn't need to re-invent the protocol 
(and shouldn't).  For any properly implemented SPF verifier, DMARC should be 
able to consume the Mail From result.  End of story.

I'd suggest close the ticket and move on.

Scott K

On Sunday, January 31, 2021 2:03:45 PM EST Douglas Foster wrote:
> I don't see any justification for using HELO unless the SMTP address is
> null.  If the SPF RFC says otherwise, this should be corrected.   Proving
> that the server domain can be tied to the IP address does nothing to prove
> that the SMTP address can be tied to the Source IP.
> 
> For DMARC, HELO is only useful if the message's From domain and the
> server's HELO domain are aligned.  A high percentage of email domains use
> servers from a different DNS domain, so this will only be true on an
> exception basis..   Consequently, software products that apply DKIM
> signatures to messages MUST be able to them to automatic messages as well.
>  Once developers provide MTA and mailstore products which service the needs
> of hosted domains, then users of non-hosted domains will be able to sign
> their automatic messages as well.   Ergo, any supposed need for HELO with
> DMARC will go away.
> 
> DF
> 
> On Sun, Jan 31, 2021 at 11:52 AM John R Levine <johnl@taugh.com> wrote:
> > On Sun, 31 Jan 2021, Alessandro Vesely wrote:
> > > One way to interpret RFC 7489 is that you can put dmarc=pass based on
> > 
> > the
> > 
> > > helo identity *only if* MAIL FROM is null.
> > 
> > That would be consistent with 7489.
> > 
> > Sec 3.1.2 says
> > 
> >     Note that the RFC5321.HELO identity is not typically used in the
> >     context of DMARC (except when required to "fake" an otherwise null
> >     reverse-path), even though a "pure SPF" implementation according to
> >     [SPF] would check that identifier.
> > 
> > But then 4.1 says
> > 
> >     o  [SPF], which can authenticate both the domain found in an [SMTP]
> >     
> >        HELO/EHLO command (the HELO identity) and the domain found in an
> >        SMTP MAIL command (the MAIL FROM identity).  DMARC uses the result
> >        of SPF authentication of the MAIL FROM identity.  Section 2.4 of
> >        [SPF] describes MAIL FROM processing for cases in which the MAIL
> >        command has a null path.
> > 
> > That section of 7208 says that if there's a null bounce address, SPF
> > pretends that the MAIL FROM was postmaster@HELO.
> > 
> > If we want, we can say not to use the SPF HELO identity, but that would be
> > an incompatible change to 7489 and I suspect would not match what most
> > DMARC checking code does.
> > 
> > Regards,
> > John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> > Please consider the environment before reading this e-mail. https://jl.ly
> > 
> > _______________________________________________
> > dmarc mailing list
> > dmarc@ietf.org
> > https://www.ietf.org/mailman/listinfo/dmarc




